CN102638582A - Data communicating method and communication end - Google Patents

Data communicating method and communication end Download PDF

Info

Publication number
CN102638582A
CN102638582A CN2012101067527A CN201210106752A CN102638582A CN 102638582 A CN102638582 A CN 102638582A CN 2012101067527 A CN2012101067527 A CN 2012101067527A CN 201210106752 A CN201210106752 A CN 201210106752A CN 102638582 A CN102638582 A CN 102638582A
Authority
CN
China
Prior art keywords
service
transport layer
plurality
shared data
conversation
Prior art date
Application number
CN2012101067527A
Other languages
Chinese (zh)
Other versions
CN102638582B (en
Inventor
胡汉强
Original Assignee
华为技术有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN201210106752.7A priority Critical patent/CN102638582B/en
Publication of CN102638582A publication Critical patent/CN102638582A/en
Application granted granted Critical
Publication of CN102638582B publication Critical patent/CN102638582B/en

Links

Abstract

The invention provides a data communicating method and a communication end. The method comprises the steps that: a connectionless-oriented transport layer shared data channel is built between a source communication end and a target communication end on the basis of connectionless-oriented transport layer shared data communication port; and the source communication end conducts interaction of business messages of a plurality of business sessions with the target communication end through the connectionless-oriented transport layer shared data channel. According to the invention, through building the connectionless-oriented transport layer shared data channel between the source communication end and the target communication end, and carrying a session identifier of the belonged business session in the interacted business messages, the business messages of a plurality of business session can be intersected between the source communication end and the target communication end through a data channel, and the problems of more concurrent connections, large connection pressure and low data channel utilization rate between the source communication end and the target communication end under a large number of concurrent business requests in the prior art can be solved.

Description

Data communications method and communication ends

Technical field

The embodiment of the invention relates to the communication technology, relates in particular to a kind of data communications method and communication ends.

Background technology

The cloud platform is in the resource set such as a calculating, storage, network, buffer memory, elasticity is shared, the platform of various services is provided as required, and the cloud platform can be in the face of the concurrent visit of mass user, the service request of concurrent processing mass user usually.In the prior art; Session between cloud client and the cloud platform is HTTP (the HyperText Transfer Protocol through stateless (stateless); Be called for short HTTP)/Secure Hypertext Transfer Protocol (HyperText Transfer Protocol over Secure Socket Layer; Be called for short HTTPS) ask to accomplish, wherein, the cloud client is meant and is used on the terminal equipment and the mutual Agent of cloud platform.Each HTTP/HTTPS request of cloud client is set up based on the short data channel that connects of transmission control protocol (Transmission Control Protocol is called for short TCP) with the cloud platform respectively, closes data channel after the request response finishes.For instance; The client that a lot of service application are arranged in the smart mobile phone; And the user can open a plurality of service customer ends (for example microblogging or internet game) simultaneously, respectively with the server communication in high in the clouds, if the client of each service application is all initiated and independently being connected of cloud platform on the mobile phone; Concurrent connection number between mobile phone and the cloud platform can increase greatly on the one hand; The connection pressure of cloud platform can increase the weight of greatly, and the utilance of data channel is lower, and the concurrent radio bearer number (eating dishes without rice or wine) between mobile phone and the base station also can increase greatly on the other hand.

Sometimes; Also need interconnect between the cloud platform, usually the cloud platform externally only provides a shared entrance and exit for security consideration, needs to transmit the customer service session data of magnanimity between two shared gateways between two cloud platforms; If the cloud platform is all initiated and independently being connected of another cloud platform to each service request; Concurrent connection number between the cloud platform also can increase greatly, and the connection pressure of cloud platform also can increase the weight of greatly, and the utilance of data channel is lower.

In realizing process of the present invention, the inventor finds to have following problem in the prior art at least: under the situation of a large amount of voice and packet data concurrent service requests, the sources traffic end is many with concurrent connection number between the destinations traffic end, be connected pressure greatly and the data channel utilance low.

Summary of the invention

The embodiment of the invention provides a kind of data communications method and communication ends, in order to solve in the prior art under the situation of a large amount of voice and packet data concurrent service requests sources traffic end many with concurrent connection number between the destinations traffic end, be connected pressure greatly and the low problem of data channel utilance.

First aspect of the embodiment of the invention provides a kind of data communications method, comprising:

The sources traffic end group in set up towards connectionless transport layer shared data PORT COM and the destinations traffic end between towards connectionless transport layer shared data passage;

Said sources traffic end is through said service message towards connectionless transport layer shared data passage and the mutual a plurality of service conversations of said destinations traffic end.

Another aspect of the embodiment of the invention provides a kind of communication ends, comprising:

Passage is set up module, be used for based on set up towards connectionless transport layer shared data PORT COM and Correspondent Node between towards connectionless transport layer shared data passage;

The service interaction module is used for through said service message towards connectionless transport layer shared data passage and the mutual a plurality of service conversations of said Correspondent Node.

Another aspect of the embodiment of the invention provides a kind of communication ends, comprising: cloud client and a plurality of service customer ends that are connected with said cloud client or a plurality of individual cloud desktop window;

Said a plurality of service customer end or a plurality of individual cloud desktop window are used for, and generate the service message of said a plurality of service conversations and send to said cloud client;

Said cloud client comprises:

Passage is set up module, be used for based on set up towards connectionless transport layer shared data PORT COM and Correspondent Node between towards connectionless transport layer shared data passage;

The service interaction module, the service message of a plurality of service conversations that are used for said a plurality of service customer ends or a plurality of individual cloud desktop are sent is said to send to said Correspondent Node through said towards connectionless transport layer shared data passage; Receive the service message of said a plurality of service conversations that said Correspondent Node sends through said towards connectionless transport layer shared data passage, and the service message of said a plurality of service conversations that said Correspondent Node is sent sends to said a plurality of service customer end or a plurality of individual cloud desktop window;

Said a plurality of service customer end or a plurality of individual cloud desktop window also are used for, and the service message of said a plurality of service conversations that said Correspondent Node is sent is handled.

Another aspect of the embodiment of the invention provides a kind of communication ends, comprising: scheduling node and the working node that is connected with said scheduling node;

Said working node is used for, and generates the service message of a plurality of service conversations and sends to said scheduling node;

Said scheduling node comprises:

Passage is set up module, be used for based on set up towards connectionless transport layer shared data PORT COM and Correspondent Node between towards connectionless transport layer shared data passage;

First interactive module, the service message of the said a plurality of service conversations that are used for said working node is sent sends to said Correspondent Node through said towards connectionless transport layer shared data passage;

Second interactive module; Be used for receiving the service message of said a plurality of service conversations that said Correspondent Node sends towards connectionless transport layer shared data passage, and the service message of said a plurality of service conversations that said Correspondent Node is sent sends to said working node through said;

Said working node also is used for, and the service message of said a plurality of service conversations that said Correspondent Node is sent is handled.

A technical scheme in above-mentioned a plurality of technical scheme has following beneficial effect or advantage at least:

The embodiment of the invention is through setting up between sources traffic end and destinations traffic end towards connectionless transport layer shared data passage; And the session identification of service conversation under in mutual service message, carrying; Make that sources traffic end and destinations traffic end can be through the service messages of the mutual a plurality of service conversations of a data passages; Solved in the prior art under the situation of a large amount of voice and packet data concurrent service requests sources traffic end many with concurrent connection number between the destinations traffic end, be connected pressure greatly and data channel utilance low problem; Make that the shared data passage can be multiplexing for multi-service message, multi-service session; Reduce the concurrent connection number between sources traffic end and destinations traffic end, improved the utilance of data channel.

Description of drawings

In order to be illustrated more clearly in the embodiment of the invention or technical scheme of the prior art; To do one to the accompanying drawing of required use in embodiment or the description of the Prior Art below introduces simply; Obviously, the accompanying drawing in describing below is some embodiments of the present invention, for those of ordinary skills; Under the prerequisite of not paying creative work property, can also obtain other accompanying drawing according to these accompanying drawings.

Fig. 1 is a kind of system architecture sketch map of the embodiment of the invention;

The schematic flow sheet of a kind of data communications method that Fig. 2 provides for the embodiment of the invention;

Fig. 3 is the system architecture sketch map of a kind of application scenarios of the embodiment of the invention;

Fig. 4 is the signaling process figure under the application scenarios shown in Figure 3;

Fig. 5 is the signaling process figure of another application scenarios of the embodiment of the invention;

Fig. 6 is the system architecture sketch map of another application scenarios of the embodiment of the invention;

Fig. 7 is the system architecture sketch map of another application scenarios of the embodiment of the invention;

Fig. 8 is the signaling process figure under the application scenarios shown in Figure 7;

Fig. 9 is the signalling diagram under another application scenarios of the embodiment of the invention;

The structural representation of a kind of communication ends that Figure 10 provides for the embodiment of the invention;

Figure 11 A is the structural representation of another communication ends of providing of the embodiment of the invention;

Figure 11 B is the structural representation of another communication ends of providing of the embodiment of the invention;

The structural representation of another communication ends that Figure 12 provides for the embodiment of the invention;

The structural representation of a kind of terminal equipment that Figure 13 provides for the embodiment of the invention;

The structural representation of scheduling node in a kind of cloud Platform Server that Figure 14 provides for the embodiment of the invention;

The structural representation of working node in a kind of cloud Platform Server that Figure 15 provides for the embodiment of the invention.

Embodiment

For the purpose, technical scheme and the advantage that make the embodiment of the invention clearer; To combine the accompanying drawing in the embodiment of the invention below; Technical scheme in the embodiment of the invention is carried out clear, intactly description; Obviously, described embodiment is the present invention's part embodiment, rather than whole embodiment.Based on the embodiment among the present invention, those of ordinary skills are not making the every other embodiment that is obtained under the creative work prerequisite, all belong to the scope of the present invention's protection.

Fig. 1 is a kind of system architecture sketch map of the embodiment of the invention.As shown in Figure 1, system comprises sources traffic end and destinations traffic end, perhaps is called communication ends and Correspondent Node.Wherein, The sources traffic end can be a terminal equipment; Comprise catv terminal and wireless terminal; As computer, mobile phone terminal, panel computer, Internet of Things transducer etc., also can be cloud Platform Server (also can be described as the cloud platform) or general server (also can be called non-cloud Platform Server or non-cloud platform) as client.The destinations traffic end can be cloud Platform Server or the general server as server.

Under system architecture shown in Figure 1; The sources traffic end is responsible for distributing fixing towards connectionless transport layer shared data PORT COM (also can be called the high in the clouds mouth); Like sharing users data pack protocol (User Datagram Protocol; Be called for short UDP) port, set up between sources traffic end and the destinations traffic end based on the high in the clouds mouth towards connectionless transport layer shared data passage, like shared UDP message passage; The sources traffic end is after the destinations traffic end is initiated two or more different service conversation establishing requests (being also referred to as the request of creating service conversation); The receiving target communication ends is being created the corresponding session identification (Session ID) of different business conversation establishing request that returns behind the corresponding service session Session; The interacting message of these two or more different service conversation establishing request corresponding service instances and destinations traffic end is all through transmitting towards connectionless transport layer shared data passage based on the high in the clouds mouth between sources traffic end and the destinations traffic end on the follow-up sources traffic end; And the Session ID of service conversation under on the sources traffic end, carrying respectively in these different business instances and the follow-up interactive messages of destinations traffic end makes a distinction with the message of these different business sessions that will transmit in the connectionless transport layer shared data passage.Wherein, The message of these different business sessions can be supported different application layer protocols; As: real time transport protocol (Real-time Transport Protocol; Be called for short RTP) or MPTS (Transport Stream is called for short TS) or HTML (Hypertext Markup Language is called for short HTML) etc.; Session ID is encapsulated by application layer protocol, and specific practice can add the unified packing of one deck in concrete application layer protocol outside, in same packing, fills out Session ID, and the uniform protocol of having packed remains the agreement of application layer; Also can revise concrete application layer protocol,, Session ID expanded to the inside, packet header of application layer protocol like RTP.At last, the sources traffic end sends the service conversation ending request to the destinations traffic end, the session of destinations traffic end deletion corresponding business.

The destinations traffic end is responsible for distributing stationary plane to connectionless transport layer shared data PORT COM (also can be called the high in the clouds mouth); As sharing udp port; Set up between sources traffic end and the destinations traffic end based on the high in the clouds mouth towards connectionless transport layer shared data passage, as sharing the UDP message passage.At the sources traffic end after the destinations traffic end is initiated two or more different service conversation establishing requests; The destinations traffic end is created these different business session service request corresponding service sessions Session; Be respectively these service conversations and create request corresponding service session assign sessions sign Session ID; And return to the sources traffic end to these Session ID; The interacting message of these two or more different service conversation establishing request corresponding service instances all transmits through the transport layer shared data passage towards connectionless based on the high in the clouds mouth between sources traffic end and the destinations traffic end on succeeding target communication ends and the sources traffic end; And the Session ID of service conversation under on destinations traffic end and sources traffic end, carrying respectively in the follow-up interactive messages of these different business instances makes a distinction with the message of these different business sessions that will transmit in the connectionless transport layer shared data passage.At last, the sources traffic end sends the service conversation ending request to the destinations traffic end, the session of destinations traffic end deletion corresponding business.

The schematic flow sheet of a kind of data communications method that Fig. 2 provides for the embodiment of the invention.As shown in Figure 2, comprising:

201, the sources traffic end group in set up towards connectionless transport layer shared data PORT COM and the destinations traffic end between towards connectionless transport layer shared data passage.

Based on being to share udp port towards connectionless transport layer shared data PORT COM, can be to share the UDP message passage towards connectionless transport layer shared data passage.

Need to prove, towards do not have connecting with respect to towards connecting so-called connection-oriented communication; As sharing transmission control protocol (Transmission Control Protocol; Be called for short TCP), be exactly before sending between sources traffic end and the destinations traffic end and receiving data, must set up a connection from the sources traffic end to the destinations traffic end; Connect like TCP and need carry out being connected of three-way handshake between sources traffic end and the destinations traffic end; Transmitting and receiving data each other just between the opisthogenesis communication ends that connects and the destinations traffic end, when send with receive data and accomplish after, break off being connected of sources traffic end and destinations traffic end again.Towards connectionless communication; Like UDP; Be exactly to send and receive before the data between sources traffic end and the destinations traffic end; Need not to set up connection, as need not be as TCP sending and need not break off again after reception finishes being connected between sources traffic end and the destinations traffic end through the be connected foundation, data of the three-way handshake between sources traffic end and the destinations traffic end from the sources traffic end to the destinations traffic end.Said is not connect the corresponding PORT COM of communication towards having for what multi-user, multi-service message, multi-service session were shared towards connectionless transport layer shared data PORT COM as sharing udp port, and said is exactly not connect the corresponding data channel of communication for what multi-user, multi-service message, multi-service session were shared towards having towards connectionless transport layer shared data passage as sharing the UDP message passage.

Specifically, have following advantage with respect to adopting connection-oriented transport layer shared data passage as sharing the tcp data passage, adopting at least as sharing the UDP message passage towards connectionless transport layer shared data passage:

1) being connected to wireless terminal and a plurality of cloud platforms: wireless terminal need use a plurality of shared tcp data passages to connect a plurality of cloud platforms respectively; The corresponding shared tcp data passage of each cloud platform; The radio bearer that wireless terminal connects/eated dishes without rice or wine is a plurality of, can not improve the utilance of radio bearer/eat dishes without rice or wine.And wireless terminal only need be opened the radio bearer of a shared UDP/eat dishes without rice or wine to get final product when connecting a plurality of cloud platform respectively with a plurality of shared UDP message passages.

2) being connected to wireless terminal and a cloud platform: when wireless terminal passes through a plurality of service messages of shared tcp data channel transfer; When promptly sharing the tcp data passage and be multi-service message on the wireless terminal and sharing; Because TCP is the transmission of strict sequenced byte stream; A plurality of service messages can only can not concurrently transmit by the byte order transmission, so the efficient of transmission is lower.And if be that multi-service message on the wireless terminal is shared through a shared UDP message passage, then a plurality of service messages can concurrently transmit.

3) because the transmitting-receiving of TCP is a non-boundary, when be a plurality of service messages when sharing, can not distinguish the agreement of a plurality of service messages, must outside each service message, pack the unified agreement of one deck again, processing is just pretty troublesome like this.And the transmitting-receiving of UDP has the border, so need not to pack the unified agreement of one deck, also can distinguish the agreement of different service messages during transmitting-receiving again.

4) in the peer server cluster; Data of transmission magnanimity between two cloud platforms for example; If with a shared tcp data passage; This shared tcp data passage can only be that a TCP of another station server of a station server in the target cloud Platform Server cluster in the cloud Platform Server cluster of source connects, and can't bring into play the effect of server cluster, and data channel is very narrow is not suitable for transmitting mass data.And if with a shared UDP message passage; Then can realize the load balancing of source cloud Platform Server cluster and target cloud Platform Server cluster; Sharing the UDP message channel in theory can infinitely widen, and therefore is adapted at sharing multi-user, the multi-service message of UDP message channel magnanimity, the data of multi-service session.

Usually, also comprised before 201:

The sources traffic end distributes said based on towards connectionless transport layer shared data PORT COM.

Accordingly, 201 be specially:

Said sources traffic end group is said towards connectionless transport layer shared data passage towards setting up towards connectionless transport layer shared data PORT COM of connectionless transport layer shared data PORT COM and the distribution of said destinations traffic end in said distribution.

Particularly, said sources traffic end can be set up respectively towards connectionless transport layer shared data passage based on one or more ports of a port that self distributes and the distribution of said destinations traffic end.When a plurality of ports that distribute with said destinations traffic end are set up respectively towards connectionless transport layer shared data passage, can distinguish corresponding according to the different port numbers of these a plurality of ports towards connectionless transport layer shared data passage.

202, said sources traffic end is through said service message towards connectionless transport layer shared data passage and the mutual a plurality of service conversations of said destinations traffic end, and the service message of each service conversation carries the session identification of affiliated service conversation respectively.

Particularly, comprise two-way data communication alternately.Accordingly, 202 comprise:

Said sources traffic end generates the service message of said a plurality of service conversations, through the said service message that sends said a plurality of service conversations towards connectionless transport layer shared data passage to said destinations traffic end;

Said sources traffic end receives the service message of said a plurality of service conversations that said destinations traffic end sends through said towards connectionless transport layer shared data passage, and the session identification of the affiliated service conversation that carries according to each service message is handled each service message.

Need to prove; In the above-mentioned two-way data communication process; The sequencing of said sources traffic termination receipts, the message of managing business and generation, transmission service message can exchange; Further, the order that receives, handles or generate, sends the service message of each service conversation also can be arbitrarily.

Usually, between the service message of sources traffic end and the session of destinations traffic end interactive service, also need to create this service conversation earlier, confirm the session identification of this service conversation.Particularly, also comprise between 201 and 202:

Said sources traffic end is initiated the request of a plurality of establishment service conversations towards connectionless transport layer shared data passage to said destinations traffic end through said, so that said destinations traffic end is created said a plurality of service conversation and is said a plurality of service conversations difference assign sessions signs according to the request of said a plurality of establishment service conversations;

Receive the response of a plurality of establishment service conversations that said destinations traffic end returns, the session identification of service conversation under each response comprises respectively through said towards connectionless transport layer shared data passage.

Further, when the service message of accomplishing a service conversation mutual, can also finish this service conversation.Particularly, can also comprise after 202:

Said sources traffic end is through said request from connectionless transport layer shared data passage to said destinations traffic end that initiate a plurality of winding-up sessions towards; The session identification of service conversation under each request is carried respectively is so that said destinations traffic end is deleted said a plurality of service conversation.

Fig. 3 is the system architecture sketch map of a kind of application scenarios of the embodiment of the invention.As shown in Figure 3, terminal equipment comprises a cloud client and a plurality of service customer end as the sources traffic end, and like service customer end 1 and service customer end 2, wherein, service customer end is meant and is used to the application program that realizes that certain is professional, like the QQ client etc.; The cloud platform comprises a scheduling node (Master Node) and a plurality of working node (Worker Node) as the destinations traffic end; Terminal equipment is connected through sharing the UDP message passage with the cloud platform, and the shared UDP message passage in this application scenarios also can be called the cloud service bus.

Fig. 4 is the signaling process figure under the application scenarios shown in Figure 3, for instance, can be multi-service client and the communication between the cloud platform on the mobile phone terminal.As shown in Figure 4, comprising:

401, the Master Node of cloud client and cloud platform distributes fixing shared udp port respectively.

402, set up shared UDP message passage between cloud client and the Master Node.

403, service customer end 1 initiates to create the request of service conversation 1 to the cloud client.

Carry the call identification Call ID (1) that is distributed for service conversation 1 by service customer end 1 in this request, Call ID (1) is unique distribution in end side.For instance, call identification can dynamically generate according to system time.

404, the cloud client initiates to create the request of service conversation 1 to Master Node.

Simultaneously, the corresponding relation of cloud client records Call ID (1) and service customer end 1.Carry above-mentioned Call ID (1) in the request of said establishment service conversation 1.

405, Master Node selects Worker Node.

Particularly, the Master Node scheduling strategy that can select to preset is selected Worker Node.Usually, can select according to factors such as the ability of each Worker Node, state, load, performances.

406, Master Node transmits the request of creating service conversation 1 to Worker Node.

407, Worker Node creates service conversation 1, assign sessions sign Session ID (1).

Simultaneously, Worker Node also creates the context environmental of service conversation 1, and sets up the corresponding relation of service conversation 1 and Session ID (1).Particularly, the context environmental of each service conversation all can leave in the shared cache of cloud platform.

408, Worker Node returns to Master Node with the session identification Session ID (1) of service conversation 1.

Except Session ID (1), also carry above-mentioned Call ID (1) in the message that Worker Node returns.

409, the Master Node response that will create service conversation 1 returns to the cloud client.

Carry above-mentioned Call ID (1) and session identification Session ID (1) in the response of establishment service conversation 1.

410, the cloud client identifies Session ID (1) according to the corresponding relation of Call ID (1) and service customer end 1 with session and Call ID (1) returns to service customer end 1.

Service customer end 1 confirms that according to the corresponding relation of Call ID (1) and service conversation 1 Session ID (1) is the session identification of service conversation 1.Afterwards; Service customer end 1 just can carry the service message of the service conversation 1 of Session ID (1) alternately with the Worker Node of cloud platform; As: order, data, incident etc.; Transmit through cloud client and cloud platform Master Node in the reciprocal process, the service message of these service conversations 1 transmits through the shared UDP message passage between cloud client and the cloud platform.Further; Master Node is behind the service message that receives service conversation 1; Can search the context environmental of service conversation 1 according to the Session ID (1) that carries in the service message; The context environmental of service conversation 1 is offered the Worker Node of selection, and Worker Node is based on the manage business service message of session 1 of the context environmental of service conversation 1; Perhaps; Master Node is behind the service message that receives service conversation 1; The service message of service conversation 1 is passed to the Worker Node of selection; Worker Node searches the context environmental of service conversation 1 according to the Session ID (1) that carries in the service message, based on the manage business service message of session 1 of the context environmental of service conversation 1.Need to prove, Master Node select to be used for the to manage business Worker Node of session 1 service message, with 405 in the Worker Node that selects can be identical, also can be different, depend on scheduling strategy.

411, service customer end 2 initiates to create the request of service conversation 2 to the cloud client.

Carry the Call ID (2) that is distributed for service conversation 2 by service customer end 2 in this request, Call ID (2) is unique distribution in end side, the corresponding relation of cloud client records Call ID (2) and service customer end (2).

412, the cloud client initiates to create the request of service conversation 2 to Master Node.

Simultaneously, the corresponding relation of cloud client records Call ID (2) and service customer end 2.Carry above-mentioned Call ID (2) in the request of said establishment service conversation 2.

413, Master Node selects Worker Node.

Particularly, the Master Node scheduling strategy that can select to preset is selected Worker Node.Usually, can select according to factors such as the ability of each Worker Node, state, load, performances.The Worker Node that selects among the Worker Node and 405 that selects in 413 can be identical, also can be different.

414, Master Node transmits the request of creating service conversation 2 to Worker Node.

Carry above-mentioned Call ID (2) in this request.

415, Worker Node creates service conversation 2, assign sessions sign Session ID (2).

Simultaneously, Worker Node also creates the context environmental of service conversation 2, and sets up the corresponding relation of service conversation 2 and Session ID (2).

416, Worker Node returns to Master Node with the session identification Session ID (2) of service conversation 2.

Except Session ID (2), also carry above-mentioned Call ID (2) in the message that Worker Node returns.

417, the Master Node response that will create service conversation 2 returns to the cloud client.

Carry above-mentioned Call ID (2) and session identification Session ID (2) in the response of establishment service conversation 2.In addition, Master Node or Worker Node can also create the context environmental of service conversation 2, the corresponding relation of the context environmental of record Session ID (2) and service conversation 2.

418, the cloud client returns to service customer end 2 according to the corresponding relation of Call ID (2) and service customer end 2 with the session identification Session ID (2) and the Call ID (2) of service conversation 2.

Service customer end 2 confirms that according to the corresponding relation of Call ID (2) and service conversation 2 Session ID (2) is the session identification of service conversation 2.Afterwards; Service customer end 2 just can carry the service message of the service conversation 2 of Session ID (2) alternately with the Worker Node of cloud platform; As: order, data, incident etc.; Transmit through cloud client and cloud platform Master Node in the reciprocal process, the service message of these service conversations 2 transmits through the shared UDP message passage between cloud client and the cloud platform.Further; Master Node is behind the service message that receives service conversation 2; Can search the context environmental of service conversation 2 according to the Session ID (2) that carries in the service message; The context environmental of service conversation 2 is offered the Worker Node of selection, and Worker Node is based on the manage business service message of session 2 of the context environmental of service conversation 2; Perhaps; Master Node is behind the service message that receives service conversation 2; The service message of service conversation 2 is passed to the Worker Node of selection; Worker Node searches the context environmental of service conversation 2 according to the Session ID (2) that carries in the service message, based on the manage business service message of session 2 of the context environmental of service conversation 2.Need to prove, Master Node select to be used for the to manage business Worker Node of session 2 service messages, with 413 in the Worker Node that selects can be identical, also can be different, try to please scheduling strategy.

419, service customer end 1 is initiated the request of winding-up session 1 to the cloud client.

Carry Session ID (1) in this message.

420, the cloud client is transmitted the request of winding-up session 1.

421, the Master Node of cloud platform distributes Worker Node.

422, Worker Node is given in the request of Master Node forwarding winding-up session 1.

423, Worker Node deletion service conversation 1.

Particularly, the context environmental of Worker Node deletion service conversation 1.

424, service customer end 2 is initiated the request of winding-up session 2 to the cloud client.

Carry Session ID (2) in this message.

425, the cloud client is transmitted the request of winding-up session 2.

426, the Master Node of cloud platform distributes Worker Node.

427, Master Node transmits the request that finishes with service conversation 2 and gives Worker Node.

428, Worker Node deletion service conversation 2.

Particularly, the context environmental of Worker Node deletion service conversation 2.

When a terminal equipment and a plurality of cloud platform communication; 402 medium cloud clients are set up a shared UDP message passage respectively based on the shared udp port and each the cloud platform that distribute; Further; For each cloud platform, the cloud client also can be set up a shared UDP message passage respectively based on a shared udp port that distributes and a plurality of ports of this cloud platform.Like this; When sending request or service message through shared udp port; Can select the shared UDP message passage between the cloud platform corresponding to send according to the address information of the cloud platform that carries in request or the service message, so that corresponding these requests of cloud platform processes and the service message of this address information with this address information.The address information of this cloud platform can be to be arranged in advance in each service customer end; The address information of the cloud platform that is provided with in each service customer end can be different; Particularly; The address information of cloud platform can comprise the IP address and the port numbers of cloud Platform Server, or the URL of cloud Platform Server (Universal Resource Locator is called for short URL) address.Further; 410 medium cloud clients also need write down Session ID (1), the address information of creating the cloud platform that carries in the request of service conversation 1 and the corresponding relation of service customer end 1 or service conversation 1; Even distributed under the situation of identical session identification for the different service session at different cloud platforms like this; Can also and send the service message that the address information of the cloud platform of service message sends service conversation 1 with the cloud platform according to Session ID (1) and pass to service customer end 1, and handle as the service message of service conversation 1.Similarly, 418 medium cloud clients also need write down Session ID (2), the address information of creating the cloud platform that carries in the request of service conversation 2 and the corresponding relation of service customer end 2 or service conversation 2.

Fig. 5 is the signaling process figure of another application scenarios of the embodiment of the invention.Compare with application scenarios shown in Figure 3, should use in the terminal equipment of scene, cloud client and service customer end merge setting; For instance, Fig. 5 can be the multi-service session communication between Internet of Things sensor terminal and the Internet of Things cloud platform.As shown in Figure 5, comprising:

501, cloud client and Master Node distribute fixing shared udp port respectively.

502, set up shared UDP message passage between the Master Node of cloud client and cloud platform.

503, the cloud client initiates to create the request of service conversation 1 to Master Node.

Carrying by the cloud client in this request is the call identification Call ID (1) that service conversation 1 distributes, and Call ID (1) is unique distribution in end side.

504, Master Node selects Worker Node.

Particularly, the Master Node scheduling strategy that can select to preset is selected Worker Node.Usually, can select according to factors such as the ability of each Worker Node, state, load, performances.

505, Master Node transmits the request of creating service conversation 1 to Worker Node.

506, Worker Node creates service conversation 1, assign sessions sign Session ID (1).

Simultaneously, Worker Node also creates the context environmental of service conversation 1, and sets up the corresponding relation of service conversation 1 and Session ID (1).

507, Worker Node returns to Master Node with the session identification Session ID (1) of service conversation 1.

Except Session ID (1), also carry above-mentioned Call ID (1) in the message that Worker Node returns.

508, the Master Node response that will create service conversation 1 returns to the cloud client.

Carry above-mentioned Call ID (1) and session identification Session ID (1) in the response of establishment service conversation 1.

The cloud client confirms that according to the corresponding relation of Call ID (1) and service conversation 1 Session ID (1) is the session identification of service conversation 1.Afterwards; The cloud client just can carry the service message of the service conversation 1 of Session ID (1) alternately with the Worker Node of cloud platform; As: order, data, incident etc.; Transmit through cloud platform Master Node in the reciprocal process, the service message of these service conversations 1 transmits through the shared UDP message passage between cloud client and the cloud platform.Further; Master Node is behind the service message that receives service conversation 1; Can search the context environmental of service conversation 1 according to the Session ID (1) that carries in the service message; The context environmental of service conversation 1 is offered the Worker Node of selection, and Worker Node is based on the manage business service message of session 1 of the context environmental of service conversation 1; Perhaps; Master Node is behind the service message that receives service conversation 1; The service message of service conversation 1 is passed to the Worker Node of selection; Worker Node searches the context environmental of service conversation 1 according to the Session ID (1) that carries in the service message, based on the manage business service message of session 1 of the context environmental of service conversation 1.Need to prove, Master Node select to be used for the to manage business Worker Node of session 1 service message, with 504 in the Worker Node that selects can be identical, also can be different, depend on scheduling strategy.

509, the cloud client initiates to create the request of service conversation 2 to the Master of cloud platform Node.

Carrying by the cloud client in this request is the Call ID (2) that service conversation 2 distributes, and Call ID (2) is unique distribution in end side.

510, Master Node selects Worker Node.

Particularly, the Master Node scheduling strategy that can select to preset is selected Worker Node.Usually, can select according to factors such as the ability of each Worker Node, state, load, performances.The Worker Node that selects among the Worker Node and 504 that selects in 510 can be identical, also can be different.

511, Master Node transmits the request of creating service conversation 2 to Worker Node.

Carry above-mentioned Call ID (2) in this request.

512, Worker Node creates service conversation 2, assign sessions sign Session ID (2).

Simultaneously, Worker Node also creates the context environmental of service conversation 2, and sets up the corresponding relation of service conversation 2 and Session ID (2).

513, Worker Node returns to Master Node with the session identification Session ID (2) of service conversation 2.

Except Session ID (2), also carry above-mentioned Call ID (2) in the message that Worker Node returns.

514, the Master Node response that will create service conversation 2 returns to the cloud client.

Carry above-mentioned Call ID (2) and session identification Session ID (2) in the response of establishment service conversation 2.

The cloud client confirms that according to the corresponding relation of Call ID (2) and service conversation 2 Session ID (2) is the session identification of service conversation 2.Afterwards; The cloud client just can carry the service message of the service conversation 2 of Session ID (2) alternately with the Worker Node of cloud platform; As: order, data, incident etc.; Transmit through cloud platform Master Node in the reciprocal process, the service message of these service conversations 2 transmits through the shared UDP message passage between cloud client and the cloud platform.Further; Master Node is behind the service message that receives service conversation 2; Can search the context environmental of service conversation 2 according to the Session ID (2) that carries in the service message; The context environmental of service conversation 2 is offered the Worker Node of selection, and Worker Node is based on the manage business service message of session 2 of the context environmental of service conversation 2; Perhaps; Master Node is behind the service message that receives service conversation 2; The service message of service conversation 2 is passed to the Worker Node of selection; Worker Node searches the context environmental of service conversation 2 according to the Session ID (2) that carries in the service message, based on the manage business service message of session 2 of the context environmental of service conversation 2.Need to prove, Master Node select to be used for the to manage business Worker Node of session 2 service messages, with 510 in the Worker Node that selects can be identical, also can be different, depend on scheduling strategy.

515, the cloud client is initiated the request of winding-up session 1.

Carry Session ID (1) in this message.

516, the Master Node of cloud platform distributes Worker Node.

517, Worker Node is given in the request of Master Node forwarding winding-up session 1.

518, Worker Node deletion service conversation 1.

Particularly, the context environmental of Worker Node deletion service conversation 1.

519, the cloud client is initiated the request of winding-up session 2 to the Master of cloud platform Node.

Carry Session ID (2) in this message.

520, Master Node distributes Worker Node.

521, Master Node transmits the request that finishes with service conversation 2 and gives Worker Node.

522, Worker Node deletion service conversation 2.

Particularly, the context environmental of Worker Node deletion service conversation 2.

When a terminal equipment and a plurality of cloud platform communication, 502 medium cloud clients are set up a shared UDP message passage respectively based on the shared udp port and each the cloud platform that distribute.Like this; When sending request or service message through shared udp port; Can select the shared UDP message passage between the cloud platform corresponding to send according to the address information of the cloud platform that carries in request or the service message, so that corresponding these requests of cloud platform processes and the service message of this address information with this address information.The address information of cloud platform can be to be arranged in advance in the cloud client and with professional corresponding; The address information of the cloud platform that each service conversation is corresponding can be different; Particularly; The address information of cloud platform can comprise the IP address and the port numbers of cloud Platform Server, or the URL address of cloud Platform Server.Further; The medium cloud client also need write down Session ID (1), the address information of creating the cloud platform that carries in the request of service conversation 1 and the corresponding relation of service conversation 1 after 508; Even distributed for the different service session under the situation of identical session identification at different cloud platforms like this, can also handle as the service message of service conversation 1 according to the service message that Session ID (1), the address information of sending the cloud platform of service message are sent the cloud platform service conversation 1.Similarly, the cloud client also need write down Session ID (2), the address information of creating the cloud platform that carries in the request of service conversation 2 and the corresponding relation of service conversation 2 after 514.

Fig. 6 is the system architecture sketch map of another application scenarios of the embodiment of the invention.As shown in Figure 6; Terminal equipment is as the sources traffic end; Comprise a cloud client and a plurality of individual cloud desktop window Window, like individual cloud desktop Window1 and individual cloud desktop Window2, wherein; Individual's cloud desktop Window can be the personal desktop Window that core code on the terminal equipment (being processing logic) leaves the cloud platform in; When starting individual cloud desktop Window for one, need to connect corresponding cloud platform, behind the processing logic of this individual's cloud desktop of cloud platform operation Window display logic is returned terminal equipment; The cloud platform comprises a Master Node and a plurality of Worker Node as the destinations traffic end; Terminal equipment is connected through sharing the UDP message passage with the cloud platform, and the shared UDP message passage in this application scenarios also can be called cloud desktop bus.Signaling process under the application scenarios shown in Figure 6 just replaces to individual cloud desktop Window with service customer end with similar like Fig. 4, repeats no more here.

Fig. 7 is the system architecture sketch map of another application scenarios of the embodiment of the invention.As shown in Figure 7, sources traffic end and destinations traffic end are the cloud Platform Server, are respectively cloud Platform Server 1 and cloud Platform Server 2; Cloud Platform Server 1 is connected through sharing the UDP message passage with cloud Platform Server 2, and the shared UDP message passage in this application scenarios also can be called the cloud service bus.For instance, this application scenarios can be distributed social networks, such as, the session communication between the SNS cloud platform of the social network services of China Mobile (Social Networking Services is called for short SNS) cloud platform and China Telecom.

Fig. 8 is the signaling process figure under the application scenarios shown in Figure 7.As shown in Figure 8, comprising:

801, distribute in cloud Platform Server 1 and cloud Platform Server 2 both sides fixing towards connectionless transport layer shared data PORT COM, based on said port set up cloud up between Platform Server 1 and the cloud Platform Server 2 towards connectionless transport layer shared data passage.

802, cloud Platform Server 1 is initiated the request of two or more different service conversation establishing to cloud Platform Server 2.

803, cloud Platform Server 2 is created request to these service conversations and is created the different service session respectively, distributes the Session ID of each service conversation respectively.

804, cloud Platform Server 2 returns to cloud Platform Server 1 with the Session ID of these different service sessions.

805, these service conversations on cloud Platform Server 1 are created request corresponding service instances and cloud Platform Server 2 to carry out subsequent message towards connectionless transport layer shared data passage mutual through said, and the Session ID that carries service conversation correspondence separately in the interactive messages respectively is with towards connectionless transport layer shared data passage.

806, cloud Platform Server 1 sends the request that finishes these service conversations to cloud Platform Server 2.

807, cloud Platform Server 2 these service conversations of deletion.

Fig. 9 is the signalling diagram under another application scenarios of the embodiment of the invention.Comparing with application scenarios shown in Figure 7, should use the destinations traffic end in the scene to do as general server, for instance, should can be that the cloud platform (sources traffic end) with first function of search is visited other member's search engines (destinations traffic end) with scene.As shown in Figure 9, comprising:

901, distribute in cloud Platform Server and general server both sides fixing towards connectionless transport layer shared data PORT COM, based on said port set up cloud up between Platform Server and the general server towards connectionless transport layer shared data passage.

902, the cloud Platform Server is initiated the request of two or more different service conversation establishing to general server.

903, general server is created request to these service conversations and is created the different service session respectively, distributes the Session ID of each service conversation respectively.

904, general server returns to the cloud Platform Server with the Session ID of these different service sessions.

905, these service conversations on the cloud Platform Server create request corresponding service instances with general server through said towards the mutual subsequent message of connectionless transport layer shared data passage, and carry the Session ID of service conversation correspondence separately in the message respectively.

906, the cloud Platform Server sends the request that finishes these service conversations to general server.

907, these service conversations of general server deletion.

Need to prove that general server is similar as the signalling interactive process under the scene of destinations traffic end and Fig. 5 as sources traffic end, cloud Platform Server.

The embodiment of the invention is through setting up between sources traffic end and destinations traffic end towards connectionless transport layer shared data passage; And the session identification of service conversation under in mutual service message, carrying; Make that sources traffic end and destinations traffic end can be through the service messages of the mutual a plurality of service conversations of a data passages; Solved in the prior art under the situation of a large amount of voice and packet data concurrent service requests sources traffic end many with concurrent connection number between the destinations traffic end, be connected pressure greatly and data channel utilance low problem; Make that the shared data passage can be multiplexing for multi-service message, multi-service session; Reduce the concurrent connection number between sources traffic end and destinations traffic end, improved the utilance of data channel.Further, owing to adopt towards connectionless transport layer shared data passage, the destinations traffic end can push PUSH to the sources traffic end with content whenever and wherever possible, realizes the forever online of sources traffic end terminal.When between the cloud platform through when mutual, between the cloud platform unified entrance and outlet being provided towards connectionless transport layer shared data passage, improved the fail safe and the reliability of cloud platform further.

The structural representation of a kind of communication ends that Figure 10 provides for the embodiment of the invention.Shown in figure 10, this communication ends comprises:

Passage is set up module 11, be used for based on set up towards connectionless transport layer shared data PORT COM and Correspondent Node between towards connectionless transport layer shared data passage;

Service interaction module 12 is used for through said service message towards connectionless transport layer shared data passage and the mutual a plurality of service conversations of said Correspondent Node, the session identification of service conversation under the service message of each service conversation carries respectively.

Further, also comprise:

Port assignment module 13 is used to distribute said towards connectionless transport layer shared data PORT COM;

Passage is set up module 11 and specifically is used for, said towards connectionless transport layer shared data passage towards setting up towards connectionless transport layer shared data PORT COM of distributing of connectionless transport layer shared data PORT COM and said Correspondent Node based on said distribution.

Further, service interaction module 12 specifically comprises:

First interactive unit is used to generate the service message of said a plurality of service conversations, through the said service message that sends said a plurality of service conversations towards connectionless transport layer shared data passage to said Correspondent Node;

Second interactive unit; Be used for receiving the service message of said a plurality of service conversations that said Correspondent Node sends through said towards connectionless transport layer shared data passage, the session identification of the affiliated service conversation that carries according to each service message is handled each service message.

Further, also comprise:

The conversation establishing module; Be used for initiating the request of a plurality of establishment service conversations towards connectionless transport layer shared data passage to said Correspondent Node, so that said Correspondent Node is created said a plurality of service conversation and is said a plurality of service conversations difference assign sessions signs according to the request of said a plurality of establishment service conversations through said; Receive the response that said Correspondent Node returns a plurality of establishment service conversations through said towards connectionless transport layer shared data passage, the session identification of service conversation under each response comprises respectively.

Further, also comprise:

The conversation end module; Be used for the request of initiating a plurality of winding-up sessions to said Correspondent Node towards connectionless transport layer shared data passage through said; The session identification of service conversation under each request is carried respectively is so that said Correspondent Node is deleted said a plurality of service conversation.

Further, said Correspondent Node is a plurality of;

Passage is set up module 11 and specifically is used for, based on said distribution towards connectionless transport layer shared data PORT COM and each Correspondent Node distribute towards connectionless transport layer shared data PORT COM set up respectively and each Correspondent Node between towards connectionless transport layer shared data passage;

Said first interactive unit specifically is used for, according to the address information of the Correspondent Node that carries in each service message, through sending each service message respectively towards connectionless transport layer shared data passage between the Correspondent Node corresponding with said address information.

Further, when said Correspondent Node was the cloud Platform Server, said communication ends was terminal equipment, cloud Platform Server or non-cloud Platform Server; When said Correspondent Node was non-cloud Platform Server, said communication ends was the cloud Platform Server.

Wherein, said communication ends is equivalent to the sources traffic end in a kind of data communications method that the embodiment of the invention provides, and said Correspondent Node is equivalent to the destinations traffic end in a kind of data communications method that the embodiment of the invention provides.

A kind of data communications method that the concrete realization of present embodiment provides with reference to the embodiment of the invention is further with reference to Fig. 5, Fig. 7, Fig. 8, Fig. 9.The embodiment of the invention is through setting up between communication ends and Correspondent Node towards connectionless transport layer shared data passage; And the session identification of service conversation under in mutual service message, carrying; Making can be through the service message of the mutual a plurality of service conversations of a data passages between sources traffic end and destinations traffic end; Solved in the prior art under the situation of a large amount of voice and packet data concurrent service requests sources traffic end many with concurrent connection number between the destinations traffic end, be connected pressure greatly and data channel utilance low problem; Make that the shared data passage can be multiplexing for multi-service message, multi-service session; Reduce the concurrent connection number between sources traffic end and destinations traffic end, improved the utilance of data channel.Further, owing to adopt towards connectionless transport layer shared data passage, the destinations traffic end can push PUSH to the sources traffic end with content whenever and wherever possible, realizes the forever online of sources traffic end terminal.When between the cloud platform through when mutual, between the cloud platform unified entrance and outlet being provided towards connectionless transport layer shared data passage, improved the fail safe and the reliability of cloud platform further.

Figure 11 A is the structural representation of another communication ends of providing of the embodiment of the invention, and Figure 11 B is the structural representation of another communication ends of providing of the embodiment of the invention.Shown in Figure 11 A and 11B, this communication ends comprises:

Cloud client 21 and a plurality of service customer ends 22 that are connected with cloud client 21 or a plurality of individual cloud desktop window 23;

A plurality of service customer ends 22 or a plurality of individual cloud desktop window 23 are used for, and generate the service message of said a plurality of service conversations and send to cloud client 21, the session identification of service conversation under the service message of each service conversation carries respectively;

Cloud client 21 comprises:

Passage is set up module 211, be used for based on set up towards connectionless transport layer shared data PORT COM and Correspondent Node between towards connectionless transport layer shared data passage;

Service interaction module 212, the service message of a plurality of service conversations that are used for said a plurality of service customer ends or a plurality of individual cloud desktop are sent is said to send to said Correspondent Node through said towards connectionless transport layer shared data passage; Through the said service message that receives said a plurality of service conversations of said Correspondent Node transmission towards connectionless transport layer shared data passage; The session identification of service conversation under the service message of each service conversation carries respectively, and the service message of said a plurality of service conversations that said Correspondent Node is sent sends to said a plurality of service customer end or a plurality of individual cloud desktop window;

A plurality of service customer ends 22 or a plurality of individual cloud desktop window 23 also are used for, and the service message of said a plurality of service conversations that said Correspondent Node is sent is handled.

Further; Said a plurality of service conversation comprises first service conversation, and said a plurality of service customer ends comprise with first service customer end of the service message of mutual said first service conversation of said Correspondent Node or said a plurality of individual cloud desktop window and comprise the first cloud desktop window with the service message of mutual said first service conversation of said Correspondent Node;

Said first service customer end or first people's cloud desktop window also are used for; Before the service message that generates said first service conversation; Generate the request of creating first service conversation; For said first service conversation distributes first call identification, said first call identification is added in the request of said establishment first service conversation, and the request of said establishment first service conversation is sent to said cloud client;

Cloud client 21 also comprises:

The conversation establishing module; Be used to receive the request of said establishment first service conversation; Set up the corresponding relation of said first service customer end or first people's cloud desktop window and first call identification, the request of said establishment first service conversation is sent to said Correspondent Node through said towards connectionless transport layer shared data passage; Through the said response that receives establishment first service conversation of said Correspondent Node transmission towards connectionless transport layer shared data passage; The response of said establishment first service conversation comprises first session identification and said first call identification; Corresponding relation according to said first service customer end or first the people's cloud desktop window and first call identification; Said first session identification and first call identification are sent to said first service customer end or first people's cloud desktop window, and set up the corresponding relation of said first session identification and said first service customer end or first people's cloud desktop window;

Said first service customer end or first people's cloud desktop window also are used for, and according to the corresponding relation of said first call identification and first service conversation, confirm that said first session identification is the session identification of said first service conversation;

Service interaction module 212 specifically is used for; Through the said service message that receives said first service conversation of said Correspondent Node transmission towards connectionless transport layer shared data passage; Said first session identification of setting up according to said conversation establishing module and the corresponding relation of said first service customer end or first people's cloud desktop window, said first service conversation that said Correspondent Node is sent service message send to said first service customer end or first people's cloud desktop window.

Wherein, said communication ends is equivalent to the sources traffic end in a kind of data communications method that the embodiment of the invention provides, and said Correspondent Node is equivalent to the destinations traffic end in a kind of data communications method that the embodiment of the invention provides.

A kind of data communications method that the concrete realization of present embodiment provides with reference to the embodiment of the invention is further with reference to Fig. 4, Fig. 6.The embodiment of the invention is through setting up between communication ends and Correspondent Node towards connectionless transport layer shared data passage; And the session identification of service conversation under in mutual service message, carrying; Making can be through the service message of the mutual a plurality of service conversations of a data passages between sources traffic end and destinations traffic end; Solved in the prior art under the situation of a large amount of voice and packet data concurrent service requests sources traffic end many with concurrent connection number between the destinations traffic end, be connected pressure greatly and data channel utilance low problem; Make that the shared data passage can be multiplexing for multi-service message, multi-service session; Reduce the concurrent connection number between sources traffic end and destinations traffic end, improved the utilance of data channel.Further, owing to adopt towards connectionless transport layer shared data passage, the destinations traffic end can push PUSH to the sources traffic end with content whenever and wherever possible, realizes the forever online of sources traffic end terminal.

The structural representation of another communication ends that Figure 12 provides for the embodiment of the invention.Shown in figure 12, this communication ends comprises: scheduling node 31 and the working node 32 that is connected with scheduling node 31;

Working node 32 is used for, and generates the service message of a plurality of service conversations and sends to scheduling node 31, the session identification of service conversation under the service message of each service conversation carries respectively;

Scheduling node 31 comprises:

Passage is set up module 311, be used for based on set up towards connectionless transport layer shared data PORT COM and Correspondent Node between towards connectionless transport layer shared data passage;

First interactive module 312, the service message of the said a plurality of service conversations that are used for working node 32 is sent sends to said Correspondent Node through said towards connectionless transport layer shared data passage;

Second interactive module 313; Be used for the service message that receives said a plurality of service conversations that said Correspondent Node sends towards connectionless transport layer shared data passage through said; The session identification of service conversation under the service message of each service conversation carries respectively, and the service message of said a plurality of service conversations that said Correspondent Node is sent sends to working node 32;

Working node 32 also is used for, and the service message of said a plurality of service conversations that said Correspondent Node is sent is handled.

Further, said a plurality of service conversation comprises first service conversation;

Second interactive module 312 specifically is used for; Through the said service message that receives said first service conversation of said Correspondent Node transmission towards connectionless transport layer shared data passage; Search the context environmental of the first corresponding service conversation of said first session identification according to first session identification in the service message of said first service conversation, and the service message of said first service conversation and the context environmental of said first service conversation are sent to working node 32; Working node 32 specifically is used for, and based on the context environmental of said first service conversation service message of said first service conversation is handled; Perhaps

Second interactive module 312 specifically is used for, and receives the service message of said first service conversation that said Correspondent Node sends through said towards connectionless transport layer shared data passage, and the service message of said first service conversation is sent to from working node 32; Working node 32 specifically is used for; Search the context environmental of the first corresponding service conversation of said first session identification according to first session identification in the service message of said first service conversation, the service message of said first service conversation is handled based on the context environmental of said first service conversation.

Wherein, said communication ends is equivalent to sources traffic end or the destinations traffic end in a kind of data communications method that the embodiment of the invention provides, and said Correspondent Node is equivalent to destinations traffic end or the sources traffic end in a kind of data communications method that the embodiment of the invention provides.

A kind of data communications method that the concrete realization of present embodiment provides with reference to the embodiment of the invention is further with reference to Fig. 3~9.The embodiment of the invention is through setting up between communication ends and Correspondent Node towards connectionless transport layer shared data passage; And the session identification of service conversation under in mutual service message, carrying; Making can be through the service message of the mutual a plurality of service conversations of a data passages between sources traffic end and destinations traffic end; Solved in the prior art under the situation of a large amount of voice and packet data concurrent service requests sources traffic end many with concurrent connection number between the destinations traffic end, be connected pressure greatly and data channel utilance low problem; Make that the shared data passage can be multiplexing for multi-service message, multi-service session; Reduce the concurrent connection number between sources traffic end and destinations traffic end, improved the utilance of data channel.Further, when between the cloud platform through when mutual, between the cloud platform unified entrance and outlet being provided towards connectionless transport layer shared data passage, improved the fail safe and the reliability of cloud platform further.

The structural representation of a kind of terminal equipment that Figure 13 provides for the embodiment of the invention.Shown in figure 13, terminal equipment generally comprises at least one processor 41, CPU for example, and at least one shared udp port 42, memory 43 and at least one communication bus 44 are used to realize the connection communication between these devices.Processor 41 is used for the executable module of execute store 43 storages, for example computer program; Terminal equipment is optional comprises user interface 45, includes but not limited to display, keyboard and pointing device, for example mouse, trace ball (trackball), touch-sensitive plate or touch sensitive display screen.Memory 43 possibly comprise the high-speed RAM memory, also possibly also comprise non-unsettled memory (non-volatile memory), for example at least one magnetic disc store.Realize that through at least one shared udp port 42 these terminal equipments are connected with communication between at least one cloud Platform Server, can internet usage, wide area network, local network, metropolitan area network etc.

In some embodiments, memory 43 has been stored following element, executable module or data structure, perhaps their subclass, perhaps their superset:

Operating system 431 comprises various system programs, is used to realize various basic businesses and handles hardware based task;

Application module 432 comprises various application programs, is used to realize various applied business.

Include but not limited to one of following module or its combination in the application module 432: a plurality of service customer ends or 4321, one cloud clients 4322 of individual cloud desktop window.

Include but not limited to one of following module or its combination in this cloud client 4322: passage is set up module, service interaction module, conversation establishing module.

The concrete realization of each module is referring to the corresponding module in Figure 11 A and the 11B illustrated embodiment in above-mentioned a plurality of service customer end or individual cloud desktop window 4321, cloud client 4322 and the cloud client 4322.

The structural representation of scheduling node in a kind of cloud Platform Server that Figure 14 provides for the embodiment of the invention.The cloud Platform Server generally comprises a scheduling node and a plurality of working node.Shown in figure 14, scheduling node generally comprises at least one processor 51, CPU for example, and at least one shared udp port 52 and other COM1s 56, memory 53 and at least one communication bus 54 are used to realize the connection communication between these devices.Processor 51 is used for the executable module of execute store 53 storages, for example computer program; Scheduling node is optional comprises user interface 55, includes but not limited to display, keyboard and pointing device, for example mouse, trace ball (trackball), touch-sensitive plate or touch sensitive display screen.Memory 53 possibly comprise the high-speed RAM memory, also possibly also comprise non-unsettled memory (non-volatile memory), for example at least one magnetic disc store.Scheduling node is realized the cloud Platform Server and is connected as the communication between the terminal equipment of Correspondent Node, non-cloud Platform Server or another cloud Platform Server through at least one shared udp port 52; Can internet usage; Wide area network, local network, metropolitan area network etc.Scheduling node through other COM1s 56 realize with same cloud Platform Server in communication between each working node be connected, can internet usage, wide area network, local network, metropolitan area network etc.

In some embodiments, memory 53 has been stored following element, executable module or data structure, perhaps their subclass, perhaps their superset:

Operating system 531 comprises various system programs, is used to realize various basic businesses and handles hardware based task;

Application module 532 comprises various application programs, is used to realize various applied business.

Include but not limited to one of following module or its combination in the application module 532: passage is set up module, first interactive module, second interactive module.

Above-mentioned passage is set up the concrete realization of module, first interactive module, second interactive module referring to the corresponding module in embodiment illustrated in fig. 12.

The structural representation of working node in a kind of cloud Platform Server that Figure 15 provides for the embodiment of the invention.Shown in figure 15, working node generally comprises at least one processor 61, CPU for example, and COM1 62, memory 63 and at least one communication bus 64 are used to realize the connection communication between these devices.Processor 61 is used for the executable module of execute store 63 storages, for example computer program; Working node is optional comprises user interface 65, includes but not limited to display, keyboard and pointing device, for example mouse, trace ball (trackball), touch-sensitive plate or touch sensitive display screen.Memory 63 possibly comprise the high-speed RAM memory, also possibly also comprise non-unsettled memory (non-volatile memory), for example at least one magnetic disc store.Working node through COM1 62 realize with same cloud Platform Server in communication between the scheduling node be connected, can internet usage, wide area network, local network, metropolitan area network etc.

In some embodiments, memory 63 has been stored following element, executable module or data structure, perhaps their subclass, perhaps their superset:

Operating system 631 comprises various system programs, is used to realize various basic businesses and handles hardware based task;

Application module 632 comprises various application programs, is used to realize various applied business.Application module 632 includes but not limited to realize following function: generate the service message of a plurality of service conversations and send to scheduling node, the session identification of service conversation under the service message of each service conversation carries respectively; The service message of said a plurality of service conversations that the said Correspondent Node that scheduling node is transmitted sends is handled.Specifically referring to the working node in embodiment illustrated in fig. 12.

Communication ends embodiment described above only is schematic; Wherein said module, unit as the separating component explanation can or can not be physically to separate also; The parts that show as module, unit can be or can not be physical locations also; Promptly can be positioned at a place, perhaps also can be distributed on a plurality of NEs.Can realize the purpose of present embodiment scheme according to needs selection some or all of module, the unit wherein of reality.Those of ordinary skills promptly can understand and implement under the situation of not paying performing creative labour.

Through the description of above execution mode, those skilled in the art can be well understood to each execution mode and can realize by the mode that software adds essential general hardware platform, can certainly pass through hardware.Based on such understanding; The part that technique scheme contributes to prior art in essence in other words can be come out with the embodied of software product; This computer software product can be stored in the computer-readable recording medium, like ROM/RAM, magnetic disc, CD etc., comprises that some instructions are with so that a computer equipment (can be a personal computer; Server, perhaps network equipment etc.) carry out the described method of some part of each embodiment or embodiment.

What should explain at last is: above each embodiment is only in order to explaining technical scheme of the present invention, but not to its restriction; Although the present invention has been carried out detailed explanation with reference to aforementioned each embodiment; Those of ordinary skill in the art is to be understood that: it still can be made amendment to the technical scheme that aforementioned each embodiment put down in writing, perhaps to wherein part or all technical characteristic are equal to replacement; And these are revised or replacement, do not make the scope of the essence disengaging various embodiments of the present invention technical scheme of relevant art scheme.

Claims (24)

1. a data communications method is characterized in that, comprising:
The sources traffic end group in set up towards connectionless transport layer shared data PORT COM and the destinations traffic end between towards connectionless transport layer shared data passage;
Said sources traffic end is through said service message towards connectionless transport layer shared data passage and the mutual a plurality of service conversations of said destinations traffic end, and the service message of each service conversation carries the session identification of affiliated service conversation respectively.
2. method according to claim 1 is characterized in that, said sources traffic end group in set up towards connectionless transport layer shared data PORT COM with the destinations traffic end between also comprising before towards connectionless transport layer shared data passage:
Said sources traffic end distributes said towards connectionless transport layer shared data PORT COM;
Said sources traffic end group in set up towards connectionless transport layer shared data PORT COM and said destinations traffic end between comprising towards connectionless transport layer shared data passage:
Said sources traffic end group is said towards connectionless transport layer shared data passage towards setting up towards connectionless transport layer shared data PORT COM of connectionless transport layer shared data PORT COM and the distribution of said destinations traffic end in said distribution.
3. method according to claim 2 is characterized in that, said sources traffic end comprises through said service message towards connectionless transport layer shared data passage and the mutual a plurality of service conversations of said destinations traffic end:
Said sources traffic end generates the service message of said a plurality of service conversations, through the said service message that sends said a plurality of service conversations towards connectionless transport layer shared data passage to said destinations traffic end;
Said sources traffic end receives the service message of said a plurality of service conversations that said destinations traffic end sends through said towards connectionless transport layer shared data passage, and the session identification of the affiliated service conversation that carries according to each service message is handled each service message.
4. method according to claim 3 is characterized in that, said sources traffic end also comprised before the service message of connectionless transport layer shared data passage and the mutual a plurality of service conversations of said destinations traffic end through said:
Said sources traffic end is initiated the request of a plurality of establishment service conversations towards connectionless transport layer shared data passage to said destinations traffic end through said, so that said destinations traffic end is created said a plurality of service conversation and is said a plurality of service conversations difference assign sessions signs according to the request of said a plurality of establishment service conversations;
Receive the response of a plurality of establishment service conversations that said destinations traffic end returns, the session identification of service conversation under each response comprises respectively through said towards connectionless transport layer shared data passage.
5. method according to claim 4 is characterized in that, said sources traffic end comprises the cloud client, and said destinations traffic end comprises the cloud Platform Server, and said cloud Platform Server comprises scheduling node and the working node that is connected with said scheduling node;
Said sources traffic end distribution is said to be comprised towards connectionless transport layer shared data PORT COM:
Said cloud client is distributed said towards connectionless transport layer shared data PORT COM;
Said sources traffic end group saidly comprises towards connectionless transport layer shared data passage towards setting up towards connectionless transport layer shared data PORT COM of distributing of connectionless transport layer shared data PORT COM and said destinations traffic end in said distribution:
Said cloud client is said towards connectionless transport layer shared data passage towards setting up towards connectionless transport layer shared data PORT COM of connectionless transport layer shared data PORT COM and the distribution of said scheduling node based on said distribution;
Saidly comprise to the service message that said destinations traffic end sends said a plurality of service conversations towards connectionless transport layer shared data passage through said:
Said cloud client is sent the service message of said a plurality of service conversations towards connectionless transport layer shared data passage to said scheduling node through said so that said scheduling node respectively with said a plurality of service messages send to said working node, said working node is handled each service message according to the session identification of the affiliated service conversation that each service message carries;
Said sources traffic end comprises through the said service message that receives said a plurality of service conversations that said destinations traffic end sends towards connectionless transport layer shared data passage:
Said cloud client is through the said service message that receives said a plurality of service conversations of said scheduling node transmission towards connectionless transport layer shared data passage.
6. method according to claim 5 is characterized in that, the service message that said sources traffic end generates said a plurality of service conversations comprises:
Said cloud client generates the service message of said a plurality of service conversations;
The session identification of the said affiliated service conversation that carries according to each service message is handled each service message and is comprised:
Said cloud client is handled each service message according to the session identification of the affiliated service conversation that each service message carries.
7. method according to claim 5 is characterized in that, said sources traffic end also comprises a plurality of service customer ends or a plurality of individual cloud desktop window that is connected with said cloud client;
The service message that said sources traffic end generates said a plurality of service conversations comprises:
Said a plurality of service customer end or a plurality of individual cloud desktop window generate the service message of said a plurality of service conversations, and the service message of said a plurality of service conversations is sent to said cloud client;
The session identification of the said affiliated service conversation that carries according to each service message is handled each service message and is comprised:
Said cloud client sends to said a plurality of service customer end or a plurality of individual cloud desktop window with the service message of said a plurality of service conversations, and said a plurality of service customer ends or a plurality of individual cloud desktop window are handled each service message according to the session identification of the affiliated service conversation that each service message carries.
8. method according to claim 7 is characterized in that, said a plurality of service conversations comprise first service conversation;
Said sources traffic end comprises through the said request of initiating a plurality of establishment service conversations to said destinations traffic end towards connectionless transport layer shared data passage:
First people's cloud desktop window in first service customer end in said a plurality of service customer end or the said a plurality of individual cloud desktop window generates the request of creating first service conversation; For said first service conversation distributes first call identification; Said first call identification is added in the request of said establishment first service conversation, and the request of said establishment first service conversation is sent to said cloud client;
Said cloud client is set up the corresponding relation of said first service customer end or first the people's cloud desktop window and first call identification, and with the request of said establishment first service conversation through giving said scheduling node towards connectionless transport layer shared data passage;
Saidly receive the response that said destinations traffic end returns a plurality of establishment service conversations towards connectionless transport layer shared data passage and comprise through said:
Said cloud client receives the response of establishment first service conversation that said scheduling node returns through said towards connectionless transport layer shared data passage, and the response of said establishment first service conversation comprises first session identification and said first call identification;
Corresponding relation according to said first service customer end or first the people's cloud desktop window and first call identification; Said first session identification and first call identification are sent to said first service customer end or first people's cloud desktop window, and confirm the corresponding relation of said first session identification and said first service customer end or first people's cloud desktop window;
Said first service customer end or first people's cloud desktop window confirm that according to the corresponding relation of said first call identification and first service conversation said first session identification is the session identification of said first service conversation;
The service message of said a plurality of service conversations is sent to said a plurality of service customer end to said cloud client or a plurality of individual cloud desktop window comprises:
Said first session identification that comprises in the service message of said cloud client according to said first service conversation; And the corresponding relation of said first session identification and said first service customer end or first people's cloud desktop window, the service message of said first service conversation is sent to said first service customer end or first people's cloud desktop window.
9. method according to claim 4 is characterized in that, said sources traffic end comprises the cloud Platform Server, and the destinations traffic end comprises another cloud Platform Server, and each cloud Platform Server includes scheduling node and the working node that is connected with said scheduling node;
Said sources traffic end distribution is said to be comprised towards connectionless transport layer shared data PORT COM:
The scheduling node of said sources traffic end distributes said towards connectionless transport layer shared data PORT COM;
Said sources traffic end group saidly comprises towards connectionless transport layer shared data passage towards setting up towards connectionless transport layer shared data PORT COM of distributing of connectionless transport layer shared data PORT COM and said destinations traffic end in said distribution:
The scheduling node of said sources traffic end is said towards connectionless transport layer shared data passage towards setting up towards connectionless transport layer shared data PORT COM of distributing of the scheduling node of connectionless transport layer shared data PORT COM and said destinations traffic end based on said distribution;
Said sources traffic end comprises to the service message that said destinations traffic end sends said a plurality of service conversations towards connectionless transport layer shared data passage through said:
The working node of said sources traffic end sends the service message of said a plurality of service conversations respectively to the scheduling node of said sources traffic end; The scheduling node of said sources traffic end sends the service message of said a plurality of service conversations towards connectionless transport layer shared data passage to the scheduling node of said destinations traffic end through said, so that the session identification of the affiliated service conversation that the working node that the scheduling node of said destinations traffic end sends to the working node of said destinations traffic end, said destinations traffic end with said a plurality of service messages respectively carries according to each service message is handled each service message;
Said sources traffic end comprises through the said service message that receives said a plurality of service conversations that said destinations traffic end sends towards connectionless transport layer shared data passage:
The scheduling node of said sources traffic end is through the said service message that receives said a plurality of service conversations that the scheduling node of said destinations traffic end sends towards connectionless transport layer shared data passage;
The scheduling node of said sources traffic end sends to the working node of said sources traffic end respectively with the service message of said a plurality of service conversations, and the working node of said sources traffic end is handled each service message respectively according to the session identification of the affiliated service conversation that each service message carries.
10. method according to claim 9; It is characterized in that; The service message of said a plurality of service conversations comprises the service message of first service conversation; The scheduling node of said sources traffic end sends to the working node of said sources traffic end respectively with the service message in said a plurality of service conversations, and the session identification of the affiliated service conversation that the working node of said sources traffic end carries according to each service message is handled each service message respectively and comprised:
The scheduling node of said sources traffic end is searched the context environmental of the first corresponding service conversation of said first session identification according to first session identification in the service message of said first service conversation; And the context environmental of the service message of said first service conversation and said first service conversation sent to the working node of said sources traffic end, the working node of said sources traffic end is handled the service message of said first service conversation based on the context environmental of said first service conversation; Perhaps
The scheduling node of said sources traffic end sends to the service message of said first service conversation from the working node of said sources traffic end; The working node of said sources traffic end is searched the context environmental of the first corresponding service conversation of said first session identification according to first session identification in the service message of said first service conversation, based on the context environmental of said first service conversation service message of said first service conversation is handled.
11. method according to claim 4 is characterized in that, said sources traffic end comprises the cloud Platform Server, and said destinations traffic end comprises non-cloud Platform Server; Perhaps, said sources traffic end comprises non-cloud Platform Server, and said destinations traffic end comprises the cloud Platform Server.
12., it is characterized in that said sources traffic end also comprises after the service message of connectionless transport layer shared data passage and the mutual a plurality of service conversations of said destinations traffic end through said according to each described method among the claim 4-11:
Said sources traffic end is through said request from connectionless transport layer shared data passage to said destinations traffic end that initiate a plurality of winding-up sessions towards; The session identification of service conversation under each request is carried respectively is so that said destinations traffic end is deleted said a plurality of service conversation.
13., it is characterized in that said destinations traffic end is a plurality of according to each described method among the claim 4-12;
Said sources traffic end group saidly comprises towards connectionless transport layer shared data passage towards setting up towards connectionless transport layer shared data PORT COM of distributing of connectionless transport layer shared data PORT COM and said destinations traffic end in said distribution:
Said sources traffic end group in said distribution distribute towards connectionless transport layer shared data PORT COM and each destinations traffic end set up respectively towards connectionless transport layer shared data PORT COM and each destinations traffic end between towards connectionless transport layer shared data passage;
Saidly comprise to the service message that said destinations traffic end sends said a plurality of service conversations towards connectionless transport layer shared data passage through said:
Said sources traffic end is according to the address information of the destinations traffic end that carries in each service message, through sending each service message respectively towards connectionless transport layer shared data passage between the destinations traffic end corresponding with said address information.
14. a communication ends is characterized in that, comprising:
Passage is set up module, be used for based on set up towards connectionless transport layer shared data PORT COM and Correspondent Node between towards connectionless transport layer shared data passage;
The service interaction module is used for through said service message towards connectionless transport layer shared data passage and the mutual a plurality of service conversations of said Correspondent Node, the session identification of service conversation under the service message of each service conversation carries respectively.
15. communication ends according to claim 14 is characterized in that, also comprises:
The port assignment module is used to distribute said towards connectionless transport layer shared data PORT COM;
Said passage is set up module and specifically is used for, said towards connectionless transport layer shared data passage towards setting up towards connectionless transport layer shared data PORT COM of distributing of connectionless transport layer shared data PORT COM and said Correspondent Node based on said distribution.
16. communication ends according to claim 15 is characterized in that, said service interaction module specifically comprises:
First interactive unit is used to generate the service message of said a plurality of service conversations, through the said service message that sends said a plurality of service conversations towards connectionless transport layer shared data passage to said Correspondent Node;
Second interactive unit; Be used for receiving the service message of said a plurality of service conversations that said Correspondent Node sends through said towards connectionless transport layer shared data passage, the session identification of the affiliated service conversation that carries according to each service message is handled each service message.
17. communication ends according to claim 16 is characterized in that, also comprises:
The conversation establishing module; Be used for initiating the request of a plurality of establishment service conversations towards connectionless transport layer shared data passage to said Correspondent Node, so that said Correspondent Node is created said a plurality of service conversation and is said a plurality of service conversations difference assign sessions signs according to the request of said a plurality of establishment service conversations through said; Receive the response that said Correspondent Node returns a plurality of establishment service conversations through said towards connectionless transport layer shared data passage, the session identification of service conversation under each response comprises respectively.
18. communication ends according to claim 17 is characterized in that, also comprises:
The conversation end module; Be used for the request of initiating a plurality of winding-up sessions to said Correspondent Node towards connectionless transport layer shared data passage through said; The session identification of service conversation under each request is carried respectively is so that said Correspondent Node is deleted said a plurality of service conversation.
19. communication ends according to claim 16 is characterized in that, said Correspondent Node is a plurality of;
Said passage is set up module and specifically is used for, based on said distribution towards connectionless transport layer shared data PORT COM and each Correspondent Node distribute towards connectionless transport layer shared data PORT COM set up respectively and each Correspondent Node between towards connectionless transport layer shared data passage;
Said first interactive unit specifically is used for, according to the address information of the Correspondent Node that carries in each service message, through sending each service message respectively towards connectionless transport layer shared data passage between the Correspondent Node corresponding with said address information.
20., it is characterized in that when said Correspondent Node was the cloud Platform Server, said communication ends was terminal equipment, cloud Platform Server or non-cloud Platform Server according to each described communication ends among the claim 14-19; When said Correspondent Node was non-cloud Platform Server, said communication ends was the cloud Platform Server.
21. a communication ends is characterized in that, comprising: cloud client and a plurality of service customer ends that are connected with said cloud client or a plurality of individual cloud desktop window;
Said a plurality of service customer end or a plurality of individual cloud desktop window are used for, and generate the service message of said a plurality of service conversations and send to said cloud client, the session identification of service conversation under the service message of each service conversation carries respectively;
Said cloud client comprises:
Passage is set up module, be used for based on set up towards connectionless transport layer shared data PORT COM and Correspondent Node between towards connectionless transport layer shared data passage;
The service interaction module, the service message of a plurality of service conversations that are used for said a plurality of service customer ends or a plurality of individual cloud desktop are sent is said to send to said Correspondent Node through said towards connectionless transport layer shared data passage; Through the said service message that receives said a plurality of service conversations of said Correspondent Node transmission towards connectionless transport layer shared data passage; The session identification of service conversation under the service message of each service conversation carries respectively, and the service message of said a plurality of service conversations that said Correspondent Node is sent sends to said a plurality of service customer end or a plurality of individual cloud desktop window;
Said a plurality of service customer end or a plurality of individual cloud desktop window also are used for, and the service message of said a plurality of service conversations that said Correspondent Node is sent is handled.
22. communication ends according to claim 21; It is characterized in that; Said a plurality of service conversation comprises first service conversation, and said a plurality of service customer ends comprise with first service customer end of the service message of mutual said first service conversation of said Correspondent Node or said a plurality of individual cloud desktop window and comprise the first cloud desktop window with the service message of mutual said first service conversation of said Correspondent Node;
Said first service customer end or first people's cloud desktop window also are used for; Before the service message that generates said first service conversation; Generate the request of creating first service conversation; For said first service conversation distributes first call identification, said first call identification is added in the request of said establishment first service conversation, and the request of said establishment first service conversation is sent to said cloud client;
Said cloud client also comprises:
The conversation establishing module; Be used to receive the request of said establishment first service conversation; Set up the corresponding relation of said first service customer end or first people's cloud desktop window and first call identification, the request of said establishment first service conversation is sent to said Correspondent Node through said towards connectionless transport layer shared data passage; Through the said response that receives establishment first service conversation of said Correspondent Node transmission towards connectionless transport layer shared data passage; The response of said establishment first service conversation comprises first session identification and said first call identification; Corresponding relation according to said first service customer end or first the people's cloud desktop window and first call identification; Said first session identification and first call identification are sent to said first service customer end or first people's cloud desktop window, and set up the corresponding relation of said first session identification and said first service customer end or first people's cloud desktop window;
Said first service customer end or first people's cloud desktop window also are used for, and according to the corresponding relation of said first call identification and first service conversation, confirm that said first session identification is the session identification of said first service conversation;
Said service interaction module specifically is used for; Through the said service message that receives said first service conversation of said Correspondent Node transmission towards connectionless transport layer shared data passage; Said first session identification of setting up according to said conversation establishing module and the corresponding relation of said first service customer end or first people's cloud desktop window, said first service conversation that said Correspondent Node is sent service message send to said first service customer end or first people's cloud desktop window.
23. a communication ends is characterized in that, comprising: scheduling node and the working node that is connected with said scheduling node;
Said working node is used for, and generates the service message of a plurality of service conversations and sends to said scheduling node, the session identification of service conversation under the service message of each service conversation carries respectively;
Said scheduling node comprises:
Passage is set up module, be used for based on set up towards connectionless transport layer shared data PORT COM and Correspondent Node between towards connectionless transport layer shared data passage;
First interactive module, the service message of the said a plurality of service conversations that are used for said working node is sent sends to said Correspondent Node through said towards connectionless transport layer shared data passage;
Second interactive module; Be used for the service message that receives said a plurality of service conversations that said Correspondent Node sends towards connectionless transport layer shared data passage through said; The session identification of service conversation under the service message of each service conversation carries respectively, and the service message of said a plurality of service conversations that said Correspondent Node is sent sends to said working node;
Said working node also is used for, and the service message of said a plurality of service conversations that said Correspondent Node is sent is handled.
24. communication ends according to claim 23 is characterized in that, said a plurality of service conversations comprise first service conversation;
Said second interactive module specifically is used for; Through the said service message that receives said first service conversation of said Correspondent Node transmission towards connectionless transport layer shared data passage; Search the context environmental of the first corresponding service conversation of said first session identification according to first session identification in the service message of said first service conversation, and the service message of said first service conversation and the context environmental of said first service conversation are sent to said working node; Said working node specifically is used for, and based on the context environmental of said first service conversation service message of said first service conversation is handled; Perhaps
Said second interactive module specifically is used for; Receive the service message of said first service conversation that said Correspondent Node sends through said towards connectionless transport layer shared data passage, the service message of said first service conversation is sent to from said working node; Said working node specifically is used for; Search the context environmental of the first corresponding service conversation of said first session identification according to first session identification in the service message of said first service conversation, the service message of said first service conversation is handled based on the context environmental of said first service conversation.
CN201210106752.7A 2012-04-12 2012-04-12 Data communicating method and communication end CN102638582B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201210106752.7A CN102638582B (en) 2012-04-12 2012-04-12 Data communicating method and communication end

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201210106752.7A CN102638582B (en) 2012-04-12 2012-04-12 Data communicating method and communication end

Publications (2)

Publication Number Publication Date
CN102638582A true CN102638582A (en) 2012-08-15
CN102638582B CN102638582B (en) 2015-07-08

Family

ID=46622823

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201210106752.7A CN102638582B (en) 2012-04-12 2012-04-12 Data communicating method and communication end

Country Status (1)

Country Link
CN (1) CN102638582B (en)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102801737A (en) * 2012-08-28 2012-11-28 北京城市网邻信息技术有限公司 Asynchronous network communication method and device
CN103607600A (en) * 2013-11-19 2014-02-26 乐视致新电子科技(天津)有限公司 Method and device for cloud backup
CN103905509A (en) * 2012-12-30 2014-07-02 青岛海尔软件有限公司 Information push system and information push method based on wide area network in Internet-of-Things applications
WO2015101234A1 (en) * 2013-12-30 2015-07-09 Tencent Technology (Shenzhen) Company Limited A data transfer method and system
CN105847217A (en) * 2015-01-12 2016-08-10 阿里巴巴集团控股有限公司 Multi-service session concurrence method and system

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101184052A (en) * 2007-12-25 2008-05-21 北京广视通达网络技术有限公司 Congestion control method of implementing reliable UDP transmission
WO2010150848A1 (en) * 2009-06-25 2010-12-29 ヤマハ株式会社 Communication device
CN102045362A (en) * 2010-12-21 2011-05-04 北京高森明晨信息科技有限公司 Data transmission method and system based on UDP protocol
CN102137032A (en) * 2011-03-24 2011-07-27 上海云高软件科技有限公司 Cloud message system and cloud message transmitting and receiving method

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101184052A (en) * 2007-12-25 2008-05-21 北京广视通达网络技术有限公司 Congestion control method of implementing reliable UDP transmission
WO2010150848A1 (en) * 2009-06-25 2010-12-29 ヤマハ株式会社 Communication device
CN102045362A (en) * 2010-12-21 2011-05-04 北京高森明晨信息科技有限公司 Data transmission method and system based on UDP protocol
CN102137032A (en) * 2011-03-24 2011-07-27 上海云高软件科技有限公司 Cloud message system and cloud message transmitting and receiving method

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102801737A (en) * 2012-08-28 2012-11-28 北京城市网邻信息技术有限公司 Asynchronous network communication method and device
CN102801737B (en) * 2012-08-28 2016-04-27 北京城市网邻信息技术有限公司 A kind of asynchronous network communication means and device
CN103905509A (en) * 2012-12-30 2014-07-02 青岛海尔软件有限公司 Information push system and information push method based on wide area network in Internet-of-Things applications
CN103607600A (en) * 2013-11-19 2014-02-26 乐视致新电子科技(天津)有限公司 Method and device for cloud backup
WO2015101234A1 (en) * 2013-12-30 2015-07-09 Tencent Technology (Shenzhen) Company Limited A data transfer method and system
US10181963B2 (en) 2013-12-30 2019-01-15 Tencent Technology (Shenzhen) Company Limited Data transfer method and system
CN105847217A (en) * 2015-01-12 2016-08-10 阿里巴巴集团控股有限公司 Multi-service session concurrence method and system
CN105847217B (en) * 2015-01-12 2019-09-06 阿里巴巴集团控股有限公司 The method and its system of concurrent multi-service session

Also Published As

Publication number Publication date
CN102638582B (en) 2015-07-08

Similar Documents

Publication Publication Date Title
CN104348710B (en) For the method and system for obtaining with associating WEB real-time Communication for Power interaction properties of flow
US10341427B2 (en) Forwarding policies on a virtual service network
US8996618B2 (en) System and method for providing sequenced anonymous communication sessions over a network
EP3284211B1 (en) Handling conferences using highly-distributed agents
Jennings et al. Real-time communications for the web
CN102238226B (en) Conversation shift on the network centered by content
CN104113879B (en) It is deployed with cloud AC WiFi communication system and communication means
CN104253857B (en) Virtual WEB real-time Communication for Power agency is with and related methods, system back-to-back
US20140244473A1 (en) System and methods for matching electronic proposals to electronic requests
CN103051629B (en) Software defined network-based data processing system, method and node
CN104796396B (en) The method and medium of network agent layer for the application proxy based on strategy are provided
US6178453B1 (en) Virtual circuit switching architecture
Turner et al. Diversifying the internet
EP1494410B1 (en) Method and device for instant messaging
CN101741832B (en) Method and system for dispatching received sessions between a plurality of instances of an application using the same ip port
Belqasmi et al. Soap-based vs. restful web services: A case study for multimedia conferencing
JP2013524632A (en) Management of network communication between network nodes and stream transport protocol
US8885012B2 (en) System and method for providing anonymity in a video/multimedia communications session over a network
CN103188339A (en) Connecting on-premise networks with public clouds
US9178925B2 (en) Exchanging media stream data between thin client and media gateway, bypassing virtual machine, in cloud computing system
CN103339910B (en) Full-duplex bi-directional communication over a remote procedure call based communications protocol, and applications thereof
CN101247361B (en) Member dynamic information display system and method in user group
US20010054070A1 (en) Facilitating real-time, multi-point communications over the internet
CN103188300B (en) The methods, devices and systems of VOIP phone are realized in cloud computing environment
CN1311658C (en) Configuration means and a data processing method

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