CN114666304A - Message processing method, message sending method, terminal, communication device and computer storage medium - Google Patents
Message processing method, message sending method, terminal, communication device and computer storage medium Download PDFInfo
- Publication number
- CN114666304A CN114666304A CN202011439030.4A CN202011439030A CN114666304A CN 114666304 A CN114666304 A CN 114666304A CN 202011439030 A CN202011439030 A CN 202011439030A CN 114666304 A CN114666304 A CN 114666304A
- Authority
- CN
- China
- Prior art keywords
- network slice
- message
- network
- terminal
- identifier
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
Abstract
The embodiment of the invention provides a message processing and sending method, a terminal, a communication device and a computer storage medium, wherein when an IP (Internet Protocol) address of a first network slice applied by the terminal is the same as an IP address of an accessed second network slice, the first network slice is accessed, and a network interface different from a network interface of the second network slice is configured for the first network slice; receiving a first message sent by a network side, wherein the first message comprises a network slice identifier, and the network slice identifier corresponds to a first network slice or a second network slice which is accessed by the terminal currently; the first message is distributed to the network interface configured by the corresponding network slice according to the network slice identifier, so that the technical effect that normal communication can be completed according to the network slice identifier even if the IP address conflict of the network slice occurs in the terminal in some implementation processes is achieved, and the user experience is improved.
Description
Technical Field
Embodiments of the present invention relate to, but are not limited to, the field of mobile communications, and in particular, but not limited to, a message processing method, a message sending method, a terminal, a communication device, and a computer storage medium.
Background
The network slice is a networking mode according to needs, and in 5G communication, network connection characteristics capable of adapting to requirements of different fields are to be provided, so that network supply according to needs is realized. In the related art, a terminal supports simultaneous access to multiple network slices (for example, up to 8 network slices defined in 3GPP (3rd Generation Partnership Project) protocol), an IP address of each network slice may be independently allocated, and allocation of the IP address may be not controlled by an operator and may be allocated by an enterprise purchasing the slices, and at some time, an IP address conflict may occur. Once a network slice IP address conflict occurs, the terminal will not be able to use the desired network slice, which will incur a lot of complaints and may even affect the business process of the network slice.
Disclosure of Invention
The message processing and sending method, the terminal, the communication device and the computer storage medium provided by the embodiment of the invention mainly solve the technical problem that the terminal cannot normally perform network communication after IP addresses of network slices conflict in the related technology.
In order to solve the foregoing technical problem, an embodiment of the present invention provides a message processing method, applied to a terminal, including:
when the IP addresses of a first network slice and an accessed second network slice applied by a terminal are the same, accessing the first network slice, and configuring a network interface different from that of the second network slice for the first network slice;
receiving a first message sent by a network side, wherein the first message comprises a network slice identifier, and the network slice identifier corresponds to the first network slice or the second network slice;
and distributing the first message to a network interface configured by the corresponding network slice according to the network slice identifier.
The embodiment of the invention also provides a message sending method, which is applied to network side equipment and comprises the following steps:
filling a network slice identifier in a first message sent to a terminal, wherein 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;
and sending the first message to the terminal.
The embodiment of the invention also provides a terminal, which comprises a processor, a memory and a communication bus;
the communication bus is used for realizing connection communication between the processor and the memory;
the processor is configured to execute one or more computer programs stored in the memory to implement the steps of the message processing method as described above.
The embodiment of the invention also provides a communication device, which is arranged at the network side and comprises a processor, a memory and a communication bus;
the communication bus is used for realizing connection communication between the processor and the memory;
the processor is configured to execute one or more computer programs stored in the memory to implement the steps of the messaging method as described above.
An embodiment of the present invention further provides a computer storage medium, where one or more programs are stored, and the one or more programs may be executed by one or more processors to implement the message processing method or the message sending method as described above.
According to the message processing and sending method, the terminal, the communication device and the computer storage medium provided by the embodiment of the invention, after the IP address of the first network slice conflicts with the IP address of the accessed second network slice, the first network slice is still accessed, different network interfaces are configured for the first network slice, the first message sent by the network side is received, the first message comprises a network slice identifier, the first message is distributed to the corresponding network interface according to the network slice identifier, and the network slice identifier uniquely corresponds to the network slice with the IP address conflict currently accessed by the terminal.
Additional features and corresponding advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention.
Drawings
Fig. 1 is a schematic flow chart of a message processing method according to a first embodiment of the present invention;
fig. 2 is a schematic diagram of an IP packet format according to a first embodiment of the present invention;
FIG. 3 is a diagram illustrating the IP header options field classification according to a first embodiment of the present invention;
FIG. 4 is a diagram illustrating a format of an option field of an IP header according to a first embodiment of the present invention;
fig. 5 is a schematic flowchart of a message sending method according to a first embodiment of the present invention;
fig. 6 is a schematic structural diagram of a terminal according to a second embodiment of the present invention;
fig. 7 is a first flowchart illustrating a process of processing a message by the terminal of fig. 6 according to a second embodiment of the present invention;
fig. 8 is a second schematic flow chart illustrating the process of the terminal of fig. 6 on message processing according to a second embodiment of the present invention;
fig. 9 is a schematic structural diagram of a network-side device according to a second embodiment of the present invention;
fig. 10 is a schematic flow chart of the network side device in fig. 9 according to a second embodiment of the present invention for packet transmission;
fig. 11 is a schematic structural diagram of a terminal according to a third embodiment of the present invention;
fig. 12 is a schematic structural diagram of a communication device according to a third embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention are described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The first embodiment is as follows:
the method aims to solve the problem that the terminal cannot use the required network slice due to the fact that IP address conflicts can occur in the network slice. An embodiment of the present invention provides a method for processing a message, where the method is applied to a terminal, please refer to fig. 1, and the method includes:
s101, when the IP address of a first network slice applied by a terminal is the same as the IP address of an accessed second network slice, accessing the first network slice, and configuring a network interface different from the network interface of the second network slice for the first network slice;
after the terminal accesses the operator network, a network interface is virtualized, and an IP address allocated by a core network is configured on the network interface. Generally, the IP addresses allocated on each network interface should be different from each other, and in the related art, if the IP addresses of the network slices conflict (that is, there is a conflict between the IP addresses allocated to two or more network interfaces that are the same), the terminal will refuse to access the network slice of the application. However, in this embodiment, if the terminal is assigned the same IP address as one or more second network slices that have been accessed after applying for the first network slice, the terminal is still accessed to 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.
For example, if a network slice a is currently accessed, and a network interface 0 is configured corresponding to the network slice a; if the IP address allocated to the terminal by the network side is the same as the IP address corresponding to the network slice A when the network slice B is applied, the IP address conflict occurs at the moment. 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.
It can be understood that, after accessing the first network slice, other configurations, such as routing rules, may be performed to ensure that the first network slice can be subsequently serviced normally. For example, in the above example, a routing rule 0 is also configured for network slice a, and a routing rule 1 is configured for network slice B, but of course, due to the difference of network interfaces, the routing rule 0 and the routing rule 1 are also different.
S102, receiving a first message sent by a network side, wherein the first message comprises a network slice identifier, and the network slice identifier corresponds to a first network slice or a second network slice;
in practical application, the network slice identifier should specifically and uniquely correspond to one of at least two network slices in which an IP address conflict occurs, and it should be noted that, in this embodiment, the network slice identifier may only and uniquely correspond to one network slice, but a plurality of network slice identifiers may correspond to the same network slice. It should be understood that, for a network slice where no IP address collision occurs, a first message sent by the network side may not include a network slice identifier, but normal communication can be implemented according to a normal message processing flow.
In some embodiments, the network slice identification includes at least one of: a Protocol Data Unit session identifier (PDU session ID), an Application identifier (APP ID), and a network interface suffix. It should be noted that the network interface suffix is, for example, "0" for network interface 0 and "1" for network interface 1. It will be appreciated that the network slice identifier can represent which network slice the first message corresponds to, thereby providing a means other than an IP address for determining to which corresponding network interface the first message should be distributed. It should be noted that the network slice identifier in the first message is added by the device on the network side before sending the first message.
S103, distributing the first message to the network interface configured by the corresponding network slice according to the network slice identifier.
The network slice identifier corresponds to a certain network slice currently accessed by the terminal, and thus the first packet should be distributed to the network interface corresponding to the network slice. As a specific example, if it is determined from the parsed network slice identifier that the information recorded in the network slice identifier corresponds to the network slice a, the first packet is distributed to the network interface 0 corresponding to the network slice a.
In some embodiments, the terminal includes a mapping table between a network slice identifier and a network interface, and distributing the first packet to the corresponding network interface according to the network slice identifier includes:
and inquiring the target network interface in the mapping table according to the network slice identifier, and distributing the first message to the target network interface.
The mapping table may be dynamically maintained according to the actual network slice of the terminal and the access and configuration conditions of the corresponding network interface, and the target network interface is the network interface correctly corresponding to the current first packet.
In some embodiments, the message processing method further includes, when sending a second message to the network side, filling a network slice identifier in the second message sent by the terminal to the network side;
it should be noted that, in the embodiment of the present invention, the first packet refers to a packet sent by the network side to the terminal, and the second packet refers to a packet sent by the terminal to the network side. Although the second packet is not carried with the network slice identifier when being sent to the network side, the second packet can be normally sent to the corresponding network side device. However, in this embodiment, it may be selected to also fill the network slice identifier in the second packet when the terminal sends the second packet 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 may directly extract the network slice identifier filled when the terminal sends the second packet to the network side, and directly fill the network slice identifier in the first packet when the terminal sends the first packet to the terminal.
In some embodiments, the network slice identifier is specifically populated in an option field of the IP header of the first packet, which may add functionality to the packet and may be used to support troubleshooting, measurement, and security measures. Referring to fig. 2, a format of an IP packet is illustrated, wherein an option field of an IP header is composed of three parts: option code, option length and option data. Please refer to fig. 3 and 4, which illustrate the classification of the option field 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, no matter 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 fields of the IP headers of the two messages respectively.
The message processing method of the embodiment of the invention still allows the access of the first network slice which is applied for the terminal and has the same IP address (namely, the IP address conflict of the network slice occurs), configures the network interface which is different from the network interface of the second network slice with the same IP address for the first network slice, receives the first message sent by the network side, the first message comprises the network slice identifier, and distributes the first message to the corresponding network interface according to the network slice identifier.
An embodiment of the present invention further provides a packet sending method, where the method is applied to a network side device, where the network side device may be a communication device arranged on a network side, please refer to fig. 5, and the method includes:
s201, filling a network slice identifier in a first message sent to a terminal, wherein the network slice identifier corresponds to a first network slice or a second network slice currently accessed by the terminal; the first network slice and the second network slice of this embodiment have the same IP address, and the network slice identifier is filled in the first packet, so that the terminal can determine to which network interface the first packet should be distributed to according to the network slice identifier after receiving the first packet, and therefore, even when the IP address of the network slice of the terminal conflicts, a normal communication interaction condition can be provided for the terminal.
It can be understood that the network slice identifier may be filled in the first packet sent to the terminal only after the terminal has an IP address collision of the network slice. The network slice identifier can be filled in any case, and the terminal judges whether a network interface to be distributed needs to be determined according to the network slice identifier. As a more specific example, when a network slice identifier is filled in a second message sent by a terminal, it indicates that there may be a case where an IP address conflict of a network slice exists in the terminal, and therefore, a network slice identifier is also filled in a first message sent by the terminal, and a 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. Or, by any other method, it is determined that the terminal may be in a situation where the IP address of the network slice conflicts or directly receives the relevant request, and then the network slice identifier is filled in the first message sent to the terminal through this step S201.
In some embodiments, the network slice identifier filled in the first message sent to the terminal by the network side includes at least one of the following: a Protocol Data Unit session identifier (PDU session ID), an Application identifier (APP ID), and a network interface suffix.
In some embodiments, the network slice identifies an option field that is specifically filled in the IP header. In this embodiment, the network slice identifier is filled in the option data in the option field of the IP header.
S202, sending the first message to a terminal.
After the network slice identifier is filled in the first message, the first message is sent to the terminal, and the sending process of the first message can be in any mode.
The message sending method provided by the embodiment of the invention is applied to network side equipment, and the network slice identifier is filled in the first message sent to the terminal, so that the terminal can determine which network interface the first message should be distributed to according to the network slice identifier after receiving the first message, therefore, the effect of providing the condition of normal communication interaction for the terminal can be realized in some implementation processes, including but not limited to when the IP address of the network slice of the terminal conflicts, the problem that the terminal cannot normally carry out network communication after the IP address of the network slice conflicts is favorably avoided, and the user experience is favorably improved.
Example two:
the following takes some specific processes as examples to further describe the message processing method and the message sending method in the embodiments of the present invention.
Referring to fig. 6, this embodiment shows a terminal, and each step of the message processing method according to the embodiment of the present invention may be executed by one or more modules in the terminal. The terminal in this example includes a slice management module 11, a connection management module 12, a monitoring module 13, an IP packet filling module 14, a sending module 15, and an IP packet parsing module 16. The slice management module 11 is configured to apply for, maintain, and release a network slice. The connection management module 12 is configured to configure a network interface, and in this embodiment, other configurations, such as a routing rule, may also be configured. The monitoring module 13 is configured to monitor whether there is a second packet sent to the network side, and whether a first packet sent by the network side is received. The IP packet padding module 14 is configured to pad a network slice identifier in an option field of an IP header of the second packet. The sending module 15 is configured to send the second message filled with the network slice identifier to the network side. The IP packet parsing module 16 is configured to parse a network slice identifier from an option field of an IP header of the first packet, and distribute the first packet to a correct network interface according to the network slice identifier.
Referring to fig. 7, a process of processing a first packet by a terminal in this example includes:
s301, the slice management module 11 applies for a network slice A to the network side, and the network side allocates a corresponding IP address to the terminal;
taking a Network Slice application as an example, the Slice management module 11 matches a corresponding S-NSSAI (Single Network Slice Selection Assistance Information) in a URSP (UE Route Selection Policy) rule list according to a DNN (Data Network Name ), and then initiates a PDU (Protocol Data Unit) session creation request to a Network side, where the S-NSSAI is carried in a signaling. The network side replies PDU conversation establishment acceptance to complete the PDU conversation establishment process.
S302, the connection management module 12 configures a network interface rmnet _ data0 and a routing rule route 0;
the network interface rmnet _ data0 and routing rule route0 correspond to network slice a.
S303, the slice management module 11 applies for a network slice B to the network side, and the network side allocates the same IP address to the terminal as that in the step S301;
s304, the connection management module 12 configures a network interface rmnet _ data1 and a routing rule route 1;
the network interface rmnet _ data1 and routing rule route1 correspond to network slice B.
In the related art, when the network slice to which the same IP address is allocated is found in step S303, the network slice B is not accessed, and the terminal still accesses the network and configures a network interface and a routing rule for the terminal in this example. It is understood that the network interface rmnet _ data1 and the routing rule route1 configured in this step are different from the network interface rmnet _ data0 and the routing rule route0 in step S302, respectively.
S305, the monitoring module 13 monitors whether there is a first message from the network side, if yes, step S306 is executed, otherwise, step S307 is executed;
s306, the IP message analysis module 16 analyzes the network slice identifier from the first message and distributes the first message to a correct network interface according to the network slice identifier;
specifically, the IP packet parsing module 16 locally maintains a mapping table between a network slice identifier and a network interface at the terminal, and distributes the first packet to the correct network interface according to the mapping table after parsing out the network slice identifier.
And S307, ending the session.
Referring to fig. 8, a flow of a second packet sent by the terminal to the network side is illustrated based on the processing procedure of the first packet by the terminal. It should be noted that the following steps should be performed after the terminal has applied for a network slice, i.e. for example after the above-mentioned steps S301, S302, S303 and S304.
S405, the monitoring module 13 monitors whether a second message sent to the network side exists, if so, step S406 is executed, and if not, step S408 is executed;
s406, the IP packet filling module 14 fills a network slice identifier in an option field of an IP header of the second packet;
after a terminal applies for a network slice, there may be a session process that lasts for many times, and in these processes, as long as the IP address of the network slice conflicts still exist, a network slice identifier should be filled in an option field of an IP header of each packet.
S407, the sending module 15 sends the second message filled with the network slice identifier to the network side;
the manner of sending the second packet to the network side may be any manner including the existing manner.
And S408, ending the session.
Referring to fig. 9, this embodiment further illustrates a network side device, where the network side device may be a communication device disposed on a network side, and each step of the message sending method according to the embodiment of the present invention may be executed by one or more modules in the network side device. The network side device in this example includes a monitoring module 23, an IP packet stuffing module 24, and a sending module 25. The monitoring module 23 in the network side device is configured to monitor whether there is a first message sent to the terminal. The IP packet padding module 24 is configured to pad a network slice identifier in an option field of an IP header of the first packet. The sending module 25 is configured to send the filled first message to the terminal.
Referring to fig. 10, a process of sending a packet by a network side device in this example includes:
s501, the monitoring module 23 monitors whether a first message sent to the terminal exists, if so, step S502 is executed, and if not, step S504 is executed;
s502, an IP message filling module 24 fills a network slice identifier in the first message;
s503, the sending module 25 sends the first message filled with the network slice identifier to the terminal;
and S504, ending the session.
It should be understood that, in an actual implementation process, the module division manner of the terminal or the network side device shown in the above example of this embodiment may be arbitrary.
Therefore, according to the message processing method provided by the embodiment of the invention, when the IP addresses allocated by the network slices conflict, the corresponding network interface can still be found according to the network slice identifier in the first message sent by the network side equipment, so that the communication of the network can be ensured, and the user experience is improved. Meanwhile, the message sending method of the embodiment of the invention fills the network slice identifier in the first message sent to the terminal, so that the terminal can obtain effective information of the network interface beyond the IP address, provide a normal communication interaction condition for the terminal, and is favorable for avoiding the problem that the terminal cannot normally carry out network communication after the IP addresses of the network slices conflict.
Example three:
the present embodiment further provides a terminal, as shown in fig. 11, which includes a processor 111, a memory 112 and a communication bus 113, where:
the communication bus 113 is used for realizing connection communication between the processor 111 and the memory 112;
the processor 111 is configured to execute one or more computer programs stored in the memory 112 to implement at least one step of the message processing method in the first embodiment and the second embodiment.
The present embodiment further provides a communication device, which is disposed on the network side, and as shown in fig. 12, the communication device includes a processor 121, a memory 122, and a communication bus 123, where:
the communication bus 123 is used for realizing connection communication between the processor 121 and the memory 122;
the processor 121 is configured to execute one or more computer programs stored in the memory 122 to implement at least one step of the message sending method in the first embodiment and the second embodiment.
The present embodiments also provide a computer storage medium including volatile or non-volatile, removable or non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, computer program modules or other data. Computer storage media includes, but is 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 Discs (DVD) or other optical Disc storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer.
The computer storage medium in this embodiment may be used to store one or more computer programs, and the stored one or more computer programs may be executed by the processor to implement at least one step of the message processing method or the message sending method in the first and second embodiments.
It will be apparent to those skilled in the art that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software (which may be implemented in computer program code executable by a computing device), firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit.
In addition, communication media typically embodies computer readable instructions, data structures, computer program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to one of ordinary skill in the art. Thus, the present invention is not limited to any specific combination of hardware and software.
The foregoing is a more detailed description of embodiments of the present invention, and the present invention is not to be considered limited to such descriptions. For those skilled in the art to which the invention pertains, several simple deductions or substitutions can be made without departing from the spirit of the invention, and all shall be considered as belonging to the protection scope of the invention.
Claims (10)
1. A message processing method is applied to a terminal and comprises the following steps:
when the IP addresses of a first network slice and an accessed second network slice applied by a terminal are the same, accessing the first network slice, and configuring a network interface different from that of the second network slice for the first network slice;
receiving a first message sent by a network side, wherein the first message comprises a network slice identifier, and the network slice identifier corresponds to the first network slice or the second network slice;
and distributing the first message to a network interface configured by the corresponding network slice according to the network slice identifier.
2. The message processing method of claim 1, wherein the network slice identifier comprises 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 of 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:
and inquiring a target network interface in the mapping table according to the network slice identifier, and distributing the first message to the target network interface.
4. The message processing method according to any of claims 1-3, characterized in that the network slice identifies an option field located in the IP header of the first message.
5. The message processing method of claim 1, further comprising:
and when the terminal sends a second message to the network side, filling a network slice identifier in the second message.
6. A message sending method is applied to network side equipment and comprises the following steps:
filling a network slice identifier in a first message sent to a terminal, wherein 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;
and sending the first message to the terminal.
7. The message sending method according to claim 6, wherein before filling the network slice identifier in the first message sent to the terminal, the method further comprises:
receiving a second message sent by the terminal, wherein the second message comprises a network slice identifier;
and 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 for realizing connection communication between the processor and the memory;
the processor is configured to execute one or more computer programs stored in the memory to implement the steps of the message processing method according to any of claims 1 to 5.
9. A communication device is arranged on a network side and comprises a processor, a memory and a communication bus;
the communication bus is used for realizing connection communication between the processor and the memory;
the processor is configured to execute one or more computer programs stored in the memory to implement the steps of the messaging method according to any of claims 6 to 7.
10. A computer storage medium, characterized in that the computer storage medium stores one or more computer programs executable by one or more processors to implement the message processing method of any one of claims 1 to 5 or the steps of the message sending method of any one of claims 6 to 7.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011439030.4A CN114666304A (en) | 2020-12-07 | 2020-12-07 | Message processing method, message sending method, terminal, communication device and computer storage medium |
| PCT/CN2021/127537 WO2022121552A1 (en) | 2020-12-07 | 2021-10-29 | Packet processing and sending methods, terminal, communication device, and computer storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011439030.4A CN114666304A (en) | 2020-12-07 | 2020-12-07 | Message processing method, message sending method, terminal, communication device and computer storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114666304A true CN114666304A (en) | 2022-06-24 |
Family
ID=81973084
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011439030.4A Pending CN114666304A (en) | 2020-12-07 | 2020-12-07 | Message processing method, message sending method, terminal, communication device and computer storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN114666304A (en) |
| WO (1) | WO2022121552A1 (en) |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108833181B (en) * | 2018-06-25 | 2020-10-30 | 北京邮电大学 | NG-CN network slice system and network slice selection method |
| CN112602292B (en) * | 2018-08-28 | 2022-06-14 | 华为技术有限公司 | Inter-slice sharing in a 5G core network |
| US11588733B2 (en) * | 2019-05-14 | 2023-02-21 | Vmware, Inc. | Slice-based routing |
| CN111698725A (en) * | 2020-06-23 | 2020-09-22 | 腾讯科技（深圳）有限公司 | Method for dynamically determining network slice and electronic equipment |
-
2020
- 2020-12-07 CN CN202011439030.4A patent/CN114666304A/en active Pending
-
2021
- 2021-10-29 WO PCT/CN2021/127537 patent/WO2022121552A1/en unknown
Also Published As
| Publication number | Publication date |
|---|---|
| WO2022121552A1 (en) | 2022-06-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3361675A1 (en) | Distributed load balancing system, health check method and service node | |
| CN110226308B (en) | Network slice management method, management unit and system | |
| WO2019056883A1 (en) | Network slice deployment method and related device | |
| US9148778B2 (en) | Activating a mobile terminal from mobile network side | |
| EP3585114A1 (en) | Method, device and system for configuring network slice | |
| EP4037281A1 (en) | Transmission control method, network management server, base station and storage medium | |
| EP3496432A1 (en) | Communication method and device | |
| US11025490B2 (en) | Method for dynamically managing a network service in a communication network | |
| CN107332814B (en) | Request message transmission method and device | |
| CN109391503B (en) | Network slice management method and device | |
| CN111327668A (en) | Network management method, device, equipment and storage medium | |
| CN114364031B (en) | Service providing method, device and storage medium | |
| CN113938814B (en) | Service scheduling method, UPF, system and medium of content distribution network | |
| CN110661673A (en) | Heartbeat detection method and device | |
| CN114666304A (en) | Message processing method, message sending method, terminal, communication device and computer storage medium | |
| US20120254393A1 (en) | Device management method, device management apparatus, and device management system | |
| CN112954669A (en) | Method, device, network element and storage medium for controlling service of shared terminal | |
| US20230074779A1 (en) | Service relations in provisioning of communication service instance | |
| WO2022001732A1 (en) | Cdn scheduling method, access device, cdn scheduler, and storage medium | |
| EP3107352A1 (en) | Information transfer method and apparatus | |
| CN113391759A (en) | Communication method and device | |
| CN113840277A (en) | Download control method, system, terminal and medium for user subscription data | |
| CN109451093A (en) | A kind of loopback port address distribution method and device | |
| CN114095976B (en) | Distribution method and device of network slices, electronic equipment and readable medium | |
| CN114584558B (en) | Cloud edge cooperative distributed API gateway system and API calling method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |