An MSRP protocol routing method and system under a microservices architecture

Abstract

The present invention provides a method and system for MSRP protocol routing under a microservices architecture, including: Step 1: Initialize the 5G messaging platform and initialize the configuration information of the SIP and MSRP services, where the configuration information includes the OpenSips service address, the MSRP routing service address, the SIP service address, and the MSRP message address; Step 2: Execute MSRP routing, where the MSRP message includes the MSRP message address, and the MSRP message address format includes the MSRP message address prefix, the MSRP routing service address, the INDEX globally incrementing index, the encryption field, and the MSRP message address suffix. Through the above technical solution, the technical problem of correct routing of the stateful service between the SIP signaling and the MSRP media is solved, and the processing efficiency is high, and the security and reliability are high.

Description

Technical Field

[0001] The present invention relates to the technical fields of wireless communication, SIP access, and MSRP protocol, and particularly relates to an MSRP protocol routing method and system under a microservices architecture. Background Art

[0002] In the 5G messaging platform project, 5G text messages are instant messages based on the SIP / IP network, and are divided into Pager mode messages and Large mode messages.

[0003] The delivery process of Pager mode messages is completed through the SIP message method. Pager messages are limited by the size of the SIP message body (1300 bytes) and are suitable for sending and receiving small messages. The delivery process of Large messages is completed through the combination of SIP / MSRP. First, a SIP session is established to negotiate the MSRP transmission path, etc., and then the message transmission process is completed through the MSRP protocol in the data plane.

[0004] Under the cloud-native microservices framework, the 5G messaging platform needs to support horizontal scaling of SIP and MSRP services to achieve message processing capabilities under high traffic. The 5G messaging platform needs to expose gateways to handle SIP access requests and MSRP access requests respectively, and forward the requests by routing.

[0005] OpenSips is a popular load balancing tool for the SIP protocol in the industry. When OpenSips routes call requests sent to a group of destinations, it can record the load situation of each destination and send new call requests to the destination with less load.

[0006] However, there is currently no available routing service for the MSRP protocol service on the market. Based on such a technical background, this application is proposed to implement routing at the data level to solve the current technical gap in this field. Summary of the Invention

[0007] In view of this, the present invention provides a design of an MSRP protocol routing algorithm under a microservices architecture to solve functions such as routing, forwarding, and shunting of MSRP packets.

[0008] According to the first aspect of the present invention, there is provided an MSRP protocol routing method under a microservice architecture, characterized in that it includes: Step 1: Initialize the 5G message platform, and initialize the configuration information of the SIP and MSRP services, where the configuration information includes the OpenSips service address, the MSRP routing service address, the SIP service address, and the MSRP message address; Step 2: Execute MSRP routing, where the MSRP message includes the MSRP message address, and the MSRP message address format includes the MSRP message address prefix, the MSRP routing service address, the INDEX globally incrementing index, the encryption field, and the MSRP message address suffix. When the above method is applied to the uplink, Step 2 further includes: Step 2.1a: Establish a SIP signaling channel and negotiate data interaction information; Step 2.2a: The SIP service generates the MSRP message address according to the MSRP message address format of Step 2; Step 2.3a: Confirm that the signaling channel is successfully established and return the negotiated MSRP address; Step 2.4a: The terminal initiates an MSRP data request; Step 2.5a: Parse the MSRP message address; Step 2.6a: Perform routing and forwarding according to the MSRP message address; Step 2.7a: The data channel is successfully established; Step 2.8a: The MSRP service saves the received message data; Step 2.9a: Add the MSRP interaction result to the queue and terminate the SIP session.

[0009] Further, Step 1 includes: starting the SIP service and the MSRP service.

[0010] Further, when the above method is applied to the downlink, Step 2 further includes: Step 2.1b: Establish a SIP signaling channel and negotiate data interaction information; Step 2.2b: The SIP service generates the MSRP message address according to the MSRP message address format of Step 2; Step 2.3b: Confirm that the signaling channel is successfully established and return the negotiated MSRP address; Step 2.4b: The terminal initiates an MSRP Send request and establishes an MSRP link; Step 2.5b: Parse the MSRP message address; Step 2.6b: Perform routing and forwarding according to the MSRP message address; Step 2.7b: The data channel is successfully established; Step 2.8b: The MSRP service reads the message data stored in the database in Step 2.8a, sends an MSRP Send to the terminal, and notifies the SIP service that the MSRP message interaction is over; Step 2.9b: Add the MSRP interaction result to the queue and terminate the SIP session.

[0011] Further, the method includes that the terminal includes at least one terminal; the encryption field includes the MSRP message address and port MSRPHex within the platform, and a 16-bit MD5 value calculated based on the INDEX field, the MSRPHex, and an internal key.

[0012] According to a second aspect of the present invention, there is provided an MSRP protocol routing system under a microservices architecture, characterized by comprising: an initialization module: initializing the 5G message platform, and initializing configuration information for SIP and MSRP services, where the configuration information includes the OpenSips service address, the MSRP routing service address, the SIP service address, and the MSRP message address; an MSRP routing module: performing MSRP routing, where the MSRP message includes the MSRP message address, and the MSRP message address format includes the MSRP message address prefix, the MSRP routing service address, the INDEX global increment index, the encryption field, and the MSRP message address suffix. When applied to the uplink, the MSRP routing module further includes: Module 2.1a: establishing a SIP signaling channel and negotiating data interaction information; Module 2.2a: the SIP service generating the MSRP message address according to the MSRP message address format in step 2; Module 2.3a: confirming the successful establishment of the signaling channel and returning the negotiated MSRP address; Module 2.4a: the terminal initiating an MSRP data request; Module 2.5a: parsing the MSRP message address; Module 2.6a: performing routing and forwarding according to the MSRP message address; Module 2.7a: successfully establishing a data channel; Module 2.8a: the MSRP service saving the received message data; Module 2.9a: adding the MSRP interaction result to a queue and terminating the SIP session.

[0013] Further, the initialization module includes: starting the SIP service and the MSRP service.

[0014] Further, when it is applied to the downlink, the MSRP routing module further includes: Module 2.1b: Establish an SIP signaling channel and negotiate data interaction information; Module 2.2b: The SIP service generates the MSRP message address according to the MSRP message address format in Step 2; Module 2.3b: Confirm that the signaling channel is successfully established and return the negotiated MSRP address; Module 2.4b: The terminal initiates an MSRP Send request to establish an MSRP link; Module 2.5b: Parse the MSRP message address; Module 2.6b: Perform routing and forwarding according to the MSRP message address; Module 2.7b: The data channel is successfully established; Module 2.8b: The MSRP service reads the message data stored in the database in Step 2.8a, sends an MSRP Send to the terminal, and notifies the SIP service that the MSRP message interaction is ended; Module 2.9b: Add the MSRP interaction result to the queue and terminate the SIP session.

[0015] Further, the terminal of the system includes at least one terminal; the encryption field includes the MSRP message address and port MSRPHex within the platform and the 16-bit MD5 value calculated according to the INDEX field, the MSRPHex, and the internal key. The execution entity calls the event collection interface according to the API request to generate an event.

[0016] The advantages of the present invention over the prior art are as follows:

[0017] Aiming at the defects of MSRP routing in the prior art, the present invention is implemented based on the load balancing function of the OpenSips tool. When negotiating through SIP signaling, the MSRP routing address and the internal service address are simultaneously embedded in the MSRP path. When an external node initiates an MSRP request, it carries both the MSRP routing address and the address information of the internal MSRP service. In this way, the MSRP routing service can perform routing and forwarding based on the internal service address in the path of the message, perfectly solving the difficulty of correct routing for multiple stateful services in the cloud native environment. Secondly, a unique global incrementing index and MSRP address information are added to the MSRP negotiation address, ensuring that each address is processed by one MSRP service and the uniqueness of the message. Thirdly, the present application encrypts and obfuscates the internal service address to prevent the external from knowing the internal address and blocking illegal requests.

[0018] The above description is only an overview of the technical solution of the present invention. In order to be able to understand the technical means of the present invention more clearly and implement it according to the content of the specification, the following describes in detail with the preferred embodiments of the present invention in conjunction with the accompanying drawings. Description of the Drawings

[0019] The accompanying drawings, which form a part of this invention, are used to provide a further understanding of this invention. The schematic embodiments of this invention and their descriptions are used to explain this invention and shall not unduly limit this invention. In the drawings:

[0020] Figure 1 A method flow chart of this invention is shown;

[0021] Figure 2 A system structure diagram of this invention is shown;

[0022] Figure 3 Another method flow chart of this invention is shown;

[0023] Figure 4 An example of an MSRP message of this invention is shown. Detailed implementation manners

[0024] To make the objectives, technical solutions and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below in conjunction with specific embodiments of this invention and the corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this invention, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of this invention without creative efforts shall fall within the scope of protection of this invention.

[0025] First, in combination with Figure 1 describe the process of this invention. As Figure 1 shown, a method for routing the MSRP protocol under a microservice architecture is characterized by including: Step 1: Initialize the 5G message platform, and initialize the configuration information of the SIP and MSRP services, where the configuration information includes the OpenSips service address, the MSRP routing service address, the SIP service address, and the MSRP message address; Step 2: Execute MSRP routing, where the MSRP message includes the MSRP message address, and the MSRP message address format includes the MSRP message address prefix, the MSRP routing service address, the INDEX globally incrementing index, the encryption field, and the MSRP message address suffix.

[0026] Next, in combination with Figure 3 describe another process of this invention. As Figure 3 shown, this invention provides a method for routing the MSRP protocol under a microservice architecture, including the following steps:

[0027] 1. Routing algorithm

[0028] In the 5G message platform project, SIP service and MSRP service jointly implement the transmission of large messages, where SIP service is responsible for signaling and MSRP is responsible for the transmission of media data. Because for a session of a large message, SIP service and MSRP service need to be implemented together, and both services are stateful. In deployment, usually the number of instances of the two is the same and they are bound to each other, so that it is easy to achieve matching interaction of signaling and data.

[0029] Considering that there is a state between SIP and MSRP services, the message request routed to the SIP service, the corresponding media message needs to be routed to the corresponding MSRP service. Because OpenSips implements signaling load balancing and routing. If it is possible to route to the SIP signaling numbered n, and also to the MSRP service numbered n, then accurate routing and forwarding of the MSRP service can be achieved, while also ensuring the matching relationship between the SIP service and the MSRP service.

[0030] It just so happens that when the SIP service is conducting signaling negotiation with the terminal, the SIP service needs to embed the routing address and the internal address of the MSRP internal service instance into the MSRP message path. If we write the corresponding MSRP message address into the message path during SIP negotiation, then when the MSRP request comes, it can be routed and forwarded according to the path in the message.

[0031] Based on this idea, an MSRP routing service is developed to implement the routing of the data part.

[0032] 2. MSRP message definition

[0033] Figure 4 For example, each MSRP message has a To-Path and From-Path field. These two fields represent the addresses of the services at both ends of the MSRP session. When the terminal initiates a SIP signaling session, the terminal fills in the local address as From-Path, and the SIP service fills in the To-Path address. These two addresses are used as the negotiation address in the SIP message. The UE terminal will use this address to transmit the MSRP message. The MSRP routing service will be distributed according to the address information in the message. We need to define an address information structure that can meet the routing distribution.

[0034] 3. MSRP routing algorithm address format definition

[0035] According to the forwarding requirements of the MSRP routing algorithm, the following format is defined:

[0036] msrp: / / msrpRouter / Index-MSRPHexAndMD5;tcp

[0037] 3.1) Definitions of each part of the message address:

[0038] "msrp: / / ": Message address prefix;

[0039] ";tcp": Message address suffix;

[0040] msrpRouter: Address of the MSRP routing service. This address is the external address through which the terminal can access the message platform, e.g., 10.23.34.120:9000;

[0041] Index, a globally incrementing index string, 16 bits in total. The globally incrementing index ensures the uniqueness and accuracy of each MSRP session. E.g., 0000001234567890;

[0042] MSRPHexAndMD5, a string composed of two parts spliced together. The first part is the MSRP message address and port within the platform, and the second part is a 16-bit MD5 value calculated based on Index, MSRPHex, and the internal key. To ensure the security of the internal address information, the MSRP address information is converted into a hexadecimal code and interleaved with the MD5 string.

[0043] 3.2) Definitions of MSRP message address and port

[0044] MSRP address e.g., 192.168.0.30:6070.

[0045] Converted to hexadecimal string: c0a8001e17b6

[0046] 3.3) MD5 value calculation method

[0047] The 5G message platform uses the internal key to implement MD5 encryption. E.g., the key is: kmdne.

[0048] Calculate the MD5 value, md5(Index - MSRPAddr - key)

[0049] md5(0000001234567890 - 192.168.0.30:6070, kmdne) = f239dee25f1c3d4b

[0050] 3.4) Definition of the interleaving rule for MSRP address code and MD5, MSRPHexAndMD5

[0051] Split the address code into two parts: IP address and port; split the 16-bit MD5 into three parts: the first 6 bits, the middle 4 bits, and the last 6 bits; combine the address code and the MD5 string into a new string: the first 6 bits of MD5 + IP address + the middle 4 bits of MD5 + port of address + the last 6 bits of MD5.

[0052] Then the above MSRP address can be combined into a new string: 9bbbcfc0a8001e2d8717b600fd9c

[0053] 3.5) The address prefix "msrp: / / " and the suffix ";tcp" are in the MSRP message format and remain unchanged.

[0054] 3.6) The finally generated msrp message address string is:

[0055] msrp: / / 10.23.34.120:9000 / 0000001234567890-9bbbcfc0a8001e2d8717b600fd9c;tcp

[0056] 4. MSRP Routing and Forwarding Process

[0057] The MSRP receiving service and the sending service have similar functions. The following takes the receiving service as an example for explanation.

[0058] 4.1) In the initialization stage of the 5G messaging platform, the SIP and MSRP service initialization configuration information, including the address of the OPENSIPS service, the MSRP routing service address, the SIP service address, and the MSRP message address, etc.;

[0059] Start the SIP service and attempt to establish a long TCP connection with an idle MSRP service and bind to it, and the two exchange their respective information;

[0060] Start the MSRP service, obtain the address information of the running SIP service in the platform cluster, and wait for the TCP connection request from the SIP service. Once a SIP service attempts to establish a TCP connection with it, accept and maintain a long connection with the SIP;

[0061] The 5G messaging platform exposes an MSRP routing service externally. All MSRP services establish long TCP connections with the MSRP routing service through TCP connections. Once there is an external MSRP request coming to the MSRP routing service, the MSRP routing service will perform matching and forwarding according to the service address information in the MSRP message.

[0062] 4.2) MSRP Routing Workflow (Upstream) (See specifically Figure 3 )

[0063] Step 4.2.1): The terminals UE A and UE B respectively initiate SIP Invite to the OpenSips load balancer. OpenSips distributes new SIP services to receive this Invite according to the load conditions of each SIP service, realizes the forwarding of signaling, and establishes a SIP session; among them, the SIP request of UE A is distributed to SIP service 1; the SIP request of UE B is distributed to SIP service n.

[0064] Purpose: To establish a SIP signaling channel, negotiate information for data interaction, etc.

[0065] Step 4.2.2): The SIP service generates an MSRP message address in a custom format as follows: msrp: / / msrpRouter / Index-MSRPHexAndMD5; tcp

[0066] The SIP request of UE A is routed to SIP service 1:

[0067] The global index is: 0000000000000001, and the address and port of the corresponding MSRP service 1 are: 192.168.0.10:30111;

[0068] The negotiated MSRP address generated is:

[0069] msrp: / / 10.23.34.120:9000 / 0000000000000001-631ecbc0a8000a3261759f4ee299; tcp The SIP request of UE B is routed to SIP service n:

[0070] The global index is: 0000000000000002, and the address and port of the corresponding MSRP service 1 are: 192.168.0.11:30112;

[0071] The generated negotiated MSRP address is:

[0072] msrp: / / 10.23.34.120:9000 / 0000000000000002-f4e6e6c0a8000badd375a0260850; tcp

[0073] Purpose: To negotiate and generate a unique MSRP message address information, which is one of the main algorithms of this algorithm.

[0074] Step 4.2.3): The SIP service responds with 200 OK and returns the negotiated MSRP address.

[0075] Purpose: To confirm the successful establishment of a signaling channel and return the negotiated MSRP address.

[0076] Step 4.2.4): The terminal UE sends an MSRP Send request to the MSRP router;

[0077] The specific message is as follows:

[0078] UE A:

[0079] MSRP a786hjs2 SEND

[0080] To-Path: msrp: / / 10.23.34.120:9000 / 0000000000000001-631ecbc0a8000a3261759f4ee299;tcp

[0081] From-Path: msrp: / / 10.190.123.90:5060 / kjhd37s2s20w2a;tcp

[0082] Message-ID: 87652491

[0083] Byte-Range: 1-25 / 25

[0084] Content-Type: text / plain

[0085] Hey Bob, are you there?

[0086] -------a786hjs2$

[0087] UE B:

[0088] MSRP hjsa7862 SEND

[0089] To-Path: msrp: / / 10.23.34.120:9000 / 0000000000000002-f4e6e6c0a8000badd375a0260850;tcp

[0090] From-Path: msrp: / / 10.190.123.91:5060 / kjhd37s2s20w2a;tcp

[0091] Message-ID: 87652492

[0092] Byte-Range: 1-26 / 26

[0093] Content-Type:text / plain

[0094] Hey Mary,are you there?

[0095] -------hjsa7862$

[0096] Purpose: The terminal initiates an MSRP data request.

[0097] Step 4.2.5): After the MSRP route receives the MSRP request, it reads the information in the To-Path field of the MSRP message, and according to the custom message address format above, extracts and parses the information to obtain the globally incrementing index, MSRP address and port, and MD5 value. Then, it calculates the MD5 value based on the extracted global index and MSRP address port, and compares it with the MD5 value extracted from the message. If they are inconsistent, it is considered an illegal request and will not be processed; if they are consistent, it is considered a legal MSRP request and proceeds to the next step of forwarding.

[0098] Purpose: Parse the MSRP message address.

[0099] Step 4.2.6): The MSRP route service forwards this message request to the corresponding MSRP service according to the IP address and port in the MSRP address information; the MSRP request of UE A will be forwarded to MSRP service 1, and the MSRP request of UE B will be forwarded to MSRP service n.

[0100] Purpose: Perform routing and forwarding according to the MSRP message address.

[0101] Step 4.2.7): The MSRP service responds with 200 OK.

[0102] Purpose: The data channel is successfully established.

[0103] Step 4.2.8): The MSRP service saves the message content to the database and notifies the SIP service that the data reception is complete.

[0104] Purpose: The MSRP service saves the received message content.

[0105] Step 4.2.9): The SIP service adds the relevant information of the stored message to the Kafka queue and sends BYE to end the SIP session.

[0106] Purpose: Add the MSRP interaction result to the queue and terminate the SIP session.

[0107] 4.3) MSRP Routing Workflow (Downlink)

[0108] The downlink process is mostly the same as the uplink process. The main difference is that during the uplink, the terminal sends data to the 5G messaging platform, while during the downlink, the 5G messaging platform sends data to the terminal.

[0109] The different steps in the process are:

[0110] Step 4.3.4): The terminal UE initiates an MSRP Send request (empty message) to the MSRP router in order to establish an MSRP link;

[0111] Step 4.3.8): The MSRP service reads the sent data stored in the upstream phase in the database, sends MSRP Send to the terminal, and notifies the SIP service. The MSRP message interaction ends.

[0112] Through this application, based on the load balancing function of the OpenSips tool in the industry, the MSRP routing address and the internal service address are embedded in the MSRP path at the same time during SIP signaling negotiation. When the external node initiates an MSRP request, it carries the MSRP routing address and the address information of the internal MSRP service at the same time. In this way, the MSRP routing service can perform routing forwarding based on the internal service address of the path in the message, which perfectly solves the difficulty of achieving correct routing for multiple stateful services in a cloud-native environment. Secondly, a unique global incremental index and MSRP address information are added to the MSRP negotiation address to ensure that each address is processed by an MSRP service and the uniqueness of the message. Third, this application encrypts and obfuscates the internal service address to prevent the external from knowing the internal address and prevent illegal requests. In addition, this application has been deployed in China Telecom's 5G messaging system and has achieved the expected technical effects.

[0113] According to the method proposed in the present application, there are at least the following significant technical effects: 1) The present invention creatively proposes a new routing algorithm for the MSRP protocol. The algorithm is combined with the OpenSips service implementation commonly used in the industry, and the SIP protocol negotiation address is used as the basis for routing distribution, making full use of the SIP protocol and OpenSips load balancing function, perfectly solving the problem of stateful connection between SIP signaling and MSRP media. 2) A unique global incremental index and MSRP address information are added to the MSRP negotiation address to ensure that each address is processed by an MSRP service and the uniqueness of the message. 3) The routing algorithm service is small in size, easy to deploy, and has high processing efficiency. 4) According to the protocol specification, MSRP messages are all transmitted in plain text, and the invention takes into account the security of the negotiation address, and the MSRP internal address information is re-arranged and MD5 encrypted to ensure the security and reliability of the algorithm and communication.

[0114] It should be noted that, without conflict, the embodiments in the present invention and the features in the embodiments may be combined with each other.

[0115] As mentioned above, the above are only the preferred embodiments of the present invention, and do not impose any formal restrictions on the present invention. Any simple modifications, equivalent changes and modifications made to the above embodiments based on the technical essence of the present invention still fall within the scope of the technical solutions of the present invention.

Claims

1. A routing method for the MSRP protocol under a microservices architecture, characterized in that, including: Step 1: Initialize the 5G messaging platform, and initialize the configuration information of SIP and MSRP services, where the configuration information includes the OpenSips service address, the MSRP routing service address, the SIP service address, and the MSRP message address; Step 2: Execute MSRP routing. Among them, the MSRP message includes the MSRP message address, and the MSRP message address format includes the MSRP message address prefix, the MSRP routing service address, the INDEX global increment index, the encryption field, and the MSRP message address suffix; The Step 2 further includes: Step 2.1a: Establish a SIP signaling channel and negotiate data interaction information; Step 2.2a: The SIP service generates the MSRP message address according to the MSRP message address format in Step 2; Step 2.3a: Confirm that the signaling channel is successfully established and return the negotiated MSRP address; Step 2.4a: The terminal initiates an MSRP data request; Step 2.5a: Parse the MSRP message address; Step 2.6a: Perform routing and forwarding according to the MSRP message address; Step 2.7a: The data channel is successfully established; Step 2.8a: The MSRP service saves the received message data; Step 2.9a: Add the MSRP interaction result to the queue and terminate the SIP session.

2. The method according to claim 1, characterized in that The Step 1 further includes: Start the SIP service and the MSRP service.

3. According to the method described in claim 1 or 2, when it is applied to the downlink, the Step 2 further includes: Step 2.1b: Establish a SIP signaling channel and negotiate data interaction information; Step 2.2b: The SIP service generates the MSRP message address according to the MSRP message address format in Step 2; Step 2.3b: Confirm that the signaling channel is successfully established and return the negotiated MSRP address; Step 2.4b: The terminal initiates an MSRP Send request to establish an MSRP link; Step 2.5b: Parse the MSRP message address; Step 2.6b: Perform routing and forwarding according to the MSRP message address; Step 2.7b: The data channel is successfully established; Step 2.8b: The MSRP service reads the message data stored in the database in Step 2.8a, sends an MSRP Send to the terminal, and notifies the SIP service that the MSRP message interaction is over; Step 2.9b: Add the MSRP interaction result to the queue and terminate the SIP session.

4. According to the method described in claim 2, it further includes: The number of the terminals is at least one; The encryption field includes the MSRP message address and port MSRPHex within the platform, and a 16-bit MD5 value calculated according to the INDEX field, the MSRPHex, and the internal key.

5. A MSRP protocol routing system under a microservices architecture, characterized in that, including: Initialization module: Initialize the 5G messaging platform, and initialize the configuration information of SIP and MSRP services, where the configuration information includes the OpenSips service address, the MSRP routing service address, the SIP service address, and the MSRP message address; MSRP Routing Module: Performs MSRP routing. The MSRP message includes an MSRP message address, and the MSRP message address format includes the MSRP message address prefix, MSRP routing service address, INDEX global increment index, encryption field, and MSRP message address suffix; When it is applied to the uplink, the MSRP routing module further includes: Module 2.1a: Establishes a SIP signaling channel and negotiates data interaction information; Module 2.2a: The SIP service generates the MSRP message address according to the MSRP message address format of the MSRP routing module; Module 2.3a: Confirms that the signaling channel is successfully established and returns the negotiated MSRP address; Module 2.4a: The terminal initiates an MSRP data request; Module 2.5a: Parses the MSRP message address; Module 2.6a: Performs routing and forwarding according to the MSRP message address; Module 2.7a: Successfully establishes a data channel; Module 2.8a: The MSRP service saves the received message data; Module 2.9a: Adds the MSRP interaction result to the queue and terminates the SIP session.

6. The system according to claim 5, wherein the initialization module further includes: Starts the SIP service and the MSRP service.

7. The system according to claim 6, when it is applied to the downlink, the MSRP routing module further includes: Module 2.1b: Establishes a SIP signaling channel and negotiates data interaction information; Module 2.2b: The SIP service generates the MSRP message address according to the MSRP message address format of the MSRP routing module; Module 2.3b: Confirms that the signaling channel is successfully established and returns the negotiated MSRP address; Module 2.4b: The terminal initiates an MSRP Send request to establish an MSRP link; Module 2.5b: Parses the MSRP message address; Module 2.6b: Performs routing and forwarding according to the MSRP message address; Module 2.7b: Successfully establishes a data channel; Module 2.8b: The MSRP service reads the message data stored by module 2.8a in the database, sends an MSRP Send to the terminal, and notifies the SIP service that the MSRP message interaction is over; Module 2.9b: Adds the MSRP interaction result to the queue and terminates the SIP session.

8. The system according to claim 7, which further includes: The number of the terminals is at least one; The encryption field includes the MSRP message address and port MSRPHex within the platform and a 16-bit MD5 value calculated according to the INDEX field, the MSRPHex, and the internal key; According to the API request, call the event collection interface to generate an event.

Images