WO2021115464A1

WO2021115464A1 - Network slice selection method and related device

Info

Publication number: WO2021115464A1
Application number: PCT/CN2020/135969
Authority: WO
Inventors: 陈殿福
Original assignee: 华为技术有限公司
Priority date: 2019-12-13
Filing date: 2020-12-11
Publication date: 2021-06-17
Also published as: CN112994913A; CN112994913B

Abstract

Disclosed is a network slice selection method, comprising: a first NSSF receives a first request message from a first AMF, the first request message comprising location information of a user; if it is determined that information permitting the user to access network slice instances of a first area is not recorded in first NSSF, the first NSSF receives indication information of a first network slice instance from a second NSSF and an identifier of a second AMF; the first network slice instance being a network slice instance selected from network slice instances recorded in the second NSSF and to which access by the user is permitted in the first area, the first area being an area expressed by the location information; network slice instances supported by an AMF in the first area being recorded in the first NSSF, network slice instances supported by AMF of K areas being recorded in the second NSSF, and the K areas comprising the first area. The embodiments of the present application reduce the risks of overload and access delays, thus enhancing user experience.

Description

A network slice selection method and related device

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office, the application number is 201911285716.X, and the application name is "a network slicing selection method and related device" on December 13, 2019, the entire content of which is incorporated by reference In this application.

Technical field

This application relates to the field of electronic technology, and in particular to a network slice selection method and related devices.

Background technique

With the advent of the 5th generation mobile networks (5G) era, 5G mobile networks can not only meet the communication needs of people, but also support the connection of a large number of Internet of Things devices and provide mobile communication services for thousands of industries. The industry's bandwidth, delay differences, and security isolation requirements may all be different. The network slicing technology provides isolated network environments for different application scenarios by deploying multiple virtual networks on the basis of a shared infrastructure, thereby providing differentiated network services for different businesses or user groups. The network slice selection function (NSSF) entity can provide slice instance selection and target AMF selection services for the access and mobility management function (AMF) entities of the home network. NSSF can provide AMF based Tracking area (Tracking Area, TA) slice update, subscription, and notification functions.

With the increase in the number of users, network access to large and medium-sized operators has become more frequent, and there is a risk of overloading the centralized deployment of NSSF. In addition, due to the large geographic span, centralized deployment of NSSF will increase access latency and affect user experience.

Summary of the invention

The embodiments of the present application provide a network slice selection method and related devices, which can reduce the risk of overload and access delay, and improve user experience.

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

The first NSSF receives a first request message from the first AMF, where the first request message includes location information of the user;

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

The first network slice instance is a network slice instance that is selected from the network slice instances recorded in the second NSSF to allow users to access in the first area, and the first area is an area characterized by location information;

Wherein, the information of the foregoing network slice instance includes the indication information of the network slice instance, the identifier of the AMF configured in the network slice instance, and the identifier of the area served by the network slice instance. The first NSSF records the information supported by the AMF in the first area. The information of the network slice instance, the second NSSF records the information of the network slice instance supported by the AMF of K areas, the above 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 the network slice selection service for the user. In the embodiment of this application, only the network slice instances supported by the AMF in the first area are recorded in the first NSSF, and the network slice instances supported by the AMF in all areas are recorded in the second NSSF. Therefore, the second NSSF can Provide network slice selection service for the above-mentioned users. The implementation of this application reduces the risk of overloading the NSSF, reduces the user's access delay, and effectively improves the user experience.

In an implementation manner, the first request message also includes the network slice selection assistance information (NSSAI) of the user; if it is determined that the first NSSF does not record that the user is allowed to access the network in the first area Information about the slice instance, the first NSSF receives the indication information of the first network slice instance from the second NSSF and the identification of the second AMF, including: if the NSSAI of the user is subscribed, it is determined that the first NSSF does not record allowing the user to access For the information of the network slice instance of an area, the first NSSF receives the indication information of the first network slice instance and the identifier of the second AMF from the second NSSF.

In an implementation manner, the first request message further includes a user identification; if it is determined that the first NSSF does not record the information of the network slice instance that allows the user to access the first area, the first NSSF receives the first NSSF from the second NSSF. The indication information of a network slice instance and the identity of the second AMF include: if it is determined that the first NSSF does not record the information of the network slice instance that allows the user to access the first area according to the user’s subscription NSSAI information characterized by the user identity, then The first NSSF receives the indication information of the first network slice instance from the second NSSF and the identifier of the second AMF, and the user's subscription NSSAI is obtained by requesting the Unified Data Manager (UDM) according to the user identifier.

In an implementation manner, 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 the second NSSF, and the second request message includes the first AMF And the 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.

In an implementation manner, after the above-mentioned 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, and the third request message includes the information of the first AMF. Identification, information of the second network slice instance, and the third request message is used to request the second NSSF to add the second network slice instance to the network slice instance supported by the first AMF.

In an implementation manner, after the above-mentioned 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, and the fourth request message includes the information of the first AMF The identifier, the indication information of the third network slice instance, the 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 an implementation manner, after the above-mentioned 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, and the fifth request message includes the information of the first AMF. Identifier, indication information of the 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 instance supported by the first AMF.

In an implementation manner, after the above-mentioned 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, and the sixth request message includes the information of the first AMF. Identification, the sixth request message is used to request 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 an implementation manner, the indication information of the foregoing network slice instance includes the NSSAI of the network slice instance.

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

In one implementation, the second NSSF also records the information of the network slice instance supported by the global AMF. The global AMF provides access and mobility management services for the global user, and the network slice instance subscribed by the global user is allowed to access Enter M of the above K regions, and M is a positive integer greater than 1 and less than or equal to K.

In an implementation manner, the user's location information is the user's TA information.

In an implementation manner, the above-mentioned user is a global user.

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

The second NSSF receives the seventh request message from the first NSSF;

The seventh request message includes the location information of the user. The seventh request message is used to request the second NSSF to select a network slice instance that allows the user to access in the first area. The first area is the area characterized by the location information. The information of the network slice instance supported by the AMF in the first area is recorded;

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

Wherein, the information of the aforementioned network slice instance includes the indication information of the network slice instance, the identifier of the AMF configured in the network slice instance, and the identifier of the area served by the network slice instance. The first network slice instance is the network slice recorded from the second NSSF. The second NSSF of the network slice instance that allows users to access the first area selected in the example records information about the network slice instances supported by the AMF of K areas. The above K areas include the first area, and K is greater than 1. Is a positive integer.

Implementing the method described in the second aspect, after the second NSSF receives the seventh request message from the first NSSF, the seventh request message includes the location information of the user that characterizes the first area, and the second NSSF can provide network slicing options for the above-mentioned user service. This is because only the network slice instances supported by the AMF in the first area are recorded in the first NSSF, while the network slice instances supported by the AMF in all areas are recorded in the second NSSF. The implementation of this application reduces the risk of overloading the NSSF, reduces the user's access delay, and effectively improves the user experience.

In an implementation manner, the seventh request message also includes the user's subscription NSSAI; the seventh request message is used to request the second NSSF to select the network slice instance that allows the user to access in the first area according to the user's subscription NSSAI .

In an implementation manner, the first request message further includes a user identification; the seventh request message is used to request the second NSSF to select the network that the user is allowed to access in the first area according to the user's subscription NSSAI characterized by the user identification. In the slice example, the user's subscription NSSAI is obtained by requesting UDM according to the above-mentioned user identification.

In an implementation manner, 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, and the second request message includes the first request message. The identifier of the AMF, the 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.

In an implementation manner, 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, and the third request message includes the first request message. The identifier of the AMF, the information of the second network slice instance, and the third request message is used to request the second NSSF to add the second network slice instance to the network slice instance 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 fourth request message from the first NSSF, and the fourth request message includes the first AMF , The indication information of the third network slice instance, the 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 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 fifth request message from the first NSSF, and the fifth request message includes the first AMF And the indication information of the 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 instance 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, and the sixth request message includes the first AMF The sixth request message is used to request the second NSSF to remove the network slice instance of the first AMF from the network slice instance recorded by the second NSSF.

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

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

In one implementation, if the network slice instance ordered by the user includes a network slice instance that allows the user to access in the first area, then the first network slice instance is an allowed user selected from the network slices ordered by the user An instance of the network slice accessed in the first area.

In an implementation manner, if the network slice instance corresponding to the user's subscription NSSAI does not include a network slice instance that allows the user to access in the first area, the first network slice instance is the second NSSF according to the roaming mapping table, The network slice instance that allows the user to access in the first area selected from the network slice instances recorded in the second NSSF. The roaming mapping table includes the mapping relationship between the user's subscription NSSAI and the user's allowed NSSAI, and the user's subscription NSSAI 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 allows the user to access in the first area.

In one implementation, the second NSSF also records the information of the network slice instance supported by the global AMF. The global AMF provides access and mobility management services for the global user, and the network slice instance subscribed by the global user is allowed to access Among the M regions in the above K regions, M is a positive integer greater than 1 and less than or equal to K.

In an implementation manner, the above-mentioned users are global users.

In a third aspect, an embodiment of the present application provides a network device. The user equipment may include multiple functional modules or units for correspondingly executing the network slice selection method provided in the first aspect.

For example, the first receiving unit and the second receiving unit.

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

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

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

In an implementation manner, the first request message further includes the NSSAI of the user; the first receiving unit is specifically configured to: if according to the NSSAI of the user, it is determined that the network device has no record allowing the user to access the first For the information of the network slice instance of the area, the indication information of the first network slice instance of the second NSSF and the identifier of the second AMF are received.

In an implementation manner, the first request message further includes a user ID; the first receiving unit is specifically configured to: if the NSSAI of the user represented by the user ID is used, it is determined that the network device does not record the permission of the user to access the first area. For the information of the network slice instance, the indication information of the first network slice instance from the second NSSF and the identity of the second AMF are received, and the user's subscribed NSSAI is obtained by requesting UDM according to the user identity.

In an implementation manner, before the first receiving unit receives the first request message from the first AMF, the network device further includes: a first sending unit, configured to send a second request message to the second NSSF, and The request message includes the identification of the first AMF and the information of the network slice instance supported by the first AMF. The second request message is used to request the second NSSF to record the network slice instance supported by the first AMF to the network slice instance recorded by the second NSSF. in.

In an implementation manner, after the above-mentioned first sending unit sends the second request message to the second NSSF, the first sending unit is further configured to: send a third request message to the second NSSF, the third request message including the first AMF Identification, information of the second network slice instance, and the third request message is used to request the second NSSF to add the second network slice instance to the network slice instance 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: send a fourth request message to the second NSSF, the fourth request message including the first AMF The identifier, the indication information of the third network slice instance, the 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 an implementation manner, after the above-mentioned first sending unit sends the second request message to the second NSSF, the first sending unit is further configured to: send a fifth request message to the second NSSF, the fifth request message including the first AMF Identifier, indication information of the 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 instance supported by the first AMF.

In an implementation manner, after the above-mentioned first sending unit sends the second request message to the second NSSF, the first sending unit is further configured to: send a sixth request message to the second NSSF, the sixth request message including the first AMF Identification, the sixth request message is used to request 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 an implementation manner, the indication information of the foregoing network slice instance further includes the NSIID of the network slice instance.

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

In an implementation manner, the above-mentioned user is a global user.

In a fourth aspect, an embodiment of the present application provides a network device. The user equipment may include multiple functional modules or units for correspondingly executing the network slice selection method provided in the second aspect.

For example, the third receiving unit and the second sending unit.

The third receiving unit is configured to receive the seventh request message from the first NSSF; wherein the seventh request message includes the location information of the user, and the seventh request message is used to request the network device to select the network that the user is allowed to access in the first area A slice instance, the first area is an area characterized by location information, and the first NSSF records information about the network slice instance supported by the AMF in the first area;

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

Wherein, the information of the aforementioned network slice instance includes the indication information of the network slice instance, the identifier of the AMF configured in the network slice instance, and the identifier of the area served by the network slice instance, and the first network slice instance is the network slice instance recorded from the network device. The network slice instance that allows the user to access in the first area selected in the network device, the network device records the information of the network slice instance supported by the AMF of K areas, the above K areas include the first area, and K is greater than 1. Positive integer.

In an implementation manner, the seventh request message further includes the user's subscription NSSAI; the seventh request message is used to request the network device to select the network slice instance that allows the user to access in the first area according to the user's subscription NSSAI.

In an implementation manner, the first request message further includes a user identification; the seventh request message is used to request the network device to select the network slice instance that allows the user to access in the first area according to the user's subscription NSSAI characterized by the user identification. The user's subscription NSSAI is obtained by requesting UDM based on the user ID.

In an implementation manner, before the third receiving unit receives the seventh request message from the first NSSF, the third receiving unit is further configured to: receive a second request message from the first NSSF, and the second request message includes the first request message. The identifier of the AMF, the information of the network slice instance supported by the first AMF, and the second request message is used to request the network device to record the network slice instance supported by the first AMF into the network slice instance 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: receive a third request message from the first NSSF, and the third request message includes the first request message. The identifier of the AMF, the information of the second network slice instance, and the third request message is used to request the network device to add the second network slice instance to the network slice instance 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: receive a fourth request message from the first NSSF, and the fourth request message includes the first request message. The identifier of the AMF, the indication information of the third network slice instance, the information of the fourth network slice instance, and the fourth request message is used to request the network device 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: receive a fifth request message from the first NSSF, and the fifth request message includes the first request message. The identifier of the AMF, the indication information of the fifth network slice instance, and the fourth request message is used to request the network device to remove the fifth network slice instance from the network slice instance 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: receive a sixth request message from the first NSSF, where the sixth request message includes the first request message. The identifier of the AMF, the sixth request message is used to request the network device to remove the network slice instance of the first AMF from the network slice instance recorded by the network device.

In one implementation, if the network slice instance corresponding to the user's subscription NSSAI does not include a network slice instance that allows the user to access in the first area, the first network slice instance is the network device from the network device according to the roaming mapping table. The network slice instance that allows the user to access in the first area selected from the network slice instances recorded in the roaming mapping table includes the mapping relationship between the user's subscription NSSAI and the user's allowed NSSAI, and the user's subscription NSSAI is the subscription for the user The NSSAI of the network slice instance, 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.

In one implementation, the network device also records the information of the network slice instance supported by the global AMF. The global AMF provides access and mobility management services for the global user. The network slice instance subscribed by the global user is allowed to access the above Among the K areas, 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 the fifth aspect, an embodiment of the present application provides a network device for executing the network slice selection method provided in the first aspect. The network device may include: a memory, a processor, a transmitter, and a receiver, where the transmitter and the receiver are used to communicate with other communication devices (such as network devices or user equipment). The memory is used to store the implementation code of the network slice selection method provided in the first aspect, and the processor is used to execute the program code stored in the memory, that is, to execute the network slice selection method provided in the first aspect.

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

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

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

The second NSSF may be the network device described in the foregoing fourth aspect, or may be the network device described in the foregoing sixth aspect.

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

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

In a tenth aspect, an embodiment of the present application provides a computer-readable storage medium with instructions stored on the readable storage medium, which when run on a processor, cause the processor to execute the network slice selection method described in the first aspect above .

In an eleventh aspect, an embodiment of the present application provides a computer-readable storage medium with instructions stored on the readable storage medium, which when run on a processor, cause the processor to execute the network slice selection described in the second aspect above method.

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

In a thirteenth aspect, an embodiment of the present application provides a computer program product containing instructions, which when run on a processor, causes the processor to execute the network slice selection method described in the second aspect.

Description of the drawings

FIG. 1 is a schematic diagram of a system architecture of a communication system provided by an embodiment of this application;

2 is a schematic diagram of the system architecture of another communication system provided by an embodiment of the application;

3 is a schematic diagram of the system architecture of another communication system provided by an embodiment of the application;

FIG. 4 is a schematic flowchart of a method for selecting a network slice according to an embodiment of this application;

FIG. 5 is a schematic flowchart of another network slice selection method provided by an embodiment of this application;

FIG. 6 is a schematic flowchart of another network slice selection method provided by an embodiment of this application;

FIG. 7 is a schematic flowchart of another network slice selection method provided by an embodiment of this application;

FIG. 8 is a schematic flowchart of another network slice selection method provided by an embodiment of this application;

FIG. 9 is a schematic flowchart of another network slice selection method provided by an embodiment of this application;

FIG. 10 is a schematic structural diagram of a network device provided by an embodiment of this application;

FIG. 11 is a schematic diagram of the structure of another network device provided by an embodiment of this application;

FIG. 12 is a schematic structural diagram of a user equipment provided by an embodiment of this application;

FIG. 13 is a schematic structural diagram of another network device provided by an embodiment of this application.

Detailed ways

The technical solutions in the embodiments of the present application will be cleared and described in detail below in conjunction with the accompanying drawings. Among them, in the description of the embodiments of the present application, unless otherwise specified, "/" means or, for example, A/B can mean A or B; the "and/or" in the text is only a description of related objects The association relationship of indicates that there may be three relationships, for example, A and/or B, which may indicate: A alone exists, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application , "Multiple" means two or more than two.

Hereinafter, the terms "first" and "second" are only used for descriptive purposes, and cannot be understood as implying or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, the features defined with “first” and “second” may explicitly or implicitly include one or more of these features. In the description of the embodiments of the present application, unless otherwise specified, “multiple” The meaning is two or more.

First, the concepts of network slicing, network slicing instances, and network functions involved in the embodiments of this application are introduced.

Network slice (NS) refers to different logical networks customized according to different service requirements. A network slice can be a complete end-to-end network including terminals, access networks, transmission networks, core networks, and application servers, which can provide complete telecommunication services and have certain network capabilities. The network slicing can also be any combination of the aforementioned terminal, access network, transmission network, core network, and application server.

A Network Slice Instance (NSI) is an instantiation of NS, that is, a logical network that is actually running and can meet certain network characteristics or service requirements. A network slice instance can provide one or more services. A network slice instance can be created by a network slice management function device. A network slice management function device can create multiple network slice instances and manage them at the same time, including performance monitoring and fault management during the operation of the network slice instance. When multiple network slice instances coexist, some network resources and network functions can be shared among network slice instances. The network slice instance can be created from the network slice template or not from the network slice template. A complete network slice instance can provide a complete end-to-end network service, and the network slice instance can be a network slice subnet instance (Network Slice Subnet Instance, NSSI) and/or network function. A network slice instance can be divided into several network slice subnet instances to facilitate network management system management. The network functions may include physical network functions and/or virtual network functions. Hereinafter, physical network functions and/or virtual network functions are collectively referred to as network functions.

Network function (Network function, NF) is a processing function in the network, which defines functional behavior and interfaces. The network function can be realized by dedicated hardware, by running software on dedicated hardware, or in the form of virtual functions on a general hardware platform. Therefore, from the perspective of implementation, network functions can be divided into physical network functions and virtual network functions. From the perspective of usage, network functions can be divided into dedicated network functions and shared network functions.

A network management system can create multiple network slice instances and manage them at the same time, for example, modify or delete multiple network slice instances, and perform performance monitoring and fault management on them during the operation of network slice instances. A complete network slice instance can provide a complete end-to-end network service, and the network slice instance can be a network slice subnet instance and/or network function. A network slice instance is identified by an NSI ID. Exemplarily, the NSI ID may be a character string, or may be a name that can be understood by humans. Each network slice instance has one or more single network slice selection assistance information (Single Network Slice Selection Assistance Information, S-NSSAI) identification, S-NSSAI includes slice type (slice/service type, SST) and user group (slice differententiator) , SD), SST is used to define service scenarios/types of network slice standardization, and SD is used to distinguish different network slices of the same network slice type. NSSAI is a collection of S-NSSAI, which identifies a group of network slices.

When a UE is registered to a telecommunications network, the network needs to select a network slice instance/network slice subnet instance for the UE according to the single network slice selection assistance information (Single Network Slice Selection Assistance Information, S-NSSAI) corresponding to the UE. In addition, the network also needs to select an appropriate AMF for the UE according to the selected network slice instance/network slice subnet instance, that is, the target AMF. Among them, the AMF belongs to the core network element and is mainly responsible for the signaling processing part, that is, the control plane functions, including functions such as access control, mobility management, and gateway selection. The NSSF can provide the UE with the selection of the target AMF and can also provide the slice selection service for the AMF selection of the home network. The address information of the NSSF that provides the network slice selection service is stored in the AMF.

In the large and medium-sized public land mobile network (Public Land Mobile Network, PLMN), there are both local network slices and global network slices. If the coverage area of the above-mentioned PLMN includes K areas, the localized network slicing example refers to only one of the above-mentioned K areas is allowed to access, and K is a positive integer greater than 1; the global network slicing example is It means that only M areas in the above PLMN area are allowed to access. M is a positive integer greater than 1 and less than or equal to K. For ease of description, in this application, a local network slice instance is referred to as a local area network slice instance, and a global network slice instance is referred to as a global network slice instance. The users who subscribe to the local area network slice instance are called local users, the AMF that will provide access and mobility management services for local users is called local AMF, and the NSSF that provides network slice selection services for local AMF is called global network slice selection. Function (Local network slice selection function, L-NSSF); the user who subscribes to the global network slice instance is called the global user, and the AMF that will provide access and mobility management services for the global user is called the global AMF, which will provide the global AMF to The NSSF of the network slice selection service is called the global network slice selection function (G-NSSF).

For large and medium-sized operators, the geographical span is large, and network access is becoming more frequent. Centralized deployment of NSSF will have the risk of overload, increase access delay, and affect user experience. To solve the above problems, a distributed deployment of multiple NSSFs can be considered.

As shown in FIG. 1, it is a communication system 100 for distributed deployment of NSSF involved in an embodiment of the present application. The communication system 100 may include: user equipment (Ueser, UE) 101, (Radio) access network (access network, AN), local AMF 103, local L-NSSF 104, global AMF 105, and G-NSSF 106. The communication system 100 adopts a PLMN, and the coverage area of the PLMN includes K areas, namely area 1, area 2...area K.

The UE 101 involved in the embodiment of the present application may refer to a wireless terminal device with a wireless connection function. The UE 101 can communicate with one or more core networks via the (R)AN 102. For example, the UE 101 can be a mobile phone, a computer, a tablet computer, a personal communication service (PCS) phone, or a personal digital assistant (Personal Digital Assistant). Digital Assistant, PDA) and other mobile terminal equipment; it can also be a mobile station, mobile unit, M2M terminal, wireless unit, remote unit, terminal agent, mobile client, etc.; it can also be the Internet of Things The terminal equipment of the Internet of Vehicles, and the terminal equipment of the Internet of Vehicles; this embodiment of the application is not limited to this.

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

It should be noted that in this embodiment of the application, the AMF records the information of the network slice instance supported by the AMF, that is, the local AMF 103 records the information of the local area network slice instance supported by the local AMF 103, and the global AMF 105 records Information about the global network slice instance supported by the global AMF 105. L-NSSF 1 104 records the information of the network slice instance supported by the AMF of area 1, and G-NSSF 1 106 records the information of the global network slice instance supported by the global AMF. The information of the foregoing network slice instance includes the indication information of the network slice instance, the identifier of the AMF configured in the network slice instance, and the identifier of the area served by the network slice instance. Each of the K areas may include one or more L-NSSF.

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

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

It should be noted that the network slice instance supported by the first AMF refers to the 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 Figure 1, UE 101 performs initial access in area 1. UE 101 first sends a registration request to (R)AN 102, and (R)AN 102 that receives the registration request will select an initial AMF for UE 101 to process the above Registration request. If the aforementioned initial AMF cannot support all the network slices ordered by the user, the initial AMF requests the NSSF corresponding to the initial AMF to select a network slice instance that allows access to area 1 for the UE 101.

For the above-mentioned communication system 100, there are several problems as follows:

(1) A local user initiates a registration request in area 1 through the UE 101, and the global AMF 105 processes the registration request. Since the global AMF 105 may not support all the local network slice instances ordered by the above local users, the global AMF 105 sends a request message to the G-NSSF 106, requesting the G-NSSF 106 to select the network that allows the local users to access area 1 for the above local users Slice instance. However, G-NSSF 106 does not record the information of the network slice instance ordered by the local user. G-NSSF 106 also cannot provide network slice selection services for local users.

(2) A local user in area K initiates a registration request in area 1 through UE 101, and the local AMF 103 in area 1 processes the registration request. Since the local AMF 103 in area 1 may not support all local network slice instances ordered by local users in area K, the local AMF 103 in area 1 sends a request message to L-NSSF 1 104, requesting that L-NSSF 1 104 be the above-mentioned area K. The local user chooses to allow access to the network slice instance in area 1. However, L-NSSF 1 104 does not record the information of the network slice instance subscribed by the local user in area K. Local users in area K refer to users whose home is in area K. L-NSSF 1 104 cannot provide network slice selection services for local users in the above-mentioned area K.

(3) A global user initiates a registration request in area 1 through UE 101, and the local AMF 103 in area 1 handles the registration request. Since the local AMF 103 may not support all the global network slice instances ordered by the above global users, the local AMF 103 sends a request message to L-NSSF 1 104, requesting L-NSSF 1 104 to select the network slice that allows access to area 1 for the above global users Instance. However, L-NSSF 1 104 does not record the information of the network slice instance subscribed by the global user. L-NSSF 1 104 cannot provide network slice selection services for the aforementioned global users.

As shown in FIG. 2, in order to solve the above-mentioned problems, the operator adds a management device 107 to the communication system 100. When one or more network slice instances supported by AMF in the local AMF and global AMF of the above K regions change, the management device 107 will compare the data of the network slice instances supported by the local AMF in the above K regions and the network supported by the global AMF. The information of the slice instance is synchronized to each NSSF in the communication system 100 through manual configuration, that is, L-NSSF 1, L-NSSF 2, ..., L-NSSF K, and G-NSSF of the above K areas.

When the network slice instance in the communication system 100 changes (create network slice, modify network slice and/or delete network slice, etc.), all NSSFs in the entire network must be updated synchronously. This synchronization method will undoubtedly consume a lot of transmission resources and labor costs. In addition, manual configuration is a lot of work, and it is easy to introduce human errors;

Therefore, as shown in FIG. 3, in order to solve the problems of the communication system 100 shown in FIG. 1, the embodiment of the present application adds a communication interface between L-NSSF and G-NSSF. Through the communication interface, K areas L-NSSF can synchronize the information of the network slice instances supported by the local AMF in each area to G-NSSF. L-NSSF can request to query the network slices supported by any AMF in the communication system 100 recorded on the G-NSSF. Information about the instance.

Applicable to the communication system shown in FIG. 3, an embodiment of the present application provides a network slice selection method, which can reduce the risk of NSSF overload, reduce access delay, and improve user experience. In addition, compared with the network slicing synchronization method in the communication system shown in FIG. 2, the cost is lower, and human misoperation can also be avoided.

FIG. 4 is a schematic flowchart of a method for selecting a network slice according to an embodiment of the present application. As shown in FIG. 4, the network slice selection method provided by the embodiment of the present application includes but is not limited to steps S401 to S404. The possible implementation of this method embodiment will be further described below.

S401. The first AMF sends a first request message to the first NSSF, and the first NSSF receives the first request message sent by the first AMF, where the first request message includes location information of the user.

It should be noted that the above-mentioned location information may be used to characterize one of the K areas in the communication system 100, for example, TA information of the user.

S402. The first NSSF determines whether the first NSSF records the information of the network slice instance that allows the above-mentioned user to access the first area; the first area is the area characterized by the above-mentioned location information, and the first NSSF records the information in the first area. Information about the network slice instance supported by the AMF. The above-mentioned network slice instance information includes the indication information of the network slice instance, the identifier of the AMF configured in the network slice instance, and the identifier of the area served by the network slice instance.

In the embodiment of the present application, the first request message further includes at least one parameter of the user's subscription NSSAI and user identification. The first NSSF determines whether the first NSSF records information about the network slice instance that allows the user to access the first area according to the user's subscription NSSAI and/or user identity.

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

Optionally, the first request message may also include the user's subscription NSSAI. The first NSSF determining whether the first NSSF records the information of the network slice instance that allows the user to access the first area, including: the first NSSF determines whether the first NSSF records the record of allowing the user to access the NSSAI according to the user's subscription NSSAI Enter the information of the network slice instance in the first area.

Optionally, the first request message further includes a user identification. The first NSSF determines whether the first NSSF records the information of the network slice instance that allows the user to access the first area, including: the first NSSF determines whether the first NSSF records according to the user's subscription NSSAI represented by the user identifier There is information that allows the user identified by the user to access the network slice instance of the first area. Wherein, the user's subscription NSSAI is obtained by the first NSSF by requesting UDM according to the above-mentioned user identification.

Specifically, the first NSSF first determines whether the first NSSF records the network slice instance corresponding to the user's contracted NSSAI, and if so, determines whether the network slice instance corresponding to the user's contracted NSSAI allows access to the first area.

It can be understood that the information of the network slice instance recorded by the first NSSF includes the identifier of the area served by the network slice instance, and the first NSSF may determine whether the network slice instance is allowed to access the first area according to the identifier of the area served by the network slice instance. . If the identifier of the area served by the network slice instance is the identifier of the first area, the network slice instance allows access to the first area.

In the embodiment of the present application, the user's contracted NSSAI is the S-NSSAI of the network slice instance subscribed by the user, and the user's contracted NSSAI includes one or more S-NSSAIs. The request NSSAI indicates the S-NSSAI of the network slice that the UE wants to register, and the request NSSAI includes one or more S-NSSAIs.

Optionally, the aforementioned user identity may be an International Mobile Subscriber Identification Number (IMSI), a Globally Unique Temporary UE Identity (GUTI), etc.

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

It can be understood that the first NSSF records information about one or more network slice instances supported by the AMF corresponding to the first NSSF.

S403. If there is no record, 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. The seventh request message includes the location information of the above-mentioned user, and the seventh request message Used to request the second NSSF to select a network slice instance for the user; the second NSSF records information about network slice instances supported by the AMF of K areas, the K areas include the first area, and K is greater than 1. Positive integer.

In the embodiment of the present application, the seventh request message also includes at least one parameter of the user's subscription NSSAI and user identity. The seventh request message may be used to request the second NSSF to select a network slice instance that allows the user to access in the first area according to the user's subscription NSSAI and/or user identity.

Optionally, the seventh request message further includes the user's request for S-NSSAI; the seventh request message is used to request the second NSSF to choose to allow the above according to the user's request S-NSSAI, the user's subscription NSSAI and/or the user identity Instance of the network slice accessed by the user in the first area.

Optionally, the seventh request message further includes the user's subscription NSSAI; the seventh request message is used to request the second NSSF to select the network slice instance that allows the user to access in the first area according to the user's subscription NSSAI.

Optionally, the seventh request message further includes a user ID; the seventh request message is used to request the second NSSF to select the network slice instance that allows the user to access in the first area according to the user's subscription NSSAI characterized by the user ID. , Wherein, the user's subscription NSSAI is obtained by requesting UDM according to the above-mentioned user identification.

The specific implementation process is analogous to the first NSSF, and will not be repeated here.

In this embodiment of the application, the second NSSF directly obtains the user's subscribed NSSAI 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 there is a network slice instance corresponding to the user's subscription NSSAI and allowed to access the first area recorded in the second NSSF.

In this embodiment of the application, before the second NSSF receives the seventh request message sent by the first NSSF, the second NSSF records the network slice instances supported by the AMF in the K areas, so that users in the K areas may be Provide network slice selection service.

In the embodiment of the present application, the network slice instance data supported by the AMFs of the above K areas are synchronized to the second NSSF in real time. When the network slice instances supported by the first AMF in the above K areas change, the changed first AMF will notify the first NSSF so that the first NSSF can update the network slices supported by the first AMF recorded by the first NSSF Example: After receiving the notification from the AMF, the first NSSF will notify the second NSSF so that the second NSSF can update the network slice instances supported by the first AMF recorded by the second NSSF.

Optionally, changes to the network slice instances supported by the AMF in the above K regions include: adding an AMF to the above K regions, and the newly added AMF supports one or more network slice instances; one of the above K regions One or more network slice instances supported by the existing AMF have changed (for example, addition, replacement, or removal); one AMF is removed from the above K areas, and the removed AMF supports one or more networks Slice instance.

S404: The second NSSF sends the indication information of the first network slice instance and the identifier of the second AMF to the first NSSF, and 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; A network slice instance is a network slice instance that is selected from the network slice instances recorded in the second NSSF to allow the user to access the first area, and the second AMF is the 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 also determines whether there is a network slice instance that allows the user to access the first area in the network slice instance corresponding to the above-mentioned user's subscription NSSAI; if so, the user is allowed to access the first area from the above-mentioned network slice instance. The first network slice instance is determined from the network slice instances of the area; if not, the first network slice instance can be selected for the user according to the roaming service subscribed by the user.

In the embodiment of the present application, that a network slice instance is recorded in the first NSSF means that the first NSSF records information of the network slice instance.

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

FIG. 5 is a schematic flowchart of a method for selecting a network slice according to an embodiment of the present application. As shown in FIG. 5, the network slice selection method provided by the embodiment of the present application includes but is not limited to steps S501 to S503. The possible implementation of this method embodiment will be further described below.

S501. The UE sends a registration request message to the first AMF, and the first AMF receives the registration request message sent by the UE. The registration request message includes a user identifier and location 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. The eighth request message includes a user ID, and the eighth request message is used to obtain the subscription NSSAI of the user with the user ID.

In the embodiment of the present application, the eighth request message is used to obtain the S-NSSAI of the network slice instance subscribed by the user, that is, the user's subscribed NSSAI, and the user's subscribed NSSAI includes one or more S-NSSAIs.

S503. The UDM sends the user's subscription NSSAI to the first AMF, and the first AMF receives the user's subscription NSSAI sent by the UDM.

S504: If the first AMF cannot provide services for all network slice instances corresponding to the user's subscribed NSSAI, send a first request message to the first NSSF, where the first request message includes the user's location information and the user's subscribed NSSAI.

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 cannot provide services for all network slice instances corresponding to the user's contracted NSSAI according to the user's contracted NSSAI, that is, all S-NSSAIs in the user's contracted NSSAI, then sends a first request to the first NSSF news.

In some embodiments of the present application, the registration request message also includes the user's request NSSAI, and the request NSSAI is used to select a network slice instance for the above-mentioned user. The first request message also includes the user's requested NSSAI. If the first AMF cannot provide services for all network slice instances corresponding to one or more S-NSSAIs that exist in both the contracted NSSAI and the requested NSSAI, it will be sent to the first NSSF The first request message.

S505. The first NSSF determines whether the first NSSF records the information of the network slice instance that allows the user to access the first area, the first area is the area characterized by the location information, and the first NSSF records the information in the first area. Information about the network slicing instance supported by AMF.

In the embodiment of the present application, the first request message may also include the user's subscribed NSSAI and/or user identification. In addition, the first request message may also include the user's request for NSSAI.

S506: If the first NSSF determines that there is no network slice instance that allows the user to access the first area is recorded in the first NSSF, the first NSSF sends a seventh request message to the second NSSF, where the seventh request message includes the location information of the user. With the user's subscription NSSAI, the seventh request message is used to request the second NSSF to select the network slice instance that allows the user to access in the first area.

Wherein, the second NSSF records the network slice examples supported by the AMF of K areas, the above K areas include the first area, and K is a positive integer greater than 1.

In some embodiments of the present application, the first NSSF records the S-NSSAI of the network slice instance supported by the AMF in the first area. The first NSSF obtains the S-NSSAI of the network slice instance subscribed by the user, that is, the user's subscribed NSSAI, and according to the user's subscribed NSSAI and the above location information, it can determine whether the first NSSF record exists in all network slice instances corresponding to the user's subscribed NSSAI An instance of the network slice that allows access to the first area.

In some embodiments of the present application, the first NSSF is L-NSSF in the above K areas, and the second NSSF is G-NSSF. If the user is a global user, the network slice instance subscribed by the global user is not recorded on the first NSSF; if the user is a roaming user located in another area, the network slice instance subscribed by the user may not be recorded on the first NSSF. Since the second NSSF not only saves the information of the network slice instances supported by the AMF in the K areas, but also saves the information of the network slice instances supported by the global AMF, in the above two cases, the first NSSF can request the second NSSF provides network slice selection service for this user.

In the embodiment of the present application, the seventh request message may also include the user's subscribed NSSAI and/or user identification. In addition, the seventh request message may also include the user's request for NSSAI.

S507. The second NSSF selects, among the network slice instances recorded in the second NSSF, a network slice instance that allows access to the first area for the above-mentioned user.

It can be understood that the second NSSF records the information of the network slice instance supported by the AMF in the first area, and records the information of the network slice instance subscribed by the user. Therefore, according to the user's contracted NSSAI and the aforementioned location information, it can be determined whether there is a network slice instance that allows access to the first area among all network slice instances corresponding to the user's contracted NSSAI.

In some embodiments of the present application, if the network slice instance subscribed by the user includes a network slice instance that allows the user to access in the first area, the first network slice instance is the network slice subscribed by the second NSSF from the user Selected from the network slice instances that allow users to access in the first area. If the network slice instance ordered by 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 the second NSSF from the network slice instance recorded in the second NSSF according to the roaming mapping table The selected network slice instance that allows the user to access in the first area. Wherein, the roaming mapping table includes the 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 S-NSSAI of the network slice instance 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 the user subscribes does not include the network slice instance that allows the user to access in the first area, and the user is determined to subscribe to the related roaming according to the subscription information stored in the UDM Service, the network slice instance can be selected for the above-mentioned user according to the roaming mapping table.

S508. The indication information of the first network slice instance and the identifier of the second AMF sent by the second NSSF to the first NSSF, and 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. The second AMF is the AMF configured in the first network slice instance.

S509. The indication information of the first network slice instance and the identifier of the second AMF sent by the first NSSF to the first AMF, and the first AMF receives the indication information of the first network slice instance and the identifier of the second AMF sent by the first NSSF.

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

S510: If the first AMF determines, according to the indication information of the first network slice instance, that the first AMF cannot provide services for the first network slice instance, determine the identity of the target AMF according to the identity 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 the first AMF according to the S-NSSAI of the network slice instance recorded by the first AMF, An AMF can provide services for the first network slice instance, and the first AMF serves as the target AMF, and the UE can register to the network through the first AMF. If the first AMF determines that the first AMF cannot provide services for the first network slice instance, and the second AMF contains only one AMF, the second AMF is determined to be the target AMF, and the first AMF sends a registration request message from the UE to the target AMF . If the first AMF determines that the first AMF cannot provide services for the first network slice instance, and the second AMF only contains multiple AMFs, the first AMF can send a request message to the NRF, requesting that the target AMF be determined according to the identifier of the second AMF Identify and send a registration request message from the UE to the target AMF.

In this embodiment of the application, 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 areas have been synchronized to the second NSSF, so the second NSSF may be the above Users in K regions provide network slice selection services. The following describes in detail the synchronization of network slicing instance data.

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. The possible implementation of this method embodiment will be further described below.

S601. The first AMF sends a ninth request message to the first NSSF, and the first NSSF receives the ninth request message sent by the first AMF. The ninth request message includes the identifier of the first AMF and the network slice instance supported by the first AMF.的信息; The ninth request message is used to request the first NSSF to add the network slice instance supported by the first AMF to the network slice instance recorded by the first NSSF.

S602. The first NSSF sends a second request message to the second NSSF, and the second NSSF receives the second request message sent by the first NSSF. The second request message includes the identity of the first NSSF, the identity of the first AMF, and the support of the first AMF. Information about the network slice instance; the second request message is used to request the second NSSF to add the network slice instance supported by the first AMF to the network slice instance 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 the identifier of the AMF configured by the network slice instance supported by the first AMF. The network slice instance supported by the first AMF of the second NSSF includes: recording the information of the network slice instance supported by the first AMF and the identifier of the AMF configured by the network slice instance supported by the first AMF.

It is understandable that the first AMF is a newly added AMF in the first area. When an AMF is newly added in the first area, the newly added AMF sends a request message to the first NSSF to notify the first NSSF to record that the newly added AMF supports Instance of network slicing. While recording the network slice instance supported by the newly added AMF, the first NSSF also sends a request message to the second NSSF to synchronously add the network slice instance supported by the newly added AMF to the second NSSF at the granularity of AMF. in. The network slice instance supported by the newly added AMF is recorded in the network slice instance corresponding to the first NSSF in the second NSSF.

Optionally, after the foregoing 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:

S604. The first AMF sends a tenth request message to the first NSSF, and the first NSSF receives the tenth request message sent by the first AMF. The tenth request message includes the identifier of the first AMF and the information of the second network slice instance; The request message is used to request the first NSSF to add the second network slice instance to the network slice instance supported by the first AMF.

S605. The first NSSF sends a third request message to the second NSSF, and the second NSSF receives the third request message sent by the first NSSF. The third request message includes the identity of the first NSSF, the identity of the first AMF, and the second network slice. Instance information; the third request message is used to request the second NSSF to add the second network slice instance to the network slice instance supported by the first AMF.

S606. The second NSSF records the second network slice instance in the network slice instance supported by the first AMF.

Optionally, the tenth request message further includes the identifier of the AMF configured by the second network slice instance. The recording of the second network slice instance by the second NSSF includes: recording the information of the second network slice instance and the identifier of the AMF configured by the second network slice instance.

It can be understood that the second network slice instance is a newly added network slice instance that can be supported by the first AMF. When the first AMF adds a new network slice instance, the first AMF sends a request message to the first NSSF to notify the first NSSF records the newly added network slice instance of the first AMF. While recording the network slice instance newly added by the first AMF, the first NSSF also sends a request message to the second NSSF to synchronously add the network slice instance newly added by the first AMF to the second NSSF. The newly added second network slice instance is recorded in the network slice instance of the first AMF corresponding to the first NSSF in the second NSSF.

S607. The first AMF sends an eleventh request message to the first NSSF, and the first NSSF receives the eleventh request message sent by the first AMF. The eleventh request message includes the identifier of the first AMF and the indication of the third network slice instance. Information, information of the fourth network slice instance; the eleventh request message is used to request 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. The fourth request message includes the identity of the first NSSF, the identity of the first AMF, and the third network slice. The indication information of the instance and the information of the fourth network slice instance; 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.

S609. The second NSSF replaces the third network slice instance supported by the first AMF recorded by the second NSSF with the fourth network slice instance.

Optionally, the eleventh request message further includes the identifier of the AMF configured by the fourth network slice instance. The recording of the fourth network slice instance by the second NSSF includes: recording the information of the fourth network slice instance and the identifier of the AMF configured by the fourth network slice instance.

It can be understood that the fourth network slice instance is a newly added 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 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 network slice instance of the first AMF is replaced and updated, the first AMF sends a request message to the first NSSF to notify the first NSSF to record that the first AMF replaces the updated network slice instance. While recording the network slice instance replaced by the first AMF, the first NSSF also sends a request message to the second NSSF to synchronize the updated network slice instance replaced by the first AMF to the second NSSF. The fourth network slice instance is recorded in the network slice instance of the first AMF corresponding to the first NSSF in the second NSSF.

S610. The first AMF sends a twelfth request message to the first NSSF, and the first NSSF receives the twelfth request message sent by the first AMF. The twelfth request message includes the identifier of the first AMF and the indication of the fifth network slice instance. Information; the twelfth request message is used to request the first NSSF to remove the fifth network slice instance from the network slice instance supported by the first AMF.

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. The fifth request message includes the identity of the first NSSF, the identity of the first AMF, and the fifth network slice. Indication information of the instance; the fifth request message is used to request the second NSSF to remove the fifth network slice instance from the network slice instance supported by the first AMF.

S612. The second NSSF deletes the fifth network slice instance supported by the first AMF recorded by the second NSSF.

It can be understood that the fifth network slice instance is an old network slice instance supported by the first AMF. When the first AMF no longer supports the fifth network slice instance, the first AMF sends a request message to the first NSSF to notify the first NSSF Remove the fifth network slice instance supported by the first AMF recorded by the first NSSF. While removing the fifth network slice instance supported by the first AMF recorded by the first NSSF, the first NSSF also sends a request message to the second NSSF to synchronously update the network slice instance supported by the first AMF to the second NSSF in. 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. The thirteenth request message includes the identifier of the first AMF; the thirteenth request message is used for Request the first NSSF to remove the network slice instance supported by the first AMF from the network slice instance 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. The sixth request message includes the identity of the first NSSF and the identity of the first AMF; the third request message It is used to request the second NSSF to remove the network slice instance supported by the first AMF from the network slice instance recorded by the second NSSF.

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 can be understood 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 recorded by the first NSSF. While deleting the network slice instance of the first AMF recorded by the first NSSF, the first NSSF also sends a request message to the second NSSF to synchronize the AMF corresponding to the first NSSF to the second NSSF as a whole with the granularity of AMF. 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 the embodiment of the present application, 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 the embodiment of this application, only the network slice instances supported by the AMF in the first area are recorded in the first NSSF, and the network slice instances supported by the AMF in all areas are recorded in the second NSSF. Therefore, the second NSSF can Provide network slice selection service for the above-mentioned users. The implementation of this application reduces the risk of overloading the NSSF, reduces the user's access delay, and effectively improves the user experience. In addition, only the second NSSF automatically synchronizes the data of the network slice instances supported by the AMF in all regions. The proposed solution has low cost, fast response, and can avoid human error.

Based on the communication system shown in FIG. 3, the following describes the network slice selection method provided by the embodiment of the present application for two specific application scenarios.

Scenario 1: A local user whose home is area i initiates a registration request in area 1 through the UE, and the global AMF processes the registration request.

As shown in FIG. 7, the network slice selection method based on scenario one provided by the embodiment of the present application includes but is not limited to steps S701 to S708. The possible implementation of this method embodiment will be further described below.

S701. The first local user sends a registration request message to the first global AMF through the UE in area 1, and the first global AMF receives the registration request message sent by the UE. The registration request message includes the user identity of the first local user and the first local user's location information.

In the embodiment of the present application, the attribution of the first local user is area i, the above-mentioned location information characterizes area 1, and area i may be area 1, or other areas among the above K areas, which is not specifically limited here.

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. The eighth request message includes the user identifier of the first local user, and the eighth request message is used to obtain the first local user. The user's subscription NSSAI.

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

S704. If the first global AMF cannot provide services for all network slice instances corresponding to the subscribed 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. The request message, the first request message includes the location information of the first local user and the NSSAI subscribed by the first local user.

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

It can 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 local users.

S705. The G-NSSF selects the first network slice instance that allows the first local user to access area 1 from the network slice instances recorded in the G-NSSF according to the NSSAI of the first local user's subscription.

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

S707. If the first AMF determines, according to the S-NSSAI of the first network slice instance, that the first AMF cannot provide services for the first network slice instance, determine the identity of the target AMF according to the identity 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.

Scenario 2: The first local user whose home is area i initiates a registration request in area 1 through UE 101, and the local AMF 103 of area 1 is processing the registration request, and i is not equal to 1.

As shown in FIG. 8, the network slice selection method based on scenario 2 provided by the embodiment of the present application includes but is not limited to steps S801 to S812. The possible implementation of this method embodiment will be further described below.

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

S802. The first local AMF sends an eighth request message to the UDM, and the UDM receives the eighth request message sent by the first local AMF. The eighth request message includes the user ID of the first local user, and the eighth request message is used to obtain the user ID. The corresponding NSSAI contract of the first local user.

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

S804. If the first local AMF cannot provide services for all network slice instances corresponding to the subscribed NSSAI of the first local user, send a first request message to the L-NSSF 1 of area 1, where the first request message includes the first local user's Location information and the NSSAI of the first local user's subscription.

It can be understood that the first local user is a roaming user from the above K areas except for area 1, and the first local AMF may not be able to provide services for all network slice instances corresponding to the first local user's contracted NSSAI.

S805. If L-NSSF 1 determines that L-NSSF 1 does not record the first local user's subscription NSSAI corresponding to all network slice instances, L-NSSF 1 sends a seventh request message to G-NSSF, and the seventh request message includes the first The location information of a local user and the subscription NSSAI of the first local user. The seventh request message is used to request the G-NSSF to select a network slice instance that allows the first local user to access area 1.

It can be understood that the first local user is a roaming user from the above K areas except for area 1. Therefore, L-NSSF 1 may not record the first local user's contracted NSSAI corresponding to all network slice instances. The G-NSSF records the network slice instances supported by the AMF of the K areas. Therefore, the G-NSSF records the first local user's contracted NSSAI corresponding to all network slice instances. G-NSSF can provide a network slice selection service for the first local user.

S806: The G-NSSF selects the first network slice instance that allows the first local user to access area 1 from the network slice instances recorded by the G-NSSF according to the NSSAI of the first local user's subscription.

S807. The S-NSSAI of the first network slice instance and the identifier of the second local AMF sent by the G-NSSF to the L-NSSF 1, and the first L-NSSF 1 receives the S-NSSAI of the first network slice instance sent by the G-NSSF And the identifier of the second local AMF, the second local AMF is the AMF configured in the first network slice instance.

S808, L-NSSF 1 sends the S-NSSAI of the first network slice instance and the identifier of the second local AMF to the first local AMF, and the first local AMF receives the S-NSSAI and S-NSSAI of the first network slice instance sent by L-NSSF 1 The identifier of the second local AMF.

S809. If the first local AMF determines according to the S-NSSAI of the first network slice instance that the first AMF cannot provide services for the first network slice instance, determine the identity of the target AMF according to the identity 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.

Scenario 3: A global user initiates a registration request in area 1 through the UE, and the first local AMF in area 1 is processing the registration request.

As shown in FIG. 9, the network slice selection method based on scenario 3 provided in the embodiment of the present application includes but is not limited to steps S901 to S912. The possible implementation of this method embodiment will be further described below.

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

S902. The first local AMF sends an eighth request message to the UDM, and the UDM receives the eighth request message sent by the first local AMF. The eighth request message includes the user ID of the global user, and the eighth request message is used to obtain the user ID corresponding to the user ID. The subscription NSSAI of the global user.

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

S904. If the first local AMF cannot provide services for all network slice instances corresponding to the NSSAI subscribed to the global user, it sends a first request message to the L-NSSF 1 of area 1. The first request message includes the location information of the global user and the global user. The user's subscription NSSAI.

It can be understood that the first local AMF cannot provide services for all network slice instances corresponding to the subscribed NSSAI of the global user.

S905. If L-NSSF 1 determines that no global user’s subscription NSSAI corresponds to all network slice instances in L-NSSF 1, L-NSSF 1 sends a seventh request message to G-NSSF, and the seventh request message includes the global user’s Location information and the subscription NSSAI of the global user. The seventh request message is used to request the G-NSSF to select a network slice instance that allows the global user to access area 1.

It can be understood that L-NSSF 1 does not record that the NSSAI of the global user corresponds to all network slice instances, and the G-NSSF records that the NSSAI of the global user corresponds to all network slice instances. G-NSSF can provide network slice selection services for global users.

S906: The G-NSSF selects the first network slice instance that allows the global user to access area 1 from the network slice instances recorded by the G-NSSF according to the subscription NSSAI of the global user.

S907, the S-NSSAI of the first network slice instance and the identifier of the second local AMF sent by the G-NSSF to the L-NSSF 1, and the first L-NSSF 1 receives the S-NSSAI of the first network slice instance sent by the G-NSSF And the identifier of the second local AMF, the second local AMF is the AMF configured in the first network slice instance.

S908, L-NSSF 1 sends the S-NSSAI of the first network slice instance and the identifier of the second local AMF to the first local AMF, and the first local AMF receives the S-NSSAI and S-NSSAI of the first network slice instance sent by L-NSSF 1 The identifier of the second local AMF.

S909: If the first local AMF determines according to the S-NSSAI of the first network slice instance that the first AMF cannot provide services for the first network slice instance, determine the identity of the target AMF according to the identity 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.

Refer to FIG. 10, which is a schematic structural diagram of a network device provided by an embodiment of the present application. As shown in FIG. 10, the network device 10 includes: a first receiving unit 11 and a second receiving unit 12.

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

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

In an implementation manner, the first request message further includes the user's subscription NSSAI; the first receiving unit 11 is specifically configured to: if according to the user's subscription NSSAI, determine that the network device has no record of allowing the user to access If the information of the network slice instance entering the first area is received, the indication information of the first network slice instance and the identifier of the second AMF from the second NSSF are received.

In an implementation manner, the first request message further includes a user identification; the first receiving unit 11 is specifically configured to: if the user's subscription NSSAI is represented by the user identification, determine that the network device does not record allowing the user to access the first The information of the network slice instance of the area is received from the indication information of the first network slice instance of the second NSSF and the identification of the second AMF. The user's subscription NSSAI is obtained by requesting UDM according to the user identification.

In an implementation manner, before the above-mentioned first receiving unit 11 receives the first request message from the first AMF, the network device further includes: a first sending unit configured to send a second request message to the second NSSF. The second request message includes the identifier of the first AMF and the information of the network slice instance supported by the first AMF. The second request message is used to request the second NSSF to record the network slice instance supported by the first AMF to the network slice recorded by the second NSSF. In the instance.

In an implementation manner, the above-mentioned user is a global user.

Refer to FIG. 11, which is a schematic structural diagram of a network device provided by an embodiment of the present application. As shown in FIG. 11, the network device 20 includes: a third receiving unit 21 and a second sending unit 22.

The third receiving unit 21 is configured to receive a seventh request message from the first NSSF; wherein, the seventh request message includes the location information of the user, and the seventh request message is used to request the network device to select the one that allows the user to access in the first area A network slicing instance, the first area is an area characterized by location information, and the first NSSF records information about the network slicing instance supported by the AMF in the first area;

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

In an implementation manner, before the third receiving unit 21 receives the seventh request message from the first NSSF, the third receiving unit 21 is further configured to: receive a second request message from the first NSSF, where the second request message includes The identifier of the first AMF, the information of the network slice instance supported by the first AMF, and the second request message is used to request the network device to record the network slice instance supported by the first AMF in the network slice instance recorded by the network device.

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: receive a third request message from the first NSSF, where the third request message includes The identifier of the first AMF, the information of the second network slice instance, and the third request message is used to request the network device to add the second network slice instance to the network slice instance 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: receive a fourth request message from the first NSSF, where the fourth request message includes The identifier of the first AMF, the indication information of the third network slice instance, the information of the fourth network slice instance, and the fourth request message is used to request the network device 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 21 receives the second request message from the first NSSF, the third receiving unit 21 is further configured to: receive a fifth request message from the first NSSF, where the fifth request message includes The identifier of the first AMF, the indication information of the fifth network slice instance, and the fourth request message is used to request the network device to remove the fifth network slice instance from the network slice instance 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: receive a sixth request message from the first NSSF, where the sixth request message includes The identifier of the first AMF, and the sixth request message is used to request the network device to remove the network slice instance of the first AMF from the network slice instance recorded by the network device.

In an implementation manner, the seventh request message is that the first NSSF determines that the first NSSF does not record a network slice instance that allows the user to access the first area.

In one implementation, the user is a global user.

Referring to FIG. 12, FIG. 12 shows a user equipment 1000 provided by an embodiment of the present application. As shown in FIG. 12, the user equipment 1000 may include: one or more user equipment processors 1001, a memory 1002, a communication interface 1003, a receiver 1005, a transmitter 1006, a coupler 1007, an antenna 1008, and a user equipment interface 1009. These components can be connected through the bus 1004 or other ways. FIG. 12 takes the connection through the bus as an example. among them:

The communication interface 1003 may be used for the user equipment 1000 to communicate with other communication devices, such as network devices. Specifically, 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 a communication interface of a new air interface in the future. Not limited to a wireless communication interface, the user equipment 1000 may also be configured with a wired communication interface 1003, such as a local access network (LAN) interface. The transmitter 1006 may be used to transmit and process the signal output by the user equipment processor 1001. The receiver 1005 can be used to receive and process the mobile communication signal received by the antenna 1008.

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

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

The user equipment 1000 may also include an input and output module. The input and output module can be used to realize the interaction between the user equipment 1000 and the user equipment/external environment, and can mainly include an audio input and output module, a key input module, a display, and the like. Specifically, the input and output modules may also include: cameras, touch screens, sensors, and so on. Among them, the input and output modules all communicate with the user equipment processor 1001 through the user equipment interface 1009.

The memory 1002 is coupled with the user equipment processor 1001, and is used to store various software programs and/or multiple sets of instructions. Specifically, the memory 1002 may include a high-speed random access memory, and may also include a 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 as the system), such as an embedded operating system such as ANDROID, IOS, WINDOWS, or LINUX. The memory 1002 may also store a network communication program, which may be used to communicate with one or more additional devices, one or more user devices, and one or more network devices.

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

The user equipment processor 1001 can be used to read and execute computer-readable instructions. Specifically, the user equipment processor 1001 may be used to call a program stored in the memory 1002, such as the implementation program of the network slice management method provided by one or more embodiments of the present application on the user equipment 1000 side, and execute the program including Instructions.

It can be 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 and mobile stations ( English: Mobile Station, referred to as MS) and terminal, etc.

It should be noted that the user equipment 1000 shown in FIG. 12 is only an implementation manner of the embodiment of the present application. In actual applications, the user equipment 1000 may further include more or fewer components, which is not limited here.

Referring to FIG. 13, FIG. 13 shows a network device 1100 provided by an embodiment of the present application. As shown in FIG. 13, the network device 1100 may include: one or more network device processors 1101, a memory 1102, and a communication interface 1103. These components can be connected via a bus 1104 or other types. FIG. 13 uses a bus connection as an example. among them:

The communication interface 1103 may be used for the network device 1100 to communicate with other communication devices, such as user equipment or other network devices. Specifically, the communication interface 1103 may be a 5G communication interface, or a communication interface of a new air interface in the future. Not limited to a wireless communication interface, the network device 1100 may also be configured with a wired communication interface 1103 to support wired communication. For example, the backhaul link between one network device 1100 and another network device 1100 may be a wired communication connection.

The memory 1102 is coupled with the network device processor 1101, and is used to store various software programs and/or multiple sets of instructions. Specifically, the memory 1102 may include a high-speed random access memory, and may also include a 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 system), such as embedded operating systems such as uCOS, VxWorks, and RTLinux. The memory 1102 may also store a network communication program, which may be used to communicate with one or more additional devices, one or more user devices, and one or more network devices.

In the embodiment of the present application, the network device processor 1101 may be used to read and execute computer-readable instructions. Specifically, the network device processor 1101 may be used to call a program stored in the memory 1102, such as the implementation program on the network device 1100 side of the network slice selection method provided by one or more embodiments of the present application, and execute the program included in the program. instruction.

It is understandable that the network device 1100 may be a core network entity, such as AMF, NSSF, UDM, and so on.

It should be noted that the network device 1100 shown in FIG. 13 is only an implementation manner of the embodiment of the present application. In actual applications, the network device 1100 may also include more or fewer components, which is not limited here.

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

The processor 1201 may be an integrated circuit chip with signal processing capabilities. In the implementation process, the steps of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 1201 or instructions in the form of software. The aforementioned 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 device, discrete hardware Components. The methods and steps disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.

The interface circuit 1202 can complete the sending or receiving of data, instructions or information. The processor 1201 can use the data, instructions or other information received by the interface circuit 1202 to perform processing, and can send processing completion information through the interface circuit 1202.

Optionally, the chip system further includes a memory 1203. The memory 1203 may include a read-only memory and a random access memory, and provides operation instructions and data to the processor. A part 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 can execute corresponding operations by calling operation instructions stored in the memory (the operation instructions may be stored in the operating system).

Optionally, the chip system may be used in user equipment or network equipment involved in the embodiments of the present application. Optionally, the interface circuit 1202 is configured to perform the receiving and sending steps of the user equipment, network equipment, etc. in the embodiments shown in FIG. 4 to FIG. 9. The processor 1201 is configured to execute the processing steps of the user equipment, network equipment, etc. in the embodiments shown in FIG. 4 to FIG. 9. The memory 1203 is used to store data and instructions of the user equipment, network equipment, etc. in the embodiments shown in FIG. 4 to FIG. 9. Network equipment includes core network entities such as AMF, NSSF, and UDM.

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

As an optional design, the 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 carry instructions or data. The structured form stores the required program code and can be accessed by the computer. Also, any connection is properly termed a computer-readable medium. For example, if you use coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology (such as infrared, radio and microwave) to transmit software from a website, server or other remote source, then coaxial cable, fiber optic cable , Twisted pair, DSL or wireless technologies such as infrared, radio and microwave are included in the definition of the medium. Magnetic disks and optical disks as used herein include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks and blu-ray disks, in which disks usually reproduce data magnetically, and optical disks use lasers to optically reproduce data. Combinations of the above should also be included in the scope of computer-readable media.

The embodiment of the present application also provides a computer program product. The methods described in the foregoing method embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. If it is implemented in software, it can be fully or partially implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the above computer program instructions are loaded and executed on the computer, the procedures or functions described in the above method embodiments are generated in whole or in part. The above-mentioned computer may be a general-purpose computer, a special-purpose computer, a computer network, network equipment, user equipment, or other programmable devices.

As mentioned above, the above embodiments are only used to illustrate the technical solutions of the present application, but not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: The technical solutions recorded in the embodiments are modified, or some of the technical features are equivalently replaced; these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

A network slice selection method, characterized in that it includes:

The first network slice selection function entity NSSF receives a first request message from the first access and mobility management function entity AMF, where the first request message includes location information of the user;

If it is determined that the first NSSF does not record the information of the network slice instance that allows the user to access the first area, the first NSSF receives the indication information of the first network slice instance from the second NSSF and the information of the second AMF Identification; the first network slice instance is selected from the network slice instances recorded in the second NSSF to allow the user to access in the first area, and the first area is all The area represented by the location information, the second AMF is the AMF configured in the first network slice instance;

Wherein, the information of the network slice instance includes the indication information of the network slice instance, the identifier of the AMF configured in the network slice instance, and the identifier of the area served by the network slice instance, and the first NSSF records Information about the network slice instances supported by the AMF in the first area, the second NSSF records information about the network slice instances supported by the AMF in K areas, and the K areas include the first area , K is a positive integer greater than 1.
The method according to claim 1, wherein the first request message further includes the subscribed network slice selection assistance information NSSAI of the user; if it is determined that the first NSSF does not record that the user is allowed to access The information of the network slice instance of the first area, where the first NSSF receives the indication information of the first network slice instance and the identifier of the second AMF from the second NSSF, including:

If it is determined that the first NSSF does not record the information of the network slice instance that allows the user to access the first area according to the NSSAI subscription of the user, the first NSSF receives the information from the second NSSF The indication information of the first network slice instance and the identifier of the second AMF.
The method according to claim 1, wherein the first request message further includes the user identification of the user; if it is determined that the first NSSF does not record a record that allows the user to access the network in the first area Information of the slice instance, the first NSSF receives the indication information of the first network slice instance and the identifier of the second AMF from the second NSSF, including:

If it is determined that the first NSSF does not record the information of the network slice instance that allows the user to access the first area according to the user’s subscription NSSAI characterized by the user identity, the first NSSF receives information from all The indication information of the first network slice instance of the second NSSF and the identifier of the second AMF, and the user's subscription NSSAI is obtained by the first NSSF from the unified data management entity UDM based on the user identifier .
The method according to any one of claims 1 to 3, 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 Methods also include:

The first NSSF sends a second request message to the second NSSF, where the second request message includes the identifier of the first AMF and information about the network slice instance supported by the first AMF, and the second request The 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.
The method according to claim 4, wherein after the first NSSF sends the 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 the identifier of the first AMF and the information of the second network slice instance, and the third request message is used to request all The second NSSF records the second network slice instance into a network slice instance supported by the first AMF.
The method according to claim 4 or 5, 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 the identifier of the first AMF, the indication information of the third network slice instance, and the information of the fourth network slice instance. 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.
The method according to any one of claims 4 to 6, 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 the identifier of the first AMF and the indication information of the fifth network slice instance, and the fifth request message is used to request The second NSSF removes the fifth network slice instance from the network slice instances supported by the first AMF.
The method according to any one of claims 4 to 7, wherein after the first NSSF sends a second request message to the second NSSF, the method further comprises:

The first NSSF sends a sixth request message to the second NSSF, where the sixth request message includes the identifier of the first AMF, and the sixth request message is used to request the second NSSF to transfer the first AMF to the second NSSF. An AMF-supported network slice instance is removed from the network slice instance recorded by the second NSSF.
The method according to any one of claims 1 to 8, wherein the indication information of the network slicing instance includes the NSSAI of the network slicing instance.
The method according to any one of claims 1 to 8, wherein the indication information of the network slice instance includes the network slice instance identifier NSI ID of the network slice instance.
The method according to any one of claims 1 to 8, wherein the second NSSF also records information about network slice instances supported by the global AMF, and the global AMF provides access and mobility for global users. Management service, the network slice instance subscribed by the global user is allowed to access M of the K areas, and M is a positive integer greater than 1 and less than or equal to K.
The method according to claim 11, wherein the user is a global user.
The method according to any one of claims 1 to 8, wherein the location information of the user is TA information of the user's tracking area.
A network slice selection method, characterized in that it includes:

The second network slice selection function entity NSSF receives the seventh request message from the first NSSF; wherein, 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 permission An example of a network slice accessed by a user in a first area, where the first area is an area characterized by the location information, and the access and mobility management function entities in the first area are recorded in the first NSSF Information about network slicing instances supported by AMF;

Sending, by the second NSSF, the indication information of the first network slice instance and the identifier of the second AMF to the first NSSF;

Wherein, the information of the network slice instance includes the indication information of the network slice instance, the identifier of the AMF configured in the network slice instance, and the identifier of the area served by the network slice instance, and the first network slice instance is A network slice instance selected from the network slice instances recorded in the second NSSF to allow the user to access in the first area, and the second NSSF records the networks supported by the AMF in K areas Information about the slice instance, 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.
The method according to claim 14, characterized in that the seventh request message further includes the subscriber's subscription network slice selection assistance information NSSAI, and the seventh request message is used to request the second NSSF according to the The user's subscription NSSAI selects a network slice instance that allows the user to access in the first area.
The method according to claim 14, characterized in that the seventh request message further includes the user identification of the user; the seventh request message is used to request the second NSSF to request all information represented by the user identification. The user's subscription NSSAI is selected to allow the user to access the network slice instance in the first area, and the user's subscription NSSAI is obtained by the second NSSF from the unified data management entity UDM based on the user identifier .
The method according to any one of claims 14 to 16, wherein before the second network slice selection function entity NSSF receives the 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 the identifier of the first AMF and information about the network slice instance supported by the first AMF, and the second request message It 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.
The method according to claim 17, wherein after the second NSSF receives the second request message from the first NSSF, the method further comprises:

The second NSSF receives a third request message from the first NSSF, where the third request message includes the identifier of the first AMF and the information of the second network slice instance, and the third request message is used to request The second NSSF adds the second network slice instance to the network slice instance supported by the first AMF.
The method according to claim 17 or 18, wherein after the first NSSF sends a second request message to the second NSSF, the method further comprises:

Receiving, by the second NSSF, a fourth request message from the first NSSF, where the fourth request message includes the identifier of the first AMF, the indication information of the third network slice instance, and the information of the fourth network slice instance, 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.
The method according to any one of claims 17 to 19, wherein after the first NSSF sends a second request message to the second NSSF, the method further comprises:

The second NSSF receives a fifth request message from the first NSSF, where the fifth request message includes the identifier of the first AMF and information about the fifth network slice instance, and the fourth request message is used to request The second NSSF removes the fifth network slice instance from the network slice instances supported by the first AMF.
The method according to any one of claims 17 to 18, wherein after the first NSSF sends a second request message to the second NSSF, the method further comprises:

The second NSSF receives a sixth request message from the first NSSF, where the sixth request message includes the identifier of the first AMF, and the sixth request message is used to request the second NSSF to transfer the The network slice instance of the first AMF is removed from the network slice instance recorded by the second NSSF.
The method according to any one of claims 14 to 21, wherein the seventh request message is when the first NSSF determines that the first NSSF has no record allowing the user to access the first area Sent after the instance of the network slicing.
The method according to any one of claims 14 to 22, wherein the indication information of the network slicing instance comprises the NSSAI of the network slicing instance.
The method according to any one of claims 14 to 23, wherein the indication information of the network slice instance includes the network slice instance identifier NSI ID of the network slice instance.
The method according to any one of claims 14 to 23, wherein if the network slice instance subscribed by the user includes a network slice instance that allows the user to access in the first area, the The first network slice instance is a network slice instance selected from the network slices ordered by the user that allows the user to access in the first area.
The method according to any one of claims 14 to 23, wherein if the network slice instance corresponding to the NSSAI subscription of the user does not include a network slice instance that allows the user to access in the first area, Then the first network slice instance is the network slice selected by the second NSSF from the network slice instances recorded in the second NSSF according to the roaming mapping table to allow the user to access in the first area For example, the roaming mapping table includes the mapping relationship between the user's subscription NSSAI and the user's allowed NSSAI, and the user's allowed NSSAI includes a network slice instance that allows the user to access in the first area NSSAI.
The method according to any one of claims 14 to 23, wherein the second NSSF also records information about network slice instances supported by the global AMF, and the global AMF provides access and mobility for global users. Management service, the network slice instance subscribed by the global user is allowed to access M of the K areas, and M is a positive integer greater than 1 and less than or equal to K.
The method according to claim 27, wherein the user is a global user.
The method according to any one of claims 14 to 23, wherein the location information of the user is TA information of the user's tracking area.
A network device, characterized in that it comprises:

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

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

Wherein, the information of the network slice instance includes the indication information of the network slice instance, the identifier of the AMF configured in the network slice instance, and the identifier of the area served by the network slice instance. The information of the network slice instances supported by the AMF in the first area, the second NSSF records the information of the network slice instances supported by the AMF of K areas, and the K areas include the first area, K is a positive integer greater than 1.
The network device according to claim 30, wherein the first request message further includes the subscriber's subscription network slice selection assistance information NSSAI;

The first receiving unit is specifically configured to: if it is determined that the network device does not record information about the network slice instance that allows the user to access the first area according to the NSSAI subscription of the user, then receive information from the second The indication information of the first network slice instance of the NSSF and the identifier of the second AMF.
The network device according to claim 30, wherein the first request message further includes a user identification of the user;

The first receiving unit is specifically configured to: if it is determined that the network device does not record the information of the network slice instance that allows the user to access the first area according to the subscription NSSAI of the user represented by the user identifier, then Receive the indication information of the first network slice instance from the second NSSF and the identifier of the second AMF, the user's subscription NSSAI is obtained by the network device from the unified data management entity UDM based on the user identifier .
The network device according to any one of claims 30 to 32, 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 include:

The first sending unit is configured to send a second request message to the second NSSF, where the second request message includes the identifier of the first AMF and the information of the network slice instance supported by the first AMF. 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.
The network device according to claim 33, wherein after the first sending unit sends the second request message to the second NSSF, the first sending unit is further configured to:

Send a third request message to the second NSSF, where the third request message includes the identifier of the first AMF and the information of the second network slice instance, and the third request message is used to request the second NSSF to The second network slice instance is recorded in the network slice instance supported by the first AMF.
The network device according to claim 33 or 34, wherein after the first sending unit sends the second request message to the second NSSF, the first sending unit is further configured to:

A fourth request message is sent to the second NSSF, where the fourth request message includes the identifier of the first AMF, the indication information of the third network slice instance, and the information of the fourth network slice instance, the fourth request message For requesting the second NSSF to replace the third network slice instance supported by the first AMF with the fourth network slice instance.
The network device according to any one of claims 33 to 35, wherein after the first sending unit sends a second request message to the second NSSF, the first sending unit is further configured to:

Send a fifth request message to the second NSSF, where the fifth request message includes the identifier of the first AMF and the indication information of the fifth network slice instance, and the fifth request message is used to request the second NSSF Removing the fifth network slice instance from the network slice instances supported by the first AMF.
The network device according to any one of claims 33 to 36, wherein after the first sending unit sends a second request message to the second NSSF, the first sending unit is further configured to:

Send a sixth request message to the second NSSF, where the sixth request message includes the identifier of the first AMF, and the sixth request message is used to request the second NSSF to use the network supported by the first AMF The slice instance is removed from the network slice instance recorded by the second NSSF.
The network device according to any one of claims 33 to 37, wherein the indication information of the network slice instance includes the NSSAI of the network slice instance.
The method according to any one of claims 33 to 36, wherein the indication information of the network slice instance includes the network slice instance identifier NSI ID of the network slice instance.
The network device according to any one of claims 30 to 38, wherein the second NSSF also records information about network slice instances supported by the global AMF, and the global AMF provides access and access for global users. For mobile management services, the network slice instance subscribed by the global user is allowed to access M of the K areas, and M is a positive integer greater than 1 and less than or equal to K.
The network device according to claim 40, wherein the user is a global user.
The method according to any one of claims 30 to 38, wherein the location information of the user is TA information of the tracking area of the user.
A network device, characterized in that it comprises:

The second receiving unit is configured to receive a seventh request message from the first NSSF; wherein, the seventh request message includes the location information of the user, and the seventh request message is used to request the network device to choose to allow the user An example of a network slice accessed in the first area, the first area is an area characterized by the location information, and the access and mobility management function entities in the first area are recorded in the first NSSF Information about network slicing instances supported by AMF;

The second sending unit is configured to send 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 the indication information of the network slice instance, the The identifier of the AMF configured in the network slice instance and the identifier of the area served by the network slice instance, the first network slice instance is selected from the network slice instances recorded in the network device to allow the user to be In the network slice instance of the first area access, information of the network slice instance supported by the AMF of K areas is recorded on the network device, the K areas include the first area, and the second AMF is In the AMF configured in the first network slice instance, K is a positive integer greater than 1.
The network device according to claim 43, wherein the seventh request message further includes the user's subscription network slice selection assistance information NSSAI; the seventh request message is used to request the network device to select the network slice according to the The user's subscription NSSAI selects a network slice instance that allows the user to access in the first area.
The network device according to claim 43, wherein the first request message further includes a user identification; the seventh request message is used to request the network device to sign the user's subscription according to the user identification NSSAI, selecting a network slice instance that allows the user to access in the first area, and the user's subscription NSSAI is obtained by the network device from a unified data management entity UDM based on the user identifier.
The network device according to any one of claims 43 to 45, wherein before the second receiving unit receives the seventh request message from the first NSSF, the second receiving unit is further configured to:

Receive a second request message from the first NSSF, where the second request message includes the identifier of the first AMF and information about the network slice instance supported by the first AMF, and the second request message is used to request the The network device records the network slice instance supported by the first AMF into the network slice instance recorded by the network device.
The network device according to claim 46, wherein after the second receiving unit receives the second request message from the first NSSF, the second receiving unit is further configured to:

Receive a third request message from the first NSSF, where the third request message includes the identifier of the first AMF and information about the second network slice instance, and the third request message is used to request the network device to The second network slice instance is added to the network slice instance supported by the first AMF.
The network device according to claim 46 or 47, wherein after the second receiving unit receives the second request message from the first NSSF, the second receiving unit is further configured to:

Receive a fourth request message from the first NSSF, where the fourth request message includes the identifier of the first AMF, the indication information of the third network slice instance, and the information of the fourth network slice instance, the fourth request The message is used to request the network device to replace the third network slice instance supported by the first AMF with the fourth network slice instance.
The network device according to any one of claims 46 to 48, wherein after the second receiving unit receives the second request message from the first NSSF, the second receiving unit is further configured to:

Receive a fifth request message from the first NSSF, where the fifth request message includes the identifier of the first AMF and the indication information of the fifth network slice instance, and the fourth request message is used to request the network device Removing the fifth network slice instance from the network slice instances supported by the first AMF.
The network device according to any one of claims 46 to 49, wherein after the second receiving unit receives the second request message from the first NSSF, the second receiving unit is further configured to:

Receive a sixth request message from the first NSSF, where the sixth request message includes the identifier of the first AMF, and the sixth request message is used to request the network device to slice the network of the first AMF The instance is removed from the network slice instance recorded by the network device.
The network device according to any one of claims 46 to 50, wherein the seventh request message is when the first NSSF determines that the first NSSF has no record allowing the user to access the first NSSF. Sent after the network slice instance of the area.
The network device according to any one of claims 46 to 51, wherein the indication information of the network slice instance comprises the NSSAI of the network slice instance.
The method according to any one of claims 46 to 51, wherein the indication information of the network slice instance includes the network slice instance identifier NSI ID of the network slice instance.
The network device according to any one of claims 46 to 52, wherein if the network slice instance corresponding to the NSSAI of the user's subscription does not include a network slice instance that allows the user to access in the first area , The first network slice instance is the network slice instance that the network device selects from the network slice instances recorded in the network device according to the roaming mapping table and allows the user to access in the first area The roaming mapping table includes the mapping relationship between the user's subscription NSSAI and the user's allowed NSSAI, and the user's allowed NSSAI includes the network slice instance that allows the user to access in the first area NSSAI.
The network device according to any one of claims 46 to 54, characterized in that, the network device also records information about network slice instances supported by the global AMF, and the global AMF provides access and mobility for global users. Management service, the network slice instance ordered by the global user is allowed to access M of the K areas, and M is a positive integer greater than 1 and less than or equal to K.
The network device according to claim 55, wherein the user is a global user.
The method according to any one of claims 46 to 56, wherein the location information of the user is TA information of the tracking area of the user.
A communication system, characterized by comprising a first NSSF that executes the method according to any one of claims 1 to 13, and a second NSSF that executes the method according to any one of claims 14 to 29.
A communication device, characterized by comprising: at least one processor; wherein, the at least one processor is used to couple with a memory, read computer instructions stored in the memory, and execute according to the computer instructions as claimed in claim The method steps described in any one of 1-13.
A communication device, characterized by comprising: at least one processor; wherein, the at least one processor is used to couple with a memory, read computer instructions stored in the memory, and execute according to the computer instructions as claimed in claim The method steps described in any one of 14-29.
A communication device, characterized in that it is used to execute the method according to any one of claims 1 to 13.
A communication device, characterized in that it is used to execute the method according to any one of claims 14 to 29.
A computer-readable storage medium, characterized in that it stores computer-executable instructions for causing a computer to execute the method according to any one of claims 1 to 13; or to execute the method as claimed in any one of claims 1 to 13; The method of any one of 14-29.
A computer program product, characterized in that it contains computer-executable instructions for causing a computer to execute the method according to any one of claims 1 to 13; or to execute the method according to any one of claims 1 to 13; The method of any one of 29.