PDU session establishment or modification method, terminal, network-side device, and storage medium

Abstract

The present application relates to the technical field of wireless communications, and discloses a PDU session establishment or modification method, a terminal, a network-side device, and a storage medium. The PDU session establishment or modification method according to an embodiment of the present application comprises: a terminal receives a first request, the first request being used for requesting establishment or modification of a first PDU session for a new service; and the terminal sends a first response in response to the first request, the first response being used for indicating whether establishment or modification of the first PDU session is successful.

Description

PDU session establishment or modification methods, terminals, network-side devices, and storage media

[0001] Cross-referencing

[0002] This disclosure claims priority to Chinese Patent Application No. 202411993812.0, filed on December 31, 2024, entitled "PDU Session Establishment or Modification Method, Terminal, Network Side Device and Storage Medium", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application belongs to the field of wireless communication technology, specifically relating to a method for establishing or modifying a PDU session, a terminal, a network-side device, and a storage medium. Background Technology

[0004] Existing user plane protocols are primarily used to transmit application functions of user equipment (UE, also known as a terminal) and existing user plane data between the data network (DN). During existing user plane data transmission, transparently transmitted data is mapped to appropriate QoS streams and data radio bearers (DRBs) according to Quality of Service (QoS) rules. However, the new services of the sixth-generation mobile communication standard (6G) cause 6G networks to generate and transmit a large amount of new service data, which is different from the aforementioned existing user plane data. The requirements of the new service data (e.g., priority, endpoint, etc.) differ from those of existing user plane data, making it difficult for existing user plane protocols to support the transmission of this new service data. Summary of the Invention

[0005] This application provides a method for establishing or modifying a PDU session, a terminal, a network-side device, and a storage medium, which can solve the problem of how to establish a PDU session for a new service.

[0006] Firstly, a method for establishing or modifying a PDU session is provided, including:

[0007] The terminal receives a first request, which is used to request the establishment or modification of a first PDU session for a new service;

[0008] The terminal sends a first response to the first request, the first response indicating whether the first PDU session was successfully established or modified.

[0009] Secondly, a method for establishing or modifying a PDU session is provided, including:

[0010] The new service function node sends a first request to the terminal; the first request is used to request the establishment or modification of a first PDU session for the new service.

[0011] or,

[0012] The new service function node sends a second request to the radio access network function node; the second request is used to request the establishment or modification of a second PDU session for the new service.

[0013] Thirdly, a method for establishing or modifying a PDU session is provided, including:

[0014] The radio access network functional node receives a second request, which is used to request the establishment of a second PDU session for the new service;

[0015] The radio access network functional node sends a second response to the second request, the second response being used to indicate whether the second PDU session was successfully established or modified.

[0016] or,

[0017] The radio access network functional node receives a third request, which instructs the radio access network functional node to configure a DRB for a first PDU session for a new service for the terminal.

[0018] The radio access network functional node sends a third response to the third request, the third response indicating whether the first PDU session was successfully established or modified.

[0019] Fourthly, a method for establishing or modifying a PDU session is provided, including:

[0020] The terminal sends a fourth request, which is used to request the establishment or modification of a third PDU session for the new service;

[0021] The terminal receives a fourth response, which indicates whether the third PDU session was successfully established or modified.

[0022] Fifthly, a method for establishing or modifying a PDU session is provided, including:

[0023] The AMF receiving terminal sends a fourth request, which is used to request the establishment or modification of a third PDU session for a new service;

[0024] The AMF selects an SMF for the terminal and sends a fifth request to the SMF, the fifth request being used to request the establishment or modification of the third PDU session.

[0025] Sixthly, a method for establishing or modifying a PDU session is provided, including:

[0026] SMF receives a fifth request from AMF; the fifth request is used to request the establishment or modification of a third PDU session for a new service;

[0027] The SMF selects the UPF based on the fifth request;

[0028] The SMF sends a fifth response to the terminal or the radio access network functional node, the fifth response being used to indicate whether the third PDU session was successfully established or modified.

[0029] Seventhly, a method for establishing or modifying a PDU session is provided, including:

[0030] The radio access network functional node receives a fifth response sent by the SMF; the fifth response is used to indicate whether the third PDU session for the new service was successfully created or modified.

[0031] The fifth response includes at least one of the following:

[0032] The QoS flow identifier of the new service;

[0033] The QoS parameters of the new service;

[0034] The new service uses the PDU session type;

[0035] RAN termination indication is used to indicate whether the data of the new service is resolved by the radio access network function node.

[0036] Eighthly, a device for establishing or modifying a PDU session is provided, comprising:

[0037] The receiving module is configured to receive a first request, wherein the first request is used to request the establishment or modification of a first PDU session for a new service;

[0038] The sending module is used to send a first response to the first request, the first response being used to indicate whether the first PDU session has been successfully established or modified.

[0039] Ninthly, a device for establishing or modifying a PDU session is provided, comprising:

[0040] The sending module is configured to send a first request to the terminal; the first request is used to request the establishment or modification of a first PDU session for a new service; or, send a second request to the radio access network functional node; the second request is used to request the establishment or modification of a second PDU session for a new service.

[0041] In a tenth aspect, a device for establishing or modifying a PDU session is provided, comprising:

[0042] The receiving module is used to receive a second request, which is used to request the establishment of a second PDU session for the new service;

[0043] The sending module is used to send a second response to the second request, the second response being used to indicate whether the second PDU session was successfully established or modified;

[0044] or,

[0045] The receiving module is configured to receive a third request, the third request being used to instruct the radio access network functional node to configure the DRB for the terminal for the first PDU session of the new service;

[0046] The sending module is used to send a third response to the third request, the third response being used to indicate whether the first PDU session was successfully established or modified.

[0047] Eleventhly, a device for establishing or modifying a PDU session is provided, comprising:

[0048] A sending module is used to send a fourth request, which is used to request the establishment or modification of a third PDU session for a new service;

[0049] The receiving module is used to receive a fourth response, which indicates whether the third PDU session was successfully established or modified.

[0050] In a twelfth aspect, a PDU session establishment or modification apparatus is provided, comprising:

[0051] The receiving module is used to receive a fourth request sent by the terminal, the fourth request being used to request the establishment or modification of a third PDU session for a new service;

[0052] The processing module is used to select an SMF for the terminal;

[0053] The sending module is used to send a fifth request to the SMF, the fifth request being used to request the establishment or modification of the third PDU session.

[0054] In a thirteenth aspect, a device for establishing or modifying a PDU session is provided, comprising:

[0055] The receiving module is used to receive the AMF's fifth request; the fifth request is used to request the establishment or modification of a third PDU session for a new service;

[0056] The processing module is used to select a UPF based on the fifth request;

[0057] The sending module is used to send a fifth response to the terminal or the wireless access network functional node, the fifth response being used to indicate whether the third PDU session has been successfully established or modified.

[0058] In a fourteenth aspect, a PDU session establishment or modification apparatus is provided, comprising:

[0059] The receiving module is used to receive the fifth response sent by the SMF; the fifth response is used to indicate whether the third PDU session for the new service was successfully created or modified.

[0060] The fifth response includes at least one of the following:

[0061] The QoS flow identifier of the new service;

[0062] The QoS parameters of the new service;

[0063] The new service uses the PDU session type;

[0064] RAN termination indication is used to indicate whether the data of the new service is resolved by the radio access network function node.

[0065] In a fifteenth aspect, a PDU session establishment or modification apparatus is provided, the apparatus being configured to perform the steps of the methods described in the first, second, third, fourth, fifth, sixth, or seventh aspects.

[0066] In a sixteenth aspect, a terminal is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first or fourth aspect.

[0067] In a seventeenth aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is configured to receive a first request, the first request being configured to request the establishment or modification of a first PDU session for a new service; and to send a first response to the first request, the first response being configured to indicate whether the first PDU session has been successfully established or modified.

[0068] In an eighteenth aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is configured to send a fourth request, the fourth request being configured to request the establishment or modification of a third PDU session for a new service; and to receive a fourth response, the fourth response being configured to indicate whether the third PDU session has been successfully established or modified.

[0069] In a twenty-ninth aspect, a network-side device is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the methods described in the second, third, fifth, sixth, or seventh aspects.

[0070] In a twentieth aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is used to send a first request to a terminal; the first request is used to request the establishment or modification of a first PDU session for a new service; or, to send a second request to a radio access network functional node; the second request is used to request the establishment or modification of a second PDU session for a new service.

[0071] In a twenty-first aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is configured to receive a second request, the second request being for requesting the establishment of a second PDU session for a new service; send a second response to the second request, the second response being for indicating whether the second PDU session has been successfully established or modified; or, receive a third request, the third request being for instructing the radio access network functional node to configure a DRB for a first PDU session for a new service for a terminal; and send a third response to the third request, the third response being for indicating whether the first PDU session has been successfully established or modified.

[0072] In a twenty-second aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is configured to receive a fourth request sent by a terminal, the fourth request being for requesting the establishment or modification of a third PDU session for a new service; the processor is configured to select an SMF for the terminal; and the communication interface is further configured to send a fifth request to the SMF, the fifth request being for requesting the establishment or modification of the third PDU session.

[0073] In a twentieth aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is used to receive a fifth request from an AMF; the fifth request is used to request the establishment or modification of a third PDU session for a new service; the processor is used to select a UPF according to the fifth request; and the communication interface is used to send a fifth response to the terminal or a radio access network functional node, the fifth response being used to indicate whether the third PDU session has been successfully established or modified.

[0074] In a twenty-fourth aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is used to receive a fifth response sent by an SMF; the fifth response is used to indicate whether a third PDU session for a new service has been successfully created or modified; wherein the fifth response includes at least one of the following:

[0075] The QoS flow identifier of the new service;

[0076] The QoS parameters of the new service;

[0077] The new service uses the PDU session type;

[0078] RAN termination indication is used to indicate whether the data of the new service is resolved by the radio access network function node.

[0079] In a twenty-fifth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the methods described in the first, second, third, fourth, fifth, sixth, or seventh aspects.

[0080] In a twenty-sixth aspect, a wireless communication system is provided, comprising: a terminal and a network-side device, wherein the terminal is configured to perform the steps of the method described in the first aspect, and the network-side device is configured to perform the steps of the method described in the second or third aspect.

[0081] In a twentieth aspect, a wireless communication system is provided, comprising: a terminal and a network-side device, wherein the terminal is configured to perform the steps of the method described in the fourth aspect, and the network-side device is configured to perform the steps of the method described in the fifth, sixth, or seventh aspect.

[0082] In a twenty-eighth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run programs or instructions to implement the steps of the methods described in the first, second, third, fourth, fifth, sixth, or seventh aspects.

[0083] In a twenty-ninth aspect, a computer program / program product is provided, the computer program / program product being stored in a storage medium, the computer program / program product being executed by at least one processor to implement the steps of the method as described in the first aspect, second aspect, third aspect, fourth aspect, fifth aspect, sixth aspect, or seventh aspect.

[0084] In the embodiments of this application, the establishment or modification process of the PDU session of the new service is triggered by the new service function node, or the existing PDU session establishment or modification process is extended so that the terminal triggers the establishment or modification process of the PDU session for the new service, thereby completing the establishment or modification of the PDU session of the new service. Attached Figure Description

[0085] Figure 1 is a block diagram of a wireless communication system applicable to an embodiment of this application;

[0086] Figure 2 is a schematic diagram of the user plane protocol stack between the UE and gNB;

[0087] Figure 3 is a schematic diagram of the user plane protocol stack between the UE and the UPF;

[0088] Figure 4 is a schematic diagram of the data plane protocol stack between the UE and the network;

[0089] Figure 5 is a flowchart illustrating one of the PDU session establishment or modification methods according to an embodiment of this application;

[0090] Figure 6 is a second schematic flowchart of the PDU session establishment or modification method according to an embodiment of this application;

[0091] Figure 7 is a third flowchart illustrating the PDU session establishment or modification method according to an embodiment of this application;

[0092] Figure 8 is a flowchart of the PDU session establishment or modification method according to an embodiment of this application (fourth one).

[0093] Figure 9 is a fifth flowchart illustrating the PDU session establishment or modification method according to an embodiment of this application;

[0094] Figure 10 is a flowchart of the PDU session establishment or modification method according to an embodiment of this application.

[0095] Figure 11 is a flowchart of the PDU session establishment or modification method according to an embodiment of this application (the seventh one).

[0096] Figure 12 is a flowchart of the PDU session establishment or modification method according to an embodiment of this application (the eighth one).

[0097] Figure 13 is a flowchart of the PDU session establishment or modification method according to an embodiment of this application (the ninth one).

[0098] Figure 14 is a flowchart illustrating the PDU session establishment or modification method according to Embodiment 1 of this application;

[0099] Figure 15 is a flowchart illustrating the PDU session establishment or modification method according to Embodiment 2 of this application;

[0100] Figure 16 is a schematic diagram of the SDAP header according to an embodiment of this application;

[0101] Figure 17 is a schematic diagram of one of the structures of the PDU session establishment or modification device according to an embodiment of this application;

[0102] Figure 18 is a second schematic diagram of the structure of the PDU session establishment or modification device according to an embodiment of this application;

[0103] Figure 19 is a third schematic diagram of the structure of the PDU session establishment or modification device according to an embodiment of this application;

[0104] Figure 20 is a fourth structural schematic diagram of the PDU session establishment or modification device according to an embodiment of this application;

[0105] Figure 21 is a fifth structural schematic diagram of the PDU session establishment or modification device according to an embodiment of this application;

[0106] Figure 22 is a sixth structural schematic diagram of the PDU session establishment or modification device according to an embodiment of this application;

[0107] Figure 23 is a seventh structural schematic diagram of the PDU session establishment or modification device according to an embodiment of this application;

[0108] Figure 24 is a schematic diagram of the structure of the PDU session establishment or modification device according to an embodiment of this application;

[0109] Figure 25 is a schematic diagram of the structure of a communication device according to an embodiment of this application;

[0110] Figure 26 is a schematic diagram of the hardware structure of the terminal according to an embodiment of this application;

[0111] Figure 27 is a schematic diagram of the hardware structure of the network-side device according to an embodiment of this application;

[0112] Figure 28 is a second schematic diagram of the hardware structure of the network-side device according to an embodiment of this application. Detailed Implementation

[0113] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0114] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0115] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as the sender explicitly informing the receiver of specific information, the required operation, or the requested result in the instruction sent. An indirect instruction can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the required operation or requested result based on the judgment result.

[0116] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0117] Figure 1 shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as User Equipment (UE), and can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (APs), or Wireless Fidelity (WiFi) nodes, etc.Among them, base stations can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform stations). The term "base station" can be any suitable term in the field, such as "station" or any other appropriate term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to specific technical terms. It should be noted that the embodiments of this application only use the base station in the NR system as an example for introduction, and do not limit the specific type of base station.

[0118] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (L-NEF), and Binding Support. Functions include BSF, Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), Network Data Analytics Function (NWDAF), and Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform station).It should be noted that the embodiments of this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment. If the name of the core network equipment mentioned in the embodiments of this application changes in subsequent protocol versions (e.g., 6G), it is also within the scope of protection of this application.

[0119] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0120] The following is a brief explanation of the technical terms used in this application.

[0121] 1. New Services

[0122] The convergence of communication and sensing, along with 6G applications such as Artificial Intelligence (AI) and communication, enables 6G networks to provide new services (such as sensing services, AI services, and computing services). These new services can be further categorized into external services and service networks based on their target audience. Taking sensing as an example, the sensing services provided by 6G to external network functions such as application functions are called external sensing services; the sensing services provided by 6G to core network functions, radio access network function nodes, or user equipment (UE, also known as terminals) are called service networks.

[0123] The new services will generate a large amount of internal network data. This internal network data is typically transmitted to core network functions, radio access network function nodes, or UEs for use, rather than external network functions. Therefore, this type is called service network data service, also known as internal data service. Regarding network exposure, data generated by the 6G network may also be sent to external network functions such as application functions; this is called external data service.

[0124] 2. User Interface

[0125] The 5G User Plane (UP) protocol stack is shown in Figure 2. The air interface protocols between the UE and the Radio Access Network (RAN) include the Service Data Adaptation Protocol (SDAP), the Packet Data Convergence Protocol (PDCP), the Radio Link Control (RLC), the Media Access Control (MAC), and the Physical Layer (PHY). The SDAP sublayer is configured by the Radio Resource Control (RRC) (TS 38.331[3]), such as the uplink (UL) Quality of Service (QoS) flow to Data Radio Bearer (DRB) mapping rules. The SDAP sublayer maps QoS flows to DRBs. One or more QoS flows can be mapped to one DRB. In the UL, a QoS flow can only be mapped to one DRB at a time. Among them, SDAP provides the upper layer of the user plane with the service of transmitting user plane data. SDAP expects the lower layer to provide the following services:

[0126] -User plane data transmission service;

[0127] - Deliver in order unless RRC is configured to deliver out of order (TS 38.331[3]).

[0128] The SDAP Protocol Data Unit (PDU) includes data PDUs and control PDUs. Its format and parameters are detailed in TS 37.324.

[0129] Please refer to Figure 3. The main function of the core network UPF is to respond to SMF requests. As the connection point between the RAN and the data network (DN), the PDU session anchor is responsible for handling network user plane processing such as encapsulation and decapsulation of the GPRS Tunneling Protocol User Plane (GTP-U) protocol, packet routing and forwarding, packet inspection, and QoS flow mapping. It also implements policies and rules such as user plane gating, redirection, and traffic redirection. Simultaneously, it provides user traffic collection interfaces and traffic usage reports for billing and legitimate interception.

[0130] 3. Data plane

[0131] Because sensing / AI data is characterized by large volume, flexible endpoints, and flexible priorities, and because multi-UE data and UE and base station data can have their volume reduced or their quality improved through preprocessing at the base station, a data plane can be introduced in 6G networks to collect, transmit, and process the aforementioned internal network data. The data plane is a protocol stack used for data collection and transmission within the mobile network. Introducing a data plane function (DPF) in the core network, the underlying transport protocol between the RAN and the core network in 5G is either Stream Control Transmission Protocol (SCTP) / Internet Protocol (IP), GTP-U / User Datagram Protocol (UDP) / IP, or a UDP-based transport layer protocol (Quick UDP Internet Connections, QUIC) / UDP / IP, etc.

[0132] Figure 4 shows a data plane protocol stack between a UE and the network, which includes functions such as forwarding data via the core network DPF.

[0133] 4. Sensing Data

[0134] Sensing data is generated by the UE or base station and can also be called sensing measurement data or sensing result.

[0135] Regarding sensing measurement data, one possible classification method is to divide the sensing measurements into the following four categories (this description focuses on the measurement quantities; it can also be divided into three categories or no classification, etc.; the four categories are for illustrative purposes only). Based on the relationship between sensing measurements and sensing services, the third and fourth level measurements below are often also referred to as sensing results. The measurement results of the second level measurements and / or the first level measurements are also referred to as sensing measurement data.

[0136] a) First-level measurement quantities (received signal / raw channel information), including at least one of the following: complex result of received signal / channel response, amplitude / phase, I-channel / Q-channel and its operation results (operations include: addition, subtraction, multiplication, division, matrix addition, subtraction, multiplication, matrix transpose, trigonometric operations, square root operations and power operations, etc., as well as threshold detection results, maximum / minimum value extraction results, etc. of the above operation results; operations also include Fast Fourier Transform (FFT) / Inverse Fast Fourier Transform (IFFT), Discrete Fourier Transform (DFT) / Inverse Discrete Fourier Transform (IDFT), 2D-FFT, 3D-FFT, matched filtering, autocorrelation operation, wavelet transform and digital filtering, etc., as well as threshold detection results, maximum / minimum value extraction results, etc. of the above operation results);

[0137] b) Second-level measurements (basic measurements), including at least one of the following: time delay, Doppler, angle, signal strength, and their multidimensional combined representations;

[0138] c) Third-level measurements (basic attributes / states), including at least one of the following: distance, velocity, angle / orientation, radar cross section (RCS), and acceleration;

[0139] d) Level 4 measurement quantities (advanced attributes / states), including at least one of the following: spatial location, presence of target, trajectory, action, expression, vital signs, quantity, imaging results, weather, air quality, shape, material, and composition.

[0140] The following description, in conjunction with the accompanying drawings, details the PDU session establishment or modification method, terminal, network-side device, and storage medium provided in this application embodiment through some embodiments and application scenarios.

[0141] To address the challenges of transmitting new service data within the network, including but not limited to the inability to terminate at radio access network (RAN) functional nodes, the inability to support higher or lower priorities compared to existing user plane data, the inability to map new service QoS flows or tasks to multiple DRBs, and the additional latency caused by UPF processing and forwarding, improvements to existing user plane protocols are needed to meet the following requirements for new service data: transmission of data packets encapsulated using IP protocols, transmission of data packets encapsulated using non-IP protocols, new service data flow identification and flow mapping, flexible prioritization, and flexible endpoints. Simultaneously, since new service data is intra-network data, unnecessary forwarding nodes or protocol functions within the network should be reduced to improve the efficiency of new service data transmission.

[0142] Please refer to Figure 5. This embodiment of the application provides a method for establishing or modifying a PDU session, including:

[0143] Step S11: The terminal receives a first request, which is used to request the establishment or modification of a first PDU session for a new service;

[0144] Optionally, the first request is sent by a new service function node. The new service function node can be a Data Plane Function (DPF), Sensing Function (SF), Artificial Intelligence Function (AIF), Computing Function (CF), Artificial Intelligence Control Function (AICF), Computing Control Function (CCF), NET for AIF (for external services), NET for AI (for internal services, such as Network Data Analytics Function (NWDAF)), NET for Computing (NETforCF), NET for Computing (Cfor NETF) (for internal services), NET for Sensing (for internal services), or NET for Sensing (for external services). In some embodiments, the new service function node can be an SMF or an enhanced SMF.

[0145] Optionally, the new service type includes at least one of the following: perception service, AI service, computing service, external perception service, internal perception service, external AI service, internal AI service, external computing service, internal computing service, AI model, AI training, and AI inference.

[0146] Step S12: The terminal sends a first response to the first request, the first response being used to indicate whether the first PDU session was successfully established or modified.

[0147] In this embodiment of the application, the establishment or modification process of the PDU session of the new service is triggered by the new service function node, thereby completing the establishment or modification of the PDU session of the new service.

[0148] In some embodiments, optionally, the first request includes at least one of the following information elements:

[0149] New service PDU session indication, used to indicate that the first PDU session is used for a new service;

[0150] A new service PDU session identifier is used to identify the first PDU session;

[0151] New service type, used to indicate the type of the new service;

[0152] New service PDU session type, used to indicate the type of the first PDU session;

[0153] Terminal identifier, also known as terminal address, is used to identify the terminal participating in the new service; for example, when the new service PDU session type is IPv4, IPv6, or IPv4v6, the terminal identifier is the IP address and prefix(es). When the new service PDU session type is a 3GPP protocol, the terminal identifier is the identifier assigned to the terminal by the new service function node, or the identifier assigned to the terminal by the access and mobility management function.

[0154] The task identifier, also known as the new service flow identifier, is used to identify the task of the first PDU session. Existing QoS flows belong to a traditional user plane service and are QoS flows for a single UE; that is, one QoS flow is mapped to at most one DRB or multiple QoS flows are mapped to one DRB. New service tasks may sometimes be associated with multiple UEs. That is, one task is mapped to one DRB or one task is mapped to multiple DRBs. When mapped to multiple DRBs, if multiple DRBs of multiple UEs are involved, then the task identifier is a single task identifier shared by all UEs.

[0155] QoS rules, also known as task rules, are used by the terminal to mark and map uplink data for the new service. For example, the QoS rule includes the mapping relationship between the new service type, the new service function node identifier, and the task identifier. The UE marks the uplink data as the corresponding task identifier according to the new service type to which the uplink data belongs and the new service function node identifier to which the UE sends the uplink data.

[0156] The priority indicator, which can be a task-level parameter or a new service PDU session-level parameter, is used to indicate the priority information of the first PDU session or the tasks within the first PDU session. For example, when the priority indicator is a task-level parameter, it indicates whether the data for the task is high-priority or low-priority business data. When the priority indicator is a PDU session-level parameter, it indicates whether the data for the new service PDU session is high-priority or low-priority business data.

[0157] The RAN termination indication, which can be a session-level parameter or a task-level parameter for a new serving PDU, indicates whether the first PDU session or its task is resolved by the Radio Access Network Functional Node (RANFNode). By configuring the RANFNode to indicate whether data is terminated, the terminal sends the RAN termination indication to the RANFNode via the SDAP header, offering greater flexibility.

[0158] In some embodiments, optionally, the type of the new service includes at least one of the following: perception service, AI service, computing service, external perception service, internal perception service, external AI service, internal AI service, external computing service, internal computing service, AI model, AI training, and AI inference.

[0159] In some embodiments, optionally, the new service PDU session type includes one of the following: IPv4, IPv6, IPv4v6, and 3GPP protocols (such as location protocols, sensing protocols, or AI protocols).

[0160] In some embodiments, optionally, the priority indication includes at least one of the following: a high-priority indication and a low-priority indication. The high-priority indication is used to indicate whether the priority of data from the first PDU session or the task of the first PDU session is higher than that of non-new service data. For example, external AI services or computing services are geared towards low-latency scenarios, therefore the corresponding AI services or computing services should have a higher priority to ensure that the AI ​​services or computing services provided by 6G have higher service quality. One example is to prioritize processing data packets for this task, and then process other data packets when there are no indicated higher-priority data packets. The low-priority indication is used to indicate whether the priority of data from the first PDU session or the task of the first PDU session is lower than that of the non-new service data. For example, in scenarios such as external AI training data or non-real-time sensing data (such as sensing measurement data required for long-term environmental reconstruction), these data do not have short-term transmission requirements and can be transmitted when network resources are idle, so as to facilitate more reasonable scheduling and use of 6G transmission resources. One example is to process the indicated lower-priority data packets when there are no other data packets.

[0161] Optionally, the non-new service data refers to other user plane data besides new service data. The non-new service data can also be referred to as existing user plane data or external network user data. The existing user plane data can be voice service data or short messages from the IP Multimedia Subsystem (IMS), or application data from over-the-top (OTT) services (such as WeChat data, short video application data, etc.). In this embodiment, the first operation described above is compatible with existing user plane data in addition to new service data, thus supporting the transmission of both new service data and existing user plane data simultaneously.

[0162] The new service data, also known as network internal user data, may include at least one of the following: perception data, AI data, or computational data. Perception data includes at least the perception data obtained by the UE or base station through perception measurements. AI data may include at least one of the following: AI models, AI training data, AI inference data, etc. AI model data includes parameters of known model structures or new models and parameters. Regarding AI data or computational data, when the mobile communication network provides AI services or computational services for application functions deployed on terminals or application servers, we refer to it as NETforAI or NETforComputing data, or external AI or external computational service data. The main difference between external AI service data or external computational service data and existing cloud computing is that the AI ​​nodes or computational nodes providing the service are located within the mobile network. Regarding AI data or computational data, when the mobile communication network provides AI services or computational services to the UE or network (such as base stations, core network function nodes, or network management functions), we refer to it as AIforNET or ComputingforNET data, or internal AI or internal computational service data. Internal AI service data or internal computational service data is typically generated by the aforementioned internal nodes of the mobile communication network, and the data is transmitted to the internal nodes of the mobile network.

[0163] In some embodiments, optionally, the priority indication includes at least one of the following: a high priority indication and a low priority indication, wherein the high priority indication is used to indicate whether the data of the first PDU session or the task of the first PDU session has the highest priority, and the low priority indication is used to indicate whether the data of the first PDU session or the task of the first PDU session has the lowest priority. "Highest" or "lowest" means that the data of the first PDU session or the task data of the first PDU session has the highest or lowest priority, and the potential data range includes existing user plane data and new service data.

[0164] In some embodiments, optionally, the first response includes at least one of the following:

[0165] A new service PDU session identifier is used to identify the first PDU session;

[0166] Indication information indicating whether the first PDU session was successfully established or modified;

[0167] The reason why the first PDU session failed to be established or modified. For example, the reason why the DRB establishment failed.

[0168] In some embodiments, optionally, the PDU session establishment or modification method further includes:

[0169] The terminal receives configuration information sent by the radio access network functional node. The configuration information is used to indicate the addition of a DRB for the first PDU session. In some embodiments, the configuration information is user plane protocol sublayer (such as SDAP sublayer) configuration information.

[0170] If the SDAP entity for the first PDU session does not exist, the terminal establishes an SDAP entity for the first PDU session according to the configuration information;

[0171] The terminal sends an establishment completion message to the radio access network functional node, the establishment completion message being used to indicate that the SDAP entity has been established.

[0172] In some embodiments, optionally, the configuration information includes at least one of the following information elements:

[0173] New Service PDU Session Indicator, used to instruct the SDAP entity to use the first PDU session;

[0174] A new service PDU session identifier is used to identify the first PDU session;

[0175] SDAP header configuration information, wherein the SDAP header includes at least one of an uplink SDAP header (sdap-HeaderUL) and a downlink SDAP header (sdap-HeaderDL);

[0176] Default DRB, used to indicate whether the DRB is the default DRB;

[0177] Add a new task identifier to indicate one or more new task identifiers mapped to the DRB;

[0178] Release task identifiers, used to indicate the release of one or more task identifiers mapped to the DRB;

[0179] A start marker is used to indicate that the data SDU of the new service task indicated by the task identifier has begun to be mapped to the DRB;

[0180] An end marker is used to indicate that the data SDU of the new service task indicated by the task identifier has stopped being mapped to the DRB.

[0181] In some embodiments, optionally, the SDAP header includes at least one of the following information elements:

[0182] New service data indication is used to indicate whether the SDAP PDU is new service data;

[0183] New service type, used to indicate the type of new service;

[0184] User plane data type, used to indicate the user plane data type of the SDAP PDU;

[0185] Next-hop node type, used to indicate the type of the next-hop node after the SDAP PDU is transmitted to the RAN device;

[0186] Priority indicator, used to indicate the priority information of the SDAP PDU;

[0187] Task identifier, used to identify new service tasks;

[0188] RAN termination indication is used to indicate whether the SDAP PDU has been resolved by the RAN device;

[0189] An extension header indicator is used to indicate whether the information unit following the extension header indicator needs to be parsed.

[0190] The next-hop node address is used to indicate the next-hop node address of the SDAP PDU;

[0191] Destination address, used to indicate the destination address of the SDAP PDU.

[0192] In some embodiments, optionally, the SDAP header configuration information includes one of the following:

[0193] Does an SDAP header exist?

[0194] The number of bits in the SDAP header;

[0195] The format name of the SDAP header.

[0196] In some embodiments, the configuration information may optionally be carried in an RRC reconfiguration message.

[0197] In some embodiments, optionally, the PDU session suggestion or modification method further includes: the terminal sending an uplink SDAP PDU, the uplink SDAP PDU carrying a first information element, the first information element including the information element not carried in the first request and the configuration information.

[0198] For example, if neither the first request nor the configuration information carries a RAN termination indication, the uplink SDAP PDU may carry a RAN termination indication to instruct the radio access network device to parse the uplink SDAP PDU. If the uplink SDAP PDU is a data PDU, the first information element is carried in the SDAP header of the uplink SDAP PDU.

[0199] In some embodiments, optionally, the first request includes the QoS rule and the task identifier, and the method further includes:

[0200] The terminal stores the QoS rules;

[0201] The SADP entity of the terminal marks the task identifier on the uplink data of the task of the first PDU session according to the QoS rules, and maps the uplink data to the DRB of the first PDU session.

[0202] In some embodiments, optionally, the PDU session establishment or modification method further includes:

[0203] The terminal reports terminal capability information, which includes whether the terminal supports the new service.

[0204] Please refer to Figure 6. This application embodiment also provides a method for establishing or modifying a PDU session, including:

[0205] Step S21: The new service function node sends a first request; the first request is used to request the establishment or modification of a first PDU session for the new service.

[0206] In this embodiment of the application, the new service function node can trigger the establishment or modification of the first PDU session for the terminal.

[0207] In some embodiments, optionally, the new service function node can select a terminal that can participate in the new service based on the new service requirements (e.g., perception requirements, AI model transmission requirements, or AI training data collection requirements) and terminal capability information, and send the first request to the selected terminal.

[0208] In some embodiments, optionally, a new serving function node sends a first request via a Non-Access Stratum (NAS) message, in which case the NAS message needs to be forwarded to the radio access network function node and the terminal via the Access and Mobility Management function. Alternatively, another method is for the new serving function node to obtain the terminal's radio access network function node information and directly send the message to the radio access network function node and the terminal.

[0209] Optionally, the new service function node may be a Data Plane Function (DPF), a Sensing Function (SF), an AI Function (AIF), a Computing Function (CF), an AI Service Control Function (AICF), a Computing Control Function (CCF), an external service AI function (NETforAIF), an internal service AI function (such as a Network Data Analytics Function (NWDAF)), an external service computing function (NET for Computing function, NETforCF), an internal service computing function (Computing for NET function, Cfor NETF), an internal service sensing function (Sensing for NET function), or an external service sensing function (NET for Sensing function), etc.

[0210] Optionally, the radio access network functional node can be a base station (nodeB), a centralized unit (CU), a centralized unit control plane (CU-CP), or a newly introduced radio access network control unit, etc.

[0211] In some embodiments, optionally, the PDU session suggestion or modification method further includes: the new service function node sending a third request to the radio access network function node, the third request being used to instruct the radio access network function node to configure a DRB for the terminal for the first PDU session.

[0212] In some embodiments, optionally, the interface between the new service function node and the radio access network function node is a D1 interface, and the third request is sent through the D1 interface.

[0213] Optionally, the new service function node may directly send the third request to the radio access network function node, or it may forward it through the access and mobility management function.

[0214] Optionally, the new service function node can send the first request and the third request separately through two messages, or it can send the first request and the third request to the radio access network function node through the same message, and the radio access network function node will send the first request to the terminal.

[0215] In some embodiments, optionally, the first request includes at least one of the following information elements:

[0216] New service PDU session indication, used to indicate that the first PDU session is used for a new service;

[0217] A new service PDU session identifier is used to identify the first PDU session;

[0218] New service type, used to indicate the type of the new service;

[0219] New service PDU session type, used to indicate the type of the first PDU session;

[0220] Terminal identifier, used to identify the terminal for the new service;

[0221] Task identifier, used to identify the task of the first PDU session;

[0222] QoS rules are used by the terminal to mark and map the uplink data of the new service;

[0223] Priority indicator, used to indicate priority information of the first PDU session or the task of the first PDU session.

[0224] In some embodiments, optionally, the third request includes at least one of the following:

[0225] New service PDU session indication, used to indicate that the first PDU session is used for a new service;

[0226] A new service PDU session identifier is used to identify the first PDU session;

[0227] New service type, used to indicate the type of the new service;

[0228] New service PDU session type, used to indicate the type of the first PDU session;

[0229] QoS summary, used by the radio access network functional node to perform the mapping between the tasks of the first PDU session and the DRB;

[0230] Task identifier, used to identify the task of the first PDU session;

[0231] Maximum transmission delay, used to indicate the maximum transmission delay of the first PDU session or the task of the first PDU session;

[0232] Minimum bit rate, used to indicate the minimum bit rate of the first PDU session or the task of the first PDU session;

[0233] Minimum time window, used to indicate the time interval for statistical analysis of the maximum transmission delay and / or minimum bit rate;

[0234] Priority indicator, used to indicate the priority information of the first PDU session or the task of the first PDU session;

[0235] The RAN termination indication, which can be a task-level parameter or a new service PDU session-level parameter, is used to indicate whether the second PDU session or its task is parsed by the radio access network function node. For example, if the new service is an internal sensing service (SensingforNET) or an internal AI service (AIforNET), the sensing data or AI data may be sent to the base station, which then parses it for base station-assisted channel estimation, beam management, or fine-tuning of the AI ​​model. Another example is if the new service is an external sensing service (NETforSensing), the UE sensing data is processed by the base station before being sent to the core network sensing function. In this embodiment, if the second request includes the RAN termination indication, the termination at the radio access network function node is transparent to the UE. The radio access network function node determines whether it needs to parse the data of the second PDU session or the task data of the second PDU session based on the configuration of the new service function node.

[0236] The next-hop node type can be a task-level parameter or a new service PDU session-level parameter, used to indicate the next-hop node type after the uplink data of the second PDU session or the task of the second PDU session is transmitted to the radio access network function node; optionally, the next-hop node type includes user plane function (UPF), data plane function (DPF), or new service function (such as sensing function, AI function, or computing function, etc.). If there is no next-hop node type in the second request, the default next-hop node is the new service function node.

[0237] The next-hop node address, which can be a task-level parameter or a new service PDU session-level parameter, indicates the next-hop node address of the data for the second PDU session or the task of the second PDU session. When the new service PDU session type is IPv4, IPv6, or IPv4v6, the next-hop node address may include an IP address and / or a port number. When the new service PDU session type is a 3GPP protocol, the next-hop node address may be a network function identifier, such as the identifier of a new service function node or a UPF ID.

[0238] The destination address, which can be a task-level parameter or a new service PDU session-level parameter, indicates the destination address of the data for the second PDU session or the task of the second PDU session. When the new service PDU session type is IPv4, IPv6, or IPv4v6, the destination address may include an IP address and / or a port number. When the new service PDU session type is a 3GPP protocol, the destination address may be an identifier of the core network functional node, such as the identifier of the new service functional node or a UPF ID.

[0239] In some embodiments, optionally, the type of the new service includes at least one of the following: perception service, AI service, computing service, external perception service, internal perception service, external AI service, internal AI service, external computing service, internal computing service, AI model, AI training, and AI inference.

[0240] In some embodiments, optionally, the new service PDU session type includes one of the following: IPv4, IPv6, IPv4v6, and 3GPP protocols (such as location protocols, sensing protocols, or AI protocols).

[0241] In some embodiments, optionally, the priority indication includes at least one of the following: a high priority indication and a low priority indication, wherein the high priority indication is used to indicate whether the priority of the data of the new service PDU session or the task of the new service PDU session is higher than that of the non-new service data, and the low priority indication is used to indicate whether the priority of the data of the new service PDU session or the task of the new service PDU session is lower than that of the non-new service data, wherein the new service PDU session is the first PDU session or the second PDU session;

[0242] Alternatively, the priority indication may include at least one of the following: a high priority indication and a low priority indication, wherein the high priority indication is used to indicate whether the data of the first PDU session or the task of the first PDU session has the highest priority, and the low priority indication is used to indicate whether the data of the first PDU session or the task of the first PDU session has the lowest priority.

[0243] In some embodiments, optionally, the PDU session suggestion or modification method further includes:

[0244] The new service function node obtains the terminal capability information of the terminal, including whether the terminal supports the new service;

[0245] The new service function node determines whether to select the terminal for the new service based on the terminal's terminal capability information.

[0246] In some embodiments, optionally, the PDU session suggestion or modification method further includes:

[0247] The new service function node receives a third response to the third request sent by the radio access network function node, the third response including at least one of the following:

[0248] A new service PDU session identifier is used to identify the first PDU session;

[0249] Transmission information between the new service function node and the wireless access network function node;

[0250] Indication information indicating whether the first PDU session was successfully established or modified;

[0251] The list of task identifiers accepted for the new service;

[0252] A list of task identifiers for the rejected new service;

[0253] Reasons for refusal.

[0254] In some embodiments, optionally, the PDU session suggestion or modification method further includes: if the third response indicates that the establishment or modification of the first PDU session has failed, the new service function node modifies at least one of the following in the first request: QoS rules, priority indication, and resends the modified first request, or reselects a terminal for the new service.

[0255] In some embodiments, optionally, the PDU session suggestion or modification method further includes:

[0256] The new service function node marks the downlink data of the new service with a task identifier, and sends the downlink data marked with the task identifier to the radio access network function node or the terminal.

[0257] Please refer to Figure 7. This application embodiment also provides a method for establishing or modifying a PDU session, including:

[0258] Step S31: The new service function node sends a second request to the radio access network function node, the second request being used to request the establishment or modification of a second PDU session for the new service.

[0259] In this embodiment of the application, the new service function node can trigger the establishment or modification of a second PDU session for the radio access network function node.

[0260] Optionally, the new service function node may be a Data Plane Function (DPF), a Sensing Function (SF), an AI Function (AIF), a Computing Function (CF), an AI Service Control Function (AICF), a Computing Control Function (CCF), an external service AI function (NETforAIF), an internal service AI function (such as a Network Data Analytics Function (NWDAF)), an external service computing function (NET for Computing function, NETforCF), an internal service computing function (Computing for NET function, Cfor NETF), an internal service sensing function (Sensing for NET function), or an external service sensing function (NET for Sensing function), etc.

[0261] Optionally, the radio access network functional node can be a base station (nodeB), a centralized unit (CU), a centralized unit control plane (CU-CP), or a newly introduced radio access network control unit, etc.

[0262] In some embodiments, optionally, the interface between the new service function node and the radio access network function node is a D1 interface, and the second request is sent through the D1 interface.

[0263] Optionally, the new service function node may send the second request directly to the radio access network function node, or it may forward it through the access and mobility management function.

[0264] In some embodiments, optionally, the second request includes at least one of the following:

[0265] New service PDU session indication, used to indicate that the second PDU session is used for a new service;

[0266] A new service PDU session identifier is used to identify the second PDU session;

[0267] New service type, used to indicate the type of the new service;

[0268] New service PDU session type, used to indicate the type of the second PDU session;

[0269] A task identifier is used to identify the task of the second PDU session;

[0270] The associated new service PDU session identifier is used to indicate the identifier of the terminal's first PDU session, which is associated with the second PDU session and terminated at the radio access network function node; that is, the data of the indicated UE's first PDU session needs to be sent through the second PDU session established in this procedure after being processed by the radio access network function node. One example is that the identifier of the associated first PDU session consists of the terminal identifier and the terminal's new service PDU session identifier.

[0271] The associated task identifier is used to indicate the identifier of the task of the terminal's first PDU session, which is associated with the second PDU session and terminated at the radio access network functional node. That is, the data of the task in the indicated UE's first PDU session needs to be sent through the second PDU session established in this procedure after processing by the radio access network functional node. When the associated task identifier is used together with the aforementioned associated new service PDU session identifier, one example is that the associated task identifier is the task identifier in the aforementioned associated new service PDU session. When the associated task identifier is used alone, one example is that the associated task identifier consists of the terminal identifier, the terminal's new service PDU session identifier, and the task identifier.

[0272] In some embodiments, optionally, the type of the new service includes at least one of the following: perception service, AI service, computing service, external perception service, internal perception service, external AI service, internal AI service, external computing service, internal computing service, AI model, AI training, and AI inference.

[0273] In some embodiments, optionally, the new service PDU session type includes one of the following: IPv4, IPv6, IPv4v6, and 3GPP protocols (such as location protocols, sensing protocols, or AI protocols).

[0274] In some embodiments, optionally, the PDU session suggestion or modification method further includes:

[0275] The new service function node marks the downlink data of the new service with a task identifier, and sends the downlink data marked with the task identifier to the radio access network function node or the terminal.

[0276] Please refer to Figure 8. This application embodiment also provides a method for establishing or modifying a PDU session, including:

[0277] Step S41: The radio access network functional node receives a third request, the third request being used to instruct the radio access network functional node to configure the DRB for the first PDU session for the new service for the terminal;

[0278] Optionally, the radio access network functional node can be a base station (nodeB), a centralized unit (CU), a centralized unit control plane (CU-CP), or a newly introduced radio access network control unit, etc.

[0279] Optionally, the third request is sent by a new service function node. The new service function node may be a Data Plane Function (DPF), Sensing Function (SF), AI Function (AIF), Computing Function (CF), AI Service Control Function (AICF), Computing Control Function (CCF), External Service AI Function (NETforAIF), Internal Service AI Function (such as Network Data Analytics Function (NWDAF)), External Service Computing Function (NETforCF), Internal Service Computing Function (Computing for NET function (Cfor NETF), Internal Service Sensing Function (Sensing for NET function), or External Service Sensing Function (NET for Sensing function), etc.

[0280] Step S42: The radio access network functional node sends a third response to the third request, the third response indicating whether the first PDU session was successfully established or modified.

[0281] In this embodiment, the new service function node triggers the radio access network device to configure the DRB for the first PDU session of the new service for the terminal, thereby completing the establishment or modification of the PDU session for the terminal.

[0282] In some embodiments, optionally,

[0283] The third request includes at least one of the following:

[0284] New service PDU session indication, used to indicate that the first PDU session is used for a new service;

[0285] A new service PDU session identifier is used to identify the first PDU session;

[0286] New service type, used to indicate the type of the new service;

[0287] New service PDU session type, used to indicate the type of the first PDU session;

[0288] QoS summary, used by the radio access network functional node to perform the mapping between the tasks of the first PDU session and the DRB;

[0289] Task identifier, used to identify the task of the first PDU session;

[0290] Maximum transmission delay, used to indicate the maximum transmission delay of the first PDU session or the task of the first PDU session;

[0291] Minimum bit rate, used to indicate the minimum bit rate of the first PDU session or the task of the first PDU session;

[0292] Minimum time window, used to indicate the time interval for statistical analysis of the maximum transmission delay and / or minimum bit rate;

[0293] Priority indicator, used to indicate the priority information of the first PDU session or the task of the first PDU session;

[0294] RAN termination indication is used to indicate whether the first PDU session or the task of the first PDU session is resolved by the radio access network function node.

[0295] Next-hop node type, used to indicate the next-hop node type after the uplink data of the first PDU session or the task of the first PDU session is transmitted to the radio access network function node;

[0296] The next-hop node address is used to indicate the next-hop node address of the data of the first PDU session or the task of the first PDU session;

[0297] Destination address, used to indicate the destination address of the data of the first PDU session or the task of the first PDU session.

[0298] In some embodiments, optionally, the type of the new service includes at least one of the following: perception service, AI service, computing service, external perception service, internal perception service, external AI service, internal AI service, external computing service, internal computing service, AI model, AI training, and AI inference.

[0299] In some embodiments, optionally, the new service PDU session type includes one of the following: IPv4, IPv6, IPv4v6, and 3GPP protocols.

[0300] In some embodiments, optionally, the priority indication includes at least one of the following: a high priority indication and a low priority indication, wherein the high priority indication is used to indicate whether the priority of the data of the second PDU session or the task of the second PDU session is higher than that of the non-new service data, and the low priority indication is used to indicate whether the priority of the data of the second PDU session or the task of the second PDU session is lower than that of the non-new service data.

[0301] In some embodiments, optionally, the priority indication includes at least one of the following: a high priority indication and a low priority indication, wherein the high priority indication is used to indicate whether the data of the first PDU session or the task of the first PDU session has the highest priority, and the low priority indication is used to indicate whether the data of the first PDU session or the task of the first PDU session has the lowest priority.

[0302] In some embodiments, optionally, if no RAN termination indication is configured, the Radio Access Network Function (RAF) node allocates transmission information between the RAF and the new serving function node for the new service session. For example, if the GTP-U protocol is used between the RAF and the new serving function node, a tunnel identifier is allocated. Another example is if Quick UDP Internet Connections (QUIC) are used between the RAF and the new serving function node, a connection ID is allocated. That is, the PDU session suggestion or modification method further includes: when the first PDU session is not configured with a RAN termination indication, the RAF node allocates transmission information between the new serving function node and the RAF for the first PDU session.

[0303] In some embodiments, optionally, the third response includes at least one of the following:

[0304] A new service PDU session identifier is used to identify the first PDU session;

[0305] Transmission information between the new service function node and the wireless access network function node; for example, the aforementioned tunnel ID or connection ID;

[0306] Indication information indicating whether the first PDU session was successfully established or modified;

[0307] The list of task identifiers accepted for the new service;

[0308] A list of task identifiers for the rejected new service;

[0309] Reasons for rejection, such as insufficient resources.

[0310] In some embodiments, optionally, the PDU session suggestion or modification method further includes: the radio access network functional node determining whether a DRB needs to be added based on the third request; and when it is determined that a DRB needs to be added, sending configuration information to the terminal, wherein the configuration information is used to indicate the addition of a DRB for the first PDU session.

[0311] In some embodiments, optionally, the configuration information includes at least one of the following information elements:

[0312] New Service PDU Session Indicator, used to instruct the SDAP entity to use the first PDU session;

[0313] A new service PDU session identifier is used to identify the first PDU session;

[0314] SDAP header configuration information, wherein the SDAP header includes at least one of an uplink SDAP header and a downlink SDAP header;

[0315] Default DRB, used to indicate whether the DRB is the default DRB;

[0316] Add a new task identifier to indicate one or more new task identifiers mapped to the DRB;

[0317] Release task identifiers, used to indicate the release of one or more task identifiers mapped to the DRB;

[0318] A start marker is used to indicate that the data SDU of the new service task indicated by the task identifier has begun to be mapped to the DRB;

[0319] An end marker is used to indicate that the data SDU of the new service task indicated by the task identifier has stopped being mapped to the DRB.

[0320] In some embodiments, optionally, the SDAP header configuration information includes one of the following:

[0321] Does an SDAP header exist?

[0322] The number of bits in the SDAP header;

[0323] The format name of the SDAP header.

[0324] In some embodiments, the configuration information may optionally be sent using an RRC reconfiguration message.

[0325] Please refer to Figure 9. This application embodiment also provides a method for establishing or modifying a PDU session, including:

[0326] Step S51: The radio access network functional node receives a second request, which is used to request the establishment of a second PDU session for the new service;

[0327] Optionally, the radio access network functional node can be a base station (nodeB), a centralized unit (CU), a centralized unit control plane (CU-CP), or a newly introduced radio access network control unit, etc.

[0328] Optionally, the second request is sent by a new service function node. The new service function node may be a Data Plane Function (DPF), Sensing Function (SF), AI Function (AIF), Computing Function (CF), AI Service Control Function (AICF), Computing Control Function (CCF), External Service AI Function (NETforAIF), Internal Service AI Function (such as Network Data Analytics Function (NWDAF)), External Service Computing Function (NETforCF), Internal Service Computing Function (Computing for NET function (Cfor NETF), Internal Service Sensing Function (Sensing for NET function), or External Service Sensing Function (NET for Sensing function), etc.

[0329] Step S52: The radio access network functional node sends a second response to the second request, the second response indicating whether the second PDU session has been successfully established or modified.

[0330] In this embodiment of the application, the process of establishing or modifying the PDU session for the new service is triggered by the new service function node, thereby completing the establishment or modification of the PDU session for the new service.

[0331] In some embodiments, optionally, the second request includes at least one of the following:

[0332] New service PDU session indication, used to indicate that the second PDU session is used for a new service;

[0333] A new service PDU session identifier is used to identify the second PDU session;

[0334] New service type, used to indicate the type of the new service;

[0335] New service PDU session type, used to indicate the type of the second PDU session;

[0336] A task identifier is used to identify the task of the second PDU session;

[0337] The associated new service PDU session identifier is used to indicate the identifier of the terminal's first PDU session, which is associated with the second PDU session and terminated at the radio access network functional node;

[0338] The associated task identifier is used to indicate the identifier of the task associated with the second PDU session and terminated at the radio access network functional node of the terminal's first PDU session.

[0339] In some embodiments, optionally, the type of the new service includes at least one of the following: perception service, AI service, computing service, external perception service, internal perception service, external AI service, internal AI service, external computing service, internal computing service, AI model, AI training, and AI inference.

[0340] In some embodiments, optionally, the new service PDU session type includes one of the following: IPv4, IPv6, IPv4v6, and 3GPP protocols.

[0341] In some embodiments, optionally, the PDU session suggestion or modification method further includes:

[0342] The wireless access network functional node receives uplink data sent by the terminal;

[0343] If the task identifier of the uplink data is an associated task identifier, the radio access network function node sends the uplink data to the new service function node through the second PDU session.

[0344] Please refer to Figure 10. This embodiment of the application also provides a method for establishing or modifying a PDU session, including:

[0345] Step S61: The terminal sends a fourth request, which is used to request the establishment or modification of a third PDU session for the new service;

[0346] Step S62: The terminal receives a fourth response, which is used to indicate whether the third PDU session was successfully established or modified.

[0347] Optionally, the new service type includes at least one of the following: perception service, AI service, computing service, external perception service, internal perception service, external AI service, internal AI service, external computing service, internal computing service, AI model, AI training, and AI inference.

[0348] In this embodiment of the application, the existing process for establishing or modifying a PDU session is extended so that the terminal triggers a PDU session for the new service, thereby completing the establishment or modification of the PDU session for the new service.

[0349] In some embodiments, optionally, the fourth request includes at least one of the following:

[0350] The data network requested by the terminal is used to indicate that the data network is a new service data network;

[0351] New service type, used to indicate the type of the new service;

[0352] The PDU session request type is used to indicate that the PDU session request is a PDU session request for the new service.

[0353] Optionally, the new service type includes at least one of the following: perception service, AI service, computing service, external perception service, internal perception service, external AI service, internal AI service, external computing service, internal computing service, AI model, AI training, and AI inference.

[0354] Optionally, the new service function node may be a Data Plane Function (DPF), a Sensing Function (SF), an AI Function (AIF), a Computing Function (CF), an AI Service Control Function (AICF), a Computing Control Function (CCF), an external service AI function (NETforAIF), an internal service AI function (such as a Network Data Analytics Function (NWDAF)), an external service computing function (NET for Computing function, NETforCF), an internal service computing function (Computing for NET function, Cfor NETF), an internal service sensing function (Sensing for NET function), or an external service sensing function (NET for Sensing function), etc.

[0355] In some embodiments, optionally, the fourth response includes at least one of the following:

[0356] The QoS flow identifier of the new service;

[0357] The QoS parameters of the new service;

[0358] The new service uses the PDU session type;

[0359] RAN termination indication is used to indicate whether the data of the new service is resolved by the radio access network function node.

[0360] Please refer to Figure 11. This embodiment of the application also provides a method for establishing or modifying a PDU session, including:

[0361] Step S71: The AMF receives a fourth request from the terminal, the fourth request being used to request the establishment or modification of a third PDU session for a new service;

[0362] Step S72: The AMF selects an SMF for the terminal and sends a fifth request to the SMF, the fifth request being used to request the establishment or modification of the third PDU session.

[0363] In some embodiments, optionally, the fourth request includes at least one of the following:

[0364] The data network requested by the terminal is used to indicate that the data network is a new service data network;

[0365] New service type, used to indicate the type of the new service;

[0366] PDU session request type, used to indicate that the PDU session request is a PDU session request for the new service;

[0367] Optionally, the new service type includes at least one of the following: perception service, AI service, computing service, external perception service, internal perception service, external AI service, internal AI service, external computing service, internal computing service, AI model, AI training, and AI inference.

[0368] Optionally, the new service function node may be a Data Plane Function (DPF), a Sensing Function (SF), an AI Function (AIF), a Computing Function (CF), an AI Service Control Function (AICF), a Computing Control Function (CCF), an external service AI function (NETforAIF), an internal service AI function (such as a Network Data Analytics Function (NWDAF)), an external service computing function (NET for Computing function, NETforCF), an internal service computing function (Computing for NET function, Cfor NETF), an internal service sensing function (Sensing for NET function), or an external service sensing function (NET for Sensing function), etc.

[0369] In some embodiments, optionally,

[0370] The fifth request includes at least one of the following:

[0371] The data network requested by the terminal is used to indicate that the data network is a new service data network;

[0372] PDU session request type, used to indicate that the PDU session request is a PDU session request for the new service;

[0373] New service type, used to indicate the type of the new service;

[0374] The AMF is the name of the data network selected by the terminal;

[0375] The AMF is the identifier of the new service function node selected by the terminal.

[0376] Please refer to Figure 12. This application embodiment also provides a method for establishing or modifying a PDU session, including:

[0377] Step S81: The SMF receives the AMF's fifth request; the fifth request is used to request the establishment or modification of a third PDU session for a new service;

[0378] Step S82: The SMF selects a UPF according to the fifth request;

[0379] Optionally, UPF performs at least one of the following functions:

[0380] As an internal PDU session point for interconnection with the data network;

[0381] The transport layer supports uplink and downlink data tagging for the new service and maps the data of the new service to QoS streams;

[0382] If the new service uses a transport protocol other than GTP-U, it supports the encapsulation and decapsulation of the transport protocol on the user plane;

[0383] Assign the IP address or prefix used by the new service to the terminal.

[0384] Step S83: The SMF sends a fifth response to the terminal or the radio access network functional node, the fifth response being used to indicate whether the third PDU session has been successfully established or modified.

[0385] In some embodiments, optionally, the fifth request includes at least one of the following:

[0386] The data network requested by the terminal is used to indicate that the data network is a new service data network;

[0387] PDU session request type, used to indicate that the PDU session request is a PDU session request for the new service;

[0388] New service type, used to indicate the type of the new service;

[0389] The AMF is the name of the data network selected by the terminal;

[0390] The AMF is the identifier of the new service function node selected by the terminal.

[0391] In some embodiments, optionally, it also includes:

[0392] The SMF sends a sixth request to the UPF, the sixth request including at least one of the following:

[0393] New QoS flow UL packet detection rules;

[0394] New QoS flow DL packet detection rules;

[0395] New service access network tunnel information;

[0396] Forwarding rules.

[0397] In some embodiments, optionally, the fifth response includes at least one of the following:

[0398] The QoS flow identifier of the new service;

[0399] The QoS parameters of the new service;

[0400] The new service uses the PDU session type;

[0401] RAN termination instruction.

[0402] Please refer to Figure 13. This application embodiment also provides a method for establishing or modifying a PDU session, including:

[0403] Step S101: The radio access network functional node receives the fifth response sent by the SMF; the fifth response is used to indicate whether the third PDU session for the new service was successfully created or modified;

[0404] The fifth response includes at least one of the following:

[0405] The QoS flow identifier of the new service;

[0406] The QoS parameters of the new service;

[0407] The new service uses the PDU session type;

[0408] RAN termination indication is used to indicate whether the data of the new service is resolved by the radio access network function node.

[0409] Optionally, the PDU session establishment or modification method further includes:

[0410] If the RAN termination indication in the fifth response indicates that the data of the new service is not parsed by the Radio Access Network Function Node, or if the fifth response does not include the RAN termination indication, the Radio Access Network Function Node allocates the transmission information between the new service function node and the Radio Access Network Function Node for the third PDU session;

[0411] and / or

[0412] If the RAN termination indication in the fifth response indicates that the data of the new service is parsed by the Radio Access Network Functional Node, the Radio Access Network Functional Node sends configuration information to the terminal. The configuration information includes SDAP header configuration information, the SDAP header including at least one of an uplink SDAP header and a downlink SDAP header, and the SDAP header contains a RAN termination indication.

[0413] The following examples illustrate the PDU session establishment or modification method of this application embodiment, using specific application scenarios as examples.

[0414] Embodiment 1 of this application: A method for establishing or modifying a new service PDU session.

[0415] This embodiment primarily addresses the issue of new service function nodes triggering the establishment or modification of new service PDU sessions. During the PDU session establishment or modification process, configuration information is used to resolve the mapping between the new service session, new service tasks, and radio bearers, as well as the configuration of data endpoints and priorities. This solves the problem that existing user plane configurations cannot support new service data flow identification, mapping, flexible prioritization, and flexible endpoints. Furthermore, this embodiment configures at the level of a new service PDU session or tasks within a new service PDU session. Although this provides a larger granularity compared to Protocol Data Unit (PDU) level configuration, it incurs less overhead and is more suitable for situations with a large number of PDUs or multiple PDUs with identical configurations. Additionally, this method can reduce unnecessary user plane node (such as UPF) forwarding and processing based on new service data requirements.

[0416] Please refer to Figure 14. The PDU session establishment or modification method in this embodiment includes:

[0417] Step 0 (not shown in the figure): Optionally, the UE reports terminal capability information. The terminal capability information includes whether the UE supports the new service.

[0418] If the UE supports a new service, the new service function node selects UEs eligible to participate in the new service based on the new service requirements (e.g., perception requirements, AI model transmission requirements, or AI training data collection requirements) and terminal capability information. The new service function node obtains the UE's service access and mobility management functions and service cell information through the Access and Mobility Management Function (AMF) (if access management and mobility management functions are two separate functions, then it is the mobility management function here).

[0419] Step 1a: The new service function node sends a first request (which in this embodiment can also be called a new service PDU session establishment or modification request) to the UE. The first request is used to establish or modify a first PDU session for the new service. One method is to send the new service PDU session establishment or modification request through a Non-Access Stratum (NAS) message. In this case, the message needs to be forwarded to the Radio Access Network Function Node and the UE via the Access and Mobility Management Function. Alternatively, another method is for the new service function node to obtain the UE's Radio Access Network Function Node information and directly send the message to the Radio Access Network Function Node and the UE.

[0420] Optionally, the first request includes at least one of the following:

[0421] New service PDU session indicator, used to indicate that the first PDU session is used for a new service;

[0422] The new services PDU session identifier is used to identify the first PDU session;

[0423] New service type, used to indicate the type of the new service; optionally, the type of the new service includes at least one of the following: perception service, AI service, computing service, external perception service, internal perception service, external AI service, internal AI service, external computing service, internal computing service, AI model, AI training, AI inference.

[0424] The new service PDU session type is used to indicate the type of the first PDU session; optionally, the new service PDU session type includes one of the following: IPv4, IPv6, IPv4v6 and 3GPP protocols (such as positioning protocols, sensing protocols or AI protocols, etc.).

[0425] Terminal identifier, used to identify the UE for the new service; for example, when the new service PDU session type is IPv4, IPv6, or IPv4v6, the terminal identifier is the IP address and prefix(es). When the new service PDU session type is a 3GPP protocol, the terminal identifier is the identifier assigned to the terminal by the new service function node, or the identifier assigned to the terminal by the access and mobility management function.

[0426] The task identifier is used to identify the task of the first PDU session. Existing QoS flows belong to a traditional user plane service and are QoS flows of a single UE; that is, one QoS flow is mapped to at most one DRB or multiple QoS flows are mapped to one DRB. Tasks of new services may sometimes be associated with multiple UEs. That is, one task is mapped to one DRB or one task is mapped to multiple DRBs. When mapped to multiple DRBs, if multiple DRBs of multiple UEs are involved, then the task identifier is a single task identifier shared by multiple UEs.

[0427] QoS rules are used by the terminal to mark and map uplink data for the new service. For example, the QoS rule includes the mapping relationship between the new service type, the new service function node identifier, and the task identifier. The UE marks the uplink data as the corresponding task identifier according to the new service type to which the uplink data belongs and the new service function node identifier to which the UE sends the uplink data.

[0428] The priority indicator, which can be a task-level parameter or a new service PDU session-level parameter, is used to indicate the priority information of the first PDU session or the tasks within the first PDU session. For example, when the priority indicator is a task-level parameter, it indicates whether the data for the task is high-priority or low-priority business data. When the priority indicator is a PDU session-level parameter, it indicates whether the data for the new service PDU session is high-priority or low-priority business data.

[0429] In some embodiments, optionally, the priority indication includes at least one of the following: a high-priority indication and a low-priority indication. The high-priority indication is used to indicate whether the priority of data from the first PDU session or the task of the first PDU session is higher than that of non-new service data. For example, external AI services or computing services are geared towards low-latency scenarios, therefore the corresponding AI services or computing services should have a higher priority to ensure that the AI ​​services or computing services provided by 6G have higher service quality. One example is to prioritize processing data packets for this task, and then process other data packets when there are no indicated higher-priority data packets. The low-priority indication is used to indicate whether the priority of data from the first PDU session or the task of the first PDU session is lower than that of the non-new service data. For example, in scenarios such as external AI training data or non-real-time sensing data (such as sensing measurement data required for long-term environmental reconstruction), these data do not have short-term transmission requirements and can be transmitted when network resources are idle, so as to facilitate more reasonable scheduling and use of 6G transmission resources. One example is to process the indicated lower-priority data packets when there are no other data packets.

[0430] Step 1b: If the interface between the new Serving Function Node (NFNode) and the Radio Access Network Function Node (RAFNode) is referred to as D1, then the NFNode sends a third request (also known as a D1 interface new service / modification request) to the RAFNode via the D1 interface. The third request instructs the RAFNode to configure the DRB for the UE in the first PDU session. The NFNode may send the third request directly to the RAFNode or forward it through the Access and Mobility Management (AMM) function.

[0431] Optionally, the third request includes at least one of the following:

[0432] New service PDU session indication, used to indicate that the first PDU session is used for a new service;

[0433] A new service PDU session identifier is used to identify the first PDU session;

[0434] New service type, used to indicate the type of the new service; optionally, the type of the new service includes at least one of the following: perception service, AI service, computing service, external perception service, internal perception service, external AI service, internal AI service, external computing service, internal computing service, AI model, AI training, AI inference.

[0435] The new service PDU session type is used to indicate the type of the first PDU session; optionally, the new service PDU session type includes one of the following: IPv4, IPv6, IPv4v6 and 3GPP protocols (such as positioning protocols, sensing protocols or AI protocols, etc.).

[0436] QoS summary, used by the radio access network functional node to perform the mapping between the tasks of the first PDU session and the DRB;

[0437] Task identifier, used to identify the task of the first PDU session;

[0438] Maximum transmission latency can be a task-level parameter or a new service PDU session-level parameter, used to indicate the maximum transmission latency of the first PDU session or the task of the first PDU session.

[0439] The minimum bit rate can be a task-level parameter or a new service PDU session-level parameter, used to indicate the minimum bit rate of the first PDU session or the task of the first PDU session.

[0440] The minimum time window, which can be a task-level parameter or a new service PDU session-level parameter, is used to indicate the time interval for calculating the maximum transmission delay and / or the minimum bit rate.

[0441] Priority indication, which can be a task-level parameter or a new service PDU session-level parameter, is used to indicate the priority information of the first PDU session or the task of the first PDU session;

[0442] The RAN termination indication can be a task-level parameter or a new service PDU session-level parameter, used to indicate whether the first PDU session or the task of the first PDU session is parsed by the radio access network function node. For example, if the new service is an internal sensing service (SensingforNET) or an internal AI service (AIforNET), the sensing data or AI data may be sent to the base station, which then parses it for base station-assisted channel estimation, beam management, or fine-tuning of the AI ​​model. Another example is if the new service is an external sensing service (NETforSensing), the UE sensing data is processed by the base station before being sent to the core network sensing function. In this embodiment, if the second request includes the RAN termination indication, then the termination at the radio access network function node is transparent to the UE. The radio access network function node determines whether it needs to parse the data of the first PDU session or the task data of the first PDU session based on the configuration of the new service function node.

[0443] The next-hop node type can be a task-level parameter or a new service PDU session-level parameter, used to indicate the next-hop node type after the uplink data of the first PDU session or the task of the first PDU session is transmitted to the radio access network function node; optionally, the next-hop node type includes user plane function (UPF), data plane function (DPF), or new service function (such as sensing function, AI function, or computing function, etc.). If there is no next-hop node type in the second request, the default next-hop node is the new service function node.

[0444] The next-hop node address, which can be a task-level parameter or a new service PDU session-level parameter, indicates the next-hop node address of the data for the first PDU session or the task of the first PDU session. When the new service PDU session type is IPv4, IPv6, or IPv4v6, the next-hop node address may include an IP address and / or a port number. When the new service PDU session type is a 3GPP protocol, the next-hop node address may be a network function identifier, such as the identifier of a new service function node or a UPF ID.

[0445] The destination address is used to indicate the destination address of data for the first PDU session or the task of the first PDU session. When the new service PDU session type is IPv4, IPv6, or IPv4v6, the destination address may include an IP address and / or a port number. When the new service PDU session type is a 3GPP protocol, the destination address may be an identifier of the core network functional node, such as the identifier of the new service functional node or a UPF ID.

[0446] In this embodiment, steps 1a and 1b can be performed in any order. The new service function node can send the first request and the third request separately through two messages, or it can send the first request and the third request to the radio access network function node through the same message. The radio access network function node then sends the first request to the UE.

[0447] Step 2: The Radio Access Network (RAB) functional node receives the third request and determines whether to add a DRB. If a DRB is added, it sends user plane protocol sublayer (e.g., SDAP sublayer) configuration information to the UE. One method is to send this information to the UE via an RRC reconfiguration message.

[0448] This configuration information includes at least one of the following:

[0449] New Service PDU Session Indicator, used to instruct the SDAP entity to use the first PDU session;

[0450] A new service PDU session identifier is used to identify the first PDU session;

[0451] SDAP header configuration information, wherein the SDAP header includes at least one of an uplink SDAP header and a downlink SDAP header;

[0452] Default DRB, used to indicate whether the DRB is the default DRB;

[0453] Add a new task identifier to indicate one or more new task identifiers mapped to the DRB;

[0454] Release task identifiers, used to indicate the release of one or more task identifiers mapped to the DRB;

[0455] A start marker is used to indicate that the data SDU of the new service task indicated by the task identifier has begun to be mapped to the DRB;

[0456] An end marker is used to indicate that the data SDU of the new service task indicated by the task identifier has stopped being mapped to the DRB.

[0457] Step 3: The UE receives the configuration information. If the SDAP entity for the first PDU session does not exist, then the SDAP entity is established. The UE sends an RRC reconfiguration complete message to indicate that the SDAP entity establishment is complete.

[0458] Step 4a: If the RAN termination indication is not configured in the third request, then the Radio Access Network Functional Node (RAFNF) allocates transmission information between the RAFNF and the new Serving Functional Node for the new service session. For example, if the RAFNF and the new Serving Functional Node use the GTP-U protocol, then a tunnel identifier is allocated. Another example is if the RAFNF and the new Serving Functional Node use Quick UDP Internet Connections (QUIC), then a connection ID is allocated.

[0459] The radio access network functional node sends a third response (also known as a D1 interface new service PDU session response), which includes:

[0460] New service PDU session identifier, used to identify the first PDU session;

[0461] Transmission information between the new service function node and the wireless access network function node; for example, the aforementioned tunnel ID or connection ID;

[0462] Indication information indicating whether the first PDU session was successfully established or modified;

[0463] The list of task identifiers accepted for the new service;

[0464] A list of task identifiers for the rejected new service;

[0465] Reasons for rejection, such as insufficient resources.

[0466] If the radio access network function node rejects the new service, optionally, if the third response indicates that the establishment or modification of the first PDU session failed, the new service function node may modify at least one of the following in the first request: QoS rules, priority indication, and resend the modified first request, or reselect the terminal for the new service.

[0467] Optionally, if a third request is sent first, and the third response indicates that the establishment or modification of the first PDU session has failed, then one possibility is that the first request will not be sent again, i.e., steps 1a and 4b are not included in the accompanying drawings of this embodiment.

[0468] Step 4b: Optionally, the UE receives the first request and stores QoS rules for uplink data marking and mapping for the new service. If the UE has already established the DRB corresponding to the first PDU session, then it sends a first response to the new service function node. The first response includes at least one of the following:

[0469] A new service PDU session identifier is used to identify the first PDU session;

[0470] Indication information indicating whether the first PDU session was successfully established or modified;

[0471] The reason why the first PDU session failed to be established or modified. For example, the reason why the DRB establishment failed.

[0472] Step 5 (not shown in the figure): Optionally, if a new task (such as a task for a new service) is to be created, the new service function node will send the UL packet detection rules for the new task to the UPF. The UPF identifies the uplink new service data packets according to the received UL packet detection rules and forwards them to the new service function node.

[0473] Optionally, if a new task (such as a new service task) needs to be created, the new service function node will send the DL packet detection rules for the new task to the UPF. The UPF identifies the downlink new service data packet and the corresponding task identifier based on the received DL packet detection rules, and forwards the new service data packet to the base station based on the aforementioned transmission information (such as tunnel ID or connection ID).

[0474] Step 6: Optionally, the UE maps a task data of a new service as task identifier N according to the QoS rule, maps the task data packet to the corresponding DRB according to the RRC configuration, and submits the constructed UL SDAP data PDU to the lower layer.

[0475] Optionally, the new service function node marks the downlink new service data packet with a task identifier M and sends it to the radio access network function node. The radio access network function node maps the task packet data to the corresponding DRB according to its configuration and submits the constructed DL SDAP data PDU to the lower layer. The UE obtains the SDAP SDU according to the RRC configuration and submits it to the upper layer.

[0476] Embodiment 2 of this application: A data collection method for association between UE and base station

[0477] The new service PDU session in Implementation Example 1 is a UE-related session. Since the new service, such as sensing services or internal AI services, may also involve base stations, or data collection associated with base stations and UEs, the main solution in this embodiment is to associate the new service PDU session of the radio access network functional node with the new service PDU session of the UE through configuration information, thereby collecting data and improving data collection and transmission efficiency. This solves the problem of traditional user plane data transmission being point-to-point transmission between the UE and the UPF, supporting a more flexible transmission topology between the UE, the new service functional node, and the radio access network functional node.

[0478] Please refer to Figure 15. The method in this embodiment includes:

[0479] Step 1: The new service function node establishes or modifies the new service PDU session according to the procedure described in Example 1, so that the selected UE has a first PDU session terminated at the radio access network function node, or a task that terminates the first PDU session at the radio access network function node. For the specific procedure for establishing or modifying the first PDU session, please refer to Example 1, which will not be repeated here.

[0480] In addition to the RAN termination configuration method transparent to the UE as described in Embodiment 1, optionally, the first request sent by the new serving function node to the UE may also include a RAN termination indication. The RAN termination indication can be a session-level parameter of the new serving PDU or a task-level parameter. This method configures whether data is terminated at the radio access network function node to the UE, and the UE indicates the RAN termination indication to the radio access network function node through the SDAP header, providing greater flexibility.

[0481] When the RAN Termination Indication is a task-level parameter, one approach is for the UE to use an SDAP header containing the RAN Termination Indication (RTI) when sending the uplink data packet for that task (an example is shown in Figure 16). The Radio Access Network Functional Node can then determine whether to parse the PDU based on the RTI.

[0482] Step 2: The new Serving Function Node (NFNode) sends a second request to the Radio Access Network Function Node (RAN Function Node). If the interface between the NFNode and the RAF Function Node is called D1, the NFNode can send the second request through the D1 interface. The NFNode can send the second request directly to the RAF Function Node, or it may forward it through the Access and Mobility Management (AMM) function.

[0483] Optionally, the second request includes at least one of the following:

[0484] New service PDU session indication, used to indicate that the second PDU session is used for a new service;

[0485] A new service PDU session identifier is used to identify the second PDU session;

[0486] New service type, used to indicate the type of the new service; optionally, the type of the new service includes at least one of the following: perception service, AI service, computing service, external perception service, internal perception service, external AI service, internal AI service, external computing service, internal computing service, AI model, AI training, AI inference.

[0487] The new service PDU session type is used to indicate the type of the second PDU session; optionally, the new service PDU session type includes one of the following: IPv4, IPv6, IPv4v6.

[0488] A task identifier is used to identify the task of the second PDU session;

[0489] The associated new service PDU session identifier is used to indicate the identifier of the terminal's first PDU session, which is associated with the second PDU session and terminated at the radio access network function node; that is, the data of the indicated UE's first PDU session needs to be sent through the second PDU session established in this procedure after being processed by the radio access network function node. One example is that the identifier of the associated first PDU session consists of the UE identifier and the UE's new service PDU session identifier.

[0490] The associated task identifier is used to indicate the identifier of the task of the terminal's first PDU session, which is associated with the second PDU session and terminated at the radio access network functional node. That is, the data of the task in the indicated UE's first PDU session needs to be sent through the second PDU session established in this procedure after processing by the radio access network functional node. When the associated task identifier is used together with the aforementioned associated new service PDU session identifier, one example is that the associated task identifier is the task identifier in the aforementioned associated new service PDU session. When the associated task identifier is used alone, one example is that the associated task identifier consists of the UE identifier, the UE's new service PDU session identifier, and the task identifier.

[0491] Step 3: The Radio Access Network (RAN) Functional Node (RAN) receives the second request and allocates transmission information between the RAVN and the new Serving Functional Node for the second PDU session. For example, if the RAVN and the new Serving Functional Node use the GTP-U protocol, then a tunnel identifier is allocated. Or, if the RAVN and the new Serving Functional Node use Quick UDP Internet Connections (QUIC), then a connection ID is allocated.

[0492] The radio access network functional node sends a second response, which includes:

[0493] A new service PDU session identifier is used to identify the second PDU session;

[0494] Transmission information between the new service function node and the wireless access network function node; for example, the aforementioned tunnel ID or connection ID;

[0495] Indication information indicating whether the second PDU session was successfully established or modified;

[0496] Reasons for rejection, such as insufficient resources.

[0497] Step 4: Optionally, the UE marks a task data mapping of the new service as task identifier N according to the configuration information in the new service PDU session establishment or modification process, and maps the task data packet to the corresponding DRB according to the RRC configuration, and submits the constructed UL SDAP data PDU to the lower layer.

[0498] Optionally, the radio access network function node obtains the SDAP SDU from the SDAP PDU of the task packet N sent by the UE according to the configuration. After processing it according to the associated task identifier in step 2, it sends the second PDU session established through this procedure to the new serving function node.

[0499] Embodiment 3 of this application: A new service transport configuration method based on PDU session establishment enhancement

[0500] Since new services, such as perception services or internal AI services, are typically triggered by new service function nodes, Implementation 1 involves the new service function node triggering the establishment or modification of a new service PDU session, thereby configuring the data transmission of the new service PDU session between the radio access network function node and the UE. This implementation, however, enhances the messages in the existing UE-triggered PDU session establishment or modification process to support the data transmission requirements of new services such as external AI services or computing services. This implementation also addresses the issue of existing user planes not supporting new service data transmission requirements, while maximizing the reuse of existing user plane PDU session procedures.

[0501] It should be noted that this embodiment focuses on explaining the differences from the existing PDU session establishment or modification process.

[0502] Step 1: The UE sends a fourth request (PDU session establishment request) to the AMF. The fourth request is used to request the establishment or modification of a third PDU session for the new service.

[0503] The fourth request (PDU session establishment request) includes at least one of the following: Single Network Slice Selection Assistance Information(s), S-NSSAI(s), UE Requested DNN, PDU Session ID, Request type, Old PDU Session ID, and N1 SM container (PDU Session Establishment Request [Port Management Information Container]).

[0504] In some embodiments, optionally, the data network requested by the terminal in the fourth request (UE Requested DNN) indicates that the data network is a new service data network. For example, one method uses the UE Requested DNN to indicate that the data network name is the new service, such as NSNET as the DNN.

[0505] In some embodiments, optionally, the fourth request may further include: a PDU session request type, used to indicate that the PDU session request is a PDU session request for the new service. For example, one method indicates that the PDU session type is a PDU session for the new service by setting the Request Type to new services.

[0506] Step 2: When the data network requested by the UE in the fourth request indicates a new service or the Request Type indicates a new service, the AMF determines that the PDU session ID of the requested third PDU session is not used by the UE's existing PDU session, selects a suitable SMF, such as an SMF that supports the new service requested by the UE, and sends a fifth request (such as PDU session creation information) to the SMF. Optionally, the AMF selects a suitable new service function node, such as a new service function node that supports the new service requested by the UE. If the fourth request does not include the data network requested by the UE, then the AMF selects a data network for the UE, such as the new service data network mentioned above. The fifth request includes at least one of the following:

[0507] The UE-Requested DNN is used to indicate that the data network is a new service data network; for example, one method uses the UE-Requested DNN to indicate that the data network name is a new service.

[0508] The PDU session request type is used to indicate that the PDU session request is a PDU session request for the new service; for example, one method indicates that the PDU session type is a PDU session for the new service by setting the Request Type to new services.

[0509] New service type, used to indicate the type of the new service;

[0510] The AMF is the name of the data network selected by the terminal to support new UE services, such as the aforementioned new service data network;

[0511] The AMF is the identifier of the new service function node selected by the terminal.

[0512] Step 3: The SMF receives the fifth request (PDU session creation information) and selects the appropriate UPF;

[0513] The UPF is capable of performing at least one of the following functions:

[0514] As an internal PDU session point for interconnection with the data network;

[0515] The transport layer supports uplink and downlink data tagging for the new service and maps the data of the new service to QoS streams;

[0516] If the new service uses a transport protocol other than GTP-U (such as QUIC), it supports encapsulation and decapsulation of the transport protocol on the user plane;

[0517] Assign the IP address or prefix used by the new service to the UE.

[0518] Step 4: The SMF sends a fifth response (N1N2MessageTransfer) to the AMF, which then forwards it to the base station and the UE. The fifth response sent to the base station or UE includes at least one of the following:

[0519] The QoS flow identifier of the new service; for example, assigning a QFI to the AI ​​service for the scheduling of transmission resources of the AI ​​service to optimize service quality.

[0520] The QoS parameters for the new service include, for example, introducing new resource types for AI services (such as computation speed guarantees or computation intensity guarantees). Priority types, for instance, indicate whether the QoS has a higher, lower, or the same priority than existing user plane data QoS.

[0521] The new service uses a PDU session type; for example, "PDU Session Type" indicates that the PDU session type is a PDU session for the new service, or indicates a 3GPP-defined protocol for the new service, such as a positioning protocol, a sensing protocol, or an AI protocol.

[0522] RAN termination indication is used to indicate whether the data of the new service is resolved by the radio access network function node.

[0523] Step 5: The base station receives the fifth response (N1N2MessageTransfer). If the third PDU session is not configured for RAN termination, the base station allocates transmission information, such as tunnel information, between the Radio Access Network Functional Node (RANF) and the New Serving Functional Node (NSF) for the third PDU session. If the third PDU session is configured for RAN termination, or if the QoS flow of the third PDU session is configured for RAN termination, the base station configures the UE to use an appropriate SDAP header (which contains a RAN termination indication) via RRC. The base station sends an N2 session response message to the AMF and SMF. The N2 session response message includes at least one of the following:

[0524] The PDU session identifier used for new services, i.e., the third PDU session identifier;

[0525] The base station uses tunnel information, such as the tunnel ID, for transmitting new services;

[0526] The list of accepted QFIs for the new service;

[0527] List of QFIs rejected for new services;

[0528] Reasons for rejection, such as insufficient resources.

[0529] If the base station rejects the QFI for the new service, the SMF determines whether the QoS rules or QoS flow level parameters for the new service need to be updated. If an update is required, the SMF is responsible for updating the QoS rules and QoS flow level parameters for the new service to match the QoS rules in the UE and the associated PDU session for the new service.

[0530] Step 6: Optionally, if the aforementioned N2 interface message indicates that PDU session establishment or modification failed, then the SMF sends a rejection message containing the PDU session establishment or modification information to the UE. This message is typically sent to the UE via the N2 interface and the N1 session management container.

[0531] Step 7: Optionally, if a new QoS flow is to be created (such as a QoS flow for a new service), the SMF will send the UL packet detection rules for the new QoS flow to the UPF. The UPF identifies the uplink new service packets according to the received UL packet detection rules and forwards them to the new service function node.

[0532] Optionally, if a new QoS flow (such as a QoS flow for a new service) needs to be created, the SMF will send the DL packet detection rules for the new QoS flow to the UPF. The UPF will identify the downlink new service data packet and mark the corresponding QFI according to the received DL packet detection rules, and forward the new service data packet to the base station based on the aforementioned tunnel ID and other transmissions.

[0533] Optionally, the SMF sends new service access network tunnel information and forwarding rules to the UPF. For example, in uplink transmission, the forwarding rule is to forward the data packets of the new service transmitted by the PDU session to the aforementioned new service function node. Alternatively, in downlink transmission, the forwarding rule is to forward the data packets of the new service transmitted by the PDU session to the base station. For example, message sending can be established or modified through an N4 session.

[0534] Step 8: Optionally, the UE sends new service uplink data through the established third PDU session, or the new service function node sends new service downlink data through the established third PDU session.

[0535] In this embodiment, user plane configuration enhancement enables the user plane protocol to support not only existing user plane data transmission but also new 6G service data transmission. User plane configuration enhancement includes adding new service PDU session establishment, base station new service PDU session establishment, existing PDU session enhancement, and SDAP configuration enhancement (optionally including enhanced SDAP header). User plane configuration enhancement meets the requirements of new service data and can support new service configurations at the session or task level. This method, through control plane configuration, is more suitable for situations with a large number of PDUs or multiple PDUs with identical configurations, thereby solving problems encountered when transmitting new service data through the existing user plane, including but not limited to the inability to terminate at the radio access network functional node, the inability to support higher or lower priorities than existing user plane data, the inability to map new service QoS flows or tasks to multiple DRBs, and the additional latency caused by UPF processing and forwarding. Furthermore, this method can also be used with a new SDAP header to support packet-level configuration on top of session-level or task-level configuration.

[0536] The PDU session establishment or modification method provided in this application can be executed by a PDU session establishment or modification device. This application uses the execution of the PDU session establishment or modification method by a PDU session establishment or modification device as an example to illustrate the PDU session establishment or modification device provided in this application.

[0537] This application provides a PDU session establishment or modification apparatus. As an example, the PDU session establishment or modification apparatus can be a communication device or a component within a communication device, such as a chip. The communication device can be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal can be, but is not limited to, the type of terminal 11 listed above, and the network-side device can be, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0538] The PDU session establishment or modification apparatus includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, etc., such as central processing units (CPUs), microprocessors, digital signal processors (DSPs), artificial intelligence (AI) processors, graphics processing units (GPUs), application-specific integrated circuits (ASICs), network processors (NPs), field-programmable gate arrays (FPGAs), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceivers, pins, circuits, buses, radio frequency units, etc.

[0539] In some embodiments, referring to FIG17, when the PDU session establishment or modification device is a terminal or a component in a terminal, the PDU session establishment or modification device 10 includes a receiving module 11 for receiving a first request, the first request being for requesting the establishment or modification of a first PDU session for a new service; and a sending module 12 for sending a first response to the first request, the first response being for indicating whether the first PDU session has been successfully established or modified.

[0540] Optionally, the first request includes at least one of the following information elements:

[0541] New service PDU session indication, used to indicate that the first PDU session is used for a new service;

[0542] A new service PDU session identifier is used to identify the first PDU session;

[0543] New service type, used to indicate the type of the new service;

[0544] New service PDU session type, used to indicate the type of the first PDU session;

[0545] Terminal identifier, used to identify the terminal participating in the new service;

[0546] Task identifier, used to identify the task of the first PDU session;

[0547] QoS rules are used by the terminal to mark and map the uplink data of the new service;

[0548] Priority indicator, used to indicate the priority information of the first PDU session or the task of the first PDU session;

[0549] RAN termination indication is used to indicate whether the first PDU session or the task of the first PDU session is resolved by the radio access network function node.

[0550] Optionally, the new service type includes at least one of the following: perception service, AI service, computing service, external perception service, internal perception service, external AI service, internal AI service, external computing service, internal computing service, AI model, AI training, and AI inference.

[0551] Optionally, the new service PDU session type includes one of the following: IPv4, IPv6, IPv4v6, and 3GPP protocol.

[0552] Optionally, the priority indication includes at least one of the following: a high priority indication and a low priority indication, wherein the high priority indication is used to indicate whether the priority of the data of the first PDU session or the task of the first PDU session is higher than that of the non-new service data, and the low priority indication is used to indicate whether the priority of the data of the first PDU session or the task of the first PDU session is lower than that of the non-new service data.

[0553] Alternatively, the priority indication may include at least one of the following: a high priority indication and a low priority indication, wherein the high priority indication is used to indicate whether the data of the first PDU session or the task of the first PDU session has the highest priority, and the low priority indication is used to indicate whether the data of the first PDU session or the task of the first PDU session has the lowest priority.

[0554] Optionally, the first response includes at least one of the following:

[0555] A new service PDU session identifier is used to identify the first PDU session;

[0556] Indication information indicating whether the first PDU session was successfully established or modified;

[0557] The reason why the first PDU session failed to be established or modified.

[0558] Optionally, the receiving module 11 is further configured to receive configuration information sent by the radio access network functional node, the configuration information being used to indicate the addition of a DRB for the first PDU session;

[0559] The PDU session establishment or modification device 10 further includes:

[0560] The processing module is configured to, if the SDAP entity for the first PDU session does not exist, establish an SDAP entity for the first PDU session according to the configuration information;

[0561] The sending module 12 is also used to send establishment completion information to the radio access network functional node, the establishment completion information being used to indicate that the SDAP entity has been established.

[0562] Optionally, the configuration information includes at least one of the following information elements:

[0563] New Service PDU Session Indicator, used to instruct the SDAP entity to use the first PDU session;

[0564] A new service PDU session identifier is used to identify the first PDU session;

[0565] SDAP header configuration information, wherein the SDAP header includes at least one of an uplink SDAP header and a downlink SDAP header;

[0566] Default DRB, used to indicate whether the DRB is the default DRB;

[0567] Add a new task identifier to indicate one or more new task identifiers mapped to the DRB;

[0568] Release task identifiers, used to indicate the release of one or more task identifiers mapped to the DRB;

[0569] A start marker is used to indicate that the data SDU of the new service task indicated by the task identifier has begun to be mapped to the DRB;

[0570] An end marker is used to indicate that the data SDU of the new service task indicated by the task identifier has stopped being mapped to the DRB.

[0571] Optionally, the SDAP header configuration information includes one of the following:

[0572] Does an SDAP header exist?

[0573] The number of bits in the SDAP header;

[0574] The format name of the SDAP header.

[0575] Optionally, the configuration information is carried in an RRC reconfiguration message.

[0576] Optionally, the sending module 12 is further configured to send an uplink SDAP PDU, the uplink SDAP PDU carrying a first information unit, the first information unit including the information unit not carried in the first request and the configuration information.

[0577] Optionally, the sending module 12 is further configured to report terminal capability information, including whether the terminal supports the new service.

[0578] Referring to Figure 18, when the PDU session establishment or modification device is a network-side device or a component of a network-side device, the PDU session establishment or modification device 20 includes a sending module 21, which is used to send a first request to the terminal; the first request is used to request the establishment or modification of a first PDU session for a new service; or, to send a second request to the radio access network functional node; the second request is used to request the establishment or modification of a second PDU session for a new service.

[0579] The first request includes at least one of the following information elements:

[0580] New service PDU session indication, used to indicate that the first PDU session is used for a new service;

[0581] A new service PDU session identifier is used to identify the first PDU session;

[0582] New service type, used to indicate the type of the new service;

[0583] New service PDU session type, used to indicate the type of the first PDU session;

[0584] Terminal identifier, used to identify the terminal for the new service;

[0585] Task identifier, used to identify the task of the first PDU session;

[0586] QoS rules are used by the terminal to mark and map the uplink data of the new service;

[0587] Priority indicator, used to indicate priority information of the first PDU session or the task of the first PDU session.

[0588] Optionally, the sending module 21 is further configured to send a third request to the radio access network function node, the third request being used to instruct the radio access network function node to configure a DRB for the terminal for the first PDU session.

[0589] Optionally, the third request includes at least one of the following:

[0590] New service PDU session indication, used to indicate that the first PDU session is used for a new service;

[0591] A new service PDU session identifier is used to identify the first PDU session;

[0592] New service type, used to indicate the type of the new service;

[0593] New service PDU session type, used to indicate the type of the first PDU session;

[0594] QoS summary, used by the radio access network functional node to perform the mapping between the tasks of the first PDU session and the DRB;

[0595] Task identifier, used to identify the task of the first PDU session;

[0596] Maximum transmission delay, used to indicate the maximum transmission delay of the first PDU session or the task of the first PDU session;

[0597] Minimum bit rate, used to indicate the minimum bit rate of the first PDU session or the task of the first PDU session;

[0598] Minimum time window, used to indicate the time interval for statistical analysis of the maximum transmission delay and / or minimum bit rate;

[0599] Priority indicator, used to indicate the priority information of the first PDU session or the task of the first PDU session;

[0600] RAN termination indication is used to indicate whether the first PDU session or the task of the first PDU session is resolved by the radio access network function node.

[0601] Next-hop node type, used to indicate the next-hop node type after the uplink data of the first PDU session or the task of the first PDU session is transmitted to the radio access network function node;

[0602] The next-hop node address is used to indicate the next-hop node address of the data of the first PDU session or the task of the first PDU session;

[0603] Destination address, used to indicate the destination address of the data of the first PDU session or the task of the first PDU session.

[0604] Optionally, the second request includes at least one of the following:

[0605] New service PDU session indication, used to indicate that the second PDU session is used for a new service;

[0606] A new service PDU session identifier is used to identify the second PDU session;

[0607] New service type, used to indicate the type of the new service;

[0608] New service PDU session type, used to indicate the type of the second PDU session;

[0609] A task identifier is used to identify the task of the second PDU session;

[0610] The associated new service PDU session identifier is used to indicate the identifier of the terminal's first PDU session, which is associated with the second PDU session and terminated at the radio access network functional node;

[0611] The associated task identifier is used to indicate the identifier of the task associated with the second PDU session and terminated at the radio access network functional node of the terminal's first PDU session.

[0612] Optionally, the new service type includes at least one of the following: perception service, AI service, computing service, external perception service, internal perception service, external AI service, internal AI service, external computing service, internal computing service, AI model, AI training, and AI inference.

[0613] Optionally, the new service PDU session type includes one of the following: IPv4, IPv6, IPv4v6, and 3GPP protocol.

[0614] Optionally, the priority indication includes at least one of the following: a high priority indication and a low priority indication, wherein the high priority indication is used to indicate whether the priority of the data of the new service PDU session or the task of the new service PDU session is higher than that of the non-new service data, and the low priority indication is used to indicate whether the priority of the data of the new service PDU session or the task of the new service PDU session is lower than that of the non-new service data, wherein the new service PDU session is the first PDU session or the second PDU session;

[0615] Alternatively, the priority indication may include at least one of the following: a high priority indication and a low priority indication, wherein the high priority indication is used to indicate whether the data of the first PDU session or the task of the first PDU session has the highest priority, and the low priority indication is used to indicate whether the data of the first PDU session or the task of the first PDU session has the lowest priority.

[0616] Optionally, the PDU session establishment or modification device 20 further includes:

[0617] The processing module is configured to acquire terminal capability information of the terminal, including whether the terminal supports the new service; and determine whether to select the terminal for the new service based on the terminal capability information.

[0618] Optionally, the PDU session establishment or modification device 20 further includes:

[0619] A receiving module is configured to receive a third response to the third request sent by the radio access network functional node, wherein the third response includes at least one of the following:

[0620] A new service PDU session identifier is used to identify the first PDU session;

[0621] Transmission information between the new service function node and the wireless access network function node;

[0622] Indication information indicating whether the first PDU session was successfully established or modified;

[0623] The list of task identifiers accepted for the new service;

[0624] A list of task identifiers for the rejected new service;

[0625] Reasons for refusal.

[0626] Optionally, the PDU session establishment or modification device 20 further includes:

[0627] The processing module is configured to modify at least one of the following in the first request if the third response indicates that the establishment or modification of the first PDU session has failed: QoS rules, priority indication;

[0628] The sending module 21 is used to resend the modified first request, or to reselect a terminal for the new service.

[0629] Optionally, the sending module 21 is further configured to mark the downlink data of the new service with a task identifier, and send the downlink data marked with the task identifier to the radio access network functional node or the terminal.

[0630] Referring to Figure 19, when the PDU session establishment or modification device is a network-side device or a component in a network-side device, the PDU session establishment or modification device 30 includes a receiving module 31 for receiving a second request, the second request being used to request the establishment of a second PDU session for a new service; and a sending module 32 for sending a second response to the second request, the second response being used to indicate whether the second PDU session has been successfully established or modified.

[0631] Optionally, the second request includes at least one of the following:

[0632] New service PDU session indication, used to indicate that the second PDU session is used for a new service;

[0633] A new service PDU session identifier is used to identify the second PDU session;

[0634] New service type, used to indicate the type of the new service;

[0635] New service PDU session type, used to indicate the type of the second PDU session;

[0636] A task identifier is used to identify the task of the second PDU session;

[0637] The associated new service PDU session identifier is used to indicate the identifier of the terminal's first PDU session, which is associated with the second PDU session and terminated at the radio access network functional node;

[0638] The associated task identifier is used to indicate the identifier of the task associated with the second PDU session and terminated at the radio access network functional node of the terminal's first PDU session.

[0639] Optionally, the new service type includes at least one of the following: perception service, AI service, computing service, external perception service, internal perception service, external AI service, internal AI service, external computing service, internal computing service, AI model, AI training, and AI inference.

[0640] Optionally, the new service PDU session type includes one of the following: IPv4, IPv6, IPv4v6, and 3GPP protocol.

[0641] Optionally, the priority indication includes at least one of the following: a high priority indication and a low priority indication, wherein the high priority indication is used to indicate whether the priority of the data of the second PDU session or the task of the second PDU session is higher than that of the non-new service data, and the low priority indication is used to indicate whether the priority of the data of the second PDU session or the task of the second PDU session is lower than that of the non-new service data;

[0642] Alternatively, the priority indication may include at least one of the following: a high priority indication and a low priority indication, wherein the high priority indication is used to indicate whether the data of the first PDU session or the task of the first PDU session has the highest priority, and the low priority indication is used to indicate whether the data of the first PDU session or the task of the first PDU session has the lowest priority.

[0643] Optionally, the receiving module 31 is further configured to receive uplink data sent by the terminal; the sending module 32 is further configured to send the uplink data to the new service function node through the second PDU session if the first PDU session of the terminal is a new service PDU session associated with the second PDU session, or if the task identifier of the uplink data is a task identifier associated with the second PDU session.

[0644] Referring to Figure 20, when the PDU session establishment or modification device is a network-side device or a component of a network-side device, the PDU session establishment or modification device 40 includes a receiving module 41 for receiving a third request, the third request being used to instruct the radio access network functional node to configure the DRB of the first PDU session for the new service for the terminal; and a sending module 42 for sending a third response to the third request, the third response being used to indicate whether the first PDU session was successfully established or modified.

[0645] Optionally, the third request includes at least one of the following:

[0646] New service PDU session indication, used to indicate that the first PDU session is used for a new service;

[0647] A new service PDU session identifier is used to identify the first PDU session;

[0648] New service type, used to indicate the type of the new service;

[0649] New service PDU session type, used to indicate the type of the first PDU session;

[0650] QoS summary, used by the radio access network functional node to perform the mapping between the tasks of the first PDU session and the DRB;

[0651] Task identifier, used to identify the task of the first PDU session;

[0652] Maximum transmission delay, used to indicate the maximum transmission delay of the first PDU session or the task of the first PDU session;

[0653] Minimum bit rate, used to indicate the minimum bit rate of the first PDU session or the task of the first PDU session;

[0654] Minimum time window, used to indicate the time interval for statistical analysis of the maximum transmission delay and / or minimum bit rate;

[0655] Priority indicator, used to indicate the priority information of the first PDU session or the task of the first PDU session;

[0656] RAN termination indication is used to indicate whether the first PDU session or the task of the first PDU session is resolved by the radio access network function node.

[0657] Next-hop node type, used to indicate the next-hop node type after the uplink data of the first PDU session or the task of the first PDU session is transmitted to the radio access network function node;

[0658] The next-hop node address is used to indicate the next-hop node address of the data of the first PDU session or the task of the first PDU session;

[0659] Destination address, used to indicate the destination address of the data of the first PDU session or the task of the first PDU session.

[0660] Optionally, the new service type includes at least one of the following: perception service, AI service, computing service, external perception service, internal perception service, external AI service, internal AI service, external computing service, internal computing service, AI model, AI training, and AI inference.

[0661] Optionally, the new service PDU session type includes one of the following: IPv4, IPv6, IPv4v6, and 3GPP protocol.

[0662] Optionally, the priority indication includes at least one of the following: a high priority indication and a low priority indication, wherein the high priority indication is used to indicate whether the priority of the data of the second PDU session or the task of the second PDU session is higher than that of the non-new service data, and the low priority indication is used to indicate whether the priority of the data of the second PDU session or the task of the second PDU session is lower than that of the non-new service data;

[0663] Alternatively, the priority indication may include at least one of the following: a high priority indication and a low priority indication, wherein the high priority indication is used to indicate whether the data of the first PDU session or the task of the first PDU session has the highest priority, and the low priority indication is used to indicate whether the data of the first PDU session or the task of the first PDU session has the lowest priority.

[0664] Optionally, the third response includes at least one of the following:

[0665] A new service PDU session identifier is used to identify the first PDU session;

[0666] Transmission information between the new service function node and the wireless access network function node;

[0667] Indication information indicating whether the first PDU session was successfully established or modified;

[0668] The list of task identifiers accepted for the new service;

[0669] A list of task identifiers for the rejected new service;

[0670] Reasons for refusal.

[0671] Optionally, the PDU session establishment or modification device 40 further includes:

[0672] The processing module is used to determine whether a DRB needs to be added based on the third request.

[0673] The sending module 42 is further configured to send configuration information to the terminal when it is determined that a DRB needs to be added, the configuration information being used to instruct the addition of a DRB for the first PDU session.

[0674] Optionally, the configuration information includes at least one of the following information elements:

[0675] New Service PDU Session Indicator, used to instruct the SDAP entity to use the first PDU session;

[0676] A new service PDU session identifier is used to identify the first PDU session;

[0677] SDAP header configuration information, wherein the SDAP header includes at least one of an uplink SDAP header and a downlink SDAP header;

[0678] Default DRB, used to indicate whether the DRB is the default DRB;

[0679] Add a new task identifier to indicate one or more new task identifiers mapped to the DRB;

[0680] Release task identifiers, used to indicate the release of one or more task identifiers mapped to the DRB;

[0681] A start marker is used to indicate that the data SDU of the new service task indicated by the task identifier has begun to be mapped to the DRB;

[0682] An end marker is used to indicate that the data SDU of the new service task indicated by the task identifier has stopped being mapped to the DRB.

[0683] Optionally, the SDAP header configuration information includes one of the following:

[0684] Does an SDAP header exist?

[0685] The number of bits in the SDAP header;

[0686] The format name of the SDAP header.

[0687] Optionally, the configuration information is sent using an RRC reconfiguration message.

[0688] Optionally, the PDU session establishment or modification device 40 further includes:

[0689] The processing module is configured to allocate transmission information between the new service function node and the radio access network function node for the first PDU session when the first PDU session is not configured with a RAN termination indication.

[0690] Referring to Figure 21, when the PDU session establishment or modification device is a terminal or a component in a terminal, the PDU session establishment or modification device 50 includes a sending module 51 for sending a fourth request, which is used to request the establishment or modification of a third PDU session for a new service; and a receiving module 52 for receiving a fourth response, which is used to indicate whether the third PDU session has been successfully established or modified.

[0691] The fourth request includes at least one of the following:

[0692] Optionally, the data network requested by the terminal is used to indicate that the data network is a new service data network;

[0693] New service type, used to indicate the type of the new service;

[0694] The PDU session request type is used to indicate that the PDU session request is a PDU session request for the new service.

[0695] Optionally, the fourth response includes at least one of the following:

[0696] The QoS flow identifier of the new service;

[0697] The QoS parameters of the new service;

[0698] The new service uses the PDU session type;

[0699] RAN termination indication is used to indicate whether the data of the new service is resolved by the radio access network function node.

[0700] Referring to Figure 22, when the PDU session establishment or modification device is a network-side device or a component within a network-side device, the PDU session establishment or modification device 60 includes: a receiving module 61, used to receive a fourth request sent by a terminal, the fourth request being used to request the establishment or modification of a third PDU session for a new service; a processing module 62, used to select an SMF for the terminal; and a sending module 63, used to send a fifth request to the SMF, the fifth request being used to request the establishment or modification of the third PDU session.

[0701] Optionally, the fourth request includes at least one of the following:

[0702] The data network requested by the terminal is used to indicate that the data network is a new service data network;

[0703] New service type, used to indicate the type of the new service;

[0704] The PDU session request type is used to indicate that the PDU session request is a PDU session request for the new service.

[0705] Optionally, the fifth request includes at least one of the following:

[0706] The data network requested by the terminal is used to indicate that the data network is a new service data network;

[0707] PDU session request type, used to indicate that the PDU session request is a PDU session request for the new service;

[0708] New service type, used to indicate the type of the new service;

[0709] The AMF is the name of the data network selected by the terminal;

[0710] The AMF is the identifier of the new service function node selected by the terminal.

[0711] Referring to Figure 23, when the PDU session establishment or modification device is a network-side device or a component within a network-side device, the PDU session establishment or modification device 70 includes: a receiving module 71, used to receive a fifth request from an AMF; the fifth request is used to request the establishment or modification of a third PDU session for a new service; a processing module 72, used to select a UPF according to the fifth request; and a sending module 73, used to send a fifth response to the terminal or radio access network functional node, the fifth response being used to indicate whether the third PDU session has been successfully established or modified.

[0712] Optionally, the fifth request includes at least one of the following:

[0713] The data network requested by the terminal is used to indicate that the data network is a new service data network;

[0714] PDU session request type, used to indicate that the PDU session request is a PDU session request for the new service;

[0715] New service type, used to indicate the type of the new service;

[0716] The AMF is the name of the data network selected by the terminal;

[0717] The AMF is the identifier of the new service function node selected by the terminal.

[0718] Optionally, the sending module 73 is further configured to send a sixth request to the UPF, the sixth request including at least one of the following:

[0719] New QoS flow UL packet detection rules;

[0720] New QoS flow DL packet detection rules.

[0721] Optionally, the fifth response includes at least one of the following:

[0722] The QoS flow identifier of the new service;

[0723] The QoS parameters of the new service;

[0724] The new service uses the PDU session type;

[0725] RAN termination instruction.

[0726] Referring to Figure 26, when the PDU session establishment or modification device is a network-side device or a component within a network-side device, the PDU session establishment or modification device 90 includes:

[0727] The receiving module 91 is used to receive the fifth response sent by the SMF; the fifth response is used to indicate whether the third PDU session for the new service was successfully created or modified.

[0728] The fifth response includes at least one of the following:

[0729] The QoS flow identifier of the new service;

[0730] The QoS parameters of the new service;

[0731] The new service uses the PDU session type;

[0732] RAN termination indication is used to indicate whether the data of the new service is resolved by the radio access network function node.

[0733] Optionally, the PDU session establishment or modification device 90 further includes:

[0734] The processing module is configured to allocate transmission information between the new service function node and the radio access network function node for the third PDU session if the RAN termination indication in the fifth response indicates that the data of the new service is not parsed by the radio access network function node, or if the fifth response does not include the RAN termination indication.

[0735] and / or

[0736] The sending module is configured to send configuration information to the terminal if the RAN termination indication in the fifth response indicates that the data of the new service is parsed by the radio access network function node. The configuration information includes: SDAP header configuration information, wherein the SDAP header includes at least one of an uplink SDAP header and a downlink SDAP header, and the SDAP header contains a RAN termination indication.

[0737] In the embodiments of this application, the establishment or modification process of the PDU session of the new service is triggered by the new service function node, or the existing PDU session establishment or modification process is extended so that the terminal triggers the establishment or modification process of the PDU session for the new service, thereby completing the establishment or modification of the PDU session of the new service.

[0738] The PDU session establishment or modification apparatus provided in this application embodiment can implement the various processes implemented in the method embodiments of Figures 5 to 13 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0739] As shown in Figure 25, this application embodiment also provides a communication device 100, including a processor 101 and a memory 102. The memory 102 stores a program or instructions that can run on the processor 101. When the program or instructions are executed by the processor 101, they implement the various steps of the above-described PDU session establishment or modification method embodiment and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0740] This application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the method embodiments shown in FIG5 or FIG10. This terminal embodiment corresponds to the above-described terminal-side method embodiments, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and can achieve the same technical effect. The terminal can be the PDU session establishment or modification device shown in FIG17 or FIG21. Specifically, FIG26 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0741] The terminal 110 includes, but is not limited to, at least some of the following components: radio frequency unit 111, network module 112, audio output unit 113, input unit 114, sensor 115, display unit 116, user input unit 117, interface unit 118, memory 119, and processor 1110.

[0742] Those skilled in the art will understand that terminal 110 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to processor x 10 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in Figure 26 does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0743] It should be understood that, in this embodiment, the input unit 114 may include a graphics processor 1141 and a microphone 1142. The graphics processor 1141 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 116 may include a display panel 1161, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 117 includes at least one of a touch panel 1171 and other input devices 1172. The touch panel 1171 is also called a touch screen. The touch panel 1171 may include two parts: a touch detection device and a touch controller. Other input devices 1172 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0744] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 111 can transmit it to the processor 1110 for processing; in addition, the radio frequency unit 111 can send uplink data to the network-side device. Typically, the radio frequency unit 111 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0745] The memory 119 can be used to store software programs or instructions, as well as various data. The memory 119 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 119 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 119 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0746] Processor 1110 may include one or more processing units; optionally, processor 1110 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 1110.

[0747] The radio frequency unit 111 is used to receive a first request, the first request being used to request the establishment or modification of a first PDU session for a new service and to send a first response to the first request, the first response being used to indicate whether the first PDU session has been successfully established or modified.

[0748] In the embodiments of this application, the establishment or modification process of the PDU session of the new service is triggered by the new service function node, or the existing PDU session establishment or modification process is extended so that the terminal triggers the establishment or modification process of the PDU session for the new service, thereby completing the establishment or modification of the PDU session of the new service.

[0749] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment shown in Figure 5 or Figure 10, and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0750] This application also provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method embodiments shown in Figures 6, 7, 8, 9, 11, 12, 13, or 13. This network-side device embodiment corresponds to the above-described network-side device method embodiments. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and achieve the same technical effects.

[0751] Specifically, this application embodiment also provides a network-side device, which may be the PDU session establishment or modification device shown in FIG27. As shown in FIG27, the network-side device 120 includes: an antenna 121, a radio frequency device 122, a baseband device 123, a processor 124, and a memory 125. The antenna 121 is connected to the radio frequency device 122. In the uplink direction, the radio frequency device 122 receives information through the antenna 121 and sends the received information to the baseband device 123 for processing. In the downlink direction, the baseband device 123 processes the information to be transmitted and sends it to the radio frequency device 122. The radio frequency device 122 processes the received information and transmits it through the antenna 121.

[0752] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 123, which includes a baseband processor.

[0753] The baseband device 123 may include at least one baseband board, on which multiple chips are disposed, as shown in FIG12. One of the chips is, for example, a baseband processor, which is connected to the memory 125 via a bus interface to call the program or instructions in the memory 125 to execute the network-side device operation shown in the above method embodiment.

[0754] The network-side device may also include a network interface 126, such as a Common Public Radio Interface (CPRI).

[0755] The radio frequency device 122 is used to receive a second request, which is used to request the establishment of a second PDU session for a new service; and to send a second response to the second request, which is used to indicate whether the second PDU session has been successfully established or modified.

[0756] or,

[0757] The radio frequency device 122 is configured to receive a third request, which instructs the radio access network functional node to configure a DRB for a first PDU session for a new service for the terminal; and to send a third response to the third request, which instructs whether the first PDU session has been successfully established or modified.

[0758] or,

[0759] The radio frequency device 122 is used to receive a fifth response sent by the SMF; the fifth response is used to indicate whether the third PDU session for the new service was successfully created or modified;

[0760] The fifth response includes at least one of the following:

[0761] The QoS flow identifier of the new service;

[0762] The QoS parameters of the new service;

[0763] The new service uses the PDU session type;

[0764] RAN termination indication is used to indicate whether the data of the new service is resolved by the radio access network function node.

[0765] In addition, the network-side device 120 of this application embodiment also includes: a program or instructions stored in the memory 125 and executable on the processor 124. The processor 124 calls the program or instructions in the memory 125 to execute the methods executed by the modules shown in FIG19, FIG20 or FIG26 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0766] Specifically, this application embodiment also provides a network-side device. As shown in FIG28, the network-side device 130 includes: a processor 131, a network interface 132, and a memory 133. The network-side device may be the XX device shown in FIG28. The network interface 132 is, for example, a Common Public Radio Interface (CPRI).

[0767] The network interface 132 is used to send a first request to the terminal; the first request is used to request the establishment or modification of a first PDU session for a new service; or, to send a second request to the radio access network functional node; the second request is used to request the establishment or modification of a second PDU session for a new service.

[0768] or,

[0769] Network interface 132 is used to receive a fourth request sent by the terminal, the fourth request being used to request the establishment or modification of a third PDU session for a new service;

[0770] Processor 131 is configured to select an SMF for the terminal;

[0771] Network interface 132 is also used to send a fifth request to the SMF, the fifth request being used to request the establishment or modification of the third PDU session.

[0772] or,

[0773] Network interface 132 is used to receive a fifth request from the AMF; the fifth request is used to request the establishment or modification of a third PDU session for a new service;

[0774] Processor 131 is configured to select a UPF based on the fifth request;

[0775] Network interface 132 is also used to send a fifth response to the terminal or wireless access network functional node, the fifth response being used to indicate whether the third PDU session was successfully established or modified.

[0776] or,

[0777] Network interface 132 is used to receive a fifth response sent by SMF; the fifth response is used to indicate whether the third PDU session for the new service was successfully created or modified;

[0778] The fifth response includes at least one of the following:

[0779] The QoS flow identifier of the new service;

[0780] The QoS parameters of the new service;

[0781] The new service uses the PDU session type;

[0782] RAN termination indication is used to indicate whether the data of the new service is resolved by the radio access network function node.

[0783] In addition, the network-side device 130 of this application embodiment also includes: a program or instructions stored in a memory 133 and executable on a processor 131. The processor 131 calls the program or instructions in the memory 133 to execute the methods executed by the modules shown in FIG18, FIG22, FIG23, or FIG24 and achieves the same technical effect. To avoid repetition, it will not be described in detail here.

[0784] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described PDU session establishment or modification method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0785] The processor mentioned above is either the processor in the terminal described in the above embodiments or the processor in the network-side device. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0786] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run programs or instructions to implement the various processes of the above-described PDU session establishment or modification method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0787] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0788] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described PDU session establishment or modification method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0789] This application also provides a wireless communication system, including: a terminal and a network-side device. The terminal can be used to perform the steps of the PDU session establishment or modification method as described above, and the network-side device can be used to perform the steps of the PDU session establishment or modification method as described above, as described above, performed by a wireless access network function node or a new service function node.

[0790] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0791] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.), and the computer software product includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0792] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

A method for establishing or modifying a PDU session includes: The terminal receives a first request, which is used to request the establishment or modification of a first PDU session for a new service; The terminal sends a first response to the first request, the first response indicating whether the first PDU session was successfully established or modified. According to the method of claim 1, wherein, The first request includes at least one of the following information elements: New service PDU session indication, used to indicate that the first PDU session is used for a new service; A new service PDU session identifier is used to identify the first PDU session; New service type, used to indicate the type of the new service; New service PDU session type, used to indicate the type of the first PDU session; Terminal identifier, used to identify the terminal participating in the new service; Task identifier, used to identify the task of the first PDU session; QoS rules are used by the terminal to mark and map the uplink data of the new service; Priority indicator, used to indicate the priority information of the first PDU session or the task of the first PDU session; RAN termination indication is used to indicate whether the first PDU session or the task of the first PDU session is resolved by the radio access network function node. The method according to claim 1 or 2, wherein, The new service types include at least one of the following: perception service, AI service, computing service, external perception service, internal perception service, external AI service, internal AI service, external computing service, internal computing service, AI model, AI training, and AI inference. The method according to claim 2, wherein, The new service PDU session type includes one of the following: IPv4, IPv6, IPv4v6, and 3GPP protocol. The method according to claim 2, wherein, The priority indication includes at least one of the following: a high priority indication and a low priority indication, wherein the high priority indication is used to indicate whether the priority of the data of the first PDU session or the task of the first PDU session is higher than that of the non-new service data, and the low priority indication is used to indicate whether the priority of the data of the first PDU session or the task of the first PDU session is lower than that of the non-new service data. Alternatively, the priority indication may include at least one of the following: a high priority indication and a low priority indication, wherein the high priority indication is used to indicate whether the data of the first PDU session or the task of the first PDU session has the highest priority, and the low priority indication is used to indicate whether the data of the first PDU session or the task of the first PDU session has the lowest priority. The method according to any one of claims 1-5, wherein, The first response includes at least one of the following: A new service PDU session identifier is used to identify the first PDU session; Indication information indicating whether the first PDU session was successfully established or modified; The reason why the first PDU session failed to be established or modified. The method according to any one of claims 1-6, wherein, Also includes: The terminal receives configuration information sent by the radio access network functional node, the configuration information being used to instruct the addition of a DRB for the first PDU session; If the SDAP entity for the first PDU session does not exist, the terminal establishes an SDAP entity for the first PDU session according to the configuration information; The terminal sends an establishment completion message to the radio access network functional node, the establishment completion message being used to indicate that the SDAP entity has been established. The method according to claim 7, wherein, The configuration information includes at least one of the following information elements: New Service PDU Session Indicator, used to instruct the SDAP entity to use the first PDU session; A new service PDU session identifier is used to identify the first PDU session; SDAP header configuration information, wherein the SDAP header includes at least one of an uplink SDAP header and a downlink SDAP header; Default DRB, used to indicate whether the DRB is the default DRB; Add a new task identifier to indicate one or more new task identifiers mapped to the DRB; Release task identifiers, used to indicate the release of one or more task identifiers mapped to the DRB; A start marker is used to indicate that the data SDU of the new service task indicated by the task identifier has begun to be mapped to the DRB; An end marker is used to indicate that the data SDU of the new service task indicated by the task identifier has stopped being mapped to the DRB. The method according to claim 8, wherein, The SDAP header configuration information includes one of the following: Does an SDAP header exist? The number of bits in the SDAP header; The format name of the SDAP header. The method according to any one of claims 7-9, wherein, The configuration information is carried in an RRC reconfiguration message. The method according to claim 7, wherein, Also includes: The terminal sends an uplink SDAP PDU, which carries a first information unit, including information units not carried in the first request and the configuration information. The method according to any one of claims 1-11, wherein, Also includes: The terminal reports terminal capability information, which includes whether the terminal supports the new service. A method for establishing or modifying a PDU session includes: The new service function node sends the first request to the terminal; The first request is used to request the establishment or modification of a first PDU session for the new service; or, The new service function node sends a second request to the radio access network function node; the second request is used to request the establishment or modification of a second PDU session for the new service. The method according to claim 13, wherein, The first request includes at least one of the following information elements: New service PDU session indication, used to indicate that the first PDU session is used for a new service; A new service PDU session identifier is used to identify the first PDU session; New service type, used to indicate the type of the new service; New service PDU session type, used to indicate the type of the first PDU session; Terminal identifier, used to identify the terminal for the new service; Task identifier, used to identify the task of the first PDU session; QoS rules are used by the terminal to mark and map the uplink data of the new service; Priority indicator, used to indicate priority information of the first PDU session or the task of the first PDU session. The method according to claim 13 or 14, wherein, Also includes: The new service function node sends a third request to the radio access network function node, the third request being used to instruct the radio access network function node to configure a DRB for the terminal for the first PDU session. The method according to claim 15, wherein, The third request includes at least one of the following: New service PDU session indication, used to indicate that the first PDU session is used for a new service; A new service PDU session identifier is used to identify the first PDU session; New service type, used to indicate the type of the new service; New service PDU session type, used to indicate the type of the first PDU session; QoS summary, used by the radio access network functional node to perform the mapping between the tasks of the first PDU session and the DRB; Task identifier, used to identify the task of the first PDU session; Maximum transmission delay, used to indicate the maximum transmission delay of the first PDU session or the task of the first PDU session; Minimum bit rate, used to indicate the minimum bit rate of the first PDU session or the task of the first PDU session; Minimum time window, used to indicate the time interval for statistical analysis of the maximum transmission delay and / or minimum bit rate; Priority indicator, used to indicate the priority information of the first PDU session or the task of the first PDU session; RAN termination indication is used to indicate whether the first PDU session or the task of the first PDU session is resolved by the radio access network function node. Next-hop node type, used to indicate the next-hop node type after the uplink data of the first PDU session or the task of the first PDU session is transmitted to the radio access network function node; The next-hop node address is used to indicate the next-hop node address of the data of the first PDU session or the task of the first PDU session; Destination address, used to indicate the destination address of the data of the first PDU session or the task of the first PDU session. The method according to claim 13, wherein, The second request includes at least one of the following: New service PDU session indication, used to indicate that the second PDU session is used for a new service; A new service PDU session identifier is used to identify the second PDU session; New service type, used to indicate the type of the new service; New service PDU session type, used to indicate the type of the second PDU session; Task identifier, used to identify the task of the second PDU session; The associated new service PDU session identifier is used to indicate the identifier of the terminal's first PDU session, which is associated with the second PDU session and terminated at the radio access network functional node; The associated task identifier is used to indicate the identifier of the task associated with the second PDU session and terminated at the radio access network functional node of the terminal's first PDU session. The method according to claim 14, 16, or 17, wherein, The new service types include at least one of the following: perception service, AI service, computing service, external perception service, internal perception service, external AI service, internal AI service, external computing service, internal computing service, AI model, AI training, and AI inference. The method according to claim 14, 16, or 17, wherein, The new service PDU session type includes one of the following: IPv4, IPv6, IPv4v6, and 3GPP protocol. The method according to claim 14 or 16, wherein, The priority indication includes at least one of the following: a high priority indication and a low priority indication, wherein the high priority indication is used to indicate whether the priority of the data of the new service PDU session or the task of the new service PDU session is higher than that of the non-new service data, and the low priority indication is used to indicate whether the priority of the data of the new service PDU session or the task of the new service PDU session is lower than that of the non-new service data, wherein the new service PDU session is the first PDU session or the second PDU session. Alternatively, the priority indication may include at least one of the following: a high priority indication and a low priority indication, wherein the high priority indication is used to indicate whether the data of the first PDU session or the task of the first PDU session has the highest priority, and the low priority indication is used to indicate whether the data of the first PDU session or the task of the first PDU session has the lowest priority. The method according to any one of claims 13-20, wherein, Also includes: The new service function node obtains the terminal capability information of the terminal, including whether the terminal supports the new service; The new service function node determines whether to select the terminal for the new service based on the terminal's terminal capability information. The method according to claim 15, wherein, Also includes: The new service function node receives a third response to the third request sent by the radio access network function node, the third response including at least one of the following: A new service PDU session identifier is used to identify the first PDU session; Transmission information between the new service function node and the wireless access network function node; Indication information indicating whether the first PDU session was successfully established or modified; The list of task identifiers accepted for the new service; A list of task identifiers for the rejected new service; Reasons for refusal. The method according to claim 22, wherein, Also includes: If the third response indicates that the establishment or modification of the first PDU session has failed, the new service function node shall modify at least one of the following in the first request: QoS rules, priority indication, and resend the modified first request, or reselect the terminal for the new service. The method according to any one of claims 13-23, wherein, Also includes: The new service function node marks the downlink data of the new service with a task identifier, and sends the downlink data marked with the task identifier to the radio access network function node or the terminal. A method for establishing or modifying a PDU session includes: The radio access network functional node receives a second request, which is used to request the establishment of a second PDU session for the new service; The radio access network functional node sends a second response to the second request, the second response being used to indicate whether the second PDU session was successfully established or modified. or, The radio access network functional node receives a third request, which instructs the radio access network functional node to configure a DRB for a first PDU session for a new service for the terminal. The radio access network functional node sends a third response to the third request, the third response indicating whether the first PDU session was successfully established or modified. The method according to claim 25, wherein, The second request includes at least one of the following: New service PDU session indication, used to indicate that the second PDU session is used for a new service; A new service PDU session identifier is used to identify the second PDU session; New service type, used to indicate the type of the new service; New service PDU session type, used to indicate the type of the second PDU session; Task identifier, used to identify the task of the second PDU session; The associated new service PDU session identifier is used to indicate the identifier of the terminal's first PDU session, which is associated with the second PDU session and terminated at the radio access network functional node; The associated task identifier is used to indicate the identifier of the task associated with the second PDU session and terminated at the radio access network functional node of the terminal's first PDU session. The method according to claim 25, wherein, The third request includes at least one of the following: New service PDU session indication, used to indicate that the first PDU session is used for a new service; A new service PDU session identifier is used to identify the first PDU session; New service type, used to indicate the type of the new service; New service PDU session type, used to indicate the type of the first PDU session; QoS summary, used by the radio access network functional node to perform the mapping between the tasks of the first PDU session and the DRB; Task identifier, used to identify the task of the first PDU session; Maximum transmission delay, used to indicate the maximum transmission delay of the first PDU session or the task of the first PDU session; Minimum bit rate, used to indicate the minimum bit rate of the first PDU session or the task of the first PDU session; Minimum time window, used to indicate the time interval for statistical analysis of the maximum transmission delay and / or minimum bit rate; Priority indicator, used to indicate the priority information of the first PDU session or the task of the first PDU session; RAN termination indication is used to indicate whether the first PDU session or the task of the first PDU session is resolved by the radio access network function node. Next-hop node type, used to indicate the next-hop node type after the uplink data of the first PDU session or the task of the first PDU session is transmitted to the radio access network function node; The next-hop node address is used to indicate the next-hop node address of the data of the first PDU session or the task of the first PDU session; Destination address, used to indicate the destination address of the data of the first PDU session or the task of the first PDU session. The method according to claim 26 or 27, wherein, The new service types include at least one of the following: perception service, AI service, computing service, external perception service, internal perception service, external AI service, internal AI service, external computing service, internal computing service, AI model, AI training, and AI inference. The method according to claim 26 or 27, wherein, The new service PDU session type includes one of the following: IPv4, IPv6, IPv4v6, and 3GPP protocol. The method according to claim 27, wherein, The priority indication includes at least one of the following: a high priority indication and a low priority indication, wherein the high priority indication is used to indicate whether the priority of the data of the second PDU session or the task of the second PDU session is higher than that of the non-new service data, and the low priority indication is used to indicate whether the priority of the data of the second PDU session or the task of the second PDU session is lower than that of the non-new service data. Alternatively, the priority indication may include at least one of the following: a high priority indication and a low priority indication, wherein the high priority indication is used to indicate whether the data of the first PDU session or the task of the first PDU session has the highest priority, and the low priority indication is used to indicate whether the data of the first PDU session or the task of the first PDU session has the lowest priority. The method according to claim 25, wherein, The third response includes at least one of the following: A new service PDU session identifier is used to identify the first PDU session; Transmission information between the new service function node and the wireless access network function node; Indication information indicating whether the first PDU session was successfully established or modified; The list of task identifiers accepted for the new service; A list of task identifiers for the rejected new service; Reasons for refusal. The method according to claim 25, wherein, After receiving the third request, the wireless access network functional node also includes: The wireless access network functional node determines whether a DRB needs to be added based on the third request. If it is determined that a DRB needs to be added, it sends configuration information to the terminal. The configuration information is used to instruct the addition of a DRB for the first PDU session. The method according to claim 32, wherein, The configuration information includes at least one of the following information elements: New service PDU session indication, used to indicate that the created SDAP entity is used for the first PDU session; A new service PDU session identifier is used to identify the first PDU session; SDAP header configuration information, wherein the SDAP header includes at least one of an uplink SDAP header and a downlink SDAP header; Default DRB, used to indicate whether the DRB is the default DRB; Add a new task identifier to indicate one or more new task identifiers mapped to the DRB; Release task identifiers, used to indicate the release of one or more task identifiers mapped to the DRB; A start marker is used to indicate that the data SDU of the new service task indicated by the task identifier has begun to be mapped to the DRB; An end marker is used to indicate that the data SDU of the new service task indicated by the task identifier has stopped being mapped to the DRB. The method according to claim 33, wherein, The SDAP header configuration information includes one of the following: Does an SDAP header exist? The number of bits in the SDAP header; The format name of the SDAP header. The method according to any one of claims 32-34, wherein, The configuration information is sent using RRC reconfiguration messages. The method according to claim 25, wherein, Also includes: If the first PDU session is not configured with a RAN termination indication, the Radio Access Network Functional Node (RAF Node) allocates transmission information between the new Service Functional Node (SNF Node) and the RAF Node for the first PDU session. The method according to claim 25, wherein, Also includes: The wireless access network functional node receives uplink data sent by the terminal; If the first PDU session of the terminal is a new service PDU session associated with the second PDU session, or if the task identifier of the uplink data is a task identifier associated with the second PDU session, the radio access network function node sends the uplink data to the new service function node through the second PDU session. A method for establishing or modifying a PDU session includes: The terminal sends a fourth request, which is used to request the establishment or modification of a third PDU session for the new service; The terminal receives a fourth response, which indicates whether the third PDU session was successfully established or modified. The method according to claim 38, wherein, The fourth request includes at least one of the following: The data network requested by the terminal is used to indicate that the data network is a new service data network; New service type, used to indicate the type of the new service; The PDU session request type indicates that the PDU session request is a PDU session request for the new service. The method according to claim 38 or 39, wherein, The fourth response includes at least one of the following: The QoS flow identifier of the new service; The QoS parameters of the new service; The new service uses the PDU session type; RAN termination indication is used to indicate whether the data of the new service is resolved by the radio access network function node. A method for establishing or modifying a PDU session includes: The AMF receiving terminal sends a fourth request, which is used to request the establishment or modification of a third PDU session for a new service; The AMF selects an SMF for the terminal and sends a fifth request to the SMF, the fifth request being used to request the establishment or modification of the third PDU session. The method according to claim 41, wherein, The fourth request includes at least one of the following: The data network requested by the terminal is used to indicate that the data network is a new service data network; New service type, used to indicate the type of the new service; The PDU session request type indicates that the PDU session request is a PDU session request for the new service. The method according to claim 41, wherein, The fifth request includes at least one of the following: The data network requested by the terminal is used to indicate that the data network is a new service data network; PDU session request type, used to indicate that the PDU session request is a PDU session request for the new service; New service type, used to indicate the type of the new service; The AMF is the name of the data network selected by the terminal; The AMF is the identifier of the new service function node selected by the terminal. A method for establishing or modifying a PDU session includes: SMF receives AMF's fifth request to send; The fifth request is used to request the establishment or modification of a third PDU session for the new service; The SMF selects the UPF based on the fifth request; The SMF sends a fifth response to the terminal or radio access network functional node, the fifth response being used to indicate whether the third PDU session was successfully established or modified. The method according to claim 44, wherein, The fifth request includes at least one of the following: The data network requested by the terminal is used to indicate that the data network is a new service data network; PDU session request type, used to indicate that the PDU session request is a PDU session request for the new service; New service type, used to indicate the type of the new service; The AMF is the name of the data network selected by the terminal; The AMF is the identifier of the new service function node selected by the terminal. The method according to claim 44, wherein, Also includes: The SMF sends a sixth request to the UPF, the sixth request including at least one of the following: New QoS flow UL packet detection rules; New QoS flow DL packet detection rules; New service access network tunnel information; Forwarding rules. The method according to claim 44, wherein, The fifth response includes at least one of the following: The QoS flow identifier of the new service; The QoS parameters of the new service; The new service uses the PDU session type; RAN termination instruction. A method for establishing or modifying a PDU session includes: The radio access network functional node receives the fifth response sent by the SMF; The fifth response is used to indicate whether the third PDU session for the new service was successfully created or modified. The fifth response includes at least one of the following: The QoS flow identifier of the new service; The QoS parameters of the new service; The new service uses the PDU session type; RAN termination indication is used to indicate whether the data of the new service is resolved by the radio access network function node. The method according to claim 48, wherein, Also includes: If the RAN termination indication in the fifth response indicates that the data of the new service is not parsed by the Radio Access Network Function Node, or if the fifth response does not include the RAN termination indication, the Radio Access Network Function Node allocates transmission information between the New Service Function Node and the Radio Access Network Function Node for the third PDU session; and / or If the RAN termination indication in the fifth response indicates that the data of the new service is parsed by the Radio Access Network Functional Node, the Radio Access Network Functional Node sends configuration information to the terminal. The configuration information includes SDAP header configuration information, wherein the SDAP header includes at least one of an uplink SDAP header and a downlink SDAP header, and the SDAP header contains the RAN termination indication. A PDU session establishment or modification apparatus, comprising: The receiving module is configured to receive a first request, wherein the first request is used to request the establishment or modification of a first PDU session for a new service; The sending module is used to send a first response to the first request, the first response being used to indicate whether the first PDU session has been successfully established or modified. A PDU session establishment or modification apparatus, comprising: The sending module is used to send the first request to the terminal; The first request is used to request the establishment or modification of a first PDU session for the new service; Alternatively, a second request may be sent to the radio access network functional node; the second request is used to request the establishment or modification of a second PDU session for the new service. A PDU session establishment or modification apparatus, comprising: The receiving module is used to receive a second request, which is used to request the establishment of a second PDU session for the new service; The sending module is used to send a second response to the second request, the second response being used to indicate whether the second PDU session was successfully established or modified; or, The receiving module is configured to receive a third request, which instructs the radio access network functional node to configure the DRB for the first PDU session for the new service for the terminal. The sending module is used to send a third response to the third request, the third response being used to indicate whether the first PDU session was successfully established or modified. A PDU session establishment or modification apparatus, comprising: A sending module is used to send a fourth request, which is used to request the establishment or modification of a third PDU session for a new service; The receiving module is used to receive a fourth response, which indicates whether the third PDU session was successfully established or modified. A PDU session establishment or modification apparatus, comprising: The receiving module is used to receive a fourth request sent by the terminal, the fourth request being used to request the establishment or modification of a third PDU session for a new service; The processing module is used to select an SMF for the terminal; The sending module is used to send a fifth request to the SMF, the fifth request being used to request the establishment or modification of the third PDU session. A PDU session establishment or modification apparatus, comprising: The receiving module is used to receive the AMF's fifth transmission request; The fifth request is used to request the establishment or modification of a third PDU session for the new service; The processing module is used to select a UPF based on the fifth request; The sending module is used to send a fifth response to the terminal or the wireless access network functional node, the fifth response being used to indicate whether the third PDU session has been successfully established or modified. A PDU session establishment or modification apparatus, comprising: The receiving module is used to receive the fifth response sent by the SMF; The fifth response is used to indicate whether the third PDU session for the new service was successfully created or modified. The fifth response includes at least one of the following: The QoS flow identifier of the new service; The QoS parameters of the new service; The new service uses the PDU session type; RAN termination indication is used to indicate whether the data of the new service is resolved by the radio access network function node. A terminal includes a processor and a memory, the memory storing a program or instructions executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the PDU session establishment or modification method as described in any one of claims 1 to 12, or, when executed by the processor, the program or instructions implement the steps of the PDU session establishment or modification method as described in any one of claims 38 to 40. A network-side device includes a processor and a memory, the memory storing a program or instructions executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the PDU session establishment or modification method as described in any one of claims 13 to 24; or, the program or instructions, when executed by the processor, implement the steps of the PDU session establishment or modification method as described in any one of claims 25 to 37; or, the program or instructions, when executed by the processor, implement the steps of the PDU session establishment or modification method as described in any one of claims 41 to 43; or, the program or instructions, when executed by the processor, implement the steps of the PDU session establishment or modification method as described in any one of claims 44 to 47; or, the program or instructions, when executed by the processor, implement the steps of the PDU session establishment or modification method as described in claim 48 or 49. A readable storage medium storing a program or instructions that, when executed by a processor, implement the PDU session establishment or modification method as claimed in any one of claims 1 to 12, or implement the steps of the PDU session establishment or modification method as claimed in any one of claims 13 to 24, or implement the steps of the PDU session establishment or modification method as claimed in any one of claims 25 to 37, or implement the steps of the PDU session establishment or modification method as claimed in any one of claims 38 to 40, or implement the steps of the PDU session establishment or modification method as claimed in any one of claims 41 to 43, or implement the steps of the PDU session establishment or modification method as claimed in any one of claims 44 to 47, or implement the steps of the PDU session establishment or modification method as claimed in claim 48 or 49.

Images