Connectionless service message transmission

By introducing shared transport tunnels and CLSI binding mechanisms into the communication network, the problems of signaling overhead and resource waste in connectionless service message transmission are solved, achieving efficient connectionless services and simplified mobility management.

CN123075735APending Publication Date: 2026-11-10NOKIA TECHNOLOGIES OY
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202610623674.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2025-05-08
Filing Date
2026-05-08
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

In the existing technology, communication networks lack an effective mechanism to manage the establishment and maintenance of shared tunnels in connectionless service message transmission, which requires dedicated network signaling each time a UE accesses the network, increasing signaling overhead and wasting resources, and failing to effectively solve the mobility management of UEs between different cells.

Method used

By defining a shared transport tunnel and utilizing an extension of the GTP-U protocol, the RAN and UPF maintain the binding between the UE Connectionless Service Identifier (CLSI) and the shared tunnel, supporting connectionless message transmission, and managing the UE's connectionless service between different cells through radio configuration and binding information.

Benefits of technology

It achieves efficient transmission of connectionless service messages, reduces signaling overhead during each access, optimizes resource utilization, supports connectionless services for UEs in different cells, and simplifies mobility management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123075735A_ABST
    Figure CN123075735A_ABST
Patent Text Reader

Abstract

Example embodiments of this disclosure relate to connectionless service message transmission. In one method, a first network entity receives a first connectionless service message from a device, the first connectionless service message including a connectionless service identifier (CLSI) associated with the device. The first network entity transmits a second connectionless service message to a second network entity, the second connectionless service message including the CLSI and a request for binding the device to a transport tunnel for at least one connectionless service. The first network entity receives from the second network entity an indication of acknowledgment or rejection of the binding of the device to the transport tunnel.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Various exemplary embodiments of this disclosure generally relate to the telecommunications field, and more particularly to methods, apparatuses, devices, and computer-readable storage media for connectionless (CL) service message transmission. Background Technology

[0002] A communication network can serve as a facility to enable communication between two or more communication devices or to provide communication devices with access to a data network. A mobile or wireless communication network is an example of a communication network. Services can be provided to communication devices by an application server.

[0003] Communication networks can operate according to standards provided by organizations such as the 3rd Generation Partnership Project (3GPP) or the European Telecommunications Standards Institute (ETSI). Examples of standards provided by 3GPP are the so-called 3GPP standards for cellular technologies, such as those for 4G, 5G, and 6G technologies. Summary of the Invention

[0004] In a first aspect of this disclosure, a first network entity is provided. The first network entity includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first network entity to at least: receive a first connectionless service message from a device, the first connectionless service message including a connectionless service identifier (CLSI) associated with the device; transmit a second connectionless service message to a second network entity, the second connectionless service message including the CLSI and a request for binding the device to a transport tunnel for at least one connectionless service; and receive from the second network entity an indication of acknowledgment or rejection of the binding of the device to the transport tunnel.

[0005] In a second aspect of this disclosure, a second network entity is provided. The second network entity includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second network entity to at least: receive a connectionless service message from a first network entity, the connectionless service message including a connectionless service identifier (CLSI) associated with a device and a request for binding the device to a transport tunnel for at least one connectionless service; and, based on the CLSI, transmit to the first network entity an indication of acknowledgment or rejection of the binding of the device to the transport tunnel.

[0006] In a third aspect of this disclosure, an apparatus is provided. The apparatus includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: determine a radio configuration for connectionless service by monitoring broadcast information from at least one cell, the radio configuration being associated with a target cell of a network entity; and transmit a connectionless service message including a connectionless service identifier (CLSI) associated with the apparatus to the network entity via random access to the network entity; and receive another connectionless service message including the CLSI or another CLSI from the network entity.

[0007] In a fourth aspect of this disclosure, a method is provided. The method includes: receiving a first connectionless service message from a device, the first connectionless service message including a connectionless service identifier (CLSI) associated with the device; transmitting a second connectionless service message to a second network entity, the second connectionless service message including the CLSI and a request for binding the device to a transport tunnel for at least one connectionless service; and receiving from the second network entity an indication of acknowledgment or rejection of the binding of the device to the transport tunnel.

[0008] In a fifth aspect of this disclosure, a method is provided. The method includes: receiving a connectionless service message from a first network entity, the connectionless service message including a connectionless service identifier (CLSI) associated with a device and a request for binding the device to a transport tunnel for at least one connectionless service; and, based on the CLSI, transmitting to the first network entity an indication of acknowledgment or rejection of the binding of the device to the transport tunnel.

[0009] In a sixth aspect of this disclosure, a method is provided. The method includes: determining a radio configuration for connectionless service by monitoring broadcast information from at least one cell, the radio configuration being associated with a target cell of a network entity; transmitting a connectionless service message including a connectionless service identifier (CLSI) associated with a device to the network entity via random access to the network entity; and receiving another connectionless service message including the CLSI or another CLSI from the network entity.

[0010] In a seventh aspect of this disclosure, a first network entity is provided. The first network entity includes: means for receiving a first connectionless service message from a device, the first connectionless service message including a connectionless service identifier (CLSI) associated with the device; means for transmitting a second connectionless service message to a second network entity, the second connectionless service message including the CLSI and a request for binding the device to a transport tunnel for at least one connectionless service; and means for receiving from the second network entity an indication of acknowledgment or rejection of binding the device to the transport tunnel.

[0011] In an eighth aspect of this disclosure, a second network entity is provided. The second network entity includes: components for receiving a connectionless service message from a first network entity, the connectionless service message including a connectionless service identifier (CLSI) associated with a device and a request for binding the device to a transport tunnel for at least one connectionless service; and components for transmitting to the first network entity, based on the CLSI, an indication of acknowledgment or rejection of the binding of the device to the transport tunnel.

[0012] In a ninth aspect of this disclosure, an apparatus is provided. The apparatus includes: means for determining a radio configuration for connectionless service by monitoring broadcast information from at least one cell, the radio configuration being associated with a target cell of a network entity; means for transmitting a connectionless service message including a connectionless service identifier (CLSI) associated with the apparatus to a network entity via random access to the network entity; and means for receiving another connectionless service message including the CLSI or another CLSI from the network entity.

[0013] In a tenth aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to perform at least the method according to the fourth, fifth, or sixth aspect.

[0014] It should be understood that the summary portion is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0015] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which: Figure 1 An example communication environment in which example embodiments of this disclosure may be implemented is shown; Figure 2A An example diagram illustrating connection-oriented (CO) user plane access is shown; Figure 2B An example diagram illustrating the CL access mode is shown; Figure 3 Signaling flows for CL service message transmission according to some example embodiments of this disclosure are shown; Figure 4 The structure of the shared tunnel between the DU and CU-UP and between the RAN and UPF is shown according to some example embodiments of the present disclosure; Figure 5 The signaling flow for CL access initiated by a UE during CL Service (CLS)-INACTIVE, according to some example embodiments of the present disclosure, is illustrated; Figure 6The signaling flow of a UE-initiated CL access when CLS-ACTIVE is shown according to some example embodiments of this disclosure; Figure 7 The signaling flow of CL access initiated by DN when CLS-ACTIVE is shown according to some example embodiments of the present disclosure; Figure 8 Signaling flows for intra-DU mobility according to some example embodiments of this disclosure are shown; Figure 9 Signaling flows for inter-DU mobility according to some example embodiments of this disclosure are shown; Figure 10 Signaling flows for inter-RAN mobility according to some example embodiments of this disclosure are shown; Figure 11 The following is illustrated: a signaling flow for DL ​​message transmission failure according to some example embodiments of the present disclosure; Figure 12 The following are illustrated signaling flows for processing CL-RNTI and CLSI validity expiration according to some example embodiments of this disclosure; Figure 13 Signaling flows for RAN detection to handle excessive connectionless traffic are shown according to some example embodiments of this disclosure; Figure 14 Signaling flows for establishing a shared CLS tunnel are shown according to some example embodiments of this disclosure; Figure 15 A flowchart is shown illustrating a method implemented at a network entity according to some example embodiments of the present disclosure; Figure 16 A flowchart is shown illustrating a method implemented at a CN entity according to some example embodiments of this disclosure; Figure 17 A flowchart is shown of another method implemented at a device according to some example embodiments of the present disclosure; Figure 18 A simplified block diagram of a device suitable for implementing example embodiments of the present disclosure is shown; and Figure 19 A block diagram of an example computer-readable medium according to some example embodiments of the present disclosure is shown.

[0016] In all the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0017] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. The embodiments described herein can be implemented in various ways other than those described below.

[0018] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0019] References to "an embodiment," "embodiment," "example embodiment," etc., in this disclosure indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment must include that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Additionally, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is believed that incorporating other embodiments, whether explicitly described or not, to affect such a feature, structure, or characteristic is within the knowledge of those skilled in the art.

[0020] It should be understood that although terms such as "first," "second," etc., preceding nouns may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another, and they do not restrict the order of nouns. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0021] As used herein, “at least one of the following: a list of two or more elements” and “at least one of the following: a list of two or more elements” and similar wording (where the list of two or more elements is connected by “and” or “or”) means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0022] As used herein, unless explicitly stated otherwise, the execution step “in response to A” does not indicate that the step is performed immediately after “A” occurs, and may include one or more intermediate steps.

[0023] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that, when used herein, the terms “comprises,” “comprising,” “has,” “having,” “includes,” and / or “including” specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0024] As used in this application, the term "circuit system" may refer to one or more of the following: (a) Hardware circuit system implementation only (such as implementations in analog, digital, and / or quantum circuit systems) and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of analog, digital, and / or quantum hardware circuit systems with software / firmware, and (ii) Any or all portions of a hardware processor (including digital and / or quantum processors(s) with software), and memory that works together to enable devices such as mobile devices, computing devices, or servers to perform various functions, and (c) Any or all parts of a hardware circuit system, such as a microprocessor, processor and / or quantum processor, that require software (e.g., firmware) to operate, but which may not exist when no software is required to operate.

[0025] This definition of circuit system applies to all uses of the term in this application (including in any claim). As another example, as used in this application, the term circuit system also covers only hardware circuit systems or processors (or processors in general) or a portion thereof and their accompanying software and / or firmware implementations. The term circuit system also covers, for example and if applicable to a particular claim element, baseband integrated circuit systems or processor integrated circuit systems for mobile devices or similar integrated circuit systems in servers, cellular network devices, or other computing or network devices.

[0026] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-A Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation of communication protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), 5.5G, sixth-generation (6G) communication protocols and / or any other currently known or future-developed protocols. Embodiments of this disclosure can be applied to a variety of communication systems. Given the rapid development of communications, there will certainly be future types of communication technologies and systems that embody the future types of this disclosure. The scope of this disclosure should not be construed as limited to the aforementioned systems.

[0027] As used herein, the terms “network device,” “network entity,” “Radio Access Network (RAN) device,” or “RAN node” refer to a node in a communication network through which terminal devices access the network and receive services. Depending on the terminology and technology applied, a network device can refer to a base station (BS) or access point (AP), such as a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also known as a gNB), a Remote Radio Unit (RRU), a Radio Header (RH), a Remote Radio Header End (RRH), a relay, an Integrated Access and Backhaul (IAB) node, a low-power node (such as a femtosecond or picosecond), a non-terrestrial network (NTN) or non-terrestrial network device (such as a satellite network device), low Earth orbit (LEO) satellites and geostationary Earth orbit (GEO) satellites, spacecraft network devices, etc. In some example embodiments, a RAN split architecture can be applied. That is, a RAN node can include a centralized unit (CU) and a distributed unit (DU). A CU can include a control plane (CP) (i.e., CU-CP) and a user plane (UP) (i.e., CU-UP). For example, CU and DU can be located at the IAB donor node. The IAB node includes the mobile terminal (IAB-MT) portion, which behaves as a UE toward the parent node, and the DU portion of the IAB node behaves as a base station toward the next-hop IAB node.

[0028] The term "terminal device" refers to any terminal device capable of wireless communication. As an example and not a limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. The terminal equipment may also correspond to the mobile termination (MT) portion of an IAB node (e.g., a relay node). In the following description, the terms "terminal equipment," "communication equipment," "terminal," "user equipment," and "UE" are used interchangeably.

[0029] As used herein, the term "core network function" or "core network entity" can be implemented as a core network entity that includes a combination of a hardware processing circuitry system and software and / or firmware comprising machine-readable instructions, or software comprising machine-readable instructions executable by at least one processor of the hardware processing circuitry system of the device. The hardware processing circuitry system includes at least one processor and at least one memory storing machine-readable instructions executable by at least one processor of the hardware processing circuitry system. The processor includes any one or a combination of accelerators, microprocessors, cores of multi-core microprocessors, microcontrollers, programmable integrated circuit systems, programmable gate arrays, digital signal processors, central processing units, graphics processing units, and tensor processing units. The memory includes any or a combination of volatile or non-volatile memory (e.g., flash memory, cache, random access memory (RAM), and / or read-only memory (ROM)). The memory stores machine-readable instructions for the software and / or firmware executed by at least one processor of the hardware processing circuitry system. The machine-readable instructions are executable by at least one processor of the hardware processing circuitry system, causing the hardware processing circuitry system to perform the actions or operations of the methods described herein. For example, the session management function described in this paper can be implemented as a session management entity, and the session management policy control function described in this paper can be implemented as a session management policy control entity.

[0030] As used herein, the terms “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink resource,” or “downlink resource” can refer to any resource used to perform communication, such as communication between a terminal device and a network device, including resources in the time domain, frequency domain, spatial domain, code domain, or any other combination of time, frequency, spatial, and / or code domain resources used to enable communication. In the following, unless explicitly stated otherwise, resources in the frequency and time domains will be used as examples of transmission resources used to describe some exemplary embodiments of this disclosure. Note that the exemplary embodiments of this disclosure are equally applicable to other resources in other domains.

[0031] Figure 1 An example communication environment 100 in which exemplary embodiments of the present disclosure may be implemented is shown. The communication environment 100 includes a plurality of devices or apparatuses, such as terminal device 110, RAN node 120 and CN entity 130.

[0032] RAN node 120 can provide one or more coverage areas (or cells) for terminal equipment 110. RAN node 120 may include CU (Central Unit) and DU (Distributed Unit). CU may include CU-CP (CU Control Plane) and CU-UP (CU User Plane). CU-CP and DU can be connected to each other via a so-called FL-C interface. CU-UP and DU can be connected to each other via a so-called FL-U interface. RAN node 120 may refer to a base station (such as a Next Generation Node B, gNB).

[0033] Terminal device 110 and / or RAN node 120 can communicate with the CN. For example, terminal device 110 and / or RAN node 120 can communicate with CN entity 130. In some examples, the network entity may include or implement User Plane Function (UPF). UPF can handle user data traffic, including packet routing, forwarding, and Quality of Service (QoS) enforcement. CN entity 130 can connect the RAN to an external data network (DN) 150, such as the Internet or any other suitable network. CN entity 130 can forward data traffic from terminal device 110 to data network 150. CN entity 130 can perform tasks such as traffic optimization, data buffering, and local interruption of edge computing.

[0034] In addition, another CN entity 140 may be located within the communication environment 100. For example, CN entity 130, RAN node 120, and / or terminal device 110 may communicate with CN entity 140. As an example, CN entity 140 may include or implement Access and Mobility Management (AMF), Session Management (SMF), etc. AMF can manage device connectivity and mobility, such as registration, authentication, and tracking location changes. SMF can control user sessions, including the establishment, modification, and termination of user sessions.

[0035] In some example embodiments, the direction from RAN node 120 or CN entity 130 or CN entity 140 to terminal device 110 is referred to as the downlink (DL), while the direction from terminal device 110 to RAN node 120 or CN entity 130 or CN entity 140 is referred to as the uplink (UL). In the DL, RAN node 120 or CN entity 130 or CN entity 140 is a transmit (TX) device (or transmitter), and terminal device 110 is a receive (RX) device (or receiver). In the UL, terminal device 110 is a TX device (or transmitter), and RAN node 120 or CN entity 130 or CN entity 140 is an RX device (or receiver).

[0036] It should be understood that Figure 1 The number of devices and their connections shown are for illustrative purposes only and do not imply any limitation. Communication environment 100 may include any suitable number of devices configured to implement the exemplary embodiments of this disclosure. Although not shown, it should be understood that one or more additional devices may be located in a cell provided by RAN node 120, and one or more additional cells may be deployed in communication environment 100, each cell associated with the same RAN node 120 or other RAN nodes. Note that although shown as a network node or entity, RAN node 120, CN entity 130, or CN entity 140 may be another device besides a network node or entity. Although illustrated as a terminal device, terminal device 110 may be another device besides a terminal device.

[0037] Communication in communication environment 100 may be implemented according to any suitable communication protocol, including but not limited to cellular communication protocols defined by 3GPP technical specifications, wireless local network communication protocols such as IEEE 802.11, and / or any other currently known or future-developed protocols. Furthermore, communication may utilize any suitable wireless communication technology, including but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), Discrete Fourier Transform Extended OFDM (DFT-s-OFDM), and / or any other currently known or future-developed technologies.

[0038] In some examples, communication between devices and nodes in communication environment 100 can utilize CO access and / or CL access. Figure 2A Example Figure 200A illustrates CO user plane access. As shown, multiple UEs (such as UE 210-1, ..., UE 210-N (N is a positive integer)) are connected to RAN 220. For discussion purposes, UE 210-1, ..., UE 210-N can be collectively referred to as "UE 210" or individually. In CO access mode, UE 210 can communicate with AMF or SMF 240 via Radio Resource Control (RRC) - Packet Data Convergence Protocol (PDCPc) for the control plane. UE 210 can communicate with UPF 230 via Data Radio Bearer (DRB) - Packet Data Convergence Protocol (PDCPu) for the user plane. UPF 230 can connect to DN 250 via Protocol Data Unit (PDU) anchors. This CO access mode uses the RRC Connected (RRC_CONNECTED) mode.

[0039] Figure 2BExample Figure 200B illustrates the CL access mode. In CL access mode, UE 210 can communicate with CL serving (CLS) trunk 260 via CL-PDCPu. CLS trunk 260 is connected to CLS trunk 270 in UPF 230. CLS trunk 270 can be connected to the PDU anchor in UPF 230 for DN 250 via at least one association (such as association 280-1 for UE 210-1 and association 280-N for UE 210-N). For the purposes of discussion, association 280-1, ..., association 280-N can be collectively referred to or individually as "association 280". It can also be referred to as "UE binding". For example, association 280-1 can refer to the association between UE 210-1 and the PDU anchor of serving DN 250 in UPF 230. Furthermore, a given UE can use CL mode access to communicate with one or more data networks. In this scenario, the same UE can have one or more CL mode access associations, one for each data network served, where potentially different UPFs are used to provide CL mode access for different data networks serving the same UE.

[0040] The CL concept for networks such as 6G provides a mechanism for UEs to obtain limited PDU session access when in an RRC_IDLE state. When in an RRC_INACTIVE state, CL access can be used as a supplement to CO mode access using RRC_CONNECTED and Small Data Transmission (SDT).

[0041] The general concept of connectionless access is based on the following assumptions: the UE can obtain a radio configuration for connectionless access, and this configuration remains valid within a defined set of cells when the UE is in RRC_IDLE. Assuming the UE remains within the valid radio configuration area and has a valid temporary identifier for connectionless access, the UE can initiate connectionless access without requiring RRC or Non-Access Stratum (NAS) signaling, and the RAN can serve the UE without any stored UE context information.

[0042] Furthermore, since shared transport for user plane services within the RAN and on the RAN-core interface will be used instead of dedicated transport to support connectionless access, dedicated network interface control plane signaling will not be required each time a UE initiates connectionless access.

[0043] Connectionless access offers the potential to significantly reduce the need for the UE to send context information and RRC and NAS signaling each time a UE needs to send short data messages. Furthermore, it reduces the need for the RAN to maintain collected UE context information when the UE is in Connection Management (CM)_CONNECTED (i.e., in RRC_CONNECTED or RRC_INACTIVE), and the need to establish RAN and core networks to establish and hold dedicated user plane connections held by a given UE for each active PDU session.

[0044] In some mechanisms, 5G CIoT (Cellular Internet of Things) does not employ a complete proposal for connectionless access. A similar UE identifier (called UPF CL Service ID or UCLSI) and the general principles governing UE-initiated messages, mobility support, and UPF-triggered service delivery mode changes are described. However, it does not describe how the RAN and UPF learn UE bindings, how shared tunnels are established, how the RAN or UPF can trigger service delivery mode changes, or how shared tunnels can be used to carry services associated with multiple UEs and how it can be defined as an evolution of GTPu (General Packet Radio System (GPRS) Tunneling Protocol user plane, such as that defined in 3GPP TS 29.281).

[0045] The RRC-INACTIVE state and the associated mechanism for providing Small Data Transfer (SDT) when the UE is in the RRC-INACTIVE state are defined. When the UE is in the RRC-INACTIVE state, this solution requires the last serving RAN to hold the UE context information and requires a significant amount of intra-RAN signaling to handle the SDT. The RRC-INACTIVE mechanism is not a connectionless solution and requires dedicated user plane connections for each UE within the RAN and CN.

[0046] In some mechanisms, general approaches to using connectionless access in mobile networks and radio interface aspects of a possible connectionless access mechanism are discussed. However, how the principles of connectionless access can be applied to mobile networks using shared transport tunnels is not discussed.

[0047] Furthermore, the GTPu protocol and the mechanism for adding extended headers are defined. However, no specific extended headers are discussed to meet the requirements of connectionless message transmission via a shared tunnel.

[0048] Work is underway on how to ensure the secure transmission of CL messages between the UE and the UPF. In particular, issues such as how to establish an association between the UE and the UPF, and the protocols or messages used for association, have become relevant.

[0049] Stateless RAN and RAN-Core user plane connectionless access requires solutions for transmitting UL and DL messages between the UE and UPF, thereby terminating the connectionless access mechanism. Specific requirements exist, including but not limited to: This mechanism is used by the RAN and UPF to forward UL and DL messages over a shared tunnel while maintaining an explicit indication of the UE's identity as both the sender and receiver of the messages, and to use the initial UL message to establish secure UE binding information to assist in mapping UE-related messages to a specific shared tunnel.

[0050] Mechanisms for UEs to change serving cells during active connectionless transactions and for RAN and UPF to process updates of UE binding information.

[0051] A mechanism used by the RAN to report DL message delivery failures and return undelivered DL messages to the UPF.

[0052] A mechanism used by the RAN to initiate the establishment of a shared transport tunnel.

[0053] A mechanism for UEs, RANs, and UPFs to appropriately release UE bindings after periods of inactivity.

[0054] The mechanism used by the RAN to request the UPF to initiate a change in the service delivery method from connectionless to connection-oriented.

[0055] A solution for transmitting messages within the RAN and between the RAN and UPF via a shared transport tunnel.

[0056] To address at least some of the aforementioned or other potential problems, several solutions regarding CL service message transmission are proposed. In these solutions, a device (such as a terminal device) transmits a connectionless (CL) service message associated with a CL service to a CN entity via a RAN node. The CL service supports data transmission without an RRC connection. The message includes a header and a body. Specifically, the header includes an identifier (ID) for the CL service. The body includes at least a common portion indicating information about the message. The RAN node transmits a second connectionless service message to the CN entity, which includes an identifier for the connectionless service and a request to bind the device to a shared tunnel used for the connectionless service. The RAN node receives from the CN entity an indication to confirm or reject the binding of the device to the shared tunnel. This solution provides a connectionless message transmission solution using a shared transport tunnel, thus avoiding the need to establish and release network signaling for dedicated transports for each device (e.g., a UE).

[0057] In some example embodiments, the proposed solution relies on the following key features: Shared transport tunnels are defined as an extension of the well-known 3GPP-defined GTP-U protocol (here referred to as GTPu). These shared tunnels support both connectionless message transmission between the UE and the UPF and the transmission of associated messages used to manage the association between the UE and the shared transport tunnel.

[0058] The RAN and UPF maintain a "UE binding" between the UE's Connectionless Service Identifier (CLSI) and the selected shared tunnel. This binding information is initially set when the first UL message transmitted by the UE over a specific radio cell is transmitted, and is confirmed by the UPF using the associated message carried by the first DL message. The UE binding corresponds to the context established within the RAN during the duration of the CLS exchange. It is used for the purpose of establishing CLS_ACTIVE mode and is maintained until the RAN and UPF infer that the UE has switched to CLS_INACTIVE.

[0059] The RAN can initiate the establishment and eventual release of shared tunnels.

[0060] Figure 3 Signaling stream 300 for CL service message transmission according to some example embodiments of the present disclosure is shown. Signaling stream 300 relates to apparatus 310 (such as terminal device 110), first network entity 320, and second network entity 330.

[0061] In operation, device 310 transmits (3020) a Connectionless Service (CLS) message to first network entity 320. The CLS message includes a message header and a message body. The message header contains at least an identifier of the connectionless service associated with device 310 (also referred to as a Connectionless Service Identifier (CLSI)). The message body may contain a user plane payload and other information related to the connectionless service. First network entity 320 receives (3025) a first CLS message.

[0062] As used herein, a CLS message from device 310 may be referred to as a UL CLS message or a first message. The message header portion may be sent without encryption, and a first network entity (320) may examine the header to help select an appropriate second network entity (330). In some examples, the message header may include a CLSI, which may be associated with a Protocol Data Unit (PDU) session associated with device 310. The CLSI may be a unique ID for a specific PDU session for device 310 (such as a UE). The CLSI may be used by the RAN to select an appropriate UPF assigned to support the PDU session, and the CLSI may be used by the UPF to retrieve UE session information, including a security key. The CLSI in the header may also be used by the UE to distinguish DL messages for one of potentially multiple concurrent PDU sessions using connectionless access.

[0063] The message body may include a connectionless message type, additional connectionless access-related information, and / or a connectionless message payload to be carried between device 310 and the second network entity 330. Furthermore, at least a portion of the message body of the connectionless service message may be encrypted, allowing only device 310 and the second network entity 330 to access the content, and thus enabling the first network entity to inspect only the message header.

[0064] First network entity 320 transmits (3030) a first connectionless service message to second network entity 330. The first connectionless service message includes a CLSI and a request to bind device 310 to a transport tunnel for at least one connectionless service. For example, the transport tunnel may be at least one shared transport tunnel for one or more CL services. (See reference...) Figure 4 The details of the transmission tunnel are described. The second network entity 330 receives the (3035) CLS message accordingly.

[0065] The second network entity 330 transmits (3060) an indication to the first network entity 320, indicating whether to confirm or deny the binding of the device 310 to the transport tunnel. Accordingly, the first network entity 320 receives (3065) the indication. In this way, the first network entity 330 can be notified whether binding (such as UE binding) can be confirmed or denied.

[0066] Additionally, in some example embodiments, the second network entity 330 transmits (3070) another CLS message to the first network entity 320. The first network entity 320 receives (3075) another CLS message and transmits (3080) another CLS message to the device 310. In some embodiments, messages 3060 and 3070 may be combined into a common message. The device 310 receives (3085) another CLS message. As used herein, the CLS message to the device 310 may be referred to as a DL CLS message or a second message.

[0067] In some embodiments, device 310 can determine the radio configuration for connectionless service by monitoring broadcast information from at least one cell, the radio configuration being associated with a target cell of a network entity. Device 310 can determine whether it is within a connectionless notification area for which the radio configuration is valid. The broadcast information may include an indication of a connectionless notification area. For example, the connectionless notification area may be assigned to device 310 along with the radio configuration via RRC signaling.

[0068] Device 310 can be Figure 1 An example implementation of terminal device 110 is provided. In one example, first network entity 320 may include or be implemented as RAN node 120, and second network entity 330 may include or be implemented as CN entity 130, such as UPF. Transport tunnels may include next-generation transport tunnels for user planes such as NGu-sh. In another example, first network entity 320 may include or be implemented as a distributed unit (DU) of RAN node 120, and second network entity 330 may include or be implemented as a centralized unit for user planes (CU-UP) of RAN node 120. Transport tunnels may include F1-U transport tunnels for user planes such as F1u-sh.

[0069] In embodiments where the second network entity 330 includes or implements a UPF and the first network entity 320 includes a RAN node 120, the second network entity 330 can obtain binding information of the device 310 based on the CLSI. The binding information indicates the association between the CLSI and the transport tunnel. The second network entity 330 can decrypt connectionless service messages based on the CLSI. The second network entity 330 can determine, based on the decryption, an indication of acceptance or rejection of the binding.

[0070] As an example, a CLS message may include an encrypted message body, which may include a message payload. The second network entity 330 can obtain service information of device 310 based on the CLSI. Service information, such as UE service information, may indicate one or more of the following: a PDU session associated with device 310, a session security key, the address of device 310, etc. The second network entity 330 can decrypt connectionless service messages based on the service information.

[0071] In response to a failure to decrypt the encrypted payload, the second network entity 330 may transmit an indication of rejection of the binding to the first network entity 320. In response to a successful decryption of the encrypted payload, the second network entity 330 may transmit an indication of confirmation of the binding to the first network entity 320. In response to a connectionless service message including an empty message, the second network entity 330 may transmit the payload of the connectionless service message to the first network entity 320.

[0072] In some examples, the second network entity 330 may encrypt the message body of another DL connectionless service message destined for device 310. The second network entity 330 may identify the first network entity 320 based on the binding information of device 310. The second network entity 330 may transmit another connectionless service message with an encrypted payload to the first network entity 320, the other connectionless service message including CLSI or another CLSI.

[0073] Alternatively, in some examples, the first network entity 320 may be a DU of RAN node 120, and the second network entity 330 may be a CU-UP of RAN node 120. In such cases, the second network entity 330 may transmit a connectionless service message including a CLSI to the user plane function. The second network entity 330 may receive an indication of acknowledgment or rejection of a binding from the user plane function. The second network entity 330 may transmit this indication to the first network entity 320.

[0074] In some example embodiments, in response to an indication of rejection of the binding and a CLSI, the first network entity 320 may remove the binding information of the device 310, which indicates the association between the CLSI and the transport tunnel.

[0075] In response to an indication of confirmation of the binding and a CLSI, the first network entity 320 may store binding information of device 310, which indicates the association between the CLSI and the transport tunnel. At least one of the transmissions from or to device 310 is based on the binding information via the transport tunnel.

[0076] In some examples, the first network entity 320 may determine radio configuration information for device 310 based on the CLSI. The first network entity 320 may also recover stored binding information for device 310 based on the CLSI. The first network entity 320 may receive or transmit connectionless service messages from or to device 310 based on the stored binding information and radio configuration.

[0077] Device 310 can encrypt the message body of a UL connectionless service message based on a security key. Device 310 can decrypt the message body of a DL connectionless service message based on the same security key.

[0078] Device 310 may receive a temporary identifier for device 310, such as CL-RNTI, from first network entity 320. UL connectionless service messages and / or DL ​​connectionless service messages may include CLSI and a temporary identifier for device 310.

[0079] In some examples, in response to receiving a connectionless service message from the first network entity 320, device 310 may set or reset a timer for a temporary identifier used by device 310. When the timer expires, device 310 may release the temporary identifier. Device 310 may then transmit a connectionless service message to initiate a connection service.

[0080] In some examples, in response to receiving another connectionless service message from the first network entity 320, device 310 may decrypt the other connectionless service message. In response to successful decryption of the other connectionless service message, device 310 may store confirmation that connectionless access is active.

[0081] In some examples, the first network entity 320 may receive a first connectionless service message including a CLSI from the device 310 during random access to the first network entity 320. The first network entity 320 may determine a temporary identifier for the device 310 and a radio configuration for the connectionless service. The first network entity 320 may receive or transmit a connectionless service message including a temporary identifier to the device 310.

[0082] Device 310 can select another target cell or a second cell based on monitoring broadcast information. Device 310 can transmit an initial connectionless service message to another target cell. The initial connectionless service message may include a connectionless service message or an empty message.

[0083] In some examples, the first network entity 320 may include a second cell (also referred to as a target cell). A first connectionless service message may indicate a cell handover from the first cell (or serving cell) to the second cell. The first network entity 320 may transmit a connectionless service message to the first cell, which includes a request to release binding information of the device 310. The first network entity 320 may receive a connectionless service message from the first cell that includes confirmation of the release.

[0084] In some examples, the first network entity 320 may determine the transport tunnel for connectionless services associated with the second network entity 330 based on the CLSI. The CLSI may include a prefix indicating an identifier for the second network entity 330.

[0085] In some examples, the first network entity 320 can set or reset the validity timer for the CLSI. When the validity timer expires, the first network entity 320 can release the binding information of the CLSI and the stored device 310.

[0086] In some examples, the second network entity 330 can set or reset the validity timer for the CLSI. When the validity timer expires, the second network entity 330 can update or release the binding information of the CLSI and the stored device 310.

[0087] In some examples, the first network entity 320 includes a first cell serving device 310. The first network entity 320 can receive a connectionless service message from a second cell (i.e., the target cell), which includes a request to release binding information of device 310. A cell handover or handover from the first cell to the second cell can be performed. The first network entity 320 can release the binding information and transmit a connectionless service message to the second cell including confirmation of the release.

[0088] Several example implementations regarding mobility have been described, such as cell handover associated with a CLS. Reference will be made to... Figures 8 to 10 Describe other examples related to mobility.

[0089] In some example embodiments, in response to a failure to transmit a connectionless service message to device 310, the first network entity 320 may transmit an indication of the failure of the connectionless service message to the second network entity 330. In response to receiving the indication of failure, the second network entity 330 may release binding information, such as UE binding. The second network entity 330 may transmit a request to the first network entity 320 to release the binding information of device 320. The first network entity 320 may receive a request from the second network entity 330 to release the binding information of device 310. The first network entity 320 may release at least one of the following: a temporary identifier of device 310 (such as a CL radio network temporary identifier (RNTI)), or binding information of device 310.

[0090] In response to the expiration of a timer associated with the temporary identifier of device 310, the first network entity 320 may transmit an indication to the second network entity 330 that binding information needs to be released (such as UE binding release). In response to receiving the indication that binding information needs to be released, the second network entity 330 may release the binding information of device 310. The second network entity 330 may transmit a request to the first network entity 320 for the release of the binding information of device 310, such as UE binding release. In response to receiving the request for the release of binding information, the first network entity 320 may release the temporary identifier of device 310 and / or the binding information of device 310. The first network entity 320 may transmit confirmation of the binding release to the second network entity 330, such as UE binding release confirmation (or verification).

[0091] In some example embodiments, in response to a connectionless service traffic volume exceeding a threshold, the first network entity 320 may transmit a request to the second network entity 330 for changing the delivery mode of services associated with device 310, such as a RAN delivery mode change request. In this way, the delivery mode can be changed upon request. (See also...) Figure 13 Describe the details of the changes in delivery patterns.

[0092] In some examples, the first network entity 320 may transmit a request for a transport tunnel to the second network entity 330 to a third network entity (such as an AMF). The AMF may transmit the request for the transport tunnel to another network entity, such as an SMF. The second network entity 330 may receive a session establishment request from the SMF, which includes the Receive End Termination Identifier (TEID) of the transport tunnel and an upper limit value for the CLSI. The second network entity 330 may establish a transport tunnel for at least one connectionless service. The second network entity 330 may transmit a response to the session establishment request to the SMF. This response includes the TEID of the transport tunnel and a range limit for the CLSI value. The SMF may forward the response to the AMF. The AMF may transmit a response to the request to the first network entity 320. This response may include the TEID of the transport tunnel and a set of values ​​for the CLSI of the transport tunnel. In this way, a transport tunnel can be established between the first network entity 320 and a specific second network entity 330, and the first network entity 320 will hold sufficient information to select the appropriate second network entity 330 for a specific connectionless service message received from device 310 (3025). Reference Figure 14 Describe the details of establishing the teleportation tunnel.

[0093] The CL service supports data transfer without an RRC connection. As used herein, messages associated with the CL service may be referred to as CL service messages or CLS messages.

[0094] In some example implementations, transport tunnels for connectionless access rely on one or more shared NGu or N3 tunnels between the RAN and the UPF, which can be used to carry connectionless UL and DL messages between multiple UEs and a given UPF that terminates the connectionless access mechanism. For the cloud RAN case, similar shared F1u tunnels can exist between the DU and CU-UP components of a given RAN. Both NGu and F1u tunnels are proposed to be supported using the same baseline extensions, such as the 3GPP GTPu protocol.

[0095] Furthermore, it is proposed that, in at least one implementation, a public F1u-sh (F1u shared) tunnel can be used to carry connectionless services between a given DU and a given CU-UP. Similarly, in at least one implementation, multiple parallel NGu-sh (NGu shared) tunnels can be established to carry connectionless services between a given RAN (or a CU-UP portion of the RAN) and a given UPF, wherein each tunnel is used to carry connectionless services associated with one or more specific PDU session service types, and each tunnel will be used to carry services from multiple UEs configured to use the same PDU session service type. Additional NGush shared tunnels can be established to carry connectionless services between the RAN and other UPFs that support the same or other PDU session service types.

[0096] Figure 4 Structure 400 of a shared tunnel between RAN DU and RANCU and between RAN and UPF for a user plane (CU-UP) is illustrated according to some example embodiments of the present disclosure. Structure 400 involves UE 401, UE 402, UE 403, RAN node 120, and a core network including UPF 404 and UPF 405, serving DN 406 and DN 407 respectively. UE 401, UE 402, and UE 403 may be example implementations of terminal device 110, UPF 404 and UPF 405 may be example implementations of CN entity 130, and DN 406 and DN 407 may be... Figure 1 An example implementation of data network 150 is shown. RAN node 120 may include DU and CU-UP, or these two components of the RAN may be combined into a common network entity. UE 401, UE 402, and UE 403 may have specific packet data network (PDN) services.

[0097] As shown in the figure, a PDU session 4042 is established between UE 401 and UPF 404 via RAN node 120. A CLS-TP tunnel 4052 is established for PDU session 4042. A shared CLS tunnel 4012, such as F1u-sh, is established between DU and CU-UP of RAN node 120. A shared CLS tunnel 4022, such as NGu-sh, is established between RAN node 120 and UPF 404. An N6 connection 4032 is established between UPF 404 and DN 406. Similar tunnels can be established for other UEs, UPFs, DNs, and RAN nodes, as shown in the figure.

[0098] In some exemplary embodiments, terminal device 110 (such as a UE) can initiate message transmission between terminal device 110 and CN node 130. For UE-initiated message transmission, three scenarios can be considered. In the first scenario, the UE can initiate message transmission when it no longer holds a valid CLSI. This scenario is referred to as CLS-IDLE. In the second scenario, the UE can initiate message transmission when it holds a valid CLSI but the RAN is unaware of it and the UPF does not know which RAN can serve the UE. This scenario is referred to as CLS-INACTIVE. In the third scenario, the UE can initiate message transmission when the RAN is aware of the UE and the UPF has a “binding” between the UE and a specific RAN. This scenario is referred to as CLS-ACTIVE.

[0099] In the first scenario, the UE is CLS-IDLE and can use a service request for CL-only, CO-only, or a combination of CO and CL access for a specific PDU session. When using a service request to request a PDU session with CL-only or a combination of CO and CL access, the UE can acquire a new CLSI and learn at least one Connectionless Notification Area (CLNA) and the corresponding radio configuration for connectionless service access. Once this is complete and the UE has returned to RRC-IDLE, the UE is now CLS-INACTIVE, and the process can be completed using the second scenario described below.

[0100] In the second scenario of message transmission initiated by the UE when it is in CLS-INACTIVE, the UE holds a PDU session supporting connectionless access and the necessary connectionless service information, including PDU session information, the corresponding CLSI, and secure session key information. It has also been assigned one or more CLNAs and corresponding connectionless radio configuration information for accessing the UPF supporting the PDU session. In this case, whenever the UE requests connectionless access, it can use contention-based random access.

[0101] The following preconditions may apply: The UE has completed PDU session establishment and may have completed subsequent service requests; it holds a valid CLSI and security information (e.g., via NAS signaling) and radio configuration for at least one CLNA (e.g., via RRC signaling previously in RRC_CONNECTED); and it has determined that messages need to be sent using CL mode. The RAN and UPF have a shared tunnel in place to carry connectionless messages. The UE and UPF have initialized connectionless security between the UE and UPF.

[0102] Figure 5Signaling flow 500 for a CL access initiated by a UE when CL Service (CLS) is INACTIVE, according to some example embodiments of this disclosure, is illustrated. Signaling flow 500 involves UE 501, RAN node 120, core network, and DN 508. RAN node 120 includes DU 502, CU-CP 503, and CU-UP 504. Core network includes UPF 505, AMF 506, and SMF 507. UE 501 may be an example implementation of terminal device 110, UPF 505 may be an example implementation of CN entity 130, and DN 508 may be... Figure 1 Example implementation of data network 150 in the example.

[0103] UE 501 is in CLS-INACTIVE state and needs to send a CLS message. During operation, UE 501 selects (or reselects) a radio cell and verifies that the cell supports the assigned CLNA, so it can use the pre-configured radio configuration.

[0104] In step 1, UE 501 uses the previously acquired key for connectionless access to encrypt the message body portion of the UL CLS message and adds the CLSI as the UE identifier to the unencrypted CLS message header.

[0105] UE 501 can initiate contention-based access, obtain a RAN temporary identifier for Connectionless Access (CL-RNTI) for UE 501, and send a CLS message. In some cases, the payload portion of the message body can be empty (NULL) (e.g., when the UE changes cells).

[0106] In step 2, RAN node 120 processes connectionless message reception according to the radio configuration associated with the broadcast CLNA.

[0107] After successfully receiving the message, RAN node 120 reads the CLS message header and uses CLSI to select a UPF, such as UPF 505.

[0108] RAN node 120 can select an appropriate shared CLS tunnel and forward the connectionless UL message along with the UE binding request to UPF 505. During this phase, RAN node 120 can record the CLSI, RAN Temporary Identifier (CL-RNTI), the selected CLNA radio configuration profile, and the binding between RAN node 120 and UPF 505, and optionally within RAN node 120, the shared CLS tunnel (e.g., the F1u-sh tunnel). This step can be performed by the RAN without first establishing an RRC connection with the UE.

[0109] In step 3, the UPF 505 reads the CLS message header and uses the CLSI to select the storage key for message decryption, selects the target DN, and, for unstructured data, retrieves the UE address. The UPF 505 can obtain the necessary information from the SMF 507.

[0110] The UPF 505 can decrypt the payload portion of a message. If decryption fails, the UPF 505 rejects the UE binding request from RAN node 120 and notifies RAN node 120. If decryption succeeds, the UPF 505 can set up UE binding between the CLSI and the RAN-shared CLS tunnel.

[0111] At step 4, if the message is not NULL, UPF 505 can forward the payload portion of the UL message to DN 508, and optionally add the UE address. At step 5, DN 508 can process the UL message and can send a response DL message to UPF 505 using the UE address.

[0112] In step 6, the UPF 505 uses the UE address to select the stored key and the current CLSI, encrypts the DL message body portion and an optional new CLSI, and resets the CLSI validity timer. In step 7, UPF 505 sends a DL message to RAN node 120, which contains the previous CLSI and UE binding acknowledgment in the message header.

[0113] In step 8, RAN node 120 confirms UE binding using the UE binding acknowledgment carried in the DL message, and uses CLSI to restore the RAN Temporary Identifier (CL-RNTI) and the appropriate radio configuration for CLS scheduled access, in order to send a CLS message to UE 501. RAN node 120 may reset the CLSI validity timer.

[0114] In step 9, after successfully receiving the message, UE 501 can reset the CL-RNTI validity timer, decrypt the CLDL message content, store the new CLSI (if it exists), and reset the CLSI validity timer. UE 501 is now in CLS-ACTIVE and can use scheduled access in the same cell for subsequent CLS message transmissions.

[0115] Using these embodiments, the UE can initiate CLS message exchange while in CLS-INACTIVE. In some example embodiments, for the case where the UE initiates message transmission while in CLS-ACTIVE, the UE is known to the RAN, holds a temporary RAN identifier (e.g., CL-RNTI) and the appropriate CLS radio configuration to use, but the UE may need to update its CLSI (e.g., if a previous DL message contained an optional new CLSI allocation). Figure 6 Signaling flow 600 for a CL access initiated by a UE when CLS-ACTIVE is shown according to some example embodiments of the present disclosure. Similar to signaling flow 500, signaling flow 600 involves UE 501, RAN node 120 (including DU 502, CU-CP 503 and CU-UP 504), UPF 505, AMF 506, SMF 507 and DN 508.

[0116] UE 501 can currently be in CLS-ACTIVE mode. The UE is positioned between DU 502 and CU-UP 504. UE 501 may need to send a CLS message.

[0117] In step 1, the UE 501 encrypted message, appending the current CL-RNTI and CLSI, is transmitted using connectionless scheduled access.

[0118] In step 2, RAN node 120 can receive CLS messages using CL-RNTI and the radio configuration associated with the broadcast CLNA. RAN node 120 can use CL-RNTI to recover stored UE binding information and forward the received CLSI and message to UPF 505. If the received CLSI differs from the stored value in the UE binding record (e.g., if it was updated during a previous DL message), RAN node 120 can include a UE binding request in the CLS message to UPF 505.

[0119] In step 3, the UPF 505 uses the CLSI in the CLS message header to recover the UE binding information and UE service information and decrypt the message.

[0120] In step 4, if the received message is not NULL, UPF 505 can forward the payload portion of the UL message to DN 508, and optionally add the UE address.

[0121] At step 5, DN 508 can process UL messages and can send response DL messages to UPF 505 using the UE address.

[0122] In step 6, the UPF 505 can use the UE address to select the stored key and the current CLSI, encrypt the DL message and an optional new CLSI, and reset the CLSI validity timer.

[0123] In step 7, UPF 505 sends a DL message to RAN node 120, which contains the previous CLSI in the header and, if requested, a UE binding confirmation.

[0124] In step 8, if present, RAN node 120 can confirm UE binding using the UE binding acknowledgment carried in the DL message, and use the CLSI to retrieve the RAN Temporary Identifier (CL-RNTI) and the appropriate radio configuration for CLS scheduled access, in order to send a CLS message to the UE. RAN node 120 can reset the CLSI validity timer.

[0125] In step 9, after successfully receiving the message, UE 501 can reset the CL-RNTI validity timer, decrypt the CLDL message content, store the new CLSI (if it exists), and reset the CLSI validity timer.

[0126] During signaling flows 500, 600, and any other suitable signaling flows(s) described herein, such as Figure 4 The shared tunnel in the transport tunnel can be used to support the following services: (multiple) UL services and / or (multiple) DL services. UL services may involve UL CLS messages, which may include optional UE binding requests. DL services may involve DL CLS messages, which may include optional UE binding responses or UE binding rejections.

[0127] Alternatively or additionally, in some example embodiments, the DN can initiate message transmission. Three scenarios can be considered. In the first scenario, the DN can initiate message transmission when the UE no longer holds a valid CLSI. This scenario is referred to as CLS-IDLE. In the second scenario, the DN can initiate message transmission when the UE holds a valid CLSI but the RAN is unaware of it and the UPF does not know which RAN can serve the UE. This scenario is referred to as CLS-INACTIVE. In the third scenario, the DN can initiate message transmission when the RAN knows the UE and the UPF has a “binding” between the UE and a specific RAN. This scenario is referred to as CLS-ACTIVE.

[0128] In the first scenario, the UE is CLS-IDLE, and the UPF needs to store the UE's incoming messages and page the UE using network paging as defined in the 3GPP standard. The UE can respond using a service request for CLS or CO access. If the UE responds with a CLS access request, it will receive CLS-related information, such as information about... Figure 5 and Figure 6 As described. The UE is now in CLS-IDLE and can send a NULL message. The UPF responds using the stored DN message, as described below for the second scenario.

[0129] In the second scenario, the UE is in CLS-INACTIVE, and the UPF needs to store incoming messages for the UE and can use CLSI to page the UE. When the UE is in CLS-INACTIVE, the UE can reply using the UE-initiated message and send a NULL message. In this case, the UPF responds using the stored DN message.

[0130] In the third scenario, the UPF holds the UE binding information, therefore it can forward incoming messages to the UE, such as... Figure 7 As shown. Figure 7 Signaling flow 700 for CL access initiated against DN when CLS-ACTIVE is shown according to some example embodiments of the present disclosure. Similar to signaling flow 500, signaling flow 700 involves UE 501, RAN node 120 (including DU 502, CU-CP 503 and CU-UP 504), UPF 505, AMF 506, SMF 507 and DN 508.

[0131] In step 1, UPF 505 receives the incoming message from the UE and holds the UE binding information of the RAN for the currently serving UE.

[0132] In step 2, the UPF 505 uses the UE address to select the stored key and the current CLSI, encrypt the DL message and the optional new CLSI, and reset the CLSI validity timer.

[0133] In step 3, the UPF 505 sends a DL message to the RAN, which contains the previous CLSI in the header. If the previous UL message contained a UE binding request and was successfully decrypted, the UPF 505 can add a UE binding confirmation.

[0134] In step 4, RAN node 120 uses the CLSI to retrieve the RAN Temporary Identifier (CL-RNTI) and the appropriate radio configuration for CLS scheduled access in order to send a CLS message to UE 501. If the previous UL message contained a UE binding request and the UPF message contained a UE binding confirmation, RAN node 120 can reset the CLSI validity timer and update the UE binding.

[0135] In step 5, after successfully receiving the message, UE 501 can reset the CL-RNTI validity timer, decrypt the CLDL message content, store the new CLSI (if it exists), and reset the CLSI validity timer.

[0136] In step 6, UE 501 can process the message and send a response UL message. UE 501 can encrypt the message, append the current CL-RNTI and CLSI, and transmit it using connectionless scheduled access.

[0137] In step 7, RAN node 120 uses CL-RNTI and the radio configuration associated with the broadcast CLNA to receive the CLS message, uses CL-RNTI to recover the stored UE binding information, and forwards the received CLSI and message to UPF505. If the received CLSI differs from the value stored in the UE binding record (e.g., if it was updated during a previous DL message), RAN node 120 may include a UE binding request.

[0138] In step 8, the UPF 505 can use the CLSI in the CLS message header to recover the UE binding information and UE service information and decrypt the message.

[0139] In step 9, if the message is not NULL, the UPF 505 can forward the payload portion of the UL message to the DN, and optionally add the UE address. Using these embodiments, CL service message exchange can be initiated by the DN.

[0140] In some example embodiments, when the UE is in CLS-INACTIVE, the UE monitors the serving cell and neighboring cells based on the radio configuration profile obtained during service requests. If the number of neighboring cells outside the CLNA exceeds a configured threshold and optionally the serving cell becomes, for example, below a configured threshold, the UE can request an update to the CLNA. This situation can be referred to as inter-CLNA mobility.

[0141] When the UE is in CLS-ACTIVE mode, it monitors the serving cell and neighboring cells based on the radio configuration profile obtained during service requests. If the number of neighboring cells within the CLNA exceeds a configured threshold and optionally the serving cell falls below the configured threshold, the UE can use contention-based access and a UE-initiated message procedure to refresh the RAN binding to send the next UL message or NULL message. If necessary, the RAN and UPF can update the binding information, and in the case of inter-RAN mobility, the UPF can release its binding with the previous RAN.

[0142] Several scenarios need to be considered, including but not limited to mobility within a DU, mobility between DUs, mobility between RANs, and mobility between CLNAs.

[0143] For intra-DU mobility, the new cell is served by the same DU. In this case, the DU needs to update its UE binding using the new CL-RNTI and the new cell. Figure 8 Signaling flow 800 for intra-DU mobility according to some example embodiments of this disclosure is illustrated. Signaling flow 800 relates to UE 501, RAN node 810 (also referred to as serving RAN node), 5G core (5GC) 820, and DN 508. Serving RAN node 810 (which is an example implementation of RAN node 120) may include gNB-DU 812, gNB-CU-CP 814, and gNB-CU-UP 816. 5GC 820 includes UPF 822 and control plane entities (such as CN entity 824).

[0144] In step 1, UE 501 detects that it needs to change its serving cell and selects a new cell. The previous serving cell and the new cell are served by the same gNB-DU 812. In step 2, UE 501 uses contention-based access to transmit CLS UL messages (such as next message or empty message). gNB-DU 812 can assign a CL-RNTI to the new cell. gNB-DU 812 can transmit the CLS UL message to gNB-CU-UP 816, which forwards it to UPF 822. UPF 822 can decrypt the message. UPF 822 can transmit a CLS DL message including a UE binding confirmation to gNB-CU-UP 816. gNB-CU-UP 816 can transmit the CLS DL message and the UE binding confirmation to gNB-DU 812. gNB-DU 812 can then update the UE binding using the new CL-RNTI and the cell.

[0145] For inter-DU mobility, a new cell is served by a different DU within the same RAN. In this case, the new DU needs to establish a UE binding, and the CU-UP needs to release the previous DU. Figure 9 Signaling flow 900 for inter-DU mobility according to some example embodiments of this disclosure is illustrated. Signaling flow 900 relates to UE 501, serving RAN node 910, 5GC 820, and DN 508. Serving RAN node 910, as an example implementation of RAN node 120, may include gNB-DU 912, target gNB-DU 914, gNB-CU-CP 916, and gNB-CU-UP 918. 5GC 820 includes UPF 822 and control plane entities (such as CN entity 824).

[0146] In step 1, UE 501 detects that it needs to change its serving cell and selects a new cell. The previous serving cell was served by gNB-DU 912, and the new cell (also known as the target cell) is served by target gNB-DU 914.

[0147] In step 2, UE 501 transmits a CLS UL message (such as a next message or an empty message) to target gNB-DU 914 using contention-based access. Target gNB-DU 914 can allocate a CL-RNTI for the new cell. Target gNB-DU 914 can transmit the CLS UL message to gNB-CU-UP 918, which forwards the CLS UL message to UPF 822. UPF 822 can decrypt the message. UPF 822 can transmit a CLS DL message including a UE binding confirmation to gNB-CU-UP 918. gNB-CU-UP 918 can update the UE binding with the new DU (i.e., target gNB-DU 914). gNB-CU-UP 918 can transmit a UE binding release to gNB-DU 912. gNB-DU 912 can transmit a UE binding release confirmation (or affirmation) to gNB-CU-UP 918. gNB-CU-UP 918 can transmit CLS DL messages and UE binding confirmations to the target gNB-DU 914. The target gNB-DU 914 can store UE bindings with CL-RNTI. The target gNB-DU 914 can use scheduled access to transmit CLS DL messages to UE 501.

[0148] For inter-RAN mobility, a new cell is served by a different RAN within the same CLNA. In this case, the new RAN needs to establish UE binding, and the UPF needs to release the previous RAN. Figure 10Signaling flow 1000 for inter-RAN mobility according to some example embodiments of this disclosure is illustrated. Signaling flow 1000 relates to UE 501, serving RAN node 1010, target RAN node 1020, 5GC 820, and DN 508. Serving RAN node 1010 may include gNB-DU 1012, gNB-CU-CP 1014, and gNB-CU-UP 1016. Target RAN node 1020 may include gNB-DU 1022, gNB-CU-CP 1024, and gNB-CU-UP 1026. 5GC 820 includes UPF 822 and control plane entities (such as CN entity 824).

[0149] In step 1, UE 501 detects that it needs to change its serving cell and selects a new cell. The previous serving cell is served by gNB-DU 1012 of serving RAN node 1010, and the new cell (also known as the target cell) is served by gNB-DU 1022 of target RAN node 1020.

[0150] In step 2, UE 501 transmits a CLS UL message (such as a next message or an empty message) to gNB-DU 1022 using contention-based access. gNB-DU 1022 can allocate a CL-RNTI for the new cell. gNB-DU 1022 can transmit the CLS UL message to gNB-CU-UP 1026, which forwards it to UPF 822. UPF 822 can decrypt the message. UPF 822 can update the binding. UPF 822 can transmit UE binding release to gNB-CU-UP 1016. gNB-CU-UP 1016 can forward the UE binding release to gNB-DU 1012 to release the UE binding. gNB-DU 1012 can transmit a UE binding release confirmation to gNB-CU-UP 1016. gNB-CU-UP 1016 can transmit the UE binding release confirmation to UPF 822.

[0151] UPF 822 can transmit a CLS DL message, including a UE binding confirmation, to gNB-CU-UP 1026. gNB-CU-UP 1026 can store UE bindings with a new DU (i.e., gNB-DU 1022). gNB-CU-UP 1026 can transmit a CLS DL message and a UE binding confirmation to gNB-DU 1022. gNB-DU 1022 can store UE bindings with CL-RNTI. gNB-DU 1022 can use scheduled access to transmit a CLS DL message to UE 501.

[0152] For inter-CLNA mobility, the new cell is served by a different RAN outside the previous CLNA. In this case, the UE needs to initiate a service request to obtain the new CLSI, new CLNA, and radio configuration information before sending the next UL message or NULL message. The new RAN needs to establish a UE binding, and if the same UPF is serving the UE, it can release the previous RAN; otherwise, the previous RAN will be released after the CL-RNTI becomes invalid.

[0153] In signaling streams 900 and 1000, such as Figure 4 The transport tunnels of (multiple) shared transport tunnels can support the following services. For example, they can support UL services including UE binding release confirmation. They can also support DL services including UE binding release.

[0154] In some example implementations, if a DL CLS message fails to be delivered to the UE, the RAN can notify the UPF and release the CL-RNTI and the binding to the shared CLS tunnel. The UPF can release the binding to the UE with the shared CLS tunnel. If the UE subsequently attempts to transmit an uplink CLS message using the CL-RNTI, the RAN can ignore the message, and the UE can use CLS-INACTIVE to retry.

[0155] Figure 11 Signaling flow 1100 for DL ​​message delivery failure according to some example embodiments of the present disclosure is illustrated. Signaling flow 1100 relates to UE 501, RAN node 120 (including DU 502, CU-CP 503 and CU-UP 504), UPF 505, and optional AMF 506 and SMF 507.

[0156] In step 1, UPF 505 can transmit a DL CLS message to DU 502 via CU-UP 504. In step 2, if RAN node 120 determines that the CLS message failed to be delivered, then in step 3, CU-UP 504 notifies UPF 505 that the CLS message failed to be delivered. UPF 505 can transmit a UE binding release to CU-UP 504. CU-UP can transmit a UE binding release to DU 502. DU 502 can release the CL-RNTI and UE binding. DU 502 can transmit a UE binding release confirmation to CU-UP 504. CU-UP 504 can release the UE binding. CU-UP 504 can transmit a UE binding release confirmation to UPF 505. UPF 505 can release the UE binding.

[0157] In signaling flow 1100, transport tunnels such as shared tunnels can support UL services including DL message delivery failures.

[0158] In some example implementations, the UE and RAN can release the CL-RNTI when and if the CL-RNTI validity timer expires. When this occurs, the UE is CLS-INACTIVE and can re-establish the CL-RNTI by sending an initial CLS message using contention access. To avoid race conditions between the UE and RAN, the CL-RNTI validity timer in the RAN is expected to be longer than the timer in the UE.

[0159] If the CLSI validity timer expires, both the UE and UPF can release the CLSI. When this happens, the UE can use a service request to re-establish a connectionless connection. To avoid race conditions between the UE and UPF, the CLSI validity timer in the UPF is expected to be longer than the timer in the UE.

[0160] Figure 12 Signaling flow 1200 for processing CL-RNTI and CLSI validity expiration is illustrated according to some example embodiments of this disclosure. Signaling flow 1200 relates to UE 501, RAN node 810, 5GC 820, and DN 508. RAN node 810 includes gNB-DU 812, gNB-CU-CP 814, and gNB-CU-UP 816. 5GC 820 includes UPF 822 and optionally includes control plane entities such as CN entity 824.

[0161] At step 1, UE 501 can determine that there are no more messages to send to UPF 822. The CL-RNTI validity timer may expire. UE 501 may be in CLS-INACTIVE. Furthermore, at DN 508, there may be no more messages to send to UE 501.

[0162] In step 2, the CL-RNTI validity timer at gNB-DU 812 can expire. gNB-DU can transmit the required UE binding release to gNB-CU-UP 816. gNB-CU-UP 816 can transmit the required UE binding release to UPF 822. UPF 822 can transmit the UE binding release to gNB-CU-UP 816, and gNB-CU-UP 816 can forward the UE binding release to gNB-DU 812. gNB-DU 812 can release the CL-RNTI and UE binding. gNB-DU 812 can transmit a UE binding release confirmation to gNB-CU-UP 816. gNB-CU-UP 816 can release the UE binding and transmit a UE binding release confirmation to UPF 822. UPF 822 can release the UE binding.

[0163] At step 3, the CLSI validity timer may expire at UE 501. Additionally, the CLSI validity timer at UPF 822 may expire. UE 501 may be in CLS-IDLE mode.

[0164] In some example implementations, the RAN may detect that a connectionless transaction for a particular UE involves excessive traffic and will be handled better using connection-oriented access. In this case, the RAN can signal to the UPF to request a change in delivery mode.

[0165] Figure 13 Signaling flow 1300 for RAN detection of excessive connectivity-less traffic is illustrated according to some example embodiments of the present disclosure. Signaling flow 1300 relates to UE 501, RAN node 120 (including DU 502, CU-CP 503 and CU-UP 504), UPF 505, and optional AMF 506, SMF 507 and DN 508.

[0166] In operation, DU 502 can detect excessive traffic in CLS mode. DU 502 can send a delivery mode change request to CU-UP 504. RAN node 120 (such as CU-UP 504) can detect excessive traffic in CLS mode. CU-UP 504 can send a delivery mode change request to UPF 505. Using these embodiments, the delivery mode can be changed via a mode change request. In these embodiments, the UL service including the RAN delivery mode change request can be provided by a transport tunnel (such as...) Figure 4 Supports shared transport tunnels.

[0167] In some example implementations, the shared CLS tunnel establishment procedure is similar to a service request procedure, but it is initiated by the RAN, not the UE, to establish a shared transport connection between the RAN and the UPF, rather than a dedicated connection for a single UE. Therefore, it does not use NAS-level signaling and can thus be a novel non-UE-associated procedure on NGAP.

[0168] During this process, the CLSI can be used to guide the RAN, AMF, SMF, and UPF to establish appropriate shared CLS tunnels. Specifically, it is assumed that the CLSI can be defined using a prefix used to uniquely identify the serving UPF and the remainder used to uniquely identify the PDU session for a specific UE. That is: <clsi>:=<UPF identifier><PDU session identifier> wherein the <UPF identifier> identifies a serving UPF, and the <PDU session UE identifier> identifies a given PDU session for a UE served by the UPF.

[0169] Figure 14 illustrates a signaling flow 1400 for shared CLS tunnel establishment according to some example embodiments of the present disclosure. The signaling flow 1400 involves UE 501, RAN node 120 (including DU 502, CU-CP 503 and CU-UP 504), UPF 505, AMF 506 and SMF 507.

[0170] There may be preconditions that the RAN (such as RAN node 120) receives one of the following: a request from the UE for uplink CLS message transmission, or a management plane command for the RAN to preemptively establish a shared CLS tunnel. In all cases, the CLSI associated with the request is not mapped to a shared CLS tunnel established for a given UPF (such as UPF 505), so the RAN determines that shared CLS tunnel establishment needs to be initiated.

[0171] At step 1, the RAN node 120 may first need to establish a shared F1u-sh tunnel between the DU 502 and the CU-UP 504.

[0172] At step 2, the RAN node 120 sends a (new) NGAP message to the AMF 506, requesting a shared CLS tunnel to the UPF 505. The message includes the DL TEID and the requested CLSI, which has a PDU session UE identifier value set to the upper limit of the requested value range.

[0173] At step 4, the AMF 506 may use the CLSI to select an SMF, such as SMF 507, and forward the request to the SMF 507 as a modified PDU session update.

[0174] At step 5, the SMF 507 uses the CLSI to select a UPF, such as UPF 505, and determines the range of required CLSI values for a given CL service.

[0175] At step 7, the SMF 507 may establish a session on the UPF 505 for the shared CLS tunnel to the RAN node 120 for the CL service and the supported CLSI value range. The UPF 505 establishes a DL shared CLS tunnel.

[0176] At step 11, the SMF 507 replies to the AMF 506 with a modified PDU session update response including the UL TEID and the range of CLSI values to be used.

[0177] In step 12, AMF 506 replies to RAN node 120 using a (new) NGAP response message. The NGAP response message contains the UL TEID and the CLSI value range to be used for the tunnel. RAN node 120 can then establish a UL shared CLS tunnel.

[0178] After completion, RAN node 120 has a shared CLS tunnel established with UPF 505 and a permitted range of CLSI values. The RAN node can repeat the process of establishing additional tunnels to complete the coverage of the required CLSI values.

[0179] like Figure 4 The shared tunnel shown provides the following services to support the mechanisms described in the previous section.

[0180] UL Services: UL CLS message (containing an optional UE binding request).

[0181] DL CLS delivery failed (including the returned UL CLS message).

[0182] UE binding and release are required.

[0183] UE binding release response.

[0184] RAN delivery mode change request.

[0185] DL service: DL CLS message (including optional UE binding response).

[0186] UE binding rejected.

[0187] UE binding release request.

[0188] Note that shared tunnels between the RAN and UPF, and between the DU and CU-UP within the RAN, require the same service. One possible implementation of a shared tunnel is an extension of the well-known GTPu defined in the 3GPP standard. In this case, CLS messages can be carried in the GTPu payload, and a new GTPu extended header can be defined for connectionless message delivery, modifying the GTPu protocol as shown in Table 1 below. It should be understood that these components and contents shown in Table 1 are for illustrative purposes only and do not imply any limitations.

[0189] Table 1

[0190] Several supported GTPv1 header message type values ​​are allowed, including but not limited to: 1 / 2: Echo request / response.

[0191] 26: Error indication.

[0192] 254: End marker. Used when releasing a GTPu-sh tunnel.

[0193] 255: G-PDU. T-PDU contains connectionless message packets (header and payload).

[0194] CLS message type, CLSI, and UE binding request / response can be carried in a dedicated CLS extension field. TEID is the receiver termination point of the GTPu-sh tunnel and is therefore identical for all UEs associated with the same shared GTPu-sh tunnel. When forwarding undelivered DL messages, an End flag can be used to indicate that the message contains the last forwarded message.

[0195] These embodiments can be used to improve CLS message transmission. Therefore, the CL mode can be enhanced.

[0196] In some examples, a Connection-Independent Service Identifier (CLSI) has been assigned to the UE, which is used when sending or receiving Connection-Independent Access Messages. The CLSI can be specific to a particular PDU session and may have been previously assigned to the UE using NAS-level signaling.

[0197] The UE can monitor broadcast information from radio cells to determine if it remains within an area where a previously acquired connectionless radio configuration remains valid. For example, a cell may broadcast a specific indication for connectionless access, such as a CLNA. A CLNA may be specific to a particular connectionless radio configuration and may have already been assigned to the UE along with previously acquired radio configuration information using RRC-level signaling. The UE can choose a suitable cell to provide at least one CLNA it holds, and then select the appropriate radio configuration.

[0198] In some examples, the UE is able to derive a suitable security key for encrypting messages and adding integrity protection information. The UE can use the CLSI as a unique connectionless service identifier and security key to construct uplink connectionless messages.

[0199] A UE can initiate connectionless message transmission by sending an initial UL message using contention-based access, depending on the selected radio configuration. During contention-based access, the RAN can assign a temporary RAN identifier to the UE that can be used during subsequent scheduled access. In one implementation, the RAN identifier is a variant of the well-known RNTI, which may be named CL-RNTI.

[0200] All uplink and downlink connectionless messages contain an unencrypted CLSI header, along with the assigned CL-RNTI.

[0201] In some examples, the RAN can read the CLSI in the message header and use the CLSI contained in the initial UL message to determine the serving UPF and the corresponding pre-established shared tunnel for forwarding initial UL messages with requests to establish UE bindings. In one implementation, the CLSI may include a prefix indicating the serving UPF ID to help the RAN select the serving UPF.

[0202] The UPF can use the CLSI contained in the forwarded initial UL message to recover UE service information (PDU session, session security key, UE IP address). The UPF can use the recovered security key to decrypt the initial UL message. If successful, the UPF can store the UE binding information used to associate the UE PDU session with the serving RAN and forward the message to the DN. If unsuccessful, the UPF can indicate to the RAN that the UE binding request was rejected.

[0203] UPF can encrypt the corresponding DL message sent by the DN for the UE, as well as an optional new CLSI to be used by the UE for subsequent messages, and use the stored UE binding information to select the RAN and forward downlink connectionless messages, thereby placing the previous CLSI in the header. The message may include an indication in response to the UE binding request.

[0204] The RAN can use an indication in response to a UE binding request to store UE binding information used to associate the CLSI with the UPF, and use the CLSI to retrieve the previously assigned temporary RAN UE identifier and the selected radio configuration to be used with the UE. In the case of a distributed RAN, UE binding information can be set in both the DU and CU-UP components within the RAN.

[0205] In some examples, the RAN can forward DL messages to the UE, and after decryption, the UE can store an acknowledgment that connectionless access is active.

[0206] The UE can continue monitoring the radio cell signal level and determine if it is no longer within the coverage area of ​​the serving cell, then select a new cell. In this case, the UE can restore connectionless access with the new cell. After selecting a new cell, the UE can send a next UL message or a NULL message as the initial UL message on the new cell. If the UE has already sent a NULL message, the UPF can send a next DL message or a NULL message as the first DL message to the UE. Then, the RAN and UPF can update the UE binding information. The UPF can request to release the UE binding to the previously serving RAN.

[0207] The RAN can notify the UPF that it failed to deliver the DL message. In this case, the UPF can request the serving RAN to release the UE binding.

[0208] The RAN can notify the UPF UE that it is overusing connectionless access.

[0209] The UE and RAN can maintain timers to manage the validity of RAN-assigned temporary UE identifiers (i.e., CL-RNTIs). These timers can be reset each time a message is successfully transmitted. When a timer expires, the UE and RAN can assume that the identifier is no longer valid and should be updated. If the RAN temporary identifier expires, the UE will repeat the initial UL message procedure.

[0210] Shared transport tunneling services can be supported using extensions to the well-known 3GPP-defined GTPU protocol. In one implementation, the GTPU protocol has a dedicated extension header to support connectionless access. The extension header may contain a CLSI and an indication of the dedicated message type for different services, as well as an optional payload for carrying connectionless messages. The same GTPU protocol extension can be used to implement F1u-sh tunnels between RAN "DU" and "CU-UP" components, and NGu-sh tunnels between the RAN and the core network.

[0211] It should be understood that the above provides some example specifications, signaling flows, and implementation examples, and the detailed description can be changed. Note that... Figures 3 to 14 The sequence of actions shown is merely an example and not a limitation. Actions can be performed in any suitable manner. Reference Figures 3 to 14 The described example embodiments can be implemented individually or in any combination. For example, one or more example embodiments shown in a single figure can be combined with one or more example embodiments shown in one or more other figures. It should be noted that steps as illustrated in one or more figures may be selectively performed in actual embodiments. Using these embodiments, service delivery between the UE and the UPF, such as CL service delivery, can be enhanced.

[0212] Figure 15 A flowchart of an example method 1500 implemented at a first network entity according to some example embodiments of the present disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 3 Method 1500 is described from the perspective of the first network entity 320 in the first network entity.

[0213] In box 1510, the first network entity 320 receives a first connectionless service message from the device, the first connectionless service message including a connectionless service identifier (CLSI) associated with the device.

[0214] In box 1520, the first network entity 320 transmits a second connectionless service message to the second network entity. The second connectionless service message includes a CLSI and a request for binding of the device to a transport tunnel for at least one connectionless service.

[0215] At box 1530, the first network entity 320 receives from the second network entity an indication of confirmation or rejection of the binding of the device to the transmission tunnel.

[0216] In some example embodiments, method 1500 further includes: in response to an indication of rejection of binding and a CLSI, removing binding information of the device, the binding information indicating the association between the CLSI and the transport tunnel.

[0217] In some example embodiments, method 1500 further includes: in response to an indication of confirmation of binding and a CLSI, binding information of the storage device, the binding information indicating the association between the CLSI and a transport tunnel, wherein at least one of a transmission from the device or a transmission to the device is based on the binding information via the transport tunnel.

[0218] In some example embodiments, method 1500 further includes: determining radio configuration information for the device based on CLSI; recovering stored binding information of the device based on CLSI; and receiving or transmitting a connectionless service message from the device based on the stored binding information and radio configuration.

[0219] In some example embodiments, method 1500 further includes: during random access to a first network entity, receiving from the device a first connectionless service message including a CLSI; determining a temporary identifier for the device and a radio configuration for connectionless service; and receiving from the device a connectionless service message including the temporary identifier, or transmitting a connectionless service message including the temporary identifier to the device.

[0220] In some example embodiments, method 1500 further includes: transmitting a connectionless service message to a first cell including a request for binding information of the release device; and receiving a connectionless service message from the first cell including confirmation of the release.

[0221] In some example embodiments, method 1500 further includes: determining a transport tunnel associated with a second network entity for connectionless service based on the CLSI, wherein the CLSI includes a prefix of an identifier indicating the second network entity.

[0222] In some example embodiments, method 1500 further includes: setting an validity timer for the CLSI; and releasing the binding information of the CLSI and the stored device when the validity timer expires.

[0223] In some example embodiments, method 1500 further includes: receiving from a second cell a connectionless service message including a request for release device binding information, wherein a cell handover from the first cell to the second cell is to be performed; releasing the binding information; and transmitting to the second cell a connectionless service message including confirmation of the release.

[0224] In some example embodiments, method 1500 further includes: in response to the failure of a connectionless service message to be transmitted to the device, transmitting an indication of the failure of the connectionless service message to a second network entity; receiving from the second network entity a request to release the binding information of the device; and releasing at least one of the following: a temporary identifier of the device or the binding information of the device.

[0225] In some example embodiments, method 1500 further includes: in response to the expiration of a timer associated with a temporary identifier of the device, transmitting to a second network entity an indication that the release of binding information is required; receiving from the second network entity a request to release the binding information of the device; and releasing at least one of the following: the temporary identifier of the device or the binding information of the device.

[0226] In some example embodiments, method 1500 further includes: in response to traffic volume for a connectionless service exceeding a threshold, transmitting a request to a second network entity to change the delivery mode of the service associated with the device.

[0227] In some example embodiments, method 1500 further includes: transmitting a request to a third network entity for a transport tunnel to a second network entity; and receiving a response to the request from the third network entity, the response including a receiver termination identifier for the transport tunnel and a set of values ​​for the CLSI of the transport tunnel.

[0228] In some example embodiments, the CLSI is associated with a Protocol Data Unit (PDU) session associated with the device, and / or the first connectionless service message and the second connectionless service message include an encrypted payload.

[0229] In some example embodiments, the apparatus includes a terminal device, a first network entity including or implementing a radio access network (RAN) node, and a second network entity including or implementing user plane functionality, wherein the transport tunnel includes a next-generation transport tunnel for the user plane.

[0230] In some example embodiments, the apparatus includes a terminal device, a first network entity including or implementing a distributed unit (DU) of a radio access network (RAN) node, and a second network entity including or implementing a centralized unit for a user plane (CU-UP) of the RAN node, wherein the transport tunnel includes an F1 transport tunnel for the user plane.

[0231] In some example embodiments, a first network entity capable of performing any method 1500 (e.g., Figure 3 The first network entity 320 may include a component for performing the corresponding operation of method 1500. This component may be implemented in any suitable form. For example, the component may be implemented in a circuit system or a software module. The first network entity may be implemented as or included in... Figure 3 In the first network entity 320.

[0232] Figure 16 A flowchart of an example method 1600 implemented at a second network entity according to some example embodiments of the present disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 3 Method 1600 is described from the perspective of the second network entity 330 in the network.

[0233] In box 1610, the second network entity 330 receives a connectionless service message from the first network entity. The connectionless service message includes a connectionless service identifier (CLSI) associated with the device and a request for binding the device to a transport tunnel for at least one connectionless service.

[0234] At box 1620, the second network entity 330, based on CLSI, transmits an indication to the first network entity to confirm or reject the binding of the device to the transmission tunnel.

[0235] In some example embodiments, the apparatus includes a terminal device, a first network entity including or implementing a radio access network (RAN) node, and a second network entity including or implementing user plane functionality, wherein the transport tunnel includes a next-generation transport tunnel for the user plane.

[0236] In some example embodiments, method 1600 further includes: obtaining binding information of the device based on the CLSI, the binding information indicating the association between the CLSI and the transport tunnel; decrypting a connectionless service message based on the CLSI; and determining, based on the decryption, an indication indicating acceptance or rejection of the binding.

[0237] In some example embodiments, method 1600 further includes: in response to a failure to decrypt the encrypted payload, transmitting to a first network entity an indication of rejection of the binding; and / or in response to a successful decryption of the encrypted payload, transmitting to the first network entity an indication of confirmation of the binding; and in response to a connectionless service message including an empty message, transmitting to the first network entity the payload of the connectionless service message.

[0238] In some example embodiments, method 1600 further includes: obtaining service information of the device based on CLSI, the service information including at least one of the following: a protocol data unit (PDU) session associated with the device, a session security key, or the address of the device; and decrypting a connectionless service message based on the service information.

[0239] In some example embodiments, method 1600 further includes: encrypting the payload of another connectionless service message destined for the device; determining a first network entity based on the device's binding information; and transmitting to the first network entity another connectionless service message having an encrypted payload, the other connectionless service message including a CLSI or another CLSI.

[0240] In some example embodiments, the apparatus includes a terminal device, a first network entity including or implementing a distributed unit (DU) of a radio access network (RAN) node, and a second network entity including or implementing a centralized unit for a user plane (CU-UP) of the RAN node, wherein the transport tunnel includes an F1 transport tunnel for the user plane.

[0241] In some example embodiments, method 1600 further includes: transmitting a connectionless service message including CLSI to a user plane function; receiving an indication from the user plane function indicating confirmation or rejection of the binding; and transmitting the indication to a first network entity.

[0242] In some example embodiments, method 1600 further includes: setting an validity timer for the CLSI; and updating or releasing the binding information of the CLSI and the stored device when the validity timer expires.

[0243] In some example embodiments, method 1600 further includes: receiving an indication of failure of the connectionless service message from a first network entity; releasing binding information of the device; and transmitting a request to the first network entity to release the binding information of the device.

[0244] In some example embodiments, method 1600 further includes: receiving from a first network entity an indication that binding information release is required; releasing binding information of the device; and transmitting a request to the first network entity for releasing the binding information of the device.

[0245] In some example embodiments, method 1600 further includes receiving from a first network entity a request to change the delivery mode of services associated with the device.

[0246] In some example embodiments, method 1600 further includes: receiving a session establishment request from a third network entity, the session establishment request including a receiver termination identifier of a transport tunnel and an upper limit value for CLSI; establishing a transport tunnel for at least one connectionless service; and transmitting a response to the session establishment request to the third network entity, the response including a receiver termination identifier of the transport tunnel and a lower limit value for CLSI.

[0247] In some example embodiments, CLSI is associated with a Protocol Data Unit (PDU) session associated with the device.

[0248] In some example embodiments, a second network entity capable of performing any method 1600 (e.g., Figure 3 The second network entity 330 may include a component for performing the corresponding operation of method 1600. This component may be implemented in any suitable form. For example, the component may be implemented in a circuit system or a software module. The second network entity may be implemented as or included in... Figure 3 In the second network entity 330.

[0249] Figure 17 A flowchart of an example method 1700 implemented at a device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 3 The angle description method of device 310 in the middle is 1700.

[0250] In box 1710, device 310 determines the radio configuration for connectionless service by monitoring broadcast information from at least one cell, the radio configuration being associated with a target cell of a network entity.

[0251] In box 1720, device 310 transmits a connectionless service message, including a connectionless service identifier (CLSI) associated with the device, to a network entity via random access to the network entity.

[0252] At frame 1730, device 310 receives another connectionless service message from a network entity, including CLSI or another CLSI.

[0253] In some example embodiments, method 1700 further includes: determining whether the device is in a radio-configured connectionless notification area, wherein the broadcast information includes an indication of the connectionless notification area.

[0254] In some example embodiments, the connectionless notification area is allocated to the device via radio resource control signaling along with radio configuration.

[0255] In some example embodiments, method 1700 further includes: encrypting the payload of a connectionless service message based on a security key; and / or decrypting the payload of another connectionless service message based on a security key.

[0256] In some example embodiments, method 1700 further includes receiving a temporary identifier for a device from a network entity, wherein the connectionless service message and another connectionless service message include the CLSI and the temporary identifier for the device.

[0257] In some example embodiments, method 1700 further includes: resetting a timer for a temporary identifier for a device in response to receiving a connectionless service message from a network entity; releasing the temporary identifier for the device when the timer expires; and transmitting the connectionless service message to initiate a connection service.

[0258] In some example embodiments, method 1700 further includes: decrypting another connectionless service message in response to receiving another connectionless service message from a network entity; and storing an acknowledgment that connectionless access is active in response to successful decryption of the other connectionless service message.

[0259] In some example embodiments, method 1700 further includes: selecting another target cell based on monitoring of broadcast information; and transmitting an initial connectionless service message to the other target cell, the initial connectionless service message including a subsequent connectionless service message or an empty message.

[0260] In some example embodiments, CLSI is associated with a Protocol Data Unit (PDU) session associated with the device.

[0261] In some example embodiments, the connectionless service message includes a header for connectionless access, the header including CLSI and the message type of the connectionless service message.

[0262] In some example embodiments, the apparatus includes terminal equipment, and the network entity includes or implements a radio access network (RAN) node or a distributed unit (DU) of a RAN node.

[0263] In some example embodiments, the apparatus capable of performing any method 1700 (e.g., Figure 3 The device 310 may include components for performing the corresponding operations of method 1700. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module. The device may be implemented as or included in... Figure 3 In device 310.

[0264] Figure 18 This is a simplified block diagram of a device 1800 suitable for implementing exemplary embodiments of the present disclosure. The device 1800 may be provided to implement a communication device, such as... Figure 3 The device 1800 includes a device 310, a first network entity 320, and a second network entity 330. As shown, the device 1800 includes one or more processors 1810, one or more memories 1820 coupled to the processors 1810, and one or more communication modules 1840 coupled to the processors 1810.

[0265] Communication module 1840 is used for bidirectional communication. Communication module 1840 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interface can represent any interface required for communication with other network elements. In some example embodiments, communication module 1840 may include at least one antenna.

[0266] As a non-limiting example, processor 1810 can be any type suitable for a local technology network and can include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture. Device 1800 can have multiple processors, such as application-specific integrated circuit system-on-a-chip (ASIC) that is time-dependent on a clock synchronized with a main processor.

[0267] Memory 1820 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 1824, electrically programmable read-only memory (EPROM), flash memory, hard disk, optical disc (CD), digital video disc (DVD), optical disc, laser disc, and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 1822 and other volatile memories that will not persist for the duration of a power outage.

[0268] Computer program 1830 includes computer-executable instructions that are executed by an associated processor 1810. The instructions of program 1830 may include instructions for performing operations / actions of some example embodiments of this disclosure. Program 1830 may be stored in memory (e.g., ROM 1824). Processor 1810 can perform any suitable actions and processes by loading program 1830 into RAM 1822.

[0269] Example embodiments of this disclosure can be implemented by program 1830, such that device 1800 can execute as described in the reference. Figures 3 to 17 Any process discussed in this disclosure. Exemplary embodiments of this disclosure may also be implemented by hardware or by a combination of software and hardware.

[0270] In some example embodiments, program 1830 may be tangibly contained on a computer-readable medium, which may be included in device 1800 (such as memory 1820) or other storage device accessible by device 1800. Device 1800 may load program 1830 from the computer-readable medium into RAM 1822 for execution. In some example embodiments, the computer-readable medium may include any type of non-transitory storage medium, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. As used herein, the term "non-transitory" is a limitation on the medium itself (i.e., tangible, not tactile), rather than a limitation on the persistence of data storage (e.g., RAM and ROM).

[0271] Figure 19 An example of a computer-readable medium 1900 is shown, which may be in the form of a CD, DVD, or other optical storage disc. Program 1830 is stored on the computer-readable medium 1900.

[0272] Generally, the various embodiments of this disclosure can be implemented in hardware or special-purpose circuit systems, software, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of this disclosure are illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that, as non-limiting examples, the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, special-purpose circuit systems or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0273] Some exemplary embodiments of this disclosure also provide at least one computer program product tangibly stored on a computer-readable medium, such as a non-transitory computer-readable medium. The computer program product includes computer-executable instructions that execute in a device on a target physical or virtual processor, such as those included in a program module, to perform any of the methods described above. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a particular task or implement a particular abstract data type. In various embodiments, the functionality of a program module can be combined or split among program modules as needed. The machine-executable instructions for a program module can execute within a local or distributed device. In a distributed device, the program module can reside in both local and remote storage media.

[0274] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0275] In the context of this disclosure, computer program code or related data may be carried by any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, etc.

[0276] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof. More specific examples of computer-readable storage media will include electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0277] Furthermore, although operations are described in a specific order, this should not be construed as requiring that such operations be performed in the specific order shown or sequentially, or that all shown operations be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the discussion above, these details should not be construed as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to particular embodiments. Unless explicitly stated otherwise, certain features described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated otherwise, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0278] Although this disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms for implementing the claims.

[0279] Furthermore, various implementations of this disclosure can be described with reference to the following entries, and their features can be combined in any reasonable manner.

[0280] Item 1. A first network entity, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first network entity to at least: receive a first connectionless service message from a device, the first connectionless service message including a connectionless service identifier (CLSI) associated with the device; transmit a second connectionless service message to a second network entity, the second connectionless service message including the CLSI and a request for binding the device to a transport tunnel for at least one connectionless service; and receive from the second network entity an indication of acknowledgment or rejection of the binding of the device to the transport tunnel.

[0281] Item 2. The first network entity according to Item 1, wherein the first network entity is further configured to: remove binding information of the device in response to an indication of rejection of binding and a CLSI, the binding information indicating the association between the CLSI and the transport tunnel.

[0282] Item 3. The first network entity according to Item 1, wherein the first network entity is further configured to: in response to an indication of confirmation of binding and a CLSI, bind information of the storage device, the bind information indicating the association between the CLSI and the transport tunnel, wherein at least one of the transmissions from the device or to the device is based on the bind information via the transport tunnel.

[0283] Item 4. A first network entity according to any one of items 1 to 3, wherein the first network entity is further configured to: determine radio configuration information for the device based on the CLSI; recover stored binding information of the device based on the CLSI; and receive or transmit a connectionless service message from or to the device based on the stored binding information and radio configuration.

[0284] Item 5. A first network entity according to any one of items 1 to 3, wherein the first network entity is further configured to: receive a first connectionless service message including a CLSI from the device during random access to the first network entity; determine a temporary identifier for the device and a radio configuration for connectionless service; and receive a connectionless service message including a temporary identifier from the device, or transmit a connectionless service message including a temporary identifier to the device.

[0285] Item 6. A first network entity according to Item 5, wherein the first network entity includes a second cell, the first connectionless service message is to the second cell, and the first network entity is further configured to: transmit a connectionless service message to the first cell including a request for binding information of a release device; and receive from the first cell a connectionless service message including confirmation of release.

[0286] Item 7. A first network entity according to any one of items 1 to 6, wherein the first network entity is further configured to: determine a transport tunnel associated with a second network entity for connectionless services based on the CLSI, wherein the CLSI includes a prefix of an identifier indicating the second network entity.

[0287] Item 8. A first network entity according to any one of items 1 to 7, wherein the first network entity is further configured to: set an validity timer for the CLSI; and release the binding information of the CLSI and the stored device when the validity timer expires.

[0288] Item 9. A first network entity according to any one of items 1 to 8, wherein the first network entity includes a first cell of the serving device, and the first network entity is further configured to: receive from a second cell a connectionless service message including a request for release of binding information of the device, wherein a cell handover from the first cell to the second cell is to be performed; release the binding information; and transmit to the second cell a connectionless service message including confirmation of the release.

[0289] Item 10. A first network entity according to any one of items 1 to 9, wherein the first network entity is further configured to: transmit an indication of failure of the connectionless service message to a second network entity in response to the failure of the transmission of the connectionless service message to the device; receive a request from the second network entity to release the binding information of the device; and release at least one of the following: the temporary identifier of the device or the binding information of the device.

[0290] Item 11. A first network entity according to any one of items 1 to 10, wherein the first network entity is further configured to: transmit an indication to a second network entity that the binding information release is required in response to the expiration of a timer associated with a temporary identifier of the device; receive a request from the second network entity to release the binding information of the device; and release at least one of the following: the temporary identifier of the device or the binding information of the device.

[0291] Item 12. A first network entity according to any one of items 1 to 11, wherein the first network entity is further configured to: transmit a request to a second network entity to change the delivery mode of services associated with the device in response to a traffic volume exceeding a threshold for connectionless services.

[0292] Item 13. A first network entity according to any one of items 1 to 12, wherein the first network entity is further configured to: transmit a request to a third network entity for a transport tunnel to a second network entity; and receive a response to the request from the third network entity, the response including a receiver termination identifier of the transport tunnel and a set of values ​​for the CLSI of the transport tunnel.

[0293] Item 14. A first network entity according to Items 1 to 13, wherein the CLSI is associated with a Protocol Data Unit (PDU) session associated with the device, and / or wherein the first connectionless service message and the second connectionless service message include an encrypted payload.

[0294] Item 15. A first network entity according to any one of items 1 to 14, wherein the apparatus includes terminal equipment, the first network entity includes or implements a radio access network (RAN) node, and the second network entity includes or implements user plane functionality, and wherein the transport tunnel includes a next-generation transport tunnel for the user plane.

[0295] Item 16. A first network entity according to any one of items 1 to 14, wherein the apparatus includes terminal equipment, the first network entity includes or implements a distributed unit (DU) of a radio access network (RAN) node, and the second network entity includes or implements a centralized unit for a user plane (CU-UP) of the RAN node, and wherein the transmission tunnel includes an F1 transmission tunnel for the user plane.

[0296] Item 17. A second network entity, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second network entity to at least: receive a connectionless service message from a first network entity, the connectionless service message including a connectionless service identifier (CLSI) associated with a device and a request for binding the device to a transport tunnel for at least one connectionless service; and, based on the CLSI, transmit to the first network entity an indication of acknowledgment or rejection of the binding of the device to the transport tunnel.

[0297] Item 18. A second network entity according to Item 17, wherein the apparatus includes terminal equipment, the first network entity includes or implements a radio access network (RAN) node, and the second network entity includes or implements user plane functionality, and wherein the transport tunnel includes a next-generation transport tunnel for the user plane.

[0298] Item 19. The second network entity according to Item 18, wherein the second network entity is further configured to: obtain binding information of the device based on the CLSI, the binding information indicating the association between the CLSI and the transport tunnel; decrypt a connectionless service message based on the CLSI; and determine, based on the decryption, an indication indicating confirmation or rejection of the binding.

[0299] Item 20. The second network entity according to Item 19, wherein the connectionless service message includes an encrypted payload, and the second network entity is further configured to: transmit an indication of rejection of the binding to the first network entity in response to failure to decrypt the encrypted payload; and / or transmit an indication of confirmation of the binding to the first network entity in response to successful decryption of the encrypted payload; and transmit the payload of the connectionless service message to the first network entity in response to the connectionless service message including an empty message.

[0300] Item 21. A second network entity according to any one of items 19 to 20, wherein the second network entity is further configured to: obtain service information of the device based on CLSI, the service information including at least one of the following: a protocol data unit (PDU) session associated with the device, a session security key, or the address of the device; and decrypt a connectionless service message based on the service information.

[0301] Item 22. A second network entity according to any one of items 18 to 21, wherein the second network entity is further configured to: encrypt the payload of another connectionless service message destined for the device; determine the first network entity based on the device's binding information; and transmit to the first network entity another connectionless service message having an encrypted payload, the other connectionless service message including a CLSI or another CLSI.

[0302] Item 23. A second network entity according to Item 17, wherein the apparatus includes terminal equipment, the first network entity includes or implements a distributed unit (DU) of a radio access network (RAN) node, and the second network entity includes or implements a centralized unit for a user plane (CU-UP) of the RAN node, and wherein the transmission tunnel includes an F1 transmission tunnel for the user plane.

[0303] Item 24. The second network entity according to Item 23, wherein the second network entity is further configured to: transmit a connectionless service message including CLSI to the user plane function; receive an indication from the user plane function indicating confirmation or rejection of binding; and transmit the indication to the first network entity.

[0304] Item 25. A second network entity according to any one of items 17 to 24, wherein the second network entity is further configured to: set an validity timer for the CLSI; and update or release the binding information of the CLSI and the stored device when the validity timer expires.

[0305] Item 26. A second network entity according to any one of items 17 to 25, wherein the second network entity is further configured to: receive from the first network entity an indication of failure of a connectionless service message; release binding information of a device; and transmit a request to the first network entity for the release binding information of the device.

[0306] Item 27. A second network entity according to any one of items 17 to 26, wherein the second network entity is further configured to: receive from the first network entity an instruction indicating that binding information release is required; binding information of the release device; and transmit to the first network entity a request for binding information of the release device.

[0307] Item 28. A second network entity according to any one of items 17 to 27, wherein the second network entity is further configured to: receive from the first network entity a request to change the delivery mode of services associated with the device.

[0308] Item 29. A second network entity according to any one of Items 17 to 28, wherein the second network entity is further configured to: receive a session establishment request from a third network entity, the session establishment request including a receiver termination identifier of a transport tunnel and an upper limit value for CLSI; establish a transport tunnel for at least one connectionless service; and transmit a response to the session establishment request to the third network entity, the response including a receiver termination identifier of a transport tunnel and a lower limit value for CLSI.

[0309] Item 30. The second network entity according to Items 17 to 29, wherein the CLSI is associated with a Protocol Data Unit (PDU) session associated with the device.

[0310] Item 31. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: determine a radio configuration for connectionless service by monitoring broadcast information from at least one cell, the radio configuration being associated with a target cell of a network entity; and transmit a connectionless service message to a network entity, including a connectionless service identifier (CLSI) associated with the apparatus, via random access to the network entity; and receive another connectionless service message from the network entity including the CLSI or another CLSI.

[0311] Item 32. The apparatus according to Item 31, wherein the apparatus is further configured to: determine whether the apparatus is in a radio-configured connectionless notification area, wherein the broadcast information includes an indication of the connectionless notification area.

[0312] Item 33. The apparatus according to Item 32, wherein the connectionless notification area is allocated to the apparatus via radio resource control signaling together with radio configuration.

[0313] Item 34. An apparatus according to any one of items 31 to 32, wherein the apparatus is further configured to: encrypt the payload of a connectionless service message based on a security key; and / or decrypt the payload of another connectionless service message based on a security key.

[0314] Item 35. An apparatus according to any one of items 31 to 32, wherein the apparatus is further configured to: receive a temporary identifier for the apparatus from a network entity, wherein a connectionless service message and another connectionless service message include a CLSI and the temporary identifier for the apparatus.

[0315] Item 36. The apparatus according to Item 35, wherein the apparatus is further configured to: in response to receiving a connectionless service message from a network entity, reset a timer for a temporary identifier for the apparatus; and release the temporary identifier for the apparatus when the timer expires; and transmit the connectionless service message to initiate a connection service.

[0316] Item 37. An apparatus according to any one of items 31 to 36, wherein the apparatus is further configured to: decrypt another connectionless service message in response to receiving another connectionless service message from a network entity; and store an acknowledgment that connectionless access is active in response to successful decryption of the other connectionless service message.

[0317] Item 38. An apparatus according to any one of items 31 to 37, wherein the apparatus is further configured to: select another target cell based on monitoring of broadcast information; and transmit an initial connectionless service message to the other target cell, the initial connectionless service message including a subsequent connectionless service message or a null message.

[0318] Item 39. An apparatus according to any one of items 31 to 38, wherein the CLSI is associated with a Protocol Data Unit (PDU) session associated with the apparatus.

[0319] Item 40. An apparatus according to any one of items 31 to 39, wherein the connectionless service message includes a header for connectionless access, the header including a CLSI and a message type for the connectionless service message.

[0320] Item 41. An apparatus according to any one of items 31 to 39, wherein the apparatus includes terminal equipment and the network entity includes or implements a radio access network (RAN) node or a distributed unit (DU) of a RAN node.

[0321] Item 42. A method comprising: receiving, at a first network entity, a first connectionless service message from a device, the first connectionless service message including a connectionless service identifier (CLSI) associated with the device; transmitting, to a second network entity, a second connectionless service message including the CLSI and a request for binding the device to a transport tunnel for at least one connectionless service; and receiving, from the second network entity, an indication of acknowledgment or rejection of the binding of the device to the transport tunnel.

[0322] Item 43. A method comprising: receiving a connectionless service message from a first network entity at a second network entity, the connectionless service message including a connectionless service identifier (CLSI) associated with a device and a request for binding of the device to a transport tunnel for at least one connectionless service; and transmitting, based on the CLSI, an indication to the first network entity of acknowledgment or rejection of the binding of the device to the transport tunnel.

[0323] Item 44. A method comprising: determining, at a device, a radio configuration for connectionless service by monitoring broadcast information from at least one cell, the radio configuration being associated with a target cell of a network entity; transmitting, via random access to the network entity, a connectionless service message including a connectionless service identifier (CLSI) associated with the device; and receiving, from the network entity, another connectionless service message including the CLSI or another CLSI.

[0324] Item 45. An apparatus comprising: means for receiving a first connectionless service message from the apparatus, the first connectionless service message including a connectionless service identifier (CLSI) associated with the apparatus; means for transmitting a second connectionless service message to a second network entity, the second connectionless service message including the CLSI and a request for binding the apparatus to a transport tunnel for at least one connectionless service; and means for receiving from the second network entity an indication of acknowledgment or rejection of the binding of the apparatus to the transport tunnel.

[0325] Item 46. An apparatus comprising: a component for receiving a connectionless service message from a first network entity, the connectionless service message including a connectionless service identifier (CLSI) associated with the apparatus and a request for binding the apparatus to a transport tunnel for at least one connectionless service; and a component for transmitting, based on the CLSI, an indication to the first network entity of acknowledgment or rejection of the binding of the apparatus to the transport tunnel.

[0326] Item 47. An apparatus comprising: means for determining a radio configuration for connectionless service by monitoring broadcast information from at least one cell, the radio configuration being associated with a target cell of a network entity; means for transmitting a connectionless service message including a connectionless service identifier (CLSI) associated with the means to a network entity via random access to the network entity; and means for receiving another connectionless service message including the CLSI or another CLSI from the network entity.

[0327] Item 48. A computer-readable medium including instructions stored thereon for causing a device to perform at least one of the methods of Item 42, Item 43, or Item 44.< / clsi>

Claims

1. A first network entity, comprising: At least one processor; as well as At least one memory stores instructions that, when executed by the at least one processor, cause the first network entity to at least: Receive a first connectionless service message from the device, the first connectionless service message including a connectionless service identifier (CLSI) associated with the device; Transmit a second connectionless service message to a second network entity, the second connectionless service message including the CLSI and a request for binding the device to a transport tunnel for at least one connectionless service; as well as Receive from the second network entity an indication of confirmation or rejection of the binding between the device and the transmission tunnel.

2. The first network entity according to claim 1, wherein the first network entity is further configured such that: In response to the instruction indicating rejection of the binding and the CLSI, the binding information of the device, indicating the association between the CLSI and the transport tunnel, is removed.

3. The first network entity according to claim 1, wherein the first network entity is further configured such that: In response to the indication confirming the binding and the CLSI, binding information of the device is stored, the binding information indicating the association between the CLSI and the transport tunnel. At least one of the transmissions from or to the device is based on the binding information via the transmission tunnel.

4. The first network entity according to any one of claims 1 to 3, wherein the first network entity is further configured such that: Based on the CLSI, radio configuration information for the device is determined; Based on the CLSI, the stored binding information of the device is recovered; and Based on the stored binding information and the radio configuration, receive a connectionless service message from the device or transmit a connectionless service message to the device.

5. The first network entity according to any one of claims 1 to 3, wherein the first network entity is further configured such that: During random access to the first network entity, the device receives the first connectionless service message including the CLSI; Determine a temporary identifier for the device and a radio configuration for the connectionless service; and Receive a connectionless service message including the temporary identifier from the device, or transmit a connectionless service message including the temporary identifier to the device.

6. The first network entity of claim 5, wherein the first network entity includes a second cell, the first connectionless service message is addressed to the second cell, and the first network entity is further configured to: Transmit a connectionless service message to the first cell, including a request to release the binding information of the device; and Receive a connectionless service message from the first cell that confirms the release.

7. The first network entity according to any one of claims 1 to 3, wherein the first network entity is further configured such that: Based on the CLSI, the transport tunnel associated with the second network entity for the connectionless service is determined, wherein the CLSI includes a prefix indicating an identifier of the second network entity.

8. The first network entity according to any one of claims 1 to 3, wherein the first network entity is further configured such that: Set a validity timer for the CLSI; and When the validity timer expires, the CLSI and the stored binding information of the device are released.

9. The first network entity according to any one of claims 1 to 3, wherein the first network entity includes a first cell serving the device, and the first network entity is further configured such that: Receive a connectionless service message from the second cell including a request to release the binding information of the device, wherein a cell handover from the first cell to the second cell is to be performed; Release the binding information; and A connectionless service message acknowledging the release is transmitted to the second cell.

10. The first network entity according to any one of claims 1 to 3, wherein the first network entity is further configured such that: In response to a connectionless service message indicating that transmission to the device failed, Transmit an indication of the failure of the connectionless service message to the second network entity; Receive a request from the second network entity to release the binding information of the device; and Release at least one of the following: the temporary identifier of the device or the binding information of the device.