A network slice matching method and apparatus

Abstract

The embodiment of the application provides a network slice matching method and device, relates to the field of communication, can satisfy different service requirements (for example, low-latency service requirement, high-reliability service requirement and the like), and can improve user experience. The method is as follows: a terminal device acquires related information of an application program; the terminal device matches the related information of the application program with at least one 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 shows or implicitly indicates a data processing level of the terminal device; and if the first URSP rule matches the related information of the application program, the data flow of the application program is processed according to the data processing level indicated by the first network slice identifier.

Description

Technical Field

[0001] This application relates to the field of communications, and more particularly to a network slice matching method and apparatus. Background Technology

[0002] To meet the differentiated network requirements of 5G mobile communication systems, the 3rd Generation Partnership Project (3GPP) proposed network slicing technology. This technology allows a physical network to be abstractly divided into multiple network slices, each of which constitutes an end-to-end logical network.

[0003] Network slices are logically isolated from each other, and different network slices can meet different business needs. For example, for services requiring low latency, a network slice that supports low latency can be used to execute that service.

[0004] However, for services requiring low latency (such as cloud gaming), even if network slices that support low latency are used to execute the service, the overall latency of the service may still increase due to other reasons (such as high internal processing latency of the terminal), which may not meet the service requirements and result in a poor user experience. Summary of the Invention

[0005] This application provides a network slice matching method and apparatus that can meet different service requirements (e.g., low latency service requirements, high reliability service requirements, etc.) and improve user experience.

[0006] In a first aspect, embodiments of this application provide a network slice matching method, comprising: a terminal device obtaining relevant information of an application; the terminal device matching the relevant information of the application with at least one Routing Policy Request (URSP) rule, wherein the at least one URSP rule includes a first URSP rule, the first URSP rule includes a first network slice identifier, the first network slice identifier explicitly or implicitly indicating the data processing level of the terminal device; if the first URSP rule matches the relevant information of the application, the application's data stream is processed according to the data processing level indicated by the first network slice identifier.

[0007] Based on the method provided in this application embodiment, the terminal device can match application-related information with at least one URSP rule. If a first URSP rule matches the application-related information, the application's data stream 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 application's data stream, and simultaneously process the application's data stream based on the data processing level indicated by the first network slice identifier. This means that the transmission and processing performance of business data can be guaranteed through both network slicing and the terminal device's data processing level, thus meeting the business needs of different services.

[0008] In one possible implementation, the application's relevant information includes a first network slice identifier. That is, the application's relevant information may include network slice information that the application wishes to use, such as the first network slice identifier. The first URSP rule matches the application's relevant information; that is, the first network slice identifier included in the first URSP rule is the same as the first network slice identifier in the application's relevant information.

[0009] In one possible implementation, the application's relevant information includes first information indicating a first network slice identifier. That is, the first information has a mapping relationship with the network slice information the application wishes to use. A first URSP rule matches the application's relevant information; specifically, 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 application's relevant information.

[0010] In one possible implementation, the first URSP rule includes a first network slice identifier, comprising: a first routing descriptor (RSD) and the first RSD including the first network slice identifier. The first URSP rule is matched with relevant information in the application; that is, the first network slice identifier in the first RSD of the first URSP rule is the same as the first network slice identifier in the relevant information of the application.

[0011] In one possible implementation, the method further includes: the terminal device determining the Protocol Data Unit (PDU) session corresponding to the application according to a 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 aforementioned parameters in the first URSP rule.

[0012] In one possible implementation, the first network slice identifier indicating the data processing level of the terminal device includes: the first network slice identifier includes first indication information, which indicates the data processing level of the terminal device; wherein, the first indication information includes multiple values, each of which corresponds to a data processing level, and different values ​​correspond to different data processing levels. Thus, the data processing level of the terminal device can be determined based on the first indication information in the first network slice identifier. The terminal device can use the network slice corresponding to the first network slice identifier to transmit the application's data stream, and simultaneously process the application's data stream based on the data processing level indicated by the first network slice identifier. This means that the transmission and processing performance of business data can be guaranteed through the combined effect of network slicing and the terminal device's data processing level, meeting the business needs of different services.

[0013] In one possible implementation, the first network slice identifier indicates the data processing level of the terminal device by including second indication information. This second indication information indicates 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. For example, if the first network slice identifier indicates 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. A low-latency processing level means that the terminal device prioritizes processing service data internally, such as priority scheduling, priority queuing, early transmission, and priority sending. Thus, when the network slice corresponding to a service is a low-latency slice, the terminal device's internal processing level for that service is also a low-latency processing level, ensuring the service's requirements (e.g., low latency). This avoids the problem of poor service experience due to low network slice latency but high internal processing latency of the terminal device, fully leveraging the advantages of low-latency network slices to meet service needs.

[0014] In one possible implementation, the first network slice identifier includes a slice service type (SST) and a slice distinguishing symbol (SD), wherein the SST or SD includes first indication information or second indication information.

[0015] In one possible implementation, the data processing level of the terminal device includes at least one processing priority, processing latency level, processing rate level, processing security level, processing reliability level, and processing bandwidth level.

[0016] In one possible implementation, before the terminal device obtains the application's relevant information, the method further includes: the terminal device sending a registration request message to a first network device, the registration request message carrying a first network slice identifier; and the terminal device receiving a registration acceptance message from the first network device, the registration acceptance message including information about the slices allowed for access. The registration acceptance message may include allowed NSSAIs (Allowed NSSAIs), where Allowed NSSAIs represent S-NSSAIs among the NSSAIs requested by the terminal device that are allowed by the network.

[0017] In one possible implementation, the method further includes: the terminal device sending a PDU session request message to the Access and Mobility Management Function (AMF) network element, the PDU session request message including 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.

[0018] In one possible implementation, the application-related information also includes the application's identifier, and the first URSP rule also includes a traffic descriptor that matches the application's identifier.

[0019] Secondly, this application provides a computer program product that, when run on a computer, causes the computer to perform the methods described in any of the above aspects and any of their possible design schemes.

[0020] Thirdly, this application provides a computer-readable storage medium including computer instructions. When the computer instructions are executed on a terminal device (such as a mobile phone), they cause the terminal device to perform the method described in the first aspect and any possible implementation thereof.

[0021] Fourthly, embodiments of this application provide a communication device including a processor and a memory coupled together. The memory stores program instructions, which, when executed by the processor, cause the device to implement the methods described in any of the above aspects and any possible design schemes. The device may be a terminal device; or it may be a component of a terminal device, such as a chip.

[0022] Fifthly, this application provides a chip system including one or more interface circuits and one or more processors. The interface circuits and processors are interconnected via lines.

[0023] The aforementioned chip system can be applied to terminal devices that include a communication module and a memory. The interface circuit is used to receive signals from the memory of the first terminal device and send the received signals to the processor, the signals including computer instructions stored in the memory. When the processor executes the computer instructions, the terminal device can perform the methods described as described in any of the above aspects and any of their possible design embodiments.

[0024] It is understood that the beneficial effects 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 can be referred to as the beneficial effects in the first aspect and any of its possible design embodiments, which will not be repeated here. Attached Figure Description

[0025] Figure 1 A schematic diagram of the composition structure of an S-NSSAI provided in an embodiment of this application;

[0026] Figure 2 A schematic diagram of the composition structure of a URSP provided for an embodiment of this application;

[0027] Figure 3 A schematic diagram of a system architecture provided for an embodiment of this application;

[0028] Figure 4 This is a schematic diagram of the hardware structure of a terminal device provided in an embodiment of this application;

[0029] Figure 5 This is a schematic diagram of a method process provided in an embodiment of this application;

[0030] Figure 6 A schematic diagram of the composition structure of another URSP provided in the embodiments of this application;

[0031] Figure 7 A schematic diagram of the composition structure of another S-NSSAI provided in this application embodiment;

[0032] Figure 8 A schematic diagram illustrating the matching of URSP rules provided in an embodiment of this application;

[0033] Figure 9 A schematic diagram illustrating the matching of URSP rules provided in an embodiment of this application;

[0034] Figure 10 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. Detailed Implementation

[0035] To ensure clarity and conciseness in the description of the following embodiments, a brief introduction to the relevant concepts or technologies is given first:

[0036] 1. Network Slicing: A physical network can be abstractly divided into multiple network slices, and each network slice can constitute an end-to-end logical network. Network slices are logically isolated from each other and do not affect each other.

[0037] Typically, to meet different communication needs, network slicing can be divided into several types. These include, but are not limited to, enhanced mobile broad band (eMBB), massive machine type (mMTC), and ultra-reliability and low latency (uRLLC).

[0038] Different types of network slices have different network characteristics. For example, eMBB network slices are required to support high bandwidth and low latency services; mMTC network slices are required to support massive access with low bandwidth; and uRLLC slices are required to have high reliability and low latency.

[0039] As can be seen, the types of applications supported, end-to-end latency, and maximum speed of a single terminal are all characteristic attributes of network slicing, and these characteristic attributes depend on the design of the slice.

[0040] With the introduction of network slicing technology, operators can provide "dedicated" networks for users with different business needs, ensuring high-quality service levels and meeting differentiated business requirements; while users can also use more powerful application products, further stimulating the development of new industry application markets; achieving the goals of improving network resource utilization efficiency, optimizing operator network construction investment, and building a flexible and agile 5G network.

[0041] 2. Single network slice selection assistance information (S-NSSAI) is used to uniquely identify a network slice.

[0042] like Figure 1As shown, the structure of an S-NSSAI can include a slice service type (SST) and a slice differentiator (SD). The SST refers to the expected network slice behavior in terms of functionality and services. The SD is optional information that complements the slice / service type to distinguish multiple network slices of the same slice / service type. For example, the SST can include 8 bits, and the SD can include 24 bits.

[0043] 3. Network Slice Selection Assistance Information (NSSAI): NSSAI is used to indicate a set of one or more S-NSSAIs. Accordingly, NSSAI can be used to represent one or more network slices.

[0044] 4. Packet Data Unit (PDU): 5G networks transmit data between terminal devices (e.g., user equipment (UE)) and external networks in the form of data packets. These user data packets are usually called PDUs.

[0045] 5. PDU Session: A PDU session is a session service that enables PDU connectivity between the UE and the data network (DN), and is identified by the PDU session ID.

[0046] 6. User Routing Selection Policy (URSP): Typically, when operators create the required network slices for customers on the physical infrastructure of the communication network based on customer orders, they often sign a Service Level Agreement (SLA) with the customer for the network slices, according to service requirements. Within an operator's public land mobile network (PLMN), not the entire network necessarily supports the same set of network slices. Operators can divide different slice sets based on regions or even individual base stations. Thus, different regional networks may correspond to different slices. Therefore, in non-roaming scenarios, users may only be able to access the required slice through a portion of their home network, or in roaming scenarios, they may only be able to access the required slice through a portion of the visited network.

[0047] Currently, the standard defines URSP to address user routing issues. It is primarily used to determine the PDU session parameters required by different applications (APPs) or services, such as network slices, data network name (DNN), and session service continuity mode (SSC mode).

[0048] Through URSP, the terminal can determine the corresponding PDU session parameters according to the network requirements of the APP or service, and establish a PDU session based on the parameters. Then, the data of the APP or service is transmitted through the established session.

[0049] like Figure 2 As shown, a URSP may include a traffic descriptor (TD) and one or more route selection descriptors (RSDs). Of course, a URSP may also include other parameters, which are not limited in this application.

[0050] Traffic descriptors are used to match service information (application identifiers, flow identifiers, service identifiers, etc.), distinguishing different services through application identifiers or other types of identifiers. For example, a terminal modem can match the application identifier (APP ID) with the traffic descriptors in each of one or more URSP rules according to their priority from high to low. Traffic descriptors come in various types, such as Application descriptors (which can consist of an operating system identifier (OSId) and an application identifier (OSAppId), for example, those in the Android operating system). This can be represented as android+com.wechat, IP descriptors (such as the destination IP address corresponding to the initiating service), etc. Once the traffic descriptor matching the application is determined, the PDU session for transmitting the application's traffic is determined based on the RSD corresponding to that traffic descriptor (i.e., the RSD in the URSP rule corresponding to that traffic descriptor). The RSD includes parameters such as DNN, S-NSSAI, and SSCmode. The PDU session for transmitting the application's traffic supports the DNN, S-NSSAI, and SSCmode parameters in the corresponding RSD (the RSD corresponding to the application's matching traffic descriptor). In other words, after determining the traffic descriptor matching the application, the PDU session for transmitting the application's traffic can be determined based on the RSD corresponding to the matching traffic descriptor.

[0051] 7. URSP Matching: When the UE determines that it needs to initiate a specific service / application, it first matches the service / application to be initiated with the traffic descriptor in the URSP rule according to the priority order of the URSP rules.

[0052] If a specific URSP rule is matched (this URSP rule may also be a default URSP rule (also known as a wildcard URSP rule), such as a traffic descriptor in the form of match-all), 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 roaming scenarios, the terminal needs to determine whether the slice S-NSSAI belongs to the current Allowed NSSAI of the visited network; in non-roaming scenarios, the terminal needs to determine whether the slice S-NSSAI is within the current Allowed NSSAI of the home network. If the S-NSSAI is not in the Allowed NSSAI, the UE will continue to match subsequent URSP rules or subsequent RSDs according to URSP priority / RSD priority until it is determined that the slice S-NSSAI allowed for the service appears in the Allowed NSSAI and is accepted by the network side.

[0053] Currently, operators can leverage network slicing technology to provide "dedicated" networks for users with different service needs, ensuring high-quality service levels and meeting diverse business requirements. For example, services requiring low latency can utilize network slices that support low latency. However, for services requiring low latency (such as cloud gaming), even using network slices that support low latency may still lead to increased overall latency due to other factors (e.g., high internal processing latency at the terminal), failing to meet service requirements and resulting in a poor user experience.

[0054] Taking cloud gaming as an example, cloud gaming utilizes real-time audio and video streaming technology. The server sends real-time audio and video streams to the client, while the client sends control command streams to the server. The server then applies these control commands to the game. Cloud gaming can include, for example, action games, fighting games, multiplayer online battle arena (MOBA) games, first-person shooters, racing games, and more. Cloud gaming has high requirements for response latency, bandwidth, and jitter. In other words, the business requirements of cloud gaming are: low latency, high bandwidth, and minimal or no jitter. Therefore, network slices that support low latency, high bandwidth, and minimal or no jitter can be matched to cloud gaming to best meet its business needs.

[0055] However, cloud gaming's network loop involves processes such as server-side game rendering, audio and video encoding, network transmission, and client-side audio and video decoding and rendering, all of which involve a certain degree of latency. Currently, even selecting network slices that meet low-latency requirements can only reduce latency during network transmission, and it is difficult to reduce latency in other processes (such as client-side audio and video decoding and rendering), thus making it difficult to guarantee low latency from end to end in cloud gaming.

[0056] For example, suppose network slice A has a low latency of 20ms, network slice B has a medium latency of 50ms, terminal internal processing priority C has a high latency of 100ms, and terminal internal processing priority D has a low latency of 15ms. For services requiring low latency (e.g., cloud gaming), even if the low-latency network slice A is selected, if the terminal internal processing priority is C (i.e., latency reaches 100ms), the overall latency of cloud gaming will increase. It may even be worse than selecting the higher-latency network slice B and the terminal internal processing priority D. That is, the latency of A+C > the latency of B+D, which fails to leverage the advantages of network slicing and makes it difficult to meet the low-latency requirements of cloud gaming.

[0057] To address the aforementioned issues, this application provides a network slice matching method that can better meet different business needs (e.g., low latency business needs, high reliability business needs, etc.) and improve user experience.

[0058] The network slice matching method provided in this application is applied to communication systems that use network slices for communication. For example, 5G systems, or subsequent evolution systems or other systems.

[0059] See Figure 3This is an exemplary architecture of a communication system applicable to the embodiments of this application. The communication system includes: an authentication server function (AUSF), unified data management (UDM), a user data repository (UDR), a core access and mobility management function (AMF), a session management function (SMF), a policy control function (PCF), an application function (AF) / network exposure function (NEF), a user plane function (UPF), an access network (AN), and other network elements, as well as a data access network (DN) and a user equipment (UE). The AN includes a wired access network and a radio access network (RAN). The RAN may include a next-generation node (gNB).

[0060] The UE accesses the AN via wireless or wired means. Wireless access can be via Wi-Fi or cellular networks (e.g., E-UTRA, NR). The UE communicates with the AMF via N1; the AN communicates with the UPF via N3 and the AMF via N2; the UPF communicates with the SMF via N4 and the DN via N6; the AMF communicates with the UDM via N8; the SMF communicates with the AMF via N11, the UDM via N10, and the PCF via N7; the AMF communicates with the AUSF via N12 and the AUSF via N13. The AF communicates with the PCF via N5. The UDM communicates with the UDR via N35. The UDM communicates with the AF / NEF via N52. The UDR communicates with the PCF via N36. The AMF communicates with the PCF via N15. Figure 3 In the system shown, AF / NEF refers to the interaction between AF and core network elements via NEF.

[0061] Figure 3 In the system shown, some network elements have the following functions:

[0062] Application Provider (AF): Primarily conveys application-side requests to the network side, such as QoS requirements or user state event subscriptions. AFs can be third-party functional entities or application services deployed by operators, such as IMS voice call services. For third-party application functional entities, when interacting with the core network, authorization processing can also be performed through the Network Application Provider (NEF). For example, a third-party AF sends a request message to the NEF, and the NEF determines whether the AF is allowed to send the request message. If the verification is successful, the NEF forwards the request message to the corresponding PCF or UDM.

[0063] UDM: Primarily responsible for managing contract data, user access authorization, and other functions.

[0064] UDR: Primarily responsible for storing and retrieving data types such as contract data, strategy data, and application data.

[0065] In addition, UDR can add corresponding S-NSSAI to the user's Subscribed NSSAI, and also add the contractual values ​​such as bandwidth and QoS guarantees that the user is allowed to use under that SNSSAI.

[0066] PCF: Primarily responsible for policy control functions such as billing at the session and service flow levels, quality of service (QoS) bandwidth assurance, mobility management, and UE policy decisions. In this architecture, the PCFs connected to the AMF and SMF correspond to the AM PCF (PCF for access and mobility control) and SM PCF (PCF for session management), respectively. In actual deployment scenarios, the AM PCF and SM PCF may not be the same PCF entity.

[0067] SMF: Main functions include session management, execution of control policies issued by PCF, selection of UPF, and allocation of UE Internet Protocol (IP) addresses.

[0068] AMF: Primarily responsible for mobility management, access authentication / authorization, and other functions. Additionally, it is responsible for transmitting user policies between the UE and the PCF.

[0069] UPF: As the interface between the data network and the UPF, it performs functions such as user plane data forwarding, session / flow-level billing statistics, and bandwidth limiting.

[0070] AN: corresponds to different access networks, such as wired access, wireless base station access, and other methods.

[0071] in, Figure 3 In the architecture shown, some interface functions are described as follows:

[0072] 1. N7: The interface between PCF and SMF, used to issue PDU session granularity and business data flow granularity control policies.

[0073] 2. N15: The interface between PCF and AMF, used to issue UE policies and access control related policies.

[0074] 3. N5: The interface between AF and PCF, used for issuing application service requests and reporting network events.

[0075] 4. N4: The interface between SMF and UPF, used to transmit information between the control plane and the user plane, including the distribution of forwarding rules, QoS control rules, traffic statistics rules, etc. from the control plane to the user plane, as well as the reporting of information from the user plane.

[0076] 5. N11: The interface between SMF and AMF, used to transmit PDU session tunnel information between AN and UPF, transmit control messages sent to UE, and transmit radio resource control information sent to AN, etc.

[0077] 6. N2: The interface between AMF and RAN, used to transmit radio bearer control information from the core network side to AN.

[0078] 7. N1: The interface between AMF and UE, access-independent, used to transmit QoS control rules to UE, etc.

[0079] 8. N8: The interface between AMF and UDM, used by AMF to obtain access and mobility management related subscription data and authentication data from UDM, as well as by AMF to register UE's current mobility management information with UDM.

[0080] 9. N9: Used for user plane data forwarding between UPFs.

[0081] 10. N10: The interface between SMF and UDM, used by SMF to obtain session management-related subscription data from UDM, and by SMF to register UE current session-related information with UDM.

[0082] 11. N35: The interface between UDM and UDR, used by UDM to obtain user subscription data information from UDR.

[0083] 12. N36: The interface between PCF and UDR, used by PCF to obtain policy-related contract data and application data related information from UDR.

[0084] Optional, Figure 3The names of the network elements and the interfaces between them are just examples. In the actual implementation, the names of the network elements or the interfaces between them may be other names, or the network elements may also be referred to as entities. This application does not make specific limitations on this. Figure 3 All or some of the network elements in the network can be physical network elements or virtual network elements, and no limitation is made here.

[0085] Optionally, this architecture may also include other network elements, such as operation administration management (OAM) network elements, network slice selection function (NSSF), and network repository function (NRF). This application embodiment does not impose any limitations on this.

[0086] Furthermore, Figure 3 The 5G communication system shown includes systems in non-roaming scenarios and systems in roaming scenarios. Optionally, the system in each scenario can be a service-based interface system or a reference point-based system. Specific descriptions of service-based interface and reference point-based systems can be found in existing technologies and will not be repeated here.

[0087] Furthermore, the network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0088] like Figure 4 The diagram shown is a structural schematic of a terminal device 100 provided in an embodiment of this application. The terminal device 100 may be a first electronic device. Figure 4As shown, 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, a headphone jack 470D, a sensor module 480, buttons 490, a motor 491, an indicator 492, a camera 493, a display screen 494, and a subscriber identification module (SIM) card interface 495, etc. The sensor module 480 may include a pressure sensor 480A, a gyroscope sensor 480B, a barometric pressure sensor 480C, a magnetic sensor 480D, an accelerometer 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.

[0089] Processor 410 may include one or more processing units, such as: application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU), etc. The different processing units may be independent devices or integrated into one or more processors.

[0090] The controller can serve as the nerve center and command center of the terminal device 100. The controller can generate operation control signals based on the instruction opcode and timing signals to control the fetching and execution of instructions.

[0091] The processor 410 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 410 is a cache memory. This memory can store instructions or data that the processor 410 has just used or that are used repeatedly. If the processor 410 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 410, and thus improves the efficiency of the system.

[0092] The charging management module 440 receives charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 440 receives charging input from the wired charger via a USB interface 430. In some wireless charging embodiments, the charging management module 440 receives wireless charging input via the wireless charging coil of the terminal device 100. While charging the battery 442, the charging management module 440 can also supply power to the electronic device via the power management module 441.

[0093] The power management module 441 connects 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, providing power to the processor 410, internal memory 421, external memory, display screen 494, camera 493, and wireless communication module 460. The power management module 441 can also monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage current, impedance). In some other embodiments, the power management module 441 may also be located within the processor 410. In other embodiments, the power management module 441 and the charging management module 440 may be housed in the same device.

[0094] 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, etc.

[0095] 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 one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with a tuning switch.

[0096] The mobile communication module 450 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the terminal device 100. The mobile communication module 450 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 450 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 450 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 450 may be housed in the processor 410. In some embodiments, at least some functional modules of the mobile communication module 450 and at least some modules of the processor 410 may be housed in the same device.

[0097] The wireless communication module 460 can provide solutions for wireless communication applications on the terminal device 100, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. 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 antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 410. The wireless communication module 460 can also receive signals to be transmitted from processor 410, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0098] In some embodiments, antenna 1 of terminal device 100 is coupled to mobile communication module 450, and antenna 2 is coupled to wireless communication module 460, enabling terminal device 100 to communicate with networks and other devices via wireless communication technology. Wireless communication technologies 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 technologies, etc. GNSS can include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and / or satellite-based augmentation systems (SBAS).

[0099] The terminal device 100 implements display functions through a GPU, a display screen 494, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 494 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. The processor 410 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0100] Display screen 494 is used to display images, videos, etc.

[0101] The display screen 494 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a Mini LED, a MicroLED, a Micro-OLED, a quantum dot light-emitting diode (QLED), etc.

[0102] Terminal device 100 can perform shooting functions through ISP, camera 493, video codec, GPU, display 494 and application processor.

[0103] Terminal device 100 can implement audio functions, such as music playback and recording, through audio module 470, speaker 470A, receiver 470B, microphone 470C, headphone jack 470D, and application processor.

[0104] The SIM card interface 495 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 495 to make contact with and separate from the terminal device 100. The terminal device 100 can support one 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 simultaneously. The multiple cards can be of the same or different types. The SIM card interface 495 is also compatible with different types of SIM cards. The SIM card interface 495 is also compatible with external memory cards. The terminal device 100 interacts with the network through the SIM card to realize functions such as calls and data communication. In some embodiments, 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.

[0105] The methods described in the following embodiments can all be implemented in the terminal device 100 having the above-described hardware structure.

[0106] It is understood that the structure illustrated in this embodiment does not constitute a specific limitation on the terminal device 100. In other embodiments, the terminal device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware. For example, the terminal device 100 may also include auxiliary devices such as a mouse, keyboard, and drawing board.

[0107] Terminal equipment 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 capabilities; it may also include subscriber units, cellular phones, smartphones, wireless data cards, personal digital assistant (PDA) computers, tablet computers, wireless modems, handheld devices, laptop computers, cordless phones, wireless local loop (WLL) stations, machine-type communication (MTC) terminals, user equipment (UE), mobile stations (MS), terminal devices, or relay user equipment, etc. Relay user equipment may, for example, be a 5G residential gateway (RG).

[0108] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of this application, unless otherwise stated, "at least one" refers to one or more, and "multiple" refers to two or more. Furthermore, to facilitate a clear description of the technical solutions of the embodiments of this application, the terms "first," "second," etc., are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first," "second," etc., do not limit the quantity or execution order, and that "first," "second," etc., do not necessarily imply differences.

[0109] For ease of understanding, the network slice matching method provided in the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0110] like Figure 5As shown, this application provides a network slice matching method, including:

[0111] 501. Define new network slice selection rules.

[0112] Network slice selection rules are a part of URSP rules. For example, a network slice selection rule can be included in the routing descriptor (RSD) of a URSP rule. That is, defining a new network slice selection rule can also be understood as defining a new URSP rule.

[0113] The new network slice selection rule can refer to determining the data processing level (also known as data processing grade, data processing method, or internal processing level / method of the terminal device) of an application on 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, based on the network slice indication information (network slice identifier) ​​in the URSP rule. In other words, the new network slice selection rule can be used to determine the data processing level of an application on 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. For example, based on the new network slice selection rule, the terminal device can determine that the first application is processed at the first processing latency level on the terminal device. Simultaneously, the terminal device can associate the first application with the PDU session supporting the first network slice, and the identifier of the first network slice can be S-NSSAI 1.

[0114] New network slice selection rules or new URSP rules can be defined by standards organizations (e.g., 3GPP) or by operators (e.g., China Mobile, China Unicom, China Telecom, China Broadcasting Network, etc.). Operators can configure new network slice selection rules (or new URSP rules) on both the network and terminal sides. The network side refers to network equipment, such as gNB, AMF, SMF, PCF, etc. The terminal side refers to terminal equipment, such as the UE. Alternatively, the H-PCF (i.e., the home PCF) can configure new network slice selection rules (or new URSP rules) to terminal equipment through the AMF and gNB. For example, new network slice selection rules (or new URSP rules) can be configured through registration command messages.

[0115] The new network slice selection rules can correspond to three possible network slice indication methods, including the first possible indication method, the second possible indication method, and the third possible indication method. Among them, the first and second possible indication methods are explicit indication methods, and the third possible indication method is implicit indication method.

[0116] The first possible approach is to define a new network slice identifier, which represents a new network slice type. The existing network slice identifier could only be used to indicate the network slice corresponding to an application, enabling terminal devices to associate application traffic with a PDU session that supports that network slice. The new network slice identifier can not only indicate the network slice corresponding to an application, enabling terminal devices to associate application traffic with a PDU session that supports that network slice, but also indicate the data processing level of the terminal device corresponding to the application, in order to better meet business needs.

[0117] For example, first indication information can be added to the structure of S-NSSAI, such as to SD or SST. The first indication information may be, for example, a new slice type name, internal slice (IS) parameters, etc. The first indication information is used to indicate the data processing level of the application on the terminal device. The first indication information can have multiple values, each corresponding to a different data processing level. The first indication information may include one bit or multiple bits.

[0118] The application's data processing level on the terminal device can include one or more processing priorities (e.g., high, medium, and low processing priorities, which can correspond to different network transmission channels), one or more processing latency levels (e.g., 1ms, 10ms, 100ms, etc., or different levels of high, medium, and low), one or more processing speed levels (e.g., 1Mbps, 10Mbps, 100Mbps, 1000Mbps, etc., or different levels of high, medium, and low), one or more processing security levels (e.g., normal, TEE, SE, etc., or different security levels of high, medium, and low), and one or more processing reliability levels (e.g., 1 nine, 2 nines, 3 nines, 4 nines, 5 nines, etc., or different reliability and security levels of high, medium, and low). Here, X nines represent the maximum possible service interruption time during the terminal device's one-year usage period, 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 device, the higher the reliability. For example, three nines represent the maximum possible service interruption time for a terminal device as (1 - 99.9%) * 365 * 24 = 8.76 hours, meaning the maximum possible service interruption time for the terminal device in one year of continuous operation is 8.76 hours. Here, 99.9% includes three nines. Four nines represent the maximum possible service interruption time for a terminal device as (1 - 99.99%) * 365 * 24 = 0.876 hours = 52.6 minutes, meaning the maximum possible service interruption time for the terminal device in one year of continuous operation is 52.6 minutes. Here, 99.99% includes four nines.

[0119] As shown in Table 1, taking the first indication information including 2 bits as an example, the first indication information carried in S-NSSAI 1 is 00, indicating that the application's data processing level corresponding to the terminal device is the first processing priority, and the terminal device associates the application with a PDU session that supports S-NSSAI 1; the first indication information carried in S-NSSAI 2 is 01, indicating that the application's data processing level corresponding to the terminal device is the second processing priority, and the terminal device associates the application with a PDU session that supports S-NSSAI 2; the first indication information carried in S-NSSAI 3 is 10, indicating that the application's data processing level corresponding to the terminal device is the first processing latency level, and the terminal device associates the application with a PDU session that supports S-NSSAI 3; the first indication information carried in S-NSSAI 4 is 11, indicating that the application's data processing level corresponding to the terminal device is the second processing latency level, and the terminal device associates the application with a PDU session that supports S-NSSAI 4.

[0120] The first processing priority differs from the second processing priority. The first processing priority can be higher than the second processing priority. For example, the first processing priority can be applied to both call applications and game applications. When both applications run simultaneously, the call application's data stream can be processed first. The first processing latency level also differs from the second processing latency level. The first processing latency level is higher than the second processing latency level; that is, the processing latency corresponding to the first latency level is less than the processing latency corresponding to the second latency level.

[0121] Table 1

[0122]

[0123] A second possible indication method is to add secondary indication information to the existing network slice identifier. For example, secondary indication information can be added to the SST, SD, or NSSAI Information Element Identifier (IEI). The secondary indication information can include one or more bits. This secondary indication information is used to indicate the data processing level of the application on the terminal device, which corresponds to the network slice type or network slice priority.

[0124] For example, as shown in Table 2, the first network slice (S-NSSAI 1) is a low-latency slice. A second indication is added to the identifier of the first network slice. This second indication indicates that the data processing level of the terminal device is a low-latency processing level. Low-latency processing level means that the terminal device prioritizes processing of service data, such as priority scheduling, priority queuing, early transmission, and priority sending. Thus, when the network slice corresponding to a service is a low-latency slice, the terminal device's internal processing level for that service is also low-latency, ensuring the service's requirements (e.g., low latency). This avoids the problem of poor service experience due to low network slice latency but high internal processing latency of the terminal device, fully leveraging the advantages of low-latency network slices to meet service needs.

[0125] For example, if the second network slice is a high-speed slice (S-NSSAI 2), adding a second indication to the second network slice's identifier allows the terminal device to specify a high-speed processing level for its data processing. A high-speed processing level means that the terminal device allocates more processing resources (such as memory and computing resources like CPU, GPU, and NPU) to process the service data. Thus, when the network slice corresponding to a service is a high-speed slice, the terminal device's internal processing level for that service is also high-speed, ensuring the service's requirements (e.g., high speed) are met. This avoids the problem of poor service experience due to a high network slice speed but a low internal processing speed of the terminal device, fully leveraging the advantages of high-speed network slices to meet service needs.

[0126] For example, if the third network slice is a high-security slice (S-NSSAI 3), a second indication is added to the identifier of the third network slice. This second indication indicates that the processing level inside the terminal device is a high-security processing level. A high-security processing level can mean that the terminal device processes service data in a high-security zone (e.g., in the TEE or SE), and / or that the terminal device uses high encryption to ensure the security of the service data. Thus, when the network slice corresponding to a service is a high-security slice, the processing level of that service inside the terminal device is also a high-security processing level, ensuring the service's requirements (e.g., high-security service requirements). This avoids the problem of poor service experience due to high network slice security but low internal processing security of the terminal device, fully leveraging the advantages of high-security network slices to meet service needs.

[0127] For example, if the fourth network slice is a high-reliability slice (S-NSSAI 4), a second indication is added to the identifier of the fourth network slice. This second indication indicates that the processing level inside the terminal device is a high-reliability processing level. A high-reliability processing level means that the terminal device performs multiple backups and / or multiple transmissions of service data to ensure the reliability of the service data. Thus, when the network slice corresponding to a service is a high-reliability slice, the processing level of that service inside the terminal device is also a high-reliability processing level, guaranteeing the service requirements (e.g., high-reliability service requirements). This avoids the problem of poor service experience due to high network slice reliability but low internal processing reliability of the terminal device, fully leveraging the advantages of high-reliability network slices to meet service needs.

[0128] For example, if the fifth network slice is a high-bandwidth slice (S-NSSAI 5), a second indicator is added to the identifier of the fifth network slice. This second indicator indicates that the processing level within the terminal device is high-bandwidth processing. High-bandwidth processing could mean that the terminal device uses a larger bandwidth frequency band (e.g., 80MHz / 120MHz) to transmit service data, or that the terminal device uses multiple frequency bands simultaneously for data transmission. Thus, when the network slice corresponding to a service is a high-bandwidth slice, the terminal device's internal processing level for that service is also high-bandwidth processing, ensuring the service's requirements (e.g., high-bandwidth service requirements) are met. This avoids the problem of poor service experience due to high network slice reliability but limited internal processing bandwidth of the terminal device, fully leveraging the advantages of high-bandwidth network slices to meet service needs.

[0129] Table 2

[0130]

[0131] The third possible indication method is to implicitly indicate the application's data processing level on the terminal device using existing network slice identifiers. That is, without adding additional indication information, the application's data processing level on the terminal device is indicated implicitly.

[0132] As shown in Table 3, for example, the first network slice (S-NSSAI 1) is a low-latency slice, implicitly indicating that the data processing level of the terminal device is low-latency processing. The second network slice (S-NSSAI 2) is a high-speed slice, implicitly indicating that the data processing level of the terminal device is high-speed processing. The third network slice (S-NSSAI 3) is a high-security slice, implicitly indicating that the data processing level of the terminal device is high-security processing. The fourth network slice (S-NSSAI 4) is a high-reliability slice, implicitly indicating that the data processing level of the terminal device is high-reliability processing.

[0133] Table 3

[0134]

[0135] For example, as shown in Table 4, assume that network slice priorities can include three levels: high, medium, and low. The processing priorities of terminal devices can also include three levels: high, medium, and low. If the first network slice (S-NSSAI 1) has a high priority, the processing priority of the terminal device corresponding to the first network slice is also high; if the second network slice (S-NSSAI 1) has a medium priority, the processing priority of the terminal device corresponding to the first network slice is also medium; if the first network slice (S-NSSAI 1) has a low priority, the processing priority of the terminal device corresponding to the first network slice is also low. That is, when the network slice corresponding to an application has a high priority (i.e., the network slice is of high priority), the processing priority of the application within the terminal device is also high, thus ensuring the application's business requirements (e.g., low latency, high reliability). When the network slice corresponding to an application has a medium priority, the processing priority of the application within the terminal device is also medium, trying to ensure the application's business requirements (e.g., low latency). When the network slice corresponding to an application has a low priority, the processing priority of the application within the terminal device can also be low, so as to reasonably meet the application's business needs.

[0136] Table 4

[0137] S-NSSAI 1 high high S-NSSAI 2 middle middle S-NSSAI 3 Low Low

[0138] For example, network slice priority can include two levels: high and low. Terminal device processing priority can also include two levels: high and low. As shown in Table 5, the first network slice (S-NSSAI 1) has a high priority, and the terminal device corresponding to the first network slice also has a high processing priority; the second network slice (S-NSSAI 1) has a low priority, and the terminal device corresponding to the first network slice also has a low processing priority.

[0139] Table 5

[0140] S-NSSAI 1 high high S-NSSAI 2 Low Low

[0141] Of course, network slicing priority can include more levels, such as four, five, or six levels, and this application does not limit this. The processing priority of terminal devices can also include more levels, such as four, five, or six levels, and this application does not limit this.

[0142] The above describes the mapping relationship between network slice priorities and terminal device processing priorities using a one-to-one correspondence. In one possible scenario, network slice priorities include N levels, and terminal device processing priorities include M levels, where N and M are not the same. In this case, 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. This application does not impose any limitations on this.

[0143] For example, as shown in Table 6, network slice priorities can include three levels: high, medium, and low. Terminal device processing priorities can include two levels: high and low. The first network slice (S-NSSAI 1) has a high priority, and the terminal device corresponding to the first network slice also has a high processing priority; the second network slice (S-NSSAI 2) has a medium priority, and the terminal device corresponding to the second network slice has a low processing priority; the third network slice (S-NSSAI 3) has a low priority, and the terminal device corresponding to the third network slice also has a low processing priority. That is, multiple network slice priority levels can correspond to a single terminal device's processing priority level.

[0144] Table 6

[0145] S-NSSAI 1 high high S-NSSAI 2 middle Low S-NSSAI 3 Low Low

[0146] In one possible design, network slice priority can be determined based on the type of network slice. For example, network slices of types such as uRLLC, eMBB, and mMTC have priorities from high to low.

[0147] Taking the application as the first application as an example, according to the new network slice selection rules (i.e., according to the network slice identifier in the new URSP rules), it can be determined that the first application performs data processing at the first data processing level (e.g., low latency processing level, high speed processing level, etc.) on the terminal device. The network slice corresponding to the first application is the first network slice. Furthermore, the terminal device can associate the first application with the PDUsession that supports the first network slice. The first network slice is identified by the first S-NSSAI.

[0148] Wherein, the first application performing data processing at the first level on the terminal device refers to the first application's data stream (traffic of application) performing data processing at the first level on the terminal device.

[0149] In this context, "the terminal device associates the first application with a PDU session supporting the first network slice" means that the terminal device transmits or routes the data stream of the first application through a PDU session supporting the first network slice.

[0150] In one possible design, the H-PCF (i.e., the home PCF) can define new URSP rules and forward them to the terminal equipment via the AMF and gNB. Alternatively, the operator can configure new URSP rules for the terminal equipment. For example, ... Figure 6 As shown in (a), a new URSP rule can be created by adding a newly defined parameter (e.g., internal slice (IS)) to the URSP traffic descriptor. Alternatively, as... Figure 6 As shown in (b), the new URSP rule can be achieved by adding a newly defined parameter IS to the URSP RSD. IS can correspond to one or more values, indicating the mapping relationship between different network slice priorities and terminal device processing priorities. For example, when IS takes the first value (e.g., 01), it indicates a mapping relationship between high-level network slice priorities and high-level terminal device processing priorities. That is, it means that the traffic descriptor matches a service with a high-level network slice priority and a high-level terminal device processing priority. When IS takes the second value (e.g., 11), it indicates a mapping relationship between low-level network slice priorities and low-level terminal device processing priorities. That is, it means that the traffic descriptor matches a service with a low-level network slice priority and a low-level terminal device processing priority.

[0151] In one possible design, different values ​​of IS can correspond to different S-NSSAIs. For example, IS1 (where IS is the first value) corresponds to one S-NSSAI (e.g., S-NSSAI-1), and IS2 (where IS is the second value) corresponds to another S-NSSAI (e.g., S-NSSAI-2). Assuming S-NSSAI-1 has a high priority, IS1 indicates that a high-priority slice corresponds to a high-priority processing priority of the terminal device; that is, when a service corresponds to S-NSSAI-1, the terminal device's internal processing priority for that service is also high. Conversely, assuming S-NSSAI-2 has a low priority, IS2 indicates that a low-priority slice corresponds to a low-priority processing priority of the terminal device; that is, when a service corresponds to S-NSSAI-2, the terminal device's internal processing priority for that service is also low.

[0152] In another possible design, multiple new S-NSSAIs can be defined, and the structure of each new S-NSSAI can include additional information elements related to IS. For example, such as... Figure 7 As shown in (a), the new S-NSSAI's SD can include IS. Or, as Figure 7 As shown in (b), the new S-NSSAI's SST may include IS.

[0153] Different S-NSSAIs can correspond to different IS values. For example, IS1 (where the IS value is the first value) corresponds to a new S-NSSAI (e.g., S-NSSAI-1), and IS2 (where the IS value is the second value) corresponds to another new S-NSSAI (e.g., S-NSSAI-2). Assuming S-NSSAI-1 has a high priority, IS1 indicates that a high-priority slice corresponds to a high-priority processing priority of the terminal device; that is, when a service corresponds to (matches) S-NSSAI-1, the terminal device's internal processing priority for that service is also high. Assuming S-NSSAI-2 has a low priority, IS2 indicates that a low-priority slice corresponds to a low-priority processing priority of the terminal device; that is, when a service corresponds to S-NSSAI-2, the terminal device's internal processing priority for that service is also low.

[0154] 502. The terminal device sends a registration request message to the gNB.

[0155] Before performing services, terminal devices can register on the network by sending a registration request message to the gNB. This registration request message can carry a requested NSSAI (Requested NSSAI), meaning the terminal device can request a network slice available in the current PLMN and registered area.

[0156] The requested NSSAI may include at least one S-NSSAI determined by the terminal device. The NSSAI included in the "Requested NSSAI" can be selected from "Configured NSSAI", "Allowed NSSAI", or "Default Configured NSSAI". The "Requested NSSAI" does not include any S-NSSAIs that are currently rejected by the network.

[0157] It should be noted that the network slice identifier (i.e., at least one S-NSSAI) carried in the registration request message can be one of the three indication methods described above. Specifically, the registration request message can carry a new network slice identifier, which carries first indication information used to indicate the data processing level of the application on the terminal device. Alternatively, the registration request message can carry an existing network slice identifier and second indication information, the second indication information used to indicate the data processing level of the application on the terminal device. Or, the registration request message can carry an existing network slice identifier, which can implicitly indicate the data processing level of the terminal device.

[0158] After receiving a registration request message from the terminal device, the gNB can forward the registration request message to the AMF. If the terminal device is in CM-CONNECTED state, the gNB can forward the registration request message to the AMF based on the terminal device's N2 connection. If the terminal device is in CM-IDLE state, and the terminal device did not include the "requested NSSAI" and the globally unique AMF identifier (GUAMI) when establishing a connection with the RAN, the gNB can forward the registration request message to the default AMF.

[0159] The AMF can verify whether the S-NSSAIs in the "Requested NSSAIs" are allowed based on the "Contracted S-NSSAIs". 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 such that all S-NSSAIs of the "Allowed NSSAIs" in that registration area are available in all tracking areas of that registration area, and then return the "Allowed NSSAIs" to the end device. Optionally, the AMF returns a mapping from "Allowed NSSAIs" to "Contracted S-NSSAIs" to the end device. Optionally, the AMF can return one or more "Rejected S-NSSAIs" and the rejection reason for each S-NSSAI. If the S-NSSAI rejection reason value indicates network slice-specific authentication and authorization failure or revocation, the end device can retry requesting the S-NSSAI based on local policies.

[0160] The AMF sends a registration accept message to the gNB, indicating that the registration request has been accepted by the AMF. After receiving the registration accept message from the AMF, the gNB can forward the registration accept message to the terminal device, which means it can proceed to step 503.

[0161] 503. gNB sends a registration accept message to the terminal device.

[0162] The registration acceptance message may include an allowed NSSAI, which means that the S-NSSAI requested by the terminal device is allowed by the network.

[0163] Optionally, the registration acceptance message may also include a rejected NSSAI, which indicates that the network rejected the S-NSSAI in the NSSAI requested by the terminal device.

[0164] 504. The terminal device performs URSP rule matching based on the relevant information of the application.

[0165] The terminal device obtains corresponding information from the application, or identifies relevant information about the application. Optionally, the application can send its relevant information to the processing module executing URSP rules on the terminal device. Alternatively, the processing module executing URSP rules can obtain the relevant information from specific memory. In other words, the relevant information about the application is pre-configured on the terminal device, and the terminal device can obtain this information in advance; this application does not impose limitations on this.

[0166] The application-related information is used by the terminal device to perform URSP rule (new URSP rule) matching. For example, the application-related information may include the application's identifier (APP ID). Optionally, the application-related information may include network slice information that the application wishes to use, such as a first network slice identifier (S-NSSAI1). The first network slice identifier can be one of the three indication methods described above. Optionally, the application-related information may include first information, which indicates the network slice information that the application wishes to use (i.e., the first information has a mapping relationship with the network slice information that the application wishes to use), such as the first network slice identifier (S-NSSAI1).

[0167] The URSP rules configured on a terminal device (i.e., new URSP rules) can include one or more. Multiple URSP rules can correspond to different priorities. The terminal device can match application-related information according to the priority order of the URSP rules. For example, suppose the terminal device is configured with multiple URSP rules including URSP1 and URSP2. URSP1 is a URSP rule indicating a low-latency processing level, and URSP2 is a URSP rule indicating a high-rate processing level. URSP1 has a higher priority than URSP2, so the terminal device can first match the application-related information with URSP1. If no match is found, then the application-related information will be matched with URSP2.

[0168] In this embodiment of the application, the terminal device matches the application's relevant information with URSP rules specifically by matching the application's relevant information with the components in the URSP rules. For example, it could match the application's relevant information with the Traffic descriptor in the URSP rules. Alternatively, it could match the application's relevant information with the Route Selection Descriptor in the URSP rules.

[0169] If the application's information matches URSP1, the application is associated with the PDU session corresponding to the URSP1 RSD (e.g., PDU session1). This means the terminal device routes the application's data flow to PDU session1. The PDU session corresponding to the URSP1 RSD refers to a PDU session that supports the parameters in the URSP1 RSD. These parameters include S-NSSAI, DNN, and SSCmode. The S-NSSAI in the RSD can be a network slice identifier, one of the three indication methods described above.

[0170] For example, such as Figure 8 As shown, one or more URSP rules (new URSP rules) configured or obtained by the terminal device may include URSP1, URSP2, URSP3, and the default URSP rule. 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, RSD2 includes S-NSSAI-2, and RSD3 includes S-NSSAI-3. URSP2 includes a traffic descriptor and two 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 three 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 wildcard traffic descriptor and a wildcard RSD. Wildcard traffic descriptors can match all services. Wildcard RSDs include wildcard slices, and the type of wildcard slice is eMBB.

[0171] Currently, cloud gaming applications initiated by terminal devices (e.g., ), The corresponding application is identified as King of Glory. The corresponding application identifier matches the traffic descriptor in URSP1. The terminal device determines that the URSP rule matching the currently initiated service is URSP1, based on the network slice information (e.g., S-NSSAI 1) that is expected to be used and the network slice identifier in RSD1.

[0172] The terminal device determines whether the network slice (S-NSSAI 1) indicated by RSD1 belongs to the Allowed NSSAI of the current network. If the network slice indicated by RSD1 (e.g., S-NSSAI 1) belongs to the Allowed NSSAI of the current network, it can... This is associated with a PDU session that supports RSD1 in URSP1. It should be noted that the network slice indicated by RSD1 (e.g., S-NSSAI 1) can indicate more than just... The corresponding network slice, so that the terminal device can 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 (e.g., low-latency processing level) can better meet business needs. This avoids a poor business experience caused by low latency in network slicing but high latency in the terminal device's internal processing, and can fully leverage the advantages of network slicing.

[0173] In one possible design, the traffic descriptor or RSD in the URSP rule may include a parameter indicating the data processing level of the terminal device. The application's related information may also carry a parameter indicating the data processing level of the terminal device. During the URSP rule matching process, the terminal device can match the parameter indicating the data processing level carried in the application's related information with the parameter indicating the data processing level of the terminal device in the URSP rule.

[0174] For example, the URSP matching process is illustrated by including a parameter (e.g., IS) in the RSD of the URSP rule to indicate the data processing level of the terminal device. IS indicates the data processing level of the application on the terminal device. The data processing level of the application on the terminal device can be referred to the relevant description above, and will not be repeated here.

[0175] like Figure 9As shown, one or more URSP rules configured or obtained 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), and RSD3 includes S-NSSAI-3 and IS (e.g., IS3). URSP2 includes a traffic descriptor and two 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 three RSDs. Traffic descriptors include application identifiers (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, and the wildcard RSD includes wildcard slices, the type of which is eMBB.

[0176] Currently, terminal devices initiate cloud gaming applications (e.g., ), The corresponding application identifier 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 terminal device determines that the URSP rule matching the network slice information to be used matches the network slice identifier in RSD1.

[0177] The terminal device determines whether the network slice (S-NSSAI 1) indicated by RSD1 belongs to the Allowed NSSAI of the current network. If the network slice indicated by RSD1 (e.g., S-NSSAI 1) belongs to the Allowed NSSAI of the current network, it can... This is associated with a PDU session that supports RSD1 in URSP1. It should be noted that the network slice identifier (e.g., S-NSSAI 1) in RSD1 of URSP1 can indicate... The corresponding network slice, so that the terminal device can The traffic is associated with the PDU session that supports the network slice, and IS1 in RSD1 of URSP1 can indicate... The corresponding data processing level of the terminal device (e.g., low-latency processing level) can better meet business needs. This avoids a poor business experience caused by low latency in network slicing but high latency in the terminal device's internal processing, and can fully leverage the advantages of network slicing.

[0178] In other embodiments, the terminal device may also use other methods when performing URSP matching based on the relevant information of the application, such as performing URSP matching based on the domain name information (e.g., fully qualified domain name (FQDN)) and the destination server IP address information corresponding to the service to be initiated, or the modem layer may directly perform the above matching action without the application layer's participation. This application embodiment does not limit this.

[0179] Additionally, if one or more S-NSSAIs corresponding to the URSP rules that match the currently initiated service (or the current application) are not Allowed NSSAIs of the current network (i.e., not supported by the network), URSP matching is stopped; or, if one or more S-NSSAIs corresponding to the RSDs that match the currently initiated service are not Allowed NSSAIs of the current network, URSP matching is stopped.

[0180] 505. The terminal device associates the application with the PDU session.

[0181] In one possible design, if a PDU session already exists that supports the network slice identifier that the application wishes to use (e.g., S-NSSAI 1), the terminal device associates the application with that PDU session; that is, the terminal device routes the application's data flow to that PDU session. If no PDU session exists that supports the network slice identifier that the application wishes to use (e.g., S-NSSAI 1), 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.

[0182] The specific process of establishing a PDU session includes the following steps:

[0183] Step 1: The terminal device sends a PDU session establishment request to the AMF.

[0184] Terminal devices can send PDU session establishment requests to the AMF via Non-access stratum (NAS) messages.

[0185] The PDU session establishment request may include parameters such as PDU session ID, PDU session type, SSC Mode, DNN, and S-NSSAI (the S-NSSAI corresponding to the service). The S-NSSAI in the PDU session establishment request can be a network slice identifier, one of the three indication methods mentioned above.

[0186] 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 appropriate SMF based on the slicing capabilities supported by each SMF in the network, and forwards the session establishment request to the SMF.

[0187] Step 2: AMF sends a PDU session create request to SMF.

[0188] AMF can send a PDU session creation request to SMF via HTTP2 POST. The PDU session creation request can include parameters such as SUPI, DNN, PDU Session ID, S-NSSAI, and Request Type.

[0189] SMF can establish the context of a PDU session. SMF can obtain the user's subscription information from UDM, and then send policy control messages to UPF, RAN, and terminal equipment, which will then establish a connection for the PDU session.

[0190] Step 3: SMF sends a session create response (PDU) to AMF.

[0191] Once the SMF confirms that the PDU session connection has been established, it can send a session creation response to the AMF to indicate that the PDU session has been successfully established.

[0192] Step 4: AMF sends a PDU session establishment accept to the terminal device.

[0193] AMF responds to the terminal device with a session establishment request response, indicating that the PDU session has been 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 on the newly established PDU session.

[0194] In addition, if the PDU Session Establishment Request sent by the terminal device is rejected by the network side, that is, the PDU session establishment fails, the terminal device will rematch other URSP rules and initiate the establishment of the PDU session based on the rematched URSP rules.

[0195] Based on the method provided in this application embodiment, the terminal device can match application-related information with at least one URSP rule. If a URSP rule (e.g., a first URSP rule) matches the application-related information, the application's data stream can be processed according to the data processing level indicated by the network slice identifier (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 application's data stream, and simultaneously process the application's data stream based on the data processing level indicated by the first network slice identifier. That is, the transmission and processing performance of business data can be guaranteed through the network slice and the terminal device's data processing level, thus meeting the business needs of different services.

[0196] This application also provides a chip system, such as... Figure 10 As shown, the chip system includes at least one processor 1001 and at least one interface circuit 1002. The processor 1001 and the interface circuit 1002 are interconnected via lines. For example, the interface circuit 1002 can be used to receive signals from other devices (e.g., the memory of a terminal device). As another example, the interface circuit 1002 can be used to send signals to other devices (e.g., the processor 1001).

[0197] For example, interface circuit 1002 can read instructions stored in the memory of the terminal device and send those instructions to processor 1001. When the instructions are executed by processor 1001, the terminal device (e.g., ...) can... Figure 4 The terminal device 100 shown executes the steps in the above embodiments.

[0198] Of course, the chip system may also include other discrete components, and this application embodiment does not specifically limit this.

[0199] This application embodiment also provides a computer-readable storage medium, which includes computer instructions, and when the computer instructions are used in a terminal device (such as...) Figure 4When the terminal device 100 shown is run, the terminal device 100 performs the various functions or steps performed by the terminal device in the above method embodiment, and the network device performs the various functions or steps performed by the network device in the above method embodiment.

[0200] This application also provides a computer program product that, when run on a computer, causes the computer to perform various functions or steps performed by the terminal device in the above method embodiments.

[0201] This application also provides a processing device, which can be divided into different logical units or modules according to function. Each unit or module performs different functions, so that the processing device performs various functions or steps performed by the terminal device or network device in the above method embodiments.

[0202] Through the above description of the embodiments, those skilled in the art can clearly understand that the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0203] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0204] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0205] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0206] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, essentially or in other words, the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0207] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A network slice matching method, characterized in that, include: The terminal device obtains relevant information about the application, including a first network slice identifier; The terminal device matches the application's relevant information with at least one routing policy URSP rule in descending order of priority. The at least one URSP rule includes a first URSP rule and a default URSP, with the default URSP having the lowest priority. The default URSP includes a wildcard slice and a wildcard traffic descriptor that matches all services. The first URSP rule includes a first network slice identifier, which explicitly or implicitly indicates the terminal device's data processing level, and a PDU session used to transmit the application's data stream. If the first URSP rule matches the relevant information of the application, the data stream of the application is processed according to the data processing level indicated by the first network slice identifier, and the data stream of the application is routed to the PDU session; wherein, the data processing level includes multiple processing priorities, the processing priorities include M levels, the network slice priority corresponding to the first network slice identifier includes N levels, when N and M are not the same, one network slice priority level corresponds to multiple processing priority levels, or multiple network slice priority levels correspond to one processing priority level; the processing of the application's data stream according to the data processing level indicated by the first network slice identifier includes: For low-latency processing levels, business data is prioritized for processing compared to other latency processing levels; for high-speed processing levels, more processing resources are allocated to process business data compared to other speed processing levels; for high-security processing levels, business data is encrypted using high-level methods compared to other security processing levels; for high-reliability processing levels, business data is backed up and / or transmitted multiple times compared to other reliability processing levels; for high-bandwidth processing levels, business data is transmitted using a larger bandwidth frequency band compared to other bandwidth processing levels, or multiple frequency bands are used simultaneously for data transmission.

2. The method according to claim 1, characterized in that, The relevant information of the application includes first information, which is used to indicate the first network slice identifier.

3. The method according to claim 1 or 2, characterized in that, The first URSP rule includes the first network slice identifier, which includes: The first URSP rule includes a first routing descriptor (RSD), and the first RSD includes the first network slice identifier.

4. The method according to claim 1, characterized in that, The first network slice identifier indicates the data processing level of the terminal device, including: The first network slice identifier includes first indication information, which is used to indicate the data processing level of the terminal device; The first indication information includes multiple values, each of which corresponds to a data processing level, and different values ​​correspond to different data processing levels.

5. The method according to claim 1, characterized in that, The first network slice identifier indicates the data processing level of the terminal device, including: The first network slice identifier includes second indication information, which is used to indicate the data processing level of the terminal device. 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.

6. The method according to claim 4, characterized in that, The first network slice identifier includes a slice service type (SST) and a slice distinguishing symbol (SD), wherein the SST or the SD includes the first indication information.

7. The method according to claim 5, characterized in that, The first network slice identifier includes a slice service type (SST) and a slice distinguishing symbol (SD), wherein the SST or the SD includes the second indication information.

8. The method according to claim 1 or 2, characterized in that, Before the terminal device obtains the application's relevant information, the method further includes: The terminal device sends a registration request message to the first network device, the registration request message carrying the first network slice identifier; The terminal device receives a registration acceptance message from the first network device, the registration acceptance message including information about the slices that are allowed to be accessed.

9. The method according to claim 1 or 2, characterized in that, The method further includes: The terminal device sends a PDU session request message to the Access and Mobility Management Function (AMF) network element, and the PDU session request message includes the first network slice identifier.

10. The method according to claim 1 or 2, characterized in that, The relevant information of the application also includes the identifier of the application, and the first URSP rule also includes a traffic descriptor that matches the identifier of the application.

11. A computer-readable storage medium, characterized in that, Includes computer instructions; When the computer instructions are executed on a terminal device, the terminal device causes the terminal device to perform the method as described in any one of claims 1-10.

12. A terminal device, characterized in that, The terminal device includes: a wireless communication module, a memory, and one or more processors; the wireless communication module, the memory, and the processor are coupled together. The memory is used to store computer program code, which includes computer instructions; when the computer instructions are executed by the processor, the terminal device performs the method as described in any one of claims 1-10.

Images