CN112994913B

CN112994913B - Network slice selection method and related device

Info

Publication number: CN112994913B
Application number: CN201911285716.XA
Authority: CN
Inventors: 陈殿福
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-12-13
Filing date: 2019-12-13
Publication date: 2023-02-24
Anticipated expiration: 2039-12-13
Also published as: WO2021115464A1; CN112994913A

Abstract

Disclosed is a network slice selection method, comprising: the first NSSF receives a first request message from the first AMF, wherein the first request message comprises the position information of the user; if the first NSSF is determined not to record the information of the network slice example allowing the user to access the first area, the first NSSF receives the indication information of the first network slice example from the second NSSF and the identification of the second AMF; the first network slice example is a network slice example which is selected from network slice examples recorded in the second NSSF and allows the user to access in a first area, and the first area is an area characterized by the position information; the first NSSF records network slice examples supported by the AMF in the first area, and the second NSSF records network slice examples supported by the AMF of K areas, wherein the K areas comprise the first area. According to the embodiment of the application, the risk of overload of the load and the access delay can be reduced, and the user experience is improved.

Description

Network slice selection method and related device

Technical Field

The present application relates to the field of electronic technologies, and in particular, to a network slice selection method and a related device.

Background

With the advent of the fifth generation mobile communication technology (5G, 5G), the 5G mobile network can not only meet the communication requirements of people, but also support the connection of massive internet of things devices, so as to provide mobile communication services for thousands of industries, and the bandwidth, delay variation and security isolation requirements of different industries may be different. The network slicing technology provides mutually isolated network environments for different application scenes by deploying a plurality of virtual networks on the basis of shared infrastructure, thereby providing differentiated network services for different services or user groups. A Network Slice Selection Function (NSSF) entity may provide slice instance selection and target AMF selection services for an access and mobility management function (AMF) entity of a home network, and the NSSF may provide slice update, subscription, and notification functions for the AMF based on a Tracking Area (TA).

As the number of users increases, network access to medium and large operators is also more frequent, and there is a risk of overloading a centrally deployed NSSF. In addition, due to the large geographical span, the centralized deployment of NSSF may increase access delay and affect user experience.

Disclosure of Invention

The embodiment of the application provides a network slice selection method and a related device, which can reduce the risk of overload and access delay and improve the user experience.

In a first aspect, the present application provides a network slice selection method, including:

the first NSSF receives a first request message from the first AMF, wherein the first request message comprises the position information of the user;

if the first NSSF is determined not to record the information of the network slice instance allowing the user to access the first area, the first NSSF receives the indication information of the first network slice instance and the identification of the second AMF from the second NSSF;

the first network slice example is a network slice example which is selected from network slice examples recorded in the second NSSF and allows the user to access in a first area, and the first area is an area characterized by the position information;

the information of the network slice example includes indication information of the network slice example, an identifier of an AMF configured in the network slice example, and an identifier of an area served by the network slice example, where the first NSSF records information of the network slice example supported by the AMF in the first area, and the second NSSF records information of network slice examples supported by AMFs in K areas, where the K areas include the first area, and K is a positive integer greater than 1.

Implementing the method described in the first aspect, if it is determined that the first NSSF does not record the network slice instance subscribed by the user, the first NSSF may request the second NSSF to provide network slice selection service for the user. In the embodiment of the present application, the first NSSF records only the network slice instances supported by the AMF in the first area, and the second NSSF records the network slice instances supported by the AMFs in all areas, so that the second NSSF may provide the network slice selection service for the user. By implementing the method and the device, the risk of NSSF load overload is reduced, the access time delay of the user is reduced, and the user experience is effectively improved.

In one implementation, the first request message further includes Network Slice Selection Assistance Information (NSSAI) of the user; if it is determined that the first NSSF does not record information that allows the user to access the network slice instance of the first area, the first NSSF receiving the indication information of the first network slice instance and the identification of the second AMF from the second NSSF includes: if the first NSSF is determined not to record the information of the network slice example allowing the user to access the first area according to the signed NSSAI of the user, the first NSSF receives the indication information of the first network slice example from the second NSSF and the identification of the second AMF.

In one implementation, the first request message further includes a user identifier; if it is determined that the first NSSF does not record information that allows the user to access the network slice instance in the first area, the first NSSF receiving the indication information of the first network slice instance and the identifier of the second AMF from the second NSSF includes: if the first NSSF is determined not to record the information of the network slice example allowing the user to access the first area according to the signed NSSAI information of the user characterized by the user identification, the first NSSF receives the indication information of the first network slice example from the second NSSF and the identification of the second AMF, and the signed NSSAI of the user is obtained by requesting a Unified Data Manager (UDM) according to the user identification.

In one implementation, before the first NSSF receives the first request message from the first AMF, the method further includes: the first NSSF sends a second request message to a second NSSF, wherein the second request message comprises the identification of the first AMF and the information of the network slice instances supported by the first AMF, and the second request message is used for requesting the second NSSF to record the network slice instances supported by the first AMF into the network slice instances recorded by the second NSSF.

In an implementation manner, after the first NSSF sends the second request message to the second NSSF, the method further includes: the first NSSF sends a third request message to the second NSSF, the third request message including the identification of the first AMF and information of the second network slice instance, and the third request message is used for requesting the second NSSF to add the second network slice instance to the network slice instances supported by the first AMF.

In one implementation, after the first NSSF sends the second request message to the second NSSF, the method further includes: the first NSSF sends a fourth request message to the second NSSF, wherein the fourth request message comprises the identification of the first AMF, the indication information of the third network slice instance and the information of the fourth network slice instance, and the fourth request message is used for requesting the second NSSF to replace the third network slice instance supported by the first AMF with the fourth network slice instance.

In one implementation, after the first NSSF sends the second request message to the second NSSF, the method further includes: the first NSSF sends a fifth request message to the second NSSF, the fifth request message including an identifier of the first AMF and indication information of a fifth network slice instance, and the fifth request message is used for requesting the second NSSF to remove the fifth network slice instance from the network slice instances supported by the first AMF.

In one implementation, after the first NSSF sends the second request message to the second NSSF, the method further includes: the first NSSF sends a sixth request message to the second NSSF, the sixth request message including the identity of the first AMF, the sixth request message requesting the second NSSF to remove the network slice instance supported by the first AMF from the network slice instances recorded by the second NSSF.

In one implementation, the indication information of the network slice instance includes NSSAI of the network slice instance.

In an implementation manner, the indication information of the Network Slice Instance further includes a Network Slice Instance identifier (NSI ID).

In an implementation manner, the second NSSF further records information of network slice instances supported by a global AMF, where the global AMF provides access and mobility management services for a global user, the network slice instances subscribed by the global user are allowed to access M of the K regions, and M is a positive integer greater than 1 and less than or equal to K.

In one implementation, the location information of the user is TA information of the user.

In one implementation, the user is a global user.

In a second aspect, the present application provides a network slice selection method, including:

the second NSSF receiving a seventh request message from the first NSSF;

the seventh request message is used for requesting the second NSSF to select a network slice example allowing the user to access in a first area, wherein the first area is an area characterized by the location information, and the first NSSF records information of the network slice example supported by the AMF in the first area;

the second NSSF sends indication information of the first network slice instance to the first NSSF;

the information of the network slice instance includes indication information of the network slice instance, an identifier of an AMF configured in the network slice instance, and an identifier of an area served by the network slice instance, the first network slice instance is selected from network slice instances recorded in the second NSSF, and the information of network slice instances supported by AMFs of K areas recorded on the second NSSF of the network slice instance that allows the user to access the first area is recorded in the first area, the K areas include the first area, and K is a positive integer greater than 1.

Implementing the method described in the second aspect, after the second NSSF receives a seventh request message from the first NSSF, the seventh request message including location information characterizing the first area of the subscriber, and the second NSSF may provide the network slice selection service for the subscriber. This is because only network slice instances supported by AMFs in the first region are recorded in the first NSSF, while network slice instances supported by AMFs of all regions are recorded on the second NSSF. By implementing the method and the device, the risk of NSSF load overload is reduced, the access time delay of the user is reduced, and the user experience is effectively improved.

In one implementation, the seventh request message further includes a subscription NSSAI of the user; the seventh request message is used to request the second NSSF to select the network slice instance allowing the user to access in the first area according to the subscribed NSSAI of the user.

In one implementation, the first request message further includes a user identifier; the seventh request message is used to request the second NSSF to select a network slice instance allowing the user to access in the first area according to the subscription NSSAI of the user characterized by the user identifier, where the subscription NSSAI of the user is obtained by requesting the UDM according to the user identifier.

In one implementation, before the second NSSF receives the seventh request message from the first NSSF, the method further includes: the second NSSF receives a second request message from the first NSSF, wherein the second request message comprises the identification of the first AMF and the information of the network slice instances supported by the first AMF, and the second request message is used for requesting the second NSSF to record the network slice instances supported by the first AMF into the network slice instances recorded by the second NSSF.

In one implementation, after the second NSSF receives the second request message from the first NSSF, the method further includes: the second NSSF receives a third request message from the first NSSF, the third request message including an identification of the first AMF, information of the second network slice instance, and the third request message requesting the second NSSF to add the second network slice instance to the network slice instances supported by the first AMF.

In one implementation, after the first NSSF sends the second request message to the second NSSF, the method further includes: the second NSSF receives a fourth request message from the first NSSF, where the fourth request message includes an identifier of the first AMF, indication information of the third network slice instance, and information of the fourth network slice instance, and the fourth request message is used to request the second NSSF to replace the third network slice instance supported by the first AMF with the fourth network slice instance.

In one implementation, after the first NSSF sends the second request message to the second NSSF, the method further includes: the second NSSF receives a fifth request message from the first NSSF, the fifth request message including an identification of the first AMF, and indication information of a fifth network slice instance, and the fourth request message is used to request the second NSSF to remove the fifth network slice instance from the network slice instances supported by the first AMF.

In an implementation manner, after the first NSSF sends the second request message to the second NSSF, the method further includes: the second NSSF receives a sixth request message from the first NSSF, the sixth request message including an identification of the first AMF, the sixth request message requesting the second NSSF to remove the network slice instance of the first AMF from the network slice instances recorded by the second NSSF.

In one implementation, the seventh request message is sent by the first NSSF after determining that the first NSSF does not record an instance of a network slice that allows the user to access the first area.

In one implementation, the indication information of the network slice instance further includes an NSI ID of the network slice instance.

In one implementation, if the network slice instance subscribed by the user includes a network slice instance allowing the user to access the first area, the first network slice instance is a network slice instance allowing the user to access the first area selected from the network slices subscribed by the user.

In an implementation manner, if the network slice instance corresponding to the subscription NSSAI of the user does not include the network slice instance that the user is allowed to access in the first area, the first network slice instance is the network slice instance that the user is allowed to access in the first area, which is selected by the second NSSF from the network slice instances recorded in the second NSSF according to a roaming mapping table, where the roaming mapping table includes a mapping relationship between the subscription NSSAI of the user and the allowed NSSAI of the user, the subscription NSSAI of the user is the NSSAI of the network slice instance subscribed by the user, and the allowed NSSAI of the user includes the NSSAI of the network slice instance that the user is allowed to access in the first area.

In one implementation, the second NSSF further records information of network slice instances supported by the global AMF, where the global AMF provides access and mobility management services for global users, the network slice instances subscribed by the global users are allowed to access M of the K regions, and M is a positive integer greater than 1 and less than or equal to K.

In one implementation, the user is a global user.

In a third aspect, an embodiment of the present application provides a network device, where the user equipment may include a plurality of functional modules or units, and is configured to correspondingly perform the network slice selection method provided in the first aspect.

For example, a first receiving unit.

A first receiving unit, configured to receive a first request message from the first AMF, where the first request message includes location information of a user.

A first receiving unit, further configured to receive indication information of the first network slice instance from the second NSSF and an identification of the second AMF if it is determined that the network device does not record information of a network slice instance allowing the user to access the first area; the first network slice instance is a network slice instance selected from network slice instances recorded in the second NSSF that allows the user to access a first area, which is an area characterized by the location information.

The information of the network slice instance includes indication information of the network slice instance, an identifier of an AMF configured in the network slice instance, and an identifier of an area served by the network slice instance, information of the network slice instance supported by the AMF in a first area is recorded in the network device, and information of network slice instances supported by AMFs in K areas including the first area is recorded on the second NSSF, where K is a positive integer greater than 1.

In one implementation, the first request message further includes an NSSAI of the user; the first receiving unit is specifically configured to: if it is determined that the network device does not record information that allows the user to access the network slice instance of the first area according to the NSSAI of the user, indication information of the first network slice instance and an identification of the second AMF from the second NSSF is received.

In one implementation, the first request message further includes a user identifier; the first receiving unit is specifically configured to: and if the network equipment does not record the information of the network slice example allowing the user to access the first area according to the NSSAI of the user characterized by the user identification, receiving the indication information of the first network slice example from the second NSSF and the identification of the second AMF, and requesting the UDM for obtaining the signed NSSAI of the user according to the user identification.

In one implementation, before the first receiving unit receives the first request message from the first AMF, the network device further includes: and the first sending unit is used for sending a second request message to the second NSSF, wherein the second request message comprises the identification of the first AMF and the information of the network slice instances supported by the first AMF, and the second request message is used for requesting the second NSSF to record the network slice instances supported by the first AMF into the network slice instances recorded by the second NSSF.

In an implementation manner, after the first sending unit sends the second request message to the second NSSF, the first sending unit is further configured to: and sending a third request message to the second NSSF, wherein the third request message comprises the identification of the first AMF and the information of the second network slice instance, and the third request message is used for requesting the second NSSF to add the second network slice instance to the network slice instances supported by the first AMF.

In an implementation manner, after the first sending unit sends the second request message to the second NSSF, the first sending unit is further configured to: and sending a fourth request message to the second NSSF, wherein the fourth request message comprises the identification of the first AMF, the indication information of the third network slice instance and the information of the fourth network slice instance, and the fourth request message is used for requesting the second NSSF to replace the third network slice instance supported by the first AMF with the fourth network slice instance.

In an implementation manner, after the first sending unit sends the second request message to the second NSSF, the first sending unit is further configured to: and sending a fifth request message to the second NSSF, wherein the fifth request message comprises the identification of the first AMF and indication information of a fifth network slice instance, and the fifth request message is used for requesting the second NSSF to remove the fifth network slice instance from the network slice instances supported by the first AMF.

In one implementation manner, after the first sending unit sends the second request message to the second NSSF, the first sending unit is further configured to: and sending a sixth request message to the second NSSF, wherein the sixth request message comprises the identification of the first AMF, and the sixth request message is used for requesting the second NSSF to remove the network slice instance supported by the first AMF from the network slice instance recorded by the second NSSF.

In one implementation, the indication information of the network slice instance further includes NSIID of the network slice instance.

In an implementation manner, the second NSSF further records information of network slice instances supported by a global AMF, where the global AMF provides access and mobility management services for a global user, the network slice instances subscribed by the global user are allowed to access M of the K regions, and M is a positive integer greater than 1 and less than or equal to K. In one implementation, the location information of the user is TA information of the user.

In one implementation, the user is a global user.

In a fourth aspect, an embodiment of the present application provides a network device, where the user equipment may include a plurality of functional modules or units, configured to correspondingly execute the network slice selection method provided in the second aspect.

For example a third receiving unit and a second transmitting unit.

A third receiving unit, configured to receive a seventh request message from the first NSSF; the seventh request message includes location information of the user, the seventh request message is used for requesting the network device to select a network slice instance allowing the user to access in a first area, the first area is an area characterized by the location information, and information of the network slice instance supported by the AMF in the first area is recorded in the first NSSF;

a second sending unit, configured to send indication information of the first network slice instance to the first NSSF;

the information of the network slice instance comprises indication information of the network slice instance, an identifier of an AMF configured in the network slice instance, and an identifier of an area served by the network slice instance, the first network slice instance is a network slice instance which is selected from network slice instances recorded in the network equipment and allows a user to access the first area, information of network slice instances supported by AMFs of K areas is recorded on the network equipment, the K areas comprise the first area, and K is a positive integer greater than 1.

In one implementation, the seventh request message further includes a subscription NSSAI of the user; the seventh request message is used for requesting the network device to select a network slice instance allowing the user to access in the first area according to the subscribed NSSAI of the user.

In one implementation, the first request message further includes a user identifier; the seventh request message is used for requesting the network device to select a network slice instance allowing the user to access in the first area according to the subscription NSSAI of the user represented by the user identifier, and the subscription NSSAI of the user is obtained by requesting the UDM according to the user identifier.

In one implementation, before the third receiving unit receives the seventh request message from the first NSSF, the third receiving unit is further configured to: and receiving a second request message from the first NSSF, wherein the second request message comprises the identification of the first AMF and information of the network slice instances supported by the first AMF, and the second request message is used for requesting the network device to record the network slice instances supported by the first AMF into the network slice instances recorded by the network device.

In an implementation manner, after the third receiving unit receives the second request message from the first NSSF, the third receiving unit is further configured to: a third request message is received from the first NSSF, the third request message including an identification of the first AMF, information of the second network slice instance, the third request message for requesting the network device to add the second network slice instance to the network slice instances supported by the first AMF.

In an implementation manner, after the third receiving unit receives the second request message from the first NSSF, the third receiving unit is further configured to: and receiving a fourth request message from the first NSSF, wherein the fourth request message comprises the identification of the first AMF, the indication information of the third network slice instance and the information of the fourth network slice instance, and the fourth request message is used for requesting the network equipment to replace the third network slice instance supported by the first AMF with the fourth network slice instance.

In an implementation manner, after the third receiving unit receives the second request message from the first NSSF, the third receiving unit is further configured to: receiving a fifth request message from the first NSSF, the fifth request message including an identification of the first AMF and indication information of a fifth network slice instance, the fourth request message for requesting the network device to remove the fifth network slice instance from the network slice instances supported by the first AMF.

In an implementation manner, after the third receiving unit receives the second request message from the first NSSF, the third receiving unit is further configured to: a sixth request message is received from the first NSSF, the sixth request message including an identification of the first AMF, the sixth request message requesting the network device to remove the network slice instance of the first AMF from the network slice instances recorded by the network device.

In one implementation manner, if the network slice instance corresponding to the subscription NSSAI of the user does not include the network slice instance allowing the user to access in the first area, the first network slice instance is a network slice instance allowing the user to access in the first area, which is selected by the network device from the network slice instances recorded in the network device according to a roaming mapping table, where the roaming mapping table includes a mapping relationship between the subscription NSSAI of the user and the allowed NSSAI of the user, the subscription NSSAI of the user is the NSSAI of the network slice instance subscribed by the user, and the allowed NSSAI of the user includes the NSSAI of the network slice instance allowing the user to access in the first area.

In one implementation, the network device further records information of network slice instances supported by a global AMF, where the global AMF provides access and mobility management services for global users, and the network slice instances subscribed by the global users are allowed to access M of the K regions, where M is a positive integer greater than 1 and less than or equal to K.

In one implementation, the user is a global user.

In a fifth aspect, an embodiment of the present application provides a network device, configured to execute the network slice selection method provided in the first aspect. The network device may include: memory, processor, transmitter, receiver, wherein: the transmitter and receiver are used to communicate with other communication devices, such as network devices or user equipment. The memory is used for storing implementation codes of the network slice selection method provided by the first aspect, and the processor is used for executing the program codes stored in the memory, namely executing the network slice selection method provided by the first aspect.

In a sixth aspect, an embodiment of the present application provides a network device, configured to execute the network slice selection method provided in the second aspect. The network device may include: memory, processor, transmitter, receiver, wherein: the transmitter and receiver are used to communicate with other communication devices, such as network devices or user equipment. The memory is used for storing implementation codes of the network slice selection method provided by the second aspect, and the processor is used for executing the program codes stored in the memory, namely executing the network slice selection method provided by the second aspect.

In a seventh aspect, an embodiment of the present application provides a communication system, where the communication system includes: a first NSSF and a second NSSF.

Wherein:

the first NSSF may be the network device described in the third aspect, or may be the network device described in the fifth aspect.

The second NSSF may be the network device described in the fourth aspect above, and may also be the network device described in the sixth aspect above.

In an eighth aspect, the present application provides a communication chip, which may include: a processor, and one or more interfaces coupled to the processor. Wherein the processor is operable to call from the memory a program implementing the network slice selection method provided in the first aspect, and execute instructions contained in the program. The interface may be configured to output a data processing result of the processor.

In a ninth aspect, the present application provides a communication chip, which may include: a processor, and one or more interfaces coupled to the processor. Wherein the processor is operable to call a program implementing the network slice selection method provided by the second aspect from the memory and execute the instructions contained in the program. The interface may be configured to output a data processing result of the processor.

In a tenth aspect, an embodiment of the present application provides a computer-readable storage medium, which has instructions stored thereon, and when the instructions are executed on a processor, the processor is caused to execute the network slice selection method described in the first aspect.

In an eleventh aspect, embodiments of the present application provide a computer-readable storage medium having instructions stored thereon, which when executed on a processor, cause the processor to perform the network slice selection method described in the second aspect.

In a twelfth aspect, embodiments of the present application provide a computer program product containing instructions that, when run on a processor, cause the processor to perform the network slice selection method described in the first aspect above.

In a thirteenth aspect, embodiments of the present application provide a computer program product containing instructions that, when executed on a processor, cause the processor to perform the network slice selection method described in the second aspect above.

Drawings

Fig. 1 is a system architecture diagram of a communication system according to an embodiment of the present application;

fig. 2 is a system architecture diagram of another communication system according to an embodiment of the present application;

fig. 3 is a system architecture diagram of another communication system according to an embodiment of the present application;

fig. 4 is a schematic flowchart of a network slice selection method provided in an embodiment of the present application;

fig. 5 is a schematic flow chart of another network slice selection method provided in an embodiment of the present application;

fig. 6 is a schematic flow chart of another network slice selection method provided in an embodiment of the present application;

fig. 7 is a schematic flowchart of another network slice selection method provided in an embodiment of the present application;

fig. 8 is a schematic flow chart of another network slice selection method provided in an embodiment of the present application;

fig. 9 is a schematic flow chart of another network slice selection method provided in an embodiment of the present application;

fig. 10 is a schematic structural diagram of a network device according to an embodiment of the present application;

fig. 11 is a schematic structure of another network device provided in an embodiment of the present application;

fig. 12 is a schematic structural diagram of a user equipment according to an embodiment of the present application;

fig. 13 is a schematic structural diagram of another network device according to an embodiment of the present application.

Detailed Description

The technical solution in the embodiments of the present application will be described in detail and removed with reference to the accompanying drawings. In the description of the embodiments herein, "/" means "or" unless otherwise specified, for example, a/B may mean a or B; "and/or" in the text is only an association relationship describing an associated object, and means that three relationships may exist, for example, a and/or B may mean: three cases of a alone, a and B both, and B alone exist, and in addition, "a plurality" means two or more than two in the description of the embodiments of the present application.

In the following, the terms "first", "second" are used for descriptive purposes only and are not to be construed as implying or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature, and in the description of embodiments of the application, unless stated otherwise, "plurality" means two or more.

First, a description will be given of several concepts of network slices, network slice examples, and network functions according to embodiments of the present invention.

Network Slice (NS) refers to different logical networks that are customized according to different service requirements. The network slice may be a complete end-to-end network comprising the terminal, the access network, the transport network, the core network and the application server, capable of providing complete telecommunication services, with certain network capabilities. The network slice may also be any combination of the above terminals, access networks, transport networks, core networks and application servers.

A Network Slice Instance (NSI) is an instantiation of an NS, that is, a real-running logical Network, and can meet certain Network characteristics or service requirements. One network slice instance may provide one or more services. The network slice instance can be created by a network slice management function device, and one network slice management function device can create a plurality of network slice instances and manage the network slice instances simultaneously, including performance monitoring, fault management and the like during the operation of the network slice instances. When a plurality of network slice instances coexist, part of network resources and network functions can be shared among the network slice instances. The network slice instance may or may not be created from a network slice template. A complete Network Slice Instance is capable of providing a complete end-to-end Network service, and what constitutes the Network Slice Instance may be a Network Slice Subnet Instance (NSSI) and/or a Network function. One network slice example can be divided into a plurality of network slice subnet examples so as to facilitate the management of the network management system. The network functions may include physical network functions and/or virtual network functions. Hereinafter, the physical network function and/or the virtual network function are collectively referred to as a network function.

Network Function (NF) is a processing function in a Network that defines the behavior and interfaces of functionality. The network function may be implemented by dedicated hardware, may be implemented by running software on dedicated hardware, or may be implemented in the form of a virtual function on a general hardware platform. Thus, from an implementation point of view, network functions may be divided into physical network functions and virtual network functions. From a usage perspective, network functions may be divided into dedicated network functions and shared network functions.

A network management system can create a plurality of network slice instances and manage the network slice instances at the same time, for example, modify, delete and the like the plurality of network slice instances, and perform performance monitoring, fault management and the like on the network slice instances in the running process of the network slice instances. A complete network slice instance is capable of providing a complete end-to-end network service, while the network slice instances may be composed of network slice subnet instances and/or network functions. A network slice instance is identified by an NSI ID. Illustratively, the NSI ID may be a string of characters, or may be a name that is readable by humans. Each Network Slice instance has one or more Single Network Slice Selection Assistance Information (S-NSSAI) identifications, where the S-NSSAI includes a Slice type (SST) and a user group (SD), the SST is used for defining a service scene/type for Network Slice standardization, and the SD is used for distinguishing different Network slices of the same Network Slice type. NSSAI is a set of S-NSSAIs that identifies a set of network slices.

When the UE registers in the telecommunication Network, the Network needs to select a Network Slice instance/Network Slice subnet instance for the UE according to Single Network Slice Selection Assistance Information (S-NSSAI) corresponding to the UE. And, the network also needs to select an appropriate AMF, i.e. a target AMF, for the UE according to the selected network slice instance/network slice subnet instance. The AMF belongs to a core network element and is mainly responsible for a signaling processing part, that is, a control plane function, including functions such as access control, mobility management, and gateway selection. The NSSF may provide the UE with the option to provide the target AMF and may also provide slice selection services for the home network's AMF selection. The AMF stores therein address information of NSSF for which a network slice selection service is provided.

In a large and medium Public Land Mobile Network (PLMN), there are both local Network slices and global Network slices. If the coverage area of the PLMN includes K areas, the local network slice example is only allowed to access one of the K areas, and K is a positive integer greater than 1; the global network slice example refers to the network slice example which is only allowed to access M areas in the PLMN area, wherein M is a positive integer which is greater than 1 and less than or equal to K. For convenience of description, the local network slice example is simply referred to as a local network slice example, and the global network slice example is simply referred to as a global network slice example. A user subscribing the Local network slice example is called a Local user, an AMF providing access and mobile management service for the Local user is called a Local AMF, and NSSF providing network slice selection service for the Local AMF is called a Local network slice selection function (L-NSSF); a user who subscribes to a Global network slice instance is called a Global user, an AMF that provides access and mobility management services for the Global user is called a Global AMF, and an NSSF that provides the Global AMF to a network slice selection service is called a Global network slice selection function (G-NSSF).

For medium and large operators, the geographical span is large, and the network access is more frequent. The centralized deployment of the NSSF has the risk of overload, increases access delay and influences user experience. To solve the above problem, a distributed deployment with multiple NSSFs may be considered.

As shown in fig. 1, a communication system 100 for NSSF distributed deployment according to an embodiment of the present application is shown. The communication system 100 may include: a User Equipment (UE) 101, a (Radio) Access Network (AN), a local AMF103, a local L-NSSF104, a global AMF105, and a G-NSSF106. The communication system 100 employs a PLMN having a coverage area comprising K zones, zone 1, zone 2 \ 8230, zone K.

The UE101 according to the embodiment of the present application may refer to a wireless terminal device having a wireless connection function. The UE101 may communicate with one or more core networks via (R) AN 102, for example, the UE101 may be a mobile terminal device such as a mobile phone, a computer, a tablet, a Personal Communication Service (PCS) phone, a Personal Digital Assistant (PDA), etc.; but also mobile stations (mobile station), mobile units (mobile unit), M2M terminals, wireless units, remote units, terminal agents, mobile clients, etc.; the terminal equipment can also be terminal equipment of the Internet of things and terminal equipment of the Internet of vehicles; the embodiments of the present application do not limit this.

The (R) AN 102 can be a 5G base station, NR base station, or the like, through which the UE101 can access the communication system 100. The (R) AN 102 may also be a network composed of a plurality of (R) AN 102 nodes, and may implement functions such as a wireless physical layer function, resource scheduling, and radio resource management. The (R) AN 102 establishes a control plane signaling connection with the AMF through the control plane interface N2, and may be used to implement functions such as radio access bearer control.

It should be noted that, in the embodiment of the present application, information of a network slice instance supported by the AMF is recorded in the AMF, that is, information of a local network slice instance supported by the local AMF103 is recorded in the local AMF103, and information of a global network slice instance supported by the global AMF105 is recorded in the global AMF 105. Information of network slice instances supported by the AMF of the area 1 is recorded in the L-NSSF 1104, and information of global network slice instances supported by the global AMF is recorded in the G-NSSF1 106. The information of the network slice instance includes indication information of the network slice instance, an identification of the AMF configured in the network slice instance, and an identification of an area served by the network slice instance. One or more L-NSSF may be included in each of the K regions.

Optionally, the indication information of the network slice instance includes S-NSSAI of the network slice instance.

Optionally, the indication information of the network slice instance includes an S-NSSAI of the network slice instance and an NSI ID of the network slice instance.

It should be noted that the network slice instance supported by the first AMF refers to a network slice instance for which the first AMF can provide access and mobile services, and the S-NSSAI of the network slice instance is recorded in the first AMF.

As shown in fig. 1, when UE101 performs initial access in area 1, UE101 first sends a registration request to (R) AN 102, and (R) AN 102 receiving the registration request selects AN initial AMF for UE101 to process the registration request. If the initial AMF cannot support all network slices subscribed by the user, the initial AMF requests the NSSF corresponding to the initial AMF to select a network slice instance allowing the access area 1 for the UE 101.

With the above communication system 100, there are several problems as follows:

(1) The local user initiates a registration request in area 1 via UE101, and it is global AMF105 that handles the registration request. Since the global AMF105 may not support all local network slice instances subscribed to by the local subscriber, the global AMF105 sends a request message to the G-NSSF106 requesting the G-NSSF106 to select a network slice instance for the local subscriber that is allowed to access area 1 for the local subscriber. However, the information of the above-mentioned network slice instance subscribed by the local user is not recorded in the G-NSSF106. The G-NSSF106 is also unable to provide network slice selection services for local users.

(2) The local user of the area K initiates a registration request in the area 1 through the UE101, and it is the local AMF103 of the area 1 that processes the registration request. Since the local AMF103 of area 1 may not support all local network slice instances subscribed by the local users of area K, the local AMF103 of area 1 sends a request message to the L-NSSF 1104 requesting the L-NSSF 1104 to select a network slice instance allowing access to area 1 for the local users of area K. However, the information of the network slice instances subscribed by the local users of the above area K is not recorded in the L-NSSF1 104. The local user of the area K refers to a user who is attributed to the area K. L-NSSF 1104 is unable to provide network slice selection services for local users in zone K as described above.

(3) The global user initiates a registration request in area 1 via UE101, and it is local AMF103 of area 1 that processes the registration request. Since the local AMF103 may not support all global network slice instances subscribed by the global subscriber, the local AMF103 sends a request message to the L-NSSF 1104 requesting the L-NSSF 1104 to select a network slice instance allowing access to area 1 for the global subscriber. However, no information is recorded in L-NSSF 1104 for the above-mentioned network slice instances to which the global user subscribes. L-NSSF 1104 is unable to provide the network slice selection service for the global user described above.

As shown in fig. 2, to solve the above-described several problems, an operator adds a management device 107 to the communication system 100. When one or more network slice instances supported by the AMF in the local AMF and the global AMF of the K regions change, the management device 107 synchronizes the data of the network slice instances supported by the local AMF of the K regions and the information of the network slice instances supported by the global AMF to each NSSF in the communication system 100, i.e., to L-NSSF1, L-NSSF 2, \ 8230;, L-NSSF K, and G-NSSF of the K regions, through manual configuration.

When network slice instances in communication system 100 change (create a network slice, modify a network slice, and/or delete a network slice, etc.), a synchronous update is performed on all NSSFs across the network. This synchronization method will undoubtedly consume a lot of transmission resources and labor cost. In addition, the manual configuration workload is large, and human errors are easily introduced;

therefore, as shown in fig. 3, in order to solve the problem of the communication system 100 shown in fig. 1, in the embodiment of the present application, a communication interface is added between the L-NSSF and the G-NSSF, through which the L-NSSF of the K regions can respectively synchronize information of network slice instances supported by the local AMF of each region to the G-NSSF, and the L-NSSF i can request to query information of network slice instances supported by any AMF in the communication system 100 recorded on the G-NSSF.

The embodiment of the present application provides a network slice selection method, which is applicable to the communication system shown in fig. 3, and can reduce the risk of NSSF overload, reduce access delay, and improve user experience. In addition, compared with the network slice synchronization mode in the communication system shown in fig. 2, the method has lower cost and can also avoid human misoperation.

Fig. 4 is a schematic flow chart of a network slice selection method provided in an embodiment of the present application. As shown in fig. 4, the network slice selection method provided in the embodiment of the present application includes, but is not limited to, steps S401 to S404. Possible implementations of embodiments of the method are described further below.

S401, the first AMF sends a first request message to the first NSSF, the first NSSF receives the first request message sent by the first AMF, and the first request message comprises the position information of the user.

It should be noted that the location information can be used to characterize one of K areas in the communication system 100, such as TA information of the user.

S402, the first NSSF determines whether the information of the network slice example allowing the user to access the first area is recorded in the first NSSF; the first area is an area characterized by the location information, and the first NSSF records information of a network slice instance supported by an AMF in the first area, where the information of the network slice instance includes indication information of the network slice instance, an identifier of the AMF configured in the network slice instance, and an identifier of an area served by the network slice instance.

In this embodiment of the application, the first request message further includes at least one parameter of a subscription NSSAI of the user and a user identifier. The first NSSF determines whether the first NSSF records the information of the network slice example allowing the user to access the first area according to the signed NSSAI and/or the user identification of the user.

In some embodiments of the present application, the first request message may also include a request NSSAI of the user.

Optionally, the first request message may further include a subscription NSSAI of the user. The determining, by the first NSSF, whether information of a network slice instance allowing the user to access the first area is recorded in the first NSSF includes: the first NSSF determines whether information of a network slice example allowing the user to access the first area is recorded in the first NSSF according to the signed NSSAI of the user.

Optionally, the first request message further includes a user identifier. The determining, by the first NSSF, whether information of a network slice instance allowing the user to access the first area is recorded in the first NSSF includes: and the first NSSF determines whether the information of the network slice example allowing the user with the user identification to access the first area is recorded in the first NSSF according to the signed NSSAI of the user characterized by the user identification. And the signed NSSAI of the user is obtained by the first NSSF according to the user identification to the UDM.

Specifically, the first NSSF first determines whether the first NSSF records a network slice instance corresponding to the subscription NSSAI of the user, and if so, determines whether the network slice instance corresponding to the subscription NSSAI of the user allows access to the first area.

It is to be understood that the information of the network slice instance of the first NSSF record includes an identification of the area served by the network slice instance, and the first NSSF may determine whether the network slice instance allows access to the first area according to the identification of the area served by the network slice instance. The network slice instance allows access to the first area if the identity of the area served by the network slice instance is the identity of the first area.

In the embodiment of the present application, the subscription NSSAI of the user is the S-NSSAI of the network slice example subscribed by the user, and the subscription NSSAI of the user includes one or more S-NSSAIs. The request NSSAI indicates the S-NSSAI of the network slice that the UE wants to register, and one or more S-NSSAIs are included in the request NSSAI.

Optionally, the UE Identity may be an International Mobile Subscriber Identity (IMSI), a Globally Unique Temporary UE Identity (GUTI), or the like.

In this embodiment of the present application, the first NSSF directly obtains the subscription NSSAI of the user through the first request message. Or, the first NSSF may obtain the subscribed NSSAI of the user from the UDM according to the user identifier in the first request message, where the subscribed NSSAI of the user includes one or more S-NSSAIs. The first NSSF determines whether a network slice instance corresponding to the subscription NSSAI of the user and allowed to access the first area is recorded in the first NSSF.

It is to be appreciated that information of one or more AMFs supporting network slice instances corresponding to the first NSSF is recorded in the first NSSF.

S403, if no record is recorded, the first NSSF sends a seventh request message to the second NSSF, and the second NSSF receives the seventh request message sent by the first NSSF, where the seventh request message includes the location information of the user, and the seventh request message is used to request the second NSSF to select a network slice instance for the user; the second NSSF records information of network slice instances supported by AMFs of K regions, where the K regions include the first region, and K is a positive integer greater than 1.

In this embodiment, the seventh request message further includes at least one parameter of a subscription NSSAI and a subscriber identity of the subscriber. The seventh request message may be configured to request the second NSSF to select an instance of the network slice that the subscriber is allowed to access in the first area according to the subscribed NSSAI and/or the subscriber identity of the subscriber.

Optionally, the seventh request message further includes a request S-NSSAI of the user; the seventh request message is used for requesting the second NSSF to select the network slice instance allowing the user to access in the first area according to the request S-NSSAI of the user, the subscription NSSAI of the user and/or the user identifier.

Optionally, the seventh request message further includes a subscription NSSAI of the user; the seventh request message is used for requesting the second NSSF to select a network slice instance allowing the user to access in the first area according to the subscribed NSSAI of the user.

Optionally, the seventh request message further includes a user identifier; the seventh request message is used to request the second NSSF to select a network slice instance allowing the user to access in the first area according to the subscription NSSAI of the user characterized by the user identifier, where the subscription NSSAI of the user is obtained by requesting the UDM according to the user identifier.

The specific implementation process is similar to the first NSSF, and is not described herein again.

In this embodiment of the present application, the second NSSF directly obtains the subscription NSSAI of the user through the seventh request message. Alternatively, the second NSSF may obtain the subscribed NSSAI of the user from the UDM according to the user identifier in the seventh request message. The second NSSF determines whether a network slice instance corresponding to the subscribed NSSAI of the user and allowed to access the first area is recorded in the second NSSF.

In this embodiment of the present application, before the second NSSF receives the seventh request message sent by the first NSSF, the second NSSF records network slice instances supported by the AMFs of the K regions, so as to provide a network slice selection service for users in the K regions.

In this embodiment, the network slice instance data supported by the AMFs of the K regions is synchronized to the second NSSF in real time. When the network slice instance supported by the first AMF of the K areas changes, the changed first AMF informs the first NSSF, so that the first NSSF updates the network slice instance supported by the first AMF of the first NSSF record; the first NSSF receives the notification from the AMF and notifies the second NSSF so that the second NSSF updates the network slice instance supported by the first AMF in the second NSSF record.

Optionally, the changing of the network slice instance supported by the AMFs of the K regions includes: adding an AMF in the K areas, wherein the added AMF supports one or more network slice examples; one or more network slice instances supported by an existing AMF for the K regions are changed (e.g., added, replaced, or removed); one AMF is removed in the K regions, the removed AMF supporting one or more network slice instances.

S404, the second NSSF sends the indication information of the first network slice example and the identification of the second AMF to the first NSSF, and the first NSSF receives the indication information of the first network slice example and the identification of the second AMF sent by the second NSSF; the first network slice instance is a network slice instance selected from network slice instances recorded in the second NSSF and allowing the user to access the first area, and the second AMF is an AMF configured in the first network slice instance.

In the embodiment of the present application, the indication information of the first network slice instance and the identifier of the second AMF are used to determine the target AMF.

In some embodiments of the present application, the second NSSF determines whether there is a network slice instance allowing the user to access the first area in the network slice instances corresponding to the subscription NSSAI of the user; if yes, determining a first network slice example from the network slice examples allowing the user to access the first area; if not, a first network slice instance may be selected for the user based on the roaming service to which the user subscribes.

In the embodiment of the present invention, a network slice example is recorded in the first NSSF: the first NSSF records information for this network slice instance.

The following describes in detail an implementation procedure of the network slice selection method provided in the embodiment of the present application.

Fig. 5 is a schematic flow chart of a network slice selection method provided in an embodiment of the present application. As shown in fig. 5, the network slice selection method provided in the embodiment of the present application includes, but is not limited to, steps S501 to S503. Possible implementations of embodiments of the method are described further below.

S501, the UE sends a registration request message to the first AMF, the first AMF receives the registration request message sent by the UE, and the registration request message comprises a user identification and position information of the user.

S502, the first AMF sends an eighth request message to the UDM, and the UDM receives the eighth request message sent by the first AMF, where the eighth request message includes a user identifier, and the eighth request message is used to obtain a subscribed NSSAI of a user of the user identifier.

In this embodiment, the eighth request message is used to obtain the S-NSSAI of the network slice example subscribed by the user, that is, the subscription NSSAI of the user, where the subscription NSSAI of the user includes one or more S-NSSAIs.

S503, the UDM sends the signed NSSAI of the user to the first AMF, and the first AMF receives the signed NSSAI of the user sent by the UDM.

And S504, if the first AMF cannot provide service for all network slice instances corresponding to the signed NSSAI of the user, sending a first request message to a first NSSF, wherein the first request message comprises the position information of the user and the signed NSSAI of the user.

In the embodiment of the present application, the first AMF records the S-NSSAI of the network slice instance supported by the first AMF. If the first AMF determines that the first AMF can not provide service for all network slice instances corresponding to the signed NSSAI of the user according to the signed NSSAI of the user, namely all S-NSSAIs in the signed NSSAI of the user, the first AMF sends a first request message to the first NSSF.

In some embodiments of the present application, the registration request message further includes a request NSSAI of the user, the request NSSAI being used to select a network slice instance for the user. The first request message further includes a request NSSAI of the user, and if the first AMF cannot provide service for all network slice instances corresponding to one or more S-NSSAIs existing in both the subscription NSSAI and the request NSSAI, the first request message is sent to the first NSSF.

S505, the first NSSF determines whether the first NSSF records information of a network slice instance allowing the user to access the first area, where the first area is an area represented by the location information, and the first NSSF records information of a network slice instance supported by an AMF in the first area.

In an embodiment of the present application, the first request message may further include a subscription NSSAI and/or a subscriber identity of the subscriber. The first request message may also include a request NSSAI for the user.

S506, if the first NSSF determines that the first NSSF does not record the network slice instance allowing the user to access the first area, the first NSSF sends a seventh request message to the second NSSF, where the seventh request message includes the location information of the user and the subscription NSSAI of the user, and the seventh request message is used to request the second NSSF to select the network slice instance allowing the user to access the first area.

Wherein, the second NSSF records therein network slice examples supported by AMFs of K regions, where the K regions include the first region, and K is a positive integer greater than 1.

In some embodiments of the present application, the first NSSF has recorded therein an S-NSSAI of the network slice instance supported by the AMF in the first region. The first NSSF acquires the S-NSSAI of the network slice instance subscribed by the user, that is, the subscription NSSAI of the user, and according to the subscription NSSAI of the user and the location information, it may be determined whether the network slice instance, which is allowed to access the first area and recorded by the first NSSF, exists in all network slice instances corresponding to the subscription NSSAI of the user.

In some embodiments of the present application, the first NSSF is a L-NSSF of the K regions described above and the second NSSF is a G-NSSF. If the user is a global user, no network slice example ordered by the global user is recorded on the first NSSF; if the subscriber is a roaming subscriber located in another area, the first NSSF may not record the network slice instance subscribed by the subscriber. Since the second NSSF stores both information of network slice instances supported by the AMFs in the K regions and information of network slice instances supported by the global AMF, in the two cases, the first NSSF may request the second NSSF to provide a network slice selection service for the user.

In an embodiment of the present application, the seventh request message may further include a subscription NSSAI and/or a user identifier of the user. In addition, the seventh request message may further include a request NSSAI of the user.

S507, the second NSSF selects, from the network slice instances recorded in the second NSSF, a network slice instance allowing access to the first area for the user.

It is to be understood that the second NSSF records information of the AMF-supported network slice instances of the first area, and records information of the network slice instances subscribed by the user. Therefore, according to the subscription NSSAI of the user and the location information, it may be determined whether a network slice instance allowing access to the first area exists in all network slice instances corresponding to the subscription NSSAI of the user.

In some embodiments of the present application, if the network slice instance subscribed by the user includes a network slice instance allowing the user to access the first area, the first network slice instance is selected by the second NSSF from network slice instances allowing the user to access the first area in the network slice subscribed by the user. If the network slice example subscribed by the user does not contain the network slice example allowing the user to access in the first area, the first network slice example is the network slice example allowing the user to access in the first area selected by the second NSSF from the network slice examples recorded in the second NSSF according to the roaming mapping table. The roaming mapping table includes a mapping relationship between the subscribed NSSAI of the user and the allowed NSSAI of the user, and the allowed NSSAI of the user includes an S-NSSAI of a network slice example that the user is allowed to access in the first area.

It can be understood that, if the user subscribes to the roaming service, when the network slice instance subscribed by the user does not include the network slice instance allowing the user to access in the first area, and it is determined that the user subscribes to the relevant roaming service according to the subscription information stored by the user in the UDM, the network slice instance may be selected for the user according to the roaming mapping table.

S508, the second NSSF sends, to the first NSSF, the indication information of the first network slice instance and the identifier of the second AMF, where the first NSSF receives the indication information of the first network slice instance and the identifier of the second AMF sent by the second NSSF, and the second AMF is an AMF configured in the first network slice instance.

S509, the first NSSF sends, to the first AMF, the indication information of the first network slice instance and the identifier of the second AMF, and the first AMF receives, from the first NSSF, the indication information of the first network slice instance and the identifier of the second AMF.

Optionally, the second AMF includes one or more AMFs configured in the first network slice instance.

S510, if the first AMF determines that the first AMF cannot provide service for the first network slice instance according to the indication information of the first network slice instance, determining the identifier of the target AMF according to the identifier of the second AMF.

S511, the first AMF sends a registration request message from the UE to the target AMF, and the target AMF receives the registration request message sent by the first AMF.

In some embodiments of the present application, after the first AMF receives the S-NSSAI of the first network slice instance sent by the first NSSF, if the first AMF determines that the first AMF can provide a service for the first network slice instance according to the S-NSSAI of the network slice instance recorded by the first AMF, the first AMF serves as a target AMF, and the UE may register to the network through the first AMF. And if the first AMF determines that the first AMF cannot provide service for the first network slice example and the second AMF only comprises one AMF, determining that the second AMF is the target AMF, and sending a registration request message from the UE to the target AMF by the first AMF. If the first AMF determines that the first AMF cannot provide a service for the first network slice instance and the second AMF only includes multiple AMFs, the first AMF may send a request message to the NRF, request to determine an identifier of the target AMF according to the identifier of the second AMF, and send a registration request message from the UE to the target AMF.

In this embodiment, before the second NSSF receives the seventh request message sent by the first NSSF, the network slice instance data supported by the AMFs in the K regions is synchronized to the second NSSF, so that the second NSSF may provide a network slice selection service for users in the K regions. The synchronization of network slice instance data is described in detail below.

As shown in fig. 6, before the second NSSF receives the seventh request message sent by the first NSSF, the network slice selection method provided in the embodiment of the present application further includes, but is not limited to, steps S601 to S603. Possible implementations of embodiments of the method are described further below.

S601, the first AMF sends a ninth request message to the first NSSF, where the first NSSF receives the ninth request message sent by the first AMF, and the ninth request message includes an identifier of the first AMF and information of a network slice instance supported by the first AMF; the ninth request message is for requesting the first NSSF to add the first AMF-supported network slice instance to the network slice instance recorded by the first NSSF.

S602, the first NSSF sends a second request message to a second NSSF, the second NSSF receives the second request message sent by the first NSSF, and the second request message comprises an identifier of the first NSSF, an identifier of the first AMF and information of a network slice example supported by the first AMF; the second request message is for requesting the second NSSF to add the network slice instance supported by the first AMF to the network slice instances recorded by the second NSSF.

S603, the second NSSF adds the network slice instance supported by the first AMF to the network slice instance recorded by the second NSSF.

Optionally, the ninth request message further includes an identifier of an AMF of the network slice instance configuration supported by the first AMF. Examples of network slices supported by the second NSSF first AMF include: and recording the information of the network slice instance supported by the first AMF and the identification of the AMF configured by the network slice instance supported by the first AMF.

It is understood that the first AMF is an additional AMF of the first area, and when one AMF is added to the first area, the additional AMF sends a request message to the first NSSF to notify the first NSSF to record the network slice instance supported by the additional AMF. The first NSSF records the network slice example supported by the newly added AMF, and simultaneously sends a request message to the second NSSF so as to synchronously add the network slice example supported by the newly added AMF into the second NSSF by taking the AMF as a granularity. And the network slice example supported by the newly added AMF is recorded in the second NSSF in the network slice example corresponding to the first NSSF.

Optionally, after the adding, by the second NSSF, the network slice instance supported by the first AMF to the network slice instance recorded by the second NSSF, the method further includes:

s604, the first AMF sends a tenth request message to the first NSSF, where the first NSSF receives the tenth request message sent by the first AMF, and the tenth request message includes an identifier of the first AMF and information of the second network slice instance; the tenth request message is for requesting the first NSSF to add the second network slice instance to the first AMF-supported network slice instance.

S605, the first NSSF sends a third request message to a second NSSF, the second NSSF receives the third request message sent by the first NSSF, and the third request message comprises the identification of the first NSSF, the identification of the first AMF and the information of a second network slice example; the third request message is for requesting the second NSSF to add the second network slice instance to the first AMF-supported network slice instance.

S606, the second NSSF records the second network slice instance into the network slice instance supported by the first AMF.

Optionally, the tenth request message further includes an identifier of an AMF configured by the second network slice instance. The second NSSF record second network slice instance includes: information of the second network slice instance and an identification of the AMF of the second network slice instance configuration are recorded.

It is to be understood that the second network slice instance is an additional network slice instance that can be supported by the first AMF, and when the first AMF adds one additional network slice instance, the first AMF sends a request message to the first NSSF to notify the first NSSF to record the additional network slice instance of the first AMF. And the first NSSF records the newly added network slice example of the first AMF, and simultaneously sends a request message to the second NSSF so as to synchronously add the newly added network slice example of the first AMF into the second NSSF. The newly added second network slice instance is recorded in the second NSSF in the network slice instance of the first AMF corresponding to the first NSSF.

Optionally, after the second NSSF adds the network slice instance supported by the first AMF to the network slice instance recorded by the second NSSF, the method further includes:

s607, the first AMF sends an eleventh request message to the first NSSF, the first NSSF receives the eleventh request message sent by the first AMF, and the eleventh request message includes an identifier of the first AMF, indication information of the third network slice instance, and information of the fourth network slice instance; the eleventh request message is for requesting the first NSSF to replace the third network slice instance supported by the first AMF with the fourth network slice instance.

S608, the first NSSF sends a fourth request message to the second NSSF, and the second NSSF receives the fourth request message sent by the first NSSF, where the fourth request message includes an identifier of the first NSSF, an identifier of the first AMF, indication information of the third network slice instance, and information of the fourth network slice instance; the fourth request message is for requesting the second NSSF to replace the third network slice instance supported by the first AMF with a fourth network slice instance.

S609, the second NSSF replaces the third network slice instance supported by the first AMF of the second NSSF record with the fourth network slice instance.

Optionally, the eleventh request message further includes an identifier of an AMF configured by the fourth network slice instance. The second NSSF record fourth network slice instance includes: information of the fourth network slice instance and an identification of the AMF configured for the fourth network slice instance are recorded.

It is to be appreciated that the fourth network slice instance is a new network slice instance supported by the first AMF and the third network slice instance is an old network slice instance supported by the first AMF that is replaced by the fourth network slice instance. When the third network slice instance supported by the first AMF is replaced by the fourth network slice instance, the first AMF cannot support the third network slice instance. When a replacement update occurs to one network slice instance of the first AMF, the first AMF sends a request message to the first NSSF to inform the first NSSF to record that the first AMF replaces the updated network slice instance. The first NSSF records the network slice instance after the first AMF replacement and simultaneously sends a request message to the second NSSF to synchronize the network slice instance after the first AMF replacement and the updating to the second NSSF. The fourth network slice instance is recorded in the second NSSF in the network slice instance of the first AMF corresponding to the first NSSF.

s610, the first AMF sends a twelfth request message to the first NSSF, the first NSSF receives the twelfth request message sent by the first AMF, and the twelfth request message comprises the identification of the first AMF and the indication information of the fifth network slice example; the twelfth request message is for requesting the first NSSF to remove the fifth network slice instance from the first AMF-supported network slice instances.

S611, the first NSSF sends a fifth request message to the second NSSF, and the second NSSF receives the fifth request message sent by the first NSSF, where the fifth request message includes an identifier of the first NSSF, an identifier of the first AMF, and indication information of a fifth network slice instance; the fifth request message is for requesting the second NSSF to remove the fifth network slice instance from the first AMF-supported network slice instances.

S612, the second NSSF deletes the fifth network slice instance supported by the first AMF of the second NSSF record.

It is to be understood that the fifth network slice instance is an old network slice instance supported by the first AMF, and when the fifth network slice instance is no longer supported by the first AMF, the first AMF sends a request message to the first NSSF to notify the first NSSF to remove the fifth network slice instance supported by the first AMF of the first NSSF record. The first NSSF removes a fifth network slice instance supported by the first AMF of the first NSSF record, and simultaneously sends a request message to the second NSSF to synchronously update the network slice instance supported by the first AMF into the second NSSF. The fifth network slice instance is removed from the network slice instance of the first AMF corresponding to the first NSSF recorded in the second NSSF.

s613, the first AMF sends a thirteenth request message to the first NSSF, and the first NSSF receives the thirteenth request message sent by the first AMF, where the thirteenth request message includes an identifier of the first AMF; the thirteenth request message is for requesting the first NSSF to remove the network slice instance supported by the first AMF from the network slice instances recorded by the first NSSF.

S614, the first NSSF sends a sixth request message to the second NSSF, and the second NSSF receives the sixth request message sent by the first NSSF, where the sixth request message includes an identifier of the first NSSF and an identifier of the first AMF; the sixth request message is for requesting the second NSSF to remove the network slice instance supported by the first AMF from the network slice instance recorded by the second NSSF.

And S615, the second NSSF removes the network slice instance supported by the first AMF corresponding to the first NSSF from the network slice instance recorded by the second NSSF.

It is to be appreciated that when the first AMF is deleted, the first AMF sends a request message to the first NSSF to notify the first NSSF to delete the network slice instance of the first AMF for the first NSSF record. The first NSSF deletes the network slice instance of the first AMF of the first NSSF record, and simultaneously sends a request message to the second NSSF so as to integrally synchronize the AMF corresponding to the first NSSF into the second NSSF by taking the AMF as granularity. The network slice instance supported by the first AMF is deleted from the network slice instance corresponding to the first NSSF recorded in the second NSSF.

In this embodiment, if it is determined that the first NSSF does not record the information of the network slice instance subscribed by the user, the first NSSF may send a request message to the second NSSF to request the second NSSF to provide the network slice selection service for the user. In this embodiment of the present application, only the network slice instances supported by the AMFs in the first region are recorded in the first NSSF, and the network slice instances supported by the AMFs in all regions are recorded in the second NSSF, so that the second NSSF may provide the network slice selection service for the user. By implementing the method and the device, the risk of NSSF load overload is reduced, the access time delay of the user is reduced, and the user experience is effectively improved. In addition, the data of the network slice examples supported by the AMF of all the areas are automatically synchronized only on the second NSSF, the scheme is low in cost and quick in response, and manual misoperation can be avoided.

Based on the communication system shown in fig. 3, the network slice selection method provided in the embodiment of the present application is described below with respect to two specific application scenarios.

Scene one: the local user belonging to the area i initiates a registration request in the area 1 through the UE, and it is the global AMF to process the registration request.

As shown in fig. 7, the method for selecting a network slice based on scenario one provided in the embodiment of the present application includes, but is not limited to, steps S701 to S708. Possible implementations of embodiments of the method are described further below.

S701, a first local user sends a registration request message to a first global AMF through UE in an area 1, the first global AMF receives the registration request message sent by the UE, and the registration request message comprises a user identifier of the first local user and position information of the first local user.

In this embodiment of the present application, the home location of the first local user is an area i, the location information represents an area 1, and the area i may be the area 1, or may be another area of the K areas, which is not specifically limited herein.

S702, the first global AMF sends an eighth request message to the UDM, and the UDM receives the eighth request message sent by the first global AMF, where the eighth request message includes a user identifier of the first local user, and the eighth request message is used to obtain a subscription nsai of the first local user.

S703, the UDM sends the signed NSSAI of the first local user to the first global AMF, and the first global AMF receives the signed NSSAI of the first local user sent by the UDM.

S704, if the first global AMF cannot provide service for all network slice instances corresponding to the signed NSSAI of the local user, the first global AMF sends a first request message to the G-NSSF, and the G-NSSF receives the first request message sent by the first global AMF, wherein the first request message comprises the position information of the first local user and the signed NSSAI of the first local user.

In some embodiments of the present application, the first request message may further include parameters such as a request S-NSSAI of the first local user and/or a user identification of the first local user.

It is to be understood that the first global AMF is used to provide mobile and access services for global users, and the first global AMF cannot provide services for all network slice instances corresponding to the subscribed NSSAI of the local user.

S705, the G-NSSF selects, according to the subscribed NSSAI of the first local user, a first network slice instance that allows the first local user to access the area 1 from the network slice instances recorded in the G-NSSF.

S706, the G-NSSF sends the identification of the S-NSSAI and the second AMF of the first network slice example to the first global AMF, the first global AMF receives the identification of the S-NSSAI and the second AMF of the first network slice example sent by the G-NSSF, and the second AMF is the AMF configured in the first network slice example.

And S707, if the first AMF determines that the first AMF cannot provide service for the first network slice instance according to the S-NSSAI of the first network slice instance, determining the identifier of the target AMF according to the identifier of the second AMF.

S708, the first AMF sends a registration request message from the UE to the target AMF, and the target AMF receives the registration request message sent by the first AMF.

Scene two: the first local user, which is home to area i, initiates a registration request in area 1 via the UE101, and it is the local AMF103 of area 1 that processes the registration request, i is not equal to 1.

As shown in fig. 8, the method for selecting a network slice based on scenario two according to the embodiment of the present application includes, but is not limited to, steps S801 to S812. Possible implementations of embodiments of the method are described further below.

S801, a first local user belonging to an area i sends a registration request message to a first local AMF through UE in an area 1, the first local AMF receives the registration request message sent by the UE, the registration request message includes a user identifier of the first local user in the area i and location information of the first local user, and i is not equal to 1.

And S802, the first local AMF sends an eighth request message to the UDM, the UDM receives the eighth request message sent by the first local AMF, the eighth request message comprises a first local user identifier, and the eighth request message is used for acquiring the signed NSSAI of the first local user corresponding to the user identifier.

S803, the UDM sends the subscription NSSAI of the first local user to the first local AMF, and the first local AMF receives the subscription NSSAI of the first local user sent by the UDM.

S804, if the first local AMF cannot provide service for all network slice instances corresponding to the subscription NSSAI of the first local user, sending a first request message to the L-NSSF1 of the area 1, where the first request message includes location information of the first local user and the subscription NSSAI of the first local user.

It is to be understood that the first local user is a roaming user from the K areas except area 1, and the first local AMF may not be able to provide service for all network slice instances corresponding to the subscribed NSSAI of the first local user.

And S805, if the L-NSSF1 determines that all network slice examples corresponding to the signed NSSAI of the first local user are not recorded in the L-NSSF1, the L-NSSF1 sends a seventh request message to the G-NSSF, wherein the seventh request message comprises the position information of the first local user and the signed NSSAI of the first local user, and the seventh request message is used for requesting the G-NSSF to select the network slice example allowing the first local user to access the area 1.

It is understood that the first local subscriber is a roaming subscriber from the K areas except area 1, and therefore, the signed NSSAI of the first local subscriber may not be recorded in L-NSSF1 for all network slice instances. The G-NSSF records network slice instances supported by the AMFs of the K regions, and thus, the G-NSSF records all network slice instances corresponding to the contracted NSSAI of the first local user. The G-NSSF may provide network slice selection services for the first local user.

And S806, the G-NSSF selects a first network slice example allowing the first local user to access the area 1 from the network slice examples recorded by the G-NSSF according to the signed NSSAI of the first local user.

And S807, the identification of the S-NSSAI and the second local AMF of the first network slice example sent by the G-NSSF to the L-NSSF1, wherein the first L-NSSF1 receives the identification of the S-NSSAI and the second local AMF of the first network slice example sent by the G-NSSF, and the second local AMF is the AMF configured in the first network slice example.

And S808, the L-NSSF1 sends the S-NSSAI of the first network slice example and the identification of the second local AMF to the first local AMF, and the first local AMF receives the S-NSSAI of the first network slice example and the identification of the second local AMF sent by the L-NSSF 1.

And S809, if the first local AMF determines that the first AMF can not provide service for the first network slice instance according to the S-NSSAI of the first network slice instance, determining the identifier of the target AMF according to the identifier of the second local AMF.

S810, the first local AMF sends a registration request message from the UE to the target AMF, and the target AMF receives the registration request message sent by the first local AMF.

Scene three: the global user initiates a registration request in area 1 through the UE, and it is the first local AMF of area 1 to process the registration request.

As shown in fig. 9, the method for selecting a network slice based on scenario three provided in the embodiment of the present application includes, but is not limited to, steps S901 to S912. Possible implementations of embodiments of the method are described further below.

S901, the global user sends a registration request message to a first local AMF through the UE in the area 1, the first local AMF receives the registration request message sent by the UE, and the registration request message includes the user identification of the global user and the position information of the global user.

And S902, the first local AMF sends an eighth request message to the UDM, the UDM receives the eighth request message sent by the first local AMF, the eighth request message comprises a user identifier of the global user, and the eighth request message is used for acquiring the signed NSSAI of the global user corresponding to the user identifier.

S903, the UDM sends the signing NSSAI of the global user to the first local AMF, and the first local AMF receives the signing NSSAI of the global user sent by the UDM.

S904, if the first local AMF cannot provide service for all network slice instances corresponding to the subscription NSSAI of the global user, sending a first request message to the L-NSSF1 of the area 1, where the first request message includes location information of the global user and the subscription NSSAI of the global user.

It is to be appreciated that the first local AMF cannot serve all network slice instances corresponding to the contracted NSSAI of the global user.

S905, if it is determined by L-NSSF1 that all network slice instances corresponding to the global user' S subscription NSSAI are not recorded in L-NSSF1, then L-NSSF1 sends a seventh request message to G-NSSF, where the seventh request message includes location information of the global user and the subscription NSSAI of the global user, and the seventh request message is used to request G-NSSF to select a network slice instance allowing the global user to access area 1.

It can be understood that all network slice instances corresponding to the signed NSSAI of the global user are not recorded in L-NSSF1, and all network slice instances corresponding to the signed NSSAI of the global user are recorded on G-NSSF. The G-NSSF may provide network slice selection services for global users.

S906, the G-NSSF selects a first network slice example allowing the global user to access the area 1 from the network slice examples recorded by the G-NSSF according to the signed NSSAI of the global user.

And S907, the G-NSSF sends the identification of the S-NSSAI and the second local AMF of the first network slice example to the L-NSSF1, the first L-NSSF1 receives the identification of the S-NSSAI and the second local AMF of the first network slice example sent by the G-NSSF, and the second local AMF is the AMF configured in the first network slice example.

And S908, the L-NSSF1 sends the S-NSSAI of the first network slice example and the identification of the second local AMF to the first local AMF, and the first local AMF receives the S-NSSAI of the first network slice example and the identification of the second local AMF sent by the L-NSSF 1.

And S909, if the first local AMF determines that the first AMF can not provide service for the first network slice instance according to the S-NSSAI of the first network slice instance, determining the identifier of the target AMF according to the identifier of the second local AMF.

S910, the first local AMF sends a registration request message from the UE to the target AMF, and the target AMF receives the registration request message sent by the first local AMF.

Fig. 10 is a schematic structural diagram of a network device according to an embodiment of the present invention. As shown in fig. 10, the network device 10 includes: a first receiving unit 11.

A first receiving unit 11, configured to receive a first request message from the first AMF, where the first request message includes location information of a user.

A first receiving unit 11, further configured to receive indication information of the first network slice instance from the second NSSF and an identification of the second AMF if it is determined that the network device does not record information of a network slice instance allowing the user to access the first area; the first network slice instance is a network slice instance selected from network slice instances recorded in the second NSSF that allows the user to access a first area, which is an area characterized by the location information.

In one implementation, the first request message further includes a subscription NSSAI of the user; the first receiving unit 11 is specifically configured to: and if the network equipment is determined not to record the information of the network slice example allowing the user to access the first area according to the signed NSSAI of the user, receiving the indication information of the first network slice example and the identification of the second AMF from the second NSSF.

In one implementation, the first request message further includes a user identifier; the first receiving unit 11 is specifically configured to: and if the network equipment does not record the information of the network slice example allowing the user to access the first area according to the signed NSSAI of the user characterized by the user identification, receiving the indication information of the first network slice example from the second NSSF and the identification of the second AMF, and requesting the UDM for obtaining the signed NSSAI of the user according to the user identification.

In an implementation manner, before the first receiving unit 11 receives the first request message from the first AMF, the network device further includes: and the first sending unit is used for sending a second request message to the second NSSF, wherein the second request message comprises the identification of the first AMF and the information of the network slice instances supported by the first AMF, and the second request message is used for requesting the second NSSF to record the network slice instances supported by the first AMF into the network slice instances recorded by the second NSSF.

In one implementation manner, after the first sending unit sends the second request message to the second NSSF, the first sending unit is further configured to: and sending a third request message to the second NSSF, wherein the third request message comprises the identification of the first AMF and the information of the second network slice instance, and the third request message is used for requesting the second NSSF to add the second network slice instance to the network slice instances supported by the first AMF.

In one implementation manner, after the first sending unit sends the second request message to the second NSSF, the first sending unit is further configured to: and sending a fourth request message to the second NSSF, wherein the fourth request message comprises the identification of the first AMF, the indication information of the third network slice instance and the information of the fourth network slice instance, and the fourth request message is used for requesting the second NSSF to replace the third network slice instance supported by the first AMF with the fourth network slice instance.

In one implementation, the user is a global user.

Fig. 11 is a schematic structural diagram of a network device according to an embodiment of the present invention. As shown in fig. 11, the network device 20 includes: a third receiving unit 21 and a second transmitting unit 22.

A third receiving unit 21, configured to receive a seventh request message from the first NSSF; the seventh request message is used for requesting the network device to select a network slice instance allowing the user to access in a first area, the first area is an area characterized by the location information, and the first NSSF records information of the network slice instance supported by the AMF in the first area;

a second sending unit 22, configured to send indication information of the first network slice instance to the first NSSF;

In one implementation, before the third receiving unit 21 receives the seventh request message from the first NSSF, the third receiving unit 21 is further configured to: and receiving a second request message from the first NSSF, wherein the second request message comprises the identification of the first AMF and the information of the network slice instances supported by the first AMF, and the second request message is used for requesting the network equipment to record the network slice instances supported by the first AMF into the network slice instances recorded by the network equipment.

In one implementation, after the third receiving unit 21 receives the second request message from the first NSSF, the third receiving unit 21 is further configured to: a third request message is received from the first NSSF, the third request message including an identification of the first AMF, information of the second network slice instance, the third request message for requesting the network device to add the second network slice instance to the network slice instances supported by the first AMF.

In an implementation manner, after the third receiving unit 21 receives the second request message from the first NSSF, the third receiving unit 21 is further configured to: and receiving a fourth request message from the first NSSF, wherein the fourth request message comprises the identification of the first AMF, the indication information of the third network slice instance and the information of the fourth network slice instance, and the fourth request message is used for requesting the network equipment to replace the third network slice instance supported by the first AMF with the fourth network slice instance.

In one implementation, after the third receiving unit 21 receives the second request message from the first NSSF, the third receiving unit 21 is further configured to: receiving a fifth request message from the first NSSF, the fifth request message including an identification of the first AMF and indication information of a fifth network slice instance, the fourth request message for requesting the network device to remove the fifth network slice instance from the network slice instances supported by the first AMF.

In an implementation manner, after the third receiving unit 21 receives the second request message from the first NSSF, the third receiving unit 21 is further configured to: a sixth request message is received from the first NSSF, the sixth request message including an identification of the first AMF, the sixth request message requesting the network device to remove the network slice instance of the first AMF from the network slice instances recorded by the network device.

In one implementation, the seventh request message is that the first NSSF is not recording a network slice instance that allows the user to access the first area upon determining that the first NSSF is not recording the network slice instance.

In one implementation, the user is a global user.

Referring to fig. 12, fig. 12 shows a user equipment 1000 provided in an embodiment of the present application. As shown in fig. 12, the user equipment 1000 may include: one or more user equipment processors 1001, memory 1002, communications interface 1003, receiver 1005, transmitter 1006, coupler 1007, antenna 1008, user equipment interface 1009. These components may be connected by a bus 1004, or otherwise, as illustrated by the bus connection in FIG. 12. Wherein:

the communication interface 1003 may be used for the user equipment 1000 to communicate with other communication devices, such as network devices. In particular, the network device may be the user equipment 1000 shown in fig. 12. Specifically, the communication interface 1003 may be a 5G communication interface, or may be a communication interface of a future air interface. Not limited to wireless communication interfaces, the user equipment 1000 may also be configured with a wired communication interface 1003, such as a Local Access Network (LAN) interface. A transmitter 1006 may be used for transmit processing of signals output by the user equipment processor 1001. Receiver 1005 may be used for receive processing of mobile communication signals received by antenna 1008.

In some embodiments of the present application, the transmitter 1006 and receiver 1005 may be considered a wireless modem. In the user equipment 1000, the number of the transmitter 1006 and the receiver 1005 may be one or more. The antenna 1008 may be used to convert electromagnetic energy in transmission line to electromagnetic wave in free space or vice versa. The coupler 1007 is used to divide the mobile communication signal received by the antenna 1008 into a plurality of channels and distribute the channels to the plurality of receivers 1005.

In addition to the transmitter 1006 and receiver 1005 shown in fig. 12, the user device 1000 may also include other communication components, such as a GPS module, a bluetooth (bluetooth) module, a wireless fidelity (Wi-Fi) module, and so forth. Not limited to wireless communications, the user device 1000 may also be configured with a wired network interface (e.g., a LAN interface) to support wired communications.

The user device 1000 may also include an input-output module. The input and output module may be used to implement interaction between the user device 1000 and the user device/external environment, and may mainly include an audio input and output module, a key input module, a display, and the like. Specifically, the input/output module may further include: cameras, touch screens, and sensors, among others. The input and output modules all communicate with the user equipment processor 1001 via the user equipment interface 1009.

The memory 1002 is coupled to the user device processor 1001 for storing various software programs and/or sets of instructions. In particular, the memory 1002 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory 1002 may store an operating system (hereinafter referred to simply as a system), such as an embedded operating system like ANDROID, IOS, WINDOWS, or LINUX. The memory 1002 may also store a network communication program that may be used to communicate with one or more additional devices, one or more user devices, one or more network devices.

In some embodiments of the present application, the memory 1002 may be used for storing an implementation program of the network slice selection method provided by one or more embodiments of the present application on the user equipment 1000 side. For implementation of the network slice selection method provided in one or more embodiments of the present application, please refer to the above embodiments.

The user equipment processor 1001 may be used to read and execute computer readable instructions. Specifically, the ue processor 1001 may be configured to invoke a program stored in the memory 1002, for example, an implementation program of the method for managing a network slice provided in one or more embodiments of the present application on the ue 1000 side, and execute instructions contained in the program.

It is understood that the user equipment 1000 may be the user equipment 101 in the communication system 100 shown in fig. 1, and may be implemented as a handheld device, a vehicle-mounted device, a wearable device, a computing device, and various forms of user equipment, a Mobile Station (MS), a terminal (terminal), and the like.

It should be noted that the user equipment 1000 shown in fig. 12 is only one implementation manner of the embodiment of the present application, and in practical applications, the user equipment 1000 may further include more or less components, which is not limited herein.

Referring to fig. 13, fig. 13 illustrates a network device 1100 provided in an embodiment of the present application. As shown in fig. 13, the network device 1100 may include: one or more network device processors 1101, memory 1102, and communication interface 1103. These components may be connected by a bus 1104 or otherwise, which is illustrated in FIG. 13 as being connected by a bus. Wherein:

the communication interface 1103 may be used for the network device 1100 to communicate with other communication devices, such as user devices or other network devices. Specifically, the communication interface 1103 may be a 5G communication interface, or a communication interface of a future air interface. Without being limited to a wireless communication interface, the network device 1100 may also be configured with a wired communication interface 1103 to support wired communication, e.g., a backhaul link between one network device 1100 and other network devices 1100 may be a wired communication connection.

The memory 1102 is coupled to the network device processor 1101 for storing various software programs and/or sets of instructions. In particular, the memory 1102 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory 1102 may store an operating system (hereinafter referred to as a system), such as an embedded operating system (os) like uCOS, vxWorks, RTLinux, etc. The memory 1102 may also store network communication programs that may be used to communicate with one or more additional devices, one or more user devices, and one or more network devices.

In embodiments of the present application, the network device processor 1101 may be configured to read and execute computer readable instructions. In particular, the network device processor 1101 may be configured to call a program stored in the memory 1102, for example, a program for implementing the network slice selection method provided by one or more embodiments of the present application on the network device 1100 side, and execute instructions contained in the program.

It is to be appreciated that the network device 1100 can be a core network entity, such as an AMF, NSSF, UDM, or the like.

It should be noted that the network device 1100 shown in fig. 13 is only one implementation manner of the embodiment of the present application, and in practical applications, the network device 1100 may also include more or less components, which is not limited herein.

The embodiment of the present application further provides a chip system 1200, which includes one or more processors 1201 and an interface circuit 1202, where the processors 1201 and the interface circuit 1202 are connected.

The processor 1201 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be implemented by integrated logic circuits of hardware or instructions in the form of software in the processor 1201. The processor 1201 may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. The methods, steps disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The interface circuit 1202 may perform transmission or reception of data, instructions, or information, and the processor 1201 may perform processing using the data, instructions, or other information received by the interface circuit 1202, and may transmit processing completion information through the interface circuit 1202.

Optionally, the chip system further includes a memory 1203, and the memory 1203 may include a read-only memory and a random access memory and provide the processor with operating instructions and data. A portion of the memory 1203 may also include non-volatile random access memory (NVRAM).

Optionally, the memory 1203 stores executable software modules or data structures, and the processor 1203 may execute corresponding operations by calling operation instructions stored in the memory (the operation instructions may be stored in an operating system).

Optionally, the chip system may be used in a user equipment or a network device according to the embodiments of the present application. Optionally, the interface circuit 1202 is configured to perform the steps of receiving and transmitting of the user equipment, the network device, and the like in the embodiments shown in fig. 4 to 9. The processor 1201 is configured to execute steps of processing of the user equipment, the network device, and the like in the embodiments illustrated in fig. 4 to 9. The memory 1203 is used to store data and instructions for the user devices, network devices, etc. in the embodiments shown in fig. 4-9. The network equipment comprises core network entities such as AMF, NSSF and UDM.

The embodiment of the application also provides a computer readable storage medium. The methods described in the above method embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media may include both computer storage media and communication media, and may include any medium that can transfer a computer program from one place to another. A storage media may be any available media that can be accessed by a computer.

As an alternative design, a computer-readable storage medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital Subscriber Line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes Compact Disc (CD), laser disc, optical disc, digital Versatile Disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

The embodiment of the application also provides a computer program product. The methods described in the above method embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. If implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions described in the above method embodiments are generated in whole or in part when the above computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, special purpose computer, computer network, network appliance, user equipment, or other programmable device.

The above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for network slice selection, comprising:

a first network slice selection function entity NSSF receives a first request message from a first access and mobility management function entity AMF, wherein the first request message comprises the position information of a user;

receiving, by the first NSSF, indication information of the first network slice instance and an identification of the second AMF from a second NSSF if it is determined that the first NSSF does not record information that allows the user to access the network slice instance of the first area; the first network slice instance is a network slice instance selected from network slice instances recorded in the second NSSF and allowing the user to access the first area, the first area is an area characterized by the location information, and the second AMF is an AMF configured in the first network slice instance;

the information of the network slice instance includes indication information of the network slice instance, an identifier of an AMF configured in the network slice instance, and an identifier of an area served by the network slice instance, the first NSSF records information of the network slice instance supported by the AMF in the first area, the second NSSF records information of the network slice instance supported by the AMF in K areas, the K areas include the first area, and K is a positive integer greater than 1.

2. The method according to claim 1, wherein the first request message further comprises subscription network slice selection assistance information NSSAI of the user; the determining, by the first NSSF, that the first NSSF does not record information that allows the user to access the network slice instance in the first area, the receiving, by the first NSSF, the indication information of the first network slice instance from the second NSSF and the identification of the second AMF including:

if it is determined that the first NSSF does not record information that allows the user to access the network slice instance of the first area according to the subscribed NSSAI of the user, the first NSSF receives indication information of the first network slice instance from the second NSSF and the identifier of the second AMF.

3. The method of claim 1, wherein the first request message further comprises a user identification of the user; the receiving, by the first NSSF, the indication information of the first network slice instance and the identification of the second AMF from the second NSSF if it is determined that the first NSSF does not record information that allows the user to access the network slice instance of the first area includes:

if it is determined that the first NSSF does not record information of a network slice instance allowing the user to access the first area according to the signed NSSAI of the user characterized by the user identifier, the first NSSF receives indication information of the first network slice instance from the second NSSF and an identifier of the second AMF, and the signed NSSAI of the user is obtained by the first NSSF requesting a unified data management entity (UDM) according to the user identifier.

4. The method according to claim 1, wherein before the first network slice selection function entity NSSF receives the first request message from the first access and mobility management function entity AMF, the method further comprises:

the first NSSF sends a second request message to the second NSSF, wherein the second request message comprises the identification of the first AMF and the information of the network slice instances supported by the first AMF, and the second request message is used for requesting the second NSSF to record the network slice instances supported by the first AMF into the network slice instances recorded by the second NSSF.

5. The method according to claim 4, wherein after the first NSSF sends a second request message to the second NSSF, the method further comprises:

the first NSSF sends a third request message to the second NSSF, where the third request message includes an identifier of the first AMF and information of a second network slice instance, and the third request message is used to request the second NSSF to record the second network slice instance in a network slice instance supported by the first AMF.

6. The method according to claim 4, wherein after the first NSSF sends a second request message to the second NSSF, the method further comprises:

the first NSSF sends a fourth request message to the second NSSF, where the fourth request message includes an identifier of the first AMF, indication information of a third network slice instance, and information of a fourth network slice instance, and the fourth request message is used to request the second NSSF to replace the third network slice instance supported by the first AMF with the fourth network slice instance.

7. The method according to claim 4, wherein after the first NSSF sends a second request message to the second NSSF, the method further comprises:

the first NSSF sends a fifth request message to the second NSSF, where the fifth request message includes an identifier of the first AMF and indication information of a fifth network slice instance, and the fifth request message is used to request the second NSSF to remove the fifth network slice instance from the network slice instances supported by the first AMF.

8. The method according to claim 4, wherein after the first NSSF sends a second request message to the second NSSF, the method further comprises:

the first NSSF sending a sixth request message to the second NSSF, the sixth request message including the identity of the first AMF, the sixth request message requesting the second NSSF to remove the network slice instance supported by the first AMF from the network slice instances recorded by the second NSSF.

9. The method according to any of claims 1 to 8, wherein the indication information of the network slice instance comprises NSSAI of the network slice instance.

10. The method according to any of claims 1 to 8, wherein the second NSSF further records information of network slice instances supported by a global AMF, the global AMF providing access and mobility management services for a global user, the network slice instances subscribed by the global user are allowed to access M of the K regions, M is a positive integer greater than 1 and less than or equal to K.

11. The method of claim 10, wherein the user is a global user.

12. A method for network slice selection, comprising:

the second network slice selection function entity NSSF receives a seventh request message from the first NSSF; the seventh request message includes location information of a subscriber, and the seventh request message is used to request the second NSSF to select a network slice instance allowing the subscriber to access in a first area, where the first area is an area characterized by the location information, and information of the network slice instance supported by an access and mobility management function entity AMF in the first area is recorded in the first NSSF;

the second NSSF sends the indication information of the first network slice instance and the identification of the second AMF to the first NSSF;

wherein the information of the network slice instance includes indication information of the network slice instance, an identifier of an AMF configured in the network slice instance, and an identifier of an area served by the network slice instance, the first network slice instance is a network slice instance selected from network slice instances recorded in the second NSSF, where the network slice instance allows the user to access in the first area, information of network slice instances supported by AMFs of K areas is recorded on the second NSSF, the K areas include the first area, the second AMF is the AMF configured in the first network slice instance, and K is a positive integer greater than 1.

13. The method as claimed in claim 12, wherein the seventh request message further includes signed network slice selection assistance information NSSAI of the user, and wherein the seventh request message is configured to request the second NSSF to select the network slice instance allowed to be accessed by the user in the first area according to the signed NSSAI of the user.

14. The method of claim 12, wherein the seventh request message further comprises a user identification of the user; the seventh request message is used to request the second NSSF to select a network slice instance allowing the user to access in the first area according to the signed NSSAI of the user, which is characterized by the user identifier, where the signed NSSAI of the user is obtained by the second NSSF requesting a unified data management entity UDM according to the user identifier.

15. The method according to claim 12, wherein before the second network slice selection function, NSSF, receives a seventh request message from the first NSSF, the method further comprises:

the second NSSF receives a second request message from the first NSSF, where the second request message includes an identifier of the first AMF and information of the network slice instances supported by the first AMF, and the second request message is used to request the second NSSF to record the network slice instances supported by the first AMF into the network slice instances recorded by the second NSSF.

16. The method of claim 15, wherein after the second NSSF receives the second request message from the first NSSF, the method further comprises:

the second NSSF receiving a third request message from the first NSSF, the third request message including an identification of the first AMF, information of a second network slice instance, the third request message requesting the second NSSF to add the second network slice instance to the network slice instances supported by the first AMF.

17. The method of claim 15, wherein after the second NSSF receives the second request message from the first NSSF, the method further comprises:

the second NSSF receiving a fourth request message from the first NSSF, the fourth request message including an identification of the first AMF, indication information of a third network slice instance, and information of a fourth network slice instance, the fourth request message requesting the second NSSF to replace the third network slice instance supported by the first AMF with the fourth network slice instance.

18. The method of claim 15, wherein after the second NSSF receives the second request message from the first NSSF, the method further comprises:

the second NSSF receiving a fifth request message from the first NSSF, the fifth request message including an identification of the first AMF, and indication information of a fifth network slice instance, the fifth request message requesting the second NSSF to remove the fifth network slice instance from the network slice instances supported by the first AMF.

19. The method of claim 15, wherein after the second NSSF receives the second request message from the first NSSF, the method further comprises:

the second NSSF receiving a sixth request message from the first NSSF, the sixth request message including an identification of the first AMF, the sixth request message requesting the second NSSF to remove the network slice instance of the first AMF from the network slice instance recorded by the second NSSF.

20. The method according to any of claims 12 to 19, wherein the seventh request message is sent by the first NSSF after determining that the first NSSF does not record an instance of a network slice allowing the subscriber to access the first area.

21. The method according to any of claims 12 to 19, wherein the indication information of the network slice instance comprises NSSAI of the network slice instance.

22. The method according to any of claims 12 to 19, wherein if the network slice instance corresponding to the subscription NSSAI of the user does not include the network slice instance that the user is allowed to access in the first area, the first network slice instance is the network slice instance that the second NSSF is allowed to access in the first area, which is selected from the network slice instances recorded in the second NSSF according to a roaming mapping table, the roaming mapping table includes a mapping relationship between the subscription NSSAI of the user and the allowed NSSAI of the user, and the allowed NSSAI of the user includes the NSSAI of the network slice instance that the user is allowed to access in the first area.

23. The method according to any of claims 12 to 19, wherein the second NSSF has also recorded thereon information of network slice instances supported by a global AMF, the global AMF providing access and mobility management services for global users, the network slice instances subscribed by the global users being allowed to access M of the K regions, where M is a positive integer greater than 1 and smaller than or equal to K.

24. The method of claim 23, wherein the user is a global user.

25. A network device, comprising:

a first receiving unit, configured to receive a first request message from a first access and mobility management function entity, AMF, where the first request message includes location information of a user;

a first receiving unit, further configured to receive indication information of the first network slice instance from the second NSSF and an identification of the second AMF if it is determined that the network device does not record information of network slice instances allowing the user to access the first area; the first network slice instance is a network slice instance selected from network slice instances recorded in the second NSSF and allowing the user to access the first area, the first area is an area characterized by the location information, and the second AMF is an AMF configured in the first network slice instance;

the information of the network slice instance includes indication information of the network slice instance, an identifier of an AMF configured in the network slice instance, and an identifier of an area served by the network slice instance, information of network slice instances supported by the AMF in the first area is recorded in the network device, information of network slice instances supported by AMFs in K areas is recorded on the second NSSF, the K areas include the first area, and K is a positive integer greater than 1.

26. The network device of claim 25, wherein the first request message further comprises subscription network slice selection assistance information NSSAI of the subscriber;

the first receiving unit is specifically configured to: receiving indication information of the first network slice instance and an identifier of the second AMF from the second NSSF if the network device is determined not to record information of a network slice instance allowing the user to access the first area according to the signed NSSAI of the user.

27. The network device of claim 25, wherein the first request message further comprises a subscriber identity of the subscriber;

the first receiving unit is specifically configured to: and if the network equipment does not record the information of the network slice instance allowing the user to access the first area according to the signed NSSAI of the user characterized by the user identification, receiving the indication information of the first network slice instance from the second NSSF and the identification of the second AMF, wherein the signed NSSAI of the user is obtained by the network equipment according to the user identification and requesting a unified data management entity (UDM).

28. The network device according to claim 25, wherein before the first receiving unit receives the first request message from the first access and mobility management function entity, AMF, the network device further comprises:

a first sending unit, configured to send a second request message to the second NSSF, where the second request message includes an identifier of the first AMF and information of the network slice instance supported by the first AMF, and the second request message is used to request the second NSSF to record the network slice instance supported by the first AMF into the network slice instance recorded by the second NSSF.

29. The network device of claim 28, wherein after the first sending unit sends the second request message to the second NSSF, the first sending unit is further configured to:

sending a third request message to the second NSSF, where the third request message includes an identifier of the first AMF and information of a second network slice instance, and the third request message is used to request the second NSSF to record the second network slice instance in a network slice instance supported by the first AMF.

30. The network device of claim 28, wherein after the first sending unit sends the second request message to the second NSSF, the first sending unit is further configured to:

sending a fourth request message to the second NSSF, the fourth request message including an identification of the first AMF, indication information of a third network slice instance, and information of a fourth network slice instance, the fourth request message being used to request the second NSSF to replace the third network slice instance supported by the first AMF with the fourth network slice instance.

31. The network device of claim 28, wherein after the first sending unit sends the second request message to the second NSSF, the first sending unit is further configured to:

sending a fifth request message to the second NSSF, the fifth request message including an identification of the first AMF and indication information of a fifth network slice instance, the fifth request message for requesting the second NSSF to remove the fifth network slice instance from the network slice instances supported by the first AMF.

32. The network device of claim 28, wherein after the first sending unit sends the second request message to the second NSSF, the first sending unit is further configured to:

sending a sixth request message to the second NSSF, the sixth request message including an identification of the first AMF, the sixth request message requesting the second NSSF to remove network slice instances supported by the first AMF from network slice instances recorded by the second NSSF.

33. The network device according to any of claims 25 to 32, wherein the indication information of the network slice instance comprises NSSAI of the network slice instance.

34. The network device according to any of claims 25 to 32, wherein the second NSSF further records information of network slice instances supported by a global AMF, the global AMF providing access and mobility management services for a global user, the network slice instances subscribed by the global user are allowed to access M of the K regions, M is a positive integer greater than 1 and less than or equal to K.

35. The network device of claim 34, wherein the user is a global user.

36. A network device, comprising:

a second receiving unit, configured to receive a seventh request message from the first NSSF; the seventh request message includes location information of a user, where the seventh request message is used to request the network device to select a network slice instance allowing the user to access in a first area, where the first area is an area characterized by the location information, and information of the network slice instance supported by an access and mobility management function entity AMF in the first area is recorded in the first NSSF;

a second sending unit, configured to send, to the first NSSF, indication information of a first network slice instance and an identifier of a second AMF; the information of the network slice instance includes indication information of the network slice instance, an identifier of an AMF configured in the network slice instance, and an identifier of an area served by the network slice instance, the first network slice instance is a network slice instance selected from network slice instances recorded in the network device and allowing the user to access the first area, information of network slice instances supported by AMFs of K areas is recorded on the network device, the K areas include the first area, the second AMF is the AMF configured in the first network slice instance, and K is a positive integer greater than 1.

37. The network device of claim 36, wherein the seventh request message further comprises subscription network slice selection assistance information NSSAI of the subscriber; the seventh request message is used to request the network device to select a network slice instance allowing the user to access in the first area according to the subscribed NSSAI of the user.

38. The network device of claim 36, wherein the seventh request message further comprises a subscriber identity; the seventh request message is used to request the network device to select a network slice instance allowing the user to access in the first area according to the signed NSSAI of the user, which is characterized by the user identifier, where the signed NSSAI of the user is obtained by the network device through a request from a unified data management entity UDM according to the user identifier.

39. The network device of claim 36, wherein before the second receiving unit receives the seventh request message from the first NSSF, the second receiving unit is further configured to:

receiving a second request message from the first NSSF, wherein the second request message comprises identification of a first AMF and information of network slice instances supported by the first AMF, and the second request message is used for requesting the network device to record the network slice instances supported by the first AMF into the network slice instances recorded by the network device.

40. The network device of claim 39, wherein after the second receiving unit receives the second request message from the first NSSF, the second receiving unit is further configured to:

receiving a third request message from the first NSSF, the third request message including an identification of the first AMF, information of a second network slice instance, the third request message for requesting the network device to add the second network slice instance to the network slice instances supported by the first AMF.

41. The network device of claim 39, wherein after the second receiving unit receives the second request message from the first NSSF, the second receiving unit is further configured to:

receiving a fourth request message from the first NSSF, the fourth request message including an identification of the first AMF, indication information of a third network slice instance, and information of a fourth network slice instance, the fourth request message for requesting the network device to replace the third network slice instance supported by the first AMF with the fourth network slice instance.

42. The network device of claim 39, wherein after the second receiving unit receives the second request message from the first NSSF, the second receiving unit is further configured to:

receiving a fifth request message from the first NSSF, the fifth request message including an identification of the first AMF and indication information of a fifth network slice instance, the fifth request message for requesting the network device to remove the fifth network slice instance from the network slice instances supported by the first AMF.

43. The network device of claim 39, wherein after the second receiving unit receives the second request message from the first NSSF, the second receiving unit is further configured to:

receiving a sixth request message from the first NSSF, the sixth request message including an identification of the first AMF, the sixth request message for requesting the network device to remove the network slice instance of the first AMF from the network slice instances recorded by the network device.

44. The network device of any of claims 36-43, wherein the seventh request message is sent by the first NSSF after determining that the first NSSF does not record network slice instances that allow the subscriber to access the first area.

45. The network device according to any of claims 36 to 43, wherein the indication information of the network slice instance comprises NSSAI of the network slice instance.

46. The network device according to any one of claims 36 to 43, wherein if the network slice instance corresponding to the subscription NSSAI of the user does not include the network slice instance that allows the user to access in the first area, the first network slice instance is a network slice instance that allows the user to access in the first area, which is selected by the network device from the network slice instances recorded in the network device according to a roaming mapping table, where the roaming mapping table includes a mapping relationship between the subscription NSSAI of the user and the allowed NSSAI of the user, and the allowed NSSAI of the user includes the NSSAI of the network slice instance that allows the user to access in the first area.

47. The network device according to any of claims 36 to 43, wherein information of network slice instances supported by a global AMF is further recorded on the network device, the global AMF provides access and mobility management services for global users, the network slice instances subscribed by the global users are allowed to access M of the K regions, M is a positive integer greater than 1 and smaller than or equal to K.

48. The network device of claim 47, wherein the user is a global user.

49. A communication system comprising a network device according to any of claims 25 to 35 and a network device according to any of claims 36 to 48.

50. A computer storage medium comprising computer instructions that, when executed on a network device, cause the network device to perform the method of any of claims 1 to 11 or claims 12 to 24.

51. A communication chip comprising a processor, a memory, and one or more interfaces coupled to the processor; the processor is configured to retrieve and execute a computer program from the memory, the computer program being configured to perform the method of any of claims 1 to 11 or 12 to 24.