WO2020103523A1 - Procédé de sélection de tranche de réseau, dispositif de réseau et terminal - Google Patents

Procédé de sélection de tranche de réseau, dispositif de réseau et terminal

Info

Publication number
WO2020103523A1
WO2020103523A1 PCT/CN2019/104317 CN2019104317W WO2020103523A1 WO 2020103523 A1 WO2020103523 A1 WO 2020103523A1 CN 2019104317 W CN2019104317 W CN 2019104317W WO 2020103523 A1 WO2020103523 A1 WO 2020103523A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
scene
network device
network slice
network
Prior art date
Application number
PCT/CN2019/104317
Other languages
English (en)
Chinese (zh)
Inventor
李卓明
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2020103523A1 publication Critical patent/WO2020103523A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup

Definitions

  • the present application relates to the field of communication technology, and in particular, to a network slice selection method, network equipment, and terminal.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 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.
  • 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.
  • 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.
  • 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.
  • the reference information of the application includes the S-NSSAI corresponding to the application
  • the first network device selects the network slice instance for the usage scenario according to the scenario reference information, which may include :
  • 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,
  • 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.
  • 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.
  • 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.
  • 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.
  • the first network device is an AIMF entity or a PCF entity
  • 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.
  • the first network device 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the terminal 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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:
  • 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 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:
  • 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 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.
  • 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 .
  • 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.
  • 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;
  • FIG. 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.
  • FIG. 6 is a schematic diagram of an embodiment of a method for selecting a network slice in an embodiment of the present application
  • FIG. 7 is a schematic diagram of an embodiment of a method for selecting a network slice in an embodiment of this application.
  • FIG. 8 is a schematic diagram of an embodiment of a method for selecting a network slice in an embodiment of the present application.
  • FIG. 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.
  • FIG. 11 is a schematic diagram of another embodiment of a network device in an embodiment of this application.
  • FIG. 12 is a schematic diagram of an embodiment of a network device in an embodiment of this application.
  • FIG. 13 is a schematic diagram of an embodiment of a terminal in an embodiment of this application.
  • FIG. 14 is a schematic diagram of an embodiment of a network device in an embodiment of this application.
  • 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.
  • a 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).
  • NFV network function virtualization
  • SDN software-defined network
  • 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.
  • 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.
  • 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.
  • 3GPP has defined the identification and related definitions about network slicing.
  • 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 (NSI), the network slice instance is identified using a network slice instance identifier (NSI ID).
  • NSI network slice instance
  • NSSAI network slice selection assistance information
  • NSSAI may be composed of a group of S-NSSAI.
  • SST slice / service type
  • 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.
  • 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).
  • eMBB enhanced mobile broadband
  • URLLC ultra-low latency and ultra-high reliability communication
  • MIoT massive Internet of Things
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 3 a schematic diagram of a network slice selection mechanism defined by 3GPP.
  • the network slice selection mechanism is defined in 3GPP TS23.501.
  • the terminal is configured with an NSSP, and the NSSP may include one or more rules.
  • 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
  • B requests to establish a communication session the terminal uses S-NSSAI2 in the session establishment request message;
  • a default rule is set.
  • NSSAI1 initiates session establishment.
  • 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.
  • S-NSSAI1 for remote diagnostics to establish a communication session
  • S-NSSAI2 for remote control to establish a communication session
  • 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.
  • AMF access and mobility management function
  • AN access network
  • 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).
  • NSSF network slice selection function
  • 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).
  • SMF session management function
  • 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.
  • SMF session management function
  • 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.
  • UPF user plane function
  • 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.
  • AMF including S-NSSAI, and the tunnel address and quality of service (QoS) of the session user plane Parameters and other information.
  • QoS quality of service
  • 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".
  • eMBB enhanced mobile broadband
  • 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.
  • 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.
  • 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.
  • the identification of the network slice as a service (NSaaS) that the industry tenant wants to sign with the operator is S-NSSAI
  • the NSI ID is the identification of the network slice instance that actually carries the communication session after the terminal initiates the communication session .
  • 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.
  • 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.
  • 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.
  • 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).
  • SLA service level agreement
  • 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
  • QoS quality of service
  • 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.
  • 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
  • IP Internet protocol
  • 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.
  • 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.
  • 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:
  • 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.
  • 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.
  • the application may have different network performance and reliability requirements in different usage scenarios.
  • 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.
  • 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.
  • 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.
  • FIG. 5 it is a system architecture diagram applied in this application.
  • 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.
  • AIMF application information management function
  • 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.
  • PCF policy control function
  • 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:
  • the terminal obtains the scene label of the application.
  • 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.
  • the terminal receives a session establishment request message from an application client, and the session establishment request message includes a scene tag.
  • the usage scenario can be the working mode of the application (fully automatic, semi-automatic, manual),
  • the terminal sends a scene label to the first network device.
  • 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.
  • the first network device receives the first request message.
  • the first request message includes the scene tag of the application.
  • the first network device 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.
  • the first network device 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.
  • the first network device selects a network slice instance for the usage scenario according to the scenario label.
  • step 604 can be divided into the following two cases for specific description, as follows:
  • 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.
  • 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.
  • the first network device may select the network slicing instance for the usage scenario by using the following two optional implementation methods:
  • the first network device selects a network slice instance for the usage scenario according to the scenario reference information, which may include:
  • 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,
  • 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.
  • the first network device selects a network slice instance for the usage scenario according to the scenario reference information, which may include:
  • 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,
  • 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.
  • 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.
  • 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.
  • the first network device sending the first response message may include: the first network device sending a session establishment accept message to the terminal.
  • the terminal generates a mapping relationship between the scene label and the session.
  • mapping relationship between the scene label generated by the terminal and the session may be as shown in Table 1 below:
  • 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.
  • the scene label is AST-2.
  • the terminal determines the session according to the scene label and the mapping relationship.
  • the terminal may determine the session according to the scene label and the mapping relationship.
  • 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.
  • the terminal sends the data of the usage scenario through the session.
  • AST-2 is used to send application data identifying the usage scenario through Session PDU-Session-2.
  • 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.
  • 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.
  • AIMF application function
  • NEF network open function
  • 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.
  • 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.
  • FIG. 7 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:
  • the terminal obtains a scene label of the application, and the scene label is used to indicate a usage scenario of the application.
  • the terminal adds an application 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.
  • 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.
  • the terminal sends the scene label to the AMF entity through the AN entity.
  • the terminal 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.
  • the session establishment request message may also carry S-NSSAI.
  • S-NSSAI is an S-NSSAI contracted by the operator for the terminal.
  • the AMF entity sends a network slice selection request message to the NSSF entity.
  • the AMF entity 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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) .
  • the NSSF entity may select the corresponding network slice instance according to the scene label and S-NSSAI, and the above rules.
  • 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.
  • the AIMF entity determines the scene reference information according to the scene label and the applied reference information.
  • the AIMF entity pre-stores the application scene label and corresponding scene reference information set by the industry tenant's application server.
  • 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.
  • 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.
  • 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.
  • QoS quality of service
  • the functional requirements and QoS capability requirements of the application usage scenarios can be indexed by AST.
  • 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.
  • 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.
  • 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) .
  • 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.
  • 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.
  • the AIMF entity sends a scene information response message to the NSSF entity.
  • the scene information response message includes scene 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.
  • the NSSF entity selects a network slice instance for the usage scenario according to the scenario reference information.
  • 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.
  • 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.
  • 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.
  • the network slice selection result also carries the network slice instance identification NSI ID, or S-NSSAI.
  • 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.
  • the NRF entity is the NRF entity corresponding to the selected network slice instance.
  • the service discovery request can be used to request an SMF entity within the specified network slice instance.
  • 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.
  • the NRF entity sends a service discovery response message to the AMF entity.
  • 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.
  • the AMF entity forwards the session establishment request message to the selected SMF entity.
  • 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.
  • the SMF entity sends a session establishment response message to the AMF entity.
  • the SMF entity creates a session management context and sends a response message to the AMF entity to create the session management context.
  • 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.
  • the PCF entity may obtain the application-specific QoS policy from the AF entity of the industry tenant.
  • the PCF entity 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.
  • 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.
  • 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.
  • the SMF entity and the UPF entity establish an N4 control connection.
  • 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.
  • the SMF entity sends an N1N2 signaling transmission message to the AMF entity.
  • the N1N2 signaling transmission message may carry the user plane N3 tunnel address of the UPF entity, and QoS parameters for application usage scenarios.
  • 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.
  • 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.
  • 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.
  • the terminal After receiving the session establishment acceptance message, the terminal returns an interface call success value to the application client.
  • the terminal 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.
  • 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.
  • 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.
  • 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.
  • 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).
  • 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.
  • FIG. 8 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:
  • the terminal obtains a scene label of the application, and the scene label is used to indicate a usage scenario of the application.
  • the terminal sends the scene label to the AMF entity through the AN entity.
  • the AMF entity sends a network slice selection request message to the NSSF entity.
  • steps 801-803 are similar to steps 601-603 of the embodiment shown in FIG. 7 and will not be repeated here.
  • 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.
  • the PCF entity determines the scene reference information according to the scene label and the application reference information.
  • the PCF entity pre-stores the application scene label and corresponding scene reference information set by the industry tenant's application server.
  • 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.
  • 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.
  • the PCF 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.
  • QoS quality of service
  • the functional requirements and QoS capability requirements of the application usage scenarios can be indexed by AST.
  • 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.
  • 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.
  • 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) .
  • 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.
  • 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.
  • the PCF entity sends a scene information response message to the NSSF entity.
  • the scene information response message includes scene 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.
  • the NSSF entity selects a network slice instance for the usage scenario based on the scenario reference information.
  • 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.
  • the AMF entity sends a service discovery request message to the NRF entity.
  • the NRF entity sends a service discovery response message to the AMF entity.
  • the AMF entity forwards the session establishment request message to the selected SMF entity.
  • the SMF entity sends a session establishment response message to the AMF entity.
  • the SMF entity and the PCF entity interact to establish a session strategy.
  • the SMF entity and the UPF entity establish an N4 control connection.
  • 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.
  • the AMF entity sends a session establishment request message to the access network AN.
  • 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.
  • the AN replies to the AMF entity with a session establishment response message.
  • the UE After receiving the session establishment acceptance message, the UE returns an interface call success value to the application client.
  • steps 807-818 are similar to steps 707-718 of the embodiment shown in FIG. 7 and will not be repeated here.
  • 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.
  • the network equipment can select an appropriate network slicing instance and provide SLA guarantee for application scenarios defined by industry tenants.
  • FIG. 9 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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:
  • 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:
  • the processor 1203 may perform the following steps:
  • the first network device is a network slice selection function NSSF entity, and the transceiver 1202 may perform the following steps:
  • the network slice selection request message including the scene label and reference information of the 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 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.
  • 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.
  • the reference information of the application includes the S-NSSAI corresponding to the application, and the processor 1203 may perform the following steps:
  • the scene reference information includes the functional requirements of the usage scenario
  • the scene reference information includes the functional requirements of the usage scenario
  • the reference information of the application includes an identification of the application
  • the processor 1203 may perform the following steps:
  • the scenario reference information includes the functional 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.
  • the transceiver 1202 may perform the following steps:
  • the processor 1203 may perform the following steps:
  • 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:
  • the memory 1301 is used to store operation instructions
  • the processor 1303 is used to call operation instructions, and can perform corresponding steps.
  • the transceiver 1302 may perform the following steps:
  • the session establishment request message including the scene tag.
  • the transceiver 1302 may perform the following steps:
  • the processor 1303 may perform the following steps:
  • the transceiver 1302 may perform the following steps:
  • the processor 1303 may perform the following steps:
  • the data of the usage scenario is sent through the session.
  • FIG. 14 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:
  • the memory 1401 is used to store operation instructions
  • the processor 1403 is used to call operation instructions, and can perform the following steps:
  • 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.
  • 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.
  • a computer program product containing instructions 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.
  • a computer program product containing instructions 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.
  • a computer program product containing instructions 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.
  • the computer program product includes one or more computer instructions.
  • 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.
  • 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.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the units is only a division of logical functions.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Le mode de réalisation de la présente invention concerne un procédé de sélection de tranche de réseau, qui est utilisé pour qu'un premier dispositif de réseau sélectionne une instance de tranche de réseau selon une étiquette de scénario d'une application pour un scénario d'utilisation de l'application, répondant aux exigences d'applications pour utiliser différentes tranches de réseau dans différents scénarios d'utilisation. Le procédé de réalisation de la présente invention comprend les étapes suivantes : le premier dispositif de réseau reçoit un premier message de requête, le premier message de requête comprenant une étiquette de scénario d'une application pour indiquer un scénario d'utilisation de l'application ; le premier dispositif de réseau sélectionne une instance de tranche de réseau pour le scénario d'utilisation selon l'étiquette de scénario ; le premier dispositif de réseau envoie un premier message de réponse comprenant des informations d'indication pour indiquer l'instance de tranche de réseau.
PCT/CN2019/104317 2018-11-19 2019-09-04 Procédé de sélection de tranche de réseau, dispositif de réseau et terminal WO2020103523A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811377401.3 2018-11-19
CN201811377401.3A CN111200859A (zh) 2018-11-19 2018-11-19 一种网络切片的选择方法、网络设备及终端

Publications (1)

Publication Number Publication Date
WO2020103523A1 true WO2020103523A1 (fr) 2020-05-28

Family

ID=70745890

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/104317 WO2020103523A1 (fr) 2018-11-19 2019-09-04 Procédé de sélection de tranche de réseau, dispositif de réseau et terminal

Country Status (2)

Country Link
CN (1) CN111200859A (fr)
WO (1) WO2020103523A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11902109B2 (en) * 2020-04-24 2024-02-13 Samsung Electronics Co., Ltd. Method of network slice resource allocation and visualization

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113766607B (zh) * 2020-06-03 2023-03-31 华为技术有限公司 接入控制方法及相关设备
EP4173228A4 (fr) * 2020-06-28 2024-03-13 Qualcomm Inc Mise en évidence de découpage de réseau
CN113852996B (zh) * 2020-06-28 2024-01-05 中兴通讯股份有限公司 用户业务优先级调整方法、系统和存储介质
CN114050966B (zh) * 2020-07-22 2023-01-06 华为技术有限公司 业务模板的生成方法、装置、设备及存储介质
CN114389943B (zh) * 2020-10-22 2023-08-15 中移(成都)信息通信科技有限公司 一种网络配置方法、装置、设备及计算机存储介质
CN114466202B (zh) * 2020-11-06 2023-12-12 中移物联网有限公司 混合现实直播方法、装置、电子设备以及可读存储介质
CN114599046A (zh) * 2020-11-19 2022-06-07 中国移动通信有限公司研究院 业务标识的转换、信息配置方法、装置及通信设备
CN112615730B (zh) * 2020-11-23 2022-04-01 北京邮电大学 一种基于区块链网络切片代理的资源分配方法和装置
CN114640589A (zh) * 2020-11-30 2022-06-17 中国移动通信有限公司研究院 一种网络切片业务升级方法及相关设备
EP4240061A4 (fr) * 2020-12-04 2024-01-03 Guangdong Oppo Mobile Telecommunications Corp Ltd Procédé d'envoi et procédé de réception d'informations de qos, et appareils, dispositif et support de stockage
CN112770407A (zh) * 2020-12-31 2021-05-07 宇龙计算机通信科技(深圳)有限公司 一种建立数据承载的方法、装置、存储介质及电子设备
CN113347693B (zh) * 2021-05-26 2022-07-12 中国联合网络通信集团有限公司 切片参数配置方法、终端设备和基站
CN114978911B (zh) * 2022-05-20 2024-03-08 中国联合网络通信集团有限公司 网络切片的关联方法、设备主体、通信模组及终端设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017186092A1 (fr) * 2016-04-28 2017-11-02 中兴通讯股份有限公司 Procédé et appareil de sélection de tranche de réseau
CN108023757A (zh) * 2016-11-03 2018-05-11 华为技术有限公司 管理网络切片实例的方法、装置和系统
CN108132827A (zh) * 2016-11-30 2018-06-08 华为技术有限公司 一种网络切片资源映射方法、相关设备及系统
CN108632068A (zh) * 2017-03-22 2018-10-09 大唐移动通信设备有限公司 一种网络切片模板生成、网络切片模板应用方法和装置

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106341832B (zh) * 2015-07-07 2020-11-06 中国移动通信集团公司 网络切片的管理及选择方法、系统、基站、路由交换设备
CN107580360A (zh) * 2016-07-04 2018-01-12 中国移动通信有限公司研究院 一种网络切片选择的方法、设备及网络架构
CN112996087B (zh) * 2016-09-28 2023-03-10 华为技术有限公司 一种网络切片选择方法、终端设备及网络设备
CN107889169B (zh) * 2016-09-29 2021-09-03 华为技术有限公司 网络切片的建立方法和装置
CN108243483A (zh) * 2016-12-23 2018-07-03 大唐移动通信设备有限公司 一种通信方法、装置及系统
WO2018119592A1 (fr) * 2016-12-26 2018-07-05 华为技术有限公司 Procédé et appareil de détermination de tranche de réseau
CN106982458B (zh) * 2017-03-09 2019-12-17 华为技术有限公司 一种网络切片的选择方法及装置
US10736028B2 (en) * 2017-03-20 2020-08-04 Qualcomm Incorporated Network service configuration and selection using network slices
CN108632945B (zh) * 2017-03-20 2020-11-06 华为技术有限公司 一种网络切片选择方法、用户设备及网络设备
WO2018195877A1 (fr) * 2017-04-27 2018-11-01 华为技术有限公司 Procédé, dispositif et système de communication
WO2018205150A1 (fr) * 2017-05-09 2018-11-15 华为技术有限公司 Procédé et appareil de mise à jour de politique de sélection de tronçon de réseau
CN107483725A (zh) * 2017-07-31 2017-12-15 广东欧珀移动通信有限公司 资源配置方法及相关产品
CN108322350B (zh) * 2018-02-27 2021-06-01 创新先进技术有限公司 业务监控方法及装置和电子设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017186092A1 (fr) * 2016-04-28 2017-11-02 中兴通讯股份有限公司 Procédé et appareil de sélection de tranche de réseau
CN108023757A (zh) * 2016-11-03 2018-05-11 华为技术有限公司 管理网络切片实例的方法、装置和系统
CN108132827A (zh) * 2016-11-30 2018-06-08 华为技术有限公司 一种网络切片资源映射方法、相关设备及系统
CN108632068A (zh) * 2017-03-22 2018-10-09 大唐移动通信设备有限公司 一种网络切片模板生成、网络切片模板应用方法和装置

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11902109B2 (en) * 2020-04-24 2024-02-13 Samsung Electronics Co., Ltd. Method of network slice resource allocation and visualization

Also Published As

Publication number Publication date
CN111200859A (zh) 2020-05-26

Similar Documents

Publication Publication Date Title
WO2020103523A1 (fr) Procédé de sélection de tranche de réseau, dispositif de réseau et terminal
US11277306B2 (en) Sending information of a network repository function instance storing network function instance information
US11283684B2 (en) Network slice deployment method and apparatus
US10491376B1 (en) Systems, devices, and techniques for managing data sessions in a wireless network using a native blockchain platform
CN109314917B (zh) 网络切片选择策略更新方法、及装置
US11063831B2 (en) Network slice management method and apparatus
US20210344590A1 (en) Application Function In A Network And Control Thereof
EP3595244B1 (fr) Procédé, unité et système de gestion de tranche de réseau
EP4132213A1 (fr) Procédé de commande de transmission de service de diffusion en continu multimédia, terminal utilisateur, noeud de réseau, système, support d'enregistrement et dispositif électronique
WO2021037175A1 (fr) Procédé de gestion de tranche de réseau et dispositif associé
US11902891B2 (en) Apparatus and method for network slicing and slice management to support multi-slice services
US20230072956A1 (en) Slice access method, apparatus, and system
WO2022011883A1 (fr) Procédé et système d'accueil d'un réseau central multi-opérateur avec mec
WO2018137196A1 (fr) Procédé de gestion de découpage de réseau en tranches, et unité de gestion et système
EP4024956A1 (fr) Procédé, appareil et système de communication
US20220264440A1 (en) Network-slice control server, service server, and respective control methods thereby
WO2019091439A1 (fr) Procédé, dispositif et terminal de génération de tranches de réseau
WO2018152825A1 (fr) Procédé de gestion ainsi qu'unité et système de gestion
US20230156828A1 (en) Session establishment method and apparatus, system, and computer storage medium
CN114615154A (zh) 服务质量管理的方法及装置、通信系统
US20220394785A1 (en) System and Method of Managing PNF Connectivity in a Network Slice Instance
WO2021227600A1 (fr) Procédé de commande de tranche de réseau et appareil de communication
CN112954768B (zh) 通信方法、装置及系统
US20220369198A1 (en) System and method for processing enhanced route selection descriptors
CN114514764A (zh) 设备、方法和计算机程序

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19886095

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19886095

Country of ref document: EP

Kind code of ref document: A1