CN1315307C - Method for transmission using Mbus communication middle ware - Google Patents
Method for transmission using Mbus communication middle ware Download PDFInfo
- Publication number
- CN1315307C CN1315307C CNB2004100704932A CN200410070493A CN1315307C CN 1315307 C CN1315307 C CN 1315307C CN B2004100704932 A CNB2004100704932 A CN B2004100704932A CN 200410070493 A CN200410070493 A CN 200410070493A CN 1315307 C CN1315307 C CN 1315307C
- Authority
- CN
- China
- Prior art keywords
- message
- send
- mbus
- transmission
- judge
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Images
Landscapes
- Computer And Data Communications (AREA)
- Small-Scale Networks (AREA)
Abstract
The present invention provides a method for transmission by Mbus communication middleware, which comprises the steps: (A), a Mbus instruction is transmitted to an application layer of a transmission party; (B), a structural layer is used for encapsulating the Mbus instruction to be transmitted by a user and a designated destination address in a message of a specific type; (C), then, the message is coded into bytes on a coding layer for circulation over a physical network; a TCP protocol is used for transmitting the bytes to a server; (D), after a byte flow is decoded on a server end, addressing is carried out according to the destination address of the message; subsequently, codes are transmitted to a matched receiver; (E), the receiver decodes the codes; finally, the extracted Mbus instruction is transmitted to the application layer for processing the Mbus instruction.
Description
Technical field
The present invention relates to a kind of method of utilizing middleware to transmit, especially relate to the method that a kind of Mbus of utilization (The Message Bus) lightweight inter-module communication middleware transmits.
Background technology
J.Ott, C.Perkins and D.Kutscher have proposed local co-ordination message bus (A Message Bus forLocal Coordination) in the RFC 3259 that delivers in April, 2002, it is underload, a message-oriented communication matchmaking protocol between a plurality of assemblies in the application program.This agreement has proposed good address representation and addressing strategies, and the typical application field is communicating by letter of local meeting control and the interior equipment group of local area network (LAN).It for the assembly on one or more main frame in the local area network (LAN) provide one simply, message communicating channel flexibly, have characteristics such as reciprocity location, point-to-point communication, cluster communication and safety assurance, be applied to coordinate each application function assembly in fields such as distributed multimedia conference system, home network pervasive computing environments at present.But its transmission mechanism is not supported the coordination control on the wide area network on a large scale: owing to used the multicast in this machine scope that message is sent to all native object, therefore each entity is no matter need all must receive and differentiate this message, and the message number when local entity number and transmission can obviously reduce system effectiveness more for a long time like this; It realizes reliable transmission by simple overtime re-transmission policy, this is also relatively more effective in local area network (LAN), but because the uncertainty of Internet propagation delay time, the mode of this non-self-adapting can not guarantee accurate reliable semantic when crossing over local area network (LAN) border and Remote Node RN communication; Because entity perception, state-maintenance and transmission of messages all rely on and aware transport layer multicast, but not all router is all supported multicast in the present network, and this has further limited its application.
In view of local co-ordination message bus good practicality in based on the local multimedia conference system of assembly, Mbus lightweight inter-module communication middleware has been used for reference its address representation in design process, solved the above-mentioned variety of issue that it runs into simultaneously when crossing over the local area network (LAN) border, and user interface carried out reasonable optimizing, for each assembly of advanced multimedia real-time interaction system Admire provides the bottom transmission platform.Because with the issue of the form of middleware, the interface that taken into full account user's needs, good design has shielded the content relevant with particular system, thus it can be widely used in need be quasi real time, reliably or in the distributed system of group communication.
Summary of the invention
At top description, the present invention proposes the method that a kind of Mbus of utilization communication middleware transmits, the method comprising the steps of: (A) application layer at transmit leg sends the Mbus order; (B) techonosphere is encapsulated in Mbus order and the location, designated destination that user's desire sends in the message of particular type; (C) be that byte stream utilizes Transmission Control Protocol to be transferred to server by physical network with message coding after this at the coding layer; (D) byte stream carries out addressing according to the message destination address after server end is decoded, and coding sends to the recipient of coupling subsequently; And (E) recipient decodes again, and the Mbus order of extracting is the most at last sent with charge free to application layer and handled.
According to an aspect of the present invention, wherein server is further carried out following processing: (a) judge in the message of being constructed whether specified MAC Address, if specified then execution in step (b), then do not go to step (c) if specify; (b) judge whether to equal this machine MAC Address; (c) judge that type of message is REL, RPC message or COM message, if the COM message, then send to coupling local client, send to central server, send to coupling the purpose transponder, send to the purpose client.
According to a further aspect in the invention, wherein step (b) further comprises following processing: (b1) if equaling this machine MAC Address then carries out (b2), then carry out (b3) if be not equal to this machine MAC Address; (b2) judge it is REL, RPC message or COM message, if COM message, then send to the local client of coupling, if REL, RPC message, judge then whether the destination address number is unique, if not unique then the structure reply and send, if unique then send to the given client end and under the situation that structure is replied, send reply; (b3) send to central server and judge whether to send successfully, do not reply if sends successfully then transmission; If send to judge then successfully whether the destination address number is unique, if not unique then structure is replied and sent; If uniquely then send to specific transponder and judge whether to send successfully, if the then transmission that gets nowhere is replied; If then sending to the client of appointment and send under the situation that structure is replied, success replys.
According to a further aspect in the invention, wherein step (c) comprises that further (c1) if type of message is REL, RPC message, then carries out above-mentioned steps (b3).
Description of drawings
Fig. 1 has provided the structural representation of MBUS system;
Fig. 2 has provided the flow chart according to transmission message procedure of the present invention;
Fig. 3 has provided the schematic diagram according to MBUS command transfer of the present invention;
Fig. 4 has provided the schematic diagram of safeguarding according to system mode of the present invention;
Embodiment
To following we with reference to the accompanying drawings, embodiments of the invention are described in detail.
Mbus lightweight inter-module communication middleware can provide flexibly for the coordination control command based on each inter-module in the multimedia conference system of assembly, the distributed system, bottom transmission platform efficiently, make each assembly on upper strata from the network service of complexity, free the problem that solves its field itself to be absorbed in, the realization that this has improved the stability and the robustness of system to a certain extent and has simplified system.Mbus supports multiple interactive mode and reliability requirement, can finish following function:
● transmit mode and control information in real time between local and long-range assembly, to realize the interoperability of distributed objects;
● support addressing strategies flexibly, can send to single destination address, also can send to a plurality of destination addresses and realize group communication according to mode addressing such as position, component type;
● can satisfy different reliability requirements, realize three kinds of transmission meanss of unreliable transmission, reliable transmission, remote procedure call of order;
● query function is provided, and each entity can exist situation and accurate complete match address according to what certain geologic condition was inquired about other entities.
● take certain security strategy, can prevent to be subjected to the attack of unexpected interference or malice;
Accompanying drawing 1 has provided Mbus lightweight inter-module communication middleware system structure chart.It is based on C/S model, local a plurality of clients of transponder management of operation on every machine, and each transponder is connected to the global transmission that central server in the system is finished data again simultaneously.Communicate by shared drive between client of this machine and the transponder, then connect between transponder and the central server and communicate by TCP, like this by with reply to combine the system of having guaranteed accurate reliable semantic under the uncertain Internet environment of time delay.
Command format, message format, addressing strategies, transmission policy, state perception mechanism and security mechanism with regard to Mbus lightweight inter-module communication middleware describes respectively below.
◆ command format
Mbus order is made up of command header and 0 or a plurality of parameter, and its general form is:＜object〉.qry|req|ack.＜operation〉＜arg0〉＜arg1〉...＜argn 〉.Wherein＜and object〉.qry|req|ack.＜operation〉constitute command header, in order to form the order of conceptual dependency on a common level, command header is cut apart classification with ". " and is made up;＜arg0 〉～＜argn〉constitute command parameter, with space-separated, in arbitrary parameter as the space occurs, must this parameter be caused between parameter, between parameter and the command header with double quotation marks.In command header＜and object〉refer to respond inquiry, receive order or send the object of replying; The classification of qry, req and ack marking command: querying command, operational order and acknowledgement command;＜operation〉then be the command id that defines voluntarily by each Mbus object, be used for identifying various user's operations.The user can define the Mbus order by form according to the rules voluntarily, and number of parameters is not limit.
◆ addressing strategies
The Mbus address is used for Mbus object of unique identification in global scope, is the mark address element sequence that (order of acquiescence, not explicit writing out)/the value binary is right, is separated by colon between each value.As follows:
Meeting name: medium type: module type: apply names: position: process ID: MAC Address
Used the MAC Address of process ID and machine at this, like this in conjunction with first five items necessarily can be in global scope Mbus entity of unique identification.Two Mbus addresses equate that and if only if, and their address character string equates (case sensitive), and Mbus address A and Mbus address B are complementary, and then to be address A be made of the subclass order according to the rules of the address element of address B.As: Mbus address " Admire:All:Service:Gateway:Center:1012:00-E0-18-D5-01-22 " and Mbus address " Admire:All:Service:Gateway:Center:1012:00-E0-18-D5-01-22 " equates, and Mbus address " Admire::::Center::00-E0-18-D5-01-22 " is complementary with " Admire:::Gateway:Center::00-E0-18-D5-01-22 ".The destination address of Mbus message can be specified fully, also can vacancy wherein any, by the matching addresses mode realization group communication of application layer, the message that each Mbus object processing intent address and itself address equate fully or be complementary.
◆ message format
The Mbus order is encapsulated in the Mbus message to be transmitted on network, and message is made up of heading and message body two parts.Heading comprises following information: source address, destination address, type of message and sequence number, various piece with ' n ' cut apart.Source address and destination address are the Mbus address, source address field identification message sender wherein, and this must be all accurate addresses of appointment of all address element; The expection recipient of destination address domain identification message, some address element can be ignored to mate a plurality of receiving entities in this territory.The Mbus message is divided into 7 classes: send to a plurality of recipients common message (COM), require reliable transmission reliable message (REL), need the recipient to provide far call message (RPC), the response message (AEL) of reliable message, the response message (APC) of far call message, system message (SYS), the logins/logoffs message (LOG) of explicit result.Sequence number is 32 a signless integer, and all message that sends from same source has unique sequence number, serial number range from 0 to 4294967295.The message body has then stipulated to send to the actual Mbus order of destination entity or the particular value that returns, in order to realize only containing a Mbus order in simple each message or reply.Here introduce the encoding and decoding dictionary in order to reduce the network bandwidth, when sending, some frequent Mbus order and address element that occur have been encoded, submitted to the user again after the recipient decodes accordingly.
◆ transmission policy
Because the network of Domestic support multicast is not popularized at present, can cause system's dependence and dispose the single multicast transfer gateway, and under the uncertain time delay environment of Internet, can not guarantee accurate reliable semantic with the reliable transmission strategy that simple overtime retransmission mechanism is realized, also will relate to problems such as passing fire wall simultaneously, Mbus lightweight inter-module communication middleware adopts C/S model to realize based on Transmission Control Protocol.System configuration as shown in Figure 1.Here transponder and central server are independent executable program, and client is embodied as automation component, can call the turn use at the program design language of any support automation, and system has realized language independent in this way.
Consider in actual applications and have a plurality of client collaborative works on every machine, having simultaneously much is to carry out in this machine different clients alternately, and Mbus lightweight inter-module communication middleware takes out a transponder and is in charge of local a plurality of clients on every the machine that participates in service.This has alleviated the pressure of last layer in the architecture on the one hand, because local a plurality of clients externally show as a communication link, local interaction is finished by transponder needn't be via last layer; Simplify client by some complicated functions are focused on transponder on the other hand, improved the performance of system for the situation of a plurality of clients of needs especially; All send to the transponder of this machine simultaneously owing to all message earlier, and then send to specific purpose client by transponder, meaningless inspection has improved performance thereby this has been avoided irrelevant client.
Pass through shared drive message transmission efficiently between client of this machine and the transponder; Then setting up TCP between transponder and the central server connects.All messages that client sends send to central server by Transmission Control Protocol then via the transponder of shared drive to this machine, and central server is issued the pairing transponder of destination address, arrives the purpose client at last.For the message destination address that simply requires reliable transmission on realizing must be unique, at this moment each grade transmission all needs to check the return value of transmission, if the failure would construct response message notification source sender, also need send after the last success and reply: if reliable message (REL) is then sent by transponder, this is transparent concerning the user; If remote procedure call message (RPC) is then by the explicit transmission result of user, this is replying as source messages simultaneously also.
The user can realize flexile cluster communication by specifying suitable destination address, as sends to specific meeting, specific media module or specific application.By repeatedly transport layer clean culture realization, this type of message does not send and replys the communication of application layer group at bottom, but owing to is that the TCP transmission has also guaranteed very high reliability.
After application layer sent the Mbus order, system need be encapsulated in it in the Mbus message and encode to transmit on network, and server end also needs to decode after receiving message, is addressed to corresponding recipient according to the address matching strategy then.The complete transmission process of Mbus order as shown in Figure 3.
Here adopt stratification thought, lower floor provides service for the upper strata, allows each layer to change its inner realization under the immovable situation of service interface, thereby has improved the extensibility of system.Wherein each following layer of application layer belongs to the inside realization of lightweight inter-module communication middleware Mbus, is transparent to the user.A group interface that provides by Mbus the application layer user uses the function of Mbus, techonosphere is encapsulated in the Mbus order and the location, designated destination of user's desire transmission in the message of particular type, is that byte stream utilizes Transmission Control Protocol to be transferred to server by physical network at the coding layer with message coding then; Byte stream carries out addressing according to the message destination address after server end is decoded, coding sends to the recipient of coupling subsequently; The recipient decodes again, and the Mbus order of extracting is the most at last sent with charge free to application layer and handled.
Detailed process when sending message as shown in Figure 2, server is further carried out following processing: (a) judge in the message of being constructed whether specified MAC Address, if specified then execution in step (b), then do not go to step (c) if specify; (b) judge whether to equal this machine MAC Address; (c) judge that type of message is REL, RPC message or COM message, if the COM message, then send to coupling local client, send to central server, send to coupling the purpose transponder, send to the purpose client.
Wherein step (b) further comprises following processing: (b1) if equaling this machine MAC Address then carries out (b2), then carry out (b3) if be not equal to this machine MAC Address; (b2) judge it is REL, RPC message or COM message, if COM message, then send to the local client of coupling, if REL, RPC message, judge then whether the destination address number is unique, if not unique then the structure reply and send, if unique then send to the given client end and under the situation that structure is replied, send reply; (b3) send to central server and judge whether to send successfully, do not reply if sends successfully then transmission; If send to judge then successfully whether the destination address number is unique, if not unique then structure is replied and sent; If uniquely then send to specific transponder and judge whether to send successfully, if the then transmission that gets nowhere is replied; If then sending to the client of appointment and send under the situation that structure is replied, success replys.
Wherein step (c) comprises that further (c1) if type of message is REL, RPC message, then carries out above-mentioned steps (b3).
Accompanying drawing 4 is the state-maintenance figure of Mbus lightweight inter-module communication middleware system.Server all can obtain notice by system command when client establishment, destruction or implicit expression withdrawed from, simultaneously server also monitor with transponder between TCP is connected, when detect connect disconnect after the state of renewal self.
◆ the state perception
The central server of Mbus lightweight inter-module communication middleware is safeguarded addressing and the transmission that global state information is arranged and be responsible for message, and the user can obtain the reliable transmission (guarantee destination address unique) of accurate address to carry out message of certain Mbus object by specific interface.The multiple strategy of system synthesis comes the correctness (accompanying drawing 4) of maintain global state:
Can pass through system command " mbus.notify.clientadd " when at first, client is created and destroyed and " mbus.notify.cientdrop " is explicit reports to server.
Secondly, transponder monitors the process handle of client, reports to server after client implicit expression withdraws from when detecting.
The 3rd, server also monitor with transponder between TCP be connected, corresponding with it transponder record is deleted from effort scale after connect disconnecting when detecting.
The 4th, since TCP connect unexpected disconnect the back server can not very fast detecting (test result show will above 30 minutes), therefore server is by periodically sending the testing process that heartbeat message is accelerated to disconnect to transponder, the server per second sends a message to a transponder when realizing in order to prevent to take too many resource, the unexpected disconnection detection time can taper to 200 seconds (100 transponders connect simultaneously, the corresponding shortening of meeting detection time during the transponder decreased number) under increase dozens of bps bandwidth cost like this.
The state perception mechanism that adopts in the Mbus lightweight inter-module communication middleware is more timely more and efficient than the periodic heartbeat message mechanism in the local co-ordination message bus.
◆ security mechanism
In order to prevent the interference of the unexpected or malice of other program, the Mbus object can be specified password.The Mbus object is if to the object transmit operation order that is provided with password, must at first login this object, otherwise this operational order is disregarded.Continuously effective after login is finished is nullified login or Mbus object destruction itself up to the Mbus object.The quantity that the Mbus object is logined simultaneously and is logged without limits.In addition, also can encrypt and authenticate fail safe to the message of transmission with further assurance message transfer.
Because the design object of Mbus lightweight inter-module communication middleware is transmit mode and control information between each assembly or application program, these information loads are generally all not too large, so central server can't become system bottleneck.Through test repeatedly under variety of network conditions, Mbus lightweight inter-module communication middleware can well be finished intended function, and reach good performance, can be widely used in network multimedia conference system, the distributed system, coordinate the bottom transmission platform of control command as them.
Mbus lightweight inter-module communication middleware has obtained sufficient application in advanced multimedia real-time interaction system Admire at present.The Admire system makes up based on modularity, comprise audio-frequency module CAT, video sending module VideoSender, video reception module VicAdmire, file sharing module FileShare, webpage sharing module WebShare, GUI modules A dmireUI etc., also have media gateway MediaGW, audio frequency net gate way AGW, video gateway VGW, Control Server ControlServer and H323 interworking module H323Redir etc. simultaneously as service operation.All embedded the Mbus client in these assemblies and the service routine, by Mbus lightweight inter-module communication middleware quasi real time the self-defining various control commands of transmission procedure and state information between this machine or long-range each module, reach the operate as normal of whole system.Through large-scale test and actual for a long time the use, the operation of Admire system is normal, and Mbus lightweight inter-module communication middleware can well be finished the communication task between each assembly and the service routine.
What may be obvious that for the person of ordinary skill of the art draws other advantages and modification.Therefore, the present invention with wider aspect is not limited to shown and described specifying and exemplary embodiment here.Therefore, under situation about not breaking away from, can make various modifications to it by the spirit and scope of claim and the defined general inventive concept of equivalents thereof subsequently.
Claims (4)
1, the method transmitted of a kind of Mbus of utilization communication middleware, the method comprising the steps of:
(A) application layer at transmit leg sends messaging bus Mbus order;
(B) techonosphere of lightweight inter-module communication middleware Mbus is encapsulated in Mbus order and the location, designated destination that user's desire sends in the message of particular type;
(C) be that byte stream utilizes Transmission Control Protocol to be transferred to server by physical network with message coding after this at the coding layer of lightweight inter-module communication middleware Mbus;
(D) byte stream carries out addressing according to the message destination address after server end is decoded, and coding sends to the recipient of coupling subsequently; And
(E) recipient decodes again, and the Mbus order of extracting is the most at last sent with charge free to application layer and handled.
2, method according to claim 1, wherein the server in the step (D) is further carried out following processing:
(a) judge in the message of being constructed whether specified MAC Address,, then do not go to step (c) if specify if specified then execution in step (b);
(b) judge whether to equal this machine MAC Address;
(c) judge that type of message is reliable REL, remote procedure call RPC message or common COM message, if common COM message, then send to coupling local client, send to central server, send to the purpose transponder of coupling and send to the purpose client.
3, method according to claim 2, wherein step (b) further comprises following processing:
(b1), then carry out (b3) if be not equal to this machine MAC Address if equaling this machine MAC Address then carries out (b2);
(b2) judge it is REL, RPC message or COM message, if COM message, then send to the local client of coupling, if REL, RPC message, judge then whether the destination address number is unique, if not unique then the structure reply and send, if unique then send to the given client end and under the situation that structure is replied, send reply;
(b3) send to central server and judge whether to send successfully, do not reply if sends successfully then transmission; If send to judge then successfully whether the destination address number is unique, if not unique then structure is replied and sent; If uniquely then send to specific transponder and judge whether to send successfully, if the then transmission that gets nowhere is replied; If then sending to the client of appointment and send under the situation that structure is replied, success replys.
4, method according to claim 3, wherein step (c) comprises that further (c1) if type of message is REL, RPC message, then carries out above-mentioned steps (b3).
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2004100704932A CN1315307C (en) | 2004-08-05 | 2004-08-05 | Method for transmission using Mbus communication middle ware |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2004100704932A CN1315307C (en) | 2004-08-05 | 2004-08-05 | Method for transmission using Mbus communication middle ware |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1588913A CN1588913A (en) | 2005-03-02 |
| CN1315307C true CN1315307C (en) | 2007-05-09 |
Family
ID=34604477
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2004100704932A Expired - Fee Related CN1315307C (en) | 2004-08-05 | 2004-08-05 | Method for transmission using Mbus communication middle ware |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1315307C (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109981554B (en) * | 2017-12-28 | 2021-11-02 | 北京京东乾石科技有限公司 | Information processing method and system and electronic equipment |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6691151B1 (en) * | 1999-01-05 | 2004-02-10 | Sri International | Unified messaging methods and systems for communication and cooperation among distributed agents in a computing environment |
| CN1510881A (en) * | 2002-12-20 | 2004-07-07 | ���µ�����ҵ��ʽ���� | Control traffic compression method |
| CN1518290A (en) * | 2003-01-15 | 2004-08-04 | Expandable communication control piece |
-
2004
- 2004-08-05 CN CNB2004100704932A patent/CN1315307C/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6691151B1 (en) * | 1999-01-05 | 2004-02-10 | Sri International | Unified messaging methods and systems for communication and cooperation among distributed agents in a computing environment |
| CN1510881A (en) * | 2002-12-20 | 2004-07-07 | ���µ�����ҵ��ʽ���� | Control traffic compression method |
| CN1518290A (en) * | 2003-01-15 | 2004-08-04 | Expandable communication control piece |
Non-Patent Citations (1)
| Title |
|---|
| 基于消息中间件的网络协同编辑环境框架 宋捷，于敏，华中科技大学学报(自然科学版)，第31卷 2003 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1588913A (en) | 2005-03-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109687995B (en) | CoAP-based OPC UA message transmission method suitable for resource-limited industrial field equipment | |
| US6678735B1 (en) | Method and apparatus for a sip client manager | |
| CN106059848B (en) | Electric power data acquisition transmission process system and method based on Big Dipper short message communication | |
| Li et al. | Research based on OSI model | |
| US10313410B2 (en) | Systems and methods using binary dynamic rest messages | |
| US7254601B2 (en) | Method and apparatus for managing intelligent assets in a distributed environment | |
| CN109217983B (en) | Industrial Internet of things operation terminal communication protocol design method | |
| CN1507734A (en) | Generic external proxy | |
| CN1783882A (en) | Flexibly transferring typed application data | |
| CN1842075A (en) | Using subqueues to enhance local message processing | |
| CN101136943A (en) | System and method for implementing extended Diameter protocol application | |
| CN103532959A (en) | Cross-platform network communication method | |
| CN102055774B (en) | Based on http server and the data processing method thereof of bag process | |
| CN108429729B (en) | Data communication isolation system and isolation method in industrial big data acquisition environment | |
| CN1315307C (en) | Method for transmission using Mbus communication middle ware | |
| CN101500210B (en) | Instant communication method with low transmission load based on XMPP protocol and system thereof | |
| CN101068257A (en) | Immediate communication platform | |
| CN102387123B (en) | Remote desktop system and method for optimizing X protocol | |
| CN103916827A (en) | Method for acquiring message, method for transmitting message and method for processing message | |
| Klauck | Seamless integration of smart objects into the internet using XMPP and mDNS/DNS-SD | |
| CN112468513A (en) | Terminal management communication protocol architecture of enterprise network | |
| CN101888315A (en) | Network type alarming host under intelligent platform and networking fortifying method thereof | |
| US8276158B2 (en) | HTTP based bounding storage space protocol | |
| CN101883144B (en) | File breakpoint continuously-transmitting method based on SIP (Session Initiation Protocol) | |
| Green et al. | Resource-constrained Industrial Things-Proposal for the Adaptation of CoAP to EtherNet/IP™ |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20070509 Termination date: 20160805 |