CN109246813B

CN109246813B - Network slice mutual exclusion relation processing method, equipment and system

Info

Publication number: CN109246813B
Application number: CN201810777456.7A
Authority: CN
Inventors: 涂小勇; 叶敏雅
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2018-07-16
Filing date: 2018-07-16
Publication date: 2020-03-31
Anticipated expiration: 2038-07-16
Also published as: WO2020015649A1; CN109246813A

Abstract

The application discloses a method, a device and a system for processing network slice mutual exclusion relationship, wherein the method for processing the network slice mutual exclusion relationship comprises the following steps: and determining an allowed single network slice selection auxiliary information S-NSSAI list for the terminal, wherein the priority and mutual exclusion relation between the S-NSSAIs in the allowed S-NSSAI list meets a preset rule. By the method provided by at least one embodiment of the present invention, since the priority and the mutual exclusion relationship between the S-NSSAIs in the running S-NSSAI list satisfy the preset rule, the UE does not need to identify the priority and the mutual exclusion relationship between the slices, thereby simplifying the processing of the UE.

Description

Network slice mutual exclusion relation processing method, equipment and system

Technical Field

The embodiment of the invention relates to but is not limited to a network slice mutual exclusion relation processing method, equipment and system.

Background

Mobile communication has been currently developed to the 5G (5th Generation) stage. Compared with the previous generations, the network architecture of 5G is mainly characterized by a service-based architecture.

Fig. 1 is a schematic diagram of a 5G network architecture in the related art. As shown in fig. 1, the functions of each network element in the 5G network architecture are as follows:

a terminal (UE) mainly accesses to a 5G network through a wireless air interface and obtains services, and the terminal exchanges information with a base station through the air interface and exchanges information with an Access and Mobility Management function (AMF) of a core network through a Non-Access Stratum (NAS) signaling.

A Radio Access Network (RAN) is responsible for scheduling air interface resources of a terminal Access Network and managing connection of air interfaces.

Access and mobility management functions: the core network control plane entity is mainly responsible for user mobility management, including registration and temporary identifier allocation; maintaining IDLE (IDLE) and connected (CONNECT) states and state transitions; switching in the CONNECT state; and triggering functions such as paging and the like in the IDLE state of the user.

Authentication Server Function (AUSF): the core network control plane entity is mainly responsible for authentication and authorization of the user so as to ensure that the user is a legal user.

The Unified Data Management function (UDM) is a core network control plane entity, a home subscriber server and permanently stores subscriber subscription Data.

Session Management Function (SMF): a core network control plane entity, which is mainly responsible for maintaining a Protocol Data Unit (PDU) Session, is responsible for allocating a user IP address, and has Quality of Service (QoS) control and charging functions; and receiving the downlink data packet in the IDLE state of the user, caching the downlink data packet, and informing the AMF to page the user.

User Plane Function (UPF): the core network user plane functional entity is responsible for forwarding the user data message, and also has the functions of counting the user data message, charging and the like.

Policy Control Function (PCF): the core network control plane entity is responsible for a policy and charging rule function entity, and the function entity mainly generates a QoS rule, a charging rule and a mobile and access control rule for controlling user data transmission according to the service information, the user subscription information and the configuration information of an operator.

Capability opening Function (NEF), Network Exposure Function: and the core network control plane entity is responsible for opening the mobile network capability to the outside.

Network Function library Function (NRF, NF repetition Function): and the core network control plane entity is responsible for dynamic registration of service capability of the network function and network function discovery.

Network Slice Selection Function (NSSF): and the core Network control plane entity is responsible for selecting the target NSI (Network Slice Instance).

The 5G network supports various scenes, and different scenes have different requirements on the functions and the performances of the network. The network slice can lead an operator to cut out a plurality of virtual logical end-to-end networks on the same hardware infrastructure according to the requirement, each network slice is isolated logically, adapts to different characteristic requirements of various types of services, and simultaneously meets different requirements of high bandwidth, low time delay, super-large connection and multiple services on the network.

After network slicing, in order to better use network resources, different priorities can be set for different network slices, and resource application and use of high-priority network slices are preferentially guaranteed.

Disclosure of Invention

At least one embodiment of the invention provides a method, equipment and a system for processing network slice mutual exclusion relationship, which are used for realizing network slice mutual exclusion relationship processing.

At least one embodiment of the present invention provides a method for processing mutual exclusion relationship of network slices, including:

and determining an allowed single network slice selection auxiliary information S-NSSAI list for the terminal, wherein the priority and mutual exclusion relation between the S-NSSAIs in the allowed S-NSSAI list meets a preset rule.

At least one embodiment of the present invention provides a network slice mutual exclusion relationship processing device, including a memory and a processor, where the memory stores a program, and the program, when read and executed by the processor, implements the network slice mutual exclusion relationship processing method according to any embodiment.

At least one embodiment of the present invention provides a computer-readable storage medium, which is characterized by storing one or more programs, wherein the one or more programs are executable by one or more processors to implement the network slice mutual exclusion relationship processing method according to any embodiment.

At least one embodiment of the present invention provides a network slice mutual exclusion relationship processing system, including: access and mobility management functions, network slice selection functions, wherein:

the access and mobility management function is configured to send a network slice selection request message to the network slice selection function;

and the network slice selection function is used for determining an allowed S-NSSAI list for the terminal after receiving the network slice selection request message, wherein the priority and the mutual exclusion relationship among the S-NSSAIs in the allowed S-NSSAI list meet a preset rule.

Compared with the related art, in at least one embodiment of the present invention, an allowed single network slice selection assistance information S-NSSAI list is determined for a terminal, and a priority and a mutual exclusion relationship between S-NSSAIs in the allowed S-NSSAI list satisfy a preset rule. Because the priority and the mutual exclusion relationship between the S-NSSAIs in the Allowed S-NSSAIs meet the preset rule, the UE does not need to identify the priority and the mutual exclusion relationship between the slices, and the processing of the UE is simplified.

Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

Drawings

The accompanying drawings are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the example serve to explain the principles of the invention and not to limit the invention.

FIG. 1 is a diagram of a 5G network architecture of the related art;

FIG. 2 is a flowchart illustrating a method for processing mutual exclusion relationships of network slices according to an embodiment of the present invention;

FIG. 3 is a flowchart illustrating an implementation of mutual exclusion relationship between slices by NSSF decision during registration according to an embodiment of the present invention;

FIG. 4 is a flowchart illustrating AMF decision-based mutual exclusion relationship between slices during registration according to an embodiment of the present invention;

FIG. 5 is a flowchart illustrating implementation of mutual exclusion relationship between slices in a PDU session establishment procedure according to an embodiment of the present invention;

fig. 6 is a flowchart illustrating implementation of mutual exclusion relationship between slices in a PDU session release process according to an embodiment of the present invention;

FIG. 7 is a block diagram of a network slice mutual exclusion relationship processing apparatus according to an embodiment of the present invention;

fig. 8 is a block diagram of a system for processing mutual exclusion relationship of network slices according to an embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that the embodiments and features of the embodiments in the present application may be arbitrarily combined with each other without conflict.

The steps illustrated in the flow charts of the figures may be performed in a computer system such as a set of computer-executable instructions. Also, while a logical order is shown in the flow diagrams, in some cases, the steps shown or described may be performed in an order different than here.

For the same user, multiple network slices may be accessed, for example, an eMBB (enhanced mobile broadband) slice and a URLLC (Ultra Reliable & Low Latency Communication) slice may be accessed. However, there are some scenarios where there is mutual exclusion relationship between network slices, including mutual exclusion between network slices of the same priority and mutual exclusion relationship between network slices of different priorities. For example, if the user has accessed the URLLC slice, eMBB slices are prohibited from being accessed simultaneously; or the user has accessed the eMB slice with low priority, if the URLLC slice with higher priority needs to be accessed, the accessed eMB slice needs to be deactivated first, or the user has accessed the URLLC slice with high priority, the eMB slice with lower priority needs to be accessed by the UE is forbidden. However, the current standard does not define how to implement the mutual exclusion relationship between the network slices of the same priority or different priorities. In the application, a network slice mutual exclusion relationship processing method is provided, so that the UE can realize mutual exclusion between network slices with the same priority or different priorities without identifying the priority information of the network slices, and the method is complementary and perfected on a standard protocol.

Hereinafter, S-NSSAI (Single-Network Slice Selection Assistance Information) is Network Slice identification Information, and each S-NSSAI identifies one Network Slice.

In the present application, the system architecture refers to fig. 1, which is not described herein again.

As shown in fig. 2, an embodiment of the present invention provides a method for processing mutual exclusion relationship of network slices, including:

step 201, selecting an auxiliary information S-NSSAI list for a single network slice determined to be allowed by a terminal, where priority and mutual exclusion relationship between S-NSSAIs in the S-NSSAI list satisfy a preset rule.

In an embodiment, the satisfying of the predetermined rule by the priority and mutual exclusion relationship between the S-NSSAIs in the allowed S-NSSAI list includes that any first S-NSSAI and second S-NSSAI in the allowed S-NSSAI list satisfy:

rule 1, the first S-NSSAI and the second S-NSSAI have no mutually exclusive relationship;

or, rule 2, the first S-NSSAI and the second S-NSSAI have a mutual exclusion relationship, and the first S-NSSAI does not have an accessed NSI corresponding to the terminal, and the second S-NSSAI does not have an accessed NSI corresponding to the terminal;

or, rule 3, the first S-NSSAI and the second S-NSSAI have a mutual exclusion relationship, and one of the first S-NSSAI and the second S-NSSAI has an accessed NSI corresponding to the terminal, and the other has no accessed NSI corresponding to the terminal, and the priority of the S-NSSAI without the accessed NSI corresponding to the terminal is higher than the priority of the S-NSSAI with the accessed NSI corresponding to the terminal. For example, the first S-NSSAI has an accessed NSI corresponding to the terminal, the second S-NSSAI does not have an accessed NSI corresponding to the terminal, and the priority of the second S-NSSAI is higher than that of the first S-NSSAI; or the first S-NSSAI does not have an accessed NSI corresponding to the terminal, the second S-NSSAI has an accessed NSI corresponding to the terminal, and the priority of the first S-NSSAI is higher than that of the second S-NSSAI;

any first S-NSSAI and second S-NSSAI in the S-NSSAI list may satisfy only rule 1, may satisfy only rule 2, and may satisfy only rule 3, or a portion of S-NSSAIs in the S-NSSAI list satisfies rule 1 and a portion of S-NSSAIs satisfies rule 2, or a portion of S-NSSAIs in the S-NSSAI list satisfies rule 1 and a portion of S-NSSAIs satisfies rule 3, or a portion of S-NSSAIs in the S-NSSAI list satisfies rule 2 and a portion of S-NSSAI satisfies rule 3, or a portion of S-NSSAIs in the S-NSSAI list satisfies rule 1, a portion of S-NSSAIs satisfies rule 2, and a portion of S-NSSAI satisfies rule 3.

It should be noted that the preset rules are only examples, and other rules may be set as needed.

Wherein the allowed S-NSSAI list may be determined by the NSSF or AMF for the terminal.

In an embodiment, the determining an allowed list of single network slice selection assistance information S-NSSAI for the terminal includes:

determining a list of allowed S-NSSAIs for the terminal based on the S-NSSAI (S) (which may be one or more S-NSSAIs) requested by the terminal, the subscribed S-NSSAI (S) (which may be one or more S-NSSAIs) and the accessed NSI (S) (which may be one or more NSIs); for example, when the terminal registers, the terminal determines an allowed S-NSSAI list according to the information, where the accessed NSI may send the allowed S-NSSAI list to the NSSF through a network slice selection request message by the AMF. In addition, when determining the allowed S-NSSAI list, reference is also made to the current location (TA) of the terminal, the terminal identity (SUPI), and the like. The above information may be carried in a network slice selection request message.

Alternatively, the first and second electrodes may be,

and re-determining the allowed S-NSSAI list for the terminal according to the existing allowed S-NSSAI list and the NSI accessed by the terminal. For example, in the PDU session establishment or PDU release process, since the NSI changes, the allowed S-NSSAI list needs to be re-determined, at this time, the AMF sends the existing allowed S-NSSAI list and the NSI accessed by the terminal to the NSSF through the network slice selection request message, and the NSSF re-determines the allowed S-NSSAI list according to the existing allowed S-NSSAI list and the NSI accessed by the terminal.

In an embodiment, before determining the allowed S-NSSAI list for the terminal, the method further includes: acquiring the NSI accessed by the terminal from a network slice selection request message sent by the AMF, or acquiring the list of the existing allowed S-NSSAIs and the NSI accessed by the terminal.

In an embodiment, after determining the allowed S-NSSAI list for the terminal, the method further includes:

and when the determined allowed S-NSSAI list for the terminal is not consistent with the existing allowed S-NSSAI list, the NSSF sends the determined allowed S-NSSAI list for the terminal to the terminal through the AMF.

In an embodiment, the determining the allowed S-NSSAI list for the terminal includes:

and when the terminal is registered or the PDU Session of the terminal is changed, determining an allowed S-NSSAI list for the terminal. Wherein the PDU Session change of the terminal includes at least one of: and establishing PDU Session and releasing PDUSESS.

That is, when the user registers or the user slice needs to be modified, Allowed S-nsais (i.e., an Allowed S-nsai list) needs to be decided for the terminal, and it is required to ensure that preset rules are satisfied among S-nsais in the Allowed S-nsais, for example, any two S-nsais in the Allowed S-nsais satisfy one of rules 1 to 3.

In the process of PDU session release and other processes that may cause PDU session release, Allowed S-nsais may change, and Allowed S-nsais needs to be re-decided for the UE, and any two S-nsais in the re-decided Allowed S-nsais satisfy a preset rule, for example, any two S-nsais in the Allowed S-nsais satisfy one of rules 1 to 3.

In other processes that may cause the change of Allowed S-nsais or the access PDU Session of the user, the Allowed S-nsais needs to be re-determined for the UE, the Allowed S-nsais may be changed, the Allowed S-nsais needs to be re-determined for the UE, and any two S-nsais in the Allowed S-nsais obtained through re-determination satisfy the preset rule, for example, any two S-nsais in the Allowed S-nsais satisfy one of rules 1 to 3.

In an embodiment, before determining the list of allowed single network slice selection assistance information S-NSSAI for the terminal, the method further includes:

and determining NSI for the requested S-NSSAI according to the priority and mutual exclusion relationship between the requested S-NSSAI and the S-NSSAIs in the existing allowed S-NSSAI list.

In the PDU Session establishment process, when the NSSF or AMF determines the NSI for the UE, the mutual exclusion relationship between network slices of the same priority or different priorities needs to be satisfied. The following rules are followed:

rule 4: and if the requested S-NSSAI has no mutual exclusion relationship with other S-NSSAIs in the accepted S-NSSAIs, selecting one NSI for the requested S-NSSAI, and re-determining new accepted S-NSSAIs for the UE according to the information such as the NSI accessed by the UE (including the NSI selected by the requested S-NSSAI).

Rule 5: the requested S-NSSAI has a mutual exclusion relationship with other S-NSSAIs in the Allowed S-NSSAIs, if the S-NSSAI which is mutually exclusive does not have the accessed NSI corresponding to the user, one NSI is selected for the requested S-NSSAI, and new Allowed S-NSSAIs are determined for the UE again according to the information such as the NSI (including the NSI selected by the requested S-NSSAI) accessed by the UE.

Rule 6: the requested S-NSSAI has a mutual exclusion relationship with other S-NSSAIs in the Allowed S-NSSAIs, the S-NSSAI which is mutually exclusive has an accessed NSI corresponding to the user, the requested S-NSSAI has higher priority than the S-NSSAI which is mutually exclusive, the NSI which is corresponding to the S-NSSAI which is mutually exclusive (namely the PDU session which is corresponding to the S-NSSAI which is mutually exclusive) is marked to be released, one NSI is selected for the requested S-NSSAI, and new Allowed S-NSSAIs are determined for the UE again according to information such as the NSI (including the NSI selected by the requested S-NSSAI but not including the NSI which is corresponding to the S-NSSAI which is mutually exclusive) accessed by the UE.

Rule 7: the requested S-NSSAI has a mutual exclusion relationship with other S-NSSAIs in the Allowed S-NSSAIs, the S-NSSAI which is mutually exclusive has the accessed NSI corresponding to the user, and the priority of the requested S-NSSAI is not higher than that of the S-NSSAI which is mutually exclusive, so that NSI is refused to be selected for the requested S-NSSAI.

In one embodiment, if Allowed S-NSSAIs are determined by the NSSF, the AMF informs the NSSF of all the NSI information that the subscriber has accessed in the network slice selection request message.

In an embodiment, in the process of PDU session establishment or PDU session release or other processes that may cause PDU session release, Allowed S-nsais is re-determined for the terminal, and if NSSF decision Allowed S-nsais is required, the AMF notifies NSSF of all NSI information and existing Allowed S-nsais information that the user has accessed in a network slice selection request message.

In one embodiment, after NSSF redetermines Allowed S-NSSAIs, if the redetermined Allowed S-NSSAIs are found to be consistent with existing Allowed S-NSSAIs, the redetermined Allowed S-NSSAIs may not be returned to the AMF.

In an embodiment, when the re-determined Allowed S-nsais are not consistent with existing Allowed S-nsais, the NSSF sends the re-determined Allowed S-nsais to the UE through the AMF or the SMF.

Further, in the session management process, such as PDU session establishment and PDU session deletion, if the Allowed S-nsais changes, the AMF notifies the SMF of the re-determined Allowed S-nsais, and the SMF notifies the UE of the re-determined Allowed S-nsais when sending a message to the UE.

By the method provided by at least one embodiment of the invention, since the priority and mutual exclusion relationship between the S-NSSAIs in the Allowed S-NSSAIs already meet the preset rule, the UE does not need to identify the priority and mutual exclusion relationship between the slices, the processing of the UE is simplified, and the method is beneficial supplement and exploration for the standard protocol.

Fig. 3 is a flowchart illustrating an implementation of implementing an inter-slice mutual exclusion relationship by an NSSF decision in a registration process according to an embodiment of the present invention, as shown in fig. 3, including:

step 301: the UE initiates a registration process and sends a registration request message to the RAN, wherein the registration request message carries information such as Requested S-NSSAIs (Requested S-NSSAIs).

Wherein the requested S-NSSAIs include one or more S-NSSAIs.

Step 302: RAN selects a proper initial AMF (initial AMF) and sends an initial UE message to the initial AMF, wherein the initial UE message carries information such as a registration request message.

Step 303: the initial AMF completes the security function for the UE.

Step 304: and the initial AMF sends a user subscription data acquisition request message to the UDM.

Step 305: and after receiving the user subscription data acquisition request message, the UDM returns a user subscription data acquisition response message to the initial AMF, wherein the user subscription data acquisition response message carries information such as Subscribed S-NSSAIs (Subscribed S-NSSAIs).

Step 306: the initial AMF sends a network slice selection request message to the NSSF, wherein the network slice selection request message comprises information required by slice selection, such as requested S-NSSAIs, signed S-NSSAIs, user current positions (TAs), user identifications (SUPIs), user accessed NSI (NSI-ID, S-NSSAI) lists and the like.

Step 307: the NSSF determines allowable S-NSSAIs1(Allowed S-NSSAIs1) based on the requested S-NSSAIs, the subscribed S-NSSAIs, the user current location (TA), the user identity (SUPI), and the activated NSI in the network; NSSF processes Allowed S-NSSAIs1 according to the corresponding priority of each S-NSSAI and the mutual exclusion relationship among the network slices to obtain Allowed S-NSSAIs (allowable S-NSSAIs) and Rejected S-NSSAIs (Rejected S-NSSAIs), wherein the Allowed S-NSSAIs and the Rejected S-NSSAIs are combined to obtain Allowed S-NSSAIs1, and any first S-NSSAI and any second S-NSSAI in the Allowed S-NSSAIs meet the following conditions:

the first S-NSSAI and the second S-NSSAI have no mutual exclusion relationship;

or, the first S-NSSAI has a mutual exclusion relationship with the second S-NSSAI, and the first S-NSSAI does not have an accessed network slice instance corresponding to the user, and the second S-NSSAI does not have an accessed network slice instance corresponding to the user;

or, the first S-NSSAI and the second S-NSSAI have a mutual exclusion relationship, and one of the first S-NSSAI and the second S-NSSAI has an accessed network slice instance corresponding to the user, and the other has no accessed network slice instance corresponding to the user, and the priority of the S-NSSAI without the accessed network slice instance corresponding to the user is higher than the priority of the S-NSSAI with the accessed network slice instance corresponding to the user. Specifically, for example, the first S-NSSAI has a mutual exclusion relationship with the second S-NSSAI, the first S-NSSAI has an accessed network slice instance corresponding to the user, the second S-NSSAI does not have an accessed network slice instance corresponding to the user, and the priority of the second S-NSSAI is higher than the priority of the first S-NSSAI, or the first S-NSSAI has a mutual exclusion relationship with the second S-NSSAI, the first S-NSSAI does not have an accessed network slice instance corresponding to the user, the second S-NSSAI has an accessed network slice instance corresponding to the user, and the priority of the first S-NSSAI is higher than the priority of the second S-NSSAI.

Step 308: the NSSF returns a network slice selection response message to the initial AMF, wherein the network slice selection response message carries information such as Allowed S-NSSAIs, Rejected S-NSSAIs, AMF Set (Set) and the like.

It should be noted that only Allowed S-NSSAIs may be carried.

Step 309: the initial AMF completes the registration procedure processing until a registration accept message is sent to the UE.

Step 310: and the initial AMF sends a registration acceptance message to the UE, wherein the registration acceptance message carries information such as allowed S-NSSAIs and the like, and can also carry rejected S-NSSAIs.

Step 311: the initial AMF continues to process the registration process until registration is completed.

In the scheme provided by this embodiment, in the terminal registration process, the NSSF determines the allowed S-nsais according to the network slice priority and the mutual exclusion relationship, so that the priority and the mutual exclusion relationship of the S-nsais in the allowed S-nsais meet the preset rule, and the UE does not need to identify the priority and the mutual exclusion relationship of the network slice.

Fig. 4 is a flowchart illustrating implementation of an inter-slice mutual exclusion relationship by an AMF decision in a registration process according to an embodiment of the present invention. As shown in fig. 4, includes:

step 401: the UE initiates a registration process and sends a registration request message to the RAN, wherein the registration request message carries information such as Requested S-NSSAIs (Requested S-NSSAIs).

Step 402: RAN selects a proper initial AMF (initial AMF) and sends an initial UE message to the initial AMF, wherein the initial UE message carries information such as a registration request message.

Step 403: the initial AMF completes the security function for the UE.

Step 404: and the initial AMF sends a user subscription data acquisition request message to the UDM.

Step 405: and after receiving the user subscription data request message, the UDM returns a user subscription data acquisition response message to the initial AMF, wherein the user subscription data acquisition response message carries information such as Subscribed S-NSSAIs (Subscribed S-NSSAIs).

Step 406: the initial AMF determines that the AMF does not need to be redirected according to a local strategy;

step 407: the initial AMF determination may be based on local policy decisions of Allowed S-NSSAIs1(Allowed S-NSSAIs1), the initial AMF determining Allowed S-NSSAIs1(Allowed S-NSSAIs1) based on requested S-NSSAIs, subscribed S-NSSAIs, user current location (TA), user identity (SUPI), and activated NSIs in the network; and processing Allowed S-NSSAIs1 by the initial AMF according to the corresponding priority of each S-NSSAis and the mutual exclusion relationship among the network slices to obtain Allowed S-NSSAIs and Rejected S-NSSAIs, wherein the Allowed S-NSSAIs and the Rejected S-NSSAIs are combined to obtain Allowed S-NSSAIs1, and any first S-NSSAI and any second S-NSSAI in the Allowed S-NSSAIs meet the following requirements:

the first S-NSSAI and the second S-NSSAI have no mutual exclusion relationship;

or, the first S-NSSAI and the second S-NSSAI have a mutual exclusion relationship, and one of the first S-NSSAI and the second S-NSSAI has an accessed network slice instance corresponding to the user, and the other has no accessed network slice instance corresponding to the user, and the priority of the S-NSSAI without the accessed network slice instance corresponding to the user is higher than the priority of the S-NSSAI with the accessed network slice instance corresponding to the user.

Step 408: the initial AMF completes a registration procedure process until a registration accept message is sent to the UE.

Step 409: and the initial AMF sends a registration acceptance message to the UE, wherein the registration acceptance message carries information such as allowed S-NSSAIs and the like, and can also carry rejected S-NSSAIs.

Step 410: the initial AMF continues to process the registration process until registration is completed.

As shown in fig. 5, an embodiment of implementing the inter-slice mutual exclusion relationship by NSSF decision in the PDU session establishment process includes:

step 501: the UE initiates a PDU session establishment process, the UE sends a PDU session establishment request message to the AMF, and the PDU session establishment request message carries information such as requested S-NSSAI and DNN (Data Network Name).

Step 502: the AMF sends a network slice selection request message to the NSSF, where the network slice selection request message includes information required for slice selection, such as requested S-NSSAI, allowed S-NSSAIs, a list of user accessed NSI (NSI-ID (NSI identifier), S-NSSAI), and the like.

Wherein the allowable S-NSSAIs herein are the existing allowable S-NSSAIs.

Step 503: the NSSF selects one NSI for the requested S-NSSAI when determining that one NSI can be selected for the requested S-NSSAI according to the information of the requested S-NSSAI and the like; NSSF processes Allowed S-NSSAIs1 according to the priority corresponding to each S-NSSAI in the existing Allowed S-NSSAIs (hereinafter referred to as Allowed S-NSSAIs1) sent by AMF and the mutual exclusion relationship among network slices to obtain Allowed S-NSSAIs (namely, newly determined Allowed S-NSSAIs) and Rejected S-NSSAIs, wherein Allowed S-NSSAIs and Rejected S-NSSAIs are combined to obtain Allowed S-NSSAIs1, and any first S-NSSAI and second S-NSSAI in the Allowed S-NSSAIs satisfy:

the first S-NSSAI and the second S-NSSAI have no mutual exclusion relationship;

It should be noted that, in this embodiment, only Allowed S-NSSAIs may be acquired.

Step 504: the NSSF returns a network slice selection response message to the initial AMF, wherein the network slice selection response message carries information such as Allowed S-NSSAIs, Rejected S-NSSAIs, NSIs and the like.

Wherein the network slice selection response message may not carry Rejected S-NSSAIs.

Step 505: AMF completes SMF selection.

Step 506: and the AMF sends a session creating context request message to the SMF, wherein the session creating context request message carries the requested S-NSSAI, DNN and the re-determined Allowed S-NSSAIs returned by the NSSF.

Step 507: the SMF continues to process the PDU session setup procedure until a PDU session setup accept message is returned to the UE.

Step 508: the SMF returns a session context creating response message to the AMF, wherein the session context creating response message carries information such as a PDU session establishment acceptance message, and the PDU session establishment acceptance message carries information such as Allowed S-NSSAIs (namely re-determined Allowed S-NSSAIs).

Step 509: the AMF sends a PDU session resource establishment request message to the RAN, wherein the PDU session resource establishment request message carries information such as a PDU session establishment acceptance message, and the PDU session establishment acceptance message carries information such as Allowed S-NSSAIs (namely re-determined Allowed S-NSSAIs).

Step 510: and the RAN delivers information such as PDU session establishment acceptance information to the UE, wherein the PDU session establishment acceptance information carries information such as Allowed S-NSSAIs.

Step 511: the PDU session establishment procedure continues until completed.

As shown in fig. 6, an embodiment of implementing the inter-slice mutual exclusion relationship by NSSF decision in the PDU session release process includes:

step 601: UE initiates PDU conversation release course, and sends PDU conversation release request message to AMF.

Step 602: and after receiving the PDU session release request message, the AMF sends a network slice selection request message to the NSSF, wherein the network slice selection request message comprises information of allowed S-NSSAIs (namely the allowed S-NSSAIs), an NSI (NSI-ID, S-NSSAI) list accessed by the user and the like.

Step 603: NSSF processes Allowed S-NSSAIs1 according to the priority corresponding to each S-NSSAI in Allowed S-NSSAIs (hereinafter referred to as Allowed S-NSSAIs1) sent by AMF and the mutual exclusion relationship among network slices to obtain Allowed S-NSSAIs (namely, newly determined Allowed S-NSSAIs) and Rejected S-NSSAIs, wherein Allowed S-NSSAIs and Rejected S-NSSAIs are combined to obtain Allowed S-NSSAIs1, and any first S-NSSAI and second S-NSSAI in the Allowed S-NSSAIs satisfy:

the first S-NSSAI and the second S-NSSAI have no mutual exclusion relationship;

Step 604: the NSSF returns a network slice selection response message to the initial AMF, wherein the network slice selection response message carries information such as Allowed S-NSSAIs (namely re-determined Allowed S-NSSAIs), Rejected S-NSSAIs and the like.

Step 605: and the AMF sends a session context releasing request message to the SMF, wherein the session context releasing request message carries the Allowed S-NSSAIs returned by the NSSF (namely the re-determined Allowed S-NSSAIs).

Step 606: the SMF continues to process the PDU session release flow until a PDU session release acceptance message is returned to the UE.

Step 607: the SMF returns a session context release response message to the AMF, wherein the session context release response message carries information such as a PDU session release acceptance message, and the PDU session release acceptance message carries information such as Allowed S-NSSAIs (i.e. re-determined Allowed S-NSSAIs).

Step 608: the AMF sends a PDU session resource release request message to the RAN, the PDU session resource release request message carries information such as a PDU session establishment release message, and the PDU session release acceptance message carries information such as Allowed S-NSSAIs (namely re-determined Allowed S-NSSAIs).

Step 609: the RAN delivers information such as PDU session release acceptance information to the UE, wherein the PDU session release acceptance information carries information such as Allowed S-NSSAIs (namely re-determined Allowed S-NSSAIs).

Step 610: the PDU session release procedure continues to be processed until completion.

As shown in fig. 7, an embodiment of the present invention provides a network slice mutual exclusion relationship processing device 70, which includes a memory 710 and a processor 720, where the memory 710 stores a program, and when the program is read and executed by the processor 720, the program implements the network slice mutual exclusion relationship processing method according to any embodiment.

An embodiment of the present invention provides a computer-readable storage medium storing one or more programs, which are executable by one or more processors to implement the network slice mutual exclusion relationship processing method according to any embodiment.

An embodiment of the present invention provides a network slice mutual exclusion relationship processing system, as shown in fig. 8, including: AMF801 and NSSF802, wherein:

the AMF801 is configured to send a network slice selection request message to the NSSF 802;

the NSSF802 is configured to determine an allowed S-NSSAI list for the terminal after receiving the network slice selection request message, where a priority and a mutual exclusion relationship between S-NSSAIs in the S-NSSAI list satisfy a preset rule.

For the specific implementation that the priority and the mutual exclusion relationship between the S-NSSAIs in the S-NSSAI list satisfy the predetermined rule, please refer to the foregoing embodiment, which is not described herein again.

In an embodiment, the AMF801 sending the network slice selection request to the NSSF802 includes:

when the terminal registers, or receives a protocol data unit session establishment request of the terminal, or receives a protocol data unit session release request of the terminal, the AMF801 sends the network slice selection request message to the NSSF 802.

In an embodiment, the network slice selection request message carries an already allowed S-NSSAI list and an instance of a network slice that the terminal has access to.

It will be understood by those of ordinary skill in the art that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the components may be implemented as software executed by a processor, such as a digital signal processor or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those of ordinary skill in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by a computer. In addition, 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 includes any information delivery media as known to those skilled in the art.

Claims

1. A network slice mutual exclusion relationship processing method comprises the following steps:

determining an allowed single network slice selection auxiliary information S-NSSAI list for a terminal, wherein the priority and the mutual exclusion relation between S-NSSAIs in the allowed S-NSSAI list meet a preset rule;

the determining an allowed list of single network slice selection assistance information S-NSSAI for the terminal includes: determining an allowed S-NSSAI list for the terminal according to the S-NSSAI requested by the terminal, the signed S-NSSAI and the accessed network slice example; or, re-determining the allowed S-NSSAI list for the terminal according to the existing allowed S-NSSAI list and the network slice example accessed by the terminal;

the priority and mutual exclusion relationship between the S-NSSAIs in the allowed S-NSSAI list satisfying a preset rule includes that any first S-NSSAI and second S-NSSAI in the allowed S-NSSAI list satisfy:

the first S-NSSAI and the second S-NSSAI have no mutual exclusion relationship;

or, the first S-NSSAI and the second S-NSSAI have a mutual exclusion relationship, and the first S-NSSAI does not have an accessed network slice instance corresponding to the terminal, and the second S-NSSAI does not have an accessed network slice instance corresponding to the terminal;

or, the first S-NSSAI and the second S-NSSAI have a mutual exclusion relationship, and one of the first S-NSSAI and the second S-NSSAI has an accessed network slice instance corresponding to the terminal, and the other has no accessed network slice instance corresponding to the terminal, and the priority of the S-NSSAI without the accessed network slice instance corresponding to the terminal is higher than the priority of the S-NSSAI with the accessed network slice instance corresponding to the terminal.

2. The method according to claim 1, wherein the determining the list of allowed single network slice selection assistance information S-NSSAI for the terminal further comprises obtaining an instance of a network slice accessed by the terminal from a network slice selection request message sent by an access and mobility management function entity, or obtaining the list of allowed S-NSSAI and the instance of a network slice accessed by the terminal.

3. The method for processing network slice mutual exclusion relationship as claimed in claim 1, wherein after determining the list of allowed single network slice selection auxiliary information S-NSSAI for the terminal, the method further comprises:

when the determined allowed S-NSSAI list for the terminal does not coincide with the existing allowed S-NSSAI list, the network slice selection function entity transmits the determined allowed S-NSSAI list for the terminal to the terminal through the access and mobility management function entity.

4. The method according to claim 1, wherein the determining the list of allowed single network slice selection assistance information S-NSSAI for the terminal comprises:

determining an allowed S-NSSAI list for the terminal when the terminal is registered or a protocol data unit session of the terminal is changed.

5. The method of claim 4, wherein the change of the PDU session of the terminal comprises at least one of: establishing a protocol data unit session and releasing the protocol data unit session.

6. The method for processing network slice mutual exclusion relationship according to any of claims 1 to 5, wherein before determining the list of allowed single network slice selection auxiliary information S-NSSAI for the terminal, the method further comprises:

determining a network slice instance for a requested S-NSSAI based on a priority and mutual exclusion relationship of the requested S-NSSAI and S-NSSAIs in an existing allowed S-NSSAI list.

7. The method according to any of claims 1 to 5, wherein the determining the list of allowed single network slice selection auxiliary information S-NSSAI for the terminal comprises: the network slice selection function or the access and mobility management function determines an allowed list of S-NSSAIs for the terminal.

8. A network-slice mutual exclusion relationship processing apparatus comprising a memory and a processor, the memory storing a program that, when read and executed by the processor, implements the network-slice mutual exclusion relationship processing method according to any one of claims 1 to 7.

9. A computer-readable storage medium storing one or more programs, the one or more programs being executable by one or more processors to implement the network slice mutual exclusion relationship processing method according to any one of claims 1 to 7.

10. A network slice mutual exclusion relationship processing system, comprising: access and mobility management function entity, network slice selection function entity, wherein:

the access and mobile management function entity is used for sending a network slice selection request message to the network slice selection function entity;

the network slice selection functional entity is used for determining an allowed S-NSSAI list for the terminal after receiving the network slice selection request message, wherein the priority and the mutual exclusion relationship among the S-NSSAIs in the allowed S-NSSAI list meet a preset rule;

wherein the determining an allowed list of single network slice selection assistance information S-NSSAI for the terminal includes: determining an allowed S-NSSAI list for the terminal according to the S-NSSAI requested by the terminal, the signed S-NSSAI and the accessed network slice example; or, re-determining the allowed S-NSSAI list for the terminal according to the existing allowed S-NSSAI list and the network slice example accessed by the terminal;

the first S-NSSAI and the second S-NSSAI have no mutual exclusion relationship;

11. The network slice mutual exclusion relationship processing system of claim 10 wherein the access and mobility management function entity sending a network slice selection request to the network slice selection function entity comprises:

and the access and mobile management functional entity sends the network slice selection request message to the network slice selection functional entity when the terminal is registered, or receives a protocol data unit session establishment request of the terminal, or after receiving a protocol data unit session release request of the terminal.

12. The system according to any of claims 10 to 11, wherein the access and mobility management function entity is further configured to carry an existing allowed S-NSSAI list and an instance of a network slice accessed by the terminal in the network slice selection request message.