CN102638582B

CN102638582B - Data communicating method and communication end

Info

Publication number: CN102638582B
Application number: CN201210106752.7A
Authority: CN
Inventors: 胡汉强
Original assignee: Huawei Technologies Co Ltd
Current assignee: Guangdong Gaohang Intellectual Property Operation Co ltd; Taizhou Haitong Asset Management Co ltd
Priority date: 2012-04-12
Filing date: 2012-04-12
Publication date: 2015-07-08
Anticipated expiration: 2032-04-12
Also published as: CN102638582A

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 present invention relates to the communication technology, particularly relates to a kind of data communications method and communication ends.

Background technology

The platform that cloud platform is in the resource set such as calculating, storage, network, a buffer memory, various service is shared, provided as required to elasticity, usual cloud platform can in the face of the Concurrency Access of mass users, the service request of concurrent processing mass users.In prior art, session between cloud client and cloud platform is HTML (Hypertext Markup Language) (the HyperText Transfer Protocol by stateless (stateless), be called for short HTTP)/Secure Hypertext Transfer Protocol (HyperText Transfer Protocol over Secure Socket Layer, be called for short HTTPS) ask, wherein, cloud client refers on terminal equipment for the Agent mutual with cloud platform.The data channel based on transmission control protocol (Transmission Control Protocol is called for short TCP) short connection is set up in each HTTP/HTTPS request of cloud client respectively with cloud platform, request response terminates rear closedown data channel.For example, the client of a lot of service application is had in smart mobile phone, and user can open multiple service customer end (such as microblogging or internet game) simultaneously, respectively with the server communication in high in the clouds, if the client of each service application is initiated and being independently connected of cloud platform on mobile phone, concurrent connection number on the one hand between mobile phone and cloud platform can increase greatly, the Bonding pressure of cloud platform can increase the weight of greatly, and the utilance of data channel is lower, the concurrent radio bearer number (eating dishes without rice or wine) on the other hand between mobile phone and base station also can increase greatly.

Sometimes, also need between cloud platform to interconnect, usual cloud platform externally only provides a shared entrance and exit in order to security consideration, the customer service session data transmitting magnanimity is needed between two shared gateways between two cloud platforms, if cloud platform is initiated and being independently connected of another cloud platform for each service request, concurrent connection number between cloud platform also can increase greatly, and the Bonding pressure of cloud platform also can increase the weight of greatly, and the utilance of data channel is lower.

Realizing in process of the present invention, inventor finds that in prior art, at least there are the following problems: when a large amount of voice and packet data concurrent service request, the concurrent connection number between sources traffic end and destinations traffic end is many, Bonding pressure large and data channel utilance is low.

Summary of the invention

The embodiment of the present invention provides a kind of data communications method and communication ends, and in order to solve, concurrent connection number in prior art when a large amount of voice and packet data concurrent service request between sources traffic end and destinations traffic end is many, Bonding pressure large and the problem that data channel utilance is low.

First aspect of the embodiment of the present invention is to provide a kind of data communications method, comprising:

Sources traffic end group in share towards connectionless transport layer data communication port set up with destinations traffic end between share data channel towards connectionless transport layer;

Described sources traffic end is by the described service message sharing data channel and the mutual multiple service conversation of described destinations traffic end towards connectionless transport layer.

Another aspect of the embodiment of the present invention is to provide a kind of communication ends, comprising:

Path Setup module, for based on share towards connectionless transport layer data communication port set up with Correspondent Node between share data channel towards connectionless transport layer;

Service interaction module, for by the described service message sharing data channel and the mutual multiple service conversation of described Correspondent Node towards connectionless transport layer.

Another aspect of the embodiment of the present invention is to provide a kind of communication ends, comprising: cloud client and with multiple service customer end of described cloud client's side link or multiple individual cloud desktop window;

Described multiple service customer end or multiple individual cloud desktop window are used for, and generate the service message of described multiple service conversation and send to described cloud client;

Described cloud client comprises:

Service interaction module, for being shared data channel towards connectionless transport layer sent to described Correspondent Node by described described in the service message of multiple service conversations that described multiple service customer end or multiple individual cloud desktop sent; Share towards connectionless transport layer the service message that data channel receives described multiple service conversation that described Correspondent Node sends by described, and the service message of the described multiple service conversation sent by described Correspondent Node sends to described multiple service customer end or multiple individual cloud desktop window;

Described multiple service customer end or multiple individual cloud desktop window also for, the service message of described multiple service conversation that described Correspondent Node sends is processed.

Another aspect of the embodiment of the present invention is to provide a kind of communication ends, comprising: scheduling node and the working node be connected with described scheduling node;

Described working node is used for, and generates the service message of multiple service conversation and sends to described scheduling node;

Described scheduling node comprises:

First interactive module, is shared data channel towards connectionless transport layer for the service message of described multiple service conversation that sent by described working node sent to described Correspondent Node by described;

Second interactive module, for sharing towards connectionless transport layer the service message that data channel receives described multiple service conversation that described Correspondent Node sends by described, and the service message of the described multiple service conversation sent by described Correspondent Node sends to described working node;

Described working node also for, the service message of described multiple service conversation that described Correspondent Node sends is processed.

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

The embodiment of the present invention shares data channel by setting up between sources traffic end and destinations traffic end towards connectionless transport layer, and in mutual service message, carry the session identification of affiliated service conversation, make sources traffic end and destinations traffic end can by the service message of a mutual multiple service conversation of data channel, the concurrent connection number solved in prior art when a large amount of voice and packet data concurrent service request between sources traffic end and destinations traffic end is many, large and the problem that data channel utilance is low of Bonding pressure, make shared data channel can be multi-service message, multi-service session is multiplexing, decrease the concurrent connection number between sources traffic end and destinations traffic end, improve the utilance of data channel.

Accompanying drawing explanation

In order to be illustrated more clearly in the embodiment of the present invention or technical scheme of the prior art, be briefly described to the accompanying drawing used required in embodiment or description of the prior art below, apparently, accompanying drawing in the following describes is some embodiments of the present invention, for those of ordinary skill in the art, under the prerequisite not paying creative work, other accompanying drawing can also be obtained according to these accompanying drawings.

Fig. 1 is a kind of system architecture schematic diagram of the embodiment of the present invention;

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

Fig. 3 is the system architecture schematic diagram of a kind of application scenarios of the embodiment of the present invention;

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

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

Fig. 6 is the system architecture schematic diagram of another application scenarios of the embodiment of the present invention;

Fig. 7 is the system architecture schematic diagram of another application scenarios of the embodiment of the present invention;

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

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

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

The structural representation of another communication ends that Figure 11 A provides for the embodiment of the present invention;

The structural representation of another communication ends that Figure 11 B provides for the embodiment of the present invention;

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

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

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

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

Embodiment

For making the object of the embodiment of the present invention, technical scheme and advantage clearly, below in conjunction with the accompanying drawing in the embodiment of the present invention, technical scheme in the embodiment of the present invention is clearly and completely described, obviously, described embodiment is the present invention's part embodiment, instead of whole embodiments.Based on the embodiment in the present invention, those of ordinary skill in the art, not making the every other embodiment obtained under creative work prerequisite, belong to the scope of protection of the invention.

Fig. 1 is a kind of system architecture schematic diagram of the embodiment of the present invention.As shown in Figure 1, system comprises sources traffic end and destinations traffic end, or is called communication ends and Correspondent Node.Wherein, sources traffic end can be terminal equipment, comprise catv terminal and wireless terminal, as computer, mobile phone terminal, panel computer, internet of things sensors etc., also can be the cloud Platform Server (also can be described as cloud platform) as client or general server (also can be called non-cloud Platform Server or non-cloud platform).Destinations traffic end can be cloud Platform Server as server or general server.

Under the system architecture shown in Fig. 1, sources traffic end is responsible for distributing and fixing is shared data communication port (also can be called high in the clouds mouth) towards connectionless transport layer, as sharing users data pack protocol (UserDatagram Protocol, be called for short UDP) port, set up and share data channel towards connectionless transport layer, as shared UDP message passage based on high in the clouds mouth between sources traffic end and destinations traffic end, after sources traffic end initiates two or more different service conversation requests to create (request also referred to as creating service conversation) to destinations traffic end, the session identification (Session ID) that the different business conversation establishing request that receiving target communication ends returns after creating corresponding service conversation Session is corresponding, the srvice instance that on follow-up sources traffic end, these two or more different service conversation request to create is corresponding and the interacting message of destinations traffic end are all by sharing data channel to transmit based on high in the clouds mouth between sources traffic end and destinations traffic end towards connectionless transport layer, and on sources traffic end, in these different business examples and the follow-up mutual message of destinations traffic end, carry the Session ID of affiliated service conversation respectively, so that the message area of sharing these different business sessions transmitted in data channel towards connectionless transport layer is separated.Wherein, the message of these different business sessions can support different application layer protocols, as: real time transport protocol (Real-time Transport Protocol, be called for short RTP) or transport stream (Transport Stream, be 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 packaging of one deck outside embody rule layer protocol, and in same packaging, fill out Session ID, the uniform protocol of having packed remains the agreement of application layer; Also concrete application layer protocol can be revised, as RTP, inside packet header Session ID being expanded to application layer protocol.Finally, sources traffic end sends service conversation ending request to destinations traffic end, and destinations traffic end deletes corresponding service conversation.

Destinations traffic end is responsible for distributing stationary plane and is shared data communication port (also can be called high in the clouds mouth) to connectionless transport layer, as shared udp port, set up and share data channel towards connectionless transport layer, as shared UDP message passage based on high in the clouds mouth between sources traffic end and destinations traffic end.After sources traffic end initiates two or more different service conversation requests to create to destinations traffic end, destinations traffic end creates service conversation Session corresponding to these different business session service requests, be respectively service conversation corresponding to these service conversation requests to create and distribute session identification Session ID, and these Session ID are returned to sources traffic end, the interacting message of the srvice instance that succeeding target communication ends is corresponding from these two or more different service conversation request to create on sources traffic end is all by sharing data channel to transmit based on high in the clouds mouth between sources traffic end and destinations traffic end towards connectionless transport layer, and on destinations traffic end and sources traffic end, in the follow-up mutual message of these different business examples, carry the Session ID of affiliated service conversation respectively, so that the message area of sharing these different business sessions transmitted in data channel towards connectionless transport layer is separated.Finally, sources traffic end sends service conversation ending request to destinations traffic end, and destinations traffic end deletes corresponding service conversation.

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

201, sources traffic end group in share towards connectionless transport layer data communication port set up with destinations traffic end between share data channel towards connectionless transport layer.

Can be shared udp port based on sharing data communication port towards connectionless transport layer, sharing data channel towards connectionless transport layer can be shared UDP message passage.

It should be noted that, connect relative to SCCP connection-oriented towards nothing, so-called connection-oriented communication, as shared transmission control protocol (Transmission Control Protocol, be called for short TCP), be exactly send between sources traffic end and destinations traffic end and receive before data, one must be set up from sources traffic end to the connection of destinations traffic end, the connection of the three-way handshake carried out between sources traffic end and destinations traffic end is needed as TCP connects, connecting between opisthogenesis communication ends and destinations traffic end just can transmitting and receiving data mutually, after transmission and reception data complete, disconnect the connection of sources traffic end and destinations traffic end again.Towards connectionless communication, as UDP, be exactly send between sources traffic end and destinations traffic end and receive before data, without the need to setting up from sources traffic end to the connection of destinations traffic end, do not need again to disconnect the connection between sources traffic end and destinations traffic end after not needing the connection establishment of the three-way handshake as TCP between sources traffic end and destinations traffic end, data transmission and reception.Described towards connectionless transport layer share data communication port as shared udp port be can for multi-user, multi-service message, multi-service session share towards without PORT COM corresponding to connecting communication, described towards connectionless transport layer share data channel as shared UDP message passage be exactly for multi-user, multi-service message, multi-service session share towards without data channel corresponding to connecting communication.

Specifically, relative to employing connection-oriented transport layer share data channel as shared tcp data passage, adopt towards connectionless transport layer share data channel as shared UDP message passage at least tool have the following advantages:

1) for the connection of wireless terminal and multiple cloud platform: wireless terminal needs to connect multiple cloud platform respectively with multiple shared tcp data passage, the corresponding shared tcp data passage of each cloud platform, the radio bearer/eated dishes without rice or wine multiple that wireless terminal connects, can not improve the utilance of radio bearer/eat dishes without rice or wine.And wireless terminal only need open the radio bearer of a shared UDP/eat dishes without rice or wine when connecting multiple cloud platform respectively with multiple shared UDP message passage.

2) for the connection of wireless terminal and a cloud platform: when wireless terminal is by a multiple service message of shared tcp data channel transfer, namely sharing tcp data passage is that multi-service message on wireless terminal is when sharing, due to the transmission that TCP is strict sequenced byte stream, multiple service message can only can not concurrent transmission by byte order transmission, so the efficiency comparison of transmission is low.And if be that multi-service message on wireless terminal is shared by a shared UDP message passage, then multiple service message can concurrent transmission.

3) because the transmitting-receiving of TCP is non-boundary, when sharing for multiple service message, can not distinguish the agreement of multiple service message, must pack the unified agreement of one deck outward again at each service message, process is just pretty troublesome like this.And the transmitting-receiving of UDP has border, so without the need to packing the unified agreement of one deck again, the agreement of different service messages also can be distinguished during transmitting-receiving.

4) when Peer-to-peer Server Cluster, such as transmit the data of magnanimity between two cloud platforms, if with a shared tcp data passage, this shared tcp data passage can only be the TCP connection of the station server in the cloud platform server cluster of source to another station server in target cloud platform server cluster, cannot play the effect of server cluster, and very narrow being not suitable for of data channel transmits 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, share UDP message channel in theory can infinitely widen, be therefore adapted at the data of the multi-user of shared UDP message channel magnanimity, multi-service message, multi-service session.

Usually, also comprised before 201:

Sources traffic end shares data communication port based on towards connectionless transport layer described in distributing.

Accordingly, 201 be specially:

Described sources traffic end group in described distribution share that data communication port and described destinations traffic end distribute towards connectionless transport layer share data communication port towards connectionless transport layer and set up and describedly share data channel towards connectionless transport layer.

Particularly, one or more ports that described sources traffic end can distribute based on a port of self distribution and described destinations traffic end are set up respectively and are shared data channel towards connectionless transport layer.Set up respectively when the multiple ports distributed with described destinations traffic end and share data channel towards connectionless transport layer, the port numbers different according to the plurality of port can distinguish and corresponding share data channel towards connectionless transport layer.

202, described sources traffic end is by the described service message sharing data channel and the mutual multiple service conversation of described destinations traffic end towards connectionless transport layer, and the service message of each service conversation carries the session identification of affiliated service conversation respectively.

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

Described sources traffic end generates the service message of described multiple service conversation, shares the service message of data channel to the described multiple service conversation of described destinations traffic end transmission by described towards connectionless transport layer;

Described sources traffic end shares towards connectionless transport layer the service message that data channel receives described multiple service conversation that described destinations traffic end sends by described, and belonging to carrying according to each service message, the session identification of service conversation processes each service message.

It should be noted that, in above-mentioned two-way data communication process, described sources traffic termination is received, process service message and generation, transmission service message sequencing can exchange, further, the order receiving, process or generate, send the service message of each service conversation also can be arbitrary.

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

Described sources traffic end shares towards connectionless transport layer data channel to initiate request from multiple establishment service conversation to described destinations traffic end by described, creates described multiple service conversation and distribute session identification respectively for described multiple service conversation to make described destinations traffic end according to the request of described multiple establishment service conversation;

Share towards connectionless transport layer the response that data channel receives multiple establishment service conversations that described destinations traffic end returns by described, each response comprises the session identification of affiliated service conversation respectively.

Further, when completing service message mutual of a service conversation, this service conversation can also be terminated.Particularly, can also comprise after 202:

Described sources traffic end shares towards connectionless transport layer data channel to initiate request from multiple winding-up session to described destinations traffic end by described, the session identification of affiliated service conversation is carried in each request respectively, deletes described multiple service conversation to make described destinations traffic end.

Fig. 3 is the system architecture schematic diagram of a kind of application scenarios of the embodiment of the present invention.As shown in Figure 3, terminal equipment, as sources traffic end, comprises a cloud client and multiple service customer end, and as service customer end 1 and service customer end 2, wherein, service customer end refers to the application program for realizing certain business, as QQ client etc.; Cloud platform, as destinations traffic end, comprises a scheduling node (Master Node) and multiple working node (Worker Node); Terminal equipment and cloud platform are by sharing UDP message expanding channels, and the shared UDP message passage in this application scenarios also can be called cloud service bus.

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

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

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

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

To carry by service customer end 1 in this request be the call identification Call ID (1) that service conversation 1 distributes, Call ID (1) in end side is unique distribution.For example, call identification dynamically can generate according to system time.

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

Meanwhile, the corresponding relation of cloud client records Call ID (1) and service customer end 1.Above-mentioned Call ID (1) is carried in the request of described establishment service conversation 1.

405, Master Node selects Worker Node.

Particularly, Master Node can select the scheduling strategy preset to select Worker Node.Usually, can select according to the factor such as ability, state, load, performance of each Worker Node.

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

407, Worker Node creates service conversation 1, distributes session identification Session ID (1).

Meanwhile, 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 high-speed cache of cloud platform.

408, the session identification Session ID (1) of service conversation 1 is returned to MasterNode by Worker Node.

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

409, the response creating service conversation 1 is returned to cloud client by Master Node.

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

410, session identification Session ID (1) and Call ID (1) is returned to service customer end 1 according to Call ID (1) and the corresponding relation of service customer end 1 by cloud client.

Service customer end 1, according to the corresponding relation of Call ID (1) and service conversation 1, determines the session identification that Session ID (1) is 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 WorkerNode of cloud platform, as: order, data, event etc., forward through cloud client and cloud platform Master Node in reciprocal process, the service message of these service conversations 1 is transmitted by the shared UDP message passage between cloud client and cloud platform.Further, Master Node is after the service message receiving service conversation 1, the context environmental of service conversation 1 can be searched according to the Session ID (1) carried in service message, the context environmental of service conversation 1 is supplied to the Worker Node of selection, Worker Node is based on the service message of the context environmental process service conversation 1 of service conversation 1; Or, Master Node is after the service message receiving 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) carried in service message, based on the service message of the context environmental process service conversation 1 of service conversation 1.It should be noted that, MasterNode selects the Worker Node being used for processing service conversation 1 service message, can be identical with the Worker Node selected in 405, also can be different, depends on scheduling strategy.

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

Carrying by service customer end 2 in this request is the Call ID (2) that service conversation 2 distributes, 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, cloud client initiates to Master Node the request creating service conversation 2.

Meanwhile, the corresponding relation of cloud client records Call ID (2) and service customer end 2.Above-mentioned Call ID (2) is carried in the request of described establishment service conversation 2.

413, Master Node selects Worker Node.

Particularly, Master Node can select the scheduling strategy preset to select Worker Node.Usually, can select according to the factor such as ability, state, load, performance of each Worker Node.The Worker Node selected in 413 can be identical with the Worker Node selected in 405, also can be different.

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

Above-mentioned Call ID (2) is carried in this request.

415, Worker Node creates service conversation 2, distributes session identification Session ID (2).

Meanwhile, 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, the session identification Session ID (2) of service conversation 2 is returned to MasterNode by Worker Node.

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

417, the response creating service conversation 2 is returned to cloud client by Master Node.

Create in the response of service conversation 2 and carry above-mentioned Call ID (2) and session identification Session ID (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 session identification Session ID (2) of service conversation 2 and Call ID (2) is returned to service customer end 2 according to Call ID (2) and the corresponding relation of service customer end 2 by cloud client.

Service customer end 2, according to the corresponding relation of Call ID (2) and service conversation 2, determines the session identification that Session ID (2) is 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 WorkerNode of cloud platform, as: order, data, event etc., forward through cloud client and cloud platform Master Node in reciprocal process, the service message of these service conversations 2 is transmitted by the shared UDP message passage between cloud client and cloud platform.Further, Master Node is after the service message receiving service conversation 2, the context environmental of service conversation 2 can be searched according to the Session ID (2) carried in service message, the context environmental of service conversation 2 is supplied to the Worker Node of selection, Worker Node is based on the service message of the context environmental process service conversation 2 of service conversation 2; Or, Master Node is after the service message receiving 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) carried in service message, based on the service message of the context environmental process service conversation 2 of service conversation 2.It should be noted that, MasterNode selects the Worker Node being used for processing service conversation 2 service message, can be identical with the Worker Node selected in 413, also can be different, tries to please scheduling strategy.

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

Session ID (1) is carried in this message.

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

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

422, Master Node forwards the request of winding-up session 1 to Worker Node.

423, Worker Node deletes service conversation 1.

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

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

Session ID (2) is carried in this message.

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

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

427, Master Node forwards and terminates with the request of service conversation 2 to Worker Node.

428, Worker Node deletes service conversation 2.

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

When a terminal equipment and multiple cloud platform communication, 402 medium cloud clients set up a shared UDP message passage respectively based on the shared udp port distributed and each cloud platform, further, for each cloud platform, cloud client also can set up a shared UDP message passage based on multiple ports of the shared udp port distributed and this cloud platform respectively.Like this, when by share udp port send request or service message time, the shared UDP message passage between the cloud platform corresponding with this address information can be selected to send according to the address information of the cloud platform carried in request or service message, with the cloud platform processes making this address information corresponding these request and service messages.The address information of this cloud platform can be set in advance in each service customer end, the address information of the cloud platform arranged in each service customer end can be different, particularly, the address information of cloud platform can comprise IP address and the port numbers of cloud Platform Server, or the URL(uniform resource locator) of cloud Platform Server (Universal Resource Locator is called for short URL) address.Further, 410 medium cloud clients also need to record Session ID (1), create the address information of cloud platform and the corresponding relation of service customer end 1 or service conversation 1 of carrying in the request of service conversation 1, even if like this when different cloud platform be different service conversations be assigned with identical session identification, service message cloud platform can also being sent service conversation 1 according to Session ID (1) and the address information of cloud platform sending service message passes to service customer end 1, and as the service message process of service conversation 1.Similar, 418 medium cloud clients also need to record Session ID (2), create the address information of cloud platform and the corresponding relation of service customer end 2 or service conversation 2 of carrying in the request of service conversation 2.

Fig. 5 is the signaling process figure of another application scenarios of the embodiment of the present invention.Compared with the application scenarios shown in Fig. 3, in the terminal equipment of this application scene, cloud client and service customer end merge setting; For example, Fig. 5 can be the multi-service session communication between internet of things sensors terminal and Internet of Things cloud platform.As shown in Figure 5, comprising:

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

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

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

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

504, Master Node selects Worker Node.

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

506, Worker Node creates service conversation 1, distributes session identification Session ID (1).

Meanwhile, 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, the session identification Session ID (1) of service conversation 1 is returned to MasterNode by Worker Node.

508, the response creating service conversation 1 is returned to cloud client by Master Node.

Cloud client, according to the corresponding relation of Call ID (1) and service conversation 1, determines the session identification that Session ID (1) is service conversation 1.Afterwards, 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, event etc., forward through cloud platform Master Node in reciprocal process, the service message of these service conversations 1 is transmitted by the shared UDP message passage between cloud client and cloud platform.Further, MasterNode is after the service message receiving service conversation 1, the context environmental of service conversation 1 can be searched according to the SessionID carried in service message (1), the context environmental of service conversation 1 is supplied to the Worker Node of selection, Worker Node is based on the service message of the context environmental process service conversation 1 of service conversation 1; Or, Master Node is after the service message receiving 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) carried in service message, based on the service message of the context environmental process service conversation 1 of service conversation 1.It should be noted that, Master Node selects the Worker Node being used for processing service conversation 1 service message, can be identical with the Worker Node selected in 504, also can be different, depends on scheduling strategy.

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

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

510, Master Node selects Worker Node.

Particularly, Master Node can select the scheduling strategy preset to select Worker Node.Usually, can select according to the factor such as ability, state, load, performance of each Worker Node.The Worker Node selected in 510 can be identical with the Worker Node selected in 504, also can be different.

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

Above-mentioned Call ID (2) is carried in this request.

512, Worker Node creates service conversation 2, distributes session identification Session ID (2).

513, the session identification Session ID (2) of service conversation 2 is returned to MasterNode by Worker Node.

514, the response creating service conversation 2 is returned to cloud client by Master Node.

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

Cloud client, according to the corresponding relation of Call ID (2) and service conversation 2, determines the session identification that Session ID (2) is service conversation 2.Afterwards, 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, event etc., forward through cloud platform Master Node in reciprocal process, the service message of these service conversations 2 is transmitted by the shared UDP message passage between cloud client and cloud platform.Further, MasterNode is after the service message receiving service conversation 2, the context environmental of service conversation 2 can be searched according to the SessionID carried in service message (2), the context environmental of service conversation 2 is supplied to the Worker Node of selection, Worker Node is based on the service message of the context environmental process service conversation 2 of service conversation 2; Or, Master Node is after the service message receiving 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) carried in service message, based on the service message of the context environmental process service conversation 2 of service conversation 2.It should be noted that, Master Node selects the Worker Node being used for processing service conversation 2 service message, can be identical with the Worker Node selected in 510, also can be different, depends on scheduling strategy.

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

Session ID (1) is carried in this message.

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

517, Master Node forwards the request of winding-up session 1 to Worker Node.

518, Worker Node deletes service conversation 1.

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

Session ID (2) is carried in this message.

520, Master Node distributes Worker Node.

521, Master Node forwards and terminates with the request of service conversation 2 to Worker Node.

522, Worker Node deletes service conversation 2.

When a terminal equipment and multiple cloud platform communication, 502 medium cloud clients set up a shared UDP message passage respectively based on the shared udp port distributed and each cloud platform.Like this, when by share udp port send request or service message time, the shared UDP message passage between the cloud platform corresponding with this address information can be selected to send according to the address information of the cloud platform carried in request or service message, with the cloud platform processes making this address information corresponding these request and service messages.The address information of cloud platform can be set in advance in cloud client and corresponding with business, 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 IP address and the port numbers of cloud Platform Server or the URL address of cloud Platform Server.Further, after 508, medium cloud client also needs to record Session ID (1), create the address information of cloud platform and the corresponding relation of service conversation 1 of carrying in the request of service conversation 1, even if like this when different cloud platform be different service conversations be assigned with identical session identification, according to Session ID (1), the address information of cloud platform that sends service message cloud platform can also be sent the service message process of service message as service conversation 1 of service conversation 1.Similar, after 514, cloud client also needs to record Session ID (2), create the address information of cloud platform and the corresponding relation of service conversation 2 of carrying in the request of service conversation 2.

Fig. 6 is the system architecture schematic diagram of another application scenarios of the embodiment of the present invention.As shown in Figure 6, terminal equipment is as sources traffic end, comprise a cloud client and multiple individual cloud desktop window Window, as 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 terminal equipment (i.e. processing logic) leaves cloud platform in, when starting individual cloud desktop Window for one, need connect corresponding cloud platform, display logic is returned terminal equipment after running the processing logic of this individual cloud desktop Window by cloud platform; Cloud platform, as destinations traffic end, comprises a Master Node and multiple Worker Node; Terminal equipment and cloud platform are by sharing UDP message expanding channels, and the shared UDP message passage in this application scenarios also can be called cloud Desktop Bus.Service customer end, with as similar in Fig. 4, just replaced to individual cloud desktop Window, repeats no more herein by the signaling process under application scenarios shown in Fig. 6.

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

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

801, distributes in cloud Platform Server 1 and cloud Platform Server 2 both sides and fixing share data communication port towards connectionless transport layer, cloud up based on described port foundation and share data channel towards connectionless transport layer between Platform Server 1 and cloud Platform Server 2.

802, cloud Platform Server 1 initiates two or more different service conversation request to create to cloud Platform Server 2.

803, cloud Platform Server 2 creates different service conversations respectively for these service conversation requests to create, distributes the Session ID of each service conversation respectively.

804, the Session ID of these different service conversations is returned to cloud Platform Server 1 by cloud Platform Server 2.

805, the srvice instance that these service conversation requests to create on cloud Platform Server 1 are corresponding and cloud Platform Server 2 are shared data channel towards connectionless transport layer by described to carry out subsequent message mutual, and the Session ID carrying respective service conversation in mutual message respectively corresponding shares data channel by towards connectionless transport layer.

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

807, cloud Platform Server 2 deletes these service conversations.

Fig. 9 is the signalling diagram under another application scenarios of the embodiment of the present invention.Compared with application scenarios shown in Fig. 7, destinations traffic end in this application scene is that general server is done, for example, this application scene can be that other member search's engines (destinations traffic end) accessed by the cloud platform (sources traffic end) with Meta Search Engine function.As shown in Figure 9, comprising:

901, distribute at cloud Platform Server and general server both sides and fixing share data communication port towards connectionless transport layer, set up to cloud up based on described port and share data channel towards connectionless transport layer between Platform Server and general server.

902, cloud Platform Server initiates two or more different service conversation request to create to general server.

903, general server creates different service conversations respectively for these service conversation requests to create, distributes the Session ID of each service conversation respectively.

904, the Session ID of these different service conversations is returned to cloud Platform Server by general server.

905, the srvice instance that these service conversation requests to create on cloud Platform Server are corresponding and general server share the mutual subsequent message of data channel by described towards connectionless transport layer, and carry Session ID corresponding to respective service conversation in message respectively.

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

907, general server deletes these service conversations.

It should be noted that, general server as sources traffic end, cloud Platform Server as the signalling interactive process under the scene of destinations traffic end and Fig. 5 similar.

The embodiment of the present invention shares data channel by setting up between sources traffic end and destinations traffic end towards connectionless transport layer, and in mutual service message, carry the session identification of affiliated service conversation, make sources traffic end and destinations traffic end can by the service message of a mutual multiple service conversation of data channel, the concurrent connection number solved in prior art when a large amount of voice and packet data concurrent service request between sources traffic end and destinations traffic end is many, large and the problem that data channel utilance is low of Bonding pressure, make shared data channel can be multi-service message, multi-service session is multiplexing, decrease the concurrent connection number between sources traffic end and destinations traffic end, improve the utilance of data channel.Further, share data channel owing to adopting towards connectionless transport layer, content can be pushed PUSH whenever and wherever possible to sources traffic end by destinations traffic end, realizes the permanent online of sources traffic end terminal.Between cloud platform by share towards connectionless transport layer data channel mutual time, unified entrance and exit can be provided between cloud platform, further increasing the safety and reliability of cloud platform.

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

Path Setup module 11, for based on share towards connectionless transport layer data communication port set up with Correspondent Node between share data channel towards connectionless transport layer;

Service interaction module 12, for by the described service message sharing data channel and the mutual multiple service conversation of described Correspondent Node towards connectionless transport layer, the service message of each service conversation carries the session identification of affiliated service conversation respectively.

Further, also comprise:

Port assignment module 13, shares data communication port towards connectionless transport layer described in distributing;

Path Setup module 11 specifically for, based on described distribution share that data communication port and described Correspondent Node distribute towards connectionless transport layer share data communication port towards connectionless transport layer and set up and describedly share data channel towards connectionless transport layer.

Further, service interaction module 12 specifically comprises:

First interactive unit, for generating the service message of described multiple service conversation, shares the service message of data channel to the described multiple service conversation of described Correspondent Node transmission by described towards connectionless transport layer;

Second interactive unit, for sharing towards connectionless transport layer the service message that data channel receives described multiple service conversation that described Correspondent Node sends by described, belonging to carrying according to each service message, the session identification of service conversation processes each service message.

Further, also comprise:

Conversation establishing module, for sharing towards connectionless transport layer data channel to initiate request from multiple establishment service conversation to described Correspondent Node by described, creating described multiple service conversation to make described Correspondent Node according to the request of described multiple establishment service conversation and distributing session identification respectively for described multiple service conversation; Shared data channel towards connectionless transport layer and received by described the response that described Correspondent Node returns multiple establishment service conversation, each response comprises the session identification of affiliated service conversation respectively.

Further, also comprise:

Conversation end module, for sharing towards connectionless transport layer data channel to initiate request from multiple winding-up session to described Correspondent Node by described, the session identification of affiliated service conversation is carried in each request respectively, deletes described multiple service conversation to make described Correspondent Node.

Further, described Correspondent Node is multiple;

Path Setup module 11 specifically for, based on described distribution share that data communication port and each Correspondent Node distribute towards connectionless transport layer share data communication port towards connectionless transport layer and set up respectively share data channel towards connectionless transport layer between each Correspondent Node;

Described first interactive unit specifically for, according to the address information of the Correspondent Node carried in each service message, by sharing data channel towards connectionless transport layer and send each service message respectively between the Correspondent Node corresponding with described address information.

Further, when described Correspondent Node is cloud Platform Server, described communication ends is terminal equipment, cloud Platform Server or non-cloud Platform Server; When described Correspondent Node is non-cloud Platform Server, described communication ends is cloud Platform Server.

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

A kind of data communications method that the specific implementation of the present embodiment provides with reference to the embodiment of the present invention, further with reference to Fig. 5, Fig. 7, Fig. 8, Fig. 9.The embodiment of the present invention shares data channel by setting up between communication ends and Correspondent Node towards connectionless transport layer, and in mutual service message, carry the session identification of affiliated service conversation, making can by the service message of a mutual multiple service conversation of data channel between sources traffic end and destinations traffic end, the concurrent connection number solved in prior art when a large amount of voice and packet data concurrent service request between sources traffic end and destinations traffic end is many, large and the problem that data channel utilance is low of Bonding pressure, make shared data channel can be multi-service message, multi-service session is multiplexing, decrease the concurrent connection number between sources traffic end and destinations traffic end, improve the utilance of data channel.Further, share data channel owing to adopting towards connectionless transport layer, content can be pushed PUSH whenever and wherever possible to sources traffic end by destinations traffic end, realizes the permanent online of sources traffic end terminal.Between cloud platform by share towards connectionless transport layer data channel mutual time, unified entrance and exit can be provided between cloud platform, further increasing the safety and reliability of cloud platform.

The structural representation of another communication ends that Figure 11 A provides for the embodiment of the present invention, the structural representation of another communication ends that Figure 11 B provides for the embodiment of the present invention.As shown in Figure 11 A and 11B, this communication ends comprises:

Cloud client 21 and the multiple service customer ends 22 be connected with cloud client 21 or multiple individual cloud desktop window 23;

Multiple service customer end 22 or multiple individual cloud desktop window 23 for, generate the service message of described multiple service conversation and send to cloud client 21, the service message of each service conversation carries the session identification of affiliated service conversation respectively;

Cloud client 21 comprises:

Path Setup module 211, for based on share towards connectionless transport layer data communication port set up with Correspondent Node between share data channel towards connectionless transport layer;

Service interaction module 212, for being shared data channel towards connectionless transport layer sent to described Correspondent Node by described described in the service message of multiple service conversations that described multiple service customer end or multiple individual cloud desktop sent; Share towards connectionless transport layer the service message that data channel receives described multiple service conversation that described Correspondent Node sends by described, the service message of each service conversation carries the session identification of affiliated service conversation respectively, and the service message of the described multiple service conversation sent by described Correspondent Node sends to described multiple service customer end or multiple individual cloud desktop window;

Multiple service customer end 22 or multiple individual cloud desktop window 23 also for, the service message of described multiple service conversation that described Correspondent Node sends is processed.

Further, described multiple service conversation comprises the first service conversation, and described multiple service customer end comprises with described Correspondent Node that the first service customer end of the service message of described first service conversation or described multiple individual cloud desktop window comprise the first cloud desktop window with the described Correspondent Node service message of described first service conversation alternately alternately;

Described first service customer end or first man cloud desktop window also for, before the service message generating described first service conversation, generate the request of establishment first service conversation, for described first service conversation distributes the first call identification, described first call identification is added in the request of described establishment first service conversation, and the request of described establishment first service conversation is sent to described cloud client;

Cloud client 21 also comprises:

Conversation establishing module, for receiving the request of described establishment first service conversation, set up the corresponding relation of described first service customer end or first man cloud desktop window and the first call identification, the request of described establishment first service conversation is shared data channel towards connectionless transport layer sent to described Correspondent Node by described, share towards connectionless transport layer the response that data channel receives establishment first service conversation that described Correspondent Node sends by described, the response of described establishment first service conversation comprises the first session identification and described first call identification, according to the corresponding relation of described first service customer end or first man cloud desktop window and the first call identification, described first session identification and the first call identification are sent to described first service customer end or first man cloud desktop window, and set up the corresponding relation of described first session identification and described first service customer end or first man cloud desktop window,

Described first service customer end or first man cloud desktop window also for, according to the corresponding relation of described first call identification and the first service conversation, determine that described first session identification is the session identification of described first service conversation;

Service interaction module 212 specifically for, share towards connectionless transport layer the service message that data channel receives described first service conversation that described Correspondent Node sends by described, described first session identification set up according to described conversation establishing module and the corresponding relation of described first service customer end or first man cloud desktop window, described first service conversation that described Correspondent Node is sent service message send to described first service customer end or first man cloud desktop window.

A kind of data communications method that the specific implementation of the present embodiment provides with reference to the embodiment of the present invention, further with reference to Fig. 4, Fig. 6.The embodiment of the present invention shares data channel by setting up between communication ends and Correspondent Node towards connectionless transport layer, and in mutual service message, carry the session identification of affiliated service conversation, making can by the service message of a mutual multiple service conversation of data channel between sources traffic end and destinations traffic end, the concurrent connection number solved in prior art when a large amount of voice and packet data concurrent service request between sources traffic end and destinations traffic end is many, large and the problem that data channel utilance is low of Bonding pressure, make shared data channel can be multi-service message, multi-service session is multiplexing, decrease the concurrent connection number between sources traffic end and destinations traffic end, improve the utilance of data channel.Further, share data channel owing to adopting towards connectionless transport layer, content can be pushed PUSH whenever and wherever possible to sources traffic end by destinations traffic end, realizes the permanent online of sources traffic end terminal.

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

Working node 32 for, generate the service message of multiple service conversation and send to scheduling node 31, the service message of each service conversation carries the session identification of affiliated service conversation respectively;

Scheduling node 31 comprises:

Path Setup module 311, for based on share towards connectionless transport layer data communication port set up with Correspondent Node between share data channel towards connectionless transport layer;

First interactive module 312, is shared data channel towards connectionless transport layer for the service message of described multiple service conversation that sent by working node 32 sent to described Correspondent Node by described;

Second interactive module 313, for sharing towards connectionless transport layer the service message that data channel receives described multiple service conversation that described Correspondent Node sends by described, the service message of each service conversation carries the session identification of affiliated service conversation respectively, and the service message of the described multiple service conversation sent by described Correspondent Node sends to working node 32;

Working node 32 also for, the service message of described multiple service conversation that described Correspondent Node sends is processed.

Further, described multiple service conversation comprises the first service conversation;

Second interactive module 312 specifically for, share towards connectionless transport layer the service message that data channel receives described first service conversation that described Correspondent Node sends by described, search the context environmental of the first service conversation corresponding to described first session identification according to the first session identification in the service message of described first service conversation, and the context environmental of the service message of described first service conversation and described first service conversation is sent to working node 32; Working node 32 specifically for, the service message of context environmental to described first service conversation based on described first service conversation processes; Or

Second interactive module 312 specifically for, share data channel towards connectionless transport layer and receive by described the service message of described first service conversation that described Correspondent Node sends, the service message of described first service conversation is sent to from working node 32; Working node 32 specifically for, search the context environmental of the first service conversation corresponding to described first session identification according to the first session identification in the service message of described first service conversation, the service message of context environmental to described first service conversation based on described first service conversation processes.

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

A kind of data communications method that the specific implementation of the present embodiment provides with reference to the embodiment of the present invention, further with reference to Fig. 3 ~ 9.The embodiment of the present invention shares data channel by setting up between communication ends and Correspondent Node towards connectionless transport layer, and in mutual service message, carry the session identification of affiliated service conversation, making can by the service message of a mutual multiple service conversation of data channel between sources traffic end and destinations traffic end, the concurrent connection number solved in prior art when a large amount of voice and packet data concurrent service request between sources traffic end and destinations traffic end is many, large and the problem that data channel utilance is low of Bonding pressure, make shared data channel can be multi-service message, multi-service session is multiplexing, decrease the concurrent connection number between sources traffic end and destinations traffic end, improve the utilance of data channel.Further, between cloud platform by share towards connectionless transport layer data channel mutual time, unified entrance and exit can be provided between cloud platform, further increasing the safety and reliability of cloud platform.

The structural representation of a kind of terminal equipment that Figure 13 provides for the embodiment of the present invention.As shown in figure 13, terminal equipment generally comprises at least one processor 41, such as CPU, at least one shared udp port 42, memory 43, and at least one communication bus 44, for realizing the connection communication between these devices.The executable module of processor 41 for storing in execute store 43, such as computer program; Terminal equipment optionally comprises user interface 45, includes but not limited to display, keyboard and pointing device, such as mouse, trace ball (trackball), touch-sensitive plate or touch sensitive display screen.Memory 43 may comprise high-speed RAM memory, still may comprise non-labile memory (non-volatile memory), such as at least one magnetic disc store.Realize the communication connection between this terminal equipment and at least one cloud Platform Server by least one shared udp port 42, can the Internet be used, wide area network, local network, metropolitan area network etc.

In some embodiments, memory 43 stores following element, executable module or data structure, or their subset, or their superset:

Operating system 431, comprises various system program, for realizing various basic business and processing hardware based task;

Application module 432, comprises various application program, for realizing various applied business.

One of following module or its combination is included but not limited to: multiple service customer end or individual cloud desktop window 4321, cloud client 4322 in application module 432.

One of following module or its combination is included but not limited to: Path Setup module, service interaction module, conversation establishing module in this cloud client 4322.

In above-mentioned multiple service customer end or individual cloud desktop window 4321, cloud client 4322 and cloud client 4322, the specific implementation of each module is see the corresponding module in Figure 11 A and 11B illustrated embodiment.

The structural representation of scheduling node in a kind of cloud Platform Server that Figure 14 provides for the embodiment of the present invention.Cloud Platform Server generally comprises a scheduling node and multiple working node.As shown in figure 14, scheduling node generally comprises at least one processor 51, such as CPU, and at least one shared udp port 52 and other communication port 56, memory 53, and at least one communication bus 54, for realizing the connection communication between these devices.The executable module of processor 51 for storing in execute store 53, such as computer program; Scheduling node optionally comprises user interface 55, includes but not limited to display, keyboard and pointing device, such as mouse, trace ball (trackball), touch-sensitive plate or touch sensitive display screen.Memory 53 may comprise high-speed RAM memory, still may comprise non-labile memory (non-volatile memory), such as at least one magnetic disc store.Scheduling node realizes cloud Platform Server by least one shared udp port 52 and as the communication connection between the terminal equipment of Correspondent Node, non-cloud Platform Server or another cloud Platform Server, the Internet can be used, wide area network, local network, metropolitan area network etc.Scheduling node is realized by other communication port 56 and communication connection in same cloud Platform Server between each working node, can use the Internet, wide area network, local network, metropolitan area network etc.

In some embodiments, memory 53 stores following element, executable module or data structure, or their subset, or their superset:

Operating system 531, comprises various system program, for realizing various basic business and processing hardware based task;

Application module 532, comprises various application program, for realizing various applied business.

One of following module or its combination is included but not limited to: Path Setup module, the first interactive module, the second interactive module in application module 532.

Corresponding module in the specific implementation embodiment shown in Figure 12 of above-mentioned Path Setup module, the first interactive module, the second interactive module.

The structural representation of working node in a kind of cloud Platform Server that Figure 15 provides for the embodiment of the present invention.As shown in figure 15, working node generally comprises at least one processor 61, such as CPU, communication port 62, memory 63, and at least one communication bus 64, for realizing the connection communication between these devices.The executable module of processor 61 for storing in execute store 63, such as computer program; Working node optionally comprises user interface 65, includes but not limited to display, keyboard and pointing device, such as mouse, trace ball (trackball), touch-sensitive plate or touch sensitive display screen.Memory 63 may comprise high-speed RAM memory, still may comprise non-labile memory (non-volatilememory), such as at least one magnetic disc store.Working node is realized by communication port 62 and communication connection in same cloud Platform Server between scheduling node, can use the Internet, wide area network, local network, metropolitan area network etc.

In some embodiments, memory 63 stores following element, executable module or data structure, or their subset, or their superset:

Operating system 631, comprises various system program, for realizing various basic business and processing hardware based task;

Application module 632, comprises various application program, for realizing various applied business.Application module 632 includes but not limited to realize following functions: generate the service message of multiple service conversation and send to scheduling node, and the service message of each service conversation carries the session identification of affiliated service conversation respectively; The service message of described multiple service conversation of the described Correspondent Node transmission that scheduling node forwards is processed.Working node in concrete embodiment shown in Figure 12.

Communication ends embodiment described above is only schematic, wherein said module, the unit illustrated as separating component or can may not be and physically separates, parts as module, unit display can be or may not be physical location, namely can be positioned at a place, or also can be distributed in multiple network element.Some or all of module wherein, unit can be selected according to the actual needs to realize the object of the present embodiment scheme.Those of ordinary skill in the art, when not paying performing creative labour, are namely appreciated that and implement.

Through the above description of the embodiments, those skilled in the art can be well understood to the mode that each execution mode can add required general hardware platform by software and realize, and can certainly pass through hardware.Based on such understanding, technique scheme can embody with the form of software product the part that prior art contributes in essence in other words, this computer software product can store in a computer-readable storage medium, as ROM/RAM, magnetic disc, CD etc., comprising some instructions in order to make a computer equipment (can be personal computer, server, or the network equipment etc.) perform the method described in some part of each embodiment or embodiment.

Last it is noted that above each embodiment is only in order to illustrate technical scheme of the present invention, be not intended to limit; Although with reference to foregoing embodiments to invention has been detailed description, those of ordinary skill in the art is to be understood that: it still can be modified to the technical scheme described in foregoing embodiments, or carries out equivalent replacement to wherein some or all of technical characteristic; And these amendments or replacement, do not make the essence of appropriate technical solution depart from the scope of various embodiments of the present invention technical scheme.

Claims

1. a data communications method, is characterized in that, comprising:

Described sources traffic end is by sharing the service message of data channel and the mutual multiple service conversation of described destinations traffic end towards connectionless transport layer described in one, 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, described sources traffic end group in share towards connectionless transport layer data communication port set up with destinations traffic end between share data channel towards connectionless transport layer before also comprise:

Described sources traffic end shares data communication port towards connectionless transport layer described in distributing;

Described sources traffic end group sets up sharing data channel towards connectionless transport layer and comprise between described destinations traffic end in sharing data communication port towards connectionless transport layer:

3. method according to claim 2, is characterized in that, described sources traffic end is comprised by the described service message sharing data channel and the mutual multiple service conversation of described destinations traffic end towards connectionless transport layer:

4. method according to claim 3, is characterized in that, described sources traffic end by described share the service message of data channel and the mutual multiple service conversation of described destinations traffic end towards connectionless transport layer before also comprise:

5. method according to claim 4, is characterized in that, described sources traffic end comprises cloud client, and described destinations traffic end comprises cloud Platform Server, the working node that described cloud Platform Server comprises scheduling node and is connected with described scheduling node;

Share data communication port towards connectionless transport layer described in described sources traffic end distributes to comprise:

Described cloud client shares data communication port towards connectionless transport layer described in distributing;

Described sources traffic end group in described distribution share that data communication port and described destinations traffic end distribute towards connectionless transport layer share data communication port towards connectionless transport layer and set up and describedly share data channel towards connectionless transport layer and comprise:

Described cloud client based on described distribution share that data communication port and described scheduling node distribute towards connectionless transport layer share data communication port towards connectionless transport layer and set up and describedly share data channel towards connectionless transport layer;

Describedly share towards connectionless transport layer the service message that data channel sends described multiple service conversation to described destinations traffic end comprise by described:

Described cloud client shares towards connectionless transport layer data channel to send service message from described multiple service conversation to described scheduling node by described, with make described scheduling node respectively described multiple service message is sent to described working node, described working node to carry according to each service message belonging to the session identification of service conversation each service message is processed;

Described sources traffic end is shared data channel towards connectionless transport layer and is received the service message of described multiple service conversation that described destinations traffic end sends by described and comprise:

Described cloud client shares towards connectionless transport layer the service message that data channel receives described multiple service conversation that described scheduling node sends by described.

6. method according to claim 5, is characterized in that, the service message that described sources traffic end generates described multiple service conversation comprises:

Described cloud client generates the service message of described multiple service conversation;

Described carry according to each service message belonging to the session identification of service conversation process carried out to each service message comprise:

Described cloud client carry according to each service message belonging to the session identification of service conversation each service message is processed.

7. method according to claim 5, is characterized in that, described sources traffic end also comprises and multiple service customer end of described cloud client's side link or multiple individual cloud desktop window;

The service message that described sources traffic end generates described multiple service conversation comprises:

Described multiple service customer end or multiple individual cloud desktop window generate the service message of described multiple service conversation, and the service message of described multiple service conversation is sent to described cloud client;

The service message of described multiple service conversation is sent to described multiple service customer end or multiple individual cloud desktop window by described cloud client, and belonging to described multiple service customer end or multiple individual cloud desktop window carry according to each service message, the session identification of service conversation processes each service message.

8. method according to claim 7, is characterized in that, described multiple service conversation comprises the first service conversation;

Described sources traffic end is shared towards connectionless transport layer the request that data channel initiates multiple establishment service conversation to described destinations traffic end comprised by described:

First man cloud desktop window in the first service customer end in described multiple service customer end or described multiple individual cloud desktop window generates the request of establishment first service conversation, for described first service conversation distributes the first call identification, described first call identification is added in the request of described establishment first service conversation, and the request of described establishment first service conversation is sent to described cloud client;

Described cloud client sets up the corresponding relation of described first service customer end or first man cloud desktop window and the first call identification, and by the request of described establishment first service conversation by sharing data channel towards connectionless transport layer to described scheduling node;

Describedly share data channel towards connectionless transport layer and receive the response that described destinations traffic end returns multiple establishment service conversation by described and comprise:

Described cloud client shares towards connectionless transport layer the response that data channel receives establishment first service conversation that described scheduling node returns by described, and the response of described establishment first service conversation comprises the first session identification and described first call identification;

According to the corresponding relation of described first service customer end or first man cloud desktop window and the first call identification, described first session identification and the first call identification are sent to described first service customer end or first man cloud desktop window, and determine the corresponding relation of described first session identification and described first service customer end or first man cloud desktop window;

Described first service customer end or first man cloud desktop window, according to the corresponding relation of described first call identification and the first service conversation, determine that described first session identification is the session identification of described first service conversation;

The service message of described multiple service conversation sends to described multiple service customer end or multiple individual cloud desktop window to comprise by described cloud client:

Described first session identification that described cloud client comprises according to the service message of described first service conversation, and the corresponding relation of described first session identification and described first service customer end or first man cloud desktop window, the service message of described first service conversation is sent to described first service customer end or first man cloud desktop window.

9. method according to claim 4, is characterized in that, described sources traffic end comprises cloud Platform Server, and destinations traffic end comprises another cloud Platform Server, the working node that each cloud Platform Server includes scheduling node and is connected with described scheduling node;

Data communication port is shared towards connectionless transport layer described in the scheduling node distribution of described sources traffic end;

The scheduling node of described sources traffic end based on described distribution share that the scheduling node of data communication port and described destinations traffic end distributes towards connectionless transport layer share data communication port towards connectionless transport layer and set up and describedly share data channel towards connectionless transport layer;

Described sources traffic end is shared towards connectionless transport layer the service message that data channel sends described multiple service conversation to described destinations traffic end comprised by described:

The working node of described sources traffic end sends the service message of described multiple service conversation respectively to the scheduling node of described sources traffic end, the scheduling node of described sources traffic end shares the service message of data channel to the described multiple service conversation of scheduling node transmission of described destinations traffic end by described towards connectionless transport layer, with the working node making the scheduling node of described destinations traffic end respectively described multiple service message be sent to described destinations traffic end, belonging to the working node of described destinations traffic end carries according to each service message, the session identification of service conversation processes each service message,

The scheduling node of described sources traffic end shares towards connectionless transport layer the service message that data channel receives described multiple service conversation of the scheduling node transmission of described destinations traffic end by described;

The service message of described multiple service conversation is sent to the working node of described sources traffic end by the scheduling node of described sources traffic end respectively, and belonging to the working node of described sources traffic end carries according to each service message, the session identification of service conversation processes each service message respectively.

10. method according to claim 9, it is characterized in that, the service message of described multiple service conversation comprises the service message of the first service conversation, service message in described multiple service conversation is sent to the working node of described sources traffic end by the scheduling node of described sources traffic end respectively, and the session identification of service conversation belonging to the working node of described sources traffic end carries according to each service message carries out process to each service message respectively and comprises:

The scheduling node of described sources traffic end searches the context environmental of the first service conversation corresponding to described first session identification according to the first session identification in the service message of described first service conversation, and the context environmental of the service message of described first service conversation and described first service conversation being sent to the working node of described sources traffic end, the working node of described sources traffic end processes based on the service message of context environmental to described first service conversation of described first service conversation; Or

The service message of described first service conversation is sent to the working node from described sources traffic end by the scheduling node of described sources traffic end, the working node of described sources traffic end searches the context environmental of the first service conversation corresponding to described first session identification according to the first session identification in the service message of described first service conversation, the service message of context environmental to described first service conversation based on described first service conversation processes.

11. methods according to claim 4, is characterized in that, described sources traffic end comprises cloud Platform Server, and described destinations traffic end comprises non-cloud Platform Server; Or described sources traffic end comprises non-cloud Platform Server, described destinations traffic end comprises cloud Platform Server.

12. methods according to any one of claim 4-11, it is characterized in that, described sources traffic end is also comprised after connectionless transport layer shares the service message of data channel and the mutual multiple service conversation of described destinations traffic end by described:

13. methods according to any one of claim 4-11, it is characterized in that, described destinations traffic end is multiple;

Described sources traffic end group is set up respectively share data channel towards connectionless transport layer in the data communication port of sharing towards connectionless transport layer sharing towards connectionless transport layer that data communication port and each destinations traffic end distribute of described distribution between each destinations traffic end;

Described sources traffic end according to the address information of the destinations traffic end carried in each service message, by sharing data channel towards connectionless transport layer and send each service message respectively between the destinations traffic end corresponding with described address information.

14. methods according to claim 12, is characterized in that, described destinations traffic end is multiple;

15. 1 kinds of communication ends, is characterized in that, comprising:

Service interaction module, for the service message by sharing data channel and the mutual multiple service conversation of described Correspondent Node described in towards connectionless transport layer, the service message of each service conversation carries the session identification of affiliated service conversation respectively.

16. communication ends according to claim 15, is characterized in that, also comprise:

Port assignment module, shares data communication port towards connectionless transport layer described in distributing;

Described Path Setup module specifically for, based on described distribution share that data communication port and described Correspondent Node distribute towards connectionless transport layer share data communication port towards connectionless transport layer and set up and describedly share data channel towards connectionless transport layer.

17. communication ends according to claim 16, is characterized in that, described service interaction module specifically comprises:

18. communication ends according to claim 17, is characterized in that, also comprise:

19. communication ends according to claim 18, is characterized in that, also comprise:

20. communication ends according to claim 17, is characterized in that, described Correspondent Node is multiple;

Described Path Setup module specifically for, based on described distribution share that data communication port and each Correspondent Node distribute towards connectionless transport layer share data communication port towards connectionless transport layer and set up respectively share data channel towards connectionless transport layer between each Correspondent Node;

21. communication ends according to any one of claim 15-20, it is characterized in that, when described Correspondent Node is cloud Platform Server, described communication ends is terminal equipment, cloud Platform Server or non-cloud Platform Server; When described Correspondent Node is non-cloud Platform Server, described communication ends is cloud Platform Server.

22. 1 kinds of communication ends, is characterized in that, comprising: cloud client and with multiple service customer end of described cloud client's side link or multiple individual cloud desktop window;

Described multiple service customer end or multiple individual cloud desktop window are used for, and generate the service message of described multiple service conversation and send to described cloud client, the service message of each service conversation carries the session identification of affiliated service conversation respectively;

Described cloud client comprises:

Service interaction module, the service message for the multiple service conversations described multiple service customer end or multiple individual cloud desktop sent sends to described Correspondent Node by sharing data channel towards connectionless transport layer described in one; Share towards connectionless transport layer the service message that data channel receives described multiple service conversation that described Correspondent Node sends by described, the service message of each service conversation carries the session identification of affiliated service conversation respectively, and the service message of the described multiple service conversation sent by described Correspondent Node sends to described multiple service customer end or multiple individual cloud desktop window;

23. communication ends according to claim 22, it is characterized in that, described multiple service conversation comprises the first service conversation, and described multiple service customer end comprises with described Correspondent Node that the first service customer end of the service message of described first service conversation or described multiple individual cloud desktop window comprise the first cloud desktop window with the described Correspondent Node service message of described first service conversation alternately alternately;

Described cloud client also comprises:

Described service interaction module specifically for, share towards connectionless transport layer the service message that data channel receives described first service conversation that described Correspondent Node sends by described, described first session identification set up according to described conversation establishing module and the corresponding relation of described first service customer end or first man cloud desktop window, described first service conversation that described Correspondent Node is sent service message send to described first service customer end or first man cloud desktop window.

24. 1 kinds of communication ends, is characterized in that, comprising: scheduling node and the working node be connected with described scheduling node;

Described working node is used for, and generates the service message of multiple service conversation and sends to described scheduling node, and the service message of each service conversation carries the session identification of affiliated service conversation respectively;

Described scheduling node comprises:

First interactive module, the service message for the described multiple service conversation sent by described working node sends to described Correspondent Node by sharing data channel towards connectionless transport layer described in one;

Second interactive module, for sharing towards connectionless transport layer the service message that data channel receives described multiple service conversation that described Correspondent Node sends by described, the service message of each service conversation carries the session identification of affiliated service conversation respectively, and the service message of the described multiple service conversation sent by described Correspondent Node sends to described working node;

25. communication ends according to claim 24, is characterized in that, described multiple service conversation comprises the first service conversation;

Described second interactive module specifically for, share towards connectionless transport layer the service message that data channel receives described first service conversation that described Correspondent Node sends by described, search the context environmental of the first service conversation corresponding to described first session identification according to the first session identification in the service message of described first service conversation, and the context environmental of the service message of described first service conversation and described first service conversation is sent to described working node; Described working node specifically for, the service message of context environmental to described first service conversation based on described first service conversation processes; Or

Described second interactive module specifically for, share towards connectionless transport layer the service message that data channel receives described first service conversation that described Correspondent Node sends by described, the service message of described first service conversation is sent to from described working node; Described working node specifically for, search the context environmental of the first service conversation corresponding to described first session identification according to the first session identification in the service message of described first service conversation, the service message of context environmental to described first service conversation based on described first service conversation processes.