WO2015117500A1

WO2015117500A1 - M2m communication method and system, and management node in m2m network

Info

Publication number: WO2015117500A1
Application number: PCT/CN2014/093741
Authority: WO
Inventors: 谢芳; 卢忱; 吴昊
Original assignee: 中兴通讯股份有限公司
Priority date: 2014-07-24
Filing date: 2014-12-12
Publication date: 2015-08-13
Also published as: CN105282789A

Abstract

Provided are an M2M communication method and system, and a management node in an M2M network. The M2M communication method of the present invention specifically comprises: receiving, by a management node, a session establishment request sent by a first execution node as a session initiator, the session establishment request comprising identification information about a second execution node as a session receiver; and establishing a session between the first execution node and the second execution node according to the session establishment request, so that the first execution node and the second execution node can exchange data through the session. By means of the communication method, data can be exchanged using a special session when two nodes in an M2M network exchange data, thereby avoiding the problems that when the existing two nodes exchange data, the amount of data stored in a management node is large, the load is large and the data exchange is not in time due to the fact that data is sent to the management node and data is acquired from the management node when the data is required, thereby reducing the load of the management node, and improving the data transmission efficiency in the M2M.

Description

M2M communication method and system and management node in M2M network

Technical field

The present invention relates to the field of communications, and in particular, to an M2M communication method and system, and a management node in an M2M network.

Background technique

The communication network of M2M (Machine-To-Machine) communication is composed of various M2M nodes and bearer networks. The M2M nodes communicate with each other through a bearer network. An M2M node includes at least one application entity or one public service entity. M2M nodes can be divided into two categories according to their functions: nodes that contain CSE and nodes that do not contain CSE. The nodes that do not include the CSE are: application-specific nodes: there must be at least one application entity, and no public service entity (Common Service Entity, CSE for short); the node that contains the CSE is: application service node: the function must have at least An application entity and a public business entity (CSE). Physically corresponds to the terminal device. Intermediate node: functionally there must be at least one public service entity (CSE), which may have at least one application entity; physically corresponding to the gateway device, responsible for managing the terminal device connected to the gateway, and managing the connection between the terminal and the service providing server. Infrastructure node: There must be at least one public service entity (CSE) in function, and there may be at least one application entity, which is physically used as a service provider server on the network side to provide management and service support for the terminal device and the gateway device.

The configuration of a basic M2M service provider is usually: an infrastructure node, multiple intermediate nodes, and multiple service application nodes.

As shown in Figure 1, the communication between the M2M application entities is implemented through the interaction between the public service entities CSE. The M2M application entities are connected to the CSE through the Mca interface, and the CSEs communicate through the Mcc interface. The premise of the communication is The M2M application entity first needs to register with the local CSE, and then can realize the interaction of the M2M application entity through communication between the CSEs. However, the existing data interaction between the nodes is stored in the CSE, and when the data is needed, it is acquired in the CSE, which results in untimely data interaction and causes the CSE to store a large amount of data, resulting in excessive load.

Summary of the invention

The embodiments of the present invention address at least the following technical problems, how to reduce the load of the CSE in the M2M and how to make the data between the nodes interact in time.

To solve the above problem, an embodiment of the present invention provides an M2M communication method, where the method includes: before data interaction between the first execution node and the second execution node:

The management node receives a session establishment request sent by the first execution node as a session initiator, where the session establishment request includes identification information of the second execution node as a session receiver;

Establishing, by the management node, a session between the first execution node and the second execution node according to the session establishment request, where the session is used for data interaction between the first execution node and the second execution node .

In an embodiment of the present invention, the establishing, by the management node, the session between the first execution node and the second execution node according to the session establishment request includes:

The management node allocates a session resource and an allocation session identifier according to the session establishment request;

The management node sends a session join request to the second execution node, where the session join request includes the session identifier and the identifier information of the first execution node;

Receiving, by the management node, a session join response message that is sent by the second execution node according to the session join request;

The management node completes session establishment according to the session join response message.

In an embodiment of the present invention, the management node includes a first management sub-node and a second management sub-node, and the establishing a session between the first execution node and the second execution node includes:

The first management sub-node allocates a session resource and a session identifier according to the session establishment request; and sends a session invitation request message to the second management sub-node; the session invitation request includes the session identifier, the first Performing identification information of the node and identification information of the second execution node;

The second management sub-node sends a session join request to the second execution node according to the session invitation request, where the session join request includes a session identifier and an identifier of the first execution node; and the second execution node is received. According to the session join request response, the session join response message is

Sending a session invitation response message to the first management child node according to the session join response message;

The first management sub-node completes session establishment according to the session invitation response message.

In an embodiment of the present invention, the first management sub-node completes session establishment according to the session invitation response message:

The second management sub-node determines whether the session join response message fed back by the second execution node includes accepting the join session response message, and if yes, sending a session invite response message including a success indication to the first management sub-node; The first management subsection accepts that the second execution node joins the session to complete session establishment; otherwise, the second management subnode sends a session invitation response message including a failure indication to the first management subnode.

In an embodiment of the present invention, the session invitation response message further includes at least one of the session identifier, the identifier of the first execution node, and the identifier of the second execution node.

In an embodiment of the present invention, before sending the session join request to the second execution node, the management node includes the steps of: determining whether the number of execution nodes joining the session is equal to the maximum number of nodes supported by the session If, for example, the session join request is not sent to the second execution node.

To solve the above problem, an embodiment of the present invention further provides an M2M communication method, where the method includes: before data interaction between the first execution node and the second execution node:

The first execution node as a session initiator sends a session establishment request to the management node; the session establishment request includes identification information of the second execution node as a session receiver;

The management node receives the session establishment request;

Establishing, by the management node, a session between the first execution node and the second execution node according to the session establishment request;

The first execution node and the second execution node join the session;

The first execution node and the second execution node perform data interaction through the session.

To solve the above problem, an embodiment of the present invention further provides a management node in an M2M communication network, where the management node includes a receiving module and an establishing module:

The receiving module is configured to receive, before the first execution node and the second execution node perform data interaction, a session establishment request sent by the first execution node as a session initiator, where the session establishment request is included as a session receiver Identification information of the second execution node;

The establishing module is configured to establish a session between the first execution node and the second execution node according to the session establishment request; the session is used by the first execution node and the second execution node Data interaction.

In an embodiment of the present invention, the establishing module includes a preparation submodule, a sending submodule, a receiving submodule, and a establishing submodule:

The preparation submodule is configured to allocate a session resource and allocate a session identifier according to the session establishment request;

The sending sub-module is configured to send a session join request to the second execution node, where the session join request includes the session identifier and the identifier information of the first execution node;

The receiving submodule is configured to receive a session join response message that is sent by the second execution node according to the session join request;

The establishing submodule is configured to complete session establishment according to the session join response message.

In an embodiment of the present invention, the management node includes a first management sub-node and a second management sub-node, and the first management sub-node includes a preparation sub-module, a first transmission sub-module, and a first receiving sub-module. And establishing a submodule, where the second management submodule includes a second registration submodule, a second receiving submodule, and a second sending submodule:

The first sending sub-module is configured to send a session invitation request message to the second management sub-node; the session invitation request includes the session identifier, the identifier information of the first execution node, and the second execution node Identification information;

The second sending sub-module is configured to send a session joining request to the second executing node according to the session invitation request, where the session joining request includes a session identifier and an identifier of the first executing node;

The second receiving submodule is configured to receive a session join response message that is sent by the second executing node according to the session joining request;

The second sending submodule is further configured to send a session invitation response message to the first management child node according to the session join response message;

The establishing submodule is configured to complete session establishment according to the session invitation response message.

In an embodiment of the invention, the establishing submodule is further configured to:

The second sending submodule determines whether the session join response message fed back by the second execution node includes accepting the join session response message, and if yes, sending a session invitation including the success indication to the first management child node The response sub-module accepts that the second execution node joins the session to complete session establishment; otherwise, the sending sub-module sends a session invitation response message including a failure indication to the first management sub-node.

In an embodiment of the present invention, the session invitation response message sent by the second sending submodule further includes at least the session identifier, the identifier of the first executing node, and the identifier of the second executing node. One.

In an embodiment of the present invention, the management node further includes a determining module, where the determining module is configured to determine whether the number of executing nodes joining the session is equal to before sending the session joining request to the second executing node. The maximum number of nodes supported by the session, if equal, does not send a session join request to the second execution node.

To solve the above problem, an embodiment of the present invention provides an M2M communication system, where the system includes a first execution node, a management node, and a second execution node:

The first execution node is configured to send a session establishment request to the management node before the first execution node and the second execution node perform data interaction; the session establishment request includes identification information of the second execution node as the session receiver ;

The management node is configured to receive the session establishment request; and establish a session between the first execution node and the second execution node according to the session establishment request;

The first execution node and the second execution node are further configured to join the session; and perform data interaction through the session.

The beneficial effects of the embodiments of the present invention are:

The M2M communication method and system in the embodiment of the present invention and the management node in the M2M network, the M2M communication method in the embodiment of the present invention is specifically: the management node receives the session establishment request sent by the first execution node as the session initiator, and establishes the session. The request includes the identification information of the second execution node as the session receiver; and establishes a session between the first execution node and the second execution node according to the session establishment request; enabling the first execution node and the second execution node to perform the session through the session Data interaction. The communication method enables the two nodes in the M2M to perform data interaction when using a dedicated session to avoid data interaction between the existing two nodes, and sends the data to the management node, where the data is needed in the management node. Obtaining data causes the management node to store large amounts of data, heavy load, and untimely data interaction. It reduces the load on the management node and improves the data transmission efficiency in M2M.

DRAWINGS

1 is a schematic structural diagram of an M2M network in related art;

2 is a schematic flowchart of an M2M communication method according to Embodiment 1 of the present invention;

3 is a schematic flowchart of an M2M communication method according to Embodiment 2 of the present invention;

4 is a schematic flowchart of an M2M communication method according to Embodiment 3 of the present invention;

5 is a schematic flowchart of an M2M communication method according to Embodiment 4 of the present invention;

FIG. 6 is a schematic flowchart of an M2M communication method according to Embodiment 5 of the present invention;

7 is a schematic diagram of a first structure of a management node in an M2M communication network according to Embodiment 6 of the present invention;

8 is a schematic diagram of a second structure of a management node in an M2M communication network according to Embodiment 6 of the present invention;

9 is a schematic diagram of a third structure of a management node in an M2M communication network according to Embodiment 6 of the present invention;

10 is a fourth structural diagram of a management node in an M2M communication network according to Embodiment 6 of the present invention;

FIG. 11 is a schematic structural diagram of an M2M communication system according to Embodiment 7 of the present invention.

detailed description

The present invention will be further described in detail below in conjunction with the accompanying drawings and specific embodiments.

Embodiment 1

The M2M communication method of this embodiment, as shown in FIG. 2, includes the following steps:

Step S101: The management node receives a session establishment request sent by the first execution node as the session initiator.

In this step, it should be understood that the first execution node is registered to the management node, and before the first execution node performs data interaction with the second execution node, the first execution node, which is the session initiator, sends a session establishment request to the management node, The session establishment request includes identification information of the second execution node that the first execution node wants to perform data interaction, that is, identification information of the second execution node that is the session receiver. It should be understood that the management node already knows the identification information of the first execution node. Of course, the session establishment request may also include the identification information of the first execution node, and may also include the number of execution nodes that can be accessed by the established session for data interaction. The first execution section The point and the second execution node may be a node including the common service entity CSE and a node not including the common service entity CSE, it being understood that the first execution node and the second execution node may be executed at the end of the logical unit including the actual M2M application. A node can also be an intermediate node or a base node that includes logical units that manage and service applications.

Step S102: The management node establishes a session between the first execution node and the second execution node according to the session establishment request.

In this step, the management node establishes a session between the first execution node and the second execution node according to the session establishment request, which is specifically performed according to the session establishment request sent by the first execution node and the session response fed back by the second execution node. The session is established. After the session is established, the first execution node and the second execution node perform data interaction through the session, so that a peer-to-peer communication can be formed between the first execution node and the second execution node, so that the data can be timely interacted, and the number of interactions is also reduced. Manage the load of the node and avoid the storage of unnecessary data. It is worth noting that M2M various execution nodes usually perform real-time communication services. This ongoing real-time communication is called a session at the service layer. After the session is established, the execution nodes communicate according to the session configuration parameters. Billing is performed separately for the session. In the M2M service, it is necessary to perform dedicated resource management on the session to facilitate statistics and management of the QoS (Quality of Service) and charging of the session.

Embodiment 2

The M2M communication method of this embodiment, as shown in FIG. 3, includes the following steps:

Step S201: The management node receives a session establishment request sent by the first execution node as the session initiator, where the session establishment request includes identification information of the second execution node as the session receiver; it should be understood that the first execution is received at the management node. Before the session establishment request sent by the node, the management node receives the registration request sent by the first execution node, and completes the registration. The session establishment request is mainly to let the management node know that the session needs to be established, and the node information that joins the session is the node information of the receiver.

Step S202: The management node allocates a session resource and allocates a session identifier according to the session establishment request.

In this step, it should be understood that the management node may randomly allocate session resources, or allocate resources according to specific information content in the session establishment request, and may also allocate resources according to a preset principle. The allocation resources of the present application can be implemented in the manner in which the existing communication mechanism performs session resource allocation.

Step S203: The management node sends a session join request to the second execution node.

In this step, the session join request includes the session identifier and the identification information of the first execution node; the main purpose is to let the receiver node know who established the session, the basic information of the session. Should be understood as sent to the second executive section The point may include being sent directly to the second execution node, and may also be forwarded to the second execution node by other management nodes.

Step S204: The management node receives a session join response message that is sent by the second execution node according to the session join request.

In this step, the session join response message fed back by the second node is received, mainly to know whether the second execution node is to join the session. And determining, according to the information content fed back by the second execution node, whether to join the session, for example, accepting the joining session or refusing to join the session, and including a success indication in the feedback response message indicating joining the session, and including a failure indication indicating refusing to join the session. And determining according to a preset principle, for example, sending a session join request to the second execution node, if receiving the feedback information within a preset time, indicating that the session is refused to join, if not receiving the feedback information, indicating joining Accept to join the session. It should be understood that the existing feedback mechanism can be used to implement the knowledge of the present application to join the session.

Step S205: The management node completes the session establishment according to the session join response message.

In this step, it should be understood that it is first determined whether the session join response message is an accepting join session or a refusal to join the session, and the session resource is correspondingly processed according to the judgment result.

Step S206: The first execution node and the second execution node perform data interaction through the session.

In this step, the first execution node and the second execution node perform data interaction through the session, so that data interaction can be performed in time, and the problem that the existing node needs to obtain data before the management node acquires data is avoided.

Embodiment 3

The M2M communication method of this embodiment, as shown in FIG. 4, includes the following steps:

Step S301: the first execution node (AE1) and the second execution node (AE2) in the M2M are registered to the first management child node (CSE1);

The step specifically includes the first management sub-node accepting the registration request of the first execution node and the second execution node, and completing registration of the first execution node and the second execution node.

Step S302: The M2M first execution node 1 (AE1) sends a session establishment request to the first management child node 1 (CSE1);

In this step, the session establishment request includes: a second execution node identifier, which may further include a first execution node identifier and a maximum session participation number; in actual operation, the session establishment request may also be composed of two messages, one is The session resource creation request message is the initiator information, which may include the identifier of the first execution node, and may optionally include the maximum number of participants in the session; the other is the session invitation request message, that is, the receiver information, where the second execution node is included. Logo.

Step S303: CSE1 allocates a session resource and allocates a session identifier according to the session establishment request.

In this step, it should be understood that after receiving the session establishment request, the session resource is created, the first branch execution node resource is created, and the session identifier is assigned. Further, the session resource attribute "state" can be set to "inactive" or "establishing". "Set the attribute "role" of the participant "AE1" to "initiator"; the attribute "role" refers to the role represented by the participant in the session, including "initiator" and "invitee". The "initiator" refers to the first execution node that initiates the session establishment, and the "invitee" refers to the object that is invited to join the session by the initiator, or the second execution node that is the object that requests to join after the session is established.

Further, if the session establishment request includes “maximum number of participants in the session”, the attribute “maximum participation number” is set for the session resource or the participant resource, and the value of the attribute “maximum participation number” is set to the received “maximum participant of the session”. number".

Step S304: CSE1 checks whether the second execution node (AE2) is locally registered;

Step 305: If not, the CSE1 does not send a session request message to the AE2, and sends a session establishment failure response message to the AE1. The session establishment failure response message includes: a failure indication, and may also include a failure reason, where the second execution node is set to Not found"; further may include a session identifier and/or an identification of the second execution node;

Step S306: If the CSE1 confirms that the second execution node (AE2) has been locally registered, the session join request is sent to the AE2, where the session join request includes: a session identifier, and an identifier of the first execution node;

Step S307: After confirming acceptance of joining the session, AE2 sends a session join response message to CSE1, where the session join response message includes accepting the join session information, and the session join response message may further include a session identifier, a first execution node, and a Performing at least one of the node identifiers;

Step S308: After receiving the session join response message of the AE2, the CSE1 considers that the session response message includes a success indication, accepts the second execution node to join the session, creates a second execution node resource, and completes the session establishment;

In this step, further, the attribute "status" of the session resource is set to "activate"; the participant resource is created for AE2, and the attribute "role" of the participant resource "AE2" is set to "invitee". Further, before receiving the AE2 session join request message, it is determined whether the maximum number of session participants is reached. If the maximum number of thresholds is reached, the session join request message is not received.

Step S309: CSE1 sends a session establishment success response message to the first execution node;

Step S310: If the acceptance session joining information of the AE2 is not received within the specified time, the user refuses to join the session or receives a session join response message including the refusal to join the session;

Step 311: CSE1 rejects the second execution node to join the session;

In this step, the session establishment failure response message includes a failure indication; and may also include a failure reason, which is set to "the second execution node is not responding"; and may further include a session identifier and/or a second execution node identifier. If the response message contains a failure indication, CSE1 marks the invitee AE2 as "failed"; or does not receive a response from AE2 within the specified time, CSE1 marks AE2 as "failed"; CSE1 confirms if all second executions If the node is marked as "failed", the session resource and its first execution node resource are deleted, a session establishment response message is sent to AE1, and the session establishment failure information is included in the response message.

Step S312: CSE1 sends a session establishment failure response message to AE1.

Embodiment 4

The M2M communication method of this embodiment, as shown in FIG. 5, includes the following steps:

Step S401: the first execution node (AE1) in the M2M is registered to the first management sub-node (CSE1), and the second execution node (AE2) is registered to the second management sub-node (CSE2);

Step S402: The first execution node 1 (AE1) in the M2M sends a session establishment request to the first management child node 1 (CSE1);

In this step, the session establishment request includes: a second execution node identifier, which may further include a first execution node identifier and a maximum session participation number; in actual operation, the session establishment request message may also be composed of two messages, one is a session. The resource creation request message may include an identifier of the first execution node, and may optionally include a maximum number of participants in the session; and another is a session invitation request message, where the identifier of the second execution node is included.

Step S403: CSE1 allocates a session resource and allocates a session identifier according to the session establishment request;

Step S404: CSE1 sends a session invitation request to CSE2; the session invitation request includes a session identifier, an identifier of the first execution node, and an identifier of the second execution node;

In this step, it should be understood that there may be multiple management sub-nodes between the first management sub-node CSE1 and the second management sub-node CSE2, and each intermediate management sub-node transmits data to the second management through the existing data transmission mode. Child node CSE2.

Step S405: CSE2 checks whether the second execution node (AE2) is locally registered;

Step S406: If not, the CSE2 does not send a session join request to the AE2, and sends a session invite response message including the failure indication to the CSE1;

Step S407: CSE1 rejects the second execution node joining the session:

Step 408: CSE1 sends a session establishment failure response message to AE1; the session establishment failure response message includes: a failure indication, and may also include a failure reason, which is set to "the second execution node is not found"; further may further include a session identifier and/or Or the identity of the second execution node;

Step S409: If the CSE2 confirms that the second execution node (AE2) has been locally registered, the session join request is sent to the AE2, and the session join request includes: the session identifier and the identifier of the initiator;

Step 410: After confirming accepting the joining session, AE2 sends a session join response message to CSE2, where the session join response message includes accepting the join session information, and the session join response message may further include a session identifier, a first execution node, and a second Executing at least one of the node identifiers;

Step S411: CSE2 sends a session invitation response message including a success indication to CSE1.

Step S412: The CSE1 receives the session invitation response message including the success indication on the CSE2, and if the session response message includes the success indication, accepts the second execution node to join the session, creates the second execution node resource, and completes the session establishment;

Step S413: CSE1 sends a session establishment success response message to the first execution node;

Step S414: After receiving the session join request, the AE2 does not send the session join response message including the accept session information to the CSE2 within a preset time, or sends a session join response message including the failure indication in the session join response message, indicating that the AE2 refuses to join. The session;

Step S415: CSE2 sends a session invitation response message including a failure indication to CSE1.

Step S416: CSE1 receives a session invitation response message including a failure indication on CSE2, and CSE1 rejects the second execution node to join the session;

In this step, the session establishment failure response message includes a failure indication; and may also include a failure reason, which is set to "the second execution node is not responding"; and may further include a session identifier and/or a second execution node identifier. If the response message contains a failure indication, CSE1 marks the invitee AE2 as "failed"; or does not receive a response from AE2 within the specified time, CSE1 marks AE2 as "failed"; CSE1 confirms if all second executions If the node is marked as "failed", the session resource and its first execution node resource are deleted, a session establishment response message is sent to AE1, and the response message contains session establishment failure information.

Step S417: And send a session establishment failure response message to AE1.

Embodiment 5

The M2M communication method of this embodiment, as shown in FIG. 6, includes the following steps:

Step S501: The first execution node as the session initiator sends a session establishment request to the management node; the session establishment request includes identification information of the second execution node as the session receiver;

Step S502: The management node receives the session establishment request.

Step S503: The management node establishes a session between the first execution node and the second execution node according to the session establishment request.

Step S504: the first execution node and the second execution node join the session;

Step S505: The first execution node and the second execution node perform data interaction through the session.

Embodiment 6

The invention also provides a management node in an M2M communication network. As shown in FIG. 7, the management node includes a receiving module and an establishing module. The receiving module is configured to perform data exchange between the first execution node and the second execution node. Before the mutual, receiving a session establishment request sent by the first execution node as the session initiator, the session establishment request includes identification information of the second execution node as the session receiver; the establishing module is configured to establish the first execution node according to the session establishment request A session between the second execution nodes; the session is used for data interaction between the first execution node and the second execution node.

The invention also provides a management node in an additional M2M communication network. As shown in FIG. 8, the management node includes a first management sub-node, and the first management sub-node includes a first registration sub-module, a preparation sub-module, a first transmission sub-module, a first receiving sub-module, and a establishing sub-module. The first registration sub-module is configured to receive the registration request sent by the first execution node and the second execution node to complete the registration of the first execution node and the second execution node respectively before receiving the session establishment request sent by the first execution node. The registration sub-module is configured to allocate the session resource and the allocation session identifier according to the session establishment request; the first sending sub-module is configured to send the session joining request to the second executing node, where the session joining request includes the session identifier and the identification information of the first executing node. The first receiving submodule is configured to receive a session join response message that is sent by the second executing node according to the session join request; the establishing submodule is configured to complete the session establishment according to the session join response message;

The invention also provides a management node in an additional M2M communication network. As shown in FIG. 9, the management node includes a first management sub-node and a second management sub-node, where the first management sub-node includes a first registration sub-module, a preparation sub-module, a first transmission sub-module, a first receiving sub-module, and A submodule is created, where the second management submodule includes a second registration submodule, a second receiving submodule, and a second sending submodule. The first registration submodule is configured to receive a registration request sent by the first execution node to complete registration of the first execution node before receiving the session establishment request sent by the first execution node; and the second registration submodule is configured to receive the second execution. The registration request sent by the node completes registration of the second execution node; the preparation submodule is configured to allocate the session resource and the allocation session identifier according to the session establishment request; the first sending submodule is configured to send the session invitation request message to the second management child node; The invitation request includes a session identifier, identification information of the first execution node, and identification information of the second execution node; the second receiving submodule is configured to receive the session invitation request; and the second sending submodule is configured to send the session join request according to the session invitation request. a second execution node, the session join request includes a session identifier and an identifier of the first execution node; the second receiving submodule is further configured to receive a session join response message that is sent by the second execution node according to the session join request; and the second sending submodule further sets To send a response message according to the session Invitation response message to the first sub-management node; a first receiving sub-module is further arranged to receive a second session management sub-node according to a session invitation request feedback message in response to an invitation; sub-module is configured to establish a response message according to the session invitation session establishment is completed.

Further, when the first receiving submodule receives the session joining response message fed back by the second executing node according to the session joining request, if the first receiving submodule receives the session joining response message fed back by the second executing node, including accepting the joining session, establishing the submodule Accepting the second execution node joining the session, completing the session establishment and sending a session establishment success response message to the first execution node; if the first receiving submodule receives the session feedback fed back by the second execution node The incoming response message includes a refusal to join the session, the establishing submodule rejects the second executing node to join the session, and sends a session establishment failure response message to the first executing node. When the first receiving submodule receives the session invitation response message fed back by the second sending submodule according to the session invitation request, if the second receiving submodule receives the session joining response message fed back by the second executing node, the second sending subs The module sends a session invitation response message including a success indication to the first receiving submodule, the first receiving submodule receives the session invitation response message, and the establishing submodule accepts the second executing node to join the session, completes the session establishment, and sends a session establishment success response message to the a first execution node; if the second receiving submodule receives the session join response message fed back by the second execution node, including the refusal to join the session, the second sending submodule sends a session invitation response message including the failure indication to the first receiving submodule, the receiving sub The module receives the session invitation response message, and the establishing submodule rejects the second execution node to join the session, and sends a session establishment failure response message to the first execution node, that is, the second sending submodule determines whether the session join response message fed back by the second execution node is Including acceptance a response message, if yes, sending a session invitation response message including a success indication to the first management child node; the establishing submodule accepting the second execution node joining the session to complete the session establishment; otherwise, the sending submodule sending the failure to the first management child node includes failure Indicated session invitation response message.

Further, the session invitation response message sent by the second sending submodule further includes at least one of a session identifier, an identifier of the first execution node, and an identifier of the second execution node.

The invention also provides a management node in an additional M2M communication network. As shown in FIG. 10, the management node further includes a determining module, and the determining module is configured to determine whether the number of executing nodes joining the session is equal to the maximum number of nodes supported by the session before sending the session joining request to the second executing node, if equal to, The session join request is not sent to the second execution node.

Example 7

The present invention also provides an M2M communication system. As shown in FIG. 11, the system includes a first execution node, a management node, and a second execution node. The first execution node is configured to send a session establishment request to the management node before the first execution node and the second execution node perform data interaction; the session establishment request includes identification information of the second execution node as the session receiver; the management node setting Establishing a request for receiving a session; and establishing a session between the first execution node and the second execution node according to the session establishment request; the first execution node and the second execution node are further configured to join the session; and perform data interaction through the session.

One of ordinary skill in the art will appreciate that all or a portion of the above steps may be accomplished by a program that instructs the associated hardware, such as a read-only memory, a magnetic disk, or an optical disk. Alternatively, all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the foregoing embodiment may be implemented in the form of hardware or in the form of a software function module. The invention is not limited to any specific form of combination of hardware and software.

The above embodiments are only intended to illustrate the technical solutions of the present invention and are not to be construed as limiting the invention. It should be understood by those skilled in the art that the present invention may be modified or equivalently substituted without departing from the spirit and scope of the invention.

Industrial applicability

As described above, the M2M communication method and system and the management node in the M2M network provided by the embodiments of the present invention have the following beneficial effects: the existing two nodes perform data interaction, and the data is sent to the management node. When the data is acquired at the management node, the management node stores a large amount of data, a large load, and a data interaction failure. The effect of reducing the load on the management node and improving the data transmission efficiency in the M2M is achieved.

Claims

An M2M communication method, before the first execution node and the second execution node perform data interaction:

The management node receives a session establishment request sent by the first execution node as a session initiator, where the session establishment request includes identification information of the second execution node as a session receiver;

Establishing, by the management node, a session between the first execution node and the second execution node according to the session establishment request, where the session is used for data interaction between the first execution node and the second execution node .
The M2M communication method according to claim 1, wherein the establishing, by the management node, the session between the first execution node and the second execution node according to the session establishment request comprises:

The management node allocates a session resource and an allocation session identifier according to the session establishment request;

The management node sends a session join request to the second execution node, where the session join request includes the session identifier and the identifier information of the first execution node;

Receiving, by the management node, a session join response message that is sent by the second execution node according to the session join request;

The management node completes session establishment according to the session join response message.
The M2M communication method according to claim 2, wherein said management node includes a first management child node and a second management child node, and said establishing a session between said first execution node and said second execution node includes :

The first management sub-node allocates a session resource and a session identifier according to the session establishment request; and sends a session invitation request message to the second management sub-node; the session invitation request includes the session identifier, the first Performing identification information of the node and identification information of the second execution node;

The second management sub-node sends a session join request to the second execution node according to the session invitation request, where the session join request includes a session identifier and an identifier of the first execution node; and the second execution node is received. According to the session join request response, the session join response message is

Sending a session invitation response message to the first management child node according to the session join response message;

The first management sub-node completes session establishment according to the session invitation response message.
The M2M communication method according to claim 3, wherein said first management sub-node completes session establishment according to said session invitation response message:

The second management sub-node determines whether the session join response message fed back by the second execution node includes accepting the join session response message, and if yes, sending a session invite response message including a success indication to the first management sub-node; The first management subsection accepts that the second execution node joins the session to complete session establishment; otherwise, the second management subnode sends a session invitation response message including a failure indication to the first management subnode.
The M2M communication method according to claim 4, wherein the session invitation response message further comprises at least one of the session identifier, an identifier of the first execution node, and an identifier of the second execution node.
A machine-to-machine communication method according to any one of claims 2 to 5, wherein said management node, before transmitting a session join request to said second execution node, comprises the steps of: determining the number of execution nodes joining said session Whether it is equal to the maximum number of nodes supported by the session, if equal, does not send a session join request to the second execution node.
An M2M communication method, before the first execution node and the second execution node perform data interaction:

The first execution node as a session initiator sends a session establishment request to the management node; the session establishment request includes identification information of the second execution node as a session receiver;

The management node receives the session establishment request;

Establishing, by the management node, a session between the first execution node and the second execution node according to the session establishment request;

The first execution node and the second execution node join the session;

The first execution node and the second execution node perform data interaction through the session.
A management node in an M2M communication network, the management node comprising a receiving module and an establishing module:

The receiving module is configured to receive, before the first execution node and the second execution node perform data interaction, a session establishment request sent by the first execution node as a session initiator, where the session establishment request is included as a session receiver Identification information of the second execution node;

The establishing module is configured to establish a session between the first execution node and the second execution node according to the session establishment request; the session is used by the first execution node and the second execution node Data interaction.
The management node according to claim 8, wherein the management node comprises a first management sub-node and a second management sub-node, the first management sub-node comprising a preparation sub-module, a first transmission sub-module, and a first reception a submodule and a submodule, the second management submodule comprising a second receiving submodule and a second transmitting submodule:

The preparation submodule is configured to allocate a session resource and allocate a session identifier according to the session establishment request;

The first sending sub-module is configured to send a session invitation request message to the second management sub-node; the session invitation request includes the session identifier, the identifier information of the first execution node, and the second execution node Identification information;

The second sending sub-module is configured to send a session joining request to the second executing node according to the session invitation request, where the session joining request includes a session identifier and an identifier of the first executing node;

The second receiving submodule is configured to receive a session join response message that is sent by the second executing node according to the session joining request;

The second sending submodule is further configured to send a session invitation response message to the first management child node according to the session join response message;

The establishing submodule is configured to complete session establishment according to the session invitation response message.
The management node of claim 9, wherein the establishing submodule is further configured to:

The second sending sub-module determines whether the session join response message fed back by the second executing node includes accepting the join session response message, and if yes, sending a session invite response message including a success indication to the first management child node; The establishing submodule accepts that the second executing node joins the session to complete session establishment; otherwise, the sending submodule sends a session invitation response message including a failure indication to the first management child node.
The management node according to claim 10, wherein the session invitation response message sent by the second sending submodule further includes the session identifier, the identifier of the first executing node, and the identifier of the second executing node. At least one of them.
The management node according to any one of claims 9 to 11, wherein the management node further comprises a judging module, the judging module being arranged to determine to join the session before sending the session join request to the second execution node Whether the number of execution nodes of the session is equal to the maximum number of nodes supported by the session. If equal, the session join request is not sent to the second execution node.
An M2M communication system, the system comprising a first execution node, a management node, and a second execution node:

The first execution node is configured to send a session establishment request to the management node before the first execution node and the second execution node perform data interaction; the session establishment request includes identification information of the second execution node as the session receiver ;

The management node is configured to receive the session establishment request; and establish a session between the first execution node and the second execution node according to the session establishment request;

The first execution node and the second execution node are further configured to join the session; and perform data interaction through the session.