WO2022033345A1 - 一种pdu会话建立方法、终端设备和芯片系统 - Google Patents

一种pdu会话建立方法、终端设备和芯片系统 Download PDF

Info

Publication number
WO2022033345A1
WO2022033345A1 PCT/CN2021/110029 CN2021110029W WO2022033345A1 WO 2022033345 A1 WO2022033345 A1 WO 2022033345A1 CN 2021110029 W CN2021110029 W CN 2021110029W WO 2022033345 A1 WO2022033345 A1 WO 2022033345A1
Authority
WO
WIPO (PCT)
Prior art keywords
ursp
pdu session
application
terminal device
baseband processor
Prior art date
Application number
PCT/CN2021/110029
Other languages
English (en)
French (fr)
Inventor
刘彬俊
于晓靓
樊宇伟
连海
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP21855398.0A priority Critical patent/EP4192184A4/en
Publication of WO2022033345A1 publication Critical patent/WO2022033345A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1063—Application servers providing network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1073—Registration or de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • 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/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • 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/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5019—Ensuring fulfilment of SLA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a method for establishing a PDU session, a terminal device and a chip system.
  • the fifth-generation mobile communication system (5G communication system for short) includes multiple network slices (NS), each of which can provide different service carrying capabilities for different applications at the same time, thereby improving the flexibility of the 5G communication system. and business suitability.
  • NS network slices
  • the application is usually installed on the terminal device, because the communication between the application and the application server requires a data transmission channel, and the 5G communication system supports the protocol data unit (protocol data unit, PDU) connection service. Therefore, a PDU session can be established between the terminal device and the network slice as a data transmission channel between the application and the application server.
  • protocol data unit protocol data unit
  • the present application provides a method for establishing a PDU session, a terminal device and a chip system, so as to perform URSP matching and selection through a baseband processor and establish a PDU session, so as to provide data transmission communication between an application program and an application server.
  • an embodiment of the present application provides a method for establishing a PDU session, which is applied to a terminal device, where the terminal device includes an application processor and a baseband processor, the baseband processor stores a URSP list, and the URSP list includes at least one URSP .
  • the method includes:
  • the application processor obtains the first data packet of the application; and adds the identification information of the application to the first data packet to form a second data packet; and sends the second data packet to the baseband processor.
  • the baseband processor searches the URSP corresponding to the identification information in the URSP list; and, according to the URSP corresponding to the identification information, determines the PDU session activation parameter; And, establishes the PDU session according to the PDU session activation parameter, and the PDU session uses for transmitting the second data packet.
  • the first data packet sent by the application to the application processor usually first passes through the application processor to the baseband processor, then is sent by the baseband processor to the core network device, and finally is sent by the core network device to the application server. Since the first data packet sent by the application may not include the identification information of the application, the baseband processor may not be able to perform URSP matching selection and establish a PDU session according to the identification information.
  • the application processor first adds the identification information of the application to each first data packet of the application to form a second data packet, and then sends the second data packet to the baseband processor. Then, the baseband processor can acquire the identification information of the application, determine the corresponding URSP in the URSP list according to the identification information, and establish a PDU session according to the URSP. Therefore, in the method for establishing a PDU session provided by this embodiment, the baseband processor can perform URSP matching selection and establish a PDU session, so as to provide data transmission communication between the application program and the application server.
  • the identification information is an application identification App ID, or a user account identification UID.
  • the App ID is used to uniquely identify the application
  • the UID is used to uniquely identify a user account of the application.
  • the baseband processor searches the URSP list for the URSP corresponding to the identification information, including: the baseband processor searches the URSP list for the URSP corresponding to the App ID.
  • the baseband processor can determine the App ID of the second data packet to be transmitted, perform URSP matching selection according to the App ID, and establish a PDU session to provide data transmission for the application program and the application server. Pass.
  • the baseband processor searches the URSP list for a URSP corresponding to the identification information, including: the baseband processor determines the App ID corresponding to the UID according to a preset correspondence table, and the corresponding The relationship table includes the corresponding relationship between the UID and the App ID; and the URSP corresponding to the App ID is searched in the URSP list.
  • the baseband processor can determine the UID of the second data packet to be transmitted, perform URSP matching selection and establish a PDU session according to the UID, and provide data transmission communication between the application program and the application server.
  • the application processor adds the identification information of the application to the first data packet to form the second data packet, including: the application processor adds the unoccupied field in the Ethernet header or the Ethernet tail of the first data packet
  • the identification information of the application program forms the second data packet.
  • the application processor By adding the identification information to an unoccupied field in the Ethernet header or the Ethernet tail of the first data packet, the application processor is prevented from adding a new field to the first data packet, which helps to save resources.
  • the method before the application processor acquires the first data packet of the application, the method further includes: the baseband processor sends a registration request to the core network device; and, receiving a registration acceptance message sent by the core network device, the registration The acceptance message carries the network slice selection auxiliary information Allowed NSSAI that the core network device allows the terminal device to use; and stores the Allowed NSSAI.
  • the baseband processor can select the legal S-NSSAI in the URSP according to the Allowed NSSAI to establish a PDU session. .
  • the method further includes: the baseband processor receives a terminal device management command sent by the core network device, The command carries at least one URSP; and stores the at least one URSP to form a URSP list; and sends a terminal device management complete message to the core network device, the message is used to indicate that the baseband processor has processed the terminal device management command.
  • the baseband processor can locally execute the URSP matching policy based on the URSP list according to the identification information of the application program and establish a PDU session only after locally storing the URSP list.
  • the PDU session activation parameters include single network slice selection assistance information S-NSSAI, data network name DNN and protocol type; wherein the S-NSSAI is included in the allowed network slice selection assistance information Allowed NSSAI.
  • the method further includes: the baseband processor receives a configuration update command sent by the core network device, where the configuration update command carries a first URSP and a second URSP, and the second URSP is an updated URSP of the first URSP; And, according to the configuration update command, the first URSP in the URSP list is replaced with the second URSP.
  • invalid URSPs in the URSP list can be updated, and to a certain extent, network exceptions in the running process of the application can be avoided.
  • the baseband processor establishes the PDU session according to the PDU session activation parameter, including: the baseband processor determines the established PDU session; if there is no PDU session established according to the PDU session activation parameter in the established PDU session, then The baseband processor establishes the PDU session according to the PDU session activation parameter.
  • the method can avoid the problem of resource waste caused by repeated establishment of PDU sessions according to the same PDU session activation parameters by baseband processing to a certain extent.
  • the baseband processor is a modem.
  • an embodiment of the present application provides a terminal device, the terminal device includes an application processor and a baseband processor, the baseband processor stores a terminal device routing policy URSP list, and the URSP list includes at least one URSP.
  • the application processor is configured to acquire a first data packet of an application; add identification information of the application to the first data packet to form a second data packet; and send the second data packet to the baseband processor.
  • the baseband processor is configured to search for a URSP corresponding to the identification information in the URSP list; determine a PDU session activation parameter according to the URSP corresponding to the identification information; and establish a PDU session according to the PDU session activation parameter, the PDU The session is used to transmit the second data packet.
  • the identification information is an application identification App ID, or a user account identification UID.
  • the baseband processor searches the URSP list for the URSP corresponding to the identification information, including: the baseband processor searches the URSP list for the URSP corresponding to the App ID.
  • the baseband processor searches the URSP list for the URSP corresponding to the identification information, including: the baseband processor determines the App ID corresponding to the UID according to the preset correspondence table, and the correspondence table Include the corresponding relationship between UID and App ID; and, find the URSP corresponding to the App ID in the URSP list.
  • the application processor adds the identification information of the application to the first data packet to form the second data packet, which specifically includes:
  • the application processor adds the identification information of the application to the unoccupied field of the Ethernet header or the Ethernet tail of the first data packet to form a second data packet.
  • the baseband processor before the application processor acquires the first data packet of the application, is further configured to send a registration request to the core network device; and receive a registration acceptance message sent by the core network device, the registration acceptance message Carrying network slice selection assistance information Allowed NSSAI that the core network device allows the terminal device to use; and storing the Allowed NSSAI.
  • the baseband processor is further configured to: receive a terminal device management command sent by the core network device, the The command carries at least one URSP; stores the at least one URSP to form a URSP list; and sends a terminal device management completion message to the core network device, where the message is used to indicate that the baseband processor has processed the terminal device management command.
  • the PDU session activation parameters include single network slice selection assistance information S-NSSAI, data network name DNN and protocol type; wherein S-NSSAI is included in the allowed network slice selection assistance information Allowed NSSAI.
  • the baseband processor is further configured to receive a configuration update command sent by the core network device, where the configuration update command carries a first URSP and a second URSP, and the second URSP is an updated URSP of the first URSP; and, The first URSP in the URSP list is replaced with the second URSP according to the configuration update command.
  • the baseband processor establishes the PDU session according to the PDU session activation parameter, including: the baseband processor determines the established PDU session; if there is no PDU session established according to the PDU session activation parameter in the established PDU session, Then the baseband processor establishes a PDU session according to the PDU session activation parameter.
  • the baseband processor is a modem.
  • an embodiment of the present application provides a chip system, including a memory, an application processor and a baseband processor coupled to the memory, and the application processor and the baseband processor execute a computer program stored in the memory to implement the first A PDU session establishment method provided by an aspect.
  • embodiments of the present application provide a computer-readable storage medium, where the computer-readable storage medium stores a computer program, and when the computer program is executed by an application processor and a baseband processor, implements the PDU provided in the first aspect above Session establishment method.
  • an embodiment of the present application provides a computer program product that, when the computer program product runs on a terminal device, enables the terminal device to execute the method for establishing a PDU session provided in the first aspect.
  • FIG. 1 is a schematic block diagram of a 5G communication system architecture provided by an embodiment of the present application
  • FIG. 2 is a schematic diagram of an application scenario of network slicing provided by an embodiment of the present application
  • FIG. 3 is a schematic structural diagram of a terminal device provided by an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of the first stage of PDU session establishment provided by an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of the second stage of PDU session establishment provided by an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of a URSP matching strategy provided by an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of the first stage of PDU session establishment provided by another embodiment of the present application.
  • FIG. 8 is a schematic flowchart of a method for establishing a PDU session provided by another embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a data packet provided by an embodiment of the present application.
  • FIG. 10 is a schematic flowchart of a second stage of PDU session establishment provided by yet another embodiment of the present application.
  • FIG. 11 is a schematic flowchart of the second stage of PDU session establishment provided by some other embodiments of the present application.
  • An embodiment of the present application provides a method for establishing a PDU session, and the method is applicable to a 5G communication system, a communication system above 5G, a future evolved public land mobile network (PLMN), and subsequent support for the 3rd Generation Partnership Project (3rd generation partnership project, 3GPP) protocol version communication system, which is not limited in this embodiment of the present application.
  • PLMN public land mobile network
  • 3rd generation partnership project 3rd generation partnership project, 3GPP
  • the 5G communication system is taken as an example below to describe the PDU session establishment method provided by the embodiment of the present application.
  • FIG. 1 is a schematic block diagram of a 5G communication system architecture provided by an embodiment of the present application.
  • the 5G communication system includes: a terminal device 110, an access network device 120, a core network device 130, and a data network 160 (DN).
  • DN data network 160
  • the terminal device 110 may be connected to the access network device 120 deployed by the operator through a wireless air interface, and then connected to the data network 160 through the core network device 130.
  • the terminal device 110 may be a user equipment (user equipment, UE), such as a smart phone, a tablet computer, a notebook computer, a smart wearable device, a personal digital assistant (personal digital assistant, PDA), and the like.
  • UE user equipment
  • PDA personal digital assistant
  • the access network device 120 is mainly used to implement functions such as wireless physical layer functions, resource scheduling and wireless resource management, wireless access control, and mobility management.
  • the access network device may be an access network (access network, AN) or a radio access network (radio access network, RAN) device.
  • the core network device 130 includes a management device 140 and a gateway device 150 .
  • the management device 140 may include functional units such as an access and mobility management function (access&mobility function, AMF), a session management function (session management function, SMF), and a policy control function (policy control function, PCF). These functional units can work independently, or can be combined to achieve certain control functions.
  • AMF, SMF, and PCF can work together to complete access control and mobility management functions such as access authentication, security encryption, and location registration of terminal devices, as well as session management functions such as establishment, release, and modification of user plane transmission paths. , and the function of analyzing some network slice-related data and terminal device-related data.
  • the gateway device 150 is mainly used to establish a channel with the terminal device, and forward data packets between the terminal device and the external data network on the channel.
  • the data network 160 may correspond to a variety of different service domains, such as an IP multimedia subsystem (IMS), the Internet (Internet), a third-party application-related business domain, etc., and is mainly used to provide a variety of data for terminal devices.
  • service domains such as an IP multimedia subsystem (IMS), the Internet (Internet), a third-party application-related business domain, etc.
  • Business services which may include network devices such as servers (such as third-party application servers), routers, and gateways.
  • FIG. 1 is only an exemplary architecture diagram of the 5G communication system.
  • the network architecture of the 5G communication system may also include other functional units or functional entities. This is not limited.
  • a 5G communication system includes multiple network slices.
  • network slicing is a logical network formed by combining related service functions, network resources and network configuration in a physical network, which can meet specific service requirements (such as delay, jitter, packet loss in a specific range) rate, bandwidth, etc.).
  • specific service requirements such as delay, jitter, packet loss in a specific range
  • bandwidth such as bandwidth, etc.
  • the 5G communication system can simultaneously provide different service carrying capabilities for different applications (such as game applications, chat applications, etc.), thereby improving the flexibility of the 5G network architecture, service adaptability and resource utilization.
  • the application manufacturer signs the network slicing service with the operator, so that the user can communicate with the corresponding application server through the network slice when running the application, improving the smoothness of the application running in the terminal device , to improve the user experience.
  • an application manufacturer signs a network slicing service with an operator, it will negotiate with the operator to determine a quality of service rules (quality of service rules, Qos rules).
  • Qos rules stipulate the basic parameters such as bandwidth, delay, packet loss rate and so on of the contracted network slice transmission data.
  • the operator's core network equipment will generate a terminal equipment routing policy (UE route selection policy, URSP).
  • the terminal device selects the corresponding network slice for the application according to the URSP, and establishes a PDU session with the network slice, so that the application communicates with the application server.
  • the URSP includes a traffic descriptor (traffic descriptor) and a route selection descriptor (route selection descriptor).
  • the traffic descriptor is used to describe the characteristics of the traffic transmitted by the terminal device, which can include application identification (App ID), target internet protocol (IP) triplet, and data network name (DNN) , any of the parameters such as the fully qualified domain name (FQDN) of the access target.
  • App ID application identification
  • IP internet protocol
  • DNN data network name
  • FQDN fully qualified domain name
  • the App ID is used to uniquely identify an application
  • the IP triplet includes the destination IP address, destination port number, and protocol type.
  • the routing descriptor is used to describe the parameters required by the terminal device to activate the PDU session with the network slice, and may include parameters such as network slice selection assistance information (NSSAI), DNN, and protocol type.
  • NSSAI network slice selection assistance information
  • DNN DNN
  • protocol type the NSSAI usually includes multiple single network slice selection auxiliary information (single-NSSAI, S-NSSAI), and the S-NSSAI is used to uniquely identify a single network slice.
  • the protocol type may be a transmission control protocol (transmission control protocol, TCP), a user datagram protocol (user datagram protocol, UDP), and the like.
  • the core network device may send the corresponding URSP to the terminal device according to the contract information between the terminal device and the operator.
  • a user can sign up and purchase a targeted 5G network slice package by using the operator's business hall, dialing the operator's customer service phone, or other means.
  • the resources in this package can include: 100 GB of directed traffic of multiple network slices of designated applications, which can include application A, application B, application C, application D, etc.
  • the core network device sends the relevant URSPs of all specified applications within the package scope to the terminal device corresponding to the contracted mobile phone number.
  • the related URSPs may include URSPs corresponding to application A, application B, application C, and application D.
  • each application may have multiple URSPs.
  • the URSPs of application A sent by the core network include URSP-A1, URSP-A2, and URSP-A3.
  • the traffic descriptors are usually different, and the routing descriptors can be the same or different.
  • the traffic descriptors of URSP-A1, URSP-A2 and URSP-A3 can be App ID, IP triplet and DNN respectively, and the routing descriptors can be NSSAI1+DNN+TCP, NSSAI1+DNN+TCP and NSSAI2 in order +DNN+TCP.
  • the NSSAI may be a routing list, in which multiple S-NSSAIs corresponding to the traffic descriptors are sequentially recorded according to different priorities.
  • the routing list corresponding to NSSAI1 includes S-NSSAI1, S-NSSAI2, S-NSSAI3, S-NSSAI4 and S-NSSAI5 in descending order of priority.
  • FIG. 2 is a schematic diagram of an application scenario of network slicing provided by an embodiment of the present application.
  • the application program in the terminal device can select the corresponding network slice according to the URSP, and connect to the corresponding application server.
  • the network slice used by the application in the terminal device is determined according to the network slice service contracted by the application manufacturer and the operator.
  • the correspondence between each application and network slice may include the following (1) to (3):
  • application A may connect to application server A-1 using a first network slice
  • application B may connect to application server B using a third network slice.
  • application A may connect to application server A-1 using a first network slice, and may also connect to application server A-2 using a second network slice.
  • application C may connect to application server C using a fourth network slice.
  • Application D can connect to application server D using the fourth network slice.
  • an embodiment of the present application provides a method for establishing a PDU session, which is used to establish a PDU session between a terminal device and a network slice, so as to improve the data transmission rate and user experience.
  • the terminal device involved in the embodiments of the present application may include an application program layer (APP), an application processor (application processor, AP), and a baseband processor (such as a modem Modem).
  • the application layer may include a series of application packages, and the application package may include applications such as game application, chat application, short message, calendar, camera, video, navigation, gallery, and call.
  • the application processor is used to provide an application programming interface (application programming interface, API) and a programming framework to each application in the application layer.
  • the application handler may include some predefined functions, such as functions for receiving events sent by the application framework layer.
  • Modem is used to send and receive messages from other devices (such as core network devices), convert digital signals into analog signals through modulation at the sending end, and convert analog signals into digital signals through demodulation at the receiving end.
  • the PDU session establishment process provided in this embodiment may be divided into two stages.
  • the terminal device registers with the core network device after booting, replacing the subscriber identity module (SIM) card, or canceling the airplane mode.
  • SIM subscriber identity module
  • the core network device sends the URSP to the terminal device after the terminal device is successfully registered.
  • the terminal device establishes a PDU session according to different applications. Specifically, the terminal device can execute the URSP matching policy through the application processor to establish a PDU session with the network slice; it can also execute the URSP matching policy through the modem to establish a PDU session with the network slice, as shown below.
  • the following describes two stages of establishing a PDU session with reference to the terminal device shown in FIG. 3 .
  • FIG. 4 is a schematic flowchart of the first stage of establishing a PDU session according to an embodiment of the present application. Referring to FIG. 4, the method specifically includes the following steps S401-S409.
  • the modem sends a registration request to the core network device.
  • the modem will automatically send a registration request (Registration request) to the terminal device, thereby initiating a registration process to the core network device. Or the modem sends a registration request to the core network device after receiving the command issued by the application processor.
  • the core network device sends a registration acceptance message to the modem, where the registration acceptance message carries allowed network slice selection assistance information (Allowed NSSAI).
  • the core network device After receiving the registration request sent by the terminal device, the core network device will send a registration acceptance message (Registration Accept) to the modem of the terminal device, and the registration acceptance message carries the Allowed NSSAI.
  • Registration Accept a registration acceptance message
  • Allowed NSSAI is the NSSAI that the core network device allows the terminal device to use.
  • the modem sends the Allowed NSSAI to the application processor.
  • the application processor stores the Allowed NSSAI.
  • NSSAI selects a valid S-NSSAI in the URSP to establish a PDU session.
  • the terminal device is successfully registered in the core network device.
  • the core network device continues to perform subsequent steps S405-S409, so as to send the URSP corresponding to the above-mentioned network slicing service to the terminal device.
  • the core network device sends a terminal device management command (Manage UE policy command) to the modem of the terminal device, and the command carries at least one URSP.
  • a terminal device management command Manage UE policy command
  • the core network device can use the downlink non-access stratum transport channel (DL NAS Transport)
  • DL NAS Transport downlink non-access stratum transport channel
  • the relevant URSP of the specified application is sent to the terminal device.
  • the related URSPs may include URSPs corresponding to application A, application B, application C, and application D.
  • the modem sends the at least one URSP to the application processor.
  • the application processor stores the at least one URSP to form a URSP list.
  • the terminal device can use the network slice only when the SIM card installed in the terminal device and the network slice to be used belong to the same operator. Therefore, after receiving the URSP code stream sent by the modem, the application processor needs to decode and verify the validity of the URSP.
  • verifying the validity of the URSP refers to judging whether the PLMN identification code carried by the URSP is the same as the PLMN identification code of the SIM card currently communicating with the terminal device. If not, it means that the URSP is valid, and the URSP is stored. If not, the URSP is not stored.
  • the PLMN identification code is used to identify the operator to which it belongs.
  • the URSP list may be as shown in Table 3.
  • the URSP list includes all URSPs issued by the core network device to the terminal device, including the URSPs corresponding to application A, application B, application C, and application D.
  • the priority of each URSP decreases in order from top to bottom.
  • URSP in the URSP list, at least one default URSP of the default network slice (ie Default URSP) is included.
  • Default URSP its traffic descriptor is Match All, and each application can use the default network slice.
  • the application processor sends a terminal equipment management complete message (Manage UE policy complete) to the modem.
  • a terminal equipment management complete message Manage UE policy complete
  • the application processor After storing the URSP, the application processor sends a terminal device management completion message to the modem.
  • the terminal device management completion message is used to notify the core network device that the terminal device has responded to the terminal device management command.
  • the modem sends a terminal device management completion message to the core network device.
  • the modem may send a terminal device management completion message to the core network device through an uplink non-access stratum transport channel (UL NAS Transport).
  • UL NAS Transport uplink non-access stratum transport channel
  • the application processor deletes the URSP, and the modem sends a terminal equipment management rejection message (Manage UE policy reject) to the core network device through the UL NAS Transport for Notify the core network device that the terminal device has rejected the terminal device management command.
  • a terminal equipment management rejection message Manage UE policy reject
  • the URSP of the subscribed application program may be changed, for example, from the first URSP to the second URSP. If the URSP is changed, the core network device sends a configuration update command (Configuration update command) to the terminal device.
  • the configuration update command can carry the first URSP and the second URSP to instruct the application processor to update the first URSP in the URSP list. Replaced with the second URSP.
  • FIG. 5 is a schematic flowchart of the second stage of establishing a PDU session according to an embodiment of the present application.
  • the application processor of the terminal device executes the URSP matching policy and controls the establishment of a PDU session with the network slice.
  • the method specifically includes the following steps S501-S506.
  • the application processor monitors that the application program arrives in the foreground to run.
  • the running of the application includes foreground running and background running.
  • foreground running means that the user can currently operate and control the application during the running process of the terminal device.
  • running in the background means that when the application is running on the terminal device, the user cannot operate and control the application.
  • the foreground running of the application may be that the current application is in the active state, and when the application is running in the background, the application is in the inactivity state.
  • the application processor acquires the identification information of the data packet of the application program.
  • the identification information of the data packet may be App ID, IP triplet, DNN, FQDN, etc.
  • the application processor searches for the PDU session activation parameter in the URSP list according to the identification information and the URSP matching policy.
  • the application processor After the application processor detects that the application program arrives to run in the foreground, the application processor can use the identification information to match and select the corresponding URSP according to the URSP matching policy (see steps S601-S609 shown below), and select the corresponding URSP from the URSP. PDU session activation parameters, so as to activate the corresponding PDU session according to the PDU session activation parameters in the subsequent steps.
  • the application processor sends a PDU session establishment request to the modem according to the PDU session activation parameter.
  • the network slice corresponding to the PDU session activation parameter may have been activated, that is, the PDU session between the terminal device and the network slice has been established. Therefore, in a possible implementation manner, before sending the PDU session establishment request to the modem according to the PDU session activation parameter, the application processor may first determine whether the network slice corresponding to the PDU session activation parameter has been successfully activated. If the activation has been successful, there is no need to activate it again to avoid repeated operations. If the activation is not successful, send a PDU session establishment request to the modem according to the PDU session activation parameter to activate the network slice. It should be noted that activating the network slice refers to establishing a PDU session between the terminal device and the network slice.
  • the PDU session establishment request (PDU session establishment request) carries the PDU session activation parameter, so as to request to activate the PDU session of the network slice corresponding to the PDU session activation parameter.
  • the PDU session activation parameter is S-NSSAI1
  • the PDU session establishment request is used to request to activate the PDU session with the network slice identified as S-NSSAI1.
  • the modem sends the PDU session establishment request to the core network device.
  • the core network device sends a PDU session acceptance message to the modem.
  • the PDU session establishment accept message (PDU session establishment accept) carries the PDU session activation parameter, which is used to indicate that the PDU session of the network slice corresponding to the PDU session activation parameter has been activated.
  • the PDU session activation parameter includes S-NSSAI1
  • the PDU session acceptance message is used to indicate that the PDU session of the network slice corresponding to S-NSSAI1 has been activated.
  • the modem sends a PDU session acceptance message to the application processor.
  • the terminal device can execute the URSP matching policy through the application processor according to the identification information of the data packet of the application program, and establish a PDU session with the network slice.
  • the application processor binds the data packet route containing the identification information to the PDU session. After that, the data packet including the identification information can be transmitted through the PDU session, so as to realize the communication between the application program and the application server through the network slice.
  • FIG. 6 is a schematic flowchart of a URSP matching strategy provided by an embodiment of the present application, which describes the process of searching for PDU session activation parameters in the URSP list according to the identification information of the data packet and the URSP matching strategy in the above step S503.
  • the URSP matching strategy can be applied to the application processor as well as to the modem. Specifically, it includes the following steps S601-S608.
  • S601 start to traverse the URSP list according to the priority.
  • S602 Determine whether there is an unvisited URSP in the URSP list. If there are no unvisited URSPs, the PDU activation parameter selection fails. If there is an unvisited URSP, the next step S603 is performed.
  • S603 Match the traffic descriptor of the URSP with the highest priority among the unvisited URSPs according to the identification information. Exemplarily, if among the unvisited URSPs, the URSP with the highest priority is URSP-A1, and its traffic descriptor includes the App ID, then the App ID of the application is matched with the traffic descriptor.
  • step S605 the next step S605 is executed.
  • S606 Determine whether there is an unvisited S-NSSAI in the routing list.
  • step S607 if there is an unvisited S-NSSAI in the routing list, the next step S607 is executed. If there is no unvisited S-NSSAI in the routing list, step S609 is executed.
  • S607 Determine whether the S-NSSAI with the highest priority among the unvisited S-NSSAIs is in the Allowed NSSAI list.
  • step S608 is performed.
  • S608 select the S-NSSAI and other routing information in the currently visited URSP as the PDU session activation parameters.
  • the remaining routing information refers to the remaining information in the routing descriptor other than NSSAI, such as DNN, protocol type, and the like.
  • DNN is cmnet
  • protocol type may be TCP protocol or UDP protocol.
  • S609 select the remaining routing descriptors in the currently accessed URSP as the PDU session activation parameters. It should be noted that since the terminal device does not select S-NSSAI, the terminal device uses the default network slice according to information such as DNN and protocol type.
  • the PDU session activation parameter corresponding to the identification information can be selected.
  • FIG. 7 is a schematic flowchart of the first stage of establishing a PDU session according to another embodiment of the present application. Referring to FIG. 7, the method specifically includes the following steps S701-S706.
  • the modem sends a registration request to the core network device.
  • the modem will automatically send a registration request (Registration request) to the terminal device, thereby initiating a registration process to the core network device. Or the modem sends a registration request to the core network device after receiving the command issued by the application processor.
  • the core network device sends a registration acceptance message to the modem, where the message carries the Allowed NSSAI.
  • step S702 For the specific content of step S702, please refer to S402, which is not repeated in this embodiment.
  • the modem stores the Allowed NSSAI.
  • the terminal device is successfully registered in the core network.
  • the core network device After the terminal device is successfully registered in the core network device, for example, if the mobile phone number currently used by the terminal device subscribes to the network slicing service, or some application manufacturers configure the terminal device with the application program provided by the network slicing service , the core network device continues to perform subsequent steps S704-S706, so as to send the URSP corresponding to the above-mentioned network slicing service to the terminal device.
  • the core network device sends a terminal device management command to the modem, where the command carries at least one URSP.
  • the core network may send a terminal device management command through a downlink non-access stratum transport channel (DL NAS Transport) to transmit the relevant URSP to the terminal device.
  • DL NAS Transport downlink non-access stratum transport channel
  • the modem stores the at least one URSP to form a URSP list.
  • the modem decodes and checks the validity of the URSP, and stores the URSP after checking the validity to form a URSP list.
  • the specific content of the validity check please refer to step S407, which is not repeated in this embodiment.
  • the modem sends a terminal device management completion message to the core network device.
  • the modem may send a terminal device management completion message to the core network device through an uplink non-access stratum transport channel (UL NAS Transport).
  • UL NAS Transport uplink non-access stratum transport channel
  • the baseband processor can locally execute the URSP matching policy based on the URSP list according to the identification information of the application program and establish a PDU session only after locally storing the URSP list.
  • steps S701-S706 Compared with the first-phase flow of establishing a PDU session shown in steps S401-S409, the flow shown in steps S701-S706 is simpler. In steps S701-S706, after acquiring the Allowed NSSAI, URSP and other parameters, the modem directly stores them locally without forwarding them to the application processor, which helps to improve the efficiency of registration and URSP delivery.
  • the modem deletes the URSP and sends a terminal device management rejection message to the core network device.
  • the terminal device after the terminal device is successfully registered in the core network, its URSP may be changed, for example, from the first URSP to the second URSP. If the URSP is changed, the core network device sends a configuration update command (Configuration update command) to the terminal device.
  • the configuration update command can carry the first URSP and the second URSP to instruct the modem to replace the first URSP in the URSP list with Second URSP.
  • the second stage of the establishment of the PDU session will be described below based on the content of the first stage of the establishment of the PDU session shown in steps S701-S706.
  • FIG. 8 is a schematic flowchart of the second stage of establishing a PDU session provided by an embodiment of the present application, which describes the process that the modem side executes the URSP matching policy and establishes a PDU session, which specifically includes the following steps S801-S807.
  • the application program sends the first data packet to the application processor.
  • a plurality of first data packets are usually generated, and these first data packets are sent to the application processor.
  • the application processor adds an App ID to the first data packet to form a second data packet.
  • the application processor adds an App ID to each received first data packet to identify the application to which the first data packet belongs.
  • the software system architecture of the terminal device may include an application layer, a TCP layer, an IP layer and a physical layer.
  • the user data generated by the application program in the running process can be transmitted to the core network device sequentially through the application program layer, the TCP layer, the IP layer and the physical layer.
  • the application layer adds application headers to user data to form application data, and sends the application data to the TCP layer.
  • the TCP layer adds a TCP header to the application data to form a TCP segment.
  • the IP layer adds an IP header to the TCP segment to form an IP packet.
  • the maximum size of IP data packets is 1500 bytes.
  • the physical layer adds an Ethernet (Ethernet) header and an Ethernet tail to the IP data packet to form an Ethernet frame.
  • the application processor may add the App ID in the invalid field of the Ethernet header or the tail of the data packet.
  • the invalid field refers to a field that is not occupied.
  • the application processor avoids adding a new field to the first data packet by adding the identification information to the invalid field in the Ethernet header or the Ethernet tail of the first data packet.
  • the application processor sends the second data packet to the modem.
  • the modem searches for the PDU session activation parameter in the URSP list according to the App ID and the URSP matching policy.
  • step S804 according to the App ID and the URSP matching policy, the specific content of the PDU session activation parameter is searched in the URSP list, please refer to steps S601-S609, which will not be repeated in this embodiment.
  • the modem sends a PDU session establishment request (PDU session establishment request) to the core network device according to the PDU session activation parameter.
  • the modem when sending a PDU session establishment request to the terminal device according to the PDU session activation parameter, the modem first determines whether there is a PDU session established according to the PDU session activation parameter in the established PDU session. If the PDU session does not exist, a PDU session establishment request is sent to the core network device to establish a PDU session. If the PDU session exists, the modem does not repeat the establishment of the PDU session according to the PDU session activation parameter, and uses the established PDU session to transmit the second data packet.
  • the PDU session establishment request carries the PDU session activation parameter, so as to request to activate the PDU session of the network slice corresponding to the PDU session activation parameter.
  • the PDU session activation parameter includes S-NSSAI1
  • the PDU session establishment request is used to request to activate the PDU session with the network slice identified as S-NSSAI1.
  • the core network device sends a PDU session acceptance message to the modem.
  • the PDU session establishment accept message (PDU session establishment accept) carries the PDU session activation parameter, which is used to indicate that the PDU session of the network slice corresponding to the PDU session activation parameter has been activated.
  • the PDU session activation parameter includes S-NSSAI1
  • the PDU session acceptance message is used to indicate that the PDU session of the network slice corresponding to S-NSSAI1 has been activated.
  • the modem routes the packets containing the App ID to the PDU Session. After that, the data packet including the App ID can be transmitted through the PDU session, realizing the communication between the application and the application server through the network slice.
  • the first data packet sent by the application to the application processor usually first reaches the modem through the application processor, then is sent by the modem to the core network device, and finally sent by the core network device to the application server. Since the first data packet sent by the application may not include the identification information of the application, the modem cannot perform URSP matching selection and establish a PDU session according to the identification information.
  • the application processor first adds identification information of the application to each first data packet of the application to form a second data packet, and then sends the second data packet to the modem. Then, the modem can obtain the identification information of the application, determine the corresponding URSP in the URSP list according to the identification information, and establish a PDU session according to the URSP. Therefore, in the method for establishing a PDU session provided by this embodiment, URSP matching and selection can be performed through a modem and a PDU session can be established to provide data transmission communication between an application program and an application server.
  • FIG. 10 is a schematic flowchart of the second stage of PDU session establishment provided by another embodiment of the present application, which describes the process of the modem executing the URSP matching policy and establishing a PDU session with a network slice, including the following steps S1001-S1007.
  • the terminal device before the second stage of PDU session establishment provided in this embodiment, the terminal device also needs to perform the first stage process of PDU session establishment shown in steps S701 to S706, which is not repeated here in this implementation.
  • the application processor also needs to send the correspondence table between the user account identifier (User Identification, UID) of each application and the App ID to the modem for storage, and the modem forwards it to the core network device.
  • UID user account identifier
  • the UID is used to uniquely identify an account of the application, which may be the account's registered mobile phone number, registered email number, registered ID card number, account identification (Identification, ID) allocated by the application server, and the like.
  • an application program sends a first data packet to an application processor.
  • a plurality of first data packets are usually generated, and these first data packets are sent to the application processor.
  • the application processor adds a UID to the first data packet to form a second data packet.
  • step S802 for the method for the application processor to add the UID in the first data packet, please refer to the method for the application processor to add the App ID in the first data packet in step S802, which will not be repeated in this embodiment.
  • the application processor sends the second data packet to the modem.
  • the modem determines the App ID corresponding to the UID according to the preset correspondence table.
  • UID-A of application A corresponds to App ID-A.
  • App ID-B corresponding to UID-B of application B.
  • the modem searches for the PDU session activation parameter in the URSP list according to the App ID and the URSP matching policy.
  • the modem sends a PDU session establishment request to the core network device according to the PDU session activation parameter.
  • the core network device sends a PDU session acceptance message to the modem.
  • steps S1005-S1007 please refer to steps S804-S806, which will not be repeated in this embodiment.
  • the terminal device can execute the URSP matching policy through the modem by using the UID, and establish a PDU session with the network slice.
  • the modem routes the packets containing the UID to the PDU session.
  • the data packet including the UID can be transmitted through the PDU session, so as to realize the communication between the application and the application server through the network slice.
  • FIG. 11 is a schematic flowchart of the second stage of establishing a PDU session provided by some other embodiments of the present application, which describes the process that the modem executes a URSP matching policy at the modem according to IP triplet, FQND or DNN, and establishes a PDU session.
  • the method includes the following steps S1101-S1105.
  • the application program sends the data packet to the application processor.
  • the application processor sends the data packet to the modem.
  • the modem searches for the PDU session activation parameter in the URSP list according to any one of the IP triplet, FQND, and DNN of the data packet and the URSP matching policy.
  • the modem sends a PDU session establishment request to the core network device according to the PDU session activation parameter.
  • the core network device sends a PDU session acceptance message to the modem.
  • steps S1104-S1105 please refer to steps S805-S806, and details are not described herein again in this embodiment.
  • the terminal device can execute the URSP matching policy through the modem according to the IP triplet, FQND or DNN, and establish a PDU session with the network slice.
  • the modem binds the data packet route containing the IP triplet, FQND or DNN to the PDU session, so as to realize the communication between the application and the application server through the network slice.
  • this embodiment also provides a terminal device, the terminal device includes an application processor and a baseband processor, and the baseband processor stores a terminal device routing policy URSP list, the URSP The list includes at least one URSP.
  • the application processor is configured to obtain a first data packet of the application; add identification information of the application to the first data packet to form a second data packet; and send the second data packet to the baseband processor.
  • the baseband processor is configured to search for a URSP corresponding to the identification information in the URSP list; determine a PDU session activation parameter according to the URSP corresponding to the identification information; and establish a PDU session according to the PDU session activation parameter, and the PDU session is used for transmission second data packet.
  • the identification information is an application identification App ID, or a user account identification UID.
  • the baseband processor searches the URSP list for the URSP corresponding to the identification information, including: the baseband processor searches the URSP list for the URSP corresponding to the App ID.
  • the baseband processor searches the URSP list for the URSP corresponding to the identification information, including: the baseband processor determines the App ID corresponding to the UID according to the preset correspondence table, and the correspondence table Include the corresponding relationship between UID and App ID; and, find the URSP corresponding to the App ID in the URSP list.
  • the application processor adds the identification information of the application to the first data packet to form the second data packet, which specifically includes: the application processor is not occupied by the Ethernet header or the Ethernet tail of the first data packet.
  • the identification information of the application is added to the field to form a second data packet.
  • the baseband processor before the application processor acquires the first data packet of the application, is further configured to send a registration request to the core network device; and receive a registration acceptance message sent by the core network device, the registration acceptance message Carrying network slice selection assistance information Allowed NSSAI that the core network device allows the terminal device to use; and storing the Allowed NSSAI.
  • the baseband processor is further configured to: receive a terminal device management command sent by the core network device, the The command carries the URSP; stores the at least one URSP to form a URSP list; and sends a terminal device management complete message to the core network device, where the message is used to indicate that the baseband processor has processed the terminal device management command.
  • the PDU session activation parameters include single network slice selection assistance information S-NSSAI, data network name DNN and protocol type; wherein the S-NSSAI is included in the allowed network slice selection assistance information Allowed NSSAI.
  • the baseband processor is further configured to receive a configuration update command sent by the core network device, where the configuration update command carries the first URSP and the second URSP, and the second URSP is the URSP updated by the first URSP; according to the Configure an update command to replace the first URSP in the URSP list with the second URSP.
  • the baseband processor establishes the PDU session according to the PDU session activation parameter, including: the baseband processor determines the established PDU session; if there is no PDU session established according to the PDU session activation parameter in the established PDU session, Then the baseband processor establishes a PDU session according to the PDU session activation parameter.
  • the baseband processor is a modem.
  • Embodiments of the present application further provide a chip system, the chip system includes a memory, an application processor and a baseband processor coupled to the memory, and the application processor and the baseband processor execute a computer program stored in the memory to achieve The method for establishing a PDU session is provided by the above embodiments.
  • Embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, wherein, when the computer program is executed by the application processor and the baseband processor, the PDU provided by the foregoing embodiment is implemented Session establishment method.
  • the computer-readable medium in this embodiment may at least include: any entity or device capable of carrying the computer program code to the terminal device, recording medium, computer memory, read-only memory (ROM, Read-Only Memory), random Access memory (RAM, Random Access Memory), electrical carrier signals, telecommunications signals, and software distribution media.
  • ROM read-only memory
  • RAM random Access memory
  • electrical carrier signals telecommunications signals
  • software distribution media For example, U disk, mobile hard disk, disk or CD, etc.
  • computer readable media may not be electrical carrier signals and telecommunications signals.
  • Embodiments of the present application further provide a computer program product, which, when the computer program product runs on a terminal device, enables the terminal device to execute the method for establishing a PDU session as provided in the foregoing embodiments.
  • the computer program includes computer program code
  • the computer program code may be in the form of source code, object code, executable file or some intermediate form.
  • references in this specification to "one embodiment” or “some embodiments” and the like mean that a particular feature, structure or characteristic described in connection with the embodiment is included in one or more embodiments of the present application.
  • appearances of the phrases “in one embodiment,” “in some embodiments,” “in other embodiments,” “in other embodiments,” etc. in various places in this specification are not necessarily All refer to the same embodiment, but mean “one or more but not all embodiments” unless specifically emphasized otherwise.
  • the terms “including”, “including”, “having” and their variants mean “including but not limited to” unless specifically emphasized otherwise.

Abstract

本申请涉及通信技术领域，提供了一种PDU会话建立方法、终端设备和芯片系统。该方法应用于终端设备，终端设备包括应用处理器和基带处理器，基带处理器中存储有URSP列表，URSP列表中包括至少一个URSP。该方法包括：应用处理器获取应用程序的第一数据包，给第一数据包添加应用程序的标识信息形成第二数据包，并将第二数据包发送给基带处理器。基带处理器在URSP列表中查找与标识信息对应的URSP，根据该URSP确定PDU会话激活参数，并根据PDU会话激活参数建立PDU会话，该PDU会话用于传输第二数据包。本实施例提供的PDU会话建立方法能够通过基带处理器进行URSP匹配选择并建立PDU会话，为应用程序与应用服务器提供数据传输通道。

Description

一种PDU会话建立方法、终端设备和芯片系统
本申请要求于2020年08月13日提交国家知识产权局、申请号为202010813681.9、申请名称为“一种PDU会话建立方法、终端设备和芯片系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种PDU会话建立方法、终端设备和芯片系统。
背景技术
第五代移动通信系统(简称5G通信系统)中包括多个网络切片(network slicing，NS)，各个网络切片可以同时对不同的应用程序提供不同的业务承载能力，从而提高5G通信系统的灵活性和业务适应性。
应用程序通常安装在终端设备上，由于应用程序与应用服务器之间的通信需要一条数据传输通道，并且5G通信系统支持协议数据单元(protocol data unit，PDU)连接业务。因此，可以在终端设备和网络切片之间建立一个PDU会话，作为应用程序与应用服务器之间的数据传输通道。
发明内容
本申请提供一种PDU会话建立方法、终端设备和芯片系统，以通过基带处理器进行URSP匹配选择并建立PDU会话，为应用程序与应用服务器提供数据传输通。
为达到上述目的，本申请采用如下技术方案：
第一方面，本申请实施例提供一种PDU会话建立方法，应用于终端设备，该终端设备包括应用处理器和基带处理器，该基带处理器中存储有URSP列表，URSP列表中包括至少一个URSP。该方法包括：
应用处理器，获取应用程序的第一数据包；以及，给第一数据包添加该应用程序的标识信息形成第二数据包；以及，将该第二数据包发送给该基带处理器。
基带处理器，在URSP列表中查找与该标识信息对应的URSP；以及，根据与该标识信息对应的URSP，确定PDU会话激活参数；以及，根据该PDU会话激活参数建立PDU会话，该PDU会话用于传输第二数据包。
应用程序向应用处理器发送的第一数据包，通常先经过应用处理器到达基带处理器，再由基带处理器发送给核心网设备，最后由核心网设备发送给应用服务器。由于应用程序发送第一数据包可能并不包括应用程序的标识信息，所以基带处理器可能无法根据其标识信息进行URSP匹配选择并建立PDU会话。
而在本实施例中，应用处理器先给应用程序的每一个第一数据包均添加应用程序的标识信息形成第二数据包之后，再将第二数据包发送给基带处理器。随后，基带处理器就能够获取到该应用程序的标识信息，根据该标识信息在URSP列表中确定对应的URSP，并根据该URSP建立PDU会话。因此，本实施例提供的PDU会话建立方法，可以通过基带 处理器进行URSP匹配选择并建立PDU会话，为应用程序与应用服务器提供数据传输通。
在一些实施例中，标识信息为应用标识App ID，或者用户账号标识UID。其中，App ID用于唯一标识该应用程序，UID用于唯一标识该应用程序的一个用户账号。
在一些实施例中，若标识信息为App ID，则基带处理器在URSP列表中查找与该标识信息对应的URSP，包括：基带处理器在URSP列表查找与App ID对应的URSP。
通过本实施例提供的PDU会话建立方法，基带处理器能够确定待传输的第二数据包的App ID，并根据该App ID进行URSP匹配选择并建立PDU会话，为应用程序与应用服务器提供数据传输通。
在一些实施例中，若标识信息为UID，则基带处理器在URSP列表中查找与标识信息对应的URSP，包括：基带处理器根据预设的对应关系表确定该UID对应的App ID，该对应关系表中包括UID和App ID的对应关系；以及，在URSP列表查找与该App ID对应的URSP。
通过本实施例提供的PDU会话建立方法，基带处理器能够确定待传输的第二数据包的UID，并根据该UID进行URSP匹配选择并建立PDU会话，为应用程序与应用服务器提供数据传输通。
在一些实施例中，应用处理器给第一数据包添加应用程序的标识信息形成第二数据包，包括：应用处理器在第一数据包的以太网首部或者以太网尾部未被占用的字段添加应用程序的标识信息，形成该第二数据包。
通过将标识信息添加在第一数据包的以太网首部或者以太网尾部中的未被占用的字段，避免了应用处理器给该第一数据包添加新的字段，有助于节约资源。
在一些实施例中，在应用处理器获取应用程序的第一数据包之前，该方法还包括：基带处理器向核心网设备发送注册请求；以及，接收核心网设备发送的注册受理消息，该注册受理消息携带核心网设备允许该终端设备使用的网络切片选择辅助信息Allowed NSSAI；以及，存储该Allowed NSSAI。
可以理解，基带处理器向核心网注册并将Allowed NSSAI存储在本地之后，在根据URSP确定PDU会话激活参数的过程中，基带处理器便能够根据Allowed NSSAI选择URSP中合法的S-NSSAI建立PDU会话。
在一些实施例中，在基带处理器存储该Allowed NSSAI之后，在应用处理器获取应用程序发送的第一数据包之前，该方法还包括：基带处理器接收核心网设备发送的终端设备管理命令，该命令中携带至少一个URSP；以及存储该至少一个URSP，形成URSP列表；以及，向核心网设备发送终端设备管理完成消息，该消息用于指示该基带处理器已处理该终端设备管理命令。
可以理解，基带处理器通过在本地存储URSP列表之后，才能在本地根据应用程序的标识信息基于该URSP列表执行URSP匹配策略，建立PDU会话。
在一些实施例中，PDU会话激活参数包括单个网络切片选择辅助信息S-NSSAI、数据网络名称DNN和协议类型；其中，该S-NSSAI包括在允许的网络切片选择辅助信息Allowed NSSAI中。
在一些实施例中，该方法还包括：基带处理器接收核心网设备发送的配置更新命令，该配置更新命令携带第一URSP和第二URSP，该第二URSP为第一URSP更新后的URSP； 以及，根据配置更新命令，将URSP列表中的第一URSP替换为第二URSP。
通过该方法可以更新URSP列表中无效的URSP，在一定程度上避免应用程序在运行过程中出现网络异常的情况。
在一些实施例中，基带处理器根据PDU会话激活参数建立PDU会话，包括：基带处理器确定已建立的PDU会话；若已建立的PDU会话中不存在根据PDU会话激活参数建立的PDU会话，则基带处理器根据PDU会话激活参数建立PDU会话。通过该方法可以在一定程度上避免基带处理根据同一PDU会话激活参数重复建立PDU会话，造成资源浪费的问题。
在一些实施例中，基带处理器为调制解调器。
第二方面，本申请实施例提供一种终端设备，该终端设备包括应用处理器和基带处理器，基带处理器中存储有终端设备路由选择策略URSP列表，该URSP列表中包括至少一个URSP。
应用处理器被配置为，获取应用程序的第一数据包；给第一数据包添加该应用程序的标识信息形成第二数据包；以及，将该第二数据包发送给该基带处理器。
基带处理器被配置为，在该URSP列表中查找与该标识信息对应的URSP；根据与该标识信息对应的URSP，确定PDU会话激活参数；以及，根据该PDU会话激活参数建立PDU会话，该PDU会话用于传输第二数据包。
在一些实施例中，标识信息为应用标识App ID，或者用户账号标识UID。
在一些实施例中，若标识信息为App ID，则基带处理器在URSP列表中查找与标识信息对应的URSP，包括：基带处理器在URSP列表查找与App ID对应的URSP。
在一些实施例中，若标识信息为UID，则基带处理器在URSP列表中查找与标识信息对应的URSP，包括：基带处理器根据预设的对应关系表确定UID对应的App ID，对应关系表中包括UID和App ID的对应关系；以及，在URSP列表查找与App ID对应的URSP。
在一些实施例中，应用处理器给第一数据包添加应用程序的标识信息形成第二数据包，具体包括：
应用处理器在第一数据包的以太网首部或者以太网尾部未被占用的字段添加该应用程序的标识信息，形成第二数据包。
在一些实施例中，在应用处理器获取应用程序的第一数据包之前，基带处理器还被配置为，向核心网设备发送注册请求；接收核心网设备发送的注册受理消息，该注册受理消息携带核心网设备允许该终端设备使用的网络切片选择辅助信息Allowed NSSAI；以及，存储该Allowed NSSAI。
在一些实施例中，在基带处理器存储Allowed NSSAI之后，在应用处理器获取应用程序发送的第一数据包之前，基带处理器还被配置为：接收核心网设备发送的终端设备管理命令，该命令中携带至少一个URSP；存储该至少一个URSP，形成URSP列表；以及，向核心网设备发送终端设备管理完成消息，该消息用于指示基带处理器已处理终端设备管理命令。
在一些实施例中，PDU会话激活参数包括单个网络切片选择辅助信息S-NSSAI、数据网络名称DNN和协议类型；其中，S-NSSAI包括在允许的网络切片选择辅助信息Allowed NSSAI中。
在一些实施例中，基带处理器还被配置为，接收核心网设备发送的配置更新命令，配置更新命令携带第一URSP和第二URSP，第二URSP为第一URSP更新后的URSP；以及，根据配置更新命令将URSP列表中的该第一URSP替换为第二URSP。
在一些实施例中，基带处理器根据PDU会话激活参数建立PDU会话，包括：基带处理器确定已建立的PDU会话；若已建立的PDU会话中不存在根据该PDU会话激活参数建立的PDU会话，则基带处理器根据该PDU会话激活参数建立PDU会话。
在一些实施例中，基带处理器为调制解调器。
第三方面，本申请实施例提供一种芯片系统，包括存储器，与存储器耦合的应用处理器和基带处理器，应用处理器和基带处理器执行存储器中存储的计算机程序，以实现如上述第一方面提供的PDU会话建立方法。
第四方面，本申请实施例提供一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序，该计算机程序被应用处理器和基带处理器执行时实现如上述第一方面提供的PDU会话建立方法。
第五方面，本申请实施例提供一种计算机程序产品，当该计算机程序产品在终端设备上运行时，使得该终端设备执行如上述第一方面提供的PDU会话建立方法。
可以理解的是，上述第二方面至第五方面的有益效果可以参见上述第一方面中的相关描述，在此不再赘述。
附图说明
图1为本申请实施例提供的5G通信系统架构的示意性框图；
图2为本申请实施例提供的网络切片的应用场景示意图；
图3为本申请实施例提供的终端设备的结构示意图；
图4为本申请的一个实施例提供的PDU会话建立的第一阶段的流程示意图；
图5为本申请的一个实施例提供的PDU会话建立的第二阶段的流程示意图；
图6为本申请实施例提供的URSP匹配策略的流程示意图；
图7为本申请的另一个实施例提供的PDU会话建立的第一阶段的流程示意图；
图8为本申请的另一个实施例提供的PDU会话的建立方法的流程示意图；
图9为本申请实施例提供的数据包的结构示意图。
图10为本申请的又一个实施例提供的PDU会话建立的第二阶段的流程示意图；
图11为本申请的其他一些实施例提供的PDU会话建立的第二阶段的流程示意图。
具体实施方式
本申请实施例提供一种PDU会话建立方法，该方法适用于5G通信系统、5G以上的通信系统、未来演进的公共陆地移动网络(public land mobile network，PLMN)以及后续支持第三代合作伙伴计划(3rd generation partnership project，3GPP)协议版本的通信系统，本申请实施例对此不进行限定。
下面以5G通信系统为例，对本申请实施例提供的PDU会话建立方法进行说明。
图1为本申请实施例提供的5G通信系统架构的示意性框图。参见图1所示，5G通信系统包括：终端设备110、接入网设备120、核心网设备130以及数据网络160(data network，DN)。
其中，终端设备110可以通过无线空口连接到运营商部署的接入网设备120，继而通 过核心网设备130连接到数据网络160。在本实施例中，终端设备110可以为用户设备(user equipment，UE)，例如智能手机、平板电脑、笔记本电脑、智能可穿戴设备、个人数字助理(personal digital assistant，PDA)等。
接入网设备120主要用于实现无线物理层功能、资源调度和无线资源管理、无线接入控制以及移动性管理等功能。在本实施例中，接入网设备可以为接入网(access network，AN)或者无线接入网(radio access network，RAN)设备。
核心网设备130包括管理设备140和网关设备150。其中，管理设备140可以包括接入与移动性管理功能(access&mobility function，AMF)、会话管理功能(session management function，SMF)、策略控制功能(policy control function，PCF)等功能单元。这些功能单元可以独立工作，也可以组合在一起实现某些控制功能。例如，AMF、SMF和PCF可以协同工作，完成终端设备的接入鉴权、安全加密、位置注册等接入控制和移动性管理功能，以及用户面传输路径的建立、释放和更改等会话管理功能，以及分析一些网络切片相关的数据、终端设备相关的数据的功能。网关设备150主要用于与终端设备间建立通道，在该通道上转发终端设备和外部数据网络之间的数据包。
数据网络160可对应于多种不同的业务域，例如IP多媒体子系统(IP multimedia subsystem，IMS)、互联网(Internet)、第三方应用相关的业务领域等，主要用于为终端设备提供多种数据业务服务，其中可以包含例如服务器(如第三方的应用服务器)、路由器、网关等网络设备。
需要说明的是，图1仅为5G通信系统的示例性架构图，除过图1中所示功能单元之外，5G通信系统的网络架构还可以包括其他功能单元或者功能实体，本实施例对此不进行限定。
5G通信系统中包括多个网络切片。其中，网络切片是在物理网络中，将相关的业务功能、网络资源和网络配置组合在一起而形成的一个逻辑网络，能够满足特定的业务需求(例如特定范围内的时延、抖动、丢包率、带宽等)。通过网络切片，5G通信系统可以对不同的应用程序(例如游戏应用程序、聊天应用程序等)同时提供不同的业务承载能力，从而提高5G网络架构的灵活性、业务适应性以及资源利用率。
应用厂商(即应用程序的提供厂商)通过与运营商签约网络切片业务，使得用户在运行该应用程序时能够通过网络切片与对应的应用服务器通信，提高该应用程序在终端设备中运行的流畅性，提高用户体验。具体地，应用厂商与运营商签约网络切片业务时，会与运营商协商确定一个服务质量规则(quality of service rules，Qos rules)。其中，Qos rules中约定了所签约的网络切片传输数据的带宽、时延、丢包率等基本参数。在Qos rules确定之后，运营商的核心网设备会生成一个终端设备路由选择策略(UE route selection policy，URSP)。
终端设备根据URSP为应用程序选择对应的网络切片，并建立与该网络切片的PDU会话，以便应用程序与应用服务器通信。其中，URSP包括流量描述符(traffic descriptor)和路由选择描述符(route selection descriptor)。
流量描述符用于描述终端设备传输的流量的特性，可以包括应用标识(application identification，App ID)、目标网际互联协议(internet protocol，IP)三元组、数据网络名称(data network name，DNN)、访问目标的全限定域名(fully qualified domain name，FQDN) 等参数中的任意一种。其中，App ID用于唯一标识一个应用程序，IP三元组包括目的IP地址、目的端口号以及协议类型。
路由选择描述符用于描述终端设备激活与网络切片的PDU会话所需的参数，可以包括网络切片选择辅助信息(network slice selection assistance information，NSSAI)、DNN、协议类型等参数。其中，NSSAI通常包括多个单个网络切片选择辅助信息(single-NSSAI，S-NSSAI)，S-NSSAI用于唯一标识一个单独的网络切片。此外，协议类型可以为传输控制协议(transmission control protocol，TCP)、用户数据报协议(user datagram protocol，UDP)等。
在一些实施例中，核心网设备可以根据终端设备与运营商的签约信息，将对应的URSP发送给终端设备。示例性的，用户可以通过运营商的营业大厅、拨打运营商客服电话等方式签约购买一个定向5G网络切片套餐。该套餐内的资源可以包含：100GB指定应用程序的多网络切片定向流量，这些指定应用程序可以包括应用程序A、应用程序B、应用程序C、应用程序D等。签约成功之后，或者终端设备在核心网设备注册成功之后，核心网设备便将该套餐范围内所有指定应用程序的相关URSP发送给签约手机号码对应的终端设备。示例性的，该相关的URSP可以包括应用程序A、应用程序B、应用程序C、应用程序D对应的URSP。
需要说明的是，每一个应用程序都可能有多个URSP。以应用程序A为例，例如表1所示，核心网发送的应用程序A的URSP包括URSP-A1、URSP-A2和URSP-A3。在应用程序A的各个URSP中，流量描述符通常是不同的，路由选择描述符可以相同，也可以不同。例如，URSP-A1、URSP-A2和URSP-A3的流量描述符可以分别为App ID、IP三元组和DNN，路由选择描述符可以依次为NSSAI1+DNN+TCP、NSSAI1+DNN+TCP和NSSAI2+DNN+TCP。其中，NSSAI可以是一个路由选择列表，在该路由选择列表中，按照优先级的不同依次记录了与流量描述符对应的多个S-NSSAI。示例性的，如表2所示，在NSSAI1对应的路由选择列表中，按照优先级由高到低的次序依次包括S-NSSAI1、S-NSSAI2、S-NSSAI3、S-NSSAI4和S-NSSAI5。
表1应用程序A的URSP
Figure PCTCN2021110029-appb-000001
表2路由选择列表
S-NSSAI1
S-NSSAI2
S-NSSAI3
S-NSSAI4
S-NSSAI5
图2为本申请实施例提供的网络切片的应用场景示意图。参见图2，终端设备中的应用程序可以根据URSP选择对应的网络切片，并连接到对应的应用服务器。终端设备中应用程序所使用的网络切片，是根据应用厂商与运营商签约的网络切片业务确定的。各个应用程序与网络切片之间的对应关系可以包括如下(1)～(3)所示：
(1)不同的应用程序可以通过不同的网络切片连接到不同的应用服务器。例如，参见图2，应用程序A可以使用第一网络切片连接到应用服务器A-1，应用程序B使用第三网络切片连接到应用服务器B。
(2)同一应用程序可以通过不同的网络切片连接到不同的应用服务器。例如，参见图2，应用程序A可以使用第一网络切片连接到应用服务器A-1，也可以使用第二网络切片连接到应用服务器A-2。
(3)不同应用程序可以通过同一网络切片连接到不同的应用服务器。例如，参见图2，应用程序C可以使用第四网络切片连接到应用服务器C。应用程序D可以使用第四网络切片连接到应用服务器D。
然而，终端设备只有在建立与网络切片之间的PDU会话之后，应用程序才能使用该PDU会话，通过网络切片与应用服务器通信。为此，本申请实施例提供一种PDU会话建立方法，用于建立终端设备与网络切片之间的PDU会话，提高数据传输速率，提高用户体验。
参见图3，本申请实施例所涉及的终端设备可以包括应用程序层(APP)、应用处理器(application processor，AP)和基带处理器(如调制解调器Modem)。其中，应用程序层可以包括一系列应用程序包，该应用程序包可以包括游戏应用、聊天应用，短信息，日历，相机，视频，导航，图库，通话等应用程序。应用处理器用于向应用程序层的各个应用程序提供应用编程接口(application programming interface，API)和编程框架。应用处理器可以包括一些预先定义的函数，例如用于接收应用程序框架层所发送的事件的函数。Modem用于收发其他设备(例如核心网设备)的消息，在发送端通过调制将数字信号转换为模拟信号，在接收端通过解调再将模拟信号转换为数字信号。
本实施例提供的PDU会话建立过程可以分两个阶段。第一阶段，终端设备在开机、更换客户识别模块(subscriber identity module，SIM)卡或者取消飞行模式等场景之后，向核心网设备注册。并且如果终端设备有被配置使用的网络切片，则核心网设备在终端设备注册成功之后，向终端设备发送URSP。第二阶段，终端设备根据不同的应用程序建立PDU会话。具体地，终端设备可以通过应用处理器执行URSP匹配策略，建立与网络切片的PDU会话；也可以通过调制解调器执行URSP匹配策略，建立与网络切片的PDU会话，具体如下所示。
下面结合图3所示的终端设备，对PDU会话建立的两个阶段进行介绍。
图4为本申请的一个实施例提供的PDU会话建立的第一阶段的流程示意图。参见图4，该方法具体包括如下步骤S401～S409。
S401，调制解调器向核心网设备发送注册请求。
示例性的，终端设备在开机、更换SIM卡或者取消飞行模式之后，调制解调器会自动向终端设备发送注册请求(Registration request)，从而向核心网设备发起注册流程。或者调制解调器在接收到应用处理器下发的命令之后，向核心网设备发送注册请求。
S402，核心网设备向调制解调器发送注册受理消息，该注册受理消息携带允许的网络切片选择辅助信息(Allowed NSSAI)。
核心网设备在接收到终端设备发送的注册请求之后，会向终端设备的调制解调器发送注册受理消息(Registration Accept)，该注册受理消息中携带Allowed NSSAI。其中，Allowed NSSAI为核心网设备允许该终端设备使用的NSSAI。
S403，调制解调器将Allowed NSSAI发送给应用处理器。
S404，应用处理器存储Allowed NSSAI。
可以理解，结合参见下文步骤S601-S609中示出的PDU会话激活参数的确定过程可知，应用处理器将Allowed NSSAI存储在本地之后，便能够在根据URSP确定PDU会话激活参数的过程中，根据Allowed NSSAI选择URSP中合法的S-NSSAI建立PDU会话。
通过上述步骤S401～S404，终端设备在核心网设备注册成功。在终端设备在核心网设备注册成功之后，示例性的，如果终端设备当前使用的手机号码签约了网络切片业务，或者某些应用厂商给该终端设备配置了其所提供的应用程序时的网络切片，则核心网设备继续执行后续步骤S405-S409，以便向该终端设备发送与上述网络切片业务对应的URSP。
S405，核心网设备向终端设备的调制解调器发送终端设备管理命令(Manage UE policy command)，该命令中携带至少一个URSP。
示例性的，若终端设备当前所使用的手机号码签约了上述本实施例提供的5G定向网络切片套餐，核心网设备可以通过下行非接入层传输通道(DL NAS Transport)将该套餐范围内所有指定应用程序的相关URSP发送给该终端设备。示例性的，该相关的URSP可以包括应用程序A、应用程序B、应用程序C、应用程序D对应的URSP。
S406，调制解调器将该至少一个URSP发送给应用处理器。
S407，应用处理器存储该至少一个URSP，形成URSP列表。
由于5G通信系统的运营商有多个，只有当终端设备所安装的SIM卡和所要使用的网络切片属于同一运营商时，终端设备才能使用该网络切片。因此，应用处理器在收到调制解调器发送的URSP码流之后，需要对URSP进行解码和合法性校验。其中，对URSP进行合法性校验是指将判断URSP携带的PLMN标识码，是否与终端设备当前通信的SIM卡的PLMN标识码相同。如果不相同，则说明该URSP合法，存储该URSP。如果不相同，则不存储该URSP。其中，PLMN标识码用于标识所属的运营商。
示例性的，基于终端设备当前所使用的手机号码签约了上述本实施例提供的5G定向网络切片套餐，该URSP列表可以如表3所示。该URSP列表中包括有核心网设备下发给终端设备的所有URSP，其中包括应用程序A、应用程序B、应用程序C以及应用程序D对应的URSP。在该URSP列表中，按照从上到下的顺序，各个URSP的优先级依次降低。
需要说明的是，在URSP列表中，至少包括一个默认网络切片的默认URSP(即Default URSP)。在该Default URSP中，其流量描述符为Match All，各个应用程序均可使用该默认网络切片。
表3URSP列表
URSP-A1
URSP-A2
URSP-A3
URSP-B1
URSP-B2
…
Default URSP
S408，应用处理器向调制解调器发送终端设备管理完成消息(Manage UE policy complete)。
应用处理器在存储URSP之后，向调制解调器发送终端设备管理完成消息。其中，终端设备管理完成消息用于通知核心网设备终端设备已响应终端设备管理命令。
S409，调制解调器向核心网设备发送终端设备管理完成消息。
具体地，调制解调器可以通过上行非接入层传输通道(UL NAS Transport)向核心网设备发送终端设备管理完成消息。
需要说明的是，在上述过程中，如果URSP校验不合法，则应用处理器删除该URSP，并且调制解调器通过UL NAS Transport向核心网设备发送终端设备管理拒绝消息(Manage UE policy reject)，用于通知核心网设备终端设备已拒绝终端设备管理命令。
此外，在一些实施例中，终端设备在核心网设备注册成功之后，其所签约的应用程序的URSP可能会发生变更，例如由第一URSP变更为第二URSP。若URSP发生变更，核心网设备则向终端设备发送配置更新命令(Configuration update command)，该配置更新命令可以携带第一URSP和第二URSP，用于指示应用处理器将URSP列表中的第一URSP替换为第二URSP。
下面基于步骤S401～S409示出的PDU会话建立的第一阶段的内容，对PDU会话的建立的第二阶段进行说明。
图5为本申请的一个实施例提供的PDU会话建立的第二阶段的流程示意图。在该方法中，终端设备的应用处理器执行URSP匹配策略，并控制建立与网络切片的PDU会话。该方法具体包括如下步骤S501～S506。
S501，应用处理器监听到应用程序到达前台运行。
应理解，在本实施例中，应用程序的运行包括前台运行和后台运行。
在一些实施例中，前台运行是指应用程序在终端设备运行过程中，用户当前可以操作控制该应用程序。而后台运行是指应用程序在终端设备运行过程中，用户无法操作控制该应用程序。
在另一些实施例中，应用程序前台运行可以是当前应用程序处于激活态activity态，而应用程序处于后台运行时，应用程序处于inactivity态。
S502，响应于应用程序到达前台运行，应用处理器获取该应用程序的数据包的标识信息。示例性的，该数据包的标识信息可以为App ID、IP三元组、DNN、FQDN等。
S503，应用处理器根据该标识信息和URSP匹配策略，在URSP列表中查找PDU会 话激活参数。
应用处理器在监听到应用程序到达前台运行之后，应用处理器可以根据URSP匹配策略(请参见下文所示的步骤S601-S609)，使用该标识信息匹配选择对应的URSP，并从该URSP中选择PDU会话激活参数，以便在后续步骤中根据该PDU会话激活参数激活对应的PDU会话。
S504，应用处理器根据PDU会话激活参数，向调制解调器发送PDU会话建立请求。
由于不同的应用程序可能会使用同一网络切片，所以该PDU会话激活参数对应的网络切片可能已经激活，即终端设备和该网络切片之间的PDU会话已建立。因此，在一种可能的实现方式中，应用处理器在根据该PDU会话激活参数，向调制解调器发送PDU会话建立请求之前，可以先判断该PDU会话激活参数对应的网络切片是否已经激活成功。如果已经激活成功，则无需再进行激活，避免重复操作。如果未激活成功，则根据该PDU会话激活参数，向调制解调器发送PDU会话建立请求，以激活该网络切片。需要说明的是，激活网络切片是指建立终端设备与网络切片的PDU会话。
其中，PDU会话建立请求(PDU session establishment request)携带PDU会话激活参数，以请求激活与该PDU会话激活参数对应的网络切片的PDU会话。例如，当该PDU会话激活参数是S-NSSAI1时，PDU会话建立请求用于请求激活与标识为S-NSSAI1的网络切片的PDU会话。
S505，调制解调器向核心网设备发送该PDU会话建立请求。
S506，核心网设备向调制解调器发送的PDU会话受理消息。
PDU会话受理消息(PDU session establishment accept)携带PDU会话激活参数，用于表示已激活与该PDU会话激活参数对应的网络切片的PDU会话。例如，当该PDU会话激活参数包括S-NSSAI1时，PDU会话受理消息用于表示S-NSSAI1对应的网络切片的PDU会话已激活。
S507，调制解调器向应用处理器发送的PDU会话受理消息。
通过上述步骤S501-S507，终端设备即可根据应用程序的数据包的标识信息，通过应用处理器执行URSP匹配策略，建立与网络切片的PDU会话。在PDU会话激活之后，应用处理器将包含该标识信息的数据包路由绑定在该PDU会话上。此后，包括该标识信息的数据包即可通过该PDU会话传输，实现应用程序与应用服务器之间通过网络切片通信。
图6为本申请实施例提供的URSP匹配策略的流程示意图，描述了上述步骤S503中根据数据包的标识信息和URSP匹配策略，在URSP列表中查找PDU会话激活参数的过程。该URSP匹配策略可以应用于应用处理器，也可以应用于调制解调器。具体包括如下步骤S601～S608。
S601，开始按照优先级遍历URSP列表。
S602，判断URSP列表中是否存在未访问的URSP。如果不存在未访问的URSP，则PDU激活参数选择失败。如果存在未访问的URSP，则执行下一步骤S603。
S603，根据标识信息匹配未访问的URSP中，优先级最高的URSP的流量描述符。示例性的，若未访问的URSP中，优先级最高的URSP是URSP-A1，其流量描述符包括App ID，则将该应用程序的App ID与该流量描述符进行匹配。
S604，判断流量描述符是否匹配成功。
具体地，如果该应用程序的App ID与当前访问的URSP的流量描述符不同，则流量描述符匹配失败，返回执行步骤S602。如果相同，则流量描述符匹配成功，则说明URSP选择成功，执行下一步骤S605。
S605，开始按照优先级遍历该URSP的路由选择列表(route selection list)。
S606，判断该路由选择列表中是否存在未访问的S-NSSAI。
具体地，如果该路由选择列表中存在未访问的S-NSSAI，则执行下一步骤S607。如果该路由选择列表中不存在未访问的S-NSSAI，则执行步骤S609。
S607，判断未访问的S-NSSAI中，优先级最高的S-NSSAI是否在Allowed NSSAI列表中。
具体地，如果未访问的S-NSSAI中，优先级最高的S-NSSAI不在Allowed NSSAI列表中，则返回执行步骤S606。如果该优先级最高的S-NSSAI在Allowed NSSAI列表中，则执行下一步骤S608。
S608，选择该S-NSSAI和当前访问的URSP中的其余路由信息作为PDU会话激活参数。
在本实施例中，其余路由信息是指路由选择描述符中除NSSAI之外的其余信息，例如DNN、协议类型等。示例性的，以网络切片的运营商时中国移动为例，其DNN为cmnet，其协议类型可以为TCP协议或者UDP协议等。
S609，选择当前访问的URSP中的其余路由选择描述符作为PDU会话激活参数。需要说明的是，由于终端设备没有选择到S-NSSAI，因此终端设备根据DNN、协议类型等信息使用默认网络切片。
通过上述步骤S601～S609，即可选择到与标识信息对应的PDU会话激活参数。
图7为本申请的另一个实施例提供的PDU会话建立的第一阶段的流程示意图。参见图7，该方法具体包括如下步骤S701～S706。
S701，调制解调器向核心网设备发送注册请求。
示例性的，终端设备开机、更换SIM卡或者取消飞行模式之后，调制解调器会自动向终端设备发送注册请求(Registration request)，从而向核心网设备发起注册流程。或者调制解调器接收到应用处理器下发的命令之后，向核心网设备发送注册请求。
S702，核心网设备向调制解调器发送注册受理消息，该消息携带Allowed NSSAI。
步骤S702的具体内容请参见S402，本实施例在此不再赘述。
S703，调制解调器存储Allowed NSSAI。
可以理解，结合参见上文步骤S601-S609中示出的PDU会话激活参数的确定过程可知，调制解调器将Allowed NSSAI存储在本地之后，在根据URSP确定PDU会话激活参数的过程中，便能够根据Allowed NSSAI选择URSP中合法的S-NSSAI建立PDU会话。
通过上述步骤S701～S703，终端设备即在核心网注册成功。
在终端设备在核心网设备注册成功之后，示例性的，如果终端设备当前使用的手机号码签约了网络切片业务，或者某些应用厂商给该终端设备配置了其所提供的应用程序时的网络切片，则核心网设备继续执行后续步骤S704-S706，以便向终端设备发送与上述网络切片业务对应的URSP。
S704，核心网设备向调制解调器发送终端设备管理命令，该命令中携带至少一个URSP。
在本实施例中，核心网可以通过下行非接入层传输通道(DL NAS Transport)发送终端设备管理命令，以传递相关的URSP给终端设备。
S705，调制解调器存储该至少一个URSP，形成URSP列表。
具体地，调制解调器在收到应用处理器下发的URSP码流之后，对URSP进行解码和合法性校验，并在校验合法之后存储URSP，形成URSP列表。其中，关于合法性校验的具体内容请参见步骤S407，本实施例在此不在赘述。
S706，调制解调器向核心网设备发送终端设备管理完成消息。
具体地，调制解调器可以通过上行非接入层传输通道(UL NAS Transport)向核心网设备发送终端设备管理完成消息。
可以理解，基带处理器通过在本地存储URSP列表之后，才能在本地根据应用程序的标识信息基于该URSP列表执行URSP匹配策略，建立PDU会话。
相比于步骤S401-S409示出的建立PDU会话的第一阶段的流程，步骤S701～S706示出的流程更加简单。在步骤S701～S706中，调制解调器在获取Allowed NSSAI、URSP等参数之后，直接将其存储在本地，而无需再将其转发给应用处理器，有助于提高注册和URSP的下发效率。
需要说明的是，在终端设备向核心网注册的过程中，如果URSP校验不合法，则调制解调器删除URSP，并向核心网设备发送终端设备管理拒绝消息。
此外，在一些实施例中，终端设备在核心网注册成功之后，其URSP可能会发生变更，例如由第一URSP变更为第二URSP。若URSP发生变更，核心网设备则向终端设备发送配置更新命令(Configuration update command)，该配置更新命令可以携带第一URSP和第二URSP，用于指示调制解调器将URSP列表中的第一URSP替换为第二URSP。
下面基于步骤S701-S706示出的PDU会话建立的第一阶段的内容，对PDU会话的建立的第二阶段进行说明。
图8为本申请的一个实施例提供的PDU会话的建立的第二阶段的流程示意图，描述了调制解调器侧执行URSP匹配策略，建立PDU会话的过程，具体包括如下步骤S801～S807。
S801，应用程序将第一数据包发送给应用处理器。
应用程序在运行过程中，通常会产生多个第一数据包，并将这些第一数据包发送给应用处理器。
S802，应用处理器在第一数据包中添加App ID，形成第二数据包。
应用处理器在接收到的每一个第一数据包中添加一个App ID，以标识该第一数据包所属的应用程序。
参见图9，终端设备的软件系统架构可以包括应用程序层、TCP层、IP层和物理层。在终端设备中，应用程序在运行过程中产生的用户数据可以依次经过应用程序层、TCP层、IP层和物理层传输给核心网设备。首先，应用程序层给用户数据添加应用头部形成应用数据，并将应用数据发送给TCP层。其次，TCP层给该应用数据添加TCP首部，形成TCP段。随后，IP层给TCP段添加IP首部，形成IP数据包。其中，IP数据包最大为1500字节。最后，物理层给IP数据包添加以太网(Ethernet)首部和以太网尾部，形成以太网帧。在本实施例中，应用处理器可以在该数据包的以太网首部或者尾部的无效字段中添加App ID。其中，该无效字段是指没有被占用的字段。
可以理解，应用处理器通过将标识信息添加在第一数据包的以太网首部或者以太网尾部中的无效字段，避免了给该第一数据包添加新的字段。
S803，应用处理器将第二数据包发送给调制解调器。
S804，调制解调器根据App ID和URSP匹配策略，在URSP列表中查找PDU会话激活参数。
步骤S804中根据App ID和URSP匹配策略，在URSP列表中查找PDU会话激活参数的具体内容，请参见步骤S601～S609，本实施例在此不再赘述。
S805，调制解调器根据PDU会话激活参数向核心网设备发送PDU会话建立请求(PDU session establishment request)。
由于终端设备中安装有不同的应用程序，这些应用程序可能会使用相同的网络切片，访问相同的服务器，因此，其可能会具有相同的PDU会话激活参数。因此，在本实施例中，调制解调器在根据PDU会话激活参数向终端设备发送PDU会话建立请求时，首先确定已建立的PDU会话是否存在根据该PDU会话激活参数建立的PDU会话。若不存在该PDU回话，则向核心网设备发送PDU会话建立请求，以建立PDU会话。若存在该PDU会话，则调制解调器不再重复根据该PDU会话激活参数建立PDU会话，并使用已建立的该PDU会话传输第二数据包。
其中，PDU会话建立请求携带PDU会话激活参数，以请求激活与该PDU会话激活参数对应的网络切片的PDU会话。例如，当该PDU会话激活参数包括S-NSSAI1时，PDU会话建立请求用于请求激活与标识为S-NSSAI1的网络切片的PDU会话。
S806，核心网设备向调制解调器发送PDU会话受理消息。
其中，PDU会话受理消息(PDU session establishment accept)携带PDU会话激活参数，用于表示已激活与该PDU会话激活参数对应的网络切片的PDU会话。例如，当该PDU会话激活参数包括S-NSSAI1时，该PDU会话受理消息用于表示S-NSSAI1对应的网络切片的PDU会话已激活。
在PDU会话激活之后，调制解调器将包含该App ID的数据包路由绑定在该PDU会话上。此后，包括该App ID的数据包即可通过该PDU会话传输，实现应用程序与应用服务器之间通过网络切片通信。
本领域技术人员可以理解，应用程序向应用处理器发送的第一数据包，通常先经过应用处理器到达调制解调器，再由调制解调器发送给核心网设备，最后由核心网设备发送给应用服务器。由于应用程序发送第一数据包可能并不包括应用程序的标识信息，所以调制解调器无法根据其标识信息进行URSP匹配选择并建立PDU会话。
而在本实施例中，应用处理器先给应用程序的每一个第一数据包均添加应用程序的标识信息，形成第二数据包之后，再将第二数据包发送给调制解调器。随后，调制解调器就能够获取到该应用程序的标识信息，根据该标识信息在URSP列表中确定对应的URSP，并根据该URSP建立PDU会话。因此，本实施例提供的PDU会话建立方法，可以通过调制解调器进行URSP匹配选择并建立PDU会话，为应用程序与应用服务器提供数据传输通。
图10为本申请的又一个实施例提供的PDU会话建立的第二阶段的流程示意图，描述了调制解调器执行URSP匹配策略，建立与网络切片的PDU会话的过程，包括如下步骤 S1001～S1007。
需要说明的是，在本实施例提供的PDU会话建立的第二阶段之前，终端设备也需要执行步骤S701～S706示出的PDU会话建立的第一阶段的流程，本实施在此不再赘述。此外，应用处理器还需要将各个应用程序的用户账号标识(User Identification，UID)与App ID的对应关系表发送给调制解调器进行存储，并由调制解调器转发送给核心网设备。其中，UID用于唯一标识应用程序的一个账户，其可以为该账户的注册手机号码、注册邮箱号码、注册身份证号码、应用服务器分配的账号标识(Identification，ID)等。
S1001，应用程序将第一数据包发送给应用处理器。
应用程序在运行过程中，通常会产生多个第一数据包，并将这些第一数据包发送给应用处理器。
S1002，应用处理器在第一数据包中添加UID，形成第二数据包。
在本实施例中，应用处理器在第一数据包中添加UID的方法，请参见步骤S802中应用处理器在第一数据包中添加App ID的方法，本实施例在此不再赘述。
S1003，应用处理器将第二数据包，发送给调制解调器。
S1004，调制解调器根据预设的对应关系表，确定该UID对应的App ID。
示例性的，UID与App ID的对应关系表可以如表4所示。示例性的，应用程序A的UID-A对应的App ID-A。应用程序B的UID-B对应的App ID-B。
表4对应关系表
UID App ID
UID-A App ID-A
UID-B App ID-B
UID-C App ID-C
UID-D App ID-D
… …
S1005，调制解调器根据App ID和URSP匹配策略，在URSP列表中查找PDU会话激活参数。
S1006，调制解调器根据该PDU会话激活参数向核心网设备发送PDU会话建立请求。
S1007，核心网设备向调制解调器发送PDU会话受理消息。
步骤S1005-S1007的内容请参见步骤S804-S806，本实施例在此不再赘述。
在本实施例中，终端设备使用UID即可通过调制解调器执行URSP匹配策略，建立与网络切片的PDU会话。在PDU会话激活之后，调制解调器将包含该UID的数据包路由绑定在该PDU会话上。此后，包括该UID的数据包即可通过该PDU会话传输，实现应用程序与应用服务器之间通过网络切片通信。
图11为本申请的其他一些实施例提供的PDU会话建立的第二阶段的流程示意图，描述了调制解调器根据IP三元组、FQND或者DNN，在调制解调器执行URSP匹配策略，并建立PDU会话的过程。该方法包括如下步骤S1101-S1105。
S1101，应用程序将数据包发送给应用处理器。
S1102，应用处理器将数据包发送给调制解调器。
S1103，调制解调器根据数据包的IP三元组、FQND、DNN中的任意一个以及URSP 匹配策略，在URSP列表中查找PDU会话激活参数。
其中，根据IP三元组、FQND、DNN中的任意一个，确定PDU会话激活参数的过程，请参见步骤S601-S608中示出的根据标识信息确定PDU会话激活参数的过程，本实施例在此不再赘述。
S1104，调制解调器根据该PDU会话激活参数向核心网设备发送PDU会话建立请求。
S1105，核心网设备向调制解调器发送PDU会话受理消息。
步骤S1104-S1105请参见步骤S805-S806，本实施例在此不再赘述。
在本实施例中，终端设备可以根据IP三元组、FQND或者DNN，通过调制解调器执行URSP匹配策略，建立与网络切片的PDU会话。在PDU会话激活之后，调制解调器将包含该IP三元组、FQND或者DNN的数据包路由绑定在该PDU会话上，实现应用程序与应用服务器之间通过网络切片通信。
应理解，上述实施例中各步骤的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
基于上述本实施例提供的PDU会话建立方法，本实施例还提供一种终端设备，该终端设备包括应用处理器和基带处理器，基带处理器中存储有终端设备路由选择策略URSP列表，该URSP列表中包括至少一个URSP。其中，应用处理器被配置为，获取应用程序的第一数据包；给第一数据包添加该应用程序的标识信息形成第二数据包；以及，将第二数据包发送给基带处理器。基带处理器被配置为，在URSP列表中查找与该标识信息对应的URSP；根据与标识信息对应的URSP，确定PDU会话激活参数；以及，根据PDU会话激活参数建立PDU会话，PDU会话用于传输第二数据包。
在一些实施例中，标识信息为应用标识App ID，或者用户账号标识UID。
在一些实施例中，若标识信息为App ID，则基带处理器在URSP列表中查找与标识信息对应的URSP，包括：基带处理器在URSP列表查找与App ID对应的URSP。
在一些实施例中，若标识信息为UID，则基带处理器在URSP列表中查找与标识信息对应的URSP，包括：基带处理器根据预设的对应关系表确定UID对应的App ID，对应关系表中包括UID和App ID的对应关系；以及，在URSP列表查找与App ID对应的URSP。
在一些实施例中，应用处理器给第一数据包添加该应用程序的标识信息形成第二数据包，具体包括：应用处理器在第一数据包的以太网首部或者以太网尾部未被占用的字段添加该应用程序的标识信息，形成第二数据包。
在一些实施例中，在应用处理器获取应用程序的第一数据包之前，基带处理器还被配置为，向核心网设备发送注册请求；接收核心网设备发送的注册受理消息，该注册受理消息携带核心网设备允许该终端设备使用的网络切片选择辅助信息Allowed NSSAI；以及，存储该Allowed NSSAI。
在一些实施例中，在基带处理器存储Allowed NSSAI之后，在应用处理器获取应用程序发送的第一数据包之前，基带处理器还被配置为：接收核心网设备发送的终端设备管理命令，该命令中携带URSP；存储该至少一个URSP，形成URSP列表；以及，向核心网设备发送终端设备管理完成消息，该消息用于指示基带处理器已处理终端设备管理命令。
在一些实施例中，PDU会话激活参数包括单个网络切片选择辅助信息S-NSSAI、数据网络名称DNN和协议类型；其中，该S-NSSAI包括在允许的网络切片选择辅助信息 Allowed NSSAI中。
在一些实施例中，基带处理器还被配置为，接收核心网设备发送的配置更新命令，配置更新命令携带第一URSP和第二URSP，第二URSP为第一URSP更新后的URSP；根据该配置更新命令，将URSP列表中的该第一URSP替换为第二URSP。
在一些实施例中，基带处理器根据PDU会话激活参数建立PDU会话，包括：基带处理器确定已建立的PDU会话；若已建立的PDU会话中不存在根据该PDU会话激活参数建立的PDU会话，则基带处理器根据该PDU会话激活参数建立PDU会话。
在一些实施例中，基带处理器为调制解调器。
本申请实施例还提供一种芯片系统，该芯片系统包括存储器，与该存储器耦合的应用处理器和基带处理器，该应用处理器和该基带处理器执行该存储器中存储的计算机程序，以实现如上述实施例提供的PDU会话建立方法。
本申请实施例还提供一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序，其特征在于，该计算机程序被应用处理器和基带处理器执行时实现如上述实施例提供的PDU会话建立方法。
应理解，本实施例中的计算机可读介质至少可以包括：能够将计算机程序代码携带到终端设备的任何实体或装置、记录介质、计算机存储器、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、电载波信号、电信信号以及软件分发介质。例如U盘、移动硬盘、磁碟或者光盘等。在某些司法管辖区，根据立法和专利实践，计算机可读介质不可以是电载波信号和电信信号。
本申请实施例还提供一种计算机程序产品，当该计算机程序产品在终端设备上运行时，使得该终端设备执行实现如上述实施例提供的PDU会话建立方法。其中，计算机程序包括计算机程序代码，计算机程序代码可以为源代码形式、对象代码形式、可执行文件或某些中间形式等。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的网络切片管理系统、应用服务器和终端设备的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
应理解，在本申请说明书和所附权利要求书的描述中，术语“第一”、“第二”、“第三”等仅用于区分描述，而不能理解为指示或暗示相对重要性。
在本申请说明书中描述的参考“一个实施例”或“一些实施例”等意味着在本申请的一个或多个实施例中包括结合该实施例描述的特定特征、结构或特点。由此，在本说明书中的不同之处出现的语句“在一个实施例中”、“在一些实施例中”、“在其他一些实施例中”、“在另外一些实施例中”等不是必然都参考相同的实施例，而是意味着“一个或多个但不是所有的实施例”，除非是以其他方式另外特别强调。术语“包括”、“包含”、“具有”及它们的变形都意味着“包括但不限于”，除非是以其他方式另外特别强调。
最后应说明的是：以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何在本申请揭露的技术范围内的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (25)

  1. 一种PDU会话建立方法，应用于终端设备，所述终端设备包括应用处理器和基带处理器，其特征在于，所述基带处理器中存储有终端设备路由选择策略URSP列表，所述URSP列表中包括至少一个URSP；所述方法包括：
    所述应用处理器，获取应用程序的第一数据包；以及，
    给所述第一数据包添加所述应用程序的标识信息形成第二数据包；以及，
    将所述第二数据包发送给所述基带处理器；
    所述基带处理器，在所述URSP列表中查找与所述标识信息对应的URSP；以及，
    根据与所述标识信息对应的URSP，确定协议数据单元PDU会话激活参数；以及，
    根据所述PDU会话激活参数建立PDU会话，所述PDU会话用于传输所述第二数据包。
  2. 根据权利要求1所述的方法，其特征在于，所述标识信息为应用标识App ID，或者用户账号标识UID。
  3. 根据权利要求2所述的方法，其特征在于，若所述标识信息为App ID，则所述基带处理器在所述URSP列表中查找与所述标识信息对应的URSP，包括：
    所述基带处理器在所述URSP列表查找与所述App ID对应的URSP。
  4. 根据权利要求2所述的方法，其特征在于，若所述标识信息为UID，则所述基带处理器在所述URSP列表中查找与所述标识信息对应的URSP，包括：
    所述基带处理器根据预设的对应关系表确定所述UID对应的App ID，所述对应关系表中包括UID和App ID的对应关系；以及，
    在所述URSP列表查找与所述App ID对应的URSP。
  5. 根据权利要求1-4任一项所述的方法，其特征在于，所述应用处理器给所述第一数据包添加所述应用程序的标识信息形成第二数据包，包括：
    所述应用处理器在所述第一数据包的以太网首部或者以太网尾部未被占用的字段添加所述标识信息，形成所述第二数据包。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，在所述应用处理器获取应用程序的第一数据包之前，所述方法还包括：
    所述基带处理器向核心网设备发送注册请求；以及，
    接收所述核心网设备发送的注册受理消息，所述注册受理消息携带核心网设备允许所述终端设备使用的网络切片选择辅助信息Allowed NSSAI；以及，
    存储所述Allowed NSSAI。
  7. 根据权利要求6所述的方法，其特征在于，在所述基带处理器存储所述Allowed NSSAI之后，在所述应用处理器获取应用程序发送的第一数据包之前，所述方法还包括：
    所述基带处理器接收所述核心网设备发送的终端设备管理命令，所述命令中携带所述至少一个URSP；以及，
    存储所述至少一个URSP，形成URSP列表；以及，
    向所述核心网设备发送终端设备管理完成消息，所述消息用于指示所述基带处理器已处理所述终端设备管理命令。
  8. 根据权利要求6或7所述的方法，其特征在于，所述PDU会话激活参数包括单个网 络切片选择辅助信息S-NSSAI、数据网络名称DNN和协议类型；其中，所述S-NSSAI包括在所述Allowed NSSAI中。
  9. 根据权利要求1-8任一项所述的方法，其特征在于，所述方法还包括：
    所述基带处理器接收核心网设备发送的配置更新命令，所述配置更新命令携带第一URSP和第二URSP，所述第二URSP为所述第一URSP更新后的URSP；以及，
    根据所述配置更新命令，将所述URSP列表中的所述第一URSP替换为所述第二URSP。
  10. 根据权利要求1-9任一项所述的方法，其特征在于，所述基带处理器根据所述PDU会话激活参数建立PDU会话，包括：
    若已建立的PDU会话中不存在根据所述PDU会话激活参数建立的PDU会话，则所述基带处理器根据所述PDU会话激活参数建立PDU会话。
  11. 根据权利要求1-10任一项所述的方法，其特征在于，所述基带处理器为调制解调器。
  12. 一种终端设备，所述终端设备包括应用处理器和基带处理器，其特征在于，所述基带处理器中存储有终端设备路由选择策略URSP列表，所述URSP列表中包括至少一个URSP；
    所述应用处理器被配置为，
    获取应用程序的第一数据包；
    给所述第一数据包添加所述应用程序的标识信息形成第二数据包；
    将所述第二数据包发送给所述基带处理器；
    所述基带处理器被配置为，
    在所述URSP列表中查找与所述标识信息对应的URSP；
    根据与所述标识信息对应的URSP，确定协议数据单元PDU会话激活参数；
    根据所述PDU会话激活参数建立PDU会话，所述PDU会话用于传输所述第二数据包。
  13. 根据权利要求12所述的终端设备，其特征在于，所述标识信息为应用标识App ID，或者用户账号标识UID。
  14. 根据权利要求13所述的终端设备，其特征在于，若所述标识信息为App ID，则所述基带处理器在所述URSP列表中查找与所述标识信息对应的URSP，包括：
    所述基带处理器在所述URSP列表查找与所述App ID对应的URSP。
  15. 根据权利要求13所述的终端设备，其特征在于，若所述标识信息为UID，则所述基带处理器在所述URSP列表中查找与所述标识信息对应的URSP，包括：
    所述基带处理器根据预设的对应关系表确定所述UID对应的App ID，所述对应关系表中包括UID和App ID的对应关系；以及，
    在所述URSP列表查找与所述App ID对应的URSP。
  16. 根据权利要求12-15任一项所述的终端设备，其特征在于，所述应用处理器给所述第一数据包添加所述应用程序的标识信息形成第二数据包，具体包括：
    所述应用处理器在所述第一数据包的以太网首部或者以太网尾部未被占用的字段添加所述标识信息，形成所述第二数据包。
  17. 根据权利要求12-16任一项所述的终端设备，其特征在于，在所述应用处理器获取 应用程序的第一数据包之前，所述基带处理器还被配置为，
    向核心网设备发送注册请求；
    接收所述核心网设备发送的注册受理消息，所述注册受理消息携带核心网设备允许所述终端设备使用的网络切片选择辅助信息Allowed NSSAI；
    存储所述Allowed NSSAI。
  18. 根据权利要求17所述的终端设备，其特征在于，在所述基带处理器存储所述Allowed NSSAI之后，在所述应用处理器获取应用程序发送的第一数据包之前，所述基带处理器还被配置为：
    接收所述核心网设备发送的终端设备管理命令，所述命令中携带所述至少一个URSP；
    存储所述至少一个URSP，形成URSP列表；
    向所述核心网设备发送终端设备管理完成消息，所述消息用于指示所述基带处理器已处理所述终端设备管理命令。
  19. 根据权利要求17或18所述的终端设备，其特征在于，所述PDU会话激活参数包括单个网络切片选择辅助信息S-NSSAI、数据网络名称DNN和协议类型；
    其中，所述S-NSSAI包括在所述Allowed NSSAI中。
  20. 根据权利要求12-19任一项所述的终端设备，其特征在于，所述基带处理器还被配置为，
    接收核心网设备发送的配置更新命令，所述配置更新命令携带第一URSP和第二URSP，所述第二URSP为所述第一URSP更新后的URSP；
    根据所述配置更新命令，将所述URSP列表中的所述第一URSP替换为所述第二URSP。
  21. 根据权利要求12-20任一项所述的终端设备，其特征在于，所述基带处理器根据所述PDU会话激活参数建立PDU会话，包括：
    若已建立的PDU会话中不存在根据所述PDU会话激活参数建立的PDU会话，则所述基带处理器根据所述PDU会话激活参数建立所述PDU会话。
  22. 根据权利要求12-21任一项所述的终端设备，其特征在于，所述基带处理器为调制解调器。
  23. 一种芯片系统，其特征在于，所述芯片系统包括存储器，与所述存储器耦合的应用处理器和基带处理器，所述应用处理器和所述基带处理器执行所述存储器中存储的计算机程序，以实现如权利要求1至11任一项中的协议数据单元PDU会话建立方法。
  24. 一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，其特征在于，所述计算机程序被应用处理器和基带处理器执行时实现如权利要求1至11任一项中的协议数据单元PDU会话建立方法。
  25. 一种计算机程序产品，其特征在于，当所述计算机程序产品在终端设备上运行时，使得所述终端设备执行如权利要求1至11任一项中的协议数据单元PDU会话建立方法。
PCT/CN2021/110029 2020-08-13 2021-08-02 一种pdu会话建立方法、终端设备和芯片系统 WO2022033345A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP21855398.0A EP4192184A4 (en) 2020-08-13 2021-08-02 PDU SESSION SETUP METHOD, TERMINAL DEVICE AND CHIP SYSTEM

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010813681.9A CN114080054A (zh) 2020-08-13 2020-08-13 一种pdu会话建立方法、终端设备和芯片系统
CN202010813681.9 2020-08-13

Publications (1)

Publication Number Publication Date
WO2022033345A1 true WO2022033345A1 (zh) 2022-02-17

Family

ID=80247710

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/110029 WO2022033345A1 (zh) 2020-08-13 2021-08-02 一种pdu会话建立方法、终端设备和芯片系统

Country Status (3)

Country Link
EP (1) EP4192184A4 (zh)
CN (1) CN114080054A (zh)
WO (1) WO2022033345A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114978911A (zh) * 2022-05-20 2022-08-30 中国联合网络通信集团有限公司 网络切片的关联方法、设备主体、通信模组及终端设备
CN116723587A (zh) * 2023-08-07 2023-09-08 荣耀终端有限公司 一种会话管理方法及电子设备

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116866942A (zh) * 2022-03-28 2023-10-10 维沃移动通信有限公司 Ursp规则优化方法、装置、终端、网络侧设备及介质
CN114980364A (zh) * 2022-04-18 2022-08-30 成都鼎桥通信技术有限公司 基于ursp规则的本地局域网通信方法、装置及介质
CN114845355A (zh) * 2022-04-29 2022-08-02 中国电信股份有限公司 网络接入方法及装置、终端设备、网络设备、存储介质
CN114915996A (zh) * 2022-05-16 2022-08-16 Oppo广东移动通信有限公司 通信异常处理方法及相关装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109548175A (zh) * 2017-08-15 2019-03-29 华为技术有限公司 一种会话处理方法及装置
US20200092380A1 (en) * 2018-09-17 2020-03-19 Samsung Electronics Co., Ltd. Packet data unit (pdu) session control method and apparatus
CN111034268A (zh) * 2018-08-10 2020-04-17 联发科技股份有限公司 增强型用户设备路径选择策略规则匹配
CN111314475A (zh) * 2020-02-21 2020-06-19 北京紫光展锐通信技术有限公司 会话创建方法及相关设备

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109922472B (zh) * 2017-12-13 2021-10-26 华为技术有限公司 用户策略的获取
CN110149670A (zh) * 2018-02-13 2019-08-20 华为技术有限公司 一种数据路由选择的方法及装置
CN110474840B (zh) * 2018-05-09 2022-05-10 华为技术有限公司 数据传输方法、装置和可读存储介质
CN110602761B (zh) * 2018-06-13 2020-12-08 华为技术有限公司 一种数据传输方法及装置
CN111988828B (zh) * 2018-11-23 2021-08-10 腾讯科技（深圳）有限公司 路由选择策略的获取方法、装置及设备
US10602422B1 (en) * 2018-12-10 2020-03-24 Verizon Patent And Licensing Inc. Application-based user equipment route selection policy mapping

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109548175A (zh) * 2017-08-15 2019-03-29 华为技术有限公司 一种会话处理方法及装置
CN111034268A (zh) * 2018-08-10 2020-04-17 联发科技股份有限公司 增强型用户设备路径选择策略规则匹配
US20200092380A1 (en) * 2018-09-17 2020-03-19 Samsung Electronics Co., Ltd. Packet data unit (pdu) session control method and apparatus
CN111314475A (zh) * 2020-02-21 2020-06-19 北京紫光展锐通信技术有限公司 会话创建方法及相关设备

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INC.: "TS 23.501: Handling of PDU sessions at slice unavailability", SA WG2 MEETING #121 S2-173923, 19 May 2017 (2017-05-19), XP051289400 *
QUALCOMM INC.: "TS 23.501: Handling of PDU sessions at slice unavailability", SA WG2 MEETING #121 S2-174018, 19 May 2017 (2017-05-19), XP051289485 *
See also references of EP4192184A4

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114978911A (zh) * 2022-05-20 2022-08-30 中国联合网络通信集团有限公司 网络切片的关联方法、设备主体、通信模组及终端设备
CN114978911B (zh) * 2022-05-20 2024-03-08 中国联合网络通信集团有限公司 网络切片的关联方法、设备主体、通信模组及终端设备
CN116723587A (zh) * 2023-08-07 2023-09-08 荣耀终端有限公司 一种会话管理方法及电子设备
CN116723587B (zh) * 2023-08-07 2023-11-21 荣耀终端有限公司 一种会话管理方法及电子设备

Also Published As

Publication number Publication date
EP4192184A1 (en) 2023-06-07
CN114080054A (zh) 2022-02-22
EP4192184A4 (en) 2024-01-24

Similar Documents

Publication Publication Date Title
WO2022033345A1 (zh) 一种pdu会话建立方法、终端设备和芯片系统
CN109842906B (zh) 一种通信的方法、装置及系统
US11671373B2 (en) Systems and methods for supporting traffic steering through a service function chain
US11470657B2 (en) Method, user equipment, and network node for performing PDU session establishment procedure for LADN
US20210282203A1 (en) Establishing a Session or Cellular Internet of Things Packet Transmission
US11917498B2 (en) Communication method and communications apparatus
WO2022206260A1 (zh) 地址信息发送方法、获取方法、装置、设备及介质
US20200059761A1 (en) Systems and methods for enabling private communication within a user equipment group
WO2018006784A1 (zh) 一种网络切片选择方法、设备及系统
CN111698725A (zh) 动态确定网络切片的方法及电子设备
KR20210005279A (ko) 세션 관리 방법, 장치 및 시스템
US11729137B2 (en) Method and device for edge application server discovery
US10820231B2 (en) Systems and methods for APN based CoS and QoS control for network services
WO2020224559A1 (zh) 群组管理方法、装置及系统
CN114365518B (zh) 一种通过服务应用影响核心网络中数据业务路由的方法
CN114651477A (zh) 用于用户面处理的系统和方法
KR20230007473A (ko) 슬라이스 액세스 방법, 디바이스 및 시스템
US10716159B2 (en) Method and user equipment for connecting by means of plurality of accesses in next generation network
US20200228618A1 (en) Content delivery method, device, and system
WO2022021971A1 (zh) 通信方法、第一策略控制网元及通信系统
WO2022033346A1 (zh) 网络切片管理系统、应用服务器和终端设备
WO2022099484A1 (zh) 标识发送方法和通信装置
CN113709677A (zh) 加入组播广播业务mbs会话的方法及装置
WO2023056784A1 (zh) 数据收集方法、通信装置及通信系统
WO2024061205A1 (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: 21855398

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021855398

Country of ref document: EP

Effective date: 20230301