WO2024124949A1 - 通信方法及终端设备 - Google Patents

通信方法及终端设备 Download PDF

Info

Publication number
WO2024124949A1
WO2024124949A1 PCT/CN2023/114031 CN2023114031W WO2024124949A1 WO 2024124949 A1 WO2024124949 A1 WO 2024124949A1 CN 2023114031 W CN2023114031 W CN 2023114031W WO 2024124949 A1 WO2024124949 A1 WO 2024124949A1
Authority
WO
WIPO (PCT)
Prior art keywords
network slice
target
terminal device
identifier
app
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2023/114031
Other languages
English (en)
French (fr)
Inventor
庞高昆
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Honor Device Co Ltd
Original Assignee
Honor Device Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Honor Device Co Ltd filed Critical Honor Device Co Ltd
Priority to US19/117,016 priority Critical patent/US20260122556A1/en
Priority to CN202380059429.5A priority patent/CN119698861A/zh
Priority to EP23902158.7A priority patent/EP4576863A4/en
Publication of WO2024124949A1 publication Critical patent/WO2024124949A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/03—Protecting confidentiality, e.g. by encryption
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0866—Checking the configuration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service

Definitions

  • the present application relates to the field of intelligent terminal technology, and in particular to a communication method and terminal equipment.
  • Network slice is a logically isolated network used to support specific network capabilities and network features. It is a key technology to meet the network differentiation requirements of the fifth generation (5G) mobile communication technology proposed by the 3rd generation partnership project (3GPP).
  • 5G fifth generation
  • 3GPP 3rd generation partnership project
  • the network characteristics of different network slices are not the same, and the network slices are required to be isolated from each other and not affect each other.
  • the network slice of the enhanced mobile broadband (eMBB) service can provide a transmission rate that is more than 10 times faster than 4G, and can be applied to the currently popular augmented reality (AR) or virtual reality (VR), and high-definition video live broadcast, so that users can get a fast experience.
  • the network slice of the massive machine communication (mMTC) service requires support for massive terminal access, but the bandwidth is small and there is no requirement for latency.
  • the network slice of the ultra-reliable low-latency communication (URLLC) service has the characteristics of large bandwidth, low latency and high reliability, and can be applied to cloud games, autonomous driving and other scenarios.
  • the embodiments of the present application provide a communication method and a terminal device.
  • the method adopts a terminal-centric solution to determine the matching network slices and the data processing level in the terminal device for the application, making the update, management and maintenance of the network slice selection rules more convenient, and the processing level of the application service data in the terminal matches the network slice, which can also give full play to the advantages of network slicing.
  • an embodiment of the present application provides a communication method.
  • the method is applied to a terminal device, and the terminal device includes an SDK module, an OS module, and a Modem module.
  • the method includes:
  • the SDK module obtains the activation request for establishing a network connection service sent by the target APP; the activation request includes a TD parameter; based on the URSP rule, the SDK module determines the target network slice corresponding to the target APP according to the TD parameter, and sends the identifier of the target network slice to the OS module; the OS module sends the identifier of the target network slice to the Modem module; the Modem module interacts with the network device according to the identifier of the target network slice and sends the target APP to the OS module.
  • the PDU session that supports the target network slice; wherein the business data of the target APP is processed in the terminal device according to the data processing level matching the target network slice.
  • the target APP can be any APP running in the terminal device that needs to establish a network connection service.
  • Different APPs have different requirements for network connection services, such as high speed, large bandwidth, low latency, etc.
  • This method adopts a terminal-centric solution to determine the matching network slice and the data processing level in the terminal device for the application. Compared with the modem-centric solution and the operating system-centric solution, this makes the update, management and maintenance of the network slice selection rules more convenient, and the processing level of the application business data in the terminal matches the network slice, which can also give full play to the advantages of network slicing.
  • the activation request also includes a TD parameter signature; the corresponding SDK module determines the target network slice corresponding to the target APP based on the TD parameters, which may include: when the SDK module determines that the target APP security verification is successful based on the TD parameter signature, the target network slice corresponding to the target APP is determined based on the TD parameters.
  • the TD parameter signature may be generated by encrypting a hash value of the TD parameter.
  • the SDK module uses a security verification mechanism to perform security verification on the APP, which can avoid the problem of APP abusing network slicing.
  • the SDK module may include, when determining that the target APP security verification is successful according to the TD parameter signature:
  • the SDK module decrypts the TD parameter signature according to the signature public key to obtain the first hash value; the TD parameter signature is generated based on the signature private key paired with the signature public key; if the SDK module determines that the first hash value and the second hash value are consistent, it determines that the target APP security verification is successful; wherein, the second hash value is obtained by hashing the TD parameters of the target APP.
  • the method further includes: the Modem module receives the updated URSP rules, and sends the updated URSP rules to the SDK module, so that the SDK module updates the local URSP rules.
  • the embodiment of the present application adopts a terminal-centric solution. Compared with the operating system-centric solution and the modem-centric solution, the cycle required for updating the URSP rules is shorter, and the URSP rules are more limited to maintenance management.
  • the method further includes: the SDK module determines, according to the first identifier of the target network slice, a data processing level of the service data of the target APP in the terminal device; or,
  • the SDK module determines the data processing level of the service data of the target APP in the terminal device according to the second identifier of the target network slice and the type of the target network slice; or,
  • the SDK module determines the data processing level of the target APP's business data in the terminal device according to the type of the target network slice or the priority of the target network slice.
  • the first identifier is the identifier of the newly defined network slice.
  • the SDK module determines the data processing level of the target APP's business data in the terminal device according to the first identifier of the target network slice, and can refer to the first possible implementation method below.
  • the second identifier is an existing network slice identifier, but with new related indication information.
  • the SDK module determines the data processing level of the target APP's business data in the terminal device based on the second identifier of the target network slice and the type of the target network slice. Please refer to the second possible implementation method below.
  • the SDK module determines the data processing level of the target APP's business data in the terminal device according to the type of the target network slice or the priority of the target network slice. Please refer to the third possible implementation method below.
  • the SDK module determines, according to the first identifier of the target network slice, a data processing level of the service data of the target APP in the terminal device, including:
  • the SDK module determines the data processing level of the target APP's business data in the terminal device based on the first indication information in the first identifier of the target network slice; wherein the first identifier is a custom identifier of the network slice, and the first indication information is used to indicate the data processing level of the APP in the terminal device.
  • the first indication information can refer to the first possible implementation method below.
  • the identifier of the target network slice sent by the SDK module to the OS module, and the identifier of the target network slice sent by the OS module to the Modem module are the first identifier of the target network slice.
  • the SDK module determines the data processing level of the service data of the target APP in the terminal device according to the second identifier of the target network slice and the type of the target network slice, which may include:
  • the SDK module determines the data processing level of the target APP's business data in the terminal device based on the second indication information in the second identifier of the target network slice and the type of the target network slice; wherein the second identifier is the network slice identifier specified in the communication protocol, and the second indication information is the indication information newly added to the network slice identifier, which is used to indicate the data processing level of the APP in the terminal device.
  • the first indication information can refer to the second possible implementation method below.
  • the identifier of the target network slice sent by the SDK module to the OS module, and the identifier of the target network slice sent by the OS module to the Modem module are the second identifier of the target network slice.
  • aspects related to the data processing level include at least one of the following: priority, latency, rate, data security, and data reliability.
  • the data processing level may be a priority processing level, a delay processing level, a rate processing level, a security processing level, a reliable processing level, and the like.
  • the SDK module determines the data processing level of the service data of the target APP in the terminal device according to the first identifier of the target network slice
  • the first indication information is the target parameter
  • the TD parameter of the target APP includes the target parameter
  • the SDK module determines the target network slice corresponding to the target APP based on the TD parameters, which may include:
  • the SDK module uses the first network slice as the target network slice corresponding to the target APP; wherein the target parameter value in the first identifier of the first network slice is the same as the target parameter value of the target APP.
  • the target parameter may be the IS parameter mentioned below.
  • the SDK module can match the corresponding target network slice for the APP based on the target parameter value.
  • the data processing level of APP in terminal devices is different.
  • the target parameter value of the target APP is determined by negotiation between the developer of the target APP and the manufacturer of the terminal device.
  • the developer of the target APP can negotiate with the manufacturer of the terminal device to determine the data processing level that meets its business needs.
  • an embodiment of the present application provides a terminal device, which includes one or more processors; a memory; and one or more computer programs, wherein the one or more computer programs are stored in the memory, and when the computer programs are executed by the one or more processors, the terminal device executes a communication method such as the first aspect or any one of the first aspects.
  • the terminal device includes an SDK module, an OS module and a Modem module.
  • the SDK module is used to: obtain an activation request for establishing a network connection service sent by a target APP; wherein the activation request includes a path descriptor TD parameter;
  • the SDK module is also used to: determine the target network slice corresponding to the target APP according to the TD parameters based on the UE routing selection policy URSP rule, and send the identifier of the target network slice to the OS module;
  • the OS module is used to: send the identifier of the target network slice to the Modem module;
  • the Modem module is used to: interact with the network device according to the identification of the target network slice, and associate the target APP with the PDU session that supports the target network slice;
  • the business data of the target APP is processed in the terminal device according to the data processing level matching the target network slice.
  • the second aspect and any implementation of the second aspect correspond to the first aspect and any implementation of the first aspect respectively.
  • the technical effects corresponding to the second aspect and any implementation of the second aspect can refer to the technical effects corresponding to the first aspect and any implementation of the first aspect, which will not be repeated here.
  • an embodiment of the present application provides a chip, the chip comprising a processing circuit and a transceiver pin, wherein the transceiver pin and the processing circuit communicate with each other through an internal connection path, and the processing circuit executes the communication method as in the first aspect or any one of the first aspects to control the receiving pin to receive a signal, and to control the sending pin to send a signal.
  • the third aspect and any implementation of the third aspect correspond to the first aspect and any implementation of the first aspect, respectively.
  • the technical effects corresponding to the third aspect and any implementation of the third aspect can refer to the technical effects corresponding to the first aspect and any implementation of the first aspect, which will not be repeated here.
  • an embodiment of the present application provides a computer program product, including a computer program, which, when executed, enables a computer to execute a communication method as described in the first aspect and any one of the items in the first aspect.
  • the fourth aspect and any implementation of the fourth aspect correspond to the first aspect and any implementation of the first aspect, respectively.
  • the technical effects corresponding to the fourth aspect and any implementation of the fourth aspect can refer to the technical effects corresponding to the above-mentioned first aspect and any implementation of the first aspect, which will not be repeated here.
  • an embodiment of the present application provides a computer-readable storage medium.
  • the computer-readable storage medium includes a computer program, and when the computer program is executed on an electronic device, the electronic device executes the communication method of the first aspect and any one of the first aspects.
  • the fifth aspect and any implementation of the fifth aspect correspond to the first aspect and any implementation of the first aspect, respectively.
  • the technical effects corresponding to the fifth aspect and any implementation of the fifth aspect can refer to the technical effects corresponding to the first aspect and any implementation of the first aspect, which will not be repeated here.
  • FIG1 is a schematic diagram of the data structure of S-NSSAI
  • FIG2 is a schematic diagram of a 5G communication system provided in an embodiment of the present application.
  • FIG3 is a schematic diagram of a data structure of an S-NSSAI provided in an embodiment of the present application.
  • FIG4 is a schematic diagram showing a hardware structure of an electronic device
  • FIG5 is a schematic diagram showing an exemplary software structure of an electronic device
  • FIG6 is a flowchart of module interactions involved in a communication method provided in an embodiment of the present application.
  • FIG7 is a schematic diagram of the data structure of URSP rules
  • FIG8 is a schematic diagram of a data structure of a URSP rule provided in an embodiment of the present application.
  • FIG9 is a schematic diagram of module interactions involved in a communication method provided in an embodiment of the present application.
  • FIG10 is a flowchart of module interactions involved in a communication method provided in an embodiment of the present application.
  • FIG. 11 is a schematic diagram showing an exemplary scenario of encrypting TD parameters.
  • a and/or B in this article is merely a description of the association relationship of associated objects, indicating that three relationships may exist.
  • a and/or B can mean: A exists alone, A and B exist at the same time, and B exists alone.
  • first and second in the description and claims of the embodiments of the present application are used to distinguish different objects rather than to describe a specific order of objects.
  • a first target object and a second target object are used to distinguish different target objects rather than to describe a specific order of target objects.
  • words such as “exemplary” or “for example” are used to indicate examples, illustrations or descriptions. Any embodiment or design described as “exemplary” or “for example” in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as “exemplary” or “for example” is intended to present related concepts in a specific way.
  • multiple refers to two or more than two.
  • multiple processing units refer to two or more processing units; multiple systems refer to two or more systems.
  • 5G will usher in an era of the Internet of Everything. 5G supports three major scenarios: eMBB, mMTC and URLLC, which include diverse and differentiated applications.
  • eMBB Based on breakthroughs in spectrum utilization and spectrum bandwidth technology on the wireless side, 5G can provide a transmission rate that is more than 10 times faster than 4G. For the currently popular AR/VR and HD video live broadcast, only 5G ultra-high speed can meet the needs, and 4G transmission rate cannot support it. When using VR to watch HD or large interactive games, you must drag the network cable to obtain data. In the future, through wireless connection through 5G network, VR/AR can get a fast experience.
  • 5G Through multi-user shared access, ultra-dense heterogeneous networks and other technologies, 5G can support access to 1 million devices per square kilometer, which is 10 times that of 4G.
  • public facilities such as street lights, manhole covers, and water meters have network connectivity and can be managed remotely, but 5G will bring greater innovation.
  • public equipment in various industries in the city can be connected to the intelligent management platform.
  • URLLC The most typical application in 5G scenarios is autonomous driving.
  • the most common scenarios of autonomous driving include emergency braking, vehicle-to-vehicle, vehicle-to-person, vehicle-to-infrastructure and other multi-channel communications at the same time, which requires instant processing of a large amount of data and decision-making. Therefore, the network needs to have large bandwidth, low latency and high reliability at the same time. 5G networks have the ability to cope with such scenarios.
  • one network is used to satisfy all application scenarios and customer groups. For example, if the network wants to provide narrowband Internet of Things (NB-IoT) capabilities, it must enable NB-related features on the network elements. If network reliability is to be improved, redundant backups must be added at the device level of the network elements. This allows the continuous addition of features to meet the demands of the mass market.
  • NB-IoT narrowband Internet of Things
  • AR services require ultra-high network bandwidth of >1600Mbps
  • energy meter reading services require the network to provide massive connections
  • autonomous driving requires the network to guarantee end-to-end low latency of several milliseconds and high reliability of more than 99.999%. If you still want to use one network to meet all current needs and possible future needs, it is impossible to achieve.
  • Network slicing technology allows operators to divide a hardware infrastructure into multiple virtual networks, allocate resources on demand, and flexibly combine capabilities to meet the different needs of various businesses. When new demands are put forward and the current network cannot meet the requirements, operators only need to virtualize a new slice network for this demand without affecting the existing slice network, and launch the business as quickly as possible.
  • Network slicing is to virtualize multiple end-to-end networks on a common hardware basis through slicing technology. Each network has different network functions and adapts to different types of service requirements. After purchasing physical resources, operators use physical resources to virtualize an eMBB slice network for mass Internet access services, and then use physical resources to virtualize an mMTC slice network for the smart meter reading needs of certain manufacturers in vertical industries. The two slice networks provide services for different business scenarios.
  • the demands for network functions in various vertical industries are diverse, these demands can be analyzed into demands for network bandwidth, number of connections, latency, reliability, etc.
  • the 5G standard also summarizes the characteristics of network function demands of different services into three typical scenarios.
  • the types of network slices corresponding to these three typical scenarios are eMBB slices, mMTC slices, and URLLC slices.
  • S-NSSAI Single Network Slice Selection Assistance Information
  • S-NSSAI is used to identify a network slice.
  • an S-NSSAI can be associated with one or more network slice instances, and a network slice instance can be associated with one or more S-NSSAIs.
  • eMBB slice 1, eMBB slice 2, and eMBB slice 3 are all eMBB type slices, and their S-NSSAI values are all 0x01000000;
  • eMBB+mMTC slice 4 can provide services for both eMBB type services and mMTC services, so it is both an eMBB type slice and an mMTC type slice, and the corresponding S-NSSAI values are 0x01000000 and 0x02000000 respectively.
  • S-NSSAI consists of two parts: Slice/ServiceType (SST) and Slice Differentiator (SD):
  • SST refers to the expected network slice behavior in terms of features and services.
  • the standard value range of SST is 1, 2, and 3, with 1 representing eMBB, 2 representing URLLC, and 3 representing Massive Internet of Things (MIoT).
  • MIoT Massive Internet of Things
  • SD is an optional information used to supplement SST to distinguish multiple network slices of the same slice/service type.
  • SST and SD indicates the slice type and multiple slices of the same slice type.
  • S-NSSAI values of 0x01000000, 0x02000000, and 0x03000000 respectively indicate eMBB type slices, URLLC type slices, and MIoT type slices.
  • S-NSSAI values of 0x01000001 and 0x01000002 indicate eMBB type slices, serving user groups 1 and 2, respectively.
  • NSSAI Network Slice Selection Assistance Information
  • NSSAI is a collection of S-NSSNI.
  • the NSSAI used in 5G networks include Requested NSSAI, Allowed NSSAI, and Configured NSSAI. Their specific definitions are shown in Table 1.
  • the radio access network first selects an initial AMF to provide services for the UE based on the locally stored information and the UE registration request message.
  • the initial AMF may not support the network slice that the UE wants to use.
  • the initial AMF only supports URLLC type network slices, but the UE requests eMBB type network slices.
  • the initial AMF queries and selects a target AMF that can support the UE network slice from the network slice selection function (NSSF), and then sends the UE's registration request message to the target AMF directly or indirectly.
  • the target AMF processes the UE's registration request and provides network services for the UE.
  • the specific steps may include the following:
  • Step 1 When the UE registers to a PLMN through an access type, it sends a registration request message to the RAN. If the UE stores the Configured NSSAI of this PLMN or the Allowed NSSAI of this PLMN and this access type, the UE will carry the Requested NSSAI information in the non-access stratum (NAS) registration request message and the AN message.
  • the Requested NSSAI contains the S-NSSAI of the slice that the UE wishes to register.
  • Step 2. RAN selects the initial AMF based on the globally unique AMF identifier (GUAMI) or Requested NSSAI. If the UE does not provide Requested NSSAI and GUAMI in the AN message, the RAN shall send the Registration Request message from the UE to the default AMF.
  • GUIMI globally unique AMF identifier
  • the initial AMF queries the unified data management (UDM) to obtain the UE subscription information including Subscribed S-NSSAIs.
  • the initial AMF determines whether it can provide services to the UE based on the received Requested NSSAI, Subscribed S-NSSAI and local configuration. If the AMF can serve the UE, the initial AMF remains the service AMF of the UE, and then the AMF constructs the Allowed NSSAI based on the Subscribed S-NSSAI and Requested NSSAI, and returns the Allowed NSSAI to the UE through the registration acceptance message. If the initial AMF cannot serve the UE or cannot make a judgment, the AMF needs to query the NSSF.
  • UDM unified data management
  • Step 4.AMF sends the Requested NSSAI, Subscribed S-NSSAI, PLMN of subscription permanent identifier (SUPI), tracking area identifier (TAI) and other information to NSSF for query.
  • SUPI subscription permanent identifier
  • TAI tracking area identifier
  • the NSSF selects the AMF set (AMF Set) or candidate AMF list that can serve the UE, the Allowed NSSAI applicable to this access type, and may also select the network slice instance to serve the UE and the network repository function (NRF) within the instance for selecting the network function (NF), and sends this information to the initial AMF.
  • AMF Set AMF Set
  • NRF network repository function
  • Step 6 If the initial AMF is not in the AMF Set and the AMF address information is not stored locally, the initial AMF obtains the candidate AMF list by querying the NRF.
  • the NRF returns a set of available AMF lists, including AMF pointers (AMF Pointer) and address information.
  • AMF Pointer AMF pointers
  • the initial AMF selects one as the target AMF. If the initial AMF cannot obtain the candidate AMF list by querying the NRF, the initial AMF needs to send the UE's registration request message to the target AMF through the RAN.
  • the message sent by the initial AMF to the RAN contains the AMF Set and Allowed NSSAI.
  • Step 7 If the initial AMF decides to send the NAS message directly to the target AMF based on the local policy and subscription information, the initial AMF sends the UE registration request message and other information obtained from the NSSF except the AMF set to the target AMF.
  • the initial AMF decides to forward the NAS message to the target AMF via RAN based on local policy and subscription information, the initial AMF sends a reroute NAS message to RAN.
  • the reroute NAS message includes the target AMF Set information and the registration request message, as well as the relevant information obtained from the NSSF.
  • Step 8 After receiving the registration request message sent in step 7, the target AMF continues to execute the relevant steps of the registration process and finally sends a registration acceptance message to the UE, which carries information such as Allowed NSSAI.
  • Cloud gaming applications are implemented based on real-time audio and video streaming technology.
  • the server sends real-time audio and video streams to the client, and the client sends control command streams to the server.
  • the server applies the received control commands to the game.
  • the entire data processing loop involves: server-side game rendering, audio and video encoding, network transmission, and client-side audio and video decoding and rendering. These processes are time-consuming to a certain extent, but network transmission is the factor that has the greatest impact on user experience. In view of the special business scenarios of cloud gaming, higher requirements are placed on the network: low latency, high bandwidth, and no jitter (or small jitter).
  • cloud gaming applications require low latency for network slicing. If the existing 4G network and Wi-Fi (wireless fidelity) network are used, the response delay of cloud gaming fluctuates within the range of 50ms to 140ms when the network is normal. For some games that require high operation response delay (for example: action games, fighting games, multiplayer online tactical competitive games, first-person shooter games, racing games, etc.), there is a significant gap in experience between cloud gaming and local games, and the operation response delay needs to be further reduced. Due to the particularity of the headset, VR devices can cause motion sickness when the delay is large, and the delay needs to be controlled within 20ms to effectively control the rejection reaction.
  • Wi-Fi wireless fidelity
  • the terminal device determines the network slice that matches the application based on the application's business characteristics or business needs, so as to associate the application with the PDU (Protocol Data Unit) session that supports the network slice, so that the application's business data can be transmitted or routed through the PDU session that supports the network slice, is a problem that needs to be solved.
  • PDU Protocol Data Unit
  • URSP UE Route Selection Policy
  • URSP UE Route Selection Policy
  • Fig. 2 shows a schematic diagram of a 5G communication system provided by an embodiment of the present application.
  • the communication system may include at least one of a UE, an (R)AN device, an AMF device, a session management function (SMF) device, a user plane function (UPF) device, a policy control function (PCF) device, an NSSF device, an application function (AF) device, and a UDM device.
  • a UE UE
  • R Access Management Function
  • AMF session management function
  • UPF user plane function
  • PCF policy control function
  • NSSF an application function
  • AF application function
  • the terminal device in the embodiment of the present application can be a device for realizing wireless communication functions, for example, it can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites, etc.).
  • the terminal device can be a UE, access terminal, terminal unit, terminal station, mobile station, mobile station, remote station, remote terminal, mobile device, wireless communication equipment, terminal agent or terminal device in a 5G network or a future evolved PLMN.
  • the access terminal may be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device or a wearable device, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc.
  • the terminal device may be mobile or fixed.
  • the access network device in the embodiment of the present application is a device that provides wireless communication functions for terminal devices.
  • base stations include but are not limited to: the next generation base station (gnodeB, gNB) in 5G, evolved node B (evolved node B, eNB), radio network controller (radio network controller, RNC), node B (node B, NB), base station controller (basestation controller, BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved nodeB, or home node B, HNB), baseband unit (baseBand unit, BBU), transmission point (transmitting and receiving point, TRP), transmitting point (transmitting point, TP), mobile switching center.
  • gnodeB, gNB next generation base station
  • eNB evolved node B
  • RNC radio network controller
  • node B node B
  • base station controller basestation controller
  • BTS base transceiver station
  • home base station for example, home evolved nodeB
  • the mobility management network element in the embodiment of the present application has main functions including: connection management, mobility management, registration management, access authentication and authorization, reachability management, security context management and other access and mobility related functions.
  • the session management network element in the embodiment of the present application is used for session management in the mobile network, such as session establishment, modification, and release.
  • Specific functions include allocating Internet Protocol (IP) addresses to terminal devices, selecting UPF that provides message forwarding functions, service and session continuity (SSC) mode selection, roaming and other session-related functions.
  • IP Internet Protocol
  • SSC session continuity
  • the user plane function network element in the embodiment of the present application mainly has the following functions: data packet routing and transmission, packet detection, service usage reporting, QoS processing, legal monitoring, uplink packet detection, downlink packet storage and other user plane related functions.
  • the UPF can be connected to a data network (DN).
  • DN data network
  • the policy control function network element in the embodiment of the present application is a PCF device as shown in FIG2 , and its main functions include: unified policy formulation, provision of policy control, and acquisition of policy information from a user database (User Data Repository, UDR). Strategy-related functions such as contract information related to strategic decision-making.
  • UDR User Data Repository
  • the network slice selection function network element in the embodiment of the present application has main functions including: selecting a group of network slice instances for the UE, determining the allowed NSSAI, and determining the AMF set that can serve the UE.
  • the application function network element in the embodiment of the present application is responsible for interacting with the 3GPP core network to provide business or services, including interacting with the network exposure function (NEF) and policy architecture interaction.
  • NEF network exposure function
  • the unified data management network element in the embodiment of the present application such as the UDM device shown in Figure 2, supports authentication credential processing, user identity processing, access authorization, registration and mobility management, contract management, short message management, etc. in the 3GPP authentication and key negotiation mechanism.
  • the above-mentioned network elements can be implemented by designated hardware, or by software instances on designated hardware, or by virtual functions instantiated on a suitable platform, and the present application is not limited thereto.
  • Namf is a service-based interface provided by the AMF network element.
  • the AMF network element can communicate with other network functions through Namf.
  • Nsmf is a service-based interface provided by the SMF.
  • the SMF can communicate with other network functions through Nsmf.
  • Nnssf is a service-based interface provided by the NSSF network element.
  • the NSSF network element can communicate with other network functions through Nnssf.
  • a functional network element can open its capabilities to other authorized functional network elements through a service-based interface, thereby providing network function (NF) services.
  • NF services refer to the various capabilities that can be provided.
  • the embodiments of the present application can also be applied to other future-oriented communication technologies.
  • the network architecture and business scenarios described in this application are intended to more clearly illustrate the technical solutions of this application, and do not constitute a limitation on the technical solutions provided by this application.
  • a person of ordinary skill in the art will know that with the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided by this application are also applicable to similar technical problems.
  • this application is applicable to a communication network with network slices.
  • a network slice is a logically isolated network used to support specific network capabilities and network characteristics.
  • the embodiment of the present application provides a new network slice selection rule.
  • the UE can determine the network slices that match different applications according to the new network slice selection rule to associate the application with the PDU session that supports the corresponding network slice, and the UE can also determine the data processing level inside the service data terminal device of the application according to the new network slice selection rule.
  • the UE associating the first application to the PDU session supporting the first network slice means that the UE transmits or routes the data flow of the first application through the PDU session supporting the first network slice.
  • a new network slice selection rule provided in the embodiment of the present application is part of the URSP rule.
  • the network slice selection rule can be set in the route selection descriptor (RSD) of the URSP rule. Therefore, it can also be said that the embodiment of the present application provides a new URSP rule.
  • the mainstream URSP rule execution methods include modem-centric solutions and operating system (OS)-centric solutions.
  • the matching process of service attributes and network slices is implemented in the terminal modem, and the terminal modem implements the corresponding binding between the characteristic attributes of the terminal service application and the network slice according to the URSP rules.
  • the matching process of service attributes and network slices is implemented in the terminal operating system, and the terminal operating system implements the corresponding binding between the characteristic attributes of the terminal service application and the network slice according to the URSP rules.
  • the embodiment of the present application adopts a terminal-centric solution.
  • the matching process between service attributes and network slices, as well as the matching process between service data and data processing levels are implemented in the terminal, for example, in an SDK (Software Development Kit) or middleware developed and maintained by the terminal company, and the SDK or middleware in the terminal implements the corresponding binding between the terminal application and the network slice according to the new network slice selection rule (or new URSP rule).
  • SDK Software Development Kit
  • middleware developed and maintained by the terminal company
  • the terminal-centric solution provided in the embodiment of the present application is more convenient for updating, managing and maintaining network slice selection rules.
  • the terminal company has higher initiative and is more conducive to ecological cooperation.
  • the APP (application) developer can negotiate with the terminal device party to determine the network slice selection rules, and specifically negotiate to determine the network slice corresponding to the APP, and the data processing level of the APP in the terminal device.
  • the SDK or middleware in the terminal can select a matching network slice for the application based on the corresponding network slice selection rules to associate the application with the PDU session that supports the corresponding network slice, and the business data of the APP can be processed in the terminal device according to the corresponding data processing level.
  • the new network slice selection rule provided in the embodiment of the present application can be defined by a standard organization (such as 3GPP) or by a communication operator.
  • the new network slice selection rule is configured on the network side or the terminal side.
  • the network side may refer to network equipment, for example, it may include gNB (the next Generation Node B), AMF, SMF (Session Management function), PCF (Policy Control function) and other network equipment (or network elements), and the terminal side may refer to terminal equipment, such as UE.
  • the network slice selection rule can be sent to the terminal side through the network device.
  • the H-PCF home PCF
  • the new network slice selection rule can be configured to the terminal device through a registration command message.
  • the communication operator can configure the new network slice selection rule to the terminal device.
  • a mapping relationship between an application and a network slice may be included, and a mapping relationship between a data processing level of an application in a terminal device and a network slice corresponding to the application may also be included.
  • the new network slice selection rule can not only be used to determine the network slice corresponding to the application and support the PDU session of the corresponding network slice, but also can be used to determine the data processing level of the application in the terminal device.
  • the data processing level which can also be called data processing level, data processing mode, internal processing level/mode, etc., is used to indicate the level division when the APP processes data inside the terminal.
  • the data processing level can be a priority processing level, a delay processing level, a rate processing level, a security processing level, a reliable processing level, etc. It should be pointed out that the data processing level of the APP in the terminal device is determined by negotiation between the APP developer and the terminal device.
  • the SDK or middleware in the terminal can determine the network slice corresponding to the application according to the URSP rules, support the PDU session of the corresponding network slice, and determine the data processing level of the application in the terminal device according to the network slice indication information.
  • the network slice indication information can be a network slice identifier, which is used to describe the information of the network slice, such as S-NSSAI.
  • the embodiments of the present application provide several possible implementation methods.
  • the network slice indication information is a newly defined network slice identifier, and the newly defined network slice is used to identify the network slice type.
  • the newly defined network slice identifier can not only be used to indicate the network slice corresponding to the application so that the terminal device can associate the application with the PDU session supporting the network slice, but also can be used to indicate the data processing level corresponding to the application so as to better meet the business needs of the application.
  • the data structure of the newly defined network slice identifier adds the first indication information based on the data structure of the existing network slice identifier.
  • the first indication information may be an internal slice (IS) parameter.
  • the first indication information may be set in the SD part of the network slice identifier S-NSSAI, as shown in FIG3(a), and the first indication information may also be set in the SST part of the network slice identifier S-NSSAI, as shown in FIG3(b).
  • the first indication information is used to indicate the data processing level of the application in the terminal device.
  • the first indication information may be a slice parameter newly defined by the terminal device vendor (such as type, name, etc., which is different from the existing network slice type or name). This embodiment does not limit the form of the first indication information.
  • the first indication information may include one or more bits.
  • the data processing level of the corresponding application in the terminal device is different.
  • the data processing level of the application in the terminal device may be a priority level, such as high priority, medium priority, low priority, etc.
  • a priority level such as high priority, medium priority, low priority, etc.
  • the data processing level of the application in the terminal device may be a delay processing level, such as a delay level of 1ms, 10ms, 100ms, etc., or a delay level of low delay, medium delay, high delay, etc.
  • a delay processing level such as a delay level of 1ms, 10ms, 100ms, etc., or a delay level of low delay, medium delay, high delay, etc.
  • the delay processing level is different, the network transmission channel corresponding to the application is different or not completely the same.
  • the data processing level of the application in the terminal device may be a rate processing level, such as 1Mbps, 10Mbps, 100Mbps, 1000Mbps, etc., or a low rate, medium rate, high rate, etc.
  • rate processing levels such as 1Mbps, 10Mbps, 100Mbps, 1000Mbps, etc.
  • the network transmission channels corresponding to the application are different or not completely the same.
  • the data processing level of the application in the terminal device can be a security processing level, such as normal, TEE (Trusted Execution Environment), SE (Secure Element) and other security levels, or low, medium, high and other security levels.
  • TEE Trusted Execution Environment
  • SE Secure Element
  • the security processing level is different, the network transmission channel corresponding to the application is different or not completely the same.
  • the data processing level of the application in the terminal device can be a reliable processing level, such as 99%, 99.9%, 99.99%, 99.999% or other reliability levels, or low, medium or high reliability levels.
  • the reliable processing level is different, the network transmission channels corresponding to the application are different or not completely the same.
  • the reliable processing level is "x%" it means that the maximum possible service interruption time of the terminal device when it runs continuously for 1 year is (1- x%)*365*24. It is understandable that the shorter the maximum possible service interruption time of the terminal equipment, the higher the reliability level.
  • Table 2 exemplifies a mapping relationship between a network slice identifier, first indication information, and the data processing level corresponding to an application in a terminal device.
  • the first indication information includes 2 bits as an example, "00", "01”, “10” and “11” respectively identify different data processing levels.
  • the terminal device associates the application to the PDU session supporting S-NSSAI 1
  • the terminal device associates the application to the PDU session supporting S-NSSAI 2
  • the terminal device associates the application to the PDU session supporting S-NSSAI 2
  • the terminal device associates the application to the PDU session supporting S-NSSAI 2
  • the first indication information carried in S-NSSAI 3 is "10" it indicates that the data processing level corresponding to the application in the terminal device is the first delay processing level, and the terminal device associates the application to the PDU session supporting S-NSSAI 3
  • the first indication information carried in S-NSSAI 4 is "11" it indicates that the data processing level corresponding to the
  • the first priority processing level is different from the second priority processing level, and the first priority processing level can be higher than the second priority processing level.
  • the terminal device can process the call application at the first priority processing level, and can process the game application at the first priority processing level.
  • the data flow of the call application can be processed first.
  • the first delay processing level is different from the second delay processing level, and the first delay processing level can be higher than the second delay processing level, that is, the processing delay corresponding to the first delay processing level is less than the processing delay corresponding to the second delay processing level.
  • the network slice indication information is an existing network slice identifier
  • the second indication information is added to the existing network slice identifier.
  • the second indication information may be added to the SST part, the SD part, or the NSSAI information element identifier (IEI) of the network slice identifier.
  • the second indication information may include one or more bits for indicating the data processing level of the application in the terminal device, and the data processing level corresponds to the network slice type (or network slice priority). For example, when the network slice type is low latency, the corresponding data processing level is a low latency processing level; when the network slice type is high rate, the corresponding data processing level is a high rate processing level, and so on.
  • Table 3 exemplifies a mapping relationship between a network slice identifier, a network slice type, a second indication information, and a corresponding data processing level of an application in a terminal device.
  • the type of network slice S-NSSAI 1 is a low-latency network slice
  • the second indication information "1" is added to the identifier of the network slice S-NSSAI 1.
  • the second indication information "1" can indicate that the corresponding data processing level of the application in the terminal device is a low-latency processing level.
  • the low-latency processing level can refer to the priority processing of service data inside the terminal device, such as priority scheduling, priority queuing, queue-jumping and early sending, priority sending, etc.
  • the data processing level of the service inside the terminal device is a low-latency processing level, which can meet the low-latency requirements of the service and avoid the problem of poor service experience caused by low network slicing latency and high processing latency inside the terminal device.
  • the advantages of low-latency network slicing can be fully utilized to meet service needs.
  • the type of network slice S-NSSAI 2 is a high-rate network slice.
  • the second indication information "1" may indicate that the corresponding data processing level of the application in the terminal device is a high-rate processing level.
  • the high-rate processing level may refer to the deployment of more processing resources inside the terminal device to process business data.
  • the processing resources may be, for example, memory resources, computing resources (such as CPU (central processing unit), GPU (graphics processing unit), NPU (Neural-network Processing Unit), etc.).
  • the processing level of the service inside the terminal device is a high-rate processing level, which can ensure the high-rate requirement of the service and avoid the problem of poor service experience caused by the high rate of the network slice and the low rate of processing inside the terminal device.
  • the advantages of high-rate network slicing can be fully utilized to meet business needs.
  • the type of network slice S-NSSAI 3 is a high-security network slice.
  • the second indication information "1" may indicate that the corresponding data processing level of the application in the terminal device is a high-security processing level.
  • the high-security processing level may mean that the terminal device processes the service data in a high-security area (such as TEE, SE, etc.), and/or the terminal device uses a high encryption method for the service data to ensure the security of the service data.
  • the processing level of the service inside the terminal device is a high-security processing level, which can ensure the high security requirements of the service and avoid the problem of poor service experience caused by high security of the network slice and low security of the terminal device during internal processing.
  • the advantages of full network slicing meet business needs.
  • the type of network slice S-NSSAI 4 is a high-reliability network slice.
  • the second indication information "1" may indicate that the corresponding data processing level of the application in the terminal device is a high-reliability processing level.
  • the high-reliability processing level may mean that the terminal device backs up and/or transmits the service data multiple times to ensure the reliability of the service data.
  • the processing level of the service inside the terminal device is a high-reliability processing level, which can ensure the high reliability requirements of the service and avoid the problem of poor service experience caused by high reliability of the network slice and low reliability of processing inside the terminal device.
  • the advantages of high-reliability network slices can be fully utilized to meet business needs.
  • the type of network slice S-NSSAI 5 is a large bandwidth network slice.
  • the second indication information "1" may indicate that the corresponding data processing level of the application in the terminal device is a large bandwidth processing level.
  • the large bandwidth processing level may be, for example, that the terminal device uses a frequency band with a larger bandwidth (for example, 80M/120M) to transmit service data, or that the terminal device uses multiple frequency bands to transmit data simultaneously.
  • the processing level of the service inside the terminal device is the high-bandwidth processing level, which can ensure the high bandwidth demand of the service and avoid the problem of poor service experience caused by the large bandwidth of the network slice and the small bandwidth during internal processing of the terminal device.
  • the advantages of high-bandwidth network slices can be fully utilized to meet business needs.
  • an existing network slice identifier indicates a data processing level of an application in a terminal device, and the data processing level corresponds to a network slice type (or a network slice priority).
  • indication information is not added to the existing network slice identifier, but the data processing level of an application in a terminal device is implicitly indicated based on the type of the network slice.
  • Table 4 exemplifies a mapping relationship between a network slice identifier, a network slice type, and the data processing level corresponding to an application in a terminal device.
  • the type of network slice S-NSSAI 1 is a low-latency network slice, implicitly indicating that the data processing level of the application in the terminal device is a low-latency processing level
  • the type of network slice S-NSSAI 2 is a high-rate network slice, implicitly indicating that the data processing level of the application in the terminal device is a high-rate processing level
  • the type of network slice S-NSSAI 3 is a high-security network slice, implicitly indicating that the data processing level of the application in the terminal device is a high-security processing level
  • the type of network slice S-NSSAI 4 is a high-reliability network slice, implicitly indicating that the data processing level of the application in the terminal device is a high-reliability processing level.
  • Table 5 exemplifies a mapping relationship between a network slice identifier, a network slice priority, and an application's processing priority level in a terminal device.
  • the network slice priority can include three levels, namely high, medium and low.
  • the corresponding processing priority levels of the application in the terminal device can also include three levels, namely high, medium and low.
  • the priority of network slice S-NSSAI 1 is "high", and the processing priority level of the application corresponding to network slice S-NSSAI 1 in the terminal device is also "high”;
  • the priority of network slice S-NSSAI 2 is "medium”, and the processing priority level of the application corresponding to network slice S-NSSAI 2 in the terminal device is also “medium”;
  • the priority of network slice S-NSSAI 3 is "low", and the processing priority level of the application corresponding to network slice S-NSSAI 3 in the terminal device is also "low”.
  • the priority of network slice S-NSSAI 1 is “low", and the processing priority level of the application corresponding to network slice S-NSSAI 1 in the terminal device is also “low”. That is, when the priority of the network slice corresponding to the application is "high”, the priority level of the terminal device for the application service is also “high”, so as to ensure the service requirements of the application (such as low latency, high reliability, etc.). When the priority of the network slice corresponding to the application is "medium”, the priority level of the terminal device for the application service is also “medium”, and the service requirements of the application (such as low latency, etc.) are guaranteed as much as possible. When the priority of the network slice corresponding to the application is "low”, the priority level of the terminal device for the application service is also "low” to reasonably meet the service requirements of the application.
  • Table 6 exemplifies a mapping relationship between a network slice identifier, a network slice priority, and an application processing priority level in a terminal device.
  • the network slice priority can include two levels, high and low.
  • the processing priority level of the application corresponding to the terminal device can also include two levels, high and low.
  • Table 6 the priority of network slice S-NSSAI 1 is "high”, and the processing priority level of the application corresponding to network slice S-NSSAI 1 in the terminal device is also "high”; the priority of network slice S-NSSAI 2 is “low”, and the processing priority level of the application corresponding to network slice S-NSSAI 2 in the terminal device is also "low”.
  • the network slice priority may include more levels, for example, four levels, five levels, six levels, etc., which are not limited in the embodiments of the present application.
  • the processing priority level corresponding to the application in the terminal device may also include four levels, five levels, six levels, etc.
  • the network slice priority is related to the application on the terminal device. The following explains the situations in which the processing priorities correspond to each other.
  • the network slice priority includes N levels, and the processing priority levels corresponding to the application in the terminal device include M levels, where N and M are positive integers, and N and M are not equal.
  • one network slice priority level may correspond to multiple processing priority levels of the application in the terminal device, or multiple network slice priority levels may correspond to one processing priority level of the application in the terminal device, which is not limited in this embodiment.
  • Table 7 exemplifies a mapping relationship between a network slice identifier, a network slice priority, and an application's processing priority level in a terminal device.
  • the processing priority level corresponding to the application in the terminal device can also include two levels, namely high and low.
  • the priority of network slice S-NSSAI 1 is "high", and the processing priority level of the application corresponding to network slice S-NSSAI 1 in the terminal device is also "high”; the priority of network slice S-NSSAI 2 is “medium”, and the processing priority level of the application corresponding to network slice S-NSSAI 2 in the terminal device is "low”; the priority of network slice S-NSSAI 3 is "low”, and the processing priority level of the application corresponding to network slice S-NSSAI 3 in the terminal device is "low”. That is, multiple network slice priority levels can correspond to one processing priority level of the application in the terminal device.
  • the network slice priority may be determined based on the type of network slice. For example, the priorities of network slices of types such as uRLLC, eMBB, and mMTC are sorted from high to low.
  • the terminal device can determine that a certain application performs data processing at a corresponding data processing level (such as a low-latency processing level, a high-rate processing level, etc.) in the terminal device according to the corresponding network slice selection rule, and the network slice corresponding to the application, and the terminal device can associate the application with a PDU session that supports the network slice, and the network slice can be identified using the network slice indication information (such as a network slice identifier) in the network slice selection rule.
  • the application performs data processing at a corresponding data processing level in the terminal device, which means that the data flow (traffic of application) of the application performs data processing at a corresponding data processing level in the terminal device.
  • FIG4 it is a schematic diagram of the structure of the electronic device 100.
  • the electronic device 100 may be referred to as a terminal or a terminal device, which is not limited in this application.
  • the schematic diagram of the structure of the electronic device 100 may be applicable to the UE mentioned above.
  • the electronic device 100 shown in FIG4 is only an example of an electronic device, and the electronic device 100 may have more or fewer components than those shown in the figure, may combine two or more components, or may have different component configurations.
  • the various components shown in FIG4 may be implemented in hardware, software, or a combination of hardware and software including one or more signal processing and/or application-specific integrated circuits. now.
  • the electronic device 100 may include: a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a SIM card interface 195, etc.
  • a processor 110 an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C
  • the sensor module 180 may include a pressure sensor, a gyroscope sensor, an acceleration sensor, a temperature sensor, a motion sensor, an air pressure sensor, a magnetic sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, etc.
  • the processor 110 may include one or more processing units, for example, the processor 110 may include an application processor (AP), a modem processor (Modem), a graphics processor (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and/or a neural-network processing unit (NPU), etc.
  • AP application processor
  • Modem modem processor
  • GPU graphics processor
  • ISP image signal processor
  • controller a memory
  • DSP digital signal processor
  • DSP digital signal processor
  • NPU neural-network processing unit
  • Different processing units may be independent devices or integrated in one or more processors.
  • the controller may be the nerve center and command center of the electronic device 100.
  • the controller may generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.
  • a memory may also be provided in the processor 110 for storing instructions and data.
  • the memory in the processor 110 is a cache memory.
  • the USB interface 130 is an interface that complies with USB standard specifications, and may be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc.
  • the USB interface 130 may be used to connect a charger to charge the electronic device 100, or may be used to transmit data between the electronic device 100 and a peripheral device. It may also be used to connect headphones to play audio through the headphones.
  • the charging management module 140 is used to receive charging input from a charger.
  • the charger can be a wireless charger or a wired charger. While the charging management module 140 is charging the battery 142, it can also power the electronic device through the power management module 141.
  • the power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110.
  • the power management module 141 receives input from the battery 142 and/or the charging management module 140 to power the processor 110, the internal memory 121, the external memory, the display screen 194, the camera 193, and the wireless communication module 160.
  • the wireless communication function of the electronic device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.
  • Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals.
  • Each antenna in electronic device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve the utilization of antennas.
  • antenna 1 can be reused as a diversity antenna for a wireless local area network.
  • the antenna can be used in combination with a tuning switch.
  • the mobile communication module 150 can provide solutions for wireless communications including 2G/3G/4G/5G, etc., applied to the electronic device 100.
  • the mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc.
  • the mobile communication module 150 may receive electromagnetic waves through the antenna 1, The received electromagnetic waves are filtered, amplified, and transmitted to the modulation and demodulation processor for demodulation.
  • the mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1.
  • at least some functional modules of the mobile communication module 150 can be set in the processor 110.
  • at least some functional modules of the mobile communication module 150 can be set in the same device as at least some modules of the processor 110.
  • the modem processor runs on the baseband chip and the coprocessor.
  • the Modem is provided with a SIM card module, which can be used to provide network registration, authentication and other functions related to SIM information.
  • a SIM card module can be used to provide network registration, authentication and other functions related to SIM information.
  • a user uses an electronic device with a Modem, he can implement a series of SIM card functions by triggering a local application.
  • the SIM card mentioned above can be a physical card (or hard card) or a virtual SIM card (or soft card), and can include an embedded chip user identity card (embedded-SIM, eSIM), etc.
  • the specific form of the SIM card is not limited in the embodiments of the present application.
  • the modem processor may include a modulator and a demodulator.
  • the modulator is used to modulate the low-frequency baseband signal to be sent into a medium-high frequency signal.
  • the demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal.
  • the demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing.
  • the application processor outputs a sound signal through an audio device (not limited to a speaker 170A, a receiver 170B, etc.), or displays an image or video through a display screen 194.
  • the modem processor may be an independent device.
  • the modem processor may be independent of the processor 110 and be set in the same device as the mobile communication module 150 or other functional modules.
  • the wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) network), bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR) and the like applied to the electronic device 100.
  • WLAN wireless local area networks
  • BT wireless fidelity
  • GNSS global navigation satellite system
  • FM frequency modulation
  • NFC near field communication
  • IR infrared
  • the wireless communication module 160 can be one or more devices integrating at least one communication processing module.
  • the wireless communication module 160 receives electromagnetic waves via the antenna 2, modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110.
  • the wireless communication module 160 can also receive the signal to be sent from the processor 110, modulate the frequency, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.
  • antenna 1 of electronic device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, so that electronic device 100 can communicate with the network and other devices through wireless communication technology.
  • the electronic device 100 implements a display function through a GPU, a display screen 194, and an application processor.
  • the processor 110 may include one or more GPUs that execute program instructions to generate or change display information.
  • the display screen 194 is used to display images, videos, etc.
  • the electronic device 100 can implement a shooting function through an ISP, a camera 193, a video codec, a GPU, a display screen 194, and an application processor.
  • the camera 193 is used to capture static images or videos.
  • the external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100.
  • an external memory card such as a Micro SD card
  • the internal memory 121 may be used to store computer executable program codes, which include instructions.
  • the processor 110 executes various operations of the electronic device 100 by running the instructions stored in the internal memory 121. Functional application and data processing enable the electronic device 100 to implement the communication method in the embodiment of the present application.
  • the electronic device 100 can implement audio functions such as music playing and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor.
  • the audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals.
  • the audio module 170 can also be used to encode and decode audio signals.
  • the audio module 170 can be arranged in the processor 110, or some functional modules of the audio module 170 can be arranged in the processor 110.
  • the pressure sensor is used to sense the pressure signal and can convert the pressure signal into an electrical signal.
  • the pressure sensor can be disposed on the display screen 194.
  • the electronic device 100 can also calculate the touch position according to the detection signal of the pressure sensor.
  • the touch sensor is also called a "touch panel”.
  • the touch sensor can be set on the display screen 194.
  • the touch sensor and the display screen 194 form a touch screen, also called a "touch screen”.
  • the touch sensor is used to detect a touch operation on or near it.
  • the touch sensor can pass the detected touch operation to the application processor to determine the type of touch event.
  • the key 190 includes a power key (or power key), a volume key, etc.
  • the key 190 may be a mechanical key or a touch key.
  • the electronic device 100 may receive key input and generate key signal input related to user settings and function control of the electronic device 100.
  • Motor 191 can generate vibration prompts.
  • Motor 191 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback.
  • touch operations acting on different applications can correspond to different vibration feedback effects.
  • the indicator 192 may be an indicator light, which may be used to indicate the charging status, power changes, messages, missed calls, notifications, etc.
  • the SIM card interface 195 is used to connect a SIM card.
  • the SIM card can be connected to and separated from the electronic device 100 by inserting it into the SIM card interface 195 or pulling it out from the SIM card interface 195.
  • the electronic device 100 can support 1 or N SIM card interfaces, where N is a positive integer greater than 1.
  • the SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, and the like. Multiple cards can be inserted into the same SIM card interface 195 at the same time. The types of the multiple cards can be the same or different.
  • the SIM card interface 195 can also be compatible with different types of SIM cards.
  • the SIM card interface 195 can also be compatible with external memory cards.
  • the electronic device 100 interacts with the network through the SIM card to implement functions such as calls and data communications.
  • the electronic device 100 uses an eSIM, i.e., an embedded SIM card.
  • the eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.
  • the software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture.
  • the embodiment of the present application takes the Android system of the layered architecture as an example to exemplify the software structure of the electronic device 100.
  • FIG. 5 is a software structure block diagram of the electronic device 100 according to an embodiment of the present application.
  • the layered architecture of the electronic device 100 divides the software into several layers, each with a clear role and division of labor.
  • the layers communicate with each other through software interfaces.
  • the Android system is divided into four layers, from top to bottom, namely, the application layer, the application framework layer, the radio interface layer (Radio Layer Interface, RIL), and the modulation layer.
  • Modem Modem processor
  • the application layer and the application framework layer can exchange data through a conventional interface.
  • the application framework layer and the RIL can exchange data through a hardware abstraction layer interface definition language (HIDL) interface.
  • HIDL hardware abstraction layer interface definition language
  • the RIL and the Modem layer can exchange data based on the chip architecture of the electronic device.
  • the RIL and the Modem layer exchange data through PCI Express (peripheral component interconnect express, PCIE) or memory sharing.
  • PCI Express peripheral component interconnect express
  • the application layer can include a series of application packages.
  • the application package may include applications such as call, camera, gallery, video, map, navigation, Bluetooth, network slice selection SDK, etc.
  • the network slice selection SDK can determine the network slice corresponding to the APP based on the URSP rules, and determine the data processing level corresponding to the APP in the electronic device.
  • the application framework layer provides application programming interface (API) and programming framework for the applications in the application layer.
  • API application programming interface
  • the application framework layer includes some predefined functions.
  • the application framework layer may include a telephony manager (Telephony), a connectivity service (Connectivity Service), etc.
  • Telephony Telephony
  • Connectivity Service connectivity service
  • the phone manager is used to provide management functions for cellular-related services of the electronic device 100.
  • the phone manager is used to provide management of call status (including connected, hung up, etc.) and cellular data connection status (including connected to the cellular network, disconnected from the cellular network, establishing a connection with the cellular network, disconnecting from the cellular network, etc.).
  • the cellular network can include 2G network, 3G network, 4G network and 5G network (such as SA network), etc.
  • the application framework layer may also include a window manager, a content provider, a view system, a resource manager, a notification manager, etc. (not shown in FIG. 5 ), which is not limited in the embodiment of the present application.
  • the window manager is used to manage window programs.
  • the window manager can obtain the display screen size, determine whether there is a status bar, lock the screen, capture the screen, etc.
  • Content providers are used to store and retrieve data and make it accessible to applications.
  • the data may include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.
  • the view system includes visual controls, such as controls for displaying text, controls for displaying images, etc.
  • the view system can be used to build applications.
  • a display interface can be composed of one or more views.
  • a display interface including a text notification icon can include a view for displaying text and a view for displaying images.
  • the resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.
  • the notification manager allows applications to display notification information in the status bar. It can be used to convey notification-type messages and can disappear automatically after a short stay without user interaction. For example, notification information is used to inform download completion, message reminders, etc.
  • the application layer and the application framework layer can be referred to as the AP side.
  • the network slice corresponding to the APP is determined based on the URSP rule, and the data processing level corresponding to the APP in the electronic device is determined to be implemented on the AP side, which can be specifically selected by the SDK on the AP side. implemented in .
  • RIL is the interface layer between the application framework layer and the Modem layer, responsible for the transmission of cellular-related service control plane operations and the reliable transmission of data.
  • RIL can include the Radio Interface Layer Daemon (rild), and rild can include: ril service module.
  • the ril service module can be used to forward the instructions sent by the phone manager via the HIDL interface to the Modem layer, and forward the response data corresponding to the instructions returned by the Modem layer, and the status or notification actively reported by the Modem layer to the phone manager.
  • the modem layer includes a modem processor (Modem), which may include: a protocol stack and a card processing module.
  • the protocol stack may include wireless communication protocol stacks such as 2G protocol stack, 3G protocol stack, 4G protocol stack and 5G protocol stack.
  • the card processing module may include modules related to the SIM card, such as a SIM card module, a local SIM card module, and a SIM card slot driver, etc.
  • the SIM card slot driver may be connected to a SIM hard card.
  • SIM card module used to provide network registration, authentication and other functions related to SIM information.
  • the SIM card module can support the local SIM card calling mode provided by the local SIM card module.
  • Local SIM card module used to use the SIM card slot driver to access local SIM card information.
  • the modem of the electronic device 100 may be provided with a SIM card slot driver and a SIM hard card; or, the modem of the electronic device 100 may not be provided with a SIM card slot driver and a SIM hard card, in which case the electronic device 100 may use a local eSIM.
  • the layers in the software structure shown in FIG5 and the components contained in each layer do not constitute a specific limitation on the electronic device 100.
  • the electronic device 100 may include more or fewer layers than shown in the figure, and each layer may include more or fewer components, which is not limited in the present application.
  • the electronic device includes hardware and/or software modules corresponding to the execution of each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in combination with the embodiments, but such implementation should not be considered to be beyond the scope of the present application.
  • the embodiment of the present application provides a communication method, which may specifically include the following steps:
  • the APP sends an activation request to the network slice selection SDK to establish a network connection service.
  • the activation request may include TD (Traffic Descriptor) parameters of the APP.
  • TD parameters of the APP may include, but are not limited to, APP ID, data network name (DNN), IP triplet (IP Descriptor), domain name descriptor (Domain Descriptor), connection capabilities (Connection Capabilities) and other parameters.
  • the network slice selection SDK determines the target network slice corresponding to the APP according to the TD parameters, and sends the identifier of the target network slice to the OS module.
  • the URSP rules there are mainly two groups of important parameters, one group is the TD parameters describing the APP attributes, and the other group is the RSD parameters describing the data bearer attributes, which may include but are not limited to S-NSSAI, SSC Mode (session and service continuity mode), DNN and other parameters.
  • the URSP rule is essentially the correspondence between multiple groups of TD parameters and multiple groups of RSD parameters.
  • the network slice selection SDK After the network slice selection SDK obtains the TD parameters of the APP, it can find the corresponding RSD parameters based on the URSP rules. Since the RSD parameters contain the network slice identifier S-NSSAI, the target network slice that the APP can access is determined.
  • the network slice selection SDK can match the network slice corresponding to the APP based on the URSP rule and the priority of the network slice. For example, the network slice selection SDK first matches the network slice corresponding to the APP in the network slice of the first priority based on the URSP rule. If no match is found, it matches the network slice corresponding to the APP in the network slice of the second priority based on the URSP rule. Among them, the first priority is higher than the second priority.
  • the network slice selection SDK can send the identifier of the target network slice corresponding to the APP to the OS module through the API (Application Program Interface) provided by the OS module.
  • API Application Program Interface
  • the OS module sends the identifier of the target network slice to the Modem module.
  • the OS module sends the received identifier of the target network slice corresponding to the APP to the Modem module through the API provided by the Modem module.
  • the Modem module interacts with the network device, associates the APP to the PDU session that supports the target network slice, and feeds back the indication of successful association to the network slice selection SDK.
  • the network slice selection SDK can also directly send the identifier of the target network slice corresponding to the APP to the Modem module through the API provided by the Modem module.
  • the identifier of the target network slice corresponding to the APP received by the modem module is the identifier of the network slice that the UE wishes to register, that is, the identifier of the requested network slice.
  • the modem module generates a registration request message based on the identifier of the target network slice, that is, the registration request message includes the identifier of the target network slice (NSSAI), and sends the registration request message to the network side device (such as gNB).
  • NSSAI identifier of the target network slice
  • the identifier of the target network slice included in the registration request message may be the network slice identifier mentioned in the first possible implementation method, the second possible implementation method, and the third possible implementation method. If the identifier of the target network slice is the network slice identifier newly defined in the first possible implementation method, the first indication information is carried in the identifier of the target network slice, and the first indication information is used to indicate the data processing level of the application in the terminal device. If the identifier of the target network slice is the network slice identifier mentioned in the second possible implementation method and added with the second indication information, the second indication information is carried in the identifier of the target network slice, and the second indication information is used to indicate the data processing level of the application in the terminal device. If the identifier of the target network slice is the network slice identifier in the existing technology mentioned in the third possible implementation method, the data processing level of the application in the terminal device can be implicitly indicated in the target network slice.
  • the gNB may forward the Registration Request message to the AMF. If the UE is in the CM-CONNECTED state, the gNB may forward the Registration Request message to the AMF based on the UE's N2 connection. If the UE is in the CM-IDLE state and the UE does not include the "Requested NSSAI" and the globally unique AMF identifier (globally uniq AMF identifier, GUAMI) when establishing a connection with the RAN, the gNB may forward the Registration Request message to the default AMF.
  • GUAMI globally uniq AMF identifier
  • the AMF can verify whether the S-NSSAI in the "Requested NSSAI” is allowed based on the "Contracted S-NSSAIs" Allowed. Among them, the "contracted S-NSSAIs" can be obtained by the AMF from the unified data management UDM network element. The AMF can determine a registration area so that all S-NSSAIs of the "allowed NSSAI” of the registration area are available in all tracking areas of the registration area, and then return the "allowed NSSAI” to the terminal device. Optionally, the AMF returns a mapping of "allowed NSSAI" to "contracted S-NSSAIs" to the terminal device.
  • the AMF can return one or more "rejected S-NSSAIs" and the reason for rejection of each S-NSSAI. If the S-NSSAI rejection reason value indicates a network slice-specific authentication and authorization failure or revocation, the UE can retry requesting the S-NSSAI based on local policy.
  • AMF sends a registration accept message to gNB, which indicates that the registration request has been accepted by AMF. After receiving the registration accept message from AMF, gNB can forward the registration accept message to UE.
  • the network slice selection process can be completed through the interaction between the Modem module and the network device.
  • the steps of the slice selection process described above can be referred to.
  • parts of the process that are not explained in detail please refer to the existing technology and will not be repeated here.
  • the APP can be bound to the target network slice and associated with the PDU session that supports the target network slice.
  • the modem module can also feed back the indication of successful association to the network slice selection SDK.
  • the terminal device associates the application with the PDU session that supports the target network slice, that is, the terminal device routes the data flow of the application to the PDU session. If there is no PDU session that supports the target network slice that the APP wants to use, the terminal device initiates the establishment process of the PDU session that supports the target network slice in order to associate the application with the established PDU session.
  • the PDU session establishment process may include the following steps:
  • Step 1 The modem of the terminal device sends a PDU session establishment request to the AMF.
  • the terminal device can send a PDU session establishment request (PDU session establishment request) to the AMF through a non-access stratum (NAS) message.
  • PDU session establishment request PDU session establishment request
  • NAS non-access stratum
  • the PDU session establishment request may include parameters such as PDU session ID (PDU session ID), PDU session type (PDU Session type), SSC Mode, DNN, S-NSSAI (S-NSSAI corresponding to the service).
  • PDU session ID PDU session ID
  • PDU session type PDU Session type
  • SSC Mode DNN
  • S-NSSAI S-NSSAI corresponding to the service.
  • the S-NSSAI in the PDU session establishment request can be a network slice identifier in one of the three indication methods described above.
  • the S-NSSAI carried in the PDU session request message is forwarded to the AMF via the wireless network.
  • the AMF checks the S-NSSAI in the PDU session request message, selects the corresponding SMF according to the slice capabilities supported by each SMF in the network, and forwards the session establishment request to the SMF.
  • Step 2.AMF sends a PDU session create request (PDU session create request) to SMF.
  • AMF can send a PDU session creation request to SMF via HTTP2POST.
  • the PDU session creation request can contain parameters such as SUPI, DNN, PDU Session ID, S-NSSAI, Request Type, etc.
  • SMF can establish the context of PDU session.
  • SMF can obtain the subscription information of the user response from UDM, and then send policy control messages to UPF, RAN and terminal equipment, and UPF, RAN and terminal equipment establish the connection of PDU session.
  • Step 3 SMF sends a session creation response (PDU session create response) to AMF.
  • SMF After SMF determines that the PDU session connection is established, it can send a session creation response to AMF, indicating that the PDU The session was established successfully.
  • Step 4.AMF sends PDU session establishment accept to the terminal device.
  • the AMF replies to the terminal device with a session establishment request response, indicating that the PDU session is successfully established.
  • the terminal device associates the application with the newly established PDU session, that is, the terminal device routes the application's data flow to the newly established PDU session.
  • the terminal device re-matches other URSP rules and initiates the establishment of the PDU session based on the re-matched URSP rules.
  • the above explanation is based on the example of the network slice selection SDK determining a target network slice corresponding to the APP based on the URSP rule. If the network slice selection SDK determines multiple target network slices corresponding to the APP based on the URSP rule, it is also the same. There may be a phenomenon that one or more network slices are rejected for registration. It is understandable that the APP will eventually be bound to one of the target network slices, and the APP is associated with the PDU session that supports the target network slice.
  • the network slice selection SDK determines the data processing level of the APP's business data in the UE according to the target network slice.
  • the network slice selection SDK can also determine the data processing level of the APP's business data in the UE according to the target network slice.
  • the network slice selection SDK can explicitly indicate the data processing level of the application in the terminal device by adding the first indication information in the newly defined network slice identifier; in the second possible implementation method mentioned above, the network slice selection SDK can explicitly indicate the data processing level of the application in the terminal device by adding the second indication information in the existing network slice identifier and the type of network slice; in the third possible implementation method mentioned above, the network slice selection SDK implicitly indicates the data processing level of the application in the terminal device through the existing network slice identifier.
  • the network slice selection SDK determines the data processing level of the APP's business data in the UE according to the target network slice, as well as a detailed explanation of the data processing level, can be found in the previous article and will not be repeated here.
  • the UE processes the service data of the APP according to the data processing level.
  • the UE After determining the data processing level of the service data of the APP in the UE, the UE can process the service data of the APP according to the corresponding data processing level.
  • the business data of the APP is matched with the data processing level inside the UE, which can ensure the corresponding requirements of the business data (such as low latency, high rate, high priority, etc.), and avoid the problem of poor business experience caused by the mismatch between network slicing performance and the data processing situation inside the terminal.
  • the TD parameter of the S-NSSAI includes a newly defined IS parameter, and a new network slice selection rule provided in this embodiment is set in the RSD of the URSP rule.
  • the IS parameter corresponds to one or more values
  • different IS parameter values correspond to different network slices.
  • the network slice The slice selection SDK can match the target network slice corresponding to the APP based on the IS parameters. For example, IS 1 corresponds to network slice NSSAI 1, and IS 2 corresponds to network slice NSSAI 2.
  • the first indication information in the newly defined network slice identifier is an IS parameter. If the IS parameter value sent by the first APP to the network slice selection SDK is the same as the value of the first indication information (i.e., IS parameter) in the first network slice identifier, the network slice corresponding to the first APP is the first network slice.
  • the IS parameter can also be used to determine the data processing level of the application in the terminal device. At this time, the network slice selection SDK can determine the data processing level of the APP in the terminal device based on the IS parameter.
  • different IS parameter values correspond to different data processing levels. For example, IS 1 corresponds to a low-latency processing level, and IS 2 corresponds to a high-latency processing level.
  • the IS parameter value of the target APP can be determined by negotiation between the developer of the APP and the manufacturer of the terminal device, for example, the developer of the APP can purchase it from the manufacturer of the terminal device. In this way, the developer of the target APP can negotiate with the manufacturer of the terminal device to determine the data processing level that meets its business needs.
  • APP sends an activation request to establish a network connection service to the network slice selection SDK.
  • the activation request may include the TD (Traffic Descriptor) parameter of the APP, and the TD parameter includes the IS parameter.
  • TD Traffic Descriptor
  • the network slice selection SDK determines the target network slice corresponding to the APP based on the IS parameters, and sends the identifier of the target network slice to the OS module.
  • the identification of the target network slice includes IS parameters.
  • the OS module sends the identifier of the target network slice to the Modem module.
  • the Modem module interacts with the network device, associates the APP to the PDU session that supports the target network slice, and feeds back the indication of successful association to the network slice selection SDK.
  • the network slice selection SDK determines the data processing level of the APP's business data in the UE based on the IS parameter in the target network slice identifier.
  • the UE processes the service data of the APP according to the data processing level.
  • a newly defined IS parameter is added to the RSD parameter of the URSP rule.
  • the IS parameter corresponds to one or more values, and different IS parameter values correspond to different data processing levels.
  • the network slice selection SDK can determine the data processing level of the APP in the terminal device according to the IS parameter. For example, IS 1 corresponds to a low latency processing level, and IS 2 corresponds to a high latency processing level.
  • the embodiment of the present application also adds a security verification mechanism on the network slicing selection SDK side.
  • an embodiment of the present application provides a communication method, which may specifically include the following steps:
  • the APP sends an activation request to the network slice selection SDK to establish a network connection service.
  • the activation request includes the TD parameters of the APP and the TD parameter signature.
  • the TD parameter signature is generated by encrypting the hash value of the TD parameter.
  • the TD parameters may include the aforementioned IS parameters.
  • the subsequent processing flow is as described above. This will not be elaborated on.
  • the network slice selects SDK to perform security verification on the APP based on TD parameters and TD parameter signature.
  • the grid slice selects SDK to decrypt the TD parameter signature and obtain the hash value of the TD parameter.
  • the APP is security verified. If the hash value of the TD parameter obtained by decryption is consistent with the hash value of the TD parameter obtained by parsing the activation request, the APP security verification succeeds, otherwise the APP security verification fails.
  • the TD parameter signature is generated based on the signature private key encryption, and the grid slice selection SDK decrypts the TD parameter signature according to the signature public key paired with the signature private key.
  • the TD parameter signature of the APP is generated by the terminal server corresponding to the UE encrypting the hash value of the TD parameter of the APP based on the signature private key.
  • the terminal server sends the signature public key paired with the signature private key to the UE (such as to the network slice selection SDK of the UE), and the network slice selection SDK stores the signature public key locally.
  • the grid slice selection SDK parses the TD parameters and TD parameter signature in the activation request, decrypts the TD parameter signature based on the locally stored signature public key, and uses the decrypted TD parameter hash value as security verification information.
  • the grid slice selection SDK verifies the parsed TD parameters based on the security verification information (i.e. the decrypted TD parameter hash value) to determine whether the two hash values are consistent. If so, it is determined that the APP security verification is successful, otherwise it is determined that the APP security verification fails.
  • the grid slice selection SDK parses the TD parameters and TD parameter signature in the activation request, decrypts the TD parameter signature based on the locally stored signature public key, and uses the hash value of the decrypted TD parameter as security verification information.
  • the grid slice selection SDK sends the security verification information (i.e., the hash value of the decrypted TD parameter) to the corresponding terminal server to perform security verification on the APP through the terminal service.
  • the terminal server performs security verification on the APP based on the received security verification information, and determines whether the security verification information is consistent with the hash value of the TD parameter of the corresponding APP. If so, it feeds back an indication of successful security verification to the UE's grid slice selection SDK, otherwise it feeds back an indication of failed security verification to the UE's grid slice selection SDK.
  • the network slice selection SDK determines the target network slice corresponding to the APP according to the TD parameters, and sends the identifier of the target network slice to the OS module.
  • the OS module sends the identifier of the target network slice to the Modem module.
  • the Modem module interacts with the network device, associates the APP to the PDU session that supports the target network slice, and feeds back the indication of successful association to the network slice selection SDK.
  • the network slice selection SDK determines the data processing level of the APP's business data in the UE according to the target network slice.
  • the UE processes the service data of the APP according to the data processing level.
  • the UE can not only ensure the corresponding requirements of business data (such as low latency, high rate, high priority, etc.), avoid the problem of poor business experience caused by the mismatch between network slicing performance and the internal data processing situation of the terminal, but also perform security verification on the APP before associating the APP with the network slice to avoid the abuse of network slices.
  • business data such as low latency, high rate, high priority, etc.
  • the network slice selection SDK can also update the URSP rules (including network slice selection rules) configured on the terminal side to determine the network slice corresponding to the APP through the updated URSP rules. slice, and determine the data processing level of the APP in the terminal device.
  • the URSP rules including network slice selection rules
  • the updated URSP rules can be sent to the terminal side through the network device.
  • the H-PCF can configure the updated network slice selection rules to the terminal device through the AMF and gNB.
  • the updated URSP rules can be configured to the terminal device through a registration command message.
  • the communication operator can configure the updated URSP rules to the terminal device.
  • the updated URSP rules are received by the Modem module of the UE and sent to the network slice selection SDK through the Modem module.
  • the URSP rule when the URSP rule is configured on the terminal side, the URSP rule can be updated based on the terminal platform or the SDK platform of the terminal.
  • the embodiment of the present application adopts a terminal-centric solution. Compared with the operating system-centric solution and the modem-centric solution, the cycle required for updating the URSP rules is shorter, and the URSP rules are more limited to maintenance management.
  • This embodiment further provides a computer storage medium, in which computer instructions are stored.
  • the computer instructions are executed on an electronic device, the electronic device executes the above-mentioned related method steps to implement the communication method in the above-mentioned embodiment.
  • This embodiment also provides a computer program product.
  • the computer program product When the computer program product is run on a computer, the computer is enabled to execute the above-mentioned related steps to implement the communication method in the above-mentioned embodiment.
  • an embodiment of the present application also provides a device, which can specifically be a chip, component or module, and the device may include a connected processor and memory; wherein the memory is used to store computer-executable instructions, and when the device is running, the processor can execute the computer-executable instructions stored in the memory so that the chip executes the communication method in the above-mentioned method embodiments.
  • the electronic device such as a mobile phone, etc.
  • computer storage medium, computer program product or chip provided in this embodiment is used to execute the corresponding method provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method provided above, and will not be repeated here.
  • the disclosed devices and methods can be implemented in other ways.
  • the device embodiments described above are only schematic, for example, the division of modules or units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed.
  • Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

Landscapes

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

Abstract

本申请实施例提供了一种通信方法及终端设备。该方法应用于终端设备中，SDK模块获取目标APP发送的TD参数；基于URSP规则，SDK模块根据TD参数确定目标APP对应的目标网络切片，并将目标网络切片的标识发送给OS模块，通过OS模块发送至Modem模块；Modem模块根据目标网络切片的标识与网络设备进行交互，将目标APP关联到支持目标网络切片的PDU会话上；目标APP业务数据按照与目标网络切片匹配的数据处理等级在终端设备中进行处理。这样，采用终端中心化的方案更便于对网络切片选择规则的更新、管理以及维护，且APP的业务数据在终端内的处理级别与网络切片匹配，能够充分发挥网络切片的优势。

Description

通信方法及终端设备
本申请要求于2022年12月12日提交中国国家知识产权局、申请号为202211589413.9、申请名称为“通信方法及终端设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及智能终端技术领域，尤其涉及一种通信方法及终端设备。
背景技术
网络切片(network slice)是一个用于支持特定网络能力与网络特性的逻辑隔离网络，是满足第三代合作伙伴项目(3rd generation partnership project，3GPP)提出的第五代(5th generation，5G)移动通信技术关于网络差异化需求的关键技术。
通常，不同网络切片的网络特征并不相同，且要求网络切片之间相互隔离，互不影响。例如，增强型移动宽带业务(enhanced mobile broadband，eMBB)业务的网络切片可以提供比4G快10倍以上的传输速率，可应用于当下流行的增强实现(augmented reality，AR)或虚拟实现(virtual reality，VR)、高清视频直播中，让用户获得快捷的体验。大规模机器通信(Massive Machine-Type Communications，mMTC)业务的网络切片要求支持海量终端接入，但带宽小，对时延没要求。超可靠低时延通信(ultra-reliable low-latency communication，URLLC)业务的网络切片具有大带宽、低时延和高可靠性的特点，可应用于云游戏、自动驾驶等场景。
由此，不同类型的网络切片适用于不同的数据传输场景。然而，现有的5G标准中没有描述如何为不同的应用程序确定匹配的网络切片，以使应用程序的数据流可以通过相应的网络切片进行传输。
发明内容
为了解决上述技术问题，本申请实施例提供一种通信方法及终端设备。该方法采用终端中心化的方案，为应用程序确定匹配的网络切片以及在终端设备中的数据处理级别，使得网络切片选择规则的更新、管理以及维护更加便捷，而且应用程序业务数据在终端内的处理级别与网络切片匹配，也能够充分发挥网络切片的优势。
第一方面，本申请实施例提供了一种通信方法。该方法应用于终端设备中，终端设备包括SDK模块、OS模块和Modem模块。其中，该方法包括：
SDK模块获取目标APP发送的建立网络连接服务的激活请求；其中，激活请求中包括TD参数；基于URSP规则，SDK模块根据TD参数确定目标APP对应的目标网络切片，并将目标网络切片的标识发送给OS模块；OS模块将目标网络切片的标识发送至Modem模块；Modem模块根据目标网络切片的标识与网络设备进行交互，将目标APP 关联到支持目标网络切片的PDU会话上；其中，目标APP的业务数据按照与目标网络切片匹配的数据处理等级在终端设备中进行处理。
其中，目标APP可以是运行在终端设备中的任一需要建立网络连接服务的APP。其中，不同APP对网络连接服务的需求不尽相同，如高速率、大带宽、低时延等。
该方法采用终端中心化的方案，为应用程序确定匹配的网络切片以及在终端设备中的数据处理级别。相比于调制解调器中心化方案以及操作系统中心化方案，这样使得网络切片选择规则的更新、管理以及维护更加便捷，而且应用程序业务数据在终端内的处理级别与网络切片匹配，也能够充分发挥网络切片的优势。
根据第一方面，激活请求中还包括TD参数签名；相应的SDK模块根据TD参数确定目标APP对应的目标网络切片，可以包括：SDK模块在根据TD参数签名确定目标APP安全验证成功时，根据TD参数确定目标APP对应的目标网络切片。
其中，TD参数签名可以是对TD参数的哈希值加密而生成的。
这样，SDK模块采用安全验证机制对APP进行安全验证，能够避免出现APP滥用网络切片的问题。
根据第一方面，或者以上第一方面的任意一种实现方式，SDK模块在根据TD参数签名确定目标APP安全验证成功，可以包括：
SDK模块根据签名公钥对TD参数签名进行解密，得到第一哈希值；TD参数签名是基于与签名公钥成对的签名私钥而生成的；SDK模块如果确定第一哈希值和第二哈希值一致，则确定目标APP安全验证成功；其中，第二哈希值是对目标APP的TD参数进行哈希计算得到的。
根据第一方面，或者以上第一方面的任意一种实现方式，该方法还包括：Modem模块接收更新后的URSP规则，并将更新后的URSP规则发送至SDK模块，以使SDK模块对本地URSP规则进行更新。
本申请实施例采用终端中心化方案，相对于操作系统中心化方案以及Modem中心化方案，更新URSP规则所需的周期更短，URSP规则更限于维护管理。
根据第一方面，或者以上第一方面的任意一种实现方式，该方法还包括：SDK模块根据目标网络切片的第一标识，确定目标APP的业务数据在终端设备中的数据处理等级；或者，
SDK模块根据目标网络切片的第二标识以及目标网络切片的类型，确定目标APP的业务数据在终端设备中的数据处理等级；或者，
SDK模块根据目标网络切片的类型或目标网络切片的优先级，确定目标APP的业务数据在终端设备中的数据处理等级。
其中，第一标识为新定义的网络切片的标识。SDK模块根据目标网络切片的第一标识，确定目标APP的业务数据在终端设备中的数据处理等级，可以参照下文第一种可能的实现方式。
第二标识为已有的网络切片标识，但新增了相关指示信息。SDK模块根据目标网络切片的第二标识以及目标网络切片的类型，确定目标APP的业务数据在终端设备中的数据处理等级，可以参照下文第二种可能的实现方式。
SDK模块根据目标网络切片的类型或目标网络切片的优先级，确定目标APP的业务数据在终端设备中的数据处理等级，可以参照下文第三种可能的实现方式。
由于应用程序业务数据在终端内的处理级别与网络切片匹配的，这样能够充分发挥网络切片的优势，避免出现网络切片性能与业务数据处理级别不匹配而导致的业务体验不佳的问题。
根据第一方面，或者以上第一方面的任意一种实现方式，SDK模块根据目标网络切片的第一标识，确定目标APP的业务数据在终端设备中的数据处理等级，包括：
SDK模块根据目标网络切片的第一标识中的第一指示信息，确定目标APP的业务数据在终端设备中的数据处理等级；其中，第一标识为网络切片的自定义标识，第一指示信息用于指示APP在终端设备中的数据处理级别。
其中，第一指示信息可以参照下文第一种可能的实现方式。
根据第一方面，或者以上第一方面的任意一种实现方式，SDK模块发送给OS模块的目标网络切片的标识，以及OS模块发送给Modem模块的目标网络切片的标识，为目标网络切片的第一标识。
根据第一方面，或者以上第一方面的任意一种实现方式，SDK模块根据目标网络切片的第二标识以及目标网络切片的类型，确定目标APP的业务数据在终端设备中的数据处理等级，可以包括：
SDK模块根据目标网络切片的第二标识中的第二指示信息，以及目标网络切片的类型，确定目标APP的业务数据在终端设备中的数据处理等级；其中，第二标识为通信协议中规定的网络切片标识，第二指示信息为网络切片标识中新增的指示信息，用于指示APP在终端设备中的数据处理级别。
其中，第一指示信息可以参照下文第二种可能的实现方式。
根据第一方面，或者以上第一方面的任意一种实现方式，SDK模块发送给OS模块的目标网络切片的标识，以及OS模块发送给Modem模块的目标网络切片的标识，为目标网络切片的第二标识。
根据第一方面，或者以上第一方面的任意一种实现方式，数据处理级别涉及的方面包括下述至少一项：优先级、时延、速率、数据安全、数据可靠性。
相应的，数据处理级别可以为优先处理级别、时延处理级别、速率处理级别、安全处理级别、可靠处理级别等。
根据第一方面，或者以上第一方面的任意一种实现方式，在SDK模块根据目标网络切片的第一标识，确定目标APP的业务数据在终端设备中的数据处理等级的情形下，第一指示信息为目标参数；目标APP的TD参数包括目标参数；相应的，
SDK模块根据TD参数确定目标APP对应的目标网络切片，可以包括：
SDK模块将第一网络切片作为目标APP对应的目标网络切片；其中，第一网络切片的第一标识中目标参数值与目标APP的目标参数值相同。
其中，目标参数可以为下文提及的IS参数。
这样，SDK模块可以基于目标参数值为APP匹配对应的目标网络切片。
根据第一方面，或者以上第一方面的任意一种实现方式，目标参数的值不同时， APP在终端设备中的数据处理级别不同。
根据第一方面，或者以上第一方面的任意一种实现方式，目标APP的目标参数值是目标APP的开发方与终端设备的生产方协商确定的。
这样，目标APP的开发方可以同终端设备的生产方协商确定满足其业务需求的数据处理级别。
第二方面，本申请实施例提供了一种终端设备，该终端设备包括一个或多个处理器；存储器；以及一个或多个计算机程序，其中一个或多个计算机程序存储在存储器上，当计算机程序被一个或多个处理器执行时，使得终端设备执行如第一方面或第一方面中任意一项的通信方法。
其中，该终端设备包括SDK模块、OS模块和Modem模块。
SDK模块用于：获取目标APP发送的建立网络连接服务的激活请求；其中，激活请求中包括通路描述符TD参数；
SDK模块还用于：基于UE路由选择策略URSP规则，根据TD参数确定目标APP对应的目标网络切片，并将目标网络切片的标识发送给OS模块；
OS模块用于：将目标网络切片的标识发送至Modem模块；
Modem模块用于：根据目标网络切片的标识与网络设备进行交互，将目标APP关联到支持目标网络切片的PDU会话上；
其中，目标APP的业务数据按照与目标网络切片匹配的数据处理等级在终端设备中进行处理。
第二方面以及第二方面的任意一种实现方式分别与第一方面以及第一方面的任意一种实现方式相对应。第二方面以及第二方面的任意一种实现方式所对应的技术效果可参见上述第一方面以及第一方面的任意一种实现方式所对应的技术效果，此处不再赘述。
第三方面，本申请实施例提供了一种芯片，该芯片包括处理电路、收发管脚。其中，该收发管脚和该处理电路通过内部连接通路互相通信，该处理电路执行如第一方面或第一方面中任意一项的通信方法，以控制接收管脚接收信号，以控制发送管脚发送信号。
第三方面以及第三方面的任意一种实现方式分别与第一方面以及第一方面的任意一种实现方式相对应。第三方面以及第三方面的任意一种实现方式所对应的技术效果可参见上述第一方面以及第一方面的任意一种实现方式所对应的技术效果，此处不再赘述。
第四方面，本申请实施例提供一种计算机程序产品，包括计算机程序，当计算机程序被运行时，使得计算机执行如第一方面以及第一方面中任意一项的通信方法。
第四方面以及第四方面的任意一种实现方式分别与第一方面以及第一方面的任意一种实现方式相对应。第四方面以及第四方面的任意一种实现方式所对应的技术效果可参见上述第一方面以及第一方面的任意一种实现方式所对应的技术效果，此处不再赘述。
第五方面，本申请实施例提供一种计算机可读存储介质。该计算机可读存储介质包括计算机程序，当计算机程序在电子设备上运行时，使得电子设备执行第一方面以及第一方面中任意一项的通信方法。
第五方面以及第五方面的任意一种实现方式分别与第一方面以及第一方面的任意一种实现方式相对应。第五方面以及第五方面的任意一种实现方式所对应的技术效果可参见上述第一方面以及第一方面的任意一种实现方式所对应的技术效果，此处不再赘述。
附图说明
图1为S-NSSAI的数据结构示意图；
图2为本申请实施例提供的一种5G通信系统示意图；
图3为本申请实施例提供的一种S-NSSAI的数据结构示意图；
图4为示例性示出的电子设备的硬件结构示意图；
图5为示例性示出的电子设备的软件结构示意图；
图6为本申请实施例提供的通信方法涉及的模块交互流程图；
图7为URSP规则的数据结构示意图；
图8为本申请实施例提供的一种URSP规则的数据结构示意图；
图9为本申请实施例提供的通信方法涉及的模块交互示意图；
图10为本申请实施例提供的通信方法涉及的模块交互流程图；
图11为示例性示出的加密TD参数的场景示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。
本申请实施例的说明书和权利要求书中的术语“第一”和“第二”等是用于区别不同的对象，而不是用于描述对象的特定顺序。例如，第一目标对象和第二目标对象等是用于区别不同的目标对象，而不是用于描述目标对象的特定顺序。
在本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
在本申请实施例的描述中，除非另有说明，“多个”的含义是指两个或两个以上。例如，多个处理单元是指两个或两个以上的处理单元；多个系统是指两个或两个以上的系统。
以下将先对本申请涉及的一些概念进行介绍：
1.网络切片：
5G将开启一个万物互联的时代，5G支持eMBB、mMTC和URLLC三大场景，三大场景中包含了多样化差异化的应用。
eMBB：基于无线侧频谱利用率和频谱带宽技术的突破，5G可以提供比4G快10倍以上的传输速率。对于当下流行的AR/VR、高清视频直播，只有5G超高速率才能满足需求，4G的传输速率是无法支持的。现在使用VR看高清或者大型交互游戏时，必须要拖着网线来获取数据，在未来通过5G网络进行无线连接，VR/AR可以获得快捷的体验。
mMTC：通过多用户共享接入，超密集异构网络等技术，5G可以支持每平方公里接入100万个设备，是4G的10倍。近来智慧城市的快速发展，路灯，井盖，水表等公共设施都已经拥有了网络连接能力，可以进行远程管理，但是5G会有更大的革新。基于5G网络的强大连接能力，才可以把城市各个行业的公共设备都接入智能管理平台。这些公共设施通过5G网络协同工作，只需要少量的维护人员就可以统一管理，大大提升城市的运营效率。
URLLC：在5G场景下最典型的应用就是自动驾驶，自动驾驶最常用的场景如急刹车、车对车，车对人，车对基础设施等多路通信同时进行，需要瞬间进行大量的数据处理并决策。因此需要网络同时具有大带宽、低时延和高可靠性，5G网络具备应对这种场景的能力。
4G时代是通过一张网络满足所有的应用场景和客户群体，例如网络要提供窄带物联网(Narrowband Internet of Things，NB-IoT)能力就开通网元上的NB相关特性，要构筑网络可靠性，就增加网元设备级的冗余备份，通过不断叠加特性去满足大众市场不断提出的诉求。
但是垂直行业中各种业务在时延、连接数、可靠性、安全性等方面的要求相去甚远而且具有不可预知性，比如AR业务需要使用>1600Mbps的网络超高带宽、能源抄表业务需要网络提供海量连接，自动驾驶需要网络保证几毫秒的端到端低时延以及99.999％以上的高可靠性，如果还想通过一张网络满足目前所有需求以及未来可能提出的需求，根本不可能实现。
网络切片技术可以让运营商在一个硬件基础设施切分出多个虚拟的网络，按需分配资源、灵活组合能力，满足各种业务的不同需求。当新需求提出而目前网络无法满足要求时，运营商只需要为此需求虚拟出一张新的切片网络，而不需要影响已有的切片网络，以最快速度上线业务。
网络切片是通过切片技术在一个通用硬件基础上虚拟出多个端到端的网络，每个网络具有不同网络功能，适配不同类型服务需求。运营商购买物理资源后，针对大众上网业务使用物理资源虚拟出一个eMBB切片网络，之后再针对垂直行业中某些厂商的智能抄表需求，使用物理资源再虚拟出一个mMTC切片网络，两个切片网络分别为不同业务场景提供服务。
虽然垂直行业中各行各业对对网络功能的需求多种多样，但是这些需求都可以解析成对网络带宽、连接数、时延、可靠性等网络功能的需求。5G标准也将不同业务对网络功能的需求特点归纳为三大典型场景，相应的这三大典型场景对应的网络切片的类型分别是eMBB切片、mMTC切片、URLLC切片。
2.单网络切片选择辅助信息(Single Network Slice Selection Assistance Information，S-NSSAI)：
S-NSSAI用来标识一个网络切片。根据运营商的运营或部署需要，一个S-NSSAI可以关联一个或多个网络切片实例，一个网络切片实例可以关联一个或多个S-NSSAI。例如，eMBB切片1、eMBB切片2和eMBB切片3都是eMBB类型的切片，它们的S-NSSAI值都是0x01000000；eMBB+mMTC切片4既可以为eMBB类型业务提供服务，同时又可以为mMTC业务提供服务，所以它既是eMBB类型切片，又是mMTC类型的切片，对应的S-NSSAI值分别是0x01000000和0x02000000。
如图1所示，S-NSSAI包括切片/服务类型(Slice/ServiceType，SST)和切片差异(Slice Differentiator，SD)两部分：
SST是指在特性和服务方面预期的网络切片行为。SST的标准取值范围为1、2、3，取值1表示eMBB、2表示URLLC、3表示大规模物联网(Massive Internet of Things，MIoT)。
SD是一个可选信息，用来补充SST以区分同一个切片/业务类型的多个网络切片。
SST和SD两部分结合起来表示切片类型及同一切片类型的多个切片。例如S-NSSAI取值为0x01000000、0x02000000、0x03000000分别表示eMBB类型切片、URLLC类型切片、MIoT类型切片。而S-NSSAI取值为0x01000001、0x01000002则表示eMBB类型切片，分别服务于用户群1和用户群2。
3.网络切片选择辅助信息(Network Slice Selection Assistance Information，NSSAI)：
NSSAI是S-NSSNI的集合。5G网络中使用到的NSSAI有请求的NSSAI(Requested NSSAI)、允许的NSSAI(Allowed NSSAI)、配置的NSSAI(Configured NSSAI)，它们的具体定义如表1所示。
表1

4.切片选择流程
在UE注册流程中，无线接入网(radio access network，RAN)首先根据本地存储信息及UE注册请求消息为UE选择一个初始AMF为其提供服务。但是初始AMF可能不支持UE要使用的网络切片，例如初始AMF只支持URLLC类型网络切片，但是UE请求的是eMBB类型的网络切片。如果初始AMF无法为UE提供服务，则初始AMF向网络切片选择功能(network sliceselection function，NSSF)查询和选择能支持UE网络切片的目标AMF，然后将UE的注册请求消息通过直接或间接的方式发送给目标AMF，由目标AMF处理UE的注册请求进而为UE提供网络服务。具体可以包括如下步骤：
步骤1.UE通过一种接入类型注册到一个PLMN上时，发送注册请求消息给RAN。如果UE上存储有此PLMN的Configured NSSAI或者此PLMN此接入类型的Allowed NSSAI，那么UE将在非接入层(non-access stratum，NAS)注册请求消息以及AN消息中携带Requested NSSAI信息，Requested NSSAI包含UE希望注册的切片的S-NSSAI。
步骤2.RAN根据全球唯一AMF标识(globally unique AMF identifier，GUAMI)或Requested NSSAI选择初始AMF。如果UE没有在AN消息中提供Requested NSSAI和GUAMI，则RAN应将来自UE的注册请求消息发送给缺省AMF。
步骤3.初始AMF查询统一数据管理(unified data management，UDM)获取包括Subscribed S-NSSAIs在内的UE签约信息。初始AMF根据收到的Requested NSSAI、Subscribed S-NSSAI及本地配置判断是否可以为UE提供服务。如果AMF可以为UE服务，则初始AMF仍然是UE的服务AMF，然后AMF基于Subscribed S-NSSAI和Requested NSSAI构造出Allowed NSSAI，并通过注册接受消息将Allowed NSSAI返回给UE。如果初始AMF无法为UE服务或者无法做出判断，则AMF需要向NSSF进行查询。
步骤4.AMF将Requested NSSAI、Subscribed S-NSSAI、签约永久标识(subscription permanent identifier，SUPI)的PLMN、跟踪区标识(tracking area identifier，TAI)等信息发送给NSSF进行查询。
步骤5.NSSF根据接收到的信息及本地配置，选出可以为UE服务的AMF集合(AMF Set)或候选AMF列表、适用于此次接入类型的Allowed NSSAI，可能还选出为UE服务的网络切片实例、实例内用于选择网络功能(network function，NF)的网络存储功能(network repository function，NRF)，并将这些信息发送给初始AMF。
步骤6.如果初始AMF不在AMF Set内且本地未存储AMF地址信息，则初始AMF通过查询NRF获得候选AMF列表。NRF返回一组可用的AMF列表，包括AMF指针(AMF Pointer)和地址信息。初始AMF从中选择一个作为目标AMF。如果初始AMF无法通过查询NRF获得候选AMF列表，则初始AMF需要通过RAN将UE的注册请求消息发给目标AMF，初始AMF发送给RAN的消息里面包含AMF Set和Allowed NSSAI。
步骤7.如果初始AMF基于本地策略和签约信息决定直接将NAS消息发送给目标AMF，则初始AMF将UE注册请求消息以及从NSSF获得的除了AMF集合之外的其他信息都发送给目标AMF。
如果初始AMF基于本地策略和签约信息决定将NAS消息通过RAN转发给目标AMF，则初始AMF向RAN发送一条重路由(Reroute)NAS消息。Reroute NAS消息包括目标AMF Set信息和注册请求消息，以及从NSSF获得的相关信息。
步骤8.在接收到步骤7中发送的注册请求消息后，目标AMF继续执行注册流程的相关步骤，最终向UE发送注册接受消息，消息中携带Allowed NSSAI等信息。
随着网络切片技术的引入，运营商将能够提供不同功能特点的网络能力，为不同业务需求的用户提供“专属”的网络，保障优质化的服务水平，满足差异化的业务需求。而用户也能够使用更加炫酷的应用产品，进一步激发新的行业应用蓝海大发展。最终实现提升网络资源使用效率、优化运营商网络建设投资、构建灵活敏捷的5G网络的目标。
下述以云游戏应用对网络切片的需求为例进行解释说明。
云游戏应用是基于实时音视频流技术实现的，由服务端向客户端发送实时的音视频流，客户端向服务端发送控制指令流，并由服务端将接收到的控制指令应用到游戏中。整个数据处理回路涉及到：服务端游戏渲染、音视频编码、网络传输，以及客户端音视频解码和渲染等过程。这些过程都有一定程度的耗时，但网络传输是对用户体验影响最大的因素。鉴于云游戏特殊的业务场景，对网络提出了更高的要求：低延迟、高带宽、无抖动(或小抖动)。
由此，云游戏应用对网络切片的需求为低延迟需求。若使用目前已有的4G网络和Wi-Fi(wireless fidelity，无线保真)网络，在网络正常的情况下，云游戏的响应延迟大约在50ms～140ms范围内波动。对于一些对操作响应延迟要求较高的游戏(例如：动作类游戏、格斗类游戏、多人在线战术竞技类游戏、第一人称射击类游戏、赛车类游戏等)，云游戏与本地游戏在体验上有较为明显的差距，需要进一步降低操作响应延迟。VR设备由于其头显的特殊性，在延迟较大时会使人产生晕动症(motion sickness)，也需要把延迟控制在20ms以内才能有效控制排斥反应。
鉴于不同应用程序的业务场景不同，故不同应用程序对网络切片的需求也不尽相同。由此，终端设备如何基于应用程序的业务特征或业务需求等，确定与应用程序匹配的网络切片，以将应用程序关联到支持该网络切片的PDU(Protocol Data Unit，协议数据单元)会话上，使应用程序的业务数据可以通过支持该网络切片的PDU会话进行传输或路由，是需要解决的问题。
URSP(UE Route Selection Policy，UE路由选择策略)规则，是对终端进行网络切片配置与管理的核心规则，在网络切片业务流程中作用于终端，用于指导终端根据业务特征将业务数据关联到匹配的网络切片上。然而，目前URSP机制在标准中还没完全确定下来，故需要制定一些标准化的机制来实现URSP方案，以进一步实现产业化。
图2示出了本申请实施例提供的一种5G通信系统示意图。该通信系统可以包括UE、(R)AN设备、AMF设备、会话管理功能(Session Management function，SMF)设备、用户面功能(User Plane Function，UPF)设备、策略控制功能(Policy Control Function，PCF)设备、NSSF设备、应用功能(application function，AF)设备、UDM设备中的至少一项。
本申请实施例中的终端设备，如图2所示的UE，可以是用于实现无线通信功能的设备，例如其可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。其中，终端设备可以是5G网络或者未来演进的PLMN中的UE、接入终端、终端单元、终端站、移动站、移动台、远方站、远程终端、移动设备、无线通信设备、终端代理或终端装置等。接入终端可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备或可穿戴设备，虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。终端设备可以是移动的，也可以是固定的。
本申请实施例中的接入网设备，如图2所示的(R)AN设备，是一种为终端设备提供无线通信功能的设备。例如，基站包括但不限于：5G中的下一代基站(gnodeB，gNB)、演进型节点B(evolved node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(basestation controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved nodeB，或home node B，HNB)、基带单元(baseBand unit，BBU)、传输点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、移动交换中心。
本申请实施例中的移动性管理网元，如图2所示的AMF设备，主要功能包含：连接管理、移动性管理、注册管理、接入认证和授权、可达性管理、安全上下文管理等接入和移动性相关的功能。
本申请实施例中的会话管理网元，如图2所示的SMF设备，用于移动网络中的会话管理，如会话建立、修改、释放。具体功能包括为终端设备分配互联网协议(internet protocol，IP)地址、选择提供报文转发功能的UPF、业务和会话连续性(Service and Session Continuity，SSC)模式选择、漫游等会话相关的功能。
本申请实施例中的用户面功能网元，如图2所示的UPF设备，主要功能包含：数据包路由和传输、包检测、业务用量上报、QoS处理、合法监听、上行包检测、下行数据包存储等用户面相关的功能。UPF可连接至数据网络(data network，DN)。
本申请实施例中的策略控制功能网元，如图2所示的PCF设备，主要功能包含：统一策略制定、策略控制的提供和从用户数据库(User Data Repository，UDR)中获取策 略决策相关的签约信息等策略相关的功能。
本申请实施例中的网络切片选择功能网元，如图2所示的NSSF设备，主要功能包含：为UE选择一组网络切片实例、确定允许的NSSAI和确定可以服务UE的AMF集等。
本申请实施例中的应用功能网元，如图2所示的AF设备，负责与3GPP核心网交互提供业务或者服务，包括与网络能力开放功能(network exposure function，NEF)交互，策略架构交互等。
本申请实施例中的统一数据管理网元，如图2所示的UDM设备，支持3GPP认证和秘钥协商机制中的认证信任状处理，用户身份处理，接入授权，注册和移动性管理，签约管理，短消息管理等。
上述各网元既可以由指定的硬件实现、或者，也可以由在指定硬件上的软件实例实现、或者，也可以由在合适的平台上实例化的虚拟功能来实现，本申请并不在此限制。
在服务化架构下，控制面内使用基于服务的接口(service-based interface)。例如，Namf是AMF网元提供的基于服务的接口，AMF网元可以通过Namf与其他的网络功能通信。Nsmf是SMF提供的基于服务的接口，SMF可以通过Nsmf与其他的网络功能通信。Nnssf是NSSF网元提供的基于服务的接口，NSSF网元可以通过Nnssf与其他的网络功能通信。一个功能网元通过基于服务的接口，可以向被授权的其他功能网元开放它的能力，从而提供网络功能(network function，NF)服务。换句话说，NF服务就是指能被提供的各种能力。
此外，本申请实施例还可以适用于面向未来的其他通信技术。本申请描述的网络架构以及业务场景是为了更加清楚的说明本申请的技术方案，并不构成对本申请提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请提供的技术方案对于类似的技术问题，同样适用。其中，本申请适用于布局了网络切片通信网络。网络切片是一个用于支持特定网络能力与网络特性的逻辑隔离的网络。
为了解决上述问题，本申请实施例提供了一种新的网络切片选择(network slice selection)规则。在相应的通信方法中，UE可以根据这种新的网络切片选择规则，确定与不同应用程序分别匹配的网络切片，以将应用程序关联到支持相应网络切片的PDU会话上，而且UE还可以根据这种新的网络切片选择规则，确定应用程序的业务数据终端设备内部的数据处理级别。
需要指出的是，UE将第一应用程序关联到支持第一网络切片的PDU会话上，指的是UE将第一应用程序的数据流通过支持第一网络切片的PDU会话进行传输或路由。
其中，本申请实施例提供的一种新的网络切片选择规则属于URSP规则的一部分。例如，网络切片选择规则可以设置于URSP规则的路由选择描述符(route selection descriptor，RSD)中。由此，也可以称之为本申请实施例提供了一种新的URSP规则。
目前，主流的URSP规则执行方式包括调制解调器(Modem)中心化方案和操作系统(Operating System，OS)中心化方案。其中，在调制解调器中心化方案中，业务属 性与网络切片的匹配过程等在终端的调制解调器中实现，由终端的Modem依据URSP规则实现终端业务应用的特征属性与网络切片之间的对应绑定。在操作系统中心化方案中，业务属性与网络切片的匹配过程等在终端的操作系统中实现，由终端的操作系统依据URSP规则实现终端业务应用的特征属性与网络切片之间的对应绑定。
本申请实施例采用终端中心化方案。在本申请实施例中，业务属性与网络切片的匹配过程，以及业务数据与数据处理级别的匹配过程等在终端中实现，例如在终端公司开发维护的SDK(Software Development Kit，软件开发工具包)或中间件中实现，由终端中的SDK或中间件依据新的网络切片选择规则(或称新的URSP规则)实现中终端应用程序与网络切片之间的对应绑定。
相比于调制解调器中心化方案以及操作系统中心化方案，本申请实施例提供的终端中心化方案，更便于对网络切片选择规则的更新、管理以及维护。而且，终端公司的主动权更高，更加利于生态合作。其中，APP(application，应用程序)开发方可以与终端设备方协商确定网络切片选择规则，具体可以协商确定与APP对应的网络切片，以及APP在终端设备中的数据处理级别。这样，终端中的SDK或中间件可以依据相应的网络切片选择规则为应用程序选取匹配的网络切片，以将应用程序关联到支持相应网络切片的PDU会话上，而且APP的业务数据在终端设备中可以按照相应的数据处理级别进行处理。
其中，本申请实施例提供的新的网络切片选择规则，可以由标准组织(如3GPP)进行定义，也可以由通信运营商进行定义。新的网络切片选择规则配置在网络侧或终端侧。网络侧可以是指网络设备，例如可以包括gNB(the next Generation Node B，下一代基站)、AMF、SMF(Session Management function，会话管理功能)、PCF(Policy Control function，策略控制功能)等网络设备(或称网元)，终端侧可以是指终端设备，例如UE。
当新的网络切片选择规则配置在网络侧时，网络切片选择规则可以通过网络设备下发至终端侧。在一种实现方式中，H-PCF(归属地的PCF)可以通过AMF和gNB将新的网络切片选择规则配置给终端设备。例如，新的网络切片选择规则可以通过注册命令(registration command)消息配置给终端设备。在一种实现方式中，通信运营商可以向终端设备配置新的网络切片选择规则。
在本申请实施例提供的一种新的网络切片选择规则中，可以包括应用程序与网络切片之间的映射关系，还可以包括应用程序在终端设备中的数据处理级别与应用程序对应的网络切片之间的映射关系。这样，新的网络切片选择规则不仅可以用于确定应用程序对应的网络切片，支持相应网络切片的PDU会话，还可以用于确定应用程序在终端设备中的数据处理级别。
其中，数据处理级别，也可以称之为数据处理等级、数据处理方式、内部处理等级/方式等，用于指示APP在终端内部进行数据处理时的级别划分。示例性的，数据处理级别可以是优先处理级别、时延处理级别、速率处理级别、安全处理级别、可靠处理级别等。需要指出的是，APP在终端设备中的数据处理级别是APP开发方与终端设备方协商确定的。
终端中的SDK或中间件可以根据URSP规则确定应用程序对应的网络切片，支持相应网络切片的PDU会话，以及根据网络切片指示信息确定应用程序在终端设备中的数据处理级别。示例性的，网络切片指示信息可以为网络切片标识，用于描述网络切片的信息，例如S-NSSAI。
关于网络切片指示信息，本申请实施例提供了几种可能的实现方式。
(1)在第一种可能的实现方式中，网络切片指示信息为新定义的网络切片标识，新定义的网络切片用于标识网络切片类型。其中，相对于已有的网络切片标识(如S-NSSAI)，新定义的网络切片标识不仅可以用于指示应用程序对应的网络切片，以使终端设备可以将应用程序关联到支持该网络切片的PDU会话上，还可以用于指示应用程序对应的数据处理级别，以便更好地满足应用程序的业务需求。
示例性的，新定义的网络切片标识的数据结构，在已有网络切片标识的数据结构基础上，增加第一指示信息。示例性的，第一指示信息可以是内部切片(Internal Slice，IS)参数。可选的，在新定义的网络切片标识中，第一指示信息可以设置于网络切片标识S-NSSAI的SD部分，如图3中(a)所示，第一指示信息也可以设置于网络切片标识S-NSSAI的SST部分，如图3中(b)所示。
其中，第一指示信息用于指示应用程序在终端设备中的数据处理级别。例如，第一指示信息可以是终端设备商新定义的切片参数(如类型、名称等，不同于已有的网络切片类型或名称)。本实施例不对第一指示信息的形式进行限定。
第一指示信息可以包括一个或多个比特。当第一指示信息取值不同时，对应的应用程序在终端设备中的数据处理级别不同。
在一种示例中，应用程序在终端设备中的数据处理级别可以为优先处理级别，例如高优先级、中优先级、低优先级等优先级别。当优先处理级别不同时，应用程序所对应的网络传输通道不同或不完全相同。
在一种示例中，应用程序在终端设备中的数据处理级别可以为时延处理级别，例如1ms、10ms、100ms等时延级别，或者低时延、中时延、高时延等时延级别。当时延处理级别不同时，应用程序所对应的网络传输通道不同或不完全相同。
在一种示例中，应用程序在终端设备中的数据处理级别可以为速率处理级别，例如1Mbps、10Mbps、100Mbps、1000Mbps等速率级别，或者低速率、中速率、高速率等速率级别。当速率处理级别不同时，应用程序所对应的网络传输通道不同或不完全相同。
在一种示例中，应用程序在终端设备中的数据处理级别可以为安全处理级别，例如普通、TEE(Trusted Execution Environment)、SE(Secure Element)等安全级别，或者低、中、高等安全级别。当安全处理级别不同时，应用程序所对应的网络传输通道不同或不完全相同。
在一种示例中，应用程序在终端设备中的数据处理级别可以为可靠处理级别，例如99％、99.9％、99.99％、99.999％等可靠级别，或者低、中、高等可靠级别。当可靠处理级别不同时，应用程序所对应的网络传输通道不同或不完全相同。其中，可靠处理级别为“x％”时，表示终端设备在连续运行1年时间时业务中断可能的最长时间为(1- x％)*365*24。可以理解的是，终端设备业务中断可能的最长时间越短，可靠处理级别越高。例如，可靠级别“99.9％”表示终端设备在连续运行1年时间时业务中断可能的最长时间为：(1-99.9％)*365*24＝8.76小时，可靠级别“99.99％”表示终端设备在连续运行1年时间时业务中断可能的最长时间为：(1-99.99％)*365*24＝0.876小时＝52.6分钟。
表2示例性的示出了一种网络切片标识、第一指示信息和应用程序在终端设备中对应的数据处理级别的映射关系。
表2
如表2所示，以第一指示信息包括2个bit为例，“00”、“01”、“10”、“11”分别标识不同的数据处理级别。其中，当S-NSSAI 1中携带的第一指示信息为“00”时，表示应用程序在终端设备中对应的数据处理级别为第一优先处理级别，同时终端设备将应用程序关联到支持S-NSSAI 1的PDU会话；当S-NSSAI 2中携带的第一指示信息为“01”时，表示应用程序在终端设备中对应的数据处理级别为第二优先处理级别，同时终端设备将应用程序关联到支持S-NSSAI 2的PDU会话；当S-NSSAI 3中携带的第一指示信息为“10”，表示应用程序在终端设备中对应的数据处理级别为第一时延处理级别，同时终端设备将应用程序关联到支持S-NSSAI 3的PDU会话；当S-NSSAI 4中携带的第一指示信息为“11”，表示应用程序在终端设备中对应的数据处理级别为第二时延处理级别，同时终端设备将应用程序关联到支持S-NSSAI 4的PDU会话。
其中，第一优先处理级别与第二优先处理级别不同，第一优先处理级别可以高于第二优先处理级别。例如，终端设备可以针对通话应用进行第一优先处理级别的处理，针对游戏应用可以进行第一优先处理级别的处理，当通话应用和游戏应用同时运行时，可以优先处理通话应用的数据流。第一时延处理级别与第二时延处理级别不同，第一时延处理级别可以高于第二时延处理级别，即第一时延处理级别对应的处理时延小于第二时延处理级别对应的处理时延。
(2)在第二种可能的实现方式中，网络切片指示信息为已有的网络切片标识，且在已有的网络切片标识中增加第二指示信息。示例性的，第二指示信息可以在网络切片标识的SST部分、SD部分或NSSAI信息单元标识(Information Element Identifier，IEI)中增加。
其中，第二指示信息可以包括一个或多个比特，用于指示应用程序在终端设备中的数据处理级别，该数据处理级别与网络切片类型(或网络切片优先级)是对应的。例如，网络切片类型为低时延时，相应的数据处理级别为低时延处理级别；网络切片类型为高速率时，相应的数据处理级别为高速率处理级别，等等。
表3示例性的示出了一种网络切片标识、网络切片类型、第二指示信息和应用程序在终端设备中对应的数据处理级别的映射关系。
表3
示例性的，如表3所示，网络切片S-NSSAI 1的类型为低时延网络切片，网络切片S-NSSAI 1的标识中增加第二指示信息“1”，第二指示信息“1”可以指示应用程序在终端设备中对应的数据处理级别为低时延处理级别。其中，低时延处理级别可以是指终端设备内部对业务数据优先处理，比如优先调度，优先排队，插队提前发送，优先发送等。
这样，当应用程序业务对应的网络切片是低时延网络切片时，终端设备内部对该业务的数据处理级别是低时延处理级别，可以满足该业务的低时延需求，能避免网络切片时延低而终端设备内部处理时延高导致的业务体验不佳的问题，可以充分发挥低时延网络切片的优势，满足业务需求。
示例性的，如表3所示，网络切片S-NSSAI 2的类型为高速率网络切片，网络切片S-NSSAI 2的标识中增加第二指示信息“1”后，第二指示信息“1”可以指示应用程序在终端设备中对应的数据处理级别为高速率处理级别。其中，高速率处理级别可以是指终端设备内部调配较多的处理资源对业务数据进行处理，处理资源例如可以是内存(memory)资源、计算资源(如CPU(central processing unit，中央处理器)、GPU(graphics processing unit，图形处理器)、NPU(Neural-network Processing Unit，网络处理器)等)等。
这样，当应用程序业务对应的网络切片是高速率网络切片时，终端设备内部对该业务的处理级别是高速率处理级别，可以保证该业务的高速率需求，能够避免网络切片速率高而终端设备内部处理时速率低导致的业务体验不佳的问题，可以充分发挥高速率网络切片的优势，满足业务需求。
示例性的，如表3所示，网络切片S-NSSAI 3的类型为高安全网络切片，网络切片S-NSSAI 3的标识中增加第二指示信息“1”后，第二指示信息“1”可以指示应用程序在终端设备中对应的数据处理级别为高安全处理级别。其中，高安全处理级别可以是指终端设备将业务数据放在高安全区(如TEE、SE等)中处理，和/或终端设备对业务数据采用高加密的方式，以保证业务数据的安全。
这样，当应用程序业务对应的网络切片是高安全网络切片时，终端设备内部对该业务的处理级别是高安全处理级别，可以保证该业务的高安全需求，能够避免网络切片安全性高而终端设备内部处理时安全性低导致的业务体验不佳的问题，可以充分发挥高安 全网络切片的优势，满足业务需求。
示例性的，如表3所示，网络切片S-NSSAI 4的类型为高可靠网络切片，网络切片S-NSSAI 4的标识中增加第二指示信息“1”后，第二指示信息“1”可以指示应用程序在终端设备中对应的数据处理级别为高可靠处理级别。其中，高可靠处理级别可以是指终端设备将业务数据进行多次备份和/或多次传输，以保障业务数据的可靠性。
这样，当应用程序业务对应的网络切片是高可靠网络切片时，终端设备内部对该业务的处理级别是高可靠处理级别，可以保证该业务的高可靠需求，能够避免网络切片可靠性高而终端设备内部处理时可靠性低导致的业务体验不佳的问题，可以充分发挥高可靠网络切片的优势，满足业务需求。
示例性的，如表3所示，网络切片S-NSSAI 5的类型为大带宽网络切片，网络切片S-NSSAI 5的标识中增加第二指示信息“1”后，第二指示信息“1”可以指示应用程序在终端设备中对应的数据处理级别为大带宽处理级别。其中，大带宽处理级别例如可以是终端设备采用较大带宽(例如，80M/120M)的频段传输业务数据，或者可以是终端设备同时使用多个频段传输数据。
这样，当应用程序业务对应的网络切片是大带宽网络切片时，终端设备内部对该业务的处理级别是大带宽处理级别，可以保证该业务的大带宽需求，能够避免网络切片带宽大而终端设备内部处理时带宽小导致的业务体验不佳的问题，可以充分发挥大带宽网络切片的优势，满足业务需求。
(3)在第三种可能的实现方式中，已有的网络切片标识指示应用程序在终端设备中的数据处理级别，该数据处理级别与网络切片类型(或网络切片优先级)是对应的。在此实现方式中，不在已有的网络切片标识中增加指示信息，而是基于网络切片的类型隐式地指示应用程序在终端设备中的数据处理级别。
表4示例性的示出了一种网络切片标识、网络切片类型和应用程序在终端设备中对应的数据处理级别的映射关系。
表4
示例性的，如表4所示，网络切片S-NSSAI 1的类型为低时延网络切片，隐式地指示应用程序在终端设备中的数据处理级别为低时延处理级别；网络切片S-NSSAI 2的类型为高速率网络切片，隐式地指示应用程序在终端设备中的数据处理级别为高速率处理级别；网络切片S-NSSAI 3的类型为高安全网络切片，隐式地指示应用程序在终端设备中的数据处理级别为高安全处理级别；网络切片S-NSSAI 4的类型为高可靠网络切片，隐式地指示应用程序在终端设备中的数据处理级别为高可靠处理级别。
表5示例性的示出了一种网络切片标识、网络切片优先级和应用程序在终端设备中的处理优先级别的映射关系。
表5
假设网络切片优先级可以包括三个级别，分别为高、中、低。相应的，应用程序在终端设备中对应的处理优先级别也可以包括三个级别，分别为高、中、低。示例性的，如表5所示，网络切片S-NSSAI 1的优先级为“高”，网络切片S-NSSAI 1对应的应用程序在终端设备中的处理优先级别也为“高”；网络切片S-NSSAI 2的优先级为“中”，网络切片S-NSSAI 2对应的应用程序在终端设备中的处理优先级别也为“中”；网络切片S-NSSAI 3的优先级为“低”，网络切片S-NSSAI 3对应的应用程序在终端设备中的处理优先级别也为“低”。
网络切片S-NSSAI 1的优先级为“低”，网络切片S-NSSAI 1对应的应用程序在终端设备中的处理优先级别也为“低”。即，当应用程序对应的网络切片的优先级为“高”时，终端设备内部对该应用程序业务的优先处理级别也是“高”，从而保证该应用程序的业务需求(例如低时延、高可靠性等需求)。当应用程序对应的网络切片的优先级为“中”时，终端设备内部对该应用程序业务的优先处理级别也是“中”，尽量保证该应用程序的业务需求(例如低时延等需求)。当应用程序对应的网络切片的优先级为“低”时，终端设备内部对该应用程序业务的优先处理级别也是“低”，以合理满足该应用程序的业务需求。
表6示例性的示出了一种网络切片标识、网络切片优先级和应用程序在终端设备中的处理优先级别的映射关系。
表6
假设网络切片优先级可以包括两个级别，分别为高、低。相应的，应用程序在终端设备中对应的处理优先级别也可以包括两个级别，分别为高、低。示例性的，如表6所示，网络切片S-NSSAI 1的优先级为“高”，网络切片S-NSSAI 1对应的应用程序在终端设备中的处理优先级别也为“高”；网络切片S-NSSAI 2的优先级为“低”，网络切片S-NSSAI 2对应的应用程序在终端设备中的处理优先级别也为“低”。
可以理解的，网络切片优先级可以包括更多个级别，例如可以包括四个级别、五个级别、六个级别等，本申请实施例不做限定。相应的，应用程序在终端设备中对应的处理优先级别也可以包括四个级别、五个级别、六个级别等。
在上述表5和表6所示的映射关系中，是以网络切片优先级与应用程序在终端设备 中的处理优先级别一一对应的情形进行解释说明的。
在一种可能的情形中，网络切片优先级包括N个级别，应用程序在终端设备中对应的处理优先级别包括M个级别，N与M为正整数，且N与M不相等。在此情形下，一个网络切片优先级别可以对应于应用程序在终端设备中的多个处理优先级别，或者多个网络切片优先级别可以对应于应用程序在终端设备中的一个处理优先级别，本实施例对此不做限定。
表7示例性的示出了一种网络切片标识、网络切片优先级和应用程序在终端设备中的处理优先级别的映射关系。
表7
假设网络切片优先级可以包括三个级别，分别为高、中、低，应用程序在终端设备中对应的处理优先级别也可以包括两个级别，分别为高、低。示例性的，如表7所示，网络切片S-NSSAI 1的优先级为“高”，网络切片S-NSSAI 1对应的应用程序在终端设备中的处理优先级别也为“高”；网络切片S-NSSAI 2的优先级为“中”，网络切片S-NSSAI 2对应的应用程序在终端设备中的处理优先级别为“低”；网络切片S-NSSAI 3的优先级为“低”，网络切片S-NSSAI 3对应的应用程序在终端设备中的处理优先级别为“低”。也即，多个网络切片优先级别可以对应于应用程序在终端设备中的一个处理优先级别。
在一种实现方式中，网络切片优先级可以基于网络切片的类型确定。例如，uRLLC、eMBB、mMTC等类型网络切片的优先级依次从高到低排序。
结合前述示例，终端设备可以根据相应的网络切片选择规则，可以确定某个应用程序在终端设备中进行相应数据处理级别(如低时延处理级别、高速率处理级别等)的数据处理，该应用程序对应的网络切片，并且终端设备可以将该应用程序关联到支持该网络切片的PDU会话上，该网络切片可以使用网络切片选择规则中网络切片指示信息(如网络切片标识)进行标识。其中，应用程序在终端设备中进行相应数据处理级别的数据处理，是指该应用程序的数据流(traffic of application)在终端设备中进行相应数据处理级别的数据处理。
如图4所示为电子设备100的结构示意图。可选地，电子设备100可以称为终端，也可以称为终端设备，本申请不做限定。需要说明的是，电子设备100的结构示意图可以适用于上述提及的UE。应该理解的是，图4所示电子设备100仅是电子设备的一个范例，并且电子设备100可以具有比图中所示的更多的或者更少的部件，可以组合两个或多个的部件，或者可以具有不同的部件配置。图4中所示出的各种部件可以在包括一个或多个信号处理和/或专用集成电路在内的硬件、软件、或硬件和软件的组合中实 现。
电子设备100可以包括：处理器110，外部存储器接口120，内部存储器121，通用串行总线(universal serial bus，USB)接口130，充电管理模块140，电源管理模块141，电池142，天线1，天线2，移动通信模块150，无线通信模块160，音频模块170，扬声器170A，受话器170B，麦克风170C，耳机接口170D，传感器模块180，按键190，马达191，指示器192，摄像头193，显示屏194，以及SIM卡接口195等。其中传感器模块180可以包括压力传感器，陀螺仪传感器，加速度传感器，温度传感器，运动传感器，气压传感器，磁传感器，距离传感器，接近光传感器，指纹传感器，触摸传感器，环境光传感器，骨传导传感器等。
处理器110可以包括一个或多个处理单元，例如：处理器110可以包括应用处理器(application processor，AP)，调制解调处理器(Modem)，图形处理器(graphics processing unit，GPU)，图像信号处理器(image signal processor，ISP)，控制器，存储器，视频编解码器，数字信号处理器(digital signal processor，DSP)，基带处理器，和/或神经网络处理器(neural-network processing unit，NPU)等。其中，不同的处理单元可以是独立的器件，也可以集成在一个或多个处理器中。
其中，控制器可以是电子设备100的神经中枢和指挥中心。控制器可以根据指令操作码和时序信号，产生操作控制信号，完成取指令和执行指令的控制。
处理器110中还可以设置存储器，用于存储指令和数据。在一些实施例中，处理器110中的存储器为高速缓冲存储器。
USB接口130是符合USB标准规范的接口，具体可以是Mini USB接口，Micro USB接口，USB Type C接口等。USB接口130可以用于连接充电器为电子设备100充电，也可以用于电子设备100与外围设备之间传输数据。也可以用于连接耳机，通过耳机播放音频。
充电管理模块140用于从充电器接收充电输入。其中，充电器可以是无线充电器，也可以是有线充电器。充电管理模块140为电池142充电的同时，还可以通过电源管理模块141为电子设备供电。
电源管理模块141用于连接电池142，充电管理模块140与处理器110。电源管理模块141接收电池142和/或充电管理模块140的输入，为处理器110，内部存储器121，外部存储器，显示屏194，摄像头193，和无线通信模块160等供电。
电子设备100的无线通信功能可以通过天线1，天线2，移动通信模块150，无线通信模块160，调制解调处理器以及基带处理器等实现。
天线1和天线2用于发射和接收电磁波信号。电子设备100中的每个天线可用于覆盖单个或多个通信频带。不同的天线还可以复用，以提高天线的利用率。例如：可以将天线1复用为无线局域网的分集天线。在另外一些实施例中，天线可以和调谐开关结合使用。
移动通信模块150可以提供应用在电子设备100上的包括2G/3G/4G/5G等无线通信的解决方案。移动通信模块150可以包括至少一个滤波器，开关，功率放大器，低噪声放大器(low noise amplifier，LNA)等。移动通信模块150可以由天线1接收电磁波， 并对接收的电磁波进行滤波，放大等处理，传送至调制解调处理器进行解调。移动通信模块150还可以对经调制解调处理器调制后的信号放大，经天线1转为电磁波辐射出去。在一些实施例中，移动通信模块150的至少部分功能模块可以被设置于处理器110中。在一些实施例中，移动通信模块150的至少部分功能模块可以与处理器110的至少部分模块被设置在同一个器件中。
调制解调处理器(Modem)运行于基带芯片和协处理器上，该Modem中设置有SIM卡模块，通过Modem中的SIM卡模块可以用于提供网络注册、鉴权等与SIM信息相关的功能。示例性的，用户在使用具有Modem的电子设备时，可以通过触发本地应用，实现一系列SIM卡功能。上述所说的SIM卡可以为实体卡(或称为硬卡)，也可以为虚拟SIM卡(或称为软卡)，可以包括内置芯片式用户身份识别卡(embedded-SIM，eSIM)等，本申请实施例中对该SIM卡的具体形态不做限定。
调制解调处理器可以包括调制器和解调器。其中，调制器用于将待发送的低频基带信号调制成中高频信号。解调器用于将接收的电磁波信号解调为低频基带信号。随后解调器将解调得到的低频基带信号传送至基带处理器处理。低频基带信号经基带处理器处理后，被传递给应用处理器。应用处理器通过音频设备(不限于扬声器170A，受话器170B等)输出声音信号，或通过显示屏194显示图像或视频。在一些实施例中，调制解调处理器可以是独立的器件。在另一些实施例中，调制解调处理器可以独立于处理器110，与移动通信模块150或其他功能模块设置在同一个器件中。
无线通信模块160可以提供应用在电子设备100上的包括无线局域网(wireless local area networks，WLAN)(如无线保真(wireless fidelity，Wi-Fi)网络)，蓝牙(bluetooth，BT)，全球导航卫星系统(global navigation satellite system，GNSS)，调频(frequency modulation，FM)，近距离无线通信技术(near field communication，NFC)，红外技术(infrared，IR)等无线通信的解决方案。无线通信模块160可以是集成至少一个通信处理模块的一个或多个器件。无线通信模块160经由天线2接收电磁波，将电磁波信号调频以及滤波处理，将处理后的信号发送到处理器110。无线通信模块160还可以从处理器110接收待发送的信号，对其进行调频，放大，经天线2转为电磁波辐射出去。
在一些实施例中，电子设备100的天线1和移动通信模块150耦合，天线2和无线通信模块160耦合，使得电子设备100可以通过无线通信技术与网络以及其他设备通信。
电子设备100通过GPU，显示屏194，以及应用处理器等实现显示功能。处理器110可包括一个或多个GPU，其执行程序指令以生成或改变显示信息。显示屏194用于显示图像，视频等。电子设备100可以通过ISP，摄像头193，视频编解码器，GPU，显示屏194以及应用处理器等实现拍摄功能。摄像头193用于捕获静态图像或视频。
外部存储器接口120可以用于连接外部存储卡，例如Micro SD卡，实现扩展电子设备100的存储能力。
内部存储器121可以用于存储计算机可执行程序代码，所述可执行程序代码包括指令。处理器110通过运行存储在内部存储器121的指令，从而执行电子设备100的各种 功能应用以及数据处理，使得电子设备100实现本申请实施例中的通信方法。
电子设备100可以通过音频模块170，扬声器170A，受话器170B，麦克风170C，耳机接口170D，以及应用处理器等实现音频功能。例如音乐播放，录音等。
音频模块170用于将数字音频信息转换成模拟音频信号输出，也用于将模拟音频输入转换为数字音频信号。音频模块170还可以用于对音频信号编码和解码。在一些实施例中，音频模块170可以设置于处理器110中，或将音频模块170的部分功能模块设置于处理器110中。
压力传感器用于感受压力信号，可以将压力信号转换成电信号。在一些实施例中，压力传感器可以设置于显示屏194。电子设备100也可以根据压力传感器的检测信号计算触摸的位置。
触摸传感器，也称“触控面板”。触摸传感器可以设置于显示屏194，由触摸传感器与显示屏194组成触摸屏，也称“触控屏”。触摸传感器用于检测作用于其上或附近的触摸操作。触摸传感器可以将检测到的触摸操作传递给应用处理器，以确定触摸事件类型。
按键190包括开机键(或称电源键)，音量键等。按键190可以是机械按键。也可以是触摸式按键。电子设备100可以接收按键输入，产生与电子设备100的用户设置以及功能控制有关的键信号输入。
马达191可以产生振动提示。马达191可以用于来电振动提示，也可以用于触摸振动反馈。例如，作用于不同应用(例如拍照，音频播放等)的触摸操作，可以对应不同的振动反馈效果。
指示器192可以是指示灯，可以用于指示充电状态，电量变化，也可以用于指示消息，未接来电，通知等。
SIM卡接口195用于连接SIM卡。SIM卡可以通过插入SIM卡接口195，或从SIM卡接口195拔出，实现和电子设备100的接触和分离。电子设备100可以支持1个或N个SIM卡接口，N为大于1的正整数。SIM卡接口195可以支持Nano SIM卡，Micro SIM卡，SIM卡等。同一个SIM卡接口195可以同时插入多张卡。所述多张卡的类型可以相同，也可以不同。SIM卡接口195也可以兼容不同类型的SIM卡。SIM卡接口195也可以兼容外部存储卡。电子设备100通过SIM卡和网络交互，实现通话以及数据通信等功能。在一些实施例中，电子设备100采用eSIM，即：嵌入式SIM卡。eSIM卡可以嵌在电子设备100中，不能和电子设备100分离。
电子设备100的软件系统可以采用分层架构，事件驱动架构，微核架构，微服务架构，或云架构。本申请实施例以分层架构的Android系统为例，示例性说明电子设备100的软件结构。
图5是本申请实施例的电子设备100的软件结构框图。
电子设备100的分层架构将软件分成若干个层，每一层都有清晰的角色和分工。层与层之间通过软件接口通信。在一些实施例中，将Android系统分为四层，从上至下分别为应用程序层，应用程序框架层，无线接口层(Radio Layer Interface，RIL)，以及调 制解调处理器(Modem)层。
针对图4中的电子设备100，应用程序层与应用程序框架层之间可以通过常规的接口进行数据交互。应用程序框架层与RIL之间可以通过硬件抽象层接口定义语言(Hardware Abstraction Layer Interface Definition Language，HIDL)接口进行数据交互。RIL与Modem层之间可以基于电子设备的芯片架构进行数据交互。例如，RIL与Modem层通过PCIExpress(peripheral component interconnect express，PCIE)或者内存共享等方式进行数据交互。
应用程序层可以包括一系列应用程序包。
如图5所示，应用程序包可以包括通话，相机，图库，视频，地图，导航，蓝牙，网络切片选择SDK等应用程序。
其中，网络切片选择SDK可以基于URSP规则确定与APP对应的网络切片，以及确定APP在电子设备中对应的数据处理级别。
应用程序框架层为应用程序层的应用程序提供应用编程接口(application programming interface，API)和编程框架。应用程序框架层包括一些预先定义的函数。
如图5所示，应用程序框架层可以包括电话管理器(Telephony)、连接服务(Connectivity Service)等。
其中，电话管理器用于提供对电子设备100蜂窝相关业务的管理功能。例如，电话管理器用于提供通话状态(包括接通，以及挂断等)和蜂窝数据连接状态(包括与蜂窝网络已建立连接、与蜂窝网络已断开连接、正在与蜂窝网络建立连接、正在与蜂窝网络断开连接等)的管理。可以理解，蜂窝网络可以包括2G网络、3G网络、4G网络和5G网络(例如SA网络)等。
在可能的实现方式中，应用程序框架层中还可以包括窗口管理器，内容提供器，视图系统，资源管理器，通知管理器等(图5未示出)，本申请实施例对此不做限定。
其中，窗口管理器用于管理窗口程序。窗口管理器可以获取显示屏大小，判断是否有状态栏，锁定屏幕，截取屏幕等。
内容提供器用来存放和获取数据，并使这些数据可以被应用程序访问。所述数据可以包括视频，图像，音频，拨打和接听的电话，浏览历史和书签，电话簿等。
视图系统包括可视控件，例如显示文字的控件，显示图片的控件等。视图系统可用于构建应用程序。显示界面可以由一个或多个视图组成的。例如，包括短信通知图标的显示界面，可以包括显示文字的视图以及显示图片的视图。
资源管理器为应用程序提供各种资源，比如本地化字符串，图标，图片，布局文件，视频文件等等。
通知管理器使应用程序可以在状态栏中显示通知信息，可以用于传达告知类型的消息，可以短暂停留后自动消失，无需用户交互。比如通知信息被用于告知下载完成，消息提醒等。
其中，相对于Modem侧，应用程序层和应用程序框架层可以称之为AP侧。在本申请实施例中，基于URSP规则确定与APP对应的网络切片，以及确定APP在电子设备中对应的数据处理级别是在AP侧实现的，具体可以是在AP侧的网络切片选择SDK 中实现的。
RIL是应用程序框架层和Modem层之间的接口层，负责蜂窝相关业务控制面操作的传输，负责数据的可靠传输。RIL中可以包括无线接口层守护进程(Radio Interface Layer Daemon，rild)，rild中可以包括：ril服务模块。例如，ril服务模块可以用于将电话管理器经由HIDL接口发送的指令转发至Modem层，以及将Modem层返回的指令对应的响应数据，和Modem层主动上报的状态或通知，转发至电话管理器。
Modem层中包括调制解调处理器(Modem)，Modem中可以包括：协议栈和卡处理模块。协议栈可以包括2G协议栈、3G协议栈、4G协议栈和5G协议栈等无线通信协议栈。
卡处理模块可以包括SIM卡的相关模块。例如，SIM卡模块、本地SIM卡模块、以及SIM卡槽驱动等。其中，该SIM卡槽驱动可以连接有SIM硬卡。
SIM卡模块：用于提供网络注册、鉴权等与SIM信息相关的功能。该SIM卡模块可以支持本地SIM卡模块提供的本地SIM卡调用模式。
本地SIM卡模块：用于使用SIM卡槽驱动实现对于本地SIM卡信息的访问。
在可能的实现方式中，电子设备100的Modem中可以设置有SIM卡槽驱动以及SIM硬卡；或者，电子设备100的Modem中也可以不设置SIM卡槽驱动以及SIM硬卡，此时电子设备100可以使用本地的eSIM。
上述Android系统架构示意图仅做举例说明，不构成任何限制。
可以理解的是，图5示出的软件结构中的层以及各层中包含的部件，并不构成对电子设备100的具体限定。在本申请另一些实施例中，电子设备100可以包括比图示更多或更少的层，以及每个层中可以包括更多或更少的部件，本申请不做限定。
可以理解的是，电子设备为了实现本申请实施例中的通信方法，其包含了执行各个功能相应的硬件和/或软件模块。结合本文中所公开的实施例描述的各示例的算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。本领域技术人员可以结合实施例对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
如图6所示，本申请实施例提供了一种通信方法，具体可以包括如下步骤：
S101，APP向网络切片选择SDK发送建立网络连接服务的激活请求。
其中，该激活请求中可以包括APP的TD(Traffic Descriptor，通路描述符)参数。示例性的，APP的TD参数可以包括但不限于APP标识(APP ID)、数据网络名称(DNN)、IP三元组(IP Descriptor)、域名描述符(Domain Descriptor)、连接能力(Connetion Capabilities)等参数。
S102，基于URSP规则，网络切片选择SDK根据TD参数确定与APP对应的目标网络切片，并将目标网络切片的标识发送给OS模块。
在URSP规则中，如图7所示，主要包括两组重要的参数，一组是描述APP属性的TD参数，一组是描述数据承载属性的RSD参数，可以包括但不限于S-NSSAI、SSC  Mode(会话与服务连续性模式)、DNN等参数。URSP规则实质上就是多组TD参数和多组RSD参数的对应关系。
在网络切片选择SDK获取到APP的TD参数之后，可以基于URSP规则找到与其相对应的RSD参数。由于在RSD参数中包含着网络切片的标识S-NSSAI，也就确定了APP可以接入的目标网络切片了。
示例性的，在网络切片选择SDK获取到APP的TD参数之后，可以基于URSP规则以及网络切片的优先级匹配与APP对应的网络切片。例如，网络切片选择SDK首先基于URSP规则在第一优先级的网络切片中匹配的与APP对应的网络切片，若匹配不到再基于URSP规则在第二优先级的网络切片中匹配的与APP对应的网络切片。其中，第一优先级高于第二优先级。
进而，网络切片选择SDK可以将与APP对应的目标网络切片的标识，通过OS模块提供的API(Application Program Interface，应用程序接口)发送至OS模块。
S103，OS模块将目标网络切片的标识发送给Modem模块。
OS模块将接收到的与APP对应的目标网络切片的标识，通过Modem模块提供的API发送给Modem模块。
S104，Modem模块与网络设备进行交互，将APP关联到支持目标网络切片的PDU会话上，并将关联成功的指示信息反馈给网络切片选择SDK。
在一种可能的实现方式中，网络切片选择SDK也可以直接将与APP对应的目标网络切片的标识，通过Modem模块提供的API发送给Modem模块。
Modem模块接收到的与APP对应的目标网络切片的标识，即为UE希望注册的网络切片的标识，也即请求的网络切片的标识。Modem模块基于目标网络切片的标识生成注册请求消息，即注册请求消息中包括目标网络切片的标识(NSSAI)，将注册请求消息发送至网络侧设备(如gNB)。
需要指出的是，注册请求消息中包括的目标网络切片的标识可以为上述第一种可能的实现方式、第二种可能的实现方式、第三种可能的实现方式中提及的网络切片标识。若目标网络切片的标识为上述第一种可能的实现方式新定义的网络切片标识，则在该目标网络切片的标识中携带第一指示信息，第一指示信息用于指示应用程序在终端设备中的数据处理级别。若目标网络切片的标识为上述第二种可能的实现方式提及添加有第二指示信息的网络切片标识，则在该目标网络切片的标识中携带第二指示信息，第二指示信息用于指示应用程序在终端设备中的数据处理级别。若目标网络切片的标识为上述第三种可能的实现方式提及的已有技术中的网络切片标识，则在该目标网络切片可以隐式地指示应用程序在终端设备中的数据处理级别。
gNB接收到来自UE的注册请求消息后，可以向AMF转发该注册请求消息。如果UE处于CM连接(CM-CONNECTED)态，gNB可以基于UE的N2连接向AMF转发注册请求消息。如果UE处于CM空闲(CM-IDLE)态，UE在与RAN建立连接时未包含“请求的NSSAI”和全局唯一的AMF标识符(globally uniq AMF identifier，GUAMI)，则gNB可以将注册请求消息转发到默认AMF。
AMF可以基于“签约的S-NSSAIs”验证“请求的NSSAI”中的S-NSSAI是否被允 许。其中，“签约的S-NSSAIs”可以是AMF从统一数据管理UDM网元获取的。AMF可以确定一个注册区域，以便该注册区域的“允许的NSSAI”的所有S-NSSAI在注册区域的所有跟踪区域中都可用，然后返回给终端设备该“允许的NSSAI”。可选的，AMF向终端设备返回“允许的NSSAI”到“签约的S-NSSAIs”的映射。可选的，AMF可以返回一个或多个“拒绝的S-NSSAI”以及其每个S-NSSAI的拒绝原因。如果S-NSSAI被拒绝原因值指示网络切片特定的身份验证和授权失败或撤销，则UE可以基于本地策略重新尝试请求该S-NSSAI。
AMF向gNB发送注册接受(registration accept)消息，注册接受消息表示注册请求已被AMF接受。gNB从AMF接收到注册接受消息后，可以将注册接受消息转发给UE。
通过Modem模块与网络设备的交互，可以完成网络切片的选择流程，可以参照前文描述的切片选择流程的步骤，有关流程未尽详细解释之处，可以参照已有技术，在此不再赘述。
这样，即可将APP与目标网络切片绑定，并将APP关联到支持目标网络切片的PDU会话上。Modem模块还可以将关联成功的指示信息反馈给网络切片选择SDK。
如果已经存在一个PDU会话支持APP希望使用的目标网络切片，终端设备将应用程序关联到这个支持目标网络切片的PDU会话上，即终端设备将应用程序的数据流路由到该PDU会话上。如果不存在一个PDU session支持APP希望使用的目标网络切片，终端设备发起支持目标网络切片的PDU会话的建立流程，以便将应用程序关联到建立的PDU会话上。其中，PDU会话的建立流程可以包括如下步骤：
步骤1.终端设备的Modem向AMF发送PDU会话建立请求。
终端设备可以通过非接入层(Non-access stratum，NAS)消息向AMF发送PDU会话建立请求(PDU session establishment request)。
其中，PDU会话建立请求中可以包括PDU会话ID(PDU session ID)，PDU会话类型(PDU Session type)，SSC Mode，DNN，S-NSSAI(业务对应的S-NSSAI)等参数。其中，PDU会话建立请求中的S-NSSAI可以是上文所述的三种指示方式之一的网络切片标识。
其中，PDU会话请求消息中携带的S-NSSAI经无线网被转发到AMF。AMF对PDU会话请求消息中的S-NSSAI进行检查，并根据网络中各个SMF所支持的切片能力情况，选择相应的SMF，并将该会话建立请求转发给SMF。
步骤2.AMF向SMF发送PDU会话创建请求(PDU session create request)。
AMF可以通过HTTP2POST向SMF发送PDU会话创建请求。PDU会话创建请求中可以包含SUPI，DNN，PDU Session ID，S-NSSAI，Request Type等参数。
SMF可以进行PDU会话的上下文的建立。SMF可以向UDM获取用户响应的签约信息，然后向UPF和RAN、终端设备下发策略控制消息，由UPF和RAN、终端设备建立PDU会话的连接。
步骤3.SMF向AMF发送会话创建响应(PDU session create response)。
SMF确定PDU会话连接建立完成后，可以向AMF发送会话创建响应，指示PDU 会话建立成功。
步骤4.AMF向终端设备发送PDU会话建立接受(PDU session establishment accept)。
AMF向终端设备回复会话建立请求响应，指示PDU会话建立成功。终端设备将应用程序关联到新建立的PDU session，即终端设备将应用程序的数据流路由(route)在所述新建立的PDU session上。
另外，如果终端设备发送的PDU Session Establishment Request被网络侧拒绝，即PDU会话建立失败，则终端设备重新匹配其他URSP规则，并发起基于重新匹配的URSP规则发起PDU session的建立。
上述以网络切片选择SDK基于URSP规则确定与APP对应的一个目标网络切片为例进行解释说明的，若网络切片选择SDK基于URSP规则确定与APP对应的多个目标网络切片亦是如此，也可能存在一个或多个网络切片被拒绝注册的现象。可以理解的，APP最终会与其中一个目标网络切片绑定，APP关联到支持目标网络切片的PDU会话上。
S105，网络切片选择SDK根据目标网络切片确定APP的业务数据在UE中的数据处理级别。
基于本申请实施例提供的一种新的网络切片选择规则(或称新的URSP规则)，网络切片选择SDK还可以根据目标网络切片确定APP的业务数据在UE中的数据处理级别。
在上述提及第一种可能的实现方式，网络切片选择SDK可以通过在新定义的网络切片标识中新增的第一指示信息显示地指示应用程序在终端设备中的数据处理级别；在上述提及的第二种可能的实现方式中，网络切片选择SDK可以通过在已有的网络切片标识中新增的第二指示信息以及网络切片的类型显示的指示应用程序在终端设备中的数据处理级别；在上述提及的第三种可能的实现方式中，网络切片选择SDK通过已有的网络切片标识隐式地指示应用程序在终端设备中的数据处理级别。
基于这三种实现方式，网络切片选择SDK如何根据目标网络切片确定APP的业务数据在UE中的数据处理级别，以及数据处理级别的详细解释，可以参照前文，在此不再赘述。
S106，UE按照数据处理级别处理APP的业务数据。
在确定了APP的业务数据在UE中的数据处理级别之后，UE即可按照相应的数据处理级别处理APP的业务数据。
这样，APP的业务数据在UE内部的数据处理级别是匹配的，能够保证业务数据的相应需求(如低延时、高速率、高优先级等)，避免网络切片性能与终端内部数据处理情形不匹配而导致业务体验不佳的问题。
在一种具体的实施方式中，如图8所示，S-NSSAI的TD参数中包含新定义的IS参数，本实施例提供的一种新的网络切片选择规则设置于URSP规则的RSD中。其中，IS参数对应于一个或多个取值，不同的IS参数值对应于不同的网络切片。此时，网络切 片选择SDK可以根据IS参数匹配与APP对应的目标网络切片。例如，IS 1对应于网络切片NSSAI 1，IS 2对应于网络切片NSSAI 2。
可选的，在上述提及的第一种可能的实现方式中，新定义的网络切片标识中第一指示信息为IS参数。若第一APP发送给网络切片选择SDK的IS参数值，与第一网络切片标识中第一指示信息(即IS参数)值相同，则第一APP对应的网络切片为第一网络切片。而且，IS参数还可以用于确定应用程序在终端设备中的数据处理级别。此时，网络切片选择SDK可以根据IS参数确定APP在终端设备中的数据处理等级。其中，不同的IS参数值对应于不同的数据处理级别。例如，IS 1对应于低时延处理等级，IS 2对应于高时延处理等级。
其中，目标APP的IS参数值可以是APP的开发方与终端设备的生产方协商确定的，例如可以是APP的开发方在终端设备的生产方购买的。这样，目标APP的开发方可以同终端设备的生产方协商确定满足其业务需求的数据处理级别。
参照图9，在此实施方式中，如图6所示的通信方法涉及的步骤可以调整为：
S201，APP向网络切片选择SDK发送建立网络连接服务的激活请求。
其中，该激活请求中可以包括APP的TD(Traffic Descriptor，通路描述符)参数，TD参数中包括IS参数。
S202，网络切片选择SDK根据IS参数确定与APP对应的目标网络切片，并将目标网络切片的标识发送给OS模块。
其中，目标网络切片的标识中包括IS参数。
S203，OS模块将目标网络切片的标识发送给Modem模块。
S204，Modem模块与网络设备进行交互，将APP关联到支持目标网络切片的PDU会话上，并将关联成功的指示信息反馈给网络切片选择SDK。
S205，网络切片选择SDK根据目标网络切片标识中的IS参数确定APP的业务数据在UE中的数据处理级别。
S206，UE按照数据处理级别处理APP的业务数据。
本流程未尽详细解释之处，可以参照前文，在此不再赘述。
在另一种具体的实施方式中，在URSP规则的RSD参数中增加新定义的IS参数。其中，IS参数对应于一个或多个取值，不同的IS参数值对应于不同的数据处理级别。此时，网络切片选择SDK可以根据IS参数确定APP在终端设备中的数据处理等级。例如，IS 1对应于低时延处理等级，IS 2对应于高时延处理等级。
为了防止网络切片被其他APP滥用，本申请实施例还在网络切片选择SDK侧增加了安全验证机制。
如图10所示，本申请实施例提供了一种通信方法，具体可以包括如下步骤：
S301，APP向网络切片选择SDK发送建立网络连接服务的激活请求。
其中，该激活请求中包括APP的TD参数以及TD参数签名。
示例性的，TD参数签名是对TD参数的哈希值进行加密而生成的。
在一种实现方式中，TD参数可以包括前述的IS参数，后续处理流程参照前文，在 此不再赘述。
S302，网络切片选择SDK根据TD参数以及TD参数签名，对APP进行安全验证。
网格切片选择SDK对TD参数签名进行解密，得到TD参数的哈希值，通过对比解密得到的TD参数哈希值以及解析激活请求得到的TD参数的哈希值，对APP进行安全验证。如果解密得到的TD参数的哈希值与解析激活请求得到的TD参数的哈希值一致，则APP安全验证成功，否则APP安全验证失败。
其中，TD参数签名是基于签名私钥加密而生成的，网格切片选择SDK根据与该签名私钥成对的签名公钥对TD参数签名进行解密。
在一种实现方式中，APP的TD参数签名是UE对应的终端服务器基于签名私钥对APP的TD参数的哈希值加密而生成的。同时，终端服务器将与签名私钥成对的签名公钥发送给UE(如发送至UE的网络切片选择SDK)，网络切片选择SDK将该签名公钥本地存储。
在一种示例中，网格切片选择SDK在激活请求中解析到TD参数以及TD参数签名，基于本地存储的签名公钥对TD参数签名进行解密，并将解密得到的TD参数哈希值作为安全验证信息。网格切片选择SDK根据安全验证信息(即解密得到的TD参数哈希值)，对解析得到的TD参数进行验证，判断二者哈希值是否一致，若是则确定APP安全验证成功，否则确定APP安全验证失败。
在一种示例中，网格切片选择SDK在激活请求中解析到TD参数以及TD参数签名，基于本地存储的签名公钥对TD参数签名进行解密，并将解密得到的TD参数的哈希值作为安全验证信息。网格切片选择SDK将安全验证信息(即解密得到的TD参数的哈希值)，发送至对应的终端服务器，以通过终端服务对APP进行安全验证。终端服务器根据接收到的安全验证信息对APP进行安全验证，判断该安全验证信息是否与相应APP的TD参数的哈希值一致，若是则向UE的网格切片选择SDK反馈安全验证成功的指示信息，否则向UE的网格切片选择SDK反馈安全验证失败的指示信息。
S303，如果APP安全验证成功，则基于URSP规则，网络切片选择SDK根据TD参数确定与APP对应的目标网络切片，并将目标网络切片的标识发送给OS模块。
S304，OS模块将目标网络切片的标识发送给Modem模块。
S305，Modem模块与网络设备进行交互，将APP关联到支持目标网络切片的PDU会话上，并将关联成功的指示信息反馈给网络切片选择SDK。
S306，网络切片选择SDK根据目标网络切片确定APP的业务数据在UE中的数据处理级别。
S307，UE按照数据处理级别处理APP的业务数据。
这样，UE不仅能够保证业务数据的相应需求(如低延时、高速率、高优先级等)，避免网络切片性能与终端内部数据处理情形不匹配而导致业务体验不佳的问题，还能对在将APP与网络切片关联前对APP进行安全验证，避免网络切片被滥用的问题。
在上述技术方案的基础上，网络切片选择SDK还可以更新配置在终端侧的URSP规则(包括网络切片选择规则)，以通过更新后的URSP规则确定与APP对应的网络切 片，以及确定APP在终端设备中的数据处理级别。
在一种实现方式中，当URSP规则配置在网络侧时，更新的URSP规则可以通过网络设备下发至终端侧。示例性的，H-PCF可以通过AMF和gNB将更新的网络切片选择规则配置给终端设备。例如，更新的URSP规则可以通过注册命令消息配置给终端设备。又示例性的，通信运营商可以向终端设备配置更新的URSP规则。其中，更新的URSP规则是由UE的Modem模块接收的，并通过Modem模块发送至网络切片选择SDK。
在一种实现方式中，当URSP规则配置在终端侧时，URSP规则可以基于终端平台或终端的SDK平台进行更新。
本申请实施例采用终端中心化方案，相对于操作系统中心化方案以及Modem中心化方案，更新URSP规则所需的周期更短，URSP规则更限于维护管理。
本实施例还提供一种计算机存储介质，该计算机存储介质中存储有计算机指令，当该计算机指令在电子设备上运行时，使得电子设备执行上述相关方法步骤实现上述实施例中的通信方法。
本实施例还提供了一种计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行上述相关步骤，以实现上述实施例中的通信方法。
另外，本申请的实施例还提供一种装置，这个装置具体可以是芯片，组件或模块，该装置可包括相连的处理器和存储器；其中，存储器用于存储计算机执行指令，当装置运行时，处理器可执行存储器存储的计算机执行指令，以使芯片执行上述各方法实施例中的通信方法。
其中，本实施例提供的电子设备(如手机等)、计算机存储介质、计算机程序产品或芯片均用于执行上文所提供的对应的方法，因此，其所能达到的有益效果可参考上文所提供的对应的方法中的有益效果，此处不再赘述。
通过以上实施方式的描述，所属领域的技术人员可以了解到，为描述的方便和简洁，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个装置，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
以上所述，以上实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的范围。

Claims (16)

  1. 一种通信方法，其特征在于，应用于终端设备中，所述终端设备包括SDK模块、OS模块和Modem模块，所述方法包括：
    SDK模块获取目标APP发送的建立网络连接服务的激活请求；其中，所述激活请求中包括通路描述符TD参数；
    基于UE路由选择策略URSP规则，所述SDK模块根据所述TD参数确定所述目标APP对应的目标网络切片，并将所述目标网络切片的标识发送给所述OS模块；
    所述OS模块将所述目标网络切片的标识发送至所述Modem模块；
    所述Modem模块根据所述目标网络切片的标识与网络设备进行交互，将所述目标APP关联到支持所述目标网络切片的PDU会话上；
    其中，所述目标APP的业务数据按照与所述目标网络切片匹配的数据处理等级在所述终端设备中进行处理。
  2. 根据权利要求1所述的方法，其特征在于，所述激活请求中还包括TD参数签名；
    所述SDK模块根据所述TD参数确定所述目标APP对应的目标网络切片，包括：
    所述SDK模块在根据所述TD参数签名确定所述目标APP安全验证成功时，根据所述TD参数确定所述目标APP对应的目标网络切片。
  3. 根据权利要求2所述的方法，其特征在于，所述SDK模块在根据所述TD参数签名确定所述目标APP安全验证成功，包括：
    所述SDK模块根据签名公钥对所述TD参数签名进行解密，得到第一哈希值；所述TD参数签名是基于与所述签名公钥成对的签名私钥而生成的；
    所述SDK模块如果确定所述第一哈希值和第二哈希值一致，则确定所述目标APP安全验证成功；其中，所述第二哈希值是对所述目标APP的TD参数进行哈希计算得到的。
  4. 根据权利要求1所述的方法，其特征在于，还包括：
    所述Modem模块接收更新后的URSP规则，并将所述更新后的URSP规则发送至所述SDK模块，以使所述SDK模块对本地URSP规则进行更新。
  5. 根据权利要求1-4任一项所述的方法，其特征在于，还包括：
    所述SDK模块根据所述目标网络切片的第一标识，确定所述目标APP的业务数据在所述终端设备中的数据处理等级；或者，
    所述SDK模块根据所述目标网络切片的第二标识以及所述目标网络切片的类型，确定所述目标APP的业务数据在所述终端设备中的数据处理等级；或者，
    所述SDK模块根据所述目标网络切片的类型或所述目标网络切片的优先级，确定 所述目标APP的业务数据在所述终端设备中的数据处理等级。
  6. 根据权利要求5所述的方法，其特征在于，所述SDK模块根据所述目标网络切片的第一标识，确定所述目标APP的业务数据在所述终端设备中的数据处理等级，包括：
    所述SDK模块根据所述目标网络切片的第一标识中的第一指示信息，确定所述目标APP的业务数据在所述终端设备中的数据处理等级；其中，所述第一标识为网络切片的自定义标识，所述第一指示信息用于指示APP在终端设备中的数据处理级别。
  7. 根据权利要求6所述的方法，其特征在于，所述SDK模块发送给所述OS模块的所述目标网络切片的标识，以及所述OS模块发送给所述Modem模块的所述目标网络切片的标识，为所述目标网络切片的第一标识。
  8. 根据权利要求5所述的方法，其特征在于，所述SDK模块根据所述目标网络切片的第二标识以及所述目标网络切片的类型，确定所述目标APP的业务数据在所述终端设备中的数据处理等级，包括：
    所述SDK模块根据所述目标网络切片的第二标识中的第二指示信息，以及所述目标网络切片的类型，确定所述目标APP的业务数据在所述终端设备中的数据处理等级；其中，所述第二标识为通信协议中规定的网络切片标识，所述第二指示信息为所述网络切片标识中新增的指示信息，用于指示APP在终端设备中的数据处理级别。
  9. 根据权利要求8所述的方法，其特征在于，所述SDK模块发送给所述OS模块的所述目标网络切片的标识，以及所述OS模块发送给所述Modem模块的所述目标网络切片的标识，为所述目标网络切片的第二标识。
  10. 根据权利要求5所述的方法，其特征在于，所述数据处理级别涉及的方面包括下述至少一项：
    优先级、时延、速率、数据安全、数据可靠性。
  11. 根据权利要求6所述的方法，其特征在于，在所述SDK模块根据所述目标网络切片的第一标识，确定所述目标APP的业务数据在所述终端设备中的数据处理等级的情形下，第一指示信息为目标参数；
    所述目标APP的TD参数包括所述目标参数；
    所述SDK模块根据所述TD参数确定所述目标APP对应的目标网络切片，包括：
    所述SDK模块将第一网络切片作为所述目标APP对应的目标网络切片；其中，所述第一网络切片的第一标识中目标参数值与所述目标APP的目标参数值相同。
  12. 根据权利要求11所述的方法，其特征在于，所述目标参数的值不同时，APP在 终端设备中的数据处理级别不同。
  13. 根据权利要求11所述的方法，其通知在于，所述目标APP的目标参数值是所述目标APP的开发方与所述终端设备的生产方协商确定的。
  14. 一种终端设备，其特征在于，包括：
    一个或多个处理器；
    存储器；
    以及一个或多个计算机程序，其中所述一个或多个计算机程序存储在所述存储器上，当所述计算机程序被所述一个或多个处理器执行时，使得所述终端设备执行如权利要求1-13中任一项所述的通信方法。
  15. 一种芯片，其特征在于，所述芯片包括处理电路、收发管脚；其中，
    所述收发管脚和所述处理电路通过内部连接通路互相通信；
    所述处理电路执行如权利要求1-13中任一项所述的通信方法，以控制接收管脚接收信号，以控制发送管脚发送信号。
  16. 一种计算机可读存储介质，包括计算机程序，其特征在于，当所述计算机程序在电子设备上运行时，使得所述电子设备执行如权利要求1-13中任一项所述的通信方法。
PCT/CN2023/114031 2022-12-12 2023-08-21 通信方法及终端设备 Ceased WO2024124949A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US19/117,016 US20260122556A1 (en) 2022-12-12 2023-08-21 Communication method and terminal device
CN202380059429.5A CN119698861A (zh) 2022-12-12 2023-08-21 通信方法及终端设备
EP23902158.7A EP4576863A4 (en) 2022-12-12 2023-08-21 COMMUNICATION METHOD AND TERMINAL DEVICE

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211589413.9 2022-12-12
CN202211589413.9A CN118200938A (zh) 2022-12-12 2022-12-12 通信方法及终端设备

Publications (1)

Publication Number Publication Date
WO2024124949A1 true WO2024124949A1 (zh) 2024-06-20

Family

ID=91395370

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/114031 Ceased WO2024124949A1 (zh) 2022-12-12 2023-08-21 通信方法及终端设备

Country Status (4)

Country Link
US (1) US20260122556A1 (zh)
EP (1) EP4576863A4 (zh)
CN (2) CN118200938A (zh)
WO (1) WO2024124949A1 (zh)

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111165025A (zh) * 2017-10-16 2020-05-15 华为技术有限公司 协同终端切片功能和网络切片功能
CN112087779A (zh) * 2019-06-13 2020-12-15 中国电信股份有限公司 网络切片优先级管理方法、装置和系统、存储介质
CN113068226A (zh) * 2021-04-06 2021-07-02 中国联合网络通信集团有限公司 流量控制方法、流量控制规则同步方法、终端、服务器
CN113498086A (zh) * 2020-04-07 2021-10-12 华为技术有限公司 调整接入网络切片的方法、通信设备、网络设备与系统
CN114040410A (zh) * 2021-11-30 2022-02-11 中国电信股份有限公司 终端认证方法、网络侧设备以及存储介质
WO2022052623A1 (zh) * 2020-09-11 2022-03-17 Oppo广东移动通信有限公司 网络接入方法、装置、终端及存储介质
CN114845355A (zh) * 2022-04-29 2022-08-02 中国电信股份有限公司 网络接入方法及装置、终端设备、网络设备、存储介质
WO2022194359A1 (en) * 2021-03-16 2022-09-22 Lenovo (Singapore) Pte. Ltd. Platform independent application programming interface configuration

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10602422B1 (en) * 2018-12-10 2020-03-24 Verizon Patent And Licensing Inc. Application-based user equipment route selection policy mapping
CN114080054B (zh) * 2020-08-13 2024-09-24 华为技术有限公司 一种pdu会话建立方法、终端设备和芯片系统

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111165025A (zh) * 2017-10-16 2020-05-15 华为技术有限公司 协同终端切片功能和网络切片功能
CN112087779A (zh) * 2019-06-13 2020-12-15 中国电信股份有限公司 网络切片优先级管理方法、装置和系统、存储介质
CN113498086A (zh) * 2020-04-07 2021-10-12 华为技术有限公司 调整接入网络切片的方法、通信设备、网络设备与系统
WO2022052623A1 (zh) * 2020-09-11 2022-03-17 Oppo广东移动通信有限公司 网络接入方法、装置、终端及存储介质
WO2022194359A1 (en) * 2021-03-16 2022-09-22 Lenovo (Singapore) Pte. Ltd. Platform independent application programming interface configuration
CN113068226A (zh) * 2021-04-06 2021-07-02 中国联合网络通信集团有限公司 流量控制方法、流量控制规则同步方法、终端、服务器
CN114040410A (zh) * 2021-11-30 2022-02-11 中国电信股份有限公司 终端认证方法、网络侧设备以及存储介质
CN114845355A (zh) * 2022-04-29 2022-08-02 中国电信股份有限公司 网络接入方法及装置、终端设备、网络设备、存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4576863A4

Also Published As

Publication number Publication date
CN119698861A (zh) 2025-03-25
EP4576863A1 (en) 2025-06-25
EP4576863A4 (en) 2025-12-24
US20260122556A1 (en) 2026-04-30
CN118200938A (zh) 2024-06-14

Similar Documents

Publication Publication Date Title
CN113518319B (zh) 一种临近服务的业务处理方法、设备及系统
US11979450B2 (en) Communication method and apparatus
CN112136304A (zh) 用于基于应用的数据传输执行网络连接的电子设备及其方法
WO2022205254A1 (zh) 一种边缘配置服务器的确定方法及装置
US20210289430A1 (en) Electronic device and method for controlling same
CN112997518B (zh) 通信系统中的分解基站中的安全性管理
US20250203347A1 (en) Augmented reality service support capability negotiation method, network element, ue, and storage medium
CN112399476A (zh) 一种数据包传输方法、终端设备及网络设备
WO2025213735A1 (zh) 编码速率调整方法及设备
WO2024109221A1 (zh) 一种网络切片匹配方法和装置
CN113938880B (zh) 一种应用的验证方法及装置
EP4712546A1 (en) Information indication method and apparatus, communication device, and storage medium
WO2023098209A1 (zh) 一种数据传输保护方法、设备及系统
WO2024061475A1 (en) Quality of service of extended reality media over a wireless communication network
US12475628B2 (en) Methods, user equipment and apparatus for controlling VR image in a communication network
CN118102382B (zh) 一种数据处理方法及相关设备
WO2024124949A1 (zh) 通信方法及终端设备
CN118450522A (zh) 数据同步方法及设备
CN119071300A (zh) 云xr服务器的选择方法、设备、装置和存储介质
US20260113694A1 (en) Method and an apparatus for user equipment status assistance operation
WO2025138744A1 (zh) 数据同步方法及设备
WO2025161027A1 (zh) 无线通信方法及通信设备
WO2025153757A1 (en) Apparatus, method and computer program for direct exposure
WO2026091686A1 (zh) 一种传输速率调整方法、通信装置及存储介质
WO2025161024A1 (zh) 无线通信方法及通信设备

Legal Events

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

Ref document number: 23902158

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202380059429.5

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 2023902158

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 202380059429.5

Country of ref document: CN

ENP Entry into the national phase

Ref document number: 2023902158

Country of ref document: EP

Effective date: 20250320

WWP Wipo information: published in national office

Ref document number: 2023902158

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE