[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

WO2024109221A1 - 一种网络切片匹配方法和装置 - Google Patents

一种网络切片匹配方法和装置 Download PDF

Info

Publication number
WO2024109221A1
WO2024109221A1 PCT/CN2023/114807 CN2023114807W WO2024109221A1 WO 2024109221 A1 WO2024109221 A1 WO 2024109221A1 CN 2023114807 W CN2023114807 W CN 2023114807W WO 2024109221 A1 WO2024109221 A1 WO 2024109221A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
network slice
application
network
nssai
Prior art date
Application number
PCT/CN2023/114807
Other languages
English (en)
French (fr)
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 WO2024109221A1 publication Critical patent/WO2024109221A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/09—Management thereof
    • H04W28/0925—Management thereof using policies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/09—Management thereof
    • H04W28/0958—Management thereof based on metrics or performance parameters
    • H04W28/0967—Quality of Service [QoS] parameters
    • H04W28/0975—Quality of Service [QoS] parameters for reducing delays
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
    • 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 communications, and in particular to a network slice matching method and device.
  • the 3rd generation partnership project (3GPP) proposed the network slice technology, which can abstractly divide a physical network into multiple network slices, each of which constitutes an end-to-end logical network.
  • Network slices are logically isolated from each other, and different network slices can meet different business requirements. For example, for a service that requires low latency, a network slice that supports low latency can be used to execute the service.
  • the overall latency of the service may still increase due to other reasons (for example, the terminal's internal processing latency for the service is large), which does not meet service requirements and results in a poor user experience.
  • the embodiments of the present application provide a network slice matching method and device that can meet different business requirements (for example, low-latency business requirements, high-reliability business requirements, etc.) and can improve user experience.
  • different business requirements for example, low-latency business requirements, high-reliability business requirements, etc.
  • an embodiment of the present application provides a network slice matching method, including: a terminal device obtains relevant information of an application; the terminal device matches the relevant information of the application with at least one routing selection strategy URSP rule, the at least one URSP rule includes a first URSP rule, the first URSP rule includes a first network slice identifier, and the first network slice identifier displays or implicitly indicates a data processing level of the terminal device; if the first URSP rule matches the relevant information of the application, the data flow of the application is processed according to the data processing level indicated by the first network slice identifier.
  • the terminal device can match the relevant information of the application with at least one URSP rule. If the first URSP rule matches the relevant information of the application, the data stream of the application can be processed according to the data processing level indicated by the first network slice identifier in the first URSP rule. In this way, the terminal device can use the network slice corresponding to the first network slice identifier to transmit the data stream of the application, and at the same time process the data stream of the application based on the data processing level indicated by the first network slice identifier, that is, the transmission and processing performance of the service data can be jointly guaranteed by the data processing level of the network slice and the terminal device, which can meet the service requirements of different services.
  • the relevant information of the application includes a first network slice identifier. That is, the relevant information of the application may include network slice information that the application wants to use, such as the first network slice identifier.
  • the first URSP rule matches the relevant information of the application, that is, the first network slice identifier included in the first URSP rule is the same as the first network slice identifier in the relevant information of the application.
  • the relevant information of the application includes first information, and the first information is used to indicate a first network slice identifier. That is, the first information has a mapping relationship with the network slice information that the application wants to use.
  • the first URSP rule matches the relevant information of the application, that is, the first network slice identifier included in the first URSP rule is the same as the first network slice identifier indicated by the first information in the relevant information of the application.
  • the first URSP rule includes a first network slice identifier, including: the first URSP rule includes a first routing descriptor RSD, and the first RSD includes a first network slice identifier.
  • the first URSP rule matches the relevant information of the application, that is, the first network slice identifier in the first RSD in the first URSP rule is the same as the first network slice identifier in the relevant information of the application.
  • the method further includes: the terminal device determines a protocol data unit PDU session corresponding to the application according to the first URSP rule.
  • the first URSP rule may include parameters such as S-NSSAI, DNN, and SSCmode, and the PDU session corresponding to the application may refer to a PDU session that supports the above parameters in the first URSP rule.
  • the first network slice identifier displays and indicates the data processing level of the terminal device, including: the first network slice identifier includes first indication information, and the first indication information is used to indicate the data processing level of the terminal device; wherein the first indication information includes multiple values, each of the multiple values corresponds to a data processing level, and different values correspond to different data processing levels.
  • the data processing level of the terminal device can be determined according to the first indication information in the first network slice identifier, and the terminal device can use the network slice corresponding to the first network slice identifier to transmit the data stream of the application, and at the same time process the data stream of the application based on the data processing level indicated by the first network slice identifier, that is, the transmission and processing performance of the service data can be jointly guaranteed by the data processing level of the network slice and the terminal device, and the service requirements of different services can be met.
  • the first network slice identifier displays an indication of the data processing level of the terminal device, including: the first network slice identifier includes second indication information, the second indication information is used to indicate the data processing level of the terminal device, and the data processing level of the terminal device corresponds to the network slice type or network slice priority corresponding to the first network slice identifier.
  • the type of the first network slice indicated by the first network slice identifier is a low-latency slice
  • the second indication information can indicate that the data processing level of the terminal device is a low-latency processing level.
  • the low-latency processing level refers to the priority processing of service data within the terminal device, such as priority scheduling, priority queuing, queue-jumping and early transmission, and priority transmission.
  • the processing level of the service within the terminal device is a low-latency processing level, which can guarantee the service requirements of the service (for example, low latency). Avoiding the problem of poor service experience caused by low network slicing latency and high internal processing latency of the terminal device can give full play to the advantages of low-latency network slicing and meet service requirements.
  • the first network slice identifier includes a slice service type SST and a slice distinguishing symbol SD
  • the SST or SD includes the first indication information or the second indication information.
  • the data processing level of the terminal device includes at least one of a processing priority, a processing delay level, a processing rate level, a processing security level, a processing reliability level, and a processing bandwidth level.
  • the method before the terminal device obtains the relevant information of the application, the method further includes: the terminal device sends a registration request message to the first network device, the registration request message carries the first network slice identifier; the terminal device receives a registration acceptance message from the first network device, the registration acceptance message includes information about the slices allowed to be accessed.
  • the registration acceptance message may include an allowed NSSAI (Allowed NSSAI), and the Allowed NSSAI indicates the S-NSSAI allowed by the network in the NSSAI requested by the terminal device.
  • the method further includes: the terminal device sends a PDU session request message to an access and mobility management function network element AMF network element, and the PDU session request message includes a first network slice identifier.
  • the terminal device can initiate the establishment of a PDU session supporting the first network slice identifier through the PDU session request message so as to associate the application with the established PDU session.
  • the application-related information further includes an identification of the application
  • the first URSP rule further includes a traffic descriptor, and the traffic descriptor matches the identification of the application.
  • the present application provides a computer program product, which, when executed on a computer, enables the computer to execute the method described in any one of the above aspects and any one of its possible designs.
  • the present application provides a computer-readable storage medium, the computer-readable storage medium comprising computer instructions.
  • a terminal device such as a mobile phone
  • the terminal device executes the method described in the first aspect and any possible implementation thereof.
  • an embodiment of the present application provides a communication device, including a processor, the processor and a memory are coupled, the memory stores program instructions, and when the program instructions stored in the memory are executed by the processor, the device implements the method described in any of the above aspects and any possible design methods thereof.
  • the device may be a terminal device; or may be a component of a terminal device, such as a chip.
  • the present application provides a chip system, which includes one or more interface circuits and one or more processors.
  • the interface circuits and processors are interconnected via lines.
  • the chip system can be applied to a terminal device including a communication module and a memory.
  • the interface circuit is used to receive a signal from the memory of the first terminal device and send the received signal to the processor, where the signal includes a computer instruction stored in the memory.
  • the terminal device can execute the method described in any of the above aspects and any possible design thereof.
  • beneficial effects that can be achieved by the computer program product described in the second aspect, the computer-readable storage medium described in the third aspect, the communication device described in the fourth aspect, and the chip system described in the fifth aspect provided above can refer to the beneficial effects in the first aspect and any possible design method thereof, and will not be repeated here.
  • FIG1 is a schematic diagram of the composition structure of an S-NSSAI provided in an embodiment of the present application.
  • FIG2 is a schematic diagram of the composition structure of a URSP provided in an embodiment of the present application.
  • FIG3 is a schematic diagram of a system architecture provided in an embodiment of the present application.
  • FIG4 is a schematic diagram of the hardware structure of a terminal device provided in an embodiment of the present application.
  • FIG5 is a schematic diagram of a method flow chart provided in an embodiment of the present application.
  • FIG6 is a schematic diagram of the composition structure of another URSP provided in an embodiment of the present application.
  • FIG7 is a schematic diagram of the composition structure of another S-NSSAI provided in an embodiment of the present application.
  • FIG8 is a schematic diagram of matching a URSP rule provided in an embodiment of the present application.
  • FIG9 is a schematic diagram of matching a URSP rule provided in an embodiment of the present application.
  • FIG10 is a schematic diagram of the structure of a chip system provided in an embodiment of the present application.
  • a physical network can be abstractly divided into multiple network slices, each of which can form an end-to-end logical network.
  • Network slices are logically isolated from each other and do not affect each other.
  • network slices can be divided into multiple types, such as but not limited to enhanced mobile broadband (eMBB), massive machine type connection (mMTC), and ultra reliability and low latency connection (ultra reliability and low latency connection, uRLLC).
  • eMBB enhanced mobile broadband
  • mMTC massive machine type connection
  • uRLLC ultra reliability and low latency connection
  • the network characteristics of different types of network slices are different.
  • the network slice of eMBB is required to support large bandwidth and low latency services
  • the network slice of mMTC is required to support massive access and small bandwidth
  • the slice of uRLLC is required to have high reliability and low latency.
  • operators can provide "exclusive" networks for users with different business needs, ensure high-quality service levels, and meet differentiated business needs; users can also use more powerful application products, further stimulating the development of new industry applications, and achieving the goal of improving the efficiency of network resource utilization, optimizing operator network construction investment, and building a flexible and agile 5G network.
  • S-NSSAI Single network slice selection assistance information
  • the composition structure of an S-NSSAI may include a slice service type (SST) and a slice differentiator (SD).
  • SST refers to the expected network slice behavior in terms of functions and services.
  • SD is optional information that supplements the slice/service type to distinguish multiple network slices of the same slice/service type.
  • SST may include 8 bits and SD may include 24 bits.
  • NSSAI Network slice selection assistance information
  • PDU Packet Data Unit
  • the 5G network transmits the data sent and received between the terminal device (for example, user equipment (UE)) and the external network in the form of data packets. These user data packets are usually called PDU.
  • UE user equipment
  • PDU session is a session service that realizes PDU connectivity between UE and data network (DN) and is identified by PDU session ID.
  • URSP User route selection policy
  • SLA service level agreement
  • PLMN public land mobile network
  • the entire network does not necessarily support the same set of network slices.
  • Operators can divide different sets of slices based on regions or even single-point base stations. In this way, networks in different regions may correspond to different slices. Therefore, in non-roaming scenarios, users may only be able to access the required slices through some areas in the home network, or, in roaming scenarios, only be able to access the required slices through some areas in some visited networks.
  • URSP is defined in the standard to solve the routing problem of users. It is mainly used to determine the PDU session parameters required by different applications (APP) or services, such as network slicing, data network name (DNN), session service continuity mode (SSC mode), etc.
  • APP applications
  • DNN data network name
  • SSC mode session service continuity mode
  • the terminal can determine the corresponding PDU session parameters according to the network requirements of the APP or service.
  • a PDU session is established based on the parameters. Afterwards, the data of the APP or service is transmitted through the established session.
  • the URSP may include a traffic descriptor (TD) and one or more route selection descriptors (RSD).
  • TD traffic descriptor
  • RSD route selection descriptors
  • the URSP may also include other parameters, which are not limited in this application.
  • the traffic descriptor is used to match the service information (application ID or flow ID or service ID, etc.), and distinguish different services by application ID or other type of ID.
  • the terminal modem can match the application ID (APP ID) with the traffic descriptors in each URSP rule according to the priority of one or more URSP rules from high to low.
  • APP ID application ID
  • the PDU session for transmitting the traffic of the application is determined according to the RSD corresponding to the traffic descriptor (that is, the RSD in the URSP rule corresponding to the traffic descriptor).
  • RSD includes parameters such as DNN, S-NSSAI, and SSCmode.
  • the PDU session for transmitting the traffic of the application is a PDU session that supports the DNN, S-NSSAI, SSCmode and other parameters in the corresponding RSD (RSD corresponding to the traffic descriptor matching the application).
  • the PDU session for transmitting the traffic of the application can be determined based on the RSD corresponding to the matching traffic descriptor.
  • URSP matching When the UE determines that a specific service/application needs to be initiated, the service/application to be initiated is first matched with the traffic descriptor in the URSP rule according to the priority order of the URSP rule.
  • the UE also needs to determine the slice S-NSSAI required for the service based on the current RSD of the URSP rule, and determine whether the slice S-NSSAI belongs to the Allowed NSSAI of the current network. Specifically, in a roaming scenario, the terminal needs to determine whether the slice S-NSSAI belongs to the current Allowed NSSAI of the visited network. In a non-roaming scenario, the terminal needs to determine whether the slice S-NSSAI is within the current Allowed NSSAI of the home network.
  • the UE will continue to match subsequent URSP rules or subsequent RSDs based on the URSP priority/RSD priority until it is determined that the slice S-NSSAI allowed for the service appears in the Allowed NSSAI and the slice S-NSSAI is accepted by the network side.
  • cloud gaming can be based on real-time audio and video streaming technology, with the server sending real-time audio and video streams to the client, the client sending control instruction streams to the server, and the server applying the received control instructions to the game.
  • Cloud gaming can include, for example, action, fighting, multiplayer online battle arena (MOBA), first-person shooter, racing and other games.
  • Cloud gaming has high requirements for operation response delay, high bandwidth, and strict jitter. That is, the business requirements of cloud gaming are: low latency, high bandwidth, and no (small) jitter. Therefore, network slices that support low latency, high bandwidth, and no (small) jitter can be matched for cloud gaming to meet the business requirements of cloud gaming as much as possible.
  • the network loop of cloud gaming involves server-side game rendering, audio and video encoding, network transmission, client-side audio and video decoding and rendering, etc., all of which have a certain degree of latency.
  • server-side game rendering, audio and video encoding, network transmission, client-side audio and video decoding and rendering, etc. all of which have a certain degree of latency.
  • it can only reduce the latency in the network transmission process, but it is difficult to reduce the latency of other processes (for example, client-side audio and video decoding and rendering), making it difficult to ensure low latency of cloud gaming end-to-end.
  • the latency of network slice A is low latency 20ms, and the latency of network slice B is medium latency 50ms; the latency of terminal internal processing priority C is high latency 100ms, and the latency of terminal internal processing priority D is low latency 15ms.
  • an embodiment of the present application provides a network slice matching method, which can better meet different business requirements (for example, low-latency business requirements, high-reliability business requirements, etc.) and improve user experience.
  • the network slice matching method provided in the embodiment of the present application is applied to a communication system that uses network slices for communication, such as a 5G system, or a subsequent evolution system or other system.
  • the communication system includes: authentication server function (AUSF), unified data management (UDM), user data repository (UDR), core access and mobility management function (AMF), session management function (SMF), policy control function (PCF), application function (AF)/network exposure function (NEF), user plane function (UPF), access network (AN) and other network elements, as well as DN and UE.
  • AUSF authentication server function
  • UDM unified data management
  • UDR user data repository
  • AMF core access and mobility management function
  • SMF session management function
  • PCF policy control function
  • AF application function
  • NEF network exposure function
  • UPF user plane function
  • AN access network
  • AN access network
  • AN access network
  • AN access network
  • AN includes wired access network and radio access network (RAN).
  • RAN may include next generation NodeB (gNB).
  • the UE accesses the AN through wireless or wired methods.
  • the wireless method can be, for example, access through wireless fidelity (WiFi), and can also access the AN through a cellular network (such as E-UTRA, NR, etc.).
  • WiFi wireless fidelity
  • a cellular network such as E-UTRA, NR, etc.
  • the UE communicates with the AMF through N1; the AN communicates with the UPF through N3, and the AN communicates with the AMF through N2; the UPF communicates with the SMF through N4, and the UPF communicates with the DN through N6; the AMF communicates with the UDM through N8; the SMF communicates with the AMF through N11, the SMF communicates with the UDM through N10, and the SMF communicates with the PCF through N7; the AMF communicates with the AUSF through N12, and the AUSF communicates with the UDM through N13.
  • the AF communicates with the PCF through N5.
  • the UDM communicates with the UDR through N35.
  • the UDM communicates with the AF/NEF through N52.
  • the UDR communicates with the PCF through N36.
  • the AMF communicates with the PCF through N15.
  • AF/NEF refers to the interaction between the AF and the core network element via the NEF.
  • AF Mainly transmits the requirements of the application side to the network side, such as QoS requirements or user status event subscriptions.
  • AF can be a third-party functional entity or an application service deployed by an operator, such as IMS voice call service.
  • the application functional entity of a third-party application when it interacts with the core network, it can also be authorized by NEF.
  • the third-party AF sends a request message to NEF, and NEF determines whether the AF is allowed to send the request message. If the verification is successful, it will forward the request message to the corresponding PCF or UDM.
  • UDM Mainly responsible for managing contract data, user access authorization and other functions.
  • UDR Mainly responsible for the storage and access functions of contract data, policy data, application data and other types of data.
  • UDR can also add the corresponding S-NSSAI to the user's Subscribed NSSAI, and at the same time increase the contract values such as bandwidth, QoS guarantee, etc. allowed for the user under the SNSSAI.
  • PCF Mainly responsible for policy control functions such as billing for session and business flow levels, quality of service (QoS) bandwidth guarantee and mobility management, UE policy decision-making, etc.
  • QoS quality of service
  • SMF Session Management Function
  • AM PCF i.e. PCF for access and mobility control
  • SM PCF i.e. PCF for session management
  • AM PCF and SM PCF may not be the same PCF entity.
  • SMF Mainly responsible for session management, execution of control policies issued by PCF, selection of UPF, allocation of UE Internet protocol (IP) addresses, etc.
  • AMF Mainly performs functions such as mobility management and access authentication/authorization. In addition, it is also responsible for transmitting user policies between UE and PCF.
  • UPF As the interface with the data network, UPF completes functions such as user plane data forwarding, session/flow-level billing statistics, and bandwidth limitation.
  • AN corresponds to different access networks, such as wired access, wireless base station access and other methods.
  • N7 The interface between PCF and SMF, used to deliver PDU session granularity and service data flow granularity control strategy.
  • N15 The interface between PCF and AMF, used to issue UE policies and access control related policies.
  • N5 The interface between AF and PCF, used for issuing application service requests and reporting network events.
  • N4 The interface between SMF and UPF is used to transmit information between the control plane and the user plane, including the control of the forwarding rules, QoS control rules, traffic statistics rules, etc. for the user plane and the reporting of information on the user plane.
  • N11 The interface between SMF and AMF, used to transfer PDU session tunnel information between AN and UPF, control messages sent to UE, radio resource control information sent to AN, etc.
  • N2 The interface between AMF and RAN, used to transmit radio bearer control information from the core network side to AN.
  • N1 The interface between AMF and UE, access-independent, used to deliver QoS control rules to UE.
  • N8 The interface between AMF and UDM is used for AMF to obtain access and mobility management-related subscription data and authentication data from UDM, and for AMF to register UE's current mobility management-related information with UDM.
  • N9 used for user plane data forwarding between UPFs.
  • N10 The interface between SMF and UDM, used by SMF to obtain session management-related contract data from UDM, and for SMF to register UE current session-related information with UDM.
  • N35 Interface between UDM and UDR, used by UDM to obtain user contract data information from UDR.
  • N36 Interface between PCF and UDR, used by PCF to obtain policy-related contract data and application data-related information from UDR.
  • the names of the network elements and the names of the interfaces between the network elements in FIG3 are only examples.
  • the names of the network elements or the interfaces between the network elements may be other names, or the network elements may also be referred to as entities, which is not specifically limited in the embodiments of the present application.
  • All or part of the network elements in FIG3 may be physical entity network elements or virtualized network elements, which is not limited here.
  • the architecture may also include other network elements, such as operation administration management (OAM) network elements, network slice selection function (NSSF), network Network repository function (NRF), etc.
  • OAM operation administration management
  • NSSF network slice selection function
  • NRF network Network repository function
  • the 5G communication system shown in FIG3 includes a system in a non-roaming scenario and a system in a roaming scenario.
  • the system in each scenario can be a system based on a service-oriented interface or a system based on a reference point.
  • the specific description based on the service-oriented interface and based on the reference point can be referred to the prior art, which will not be repeated here.
  • the network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
  • the terminal device 100 may be a first electronic device.
  • the terminal device 100 may include a processor 410, an external memory interface 420, an internal memory 421, a universal serial bus (USB) interface 430, a charging management module 440, a power management module 441, a battery 442, an antenna 1, an antenna 2, a mobile communication module 450, a wireless communication module 460, an audio module 470, a speaker 470A, a receiver 470B, a microphone 470C, an earphone interface 470D, a sensor module 480, a button 490, a motor 491, an indicator 492, a camera 493, a display screen 494, and a subscriber identification module (SIM) card interface 495, etc.
  • SIM subscriber identification module
  • the sensor module 480 may include a pressure sensor 480A, a gyroscope sensor 480B, an air pressure sensor 480C, a magnetic sensor 480D, an acceleration sensor 480E, a distance sensor 480F, a proximity light sensor 480G, a fingerprint sensor 480H, a temperature sensor 480J, a touch sensor 480K, an ambient light sensor 480L, a bone conduction sensor 480M, etc.
  • the processor 410 may include one or more processing units, for example, the processor 410 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and/or a neural-network processing unit (NPU), etc.
  • AP application processor
  • GPU graphics processor
  • ISP image signal processor
  • controller a memory
  • video codec a digital signal processor
  • DSP digital signal processor
  • NPU neural-network processing unit
  • Different processing units may be independent devices or integrated in one or more processors.
  • the controller may be the nerve center and command center of the terminal device 100.
  • the controller may generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.
  • a memory may also be provided in the processor 410 for storing instructions and data.
  • the memory in the processor 410 is a cache memory.
  • the memory may store instructions or data that the processor 410 has just used or cyclically used. If the processor 410 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 410, and thus improves the efficiency of the system.
  • the charging management module 440 is used to receive charging input from a charger.
  • the charger may be a wireless charger or a wired charger.
  • the charging management module 440 may receive charging input from a wired charger through the USB interface 430.
  • the charging management module 440 may receive wireless charging input through a wireless charging coil of the terminal device 100. While the charging management module 440 is charging the battery 442, it may also power the electronic device through the power management module 441.
  • the power management module 441 is used to connect the battery 442, the charging management module 440 and the processor 410.
  • the power management module 441 receives input from the battery 442 and/or the charging management module 440 to power the processor 410, the internal memory 421, the external memory, the display screen 494, the camera 493, and the wireless communication module 460.
  • the power management module 441 can also be used to monitor parameters such as battery capacity, battery cycle number, battery health status (leakage, impedance), etc.
  • the power management module 441 may also be disposed in the processor 410.
  • the power management module 441 and the charging management module 440 may also be disposed in the same device.
  • the wireless communication function of the terminal device 100 can be implemented through antenna 1, antenna 2, mobile communication module 450, wireless communication module 460, modem processor and baseband processor.
  • Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals.
  • Each antenna in terminal device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve the utilization of antennas.
  • antenna 1 can be reused as a diversity antenna for a wireless local area network.
  • the antenna can be used in combination with a tuning switch.
  • the mobile communication module 450 can provide solutions for wireless communications including 2G/3G/4G/5G applied to the terminal device 100.
  • the mobile communication module 450 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc.
  • the mobile communication module 450 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation.
  • the mobile communication module 450 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1.
  • at least some of the functional modules of the mobile communication module 450 can be set in the processor 410.
  • at least some of the functional modules of the mobile communication module 450 can be set in the same device as at least some of the modules of the processor 410.
  • the wireless communication module 460 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) network), bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR) and the like applied to the terminal device 100.
  • WLAN wireless local area networks
  • BT wireless fidelity
  • GNSS global navigation satellite system
  • FM frequency modulation
  • NFC near field communication
  • IR infrared
  • the wireless communication module 460 can be one or more devices integrating at least one communication processing module.
  • the wireless communication module 460 receives electromagnetic waves via the antenna 2, modulates the electromagnetic wave signal and performs filtering, and sends the processed signal to the processor 410.
  • the wireless communication module 460 can also receive the signal to be sent from the processor 410, modulate the signal, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.
  • the antenna 1 of the terminal device 100 is coupled to the mobile communication module 450, and the antenna 2 is coupled to the wireless communication module 460, so that the terminal device 100 can communicate with the network and other devices through wireless communication technology.
  • the wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and/or IR technology.
  • GSM global system for mobile communications
  • GPRS general packet radio service
  • CDMA code division multiple access
  • WCDMA wideband code division multiple access
  • TD-SCDMA time-division code division multiple access
  • LTE long term evolution
  • BT GNSS
  • WLAN wireless local area network
  • NFC long term evolution
  • FM FM
  • IR technology IR technology
  • GNSS can include the global positioning system (GPS), the global navigation satellite system (
  • the terminal device 100 implements the display function through a GPU, a display screen 494, and an application processor.
  • the GPU is a microprocessor for image processing, which connects the display screen 494 and the application processor.
  • the GPU is used to perform mathematical and geometric calculations for graphics rendering.
  • the processor 410 may include one or more GPUs, which execute program instructions to generate or change display information.
  • Display screen 494 is used to display images, videos, etc.
  • the display screen 494 includes a display panel.
  • the display panel may be a liquid crystal display (LCD).
  • LCD liquid crystal display
  • OLED Organic light-emitting diode
  • AMOLED active-matrix organic light emitting diode
  • FLED flexible light-emitting diode
  • Miniled MicroLed, Micro-oLed, quantum dot light emitting diodes (QLED), etc.
  • the terminal device 100 can realize the shooting function through ISP, camera 493, video codec, GPU, display screen 494 and application processor.
  • the terminal device 100 can implement audio functions such as music playing and recording through the audio module 470, the speaker 470A, the receiver 470B, the microphone 470C, the headphone jack 470D, and the application processor.
  • audio functions such as music playing and recording through the audio module 470, the speaker 470A, the receiver 470B, the microphone 470C, the headphone jack 470D, and the application processor.
  • the SIM card interface 495 is used to connect a SIM card.
  • the SIM card can be connected to or separated from the terminal device 100 by inserting the SIM card interface 495 or pulling it out from the SIM card interface 495.
  • the terminal device 100 can support 1 or N SIM card interfaces, where N is a positive integer greater than 1.
  • the SIM card interface 495 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. Multiple cards can be inserted into the same SIM card interface 495 at the same time. The types of multiple cards can be the same or different.
  • the SIM card interface 495 can also be compatible with different types of SIM cards.
  • the SIM card interface 495 can also be compatible with external memory cards.
  • the terminal device 100 interacts with the network through the SIM card to implement functions such as calls and data communications.
  • the terminal device 100 uses an eSIM, i.e., an embedded SIM card.
  • the eSIM card can be embedded in the terminal device 100 and cannot be separated from the terminal device 100.
  • the structure illustrated in this embodiment does not constitute a specific limitation on the terminal device 100.
  • the terminal device 100 may include more or fewer components than shown in the figure, or combine certain components, or split certain components, or arrange the components differently.
  • the components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.
  • the terminal device 100 may also include auxiliary devices such as a mouse, a keyboard, and a drawing board.
  • the terminal device 100 may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to a wireless modem with wireless communication functions; it may also include a subscriber unit, a cellular phone, a smart phone, a wireless data card, a personal digital assistant (PDA) computer, a tablet computer, a wireless modem, a handheld device, a laptop computer, a cordless phone or a wireless local loop (WLL) station, a machine type communication (MTC) terminal, a user equipment (UE), a mobile station (MS), a terminal device or a relay user device, etc.
  • the relay user device may be, for example, a 5G residential gateway (RG).
  • an embodiment of the present application provides a network slice matching method, including:
  • the network slice selection rules are part of the URSP rules.
  • the slice selection rule can be included in the routing descriptor RSD in the URSP rule. That is, defining a new network slice selection rule can also be understood as defining a new URSP rule.
  • the new network slice selection rule may refer to determining the data processing level (also referred to as data processing level, data processing mode, terminal device internal processing level/mode, etc.) corresponding to the application (application) in the terminal device, the network slice corresponding to the application (e.g., the first network slice), and the PDU session supporting the first network slice according to the network slice indication information (network slice identifier) in the URSP rule. That is, the new network slice selection rule can be used to determine the data processing level corresponding to the application in the terminal device, the network slice corresponding to the application (e.g., the first network slice), and the PDU session supporting the first network slice.
  • the data processing level also referred to as data processing level, data processing mode, terminal device internal processing level/mode, etc.
  • the new network slice selection rule can be used to determine the data processing level corresponding to the application in the terminal device, the network slice corresponding to the application (e.g., the first network slice), and the PDU session supporting the first network slice.
  • the terminal device may determine that the first application performs processing at the first processing delay level in the terminal device according to the new network slice selection rule. At the same time, the terminal device may associate the first application with the PDU session supporting the first network slice.
  • the identifier of the first network slice may be S-NSSAI 1.
  • New network slice selection rules or new URSP rules may be defined by a standard organization (e.g., 3GPP), or may be defined by an operator (e.g., China Mobile, China Unicom, China Telecom, China Broadcasting, etc.). Operators may configure new network slice selection rules (or new URSP rules) on the network side and the terminal side.
  • the network side refers to network equipment, such as network equipment (network elements) such as gNB, AMF, SMF, PCF, etc.
  • the terminal side may refer to a terminal device, such as a UE.
  • the H-PCF i.e., the PCF at the home location
  • a new network slice selection rule (or new URSP rule) may be configured through a registration command message.
  • the new network slice selection rule may correspond to three possible network slice indication methods, including a first possible indication method, a second possible indication method and a third possible indication method.
  • the first possible indication method and the second possible indication method are explicit indication methods
  • the third possible indication method is an implicit indication method.
  • the first possible indication method define a new network slice identifier, which indicates a new network slice type.
  • the original network slice identifier can only be used to indicate the network slice corresponding to the application, so that the terminal device can associate the application traffic to the PDU session that supports the network slice.
  • the new network slice identifier can not only be used to indicate the network slice corresponding to the application, so that the terminal device can associate the application traffic to the PDU session that supports the network slice, but also indicate the data processing level of the terminal device corresponding to the application, so as to better meet business needs.
  • the first indication information may be added to the structure of S-NSSAI, for example, the first indication information may be added to SD or SST.
  • the first indication information may be, for example, a new slice type name, an internal slice (IS) parameter, etc.
  • the first indication information is used to indicate the data processing level corresponding to the application on the terminal device.
  • the first indication information may have multiple values, and different values correspond to different data processing levels.
  • the first indication information may include 1 bit or multiple bits.
  • the data processing level corresponding to the application in the terminal device may include one or more processing priorities (for example: different processing priorities of high, medium and low, and different processing priorities may correspond to different network transmission channels), one or more processing delay levels (for example: different levels such as 1ms, 10ms, 100ms, or different levels of high, medium and low), one or more processing rate levels (for example: different processing levels such as 1Mbps, 10Mbps, 100Mbps, 1000Mbps, or different levels of high, medium and low), one or more processing security levels (for example: different security levels such as ordinary, TEE, SE, or different security levels of high, medium and low), one or more processing reliability levels (for example: reliability levels of 1 9, 2 9, 3 9, 4 9, 5 9, or different reliability and security levels of high, medium and low), etc.
  • processing priorities for example: different processing priorities of high, medium and low, and different processing priorities may correspond to different network transmission channels
  • processing delay levels for example: different levels such as 1ms, 10ms, 100ms, or different levels of high, medium and low
  • X 9s represent The maximum possible service interruption time of the terminal equipment during the use of the terminal equipment for 1 year is shown in Figure 1, where X is 1, 2, 3, 4, 5, etc. It can be understood that the shorter the maximum possible service interruption time of the terminal equipment, the higher the reliability.
  • 99.9% includes 3 9s.
  • the first indication information carried in S-NSSAI 1 is 00, indicating that the data processing level corresponding to the application in the terminal device is the first processing priority, and the terminal device associates the application to the PDU session supporting S-NSSAI 1;
  • the first indication information carried in S-NSSAI 2 is 01, indicating that the data processing level corresponding to the application in the terminal device is the second processing priority, and the terminal device associates the application to the PDU session supporting S-NSSAI 2;
  • the first indication information carried in S-NSSAI 3 is 10, indicating that the data processing level corresponding to the application in the terminal device is the first processing delay level, and the terminal device associates the application to the PDU session supporting S-NSSAI 3;
  • the first indication information carried in S-NSSAI 4 is 11, indicating that the data processing level corresponding to the application in the terminal device is the second processing delay level, and the terminal device associates the application to the PDU session supporting S-NSSAI 4.
  • the first processing priority is different from the second processing priority.
  • the first processing priority may be higher than the second processing priority.
  • the first processing priority may be used for call applications, and the first processing priority may be used for game applications.
  • the data flow of the call application may be processed first.
  • the first processing delay level is different from the second processing delay level.
  • the first processing delay level is higher than the second processing delay level, that is, the processing delay corresponding to the first processing delay level is less than the processing delay corresponding to the second processing delay level.
  • the second possible indication method can be added on the basis of the existing network slice identifier.
  • the second indication information can be added to the SST, SD or NSSAI information element identifier (IEI).
  • the second indication information can include 1 bit or multiple bits.
  • the second indication information is used to indicate the data processing level corresponding to the application on the terminal device, and the data processing level corresponds to the network slice type or network slice priority.
  • the type of the first network slice is a low-latency slice
  • a second indication information is added to the identifier of the first network slice
  • the second indication information can indicate that the data processing level of the terminal device is a low-latency processing level.
  • the low-latency processing level refers to the priority processing of service data within the terminal device, such as priority scheduling, priority queuing, queue-jumping and early transmission, and priority transmission.
  • the processing level of the service within the terminal device is a low-latency processing level, which can ensure the service requirements of the service (for example, low latency).
  • it can To avoid the problem of poor service experience due to low network slicing latency and high internal processing latency of the terminal device, it can To give full play to the advantages of low-latency network slicing and meet business needs.
  • the type of the second network slice is a high-rate slice (S-NSSAI 2).
  • the second indication information can indicate that the data processing level of the terminal device is a high-rate processing level.
  • the high-rate processing level refers to the use of more processing resources (such as memory resources, computing resources (CPU, GPU, NPU, etc.)) inside the terminal device to process service data.
  • the processing level of the service inside the terminal device is a high-rate processing level, which can guarantee the service requirements of the service (for example, high rate). Avoiding the problem of poor service experience caused by high network slicing rate and low internal processing rate of terminal devices can give full play to the advantages of high-rate network slicing and meet service needs.
  • the type of the third network slice is a high-security slice (S-NSSAI 3), and a second indication information is added to the identifier of the third network slice.
  • the second indication information may indicate that the processing level inside the terminal device is a high-security processing level.
  • the high-security processing level may be that the terminal device processes the service data in a high-security area (for example, in TEE, SE), and/or the terminal device uses a high-encryption method for the service data to ensure the security of the service data.
  • the processing level of the service inside the terminal device is a high-security processing level, which can guarantee the service requirements of the service (for example, high-security service requirements). This avoids the problem of poor service experience due to high security of network slices and low security of internal processing of terminal devices, and can give full play to the advantages of high-security network slices to meet service requirements.
  • the type of the fourth network slice is a high-reliability slice (S-NSSAI 4), and a second indication information is added to the identifier of the fourth network slice, and the second indication information may indicate that the processing level inside the terminal device is a high-reliability processing level.
  • the high-reliability processing level may be that the terminal device backs up and/or transmits the service data multiple times to ensure the reliability of the service data.
  • the processing level of the service inside the terminal device is a high-reliability processing level, which can guarantee the service requirements of the service (for example, high-reliability service requirements). Avoiding the problem of poor service experience caused by high reliability of network slices and low reliability of internal processing of terminal devices can give full play to the advantages of high-reliability network slices and meet service requirements.
  • the type of the fifth network slice is a large-bandwidth slice (S-NSSAI 5), and a second indication information is added to the identifier of the fifth network slice, and the second indication information may indicate that the processing level inside the terminal device is a large-bandwidth processing level.
  • the large-bandwidth processing level may be, for example, that the terminal device uses a frequency band with a larger bandwidth (for example, 80M/120M) to transmit service data, or that the terminal device uses multiple frequency bands to transmit data at the same time.
  • the processing level of the service inside the terminal device is a large-bandwidth processing level, which can guarantee the service requirements of the service (for example, large-bandwidth service requirements).
  • This avoids the problem of poor service experience caused by high reliability of network slices and small internal processing bandwidth of terminal devices, and can give full play to the advantages of large-bandwidth network slices to meet service requirements.
  • the third possible indication method implicitly indicate the application on the corresponding terminal device through the existing network slice identifier That is, without adding indication information, the data processing level corresponding to the application on the terminal device is indicated in an implicit way.
  • the first network slice (S-NSSAI 1) is a low-latency slice, implicitly indicating that the data processing level of the terminal device is a low-latency processing level.
  • the second network slice (S-NSSAI 2) is a high-rate slice, implicitly indicating that the data processing level of the terminal device is a high-rate processing level.
  • the third network slice (S-NSSAI 3) is a high-security slice, implicitly indicating that the data processing level of the terminal device is a high-security processing level.
  • the fourth network slice (S-NSSAI 4) is a high-reliability slice, implicitly indicating that the data processing level of the terminal device is a high-reliability processing level.
  • the network slice priority may include three levels, namely high, medium and low.
  • the processing priority of the terminal device may also include three levels, namely high, medium and low.
  • the priority of the first network slice (S-NSSAI1) is high, and the processing priority of the terminal device corresponding to the first network slice is also high;
  • the priority of the second network slice (S-NSSAI 1) is medium, and the processing priority of the terminal device corresponding to the first network slice is also medium;
  • the priority of the first network slice (S-NSSAI 1) is low, and the processing priority of the terminal device corresponding to the first network slice is also low.
  • the processing priority of the terminal device when processing the application is also high, so as to ensure the business requirements of the application (for example, low latency, high reliability, etc.).
  • the priority of the network slice corresponding to the application is medium, the processing priority of the terminal device when processing the application is also medium, and the business requirements of the application (for example, low latency, etc.) are guaranteed as much as possible.
  • the priority of the network slice corresponding to an application is low, the processing priority of the application inside the terminal device can also be low to reasonably meet the business needs of the application.
  • the network slice priority may include two levels, high and low.
  • the processing priority of the terminal device may also include two levels, high and low. As shown in Table 5, the priority of the first network slice (S-NSSAI 1) is high, and the processing priority of the terminal device corresponding to the first network slice is also high; the priority of the second network slice (S-NSSAI 1) is low, and the processing priority of the terminal device corresponding to the first network slice is also low.
  • the network slice priority can also include more levels, for example, it can include four, five, or six levels, which is not limited in this application.
  • the processing priority of the terminal device can also include more levels, for example, it can include four, five, or six levels, which is not limited in this application.
  • the above text illustrates the mapping relationship between network slice priority and processing priority of terminal device by using the one-to-one correspondence between network slice priority and processing priority of terminal device.
  • the network slice priority includes N levels
  • the processing priority of terminal device includes M levels, and N is different from M.
  • one network slice priority level can correspond to multiple processing priority levels, or multiple network slice priority levels can correspond to one processing priority level, which is not limited in this application.
  • the network slice priority may include three levels, namely high, medium, and low.
  • the processing priority of the terminal device may include two levels, namely high and low.
  • the priority of the first network slice (S-NSSAI 1) is high, and the processing priority of the terminal device corresponding to the first network slice is also high;
  • the priority of the second network slice (S-NSSAI 2) is medium, and the processing priority of the terminal device corresponding to the second network slice is low;
  • the priority of the third network slice (S-NSSAI3) is low, and the processing priority of the terminal device corresponding to the third network slice is low. That is, multiple network slice priority levels can correspond to the processing priority level of a terminal device.
  • the network slice priority may be determined based on the type of network slice. For example, the priorities of network slices of types such as uRLLC, eMBB, and mMTC are ranked from high to low.
  • the new network slice selection rule i.e., according to the network slice identifier in the new URSP rule
  • the first application performs data processing at a first data processing level (for example, a low-latency processing level, a high-rate processing level, etc.) on the terminal device, and the network slice corresponding to the first application is the first network slice.
  • the terminal device can associate the first application with a PDU session that supports the first network slice, and the first network slice is identified by a first S-NSSAI.
  • the first application performing data processing at a first data processing level on the terminal device means that the data flow (traffic of application) of the first application performs data processing at the first data processing level on the terminal device.
  • the terminal device associating the first application to the PDU session supporting the first network slice means that the terminal device transmits or routes the data flow of the first application through the PDU session supporting the first network slice (traffic of the application shall be routed via a PDU Session supporting any of the included S-NSSAIs).
  • the H-PCF (i.e., the PCF at the home location) can define new URSP rules and forward the new URSP rules to the terminal device through the AMF and gNB.
  • the operator can configure new URSP rules for the terminal device.
  • the new URSP rule can be to add a newly defined parameter (such as internal Slice (IS)) to the traffic descriptor of the URSP.
  • the new URSP rule can be to add a newly defined parameter IS to the RSD of the URSP.
  • IS can correspond to one or more values, indicating the mapping relationship between different network slice priorities and the processing priorities of the terminal device.
  • the IS When the value is the first value (for example, 01), it indicates the mapping relationship between the high-level network slice priority and the processing priority of the high-level terminal device. That is, the service matched by the Traffic descriptor corresponds to the high-level network slice priority and the processing priority of the high-level terminal device.
  • the value of IS is the second value (for example, 11)
  • it indicates the mapping relationship between the low-level network slice priority and the processing priority of the low-level terminal device. That is, the service matched by the Traffic descriptor corresponds to the low-level network slice priority and the processing priority of the low-level terminal device.
  • ISs with different values may correspond to different S-NSSAIs.
  • IS1 i.e., the value of IS is the first value
  • IS2 i.e., the value of IS is the second value
  • S-NSSAI-1 the priority of S-NSSAI-1
  • IS1 indicates that a high-level slice priority corresponds to a high-level processing priority of a terminal device, that is, when a service corresponds to S-NSSAI-1, the terminal device's internal processing priority for the service is also high.
  • IS2 indicates that a low-level slice priority corresponds to a low-level processing priority of a terminal device, that is, when a service corresponds to S-NSSAI-2, the terminal device's internal processing priority for the service is also low.
  • multiple new S-NSSAIs may be defined, and IS-related information elements may be added to the composition structure of the new S-NSSAI.
  • the SD of the new S-NSSAI may include the IS.
  • the SST of the new S-NSSAI may include the IS.
  • Different S-NSSAIs may correspond to ISs with different values.
  • IS1 i.e., the value of IS is the first value
  • IS2 i.e., the value of IS is the second value
  • S-NSSAI-1 a new S-NSSAI
  • S-NSSAI-2 another new S-NSSAI
  • the priority of S-NSSAI-1 is high
  • IS1 indicates that a high-level slice priority corresponds to a high-level terminal device processing priority, that is, when the service corresponds (matches) S-NSSAI-1, the terminal device's internal processing priority for the service is also high.
  • IS2 indicates that a low-level slice priority corresponds to a low-level terminal device processing priority, that is, when the service corresponds to S-NSSAI-2, the terminal device's internal processing priority for the service is also low.
  • the terminal device sends a registration request message to the gNB.
  • the terminal device Before executing services, the terminal device can register on the network, that is, it can send a registration request message (registration request) to the gNB.
  • the registration request message can carry the requested NSSAI (Requested NSSAI). That is, the terminal device can request the network side to use the network slices in the current PLMN and the current registration area.
  • the requested NSSAI may include at least one S-NSSAI determined by the terminal device.
  • the NSSAI included in the "requested NSSAI” may be selected from “configured NSSAI", “allowed NSSAI” or "default configured NSSAI”.
  • the "requested NSSAI” does not include any S-NSSAI currently rejected by the network.
  • the network slice identifier (i.e., at least one S-NSSAI) carried in the registration request message may be a network slice identifier of one of the three indication methods described above. That is, the registration request message may carry a new network slice identifier, and the new network slice identifier carries first indication information, and the first indication information is used to indicate the data processing level corresponding to the application on the terminal device. Alternatively, the registration request message may carry an existing network slice identifier and second indication information, and the second indication information is used to indicate the data processing level corresponding to the application on the terminal device. Alternatively, the registration request message may carry an existing network slice identifier, and the existing network slice identifier may implicitly indicate the data processing level of the terminal device.
  • the gNB After receiving the registration request message from the terminal device, the gNB can forward the registration request message to the AMF. If the terminal device is in the CM-CONNECTED state, the gNB can forward the registration request message to the AMF based on the N2 connection of the terminal device. If the terminal device is in the CM-IDLE state, the terminal device does not include the "Request to Register" message when establishing a connection with the RAN. If the gNB sends the Registration Request message to the default AMF, the gNB may forward the Registration Request message to the default AMF.
  • the AMF can verify whether the S-NSSAI in the "requested NSSAI" is allowed based on the "contracted S-NSSAIs". Among them, the "contracted S-NSSAIs" can be obtained by the AMF from the unified data management UDM network element. The AMF can determine a registration area so that all S-NSSAIs of the "allowed NSSAI" of the registration area are available in all tracking areas of the registration area, and then return the "allowed NSSAI” to the terminal device. Optionally, the AMF returns a mapping of "allowed NSSAI" to "contracted S-NSSAIs" to the terminal device.
  • the AMF can return one or more "rejected S-NSSAIs" and the reason for rejection of each of them. If the S-NSSAI rejection reason value indicates a network slice-specific authentication and authorization failure or revocation, the terminal device can retry requesting the S-NSSAI based on local policy.
  • AMF sends a registration accept message to gNB, which indicates that the registration request has been accepted by AMF.
  • gNB After receiving the registration accept message from AMF, gNB can forward the registration accept message to the terminal device, that is, step 503 can be executed.
  • the gNB sends a registration accept message to the terminal device.
  • the registration acceptance message may include the allowed NSSAI (Allowed NSSAI), which indicates the S-NSSAI allowed by the network in the NSSAI requested by the terminal device.
  • allowed NSSAI Allowed NSSAI
  • the registration acceptance message may also include a rejected NSSAI (Rejected NSSAI), where the rejected NSSAI indicates the S-NSSAI rejected by the network in the NSSAI requested by the terminal device.
  • rejected NSSAI Rejected NSSAI
  • the terminal device matches the URSP rule according to the relevant information of the application.
  • the terminal device obtains the corresponding information from the application, or the terminal device identifies the corresponding information of the application.
  • the application can send the corresponding information of the application to the processing module that executes the URSP rule in the terminal device.
  • the processing module that executes the URSP rule can obtain the corresponding information of the application from a specific memory. That is, the corresponding information of the application is configured in advance to the terminal device, and the terminal device can obtain the corresponding information of the application in advance, which is not limited in this application.
  • the relevant information of the application is used by the terminal device to perform URSP rule (new URSP rule) matching.
  • the relevant information of the application may include an identifier of the application (APP ID).
  • the relevant information of the application may include network slice information that the application wants to use, such as a first network slice identifier (S-NSSAI1).
  • the first network slice identifier may be a network slice identifier in one of the three indication methods described above.
  • the relevant information of the application may include first information, and the first information is used to indicate the network slice information that the application wants to use (that is, the first information has a mapping relationship with the network slice information that the application wants to use), such as a first network slice identifier (S-NSSAI 1).
  • the URSP rules (i.e., new URSP rules) configured by the terminal device may include one or more. Multiple URSP rules may correspond to different priorities.
  • the terminal device may match the relevant information of the application in the order of priority of the URSP rules. For example, assume that the multiple URSP rules configured by the terminal device include URSP1 and URSP2.
  • URSP1 is a URSP rule indicating a low-latency processing level
  • URSP2 is a URSP rule indicating a high-rate processing level. If the priority of URSP1 is higher than that of URSP2, the terminal device may first match the relevant information of the application with URSP1. If there is no match, the relevant information of the application is matched with URSP2.
  • the terminal device matches the application-related information with the URSP rule, specifically matching the application-related information with the component in the URSP rule, for example, matching the application-related information with the Traffic descriptor in the URSP rule.
  • matching the application-related information with the traffic descriptor in the URSP rule may be performed.
  • the Route Selection Descriptor in the URSP rule is matched.
  • the application is associated with the PDU session corresponding to the RSD of URSP 1 (for example, PDU session1), that is, the terminal device routes the data flow of the application to PDU session1.
  • the PDU session corresponding to the RSD of URSP 1 refers to the PDU session that supports the parameters in the RSD of URSP 1
  • the parameters in the RSD of URSP 1 include S-NSSAI, DNN, SSCmode, etc.
  • the S-NSSAI in the RSD can be a network slice identifier in one of the three indication methods described above.
  • one or more URSP rules configured or acquired by the terminal device may include URSP1, URSP2, URSP3, default URSP rules, etc.
  • URSP1 includes a traffic descriptor and 3 RSDs.
  • the traffic descriptor includes an application identifier (e.g., King of Glory);
  • RSD1 includes S-NSSAI-1,
  • RSD2 includes S-NSSAI-2, and
  • RSD3 includes S-NSSAI-3.
  • URSP2 includes a traffic descriptor and 2 RSDs.
  • the traffic descriptor includes an application identifier (e.g., King of Glory);
  • RSD4 includes S-NSSAI-4, and RSD5 includes S-NSSAI-5.
  • URSP3 includes a traffic descriptor and 3 RSDs.
  • the traffic descriptor includes an application identifier (e.g., V2X); RSD6 includes S-NSSAI-6, RSD7 includes S-NSSAI-7, and RSD8 includes S-NSSAI-8.
  • the default URSP includes a wildcarded traffic descriptor and a wildcarded RSD.
  • the wildcard traffic descriptor can match all services.
  • the wildcard RSD includes a wildcard slice, and the type of the wildcard slice is eMBB.
  • the terminal device initiates the cloud gaming application (for example, ),
  • the corresponding application ID is King of Glory.
  • the corresponding application identifier matches the traffic descriptor in URSP1
  • the network slice information desired to be used (for example, S-NSSAI 1) matches the network slice identifier in RSD1, and the terminal device determines that the URSP rule matching the current service to be initiated is URSP1.
  • the terminal device determines whether the network slice indicated by RSD1 (S-NSSAI 1) belongs to the Allowed NSSAI of the current network. If the network slice indicated by RSD1 (for example, S-NSSAI 1) belongs to the Allowed NSSAI of the current network, Associated to the PDU session supporting RSD1 in URSP1. It should be noted that the network slice indicated by RSD1 (e.g., S-NSSAI 1) can indicate not only The corresponding network slices enable the terminal device to The traffic is associated with the PDU session that supports the network slice, and can also indicate The corresponding data processing level of the terminal device (for example, the low latency processing level) can better meet the business needs. This can avoid the situation where the network slice has low latency, but the internal processing latency of the terminal device is high, resulting in poor business experience, and can give full play to the advantages of network slicing.
  • a traffic descriptor or RSD in the URSP rule may include a parameter for indicating the data processing level of the terminal device.
  • the relevant information of the application may also carry a parameter for indicating the data processing level of the terminal device.
  • the parameter for indicating the data processing level of the terminal device carried in the relevant information of the application and the parameter for indicating the data processing level of the terminal device in the URSP rule may be matched.
  • the URSP matching process is described by taking the RSD in the URSP rule as an example, which includes a parameter (for example, IS) for indicating the data processing level of the terminal device.
  • IS is used to indicate the data processing level corresponding to the application on the terminal device.
  • the data processing level corresponding to the application on the terminal device can refer to the relevant description above, which will not be repeated here.
  • the one or more URSP rules configured or acquired by the terminal device may include URSP1, URSP2, URSP3, default URSP rules, etc.
  • URSP1 includes a traffic descriptor and three RSDs.
  • the traffic descriptor includes an application identifier (e.g., King of Glory);
  • RSD1 includes S-NSSAI-1 and IS (e.g., IS1);
  • RSD2 includes S-NSSAI-2 and IS (e.g., IS2),
  • RSD3 includes S-NSSAI-3 and IS (e.g., IS3).
  • URSP2 includes a traffic descriptor and 2 RSDs.
  • the traffic descriptor includes an application identifier (e.g., King of Glory); RSD4 includes S-NSSAI-4 and IS (e.g., IS4), and RSD5 includes S-NSSAI-5 and IS (e.g., IS5).
  • URSP3 includes a traffic descriptor and 3 RSDs.
  • the traffic descriptor includes an application identifier (e.g., V2X); RSD6 includes S-NSSAI-6 and IS (e.g., IS6), RSD7 includes S-NSSAI-7 and IS (e.g., IS7), and RSD8 includes S-NSSAI-8 and IS (e.g., IS8).
  • the default URSP includes a wildcard traffic descriptor and a wildcard RSD.
  • the wildcard traffic descriptor can match all services, the wildcard RSD includes a wildcard slice, and the type of the wildcard slice is eMBB.
  • the terminal device initiates the cloud gaming application (e.g. ),
  • the corresponding application ID is King of Glory, and the corresponding IS is IS1.
  • the corresponding application identifier matches the traffic descriptor in URSP1
  • the corresponding IS matches the IS in RSD1
  • the network slice information desired to be used matches the network slice identifier in RSD1, and the terminal device determines that the URSP rule matching the current service to be initiated is URSP1.
  • the terminal device determines whether the network slice indicated by RSD1 (S-NSSAI 1) belongs to the Allowed NSSAI of the current network. If the network slice indicated by RSD1 (for example, S-NSSAI 1) belongs to the Allowed NSSAI of the current network, Associated to the PDU session supporting RSD1 in URSP1. It should be noted that the network slice identifier (e.g., S-NSSAI 1) in RSD1 in URSP1 can indicate The corresponding network slices enable the terminal device to The traffic is associated with the PDU session that supports the network slice. The IS1 in RSD1 in URSP1 can indicate The corresponding data processing level of the terminal device (for example, the low latency processing level) can better meet the business needs. This can avoid the situation where the network slice has low latency, but the internal processing latency of the terminal device is high, resulting in poor business experience, and can give full play to the advantages of network slicing.
  • S-NSSAI 1 network slice identifier
  • the terminal device may also adopt other methods when performing URSP matching based on relevant information of the application, such as performing URSP matching based on domain name information corresponding to the service to be initiated (for example, fully qualified domain name (FQDN)), destination server IP address information, etc., or directly performing the above matching action by the modem layer without the participation of the application layer, which is not limited in this embodiment of the present application.
  • domain name information for example, fully qualified domain name (FQDN)
  • destination server IP address information etc.
  • URSP matching is stopped; or, if one or more S-NSSAIs corresponding to the RSDs in one or more RSDs that match the current service to be initiated do not belong to the Allowed NSSAI of the current network, URSP matching is stopped.
  • the terminal device associates the application to the PDU session.
  • the terminal device associates the application with the PDU session, that is, the terminal device routes the data flow of the application to the PDU session. If there is no PDU session that supports the network slice identifier (e.g., S-NSSAI 1) that the application wants to use, the terminal device initiates the establishment of a PDU session that supports S-NSSAI 1 in order to associate the application with the established PDU session.
  • the network slice identifier e.g., S-NSSAI 1
  • the specific process of establishing a PDU session includes the following steps:
  • the terminal device sends a PDU session establishment request to AMF.
  • the terminal device can send a PDU session establishment request (PDU session establishment request) to the AMF through a non-access stratum (NAS) message.
  • PDU session establishment request PDU session establishment request
  • NAS non-access stratum
  • the PDU session establishment request may include a PDU session ID, a PDU session type, and a Type (PDU Session type), SSC Mode, DNN, S-NSSAI (S-NSSAI corresponding to the service) and other parameters.
  • the S-NSSAI in the PDU session establishment request can be a network slice identifier of one of the three indication methods described above.
  • the S-NSSAI carried in the PDU session request message is forwarded to the AMF via the wireless network.
  • the AMF checks the S-NSSAI in the PDU session request message, selects the corresponding SMF according to the slice capabilities supported by each SMF in the network, and forwards the session establishment request to the SMF.
  • AMF sends a PDU session create request (PDU session create request) to SMF.
  • AMF can send a PDU session creation request to SMF via HTTP2 POST.
  • the PDU session creation request can contain parameters such as SUPI, DNN, PDU Session ID, S-NSSAI, Request Type, etc.
  • SMF can establish the context of PDU session.
  • SMF can obtain the subscription information of the user response from UDM, and then send policy control messages to UPF, RAN and terminal equipment, and UPF, RAN and terminal equipment establish the connection of PDU session.
  • SMF sends a session creation response (PDU session create response) to AMF.
  • SMF After SMF determines that the PDU session connection is established, it can send a session creation response to AMF to indicate that the PDU session is successfully established.
  • AMF sends PDU session establishment accept (PDU session establishment accept) to the terminal device.
  • the AMF replies to the terminal device with a session establishment request response, indicating that the PDU session is successfully established.
  • the terminal device associates the application with the newly established PDU session, that is, the terminal device routes the application's data flow to the newly established PDU session.
  • the terminal device re-matches other URSP rules and initiates the establishment of the PDU session based on the re-matched URSP rules.
  • the terminal device can match the relevant information of the application with at least one URSP rule. If a URSP rule (for example, a first URSP rule) matches the relevant information of the application, the data stream of the application can be processed according to the data processing level indicated by the network slice identifier (first network slice identifier) in the first URSP rule.
  • a URSP rule for example, a first URSP rule
  • the terminal device can use the network slice corresponding to the first network slice identifier to transmit the data stream of the application, and at the same time process the data stream of the application based on the data processing level indicated by the first network slice identifier, that is, the transmission and processing performance of the service data can be jointly guaranteed by the data processing level of the network slice and the terminal device, which can meet the service requirements of different services.
  • the embodiment of the present application also provides a chip system, as shown in FIG10, the chip system includes at least one processor 1001 and at least one interface circuit 1002.
  • the processor 1001 and the interface circuit 1002 can be interconnected through a line.
  • the interface circuit 1002 can be used to receive signals from other devices (for example, a memory of a terminal device).
  • the interface circuit 1002 can be used to send signals to other devices (for example, the processor 1001).
  • the interface circuit 1002 may read instructions stored in a memory in the terminal device and send the instructions to the processor 1001.
  • the terminal device (such as the terminal device 100 shown in FIG4 ) may execute the various steps in the above embodiment.
  • chip system may also include other discrete devices, which is not specifically limited in the embodiments of the present application.
  • the embodiment of the present application also provides a computer-readable storage medium, which includes computer instructions.
  • a terminal device the terminal device 100 shown in FIG. 4
  • the terminal device The device 100 executes each function or step executed by the terminal device in the above method embodiment, so that the network device executes each function or step executed by the network device in the above method embodiment.
  • the embodiment of the present application also provides a computer program product.
  • the computer program product When the computer program product is run on a computer, the computer is enabled to execute each function or step executed by the terminal device in the above method embodiment.
  • An embodiment of the present application also provides a processing device, which can be divided into different logical units or modules according to functions, and each unit or module performs a different function, so that the processing device executes each function or step executed by the terminal device or network device in the above method embodiment.
  • the disclosed devices and methods can be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed.
  • Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium.
  • the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to execute all or part of the steps of the method described in each embodiment of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), 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

本申请实施例提供一种网络切片匹配方法和装置，涉及通信领域，能够满足不同业务需求(例如，低时延的业务需求，高可靠性的业务需求等)，可以提高用户体验。其方法为：终端设备获取应用程序的相关信息；终端设备将应用程序的相关信息与至少一个URSP规则进行匹配，至少一个URSP规则包括第一URSP规则，第一URSP规则包括第一网络切片标识，第一网络切片标识显示或隐式指示终端设备的数据处理级别；若第一URSP规则与应用程序的相关信息匹配，根据第一网络切片标识指示的数据处理级别对应用程序的数据流进行处理。

Description

一种网络切片匹配方法和装置
本申请要求于2022年11月25日提交国家知识产权局、申请号为202211493965.X、发明名称为“一种网络切片匹配方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种网络切片匹配方法和装置。
背景技术
为了满足第五代(5th generation，5G)移动通信系统中的网络差异化需求，第三代合作伙伴项目(3rd generation partnership project，3GPP)提出网络切片(network slice)技术。即可以将一张物理网络抽象划分成多个网络切片，每个网络切片构成一个端到端的逻辑网络。
网络切片彼此之间逻辑上是隔离的，不同的网络切片可以满足不同的业务需求。例如，对于要求低时延的业务，可以采用支持低时延业务的网络切片执行该业务。
然而，对于要求低时延的业务(例如，云游戏业务)来说，即使采用支持低时延业务的网络切片执行该业务，仍有可能由于其他原因(例如，终端对业务的内部处理时延较大)导致业务整体的时延增大，不符合业务需求，导致用户体验差。
发明内容
本申请实施例提供一种网络切片匹配方法和装置，能够满足不同业务需求(例如，低时延的业务需求，高可靠性的业务需求等)，可以提高用户体验。
第一方面，本申请实施例提供一种网络切片匹配方法，包括：终端设备获取应用程序的相关信息；终端设备将应用程序的相关信息与至少一个路由选择策略URSP规则进行匹配，至少一个URSP规则包括第一URSP规则，第一URSP规则包括第一网络切片标识，第一网络切片标识显示或隐式指示终端设备的数据处理级别；若第一URSP规则与应用程序的相关信息匹配，根据第一网络切片标识指示的数据处理级别对应用程序的数据流进行处理。
基于本申请实施例提供的方法，终端设备可以将应用程序的相关信息与至少一个URSP规则进行匹配，若第一URSP规则与应用程序的相关信息匹配，可以根据第一URSP规则中的第一网络切片标识指示的数据处理级别对应用程序的数据流进行处理。这样，终端设备可以使用第一网络切片标识对应的网络切片传输应用程序的数据流，同时基于第一网络切片标识指示的数据处理级别对该应用程序的数据流进行处理，即可以通过网络切片和终端设备的数据处理级别共同保证业务数据的传输和处理性能，能够满足不同业务的业务需求。
在一种可能的实现方式中，应用程序的相关信息包括第一网络切片标识。即应用程序的相关信息可以包括应用程序希望使用的网络切片信息，比如第一网络切片标识。第一URSP规则与应用程序的相关信息匹配，即第一URSP规则中包括的第一网络切片标识与应用程序的相关信息中的第一网络切片标识相同。
在一种可能的实现方式中，应用程序的相关信息包括第一信息，第一信息用于指示第一网络切片标识。即第一信息与应用程序希望使用的网络切片信息具有映射关系。第一URSP规则与应用程序的相关信息匹配，即第一URSP规则中包括的第一网络切片标识与应用程序的相关信息中的第一信息指示的第一网络切片标识相同。
在一种可能的实现方式中，第一URSP规则包括第一网络切片标识包括：第一URSP规则包括第一路由选择描述符RSD，第一RSD包括第一网络切片标识。第一URSP规则与应用程序的相关信息匹配，即第一URSP规则中的第一RSD中的第一网络切片标识与应用程序的相关信息中的第一网络切片标识相同。
在一种可能的实现方式中，方法还包括：终端设备根据第一URSP规则确定应用程序对应的协议数据单元PDU会话。其中，第一URSP规则可以包括S-NSSAI、DNN、SSCmode等参数，应用程序对应的PDU会话可以是指支持第一URSP规则中的上述参数的PDU会话。
在一种可能的实现方式中，第一网络切片标识显示指示终端设备的数据处理级别包括：第一网络切片标识包括第一指示信息，第一指示信息用于指示终端设备的数据处理级别；其中，第一指示信息包括多个取值，多个取值中的每个取值对应一种数据处理级别，不同取值对应的数据处理级别不同。这样，根据第一网络切片标识中的第一指示信息可以确定终端设备的数据处理级别，终端设备可以使用第一网络切片标识对应的网络切片传输应用程序的数据流，同时基于第一网络切片标识指示的数据处理级别对该应用程序的数据流进行处理，即可以通过网络切片和终端设备的数据处理级别共同保证业务数据的传输和处理性能，能够满足不同业务的业务需求。
在一种可能的实现方式中，第一网络切片标识显示指示终端设备的数据处理级别包括：第一网络切片标识包括第二指示信息，第二指示信息用于指示终端设备的数据处理级别，终端设备的数据处理级别与第一网络切片标识对应的网络切片类型或网络切片优先级具有对应关系。例如，第一网络切片标识指示的第一网络切片的类型为低时延切片，第二指示信息可以指示终端设备的数据处理级别为低时延处理级别。低时延处理级别是指终端设备内部对业务数据优先处理，比如，优先调度，优先排队，插队提前发送，优先发送。这样，当业务对应的网络切片是低时延切片时，终端设备内部对该业务的处理级别是低时延处理级别，可以保证该业务的业务需求(例如，低时延)。避免网络切片时延低而终端设备内部处理时延高导致业务体验不佳的问题，可以充分发挥低时延网络切片的优势，满足业务需求。
在一种可能的实现方式中，第一网络切片标识包括切片服务类型SST和切片区分符号SD，SST或SD中包括第一指示信息或第二指示信息。
在一种可能的实现方式中，终端设备的数据处理级别包括至少一种处理优先级，处理时延级别，处理速率级别，处理安全级别，处理可靠性级别、处理带宽级别。
在一种可能的实现方式中，终端设备获取应用程序的相关信息之前，方法还包括：终端设备向第一网络设备发送注册请求消息，注册请求消息携带第一网络切片标识；终端设备接收来自第一网络设备的注册接受消息，注册接受消息包括允许接入的切片的信息。注册接受消息中可以包括允许的NSSAI(Allowed NSSAI)，Allowed NSSAI表示终端设备请求的NSSAI中被网络允许的S-NSSAI。
在一种可能的实现方式中，方法还包括：终端设备向接入和移动性管理功能网元AMF网元发送PDU会话请求消息，PDU会话请求消息包括第一网络切片标识。终端设备可以通过PDU会话请求消息发起支持第一网络切片标识的PDU会话的建立，以便将应用程序关联到建立的PDU会话。
在一种可能的实现方式中，应用程序的相关信息还包括应用程序的标识，第一URSP规则还包括流量描述符，流量描述符与应用程序的标识匹配。
第二方面，本申请提供一种计算机程序产品，当所述计算机程序产品在计算机上运行时，使得所述计算机执行上述任一方面及其任一种可能的设计方式所述的方法。
第三方面，本申请提供一种计算机可读存储介质，该计算机可读存储介质包括计算机指令。当计算机指令在终端设备(如手机)上运行时，使得该终端设备执行如第一方面及其任一种可能的实现方式所述的方法。
第四方面，本申请实施例提供了一种通信装置，包括处理器，处理器和存储器耦合，存储器存储有程序指令，当存储器存储的程序指令被处理器执行时使得所述装置实现上述任一方面及其任一种可能的设计方式所述的方法。所述装置可以为终端设备；或可以为终端设备中的一个组成部分，如芯片。
第五方面，本申请提供一种芯片系统，该芯片系统包括一个或多个接口电路和一个或多个处理器。该接口电路和处理器通过线路互联。
上述芯片系统可以应用于包括通信模块和存储器的终端设备。该接口电路用于从第一终端设备的存储器接收信号，并向处理器发送接收到的信号，该信号包括存储器中存储的计算机指令。当处理器执行该计算机指令时，终端设备可以执行如上述任一方面及其任一种可能的设计方式所述的方法。
可以理解地，上述提供的第二方面所述的计算机程序产品，第三方面所述的计算机可读存储介质，第四方面所述的通信装置及第五方面所述的芯片系统所能达到的有益效果，可参考如第一方面及其任一种可能的设计方式中的有益效果，此处不再赘述。
附图说明
图1为本申请实施例提供的一种S-NSSAI的组成结构示意图；
图2为本申请实施例提供的一种URSP的组成结构示意图；
图3为本申请实施例提供的一种系统架构示意图；
图4为本申请实施例提供的一种终端设备的硬件结构示意图；
图5为本申请实施例提供的一种方法流程示意图；
图6为本申请实施例提供的又一种URSP的组成结构示意图；
图7为本申请实施例提供的又一种S-NSSAI的组成结构示意图；
图8为本申请实施例提供的一种URSP规则的匹配示意图；
图9为本申请实施例提供的一种URSP规则的匹配示意图；
图10为本申请实施例提供的一种芯片系统的结构示意图。
具体实施方式
为了下述各实施例的描述清楚简洁，首先给出相关概念或技术的简要介绍：
1、网络切片：一张物理网络可以被抽象划分成多个网络切片，每个网络切片可以构成一个端到端的逻辑网络。网络切片彼此之间在逻辑上是隔离的，互不影响。
通常情况下，为了满足不同的通信需求，网络切片可以被划分为多种类型。例如但不限于增强移动宽带(enhanced mobile broad band，eMBB)类型、海量机器类型连接(massive machine type connection，mMTC)、超高可靠性超低时延连接(ultra reliability and low latency connection，uRLLC)类型。
其中，不同类型网络切片的网络特征不相同。如eMBB的网络切片要求具备支持大带宽、低时延业务的特征；mMTC的网络切片要求具备支持海量接入，带宽小的特征；uRLLC的切片要求具备高可靠性、低时延的特征。
可见，支持的应用业务种类、端到端时延、单终端最大速率等，这些都属于网络切片的特征属性，这些特征属性依赖于切片的设计。
随着网络切片技术的引入，运营商可以为不同业务需求的用户提供“专属”网络，保障优质化的服务水平，满足差异化的业务需求；而用户也能够使用功能更加强大的应用产品，进一步激发新的行业应用蓝海大发展；实现提升网络资源使用效率、优化运营商网络建设投资、构建灵活敏捷的5G网络的目标。
2、单个切片接入辅助信息(single network slice selection assistance information，S-NSSAI)，用于唯一表示一个网络切片。
如图1所示，一个S-NSSAI的组成结构可以包括切片服务类型(slice serive type，SST)和切片区分符号(slice differentiator，SD)。SST指在功能和服务方面的预期网络切片行为。SD是可选信息，补充切片/服务类型，以区分相同切片/服务类型的多个网络切片。示例性的，SST可以包括8比特(bit)，SD可以包括24bits。
3、网络切片选择辅助信息(network slice selection assistance information，NSSAI)：NSSAI用于指示一个或多个S-NSSAI的集合。相应的，NSSAI可以用于表示一个或多个网络切片。
4、分组数据单元(Packet Data Unit，PDU)：5G网络以数据包的形式将终端设备(例如，用户设备(user equipment，UE))和外部网络之间发送和接收的数据进行传送，通常把这些用户的数据包叫做PDU。
5、PDU会话(session)：PDU会话是UE与数据网(data network，DN)间实现PDU连通性的会话服务，由PDU session ID标识。
6、用户路由选择策略(UE route selection policy，URSP)：通常，运营商根据客户订单，在通信网络的物理基础设施上为客户创建所需网络切片时，往往会根据业务需求，与客户签署网络切片的服务等级协议(servicelevel agreement，SLA)。在运营商的一个公共陆地移动网络(public land mobile network，PLMN)内，不一定整张网络都支持相同的网络切片集合(network slice set)。运营商可以根据区域，甚至单点基站，划分不同的切片集合。如此，不同区域网络可能对应不同切片。因此，在非漫游场景下，用户可能仅可通过归属网络中的部分区域接入所需切片，或者，在漫游场景下，仅可通过部分拜访网络中的部分区域接入所需切片。
目前，针对用户的路由问题，标准中定义了URSP。主要用于确定不同应用程序(application，APP)或业务所需的PDU会话参数，如网络切片、数据网络名称(data network name，DNN)、会话服务连续性模式(session service continuity mode，SSC mode)等。
通过URSP，终端可以根据APP或者业务的网络需求，确定对应的PDU会话参数， 并基于参数建立PDU会话。之后，通过建立的会话传输该APP或者业务的数据。
如图2所示，URSP可以包括流量描述符(traffic descriptor，TD)和一个或多个路由选择描述符(route selection descriptors，RSD)。当然，URSP还可以包括其他参数，本申请不做限定。
其中，流量描述符用于与业务信息(应用程序标识或流标识或业务标识等)进行匹配，通过应用程序标识或其他类型标识区分不同业务。比如，终端调制解调器(modem)可以按照一个或多个URSP规则的优先级从高到低，将应用程序标识(APP ID)与各个URSP规则中的流量描述符分别进行匹配。流量描述符有多种类型，比如Application descriptors(可以由操作系统标识(OSId)+应用程序标识(OSAppId)组成，例如，安卓操作系统下的可以表示为android+com.wechat)、IP descriptors(比如发起业务对应的目的IP地址)等。当确定出应用程序匹配的流量描述符后，根据该流量描述符对应的RSD(即该流量描述符对应的URSP规则中的RSD)确定传输该应用程序的流量的PDU会话。其中，RSD包括DNN、S-NSSAI、SSCmode等参数。传输该应用程序的流量的PDU会话即支持相应RSD(应用程序匹配的流量描述符对应的RSD)中的DNN、S-NSSAI、SSCmode等参数的PDU会话。也就是说，确定出应用程序匹配的流量描述符后，可以基于匹配的流量描述符对应的RSD确定出传输该应用程序的流量的PDU会话。
7、URSP匹配：当UE判断需发起特定业务/应用程序时，先按URSP规则的优先级顺序对待发起业务/应用程序与URSP规则中的流量描述符进行匹配。
若匹配到具体的URSP规则(该URSP规则也可能是默认URSP规则(也可称为通配URSP规则)，如流量描述符为match-all形式)，则UE还需根据该URSP规则的当前RSD确定该业务所需采用的切片S-NSSAI，并判断该切片S-NSSAI是否属于当前网络的Allowed NSSAI。具体的，在漫游场景中，终端需判断该切片S-NSSAI是否属于拜访网络当前的Allowed NSSAI，在非漫游场景中，终端需判断该切片S-NSSAI是否在归属网络当前的Allowed NSSAI之内。若该S-NSSAI不在Allowed NSSAI中，则UE将继续根据URSP优先级/RSD优先级对后续URSP规则或后续RSD进行匹配，直至确定该业务允许使用的切片S-NSSAI出现在Allowed NSSAI中且该切片S-NSSAI被网络侧接受。
目前，运营商可以基于网络切片技术为不同业务需求的用户提供“专属”的网络，保障优质化的服务水平，满足差异化的业务需求。例如，对于要求低时延的业务，可以采用支持低时延业务的网络切片执行该业务。然而，对于要求低时延的业务(例如，云游戏业务)来说，即使采用支持低时延业务的网络切片执行该业务，仍有可能由于其他原因(例如，终端对业务的内部处理时延较大)导致业务整体的时延增大，不符合业务需求，导致用户体验差。
以云游戏业务为例，云游戏可以基于实时音视频流技术，由服务端向客户端发送实时的音视频流，客户端向服务端发送控制指令流，并由服务端将接收到的控制指令应用到游戏中。云游戏例如可以包括动作类、格斗类、多人在线战术竞技游戏(multiplayer online battle arena，MOBA)类、第一人称射击类、赛车类等游戏。云游戏对操作响应延迟要求较高，对带宽要求高，对抖动也要求严格。即云游戏的业务需求是：低延迟、高带宽、无(小)抖动。因此，可以为云游戏匹配支持低延迟、高带宽、无(小)抖动的网络切片，以尽量满足云游戏的业务需求。
然而，云游戏的网络回路涉及到服务端游戏渲染、音视频编码、网络传输、客户端音视频解码和渲染等过程，这些过程都有一定程度的时延。目前，即使选择满足低时延要求的网络切片也只能降低网络传输过程中的时延，难以降低其他过程(例如，客户端音视频解码和渲染过程)的时延，从而难以保证云游戏端到端的低时延。
例如，假设网络切片A的时延为低时延20ms，网络切片B的时延为中时延50ms；终端内部处理优先级C的时延为高时延100ms，终端内部处理优先级D的时延为低时延15ms。对于要求低时延的业务(例如，云游戏业务)来说，即使选择低时延的网络切片A，若终端内部处理优先级为C(即时延达到100ms)，也会导致云游戏的整体时延增大，甚至不如选择时延较高的网络切片B和终端内部处理优先级D，即A+C的时延>B+D的时延，无法发挥网络切片的优势，难以满足云游戏的低时延需求。
为了解决上述问题，本申请实施例提供一种网络切片匹配方法，能够更好地满足不同业务需求(例如，低时延的业务需求，高可靠性的业务需求等)，可以提高用户体验。
本申请实施例提供的网络切片匹配方法应用于使用网络切片进行通信的通信系统中。比如，5G系统，或后续演进系统或其他系统。
参见图3，为本申请实施例所适用的一种通信系统的示例性架构。该通信系统包括：鉴权服务功能(authentication server function，AUSF)、统一数据管理(unified data management，UDM)、用户数据库(user data repository，UDR)、接入和移动性管理功能(core access and mobility management function，AMF)、会话管理功能(session management function，SMF)、策略控制功能(policy control function，PCF)、应用功能(application function，AF)/网络开放功能(network exposure function，NEF)、用户面功能(user planefunction，UPF)、接入网(access network，AN)等网元，以及DN和UE。其中，AN包括有线接入网和无线接入网(radio access network，RAN)。RAN可以包括下一代基站(next generation NodeB，gNB)。
其中，UE通过无线或有线方式接入AN.无线方式例如可以为通过无线保真(wireless-fidelity，WiFi)接入，还可以通过蜂窝网(例如E-UTRA、NR等)接入AN。UE通过N1与AMF通信；AN通过N3与UPF通信，AN通过N2与AMF通信；UPF通过N4与SMF通信，UPF通过N6与DN通信；AMF通过N8与UDM通信；SMF通过N11与AMF通信，SMF通过N10与UDM通信，SMF通过N7与PCF通信；AMF通过N12与AUSF通信，AUSF通过N13与UDM通信。AF通过N5与PCF通信。UDM通过N35与UDR通信。UDM通过N52与AF/NEF通信。UDR通过N36与PCF通信。AMF通过N15与PCF通信。其中，图3所示系统中，AF/NEF指的是AF经由NEF与核心网网元进行交互。
图3所示系统中，部分网元的功能如下：
AF：主要传递应用侧对网络侧的需求，例如，QoS需求或用户状态事件订阅等。AF可以是第三方功能实体，也可以是运营商部署的应用服务，如IMS语音呼叫业务。对于第三方应用的应用功能实体，其与核心网进行交互时，还可经由NEF进行授权处理，例如第三方AF向NEF发送请求消息，NEF判断该AF是否被允许发送该请求消息，若验证通过，则将转发该请求消息至对应PCF或UDM。
UDM：主要负责管理签约数据、用户接入授权等功能。
UDR：主要负责签约数据、策略数据、应用数据等类型数据的存取功能。
此外，UDR还可以在用户的Subscribed NSSAI中增加相应S-NSSAI，同时增加该SNSSAI下用户所允许使用的带宽、QoS保障等签约值。
PCF：主要负责针对会话、业务流级别进行计费、服务质量(quality of service，QoS)带宽保障及移动性管理、UE策略决策等策略控制功能。该架构中，AMF与SMF所连接的PCF分别对应AM PCF(即PCF for access and mobility control)和SM PCF(即PCF forsession management)，在实际部署场景中，AM PCF和SM PCF可能不是同一个PCF实体。
SMF：主要进行会话管理、PCF下发控制策略的执行、UPF的选择、UE网际互连协议(internet protocol，IP)地址分配等功能。
AMF：主要进行移动性管理、接入鉴权/授权等功能。此外，还负责在UE与PCF间传递用户策略。
UPF：作为和数据网络的接口UPF，完成用户面数据转发、基于会话/流级的计费统计，带宽限制等功能。
AN：对应不同接入网，如有线接入、无线基站接入等多种方式。
其中，图3所示架构中，部分接口功能描述如下：
1、N7：PCF与SMF之间的接口，用于下发PDU会话粒度以及业务数据流粒度控制策略。
2、N15：PCF与AMF之间的接口，用于下发UE策略及接入控制相关策略。
3、N5：AF与PCF之间的接口，用于应用业务请求下发以及网络事件上报。
4、N4：SMF与UPF之间的接口，用于控制面与用户面之间传递信息，包括控制面向用户面的转发规则、QoS控制规则、流量统计规则等的下发以及用户面的信息上报。
5、N11：SMF与AMF之间的接口，用于传递AN和UPF之间的PDU会话隧道信息、传递发送给UE的控制消息、传递发送给AN的无线资源控制信息等。
6、N2：AMF与RAN之间的接口，用于传递核心网侧至AN的无线承载控制信息等。
7、N1：AMF与UE之间的接口，接入无关，用于向UE传递QoS控制规则等。
8、N8：AMF与UDM间的接口，用于AMF向UDM获取接入与移动性管理相关签约数据与鉴权数据，以及AMF向UDM注册UE当前移动性管理相关信息等。
9、N9：用于UPF与UPF之间的用户面数据转发。
10、N10：SMF与UDM间的接口，用于SMF向UDM获取会话管理相关签约数据，以及SMF向UDM注册UE当前会话相关信息等。
11、N35：UDM与UDR间的接口，用于UDM从UDR中获取用户签约数据信息。
12、N36：PCF与UDR间的接口，用于PCF从UDR中获取策略相关签约数据以及应用数据相关信息。
可选的，图3中的各个网元的名字以及各个网元之间的接口名字只是一个示例，具体实现中各个网元或者各个网元之间的接口的名字可能为其他名字，或者网元也可以称之为实体，本申请实施例对此不作具体限定。图3中的全部或者部分网元可以是物理上的实体网元，也可以是虚拟化的网元，在此不做限定。
可选的，该架构中，还可以包括其他网元，比如运营管理(operation administration management，OAM)网元、网络切片选择功能(network slice selection function，NSSF)、网 络仓库功能(network repository function，NRF)等。本申请实施例对此不进行限制。
进一步的，图3所示5G通信系统包括非漫游场景下的系统和漫游场景下的系统。可选的，每一种场景的系统可以为基于服务化接口的系统，也可以为基于参考点的系统。这里，基于服务化接口和基于参考点的具体描述可参见现有技术，此处不再赘述。
此外，本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
如图4所示，为本申请实施例提供的一种终端设备100的结构示意图，该终端设备100可以是第一电子设备。如图4所示，终端设备100可以包括处理器410，外部存储器接口420，内部存储器421，通用串行总线(universal serial bus，USB)接口430，充电管理模块440，电源管理模块441，电池442，天线1，天线2，移动通信模块450，无线通信模块460，音频模块470，扬声器470A，受话器470B，麦克风470C，耳机接口470D，传感器模块480，按键490，马达491，指示器492，摄像头493，显示屏494，以及用户标识模块(subscriber identification module，SIM)卡接口495等。其中，传感器模块480可以包括压力传感器480A，陀螺仪传感器480B，气压传感器480C，磁传感器480D，加速度传感器480E，距离传感器480F，接近光传感器480G，指纹传感器480H，温度传感器480J，触摸传感器480K，环境光传感器480L，骨传导传感器480M等。
处理器410可以包括一个或多个处理单元，例如：处理器410可以包括应用处理器(application processor，AP)，调制解调处理器，图形处理器(graphics processing unit，GPU)，图像信号处理器(image signal processor，ISP)，控制器，存储器，视频编解码器，数字信号处理器(digital signal processor，DSP)，基带处理器，和/或神经网络处理器(neural-network processing unit，NPU)等。其中，不同的处理单元可以是独立的器件，也可以集成在一个或多个处理器中。
控制器可以是终端设备100的神经中枢和指挥中心。控制器可以根据指令操作码和时序信号，产生操作控制信号，完成取指令和执行指令的控制。
处理器410中还可以设置存储器，用于存储指令和数据。在一些实施例中，处理器410中的存储器为高速缓冲存储器。该存储器可以保存处理器410刚用过或循环使用的指令或数据。如果处理器410需要再次使用该指令或数据，可从存储器中直接调用。避免了重复存取，减小了处理器410的等待时间，因而提高了系统的效率。
充电管理模块440用于从充电器接收充电输入。其中，充电器可以是无线充电器，也可以是有线充电器。在一些有线充电的实施例中，充电管理模块440可以通过USB接口430接收有线充电器的充电输入。在一些无线充电的实施例中，充电管理模块440可以通过终端设备100的无线充电线圈接收无线充电输入。充电管理模块440为电池442充电的同时，还可以通过电源管理模块441为电子设备供电。
电源管理模块441用于连接电池442，充电管理模块440与处理器410。电源管理模块441接收电池442和/或充电管理模块440的输入，为处理器410，内部存储器421，外部存储器，显示屏494，摄像头493，和无线通信模块460等供电。电源管理模块441还可以用于监测电池容量，电池循环次数，电池健康状态(漏电，阻抗)等参数。在其他一 些实施例中，电源管理模块441也可以设置于处理器410中。在另一些实施例中，电源管理模块441和充电管理模块440也可以设置于同一个器件中。
终端设备100的无线通信功能可以通过天线1，天线2，移动通信模块450，无线通信模块460，调制解调处理器以及基带处理器等实现。
天线1和天线2用于发射和接收电磁波信号。终端设备100中的每个天线可用于覆盖单个或多个通信频带。不同的天线还可以复用，以提高天线的利用率。例如：可以将天线1复用为无线局域网的分集天线。在另外一些实施例中，天线可以和调谐开关结合使用。
移动通信模块450可以提供应用在终端设备100上的包括2G/3G/4G/5G等无线通信的解决方案。移动通信模块450可以包括至少一个滤波器，开关，功率放大器，低噪声放大器(low noise amplifier，LNA)等。移动通信模块450可以由天线1接收电磁波，并对接收的电磁波进行滤波，放大等处理，传送至调制解调处理器进行解调。移动通信模块450还可以对经调制解调处理器调制后的信号放大，经天线1转为电磁波辐射出去。在一些实施例中，移动通信模块450的至少部分功能模块可以被设置于处理器410中。在一些实施例中，移动通信模块450的至少部分功能模块可以与处理器410的至少部分模块被设置在同一个器件中。
无线通信模块460可以提供应用在终端设备100上的包括无线局域网(wireless local area networks，WLAN)(如无线保真(wireless fidelity，Wi-Fi)网络)，蓝牙(bluetooth，BT)，全球导航卫星系统(global navigation satellite system，GNSS)，调频(frequency modulation，FM)，近距离无线通信技术(near field communication，NFC)，红外技术(infrared，IR)等无线通信的解决方案。无线通信模块460可以是集成至少一个通信处理模块的一个或多个器件。无线通信模块460经由天线2接收电磁波，将电磁波信号调频以及滤波处理，将处理后的信号发送到处理器410。无线通信模块460还可以从处理器410接收待发送的信号，对其进行调频，放大，经天线2转为电磁波辐射出去。
在一些实施例中，终端设备100的天线1和移动通信模块450耦合，天线2和无线通信模块460耦合，使得终端设备100可以通过无线通信技术与网络以及其他设备通信。无线通信技术可以包括全球移动通讯系统(global system for mobile communications，GSM)，通用分组无线服务(general packet radio service，GPRS)，码分多址接入(code division multiple access，CDMA)，宽带码分多址(wideband code division multiple access，WCDMA)，时分码分多址(time-division code division multiple access，TD-SCDMA)，长期演进(long term evolution，LTE)，BT，GNSS，WLAN，NFC，FM，和/或IR技术等。GNSS可以包括全球卫星定位系统(global positioning system，GPS)，全球导航卫星系统(global navigation satellite system，GLONASS)，北斗卫星导航系统(beidou navigation satellite system，BDS)，准天顶卫星系统(quasi-zenith satellite system，QZSS)和/或星基增强系统(satellite based augmentation systems，SBAS)。
终端设备100通过GPU，显示屏494，以及应用处理器等实现显示功能。GPU为图像处理的微处理器，连接显示屏494和应用处理器。GPU用于执行数学和几何计算，用于图形渲染。处理器410可包括一个或多个GPU，其执行程序指令以生成或改变显示信息。
显示屏494用于显示图像，视频等。
显示屏494包括显示面板。显示面板可以采用液晶显示屏(liquid crystal display，LCD)， 有机发光二极管(organic light-emitting diode，OLED)，有源矩阵有机发光二极体或主动矩阵有机发光二极体(active-matrix organic light emitting diode，AMOLED)，柔性发光二极管(flex light-emitting diode，FLED)，Miniled，MicroLed，Micro-oLed，量子点发光二极管(quantum dot light emitting diodes，QLED)等。
终端设备100可以通过ISP，摄像头493，视频编解码器，GPU，显示屏494以及应用处理器等实现拍摄功能。
终端设备100可以通过音频模块470，扬声器470A，受话器470B，麦克风470C，耳机接口470D，以及应用处理器等实现音频功能。例如音乐播放，录音等。
SIM卡接口495用于连接SIM卡。SIM卡可以通过插入SIM卡接口495，或从SIM卡接口495拔出，实现和终端设备100的接触和分离。终端设备100可以支持1个或N个SIM卡接口，N为大于1的正整数。SIM卡接口495可以支持Nano SIM卡，Micro SIM卡，SIM卡等。同一个SIM卡接口495可以同时插入多张卡。多张卡的类型可以相同，也可以不同。SIM卡接口495也可以兼容不同类型的SIM卡。SIM卡接口495也可以兼容外部存储卡。终端设备100通过SIM卡和网络交互，实现通话以及数据通信等功能。在一些实施例中，终端设备100采用eSIM，即：嵌入式SIM卡。eSIM卡可以嵌在终端设备100中，不能和终端设备100分离。
以下实施例中的方法均可以在具有上述硬件结构的终端设备100中实现。
可以理解的是，本实施例示意的结构并不构成对终端设备100的具体限定。在另一些实施例中，终端设备100可以包括比图示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。图示的部件可以以硬件，软件或软件和硬件的组合实现。例如，终端设备100还可以包括鼠标，键盘、画板等辅助设备。
终端设备100可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备；还可以包括用户单元(subscriber unit)、蜂窝电话(cellular phone)、智能电话(smart phone)、无线数据卡、个人数字助理(personal digital assistant，PDA)电脑、平板型电脑、无线调制解调器(modem)、手持设备(handheld)、膝上型电脑(laptop computer)、无绳电话(cordless phone)或者无线本地环路(wireless local loop，WLL)台、机器类型通信(machine type communication,MTC)终端、用户设备(user equipment，UE)，移动台(mobile station，MS)，终端设备(terminal device)或者中继用户设备等。其中，中继用户设备例如可以是5G家庭网关(residential gateway，RG)。
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“至少一个”是指一个或多个，“多个”是指两个或多于两个。“至少一种”是指一种或多种，“多种”是指两种或多于两种。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
为了便于理解，以下结合附图对本申请实施例提供的网络切片匹配方法进行具体介绍。
如图5所示，本申请实施例提供一种网络切片匹配方法，包括：
501、定义新的网络切片选择规则。
网络切片选择(network slice selection)规则属于URSP规则的一部分。例如，网络切 片选择规则可以包含在URSP规则中的路由选择描述符RSD中。即，定义新的网络切片选择规则也可以理解为定义新的URSP规则。
新的网络切片选择规则可以是指根据URSP规则中的网络切片指示信息(网络切片标识)确定应用程序(application)在终端设备对应的数据处理级别(也可以称为数据处理等级、数据处理方式、终端设备内部处理等级/方式等)、应用程序对应的网络切片(例如，第一网络切片)，以及支持第一网络切片的PDU session。即新的网络切片选择规则可以用于确定应用程序在终端设备对应的数据处理级别、应用程序对应的网络切片(例如，第一网络切片)，以及支持第一网络切片的PDU session。例如，终端设备根据新的网络切片选择规则可以确定第一应用程序在终端设备进行第一处理时延级别的处理，同时，终端设备可以将第一应用程序关联到支持第一网络切片的PDU session，第一网络切片的标识可以是S-NSSAI 1。
新的网络切片选择规则或新的URSP规则可以由标准组织(例如，3GPP)进行定义，或者，可以由运营商(例如，中国移动、中国联通、中国电信、中国广电等)定义。运营商可以将新的网络切片选择规则(或新的URSP规则)配置在网络侧和终端侧。其中，网络侧是指网络设备，例如可以包括gNB、AMF、SMF、PCF等网络设备(网元)。终端侧可以是指终端设备，例如可以为UE。或者，H-PCF(即归属地的PCF)可以通过AMF和gNB将新的网络切片选择规则(或新的URSP规则)配置给终端设备。例如，可以通过注册命令(registration command)消息配置新的网络切片选择规则(或新的URSP规则)。
新的网络切片选择规则可以对应三种可能的网络切片的指示方式，包括第一种可能的指示方式、第二种可能的指示方式和第三种可能的指示方式。其中，第一种可能的指示方式和第二种可能的指示方式是显示的指示方式，第三种可能的指示方式是隐式的指示方式。
第一种可能的指示方式：定义新的网络切片标识，新的网络切片标识表示新的网络切片类型。原有的网络切片标识仅可以用于指示应用程序对应的网络切片，以使终端设备将应用程序的流量关联到支持该网络切片的PDU session。新的网络切片标识不仅可以用于指示应用程序对应的网络切片，以使终端设备将应用程序的流量关联到支持该网络切片的PDU session，还可以指示应用程序对应的终端设备的数据处理级别，以便更好地满足业务需求。
示例性的，可以在S-NSSAI的结构中增加第一指示信息，例如可以在SD或SST中增加第一指示信息。第一指示信息例如可以是新的切片类型名称，内部切片(internal Slice，IS)参数等。第一指示信息用于指示应用程序在终端设备对应的数据处理级别。第一指示信息可以有多种取值，不同取值对应不同的数据处理级别。第一指示信息可以包括1个bit或多个bit。
其中，应用程序在终端设备对应的数据处理级别可以包括一种或多种处理优先级(比如：高中低不同的处理优先级，不同的处理优先级可以对应不同的网络传输通道)，一种或多种处理时延级别(比如：1ms，10ms，100ms等不同的等级，或，高中低不同的级别))，一种或多种处理速率级别(比如：1Mbps，10Mbps，100Mbps，1000Mbps等不同的处理级别，或，高中低不同的级别))，一种或多种处理安全级别(比如：普通，TEE，SE等不同的安全级别，或，高中低不同的安全级别)，一种或多种处理可靠性级别(比如：1个9，2个9，3个9，4个9，5个9等可靠级别，或高中低不同的可靠性安全级别)等。其中，X个9表 示在终端设备在1年时间的使用过程中，最多可能的业务中断时间，X为1、2、3、4、5等。可以理解的是，终端设备最多可能的业务中断时间越短，可靠性越高。例如，3个9表示终端设备最多可能的业务中断时间为：(1-99.9％)*365*24＝8.76小时，即终端设备在连续运行1年时间里最多可能的业务中断时间是8.76小时。其中，99.9％中包括3个9。4个9表示终端设备最多可能的业务中断时间为：(1-99.99％)*365*24＝0.876小时＝52.6分钟，即终端设备在连续运行1年时间里最多可能的业务中断时间是52.6分钟。其中，99.99％中包括4个9。
如表1所示，以第一指示信息包括2个bit为例，S-NSSAI 1中携带的第一指示信息为00，表示应用程序在终端设备对应的数据处理级别为第一处理优先级，同时终端设备将应用程序关联到支持S-NSSAI 1的PDU session；S-NSSAI 2中携带的第一指示信息为01，表示应用程序在终端设备对应的数据处理级别为第二处理优先级，同时终端设备将应用程序关联到支持S-NSSAI 2的PDU session；S-NSSAI 3中携带的第一指示信息为10，表示应用程序在终端设备对应的数据处理级别为第一处理时延级别，同时终端设备将应用程序关联到支持S-NSSAI 3的PDU session；S-NSSAI 4中携带的第一指示信息为11，表示应用程序在终端设备对应的数据处理级别为第二处理时延级别，同时终端设备将应用程序关联到支持S-NSSAI 4的PDU session。
其中，第一处理优先级与第二处理优先级不同。第一处理优先级可以高于第二处理优先级。例如，可以针对通话应用进行第一处理优先级的处理，针对游戏应用可以进行第一处理优先级的处理，当通话应用和游戏应用同时运行时，可以优先处理通话应用的数据流。第一处理时延级别与第二处理时延级别不同。第一处理时延级别高于第二处理时延级别，即第一处理时延级别对应的处理时延小于第二处理时延级别对应的处理时延。
表1
第二种可能的指示方式：可以在现有的网络切片标识的基础上，增加第二指示信息。例如，可以在SST、SD或NSSAI信息单元标识(Information Element Identifier，IEI)中增加第二指示信息。第二指示信息可以包括1个bit或多个bit。第二指示信息用于指示应用程序在终端设备对应的数据处理级别，该数据处理级别与网络切片类型或网络切片优先级是对应的。
示例性的，如表2所示，第一网络切片(S-NSSAI 1)的类型为低时延切片，第一网络切片的标识中增加第二指示信息，第二指示信息可以指示终端设备的数据处理级别为低时延处理级别。低时延处理级别是指终端设备内部对业务数据优先处理，比如，优先调度，优先排队，插队提前发送，优先发送。这样，当业务对应的网络切片是低时延切片时，终端设备内部对该业务的处理级别是低时延处理级别，可以保证该业务的业务需求(例如，低时延)。避免网络切片时延低而终端设备内部处理时延高导致业务体验不佳的问题，可 以充分发挥低时延网络切片的优势，满足业务需求。
又例如：第二网络切片的类型为高速率切片(S-NSSAI 2)，第二网络切片的标识中增加第二指示信息后，第二指示信息可以指示终端设备的数据处理级别为高速率处理级别。高速率处理级别是指终端设备内部调配较多的处理资源(如：内存(memory)资源，计算资源(CPU,GPU,NPU等))对业务数据进行处理。这样，当业务对应的网络切片是高速率切片时，终端设备内部对该业务的处理级别是高速率处理级别，可以保证该业务的业务需求(例如，高速率)。避免网络切片速率高而终端设备内部处理速率低导致业务体验不佳的问题，可以充分发挥高速率网络切片的优势，满足业务需求。
又例如：第三网络切片的类型为高安全切片(S-NSSAI 3)，第三网络切片的标识中增加第二指示信息，第二指示信息可以指示终端设备内部的处理级别为高安全处理级别。高安全处理级别可以是终端设备将业务数据放在高安全区(比如：TEE中，SE中)中处理，和/或终端设备对业务数据采用高加密的方式，以保证业务数据的安全。这样，当业务对应的网络切片是高安全切片时，终端设备内部对该业务的处理级别是高安全处理级别，可以保证该业务的业务需求(例如，高安全业务需求)。避免网络切片安全性高而终端设备内部处理安全性低导致业务体验不佳的问题，可以充分发挥高安全网络切片的优势，满足业务需求。
又例如：第四网络切片的类型为高可靠切片(S-NSSAI 4)，第四网络切片的标识中增加第二指示信息，第二指示信息可以指示终端设备内部的处理级别为高可靠处理级别。高可靠处理级别可以是终端设备将业务数据进行多次备份和/或多次传输，以保障业务数据的可靠性。这样，当业务对应的网络切片是高可靠切片时，终端设备内部对该业务的处理级别是高可靠处理级别，可以保证该业务的业务需求(例如，高可靠业务需求)。避免网络切片可靠性高而终端设备内部处理可靠性低导致业务体验不佳的问题，可以充分发挥高可靠网络切片的优势，满足业务需求。
又例如：第五网络切片的类型为大带宽切片(S-NSSAI 5)，第五网络切片的标识中增加第二指示信息，第二指示信息可以指示终端设备内部的处理级别为大带宽处理级别。大带宽处理级别例如可以是终端设备采用较大带宽(例如，80M/120M)的频段传输业务数据，或者可以是终端设备同时使用多个频段传输数据。这样，当业务对应的网络切片是大带宽切片时，终端设备内部对该业务的处理级别是大带宽处理级别，可以保证该业务的业务需求(例如，大带宽业务需求)。避免网络切片可靠性高而终端设备内部处理带宽小导致业务体验不佳的问题，可以充分发挥大带宽网络切片的优势，满足业务需求。
表2
第三种可能的指示方式：通过现有的网络切片标识隐式指示应用程序在终端设备对应 的数据处理级别。即，不增加指示信息，通过隐式的方式指示应用程序在终端设备对应的数据处理级别。
如表3所示，例如第一网络切片(S-NSSAI 1)为低时延切片，隐式指示终端设备的数据处理级别为低时延处理级别。第二网络切片(S-NSSAI 2)为高速率切片，隐式指示终端设备的数据处理级别为高速率处理级别。第三网络切片(S-NSSAI 3)为高安全切片，隐式指示终端设备的数据处理级别为高安全处理级别。第四网络切片(S-NSSAI 4)为高可靠切片，隐式指示终端设备的数据处理级别为高可靠处理级别。
表3
又例如，如表4所示，假设网络切片优先级可以包括三个等级，分别为高、中、低。终端设备的处理优先级也可以包括三个等级，分别为高、中、低。第一网络切片(S-NSSAI1)的优先级为高，第一网络切片对应的终端设备的处理优先级也高；第二网络切片(S-NSSAI 1)的优先级为中，第一网络切片对应的终端设备的处理优先级也为中；第一网络切片(S-NSSAI 1)的优先级为低，第一网络切片对应的终端设备的处理优先级也为低。即，当应用程序对应的网络切片的优先级为高等级(即网络切片为高优先级)时，终端设备内部对该应用程序进行处理时的处理优先级也为高等级，从而保证该应用程序的业务需求(例如，低时延、高可靠性等)。当应用程序对应的网络切片的优先级为中等级时，终端设备内部对该应用程序进行处理时的处理优先级也为中等级，尽量保证该应用程序的业务需求(例如，低时延等)。当应用程序对应的网络切片的优先级为低等级时，终端设备内部对该应用程序进行处理时的处理优先级也可以为低等级，以合理满足该应用程序的业务需求。
表4
又例如，网络切片优先级可以包括两个等级，分别为高和低。终端设备的处理优先级也可以包括两个等级，分别为高和低。如表5所示，第一网络切片(S-NSSAI 1)的优先级为高，第一网络切片对应的终端设备的处理优先级也为高；第二网络切片(S-NSSAI 1)的优先级为低，第一网络切片对应的终端设备的处理优先级也为低。
表5

当然，网络切片优先级还可以包括更多等级，例如可以包括四个、五个、六个等级，本申请不做限定。终端设备的处理优先级也可以包括更多等级，例如可以包括四个、五个、六个等级，本申请不做限定。
上文是以网络切片优先级和终端设备的处理优先级一一对应的情况说明网络切片优先级和终端设备的处理优先级的映射关系的。在一种可能的情况中，网络切片优先级包括N个等级，终端设备的处理优先级包括M个等级，N与M不相同，则一个网络切片优先级等级可以对应多个处理优先级等级，或者，多个网络切片优先级等级可以对应一个处理优先级等级，本申请不做限定。
例如，如表6所示，网络切片优先级可以包括三个等级，分别为高、中、低。终端设备的处理优先级可以包括两个等级，分别为高、低。第一网络切片(S-NSSAI 1)的优先级为高，第一网络切片对应的终端设备的处理优先级也为高；第二网络切片(S-NSSAI 2)的优先级为中，第二网络切片对应的终端设备的处理优先级为低；第三网络切片(S-NSSAI3)的优先级为低，第三网络切片对应的终端设备的处理优先级为低。即多个网络切片优先级等级可以对应一个终端设备的处理优先级等级。
表6
在一种可能的设计中，网络切片优先级可以基于网络切片的类型确定。例如，uRLLC、eMBB、mMTC等类型的网络切片的优先级依次从高到低。
以应用程序为第一应用程序为例，根据新的网络切片选择规则(即根据新的URSP规则中的网络切片标识)，可以确定第一应用程序在终端设备进行第一数据处理级别(例如，低时延处理级别、高速率处理级别等)的数据处理，第一应用程序对应的网络切片是第一网络切片，并且，终端设备可以将第一应用程序关联到支持第一网络切片的PDU session，所述第一网络切片用第一S-NSSAI进行标识。
其中，第一应用程序在终端设备进行第一数据处理级别的数据处理是指第一应用程序的数据流(traffic of application)在终端设备进行第一数据处理级别的数据处理。
其中，终端设备将第一应用程序关联到支持第一网络切片的PDU session是指，终端设备将第一应用程序的数据流通过支持第一网络切片的PDU session进行传输或路由(traffic of the application shall be routed via a PDU Session supporting any of the included S-NSSAIs)。
在一种可能的设计中，H-PCF(即归属地的PCF)可以定义新的URSP规则，并通过AMF和gNB将新的URSP规则转发给终端设备。或者运营商可以向终端设备配置新的URSP规则。例如，如图6中的(a)所示，新的URSP规则可以是在URSP的流量描述符中增加新定义的参数(比如：内部切片(internal Slice，IS))这一参数。或者，如图6中的(b)所示，新的URSP规则可以是在URSP的RSD中增加新定义的参数IS。IS可以对应一个或多个取值，指示不同的网络切片优先级和终端设备的处理优先级的映射关系。例如，IS的 取值为第一值(例如，01)时，表示高等级的网络切片优先级和高等级的终端设备的处理优先级的映射关系。即表示Traffic descriptor匹配的业务对应高等级的网络切片优先级和高等级的终端设备的处理优先级。IS的取值为第二值(例如，11)时，表示低等级的网络切片优先级和低等级的终端设备的处理优先级的映射关系。即表示Traffic descriptor匹配的业务对应低等级的网络切片优先级和低等级的终端设备的处理优先级。
在一种可能的设计中，不同取值的IS可以对应不同的S-NSSAI。例如，IS1(即IS的取值为第一值)对应一个S-NSSAI(例如，S-NSSAI-1)，IS2(即IS的取值为第二值)对应另一个S-NSSAI(例如，S-NSSAI-2)。假设S-NSSAI-1的优先级是高等级的，IS1指示高等级的切片优先级对应高等级的终端设备的处理优先级，即当业务对应S-NSSAI-1时，终端设备对该业务的内部处理优先级也是高等级的。假设S-NSSAI-2的优先级是低等级的，IS2指示低等级的切片优先级对应低等级的终端设备的处理优先级，即当业务对应S-NSSAI-2时，终端设备对该业务的内部处理优先级也是低等级的。
在另一种可能的设计中，可以定义多个新的S-NSSAI，新的S-NSSAI的组成结构中可以新增与IS有关的信元。例如，如图7中的(a)所示，新的S-NSSAI的SD中可以包括IS。或者，如图7中的(b)所示，新的S-NSSAI的SST中可以包括IS。
不同的S-NSSAI可以对应不同取值的IS。例如，IS1(即IS的取值为第一值)对应一个新的S-NSSAI(例如，S-NSSAI-1)，IS2(即IS的取值为第二值)对应另一个新的S-NSSAI(例如，S-NSSAI-2)。假设S-NSSAI-1的优先级是高等级的，IS1指示高等级的切片优先级对应高等级的终端设备的处理优先级，即当业务对应(匹配)S-NSSAI-1时，终端设备对该业务的内部处理优先级也是高等级的。假设S-NSSAI-2的优先级是低等级的，IS2指示低等级的切片优先级对应低等级的终端设备的处理优先级，即当业务对应S-NSSAI-2时，终端设备对该业务的内部处理优先级也是低等级的。
502、终端设备向gNB发送注册请求消息。
终端设备执行业务前，可以在网络上进行注册，即可以向gNB发送注册请求消息(registration request)。注册请求消息中可以携带请求的NSSAI(Requested NSSAI)。即终端设备可以向网络侧请求可在当前PLMN及当前注册区域下可使用的网络切片。
其中，请求的NSSAI可以包括终端设备确定的至少一个S-NSSAI。“请求的NSSAI”所包含的NSSAI，可在“配置的NSSAI”、“允许的NSSAI”或“默认配置的NSSAI”进行选择。“请求的NSSAI”不包含任何当前被网络拒绝的S-NSSAI。
需要说明的是，注册请求消息中携带的网络切片标识(即至少一个S-NSSAI)可以是上文所述的三种指示方式之一的网络切片标识。即注册请求消息中可以携带新的网络切片标识，该新的网络切片标识中携带第一指示信息，第一指示信息用于指示应用程序在终端设备对应的数据处理级别。或者，注册请求消息中可以携带现有的网络切片标识和第二指示信息，第二指示信息用于指示应用程序在终端设备对应的数据处理级别。或者，注册请求消息中可以携带现有的网络切片标识，该现有的网络切片标识可以隐式指示终端设备的数据处理级别。
gNB接收到来自终端设备的注册请求消息后，可以向AMF转发该注册请求消息。如果终端设备处于CM-CONNECTED态，gNB可以基于终端设备的N2连接向AMF转发注册请求消息。如果终端设备处于CM-IDLE态，终端设备在与RAN建立连接时未包含“请 求的NSSAI”和全局唯一的AMF标识符(globally uniq终端设备AMF identifier，GUAMI)，则gNB可以将注册请求消息转发到默认AMF。
AMF可以基于“签约的S-NSSAIs”验证“请求的NSSAI”中的S-NSSAI是否被允许。其中，“签约的S-NSSAIs”可以是AMF从统一数据管理UDM网元获取的。AMF可以确定一个注册区域，以便该注册区域的“允许的NSSAI”的所有S-NSSAI在注册区域的所有跟踪区域中都可用，然后返回给终端设备该“允许的NSSAI”。可选的，AMF向终端设备返回“允许的NSSAI”到“签约的S-NSSAIs”的映射。可选的，AMF可以返回一个或多个“拒绝的S-NSSAI”以及其每个S-NSSAI的拒绝原因。如果S-NSSAI被拒绝原因值指示网络切片特定的身份验证和授权失败或撤销，则终端设备可以基于本地策略重新尝试请求该S-NSSAI。
AMF向gNB发送注册接受消息(registration accept)，注册接受消息表示注册请求已被AMF接受。gNB从AMF接收到注册接受消息后，可以将注册接受消息转发给终端设备，即可以执行步骤503。
503、gNB向终端设备发送注册接受消息(registration accept)。
注册接受消息中可以包括允许的NSSAI(Allowed NSSAI)，Allowed NSSAI表示终端设备请求的NSSAI中被网络允许的S-NSSAI。
可选的，注册接受消息中还可以包括拒绝的NSSAI(Rejected NSSAI)，拒绝的NSSAI表示终端设备请求的NSSAI中网络拒绝的S-NSSAI。
504、终端设备根据应用程序的相关信息执行URSP规则的匹配。
终端设备获取应用程序的相关信息(corresponding information from the application)，或终端设备识别到应用程序的相关信息。可选的，应用程序可以向终端设备中执行URSP规则的处理模块发送应用程序的相关信息。或者，执行URSP规则的处理模块可以从特定内存获取应用程序的相关信息。即应用程序的相关信息被提前配置到了终端设备，终端设备可以提前获取应用程序的相关信息，本申请不做限定。
其中，应用程序的相关信息用于终端设备执行URSP规则(新的URSP规则)匹配。示例性的，应用程序的相关信息可以包括应用程序的标识(APP ID)。可选的，应用程序的相关信息可以包括应用程序希望使用的网络切片信息，比如第一网络切片标识(S-NSSAI1)。第一网络切片标识可以是上文所述的三种指示方式之一的网络切片标识。可选的，应用程序的相关信息可以包括第一信息，第一信息用于指示应用程序希望使用的网络切片信息(即第一信息与应用程序希望使用的网络切片信息具有映射关系)，比如第一网络切片标识(S-NSSAI 1)。
终端设备配置的URSP规则(即新的URSP规则)可以包括1个或多个。多个URSP规则可以对应不同的优先级。终端设备可以按URSP规则的优先级顺序对应用程序的相关信息进行匹配。例如，假设终端设备配置的多个URSP规则包括URSP1和URSP2。URSP1是指示低时延处理级别的URSP规则，URSP2是指示高速率处理级别的URSP规则。URSP1的优先级高于URSP2的优先级，则终端设备可以先将应用程序的相关信息与URSP1进行匹配。若不匹配，再将应用程序的相关信息与URSP2进行匹配。
本申请实施例中，终端设备将应用程序的相关信息与URSP规则进行匹配具体是将应用程序的相关信息与URSP规则中的component进行匹配，例如可以是将应用程序的相关信息与URSP规则中的Traffic descriptor进行匹配。或者，可以是将应用程序的相关信息与 URSP规则中的Route Selection Descriptor进行匹配。
如果应用程序的相关信息与URSP1相匹配，则将应用程序关联到URSP 1的RSD对应的PDU session(例如，PDU session1)，即终端设备将应用程序的数据流路由(route)到PDU session1上。其中，URSP 1的RSD对应的PDU session是指支持URSP 1的RSD中的参数的PDU session，URSP 1的RSD中的参数包括S-NSSAI、DNN、SSCmode等。其中，RSD中的S-NSSAI可以是上文所述的三种指示方式之一的网络切片标识。
示例性的，如图8所示，终端设备配置或获取的一个或多个URSP规则(新的URSP规则)可以包括URSP1、URSP2、URSP3、默认URSP规则等。URSP1包括流量描述符、3个RSD。流量描述符包括应用程序标识(例如，King of Glory)；RSD1包括S-NSSAI-1，RSD2包括S-NSSAI-2，RSD3包括S-NSSAI-3。URSP2包括流量描述符、2个RSD。流量描述符包括应用程序标识(例如，King of Glory)；RSD4包括S-NSSAI-4，RSD5包括S-NSSAI-5。URSP3包括流量描述符、3个RSD。流量描述符包括应用程序标识(例如，V2X)；RSD6包括S-NSSAI-6，RSD7包括S-NSSAI-7，RSD8包括S-NSSAI-8。默认URSP包括通配流量描述符和通配RSD。通配流量描述符可以匹配全部业务，通配RSD包括通配切片，通配切片的类型是eMBB。
当前，终端设备发起云游戏应用(例如，)，对应的应用程序标识为King of Glory，若对应的应用程序标识与URSP1中的流量描述符匹配， 希望使用的网络切片信息(例如，S-NSSAI 1)与RSD1中的网络切片标识匹配，终端设备确定与当前待发起业务匹配的URSP规则为URSP1。
终端设备判断RSD1指示的网络切片(S-NSSAI 1)是否属于当前网络的Allowed NSSAI。若RSD1指示的网络切片(例如，S-NSSAI 1)属于当前网络的Allowed NSSAI，可以将 关联到支持URSP1中的RSD1的PDU session。需要说明的是，RSD1指示的网络切片(例如，S-NSSAI 1)不仅可以指示对应的网络切片，以使终端设备将 的流量关联到支持该网络切片的PDU session，还可以指示对应的终端设备的数据处理级别(例如，低时延处理级别)，可以更好地满足业务需求。这样可以避免网络切片时延低，而终端设备内部处理时延高导致业务体验不佳，可以充分发挥网络切片的优势。
在一种可能的设计中，URSP规则中的流量描述符或RSD中可以包括一个用于指示终端设备的数据处理级别的参数。应用程序的相关信息中也可以携带一个用于指示终端设备的数据处理级别的参数。终端设备执行URSP规则匹配的过程中，可以对应用程序的相关信息中携带的用于指示终端设备的数据处理级别的参数和URSP规则中的用于指示终端设备的数据处理级别的参数进行匹配。
示例性的，以URSP规则中的RSD中包括一个用于指示终端设备的数据处理级别的参数(例如，可以是IS)为例对URSP匹配过程进行说明。IS用于指示应用程序在终端设备对应的数据处理级别。应用程序在终端设备对应的数据处理级别可以参考上文的相关描述，在此不做赘述。
如图9所示，终端设备配置或获取的一个或多个URSP规则可以包括URSP1、URSP2、URSP3、默认URSP规则等。URSP1包括流量描述符、3个RSD。流量描述符包括应用程序标识(例如，King of Glory)；RSD1包括S-NSSAI-1和IS(例如，IS1)，RSD2包括S-NSSAI-2 和IS(例如，IS2)，RSD3包括S-NSSAI-3和IS(例如，IS3)。URSP2包括流量描述符、2个RSD。流量描述符包括应用程序标识(例如，King of Glory)；RSD4包括S-NSSAI-4和IS(例如，IS4)，RSD5包括S-NSSAI-5和IS(例如，IS5)。URSP3包括流量描述符、3个RSD。流量描述符包括应用程序标识(例如，V2X)；RSD6包括S-NSSAI-6和IS(例如，IS6)，RSD7包括S-NSSAI-7和IS(例如，IS7)，RSD8包括S-NSSAI-8和IS(例如，IS8)。默认URSP包括通配流量描述符和通配RSD。通配流量描述符可以匹配全部业务，通配RSD包括通配切片，通配切片的类型是eMBB。
当前，终端设备发起云游戏应用程序(例如，)，对应的应用程序标识为King of Glory，对应的IS为IS1，若对应的应用程序标识与URSP1中的流量描述符匹配，对应的IS与RSD1中的IS匹配，希望使用的网络切片信息与RSD1中的网络切片标识匹配，终端设备确定与当前待发起业务匹配的URSP规则为URSP1。
终端设备判断RSD1指示的网络切片(S-NSSAI 1)是否属于当前网络的Allowed NSSAI。若RSD1指示的网络切片(例如，S-NSSAI 1)属于当前网络的Allowed NSSAI，可以将 关联到支持URSP1中的RSD1的PDU session。需要说明的是，URSP1中的RSD1中的网络切片标识(例如，S-NSSAI 1)可以指示对应的网络切片，以使终端设备将的流量关联到支持该网络切片的PDU session，URSP1中的RSD1中的IS1可以指示对应的终端设备的数据处理级别(例如，低时延处理级别)，可以更好地满足业务需求。这样可以避免网络切片时延低，而终端设备内部处理时延高导致业务体验不佳，可以充分发挥网络切片的优势。
在另一些实施例中，终端设备在根据应用程序的相关信息执行URSP匹配时还可能采用其他方式，如根据待发起业务对应的域名信息(例如，全限定域名(fully qualified domain name，FQDN))、目的服务器IP地址信息等执行URSP匹配，或是直接由modem层执行上述匹配动作而无需应用层参与，本申请实施例对此不做限定。
另外，若一个或多个URSP规则中与当前待发起业务(或当前应用程序)匹配的URSP规则对应的一个或多个S-NSSAI均不属于当前网络的Allowed NSSAI(即不被网络支持)，停止URSP匹配；或者，若一个或多个RSD中与当前待发起业务匹配的RSD对应的一个或多个S-NSSAI均不属于当前网络的Allowed NSSAI，停止URSP匹配。
505、终端设备将应用程序关联到PDU会话。
在一种可能的设计中，如果已经存在一个PDU session支持应用程序希望使用的网络切片标识(例如，S-NSSAI 1)，终端设备将应用程序关联到该PDU session，即终端设备将应用程序的数据流路由(route)到该PDU session上。如果不存在一个PDU session支持应用程序希望使用的网络切片标识(例如，S-NSSAI 1)，终端设备发起支持S-NSSAI 1的PDU session的建立，以便将应用程序关联到建立的PDU session。
其中，PDU session具体建立过程包括如下步骤：
S1、终端设备向AMF发送PDU会话建立请求。
终端设备可以通过非接入层(Non-access stratum，NAS)消息向AMF发送PDU会话建立请求(PDU session establishment request)。
其中，PDU会话建立请求中可以包括PDU会话ID(PDU session ID)，PDU会话类 型(PDU Session type)，SSC Mode，DNN，S-NSSAI(业务对应的S-NSSAI)等参数。其中，PDU会话建立请求中的S-NSSAI可以是上文所述的三种指示方式之一的网络切片标识。
其中，PDU会话请求消息中携带的S-NSSAI经无线网被转发到AMF。AMF对PDU会话请求消息中的S-NSSAI进行检查，并根据网络中各个SMF所支持的切片能力情况，选择相应的SMF，并将该会话建立请求转发给SMF。
S2、AMF向SMF发送PDU会话创建请求(PDU session create request)。
AMF可以通过HTTP2 POST向SMF发送PDU会话创建请求。PDU会话创建请求中可以包含SUPI，DNN，PDU Session ID，S-NSSAI，Request Type等参数。
SMF可以进行PDU会话的上下文的建立。SMF可以向UDM获取用户响应的签约信息，然后向UPF和RAN、终端设备下发策略控制消息，由UPF和RAN、终端设备建立PDU会话的连接。
S3、SMF向AMF发送会话创建响应(PDU session create response)。
SMF确定PDU会话连接建立完成后，可以向AMF发送会话创建响应，指示PDU会话建立成功。
S4、AMF向终端设备发送PDU会话建立接受(PDU session establishment accept)。
AMF向终端设备回复会话建立请求响应，指示PDU会话建立成功。终端设备将应用程序关联到新建立的PDU session，即终端设备将应用程序的数据流路由(route)在所述新建立的PDU session上。
另外，如果终端设备发送的PDU Session Establishment Request被网络侧拒绝，即PDU会话建立失败，则终端设备重新匹配其他URSP规则，并发起基于重新匹配的URSP规则发起PDU session的建立。
基于本申请实施例提供的方法，终端设备可以将应用程序的相关信息与至少一个URSP规则进行匹配，若有URSP规则(例如，第一URSP规则)与应用程序的相关信息匹配，可以根据第一URSP规则中的网络切片标识(第一网络切片标识)指示的数据处理级别对应用程序的数据流进行处理。这样，终端设备可以使用第一网络切片标识对应的网络切片传输应用程序的数据流，同时基于第一网络切片标识指示的数据处理级别对该应用程序的数据流进行处理，即可以通过网络切片和终端设备的数据处理级别共同保证业务数据的传输和处理性能，能够满足不同业务的业务需求。
本申请实施例还提供一种芯片系统，如图10所示，该芯片系统包括至少一个处理器1001和至少一个接口电路1002。处理器1001和接口电路1002可通过线路互联。例如，接口电路1002可用于从其它装置(例如，终端设备的存储器)接收信号。又例如，接口电路1002可用于向其它装置(例如处理器1001)发送信号。
例如，接口电路1002可读取终端设备中存储器中存储的指令，并将该指令发送给处理器1001。当所述指令被处理器1001执行时，可使得终端设备(如图4所示的终端设备100)执行上述实施例中的各个步骤。
当然，该芯片系统还可以包含其他分立器件，本申请实施例对此不作具体限定。
本申请实施例还提供一种计算机可读存储介质，该计算机可读存储介质包括计算机指令，当所述计算机指令在终端设备(如图4所示的终端设备100)上运行时，使得终端设 备100执行上述方法实施例中终端设备执行的各个功能或者步骤，使得网络设备执行上述方法实施例中网络设备执行的各个功能或者步骤。
本申请实施例还提供一种计算机程序产品，当所述计算机程序产品在计算机上运行时，使得所述计算机执行上述方法实施例中终端设备执行的各个功能或者步骤。
本申请实施例还提供了一种处理装置，所述处理装置可以按照功能划分为不同的逻辑单元或模块，各单元或模块执行不同的功能，以使得所述处理装置执行上述方法实施例中终端设备或网络设备执行的各个功能或者步骤。
通过以上实施方式的描述，所属领域的技术人员可以清楚地了解到，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个装置，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是一个物理单元或多个物理单元，即可以位于一个地方，或者也可以分布到多个不同地方。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个可读取存储介质中。基于这样的理解，本申请实施例的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该软件产品存储在一个存储介质中，包括若干指令用以使得一个设备(可以是单片机，芯片等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上内容，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何在本申请揭露的技术范围内的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (14)

  1. 一种网络切片匹配方法，其特征在于，包括：
    终端设备获取应用程序的相关信息；
    所述终端设备将所述应用程序的所述相关信息与至少一个路由选择策略URSP规则进行匹配，所述至少一个URSP规则包括第一URSP规则，所述第一URSP规则包括第一网络切片标识，所述第一网络切片标识显示或隐式指示所述终端设备的数据处理级别；
    若所述第一URSP规则与所述应用程序的所述相关信息匹配，根据所述第一网络切片标识指示的所述数据处理级别对所述应用程序的数据流进行处理。
  2. 根据权利要求1所述的方法，其特征在于，
    所述应用程序的所述相关信息包括所述第一网络切片标识。
  3. 根据权利要求1所述的方法，其特征在于，
    所述应用程序的所述相关信息包括第一信息，所述第一信息用于指示所述第一网络切片标识。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述第一URSP规则包括第一网络切片标识包括：
    所述第一URSP规则包括第一路由选择描述符RSD，所述第一RSD包括所述第一网络切片标识。
  5. 根据权利要求1-4任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备根据所述第一URSP规则确定所述应用程序对应的协议数据单元PDU会话。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，所述第一网络切片标识显示指示所述终端设备的数据处理级别包括：
    所述第一网络切片标识包括第一指示信息，所述第一指示信息用于指示所述终端设备的数据处理级别；
    其中，所述第一指示信息包括多个取值，所述多个取值中的每个取值对应一种数据处理级别，不同取值对应的数据处理级别不同。
  7. 根据权利要求1-5任一项所述的方法，其特征在于，所述第一网络切片标识显示指示所述终端设备的数据处理级别包括：
    所述第一网络切片标识包括第二指示信息，所述第二指示信息用于指示所述终端设备的数据处理级别，所述终端设备的数据处理级别与所述第一网络切片标识对应的网络切片类型或网络切片优先级具有对应关系。
  8. 根据权利要求2或3所述的方法，其特征在于，
    所述第一网络切片标识包括切片服务类型SST和切片区分符号SD，所述SST或所述SD中包括所述第一指示信息或所述第二指示信息。
  9. 根据权利要求1-8任一项所述的方法，其特征在于，
    所述终端设备的数据处理级别包括至少一种处理优先级，处理时延级别，处理速率级别，处理安全级别，处理可靠性级别、处理带宽级别。
  10. 根据权利要求1-9任一项所述的方法，其特征在于，所述终端设备获取应用程序的相关信息之前，所述方法还包括：
    所述终端设备向第一网络设备发送注册请求消息，所述注册请求消息携带所述第一网络切片标识；
    所述终端设备接收来自所述第一网络设备的注册接受消息，所述注册接受消息包括允许接入的切片的信息。
  11. 根据权利要求1-10任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备向接入和移动性管理功能网元AMF网元发送PDU会话请求消息，所述PDU会话请求消息包括所述第一网络切片标识。
  12. 根据权利要求1-11任一项所述的方法，其特征在于，
    所述应用程序的所述相关信息还包括所述应用程序的标识，所述第一URSP规则还包括流量描述符，所述流量描述符与所述应用程序的标识匹配。
  13. 一种计算机可读存储介质，其特征在于，包括计算机指令；
    当所述计算机指令在终端设备上运行时，使得所述终端设备执行如权利要求1-12中任一项所述的方法。
  14. 一种终端设备，其特征在于，所述终端设备包括：无线通信模块、存储器和一个或多个处理器；所述无线通信模块、所述存储器与所述处理器耦合；
    其中，所述存储器用于存储计算机程序代码，所述计算机程序代码包括计算机指令；当所述计算机指令被所述处理器执行时，使得所述终端设备执行如权利要求1-12中任一项所述的方法。
PCT/CN2023/114807 2022-11-25 2023-08-24 一种网络切片匹配方法和装置 WO2024109221A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211493965.XA CN118102479A (zh) 2022-11-25 2022-11-25 一种网络切片匹配方法和装置
CN202211493965.X 2022-11-25

Publications (1)

Publication Number Publication Date
WO2024109221A1 true WO2024109221A1 (zh) 2024-05-30

Family

ID=91140926

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/114807 WO2024109221A1 (zh) 2022-11-25 2023-08-24 一种网络切片匹配方法和装置

Country Status (2)

Country Link
CN (1) CN118102479A (zh)
WO (1) WO2024109221A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113708947A (zh) * 2020-05-21 2021-11-26 华为技术有限公司 切片接入方法、装置及系统
WO2021253394A1 (en) * 2020-06-19 2021-12-23 Qualcomm Incorporated Public land mobile network search for user equipment route selection policy rule
CN114009097A (zh) * 2019-06-21 2022-02-01 Oppo广东移动通信有限公司 一种选择网络的方法、设备及存储介质
WO2022067684A1 (en) * 2020-09-30 2022-04-07 Qualcomm Incorporated Dynamic network slicing resource reselection
WO2022111113A1 (zh) * 2020-11-30 2022-06-02 中兴通讯股份有限公司 频点切换方法、终端、基站和存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114009097A (zh) * 2019-06-21 2022-02-01 Oppo广东移动通信有限公司 一种选择网络的方法、设备及存储介质
CN113708947A (zh) * 2020-05-21 2021-11-26 华为技术有限公司 切片接入方法、装置及系统
WO2021253394A1 (en) * 2020-06-19 2021-12-23 Qualcomm Incorporated Public land mobile network search for user equipment route selection policy rule
WO2022067684A1 (en) * 2020-09-30 2022-04-07 Qualcomm Incorporated Dynamic network slicing resource reselection
WO2022111113A1 (zh) * 2020-11-30 2022-06-02 中兴通讯股份有限公司 频点切换方法、终端、基站和存储介质

Also Published As

Publication number Publication date
CN118102479A (zh) 2024-05-28

Similar Documents

Publication Publication Date Title
WO2020187052A1 (zh) 一种网络切片选择方法及装置
WO2021204003A1 (zh) 一种临近服务的业务处理方法、设备及系统
CN102124778B (zh) 用于第三代合作伙伴计划多个网络间服务质量连续性的机制
CN112566149B (zh) 配置业务的方法、通信装置和通信系统
US11979450B2 (en) Communication method and apparatus
WO2020147030A1 (zh) 一种小区注册方法及终端设备
WO2018228517A1 (zh) 一种接入控制的方法、网络设备以及终端设备
CN114079937B (zh) 一种通信方法和通信装置以及系统
US20230096402A1 (en) Service obtaining method and apparatus, and communication device and readable storage medium
US20240022469A1 (en) Method for determining edge configuration server and apparatus
WO2024092664A1 (zh) 会话区分方法、装置
WO2022105711A1 (zh) Ims注册方法、终端设备及存储介质
WO2021227600A1 (zh) 一种网络切片控制方法及通信装置
WO2024088195A1 (zh) 执行结果上报方法、接收方法、终端及网络侧设备
WO2021163901A1 (zh) 一种会话处理方法及其装置
WO2024109221A1 (zh) 一种网络切片匹配方法和装置
US20220287014A1 (en) Resource allocation methods and apparatuses, message frame processing methods, apparatuses and storage mediums
US20230004839A1 (en) Model coordination method and apparatus
WO2023006400A1 (en) Communication network arrangement
WO2024124949A1 (zh) 通信方法及终端设备
CN115696463A (zh) 多终端联合会话管理方法、网络侧设备及终端
CN118102382B (zh) 一种数据处理方法及相关设备
WO2024065134A1 (zh) 终端设备状态辅助运营方法、装置
WO2024208029A1 (zh) 一种通信方法及通信装置
WO2023213226A1 (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: 23893315

Country of ref document: EP

Kind code of ref document: A1