Slice information processing method, device, equipment and storage medium

Abstract

The embodiment of the present invention discloses a slice information processing method, apparatus, device and storage medium. The method includes: a network slice selection function (NSSF) obtains multiple network slice identifiers requested by a user device for registration; the network slices corresponding to at least two of the multiple network slice identifiers conflict; based on the multiple network slice identifiers and the network slices supported by each access and mobility management function (AMF), a target AMF is selected, and the network slice identifier corresponding to the network slice supported by the target AMF among the multiple network slice identifiers is used as an available network slice identifier, and the network slice identifier corresponding to the network slice not supported by the target AMF among the multiple network slice identifiers is used as a rejected network slice identifier.

Description

Technical Field

[0001] The present invention relates to the field of mobile communications, and in particular to a slice information processing method, apparatus, device and storage medium. Background Art

[0002] Network slicing is one of the key technologies of the 5G core network. Due to the flexibility of the 5G core network's service-based architecture, network slicing can flexibly combine the network functions of the 5G core network according to the network needs of vertical industry customers, forming virtual logical networks.

[0003] When a user equipment (UE) wants to access a network slice, it must select the AMF corresponding to the network slice during the registration process. During the registration process, the radio access network (RAN) first selects an initial AMF to send a registration request. The initial AMF checks whether it can serve all the network slices requested by the UE. If not, the initial AMF initiates the AMF redirection process and sends a request to the Network Slice Selection Function (NSSF) to find an AMF that can serve all the network slices requested by the UE.

[0004] Each UE can request one or more network slices simultaneously. However, depending on network configuration and vertical industry requirements, some of the network slices requested by the UE may be incompatible. Currently, there is no effective solution for how the network handles conflicting requests from a UE. Summary of the Invention

[0005] To solve existing technical problems, embodiments of the present invention provide a slice information processing method, apparatus, device, and storage medium.

[0006] To achieve the above-mentioned purpose, the technical solution of the embodiment of the present invention is implemented as follows:

[0007] In a first aspect, an embodiment of the present invention provides a method for processing slice information, the method comprising:

[0008] The NSSF obtains multiple network slice identifiers requested to be registered by the user equipment; the network slices corresponding to at least two network slice identifiers among the multiple network slice identifiers conflict;

[0009] The target AMF is selected based on the multiple network slice identifiers and the network slices supported by each access and mobility management function (AMF), and the network slice identifier corresponding to the network slice supported by the target AMF among the multiple network slice identifiers is used as the available network slice identifier, and the network slice identifier corresponding to the network slice not supported by the target AMF among the multiple network slice identifiers is used as the rejected network slice identifier.

[0010] In the above scheme, the NSSF obtains multiple network slice identifiers requested to be registered by the user equipment, including: the NSSF receives a request message sent by the initial AMF for reselecting the AMF; the request message includes the multiple network slice identifiers requested to be registered by the user equipment; the initial AMF does not support all network slices corresponding to the multiple network slice identifiers.

[0011] In the above scheme, the method also includes: the NSSF sends the information of the target AMF to the initial AMF, and sends the available network slice identifier and / or the rejected network slice identifier.

[0012] In the above solution, the selecting the target AMF based on the multiple network slice identifiers and the network slices supported by each AMF includes: the NSSF searching for the network slices supported by each AMF, and determining whether there is a network slice corresponding to the multiple network slice identifiers;

[0013] If there are network slices that support the network slices corresponding to the multiple network slice identifiers, the AMF that supports the network slices corresponding to the multiple network slice identifiers is used as the target AMF;

[0014] If there is no network slice supporting the network slices corresponding to the multiple network slice identifiers, the AMF that supports the largest number of network slices corresponding to the multiple network slice identifiers is used as the target AMF;

[0015] If there are at least two AMFs that support the largest number of network slices corresponding to the multiple network slice identifiers, a default AMF is selected as the target AMF from the at least two AMFs, or an AMF is randomly selected from the at least two AMFs as the target AMF.

[0016] In a second aspect, an embodiment of the present invention further provides a method for processing slice information, the method comprising:

[0017] After the network slice registration based on the target AMF is completed, the user equipment obtains the available network slice identifier and / or the rejected network slice identifier and the rejection reason value sent by the target AMF; the rejection reason value indicates that at least part of the network slice corresponding to the rejected network slice identifier conflicts with at least part of the network slice corresponding to the available network slice identifier; the target AMF is determined by the NSSF based on the multiple network slice identifiers requested to be registered by the user equipment and the network slice selection supported by each AMF;

[0018] When the user equipment determines that the network slice corresponding to the available network slice identifier does not meet the service requirements, it initiates a deregistration process.

[0019] In the above solution, the method also includes: the user equipment re-initiates a registration request for the network slice, and the registration request includes a network slice identifier that does not conflict.

[0020] In a third aspect, an embodiment of the present invention further provides a slice information processing device, the device comprising: an acquisition unit and a selection unit; wherein,

[0021] The acquisition unit is configured to obtain multiple network slice identifiers requested to be registered by the user equipment; the network slices corresponding to at least two of the multiple network slice identifiers conflict;

[0022] The selection unit is used to select a target AMF based on the multiple network slice identifiers and the network slices supported by each AMF, and use the network slice identifier corresponding to the network slice supported by the target AMF among the multiple network slice identifiers as an available network slice identifier, and use the network slice identifier corresponding to the network slice not supported by the target AMF among the multiple network slice identifiers as a rejected network slice identifier.

[0023] In the above scheme, the acquisition unit is used to receive a request message sent by the initial AMF for reselecting AMF; the request message includes the multiple network slice identifiers requested to be registered by the user equipment; the initial AMF does not support all network slices corresponding to the multiple network slice identifiers.

[0024] In the above scheme, the device also includes a sending unit for sending the information of the target AMF to the initial AMF, and sending the available network slice identifier and / or the rejected network slice identifier.

[0025] In the above scheme, the selection unit is used to search for network slices supported by each AMF and determine whether there are network slices supporting the corresponding multiple network slice identifiers; if there are network slices supporting the corresponding multiple network slice identifiers, the AMF supporting the network slices corresponding to the multiple network slice identifiers is used as the target AMF; if there are no network slices supporting the corresponding multiple network slice identifiers, the AMF supporting the largest number of network slices corresponding to the multiple network slice identifiers is used as the target AMF; if there are at least two AMFs supporting the largest number of network slices corresponding to the multiple network slice identifiers, a default AMF is selected from the at least two AMFs as the target AMF, or an AMF is randomly selected from the at least two AMFs as the target AMF.

[0026] In a fourth aspect, an embodiment of the present invention further provides a slice information processing device, the device comprising: a receiving unit and an executing unit; wherein,

[0027] The receiving unit is configured to obtain, after the network slice registration based on the target AMF is completed, an available network slice identifier and / or a rejected network slice identifier and a rejection reason value sent by the target AMF; the rejection reason value indicates that at least part of the network slice corresponding to the rejected network slice identifier conflicts with at least part of the network slice corresponding to the available network slice identifier; the target AMF is determined by the NSSF based on multiple network slice identifiers requested to be registered by the user equipment and the network slice selection supported by each AMF;

[0028] The execution unit is used to initiate a deregistration process when it is determined that the network slice corresponding to the available network slice identifier does not meet business requirements.

[0029] In the above scheme, the execution unit is also used to re-initiate a registration request for the network slice, and the registration request includes a network slice identifier that does not conflict.

[0030] In a fifth aspect, an embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the slice information processing method described in the first aspect or the second aspect of the embodiment of the present invention.

[0031] In a sixth aspect, an embodiment of the present invention further provides a communication device, comprising a memory, a processor, and a computer program stored in the memory and runnable on the processor, wherein when the processor executes the program, the steps of the slice information processing method described in the first or second aspect of the embodiment of the present invention are implemented.

[0032] The slice information processing method, apparatus, device and storage medium provided by the embodiment of the present invention include: NSSF obtains multiple network slice identifiers requested by a user device for registration; there is a conflict in the network slices corresponding to at least two of the multiple network slice identifiers; based on the multiple network slice identifiers and the network slices supported by each access and mobility management function (AMF), a target AMF is selected, and the network slice identifier corresponding to the network slice supported by the target AMF among the multiple network slice identifiers is used as an available network slice identifier, and the network slice identifier corresponding to the network slice not supported by the target AMF among the multiple network slice identifiers is used as a rejected network slice identifier. By adopting the technical solution of the embodiment of the present invention, when there are conflicting network slices among the multiple network slices requested by the user device for registration, that is, when the current AMF does not support all the network slices requested by the user device for registration, the NSSF re-selects a target AMF for the user device for slice service based on the network slice requested by the user device and the network slices supported by each AMF, thereby solving the problem of AMF selection and related slice information processing when there is a conflict among the multiple network slices requested by the user device for registration at the same time. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 Schematic diagram of the process of the slice information processing method according to an embodiment of the present invention Figure 1 ;

[0034] Figure 2 Schematic diagram of the process of the slice information processing method according to an embodiment of the present invention Figure 2 ;

[0035] Figure 3 Schematic diagram of the interactive process of the slice information processing method according to an embodiment of the present invention;

[0036] Figure 4 Schematic diagram of the structure of the slice information processing device according to an embodiment of the present invention Figure 1 ;

[0037] Figure 5 Schematic diagram of the structure of the slice information processing device according to an embodiment of the present invention Figure 2 ;

[0038] Figure 6 Schematic diagram of the hardware structure of the communication device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0039] The present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0040] An embodiment of the present invention provides a method for processing slice information. Figure 1 Schematic diagram of the process of the slice information processing method according to an embodiment of the present invention Figure 1 ;like Figure 1 As shown, the method includes:

[0041] Step 101: The NSSF obtains multiple network slice identifiers requested to be registered by a user equipment; the network slices corresponding to at least two of the multiple network slice identifiers conflict;

[0042] Step 102: Select a target AMF based on the multiple network slice identifiers and the network slices supported by each AMF, and use the network slice identifier corresponding to the network slice supported by the target AMF among the multiple network slice identifiers as the available network slice identifier, and use the network slice identifier corresponding to the network slice not supported by the target AMF among the multiple network slice identifiers as the rejected network slice identifier.

[0043] The premise of the embodiment of the present invention is that the user equipment (UE) requests to register at least two network slices at the same time, and there is a conflict between at least two network slices. The conflict between the two network slices means that the two network slices cannot be registered on the same AMF at the same time. For example, an enterprise campus deploys an enterprise network slice that is independent of the large network slice. For the purpose of data confidentiality, the enterprise network slice and the large network slice are independent of each other. That is, the enterprise slice will not be deployed on the AMF where the large network slice is deployed, and the large network slice (such as the enhanced mobile broadband (eMBB, Enhanced Mobile Broadband) slice) will not be deployed on the AMF where the enterprise slice is deployed. Then the enterprise network slice and the large network slice are two conflicting network slices.

[0044] In some optional embodiments of the present invention, the NSSF obtains multiple network slice identifiers requested to be registered by the user equipment, including: the NSSF receives a request message sent by the initial AMF for reselecting the AMF; the request message includes the multiple network slice identifiers requested to be registered by the user equipment; the initial AMF does not support all network slices corresponding to the multiple network slice identifiers.

[0045] In this embodiment, when the user equipment initiates the network slice registration process, it first sends a registration request to the Radio Access Network (RAN); the RAN selects an AMF for this registration request, and the AMF serves as the initial AMF. The registration request includes multiple network slice identifiers requested by the user equipment. The initial AMF checks whether its own capabilities support the network slices corresponding to the multiple network slice identifiers requested by the user equipment. After determining that its own capabilities do not support all the network slices requested by the user equipment, it initiates the AMF redirection process and sends a request message for reselecting the AMF to the NSSF. The request message includes multiple network slice identifiers requested by the user equipment.

[0046] Among them, exemplarily, the network slice identifier can be single network slice selection assistance information (S-NSSAI, Single Network Slice Selection Assistance Information).

[0047] In this embodiment, NSSF reselects an AMF as the target AMF based on the capabilities of each AMF (i.e., the supported network slices) and the multiple network slice identifiers requested to be registered by the user equipment.

[0048] Specifically, in some optional embodiments of the present invention, the target AMF is selected based on the multiple network slice identifiers and the network slices supported by each AMF, including: the NSSF searches for the network slices supported by each AMF, and determines whether there are network slices corresponding to the multiple network slice identifiers; if there are network slices corresponding to the multiple network slice identifiers, the AMF that supports the network slices corresponding to the multiple network slice identifiers is used as the target AMF; if there are no network slices corresponding to the multiple network slice identifiers, the AMF that supports the largest number of network slices corresponding to the multiple network slice identifiers is used as the target AMF; if there are at least two AMFs that support the largest number of network slices corresponding to the multiple network slice identifiers, a default AMF is selected as the target AMF from the at least two AMFs, or an AMF is randomly selected from the at least two AMFs as the target AMF.

[0049] In this embodiment, NSSF can search for network slices supported by each AMF based on multiple network slices requested by the user device. If there is an AMF that can support all network slices requested by the user device, the AMF will be used as the target AMF; if there is no AMF that can support all network slices requested by the user device, the AMF that supports the largest number of network slices among the multiple network slices requested by the user device will be used as the target AMF; if there are at least two AMFs that support the largest number of network slices, the default AMF can be selected as the target AMF based on the configuration of at least two AMFs, that is, one of the AMFs is configured as the default AMF; or an AMF can be randomly selected as the target AMF.

[0050] In this embodiment, the NSSF may select the network slice identifier requested by the user device and supported by the target AMF as the available network slice identifier based on the network slices supported by the target AMF and the network slices requested by the user device. The available network slice identifier may also be referred to as the allowed network slice identifier. Exemplarily, the allowed network slice identifier may be recorded as allowed (Allowed NSSAI). Correspondingly, the network slice identifier requested by the user device and not supported by the target AMF is used as a rejected network slice identifier. Exemplarily, the rejected network slice identifier may be recorded as reject S-NSSAI (reject S-NSSAIs).

[0051] In some optional embodiments of the present invention, the method further includes: the NSSF sending the information of the target AMF to the initial AMF, and sending the available network slice identifier and / or the rejected network slice identifier.

[0052] In this embodiment, the NSSF sends the information of the target AMF to the initial AMF, as well as the available network slice identifier and / or the rejected network slice identifier, so that the initial AMF sends a rerouting message to the target AMF, so that the user equipment can perform a normal registration process based on the rerouting message.

[0053] Based on the above embodiments, an embodiment of the present invention further provides a slice information processing method. Figure 2 Schematic diagram of the process of the slice information processing method according to an embodiment of the present invention Figure 2 ;like Figure 2 As shown, the method includes:

[0054] Step 201: After the network slice registration based on the target AMF is completed, the user equipment obtains the available network slice identifier and / or the rejected network slice identifier and the rejection reason value sent by the target AMF; the rejection reason value indicates that at least part of the network slice corresponding to the rejected network slice identifier conflicts with at least part of the network slice corresponding to the available network slice identifier; the target AMF is determined by the NSSF based on the multiple network slice identifiers requested to be registered by the user equipment and the network slices supported by each AMF;

[0055] Step 202: When the user equipment determines that the network slice corresponding to the available network slice identifier does not meet the service requirements, it initiates a deregistration process.

[0056] Based on the above embodiment, in this embodiment, after the network slice registration is completed based on the redirected target AMF, the target AMF sends an available network slice identifier to the user equipment. The available network slice identifier represents the network slice identifier requested by the user equipment to be registered and supported by the target AMF; the rejected network slice identifier represents the network slice identifier requested by the user equipment to be registered and not supported by the target AMF.

[0057] In this embodiment, when the user equipment determines that the network slice corresponding to the available network slice identifier does not meet the service requirements, that is, when the target AMF does not meet the service requirements of the user equipment, the user equipment initiates a deregistration process.

[0058] In some optional embodiments of the present invention, the method further includes: the user equipment re-initiating a registration request for the network slice, and the registration request includes a network slice identifier with no conflict.

[0059] In this embodiment, when the user device re-initiates a registration request for the network slice, considering that the rejected network slice identifier fed back by the target AMF, and the corresponding rejection reason value is that there is a conflict between at least part of the network slice corresponding to the rejected network slice identifier and at least part of the network slice corresponding to the available network slice identifier, the registration request does not carry the conflicting network slice identifier, that is, only the network slice identifier without conflict is carried.

[0060] By adopting the technical solution of the embodiment of the present invention, when there are conflicting network slices among the multiple network slices requested to be registered by the user equipment, that is, when the current AMF does not support all the network slices requested to be registered by the user equipment, the NSSF re-selects a target AMF for the user equipment to provide slice services based on the network slices requested by the user equipment and the network slices supported by each AMF, thereby solving the selection of AMF and the processing of related slice information when there are conflicts among the multiple network slices requested to be registered by the user equipment at the same time.

[0061] The following describes the slice information processing method according to an embodiment of the present invention with reference to a specific example.

[0062] Figure 3 FIG. 1 is a schematic diagram of an interactive process of a slice information processing method according to an embodiment of the present invention; FIG. Figure 3 As shown, the method includes:

[0063] Step 301: The UE initiates a registration request to the RAN, wherein the registration request is used to request registration of a network slice. The registration request includes an AN message, which includes a requested network slice identifier. The requested network slice identifier may be, for example, a requested NSSAI, which includes at least two S-NSSAIs, and at least two of the S-NSSAIs conflict.

[0064] Step 302: RAN selects an initial AMF.

[0065] Among them, if the registration request includes 5G-S-TMSI or a globally unique AMF identifier (GUAMI), the RAN can select an AMF as the initial AMF based on the 5G-S-TMSI or GUAMI; if the registration request does not include 5G-S-TMSI or GUAMI, the RAN selects an AMF as the initial AMF according to the configuration.

[0066] Among them, GUAMI is used to uniquely identify an AMF. 5G-S-TMSI is the short form of 5G Globally Unique Temporary UE Identity (5G-GUTI).

[0067] Step 303: RAN sends an N2 message to the initial AMF. The N2 message carries the above-mentioned registration request for registering the network slice. Accordingly, the registration request includes the above-mentioned Requested NSSAI, and the Requested NSSAI includes at least two conflicting S-NSSAIs.

[0068] Step 304: The initial AMF checks whether it can serve all network slice identifiers in the Requested NSSAI requested by the UE. If it is determined that it cannot serve all network slice identifiers requested by the UE, the initial AMF initiates a redirection process and sends a request message to the NSSF. The request message is used to request an appropriate AMF. Exemplarily, the request message can be an Nnssf_NSSelection_Get message. The request message includes the at least two conflicting S-NSSAIs.

[0069] Step 305: The NSSF reselects a suitable AMF as the target AMF for the UE based on at least two S-NSSAIs and the network slice identifiers supported by each AMF.

[0070] Specifically, first, NSSF searches for the network slice identifiers supported by each AMF to determine whether there is an AMF that can support the above-mentioned at least two S-NSSAIs; if it is determined that there is an AMF that can support the above-mentioned at least two S-NSSAIs, the AMF that can support the above-mentioned at least two S-NSSAIs will be used as the target AMF; if it is determined that there is no AMF that can support the above-mentioned at least two S-NSSAIs, the number of slices that can serve the above-mentioned at least two S-NSSAIs in each AMF is compared, and the AMF that supports the largest number of network slices corresponding to the at least two S-NSSAIs is used as the target AMF; if there are at least two AMFs that support the largest number of network slices corresponding to the at least two S-NSSAIs, a default AMF is selected from the at least two AMFs as the target AMF, or an AMF is randomly selected as the target AMF; if there is no default AMF among the at least two AMFs, an AMF is randomly selected as the target AMF.

[0071] Furthermore, after NSSF determines the target AMF, it takes the S-NSSAI supported by the target AMF among the multiple at least two S-NSSAIs as the identifier corresponding to the initial available network slice, and intersects the identifier corresponding to the initial available network slice with the network slice identifier subscribed by the UE, thereby obtaining the available network slice identifier in the above embodiment, that is, the allowed NSSAI (Allowed NSSAI).

[0072] Step 306: NSSF sends a response message corresponding to the above request message to the initial AMF, and the response message includes the information of the target AMF and the above available network slice identifier (i.e., Allowed NSSAI).

[0073] Exemplarily, the response message may specifically be a Response to Nnssf_NSSelection_Get message.

[0074] Step 307: The initial AMF sends a notification message to the target AMF, where the notification message carries a rerouting message.

[0075] Exemplarily, the notification message may specifically be a Namf_Communication_N1MessageNotify message; and the rerouting message may specifically be a rerouted non-access stratum message (rerouted NAS message).

[0076] Step 308: The UE performs a normal registration process.

[0077] Step 309: After the registration process is successful, the target AMF sends a registration accept message to the UE. The registration accept message may include an available network slice identifier (i.e., Allowed NSSAI) and / or a rejected network slice identifier (reject S-NSSAIs) and a reject cause value (reject cause value); the reject cause value indicates that at least part of the network slice corresponding to the rejected network slice identifier conflicts with at least part of the network slice corresponding to the available network slice identifier. Exemplarily, the registration accept message may be a UE Registration Accept message.

[0078] Step 310: The UE determines whether the available network slice identifier can meet its own business needs. If it does not meet its own business needs, the UE initiates a deregistration process.

[0079] Here, the UE checks whether the network slice corresponding to the service it wants to request is included in the available network slice identifier (i.e., Allowed NSSAI); if the network slice corresponding to the service it wants to request is not included in the available network slice identifier (i.e., AllowedNSSAI), it is considered that the available network slice identifier cannot meet the service requirements, and the UE initiates the deregistration process.

[0080] Step 311: The UE re-initiates a registration request, considers the previously returned information to determine the conflict between slices, and carries a non-conflicting S-NSSAI in the Requested NSSAI to re-request registration.

[0081] An embodiment of the present invention further provides a slice information processing device, which is applied in NSSF. Figure 4 Schematic diagram of the structure of the slice information processing device according to an embodiment of the present invention Figure 1 ;like Figure 4 As shown, the device includes: an acquisition unit 41 and a selection unit 42; wherein,

[0082] The acquiring unit 41 is configured to obtain multiple network slice identifiers requested to be registered by a user equipment; the network slices corresponding to at least two of the multiple network slice identifiers conflict;

[0083] The selection unit 42 is used to select a target AMF based on the multiple network slice identifiers and the network slices supported by each AMF, and use the network slice identifier corresponding to the network slice supported by the target AMF among the multiple network slice identifiers as an available network slice identifier, and use the network slice identifier corresponding to the network slice not supported by the target AMF among the multiple network slice identifiers as a rejected network slice identifier.

[0084] In some optional embodiments of the present invention, the acquisition unit 41 is used to receive a request message sent by the initial AMF for reselecting the AMF; the request message includes the multiple network slice identifiers requested to be registered by the user equipment; and the initial AMF does not support all network slices corresponding to the multiple network slice identifiers.

[0085] In some optional embodiments of the present invention, the device further includes a sending unit for sending the information of the target AMF to the initial AMF, and sending the available network slice identifier and / or the rejected network slice identifier.

[0086] In some optional embodiments of the present invention, the selection unit 42 is used to search for network slices supported by each AMF, and determine whether there are network slices supporting the corresponding multiple network slice identifiers; if there are network slices supporting the corresponding multiple network slice identifiers, the AMF supporting the network slices corresponding to the multiple network slice identifiers is used as the target AMF; if there are no network slices supporting the corresponding multiple network slice identifiers, the AMF supporting the largest number of network slices corresponding to the multiple network slice identifiers is used as the target AMF; if there are at least two AMFs supporting the largest number of network slices corresponding to the multiple network slice identifiers, a default AMF is selected from the at least two AMFs as the target AMF, or an AMF is randomly selected from the at least two AMFs as the target AMF.

[0087] In an embodiment of the present invention, the selection unit 42 in the device can be implemented by a central processing unit (CPU), a digital signal processor (DSP), a microcontroller unit (MCU) or a programmable gate array (FPGA) in actual applications; the acquisition unit 41 and the sending unit in the device can be implemented by a communication module (including: basic communication kit, operating system, communication module, standardized interface and protocol, etc.) and a transceiver antenna in actual applications.

[0088] An embodiment of the present invention also provides a slice information processing device, which is applied to a user device. Figure 5 Schematic diagram of the structure of the slice information processing device according to an embodiment of the present invention Figure 2 ;like Figure 5 As shown, the device includes: a receiving unit 51 and an execution unit 52; wherein,

[0089] The receiving unit 51 is configured to obtain, after the network slice registration based on the target AMF is completed, an available network slice identifier and / or a rejected network slice identifier and a rejection reason value sent by the target AMF; the rejection reason value indicates that at least part of the network slice corresponding to the rejected network slice identifier conflicts with at least part of the network slice corresponding to the available network slice identifier; the target AMF is determined by the NSSF based on multiple network slice identifiers requested to be registered by the user equipment and the network slice selection supported by each AMF;

[0090] The execution unit 52 is used to initiate a deregistration process when it is determined that the network slice corresponding to the available network slice identifier does not meet business requirements.

[0091] In some optional embodiments of the present invention, the execution unit 52 is also used to re-initiate a registration request for the network slice, and the registration request includes a network slice identifier that does not conflict.

[0092] In an embodiment of the present invention, the execution unit 52 in the device can be implemented by a CPU, DSP, MCU or FPGA in actual applications; the receiving unit 51 in the device can be implemented by a communication module (including: basic communication kit, operating system, communication module, standardized interface and protocol, etc.) and a transceiver antenna in actual applications.

[0093] It should be noted that the slice information processing device provided in the above embodiment only uses the division of the aforementioned program modules as an example to illustrate slice information processing. In actual applications, the aforementioned processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the aforementioned processing. In addition, the slice information processing device provided in the above embodiment and the slice information processing method embodiment are based on the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0094] An embodiment of the present invention further provides a communication device, which may specifically be the NSSF or user equipment in the aforementioned embodiment. Figure 6 FIG. 1 is a schematic diagram of the hardware structure of a communication device according to an embodiment of the present invention. Figure 6 As shown, the communication device includes a memory 62, a processor 61, and a computer program stored in the memory 62 and executable on the processor 61. When the processor 61 executes the program, the steps of the slice information processing method applied to the NSSF in the embodiment of the present invention are implemented. Alternatively, when the processor 61 executes the program, the steps of the slice information processing method applied to the user equipment in the embodiment of the present invention are implemented.

[0095] Optionally, the communication device further includes a network interface 63. The various components in the communication device can be coupled together via a bus system 64. It is understood that the bus system 64 is used to achieve connection and communication between these components. In addition to the data bus, the bus system 64 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Figure 6 Various buses are labeled as bus system 64.

[0096] It is understood that the memory 62 can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a flash memory, a magnetic surface memory, an optical disk, or a compact disc read-only memory (CD-ROM); the magnetic surface memory can be a magnetic disk or a magnetic tape. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), synchronous static random access memory (SSRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus random access memory (DRRAM).The memory 62 described in the embodiments of the present invention is intended to include, but is not limited to, these and any other suitable types of memory.

[0097] The methods disclosed in the above embodiments of the present invention can be applied to or implemented by processor 61. Processor 61 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by hardware integrated logic circuits in processor 61 or by software instructions. The above processor 61 may be a general-purpose processor, a DSP, or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc. Processor 61 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present invention. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of the present invention can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium located in memory 62. Processor 61 reads information from memory 62 and, in conjunction with its hardware, completes the steps of the above method.

[0098] In an exemplary embodiment, the communication device may be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), FPGAs, general-purpose processors, controllers, MCUs, microprocessors, or other electronic components to perform the aforementioned method.

[0099] In an exemplary embodiment, the present invention further provides a computer-readable storage medium, such as a memory 62 including a computer program. The computer program can be executed by a processor 61 of a communication device to perform the steps of the aforementioned method. The computer-readable storage medium can be a memory device such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface mount storage, optical disk, or CD-ROM; or various devices including any one or any combination of the aforementioned memory devices.

[0100] An embodiment of the present invention also provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the steps of the slice information processing method applied to NSSF in the embodiment of the present invention are implemented, or when the program is executed by a processor, the steps of the slice information processing method applied to user equipment in the embodiment of the present invention are implemented.

[0101] The methods disclosed in the several method embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments.

[0102] The features disclosed in the several product embodiments provided in this application can be arbitrarily combined without conflict to obtain new product embodiments.

[0103] The features disclosed in the several method or device embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments or device embodiments.

[0104] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as: multiple units or components can be combined, or can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed can be through some interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.

[0105] The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units; some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0106] In addition, all functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be separately used as a unit, or two or more units may be integrated into one unit; the above-mentioned integrated units may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0107] Those skilled in the art will understand that all or part of the steps of implementing the above-mentioned method embodiment can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps of the above-mentioned method embodiment; and the aforementioned storage medium includes: mobile storage devices, ROM, RAM, disks or optical disks, etc. Various media that can store program codes.

[0108] Alternatively, if the above-mentioned integrated unit of the present invention is implemented in the form of a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the methods described in each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROM, RAM, magnetic disks or optical disks.

[0109] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any modifications or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present invention should be included in the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims.

Claims

1. A slice information processing method, characterized in that: The method comprises: The network slice selection function NSSF obtains multiple network slice identifiers requested to be registered by the user equipment; the network slices corresponding to at least two of the multiple network slice identifiers conflict; the multiple network slice identifiers are from the initial AMF, and the initial AMF does not support all network slices corresponding to the multiple network slice identifiers; The target AMF is selected based on the multiple network slice identifiers and the network slices supported by each access and mobility management function AMF, and the network slice identifier corresponding to the network slice supported by the target AMF among the multiple network slice identifiers is used as the available network slice identifier, and the network slice identifier corresponding to the network slice not supported by the target AMF among the multiple network slice identifiers is used as the rejected network slice identifier.

2. The method according to claim 1, characterized in that The NSSF obtains multiple network slice identifiers requested to be registered by the user equipment, including: The NSSF receives a request message sent by the initial AMF for reselecting the AMF; the request message includes the multiple network slice identifiers that the user equipment requests to register.

3. The method according to claim 2, characterized in that The method further comprises: The NSSF sends the information of the target AMF to the initial AMF, as well as the available network slice identifier and / or the rejected network slice identifier.

4. The method according to claim 1, wherein The selecting a target AMF based on the multiple network slice identifiers and the network slices supported by each AMF includes: The NSSF searches for network slices supported by each AMF, and determines whether there is a network slice corresponding to the multiple network slice identifiers; If there are network slices that support the network slices corresponding to the multiple network slice identifiers, the AMF that supports the network slices corresponding to the multiple network slice identifiers is used as the target AMF; If there is no network slice supporting the network slices corresponding to the multiple network slice identifiers, the AMF that supports the largest number of network slices corresponding to the multiple network slice identifiers is used as the target AMF; If there are at least two AMFs that support the largest number of network slices corresponding to the multiple network slice identifiers, a default AMF is selected as the target AMF from the at least two AMFs, or an AMF is randomly selected from the at least two AMFs as the target AMF.

5. A slice information processing method, characterized in that: The method comprises: After the network slice registration based on the target AMF is completed, the user equipment obtains the available network slice identifier and / or the rejected network slice identifier and the rejection reason value sent by the target AMF; the rejection reason value indicates that at least part of the network slice corresponding to the rejected network slice identifier conflicts with at least part of the network slice corresponding to the available network slice identifier; the target AMF is determined by the NSSF based on the multiple network slice identifiers requested to be registered by the user equipment and the network slice selection supported by each AMF; the multiple network slice identifiers come from the initial AMF, and the initial AMF does not support all network slices corresponding to the multiple network slice identifiers; When the user equipment determines that the network slice corresponding to the available network slice identifier does not meet the business requirements, it initiates a deregistration process.

6. The method according to claim 5, characterized in that The method further comprises: The user equipment re-initiates a registration request for the network slice, and the registration request includes a network slice identifier in which no conflict exists.

7. A slice information processing device, characterized in that: The device comprises: an acquisition unit and a selection unit; wherein, The acquisition unit is configured to obtain multiple network slice identifiers requested to be registered by the user equipment; the network slices corresponding to at least two of the multiple network slice identifiers conflict; the multiple network slice identifiers are from an initial AMF, and the initial AMF does not support all network slices corresponding to the multiple network slice identifiers; The selection unit is used to select a target AMF based on the multiple network slice identifiers and the network slices supported by each AMF, and use the network slice identifier corresponding to the network slice supported by the target AMF among the multiple network slice identifiers as an available network slice identifier, and use the network slice identifier corresponding to the network slice not supported by the target AMF among the multiple network slice identifiers as a rejected network slice identifier.

8. The device according to claim 7, characterized in that The acquisition unit is used to receive a request message sent by the initial AMF for reselecting the AMF; the request message includes the multiple network slice identifiers requested to be registered by the user equipment; the initial AMF does not support all network slices corresponding to the multiple network slice identifiers.

9. The device according to claim 8, characterized in that The device also includes a sending unit for sending the information of the target AMF to the initial AMF, and sending the available network slice identifier and / or the rejected network slice identifier.

10. The device according to claim 7, characterized in that The selection unit is configured to search for network slices supported by each AMF, and determine whether there is a network slice supporting the network slices corresponding to the multiple network slice identifiers; if there is a network slice supporting the network slices corresponding to the multiple network slice identifiers, the AMF supporting the network slices corresponding to the multiple network slice identifiers is used as the target AMF; If there is no network slice supporting the network slices corresponding to the multiple network slice identifiers, the AMF that supports the largest number of network slices corresponding to the multiple network slice identifiers is used as the target AMF; If there are at least two AMFs that support the largest number of network slices corresponding to the multiple network slice identifiers, a default AMF is selected as the target AMF from the at least two AMFs, or an AMF is randomly selected from the at least two AMFs as the target AMF.

11. A slice information processing device, characterized in that: The device comprises: a receiving unit and an executing unit; wherein, The receiving unit is configured to obtain, after the network slice registration based on the target AMF is completed, an available network slice identifier and / or a rejected network slice identifier and a rejection reason value sent by the target AMF; the rejection reason value indicates that at least part of the network slices corresponding to the rejected network slice identifier conflict with at least part of the network slices corresponding to the available network slice identifier; the target AMF is determined by the NSSF based on multiple network slice identifiers requested to be registered by the user equipment and the network slice selection supported by each AMF; the multiple network slice identifiers come from the initial AMF, and the initial AMF does not support all network slices corresponding to the multiple network slice identifiers; The execution unit is used to initiate a deregistration process when it is determined that the network slice corresponding to the available network slice identifier does not meet business requirements.

12. The device according to claim 11, characterized in that The execution unit is also used to re-initiate a registration request for the network slice, and the registration request includes a network slice identifier that does not conflict.

13. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the steps of the method according to any one of claims 1 to 4 are implemented; or, when the program is executed by a processor, the steps of the method according to claim 5 or 6 are implemented.

14. A communication 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 program, the steps of the method according to any one of claims 1 to 4 are implemented; or, when the processor executes the program, the steps of the method according to claim 5 or 6 are implemented.

Images