Session establishment method and apparatus, and terminal, network-side device, medium and product

Abstract

The present application belongs to the technical field of communications. Disclosed are a session establishment method and apparatus, and a terminal, a network-side device, a medium and a product. The session establishment method in the embodiments of the present application comprises: a terminal sending a first message to a network-side device, wherein the first message is used for establishing a session, and the session is used for transmitting a non-access stratum (NAS) message; and the terminal receiving a second message sent by the network-side device, wherein the second message is used for responding to the first message.

Description

Session establishment methods, devices, terminals, network-side equipment, media, and products

[0001] Cross-references to related applications

[0002] This disclosure claims priority to Chinese Patent Application No. 202510111388.0, filed on January 23, 2025, which is incorporated herein by reference in its entirety. Technical Field

[0003] This application belongs to the field of communication technology, specifically relating to a session establishment method, apparatus, terminal, network-side equipment, medium, and product. Background Technology

[0004] In related technologies, Non-Access Stratum (NAS) messages refer to messages used in mobile communication systems for communication between terminals and the control plane (CP) of the core network. NAS messages are primarily responsible for handling functions related to user session management, mobility management, user authentication, policy control, and security control.

[0005] In related technologies, NAS messages are only transmitted in the control plane, which results in a high load pressure on some core network nodes (especially AMF) for forwarding. Summary of the Invention

[0006] This application provides a session establishment method, apparatus, terminal, network-side device, medium, and product that can solve the problem of high load pressure on some core network nodes.

[0007] Firstly, a session establishment method is provided, which includes:

[0008] The terminal sends a first message to the network-side device. The first message is used to establish a session, and the session is used to transmit non-access stratum (NAS) messages.

[0009] The terminal receives a second message sent by the network-side device, the second message being used in response to the first message.

[0010] Secondly, a method for establishing a session is provided, which includes:

[0011] The network-side device receives a first message sent by the terminal. The first message is used to establish a session, and the session is used to transmit non-access stratum (NAS) messages.

[0012] The network-side device sends a second message to the terminal, the second message being used in response to the first message.

[0013] Thirdly, a session establishment apparatus is provided, the apparatus comprising:

[0014] The first sending module is used to send a first message to the network-side device. The first message is used to establish a session, and the session is used to transmit non-access stratum (NAS) messages.

[0015] The first receiving module is configured to receive a second message sent by the network-side device, the second message being used in response to the first message.

[0016] Fourthly, a session establishment apparatus is provided, the apparatus comprising:

[0017] The second receiving module is used to receive a first message sent by the terminal, the first message being used to establish a session, the session being used to transmit non-access stratum (NAS) messages;

[0018] The third sending module is used to send a second message to the terminal, the second message being used in response to the first message.

[0019] Fifthly, an apparatus for establishing a session is provided, the apparatus being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0020] In a sixth 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 aspect.

[0021] In a seventh aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used for:

[0022] Send a first message to the network-side device. The first message is used to establish a session, and the session is used to transmit non-access stratum (NAS) messages.

[0023] The system receives a second message sent by the network-side device, the second message being used in response to the first message.

[0024] Eighthly, 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 method as described in the second aspect.

[0025] Ninthly, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is used for:

[0026] The receiving terminal sends a first message, which is used to establish a session, and the session is used to transmit non-access stratum (NAS) messages;

[0027] A second message is sent to the terminal, the second message being a response to the first message.

[0028] In a tenth 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 method described in the first aspect, or implement the steps of the method described in the second aspect.

[0029] Eleventhly, a wireless communication system is provided, comprising: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the method as described in the first aspect, and the network-side device can be used to perform the steps of the method as described in the second aspect.

[0030] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0031] In a thirteenth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the session establishment method as described in the first aspect, or to implement the steps of the session establishment method as described in the second aspect.

[0032] In this embodiment, the terminal sends a first message to the network-side device, the first message being used to establish a session, the session being used to transmit non-access stratum (NAS) messages; the terminal receives a second message sent by the network-side device, the second message being used to respond to the first message, and transmits NAS messages by establishing a session, thereby allowing at least some NAS messages to be transmitted in the UP plane, thus enabling some NAS messages to be transmitted quickly between the terminal and the network, which can reduce the NAS message forwarding load pressure of some core network nodes (especially AMF). Attached Figure Description

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

[0034] Figure 2 is a flowchart of a session establishment method provided in an embodiment of this application;

[0035] Figure 3 is a flowchart of another session establishment method provided in an embodiment of this application;

[0036] Figure 4 is a flowchart of another session establishment method provided in an embodiment of this application;

[0037] Figure 5 is a flowchart of another session establishment method provided in an embodiment of this application;

[0038] Figure 6 is a flowchart of another session establishment method provided in an embodiment of this application;

[0039] Figure 7 is a schematic diagram of a session establishment device provided in an embodiment of this application;

[0040] Figure 8 is a schematic diagram of another session establishment device provided in an embodiment of this application;

[0041] Figure 9 is a schematic diagram of a communication device provided in an embodiment of this application;

[0042] Figure 10 is a schematic diagram of a terminal provided in an embodiment of this application;

[0043] Figure 11 is a schematic diagram of a network-side device provided in an embodiment of this application;

[0044] Figure 12 is a schematic diagram of another network-side device provided in an embodiment of this application. Detailed Implementation

[0045] 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.

[0046] 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.

[0047] 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.

[0048] 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 in the systems and radio technologies mentioned above, as well as in 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) communication systems.

[0049] 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.

[0050] 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.

[0051] 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).

[0052] The session establishment method, apparatus, terminal, network-side device, medium, and product provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0053] Referring to Figure 2, which is a flowchart of a session establishment method provided in an embodiment of this application for use on a terminal, the method includes the following steps:

[0054] Step 201: The terminal sends a first message to the network-side device. The first message is used to establish a session, and the session is used to transmit non-access stratum (NAS) messages.

[0055] In this embodiment of the application, optionally, the NAS message includes at least one of basic NAS message and service NAS message; wherein, the basic NAS message includes at least one of the following: terminal connection-related message and terminal session-related message; the service NAS message includes NAS service-related message.

[0056] Specifically, basic NAS messages refer to connection-related and session-related messages used by the terminal, mainly including basic processes such as registration, authentication, security mode, mobility registration update, session establishment, session modification, and session release. Basic NAS messages ensure basic communication connections and requirements. Service NAS messages refer to service-related messages, such as location, sensing services, AI services, and computing services.

[0057] Optionally, the NAS message can be NAS signaling or NAS data.

[0058] It is understood that the aforementioned basic NAS message can be either basic NAS signaling or basic NAS data, and the aforementioned service NAS message can also be either service NAS signaling or service NAS data.

[0059] In this embodiment of the application, the terminal sends a first message to the network-side device to establish a session for transmitting NAS messages. That is, this embodiment of the application establishes a session for transmitting NAS messages so that NAS messages can be transmitted on the session.

[0060] The sessions established in the embodiments of this application can be used to transmit at least one of basic NAS messages and service NAS messages. Some embodiments are described in relation to service NAS only as examples. It is understood that the technical solutions of basic NAS that are replaced by the above descriptions are still within the scope of protection of this application.

[0061] In this embodiment of the application, the session can be a Protocol Data Unit (PDU) session, but is not limited to this session naming method (for example, session can be replaced with channel). The session can be understood as a User Plane (UP) session.

[0062] In related technologies, NAS messages can only be transmitted on the CP plane, and NAS message transmission is not supported on sessions (such as PDU sessions). PDU sessions are mainly used to transmit user application data. However, the embodiments of this application provide a method for establishing a session for the transmission of NAS messages, which actually extends the related technologies where NAS messages can only be transmitted on the CP plane. It is understood that the embodiments of this application do not limit NAS messages to be transmitted only in the established session.

[0063] In this embodiment of the application, by establishing a session to transmit NAS messages, at least some NAS messages can be transmitted on the user plane UP, thereby enabling some NAS messages to be transmitted quickly between the terminal and the network, which can reduce the NAS message forwarding load pressure of some core network nodes (especially AMF).

[0064] Optionally, embodiments of this application can be applied to 6G network systems, enabling 6G networks to support the transmission of service NAS messages between the UE and the service network function (NF) via the user plane (i.e., via a PDU session established for the service NAS message). However, embodiments of this application are not limited to this and can be applied to other communication network systems, including 5G.

[0065] In this embodiment of the application, the terminal sends a first message to the network-side device. The first message is used to establish a session. The first message can be a session establishment request, requesting the establishment of one or more sessions to transmit NAS messages.

[0066] Taking the above session establishment request as a PDU session establishment request as an example, this application embodiment proposes a method for establishing one or more PDU sessions for transmitting NAS messages. The terminal can provide indication information in the PDU session establishment request to indicate the establishment of a PDU session dedicated to transmitting NAS messages, and the network-side device (e.g., SMF) establishes the PDU session for the terminal.

[0067] During a PDU session, network-side devices can precisely configure and dynamically manage network resources based on different service characteristics, such as bandwidth requirements, latency sensitivity, and reliability requirements, to provide differentiated service guarantees. For example, for virtual reality (VR) applications with extremely high latency requirements, network-side devices can prioritize the allocation of low-latency transmission paths and sufficient bandwidth resources in the corresponding PDU session; while for small amounts of periodic data uploaded by IoT sensors, a low-power, low-bandwidth PDU session can be configured.

[0068] In this embodiment, at the core network level, the SMF can be used to manage the entire lifecycle of PDU sessions, including creation, modification, and release. The SMF works in conjunction with other core network elements, such as the AMF or PCF, and combined with network slicing technology, to build multiple logically isolated and customized PDU sessions for different types of users and services on a unified infrastructure. In this embodiment, the network-side device is illustrated using the SMF as an example, but it is not limited to this and can also be other network elements or combinations of network elements.

[0069] Optionally, the first message includes at least one of the following:

[0070] First information, the first information being used to indicate one or more services;

[0071] The first data network name (DNN) is used to indicate the establishment of a session for transmitting NAS messages;

[0072] Information about the first slice; the information about the first slice is used to indicate the establishment of a session suitable for processing NAS messages;

[0073] First indication information, wherein the first indication information is used for at least one of the following:

[0074] A message indicating that the session is used to transmit a service;

[0075] The session is indicated to be used to transmit messages for multiple services;

[0076] The session is indicated to be used to transmit messages for at least one service.

[0077] In this embodiment of the application, the terminal sends a first message to the network-side device to establish a session for transmitting NAS messages. It can be understood that the information carried in the first message can directly indicate (or explicitly indicate) or indirectly indicate (or implicitly indicate) that the first message is used to request the establishment of a session for transmitting NAS messages. For example, the first information can be directly carried in the first message.

[0078] The first information may indicate at least one service.

[0079] Optionally, the service includes at least one of the following:

[0080] Location services, IP Multimedia Subsystem (IMS) services, Artificial Intelligence (AI) services, Computing power services, Artificial Intelligence of Things (AIoT) services, Sensing services, Slicing services, Satellite services, Proximity services, Immersive services, Data services, Short Message services, Energy-saving services, Task services, and Security services.

[0081] The first information can indicate at least one of the service types mentioned above, or it can indicate services in list form, with one or more services listed.

[0082] Optionally, the first information may be a service type list, which may indicate one or more NAS services, such as at least one of the following: location service, IP Multimedia Subsystem (IMS) service, Artificial Intelligence (AI) service, computing power service, Artificial Intelligence of Things (AIoT) service, sensing service, slicing service, satellite service, proximity service, immersive service, data service, SMS service, energy-saving service, task service, and security service.

[0083] In this embodiment of the application, optionally, the first message includes a first data network name (DNN), wherein the first DNN indicates a data network suitable for transmitting NAS messages. The so-called data network suitable for transmitting NAS messages can be understood as a data network that can meet the transmission requirements of NAS messages. When the network-side device receives the first DNN, it can know that the purpose of the current request to establish a session is to transmit NAS messages. The network-side device responds to the first message to establish a session suitable for transmitting NAS messages. That is, the first DNN is used to indicate the establishment of a session for transmitting NAS messages. The so-called session suitable for transmitting NAS messages can be understood as a session established for transmitting NAS messages, or a session suitable for transmitting NAS messages, or a session that can meet the transmission requirements of NAS messages. During the response process, the network-side device performs actions including but not limited to: selecting a suitable SMF or UPF node for the session, where suitable means suitable for transmitting NAS messages and able to meet the requirements of NAS message transmission; selecting a suitable N6 interface for the session, where the N6 interface is the interface between the UPF and the Data Network (DN); selecting a suitable policy to apply to the session, including communication policies and service policies; the aforementioned first DNN can be a dedicated DNN.

[0084] In one implementation, setting DNN="NAS" can be used to indicate the establishment of a session for transmitting NAS messages or to indicate that the first DNN is a data network suitable for transmitting NAS messages.

[0085] In this embodiment, the information of the first slice includes a slice differentiater (SD) and a slice / service type (SST). The SST indicates that the first slice is suitable for processing NAS messages. A slice suitable for processing NAS messages can be understood as a slice specifically designed for processing NAS messages, a slice applicable to processing NAS messages, or a slice capable of meeting the requirements for NAS message processing. When the network-side device receives the information of the first slice, it knows that the purpose of the current request to establish a session is for transmitting or processing NAS messages. The network-side device responds to the first message by establishing a session suitable for processing NAS messages; that is, the information of the first slice is used to indicate the establishment of a session suitable for processing NAS messages. A session suitable for processing NAS messages can be understood as a session established for processing NAS messages, a session applicable to processing NAS messages, or a session capable of meeting the requirements for NAS message processing. During the response process, the network-side device configures or reserves certain resources (such as storage resources and communication interfaces) for the session to ensure the service requirements of the slice. The first slice mentioned above can be a dedicated slice.

[0086] Optionally, the 6G network will configure dedicated DNN, slicing and other information to the UE (e.g., by issuing it to the UE through policy procedures or registration procedures or by pre-configuring it in the terminal) to establish a PDU session for serving NAS messages.

[0087] In this embodiment of the application, the aforementioned first message can also be used to directly indicate the purpose of the session. Optionally, the first indication information (service NAS indication) can indicate that the session is used to transmit messages for one service, or it can indicate that the session is used to transmit messages for multiple services, or it can indicate that the session is used to transmit messages for at least one service. It is understood that the relationship between a session and a service can be one-to-one, that is, one session corresponds to one service; it can also be one-to-many, that is, one session corresponds to at least two services; or it can be many-to-one, that is, one service can be transmitted on multiple sessions.

[0088] A PDU session can serve one or more services provided by a serving NF. The serving NF establishes one or more PDU sessions with the UE to transmit service signaling and / or service data. The UE can establish one or more PDU sessions with the network to transmit service NAS messages.

[0089] Optionally, the terminal sends a first message to the network-side device, including at least one of the following:

[0090] After completing the registration process, the terminal sends the first message to the network-side device.

[0091] After matching the Terminal Routing Policy (URSP) rules, the terminal sends the first message to the network-side device.

[0092] Upon receiving instructions from a higher layer, the terminal sends the first message to the network-side device.

[0093] When the terminal determines the session based on the third information, it sends the first message to the network-side device, wherein the third information includes an association between one or more services and the session.

[0094] In this embodiment of the application, the timing for the terminal to send a first message to the network-side device to establish a session can be as follows: after the terminal starts up, and / or completes the dwell process, and / or after receiving instructions from a higher layer, the terminal sends the first message; or it can be sent when the terminal itself has a need, for example, when the terminal needs to use one or more specific services. Sending the first message is used to establish a session for that specific one or more services.

[0095] Specifically, in an optional embodiment, when a terminal needs to use one or more services, the terminal selects a suitable route selection descriptor (RSD) through a UE Route Selection Policy (URSP), determines the attribute information of the PDU session based on the RSD, and sends the aforementioned first message when a PDU session with that attribute has not been established. The RSD includes at least one of a slice and a DNN.

[0096] Optionally, before the terminal sends the first message to the network-side device, the method includes:

[0097] The terminal selects RSD by matching the terminal routing selection policy URSP.

[0098] The first information includes RSD-related information.

[0099] Optionally, the URSP is used to indicate NAS services.

[0100] In this embodiment, connection capability information or DNN information can be added to the URSP rule to indicate new services. Taking connection capability information as an example, as shown in Table 1 below, a new 00100000 indicates service type A, such as a sensing service; a new 01000000 indicates service type B, such as a computing power service. These services include, but are not limited to: location services, IMS services, AI services, computing power services, AIoT services, sensing services, slicing services, satellite services, proximity services, immersive services, data services, SMS services, energy-saving services, task services, and security services. These are not listed exhaustively here. Each service network function entity (NF) provides one or more of the above services.

[0101] Table 1 URSP Encoding Table

[0102] It is understandable that the establishment process of certain types of PDU sessions may not require URSP matching. For example, a PDU session may be established when the terminal powers on or after the terminal completes the registration process. This PDU session can be a persistent online (always-on) PDU session, a dedicated PDU session, or a default PDU session, etc. Among these, persistent online (always-on) PDU sessions, dedicated PDU sessions, and default PDU sessions can be PDU session types that are not released after establishment and can be established after the terminal powers on. In this embodiment, the establishment process of persistent online (always-on) PDU sessions can be reused for NAS message transmission. A dedicated PDU session can be understood as a PDU session specifically used for transmitting NAS messages.

[0103] Specifically, a persistent online (always-on) PDU session, a dedicated PDU session, or a default PDU session refers to a situation where user plane resources must be established for each transition from 5GS Mobility Management-IDLE (5GMM-IDLE) to 5GS Mobility Management-CONNECTED (5GMM-CONNECTED), and the UE and Serving Network (NF) transmit Serving NAS messages through the user plane. The UE can request and receive instructions from higher layers to establish a PDU session as an always-on PDU session, and the network decides whether to establish the PDU session as an always-on PDU session.

[0104] It is understandable that if one or more UEs share a common PDU session, that PDU session may be an always-on PDU session, a dedicated PDU session, or a default PDU session.

[0105] In another optional embodiment, there is a preset association relationship (third information) between the service and the session. For example, the terminal may have a set of mapping tables configured locally, or the terminal may receive updates to the mapping table or mapping relationship from a network-side device (e.g., SMF). When the terminal establishes a PDU session for one or more services, it can determine the corresponding PDU session through the aforementioned association relationship (e.g., mapping table) and then send a first message requesting the establishment of the corresponding session.

[0106] The aforementioned first message can also be used to request the establishment of different types of PDU sessions, such as at least one of the following: requesting the establishment of a first PDU session, wherein each first PDU session is used for one NAS service; requesting the establishment of a second PDU session, wherein each second PDU session is used for multiple NAS services; requesting the establishment of a persistent online PDU session, wherein the persistent online PDU session is used for at least one NAS service; or requesting the establishment of a dedicated PDU session, wherein the dedicated PDU session is used for at least one NAS service.

[0107] Step 202: The terminal receives a second message sent by the network-side device, the second message being used in response to the first message.

[0108] In this embodiment of the application, after receiving the first message for establishing a NAS transmission message, the network-side device responds to the first message and sends a second message.

[0109] Optionally, the second message includes at least one of the following:

[0110] The address of the Network Function (NF) that provides the service;

[0111] The fully qualified domain name (FQDN) for NF services;

[0112] The port number for the NF service;

[0113] The second information is used to indicate one or more services;

[0114] QoS information;

[0115] The second indication information includes either a third indication information or a fourth indication information; the third indication information is used to indicate successful establishment of the session, and the fourth indication information is used to indicate rejection or partial rejection of establishing the session;

[0116] The fifth instruction information is used for at least one of the following:

[0117] A message indicating that the session is used to transmit a service;

[0118] The session is indicated to be used to transmit messages for multiple services;

[0119] The session is indicated to be used to transmit messages for at least one service.

[0120] In this embodiment, the network-side device receives a first message for establishing the session, and sends a second message in response to the first message. The second message can be understood as a feedback to the first message. Optionally, the first message is a session request message, and the second message is a session request response message.

[0121] After receiving the first message, the network-side device can agree to establish a session or refuse to establish a session. Correspondingly, the second indication information in the second message can be an indication of successful establishment of the session (third indication information) or an indication of refusal or partial refusal to establish the session (fourth indication information).

[0122] Optionally, the network-side device obtains a fourth piece of information about the terminal, which includes at least one of the terminal's capability information and subscription information.

[0123] The network-side device determines the second message based on at least one of the terminal's capability information and subscription information.

[0124] After receiving the first message, the network-side device can determine whether the information carried in the first message (i.e., the session-related information requested to be established) is reasonable based on the terminal's capability information and / or subscription information. In other words, the network-side device determines the second message based on the first message and the fourth information.

[0125] For example, it can be determined whether the service indicated in the first message is a service supported by the terminal and / or a subscribed service, thereby determining whether a session can be established or not. Optionally, if the first message and the fourth information match, i.e., the service indicated in the first message is a service supported by the terminal and / or a subscribed service, the network-side device sends a third indication message; if the first message and the fourth information do not match, i.e., the service indicated in the first message is not a service supported by the terminal and / or a subscribed service, the fourth indication message is sent. When requesting multiple services, there may be partial matching; in this case, the third indication message can be sent for the matching services, and the fourth indication message can be sent for the non-matching services.

[0126] The aforementioned network-side devices can obtain the fourth information through at least one of the following methods:

[0127] Obtain from UDM; the network-side device uses terminal identification information (such as Subscription Permanent Identifier (SUPI)) to query the UDM for the UE's subscription information, and the UDM replies with the service information subscribed by the UE to the network-side device;

[0128] The UE's capability information is obtained through the terminal's registration process, i.e., from the AMF. In one implementation, the network-side device uses terminal identification information (e.g., SUPI) to query the AMF for the UE's capability information, such as whether the terminal supports a specific service or which services the terminal supports. The AMF then replies to the network-side device with the UE's subscribed capability information (carrying the terminal's capability information and service capabilities). In another implementation, during the session registration process, when the AMF forwards a session establishment request message to the network-side device (e.g., SMF), it also carries the terminal's capability information to the network-side device (e.g., SMF), such as whether the terminal supports a specific service or which services the terminal supports.

[0129] Obtained through the terminal's session flow, i.e., directly from the terminal.

[0130] In this embodiment, the Serving Network Function (NF) can be understood as a network function used to transmit NAS messages. During the PDU session establishment process, the network can provide NF information (NF info) to the terminal through the PDU session flow (second message, e.g., PDU session establishment accept message), such as the NF address, fully qualified domain name (FQDN), etc.

[0131] Optionally, at least one of the service NF's address, the service NF's FQDN, and the service NF's port number may be carried via the Protocol Configuration Option (PCO) information element or the extended Protocol Configuration Option (ePCO).

[0132] In this embodiment of the application, for example, the SMF may carry the service NF address information in the Protocol Configuration Option (PCO) information element or the ePCO (extended PCO) information element in the session establishment acceptance message.

[0133] In this embodiment, the second information, used to indicate one or more services, differs from the first information in that it is carried in different messages. The first information is carried in a first message, such as a PDU session establishment request message, while the second information is carried in a second message, such as a PDU session establishment accept message or a PDU session establishment reject message. The meanings of the indications differ. In one implementation, the first information is a message (including signaling and data) used by the terminal to request the transmission of one or more services in the session, while the second information is a message (including signaling and data) used by the network-side device to indicate that one or more services can be transmitted in the session. The former emphasizes the terminal request, but the network-side device may not accept all services requested by the terminal; therefore, it is necessary to explicitly indicate in the second message which services can be transmitted in the session. It is understood that the services included in the second information can be the same as those included in the first information, or the services included in the second information can be a subset of those included in the first information.

[0134] In this embodiment, the fifth indication information is used for at least one of the following: instructing the session to transmit a message for one service; instructing the session to transmit a message for multiple services; or instructing the session to transmit a message for at least one service. The difference between the fifth indication information and the first indication information is that they are carried in different messages. The first indication information is carried in a first message, such as a PDU session establishment request message, while the fifth indication information is carried in a second message, such as a PDU session establishment accept message or a PDU session establishment reject message. The meanings of the indications are different. In one implementation, the first indication information is used for a terminal to request the session to transmit one or more services (including signaling and data), while the fifth indication information is used for a network-side device to indicate that the session can transmit one or more services (including signaling and data). The former emphasizes the terminal request, but the network-side device may not accept all services requested by the terminal. Therefore, it is necessary to explicitly indicate in the second message how many services can be transmitted on the session. It is understandable that the content indicated in the fifth instruction message can be the same as the content indicated in the first instruction message, and the content indicated in the fifth instruction message can also be a subset of the content indicated in the first instruction message.

[0135] The aforementioned network-side equipment can provide one or more Quality of Service (QoS) flows for the aforementioned session. QoS characteristics define the set of characteristic parameters for each network node (UE, gNB, UPF) when processing each QoS flow. Optionally, the aforementioned set of characteristic parameters is divided into: standardized QoS characteristics and operator-specific QoS characteristics. Standardized 5G QoS characteristics consist of predefined values ​​for each parameter, associated with a fixed set of indexes (e.g., 5QI values, or 5G QoS Identifier Values). Operator-specific 5G QoS characteristics are not predefined by the 3GPP standard and are configured by the operator during use.

[0136] Optionally, the QoS information includes at least one of the following:

[0137] QoS rule information for NAS messages;

[0138] QoS rule information for NAS signaling;

[0139] QoS rule information for NAS data.

[0140] In the embodiments of this application, one or two QoS guarantees (QoS rules) can be provided for a session. One QoS guarantee can be provided for a session, for example, one QoS guarantee can be provided for NAS messages; or two QoS guarantees can be provided for a session, for example, one QoS guarantee can be provided for NAS signaling and another QoS guarantee can be provided for NAS data.

[0141] Optionally, a higher QoS class identifier (QCI) can be assigned to the PDU session transmitting NAS messages compared to other PDUs not used for transmitting NAS messages (e.g., PDUs used only for transmitting application data). This prioritizes the delivery of NAS messages on the UP, meaning at least some NAS messages are delivered in the user plane, providing high-priority QoS guarantees on the PDU session and ensuring the delivery of NAS signaling between the UE and the core network. Furthermore, QoS rule information for NAS signaling can have a higher QCI than QoS rule information for other application data.

[0142] In this embodiment of the application, the existing 5G QCI can be reused, for example, QCI=5, which has the same priority as the IP Multiple Subsystem (IMS) signaling; or, a new QCI can be set, for example, QCI=0, QCI=7, which has a higher priority and lower latency.

[0143] In this embodiment, it can be applied to 6G communication networks, enabling 6G to support PDU session management for NAS services, thereby ensuring end-to-end QoS requirements of NAS messages. The network can provide the UE with a dedicated QCI or a higher-level QCI associated with the QoS flow during the PDU session establishment or modification process.

[0144] Optionally, the second information mentioned above may instruct the establishment of a specific session, for example, it may be at least one of the following: instructing the establishment of a first PDU session, wherein each first PDU session is used for one NAS service; instructing the establishment of a second PDU session, wherein each second PDU session is used for multiple NAS services; instructing the establishment of a persistent online PDU session, wherein the persistent online PDU session is used for at least one NAS service; instructing the establishment of a dedicated PDU session, wherein the dedicated PDU session is used for at least one NAS service.

[0145] Optionally, the method further includes:

[0146] If the session is not established, the terminal sends the first message to the network-side device.

[0147] In this embodiment of the application, the terminal sends the first message to the network-side device only when the session for transmitting NAS messages (the session to be established) has not been established. In other words, if the session for transmitting NAS messages (the session to be established) has already been established, the NAS messages can be transmitted directly on that session, and there is no need to send the first message to establish the new session.

[0148] Optionally, we can use a service NAS as an example to illustrate the overall delivery of a service NAS in the user plane:

[0149] 6G networks support the delivery of Serving NAS messages between UEs and Serving NFs via the user plane (i.e., via PDU sessions established for Serving NAS messages).

[0150] The 6G network will configure dedicated DNN, slicing and other information to the UE (e.g., by issuing it to the UE through policy procedures or registration procedures or by pre-configuring it in the terminal) to establish a PDU session for serving NAS messages.

[0151] A PDU session can serve one or more services provided by a serving NF. The serving NF establishes one or more PDU sessions with the UE to transmit service signaling and / or service data. The UE can establish one or more PDU sessions with the network to transmit service NAS messages.

[0152] 6G supports NAS service PDU session management to ensure end-to-end QoS requirements for NAS messages. The network can provide UEs with dedicated QCI or high-level QCI associated with QoS flows during NAS PDU session establishment or modification.

[0153] If one or more UEs share a common PDU session, the PDU session may be an always-on PDU session, a dedicated PDU session, or a default PDU session.

[0154] A persistent online (always-on) PDU session, a dedicated PDU session, or a default PDU session refers to a session where user plane resources must be established each time the PDU session transitions from 5GS Mobility Management-IDLE (5GMM-IDLE) to 5GS Mobility Management-CONNECTED (5GMM-CONNECTED), and the UE and Serving Network (NF) transmit Serving NAS messages through the user plane. The UE can request and receive instructions from higher layers to establish a PDU session as an always-on PDU session, and the network decides whether to establish the PDU session as an always-on PDU session.

[0155] (6G network supports communicating service NAS messages between the UE and the service NFs via the user plane (ie, via the PDU sessions established for service NAS messages).

[0156] 6G network configures the dedicated DNN, slice and so on information to the UE to establish the PDU session(s) for service NAS messages.

[0157] One PDU session may serve one or more kinds of service provided by the service NF. The service NF establishes one or more PDU sessions with the UE to transfer service signaling and / or service data. The UE may establish one or multiple PDU sessions with the network to transfer service NAS messages.

[0158] The 6G supports the PDU session management for service NAS to ensure the end-to-end QoS requirement.The network may provide the dedicated QCI or high-level QCI associated with the QoS flow during the PDU session establishment procedure or during the PDU session modification procedure.

[0159] If one or more UE shares one common PDU session,then this PDU session maybe the always-on PDU session or dedicated PDU session.

[0160] Always-on PDU session:A PDU session for which user-plane resources have to be established during every transition from 5GMM-IDLE mode to 5GMM-CONNECTED mode,and for which the UE and service NF transfer service NAS messages via the user plane.A UErequests a PDU session to be established as an always-on PDU session based on indication from upper layers and the network decides whether a PDU session is established as an always-on PDU session.)

[0161] In this embodiment of the application, by establishing a session to transmit NAS messages, at least some NAS messages can be transmitted on the UP plane, thereby enabling some NAS messages to be transmitted quickly between the terminal and the network, which can reduce the NAS message forwarding load pressure of some core network nodes (especially AMF).

[0162] Referring to Figure 3, which is a flowchart of a session establishment method provided in an embodiment of this application for use in a network-side device, the method includes the following steps:

[0163] Step 301: The network-side device receives a first message sent by the terminal. The first message is used to establish a session, and the session is used to transmit non-access stratum (NAS) messages.

[0164] Step 302: The network-side device sends a second message to the terminal, the second message being used in response to the first message.

[0165] Optionally, the first message includes at least one of the following:

[0166] First information, the first information being used to indicate one or more services;

[0167] The first data network name (DNN) is used to indicate the establishment of a session for transmitting NAS messages;

[0168] Information about the first slice; the information about the first slice is used to indicate the establishment of a session suitable for processing and transmitting NAS messages;

[0169] First indication information, wherein the first indication information is used for at least one of the following:

[0170] A message indicating that the session is used to transmit a service;

[0171] The session is indicated to be used to transmit messages for multiple services;

[0172] The session is indicated to be used to transmit messages for at least one service.

[0173] Optionally, the second message includes at least one of the following:

[0174] The address of the Network Function (NF) that provides the service;

[0175] The fully qualified domain name (FQDN) for NF services;

[0176] The port number for the NF service;

[0177] The second information is used to indicate one or more services;

[0178] QoS information;

[0179] The second indication information includes either a third indication information or a fourth indication information; the third indication information is used to indicate successful establishment of the session, and the fourth indication information is used to indicate rejection or partial rejection of establishing the session;

[0180] The fifth instruction information is used for at least one of the following:

[0181] A message indicating that the session is used to transmit a service;

[0182] The session is indicated to be used to transmit messages for multiple services;

[0183] The session is indicated to be used to transmit messages for at least one service.

[0184] Optionally, the QoS information includes at least one of the following:

[0185] QoS rule information for NAS messages;

[0186] QoS rule information for NAS signaling;

[0187] QoS rule information for NAS data.

[0188] Optionally, at least one of the service NF's address, the service NF's FQDN, and the service NF's port number may be carried through a protocol configuration option PCO information element or an ePCO information element.

[0189] Optionally, the service includes at least one of the following:

[0190] Location services, IP Multimedia Subsystem (IMS) services, Artificial Intelligence (AI) services, Computing power services, Artificial Intelligence of Things (AIoT) services, Sensing services, Slicing services, Satellite services, Proximity services, Immersive services, Data services, Short Message services, Energy-saving services, Task services, and Security services.

[0191] Optionally, the method further includes:

[0192] The network-side device obtains fourth information from the terminal, the fourth information including at least one of the terminal's capability information and subscription information;

[0193] The network-side device determines the second message based on at least one of the terminal's capability information and subscription information.

[0194] The network-side device in this embodiment can also interact with other network-side devices, for example, interact with a second network-side device to obtain the session policy of the session; and send a third message to a third network-side device, wherein the third message is based on information determined by the PDU session policy.

[0195] Optionally, the network-side device in this application embodiment may be an SMF, the second network-side device may be a PCF, UPF, RAN, etc., and the third network-side device may be at least one of RAN or UPF.

[0196] It should be noted that this embodiment is an implementation of the network-side device corresponding to the embodiment shown in Figure 2. The specific implementation method can be found in the relevant description of the embodiment shown in Figure 2, and all of them can achieve the same or similar beneficial effects. In order to avoid repeated description, this embodiment will not be described again.

[0197] To facilitate understanding of this application, the following schemes are provided as optional examples in the embodiments of this application. The following examples use a 6G communication network system as an example, but do not limit the scope of application of the embodiments of this application. The embodiments of this application can also be used in other communication network systems, including 5G.

[0198] Example 1: Establishing a PDU session for one service.

[0199] In this example, the terminal establishes a PDU session for each service. Within each PDU session, there may be two QoS flows: one QoS flow for service-related signaling and one QoS flow for service-related data, and both QoS flows have their QCI set to high level. Alternatively, there may be only one QoS flow, dedicated to or by default used to ensure the quality of service for service-related signaling, while service-related data is not transmitted in this PDU but in another regular PDU session.

[0200] Referring to Figure 4, the specific process of Example 1 is as follows:

[0201] 1. The UE needs to establish a PDU session for each service.

[0202] Optionally, when a UE needs to use a certain service, the UE selects a suitable RSD (slice, DNN, etc.) through URSP matching and needs to establish a PDU session to transmit NAS messages.

[0203] Optionally, the PDU session to be established can be an always-on PDU session or a dedicated session. In this way, the UE does not need to go through URSP matching to establish a PDU session. Multiple PDU sessions can be established directly after the UE is powered on. The corresponding PDU session is established for the service that the UE supports.

[0204] 2. The UE sends a session establishment request message (first message, e.g., PDU session establishment request) to the SMF. This message carries a service type (to support one of the above services) and a DNN (specifically for indicating service NAS). The above services are at least one of the following: location service, IP Multimedia Subsystem (IMS) service, Artificial Intelligence (AI) service, computing power service, Artificial Intelligence of Things (AIoT) service, sensing service, slicing service, satellite service, proximity service, immersive service, data service, short message service, energy-saving service, mission service, and security service.

[0205] 3. The SMF checks whether the UE supports the service. The SMF can interact with the UDM to obtain the UE's subscription information and obtain a list of services subscribed to by the UE, which includes one or more of the above services.

[0206] If the UE's subscription shows that the service type requested by the UE is one that the UE has already subscribed to, then the SMF will proceed to step 4; otherwise, the SMF will directly reply to the UE to reject the UE's session establishment request (e.g., a session establishment rejection message, which may optionally carry the rejection reason value: service not subscribed to, service not supported).

[0207] 4. The SMF establishes a PDU session. During the establishment process, the SMF interacts with network elements such as the PCF, UPF, and RAN to obtain policies dedicated to the service NAS PDU session. The policies include QoS parameters (profile), packet detection rules (PDR), and other information. The SMF configures the QoS profile to the base station and configures the PDR to the UPF.

[0208] In one implementation of this process, the SMF allocates two QoS flows to the PDU: one for signaling and one for data, and provides a high QoS guarantee for the signaling flow.

[0209] 5. After interacting with the NF or NF Repository Function (NRF), the SMF carries NF info (such as service NF IP, FQDN) and QoS rules to the UE in the PDU establishment success message.

[0210] In one implementation, the SMF sends the NF info to the UE through the PCO information or ePCO information element.

[0211] Example 2: Establish one PDU session for all services.

[0212] In this example, the terminal establishes only one PDU session to transmit service NAS messages; for example, the UE establishes an always-on PDU / dedicated PDU / default PDU session, which may have two QoS flows, one QoS flow for service-related signaling and one QoS flow for service-related data, or it may provide only one QoS flow.

[0213] One possible scenario is that all signaling for service NAS messages is transmitted on always-on PDU, dedicated PDU, or default PDU sessions, while the data for service NAS messages can be transmitted by establishing other PDU sessions.

[0214] Referring to Figure 5, the specific process of Example 2 is as follows:

[0215] 1. The UE needs to transmit a service NAS message, and determines that a dedicated PDU session needs to be established for transmitting service NAS messages. Optionally, the UE determines whether to transmit the service NAS on a dedicated, always-on, or default PDU.

[0216] 2. The UE sends a session establishment request (first message) to the SMF, requesting to establish a dedicated or always-on PDU. The message carries: indication information (service NAS indication or always-on PDU request indication).

[0217] 3. The SMF checks all services subscribed to by the UE, similar to Example 1. The difference is that Example 1 checks the requested services, while this example checks the services supported by the UE. Optionally, the services supported by the UE can be sent to the UE in step 5 (second information).

[0218] 4. SMF establishes a dedicated or always-on PDU, providing the same QoS guarantee for the service NAS in the PDU, such as setting only one QCI value.

[0219] 5. The SMF replies to the UE with a PDU session establishment success message (second message), which carries:

[0220] Indication information (service NAS indication or multiplexed always-on PDU indication), NF info (e.g., service NF IP, FQDN), and QoS rules, as in Example 1.

[0221] Example 3: Establishing multiple PDU sessions for all services.

[0222] In this example, the terminal UE maintains a mapping table or receives updates to the mapping from the network-side device. Several PDU sessions need to be established for all service NAS. One or more corresponding service NAS are transmitted on a PDU session. The mapping table carries the above-mentioned correspondence.

[0223] Referring to Figure 6, the specific process of Example 3 is as follows:

[0224] 1. Configure a set of mapping tables locally on the UE, for example:

[0225] {service A, service B, PDU session attribute X};

[0226] {service C, service D, service E: PDU session attribute Y}

[0227] 2. Before the UE establishes a service NAS PDU session, it makes a judgment based on the above mapping table.

[0228] When a UE needs to establish a PDU session for a service, the UE selects whether to create a new PDU session or reuse an existing one based on a mapping table. For example, if a UE has already established a PDU session with attribute X for service B and has not released it, when the UE needs to use service A, it does not need to re-establish the PDU session with attribute X; it can directly reuse the existing one. Alternatively, if a PDU session with attribute X currently exists (this session may be used for application data transmission or NAS message transmission), when the UE needs to use service A or service B, it also does not need to re-establish the PDU session with attribute X.

[0229] 3. The UE sends a session establishment request message (first message, such as PDU session establishment request) to the SMF. This message carries a service NAS indication, service type (service type or service list), and DNN (specifically used to indicate service NAS). The session establishment request message can indicate the service that the PDU is used to transmit NAS messages. It can be a single service or initially a list of services.

[0230] 4. The SMF checks whether the UE supports the service. The SMF can interact with the UDM to obtain the UE's subscription information and obtain a list of services subscribed to by the UE, which includes one or more of the above services.

[0231] If the UE's subscription information indicates that the requested service type is one that the UE has already subscribed to, the SMF proceeds to step 5; otherwise, the SMF directly replies to the UE, rejecting the UE's session establishment request (e.g., a session establishment rejection message, optionally carrying the rejection reason value: service not subscribed to, service not supported). If the UE's requested service type is partly subscribed and partly unsubscribed, then for the subscribed service, step 5 is executed, and for the unsubscribed service, the SMF replies to the UE, rejecting the UE's session establishment request.

[0232] 5. The SMF establishes a PDU session. During the establishment process, the SMF interacts with network elements such as the PCF, UPF, and RAN to obtain policies dedicated to the service NAS PDU session. These policies include QoS parameters (profile), packet detection rules (PDR), and other information. The SMF configures the QoS profile for the base station and the PDR for the UPF.

[0233] SMF can allocate two QoS flows for PDUs: one for signaling and one for data, and provides a high QoS guarantee for the signaling flow.

[0234] 6. After interacting with the NF or NF Repository Function (NRF), the SMF carries NF info (e.g., service NF IP, FQDN), service NAS indication, and QoS rules to the UE in the PDU establishment success message. In one implementation, the NF info (e.g., service NF IP, FQDN) is carried in the Protocol Configuration Option (PCO) information element or the ePCO (extended PCO) information element in the session establishment acceptance message.

[0235] The session establishment method provided in this application embodiment can be executed by a session establishment device. This application embodiment uses a session establishment device executing the session establishment method as an example. Referring to FIG7, the session establishment device 700 provided in this application embodiment is described. When the session establishment device is a terminal or a component in a terminal, the device includes:

[0236] The first sending module 701 is used to send a first message to the network-side device. The first message is used to establish a session, and the session is used to transmit non-access stratum (NAS) messages.

[0237] The first receiving module 702 is used to receive a second message sent by the network-side device, the second message being used to respond to the first message.

[0238] Optionally, the first message includes at least one of the following:

[0239] First information, the first information being used to indicate one or more services;

[0240] The first data network name (DNN) is used to indicate the establishment of a session for transmitting NAS messages;

[0241] Information about the first slice; the information about the first slice is used to indicate the establishment of a session suitable for processing and transmitting NAS messages;

[0242] First indication information, wherein the first indication information is used for at least one of the following:

[0243] A message indicating that the session is used to transmit a service;

[0244] The session is indicated to be used to transmit messages for multiple services;

[0245] The session is indicated to be used to transmit messages for at least one service.

[0246] Optionally, the second message includes at least one of the following:

[0247] The address of the Network Function (NF) that provides the service;

[0248] The fully qualified domain name (FQDN) for NF services;

[0249] The port number for the NF service;

[0250] The second information is used to indicate one or more services;

[0251] QoS information;

[0252] The second indication information includes either a third indication information or a fourth indication information; the third indication information is used to indicate successful establishment of the session, and the fourth indication information is used to indicate rejection or partial rejection of establishing the session;

[0253] The fifth instruction information is used for at least one of the following:

[0254] A message indicating that the session is used to transmit a service;

[0255] The session is indicated to be used to transmit messages for multiple services;

[0256] The session is indicated to be used to transmit messages for at least one service.

[0257] Optionally, the QoS information includes at least one of the following:

[0258] QoS rule information for NAS messages;

[0259] QoS rule information for NAS signaling;

[0260] QoS rule information for NAS data.

[0261] Optionally, at least one of the service NF's address, the service NF's FQDN, and the service NF's port number may be carried via the Protocol Configuration Option (PCO) information element or the extended Protocol Configuration Option (ePCO).

[0262] Optionally, the service includes at least one of the following:

[0263] Location services, IP Multimedia Subsystem (IMS) services, Artificial Intelligence (AI) services, Computing power services, Artificial Intelligence of Things (AIoT) services, Sensing services, Slicing services, Satellite services, Proximity services, Immersive services, Data services, Short Message services, Energy-saving services, Task services, and Security services.

[0264] Optionally, the first sending module includes at least one of the following:

[0265] The first sending submodule is used to send the first message to the network-side device after the registration process is completed;

[0266] The second sending submodule is used to send the first message to the network-side device after matching the terminal routing policy URSP rules;

[0267] The third sending submodule is used to send the first message to the network-side device upon receiving instructions from a higher layer;

[0268] The fourth sending submodule is used to send the first message to the network-side device when the session is determined based on third information, wherein the third information includes an association between one or more services and the session.

[0269] Optionally, the device further includes:

[0270] The second sending module is used to send the first message to the network-side device if the session has not been established.

[0271] It should be noted that the session establishment apparatus provided in this application embodiment is an apparatus capable of executing the session establishment method shown in FIG2 above. Therefore, all implementation methods in the above-described session establishment method embodiments are applicable to this session establishment apparatus and can achieve the same or similar beneficial effects. To avoid repetition, this embodiment will not elaborate further.

[0272] The session establishment method provided in this application embodiment can be executed by a session establishment device. This application embodiment uses a session establishment device executing the session establishment method as an example. Referring to FIG8, the session establishment device 800 provided in this application embodiment is described. When the session establishment device is a network-side device or a component of a network-side device, the device includes:

[0273] The second receiving module 801 is used to receive a first message sent by the terminal, the first message is used to establish a session, and the session is used to transmit non-access stratum (NAS) messages.

[0274] The third sending module 802 is used to send a second message to the terminal, the second message being used in response to the first message.

[0275] Optionally, the device further includes:

[0276] The acquisition module is used to acquire fourth information of the terminal, the fourth information including at least one of the terminal's capability information and contract information;

[0277] The determining module is used to determine the second message based on at least one of the terminal's capability information and subscription information.

[0278] Optionally, the first message includes at least one of the following:

[0279] First information, the first information being used to indicate one or more services;

[0280] The first data network name (DNN) is used to indicate the establishment of a session for transmitting NAS messages;

[0281] Information about the first slice; the information about the first slice is used to indicate the establishment of a session suitable for processing and transmitting NAS messages;

[0282] First indication information, wherein the first indication information is used for at least one of the following:

[0283] A message indicating that the session is used to transmit a service;

[0284] The session is indicated to be used to transmit messages for multiple services;

[0285] The session is indicated to be used to transmit messages for at least one service.

[0286] Optionally, the second message includes at least one of the following:

[0287] The address of the Network Function (NF) that provides the service;

[0288] The fully qualified domain name (FQDN) for NF services;

[0289] The port number for the NF service;

[0290] The second information is used to indicate one or more services;

[0291] QoS information;

[0292] The second indication information includes either a third indication information or a fourth indication information; the third indication information is used to indicate successful establishment of the session, and the fourth indication information is used to indicate rejection or partial rejection of establishing the session;

[0293] The fifth instruction information is used for at least one of the following:

[0294] A message indicating that the session is used to transmit a service;

[0295] The session is indicated to be used to transmit messages for multiple services;

[0296] The session is indicated to be used to transmit messages for at least one service.

[0297] Optionally, the QoS information includes at least one of the following:

[0298] QoS rule information for NAS messages;

[0299] QoS rule information for NAS signaling;

[0300] QoS rule information for NAS data.

[0301] Optionally, at least one of the service NF's address, the service NF's FQDN, and the service NF's port number may be carried via the Protocol Configuration Option (PCO) information element or the extended Protocol Configuration Option (ePCO).

[0302] Optionally, the service includes at least one of the following:

[0303] Location services, IP Multimedia Subsystem (IMS) services, Artificial Intelligence (AI) services, Computing power services, Artificial Intelligence of Things (AIoT) services, Sensing services, Slicing services, Satellite services, Proximity services, Immersive services, Data services, Short Message services, Energy-saving services, Task services, and Security services.

[0304] It should be noted that the session establishment apparatus provided in this application embodiment is an apparatus capable of executing the session establishment method shown in FIG3 above. Therefore, all implementation methods in the above-described session establishment method embodiments are applicable to this session establishment apparatus and can achieve the same or similar beneficial effects. To avoid repetition, this embodiment will not elaborate further.

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

[0306] The session establishment 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.

[0307] The session establishment apparatus provided in this application embodiment can implement the various processes implemented in the method embodiment of FIG2 or FIG3 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0308] As shown in Figure 9, this application embodiment also provides a communication device 900, including a processor 901 and a memory 902. The memory 902 stores programs or instructions that can run on the processor 901. For example, when the communication device 900 is a terminal, the program or instructions executed by the processor 901 implement the various steps of the above-described session establishment method embodiment and achieve the same technical effect. When the communication device 900 is a network-side device, the program or instructions executed by the processor 901 implement the various steps of the above-described session establishment method embodiment and achieve the same technical effect. To avoid repetition, this will not be described again here.

[0309] 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 embodiment shown in FIG2. This terminal embodiment corresponds to the above-described terminal-side method embodiment, 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 may be the session establishment device shown in FIG7. Specifically, FIG10 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0310] The terminal 1000 includes, but is not limited to, at least some of the following components: radio frequency unit 1001, network module 1002, audio output unit 1003, input unit 1004, sensor 1005, display unit 1006, user input unit 1007, interface unit 1008, memory 1009, and processor 1010.

[0311] Those skilled in the art will understand that the terminal 1000 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to the processor 1010 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 10 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.

[0312] It should be understood that, in this embodiment, the input unit 1004 may include a graphics processor 10041 and a microphone 10042. The graphics processor 10041 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 1006 may include a display panel 10061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1007 includes a touch panel 10071 and at least one of other input devices 10072. The touch panel 10071 is also called a touch screen. The touch panel 10071 may include a touch detection device and a touch controller. Other input devices 10072 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.

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

[0314] The memory 1009 can be used to store software programs or instructions, as well as various data. The memory 1009 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 1009 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 1009 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0315] The processor 1010 may include one or more processing units; optionally, the processor 1010 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 the processor 1010.

[0316] The radio frequency unit 1001 is used for:

[0317] Send a first message to the network-side device. The first message is used to establish a session, and the session is used to transmit non-access stratum (NAS) messages.

[0318] The terminal receives a second message sent by the network-side device, the second message being used in response to the first message.

[0319] 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 2, and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0320] 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 embodiment shown in FIG3. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and can achieve the same technical effect.

[0321] Specifically, this application embodiment also provides a network-side device, which may be the session establishment device shown in FIG8. As shown in FIG11, the network-side device 1100 includes: an antenna 111, a radio frequency device 112, a baseband device 113, a processor 114, and a memory 115. The antenna 111 is connected to the radio frequency device 112. In the uplink direction, the radio frequency device 112 receives information through the antenna 111 and sends the received information to the baseband device 113 for processing. In the downlink direction, the baseband device 113 processes the information to be transmitted and sends it to the radio frequency device 112. The radio frequency device 112 processes the received information and transmits it through the antenna 111.

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

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

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

[0325] The radio frequency device 112 is used for:

[0326] The receiving terminal sends a first message, which is used to establish a session, and the session is used to transmit non-access stratum (NAS) messages;

[0327] A second message is sent to the terminal, the second message being a response to the first message.

[0328] In addition, the network-side device 1100 of this application embodiment also includes: a program or instructions stored in the memory 115 and executable on the processor 114. The processor 114 calls the program or instructions in the memory 115 to execute the methods executed by each module shown in FIG8 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0329] Specifically, this application embodiment also provides a network-side device. As shown in FIG12, the network-side device 1200 includes: a processor 1201, a network interface 1202, and a memory 1203. The network-side device may be the session establishment device shown in FIG8. The network interface 1202 is, for example, a Common Public Radio Interface (CPRI).

[0330] Network interface 1202 is used for:

[0331] The receiving terminal sends a first message, which is used to establish a session, and the session is used to transmit non-access stratum (NAS) messages;

[0332] A second message is sent to the terminal, the second message being a response to the first message.

[0333] In addition, the network-side device 1200 of this application embodiment also includes: a program or instructions stored in the memory 1203 and executable on the processor 1201. The processor 1201 calls the program or instructions in the memory 1203 to execute the methods executed by each module shown in FIG8 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0334] 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 session establishment method embodiments shown in FIG2 or FIG3 above and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0335] 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.

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

[0337] 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.

[0338] 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 session establishment method embodiments shown in FIG2 or FIG3 above, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0339] This application embodiment also provides a communication system, including: a terminal and a network-side device, wherein the terminal can be used to execute the steps of the session establishment method shown in FIG2 as described above, and the network-side device can be used to execute the steps of the session establishment method shown in FIG3 as described above.

[0340] 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.

[0341] 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.

[0342] 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

1. A session establishment method, comprising: The terminal sends a first message to the network-side device. The first message is used to establish a session, and the session is used to transmit non-access stratum (NAS) messages. The terminal receives a second message sent by the network-side device, the second message being used in response to the first message.

2. The method of claim 1, wherein the first message comprises at least one of the following: First information, the first information being used to indicate one or more services; The first data network name (DNN) is used to indicate the establishment of a session for transmitting NAS messages; Information about the first slice; the information about the first slice is used to indicate the establishment of a session suitable for processing NAS messages; First indication information, wherein the first indication information is used for at least one of the following: A message indicating that the session is used to transmit a service; The session is indicated to be used to transmit messages for multiple services; The session is indicated to be used to transmit messages for at least one service.

3. The method according to any one of claims 1-2, wherein the second message comprises at least one of the following: The address of the Network Function (NF) that provides the service; The fully qualified domain name (FQDN) for NF services; The port number for the NF service; The second information is used to indicate one or more services; QoS information; The second instruction information includes either the third instruction information or the fourth instruction information; The third indication information is used to indicate that the session has been successfully established, and the fourth indication information is used to indicate that the session is rejected or partially rejected. The fifth instruction information is used for at least one of the following: A message indicating that the session is used to transmit a service; The session is indicated to be used to transmit messages for multiple services; The session is indicated to be used to transmit messages for at least one service.

4. The method of claim 3, wherein the QoS information includes at least one of the following: QoS rule information for NAS messages; QoS rule information for NAS signaling; QoS rule information for NAS data.

5. The method according to claim 3 or 4, wherein at least one of the address of the service NF, the FQDN of the service NF, and the port number of the service NF is carried by a protocol configuration option PCO information element or an extended protocol configuration option ePCO.

6. The method according to any one of claims 1-5, wherein the terminal sends a first message to the network-side device, comprising at least one of the following: After completing the registration process, the terminal sends the first message to the network-side device. After matching the Terminal Routing Policy (URSP) rules, the terminal sends the first message to the network-side device. Upon receiving instructions from a higher layer, the terminal sends the first message to the network-side device. When the terminal determines the session based on the third information, it sends the first message to the network-side device, wherein... The third information includes the association between one or more services and sessions.

7. The method according to any one of claims 2-6, wherein the service comprises at least one of the following: Location services, IP Multimedia Subsystem (IMS) services, Artificial Intelligence (AI) services, Computing power services, Artificial Intelligence of Things (AIoT) services, Sensing services, Slicing services, Satellite services, Proximity services, Immersive services, Data services, Short Message services, Energy-saving services, Task services, and Security services.

8. The method according to any one of claims 1-7, further comprising: If the session is not established, the terminal sends the first message to the network-side device.

9. A method for establishing a session, comprising: The network-side device receives a first message sent by the terminal. The first message is used to establish a session, and the session is used to transmit non-access stratum (NAS) messages. The network-side device sends a second message to the terminal, the second message being used in response to the first message.

10. The method of claim 9, wherein the first message comprises at least one of the following: First information, the first information being used to indicate one or more services; The first data network name (DNN) is used to indicate the establishment of a session for transmitting NAS messages; Information about the first slice; the information about the first slice is used to indicate the establishment of a session suitable for processing and transmitting NAS messages; First indication information, wherein the first indication information is used for at least one of the following: A message indicating that the session is used to transmit a service; The session is indicated to be used to transmit messages for multiple services; The session is indicated to be used to transmit messages for at least one service.

11. The method according to any one of claims 9-10, wherein the second message comprises at least one of the following: The address of the Network Function (NF) that provides the service; The fully qualified domain name (FQDN) for NF services; The port number for the NF service; The second information is used to indicate one or more services; QoS information; The second instruction information includes either the third instruction information or the fourth instruction information; The third indication information is used to indicate that the session has been successfully established, and the fourth indication information is used to indicate that the session is rejected or partially rejected. The fifth instruction information is used for at least one of the following: A message indicating that the session is used to transmit a service; The session is indicated to be used to transmit messages for multiple services; The session is indicated to be used to transmit messages for at least one service.

12. The method of claim 11, wherein the QoS information comprises at least one of the following: QoS rule information for NAS messages; QoS rule information for NAS signaling; QoS rule information for NAS data.

13. The method according to claim 11 or 12, wherein at least one of the address of the service NF, the FQDN of the service NF, and the port number of the service NF is carried by a protocol configuration option PCO information element or an extended protocol configuration option ePCO.

14. The method according to any one of claims 10-13, wherein the service comprises at least one of the following: Location services, IP Multimedia Subsystem (IMS) services, Artificial Intelligence (AI) services, Computing power services, Artificial Intelligence of Things (AIoT) services, Sensing services, Slicing services, Satellite services, Proximity services, Immersive services, Data services, Short Message services, Energy-saving services, Task services, and Security services.

15. The method according to any one of claims 9-14, further comprising: The network-side device obtains fourth information from the terminal, the fourth information including at least one of the terminal's capability information and subscription information; The network-side device determines the second message based on at least one of the terminal's capability information and subscription information.

16. A session establishment apparatus, comprising: The first sending module is used to send a first message to the network-side device. The first message is used to establish a session, and the session is used to transmit non-access stratum (NAS) messages. The first receiving module is configured to receive a second message sent by the network-side device, the second message being used in response to the first message.

17. The apparatus of claim 16, wherein the first transmitting module comprises at least one of the following: The first sending submodule is used to send the first message to the network-side device after the registration process is completed; The second sending submodule is used to send the first message to the network-side device after matching the terminal routing policy URSP rules; The third sending submodule is used to send the first message to the network-side device upon receiving instructions from a higher layer; The fourth sending submodule is used to send the first message to the network-side device when the session is determined based on third information, wherein the third information includes an association between one or more services and the session.

18. The apparatus according to claim 16 or 17, further comprising: The second sending module is used to send the first message to the network-side device if the session has not been established.

19. A session establishment apparatus, comprising: The second receiving module is used to receive a first message sent by the terminal, the first message being used to establish a session, the session being used to transmit non-access stratum (NAS) messages; The third sending module is used to send a second message to the terminal, the second message being used in response to the first message.

20. The apparatus of claim 19, further comprising: The acquisition module is used to acquire fourth information of the terminal, the fourth information including at least one of the terminal's capability information and contract information; The determining module is used to determine the second message based on at least one of the terminal's capability information and subscription information.

21. A terminal comprising 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 session establishment method as claimed in any one of claims 1 to 8.

22. A network-side device, comprising 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 session establishment method as claimed in any one of claims 9 to 15.

23. A readable storage medium storing a program or instructions that, when executed by a processor, implement the session establishment method as described in any one of claims 1-8, or implement the steps of the session establishment method as described in any one of claims 9 to 15.

24. A computer program product stored in a storage medium, the computer program product being executed by at least one processor to implement the steps of the session establishment method as claimed in any one of claims 1 to 8, or to implement the steps of the session establishment method as claimed in any one of claims 9 to 15.

25. A chip comprising a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the steps of the session establishment method as described in any one of claims 1 to 8, or to implement the steps of the session establishment method as described in any one of claims 9 to 15.

26. A session establishment apparatus configured to perform the steps of the session establishment method as claimed in any one of claims 1 to 8, or to perform the steps of the session establishment method as claimed in any one of claims 9 to 15.

Images