Information processing method, base station, bearer network equipment, core network equipment and medium

Abstract

The present invention discloses an information processing method, a base station, a bearer network device, a core network device and a medium. The information processing method comprises: obtaining slice service information from a terminal; sending an uplink slice service message carrying a network slice identifier and network slice parameters to a bearer network device according to the slice service information, so that the bearer network device processes the uplink slice service message according to the network slice identifier and network slice parameters in the uplink slice service message, wherein the network slice identifier and network slice parameters can be processed by the bearer network device. In an embodiment of the present invention, by using an uplink slice service message carrying a network slice identifier and network slice parameters that can be processed by a bearer network device, the bearer network device can process the uplink slice service message according to the network slice identifier and network slice parameters in the uplink slice service message on the forwarding plane, thereby reducing the complexity of the network slice orchestration system.

Description

Technical Field

[0001] The embodiments of the present invention relate to, but are not limited to, the field of communication technology, and in particular, to an information processing method, a base station, a bearer network device, a core network device, and a computer-readable storage medium. Background Art

[0002] In different application scenarios of the new generation of mobile communication networks (such as 5G networks), there are huge differences in mobility, bandwidth, latency, reliability, security, operation and billing. Therefore, the 3rd Generation Partnership Project (3GPP) defines network slicing to provide different service processing mechanisms for 5G services in different application scenarios through different virtual networks.

[0003] The end-to-end system of a typical new generation mobile communication network (such as 5G network) mainly involves multiple professional networks such as base stations, bearer networks and core networks. Each professional network needs to identify and distinguish network slices. In related technologies, a variety of technical solutions for identifying and distinguishing network slices have been proposed. However, in these technical solutions, between base stations and bearer networks, and between bearer networks and core networks, cross-professional orchestrators are still needed to realize the business collaborative orchestration of the end-to-end system of the network. Therefore, the overall solution is relatively complex, and the collaborative deployment between professional networks is relatively difficult. Summary of the invention

[0004] The following is a summary of the subject matter described in detail herein. This summary is not intended to limit the scope of the claims.

[0005] The embodiments of the present invention provide an information processing method, a base station, a bearer network device, a core network device and a computer-readable storage medium, which can realize the identification and differentiation of network slices on the forwarding plane, thereby reducing the complexity of the network slice orchestration system.

[0006] In a first aspect, an embodiment of the present invention provides an information processing method, including:

[0007] Obtain slice service information from the terminal;

[0008] An uplink slicing service message carrying a network slice identifier and network slice parameters is sent to a bearer network device according to the slicing service information, so that the bearer network device processes the uplink slicing service message according to the network slice identifier and the network slice parameters in the uplink slicing service message, wherein the network slice identifier and the network slice parameters can be processed by the bearer network device.

[0009] In a second aspect, an embodiment of the present invention further provides an information processing method, including:

[0010] Obtain a first slice service message from a base station or a core network device, where the first slice service message carries a network slice identifier and a network slice parameter, wherein the network slice identifier and the network slice parameter can be processed by a bearer network device;

[0011] The first slice service message is processed according to the network slice identifier and the network slice parameters in the first slice service message.

[0012] In a third aspect, an embodiment of the present invention further provides an information processing method, including:

[0013] Obtain an uplink slicing service message from a bearer network device, wherein the uplink slicing service message carries a network slicing identifier and a network slicing parameter, wherein the network slicing identifier and the network slicing parameter can be processed by the bearer network device;

[0014] The uplink slicing service message is processed according to the local slicing service configuration strategy and the network slicing identifier and the network slicing parameters in the uplink slicing service message.

[0015] In a fourth aspect, an embodiment of the present invention further provides an information processing method, including:

[0016] The base station obtains slice service information from the terminal;

[0017] The base station sends an uplink slicing service message carrying a network slicing identifier and network slicing parameters to the bearer network device according to the slicing service information, wherein the network slicing identifier and the network slicing parameters can be processed by the bearer network device;

[0018] The bearer network device forwards the uplink slicing service message to the core network device according to the network slicing identifier and the network slicing parameters in the uplink slicing service message;

[0019] The core network device processes the uplink slicing service message according to the local slicing service configuration policy and the network slicing identifier and the network slicing parameters in the uplink slicing service message.

[0020] In a fifth aspect, an embodiment of the present invention further provides a base station, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the information processing method of the first aspect as described above is implemented.

[0021] In a sixth aspect, an embodiment of the present invention further provides a bearer network device, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the information processing method of the second aspect described above is implemented.

[0022] In the seventh aspect, an embodiment of the present invention further provides a core network device, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the information processing method of the third aspect described above is implemented.

[0023] In an eighth aspect, an embodiment of the present invention further provides a computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions are used to execute the above information processing method.

[0024] The embodiment of the present invention includes: the base station obtains the slice service information from the terminal; according to the slice service information, an uplink slice service message carrying a network slice identifier and a network slice parameter is sent to the bearer network device, so that the bearer network device processes the uplink slice service message according to the network slice identifier and the network slice parameter in the uplink slice service message, wherein the network slice identifier and the network slice parameter can be processed by the bearer network device. According to the scheme provided by the embodiment of the present invention, when the base station obtains the slice service information from the terminal, the base station can send an uplink slice service message carrying a network slice identifier and a network slice parameter to the bearer network device according to the slice service information. Since the network slice identifier and the network slice parameter can be processed by the bearer network device, when the bearer network device receives the uplink slice service message, the bearer network device can identify and distinguish the uplink slice service message according to the network slice identifier and the network slice parameter in the uplink slice service message on the forwarding plane, and does not need to realize the collaborative processing of the uplink slice service message through a complex cross-professional orchestrator, thereby reducing the complexity of the network slice orchestration system.

[0025] Other features and advantages of the present invention will be described in the following description, and partly become apparent from the description, or understood by practicing the present invention. The purpose and other advantages of the present invention can be realized and obtained by the structures particularly pointed out in the description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The accompanying drawings are used to provide a further understanding of the technical solution of the present invention and constitute a part of the specification. Together with the embodiments of the present invention, they are used to explain the technical solution of the present invention and do not constitute a limitation on the technical solution of the present invention.

[0027] Figure 1is a schematic diagram of a network topology for executing an information processing method provided by an embodiment of the present invention;

[0028] Figure 2 is a flow chart of an information processing method applied to a base station provided by an embodiment of the present invention;

[0029] Figure 3 It is a structural diagram of a message substructure provided by a specific example of the present invention;

[0030] Figure 4 is a schematic diagram of a Slice ID TLV structure in a message substructure provided by another specific example of the present invention;

[0031] Figure 5 is a schematic diagram of an Isolation Type TLV structure in a message substructure provided by another specific example of the present invention;

[0032] Figure 6 is a schematic diagram of a QoS Identifier TLV structure in a message substructure provided by another specific example of the present invention;

[0033] Figure 7 is a schematic diagram of an SLA TLV structure in a message substructure provided by another specific example of the present invention;

[0034] Figure 8 It is a schematic diagram of the setting position of the message substructure in the slice service message provided by a specific example of the present invention;

[0035] Fig. 9 It is a schematic diagram of the setting position of the message substructure in the slice service message provided by another specific example of the present invention;

[0036] Fig.10 It is a schematic diagram of the setting position of the message substructure in the slice service message provided by another specific example of the present invention;

[0037] Fig.11 It is a schematic diagram of the setting position of the message substructure in the slice service message provided by another specific example of the present invention;

[0038] Fig.12 It is a schematic diagram of the setting position of the message substructure in the slice service message provided by another specific example of the present invention;

[0039] Fig.13 is a flowchart of an information processing method applied to a base station provided by another embodiment of the present invention;

[0040] Fig.14 is a flow chart of an information processing method applied to a bearer network device provided by an embodiment of the present invention;

[0041] Fig.15 It is a flowchart of processing a first slice service message in an information processing method applied to a bearer network device provided by another embodiment of the present invention;

[0042] Fig.16 is a flow chart of obtaining a forwarding strategy in an information processing method applied to a bearer network device provided by another embodiment of the present invention;

[0043] Fig.17 is a flow chart of an information processing method applied to a core network device provided by an embodiment of the present invention;

[0044] Fig.18 is a flowchart of an information processing method applied to a core network device provided by another embodiment of the present invention;

[0045] Fig.19 is a flow chart of an information processing method applied to a network system provided by an embodiment of the present invention;

[0046] Fig. 20 It is a flow chart of a bearer network device forwarding an uplink slice service message to a core network device in an information processing method applied to a network system provided by another embodiment of the present invention;

[0047] Fig.21 is a flow chart of obtaining a forwarding strategy in an information processing method applied to a network system provided by another embodiment of the present invention;

[0048] Fig. 22 is a flow chart of an information processing method applied to a network system provided by another embodiment of the present invention;

[0049] Fig.23 It is a structural diagram of an IPv6 message header provided by a specific example of the present invention;

[0050] Fig.24 It is a structural diagram of an IPv6 message header provided by another specific example of the present invention. DETAILED DESCRIPTION

[0051] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. 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.

[0052] It should be noted that, although the functional modules are divided in the device schematic diagram and the logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than the module division in the device or the order in the flowchart. The terms "first", "second", etc. in the specification, claims and the above drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0053] The present invention provides an information processing method, a base station, a bearer network device, a core network device and a computer-readable storage medium. When the base station obtains slice service information from a terminal, the base station can send an uplink slice service message carrying a network slice identifier and network slice parameters to the bearer network device according to the slice service information, so that the bearer network device processes the uplink slice service message according to the network slice identifier and network slice parameters in the uplink slice service message, wherein the network slice identifier and network slice parameters can be processed by the bearer network device. Since the uplink slice service message carrying the network slice identifier and network slice parameters that can be processed by the bearer network device is utilized, when the bearer network device receives the uplink slice service message, the bearer network device can identify and distinguish the uplink slice service message according to the network slice identifier and network slice parameters in the uplink slice service message on the forwarding plane, and does not need to realize the collaborative processing of the uplink slice service message through a complex cross-professional orchestrator, thereby reducing the complexity of the network slice orchestration system.

[0054] The embodiments of the present invention are further described below in conjunction with the accompanying drawings.

[0055] like Figure 1 As shown, Figure 1 FIG. 1 is a schematic diagram of a network topology for executing an information processing method provided by an embodiment of the present invention. Figure 1 In the example, the network topology includes a base station 110, a first bearer network device 120, a second bearer network device 130 and a core network device 140 connected in sequence, wherein the first bearer network device 120 and the second bearer network device 130 are in the bearer network, the first bearer network device 120 is an edge node connecting the bearer network and the base station 110, and the second bearer network device 130 is an edge node connecting the bearer network and the core network device 140.

[0056] The transmission direction of the service message passing through the base station 110, the first bearer network device 120, the second bearer network device 130 and the core network device 140 in sequence is the uplink transmission direction. At this time, the service message is an uplink service message; the transmission direction of the service message passing through the core network device 140, the second bearer network device 130, the first bearer network device 120 and the base station 110 in sequence is the downlink transmission direction. At this time, the service message is a downlink service message.

[0057] When the base station 110 receives a network connection request based on network slicing from a user terminal, the base station 110 can construct a corresponding uplink slicing service message according to the network connection request, and send the uplink slicing service message to the core network device 140 through the first bearer network device 120 and the second bearer network device 130. At this time, the core network device 140 can perform relevant processing on the uplink slicing service message, and can construct a corresponding downlink slicing service message according to the uplink slicing service message. Then, the core network device 140 sends the downlink slicing service message to the base station 110 through the second bearer network device 130 and the first bearer network device 120, so that after processing the downlink slicing service message, the base station 110 forwards the processed downlink slicing service message to the user terminal, thereby realizing network access based on network slicing for the user terminal.

[0058] In addition, the base station 110, the first bearer network device 120, the second bearer network device 130 and the core network device 140 are all provided with a memory and a processor, and the memory stores an information processing program that can be run on the processor. The processor and the memory can be connected via a bus or other means.

[0059] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory may optionally include a memory remotely disposed relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0060] The network topology and application scenarios described in the embodiments of the present invention are intended to more clearly illustrate the technical solutions of the embodiments of the present invention, and do not constitute a limitation on the technical solutions provided by the embodiments of the present invention. Those skilled in the art will appreciate that with the evolution of network topology and the emergence of new application scenarios, the technical solutions provided by the embodiments of the present invention are equally applicable to similar technical problems.

[0061] It can be understood by those skilled in the art that Figure 1 The topological structure shown in the figure does not constitute a limitation on the embodiments of the present invention, and may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.

[0062] exist Figure 1 In the network topology shown, each device can respectively call its stored information processing program to execute the information processing method.

[0063] Based on the above network topology structure, various embodiments of the information processing method of the present invention are proposed.

[0064] like Figure 2 As shown, Figure 2 is a flow chart of an information processing method provided by an embodiment of the present invention. The information processing method is applied to a base station, for example, Figure 1 In the base station 110 of the illustrated embodiment, the information processing method includes but is not limited to step S110 and step S120.

[0065] Step S110, obtaining slice service information from the terminal.

[0066] In one embodiment, the slice service information may include network slice selection information, and may also include a terminal identifier or an application identifier corresponding to a contracted network slice, which is not specifically limited in this embodiment. The base station may obtain the slice service information from the relevant request information sent by the terminal when the terminal initiates a network connection request. For example, for a terminal that has not signed a contract for a dedicated network slice, when the terminal initiates a connection request for a network slice, the terminal may send network slice selection information indicating the network slice to be connected to the base station, and the network slice selection information received by the base station is the slice service information from the terminal. At this time, the base station can connect the corresponding network slice for the terminal according to the network slice selection information. For another example, for a terminal that has signed a contract for a dedicated network slice, when the terminal initiates a connection request for a network slice, the terminal may only send a terminal identifier to the base station or send a terminal identifier and an application identifier of an application contracted with the network slice to the base station, and the terminal identifier or information including the terminal identifier and the application identifier received by the base station is the slice service information from the terminal. At this time, the base station can search and connect the corresponding network slice for the terminal according to the terminal identifier or the terminal identifier and the application identifier.

[0067] Step S120, sending an uplink slicing service message carrying a network slicing identifier and network slicing parameters to the bearer network device according to the slicing service information, so that the bearer network device processes the uplink slicing service message according to the network slicing identifier and network slicing parameters in the uplink slicing service message, wherein the network slicing identifier and network slicing parameters can be processed by the bearer network device.

[0068] In one embodiment, after the base station obtains the slice service information from the terminal, the base station can first obtain the network slice identifier and network slice parameters corresponding to the slice service information according to the slice service information, and then, the base station can construct an uplink slice service message carrying the network slice identifier and the network slice parameters, wherein the network slice identifier and the network slice parameters can be processed by the bearer network device, and then, the base station can send the uplink slice service message to the bearer network device, so that the bearer network device can parse the network slice identifier and the network slice parameters from the uplink slice service message, so as to identify and distinguish the uplink slice service message according to the network slice identifier and the network slice parameters.

[0069] In one embodiment, the base station obtains the network slice identifier and network slice parameter corresponding to the slice service information according to the slice service information, which may be implemented in different ways, and this embodiment does not specifically limit this. For example, the base station may pre-store network slice identifiers and network slice parameters of various network slices. When the base station obtains the slice service information from the terminal, the base station may search for the network slice identifier and network slice parameter corresponding to the terminal in the pre-stored network slice identifier and network slice parameter according to the slice service information. For another example, after obtaining the slice service information from the terminal, the base station may initiate a request to obtain the network slice identifier and network slice parameter corresponding to the slice service information to the core network device according to the slice service information, thereby obtaining the network slice identifier and network slice parameter corresponding to the slice service information in the core network device. For another example, after obtaining the slice service information from the terminal, the base station may send instruction information for obtaining the network slice identifier and network slice parameter to the terminal according to the slice service information, thereby obtaining the network slice identifier and network slice parameter corresponding to the slice service information in the terminal.

[0070] In one embodiment, the network slice identifier may be single network slice selection assistance information (S-NSSAI); the network slice parameters include but are not limited to at least one of slice isolation type parameters, slice quality requirement parameters, and slice service level agreement (Service-Level Agreement, SLA) requirement parameters. The network slice parameters may be appropriately selected according to the actual usage of the terminal, and this embodiment does not specifically limit this.

[0071] In one embodiment, a new message substructure that can be processed by the bearer network device can be set in the uplink slicing service message. The message substructure carries the network slice identifier and the network slice parameters, so that when the bearer network device receives the uplink slicing service message including the message substructure, the bearer network device can parse the network slice identifier and the network slice parameters from the message substructure, thereby being able to identify and distinguish the uplink slicing service message according to the network slice identifier and the network slice parameters.

[0072] In one embodiment, the message substructure may include a slice identification field and a slice parameter field, wherein the network slice identification is configured in the slice identification field, and the network slice parameter is configured in the slice parameter field. In addition, the slice parameter field may include multiple parameter subfields, and appropriate field extensions may be performed according to actual conditions.

[0073] The specific structure of the message substructure is described below with a specific example:

[0074] In one example, refer to Figure 3 , Figure 3 A specific structural diagram of the message substructure is given. Figure 3 The message substructure includes a Slice ID TLV structure, an Isolation Type TLV structure, a QoS Identifier TLV structure and an SLA TLV structure, wherein the Slice ID TLV structure is the slice identification field, and the combination of the Isolation Type TLV structure, the QoS Identifier TLV structure and the SLA TLV structure is the slice parameter field.

[0075] like Figure 4 As shown, the Slice ID TLV structure includes an attribute field for indicating a network slice identifier. In the Slice ID TLV structure, the explanations of the main fields are as follows:

[0076] Type: used to indicate that this TLV structure is a TLV structure with a field for indicating a network slice identifier;

[0077] Length: used to indicate the length of this TLV structure;

[0078] Slice ID: used to represent the network slice identifier. This field is used to uniquely identify a slice service and can be filled in with S-NSSAI.

[0079] like Figure 5As shown in FIG. 1 , the Isolation Type TLV structure includes an attribute field for indicating slice isolation type parameters. In the Isolation Type TLV structure, the main fields are explained as follows:

[0080] Type: used to indicate that this TLV structure is a TLV structure with a field for indicating a slice isolation type parameter;

[0081] Length: used to indicate the length of this TLV structure;

[0082] Isolation Type: used to indicate the slice isolation type parameter. The specific values ​​can be end-to-end hard isolation, hop-by-hop hard isolation, tunnel layer soft isolation, virtual private network (VPN) isolation combined with tunnel sharing, VPN sharing, etc.

[0083] like Figure 6 As shown, the QoS Identifier TLV structure includes an attribute field for indicating slice quality requirement parameters. In the QoS Identifier TLV structure, the explanations of the main fields are as follows:

[0084] Type: used to indicate that this TLV structure is a TLV structure with fields for indicating slice quality requirement parameters;

[0085] Length: used to indicate the length of this TLV structure;

[0086] QoS Identifier: used to indicate the slice quality requirement parameters. The 5G QoS Class Identifier (5QI) defined by the 3GPP standard can be filled in.

[0087] like Figure 7 As shown, the SLATLV structure includes attribute fields for representing slice SLA requirement parameters. In the SLATLV structure, the explanations of the main fields are as follows:

[0088] Type: used to indicate that this TLV structure is a TLV structure with fields for indicating slice SLA requirement parameters;

[0089] Length: used to indicate the length of this TLV structure;

[0090] BandWidth: used to indicate the bandwidth requirement of the slice service;

[0091] Delay: used to indicate the delay requirement of slice services;

[0092] Jitter: used to indicate the jitter requirement of the slice service.

[0093] It can be understood by those skilled in the art that the bearer network device generally only processes the L3 layer encapsulation structure of the message. Therefore, the message substructure carrying the network slice identifier and the network slice parameters can be set in the L2 layer encapsulation structure or the L3 layer encapsulation structure of the slice service message. It is worth noting that in some specific cases, as an option, the message substructure can also be set in the Transmission Control Protocol (TCP) message header or the User Datagram Protocol (UDP) message header. This embodiment does not specifically limit this, as long as the message substructure is set in a position in the slice service message that can be easily recognized by the wireless access device, the bearer network device and the core network device.

[0094] The following is a specific example of the location of the message substructure in the slice service message:

[0095] In one example, if Figure 8 As shown, the message substructure can be set in an extension header of the IPv6 message header (such as Figure 8 At this time, in the NH field (i.e., the next hop field) in the IPv6 message header, fill in the content used to indicate that the next hop is the SliceExt Head (for example, NH=SliceExt). Among them, the Hdr Ext Len field in the extension header (such as SliceExtHead) is used to indicate the length of the SliceExt Head. It is worth noting that the interpretation of other fields in the IPv6 message header is the same as the interpretation of the corresponding fields in the existing IPv6 message header, so it will not be repeated here. Since the bearer network device can parse and process the information in the IPv6 message header, the bearer network device can identify the information carried by the message substructure set in the extension header of the IPv6 message header. Therefore, the bearer network device can identify and distinguish the slice service message on the forwarding plane according to the network slice identifier and network slice parameters in the message substructure.

[0096] In another example, if Fig. 9 As shown, the slice identification field in the message substructure can be set in the destination address field of the IPv6 message header, and the slice parameter field in the message substructure (including the Isolation Type TLV structure, the QoSIdentifier TLV structure and the SLA TLV structure) can be set in an extension header of the IPv6 message header (such as Fig. 9In the SliceExt Head shown in the figure, the contents filled in the destination address field (i.e., the Destination Address field) in the IPv6 message header include the address prefix (Prefix), the node identifier (Node ID), and the network slice identifier (SliceID); in the NH field (i.e., the next hop field) in the IPv6 message header, the content used to indicate that the next hop is SliceExtHead is filled in (for example, NH=SliceExt). Among them, the Hdr Ext Len field in the extension header (such as SliceExt Head) is used to indicate the length of the SliceExt Head. It is worth noting that the interpretation of other fields in the IPv6 message header is the same as the interpretation of the corresponding fields in the existing IPv6 message header, so it will not be repeated here. Since the bearer network device can parse and process the information in the IPv6 message header, the bearer network device can identify the information carried by the message substructure set in the IPv6 message header. Therefore, the bearer network device can identify and distinguish the slice service message according to the network slice identifier and network slice parameters in the message substructure on the forwarding plane.

[0097] In another example, if Fig.10 As shown, the message substructure can be set in the option field of the IPv4 message header (such as Fig.10 Options) shown in the figure. It is worth noting that the interpretation of other fields in the IPv4 message header is the same as the interpretation of the corresponding fields in the existing IPv4 message header, so it will not be repeated here. Since the bearer network device can parse and process the information in the IPv4 message header, the bearer network device can identify the information carried by the message substructure set in the option field of the IPv4 message header. Therefore, the bearer network device can identify and distinguish the slice service message on the forwarding plane according to the network slice identifier and network slice parameters in the message substructure.

[0098] In another example, if Fig.11As shown, the message substructure can be set in the network service header (NSH). At this time, the slice identification field in the message substructure can be set in the service path identification (Service Path ID, SPI) field in the NSH, and the slice parameter field (including IsolationType TLV structure, QoS Identifier TLV structure and SLA TLV structure) in the message substructure can be set in the ContextHeader field in the NSH. It is worth noting that the interpretation of other fields in the NSH is the same as the interpretation of the corresponding fields in the existing NSH, so it will not be repeated here. Since the bearer network device can parse and process the information in the NSH, the bearer network device can identify the information carried by the message substructure set in the NSH, so the bearer network device can identify and distinguish the slice service message according to the network slice identification and network slice parameters in the message substructure on the forwarding plane.

[0099] In another example, if Fig.12 As shown, the message substructure can be set in the Generic Network Virtualization Encapsulation (Geneve). At this time, the slice identification field in the message substructure can be set in the Virtual Network Identifier (VNI) field in the Geneve header, and the slice parameter field in the message substructure (including the Isolation Type TLV structure, QoS IdentifierTLV structure and SLA TLV structure) can be set in the variable length option field in the Geneve header (such as Fig.12 Since the bearer network device can parse and process the information in the Geneve header, the bearer network device can identify the information carried by the message substructure set in the Geneve header. Therefore, the bearer network device can identify and distinguish the slice service message according to the network slice identifier and network slice parameters in the message substructure on the forwarding plane.

[0100] In one embodiment, by adopting the information processing method including the above-mentioned steps S110 and S120, when the base station obtains the slice service information from the terminal, the base station can send an uplink slice service message carrying a network slice identifier and network slice parameters to the bearer network device according to the slice service information, so that the bearer network device processes the uplink slice service message according to the network slice identifier and network slice parameters in the uplink slice service message, wherein the network slice identifier and network slice parameters can be processed by the bearer network device. Since the uplink slice service message carrying the network slice identifier and network slice parameters that can be processed by the bearer network device is utilized, when the bearer network device receives the uplink slice service message, the bearer network device can identify and distinguish the uplink slice service message according to the network slice identifier and network slice parameters in the uplink slice service message on the forwarding plane, and does not need to realize the collaborative processing of the uplink slice service message through a complex cross-professional orchestrator, thereby reducing the complexity of the network slice orchestration system.

[0101] In addition, in one embodiment, referring to Fig.13 The information processing method may also include but is not limited to the following steps:

[0102] Step S130, obtaining a downlink slicing service message from a bearer network device, where the downlink slicing service message corresponds to the uplink slicing service message, and the downlink slicing service message carries a network slicing identifier and a network slicing parameter;

[0103] Step S140, processes the downlink slice service message according to the local slice service configuration information and the network slice identifier and network slice parameters in the downlink slice service message.

[0104] In one embodiment, after step S120, when the base station receives a downlink slicing service message from the bearer network device, and the downlink slicing service message carries a network slice identifier and network slice parameters, the base station performs relevant processing on the downlink slicing service message according to the preset local slicing service configuration information and the network slice identifier and network slice parameters in the downlink slicing service message, such as increasing the processing priority of the downlink slicing service message and forwarding the downlink slicing service message to the terminal, thereby completing the terminal's network access based on network slicing.

[0105] It is worth noting that the downlink slice service message from the bearer network device in this embodiment is similar to Figure 2The embodiment shown corresponds to the uplink slicing service message sent by the base station to the bearer network device, and the downlink slicing service message in this embodiment is generated by the core network device according to the uplink slicing service message. Similarly, the downlink slicing service message also includes a message substructure, and the message substructure in the downlink slicing service message has the same structural format and the same field meaning as the message substructure in the uplink slicing service message. For the structural format and field meaning of the message substructure in the downlink slicing service message, refer to the following. Figure 3 , Figure 4 , Figure 5 , Figure 6 and Figure 7 In addition, the position where the message substructure is set in the downlink slicing service message is the same as the position where the message substructure is set in the uplink slicing service message. For the position where the message substructure is set in the downlink slicing service message, reference can be made to the following. Figure 8 , Fig. 9 , Fig.10 , Fig.11 and Fig.12 The relevant description in the illustrated embodiment will not be repeated here.

[0106] It should be noted that the network slice identifier and network slice parameters carried by the message substructure of the downlink slice service message in this embodiment are the same as those in the example Figure 2 The network slice identifier and network slice parameters carried in the message substructure of the uplink slicing service message in the illustrated embodiment are consistent.

[0107] In addition, if Fig.14 As shown, Fig.14 is a flowchart of an information processing method provided by another embodiment of the present invention, the information processing method is applied to a bearer network device, for example, Figure 1 In the first bearer network device 120 or the second bearer network device 130 in the illustrated embodiment, the information processing method includes but is not limited to the following steps:

[0108] Step S210, obtaining a first slice service message from a base station or a core network device, where the first slice service message carries a network slice identifier and a network slice parameter, wherein the network slice identifier and the network slice parameter can be processed by a bearer network device;

[0109] Step S220, process the first slice service message according to the network slice identifier and network slice parameters in the first slice service message.

[0110] In one embodiment, after the bearer network device obtains the first slice service message from the base station or the core network device, the bearer network device can process the first slice service message according to the network slice identifier and the network slice parameters in the first slice service message. At this time, the bearer network device can determine whether there is a network slice service corresponding to the network slice identifier in the bearer network according to the network slice identifier. If there is a corresponding network slice service, the bearer network device can directly process the first slice service message according to the configuration information corresponding to the existing network slice service, such as encapsulating the first slice service message with an additional label suitable for transmission of the bearer network and forwarding the first slice service message; if there is no corresponding network slice service, the bearer network device can request the network controller to send a forwarding strategy corresponding to the network slice identifier, thereby performing relevant encapsulation and forwarding processing on the first slice service message according to the forwarding strategy issued by the network controller.

[0111] It is worth noting that the first slice service message can be an uplink slice service message from the base station, or a downlink slice service message from the core network device, and this embodiment does not make any specific limitations on this.

[0112] In one embodiment, the network slice identifier may be S-NSSAI; the network slice parameters include but are not limited to at least one of slice isolation type parameters, slice quality requirement parameters, and slice SLA requirement parameters. The network slice parameters may be appropriately selected based on the actual usage of the terminal, and this embodiment does not specifically limit this.

[0113] In one embodiment, a new message substructure that can be processed by the bearer network device may be set in the first slice service message, and the message substructure carries the network slice identifier and the network slice parameters. When the bearer network device receives the first slice service message including the message substructure, the bearer network device can parse the network slice identifier and the network slice parameters from the message substructure, thereby being able to identify and distinguish the first slice service message based on the network slice identifier and the network slice parameters.

[0114] In one embodiment, the message substructure may include a slice identification field and a slice parameter field, wherein the network slice identification is configured in the slice identification field, and the network slice parameter is configured in the slice parameter field. In addition, the slice parameter field may include multiple parameter subfields, and appropriate field extensions may be performed according to actual conditions.

[0115] It is worth noting that the message substructure in the first slice service message in this embodiment is the same as the above-mentioned Figure 3 , Figure 4 , Figure 5 , Figure 6 and Figure 7 The message substructure in the illustrated embodiment has the same structure format and the same field meaning. For the structure format and field meaning of the message substructure in the first slice service message in this embodiment, refer to Figure 3 , Figure 4 , Figure 5 , Figure 6 and Figure 7 The relevant descriptions in the embodiment shown are not repeated here. In addition, in this embodiment, the message substructure is set in the first slice service message, and the above-mentioned Figure 8 , Fig. 9 , Fig.10 , Fig.11 and Fig.12 In the embodiment shown, the position where the message substructure is set in the uplink slice service message is the same. For the position where the message substructure is set in the first slice service message in this embodiment, reference can be made to the following. Figure 8 , Fig. 9 , Fig.10 , Fig.11 and Fig.12 The relevant description in the illustrated embodiment will not be repeated here.

[0116] In one embodiment, by adopting an information processing method including the above-mentioned steps S210 and S220, when the bearer network device receives a first slice service message carrying a network slice identifier and network slice parameters that can be processed by the bearer network device, the bearer network device can identify and distinguish the first slice service message based on the network slice identifier and network slice parameters in the first slice service message on the forwarding plane, without the need for a complex cross-professional orchestrator to achieve collaborative processing of the first slice service message, thereby reducing the complexity of the network slice orchestration system.

[0117] In addition, in one embodiment, referring to Fig.15 Step S220 may include but is not limited to the following steps:

[0118] Step S221, obtaining a forwarding strategy according to the network slice identifier and network slice parameters in the first slice service message;

[0119] Step S222: process the first slice service message according to the forwarding strategy.

[0120] In one embodiment, when the bearer network device receives a first slice service message carrying a network slice identifier and network slice parameters, the bearer network device can first obtain a corresponding forwarding strategy based on the network slice identifier and network slice parameters, and then perform relevant encapsulation and forwarding processing on the first slice service message according to the forwarding strategy.

[0121] In one embodiment, the bearer network device obtains the forwarding strategy according to the network slice identifier and network slice parameters. There may be different implementation methods. For example, the forwarding strategy may be obtained according to the network slice identifier, network slice parameters and locally stored network topology information, or the corresponding forwarding strategy may be requested from the network controller according to the network slice identifier and network slice parameters. This embodiment does not specifically limit this.

[0122] The specific method for the bearer network device to obtain the forwarding strategy based on the network slice identifier and network slice parameters is explained below with a specific example.

[0123] Assuming that the bearer network device is in a distributed system, the bearer network device can perform path calculation of the segment routing (SR) tunnel according to the network slicing parameters (such as slice SLA requirement parameters), the network slice identifier and the network slice topology information collected in advance through the interior gateway protocol (IGP), and automatically configure the diversion method of the slice service message according to the calculation result, thereby obtaining the forwarding strategy. After the bearer network device obtains the forwarding strategy, it can also exchange routing configuration information with the remote network element through the border gateway protocol (Border Gateway Protocol, BGP).

[0124] Assuming that the bearer network device is in a centralized control system, the bearer network device can first send the network slice identifier and network slice parameters to the network controller to request the corresponding forwarding strategy. When the network controller receives the network slice identifier and the network slice parameters, the network controller can perform SR tunnel path calculation according to the network slice parameters (such as slice SLA requirement parameters) based on the network slice identifier and the network slice topology information obtained in advance based on the information reported by each bearer network device, and configure the diversion method of the slice service message according to the calculation result to obtain the forwarding strategy. Then, the network controller will send the forwarding policy to the bearer network device, so that the bearer network device can obtain the forwarding strategy corresponding to the network slice identifier and the network slice parameters.

[0125] In one embodiment, the bearer network device processes the first slice service message according to the forwarding strategy, and may perform some additional encapsulation processing on the first slice service message according to the forwarding strategy, such as adding additional virtual private network routing and forwarding instance (Virtual Private Network Routing and Forwarding Instance, VRF) labels, adding additional segment routing based multi-protocol label switching (Segment Routing Multi-ProtocolLabel Switching, SR-MPLS) labels, etc. This embodiment does not specifically limit this.

[0126] In addition, in one embodiment, referring to Fig.16 Step S221 may include but is not limited to the following steps:

[0127] Step S223, reporting the network slice identifier and network slice parameters in the first slice service message to the network controller, so that the network controller configures a forwarding strategy according to the network slice identifier and the network slice parameters;

[0128] Step S224: Obtain the forwarding policy issued by the network controller.

[0129] In one embodiment, when a bearer network device receives a first slice service message carrying a network slice identifier and network slice parameters, the bearer network device may first determine whether there is a network slice service corresponding to the network slice identifier in the bearer network based on the network slice identifier. When there is no corresponding network slice service, the bearer network device may report the network slice identifier and the network slice parameters to the network controller, so that the network controller configures a forwarding policy based on the network slice identifier and the network slice parameters. When the network controller completes the configuration of the forwarding policy, the network controller will send the forwarding policy to the bearer network device, so that the bearer network device can obtain the forwarding policy corresponding to the network slice identifier and the network slice parameters, so that the bearer network device can perform relevant encapsulation and forwarding processing on the first slice service message according to the forwarding policy in subsequent steps.

[0130] In addition, if Fig.17 As shown, Fig.17 is a flowchart of an information processing method provided by another embodiment of the present invention, the information processing method is applied to a core network device, for example, Figure 1 In the core network device 140 in the illustrated embodiment, the information processing method includes but is not limited to the following steps:

[0131] Step S310, obtaining an uplink slicing service message from a bearer network device, where the uplink slicing service message carries a network slicing identifier and a network slicing parameter, wherein the network slicing identifier and the network slicing parameter can be processed by the bearer network device;

[0132] Step S320, processes the uplink slicing service message according to the local slicing service configuration strategy and the network slicing identifier and network slicing parameters in the uplink slicing service message.

[0133] In one embodiment, when the core network device receives an uplink slicing service message from a bearer network device, and the uplink slicing service message carries a network slice identifier and network slicing parameters that can be processed by the bearer network device, the core network device can perform relevant processing on the uplink slicing service message according to a preset local slicing service configuration policy and the network slice identifier and network slicing parameters of the uplink slicing service message, such as using an independent user plane function (UPF) virtual machine for processing, allocating high priority queues for priority processing, etc.

[0134] In one embodiment, the network slice identifier may be S-NSSAI; the network slice parameters include but are not limited to at least one of slice isolation type parameters, slice quality requirement parameters, and slice SLA requirement parameters. The network slice parameters may be appropriately selected based on the actual usage of the terminal, and this embodiment does not specifically limit this.

[0135] In one embodiment, a new message substructure that can be processed by the bearer network device may be set in the uplink slicing service message, and the message substructure carries the network slice identifier and the network slice parameters. When the core network device receives the uplink slicing service message including the message substructure, the core network device can parse the network slice identifier and the network slice parameters from the message substructure, so as to perform relevant processing on the first slice service message according to the network slice identifier and the network slice parameters.

[0136] In one embodiment, the message substructure may include a slice identification field and a slice parameter field, wherein the network slice identification is configured in the slice identification field, and the network slice parameter is configured in the slice parameter field. In addition, the slice parameter field may include multiple parameter subfields, and appropriate field extensions may be performed according to actual conditions.

[0137] It is worth noting that the message substructure in the uplink slice service message in this embodiment is the same as the above-mentioned Figure 3 , Figure 4 , Figure 5 , Figure 6 and Figure 7The message substructure in the embodiment shown has the same structure format and the same field meaning. For the structure format and field meaning of the message substructure in the uplink slice service message in this embodiment, refer to Figure 3 , Figure 4 , Figure 5 , Figure 6 and Figure 7 The relevant descriptions in the embodiment shown are not repeated here. In addition, in this embodiment, the message substructure is set in the uplink slice service message, and the above-mentioned Figure 8 , Fig. 9 , Fig.10 , Fig.11 and Fig.12 In the embodiment shown, the position where the message substructure is set in the uplink slicing service message is the same. For the position where the message substructure is set in the uplink slicing service message in this embodiment, reference can be made to the following. Figure 8 , Fig. 9 , Fig.10 , Fig.11 and Fig.12 The relevant description in the illustrated embodiment will not be repeated here.

[0138] In one embodiment, by adopting an information processing method including the above-mentioned steps S310 and S320, when the core network device receives an uplink slicing service message from the bearer network device, it is explained that the bearer network device is able to identify and distinguish the network slice identifier and network slice parameters carried by the uplink slicing service message on the forwarding plane, otherwise the core network device will not receive the uplink slicing service message. Therefore, the information processing method of this embodiment does not need to use a complex cross-professional orchestrator to achieve collaborative processing of uplink slicing service messages, thereby reducing the complexity of the network slicing orchestration system.

[0139] In addition, in one embodiment, referring to Fig.18 The information processing method may also include but is not limited to the following steps:

[0140] Step S330, sends a downlink slicing service message carrying a network slice identifier and network slicing parameters to the bearer network device according to the processed uplink slicing service message, so that the bearer network device processes the downlink slicing service message according to the network slice identifier and network slicing parameters in the downlink slicing service message.

[0141] In one embodiment, after step S320, when the core network device completes processing of the uplink slicing service message, the core network device can construct a corresponding downlink slicing service message based on the processed uplink slicing service message, and the downlink slicing service message carries a network slice identifier and a network slice parameter. Then, the core network device can send the downlink slicing service message to the bearer network device. When the bearer network device receives the downlink slicing service message, the bearer network device can perform relevant encapsulation and forwarding processing on the downlink slicing service message according to the network slice identifier and the network slice parameter carried by the downlink slicing service message. Since the bearer network device can identify and distinguish the information carried by the downlink slicing service message on the forwarding plane, it is not necessary to realize the collaborative processing of the downlink slicing service message through a complex cross-professional orchestrator, thereby reducing the complexity of the network slicing orchestration system.

[0142] It is worth noting that the downlink slice service message constructed by the core network device according to the processed uplink slice service message in this embodiment is similar to the downlink slice service message constructed by the core network device according to the processed uplink slice service message. Fig.17 The embodiment shown corresponds to the uplink slicing service message from the bearer network device. Similarly, the downlink slicing service message of this embodiment also includes a message substructure, which is similar to the Figure 3 , Figure 4 , Figure 5 , Figure 6 and Figure 7 The message substructure in the embodiment shown has the same structure format and the same field meaning. For the structure format and field meaning of the message substructure in the downlink slice service message of this embodiment, refer to Figure 3 , Figure 4 , Figure 5 , Figure 6 and Figure 7 The relevant descriptions in the embodiment shown are not repeated here. In addition, in this embodiment, the message substructure is set in the downlink slice service message, and Figure 8 , Fig. 9 , Fig.10 , Fig.11 and Fig.12 In the embodiment shown, the position of the message substructure in the slice service message is the same. For the position of the message substructure in the downlink slice service message in this embodiment, reference can be made to the following. Figure 8 , Fig. 9 , Fig.10 , Fig.11 and Fig.12 The relevant description in the illustrated embodiment will not be repeated here.

[0143] It should be noted that the network slice identifier and network slice parameters carried by the message substructure of the downlink slice service message in this embodiment are the same as those in the example Fig.17 The network slice identifier and network slice parameters carried in the message substructure of the uplink slicing service message in the illustrated embodiment are consistent.

[0144] In addition, if Fig.19 As shown, Fig.19 : is a flowchart of an information processing method provided by another embodiment of the present invention. The information processing method is applied to a network system, the network system includes a base station, a bearer network device and a core network device, and the information processing method includes but is not limited to the following steps:

[0145] Step S410, the base station obtains slice service information from the terminal;

[0146] Step S420: the base station sends an uplink slicing service message carrying a network slicing identifier and network slicing parameters to the bearer network device according to the slicing service information, wherein the network slicing identifier and the network slicing parameters can be processed by the bearer network device;

[0147] Step S430, the bearer network device forwards the uplink slicing service message to the core network device according to the network slicing identifier and network slicing parameters in the uplink slicing service message;

[0148] In step S440, the core network device processes the uplink slicing service message according to the local slicing service configuration policy and the network slicing identifier and network slicing parameters in the uplink slicing service message.

[0149] like Fig. 20 As shown, in one embodiment, step S430 may include but is not limited to the following steps:

[0150] Step S431, the bearer network device obtains a forwarding strategy according to the network slice identifier and network slice parameters in the uplink slice service message;

[0151] Step S432: The bearer network device forwards the uplink slice service message to the core network device according to the forwarding strategy.

[0152] like Fig.21 As shown, in one embodiment, step S431 may include but is not limited to the following steps:

[0153] Step S433, the bearer network device reports the network slice identifier and network slice parameters in the uplink slice service message to the network controller, so that the network controller configures the forwarding strategy according to the network slice identifier and the network slice parameters;

[0154] Step S434: The bearer network device obtains the forwarding policy issued by the network controller.

[0155] like Fig. 22As shown, in one embodiment, after step S440, the information processing method may further include but is not limited to the following steps:

[0156] Step S450, the core network device sends a downlink slice service message carrying a network slice identifier and network slice parameters to the bearer network device according to the processed uplink slice service message;

[0157] Step S460: The bearer network device forwards the downlink slice service message to the base station according to the forwarding strategy and the network slice identifier and network slice parameters in the downlink slice service message;

[0158] Step S470: The base station forwards the downlink slicing service message to the terminal according to the local slicing service configuration information and the network slicing identifier and network slicing parameters in the downlink slicing service message.

[0159] In one embodiment, the network slice identifier may be S-NSSAI; the network slice parameters include but are not limited to at least one of slice isolation type parameters, slice quality requirement parameters, and slice SLA requirement parameters. The network slice parameters may be appropriately selected based on the actual usage of the terminal, and this embodiment does not specifically limit this.

[0160] In one embodiment, a new message substructure that can be processed by the bearer network device can be set in both the uplink slicing service message and the downlink slicing service message. The message substructure carries the network slice identifier and the network slice parameter, so that when the bearer network device receives the uplink slicing service message or the downlink slicing service message including the message substructure, the bearer network device can parse the network slice identifier and the network slice parameter from the message substructure, thereby being able to identify and distinguish the uplink slicing service message or the downlink slicing service message according to the network slice identifier and the network slice parameter.

[0161] In one embodiment, the message substructure may include a slice identification field and a slice parameter field, wherein the network slice identification is configured in the slice identification field, and the network slice parameter is configured in the slice parameter field. In addition, the slice parameter field may include multiple parameter subfields, and appropriate field extensions may be performed according to actual conditions.

[0162] It is worth noting that in the above-mentioned information processing method applied to the network system, the message substructure in the uplink slicing service message and the message substructure in the downlink slicing service message are the same as those in the above-mentioned Figure 3 , Figure 4 , Figure 5 , Figure 6 and Figure 7The message substructures in the illustrated embodiments all have the same structural format and the same field meanings. For the message substructure of the uplink slicing service message and the message substructure of the downlink slicing service message in the information processing method applied to the network system, the structural format and field meanings can all be referred to as follows. Figure 3 , Figure 4 , Figure 5 , Figure 6 and Figure 7 In addition, in the above-mentioned information processing method applied to the network system, the message substructure of the uplink slicing service message is set at a position in the uplink slicing service message, and the message substructure of the downlink slicing service message is set at a position in the downlink slicing service message, and the above-mentioned Figure 8 , Fig. 9 , Fig.10 , Fig.11 and Fig.12 In the embodiment shown, the position where the message substructure is set in the slice service message is the same. For the position where the message substructure in the information processing method applied to the network system is set in the uplink slice service message and the position where the message substructure of the downlink slice service message is set in the downlink slice service message, reference can be made to the following. Figure 8 , Fig. 9 , Fig.10 , Fig.11 and Fig.12 The relevant description in the illustrated embodiment will not be repeated here.

[0163] It should be noted that the information processing method applied to the network system in the above-mentioned embodiments, the information processing method applied to the base station in the above-mentioned embodiments, the information processing method applied to the bearer network device in the above-mentioned embodiments, and the information processing method applied to the core network device in the above-mentioned embodiments are all based on the same inventive concept. The only difference between the four is that the focus is different. For example, the focus of the information processing method applied to the base station in the above-mentioned embodiments is the base station, the focus of the information processing method applied to the bearer network device in the above-mentioned embodiments is the bearer network device, and the focus of the information processing method applied to the core network device in the above-mentioned embodiments is the core network device, while the focus of the information processing method applied to the network system in the above-mentioned embodiments is the network system including the base station, the bearer network device and the core network device. Therefore, the above four have the same beneficial effect, that is, they can use the slice service message carrying the network slice identifier and network slice parameters that can be processed by the bearer network device, so that the bearer network device can process the slice service message according to the network slice identifier and network slice parameters in the slice service message on the forwarding plane, thereby reducing the complexity of the network slice orchestration system.

[0164] In order to more clearly illustrate the specific steps and processes of the information processing method in the above-mentioned embodiments, specific examples are given below for illustration.

[0165] Example 1:

[0166] This example is an implementation example of defining a new extension header based on the IPv6 message header to set a message substructure that carries a network slice identifier and network slice parameters.

[0167] Suppose that a slice service for a vertical industry application needs to be opened at a certain 5G base station. The service message of the base station adopts IPv6 message encapsulation. The industry is used for remote control, requiring the slice to occupy independent hardware resources and be a delay-sensitive service (for example, the delay is required to be within 5ms and the jitter is within 3us), but the bandwidth requirement is only 20M. At the same time, the bearer network adopts technologies such as L3VPN, SR-MPLS and FlexE to provide different service isolation capabilities, and adopts a centralized controller to implement service orchestration. Under the above conditions, the base station can define a message substructure, which includes a network slice identification field, a slice isolation type field, a slice quality requirement field, and a slice SLA requirement field. In addition, the base station can newly define an extension header SliceExt Header in the IPv6 message header, and set the above message substructure in the SliceExtHeader.

[0168] When the base station receives a slice service request from the terminal, the base station can complete the corresponding slice service processing (such as allocating hard-isolated spectrum resources, setting slice priority processing levels, etc.) according to the slice service request. After the base station completes the processing of the slice service, when the base station sends a slice service message to the core network device, such as Fig.23As shown, the base station can fill in the following information in the message substructure of the IPv6 message header according to the slice service request of the terminal: fill in 200001 in the network slice identification field (i.e. Slice ID = 200001), fill in End to End Hard Isolation in the slice isolation type field (i.e. Isolation Type = End to End Hard Isolation), fill in 81 in the slice quality requirement field (i.e. QoS Identifier = 81), fill in 20M, 5ms and 3us in the slice SLA requirement field (i.e. BandWidth = 20M, Delay = 5ms, Jitter = 3us), etc. After the base station completes the encapsulation processing of the above information and obtains the uplink slice service message, the source address of the uplink slice service message is the IP address of the base station, and the destination address is the IP address of the core network device, such as the IP address of the user plane function (UPF). At this time, the base station can send the uplink slice service message to the bearer network device, and the bearer network device forwards the uplink slice service message to the core network device.

[0169] After the edge device on the inlet side of the bearer network receives the uplink slicing service message from the base station, the edge device on the inlet side of the bearer network can parse out information such as the network slice identifier, slice isolation type parameters, slice quality requirement parameters and slice SLA requirement parameters from the uplink slicing service message, and judge whether there is a slice service corresponding to the network slice identifier in the current bearer network according to the network slice identifier, and perform different processing according to different judgment results. Specifically, if there is a corresponding slice service, the edge device on the inlet side of the bearer network forwards and processes the uplink slice service message according to the preset forwarding strategy and slice isolation type parameters, slice quality requirement parameters, slice SLA requirement parameters and other information, for example, L3VPN and SR-MPLS encapsulate the uplink slice service message, and map it to FlexE Channel, so that the intermediate node of the bearer network can configure and forward the uplink slice service message according to the FlexE Channel; if there is no corresponding slice service, the edge device on the inlet side of the bearer network can report information such as the network slice identifier, slice isolation type parameters, slice quality requirement parameters and slice SLA requirement parameters to the centralized controller. After receiving this information, the centralized controller can perform service orchestration according to the requirements of the slice service, and create a new L3VPN service on the basis of this service orchestration to carry the slice service, and specify a dedicated SR-MPLS tunnel, and use the FlexE Channel method at the physical layer to achieve end-to-end hard isolation and provide low-latency and low-jitter forwarding performance. Then, the centralized controller sends the corresponding configuration to the edge device on the inlet side of the bearer network, so that the edge device on the inlet side of the bearer network will report the network slice identifier (such as Fig.23 200001) is bound to the newly created L3VPN service and forwards the uplink slice service message.

[0170] After the edge device on the egress side of the bearer network receives the uplink slicing service message from the edge device on the ingress side of the bearer network, the edge device on the egress side of the bearer network can strip off the L3VPN encapsulation or SR-MPLS encapsulation in the uplink slicing service message, restore the uplink slicing service message to the original uplink slicing service message sent by the base station, and forward it to the core network device.

[0171] After the core network device receives the uplink slicing service message forwarded by the edge device on the bearer network egress side, the core network device can parse the network slice identifier, slice isolation type parameters, slice quality requirement parameters, slice SLA requirement parameters and other information from the uplink slicing service message, and process the uplink slicing service message accordingly in combination with the local slicing service configuration policy in the core network device (such as using an independent UPF virtual machine for processing, allocating high priority queues for priority processing, etc.).

[0172] When the core network device completes the processing of the slice service and sends the slice service message to the base station, such as Fig.24 As shown, the core network device can fill in the following information in the message substructure of the IPv6 message header according to the slice service after processing: fill in 200001 in the network slice identification field (i.e. Slice ID = 200001), fill in End to End Hard Isolation in the slice isolation type field (i.e. Isolation Type = End to End Hard Isolation), fill in 81 in the slice quality requirement field (i.e. QoS Identifier = 81), fill in 20M, 5ms and 3us in the slice SLA requirement field (i.e. BandWidth = 20M, Delay = 5ms, Jitter = 3us), etc. After the core network device completes the encapsulation processing of the above information and obtains the downlink slice service message, the source address of the downlink slice service message is the IP address of the core network device (e.g., the IP address of the UPF), and the destination address is the IP address of the base station. At this time, the core network device can send the downlink slice service message to the bearer network device, and the bearer network device forwards the downlink slice service message to the base station.

[0173] After the bearer network device receives the downlink slicing service message from the core network device, the bearer network device can perform relevant processing on the downlink slicing service message. The specific processing process is similar to the processing process of the uplink slicing service message by the above-mentioned bearer network device (including the processing process of the uplink slicing service message by the edge device on the inlet side of the bearer network and the processing process of the uplink slicing service message by the edge device on the outlet side of the bearer network). The only difference is that the processing object is the downlink slicing service message. Therefore, the processing process of the bearer network device on the downlink slicing service message can refer to the processing process of the uplink slicing service message by the edge device on the inlet side of the bearer network and the processing process of the uplink slicing service message by the edge device on the outlet side of the bearer network, which will not be repeated here.

[0174] After the base station receives the downlink slicing service message forwarded by the edge device on the egress side of the bearer network, the base station can parse out information such as the network slice identifier, slice isolation type parameters, slice quality requirement parameters and slice SLA requirement parameters from the downlink slicing service message, and perform corresponding processing on the downlink slicing service message in combination with the local slicing service configuration information in the base station. When the base station completes processing of the downlink slicing service message, the base station can forward the processed downlink slicing service message to the terminal, thereby realizing the terminal's network access based on network slicing.

[0175] Example 2:

[0176] This example is an implementation example based on the destination address field in the IPv6 message header and a newly defined extension header to set a message substructure carrying a network slice identifier and network slice parameters.

[0177] This example is similar to the above example 1. The base station uses IPv6 message encapsulation, and the end-to-end processing from the base station to the core network device is consistent with the processing in the above example 1. The only difference is the structure and encapsulation of the slice service message. Specifically, the destination address field of the slice service message in this example contains the addressing information of the destination node (such as the addressing information of the core network device: Perfix and Node SID) and the network slice identifier (ie, Slice ID), while the extended header of the slice service message only contains information such as the slice isolation type parameter, slice quality requirement parameter, and slice SLA requirement parameter, and no longer contains the network slice identifier (ie, Slice ID).

[0178] Example 3:

[0179] This example is an implementation example of defining a new extension header based on the IPv4 message header to set a message substructure that carries a network slice identifier and network slice parameters.

[0180] This example is similar to Example 1 above, and the end-to-end processing process from the base station to the core network device is consistent with the processing process in Example 1 above. The only difference is that the base station uses IPv4 message encapsulation, and the structure and encapsulation of the slice service message are different.

[0181] Example 4:

[0182] This example is an implementation example of setting a message substructure carrying a network slice identifier and network slice parameters based on NSH encapsulation.

[0183] This example is similar to the above example 1, and the end-to-end processing from the base station to the core network device is consistent with the processing in the above example 1, the only difference is the structure and encapsulation of the slice service message. Specifically, the slice service message is NSH encapsulated according to the standard RFC8300, and the network slice identifier (ie, Slice ID) is filled in the SPI field in the NSH encapsulation, while the slice isolation type parameter, slice quality requirement parameter, and slice SLA requirement parameter are filled in the Context Header field in the NSH encapsulation.

[0184] Example 5:

[0185] This example is an implementation example based on Geneve encapsulation to set a message substructure carrying a network slice identifier and network slice parameters.

[0186] This example is similar to Example 1 above, and the end-to-end processing from the base station to the core network device is consistent with the processing in Example 1 above, the only difference being the structure and encapsulation of the slice service message. Specifically, the slice service message is Geneve encapsulated according to the standard draft-ietf-nvo3-geneve-16, and the network slice identifier (ie, Slice ID) is filled in the VNI field in the Geneve encapsulation, while the slice isolation type parameter, slice quality requirement parameter, and slice SLA requirement parameter are filled in the variable length option field in the Geneve encapsulation.

[0187] In addition, an embodiment of the present invention further provides a base station, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor.

[0188] The processor and the memory may be connected via a bus or other means.

[0189] It should be noted that the base station in this embodiment can be applied as follows Figure 1 The base station 110 in the system architecture of the embodiment shown in the figure is a base station in the embodiment and Figure 1 The base station 110 in the system architecture of the illustrated embodiments belongs to the same inventive concept, so these embodiments have the same implementation principles and technical effects, which will not be described in detail here.

[0190] The non-transient software program and instructions required to implement the information processing method of the above embodiment are stored in the memory. When executed by the processor, the information processing method of the above embodiment is executed, for example, the above described Figure 2 Steps S110 to S120 of the method, Fig.13 Method steps S130 to S140 in.

[0191] In addition, an embodiment of the present invention further provides a bearer network device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor.

[0192] The processor and the memory may be connected via a bus or other means.

[0193] It should be noted that the bearer network device in this embodiment can be applied as follows: Figure 1 The first bearer network device 120 or the second bearer network device 130 in the system architecture of the embodiment shown in the figure, the bearer network device in this embodiment and the Figure 1 The first bearer network device 120 and the second bearer network device 130 in the system architecture of the illustrated embodiment belong to the same inventive concept, so these embodiments have the same implementation principle and technical effect, which will not be described in detail here.

[0194] The non-transient software program and instructions required to implement the information processing method of the above embodiment are stored in the memory. When executed by the processor, the information processing method of the above embodiment is executed, for example, the above described Fig.14 Steps S210 to S220 of the method, Fig.15 Steps S221 to S222 of the method, Fig.16 Method steps S223 to S224.

[0195] In addition, an embodiment of the present invention further provides a core network device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor.

[0196] The processor and the memory may be connected via a bus or other means.

[0197] It should be noted that the core network device in this embodiment can be applied as follows: Figure 1 The core network device 140 in the system architecture of the embodiment shown in the figure is a core network device in this embodiment and a core network device in this embodiment. Figure 1 The core network device 140 in the system architecture of the illustrated embodiments belongs to the same inventive concept, so these embodiments have the same implementation principles and technical effects, which will not be described in detail here.

[0198] The non-transient software program and instructions required to implement the information processing method of the above embodiment are stored in the memory. When executed by the processor, the information processing method of the above embodiment is executed, for example, the above described Fig.17 Steps S310 to S320 of the method, Fig.18 Method step S330 in .

[0199] The device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separated, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0200] In addition, an embodiment of the present invention further provides a computer-readable storage medium, which stores computer-executable instructions. The computer-executable instructions are executed by a processor or a controller, for example, by a processor in the above-mentioned base station embodiment, so that the above-mentioned processor can execute the information processing method in the above-mentioned embodiment, for example, execute the above-mentioned Figure 2 Steps S110 to S120 of the method, Fig.13or, being executed by a processor in the bearer network device embodiment, so that the processor executes the information processing method in the embodiment, for example, executing the information processing method described above. Fig.14 Steps S210 to S220 of the method, Fig.15 Steps S221 to S222 of the method, Fig.16 or, being executed by a processor in the above-mentioned core network device embodiment, so that the above-mentioned processor can execute the information processing method in the above-mentioned embodiment, for example, executing the above-mentioned Fig.17 Steps S310 to S320 of the method, Fig.18 Method step S330 in .

[0201] It will be appreciated by those skilled in the art that all or some of the steps and systems in the disclosed method above may be implemented as software, firmware, hardware and appropriate combinations thereof. Some physical components or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor or a microprocessor, or may be implemented as hardware, or may be implemented as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or a non-transitory medium) and a communication medium (or a temporary medium). As known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, disk storage or other magnetic storage devices, or any other medium that may be used to store desired information and may be accessed by a computer. Furthermore, it is well known to those skilled in the art that communication media typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0202] The above is a specific description of the preferred implementation of the present invention, but the present invention is not limited to the above-mentioned implementation mode. Technical personnel familiar with the field can also make various equivalent deformations or substitutions without violating the spirit of the present invention. These equivalent deformations or substitutions are all included in the scope defined by the claims of the present invention.

Claims

1. An information processing method, comprising: Obtain slice service information from the terminal; An uplink slicing service message carrying a network slicing identifier and network slicing parameters is sent to a bearer network device according to the slicing service information, so that the bearer network device processes the uplink slicing service message according to the network slicing identifier and the network slicing parameters in the uplink slicing service message, wherein the uplink slicing service message includes a message substructure that can be processed by the bearer network device, and the message substructure carries the network slicing identifier and the network slicing parameters. The message substructure included in the uplink slicing service message is set in any one of the IPv6 message header, IPv4 message header, network service NSH header and general network virtualization encapsulation Geneve in the uplink slicing service message, so that the network slicing identifier and the network slicing parameters can be processed by the bearer network device.

2. The method according to claim 1, characterized in that Also includes: Obtain a downlink slicing service message from a bearer network device, wherein the downlink slicing service message corresponds to the uplink slicing service message, and the downlink slicing service message carries the network slicing identifier and the network slicing parameter; The downlink slice service message is processed according to the local slice service configuration information and the network slice identifier and the network slice parameters in the downlink slice service message.

3. The method according to claim 2, characterized in that The downlink slicing service message includes a message substructure that can be processed by the bearer network device, and the message substructure carries the network slice identifier and the network slice parameters.

4. The method according to claim 3, characterized in that The message substructure included in the downlink slicing service message is set in any one of the IPv6 message header, IPv4 message header, NSH header and Geneve in the downlink slicing service message.

5. The method according to any one of claims 1 to 4, characterized in that: The network slice parameters include at least one of a slice isolation type parameter, a slice quality requirement parameter and a slice service level agreement SLA requirement parameter.

6. An information processing method, comprising: Obtain a first slice service message from a base station or a core network device, wherein the first slice service message carries a network slice identifier and a network slice parameter, wherein the first slice service message includes a message substructure that can be processed by a bearer network device, the message substructure carries the network slice identifier and the network slice parameter, and the message substructure is set in any one of an IPv6 message header, an IPv4 message header, an NSH header, and a Geneve in the first slice service message, so that the network slice identifier and the network slice parameter can be processed by the bearer network device; The first slice service message is processed according to the network slice identifier and the network slice parameters in the first slice service message.

7. The method according to claim 6, characterized in that The processing of the first slice service message according to the network slice identifier and the network slice parameter in the first slice service message includes: Acquire a forwarding strategy according to the network slice identifier and the network slice parameters in the first slice service message; The first slice service message is processed according to the forwarding strategy.

8. The method according to claim 7, characterized in that The acquiring a forwarding strategy according to the network slice identifier and the network slice parameter in the first slice service message includes: Report the network slice identifier and the network slice parameters in the first slice service message to the network controller, so that the network controller configures a forwarding strategy according to the network slice identifier and the network slice parameters; Obtain the forwarding strategy issued by the network controller.

9. The method according to any one of claims 6 to 8, characterized in that: The network slicing parameters include at least one of a slice isolation type parameter, a slice quality requirement parameter and a slice SLA requirement parameter.

10. An information processing method, comprising: Obtain an uplink slicing service message from a bearer network device, wherein the uplink slicing service message carries a network slicing identifier and a network slicing parameter, wherein the uplink slicing service message includes a message substructure that can be processed by the bearer network device, the message substructure carries the network slicing identifier and the network slicing parameter, and the message substructure included in the uplink slicing service message is set in any one of an IPv6 message header, an IPv4 message header, an NSH header, and a Geneve in the uplink slicing service message, so that the network slicing identifier and the network slicing parameter can be processed by the bearer network device; The uplink slicing service message is processed according to the local slicing service configuration strategy and the network slicing identifier and the network slicing parameters in the uplink slicing service message.

11. The method according to claim 10, characterized in that After processing the uplink slice service message, the method further includes: According to the processed uplink slicing service message, a downlink slicing service message carrying the network slice identifier and the network slice parameters is sent to the bearer network device, so that the bearer network device processes the downlink slicing service message according to the network slice identifier and the network slice parameters in the downlink slicing service message.

12. The method according to claim 11, characterized in that The downlink slicing service message includes a message substructure that can be processed by the bearer network device, and the message substructure carries the network slice identifier and the network slice parameters.

13. The method according to claim 12, characterized in that The message substructure included in the downlink slicing service message is set in any one of the IPv6 message header, IPv4 message header, NSH header and Geneve in the downlink slicing service message.

14. The method according to any one of claims 10 to 13, characterized in that: The network slicing parameters include at least one of a slice isolation type parameter, a slice quality requirement parameter and a slice SLA requirement parameter.

15. An information processing method, comprising: The base station obtains slice service information from the terminal; The base station sends an uplink slicing service message carrying a network slicing identifier and network slicing parameters to a bearer network device according to the slicing service information, wherein the uplink slicing service message includes a message substructure that can be processed by the bearer network device, and the message substructure carries the network slicing identifier and the network slicing parameters. The message substructure included in the uplink slicing service message is set in any one of an IPv6 message header, an IPv4 message header, an NSH header, and a Geneve in the uplink slicing service message, so that the network slicing identifier and the network slicing parameters can be processed by the bearer network device; The bearer network device forwards the uplink slicing service message to the core network device according to the network slicing identifier and the network slicing parameters in the uplink slicing service message; The core network device processes the uplink slicing service message according to the local slicing service configuration policy and the network slicing identifier and the network slicing parameters in the uplink slicing service message.

16. The method according to claim 15, characterized in that The bearer network device forwards the uplink slicing service message to the core network device according to the network slicing identifier and the network slicing parameter in the uplink slicing service message, including: The bearer network device obtains a forwarding strategy according to the network slice identifier and the network slice parameters in the uplink slice service message; The bearer network device forwards the uplink slice service message to the core network device according to the forwarding strategy.

17. The method according to claim 16, characterized in that The bearer network device obtains a forwarding strategy according to the network slice identifier and the network slice parameter in the uplink slice service message, including: The bearer network device reports the network slice identifier and the network slice parameters in the uplink slice service message to the network controller, so that the network controller configures the forwarding strategy according to the network slice identifier and the network slice parameters; The bearer network device obtains the forwarding strategy sent by the network controller.

18. The method according to claim 16 or 17, characterized in that After the core network device processes the uplink slicing service message according to the local slicing service configuration policy and the network slicing identifier and the network slicing parameters in the uplink slicing service message, it also includes: The core network device sends a downlink slicing service message carrying the network slicing identifier and the network slicing parameters to the bearer network device according to the processed uplink slicing service message; The bearer network device forwards the downlink slice service message to the base station according to the forwarding strategy and the network slice identifier and the network slice parameters in the downlink slice service message; The base station forwards the downlink slicing service message to the terminal according to the local slicing service configuration information and the network slicing identifier and the network slicing parameters in the downlink slicing service message.

19. The method according to claim 18, characterized in that The downlink slicing service message includes a message substructure that can be processed by the bearer network device, and the message substructure carries the network slice identifier and the network slice parameters.

20. The method according to claim 19, characterized in that The message substructure included in the downlink slicing service message is set in any one of the IPv6 message header, IPv4 message header, NSH header and Geneve in the downlink slicing service message.

21. The method according to any one of claims 15 to 17, characterized in that The network slicing parameters include at least one of a slice isolation type parameter, a slice quality requirement parameter and a slice SLA requirement parameter.

22. A base station, comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the information processing method according to any one of claims 1 to 5 when executing the computer program.

23. A bearer network device, comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the information processing method according to any one of claims 6 to 9 when executing the computer program.

24. A core network device, comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the information processing method according to any one of claims 10 to 14 when executing the computer program.

25. A computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions are used to execute the information processing method described in any one of claims 1 to 5, or the information processing method described in any one of claims 6 to 9, or the information processing method described in any one of claims 10 to 14.

Images