CN114080054A

CN114080054A - PDU session establishment method, terminal equipment and chip system

Info

Publication number: CN114080054A
Application number: CN202010813681.9A
Authority: CN
Inventors: 刘彬俊; 于晓靓; 樊宇伟; 连海
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-08-13
Filing date: 2020-08-13
Publication date: 2022-02-22
Also published as: EP4192184A4; WO2022033345A1; EP4192184A1

Abstract

The application relates to the technical field of communication, and provides a PDU session establishment method, terminal equipment and a chip system. The method is applied to terminal equipment, the terminal equipment comprises an application processor and a baseband processor, a URSP list is stored in the baseband processor, and the URSP list comprises at least one URSP. The method comprises the following steps: the application processor acquires a first data packet of an application program, adds identification information of the application program to the first data packet to form a second data packet, and sends the second data packet to the baseband processor. And the baseband processor searches the URSP corresponding to the identification information in the URSP list, determines a PDU session activation parameter according to the URSP, and establishes a PDU session according to the PDU session activation parameter, wherein the PDU session is used for transmitting a second data packet. The PDU session establishment method provided by this embodiment can perform URSP matching selection and establish a PDU session through the baseband processor, and provide a data transmission channel for an application program and an application server.

Description

PDU session establishment method, terminal equipment and chip system

Technical Field

The present application relates to the field of communications technologies, and in particular, to a PDU session establishment method, a terminal device, and a chip system.

Background

A fifth generation mobile communication system (5G communication system for short) includes multiple Network Slices (NS), and each network slice can provide different service carrying capabilities for different applications at the same time, thereby improving the flexibility and service adaptability of the 5G communication system.

The application is usually installed on the terminal device, since a data transmission channel is required for communication between the application and the application server, and the 5G communication system supports Protocol Data Unit (PDU) connection services. Thus, 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.

Disclosure of Invention

The application provides a PDU session establishing method, terminal equipment and a chip system, which are used for carrying out URSP matching selection and establishing a PDU session through a baseband processor and providing data transmission communication for an application program and an application server.

In order to achieve the purpose, the technical scheme is as follows:

in a first aspect, an embodiment of the present application provides a PDU session establishment method, which is applied to a terminal device, where the terminal device includes an application processor and a baseband processor, where a URSP list is stored in the baseband processor, and the URSP list includes at least one URSP. The method comprises the following steps:

the application processor is used for acquiring a first data packet of an application program; adding identification information of the application program to the first data packet to form a second data packet; and sending the second data packet to the baseband processor.

The baseband processor searches the URSP corresponding to the identification information in the URSP list; determining PDU session activation parameters according to the URSP corresponding to the identification information; and establishing a PDU session according to the PDU session activation parameter, wherein the PDU session is used for transmitting a second data packet.

The first data packet sent by the application program to the application processor usually reaches the baseband processor through the application processor, and then is sent to the core network device by the baseband processor, and finally is sent to the application server by the core network device. Since the application sending the first packet may not include the application's identification information, the baseband processor may not be able to make a URSP match selection and establish a PDU session based on its identification information.

In this embodiment, the application processor first adds the identification information of the application program to each first data packet of the application program 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 program, determine a corresponding URSP in the URSP list according to the identification information, and establish a PDU session according to the URSP. Therefore, the PDU session establishment method provided in this embodiment may perform URSP matching selection and establish a PDU session through the baseband processor, so as to provide data transmission communication between the application program and the application server.

In some embodiments, 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, and the UID is used to uniquely identify a user account of the application.

In some embodiments, if the identification information is App ID, the baseband processor searches for a URSP corresponding to the identification information in a URSP list, including: the baseband processor looks up the URSP corresponding to the App ID in the URSP list.

By the PDU session establishment method provided in this embodiment, the baseband processor can determine the App ID of the second data packet to be transmitted, and perform URSP matching selection and establish a PDU session according to the App ID, so as to provide data transmission communication between the application program and the application server.

In some embodiments, if the identification information is the UID, the baseband processor searches the URSP list for the URSP corresponding to the identification information, including: the baseband processor determines an App ID corresponding to the UID according to a preset corresponding relation table, wherein the corresponding relation table comprises the corresponding relation between the UID and the App ID; and searching the URSP corresponding to the App ID in the URSP list.

By the method for establishing the PDU session provided by this embodiment, the baseband processor can determine the UID of the second data packet to be transmitted, and perform URSP matching selection and establish the PDU session according to the UID, so as to provide data transmission communication between the application program and the application server.

In some embodiments, the application processor adding the identification information of the application program to the first data packet to form a second data packet, including: and the application processor adds identification information of the application program in an unoccupied field of the Ethernet head or the Ethernet tail of the first data packet to form the second data packet.

By adding the identification information to the unoccupied field in the ethernet header or the ethernet trailer of the first packet, the application processor is prevented from adding a new field to the first packet, which helps to save resources.

In some embodiments, before the application processor obtains the first data packet of the application program, the method further comprises: the baseband processor sends a registration request to the core network equipment; receiving a registration acceptance message sent by the core network equipment, wherein the registration acceptance message carries network slice selection auxiliary information Allowed by the core network equipment to be used by the terminal equipment; and storing the Allowed NSSAI.

It will be appreciated that after the baseband processor registers with the core network and stores the Allowed NSSAI locally, the baseband processor can select the legitimate S-NSSAI in the URSP to establish the PDU session based on the Allowed NSSAI in determining the PDU session activation parameters based on the URSP.

In some embodiments, after the baseband processor stores the Allowed NSSAI, before the application processor obtains the first packet sent by the application program, the method further comprises: a baseband processor receives a terminal equipment management command sent by core network equipment, wherein the command carries at least one URSP; and storing the at least one URSP to form a URSP list; and sending a terminal device management completion message to the core network device, wherein the message is used for indicating that the baseband processor has processed the terminal device management command.

It will be appreciated that the baseband processor can establish a PDU session by locally storing the list of URSPs before executing the URSP matching policy locally based on the list of URSPs based on the identification information of the application.

In some embodiments, 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.

In some embodiments, the method further comprises: the method comprises the steps that a baseband processor receives a configuration updating command sent by core network equipment, the configuration updating command carries a first URSP and a second URSP, and the second URSP is a URSP updated by the first URSP; and replacing the first URSP in the list of URSPs with the second URSP according to the configuration update command.

By the method, invalid URSPs in the URSP list can be updated, and the situation of network abnormality during the running process of the application program is avoided to a certain extent.

In some embodiments, the baseband processor establishes the PDU session according to the PDU session activation parameter, including: the baseband processor determines an established PDU session; and if the PDU session established according to the PDU session activation parameter does not exist in the established PDU session, 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 repeatedly establishing the PDU session according to the same PDU session activation parameter by the baseband processing to a certain extent.

In some embodiments, the baseband processor is a modem.

In a second aspect, an embodiment of the present application provides a terminal device, where the terminal device includes an application processor and a baseband processor, where a URSP list of a routing policy of the terminal device is stored in the baseband processor, and the URSP list includes at least one URSP.

The application processor is configured to obtain a first data packet of an application program; adding identification information of the application program to the first data packet to form a second data packet; and sending the second data packet to the baseband processor.

The baseband processor is configured to look up a URSP corresponding to the identification information in the URSP list; determining PDU session activation parameters according to the URSP corresponding to the identification information; and establishing a PDU session according to the PDU session activation parameter, wherein the PDU session is used for transmitting a second data packet.

In some embodiments, the identification information is an application identification App ID, or a user account identification UID.

In some embodiments, if the identification information is App ID, the baseband processor finds a URSP corresponding to the identification information in the URSP list, including: the baseband processor looks up the URSP corresponding to the App ID in the URSP list.

In some embodiments, if the identification information is the UID, the baseband processor searches the URSP list for the URSP corresponding to the identification information, including: the baseband processor determines an App ID corresponding to the UID according to a preset corresponding relation table, wherein the corresponding relation table comprises the corresponding relation between the UID and the App ID; and looking up the URSP corresponding to the App ID in the URSP list.

In some embodiments, the adding, by the application processor, the identification information of the application program to the first data packet to form a second data packet specifically includes:

and the application processor adds the identification information of the application program in an unoccupied field at the head part or the tail part of the Ethernet of the first data packet to form a second data packet.

In some embodiments, prior to the application processor obtaining the first data packet of the application program, the baseband processor is further configured to send a registration request to the core network device; receiving a registration acceptance message sent by core network equipment, wherein the registration acceptance message carries network slice selection auxiliary information Allowed by the core network equipment to be used by the terminal equipment; and storing the Allowed NSSAI.

In some embodiments, after the baseband processor stores the Allowed NSSAI, before the application processor retrieves the first data packet transmitted by the application program, the baseband processor is further configured to: receiving a terminal equipment management command sent by core network equipment, wherein the command carries at least one URSP; storing the at least one URSP to form a URSP list; and sending a terminal device management completion message to the core network device, wherein the message is used for indicating that the baseband processor has processed the terminal device management command.

In some embodiments, 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 replacing the first URSP in the list of URSPs with a second URSP according to the configuration update command.

In some embodiments, the baseband processor establishes the PDU session according to the PDU session activation parameter, including: the baseband processor determines an established PDU session; and if the PDU session established according to the PDU session activation parameter does not exist in the established PDU session, the baseband processor establishes the PDU session according to the PDU session activation parameter.

In some embodiments, the baseband processor is a modem.

In a third aspect, an embodiment of the present application provides a chip system, which includes a memory, and an application processor and a baseband processor coupled to the memory, where the application processor and the baseband processor execute a computer program stored in the memory to implement the PDU session establishment method as provided in the first aspect.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, where a computer program is stored, and when executed by an application processor and a baseband processor, the computer program implements the PDU session establishment method provided in the first aspect.

In a fifth aspect, an embodiment of the present application provides a computer program product, which, when running on a terminal device, causes the terminal device to execute the PDU session establishment method as provided in the first aspect.

It is understood that the beneficial effects of the second aspect to the fifth aspect can be referred to the related description of the first aspect, and are not described herein again.

Drawings

Fig. 1 is a schematic block diagram of a 5G communication system architecture provided in an embodiment of the present application;

fig. 2 is a schematic view of an application scenario of a network slice according to an embodiment of the present application;

fig. 3 is a schematic structural diagram of a terminal device according to an embodiment of the present application;

fig. 4 is a flowchart illustrating a first phase of PDU session establishment according to an embodiment of the present application;

fig. 5 is a flowchart illustrating a second phase of PDU session establishment according to an embodiment of the present application;

fig. 6 is a schematic flowchart of a URSP matching policy provided in an embodiment of the present application;

fig. 7 is a flowchart illustrating a first phase of PDU session establishment according to another embodiment of the present application;

fig. 8 is a flowchart illustrating a PDU session establishment method according to another embodiment of the present application;

fig. 9 is a schematic structural diagram of a data packet according to an embodiment of the present application.

Fig. 10 is a flowchart illustrating a second phase of PDU session establishment according to another embodiment of the present application;

fig. 11 is a flowchart illustrating a second phase of PDU session establishment according to some other embodiments of the present application.

Detailed Description

The embodiment of the present application provides a PDU session establishment method, which is applicable to a 5G communication system, a communication system over 5G, a Public Land Mobile Network (PLMN) for future evolution, and a communication system supporting a 3rd generation partnership project (3 GPP) protocol version in the following, and the present application is not limited thereto.

The following takes a 5G communication system as an example to describe a PDU session establishment method provided in the embodiments of the present application.

Fig. 1 is a schematic block diagram of a 5G communication system architecture provided in an embodiment of the present application. Referring to fig. 1, the 5G communication system includes: terminal device 110, access network device 120, core network device 130, and data network 160 (DN).

Terminal device 110 may connect to access network device 120 deployed by an operator through a wireless air interface, and then connect to data network 160 through core network device 130. In this embodiment, the terminal device 110 may be a User Equipment (UE), such as a smart phone, a tablet, a notebook, a smart wearable device, a Personal Digital Assistant (PDA), and the like.

The access network device 120 is mainly used to implement functions such as a wireless physical layer function, resource scheduling and wireless resource management, wireless access control, and mobility management. In this embodiment, the access network device may be AN Access Network (AN) or a 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 (AMF), a Session Management Function (SMF), a Policy Control Function (PCF), and the like. These functional units may operate independently or may be combined to perform certain control functions. For example, the AMF, the SMF, and the PCF may work cooperatively to perform access control and mobility management functions such as access authentication, security encryption, location registration, etc. of the terminal device, session management functions such as establishment, release, and modification of a user plane transmission path, and functions 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 a data packet between the terminal device and an external data network on the channel.

The data network 160 may correspond to a plurality of different service domains, such as an IP Multimedia Subsystem (IMS), the Internet (Internet), a third party application related service domain, and the like, and is mainly used for providing a plurality of data service services for the terminal device, wherein the data service services may include network devices such as a server (e.g., an application server of a third party), a router, a gateway, and the like.

It should be noted that fig. 1 is only an exemplary architecture diagram of the 5G communication system, and besides the functional units shown in fig. 1, the network architecture of the 5G communication system may further include other functional units or functional entities, which is not limited in this embodiment.

The 5G communication system includes a plurality of network slices. The network slice is a logical network formed by combining related service functions, network resources and network configurations in a physical network, and can meet specific service requirements (such as time delay, jitter, packet loss rate, bandwidth and the like in a specific range). Through network slicing, the 5G communication system can provide different service carrying capabilities for different applications (e.g., game applications, chat applications, etc.) at the same time, thereby improving the flexibility, service adaptability, and resource utilization rate of the 5G network architecture.

An application manufacturer (namely an application program provider) signs a network slicing service with an operator, so that a user can communicate with a corresponding application server through a network slice when the application program is operated, the smoothness of the operation of the application program in terminal equipment is improved, and the user experience is improved. Specifically, when the application vendor signs up for the network slice service with the operator, the application vendor negotiates with the operator to determine a quality of service (Qos) rule. The Qos rules stipulate basic parameters such as bandwidth, delay, packet loss rate, and the like of the subscribed network slice transmission data. After the Qos rules are determined, the core network device of the operator generates a terminal device routing policy (URSP).

And the terminal equipment selects a corresponding network slice for the application program according to the URSP, and establishes a PDU session with the network slice so that the application program can communicate with the application server. Wherein, the URSP includes a traffic descriptor (traffic descriptor) and a route selection descriptor (route selection descriptor).

The traffic descriptor is used for describing characteristics of traffic transmitted by the terminal device, and may include any one of parameters such as an application identification (App ID), a target Internet Protocol (IP) triple, a Data Network Name (DNN), a Fully Qualified Domain Name (FQDN) of an access target, and the like. The App ID is used for uniquely identifying one application program, and the IP triple comprises a destination IP address, a destination port number and a protocol type.

The routing descriptor is used to describe parameters required by the terminal device to activate a PDU session with a network slice, and may include parameters such as Network Slice Selection Assistance Information (NSSAI), DNN, and protocol type. Wherein NSSAI typically includes a plurality of individual network slice selection assistance information (S-NSSAI) that uniquely identifies an individual network slice. In addition, the protocol type may be Transmission Control Protocol (TCP), User Datagram Protocol (UDP), or the like.

In some embodiments, the core network device may send the corresponding URSP to the terminal device according to the subscription information of the terminal device and the operator. For example, a user may sign up to purchase a directed 5G network slice package through a business hall of the carrier, by dialing a customer service phone of the carrier, or the like. The resources within the package may include: the 100GB specifies multi-network slice directed traffic for applications, which may include application a, application B, application C, application D, and so on. After the subscription is successful, or after the terminal device is successfully registered in the core network device, the core network device sends the relevant URSPs of all the specified applications in the package range to the terminal device corresponding to the subscription mobile phone number. Illustratively, the relevant URSPs may include URSPs corresponding to application a, application B, application C, and application D.

It should be noted that there may be multiple URSPs per application. Taking application a as an example, for example, as shown in table 1, the URSPs of application a sent by the core network include URSP-a1, URSP-a2, and URSP-A3. The traffic descriptors are usually different in each URSP of application a, and the routing descriptors may be the same or different. For example, the traffic descriptors of URSP-A1, URSP-A2, and URSP-A3 may be App ID, IP triplet, and DNN, respectively, and the routing descriptors may be NSSAI1+ DNN + TCP, NSSAI1+ DNN + TCP, and NSSAI2+ DNN + TCP, in that order. The NSSAI may be a routing list in which a plurality of S-NSSAIs corresponding to traffic descriptors are sequentially recorded according to different priorities. Illustratively, as shown in Table 2, the routing list corresponding to NSSAI1 includes, in order of priority from high to low, S-NSSAI1, S-NSSAI2, S-NSSAI3, S-NSSAI4 and S-NSSAI 5.

Table 1 URSP for application a

Table 2 routing list

S-NSSAI1
	S-NSSAI2
S-NSSAI3
	S-NSSAI4
S-NSSAI5

Fig. 2 is a schematic view of an application scenario of a network slice according to an embodiment of the present application. Referring to fig. 2, an application in a terminal device may select a corresponding network slice according to the URSP and connect to a corresponding application server. The network slice used by the application program in the terminal equipment is determined according to the network slice service signed by the application manufacturer and the operator. The correspondence between each application and the network slice may include the following (1) to (3):

(1) different applications may connect to different application servers through different network slices. For example, referring to FIG. 2, application A may connect to application server A-1 using a first network slice and application B connects to application server B using a third network slice.

(2) The same application may be connected to different application servers through different network slices. For example, referring to FIG. 2, 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.

(3) Different applications may connect to different application servers through the same network slice. For example, referring to fig. 2, application C may connect to application server C using a fourth network slice. Application D may connect to application server D using a fourth network slice.

However, only after a PDU session with the network slice is established, can the application communicate with the application server through the network slice using the PDU session. Therefore, the embodiment of the present application provides a PDU session establishment method, which is used to establish a PDU session between a terminal device and a network slice, improve a data transmission rate, and improve user experience.

Referring to fig. 3, a terminal device according to an embodiment of the present disclosure may include an application program layer (APP), an Application Processor (AP), and a baseband processor (e.g., Modem). The application layer may include a series of application packages, which may include applications such as game applications, chat applications, short messages, calendars, cameras, videos, navigation, gallery, calls, and the like. The application processor is used for providing an Application Programming Interface (API) and a programming framework for each application program of the application layer. The application processor may include some predefined functions, such as functions for receiving events sent by the application framework layer. The Modem is used for receiving and transmitting messages of other devices (such as core network devices), converts a digital signal into an analog signal through modulation at a transmitting end, and converts the analog signal into the digital signal through demodulation at a receiving end.

The PDU session setup procedure provided by this embodiment can be divided into two phases. In the first stage, the terminal device registers with the core network device after booting, replacing a Subscriber Identity Module (SIM) card, or canceling a flight mode. And if the terminal device has a network slice configured for use, the core network device sends the URSP to the terminal device after the terminal device registration is successful. And in the second stage, the terminal equipment establishes PDU conversation according to different application programs. Specifically, the terminal device may execute a URSP matching policy through the application processor, and establish a PDU session with the network slice; the URSP matching policy may also be implemented by the modem to establish a PDU session with the network slice, as described below.

Two phases of PDU session establishment are described below in connection with the terminal device shown in fig. 3.

Fig. 4 is a flowchart illustrating a first phase of PDU session establishment according to an embodiment of the present application. Referring to fig. 4, the method specifically includes the following steps S401 to S409.

S401, the modem sends a registration request to the core network equipment.

For example, after the terminal device is powered on, the SIM card is replaced, or the airplane mode is cancelled, the modem automatically sends a Registration request (Registration request) to the terminal device, so as to initiate a Registration process to the core network device. Or after receiving the command sent by the application processor, the modem sends a registration request to the core network equipment.

S402, 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).

After receiving the Registration request sent by the terminal device, the core network device sends a Registration Accept message (Registration Accept) to the modem of the terminal device, where the Registration Accept message carries Allowed nsai. Wherein the Allowed NSSAI is an NSSAI Allowed by the core network device to be used by the terminal device.

S403, the modem sends the Allowed NSSAI to the application processor.

S404, the application processor stores the Allowed NSSAI.

It is to be understood that, as will be understood in conjunction with the determination procedure of the PDU session activation parameters shown in steps S601-S609 below, after the application processor stores the Allowed NSSAI locally, it can select the legitimate S-NSSAI in the URSP to establish the PDU session according to the Allowed NSSAI in the process of determining the PDU session activation parameters according to the URSP.

Through the above steps S401 to S404, the terminal device is successfully registered in the core network device. After the terminal device is successfully registered in the core network device, for example, if a mobile phone number currently used by the terminal device signs a network slicing service, or some application manufacturers configure a network slice when an application provided by the terminal device is configured for the terminal device, the core network device continues to perform subsequent steps S405 to S409 so as to send a URSP corresponding to the network slicing service to the terminal device.

S405, the core network device sends a terminal device management command (management UE policy command) to a modem of the terminal device, wherein the command carries at least one URSP.

For example, if the mobile phone number currently used by the terminal device signs a contract for the 5G-oriented network slice package provided in this embodiment, the core network device may send, to the terminal device, the relevant URSPs of all specified applications in the package range through a downlink non-access stratum Transport channel (DL NAS Transport). Illustratively, the relevant URSPs may include URSPs corresponding to application a, application B, application C, and application D.

S406, the modem sends the at least one URSP to the application processor.

S407, the application processor stores the at least one URSP to form a list of URSPs.

Since there are a plurality of operators of the 5G communication system, 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, the application processor needs to decode and check the URSP after receiving the URSP code stream sent by the modem. The validity check of the URSP means that 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 is judged. If not, the URSP is legal, and the URSP is stored. If not, the URSP is not stored. The PLMN identification code is used for identifying the operator to which the PLMN identification code belongs.

For example, the 5G-oriented network slice package provided in this embodiment is signed up based on the mobile phone number currently used by the terminal device, and the list of the URSPs may be shown in table 3. The URSP list includes all the URSPs issued by the core network device to the terminal device, including the URSPs corresponding to the application program a, the application program B, the application program C, and the application program D. In the URSP list, the priorities of the URSPs decrease in order from top to bottom.

It should be noted that, in the URSP list, at least one Default URSP (i.e., Default URSP) of the Default network slice is included. In the Default URSP, the traffic descriptor is Match All, and each application can use the Default network slice.

TABLE 3URSP List

URSP-A1
	URSP-A2
URSP-A3
	URSP-B1
URSP-B2
	…
Default URSP

S408, the application processor sends a terminal device management complete message (management UE policy complete) to the modem.

The application processor sends a terminal device management complete message to the modem after storing the URSP. The terminal device management completion message is used for notifying the core network device that the terminal device has responded to the terminal device management command.

S409, the modem sends a terminal equipment management completion message to the core network equipment.

Specifically, 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).

It should be noted that, in the above process, if the URSP is not verified, the application processor deletes the URSP, and the modem sends a terminal device management reject message (management UE policy reject) to the core network device through the UL NAS Transport, so as to notify the core network device that the terminal device has rejected the terminal device management command.

In addition, in some embodiments, after the terminal device successfully registers with the core network device, the URSP of the application subscribed to the terminal device may be changed, for example, from a first URSP to a second URSP. If the URSP is changed, the core network device sends a Configuration update command (Configuration update command) to the terminal device, where the Configuration update command may carry the first URSP and the second URSP, and is used to instruct the application processor to replace the first URSP in the list of URSPs with the second URSP.

The second phase of the PDU session establishment will be described based on the contents of the first phase of the PDU session establishment shown in steps S401 to S409.

Fig. 5 is a flowchart illustrating a second phase of PDU session establishment according to an embodiment of the present application. In the method, an application processor of the terminal device executes a URSP matching policy and controls the establishment of a PDU session with the network slice. The method specifically comprises the following steps S501 to S506.

S501, the application processor monitors that the application program reaches the foreground to run.

It should be understood that in the present embodiment, the running of the application includes foreground running and background running.

In some embodiments, foreground running refers to that a user can currently operate and control an application program in the running process of the terminal device. And background running means that a user cannot operate and control the application program in the running process of the terminal equipment.

In other embodiments, the foreground running of the application may be when the application is currently in the active state activity, while the background running of the application is when the application is in the inactive state.

S502, in response to the application program reaching the foreground for operation, the application processor acquires the identification information of the data packet of the application program. Illustratively, the identification information of the packet may be App ID, IP triplet, DNN, FQDN, etc.

S503, the application processor searches the PDU session activation parameter in the URSP list according to the identification information and the URSP matching strategy.

After the application processor monitors that the application program reaches the foreground for running, the application processor may select a corresponding URSP by using the identification information matching according to a URSP matching policy (see steps S601 to S609 shown below), and select a PDU session activation parameter from the URSP, so as to activate a corresponding PDU session according to the PDU session activation parameter in a subsequent step.

S504, the application processor sends a PDU session establishment request to the modem according to the PDU session activation parameter.

Since different applications may use the same network slice, the network slice corresponding to the PDU session activation parameter may already be activated, i.e. the PDU session between the terminal device and the network slice is 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 is successful, the activation is not needed, and repeated operation is avoided. If the non-activation is successful, a PDU session establishment request is sent to the modem to activate the network slice according to the PDU session activation parameter. 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 a PDU session activation parameter to request activation of the PDU session of the network slice corresponding to the PDU session activation parameter. For example, when the PDU session activation parameter is S-NSSAI1, the PDU session establishment request is for requesting activation of a PDU session with a network slice identified as S-NSSAI 1.

S505, the modem sends the PDU session establishment request to the core network device.

S506, the core network device sends a PDU session acceptance message to the modem.

The PDU session acceptance message (PDU session authorization indication accept) carries a PDU session activation parameter, and is used to indicate that the PDU session of the network slice corresponding to the PDU session activation parameter has been activated. For example, when 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 is activated.

And S507, the PDU session acceptance message sent by the modem to the application processor.

Through the steps S501 to S507, the terminal device may 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. After activation of the PDU session, the application processor routes a packet containing the identification information to be bound to the PDU session. Thereafter, 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 flowchart of the URSP matching policy provided in this embodiment of the application, and describes a process of searching the PDU session activation parameter in the URSP list according to the identification information of the data packet and the URSP matching policy in step S503. The URSP matching policy may be applied to the application processor as well as to the modem. Specifically, the method includes the following steps S601 to S608.

S601, starting to traverse the URSP list according to the priority.

S602, judging whether the URSP which is not accessed exists in the URSP list. If there is no inaccessible URSP, PDU activation parameter selection fails. If there is an unvisited URSP, the next step S603 is performed.

S603, according to the identification information, matching the flow descriptor of the URSP with the highest priority in the inaccessible URSPs. Illustratively, if the URSP with the highest priority among the unaccessed URSPs is URSP-a1, and its traffic descriptor includes an App ID, the App ID of the application is matched with the traffic descriptor.

S604, whether the traffic descriptors are successfully matched is judged.

Specifically, if the App ID of the application is different from the traffic descriptor of the currently accessed URSP, the traffic descriptor matching fails, and the process returns to step S602. If the traffic descriptors match successfully, the URSP selection is successful, and the next step S605 is executed.

S605 starts traversing the routing list (route selection list) of the URSP according to the priority.

S606, judging whether the routing list has the S-NSSAI which is not accessed.

Specifically, if there is an unaccessed S-NSSAI in the routing list, the next step S607 is performed. If there is no unaccessed S-NSSAI in the routing list, step S609 is performed.

S607, judging whether the S-NSSAI with the highest priority in the non-accessed S-NSSAIs is in the Allowed NSSAI list.

Specifically, if the S-NSSAI with the highest priority among the unaccessed S-NSSAIs is not in the Allowed NSSAI list, the process returns to step S606. If the highest priority S-NSSAI is in the Allowed NSSAI list, the next step S608 is performed.

S608, selecting the remaining routing information in the S-NSSAI and the currently visited URSP as the PDU session activation parameter.

In this embodiment, the remaining routing information refers to the remaining information in the routing descriptor except NSSAI, such as DNN, protocol type, and the like. For example, in the case of a network-sliced carrier, which is china mobile, the DNN is cmnet, and the protocol type may be TCP protocol or UDP protocol.

S609, select the rest routing descriptors in the currently visited URSP as the PDU session activation parameter. It should be noted that, since the terminal device does not select S-NSSAI, the terminal device uses a default network slice according to DNN, protocol type, and other information.

Through the steps S601 to S609, the PDU session activation parameter corresponding to the identification information can be selected.

Fig. 7 is a flowchart illustrating a first phase of PDU session establishment according to another embodiment of the present application. Referring to fig. 7, the method specifically includes the following steps S701 to S706.

S701, the modem sends a registration request to the core network equipment.

S702, the core network device sends a registration acceptance message to the modem, where the registration acceptance message carries the Allowed NSSAI.

Please refer to S402 for details of step S702, which is not described herein again.

S703, the modem stores the Allowed NSSAI.

It is understood that, as known from the determination procedure of PDU session activation parameters shown in steps S601-S609 above, after the modem stores the Allowed NSSAI locally, in the process of determining the PDU session activation parameters according to the URSP, the valid S-NSSAI in the URSP can be selected according to the Allowed NSSAI to establish the PDU session.

Through the above steps S701 to S703, the terminal device is successfully registered in the core network.

After the terminal device is successfully registered in the core network device, for example, if a mobile phone number currently used by the terminal device signs a network slicing service, or some application manufacturer configures a network slice when an application provided by the terminal device is provided for the terminal device, the core network device continues to perform subsequent steps S704-S706, so as to send a URSP corresponding to the network slicing service to the terminal device.

S704, the core network device sends a terminal device management command to the modem, where the command carries at least one URSP.

In this embodiment, the core network may send a terminal device management command through a downlink non-access stratum Transport channel (DL NAS Transport) to deliver the relevant URSP to the terminal device.

S705, the modem stores the at least one URSP to form a list of URSPs.

Specifically, after receiving the URSP code stream issued by the application processor, the modem decodes and verifies the validity of the URSP, and stores the URSP after the verification is legal, thereby forming a URSP list. Please refer to step S407 for details of the validity check, which is not described herein.

S706, the modem sends a terminal device management completion message to the core network device.

The flows shown in steps S701 to S706 are simpler than the flows shown in steps S401 to S409 in the first stage of establishing a PDU session. In steps S701 to S706, after acquiring the Allowed NSSAI, URSP, and other parameters, the modem directly stores them locally without forwarding them to the application processor, which is helpful to improve the registration and delivery efficiency of the URSP.

It should be noted that, in the process of registering the terminal device with the core network, if the URSP is not verified, the modem deletes the URSP, and sends a terminal device management rejection message to the core network device.

In addition, in some embodiments, after the terminal device successfully registers in the core network, the URSP of the terminal device may be changed, for example, from a first URSP to a second URSP. If the URSP is changed, the core network device sends a Configuration update command (Configuration update command) to the terminal device, where the Configuration update command may carry the first URSP and the second URSP, and is used to instruct the modem to replace the first URSP in the list of the URSPs with the second URSP.

The second phase of the establishment of the PDU session is explained based on the contents of the first phase of the PDU session establishment shown in steps S701-S706.

Fig. 8 is a flowchart of a second phase of the establishment of the PDU session according to an embodiment of the present application, which describes a process of the modem side executing the URSP matching policy to establish the PDU session, and specifically includes the following steps S801 to S807.

S801, the application program sends the first data packet to the application processor.

During operation, the application program usually generates a plurality of first data packets and sends the first data packets to the application processor.

S802, the application processor adds App ID in 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 program to which the first data packet belongs.

Referring to fig. 9, the software system architecture of the terminal device may include an application layer, a TCP layer, an IP layer, and a physical layer. In the terminal device, user data generated in the running process of the application program can be transmitted to the core network device through an application program layer, a TCP layer, an IP layer and a physical layer in sequence. First, the application layer adds an application header to user data to form application data, and sends the application data to the TCP layer. Second, the TCP layer adds a TCP header to the application data, forming a TCP segment. The IP layer then adds an IP header to the TCP segment, forming an IP packet. Wherein the maximum IP data packet is 1500 bytes. Finally, the physical layer adds an Ethernet (Ethernet) header and an Ethernet trailer to the IP packet to form an Ethernet frame. In this embodiment, the application processor may add the App ID in an invalid field in the ethernet header or trailer of the packet. Wherein the invalid field refers to a field that is not occupied.

It will be appreciated that the application processor avoids adding a new field to the first packet by adding the identification information to an invalid field in the ethernet header or the ethernet trailer of the first packet.

S803, the application processor sends the second data packet to the modem.

And S804, the modem searches PDU session activation parameters in the URSP list according to the App ID and the URSP matching strategy.

In step S804, specific content of the PDU session activation parameter is searched in the URSP list according to the App ID and the URSP matching policy, please refer to steps S601 to S609, which is not described herein again.

S805, the modem sends a PDU session establishment request (PDU session establishment request) to the core network equipment according to the PDU session activation parameter.

Since different applications are installed in the terminal device, they may access the same server using the same network slice, and thus, may have the same PDU session activation parameters. Therefore, in this embodiment, when the modem sends a PDU session establishment request to the terminal device according to the PDU session activation parameter, it first determines whether the established PDU session exists according to the PDU session activation parameter. And if the PDU return session does not exist, sending a PDU session establishment request to the core network equipment so as to establish the PDU session. If the PDU session exists, the modem does not repeatedly establish the PDU session according to the PDU session activation parameter, and transmits a second data packet by using the established PDU session.

The PDU session establishment request carries a PDU session activation parameter to request activation of the PDU session of the network slice corresponding to the PDU session activation parameter. For example, when the PDU session activation parameter includes S-NSSAI1, the PDU session establishment request is for requesting activation of a PDU session with a network slice identified as S-NSSAI 1.

S806, the core network device sends a PDU session acceptance message to the modem.

After the PDU session is activated, the modem binds the packet route containing the App ID to the PDU session. Thereafter, the data packet including the App ID can be transmitted through the PDU session, so as to implement the network slice communication between the application program and the application server.

As will be appreciated by those skilled in the art, the first data packet sent by the application program to the application processor typically passes through the application processor to the modem, then is sent by the modem to the core network device, and finally is sent by the core network device to the application server. Since the application sending the first packet may not include the application's identification information, the modem cannot make a URSP match selection and establish a PDU session based on its identification information.

In this embodiment, the application processor first adds the identification information of the application program to each first data packet of the application program to form a second data packet, and then sends the second data packet to the modem. Then, the modem can acquire the identification information of the application program, determine the corresponding URSP in the URSP list according to the identification information, and establish the PDU session according to the URSP. Therefore, the PDU session establishment method provided in this embodiment may perform URSP matching selection and establish a PDU session through the modem, so as to provide data transmission for the application program and the application server.

Fig. 10 is a flowchart illustrating a second phase of PDU session establishment according to another embodiment of the present application, describing a process of a modem executing a URSP matching policy to establish a PDU session with a network slice, including the following steps S1001 to S1007.

It should be noted that, before the second phase of PDU session establishment provided in this embodiment, the terminal device also needs to execute the first phase of PDU session establishment procedure shown in steps S701 to S706, which is not described herein again. In addition, the application processor needs to send a corresponding relation table between a User Identification (UID) and an App ID of each application program to the modem for storage, and the modem forwards the corresponding relation table to the core network device. The UID is used to uniquely identify an account of the application program, and may be a registered mobile phone number, a registered mailbox number, a registered Identification number, an account Identification (ID) assigned by the application server, and the like of the account.

S1001, the application program sends the first data packet to the application processor.

S1002, the application processor adds the UID to the first packet to form a second packet.

In this embodiment, please refer to the method in step S802 for adding the App ID to the first data packet by the application processor, which is not described herein again.

And S1003, the application processor sends the second data packet to the modem.

And S1004, the modem determines the App ID corresponding to the UID according to a preset corresponding relation table.

For example, the correspondence table between UID and App ID may be as shown in table 4. Illustratively, the UID-A of application A corresponds to App ID-A. And App ID-B corresponding to UID-B of the application program B.

TABLE 4 table of correspondence

UID	App ID
		UID-A	App ID-A
UID-B	App ID-B
		UID-C	App ID-C
UID-D	App ID-D
		…	…

S1005, the modem searches the PDU conversation activating parameter in the URSP list according to the App ID and the URSP matching strategy.

S1006, the modem sends a PDU session establishment request to the core network device according to the PDU session activation parameter.

S1007, the core network device sends a PDU session acceptance message to the modem.

Please refer to steps S804-S806 for the contents of steps S1005-S1007, which are not described herein again.

In this embodiment, the terminal device may execute the URSP matching policy through the modem by using the UID to establish a PDU session with the network slice. After activation of the PDU session, the modem binds the packet route containing the UID to the PDU session. Thereafter, the data packet including the UID can be transmitted through the PDU session, so as to implement the communication between the application program and the application server through the network slice.

Fig. 11 is a flowchart of a second phase of PDU session establishment according to some other embodiments of the present application, which describes a process of a modem performing a URSP matching policy at the modem according to an IP triplet, FQND or DNN, and establishing a PDU session. The method comprises the following steps S1101-S1105.

S1101, the application program sends the packet to the application processor.

S1102, the application processor sends the data packet to a modem.

S1103, the modem searches PDU session activation parameters in a URSP list according to any one of the IP triple, FQND and DNN of the data packet and the URSP matching strategy.

Please refer to the process of determining the PDU session activation parameter according to the identification information shown in steps S601 to S608, which is not described herein again in this embodiment.

S1104, the modem sends a PDU session establishment request to the core network device according to the PDU session activation parameter.

S1105, the core network device sends a PDU session acceptance message to the modem.

Please refer to steps S805 to S806 in steps S1104 to S1105, which will not be described herein.

In this embodiment, the terminal device may 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. After the PDU session is activated, the modem binds the data packet route containing the IP triple, FQND or DNN on the PDU session, and communication between the application program and the application server through the network slice is realized.

It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

Based on the PDU session establishment method provided in this embodiment, this embodiment further provides a terminal device, where the terminal device includes an application processor and a baseband processor, and the baseband processor stores a terminal device routing policy URSP list, where the URSP list includes at least one URSP. Wherein the application processor is configured to obtain a first data packet of the application program; adding identification information of the application program to the first data packet to form a second data packet; and sending the second data packet to the baseband processor. The baseband processor is configured to look up a URSP corresponding to the identification information in a URSP list; determining PDU session activation parameters according to the URSP corresponding to the identification information; and establishing a PDU session according to the PDU session activation parameter, wherein the PDU session is used for transmitting the second data packet.

In some embodiments, the adding, by the application processor, the identification information of the application program to the first data packet to form a second data packet specifically includes: and the application processor adds the identification information of the application program in an unoccupied field at the head part or the tail part of the Ethernet of the first data packet to form a second data packet.

In some embodiments, after the baseband processor stores the Allowed NSSAI, before the application processor retrieves the first data packet transmitted by the application program, the baseband processor is further configured to: receiving a terminal equipment management command sent by core network equipment, wherein the command carries URSP; storing the at least one URSP to form a URSP list; and sending a terminal device management completion message to the core network device, wherein the message is used for indicating that the baseband processor has processed the terminal device management command.

In some embodiments, 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; replacing the first URSP in the list of URSPs with a second URSP according to the configuration update command.

In some embodiments, the baseband processor is a modem.

An embodiment of the present application further provides a chip system, where the chip system includes a memory, and an application processor and a baseband processor coupled to the memory, where the application processor and the baseband processor execute a computer program stored in the memory to implement the PDU session establishment method provided in the foregoing embodiment.

An embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored, and when executed by an application processor and a baseband processor, the computer program implements the PDU session establishment method provided in the foregoing embodiment.

It should be understood that the computer-readable medium in this embodiment may include at least: any entity or apparatus capable of carrying computer program code to a terminal device, recording medium, computer Memory, Read-Only Memory (ROM), Random-Access Memory (RAM), electrical carrier wave signals, telecommunications signals, and software distribution medium. Such as a usb-disk, a removable hard disk, a magnetic or optical disk, etc. In certain jurisdictions, computer-readable media may not be an electrical carrier signal or a telecommunications signal in accordance with legislative and patent practice.

The embodiment of the present application further provides a computer program product, which, when running on a terminal device, enables the terminal device to execute a method for implementing the PDU session establishment provided in the foregoing embodiment. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc.

It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the network slice management system, the application server and the terminal device described above may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

It should be understood that the terms "first," "second," "third," and the like in the description of the present application and in the appended claims, are used for distinguishing between descriptions that are not intended to indicate or imply relative importance.

Reference throughout this specification to "one embodiment" or "some embodiments," or the like, means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," or the like, in various places throughout this specification are not necessarily all referring to the same embodiment, but rather "one or more but not all embodiments" unless specifically stated otherwise. The terms "comprising," "including," "having," and variations thereof mean "including, but not limited to," unless expressly specified otherwise.

Finally, it should be noted that: the above description is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A PDU conversation establishment method is applied to terminal equipment, the terminal equipment comprises an application processor and a baseband processor, and is characterized in that a terminal equipment routing strategy URSP list is stored in the baseband processor, and the URSP list comprises at least one URSP; the method comprises the following steps:

the application processor acquires a first data packet of an application program; and the number of the first and second groups,

adding identification information of the application program to the first data packet to form a second data packet; and the number of the first and second groups,

sending the second data packet to the baseband processor;

the baseband processor searches the URSP corresponding to the identification information in the URSP list; and the number of the first and second groups,

determining a Protocol Data Unit (PDU) session activation parameter according to the URSP corresponding to the identification information; and the number of the first and second groups,

and establishing a PDU session according to the PDU session activation parameter, wherein the PDU session is used for transmitting the second data packet.

2. The method according to claim 1, wherein the identification information is an application identification (App ID) or a user account identification (UID).

3. The method of claim 2, wherein if the identification information is App ID, the baseband processor searches the URSP list for the URSP corresponding to the identification information, comprising:

and the baseband processor searches the URSP list for the URSP corresponding to the App ID.

4. The method of claim 2, wherein if the identification information is a UID, the baseband processor searches the URSP list for a URSP corresponding to the identification information, comprising:

the baseband processor determines an App ID corresponding to the UID according to a preset corresponding relation table, wherein the corresponding relation table comprises the corresponding relation between the UID and the App ID; and the number of the first and second groups,

and searching the URSP corresponding to the App ID in the URSP list.

5. The method according to any one of claims 1-4, wherein the application processor adds the identification information of the application program to the first data packet to form a second data packet, comprising:

and the application processor adds the identification information to an unoccupied field at the head part or the tail part of the Ethernet of the first data packet to form the second data packet.

6. The method of any of claims 1-5, wherein prior to the application processor obtaining the first data packet for the application program, the method further comprises:

the baseband processor sends a registration request to core network equipment; and the number of the first and second groups,

receiving a registration acceptance message sent by the core network device, wherein the registration acceptance message carries network slice selection auxiliary information Allowed by the core network device to be used by the terminal device; and the number of the first and second groups,

storing the Allowed NSSAI.

7. The method of claim 6, wherein after the baseband processor stores the Allowed NSSAI, the method further comprises, before the application processor retrieves a first packet sent by an application program:

the baseband processor receives a terminal equipment management command sent by the core network equipment, wherein the command carries the at least one URSP; and the number of the first and second groups,

storing the at least one URSP to form a URSP list; and the number of the first and second groups,

and sending a terminal equipment management completion message to the core network equipment, wherein the message is used for indicating that the baseband processor has processed the terminal equipment management command.

8. The method according to claim 6 or 7, wherein the PDU session activation parameters include single network slice selection assistance information S-NSSAI, data network name DNN and protocol type; wherein said S-NSSAI is included in said Allowed NSSAI.

9. The method according to any one of claims 1-8, further comprising:

the baseband processor receives a configuration update command sent by core network equipment, wherein the configuration update command carries a first URSP and a second URSP, and the second URSP is a URSP updated by the first URSP; and the number of the first and second groups,

replacing the first URSP in the list of URSPs with the second URSP according to the configuration update command.

10. The method according to any of claims 1-9, wherein the baseband processor establishes the PDU session according to the PDU session activation parameter, comprising:

and if the PDU session established according to the PDU session activation parameter does not exist in the established PDU session, the base band processor establishes the PDU session according to the PDU session activation parameter.

11. The method of any of claims 1-10, wherein the baseband processor is a modem.

12. A terminal device comprises an application processor and a baseband processor, and is characterized in that a terminal device routing strategy (URSP) list is stored in the baseband processor, and the URSP list comprises at least one URSP;

the application processor is configured to, in response to the application processor being configured to,

acquiring a first data packet of an application program;

adding identification information of the application program to the first data packet to form a second data packet;

sending the second data packet to the baseband processor;

the baseband processor is configured to perform a baseband processing operation,

searching the URSP corresponding to the identification information in the URSP list;

determining a Protocol Data Unit (PDU) session activation parameter according to the URSP corresponding to the identification information;

13. The terminal device according to claim 12, wherein the identification information is an application identification (App ID) or a user account identification (UID).

14. The terminal device of claim 13, wherein if the identification information is App ID, the baseband processor searches the URSP list for the URSP corresponding to the identification information, and comprises:

15. The terminal device of claim 13, wherein if the identification information is a UID, the baseband processor searches the URSP list for a URSP corresponding to the identification information, and includes:

and searching the URSP corresponding to the App ID in the URSP list.

16. The terminal device according to any one of claims 12 to 15, wherein the application processor adds the identification information of the application program to the first data packet to form a second data packet, specifically comprising:

17. The terminal device according to any of claims 12-16, wherein prior to the application processor obtaining the first data packet of the application program, the baseband processor is further configured to,

sending a registration request to core network equipment;

receiving a registration acceptance message sent by the core network device, wherein the registration acceptance message carries network slice selection auxiliary information Allowed by the core network device to be used by the terminal device;

storing the Allowed NSSAI.

18. The terminal device of claim 17, wherein after the baseband processor stores the Allowed NSSAI, and before the application processor retrieves the first packet sent by the application program, the baseband processor is further configured to:

receiving a terminal device management command sent by the core network device, wherein the command carries the at least one URSP;

storing the at least one URSP to form a URSP list;

19. A terminal device according to claim 17 or 18, characterised in that the PDU session activation parameters comprise single network slice selection assistance information S-NSSAI, data network name DNN and protocol type;

wherein said S-NSSAI is included in said Allowed NSSAI.

20. The terminal device of any of claims 12-19, wherein the baseband processor is further configured to,

receiving a configuration updating command sent by core network equipment, wherein the configuration updating command carries a first URSP and a second URSP, and the second URSP is a URSP updated by the first URSP;

21. The terminal device according to any of claims 12-20, wherein the baseband processor establishes a PDU session according to the PDU session activation parameter, comprising:

22. A terminal device according to any of claims 12-21, wherein the baseband processor is a modem.

23. A chip system, characterized in that the chip system comprises a memory, an application processor and a baseband processor coupled with the memory, the application processor and the baseband processor executing a computer program stored in the memory to implement the protocol data unit, PDU, session establishment method as claimed in any one of claims 1 to 11.

24. A computer-readable storage medium, in which a computer program is stored, which, when being executed by an application processor and a baseband processor, carries out a protocol data unit, PDU, session establishment method according to any one of claims 1 to 11.

25. A computer program product, characterized in that, when run on a terminal device, causes the terminal device to perform a protocol data unit, PDU, session establishment method as in any one of claims 1 to 11.