WO2020103523A1

WO2020103523A1 - Network slice selection method, network device and terminal

Info

Publication number: WO2020103523A1
Application number: PCT/CN2019/104317
Authority: WO
Inventors: 李卓明
Original assignee: 华为技术有限公司
Priority date: 2018-11-19
Filing date: 2019-09-04
Publication date: 2020-05-28
Also published as: CN111200859A

Abstract

The embodiment of the present application discloses a network slice selection method, which is used for a first network device to select a network slice instance according to a scenario tag of an application for a usage scenario of the application, meeting the requirements of applications for using different network slices in different usage scenarios. The method of embodiment of the present application comprises: the first network device receiving a first request message, the first request message comprising a scenario tag of an application for indicating a usage scenario of the application; the first network device selecting a network slice instance for the usage scenario according to the scenario tag; and the first network device sending a first response message comprising indication information for indicating the network slice instance.

Description

Network slice selection method, network equipment and terminal

This application requires the priority of the Chinese patent application filed on November 19, 2018 in the Chinese Patent Office with the application number 201811377401.3 and the application name "A network slice selection method, network equipment and terminal", the entire content of which is cited by reference Incorporated in this application.

Technical field

The present application relates to the field of communication technology, and in particular, to a network slice selection method, network equipment, and terminal.

Background technique

In the prior art, the network slice selection policy (NSSP) configured by the terminal is the application ID of each application (application ID) and different single network slice selection auxiliary information (single network slice selection assistance, information, S -NSSAI) associated. For example, the terminal installs a virtual reality (virtual reality, VR) game application and a social application. The communication session initiated by the VR game application can be carried using low-latency, high-bandwidth network slice instances, while the communication session initiated by the social application You can use ordinary mobile broadband network slice instance bearer. Therefore, according to the configured NSSP, the terminal can associate the application identifier of the VR game with the S-NSSAI corresponding to the low-latency, high-bandwidth network slice instance, and associate the application identifier of the social application with the S corresponding to the ordinary mobile broadband network slice instance. -NSSAI is associated.

However, with the change of people's life needs and the development of technology, different services of the same application have different requirements for communication quality, which needs further study. For example, a real-time communication application can perform both ordinary video calls and VR video calls. Ordinary video calls use ordinary mobile broadband network slicing instances, while VR video calls require low-latency and high-bandwidth network slicing instances.

Summary of the invention

Embodiments of the present application provide a method for selecting a network slice, a network device, and a terminal. The first network device can select a network slice instance for the application's usage scenario according to the application's scene label, which can satisfy the application in different usage scenarios. Need to use different network slices.

In view of this, the first aspect of the embodiments of the present application provides a method for selecting a network slice, which may include: a first network device receives a first request message, the first request message includes an application scene tag, and the scene tag is used for Indicate the usage scenario of the application; it can be understood that the scenario tag is an identification of different usage scenarios of the application, and is used to distinguish the scenario when the application requests the terminal to establish a communication connection. The scene tags are allocated and managed by the industry tenant's application according to their own business needs. According to the scene tags, the corresponding scene reference information set by the industry tenant can be determined. Among them, the use scenario can be understood as the application client working mode, application server side usage mode, etc., which are defined and set by the application according to its own specific service requirements. The definition and setting of the use scenario are not controlled by the operator network. The first network device selects a network slice instance for the usage scenario according to the scene label; the first network device sends a first response message, and the first response message includes indication information for indicating the network slice instance. In the embodiment of the present application, the first network device may select a network slicing instance for the application's usage scenario according to the application's scenario label, to meet the application's need to use different network slicing in different usage scenarios, and no network configuration is required on the terminal With the slice selection strategy, the network equipment does not need to be maintained, which can reduce the cost of the terminal and save the system resources of the terminal.

Optionally, in some embodiments of the present application, the first network device selecting a network slice instance for the usage scenario according to the scenario label may include: the first network device obtaining scenario reference information according to the scenario label; Then, the first network device selects the network slice instance for the usage scenario according to the scenario reference information. In the embodiment of the present application, it is a specific description for the first network device to select a network slice instance for the usage scenario according to the scenario label, that is, the scenario reference information can be obtained according to the scenario label first, and then the scenario reference information can be used for the use The scene selection network slicing example improves the enforceability of the technical solution of the present application.

Optionally, in some embodiments of the present application, the first network device selects a NSSF entity for network slice selection, and the first network device receives the first request message, which may include: the first network device receives The network slice selection request message of the AMF entity of the mobile management function. The network slice selection request message includes the scene label and reference information of the application. In the embodiment of the present application, when the first network device is a network slice selection function entity, the first request message received by the first network device is a network slice selection request message sent from an access and mobility management function AMF entity. The scene tags and application reference information included in the slice selection request message can be used to select a network slice instance.

Optionally, in some embodiments of the present application, the reference information of the application may include at least one of the identification of the application or the single network slice selection auxiliary information S-NSSAI corresponding to the application. In the embodiment of the present application, a specific description of the reference information of the application provides multiple optional implementation solutions, and the reference information of the application can be used to obtain corresponding scene reference information.

Optionally, in some embodiments of the present application, the first network device acquiring the scene reference information according to the scene tag may include: the first network device sends a second request message to the second network device, the second The request message includes the scene tag and reference information of the application; the first network device receives a second response message of the second request message from the second network device, the second response message includes the scene reference information, the first The second network device is an application information management function AIMF entity or a policy control function PCF entity; or, the first network device determines the scenario reference information according to the scenario label and the application reference information. In the embodiment of the present application, the first network device is a network slice selection function NSSF entity, and there are two ways to obtain scene reference information: first, the scene reference information here is determined by the second network device, and then, the second network The device sends to the first network device; second, the first network device determines the scene reference information according to the scene label and the applied reference information. It provides a specific implementation method for obtaining scenario reference information for the technical solution of the present application, and increases the feasibility of the solution.

Optionally, in some embodiments of the present application, the scenario reference information includes at least one of functional requirements of the usage scenario or service quality QoS capability requirements of the usage scenario. In the embodiment of the present application, a specific description of the scene reference information provides multiple optional implementation solutions, and the scene reference information can be used to select a network slice instance.

Optionally, in some embodiments of the present application, the reference information of the application includes the S-NSSAI corresponding to the application, and the first network device selects the network slice instance for the usage scenario according to the scenario reference information, which may include : When the scenario reference information includes the functional requirements of the usage scenario, the first network device selects the network slice instance from the network slice instances corresponding to the S-NSSAI, and the network slice instance meets the functional requirements; or, When the scenario reference information includes the QoS capability requirements of the usage scenario, the first network device selects the network slice instance from the network slice instances corresponding to the S-NSSAI, and the network slice instance meets the QoS capability requirements. In the embodiment of the present application, when the reference information of the application includes the S-NSSAI corresponding to the application, the first network device may select a network slice instance from the network slice instances corresponding to the S-NSSAI to satisfy the scenario reference information, the The scenario reference information may include the functional requirements of the usage scenario or the QoS capability requirements of the usage scenario, and a reliable network slice instance may be selected for the usage scenario of the application.

Optionally, in some embodiments of the present application, the reference information of the application includes an identifier of the application, the application identifier corresponds to a default S-NSSAI, and the first network device selects the usage scenario according to the scenario reference information The network slice instance may include: when the scenario reference information includes the functional requirements of the usage scenario, the first network device selects the network slice instance from the network slice instances corresponding to the default S-NSSAI, and the network slice instance meets The functional requirement; or, when the scenario reference information includes the QoS capability requirement of the usage scenario, the first network device selects the network slice instance from the network slice instances corresponding to the default S-NSSAI, and the network slice instance satisfies the QoS capability requirements. In the embodiment of the present application, when the reference information of the application includes the identification of the application, the first network device may select the network slice instance from the network slice instances corresponding to the default S-NSSAI to satisfy the scene reference information, the scene The reference information may include the functional requirements of the usage scenario or the QoS capability requirements of the usage scenario, and a reliable network slice instance may be selected for the usage scenario of the application.

Optionally, in some embodiments of the present application, the first network device is an AIMF entity or a PCF entity, and the first network device receives the first request message may include: the first network device receives a scene from the NSSF entity Information request, the scene information request includes the scene label and the S-NSSAI corresponding to the application; the first network device selects a network slice instance for the usage scenario according to the scene label, which may include: the first network device according to the scene The label and the S-NSSAI select the network slice instance for the usage scenario. In the embodiment of the present application, when the first network device is an AIMF entity or a PCF entity, the first network device receives a scene information request sent from an NSSF entity, and the first network device may select a network slice instance according to the scene information request. That is, an optional implementation solution is provided for the embodiments of the present application, which increases the flexibility of the technical solution of the present application.

A second aspect of an embodiment of the present application provides a method for selecting a network slice, which may include: a terminal obtains a scene label of an application, the scene label is used to indicate a usage scenario of the application; and the terminal sends the scene label to a first network device. In the embodiment of the present application, the terminal obtains the scene label of the application, and then sends the scene label to the first network device, where the scene label is used by the first network device to select the corresponding network slice instance. To meet the needs of applications that need to use different network slices in different usage scenarios, reduce terminal costs, and save terminal system resources.

Optionally, in some embodiments of the present application, the terminal acquiring the scene label of the application may include: the terminal receiving a session establishment request message from the application client, and the session establishment request message includes the scene label. In the embodiment of the present application, a specific description is made on the terminal acquiring the scene label, that is, the terminal receives the session establishment request message from the application client, and the session establishment request message carries the scene label.

Optionally, in some embodiments of the present application, the method may further include: the terminal receiving a session establishment acceptance message sent by the first network device; the terminal generating a mapping relationship between the scene label and the session. In the embodiment of the present application, the terminal receives the session establishment acceptance message sent by the first network device, and then generates a mapping relationship between the scene label and the session according to the session establishment acceptance message. When the terminal obtains the data interface call request again, it can directly find the corresponding session from the mapping relationship according to the scene label carried in the data interface call request, so as to perform subsequent communication. If the corresponding session cannot be found, the data interface call request is sent to the first network device. Thus, time is saved, and resources for signaling interaction are saved.

Optionally, in some embodiments of the present application, the method may further include: the terminal receives a data interface call request from an application client, the data interface call request includes the scene label; the terminal according to the scene label and the mapping Relationship, the session can be determined; the terminal then sends the data of the usage scenario through the session. In the embodiment of the present application, when the terminal receives the data interface call request sent by the application client, it can determine the corresponding session according to the scene label carried in the data interface call request and the mapping relationship, thereby saving the establishment of the session Time and save system resources.

A third aspect of an embodiment of the present application provides a method for selecting a network slice, which may include: a second network device receives a second request message from the first network device, where the second request message includes an application scene tag and a reference to the application Information, the scene tag is used to indicate the usage scenario of the application; the second network device determines scene reference information according to the scene tag; the second network device sends a second response message to the first network device, the second response The message is used to respond to the second request message, and the second response message includes the scene reference information. In the embodiment of the present application, the second network device receives the second request message sent by the first network device, and the second request message may include the scene label of the application and reference information of the application, and the second network device may be based on the information, To determine the scene reference information. Then send the scene reference information to the first network identity, and the first network device may be used to select a network slice instance. The technical solution of the present application for obtaining scene reference information provides a specific implementation method and increases the feasibility of the solution.

Optionally, in some embodiments of the present application, the first network device is a network slice selection function NSSF entity; the second network device is a policy control function PCF entity or an application information management function AIMF entity. In the embodiment of the present application, a specific description is given to the first network device, which may be a network slice selection functional entity or a network slice selection functional entity, which can implement the technical solution of the present application and improve the technical solution of the present application Flexibility.

Optionally, in some embodiments of the present application, the reference information of the application includes at least one of the identification of the application or the single network slice selection auxiliary information S-NSSAI corresponding to the application; the scene reference information includes the usage At least one of the functional requirements of the scenario or the service quality QoS capability requirements of the usage scenario. In the embodiment of the present application, in the embodiment of the present application, a specific description of the reference information of the application provides multiple optional implementation solutions, and the reference information of the application can be used to obtain corresponding scene reference information.

The fourth aspect of the embodiments of the present application provides a network device, which implements an example of selecting a network slice for a usage scenario of the application according to the application scenario label provided in the first aspect above, which can satisfy that the application needs to use different scenarios under different usage scenarios. The need for network slicing. This function can be realized by hardware, and can also be realized by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

A fifth aspect of an embodiment of the present application provides a terminal having a scene tag corresponding to the application sent to a network device provided in the second aspect above. The scene tag is used by the network device to select a network slicing instance for a usage scenario of the application. Meet the needs of applications that need to use different network slices in different usage scenarios. This function can be realized by hardware, and can also be realized by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

A sixth aspect of an embodiment of the present application provides a network device having a method for determining scene reference information corresponding to the scene label provided in the third aspect above. The scene information is used by the network device to select a network slice instance for the application usage scenario. Meet the needs of applications that need to use different network slices in different usage scenarios. This function can be realized by hardware, and can also be realized by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

A seventh aspect of the embodiments of the present application provides a network device, which may include:

A memory, a transceiver and a processor, the memory, the transceiver and the processor are connected by a bus;

The transceiver is used to communicate with devices other than the network equipment;

The memory is used to store operation instructions;

The processor is configured to call the operation instruction and execute the method as described in the first aspect or any optional implementation manner of the first aspect of the present application.

An eighth aspect of an embodiment of this application provides a network device, which may include:

The transceiver is used to communicate with devices other than the terminal;

The memory is used to store operation instructions;

The processor is configured to call the operation instruction and execute the method described in the second aspect or any optional implementation manner of the second aspect of the present application.

A ninth aspect of an embodiment of the present application provides a network device, which may include:

The memory is used to store operation instructions;

The processor is configured to call the operation instruction to execute the method described in the third aspect or any optional implementation manner of the third aspect of the present application.

A tenth aspect of an embodiment of the present application provides a communication system. The communication system includes a first network device, a terminal, and a second network device. The first network device is an optional implementation of the first aspect or any of the first aspect of the present application. The network device described in the manner; the terminal is the terminal described in the second aspect of the present application or any optional implementation manner of the second aspect; the second network device is the terminal described in the third aspect or the third aspect of the present application A network device described in an optional implementation manner.

An eleventh aspect of an embodiment of the present invention provides a storage medium. It should be noted that the technical solution of the present invention essentially or part of the contribution to the existing technology or all or part of the technical solution can be produced by software Embodied in the form of, the computer software product is stored in a storage medium for storing computer software instructions used by the above-mentioned device, which contains the first network device for performing the above-mentioned first aspect, second aspect or third aspect , The program designed by the terminal or the second network device.

The storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and other media that can store program codes.

A twelfth aspect of an embodiment of the present invention provides a computer program product containing instructions, which when run on a computer, causes the computer to execute the method as described in the first aspect or any optional implementation manner of the first aspect of the present application .

A thirteenth aspect of an embodiment of the present invention provides a computer program product containing instructions that, when run on a computer, cause the computer to execute the method as described in the second aspect or any optional implementation manner of the second aspect of the present application .

A fourteenth aspect of an embodiment of the present invention provides a computer program product containing instructions that, when run on a computer, cause the computer to perform the method as described in the third aspect or any optional implementation manner of the third aspect of the present application .

It can be seen from the above technical solutions that the embodiments of the present application have the following advantages:

In the embodiment of the present application, the first network device receives a first request message, where the first request message includes an application scene tag, and the scene tag is used to indicate a usage scenario of the application; the first network device according to The scenario label selects a network slice instance for the usage scenario; the first network device sends a first response message, and the first response message includes indication information for indicating the network slice instance. That is, the first network device can select a network slicing instance for the application's usage scenario according to the application's scenario label, which can meet the application's need to use different network slicing in different usage scenarios.

BRIEF DESCRIPTION

In order to more clearly explain the technical solutions of the embodiments of the present application, the following will briefly introduce the drawings required in the embodiments and the description of the prior art. Obviously, the drawings in the following description are only some implementations of the present application For example, other drawings can be obtained from these drawings.

Figure 1 is a schematic diagram of a network slice defined by 3GPP;

FIG. 2 is a schematic diagram of a communication service instance using two network slice instances to carry business;

3 is a schematic diagram of a network slice selection mechanism defined by 3GPP;

4 is a schematic diagram of the correspondence between network slices and network slice examples in an embodiment of the present application;

Figure 5 is a system architecture diagram applied in this application;

6 is a schematic diagram of an embodiment of a method for selecting a network slice in an embodiment of the present application;

7 is a schematic diagram of an embodiment of a method for selecting a network slice in an embodiment of this application;

8 is a schematic diagram of an embodiment of a method for selecting a network slice in an embodiment of the present application;

9 is a schematic diagram of an embodiment of a network device in an embodiment of this application;

10A is a schematic diagram of an embodiment of a terminal in an embodiment of the present application;

10B is a schematic diagram of another embodiment of the terminal in the embodiment of the present application;

11 is a schematic diagram of another embodiment of a network device in an embodiment of this application;

12 is a schematic diagram of an embodiment of a network device in an embodiment of this application;

13 is a schematic diagram of an embodiment of a terminal in an embodiment of this application;

14 is a schematic diagram of an embodiment of a network device in an embodiment of this application.

detailed description

Embodiments of the present application provide a method for selecting a network slice, network equipment, and a terminal, which are used to reduce the cost of the terminal, save system resources, and meet the needs of an application that needs to use different network slices in different usage scenarios.

In order to enable those skilled in the art to better understand the solutions of the present application, the technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the present application Examples, not all examples. Based on the embodiments in this application, they should all fall within the protection scope of this application.

The following is a brief description of the terms involved in this application, as follows:

A network slice (network slice) is a logical network with specific network characteristics. Network slicing is a key feature of network function virtualization (NFV) and software-defined network (SDN) applied to communication networks (for example, 5G networks).

A physical network can be abstractly divided into multiple network slices, and each network slice constitutes an end-to-end logical network, which is logically isolated from each other. Each network slice can flexibly provide one or more network services according to user requirements, and does not affect each other in the network. Therefore, network slicing is a logical network with specific network characteristics divided in the operator's communication network.

Generally, the network characteristics of different network slices are not the same, and the network slices are required to be isolated from each other without affecting each other. For example, network slices of augmented implementation (AR) or virtual reality (VR) services require large-bandwidth and low-latency services; network slices of Internet of Things (IOT) services require support for massive terminal access Incoming, but the bandwidth is small, no delay is required. A user may order multiple network slice instances at an operator to carry application services. After the operator divides the communication network into a series of network slices, it is logically isolated from each other and has different network characteristics, so that a physical network can meet the differentiated business needs of different industries for communication networks. Users can use terminals to establish communication session connections in different network slices to carry different application services.

In order to support network slicing, as shown in Figure 1, 3GPP has defined the identification and related definitions about network slicing. According to the order of the industry tenant, the operator creates a relatively isolated logical network with specific network characteristics and supporting specific business capabilities on the physical infrastructure of the communication network according to the network slicing template, called a network slicing instance ( network slice instance (NSI), the network slice instance is identified using a network slice instance identifier (NSI ID). Users of industry tenants can use terminals to establish communication session connections on this network slice instance to carry application services. Terminals and network devices use NSSAI (network slice selection assistance information) to select appropriate network slice instances for various communication sessions of the terminal.

Among them, NSSAI may be composed of a group of S-NSSAI. Each S-NSSAI can be divided into two parts: SST (slice / service type) and SD (slice differentiator). SST is divided into two types: standard and custom. Standard SST is supported by all operators' 5G networks, which can ensure the consistency of the terminal's business experience in roaming scenarios; custom SST is only available in this operator's 5G Support within the network. If roaming, the roaming agreement signed by the operator and other operators is required to support the mapping of the customized SST to the standard SST or the customized SST of other operators in the roaming network. At present, the defined standard SSTs include enhanced mobile broadband (eMBB), ultra-low latency and ultra-high reliability communication (ultra-reliable and low-latency communication (URLLC), and massive Internet of Things (massive internet of things) , MIoT). SD is used to distinguish multiple network slices of the same SST. Generally, it will include the industry tenant ID or other custom information that subscribes to the slice. The specific use of the standard is not limited.

According to the definition of 3GPP TS (Technical Specification), industry tenants who order network slices can use terminals to carry specific application services in multiple network slice instances. As shown in FIG. 2, FIG. 2 is a schematic diagram of communication service instance 2 that can use two network slice instances NSI A and NSI B to carry services. For example, a remote control excavator application has two usage scenarios, one is a remote control scenario, and the other is a remote diagnosis scenario. The two scenarios have different requirements for optimizing network functions. The application services in the remote control scenario require large-bandwidth transmission with time delay and reliability guarantee, while the remote diagnosis scenario only requires large-bandwidth transmission without delay and reliability requirements. Therefore, after an industry tenant orders a network slice, the operator creates two different network slice instances for the industry tenant according to service differences, and transmits the application service flow of the remote diagnosis scenario and the application service flow of the remote control scenario, respectively. When an application uses a terminal to initiate a communication session, how to select different network slice instances for the terminal's communication session according to different application usage scenarios is a problem to be solved by the communication network.

As shown in FIG. 3, a schematic diagram of a network slice selection mechanism defined by 3GPP. Among them, the network slice selection mechanism is defined in 3GPP TS23.501.

In order to achieve network slice selection, the terminal is configured with an NSSP, and the NSSP may include one or more rules. Among them, Rule 1 in FIG. 3 may refer to the application using the application ID (Application ID) App-A to request to establish a communication session, the terminal uses S-NSSAI1 in the session establishment request message; Rule 2 may refer to the application using the application ID App-A When B requests to establish a communication session, the terminal uses S-NSSAI2 in the session establishment request message; In addition, a default rule is set. When an application that does not match other rules initiates a request to establish a communication session, the terminal uses the S-specified by the default rule. NSSAI1 initiates session establishment.

Exemplarily, taking the application of the remote control excavator as an example to illustrate the above process, the operator deploys two network slice instances and configures two different S-NSSAIs for the remote control excavator application, namely S-NSSAI1 and S -NSSAI 2. In order to use S-NSSAI1 for remote diagnostics to establish a communication session, and S-NSSAI2 for remote control to establish a communication session; then the application must use App-A to request the terminal to establish a session during remote diagnosis; the application must use Use App-B to request the terminal to establish a session. The specific process is as follows:

Step 1: The terminal sends a session establishment request message to the access and mobility management function (AMF) through the access network (AN), where the session establishment request message can carry S-NSSAI or Carry NSI ID.

Among them, the NSI ID may be a network slice selection function (network slice selection function, NSSF) provided in the terminal registration process for access and mobility management functions (access and mobility management function, AMF).

Step 2: Based on the S-NSSAI (optionally carrying NSI ID) carried in the session establishment request message, the AMF requests an instance of the session management function (SMF) from the network warehouse function (NRF).

The NRF may be global (for example, multiple network slices share the NRF), or may be within a network slice instance. The NRF address can be provided by the NSSF to the AMF in the terminal registration process.

NRF selects a session management function (SMF) within a suitable network slice based on S-NSSAI or NSI ID, and returns its address to AMF.

Step 3: The AMF forwards the session establishment request message to the selected SMF.

Step 4: After receiving the session establishment request message, the SMF processes it, selects the appropriate user plane function (UPF) and controls the UPF to establish a packet data unit (PDU) session.

Step 5: SMF sends the session establishment response message to the terminal through AMF and AN, and simultaneously informs AN of the session related information through AMF, including S-NSSAI, and the tunnel address and quality of service (QoS) of the session user plane Parameters and other information.

However, the existing technology is not flexible enough for applications, and adding an application usage scenario requires consultation with the operator to modify related configurations. For example, if a remote software upgrade scenario is added to the remote control excavator application, Internet access is required, and there are no special requirements for latency and bandwidth. Use a public enhanced mobile broadband (eMBB) slice instance. fulfil requirements. If existing technology is used, industry tenants and operators need to negotiate a new application identifier named "application-ID-diagnose", and a new rule configuration is added to the terminal's NSSP, which requires the establishment of "application-ID-diagnose" When communicating a session, the S-NSSAI used in the session establishment request is "S-NSSAI3". At the same time, the network side also needs to increase the corresponding configuration, that is, add the configuration of the S-NSSAI whose value is "S-NSSAI3" to the public eMBB slice instance whose NSI ID is "NS # 0" on the NSSF. As can be seen from this example: changes in application usage scenarios require industry tenants and operators to negotiate and allocate new identifiers and add corresponding configurations. The current slicing selection mechanism not only leads to complicated terminal configuration, occupies a lot of system resources, and has high costs. Changes in scenarios often require industry tenants and operators to negotiate new configurations together, which is inconvenient and cannot adapt well to the needs of rapid changes in industry applications.

Generally, there are many terminal configuration items. In addition, operators also need to maintain the NSSP on the terminal to ensure that the NSSP configured on the terminal is consistent with the contracted network slicing service. Therefore, the related configuration and maintenance are relatively complicated. At the same time, the terminal needs to store NSSP, which has higher requirements for low-cost mass IoT terminals, resulting in increased terminal costs.

At present, there is a gap between the definition of SST and the actual application requirements in the 3GPP TS 23.501 standard. After customizing the network slice type for different applications, the network slice (identified by S-NSSAI) and network slice instance (network slice instance) expected by vertical industries , NSI) relationship should be as shown in Figure 4 below, which is a schematic diagram of different network slice instances corresponding to S-NSSAI contracted by the terminal under different application usage scenarios. In fact, the identification of the network slice as a service (NSaaS) that the industry tenant wants to sign with the operator is S-NSSAI, and the NSI ID is the identification of the network slice instance that actually carries the communication session after the terminal initiates the communication session . In fact, industry tenants do not want to know this. For the sake of simplifying applications and reducing terminal costs, they only want a contracted S-NSSAI. The application uses the communication session initiated by the terminal in different scenarios to be selected by the network device to the appropriate network. Hosted on slice instance.

This application provides a method and system for selecting network slicing for application usage scenarios. When the industry tenant's application needs to use several different types of network slicing instances at the same time, within the scope of the network slicing service allowed by the contract with the operator, Part of the network slicing chooses to control the application server handed over to the industry tenant, and the application server determines the network slicing instance to use according to the application usage scenario. For example, when an industry tenant adds a new application scenario according to the application business needs, if the application's new usage scenario uses a network slice instance already deployed by the industry tenant or a network slice instance open to public use, such as the remote control excavator mentioned above The application adds a remote upgrade scenario. Use the public eMBB slicing instance. Using the technical solution of this application, industry tenants no longer need to negotiate with the operator to allocate a new application identifier and perform corresponding network configuration to choose the application usage scenario. Example of network slicing. The terminal can also not store and carry S-NSSAI, nor does it need to store and implement NSSP, which can further reduce the terminal resource occupation, simplify the terminal implementation, and reduce the terminal cost. This application is mainly a method and system for selecting network slices according to the applied scene tags. The terminal application (application, APP) sends corresponding scene tags (application scenario tags, AST) to the network equipment according to different usage scenarios. According to the signed S-NSSAI and AST, select the appropriate network slice instance for the PDU session requested to establish, to ensure that the communication connection of the application in this use scenario meets the required service level agreement (SLA). The service types (for example, video, audio, control, etc.) and service requirements (for example, performance requirements such as bandwidth and delay, reliability requirements, security isolation requirements, etc.) of applications in different use scenarios are often different. Industry tenants determine the scenario reference information according to the scenario business type and / or business requirements, which can include the functional requirements that the network needs to meet, the quality of service (QoS) capability requirements that the network needs to meet, or what they want to use in this scenario The identification of the network slice instance NSI ID, etc.

Among them, the scene label AST is an identification of different usage scenarios of the application, which can be used to distinguish the scenario when the application requests the terminal to establish a communication connection, and to determine the session established for the application usage scenario, and then send the usage scenario ’s data. The scene tag AST can be allocated and managed by the industry tenant's application according to its own business needs, and the corresponding scene reference information set by the industry tenant can be determined according to the AST.

For example, the application scenario label AST can be the number of the application usage scenario within the vertical industry, or it can be the Internet protocol (IP) address or uniformity of the vertical industry server that the terminal application needs to access in the current application scenario of the application The resource locator (uniform resource locator, URL) can also be the identifier of the sub-application included in the industry tenant's application, it can also be the number of different performance modes or different usage modes, or even identify the different data networks that the application needs to connect to The name of the private data network (Private Data Network Name, Private DNN) and so on. In addition, in order to facilitate carrying in the message, I hope that the AST has a specific length, you can also perform a hash operation of the specified length on the above number or URL, such as using the 128-bit MD5 algorithm to output the 16-byte result as the AST, not here Be specific.

Among them, the usage scenario of the application can be the working mode of the application client, for example, the client of the autonomous driving application can have a fully automatic driving mode, a semi-automatic driving mode, and a manual driving mode; the usage scenario of the application can also be the application server side used by the user The virtual scene or usage set during application service. For example, when using mobile games, the server can set home rest mode, multiplayer mode, two-player mode, or watch mode for the current user based on the user's operation selection. The application usage scenario can be defined and set by the application according to its specific service needs, and is not controlled by the operator's network. Each specific application can consider defining and setting usage scenarios from the following aspects:

1. Applications may have different types of communication services in different usage scenarios. For example, some scenarios require video communication, some scenarios require audio communication, and some scenarios require text message communication, etc.

2. Applications in different usage scenarios may require data communication to belong to different user groups, and there may be isolation requirements between user groups, such as different authorization levels and security requirements for smart meter remote meter reading and remote diagnostic verification operations. and many more.

3. The application may have different network performance and reliability requirements in different usage scenarios. For example, the vehicle automatic driving application has different network performance and reliability requirements in the fully automatic driving mode and the semi-automatic driving mode, and so on.

4. Applications may have different billing requirements in different usage scenarios. For example, some users want to use free webcast, some users want to use paid webcast with network acceleration, and so on.

5. The application in different usage scenarios may also produce the influence of other factors, or the combination of multiple factors among the above and other factors.

As shown in FIG. 5, it is a system architecture diagram applied in this application. According to the difference in logical function entities deployed by the operator's network equipment, specific embodiments of the present application are divided into two types of scenarios: network equipment deployment application data management function (application information management function, AIMF) entity and no AIMF entity deployment. In the scenario where AIMF is deployed, when the application usage scenario changes, the industry tenant ’s application server sets the application ’s scenario label and corresponding scenario reference information to the AIMF entity; in the scenario where the AIMF entity is not deployed, the application server applies the The scene label and the corresponding scene reference information are set to a policy control function (PCF) entity and / or NSSF entity.

The following further describes the technical solution of the present application by way of an embodiment. As shown in FIG. 6, it is a schematic diagram of an embodiment of a method for selecting a network handover in an embodiment of the present application, which may include:

601. The terminal obtains the scene label of the application.

Among them, the scene tag can be used to indicate the usage scene of the application, for details, please refer to the foregoing description, and no more details will be given here.

Exemplarily, the terminal receives a session establishment request message from an application client, and the session establishment request message includes a scene tag. Among them, the usage scenario can be the working mode of the application (fully automatic, semi-automatic, manual),

Different usage scenarios, requirements and impacts on the network correspond to different service types, and may have different requirements for network performance and reliability.

602. The terminal sends a scene label to the first network device.

Exemplarily, the terminal sends a session establishment request message carrying a scene tag to the core network through the wireless access network, and the scene tag is directly or indirectly sent to the first network device through a signaling message in the core network.

The first network device may be an NSSF entity, AIMF entity or PCF entity.

603. The first network device receives the first request message.

Wherein, the first request message includes the scene tag of the application.

In an example, when the first network device is an NSSF entity, the first network device receives the first request message, which may include: the first network device receives the network slice selection request message from the AMF entity of the access and mobility management function, the network The slice selection request message includes scene tags and application reference information.

The reference information of the application may include at least one of the identification of the application or the S-NSSAI corresponding to the application. It can be understood that the S-NSSAI corresponding to the application may be an S-NSSAI allocated by an industry tenant to order network slicing services from an operator, that is, a contracted S-NSSAI of the terminal.

In another example, when the first network device is an AIMF entity or a PCF entity, the first network device receives a scene information request from an NSSF entity. The scene information request may include a scene tag and an S-NSSAI corresponding to the application.

604. The first network device selects a network slice instance for the usage scenario according to the scenario label.

Among them, step 604 can be divided into the following two cases for specific description, as follows:

Case 1), the first network device is an NSSF entity.

The first network device selects a network slicing instance for the usage scenario according to the scenario label, which may include: the first network device obtains scenario reference information according to the scenario label; the first network device selects a network slicing instance for the usage scenario based on the scenario reference information.

Further, the first network device may obtain the scene reference information according to the scene label, and the following two optional implementation methods may be used:

Method 1: The first network device sends a second request message to the second network device, and the second request message includes the scene tag and application reference information; the second network device receives the second request message from the first network device, and the second request The message includes the application's scene label and application reference information. The scene label is used to indicate the usage scenario of the application; the second network device determines the scene reference information according to the scene label; The second response message is used to respond to the second request message, the second response message includes scene reference information; the first network device receives a second response message from the second network device, and the second response message includes scene reference information The second network device is an application information management function AIMF entity or a policy control function PCF entity.

Method 2: The first network device determines the scene reference information according to the scene label and the applied reference information.

The scenario reference information may include at least one of functional requirements of the usage scenario or QoS capability requirements of the usage scenario.

Further, according to the scenario reference information, the first network device may select the network slicing instance for the usage scenario by using the following two optional implementation methods:

Manner A. If the reference information of the application includes the S-NSSAI corresponding to the application, the first network device selects a network slice instance for the usage scenario according to the scenario reference information, which may include:

When the scenario reference information includes the functional requirements of the usage scenario, the first network device selects a network slice instance from the network slice instances corresponding to the S-NSSAI, and the network slice instance meets the functional requirements; or,

When the scenario reference information includes the QoS capability requirements of the usage scenario, the first network device selects a network slice instance from the network slice instances corresponding to the S-NSSAI, and the network slice instance meets the QoS capability requirements.

Manner B. If the reference information of the application includes the identification of the application, and the identification of the application corresponds to the default S-NSSAI, the first network device selects a network slice instance for the usage scenario according to the scenario reference information, which may include:

Determine the S-NSSAI corresponding to the identification of the application from the multiple contracted S-NSSAIs of the terminal as the default S-NSSAI, or use the terminal's unique contracted S-NSSAI as the default S-NSSAI.

When the scenario reference information includes the functional requirements of the usage scenario, the first network device selects a network slice instance from the network slice instances corresponding to the default S-NSSAI, and the network slice instance meets the functional requirements; or,

When the scenario reference information includes the QoS capability requirements of the usage scenario, the first network device selects a network slice instance from the network slice instances corresponding to the default S-NSSAI, and the network slice instance meets the QoS capability requirements.

Case 2). The first network device is an AIMF entity or a PCF entity.

The first network device receiving the first request message may include: the first network device receiving a scene information request from an NSSF entity, the scene information request including a scene tag and an S-NSSAI corresponding to the application;

The first network device selects a network slicing instance for the usage scenario according to the scenario label, which may include: the first network device selects a network slicing instance for the usage scenario based on the scenario label and S-NSSAI.

605. The first network device sends a first response message.

The first response message may include indication information used to indicate the network slice instance.

The indication information may be at least one of NSI ID, S-NSSAI or NRF address information.

Exemplarily, the first network device sending the first response message may include: the first network device sending a session establishment accept message to the terminal.

606. The terminal generates a mapping relationship between the scene label and the session.

Exemplarily, the mapping relationship between the scene label generated by the terminal and the session may be as shown in Table 1 below:

Table 1

607. The terminal receives a data interface call request from the application client, and the data interface call request includes a scene tag.

The terminal receives a data interface call request from the client application. The data interface call request may include a scene label. Exemplarily, the scene label is AST-2.

608. The terminal determines the session according to the scene label and the mapping relationship.

After receiving the data interface call request, the terminal may determine the session according to the scene label and the mapping relationship.

Exemplarily, the mapping relationship between the requested AST-2 sum scene label and the session is called through the data interface to determine the session PDU-Session-2.

609. The terminal sends the data of the usage scenario through the session.

Exemplarily, AST-2 is used to send application data identifying the usage scenario through Session PDU-Session-2.

In the embodiment of the present application, the first network device receives the first request message, and the first request message includes an application scene label, and the scene label is used to indicate the usage scenario of the application; the first network device selects a network for the usage scenario according to the scene label Slicing instance; the first network device sends a first response message, and the first response message includes indication information for indicating the network slicing instance. That is, the first network device may select a network slicing instance for the usage scenario of the application according to the application's scene label, instead of configuring a network slicing selection strategy on the terminal, thereby reducing the cost of the terminal and saving the terminal's system resources.

In the following, scenarios where AIMF is deployed and AIMF is not deployed in the system architecture diagram applied in the embodiments of the present application will be described separately.

1. Scenarios where AIMF entities are deployed in network equipment

Industry tenants order network slicing services from operators. Operators deploy multiple network slicing instances for industry tenants according to the business characteristics of the industry. The network functions in each network slicing instance are functional and performance-oriented according to the needs of different usage scenarios of terminal applications. For optimization, operators open the NSI IDs of these network slice instances and the SLA capability information they support to industry tenants. Operators can sign at least one S-NSSAI for industry tenants. The contracted S-NSSAI may be zero to multiple standard S-NSSAIs and / or customized S-NSSAIs. The operator can also select an S-NSSAI as the default S-NSSAI (default S-NSSAI) in the contract information. Operators do network slice selection configuration in NSSF, and can correspond the default S-NSSAI to multiple NSIs prepared for terminal applications, optionally, one of them can be set as the default selection NSI.

As shown in Figure 5 above, industry tenants (which can be application servers) use application function (application) (AF) entities to set application-specific application scenario information to AIMF entities through network open function (NEF) entities (AIMF entities can store the scene reference information of these applications by themselves, or they can store the scene reference information of the applications in a unified data storage (UDR)). The application-defined scenario reference information includes one or more items, each of which contains the application's scenario label AST and the SLA requirements associated with the application's usage scenario. The SLA requirements may include QoS support capability information, as well as specific functional requirements (optimization functions, such as dual connectivity) required by the network. Industry tenants also use AF entities to set QoS policies for application scenarios to PCF entities through NEF entities, where the QoS policies can use AST identification. When the industry tenant uses the AF entity to set the application scenario information, the operator's NEF entity will check that the industry tenant has been authorized by the operator, and the set SLA requirements are within the scope of the agreement between the two parties.

As shown in FIG. 7, which is a schematic diagram of an embodiment of a method for selecting a network slice in an embodiment of the present application, it may include:

701. The terminal obtains a scene label of the application, and the scene label is used to indicate a usage scenario of the application.

Exemplarily, before the terminal obtains the application's scene label, the terminal adds an application usage scenario. For example, after the remote control excavator application adds a remote expert fault diagnosis usage scenario, the terminal adds a corresponding scene label to the usage scenario AST, by upgrading the application program of the application client (App Client), the AST corresponding to this increased usage scenario and the AST corresponding to the original usage scenario are updated to the upgraded App Client together. Further, the App Client can use different ASTs as parameters in different usage scenarios to call the terminal's session establishment interface. It is understandable that the logic of which AST is used in what usage scenario can be implemented by the industry tenant's application program, for example, written in advance in the updated App Client program.

The terminal acquiring the scene label of the application may be that the application client calls the terminal's session establishment interface, that is, the terminal receives a session establishment request from the application client, and the session establishment request includes the scene label.

For the description of the scene label, please refer to the description in the previous text, which will not be repeated here.

702. The terminal sends the scene label to the AMF entity through the AN entity.

Exemplarily, after receiving the session interface call request from the App Client, the terminal sends a session establishment request message to the AMF entity through the AN entity, where the session establishment request message carries the AST corresponding to the newly added usage scenario.

Optionally, the session establishment request message may also carry S-NSSAI. It can be understood that the S-NSSAI is an S-NSSAI contracted by the operator for the terminal.

703. The AMF entity sends a network slice selection request message to the NSSF entity.

Exemplarily, after receiving the session establishment request message, the AMF entity sends a network slice selection request message to the NSSF entity, where the session establishment request message may carry the AST, and the network slice selection request message may carry the AST and application reference information.

The reference information of the application may include at least one of an identification of the application or a single network slice selection auxiliary information S-NSSAI corresponding to the application.

Optionally, when the session establishment request message received by the AMF entity does not carry any S-NSSAI, the AMF entity may take the default S-NSSAI from the S-NSSAI contracted by the user and carry it in the network slice selection request message Medium; when the session establishment request message received by the AMF entity carries S-NSSAI, the network slice selection request message may carry the S-NSSAI.

Optionally, before the NSSF entity receives the network slice selection request message, the AF entity may set the network slice instance selection rule of the application usage scenario of the application to the NSSF entity through the network open function (NEF) entity. The rule includes: AST , S-NSSAI and NSI ID mapping relationship. Among them, the operator's NEF entity can check whether the industry tenant is authorized by the operator, and the set S-NSSAI is signed by the operator for the industry tenant, and the set NSI ID is the network slice instance deployed by the operator for the industry tenant Logo. Exemplarily, when the session establishment request message carries the specific AST and the specific S-NSSAI, the NSSF entity may find the corresponding network slice instance identified by the NSI ID according to the specific AST and the specific S-NSSAI.

Accordingly, the NSSF entity stores the rule set by the AF entity. That is, the NSSF entity can store the rules for finding corresponding network slice instances according to the scene label of the application usage scenario and the S-NSSAI contracted by the user. Among them, the rule may be a set of rules for selecting network slice instances according to AST and S-NSSAI according to the business requirements of industry application usage scenarios. Each rule can include the AST of an application's usage scenario as an identifier, the user's contracted S-NSSAI, and the application's usage scenario requires the use of an operator's network slice instance identifier (network slice instance identifier, NSI ID) .

Further, when the network slice selection request message includes the scene label and S-NSSAI, the NSSF entity may select the corresponding network slice instance according to the scene label and S-NSSAI, and the above rules.

704. The NSSF entity sends a scene information request message to the AIMF entity.

The scene information request message may include a scene label and application reference information. For details, reference may be made to the related description in the foregoing embodiment, and details are described here again.

705. The AIMF entity determines the scene reference information according to the scene label and the applied reference information.

Exemplarily, the AIMF entity pre-stores the application scene label and corresponding scene reference information set by the industry tenant's application server. When the AIMF entity stores the application scenario tags and corresponding scenario reference information set by the industry tenants, it will also store the application reference information to distinguish different industry tenants or applications.

The reference information of the application may include at least one of the identification of the application or S-NSSAI.

Optionally, when the reference information of the application includes the identification of the application, the AIMF entity searches for the corresponding storage record according to the identification and AST of the application, and obtains the corresponding scene reference information.

Optionally, when the reference information of the application includes S-NSSAI, the AIMF entity searches corresponding storage records according to S-NSSAI and AST, and obtains corresponding scene reference information.

The scenario reference information may include, but is not limited to, functional requirements of application usage scenarios, and quality of service (QoS) capability requirements of usage scenarios. It can be understood that the functional requirements and QoS capability requirements of the application usage scenarios can be indexed by AST. Among them, the functional requirements of the usage scenario list the network functions that the network slice supporting the usage scenario should have, for example, requiring the SMF entity to enable the data caching function, the wireless node supporting dual connectivity, and so on. The QoS support capability of the usage scenario requires that the QoS parameter range that the network slice of the usage scenario should meet be listed.

Optionally, the AIMF entity can store the scenario label of the usage scenario and the S-NSSAI contracted by the user to find the corresponding network slice instance rule. The rule can be determined by the industry tenant according to the application scenario business requirements of the industry application according to AST and S- NSSAI is a set of rules for network slice instance selection. In each rule, the AST of an application usage scenario is used as the identifier, including the S-NSSAI contracted by the user, and the application scenario of the application requires the identification of the network slice instance deployed by the operator (network slice instance identifier, NSI ID) .

Further, when the scene information request message includes the scene label and the S-NSSAI, the AIMF entity may select the corresponding network slice instance according to the scene label and the identification of the S-NSSAI and the network slice instance.

Correspondingly, in step 706, the scene information response message carries the identifier of the network slice instance selected above. It should be noted that in this case, step 707 is not executed, and after step 706 is executed, step 708 is executed.

706. The AIMF entity sends a scene information response message to the NSSF entity.

The scene information response message includes scene reference information.

707. The NSSF entity selects a network slice instance for the usage scenario according to the scenario reference information.

Specifically, if the network slice selection request message carries S-NSSAI, and the S-NSSAI corresponds to multiple network slice instances, then the NSSF entity selects a network slice instance corresponding to the S-NSSAI from the network slice instance corresponding to the use scenario according to the scene reference information Network slicing examples of functional requirements and / or QoS support capability requirements.

It should be noted that when there are two or more network slicing instances that meet the demand, the NSSF entity can select the first selected network slicing instance, or it can select the network slicing instance whose load is less than the preset threshold or the load is the smallest , Or other determination methods, not specifically limited here.

708. The NSSF entity sends the network slice selection result to the AMF entity.

The network slice selection result may carry the NRF address in the selected network slice instance.

Optionally, the network slice selection result also carries the network slice instance identification NSI ID, or S-NSSAI.

709. The AMF entity sends a service discovery request message to the NRF entity.

The AMF can obtain the global NRF address shared by all network slices according to the previous network configuration, or can obtain the NRF unique to the selected network slice from step 708.

It can be understood that the NRF entity is the NRF entity corresponding to the selected network slice instance.

Among them, the service discovery request can be used to request an SMF entity within the specified network slice instance.

Among them, the service discovery request message may carry the S-NSSAI and the type of network function (ie, SMF entity), and may also carry the NSI ID.

710. The NRF entity sends a service discovery response message to the AMF entity.

Exemplarily, the NRF entity selects a suitable SMF entity to process the session establishment request message among the multiple SMF entities of the selected network slice instance, based on the business load, service range, etc., and the NRF entity sends a service discovery response to the AMF entity News.

The service discovery response message may carry the address of the SMF entity selected above.

711. The AMF entity forwards the session establishment request message to the selected SMF entity.

Exemplarily, the AMF entity forwards the received session establishment request message to the selected SMF entity. The session establishment request message may be a request message used to create a session management context, and the message may carry an AST.

712. The SMF entity sends a session establishment response message to the AMF entity.

Exemplarily, the SMF entity creates a session management context and sends a response message to the AMF entity to create the session management context.

713. The SMF entity and the PCF entity interact to establish a session strategy.

The SMF entity may carry the AST in the session policy establishment request message sent to the PCF entity.

Exemplarily, the PCF entity may obtain the application-specific QoS policy from the AF entity of the industry tenant. When the PCF entity obtains the QoS policy from the AF entity, it may carry the AST, and the AF entity will index the AST as suitable for the current application usage scenario. The QoS parameters are provided to the PCF entity, so that the PCF entity obtains the QoS policy of the specified application scenario according to the AST and passes it to the SMF entity in the response message.

It can be understood that the AF entity may set the QoS policy of the application usage scenario to the PCF entity through the NEF entity in advance, which includes a series of QoS parameter range rules set by the industry tenant that can satisfy the application scenario indexed by the AST. The PCF entity stores the QoS policy of the application scenario set by the AF entity, or stores it in the UDR entity, and the AF can also directly store the QoS policy of the application scenario in the UDR through NEF. During the session establishment phase, the PCF entity can index the QoS policies stored in itself or UDR according to the AST index, and then set the QoS parameters that meet the requirements of the application's usage scenario. The NEF entity of the operator will check that the industry tenant has been authorized by the operator, and the QoS policy set is within the SLA range agreed by both parties.

714. The SMF entity and the UPF entity establish an N4 control connection.

Exemplarily, the SMF entity selects the UPF entity and establishes an N4 control connection, and sends the QoS parameters of the application usage scenario to the UPF entity.

715. The SMF entity sends an N1N2 signaling transmission message to the AMF entity.

Among them, the N1N2 signaling transmission message may carry the user plane N3 tunnel address of the UPF entity, and QoS parameters for application usage scenarios.

716. The AMF entity sends a session establishment request message to the AN entity.

The session establishment request message may be an N2PDU session establishment request message. The N2PDU session establishment request message can be used to transfer the QoS parameters for the application scenario to the AN entity.

717. The AN entity interacts with the terminal to establish the access network resources required for the session, and sends a session establishment accept message to the terminal.

The session establishment acceptance message may be an N2PDU session establishment acceptance message.

718. The AN replies to the AMF entity with a session establishment response message.

The session establishment response message may be an N2PDU session establishment response message.

719. After receiving the session establishment acceptance message, the terminal returns an interface call success value to the application client.

In the embodiment of the present application, when the usage scenario of the application of the terminal changes, the terminal adds the scenario label of the usage scenario of the application to the session establishment interface provided by the application, and carries the scenario label of the usage scenario of the application in the session establishment request message .

The mobile network allows industry tenants to set application scene reference information identified by application scene tags in AIMF, and pre-set scene reference information identified by scene tags of application usage scenes on the PCF entity. The AMF entity uses the scene tag to request the NSSF entity to select a network slice instance suitable for the scene tag, and the SMF entity uses the scene tag to request the session QoS policy from the PCF entity. Through the above-mentioned means, the network device can select an appropriate network slicing instance and provide SLA protection for the application scenario of the application defined by the industry tenant independently.

Tenants can independently complete network-side adjustments through network capability opening, without requiring operators to allocate new Application IDs and new S-NSSAIs for new application usage scenarios, without reconfiguring network slice selection strategies for terminals, and without The configuration of the corresponding network slice selection on the NSSF needs to be adjusted and modified, and the network device can select an appropriate network slice instance for the usage scenario according to the scene label of the application usage scenario. Optionally, the terminal does not need to carry NSSAI when registering and initiating a session request, does not store and implement NSSP, and the terminal logic function is simplified, which is beneficial to reduce the cost of massive IoT terminals.

2. Scenarios where AIMF entities are not deployed in network equipment

When the operator does not deploy the AIMF entity, the industry tenant (which can be an application server) uses the AF entity to set the application-specific application scenario information to the PCF entity through the NEF entity (the PCF entity can store this information itself, or it can The application scene information is stored in the UDR, and can also be directly set into the UDR by the AF entity through the NEF entity). The application-defined scenario information includes one or more policy rules, each of which is indexed by an application scenario label AST. The policy rules indexed by the AST include two types: application scenario slice selection policy rules and application scenario QoS policy rules.

Among them, the slicing selection policy rule of the application scenario is based on the conditions required by the network function set by the industry tenant according to the SLA requirements of the application scenario (for example, SMF satisfies the data caching function, the wireless node supports dual connectivity, etc.) or the QoS support capability meets (That is, the parameter range of QoS that the network slice in this application scenario should meet). According to the conditions that the network function needs to meet and the conditions that the QoS support capability needs to meet, the NSSF can select a network slice instance that meets the requirements of the application scenario indexed by the AST among the network slices subscribed by the user.

The slicing selection policy rule of the application scenario is still: when the session establishment request carries a specific AST and a specific S-NSSAI, the network slice instance deployed by the operator identified by the NSI ID is selected.

The QoS policy rule of the application scenario is the range of QoS parameters set by the industry tenant to meet the application scenario of the AST index. The PCF can set the QoS parameter that meets the requirements of the application scenario according to the AST index during the session establishment phase.

As shown in FIG. 8, which is a schematic diagram of an embodiment of a method for selecting a network slice in an embodiment of the present application, it may include:

801. The terminal obtains a scene label of the application, and the scene label is used to indicate a usage scenario of the application.

802. The terminal sends the scene label to the AMF entity through the AN entity.

803. The AMF entity sends a network slice selection request message to the NSSF entity.

It should be noted that steps 801-803 are similar to steps 601-603 of the embodiment shown in FIG. 7 and will not be repeated here.

804. The NSSF entity sends a scene information request message to the PCF entity. The scene information request message includes the scene label and reference information of the application.

805. The PCF entity determines the scene reference information according to the scene label and the application reference information.

Exemplarily, the PCF entity pre-stores the application scene label and corresponding scene reference information set by the industry tenant's application server. When storing the application scenario label and corresponding scenario reference information set by the industry tenant, the PCF entity also stores the reference information of the application to distinguish different industry tenants or applications. It can be understood that the reference information of the application may include at least one of the identification of the application or S-NSSAI.

Optionally, when the reference information of the application includes the identification of the application, the PCF entity searches for the corresponding storage record according to the identification of the application and the AST, and obtains the corresponding scene reference information.

Optionally, when the reference information of the application includes S-NSSAI, the PCF entity searches corresponding storage records according to S-NSSAI and AST, and obtains corresponding scene reference information.

Optionally, the PCF entity can save the scenario label of the usage scenario and the S-NSSAI contracted by the user to find the corresponding network slice instance rule. The rule can be determined by the industry tenant according to the business application use scenario business requirements, according to AST and S- NSSAI is a set of rules for network slice instance selection. In each rule, the AST of an application usage scenario is used as the identifier, including the S-NSSAI contracted by the user, and the application scenario of the application requires the identification of the network slice instance deployed by the operator (network slice instance identifier, NSI ID) .

Further, when the scene information request message includes the scene label and the S-NSSAI, the PCF entity can directly select the corresponding network slice instance according to the scene label and the identification of the S-NSSAI and the network slice instance.

Correspondingly, in step 806, the scene information response message carries the identifier of the network slice instance selected above. It should be noted that in this case, step 807 is not executed, and after step 806 is executed, step 808 is executed.

806. The PCF entity sends a scene information response message to the NSSF entity.

The scene information response message includes scene reference information.

807. The NSSF entity selects a network slice instance for the usage scenario based on the scenario reference information.

808. The NSSF entity sends the network slice selection result to the AMF entity.

The NSSF entity sends a network slice selection response message to the AMF entity, and the network slice selection response message includes the network slice selection result.

809. The AMF entity sends a service discovery request message to the NRF entity.

810. The NRF entity sends a service discovery response message to the AMF entity.

811. The AMF entity forwards the session establishment request message to the selected SMF entity.

812. The SMF entity sends a session establishment response message to the AMF entity.

813. The SMF entity and the PCF entity interact to establish a session strategy.

814. The SMF entity and the UPF entity establish an N4 control connection.

815. The SMF entity sends an N1N2 signaling transmission message to the AMF entity, which carries the user plane N3 tunnel address of the UPF entity, and QoS parameters for the usage scenario of the application.

816. The AMF entity sends a session establishment request message to the access network AN.

817. The AN entity interacts with the terminal to establish access network resources required for the session, and sends a session establishment accept message to the terminal.

818. The AN replies to the AMF entity with a session establishment response message.

819. After receiving the session establishment acceptance message, the UE returns an interface call success value to the application client.

It should be noted that steps 807-818 are similar to steps 707-718 of the embodiment shown in FIG. 7 and will not be repeated here.

In the embodiment of the present application, the terminal adds the scene label of the application usage scenario to the session establishment interface provided by the application, and carries the scene label of the application usage scenario in the session establishment request message. The network equipment allows industry tenants to set scene reference information identified with scene tags on PCF entities in advance. The AMF entity requests the NSSF entity to select a network slice instance suitable for the usage scenario with the scene label of the application usage scenario, and the SMF entity requests the session QoS policy to the PCF entity with the application usage scenario label. Through the above-mentioned means, the network equipment can select an appropriate network slicing instance and provide SLA guarantee for application scenarios defined by industry tenants.

As shown in FIG. 9, which is a schematic diagram of an embodiment of a network device in an embodiment of the present application, it may include:

The receiving module 901 is configured to receive a first request message, where the first request message includes an application scene label, and the scene label is used to indicate a usage scenario of the application;

The processing module 902 is used to select a network slicing instance for the usage scene according to the scene label;

The sending module 903 is configured to send a first response message, and the first response message includes indication information used to indicate a network slice instance.

Optionally, in some embodiments of the present application,

The processing module 902 is specifically configured to obtain scene reference information according to the scene label; according to the scene reference information, select a network slice instance for the usage scene.

Optionally, in some embodiments of the present application, the first network device selects the functional NSSF entity for the network slice,

The receiving module 901 is specifically configured to receive a network slice selection request message from an AMF entity of an access and mobility management function. The network slice selection request message includes a scene label and application reference information.

Optionally, in some embodiments of the present application, the reference information of the application includes at least one of the identification of the application or the single network slice selection assistance information S-NSSAI corresponding to the application.

Optionally, in some embodiments of the present application,

The sending module 903 is further configured to send a second request message to the second network device, where the second request message includes scene tags and application reference information;

The receiving module 901 is also used to receive a second response message of a second request message from a second network device. The second response message includes scene reference information. The second network device is an application information management function AIMF entity or a policy control function PCF entity. ;or,

The processing module 902 is specifically configured to determine the scene reference information according to the scene label and the application reference information.

Optionally, in some embodiments of the present application, the scenario reference information includes at least one of functional requirements of the usage scenario or service quality QoS capability requirements of the usage scenario.

Optionally, in some embodiments of the present application, the reference information of the application includes the S-NSSAI corresponding to the application,

The processing module 902 is specifically configured to select a network slice instance from the network slice instances corresponding to the S-NSSAI when the scene reference information includes the functional requirements of the usage scene; the network slice instance meets the functional requirements; or,

The processing module 902 is specifically configured to select a network slice instance from the network slice instances corresponding to the S-NSSAI when the scene reference information includes the QoS capability requirements of the usage scene, and the network slice instance meets the QoS capability requirements.

Optionally, in some embodiments of the present application, the reference information of the application includes the identification of the application,

The processing module 902 is specifically configured to select a network slice instance from the network slice instances corresponding to the default S-NSSAI when the scene reference information includes the functional requirements of the usage scene; the network slice instance meets the functional requirements; or,

The processing module 902 is specifically configured to select a network slice instance from the network slice instances corresponding to the default S-NSSAI when the scene reference information includes usage scene QoS capability requirements, and the network slice instances meet the QoS capability requirements.

Optionally, in some embodiments of the present application,

The receiving module 901 is specifically used to receive a scene information request from an NSSF entity, and the scene information request includes a scene tag and an S-NSSAI corresponding to an application;

The processing module 902 is specifically used to select a network slicing instance for the usage scenario according to the scenario label and S-NSSAI.

As shown in FIG. 10A, it is a schematic diagram of an embodiment of a terminal in an embodiment of the present application, and may include:

The receiving module 1001 is used to obtain a scene label of an application, and the scene label is used to indicate a usage scenario of the application;

The sending module 1002 is configured to send the scene label to the first network device.

Optionally, in some embodiments of the present application,

The receiving module 1001 is specifically configured to receive a session establishment request message from an application client. The session establishment request message includes a scene tag.

Optionally, in some embodiments of the present application, as shown in FIG. 10B, it is a schematic diagram of another embodiment of the terminal in the embodiment of the present application, and may further include:

The receiving module 1001 is also used to receive a session establishment acceptance message sent by the first network device;

The processing module 1003 is configured to generate a mapping relationship between scene tags and conversations.

Optionally, in some embodiments of the present application,

The receiving module 1001 is also used to receive a data interface call request from an application client, and the data interface call request includes a scene label;

The processing module 1003 is specifically used to send data of the usage scenario through the session.

As shown in FIG. 11, it is a schematic diagram of another embodiment of a network device in an embodiment of this application, which may include:

The receiving module 1101 is configured to receive a second request message from the first network device, where the second request message includes an application scene label and application reference information, and the scene label is used to indicate a usage scenario of the application;

The processing module 1102 is used for determining scene reference information according to the scene label;

The sending module 1103 is configured to send a second response message to the first network device. The second response message is used to respond to the second request message. The second response message includes scene reference information.

Optionally, in some embodiments of the present application, the first network device is a network slice selection function NSSF entity; the second network device is a policy control function PCF entity or an application information management function AIMF entity.

Optionally, in some embodiments of the present application, the reference information of the application includes at least one of the application identification or the single network slice selection auxiliary information S-NSSAI corresponding to the application; the scenario reference information includes the functional requirements of the usage scenario Or at least one of the service quality QoS capability requirements of the usage scenario.

As shown in FIG. 12, it is a schematic diagram of an embodiment of a network device in an embodiment of the present application, which may include:

The memory 1201, the transceiver 1202 and the processor 1203, and the memory 1201, the transceiver 1202 and the processor 1203 are connected by a bus;

The transceiver 1202 is used to communicate with devices other than network equipment, and may perform the following steps:

Receiving a first request message, where the first request message includes an application scene tag, and the scene tag is used to indicate the usage scenario of the application; a first response message is sent, and the first response message includes indication information for indicating a network slice instance;

The memory 1201 is used to store operation instructions;

The processor 1203 is used to call operation instructions, and may perform the following steps:

According to the scene label, select the network slice instance for the usage scene.

Optionally, in some embodiments of the present application, the processor 1203 may perform the following steps:

Acquire scene reference information according to the scene label; select the network slice instance for the usage scene according to the scene reference information.

Optionally, in some embodiments of the present application, the first network device is a network slice selection function NSSF entity, and the transceiver 1202 may perform the following steps:

Receiving a network slice selection request message from an access and mobility management function AMF entity, the network slice selection request message including the scene label and reference information of the application.

Optionally, in some embodiments of the present application, the reference information of the application includes at least one of the identification of the application or the single network slice selection auxiliary information S-NSSAI corresponding to the application.

Optionally, in some embodiments of the present application,

The transceiver 1202 may perform the following steps:

Send a second request message to a second network device, where the second request message includes the scene tag and reference information of the application; receive a second response message from the second request message of the second network device , The second response message includes the scenario reference information, and the second network device is an application information management function AIMF entity or a policy control function PCF entity;

The processor 1203 may perform the following steps:

The scene reference information is determined according to the scene label and the reference information of the application.

Optionally, in some embodiments of the present application, the reference information of the application includes the S-NSSAI corresponding to the application, and the processor 1203 may perform the following steps:

When the scene reference information includes the functional requirements of the usage scenario, select the network slice instance from the network slice instances corresponding to the S-NSSAI, and the network slice instance meets the functional requirements; or,

Optionally, in some embodiments of the present application, the reference information of the application includes an identification of the application,

The processor 1203 may perform the following steps:

When the scenario reference information includes the functional requirements of the usage scenario, select the network slice instance from the network slice instances corresponding to the default S-NSSAI, and the network slice instance meets the functional requirements; or,

When the scenario reference information includes the QoS capability requirements of the usage scenario, the network slice instance is selected from the network slice instances corresponding to the default S-NSSAI, and the network slice instance meets the QoS capability requirements.

Optionally, in some embodiments of the present application,

The transceiver 1202 may perform the following steps:

Receiving a scene information request from an NSSF entity, the scene information request including the scene tag and the S-NSSAI corresponding to the application;

The processor 1203 may perform the following steps:

According to the scenario label and the S-NSSAI, select the network slice instance for the usage scenario.

As shown in FIG. 13, it is a schematic diagram of an embodiment of the terminal in the embodiment of the present application, and may include:

The memory 1301, the transceiver 1302 and the processor 1303, and the memory 1301, the transceiver 1302 and the processor 1303 are connected by a bus;

The transceiver 1302 is used to communicate with devices other than the terminal, and may perform the following steps:

Obtain a scene label of an application, where the scene label is used to indicate a usage scenario of the application; and send the scene label to a first network device.

The memory 1301 is used to store operation instructions;

The processor 1303 is used to call operation instructions, and can perform corresponding steps.

Optionally, in some embodiments of the present application,

The transceiver 1302 may perform the following steps:

Receiving a session establishment request message from an application client, the session establishment request message including the scene tag.

Optionally, in some embodiments of the present application,

The transceiver 1302 may perform the following steps:

Receiving a session establishment acceptance message sent by the first network device;

The processor 1303 may perform the following steps:

Generating a mapping relationship between the scene label and the session.

Optionally, in some embodiments of the present application,

The transceiver 1302 may perform the following steps:

Receiving a data interface call request from an application client, the data interface call request including the scene tag;

The processor 1303 may perform the following steps:

The data of the usage scenario is sent through the session.

As shown in FIG. 14, which is a schematic diagram of an embodiment of a network device in an embodiment of this application, it may include:

The memory 1401, the transceiver 1402 and the processor 1403, and the memory 1401, the transceiver 1402 and the processor 1403 are connected through a bus;

The transceiver 1402 is used to communicate with devices other than the terminal, and can perform the following steps:

Receiving a second request message from the first network device, the second request message including an application scene label and reference information of the application, the scene label used to indicate a usage scenario of the application; to the first The network device sends a second response message, where the second response message is used to respond to the second request message, and the second response message includes the scene reference information;

The memory 1401 is used to store operation instructions;

The processor 1403 is used to call operation instructions, and can perform the following steps:

According to the scene label, determine scene reference information.

Optionally, in some embodiments of the present application, the reference information of the application includes at least one of the identification of the application or the single network slice selection auxiliary information S-NSSAI corresponding to the application;

The scenario reference information includes at least one of functional requirements of the usage scenario or quality of service QoS capability requirements of the usage scenario.

Optionally, in some embodiments of the present application, a computer program product containing instructions is provided, which when run on a computer, causes the computer to execute the first network device as shown in any of FIGS. 6-8 above The method, the same or corresponding technical features can be cited in this embodiment.

Optionally, in some embodiments of the present application, a computer program product containing instructions is provided, which, when run on a computer, causes the computer to perform the method as shown in any one of the above FIGS. The same or corresponding technical features can be cited in this embodiment.

Optionally, in some embodiments of the present application, a computer program product containing instructions is provided, which when run on a computer, causes the computer to execute the second network device as shown in any of FIGS. 6-8 above The method, the same or corresponding technical features can be cited in this embodiment.

In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When computer program instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present invention are generated in whole or in part. The computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable devices. Computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, computer instructions can be transmitted from a website site, computer, server, or data center via wire (eg, Coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) to another website, computer, server or data center. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device including one or more available medium integrated servers, data centers, and the like. The available media may be magnetic media (eg, floppy disk, hard disk, magnetic tape), optical media (eg, DVD), or semiconductor media (eg, Solid State Disk (SSD)), and the like.

Those skilled in the art can clearly understand that for the convenience and conciseness of the description, the specific working process of the system, device and unit described above can refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a division of logical functions. In actual implementation, there may be other divisions, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

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

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit. The above integrated unit may be implemented in the form of hardware or software functional unit.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application essentially or part of the contribution to the existing technology or all or part of the technical solution can be embodied in the form of a software product, the computer software product is stored in a storage medium , Including several instructions to enable a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program code .

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, persons of ordinary skill in the art should understand that they can still The technical solutions described in the embodiments are modified, or some of the technical features are equivalently replaced; and these modifications or replacements do not deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

A method for selecting a network slice, characterized by including:

The first network device receives a first request message, where the first request message includes an application scene tag, and the scene tag is used to indicate a usage scene of the application;

The first network device selects a network slice instance for the usage scenario according to the scenario label;

The first network device sends a first response message, where the first response message includes indication information for indicating the network slice instance.
The method according to claim 1, wherein the first network device selecting a network slice instance for the usage scenario according to the scenario label includes:

The first network device obtains scene reference information according to the scene label;

The first network device selects the network slice instance for the usage scenario according to the scenario reference information.
The method according to claim 2, wherein the first network device is a network slice selection function NSSF entity, and the first network device receiving the first request message includes:

The first network device receives a network slice selection request message from an access and mobility management function AMF entity, where the network slice selection request message includes the scene tag and reference information of the application.
The method according to claim 3, wherein the reference information of the application includes at least one of an identification of the application or a single network slice selection auxiliary information S-NSSAI corresponding to the application.
The method according to claim 3 or 4, wherein the acquiring, by the first network device according to the scene label, scene reference information includes:

The first network device sends a second request message to a second network device, where the second request message includes the scene tag and reference information of the application; the first network device receives from the second network device A second response message of the second request message, the second response message includes the scenario reference information, and the second network device is an application information management function AIMF entity or a policy control function PCF entity; or,

The first network device determines the scene reference information according to the scene label and the reference information of the application.
The method according to any one of claims 2-5, wherein the scenario reference information includes at least one of functional requirements of the usage scenario or quality of service QoS capability requirements of the usage scenario.
The method according to claim 6, wherein the reference information of the application includes an S-NSSAI corresponding to the application, and the first network device selects the use scenario for the usage scenario according to the scenario reference information Examples of network slicing, including:

When the scenario reference information includes the functional requirements of the usage scenario, the first network device selects the network slice instance from the network slice instances corresponding to the S-NSSAI, and the network slice instance satisfies the Functional requirements; or,

When the scenario reference information includes the QoS capability requirements of the usage scenario, the first network device selects the network slice instance from the network slice instances corresponding to the S-NSSAI, and the network slice instance satisfies the QoS capability requirements.
The method according to claim 6, wherein the reference information of the application includes an identifier of the application, the application identifier corresponds to a default S-NSSAI, and the first network device according to the scenario reference information, Selecting the network slice instance for the usage scenario includes:

When the scenario reference information includes the functional requirements of the usage scenario, the first network device selects the network slice instance from the network slice instances corresponding to the default S-NSSAI, and the network slice instance satisfies the function Sexual needs; or,

When the scenario reference information includes the QoS capability requirements of the usage scenario, the first network device selects the network slice instance from the network slice instances corresponding to the default S-NSSAI, and the network slice instance satisfies the QoS Capacity needs.
The method according to claim 1 or 2, wherein the first network device is an AIMF entity or a PCF entity, and the first network device receiving the first request message includes:

The first network device receives a scene information request from an NSSF entity, where the scene information request includes the scene tag and the S-NSSAI corresponding to the application;

The first network device selecting the network slice instance for the usage scenario according to the scenario label includes:

The first network device selects the network slice instance for the usage scenario based on the scenario label and the S-NSSAI.
A method for selecting a network slice, characterized by including:

The terminal obtains a scene label of the application, where the scene label is used to indicate a usage scenario of the application;

The terminal sends the scene tag to the first network device.
The method according to claim 10, wherein the terminal acquiring the scene label of the application comprises:

The terminal receives a session establishment request message from an application client, and the session establishment request message includes the scene tag.
The method according to claim 11, wherein the method further comprises:

The terminal receives the session establishment accept message sent by the first network device;

The terminal generates a mapping relationship between the scene label and the session.
The method of claim 12, wherein the method further comprises:

The terminal receives a data interface call request from an application client, and the data interface call request includes the scene tag;

The terminal determines the session according to the scene label and the mapping relationship;

The terminal sends the data of the usage scenario through the session.
A method for selecting a network slice, characterized by including:

The second network device receives a second request message from the first network device, where the second request message includes an application scene label and reference information of the application, where the scene label is used to indicate a usage scenario of the application;

The second network device determines scene reference information according to the scene label;

The second network device sends a second response message to the first network device, where the second response message is used to respond to the second request message, and the second response message includes the scene reference information.
The method according to claim 14, wherein the first network device is a network slice selection function NSSF entity; and the second network device is a policy control function PCF entity or an application information management function AIMF entity.
The method according to claim 14 or 15, wherein the reference information of the application includes at least one of an identification of the application or a single network slice selection auxiliary information S-NSSAI corresponding to the application;

The scenario reference information includes at least one of functional requirements of the usage scenario or quality of service QoS capability requirements of the usage scenario.
A network device, characterized in that it includes:

A receiving module, configured to receive a first request message, where the first request message includes an application scene tag, and the scene tag is used to indicate a usage scene of the application;

A processing module, configured to select a network slice instance for the usage scenario according to the scenario label;

The sending module is configured to send a first response message, where the first response message includes indication information used to indicate the network slice instance.
The network device according to claim 17, characterized in that

The processing module is specifically configured to obtain scene reference information according to the scene label; and select the network slice instance for the usage scene according to the scene reference information.
The network device according to claim 18, wherein the first network device is a NSSF entity for network slice selection function,

The receiving module is specifically configured to receive a network slice selection request message from an access and mobility management function AMF entity, where the network slice selection request message includes the scene label and reference information of the application.
The network device according to claim 19, wherein the reference information of the application includes at least one of an identification of the application or single network slice selection assistance information S-NSSAI corresponding to the application.
The network device according to claim 19 or 20, characterized in that

The sending module is further configured to send a second request message to a second network device, where the second request message includes the scene tag and reference information of the application;

The receiving module is further configured to receive a second response message of the second request message from the second network device, the second response message includes the scene reference information, and the second network device is an application Information management function AIMF entity or policy control function PCF entity; or,

The processing module is specifically configured to determine the scene reference information according to the scene label and the reference information of the application.
The network device according to any one of claims 18 to 21, wherein the scenario reference information includes at least one of functional requirements of the usage scenario or quality of service QoS capability requirements of the usage scenario .
The network device according to claim 22, wherein the reference information of the application includes an S-NSSAI corresponding to the application,

The processing module is specifically configured to select the network slice instance from the network slice instances corresponding to the S-NSSAI when the scene reference information includes the functional requirements of the usage scene, and the network slice instance satisfies The functional requirement; or,

The processing module is specifically configured to select the network slice instance from the network slice instances corresponding to the S-NSSAI when the scene reference information includes the QoS capability requirements of the usage scene, and the network slice instance meets The QoS capability requirements.
The network device according to claim 22, wherein the reference information of the application includes an identification of the application, and the application identification corresponds to a default S-NSSAI,

The processing module is specifically configured to select the network slice instance from the network slice instance corresponding to the default S-NSSAI when the scene reference information includes the functional requirements of the usage scene, and the network slice instance satisfies all State functional requirements; or,

The processing module is specifically configured to select the network slice instance from the network slice instance corresponding to the default S-NSSAI when the scene reference information includes the QoS capability requirements of the usage scene, and the network slice instance meets Describe the QoS capability requirements.
The network device according to claim 22, characterized in that

The receiving module is specifically configured to receive a scene information request from an NSSF entity, where the scene information request includes the scene tag and the S-NSSAI corresponding to the application;

The processing module is specifically configured to select the network slice instance for the usage scenario based on the scenario label and the S-NSSAI.
A terminal is characterized by comprising:

The receiving module is used to obtain a scene label of an application, and the scene label is used to indicate a usage scenario of the application;

The sending module is configured to send the scene tag to the first network device.
The terminal according to claim 26, characterized in that

The receiving module is specifically configured to receive a session establishment request message from an application client, where the session establishment request message includes the scene tag.
The terminal according to claim 27, wherein the terminal further comprises:

The receiving module is further configured to receive a session establishment acceptance message sent by the first network device;

The processing module is configured to generate a mapping relationship between the scene label and the conversation.
The terminal according to claim 28, characterized in that

The receiving module is also used to receive a data interface call request from an application client, where the data interface call request includes the scene tag;

The processing module is specifically configured to send the data of the usage scenario through the session.
A network device, characterized in that it includes:

A receiving module, configured to receive a second request message from a first network device, where the second request message includes an application scene label and reference information of the application, where the scene label is used to indicate a usage scenario of the application;

A processing module, configured to determine scene reference information according to the scene label;

The sending module is configured to send a second response message to the first network device, where the second response message is used to respond to the second request message, and the second response message includes the scene reference information.
The network device according to claim 30, wherein the first network device is a network slice selection function NSSF entity; and the second network device is a policy control function PCF entity or an application information management function AIMF entity.
The network device according to claim 30 or 31, wherein the reference information of the application includes at least one of an identification of the application or single network slice selection assistance information S-NSSAI corresponding to the application;

The scenario reference information includes at least one of functional requirements of the usage scenario or quality of service QoS capability requirements of the usage scenario.
A network device characterized by a memory, a transceiver, and a processor, and the memory, the transceiver, and the processor are connected by a bus;

The transceiver is used to communicate with devices other than the network equipment;

The memory is used to store operation instructions;

The processor is configured to call the operation instruction and execute the method according to any one of claims 1-9 or any one of 14-16.
A terminal is characterized by a memory, a transceiver and a processor, and the memory, the transceiver and the processor are connected by a bus;

The transceiver is used to communicate with devices other than the terminal;

The memory is used to store operation instructions;

The processor is configured to call the operation instruction and execute the method according to any one of claims 10-13.
A computer-readable storage medium, including instructions, which when executed on a computer, causes the computer to execute any one of claims 1-9, or any one of 10-13, or any one of 14-16 Described method.