WO2024007137A1

WO2024007137A1 - Message processing methods and apparatuses, and device, storage medium and program product

Info

Publication number: WO2024007137A1
Application number: PCT/CN2022/103763
Authority: WO
Inventors: 吕小强
Original assignee: Oppo广东移动通信有限公司
Priority date: 2022-07-04
Filing date: 2022-07-04
Publication date: 2024-01-11

Abstract

Message processing methods and apparatuses, and a device, a storage medium and a program product, which belong to the technical field of Internet of Things. A message processing method comprises: acquiring message type indication information of a first message (401), wherein a message type indicated by the message type indication information comprises a unicast session message, a multicast session message or a message counter synchronization protocol (MCSP) session message; and setting a parameter value of a first parameter in the first message according to the message type indication information, so as to generate the first message corresponding to the message type indication information (402), wherein parameter values of the first parameter that correspond to different message types are different. The solution improves the transmission efficiency of MCSP session messages.

Description

Message processing methods, devices, equipment, storage media and program products

Technical field

This application relates to the technical field of the Internet of Things, and in particular to a message processing method, device, equipment, storage medium and program product.

Background technique

With the continuous development of Internet of Things (IoT) technology, more and more IoT devices have brought great convenience to users' production and life in many fields such as smart homes and industrial production.

In related technologies, an Internet of Things device can send a message to a specific device through unicast, or the Internet of Things device can also send a message to a certain group of devices through multicast.

Contents of the invention

Embodiments of the present application provide a message processing method, device, equipment, storage medium and program product. The technical solutions are as follows:

On the one hand, embodiments of the present application provide a message processing method, which is executed by a message sending device. The method includes:

Obtain message type indication information; the message type indicated by the message type indication information includes unicast session message, multicast session message or message count synchronization protocol MCSP session message;

Set the parameter value of the first parameter in the first message according to the message type indication information to generate the first message corresponding to the message type indication information;

Wherein, the parameter value of the first parameter corresponding to different message types is different; the parameter value of the first parameter is used to indicate whether the first field exists in the first message, and when the first field exists When, the parameter value of the first parameter is also used to indicate the identification type of the field value of the first field; the identification type includes the identification information of the receiving node group of the first message, or the first Identification information of the receiving node of the message.

On the one hand, embodiments of the present application provide a message processing method, which is executed by a message receiving device. The method includes:

receive the first message;

Parse the first parameter in the first message;

According to the parameter value of the first parameter, perform the step of obtaining the field value of the first field in the first message;

Wherein, the parameter value of the first parameter is set by the message sending device according to the message type indication information of the first message; the parameter value of the first parameter corresponding to different message types is different; the parameter value of the first parameter is The parameter value is used to indicate whether the first field exists in the first message, and when the first field exists, the parameter value of the first parameter is also used to indicate the identification of the field value of the first field. Type; the identification type includes identification information of the receiving node group of the first message, or identification information of the receiving node of the first message.

On the other hand, an embodiment of the present application provides a message processing device, which includes:

An acquisition module, configured to acquire message type indication information; the message types indicated by the message type indication information include unicast session messages, multicast session messages or message count synchronization protocol MCSP session messages;

A generating module configured to set the parameter value of the first parameter in the first message according to the message type indication information, so as to generate the first message corresponding to the message type indication information;

A receiving module, used to receive the first message;

A parsing module, used to parse the first parameter in the first message;

An obtaining module, configured to perform the step of obtaining the field value of the first field in the first message according to the parameter value of the first parameter;

On the other hand, embodiments of the present application provide a computer device, the computer device is implemented as an information reporting device, and the computer device includes a processor, a memory, and a transceiver;

A computer program is stored in the memory, and the processor executes the computer program, so that the computer device implements the above message processing method.

In yet another aspect, embodiments of the present application provide a computer device, which includes a processor, a memory, and a transceiver. The memory stores a computer program, and the computer program is configured to be executed by the processor, so as to Implement the above message processing method.

On another aspect, embodiments of the present application also provide a computer-readable storage medium, in which a computer program is stored, and the computer program is loaded and executed by a processor to implement the above message processing method.

In another aspect, the present application also provides a chip, which is used to run in a computer device, so that the computer device executes the above message processing method.

In yet another aspect, the present application provides a computer program product including computer instructions stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the above message processing method.

In another aspect, the present application provides a computer program, which is executed by a processor of a computer device to implement the above message processing method.

The technical solutions provided by the embodiments of this application can bring the following beneficial effects:

In the process of generating the first message, the message sending device sets different first parameter values for the unicast session message, multicast session message and MCSP session message. The parameter value of the first parameter can be used to indicate the first message. Whether the first field exists in , and when the first field exists, the parameter value of the first parameter is also used to indicate the identification type of the field value of the first field; the identification type includes the identification information of the receiving node group of the first message , or the identification information of the receiving node of the first message; the above solution allows the device that receives the first message to quickly determine the destination device of the first message based on the first parameter and the first field in the first message, thereby improving Transmission efficiency of MCSP session messages.

Description of the drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings without exerting creative efforts.

Figure 1 is a schematic diagram of the network architecture of the Internet of Things provided by an embodiment of the present application;

Figure 2 is a schematic diagram of the message structure in the Internet of Things provided by an embodiment of the present application;

Figure 3 is a schematic structural diagram of a message load involved in the embodiment shown in Figure 2;

Figure 4 is a flow chart of a message processing method provided by an embodiment of the present application;

Figure 5 is a flow chart of a message processing method provided by an embodiment of the present application;

Figure 6 is a flow chart of a message processing method provided by an embodiment of the present application;

Figure 7 is a schematic diagram of message generation involved in the embodiment shown in Figure 6;

Figure 8 is a schematic diagram of another message generation involved in the embodiment shown in Figure 6;

Figure 9 is a schematic diagram of yet another message generation involved in the embodiment shown in Figure 6;

Figure 10 is a block diagram of a message processing device provided by an embodiment of the present application;

Figure 11 is a block diagram of a message processing device provided by an embodiment of the present application;

Figure 12 is a schematic structural diagram of a computer device provided by an embodiment of the present application.

Detailed ways

The network architecture and business scenarios described in the embodiments of this application are to more clearly explain the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. Those of ordinary skill in the art will know that with the network architecture evolution and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

Please refer to Figure 1, which shows a schematic diagram of the network architecture of the Internet of Things provided by an embodiment of the present application. The network architecture of the Internet of Things may include: an Internet of Things device 110 (shown as an Internet of Things device 110a, an Internet of Things device 110b, an Internet of Things device 110c, and an Internet of Things device 110d in Figure 1) and a configuration device 120; optionally, the The network architecture may also include bridging devices 130;

The Internet of Things device 110 may refer to a device used to provide client functions or server functions corresponding to the Internet of Things protocol in the Internet of Things.

For example, the IoT device 110 may be a smart home device, such as a smart switch, a smart lamp, a smart TV, a smart air conditioner, a smart refrigerator, a smart microwave oven, a smart rice cooker, a sweeping robot, etc.

Alternatively, the IoT device 110 may be an industrial production equipment, such as a lathe, an industrial robot, a solar panel, a wind turbine, etc.

Alternatively, the Internet of Things device 110 may be a commercial service device, such as an unmanned vending machine or the like.

Alternatively, the IoT device 110 may be a sensing device, such as a surveillance camera, an infrared sensor, a sound sensor, a temperature sensor, etc.

In a possible implementation, the configuration device 120 is a user-side terminal device. For example, the configuration device 120 can be a smart controller, a smart remote control, a smart phone, a tablet, a smart watch, a smart TV, a smart speaker, a smart switch, a gateway, etc.; or the configuration device 120 can also be a personal computer, such as a desktop. Computers, laptops, personal workstations and more.

In another possible implementation, the configuration device 120 refers to a client entity (which may be a virtual entity) running on a terminal device. For example, the configuration device 120 may run in a terminal device and is used to configure the Internet of Things device. Application (Application, APP) for access, control, and management operations.

The bridge device 130 is used to implement interaction between two devices supporting different Internet of Things protocols. The bridge device 130 provides information conversion and transfer services between IoT devices 110 that support different IoT protocols, or between IoT devices 110 that support different IoT protocols and the configuration device 120 .

The bridging device 130 may be a device dedicated for bridging, or the bridging device 130 may also be an intelligent device with a bridging function, such as a gateway or a router.

In the embodiment of the present application, the above-mentioned Internet of Things device 110, configuration device 120, and bridge device 130 may be electronic devices that meet the same or different Internet of Things protocols. For example, they may be electronic devices that meet the requirements of the Connectivity Standards Alliance (CSA). Matter protocol for electronic devices.

In Figure 1, when the IoT device 110a and the IoT device 110c support the same protocol specification, a secure connection can be established between the IoT device 110a and the IoT device 110c, for example, a secure connection is established based on the Matter specification.

When the IoT device 110b and the IoT device 110d support different protocol specifications, for example, the IoT device 110b is a Zigbee device and the IoT device 110d is a Matter device, the IoT device 110b and the IoT device 110d can connected via a bridge device 130.

Please refer to Figure 2, which shows a schematic structural diagram of the Matter protocol message in the Internet of Things provided by an exemplary embodiment of the present application. As shown in Figure 2, a Matter protocol message in the Internet of Things can include a message header (Message Header), a message payload (Message Payload), and a message footer (Message Footer).

The message header includes the message length (Message Length) field, the message label (Message Flags) field, the session ID (session ID) field, the security label (Security Flags) field, and the message counter (Message Counter) field; the message header can also contain Source Node ID field, Destination Node ID field and Message extensions field.

The message payload may contain encrypted message payload content.

The message tail can contain a Message Integrity Check field.

In the message structure shown in Figure 2 above, Message Flags can contain S tag (S Flag) and DSIZ tag (DSIZ Flag). If S Flag = 1, the Source Node ID will be included in the message. If DSIZ Flag=1, then the Destination Node ID will be included in the message. In addition, if S Flag = 0, it means that the message does not contain the Source Node ID; if DSIZ Flag = 0, it means that the message does not contain the Destination Node ID.

In the message structure shown in Figure 2 above, the Security Flag can contain the session type (Session Type).

Among them, when Session Type=1, it means that the current message is a multicast session message. When Session Type=0, it indicates that the current message is a unicast session message.

Please refer to FIG. 3 , which shows a schematic structural diagram of a message payload related to an embodiment of the present application. As shown in Figure 3, the message payload in the Matter protocol message can include the protocol header (Protocol Header) and the application payload (Application Payload).

Among them, the protocol header can include the Exchange Flags field, the Protocol Opcode field, the Exchange ID field, the Protocol ID field, the Protocol Vendor ID field, Acknowledged Message Counter field, Secured Extensions field.

In Figure 3 above, Protocol ID is used to specify the protocol to which the current message belongs. The current protocol is shown in Table 1 below.

Table 1

取值范围Ranges	类型type
0x00000x0000	PROTOCOL_ID_SECURE_CHANNELPROTOCOL_ID_SECURE_CHANNEL
0x00010x0001	PROTOCOL_ID_INTERACTION_MODELPROTOCOL_ID_INTERACTION_MODEL
0x00020x0002	PROTOCOL_ID_BDXPROTOCOL_ID_BDX
0x00030x0003	PROTOCOL_ID_DIRECTED_COMMISSIONINGPROTOCOL_ID_DIRECTED_COMMISSIONING
0x0004-0xFFFF0x0004-0xFFFF	保留(reserved)reserved

In the above Table 1, 0X0000 represents the secure channel protocol, 0X0001 represents the interactive model protocol, 0X0002 represents the BDX (Bulk Data Exchange, block data exchange) protocol, and 0X0003 represents the protocol based on user configuration.

Message Counter Synchronization Protocol (MCSP) is a protocol used in the Internet of Things to confirm whether the received message is a new message. Through the MCSP protocol, in a broadcast/multicast group, if device A receives a broadcast message and cannot confirm whether the broadcast message is a new message, it can initiate a confirmation to device B that sent the broadcast message (that is, to device B). B sends an MCSP session message) to confirm the latest Message Counter of device B. Correspondingly, device B returns a confirmation message to device A. The confirmation message contains device B's latest Message Counter.

Among them, each broadcast/multicast session message will carry a Message Counter. A message sending device for broadcast/multicast session messages needs to ensure that the Message Counter of each broadcast/multicast session message sent is incremented (+1). The message receiving device of the broadcast/multicast session message can confirm whether the broadcast/multicast session message is a "replay" message based on the obtained Message Counter.

In related technologies, the Session Type in the MCSP session message is also set to 1, that is, the MCSP session message is regarded as a multicast session message in the Matter protocol, and the identification information of the receiving node of the MCSP session message is set in the Destination Node ID field. That is to say, in the related technology, when the message sending device generates a message, when the corresponding Session Type=1, the message sending device sets DSIZ Flag=1, indicating that the Destination Node ID field exists in the message. In addition, if the current message is a multicast session message, the message sending device sets the value of the Destination Node ID to the Group ID. If the current message is an MCSP session message, the message sending device sets the value of the Destination Node ID to the node of the receiving node. ID. This causes the message receiving device to receive a message with Session Type 1 and parse the value of the Destination Node ID field from the message. It cannot directly determine whether the value in the field is the group ID corresponding to the multicast session message or the group ID corresponding to the multicast session message. The ID of the receiving node corresponding to the MCSP session message requires additional determination of whether the message is a multicast session message or an MCSP session message, and then the meaning of the value in the Destination Node ID field can be determined, making it difficult for the message receiving device to quickly determine the destination device of the message. , thus affecting the transmission efficiency of MCSP session messages.

Please refer to Figure 4, which shows a flow chart of a message processing method provided by an embodiment of the present application. The method can be executed by a message sending device. For example, the message sending device can be an object in the network architecture shown in Figure 1. One of the networking devices 110; the method may include the following steps:

Step 401: Obtain the message type indication information; the message type indicated by the message type indication information includes a unicast session message, a multicast session message, or a Message Count Synchronization Protocol MCSP session message.

In this embodiment of the present application, during the process of generating the first message, the message sending device may obtain the message type indication information of the first message to be generated; the message type indication information may directly or indirectly indicate the message to which the current message belongs. type of information.

The above message types may include unicast session messages, multicast session messages or MCSP session messages. That is to say, the message type indication information can indicate which of the currently generated message is a unicast session message, a multicast session message, or an MCSP session message.

Step 402: Set the parameter value of the first parameter in the first message according to the message type indication information to generate the first message corresponding to the message type indication information; wherein the parameter value of the first parameter corresponding to different message types is different; The parameter value of the first parameter is used to indicate whether the first field exists in the first message, and when the first field exists, the parameter value of the first parameter is also used to indicate the identification type of the field value of the first field; identification type It includes the identification information of the receiving node group of the first message, or the identification information of the receiving node of the first message.

Wherein, the above-mentioned first parameter may be DSIZ Flag; the above-mentioned first field may be a Destination Node ID field.

When the first message is an MCSP session message, the field value of the above-mentioned Destination Node ID field may be the identification information of the receiving node of the first message. The identification information of the receiving node of the first message may be received by the message sending device. Identification information of the sending node of the preceding broadcast message corresponding to the first message (that is, the receiving node of the current first message).

When the first message is a multicast session message, the field value of the above-mentioned Destination Node ID field may be the identification information of the node group to which the receiving node of the first message belongs.

When the first message is a unicast session message, the Destination Node ID field may not exist in the first message.

In the embodiment of this application, when generating the first message in the Internet of Things, if the type of message to be generated is an MCSP session message, the message sending device can be configured for a unicast session message, a multicast session message, and an MCSP session message. According to different parameter values of the first parameter, the device that receives the first message can directly determine whether the first field exists according to the parameter value of the first parameter, and determine the meaning of subsequent field values in the first field. Whether to receive the identification information of the node or the identification information of the node group, so that it can be quickly determined that the destination device of the first message is a single device corresponding to the identification information of the receiving node without performing additional message type confirmation steps. Or a device group.

To sum up, in the embodiment of the present application, in the process of generating the first message, the message sending device sets different first parameter values for the unicast session message, the multicast session message and the MCSP session message. The parameter value of a parameter can be used to indicate whether the first field exists in the first message, and when the first field exists, the parameter value of the first parameter is also used to indicate the identification type of the field value of the first field; the identification type The type includes the identification information of the receiving node group of the first message, or the identification information of the receiving node of the first message; the above solution allows the device that receives the first message to based on the first parameter and the first field in the first message, The destination device of the first message is quickly determined, thereby improving the transmission efficiency of MCSP session messages.

Please refer to Figure 5, which shows a flow chart of a message processing method provided by an embodiment of the present application. The method can be executed by a message receiving device. For example, the message receiving device can be an object in the network architecture shown in Figure 1. One of the networking devices 110; the method may include the following steps:

Step 501: Receive the first message.

Step 502: Parse the first parameter in the first message.

Step 503: Execute the step of obtaining the field value of the first field in the first message according to the parameter value of the first parameter; the parameter value of the first parameter is set by the message sending device according to the message type indication information of the first message; The message types indicated by the message type indication information include unicast session messages, multicast session messages or message count synchronization protocol MCSP session messages; different message types correspond to different parameter values of the first parameter; the parameter value of the first parameter is used to indicate Whether the first field exists in the first message, and when the first field exists, the parameter value of the first parameter is also used to indicate the identification type of the field value of the first field; the identification type includes the identification type of the receiving node group of the first message Identification information, or identification information of the receiving node of the first message.

To sum up, in the embodiment of the present application, in the process of generating the first message, the message sending device sets different first parameter values for the unicast session message, the multicast session message and the MCSP session message. The parameter value of a parameter can be used to indicate whether the first field exists in the first message, and when the first field exists, the parameter value of the first parameter is also used to indicate the identification type of the field value of the first field; the identification type The type includes the identification information of the receiving node group of the first message, or the identification information of the receiving node of the first message, so that the device that receives the first message can quickly determine based on the first parameter and the first field in the first message. The destination device of the first message, thereby improving the transmission efficiency of MCSP session messages.

Please refer to Figure 6, which shows a flow chart of a message processing method provided by an embodiment of the present application. The method can be interactively executed by a message sending device and a message receiving device. The message sending device and the message receiving device can be the ones shown in Figure 1. Two devices in the Internet of Things device 110 in the network architecture shown; the method may include the following steps:

Step 601: In the process of generating the first message, the message sending device obtains the message type indication information.

The message type indicated by the message type indication information includes a unicast session message, a multicast session message or a Message Count Synchronization Protocol MCSP session message.

In a possible implementation, the above message type indication information may be session type identification information of the first message, such as Session Type ID.

For example, in the embodiment of this application, the session type identification information of messages in the Internet of Things may include but is not limited to three types: unicast session (Unicast Session) identification (which can be represented by a value of 0), multicast session (Group) Session) identifier (can be represented by a value of 1) and MCSP session identifier (can be represented by a value of 2).

Alternatively, in the embodiment of this application, the session type identifiers of messages in the Internet of Things can also be divided into two types, namely unicast session identifiers (which can be represented by a value of 0) and multicast session identifiers (which can be represented by a value of 0). 1 to represent).

The value of the above session type identifier is only exemplified by the above 0, 1 or 2. Optionally, the value of the above various session type identifiers can also be set to other types of values, as long as it can distinguish between unicast session, multicast session and MCSP sessions are sufficient, or as long as unicast sessions and multicast sessions can be distinguished.

In another possible implementation, the message type indication information of the first message may also be session context information (such as Session Context) of the first message.

For example, in the embodiment of this application, the session context information in the Internet of Things may include the following: secure unicast session context (secured unicast session context, corresponding to unicast session), multicast session context (groupcast session context, corresponding to group broadcast session), MCSP session context (MCSP session context, corresponding to MCSP session), and unsecured session context (unsecured session context).

Among them, in addition to the session type identification information and session context information, in the embodiment of the present application, other information can also be used to directly or indirectly indicate the message type of the current message, such as setting an additional parameter to indicate that the current message belongs to Which one among unicast session message, multicast session message and MCSP session message. The embodiment of the present application does not limit the form of the message type indication information.

In the embodiment of this application, in addition to the above message type indication information, the message sending device can also obtain the encryption key, Session ID, destination device ID and other information, and obtain the Message Counter.

Step 602: The message sending device sets the parameter value of the first parameter in the first message according to the message type indication information to generate a first message corresponding to the message type indication information.

In a possible implementation, when the message type indicated by the message type indication information is an MCSP session message, the message sending device sets the first parameter in the first message to the first parameter value, and sets the first parameter in the first message. The first field of is the first field value to generate the first message.

The first parameter value is used to indicate that the first field exists in the first message, and the field value of the first field is the identification information of the receiving node of the first message.

In the embodiment of the present application, after the message sending device receives a message (such as message A), if the message A sending device cannot determine whether the message A is a new message, the message sending device needs to send a message to the sender of the message A. An MCSP session message to confirm the latest Message Counter of the sender of message A. At this time, the message sending device can generate message type indication information of the message to be sent, and the message type indicated by the message type is an MCSP session message.

Or, when the message sending device needs to send a unicast session message to a specified device, the message sending device can generate message type indication information of the message to be sent, and the message type indicated by the message type is a unicast session message.

Alternatively, when the message sending device needs to send a multicast session message to a specified device group, the message sending device can generate message type indication information of the message to be sent, and the message type indicated by the message type is a multicast session message.

Among them, the message sending device can generate a message based on the information obtained in the above step 602, set the Session ID in the format of the message, and continue to set other parameters in the message (including the first parameter, the first field, etc.), Then set the Message Counter and encrypt the Application Payload until the complete first message is generated.

In this embodiment of the present application, the message sending device can determine whether the current first message is an MCSP session message according to the message type indication information, and if it is determined to be an MCSP session message, set the first parameter in the first message to the first message. A parameter value, and setting the first field in the first message as the first field value to generate the first message.

In a possible implementation solution of the embodiment of the present application, the message sending device may directly determine the message type of the first message through the session type identification information.

In a possible implementation, for the case where the message type indication information includes session type identification information, the message sending device sets the first parameter in the first message to the first parameter when the session type identification information is the MCSP session identification information. parameter value, and set the first field in the first message as the first field value to generate the first message.

In the embodiment of the present application, in the case where the session type identification information includes a unicast session identification, a multicast session identification and an MCSP session identification, if the message sending device obtains that the session type identification information of the first message is an MCSP session identification (such as The value of Session Type ID is 2), then the message sending device can determine that the current message is an MCSP session message. At this time, the message sending device can set the first parameter in the first message to the first parameter value, and set the first message The first field in is the first field value.

Optionally, in the case where the session type identification information includes a unicast session identification, a multicast session identification and an MCSP session identification, if the message sending device obtains that the session type identification information of the first message is a unicast session identification (such as Session Type ID value is 0), the message sending device can determine that the current message is a unicast session message. At this time, the message sending device can set the first parameter in the first message to the third parameter value, and there is no Set the first field. The third parameter value is used to indicate that the first message does not contain the first field.

Optionally, in the case where the session type identification information includes a unicast session identification, a multicast session identification and an MCSP session identification, if the message sending device obtains that the session type identification information of the first message is a multicast session identification (such as Session Type The value of the ID is 1), then the message sending device can determine that the current message is a multicast session message. At this time, the message sending device can set the first parameter in the first message to the fourth parameter value, and set the value in the first message. The first field of is the third field value, wherein the above-mentioned fourth parameter value is used to indicate that the first message contains the first field, and the field value of the first field is the group ID (Group ID).

In another possible implementation of the embodiment of the present application, the message sending device may determine the message type of the first message in combination with the session type identification information and other information.

In a possible implementation, for the case where the message type indication information includes session type identification information, the message sending device obtains the message type identification information of the first message when the session type identification information is a multicast session identification; message The type identification information is used to assist in identifying the message type of the first message; when the message type identification information satisfies the first condition, the first parameter in the first message is set to the first parameter value, and the first parameter in the first message is set. One field is a first field value to generate a first message.

In the embodiment of the present application, when the session type identification information includes a unicast session identification and a multicast session identification, if the message sending device obtains that the session type identification information of the first message is a multicast session identification (such as Session Type ID The value is 1), then the first message can be a multicast session message or an MCSP session message. At this time, the message sending device can further obtain the message type identification information of the first message to determine that the first message is a multicast Which of the session messages and MCSP session messages. The message sending device may determine whether the message type identification information satisfies the first condition. If so, determine that the first message is an MCSP session message. At this time, the first parameter in the first message may be set to the first parameter value, and the first parameter may be set to the first parameter value. The first field in the message is the first field value; if the message sending device determines that the message type identification information does not meet the first condition, it determines that the first message is a multicast session message. At this time, the message sending device can set the first message The first parameter in is a fourth parameter value, and the first field in the first message is set to a third field value, where the above fourth parameter value is used to indicate that the first message contains the first field, and the first field The field value is the group ID.

Optionally, in the case where the session type identification information includes a unicast session identification and a multicast session identification, if the message sending device obtains the session type identification information of the first message as a unicast session identification (for example, the value of Session Type ID is 0), then the first message may be a unicast session message. In this case, the message sending device may set the first parameter in the first message to the third parameter value, and the first field shall not be set in the first message. The third parameter value is used to indicate that the first message does not contain the first field.

In a possible implementation, the message type indication information includes at least one of the following information:

Protocol identification information (such as Protocol ID), and operation code (such as Opcode).

Among them, the above Opcode can be the message type information of the current message, which can be used to indicate the corresponding operation of the current message in the protocol corresponding to the Protocol ID (that is, the role of the message).

In a possible implementation manner, when the message type indication information includes protocol identification information, the first condition includes: the protocol identification information indicates that the protocol corresponding to the first message is the secure channel protocol.

In this embodiment of the present application, if the message type indication information includes protocol identification information, and the protocol identification information indicates the secure channel protocol (for example, protocol ID=0x0000), then the message type indication information can be considered to satisfy the first condition.

In a possible implementation manner, when the message type indication information includes an operation code, the first condition includes: the operation code indicates that the first message is an MCSP session message.

In this embodiment of the present application, if the message type indication information includes Opcode, and Opcode indicates an MCSP session message, it can be considered that the message type indication information satisfies the first condition.

In another possible implementation of the embodiment of the present application, the message sending device may directly determine the message type of the first message in combination with the session context information.

In a possible implementation, for the case where the message type indication information includes session context information, if the session context information is MCSP session context, set the first parameter in the first message to the first parameter value, and set The first field in the first message is a first field value to generate the first message.

In the embodiment of the present application, in the case where the session context information at least includes a secure unicast session context, a multicast session context, and an MCSP session context, if the message sending device obtains that the session context information of the first message is the MCSP session context, Then the message sending device can determine that the current message is an MCSP session message. At this time, the message sending device can set the first parameter in the first message as the first parameter value, and set the first field in the first message as the first field. value.

Optionally, in the case where the session context information at least includes a secure unicast session context, a multicast session context, and an MCSP session context, if the message sending device obtains that the session context information of the first message is a secure unicast session context, then The message sending device can determine that the current message is a unicast session message. At this time, the message sending device can set the first parameter in the first message to the third parameter value, and the first field is not set in the first message. The third parameter value is used to indicate that the first message does not contain the first field.

Optionally, in the case where the session context information at least includes a secure unicast session context, a multicast session context, and an MCSP session context, if the message sending device obtains that the session context information of the first message is a multicast session context, the message The sending device may determine that the current message is a multicast session message. At this time, the message sending device may set the first parameter in the first message to the fourth parameter value, and set the first field in the first message to the third field value. , wherein the above-mentioned fourth parameter value is used to indicate that the first message contains the first field, and the field value of the first field is the group identifier.

In a possible implementation manner, when the session context information is an MCSP session context, the message sending device may also set the session type identification information of the first message to a multicast session identification.

In the embodiment of this application, when the message sending device determines that the current message is an MCSP session message based on the session context information (MCSP session context), it can also set the session type identification information of the current message as a multicast session identification, For example, set the Session Type ID value of the first message to 1.

Optionally, when the session context information is a secure unicast session context, the message sending device can also set the session type identification information of the first message to a unicast session identification, for example, change the value of the Session Type ID of the first message to is 0. When the session context information is a multicast session context, the message sending device may also set the session type identification information of the first message to the multicast session identification, for example, set the Session Type ID value of the first message to 1.

In a possible implementation, the first parameter is the DSIZ label in the first message; the first field is the destination node identification field in the first message; for example, the first parameter and the first field can be set in the first in the message header.

In a possible implementation, the above-mentioned first parameter value is 1 (i.e., DSIZ Flag = 1), and the first field value is the node ID of the message recipient of the first message (i.e., Destination Node ID = message recipient’s Node ID).

In a possible implementation, when the parameter value of the first parameter is the third parameter value, the message sending device also obtains the third field value of the first field in the first message as the first message. Identification information of the node group to which the message recipient belongs; wherein the third parameter value and the third field value are set by the message sending device when the message type of the first message is a multicast session message.

In a possible implementation, the first parameter is the DSIZ label in the first message; the first field is the destination node identification field in the first message;

The third parameter value is 2 (that is, DSIZ Flag=2), and the third field value is the group ID of the message recipient of the first message (that is, Destination Node ID=Group ID).

Optionally, in the embodiment of this application, when the value of the DSIZ label is 0, it means that there is no destination node identification field in the message; when the value of the DSIZ label is 1, it means that there is a destination node identification field in the message, and the destination The field value of the node identification field is the node identification of the recipient of the first message; when the value of the DSIZ tag is 2, it means that there is a destination node identification field in the message, and the field value of the destination node identification field is the group identification (Group ID) .

In this embodiment of the present application, setting the first parameter and the first field mentioned above may refer to setting the DSIZ tag and the Destination Node ID field in the first message.

When the first message is a unicast session message, the message sending device can set the DSIZ tag to 0, indicating that the subsequent content of the first message does not contain the Destination Node ID field.

When the first message is a multicast session message, the message sending device can set the DSIZ tag to 1, indicating that the subsequent content of the first message contains the Destination Node ID field, and the content contained in the Destination Node ID field is the group identifier (i.e., the receiving The group ID of the device group for this multicast session message).

When the first message is an MCSP session message, the message sending device can set the DSIZ tag to 2, indicating that the subsequent content of the first message contains the Destination Node ID field, and the content contained in the Destination Node ID field is the recipient of the first message. The identifier is the identifier of the sender of the broadcast/multicast session message that the message receiving device has previously received and is not sure whether it is a new message.

In a possible implementation, when the message type indicated by the message type indication information is an MCSP session message, the message sending device also sets the second parameter in the first message to the second parameter value, and sets the first message The second field in is the second field value;

The second parameter value is used to indicate that the second field exists in the first message, and the field value of the second field is the identification information of the sending node of the first message.

In the embodiment of the present application, when the message type indicated by the message type indication information is a multicast session message, the message sending device can also set the second parameter in the first message to the second parameter value, and set the first message The second field in is the second field value.

In this embodiment of the present application, when the message type indicated by the message type indication information is a unicast session message, the message sending device may set the second parameter in the first message to the fifth parameter value, and in the first message The second field is not set. The fifth parameter value indicates that the first message does not contain the second field.

In a possible implementation, the second parameter is the S tag in the first message; the second field is the source node identification field in the first message.

In a possible implementation, the above-mentioned second parameter value is 1 (i.e. S Flag = 1), and the second field value is the node ID of the message sending device (i.e. Source Node ID = Node ID of the MCSP session message sender ).

Optionally, in the embodiment of this application, when the value of the S tag is 0, it means that there is no source node identification field in the message; when the value of the S label is 1, it means that there is a source node identification field in the message, and the source The field value of the node identification field is the node identification of the sender of the first message.

In this embodiment of the present application, setting the second parameter and the second field mentioned above may refer to setting the S tag and the Source Node ID field in the message header of the first message.

When the first message is a unicast session message, the message sending device can set the S tag to 0, indicating that the subsequent content of the first message does not contain the Source Node ID field.

When the first message is a multicast session message or MCSP session message, the message sending device can set the S tag to 1, indicating that the subsequent content of the first message contains the Source Node ID field, and the content contained in the Source Node ID field is the current The identifier of the sender of the message, such as the node identifier of the message sending device.

Step 603: The message sending device sends the first message; correspondingly, the message receiving device receives the first message.

In this embodiment of the present application, after the message sending device generates a complete first message, the first message can be sent in the Internet of Things. Correspondingly, the message receiving device may receive and parse the first message to determine whether the first message is a message sent to the message receiving device.

Step 604: The message receiving device parses the first parameter in the first message.

In this embodiment of the present application, the message receiving device may first parse the first parameter in the first message, for example, parse the DSIZ tag in the message header of the first message.

Step 605: According to the parameter value of the first parameter, perform the step of obtaining the field value of the first field in the first message.

In a possible implementation manner, when the parameter value of the first parameter is the first parameter value, the message receiving device obtains the first field value of the first field in the first message as the reception of the first message. Identification information of the node.

For example, when the message receiving device parses out that the value of the DSIZ tag is 1, it is determined that the first message contains the identification information of the receiving node of the first message. At this time, the first field in the first message can be read to obtain the The identification information of the receiving node of the first message (such as the Node ID of the receiving node).

Optionally, the message receiving device processes the first message according to the identification information of the receiving node of the first message.

In this embodiment of the present application, the message receiving device can compare the identification information of the receiving node of the first message with its own node identification information (such as Node ID). If the two are consistent, it is determined that the first message is sent to the message receiving device. Receive the message from the device. At this time, you can continue to parse the first message.

If the message receiving device can determine that the identification information of the receiving node of the first message is inconsistent with its own node identification information, the first message can be discarded.

Optionally, when the parameter value of the first parameter is the third parameter value, obtain the third field value of the first field in the first message as the identifier of the node group to which the message receiver of the first message belongs. information.

For example, when the message receiving device parses out that the value of the DSIZ tag is 2, it determines that the first message contains the identification information of the node group to which the receiving node of the first message belongs. At this time, the first message in the first message can be read. field to obtain the identification information (such as Group ID) of the node group to which the receiving node of the first message belongs.

Optionally, the message receiving device processes the first message according to the identification information of the node group to which the receiving node of the first message belongs.

In this embodiment of the present application, the message receiving device may compare the identification information of the node group to which the receiving node of the first message belongs with the identification information (such as Group ID) of the node group to which it belongs. If the two are consistent, determine that the node group belongs to the message receiving device. The first message is a message sent to the message receiving device. At this time, the first message can continue to be parsed.

If the message receiving device can determine that the identification information of the node group to which the receiving node of the first message belongs is inconsistent with the node identification information of the device group to which it belongs, the first message can be discarded.

In a possible implementation, when the message receiving device parses out that the value of the DSIZ tag is 0, it determines that the first message does not contain the first field, and in this case, the step of obtaining the first field can be skipped.

Please refer to Figure 7, which shows a schematic diagram of message generation involved in the embodiment of the present application. As shown in Figure 7, when the message initiator (ie, the above-mentioned message sending device) initiates a message, the process of generating the message can be as follows:

S71, obtain the encryption key, Session ID, destination device ID, and Session Type identifier.

S72, obtain the Message Counter.

S73, generate a message and set the Session ID in the message format.

S74, if the Session Type is 0 (Unicast Session), then the S Flag and DSIZ Flag are set to 0, which means that the Source Node ID and Destination Node ID fields will not appear later in the message.

S75, if the Session Type is 1 (Group Session), then S Flag = 1 and DSIZ Flag = 2, indicating that the Source Node ID and Destination Node ID fields will appear later in the message. The Source Node ID is specified as the Node ID of the message initiator, and the Destination Node ID is set as the Group ID.

S76, if Session Type is 2 (MCSP), set S Flag = 1 and DSIZ Flag = 1, indicating that the Source Node ID and Destination Node ID fields will appear later in the message. The Source Node ID is specified as the Node ID of the message initiator, and the Destination Node ID is set as the Node ID of the message receiver.

S77, set the Message Counter and encrypt the Application Payload.

Please refer to FIG. 8 , which shows a schematic diagram of another message generation involved in the embodiment of the present application. In the solution shown in Figure 8, the relevant parameters in the message can be set according to the session context of the message. The value of session context can include secured unicast session context, groupcast session context, MCSP session context and unsecured session context. As shown in Figure 8, when the message initiator (ie, the above-mentioned message sending device) initiates a message, the process of generating the message can be as follows:

S81, obtain the encryption key, Session ID, destination device ID, and Session Type identification.

S82, obtain the Message Counter.

S83, generate a message and set the Session ID in the message format.

S84, when session context=secured unicast session context, set session type=0, S Flag and DSIZ Flag are set to 0, indicating that the Source Node ID and Destination Node ID fields will not appear later in the message.

S85, when session context = groupcast session context, set session type = 1, and set S Flag = 1, DSIZ Flag = 2, indicating that the Source Node ID and Destination Node ID fields will appear later in the message. The Source Node ID is specified as the Node ID of the message initiator, and the Destination Node ID is set as the Group ID.

S86, when session context = MCSP session context, set session type = 1, and set S Flag = 1, DSIZ Flag = 1, indicating that the Source Node ID and Destination Node ID fields will appear later in the message. The Source Node ID is specified as the Node ID of the message initiator, and the Destination Node ID is set as the Node ID of the message receiver.

S87, set the Message Counter and encrypt the Application Payload.

Please refer to FIG. 9 , which shows another schematic diagram of message generation related to the embodiment of the present application. As shown in Figure 9, when the message initiator (ie, the above-mentioned message sending device) initiates a message, the process of generating the message can be as follows:

S91, obtain the encryption key, Session ID, destination device ID, and Session Type identifier.

S92, obtain the Message Counter.

S93, generate a message and set the Session ID in the message format.

S94, if Session Type is 0 (indicating Unicast Session), then S Flag and DSIZ Flag are set to 0, indicating that the Source Node ID and Destination Node ID fields will not appear later in the message.

S95, if Session Type is 1 (indicating Group Session), determine whether the value of protocol ID is 0x0000 (indicating Secure Channel Protocol), and whether the Opcode is an MCSP session message. If not, enter S96. If so, Enter S97.

S96, set S Flag = 1, DSIZ Flag = 2, indicating that the Source Node ID and Destination Node ID fields will appear later in the message. The Source Node ID is specified as the Node ID of the message initiator, and the Destination Node ID is set as the Group ID.

S97, set S Flag = 1, DSIZ Flag = 1, indicating that the Source Node ID and Destination Node ID fields will appear later in the message. The Source Node ID is specified as the Node ID of the message initiator, and the Destination Node ID is set as the Node ID of the device that sends the broadcast message in the preamble.

S98, set Message Counter. And encrypt the Application Payload.

The solution shown in the embodiment of this application uses a universal solution that is unified with unicast session messages and multicast session messages to process MCSP session messages.

To sum up, in the embodiment of the present application, when the message sending device generates the first message and confirms that the first message is an MCSP session message, the first parameter of the first message can be set to the first parameter value, At the same time, the identification information of the receiving node of the first message is set to the first field value in the first field, so that the device that receives the first message can quickly determine the first parameter and the first field in the first message. The destination device of a message, thereby improving the transmission efficiency of MCSP session messages.

Please refer to Figure 10, which shows a block diagram of a message processing device provided by an embodiment of the present application. The message processing device 1000 has the function of being executed by the message sending device in implementing the method shown in FIG. 4 or FIG. 6 . As shown in Figure 10, the device may include:

The acquisition module 1001 is used to obtain the message type indication information of the first message; the message type indicated by the message type indication information includes a unicast session message, a multicast session message or a message count synchronization protocol MCSP session message;

Generating module 1002, configured to set the parameter value of the first parameter in the first message according to the message type indication information, so as to generate the first message corresponding to the message type indication information;

In a possible implementation, the generating module is configured to set the first parameter in the first message when the message type indicated by the message type indication information is a Message Count Synchronization Protocol MCSP session message. is the first parameter value, and sets the first field in the first message to the first field value to generate the first message;

Wherein, the first parameter value is used to indicate the presence of the first field in the first message, and the field value of the first field is the identification information of the receiving node of the first message.

In a possible implementation, the message type indication information includes session type identification information.

In a possible implementation, the generating module 1002 is configured to set the first parameter in the first message to a first parameter value when the session type identification information is an MCSP session identification, and Set the first field in the first message to a first field value to generate the first message.

In a possible implementation, the generation module 1002 is used to:

When the session type identification information is a multicast session identification, obtain the message type identification information of the first message; the message type identification information is used to assist in identifying the message type of the first message;

When the message type identification information satisfies the first condition, setting the first parameter in the first message to a first parameter value, and setting the first field in the first message to a first field value, to generate the first message.

Protocol identification information, and, opcodes.

In a possible implementation, when the message type indication information includes the protocol identification information, the first condition includes:

The protocol identification information indicates that the protocol corresponding to the first message is a secure channel protocol.

In a possible implementation, when the message type indication information includes the operation code, the first condition includes:

The operation code indicates that the first message is an MCSP session message.

In a possible implementation, the message type indication information includes session context information.

In a possible implementation, the generating module 1002 is configured to set the first parameter in the first message to a first parameter value when the session context information is an MCSP session context, and set The first field in the first message is a first field value to generate the first message.

In a possible implementation, the device further includes:

A setting module configured to set the session type identification information of the first message to a multicast session identification when the session context information is an MCSP session context.

The first parameter value is 1, and the first field value is the node ID of the message recipient of the first message.

In a possible implementation, the generating module 1002 is further configured to set the second parameter in the first message to the first message when the message type indicated by the message type indication information is an MCSP session message. two parameter values, and set the second field in the first message to the second field value;

Wherein, the second parameter value is used to indicate the presence of the second field in the first message, and the field value of the second field is the identification information of the sending node of the first message.

In a possible implementation, the second parameter is the S tag in the first message; the second field is the source node identification field in the first message;

The second parameter value is 1, and the second field value is the node identifier of the message sending device.

In a possible implementation, the generating module 1002 is further configured to set the first parameter in the first message to be when the message type indicated by the message type indication information is a multicast session message. A third parameter value, and setting the first field in the first message to a third field value;

Wherein, the third parameter value is used to indicate the presence of the first field in the first message, and the field value of the first field is the identification information of the node group to which the message recipient of the first message belongs. .

The third parameter value is 2, and the third field value is the group identifier of the message recipient of the first message.

Please refer to Figure 11, which shows a block diagram of a message processing device provided by an embodiment of the present application. The message processing device 1100 has the function of being executed by the message receiving device in implementing the method shown in FIG. 5 or FIG. 6 . As shown in Figure 11, the device may include:

Receiving module 1101, used to receive the first message;

Parsing module 1102, used to parse the first parameter in the first message;

The obtaining module 1103 is configured to perform the step of obtaining the field value of the first field in the first message according to the parameter value of the first parameter;

Wherein, the parameter value of the first parameter is set by the message sending device according to the message type indication information of the first message; the message type indicated by the message type indication information includes unicast session message, multicast session message or MCSP Conversation message; different message types correspond to different parameter values of the first parameter; the parameter value of the first parameter is used to indicate whether the first field exists in the first message, and, when the first field exists, field, the parameter value of the first parameter is also used to indicate the identification type of the field value of the first field; the identification type includes the identification information of the receiving node group of the first message, or the third Identification information of the receiving node of a message.

In a possible implementation, the obtaining module 1103 is configured to obtain the first field of the first field in the first message when the parameter value of the first parameter is the first parameter value. The value is obtained as the identification information of the receiving node of the first message;

Wherein, the first parameter value and the first field value are set by the message sending device when the message type of the first message is an MCSP session message.

In a possible implementation, the obtaining module 1003 is further configured to obtain the third parameter of the first field in the first message when the parameter value of the first parameter is a third parameter value. The field value is obtained as the identification information of the node group to which the message recipient of the first message belongs;

Wherein, the third parameter value and the third field value are set by the message sending device when the message type of the first message is a multicast session message.

It should be noted that when the device provided in the above embodiment implements its functions, only the division of the above functional modules is used as an example. In practical applications, the above functions can be allocated to different functional modules according to actual needs. That is, the content structure of the device is divided into different functional modules to complete all or part of the functions described above.

Regarding the devices in the above embodiments, the specific manner in which each module performs operations has been described in detail in the embodiments related to the method, and will not be described in detail here.

Please refer to Figure 12, which shows a schematic structural diagram of a computer device 1200 provided by an embodiment of the present application. The computer device 1200 may include a processor 1201, a receiver 1202, a transmitter 1203, a memory 1204, and a bus 1205.

The processor 1201 includes one or more processing cores. The processor 1201 executes various functional applications and information processing by running software programs and modules.

The receiver 1202 and the transmitter 1203 can be implemented as a communication component, and the communication component can be a communication chip. This communication chip can also be called a transceiver.

Memory 1204 is connected to processor 1201 through bus 1205.

The memory 1204 can be used to store a computer program, and the processor 1201 is used to execute the computer program to implement various steps in the above method embodiments.

Additionally, memory 1204 may be implemented by any type of volatile or non-volatile storage device, or combination thereof, including but not limited to: magnetic or optical disks, electrically erasable programmable Read-only memory, erasable programmable read-only memory, static ready-access memory, read-only memory, magnetic memory, flash memory, programmable read-only memory.

In an exemplary solution, when the computer device 1200 is implemented as a message sending device, the receiving processor is configured to obtain the message type indication information of the first message; the message type indicated by the message type indication information includes unicast session message, multicast session message or message count synchronization protocol MCSP session message; set the parameter value of the first parameter in the first message according to the message type indication information to generate the third parameter corresponding to the message type indication information. A message; wherein the parameter value of the first parameter corresponding to different message types is different; the parameter value of the first parameter is used to indicate whether the first field exists in the first message, and when the first field exists, When it is the first field, the parameter value of the first parameter is also used to indicate the identification type of the field value of the first field; the identification type includes the identification information of the receiving node group of the first message, or the Identification information of the receiving node of the first message.

The process executed by the processor 1201 in the computer device 1200 may refer to the various steps executed by the message sending device in the method shown in any one of the above-mentioned FIG. 4 or FIG. 6 .

In an exemplary solution, when the computer device 1200 is implemented as a message receiving device, the transceiver is used to receive the first message. The processor is configured to parse the first parameter in the first message; and perform the step of obtaining the field value of the first field in the first message according to the parameter value of the first parameter; wherein, The parameter value of the first parameter is set by the message sending device according to the message type indication information of the first message; the message type indicated by the message type indication information includes unicast session message, multicast session message or MCSP session message. ; Different message types correspond to different parameter values of the first parameter; the parameter value of the first parameter is used to indicate whether the first field exists in the first message, and when the first field exists , the parameter value of the first parameter is also used to indicate the identification type of the field value of the first field; the identification type includes the identification information of the receiving node group of the first message, or the first message The identification information of the receiving node.

The process performed by the processor 1201 and/or the transceiver in the computer device 1200 may refer to the various steps performed by the message receiving device in the method shown in either FIG. 5 or FIG. 6 .

Embodiments of the present application also provide a computer-readable storage medium. A computer program is stored in the storage medium. The computer program is loaded and executed by a processor to implement the method shown in Figure 4, Figure 5 or Figure 6. , all or part of the steps performed by the message sending device or the message receiving device.

This application also provides a chip, which is used to run in a computer device, so that the computer device performs all the steps performed by the message sending device or the message receiving device in the method shown in Figure 4, Figure 5 or Figure 6. Or some steps.

The application also provides a computer program product, which computer program product or computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs the method shown in FIG. 4, FIG. 5 or FIG. 6, by the message sending device or the message receiving device. All or part of the steps performed by the device.

This application also provides a computer program, which is executed by the processor of the computer device to implement all or all of the steps executed by the message sending device or the message receiving device in the method shown in FIG. 4, FIG. 5 or FIG. 6. Some steps.

Those skilled in the art should realize that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. Storage media can be any available media that can be accessed by a general purpose or special purpose computer.

The above are only exemplary embodiments of the present application and are not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the protection of the present application. within the range.

Claims

A message processing method, characterized in that the method is executed by a message sending device, and the method includes:

Obtain message type indication information; the message type indicated by the message type indication information includes unicast session message, multicast session message or message count synchronization protocol MCSP session message;

Set the parameter value of the first parameter in the first message according to the message type indication information to generate the first message corresponding to the message type indication information;

Wherein, the parameter value of the first parameter corresponding to different message types is different; the parameter value of the first parameter is used to indicate whether the first field exists in the first message, and when the first field exists When, the parameter value of the first parameter is also used to indicate the identification type of the field value of the first field; the identification type includes the identification information of the receiving node group of the first message, or the first Identification information of the receiving node of the message.
The method of claim 1, wherein the parameter value of the first parameter in the first message is set according to the message type indication information to generate the first parameter value corresponding to the message type indication information. Messages, including:

When the message type indicated by the message type indication information is an MCSP session message, the first parameter in the first message is set to the first parameter value, and the first field in the first message is set to the first parameter value. a field value to generate the first message;

Wherein, the first parameter value is used to indicate the presence of the first field in the first message, and the field value of the first field is the identification information of the receiving node of the first message.
The method according to claim 2, characterized in that the message type indication information includes session type identification information.
The method according to claim 3, characterized in that, when the message type indication information indicates that the message type is an MCSP session message, setting the first parameter in the first message to a first parameter value, and setting the first field in the first message to the first field value to generate the first message, including:

When the session type identification information is an MCSP session identification, setting the first parameter in the first message to a first parameter value, and setting the first field in the first message to a first field value, to generate the first message.
The method according to claim 3, characterized in that, when the message type indication information indicates that the message type is a message count synchronization protocol MCSP session message, the first parameter in the first message is set to the first A parameter value, and setting the first field in the first message to the first field value to generate the first message, including:

When the session type identification information is a multicast session identification, obtain the message type identification information of the first message; the message type identification information is used to identify the message type of the first message;

When the message type identification information satisfies the first condition, setting the first parameter in the first message to a first parameter value, and setting the first field in the first message to a first field value, to generate the first message.
The method according to claim 5, characterized in that the message type indication information includes at least one of the following information:

Protocol identification information, and, opcodes.
The method according to claim 6, characterized in that, in the case where the message type indication information includes the protocol identification information, the first condition includes:

The protocol identification information indicates that the protocol corresponding to the first message is a secure channel protocol.
The method of claim 6, wherein when the message type indication information includes the operation code, the first condition includes:

The operation code indicates that the first message is an MCSP session message.
The method of claim 2, wherein the message type indication information includes session context information.
The method according to claim 9, characterized in that, when the message type indicated by the message type indication information is an MCSP session message, setting the first parameter in the first message to a first parameter value , and set the first field in the first message to the first field value to generate the first message, including:

When the session context information is an MCSP session context, the first parameter in the first message is set to a first parameter value, and the first field in the first message is set to a first field value, so as to Generate the first message.
The method of claim 10, further comprising:

When the session context information is an MCSP session context, the session type identification information of the first message is set to a multicast session identification.
The method according to any one of claims 2 to 11, characterized in that the first parameter is the DSIZ label in the first message; the first field is the destination node identification field in the first message. ;

The first parameter value is 1, and the first field value is the node identifier of the message recipient of the first message.
The method according to any one of claims 1 to 12, characterized in that the method further includes:

When the message type indicated by the message type indication information is an MCSP session message, the second parameter in the first message is set to a second parameter value, and the second field in the first message is set to a second parameter value. Two field values;

Wherein, the second parameter value is used to indicate the presence of the second field in the first message, and the field value of the second field is the identification information of the sending node of the first message.
The method according to claim 13, characterized in that the second parameter is the S tag of the first message; the second field is the source node identification field in the first message;

The second parameter value is 1, and the second field value is the node identifier of the message sending device.
The method according to any one of claims 1 to 14, characterized in that the method further includes:

When the message type indicated by the message type indication information is a multicast session message, the first parameter in the first message is set to a third parameter value, and the first field in the first message is set to The third field value;

Wherein, the third parameter value is used to indicate the presence of the first field in the first message, and the field value of the first field is the identification information of the node group to which the message recipient of the first message belongs. .
The method according to claim 15, characterized in that the first parameter is the DSIZ label in the first message; the first field is the destination node identification field in the first message;

The third parameter value is 2, and the third field value is the group identifier of the message recipient of the first message.
A message processing method, characterized in that the method is executed by a message receiving device, and the method includes:

receive the first message;

Parse the first parameter in the first message;

According to the parameter value of the first parameter, perform the step of obtaining the field value of the first field in the first message;

Wherein, the parameter value of the first parameter is set by the message sending device according to the message type indication information of the first message; the message type indicated by the message type indication information includes unicast session message, multicast session message or MCSP Conversation message; different message types correspond to different parameter values of the first parameter; the parameter value of the first parameter is used to indicate whether the first field exists in the first message, and, when the first field exists, field, the parameter value of the first parameter is also used to indicate the identification type of the field value of the first field; the identification type includes the identification information of the receiving node group of the first message, or the third Identification information of the receiving node of a message.
The method according to claim 17, wherein the step of obtaining the field value of the first field in the first message according to the parameter value of the first parameter includes:

When the parameter value of the first parameter is the first parameter value, obtain the first field value of the first field in the first message as the identification information of the receiving node of the first message;

Wherein, the first parameter value and the first field value are set by the message sending device when the message type of the first message is an MCSP session message.
The method according to claim 18, characterized in that the first parameter is the DSIZ label in the first message; the first field is the destination node identification field in the first message;

The first parameter value is 1, and the first field value is the node ID of the message recipient of the first message.
The method according to any one of claims 17 to 19, wherein the step of obtaining the field value of the first field in the first message according to the parameter value of the first parameter includes:

When the parameter value of the first parameter is a third parameter value, obtain the third field value of the first field in the first message as the node group to which the message recipient of the first message belongs. identification information;

Wherein, the third parameter value and the third field value are set by the message sending device when the message type of the first message is a multicast session message.
The method of claim 20, wherein the first parameter is a DSIZ label in the first message; the first field is a destination node identification field in the first message;

The third parameter value is 2, and the third field value is the group identifier of the message recipient of the first message.
A message processing device, characterized in that the device includes:

An acquisition module, configured to acquire message type indication information; the message types indicated by the message type indication information include unicast session messages, multicast session messages or message count synchronization protocol MCSP session messages;

A generating module configured to set the parameter value of the first parameter in the first message according to the message type indication information, so as to generate the first message corresponding to the message type indication information;

Wherein, the parameter value of the first parameter corresponding to different message types is different; the parameter value of the first parameter is used to indicate whether the first field exists in the first message, and when the first field exists When, the parameter value of the first parameter is also used to indicate the identification type of the field value of the first field; the identification type includes the identification information of the receiving node group of the first message, or the first Identification information of the receiving node of the message.
The method according to claim 22, characterized in that:

The generating module is configured to, when the message type indicated by the message type indication information is an MCSP session message, set the first parameter in the first message to a first parameter value, and set the first message The first field in is the first field value to generate the first message;

Wherein, the first parameter value is used to indicate the presence of the first field in the first message, and the field value of the first field is the identification information of the receiving node of the first message.
The device according to claim 23, wherein the message type indication information includes session type identification information.
The device according to claim 24, wherein the generating module is configured to set the first parameter in the first message to be the first parameter when the session type identification information is an MCSP session identification. value, and set the first field in the first message to the first field value to generate the first message.
The device according to claim 24, characterized in that the generating module is used to:

When the session type identification information is a multicast session identification, obtain the message type identification information of the first message; the message type identification information is used to assist in identifying the message type of the first message;

When the message type identification information satisfies the first condition, setting the first parameter in the first message to a first parameter value, and setting the first field in the first message to a first field value, to generate the first message.
The device according to claim 26, wherein the message type indication information includes at least one of the following information:

Protocol identification information, and, opcodes.
The device according to claim 27, wherein when the message type indication information includes the protocol identification information, the first condition includes:

The protocol identification information indicates that the protocol corresponding to the first message is a secure channel protocol.
The device according to claim 27, wherein when the message type indication information includes the operation code, the first condition includes:

The operation code indicates that the first message is an MCSP session message.
The apparatus according to claim 23, wherein the message type indication information includes session context information.
The device according to claim 30, wherein the generating module is configured to set the first parameter in the first message to a first parameter value when the session context information is an MCSP session context. , and set the first field in the first message to the first field value to generate the first message.
The device of claim 31, further comprising:

A setting module configured to set the session type identification information of the first message to a multicast session identification when the session context information is an MCSP session context.
The device according to any one of claims 23 to 32, characterized in that the first parameter is a DSIZ label in the first message; the first field is a destination node identification field in the first message. ;

The first parameter value is 1, and the first field value is the node ID of the message recipient of the first message.
The device according to any one of claims 22 to 33, characterized in that the generating module is further configured to set the first message when the message type indicated by the message type indication information is an MCSP session message. The second parameter in is the second parameter value, and the second field in the first message is set to the second field value;

Wherein, the second parameter value is used to indicate the presence of the second field in the first message, and the field value of the second field is the identification information of the sending node of the first message.
The device according to claim 34, wherein the second parameter is the S tag in the first message; the second field is the source node identification field in the first message;

The second parameter value is 1, and the second field value is the node ID of the message sending device.
The device according to any one of claims 22 to 35, characterized in that the generating module is further configured to set the first message type when the message type indicated by the message type indication information is a multicast session message. The first parameter in the message is the third parameter value, and the first field in the first message is set to the third field value;

Wherein, the third parameter value is used to indicate the presence of the first field in the first message, and the field value of the first field is the identification information of the node group to which the message recipient of the first message belongs. .
The device according to claim 36, wherein the first parameter is a DSIZ label in the first message; the first field is a destination node identification field in the first message;

The third parameter value is 2, and the third field value is the group identifier of the message recipient of the first message.
A message processing device, characterized in that the device includes:

A receiving module, used to receive the first message;

A parsing module, used to parse the first parameter in the first message;

An obtaining module, configured to perform the step of obtaining the field value of the first field in the first message according to the parameter value of the first parameter;

Wherein, the parameter value of the first parameter is set by the message sending device according to the message type indication information of the first message; the message type indicated by the message type indication information includes unicast session message, multicast session message or MCSP Conversation message; different message types correspond to different parameter values of the first parameter; the parameter value of the first parameter is used to indicate whether the first field exists in the first message, and, when the first field exists, field, the parameter value of the first parameter is also used to indicate the identification type of the field value of the first field; the identification type includes the identification information of the receiving node group of the first message, or the third Identification information of the receiving node of a message.
The method according to claim 38, characterized in that:

The obtaining module is configured to obtain the first field value of the first field in the first message as the first field value of the first message when the parameter value of the first parameter is the first parameter value. Receive the identification information of the node;

Wherein, the first parameter value and the first field value are set by the message sending device when the message type of the first message is an MCSP session message.
The device according to claim 39, wherein the first parameter is a DSIZ label in the first message; the first field is a destination node identification field in the first message;

The first parameter value is 1, and the first field value is the node ID of the message recipient of the first message.
The device according to any one of claims 38 to 40, characterized in that the acquisition module is further configured to obtain the first message in the case where the parameter value of the first parameter is a third parameter value. The third field value of the first field is obtained as the identification information of the node group to which the message recipient of the first message belongs;

Wherein, the third parameter value and the third field value are set by the message sending device when the message type of the first message is a multicast session message.
The device according to claim 41, wherein the first parameter is a DSIZ label in the first message; the first field is a destination node identification field in the first message;

The third parameter value is 2, and the third field value is the group identifier of the message recipient of the first message.
A computer device, characterized in that the computer device includes a processor, a memory and a transceiver;

A computer program is stored in the memory, and the processor executes the computer program, so that the computer device implements the message processing method as described in any one of claims 1 to 21.
A computer-readable storage medium, characterized in that a computer program is stored in the storage medium, and the computer program is used to be executed by a processor to implement the message processing method according to any one of claims 1 to 21.
A chip, characterized in that the chip is used to run in a computer device, so that the computer device executes the message processing method according to any one of claims 1 to 21.
A computer program product, characterized in that the computer program product includes computer instructions, and the computer instructions are stored in a computer-readable storage medium; and a processor of a computer device reads the computer instructions from the computer-readable storage medium. instructions, and execute the computer instructions, so that the computer device executes the message processing method according to any one of claims 1 to 21.
A computer program, characterized in that the computer program is executed by a processor of a computer device to implement the message processing method according to any one of claims 1 to 21.