Message processing, sending method, terminal, communication equipment and computer storage medium
By configuring different network interfaces in the terminal and including network slice identifiers in the packets, the communication interruption caused by network slice IP address conflicts is solved, ensuring the normal operation of the terminal in 5G communication and improving the user experience.
Patent Information
- Application Number
- CN202011439030.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-12-07
- Publication Date
- 2024-11-01
- Estimated Expiration
- 2040-12-07
AI Technical Summary
In 5G communication, the IP address conflict of network slices causes the terminal to be unable to conduct network communication normally, affecting the commercial process of network slices.
When the IP address of the first network slice applied by the terminal and the second network slice that has been connected to the same, different network interfaces are configured and the network slice identifier is included in the message, and the message is distributed to the corresponding network interface according to the identifier. , ensure that communication is carried out normally.
Even if IP address conflict occurs, the terminal can still conduct network communication normally, improve user experience, and avoid communication interruption caused by IP address conflict.
Smart Images

Figure CN114666304B_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present invention relate to but are not limited to the field of mobile communications, and specifically, relate to but are not limited to message processing, sending methods, terminals, communication equipment and computer storage media. Background Art
[0002] Network slicing is a way of networking on demand. In 5G communications, network connection features that can adapt to the needs of different fields will be provided to realize on-demand network supply. In related technologies, a terminal supports simultaneous access to multiple network slices (for example, the 3GPP (3rd Generation Partnership Project) protocol defines access to up to 8 network slices). The IP address of each network slice may be independently allocated, and the allocation of IP addresses may not be controlled by the operator but by the company that purchases the slice. In some cases, IP address conflicts may occur. Once a network slice IP address conflict occurs, the terminal will not be able to use the desired network slice, which will lead to a large number of complaints and may even affect the commercialization process of network slicing. Summary of the invention
[0003] The message processing and sending methods, terminals, communication equipment and computer storage media provided by the embodiments of the present invention mainly solve the technical problem in the related technology that after a conflict occurs in the IP address of the network slice, the terminal cannot perform normal network communication.
[0004] In order to solve the above technical problems, an embodiment of the present invention provides a message processing method, which is applied to a terminal, including:
[0005] When the IP address of the first network slice applied for by the terminal is the same as the IP address of the second network slice that has been accessed, access the first network slice, and configure a network interface for the first network slice that is different from the network interface of the second network slice;
[0006] Receive a first message sent by a network side, where the first message includes a network slice identifier, and the network slice identifier corresponds to the first network slice or the second network slice;
[0007] Distribute the first message to the network interface configured by the corresponding network slice according to the network slice identifier.
[0008] The embodiment of the present invention further provides a message sending method, which is applied to a network side device, including:
[0009] Fill in a network slice identifier in a first message sent to the terminal, where the network slice identifier corresponds to a first network slice or a second network slice currently accessed by the terminal, and the first network slice and the second network slice have the same IP address;
[0010] Send the first message to the terminal.
[0011] An embodiment of the present invention further provides a terminal, including a processor, a memory and a communication bus;
[0012] The communication bus is used to realize the connection and communication between the processor and the memory;
[0013] The processor is used to execute one or more computer programs stored in the memory to implement the steps of the message processing method as described above.
[0014] An embodiment of the present invention further provides a communication device, which is arranged on a network side and includes a processor, a memory and a communication bus;
[0015] The communication bus is used to realize the connection and communication between the processor and the memory;
[0016] The processor is used to execute one or more computer programs stored in the memory to implement the steps of the message sending method as described above.
[0017] An embodiment of the present invention also provides a computer storage medium, which stores one or more programs. The one or more programs can be executed by one or more processors to implement the message processing method as described above or the steps of the message sending method as described above.
[0018] According to the message processing and sending method, terminal, communication equipment and computer storage medium provided by the embodiments of the present invention, after the IP address of the first network slice conflicts with the IP address of the second network slice that has been connected, the first network slice is still accessed and a different network interface is configured for it, and a first message sent by the network side is received, the first message includes a network slice identifier, and the first message is distributed to the corresponding network interface according to the network slice identifier. The network slice identifier uniquely corresponds to the network slice currently connected by the terminal and where the IP address conflict occurs. Therefore, in certain implementation processes, technical effects can be achieved, including but not limited to the ability to complete normal communication according to the network slice identifier when an IP address conflict of the network slice occurs in the terminal, thereby improving user experience.
[0019] Other features and corresponding beneficial effects of the present invention are described in the latter part of the specification, and it should be understood that at least part of the beneficial effects become obvious from the description in the specification of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS
[0020] Figure 1 A schematic diagram of a flow chart of a message processing method according to a first embodiment of the present invention;
[0021] Figure 2 A schematic diagram of an IP message format according to a first embodiment of the present invention;
[0022] Figure 3 This is a schematic diagram of the classification of IP header option fields according to the first embodiment of the present invention;
[0023] Figure 4 This is a schematic diagram of the format of the IP header option field according to the first embodiment of the present invention;
[0024] Figure 5 A schematic diagram of a flow chart of a message sending method according to Embodiment 1 of the present invention;
[0025] Figure 6 This is a schematic diagram of the structure of a terminal according to Embodiment 2 of the present invention;
[0026] Figure 7 For the second embodiment of the present invention Figure 6 The process diagram of the terminal for message processing Figure 1 ;
[0027] Figure 8 For the second embodiment of the present invention Figure 6 The process diagram of the terminal for message processing Figure 2 ;
[0028] Fig. 9 This is a schematic diagram of the structure of a network side device according to Embodiment 2 of the present invention;
[0029] Fig.10 For the second embodiment of the present invention Fig. 9 A schematic diagram of the process of sending a message by a network side device;
[0030] Fig.11 This is a schematic diagram of the structure of a terminal according to Embodiment 3 of the present invention;
[0031] Fig.12 This is a schematic diagram of the structure of a communication device according to Embodiment 3 of the present invention. DETAILED DESCRIPTION
[0032] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the following is a further detailed description of the embodiments of the present invention through specific implementation methods combined with the accompanying drawings. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.
[0033] Embodiment 1:
[0034] In order to solve the problem that IP address conflicts may occur in network slices, resulting in the terminal being unable to use the required network slice. Figure 1 , the method comprising:
[0035] S101. When the IP address of the first network slice applied for by the terminal is the same as the IP address of the second network slice that has been accessed, access the first network slice, and configure a network interface for the first network slice that is different from the network interface of the second network slice;
[0036] After the terminal accesses the operator's network, a network interface will be virtualized, and an IP address assigned by the core network will be configured on this network interface. Generally speaking, the IP addresses assigned to each network interface should be different from each other. In related technologies, if there is a conflict in the IP address of a network slice (that is, there are two or more network interfaces with the same IP address assigned), the terminal will refuse to access the applied network slice. However, in this embodiment, if the terminal applies for the first network slice and is assigned the same IP address as one or more of the second network slices that have been accessed, the terminal still accesses the network slice, and a network interface different from the network interface of the second network slice is configured for the first network slice that is accessed later.
[0037] For example, if network slice A is currently accessed and network interface 0 is configured corresponding to network slice A; if the IP address assigned to the terminal by the network side is the same as the IP address corresponding to network slice A when applying for network slice B, an IP address conflict occurs. If in the related art, the terminal refuses to access network slice B, and in this example, network interface 1 is configured for network slice B, it can be understood that network interface 0 and network interface 1 are different network interfaces.
[0038] It is understandable that after accessing the first network slice, other configurations such as routing rules can be performed to ensure that the first network slice can provide normal services later. For example, in the above example, routing rule 0 is configured for network slice A, and routing rule 1 is configured for network slice B. Of course, due to the different network interfaces, routing rule 0 and routing rule 1 are also different.
[0039] S102. Receive a first message sent by a network side, where the first message includes a network slice identifier, and the network slice identifier corresponds to the first network slice or the second network slice;
[0040] In practical applications, the network slice identifier should specifically correspond uniquely to one of the at least two network slices where the IP address conflict occurs. It should be noted that in this embodiment, the network slice identifier can only correspond uniquely to one network slice, but there may be multiple network slice identifiers corresponding to the same network slice. It should be understood that for network slices where no IP address conflict occurs, the network slice identifier may not be included in the first message sent from the network side, but normal communication can be achieved according to the normal message processing process. This embodiment does not limit whether the message of the network slice where no IP address conflict occurs must carry the network slice identifier.
[0041] In some embodiments, the network slice identifier includes at least one of the following: a protocol data unit session identifier (Protocol Data Unit session id, PDU session id), an application identifier (Application ID, APP ID), and a network interface suffix. It should be noted that the network interface suffix, for example, for network interface 0, the suffix is "0", and the suffix of network interface 1 is "1". It can be understood that the network slice identifier can represent which network slice the first message corresponds to, thereby providing a method other than an IP address to determine which corresponding network interface the first message should be distributed to. It should be noted that the network slice identifier in the first message is added by the network side device before sending the first message.
[0042] S103. Distribute the first message to the network interface configured by the corresponding network slice according to the network slice identifier.
[0043] The network slice identifier corresponds to a network slice that the terminal is currently connected to, so the first message should be distributed to the network interface corresponding to the network slice. As a specific example, if it is determined based on the parsed network slice identifier that the information recorded in the network slice identifier corresponds to network slice A, the first message is distributed to network interface 0 corresponding to network slice A.
[0044] In some implementations, the terminal includes a mapping table of network slice identifiers and network interfaces, and distributing the first message to the corresponding network interface according to the network slice identifier includes:
[0045] The target network interface is queried in the mapping table according to the network slice identifier, and the first message is distributed to the target network interface.
[0046] The mapping table can be dynamically maintained based on the actual network slice of the terminal and the access and configuration of the corresponding network interface. The target network interface is the network interface correctly corresponding to the current first message.
[0047] In some implementations, the message processing method further includes, when sending the second message to the network side, filling in the network slice identifier in the second message sent by the terminal to the network side;
[0048] It should be noted that, in the embodiment of the present invention, the first message refers to the message sent by the network side to the terminal, and the second message refers to the message sent by the terminal to the network side. Even if the above-mentioned network slice identifier is not carried when the second message is sent to the network side, the second message can be delivered to the corresponding network side device normally. However, in this embodiment, it is possible to choose to fill in the network slice identifier in the second message when the terminal sends the second message to the network side, which enables the network side device to easily obtain the relevant information of the network slice. For example, the network side device can directly extract the network slice identifier filled in when the terminal sends the second message to the network side, and directly fill the above-mentioned network slice identifier into the first message when sending the first message to the terminal.
[0049] In some implementations, the network slice identifier is specifically filled into the option field of the IP header of the first message. The option field of the IP header can increase the functionality of the message and can be used to support troubleshooting, measurement, and security measures. Figure 2 , illustrates the format of an IP packet, where the option field in the IP header consists of three parts: option code, option length, and option data. Figure 3 as well as Figure 4 , illustrating the classification of option fields and the format of the option field of the IP header. In this embodiment, the network slice identifier is filled in the option data in the option field of the IP header. It can be understood that whether it is the first message received by the terminal or the second message sent by the terminal, the corresponding network slice identifier can be filled in the option field of the IP header of the above two messages respectively.
[0050] The message processing method of the embodiment of the present invention still allows access to the first network slice with the same IP address as applied for the terminal (that is, a conflict in the IP address of the network slice occurs), and configures a network interface for it that is different from the network interface of the second network slice with the same IP address, receives a first message sent by the network side, and the first message includes a network slice identifier. According to the network slice identifier, the first message is distributed to the corresponding network interface. In some implementation processes, the effect of including but not limited to completing normal communication according to the network slice identifier even if a conflict in the IP address of the network slice occurs in the terminal can be achieved, thereby avoiding the problem that the terminal cannot perform normal network communication after a conflict in the IP address of the network slice occurs, thereby improving the user experience.
[0051] The embodiment of the present invention further provides a message sending method, which is applied to a network side device, and the network side device may be a communication device arranged on the network side, see Figure 5 , the method comprising:
[0052] S201. Fill in a network slice identifier in a first message sent to a terminal, where the network slice identifier corresponds to a first network slice or a second network slice to which the terminal is currently connected. In this embodiment, the first network slice and the second network slice have the same IP address. By filling in the network slice identifier in the first message, after receiving the first message, the terminal can confirm to which network interface the first message should be distributed according to the network slice identifier. Therefore, even when an IP address conflict occurs in the network slice of the terminal, normal communication and interaction conditions can be provided for the terminal.
[0053] It is understandable that the network slice identifier may be filled in the first message sent to the terminal only after a network slice IP address conflict occurs in the terminal. The network slice identifier may also be filled in under any circumstances, and the terminal determines whether it is necessary to determine the distributed network interface based on the network slice identifier. As a more specific example, when the network slice identifier is filled in the second message received from the terminal, it indicates that the terminal may be experiencing a network slice IP address conflict, and thus the network slice identifier is also filled in the first message sent to the terminal, and the network slice corresponding to the network slice identifier corresponds to the same network slice as the network slice identifier in the second message sent by the terminal. It should be noted that one network slice identifier only corresponds to one network slice, but one network slice may be corresponded to by multiple network slice identifiers. Or any other method may be used to determine that the terminal may be experiencing a network slice IP address conflict or directly receive a related request, and then the network slice identifier is filled in the first message sent to the terminal through step S201.
[0054] In some embodiments, the network slice identifier filled in by the network side in the first message sent to the terminal includes at least one of the following: a protocol data unit session identifier (Protocol Data Unit session id, PDUsession id), an application identifier (Application ID, APP ID), and a network interface suffix.
[0055] In some embodiments, the network slice identifier is specifically filled in the option field of the IP header. In this embodiment, the network slice identifier is filled in the option data in the option field of the IP header.
[0056] S202: Send a first message to a terminal.
[0057] After the network slice identifier is filled in the first message, the first message is sent to the terminal. The sending process of the first message can be in any way.
[0058] The message sending method of an embodiment of the present invention is applied to a network side device. By filling in a network slice identifier in a first message sent to a terminal, after the terminal receives the first message, it can confirm, according to the network slice identifier, to which network interface the first message should be distributed. Therefore, in some implementation processes, it can achieve effects including but not limited to providing the terminal with conditions for normal communication and interaction even when an IP address conflict occurs in the network slice of the terminal. This is beneficial to avoiding the problem that the terminal cannot perform normal network communication after an IP address conflict occurs in the network slice, and is beneficial to improving user experience.
[0059] Embodiment 2:
[0060] The following uses some specific processes as examples to further illustrate the message processing method and the message sending method of the embodiments of the present invention.
[0061] See also Figure 6 , this embodiment shows a terminal, and each step of the message processing method of the embodiment of the present invention can be executed by one or more modules in the terminal. In this example, the terminal includes a slice management module 11, a connection management module 12, a monitoring module 13, an IP message filling module 14, a sending module 15, and an IP message parsing module 16. Among them, the slice management module 11 is used to apply for, maintain, and release network slices. The connection management module 12 is used to configure the network interface. In this embodiment, other configurations such as routing rules can also be configured. The monitoring module 13 is used to monitor whether there is a second message sent to the network side, and whether the first message sent by the network side is received. The IP message filling module 14 is used to fill in the network slice identifier in the option field of the IP header of the second message. The sending module 15 is used to send the second message filled with the network slice identifier to the network side. The IP message parsing module 16 is used to parse the network slice identifier from the option field of the IP header of the first message, and distribute the first message to the correct network interface according to the network slice identifier.
[0062] See also Figure 7 In this example, the terminal processes the first message by:
[0063] S301, the slice management module 11 applies for network slice A from the network side, and the network side allocates a corresponding IP address to the terminal;
[0064] Taking the network slice application as an example, the slice management module 11 matches the corresponding S-NSSAI (Single Network Slice Selection Assistance Information) in the URSP (UE Route Selection Policy) rule list according to the DNN (Data Network Name), and then initiates a PDU (Protocol Data Unit) session creation request to the network side, and carries the S-NSSAI in the signaling. The network side replies with the PDU session creation acceptance, completing the PDU session establishment process.
[0065] S302, the connection management module 12 configures the network interface rmnet_data0 and the routing rule route0;
[0066] The network interface rmnet_data0 and routing rule route0 correspond to network slice A.
[0067] S303: The slice management module 11 applies for network slice B from the network side, and the network side allocates the same IP address to the terminal as in step S301;
[0068] S304, the connection management module 12 configures the network interface rmnet_data1 and the routing rule route1;
[0069] The network interface rmnet_data1 and routing rule route1 correspond to network slice B.
[0070] In the related art, when a network slice with the same IP address is found in step S303, network slice B will not be accessed, but in this example, the terminal still accesses the network and configures a network interface and routing rules for it. It can be understood that the network interface rmnet_data1 and routing rule route1 configured in this step are different from the network interface rmnet_data0 and routing rule route0 in step S302.
[0071] S305, the monitoring module 13 monitors whether there is a first message from the network side, if yes, execute step S306, if no, execute step S307;
[0072] S306, the IP message parsing module 16 parses the network slice identifier from the first message, and distributes the first message to the correct network interface according to the network slice identifier;
[0073] Specifically, the IP packet parsing module 16 maintains a mapping table between a network slice identifier and a network interface locally in the terminal. After parsing the network slice identifier, the first packet is distributed to the correct network interface according to the mapping table.
[0074] S307. This session ends.
[0075] See also Figure 8 Based on the above processing process of the first message by the terminal, the process of the second message sent by the terminal to the network side is illustrated. It should be noted that the following steps should be performed after the terminal has applied for network slicing, that is, after the above steps S301, S302, S303 and S304.
[0076] S405, the monitoring module 13 monitors whether there is a second message sent to the network side, if yes, execute step S406, if no, execute step S408;
[0077] S406. The IP message filling module 14 fills the network slice identifier in the option field of the IP header of the second message;
[0078] After a terminal applies for a network slice, there may be multiple continuous sessions. During these sessions, as long as the IP address conflict of the network slice still exists, the network slice identifier should be filled in the option field of the IP header of each message.
[0079] S407, the sending module 15 sends the second message filled with the network slice identifier to the network side;
[0080] The method of sending the second message to the network side may be any method including existing methods.
[0081] S408. This session ends.
[0082] See also Fig. 9 This embodiment also shows a network side device, which may be a communication device arranged on the network side, and each step of the message sending method of the embodiment of the present invention may be executed by one or more modules in the network side device. In this example, the network side device includes a monitoring module 23, an IP message filling module 24, and a sending module 25. The monitoring module 23 in the network side device is used to monitor whether there is a first message sent to the terminal. The IP message filling module 24 is used to fill in the network slice identifier in the option field of the IP header of the first message. The sending module 25 is used to send the filled first message to the terminal.
[0083] See also Fig.10 In this example, the network-side device sends the message in the following process:
[0084] S501, the monitoring module 23 monitors whether there is a first message sent to the terminal, if yes, execute step S502, if no, execute step S504;
[0085] S502, the IP message filling module 24 fills the network slice identifier in the first message;
[0086] S503, the sending module 25 sends the first message filled with the network slice identifier to the terminal;
[0087] S504: This session ends.
[0088] It should be understood that in actual implementation, the module division method of the terminal or network side device shown in the above example of this embodiment can be arbitrary.
[0089] It can be seen that the message processing method of the embodiment of the present invention can still find the corresponding network interface according to the network slice identifier in the first message sent by the network side device when the IP address allocated by the network slice conflicts, thereby ensuring network communication and improving user experience. At the same time, the message sending method of the embodiment of the present invention fills in the network slice identifier in the first message sent to the terminal, so that the terminal can obtain valid information other than the IP address to confirm the network interface, provide the terminal with normal communication interaction conditions, and help avoid the problem that the terminal cannot perform normal network communication after the IP address of the network slice conflicts.
[0090] Embodiment three:
[0091] This embodiment also provides a terminal. Fig.11 As shown, it includes a processor 111, a memory 112 and a communication bus 113, wherein:
[0092] The communication bus 113 is used to realize the connection and communication between the processor 111 and the memory 112;
[0093] The processor 111 is used to execute one or more computer programs stored in the memory 112 to implement at least one step in the message processing method in the above-mentioned embodiment 1 and embodiment 2.
[0094] This embodiment also provides a communication device, which is arranged on the network side. Fig.12 As shown, it includes a processor 121, a memory 122 and a communication bus 123, wherein:
[0095] The communication bus 123 is used to realize the connection and communication between the processor 121 and the memory 122;
[0096] The processor 121 is used to execute one or more computer programs stored in the memory 122 to implement at least one step in the message sending method in the above-mentioned embodiment 1 and embodiment 2.
[0097] The present embodiment also provides a computer storage medium, which includes volatile or non-volatile, removable or non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, computer program modules or other data). Computer storage media include, but are not limited to, RAM (Random Access Memory), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable read only memory), flash memory or other memory technology, CD-ROM (Compact Disc Read-Only Memory), digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by a computer.
[0098] The computer storage medium in this embodiment can be used to store one or more computer programs, and the one or more computer programs stored therein can be executed by a processor to implement at least one step of the message processing method or the message sending method in the above-mentioned embodiments 1 and 2.
[0099] It can be seen that those skilled in the art should understand that all or some of the steps, systems, and functional modules / units in the above disclosed methods can be implemented as software (which can be implemented with computer program code executable by a computing device), firmware, hardware, and appropriate combinations thereof. In hardware implementations, the division between the functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component can have multiple functions, or a function or step can be performed by several physical components in cooperation. Some or all physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit.
[0100] In addition, it is well known to those skilled in the art that communication media generally contain computer readable instructions, data structures, computer program modules or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery media. Therefore, the present invention is not limited to any specific hardware and software combination.
[0101] The above contents are further detailed descriptions of the embodiments of the present invention in combination with specific implementation methods, and it cannot be determined that the specific implementation of the present invention is limited to these descriptions. For ordinary technicians in the technical field to which the present invention belongs, several simple deductions or substitutions can be made without departing from the concept of the present invention, which should be regarded as falling within the protection scope of the present invention.
Claims
1. A message processing method, applied to a terminal, comprising: When the IP address of the first network slice applied for by the terminal is the same as the IP address of the second network slice that has been accessed, access the first network slice, and configure a network interface for the first network slice that is different from the network interface of the second network slice; Receive a first message sent by a network side, where the first message includes a network slice identifier, and the network slice identifier corresponds to the first network slice or the second network slice; Distribute the first message to the network interface configured by the corresponding network slice according to the network slice identifier; The network slice identifier is an identifier that uniquely corresponds to one of the at least two network slices where an IP address conflict occurs.
2. The message processing method according to claim 1, characterized in that: The network slice identifier includes at least one of a protocol data unit session identifier, an application identifier, and a network interface suffix.
3. The message processing method according to claim 1, characterized in that: The terminal includes a mapping table between the network slice identifier and the network interface; The distributing the first message to the network interface configured by the corresponding network slice according to the network slice identifier includes: The target network interface is queried in the mapping table according to the network slice identifier, and the first message is distributed to the target network interface.
4. The message processing method according to any one of claims 1 to 3, characterized in that: The network slice identifier is located in the option field of the IP header of the first message.
5. The message processing method according to claim 1, characterized in that: Also includes: When the terminal sends a second message to the network side, the network slice identifier is filled in the second message.
6. A message sending method, applied to a network side device, comprising: Fill in a network slice identifier in a first message sent to the terminal, where the network slice identifier corresponds to a first network slice or a second network slice currently accessed by the terminal, and the first network slice and the second network slice have the same IP address; The network slice identifier is an identifier that uniquely corresponds to one of the at least two network slices in which the IP address conflict occurs; Send the first message to the terminal.
7. The message sending method according to claim 6, characterized in that: Before filling in the network slice identifier in the first message sent to the terminal, the method further includes: Receiving a second message sent by the terminal, where the second message includes a network slice identifier; The network slice corresponding to the network slice identifier filled in the first message is consistent with the network slice corresponding to the network slice identifier included in the second message.
8. A terminal comprising a processor, a memory and a communication bus; The communication bus is used to realize the connection and communication between the processor and the memory; The processor is used to execute one or more computer programs stored in the memory to implement the steps of the message processing method according to any one of claims 1 to 5.
9. A communication device, the communication device being arranged on a network side, comprising a processor, a memory and a communication bus; The communication bus is used to realize the connection and communication between the processor and the memory; The processor is used to execute one or more computer programs stored in the memory to implement the steps of the message sending method according to any one of claims 6 to 7.
10. A computer storage medium, characterized in that: The computer storage medium stores one or more computer programs, and the one or more computer programs can be executed by one or more processors to implement the steps of the message processing method as described in any one of claims 1 to 5 or the message sending method as described in any one of claims 6 to 7.
