User data transfer in communication system over control plane using specified payload container type
By using the specified payload container type in the 5G communication system to transmit the control plane user data, the problems of low efficiency and high energy consumption of control plane message management in the 5G system are solved, and low power consumption and efficient data transmission for IoT devices are realized , extends the battery life of the device.
Patent Information
- Application Number
- CN202411386282.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2019-07-29
- Filing Date
- 2020-07-29
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2040-07-29
AI Technical Summary
Existing 5G communication systems have problems with inefficiency and high energy consumption in control plane message management, especially in Internet of Things (IoT) devices, resulting in shorter battery life and poor network performance.
User data transmission is carried out through the control plane using the specified payload container type (such as CIoT small data container and CIoT user data container). Select the appropriate container type according to the data size to minimize transmission overhead, support small data transmission and optimize battery life.
By optimizing control plane messaging, significantly reduces the energy consumption of IoT devices, extends battery life, and improves network performance, and is suitable for low-power and efficient data transmission requirements in 5G CIoT deployments.
Smart Images

Figure CN119012407A_ABST
Abstract
Description
[0001] This divisional application is a divisional application of Chinese patent application No. 202080048537.9, entitled “User data transmission in a communication system through a control plane using a specified payload container type”, filed on July 29, 2020. Technical Field
[0002] The technical field relates generally to communication systems and, more particularly, but not exclusively, to control plane communications in such systems. Background Art
[0003] This section introduces aspects that may help promote a better understanding of the present invention. Therefore, the statements in this section should be read from this perspective and should not be understood as an admission that there is content in the prior art or that there is content that does not exist in the prior art.
[0004] The fourth generation (4G) of wireless mobile telecommunication technology, also known as Long Term Evolution (LTE) technology, is designed to provide high capacity mobile multimedia at high data rates, particularly for human interaction. The next or fifth generation (5G) technology is intended not only for human interaction, but also for machine-type communications in so-called Internet of Things (IoT) networks.
[0005] While 5G networks are intended to enable large-scale IoT services (e.g., a very large number of limited-capacity devices) and mission-critical IoT services (e.g., requiring high reliability), they support improvements to traditional mobile communication services in the form of enhanced mobile broadband (eMBB) services, providing improved wireless Internet access to mobile devices.
[0006] In an example communication system, a user equipment (5G UE in a 5G network, or more broadly, UE) such as a mobile terminal (subscriber) communicates over an air interface with a base station or access point referred to as a gNB in the 5G network. An access point (e.g., a gNB) is illustratively part of an access network of the communication system. For example, in a 5G network, the access network is referred to as a 5G system and is described in the 5G Technical Specification (TS) 23.501, V16.0.2 entitled "Technical Specification Group Services and System Aspects; System Architecture for the 5G System", the disclosure of which is incorporated herein by reference in its entirety. In general, an access point (e.g., a gNB) enables a UE to access a core network (CN), which in turn enables the UE to access other UEs and / or data networks, such as a packet data network (e.g., the Internet).
[0007] TS23.501 goes on to define a 5G service-based architecture (SBA) that models services as network functions (NFs) that communicate with each other using a representational state transfer application programming interface (Restful API).
[0008] In addition, the 5G Technical Specification (TS) 33.501, V15.4.0 entitled "Technical Specification Group Services and System Aspects; Security Architecture and Procedures for the 5G System" further describes the security management details associated with the 5G network, and the public content of the technical specification is incorporated herein by reference in its entirety.
[0009] Network performance is an important consideration in any communication system. For example, the processing of control plane messages received by the core network from user equipment can have a significant impact on network performance. However, the management of such communications presents several challenges in existing 5G approaches. Summary of the invention
[0010] The illustrative embodiments provide improved techniques for user data transmission in a communication system over a control plane using a specified payload container type.
[0011] For example, in one illustrative embodiment, a method includes determining a size of user data to be transmitted from a user equipment to at least one network entity of a communication system via a control plane. The method also includes, in response to determining that the size of the user data to be transmitted is at least below a small data transmission threshold, generating a control plane message, the control plane message including the user data to be transmitted via the control plane in a payload container dedicated to small user data transmission (hereinafter referred to as a small data container). The method further includes transmitting the generated control plane message from the user equipment to at least one network entity of the communication system.
[0012] In another illustrative embodiment, a method includes determining a size of user data to be transmitted from at least one network entity of a communication system to a user device via a control plane. The method also includes, in response to determining that the size of the user data to be transmitted is at least below a small data transfer threshold, generating a control plane message, the control plane message including the user data to be transmitted in a small data container. The method further includes transmitting the generated control plane message from the at least one network entity of the communication system to the user device.
[0013] Other illustrative embodiments are provided in the form of a non-transitory computer-readable storage medium having executable program code embodied therein, which, when executed by a processor, causes the processor to perform the above steps. Other illustrative embodiments include a device having a processor and a memory configured to perform the above steps.
[0014] These and other features and advantages of the embodiments described herein will become more apparent from the accompanying drawings and the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] Figure 1 A communication system is shown for implementing one or more illustrative embodiments.
[0016] Figure 2 A processing architecture of user equipment and network entities for implementing one or more illustrative embodiments is shown.
[0017] Figure 3 A portion of a communication system for implementing one or more illustrative embodiments is shown, in which a user equipment transmits data to a data network via a control plane.
[0018] Figure 4 An uplink small data transmission for a user equipment in idle mode is shown according to an illustrative embodiment.
[0019] Figure 5 An uplink small data transfer for a user equipment in connected mode is shown according to an illustrative embodiment.
[0020] Figure 6 A downlink small data transmission for a user equipment is shown according to an illustrative embodiment.
[0021] Figure 7 The structure of a small data container information element is shown according to an illustrative embodiment.
[0022] Figure 8 Shown are small data container contents according to an illustrative embodiment.
[0023] Fig. 9 The contents of a small data container information element are shown according to an illustrative embodiment.
[0024] Fig.10 The structure of a user data container information element is shown in accordance with an illustrative embodiment.
[0025] Fig.11 User data container contents are shown according to an illustrative embodiment.
[0026] Fig.12 The contents of a user data container information element are shown according to an illustrative embodiment.
[0027] Fig.13 Message and information element usage of small data containers according to an illustrative embodiment is shown.
[0028] Fig.14 The structure of a payload container information element is shown in accordance with an illustrative embodiment.
[0029] Fig.15 The structure of a payload container type information element is shown in accordance with an illustrative embodiment.
[0030] Fig.16 The contents of a payload container information element are shown according to an illustrative embodiment.
[0031] Fig.17 A control plane data size configuration is shown according to an illustrative embodiment.
[0032] Fig.18 Data protection for a small data container for a user device in idle mode is shown in accordance with an illustrative embodiment.
[0033] Fig.19 A control plane based user data delivery method using a specified payload container type is shown in accordance with an illustrative embodiment. DETAILED DESCRIPTION
[0034] Embodiments are described herein in conjunction with example communication systems and associated technologies for transmitting user data in a communication system through a control plane using a specified payload container type. However, it should be understood that the scope of the claims is not limited to the disclosed specific type of communication system and / or process. Optional processes and operations can be used in various other types of communication systems to implement embodiments. For example, although described in the context of a wireless cellular system utilizing 3GPP system elements such as 3GPP Next Generation Systems (5G), the disclosed embodiments can be used in a straightforward manner for various other types of communication systems. It should be noted that 3GPP stands for the Third Generation Partnership Project, which is a standard organization for developing protocols for mobile phones, etc.
[0035] According to the illustrative implementation scheme implemented in the 5G communication system environment, one or more 3GPP technical specifications (TS) and technical reports (TR) provide further explanations of user equipment and network entities (e.g., network elements, network functions, etc.) and / or operations, which interact with one or more illustrative implementation schemes, such as 3GPP TS23.501 and 3GPP TS 33.501 cited above. Other 3GPP TS / TR documents provide other conventional details that will be recognized by ordinary technicians in the field. For example, 5G Technical Specification (TS) 23.401, V16.2.0, entitled "Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) Enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Access", describes general principles of cellular IoT (CIoT) optimization, which will be used to describe one or more illustrative implementations below, and the disclosure of the technical specification is incorporated herein by reference in its entirety. However, while the illustrative implementations are well suited for implementations associated with the above-mentioned 5G-related 3GPP standards, alternative implementations are not necessarily intended to be limited to any particular standard.
[0036] In addition, the illustrative embodiments may be explained herein in the context of the open system interconnection model (OSI model), which is a model that conceptually characterizes the communication functions of a communication system such as a 5G network, for example. The OSI model is generally conceptualized as a layered stack, in which a given layer is served by an upper layer and is served by a lower layer. Typically, the OSI model includes seven layers, in which the top layer of the stack is the application layer (layer 7), followed by the presentation layer (layer 6), the session layer (layer 5), the transport layer (layer 4), the network layer (layer 3), the data link layer (layer 2), and the physical layer (layer 1). Those of ordinary skill in the art will understand the functions and interactions of the various layers, and therefore, further details of each layer will not be described herein. However, it should be understood that although the illustrative embodiments are well suited to implementations utilizing the OSI model, alternative embodiments are not necessarily limited to any particular communication function model.
[0037] The illustrative embodiments relate to control plane message management associated with a service-based architecture (SBA) for a 5G network. Figure 1 and Figure 2 A general description of the main components of a 5G network is described in the context of .
[0038] Figure 1 A communication system 100 is shown within which an illustrative embodiment is implemented. It should be understood that the elements shown in the communication system 100 are intended to represent the main functions provided within the system, such as UE access functions, mobility management functions, authentication functions, serving gateway functions, etc. Thus, Figure 1 The boxes shown in refer to specific elements in the 5G network that provide these main functions. However, in other embodiments, other network elements may be used to implement some or all of the main functions represented. In addition, it will be understood that in Figure 1 Not all functionality of a 5G network is depicted in the 3D images. Rather, functionality that facilitates explanation of the illustrative implementation is presented. Subsequent figures may depict some additional elements / functionality.
[0039] Thus, as shown, the communication system 100 includes a user equipment (UE) 102, which communicates with an access point (gNB) 104 via an air interface 103. In some embodiments, the UE 102 may be a mobile station, and such a mobile station may include, for example, a mobile phone, a computer, or any other type of communication device. Therefore, the term "user equipment" as used herein is intended to be understood in a broad sense so as to include various different types of mobile stations, subscriber stations, or more generally communication devices, including examples such as combinations of data cards inserted into laptops or other devices such as smart phones or other cellular devices. In one or more illustrative embodiments, the user equipment refers to an IoT device, and more specifically, supports CIoT optimization as described above and further explained herein. In such embodiments when the UE is an IoT device, non-limiting examples of such devices may include sensors, monitors, actuators, robotic devices, and / or other machine-based devices. Such communication devices are also intended to include devices commonly referred to as access terminals.
[0040] In one embodiment, the UE 102 includes a Universal Integrated Circuit Card (UICC) part and a Mobile Equipment (ME) part. The UICC is the user-related part of the UE and contains at least one Universal Subscriber Identity Module (USIM) and appropriate application software. The USIM securely stores a permanent subscription identifier and its associated keys, which are used to identify and authenticate subscribers to access the network. The ME is the user-independent part of the UE and contains terminal equipment (TE) functions and various mobile terminal (MT) functions.
[0041] Note that in one example, the permanent subscription identifier is the International Mobile Subscriber Identity (IMSI) of the UE. In one embodiment, the IMSI is a fixed length of 15 digits and consists of a 3-digit Mobile Country Code (MCC), a 3-digit Mobile Network Code (MNC), and a 9-digit Mobile Station Identification Number (MSIN). In 5G communication systems, the IMSI is referred to as a Subscription Permanent Identifier (SUPI). In the case where the IMSI is used as the SUPI, the MSIN provides the subscriber identity. Therefore, it is usually only necessary to encrypt the MSIN part of the IMSI. The MNC and MCC parts of the IMSI provide routing information, which is used by the service network to route to the correct home network. When the MSIN of the SUPI is encrypted, it is referred to as a Subscription Hidden Identifier (SUCI).
[0042] Access point 104 is illustratively part of an access network of communication system 100. Such an access network includes, for example, a 5G system having multiple base stations and one or more associated radio network control functions. The base stations and radio network control functions are logically separate entities in some embodiments, but are implemented in the same physical network element (e.g., such as a base station router or a cellular access point) in other embodiments.
[0043] In this illustrative embodiment, the access point 104 is operatively coupled to the mobility management function 106. In a 5G network, the mobility management function is implemented by an access and mobility management function (AMF). In some embodiments, the security anchor function (SEAF) can also be implemented with the AMF to connect the UE to the mobility management function. As used herein, the mobility management function is an element or function (i.e., entity) in the core network (CN) portion of the communication system that manages or otherwise participates in the access and mobility (including authentication / authorization) operations of the UE (through the access point 104) in addition to other network operations. The AMF may also be more generally referred to as an access and mobility management entity herein.
[0044] Although the illustrative embodiments will be described below from the perspective of control plane communication between UE and AMF in a 5G system environment, it should be understood that the control plane message management techniques described herein can be applied in a direct manner to other communication systems other than 5G systems, for example, LTE or other 3GPP systems, and any suitable non-3GPP systems. For example, in an alternative embodiment where the communication system is an LTE system, the mobility management function is performed by a mobility management entity (MME).
[0045] Back to Figure 1 In this illustrative embodiment, the AMF 106 is operatively coupled to a Home Subscriber Function 108, i.e., one or more functions resident in the subscriber's home network. As shown, some of these functions include a Unified Data Management (UDM) function and an Authentication Server Function (AUSF). The AUSF and UDM (individually or collectively) are also more generally referred to herein as authentication entities. In addition, the Home Subscriber Function includes, but is not limited to, a Network Slice Selection Function (NSSF), a Network Openness Function (NEF), a Network Repository Function (NRF), and a Policy Control Function (PCF).
[0046] It should be noted that a UE such as UE 102 typically subscribes to a so-called Home Public Land Mobile Network (HPLMN) in which some or all of the Home Subscriber Function 108 resides. If the UE is roaming (not in the HPLMN), it typically connects to a Visited Public Land Mobile Network (VPLMN), also referred to as a visited network or serving network. Some or all of the Mobility Management Function 106 may reside in the VPLMN, in which case the functions in the VPLMN communicate with the functions in the HPLMN as needed. However, in a non-roaming situation, the Mobility Management Function 106 and the Home Subscriber Function 108 may reside in the same communication network.
[0047] The access point 104 is also operatively coupled to a serving gateway function, i.e., a session management function (SMF) 110, which is operatively coupled to a user plane function (UPF) 112. The UPF 112 is operatively coupled to a packet data network, such as the Internet 114. As is known in 5G and other communication networks, the user plane (UP) or data plane generally carries network user traffic (user data), while the control plane (CP) generally carries control signaling traffic (control data). The SMF 110 supports functions related to UP subscriber sessions, such as the establishment, modification, and issuance of PDU sessions. The UPF 112 supports functions that facilitate UP operations, such as packet routing and forwarding, communication with data networks (e.g., Figure 1 114) of interconnection, policy implementation and data buffering.
[0048] It should be understood that Figure 1 is a simplified diagram because Figure 1 Not all communication links and connections between network functions (NFs) and other system elements are shown in the figure. Given the various 3GPP TS / TRs, a person of ordinary skill in the art will understand that not explicitly shown or may be Figure 1 Various links and connections otherwise summarized in .
[0049] Other typical operations and functions of specific network elements are not described in detail herein, as they are not the focus of the illustrative embodiments but can be found in appropriate 3GPP 5G documents. Figure 1 The specific arrangement of system elements in FIG. 1 is merely an example, and other types and arrangements of additional or optional elements may be used to implement the communication system in other embodiments. For example, in other embodiments, system 100 includes other elements / functionality not explicitly shown herein. In addition, although in FIG. Figure 1 Only a single element / function is shown in the embodiments, but this is only for simplicity and clarity of illustration. A given alternative embodiment may include more such system elements, as well as additional or alternative elements of the type normally associated with conventional system implementations.
[0050] It should also be noted that although Figure 1 The system elements are shown as single functional blocks, but the various subnetworks that make up the 5G network are divided into so-called network slices. A network slice (network partition) includes a series of network function (NF) sets (i.e., function chains) for each corresponding service type using network function virtualization (NFV) on a common physical infrastructure. Network slices are instantiated as needed for a given service, such as eMBB services, large-scale IoT services, and mission-critical IoT services. Therefore, a network slice or function is instantiated when an instance of the network slice or function is created. In some embodiments, this involves installing or otherwise running the network slice or function on one or more host devices of the underlying physical infrastructure. UE 102 is configured to access one or more of these services via gNB 104. NFs can also access the services of other NFs.
[0051] The illustrative embodiments provide improved techniques for user data transmission over a control plane of a communication system, particularly with respect to CIoT optimization. Figure 2 2 is a block diagram of a processing architecture 200 of two participants in a control plane-based user data transmission method in an illustrative embodiment, namely, a user equipment and a network function / element (e.g., AMF). It should be understood that according to the illustrative embodiment, more than two participants may be involved in the control plane-based user data transmission method. Therefore, Figure 2The processing architecture associated with any two participants in direct and / or indirect communication is shown. Thus, in the illustrative embodiment, each participant in the control plane-based user data transmission method is understood to be configured with Figure 2 The processing architecture shown.
[0052] As shown, the user equipment 202 includes a processor 212, which is coupled to a memory 216 and an interface circuit system 210. The processor 212 of the user equipment 202 includes a control plane data transmission processing module 214, which can be implemented at least in part in the form of software executed by the processor. The processing module 214 performs control plane-based user data transmission and other operations, which are described in conjunction with subsequent figures and other contents in this article. The memory 216 of the user equipment 202 includes a control plane data transmission storage module 218, which stores data generated or otherwise used during control plane-based user data transmission and other operations.
[0053] As further shown, the network function / element 204 includes a processor 222 coupled to a memory 226 and an interface circuit system 220. The processor 222 of the network function / element 204 includes a control plane data transfer process 224, which may be implemented at least in part in the form of software executed by the processor 222. The processing module 224 performs control plane based user data transfer and other operations, as described in conjunction with subsequent figures and other content herein. The memory 226 of the network function / element 204 includes a control plane data transfer storage module 228, which stores data generated or otherwise used during control plane based user data transfer and other operations.
[0054] The processors 212 and 222 of the respective user equipment 202 and network functions / elements 204 may include, for example, a microprocessor, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), or other types of processing devices or integrated circuits, and portions or combinations of such elements. Such integrated circuit devices, and portions or combinations thereof, are examples of "circuitry," as the term is used herein. Various other arrangements of hardware and associated software or firmware may be used when implementing the illustrative embodiments.
[0055] The memories 216 and 226 of the respective user equipment 202 and network function / element 204 may be used to store one or more software programs that are executed by the respective processors 212 and 222 to implement at least a portion of the functionality described herein. For example, control plane-based data transfer operations and other functionality as described herein in conjunction with subsequent figures and other content herein may be implemented in a straightforward manner using software code executed by the processors 212 and 222.
[0056] A given one of memories 216 or 226 may therefore be viewed as an example of what is more generally referred to herein as a computer program product or, still more generally, as a processor-readable storage medium having executable program code embodied therein. Other examples of processor-readable storage media may include disks or other types of magnetic or optical media (in any combination). Illustrative embodiments may include an article of manufacture that includes such a computer program product or other processor-readable storage medium.
[0057] More specifically, memory 216 or 226 may include, for example, electronic random access memory (RAM), such as static RAM (SRAM), dynamic RAM (DRAM), or other types of volatile or non-volatile electronic memory. The latter may include, for example, non-volatile memory, such as flash memory, magnetic RAM (MRAM), phase change RAM (PC-RAM), or ferroelectric RAM (FRAM). The term "memory" as used herein is intended to be understood in a broad sense and may additionally or alternatively include, for example, read-only memory (ROM), disk-based memory or other types of storage devices, as well as portions or combinations of such devices.
[0058] The interface circuitry 210 and 220 of the respective user equipment 202 and network functions / elements 204 illustratively include transceivers or other communication hardware or firmware that allow the associated system elements to communicate with each other in the manner described herein.
[0059] from Figure 2It is apparent from the user equipment 202 that the user equipment 202 is configured to communicate with the network function / element 204 via the respective interface circuit systems 210 and 220, and vice versa. This communication involves the user equipment 202 sending data to the network function / element 204 and the network function / element 204 sending data to the user equipment 202. However, in alternative embodiments, other network elements or other components may be operatively coupled between the user equipment 202 and the network function / element 204 and to the user equipment and / or the network function / element. The term "data" as used herein is intended to be understood in a broad sense so as to include any type of information that may be sent between control plane message management participants, including but not limited to messages, tokens, identifiers, keys, indicators, user data, control data, etc.
[0060] It should be understood that Figure 2 The specific component arrangements shown in are examples only, and many alternative configurations are used in other embodiments. For example, any given network element / function may be configured to incorporate additional or alternative components and support other communication protocols.
[0061] In view of the above illustrative architecture, an illustrative implementation of the control plane based user data transfer method will be further described below in the context of IoT connectivity in a 3GPP network.
[0062] 3GPP defines a set of technologies for enabling IoT connectivity in 3G and 4G deployments, including extended coverage of Global System for Mobile Communications (GSM) IoT (EC-GSM-IoT), narrowband IoT (NB-IoT), and enhanced machine type communications (eMTC). NB-IoT and eMTC radio technologies will be used in 5G CIoT deployments.
[0063] As mentioned above, the general principles of CIoT optimization are described in TS23.401 cited above (e.g., Section 4.10: Introduction to C-IoT Evolved Packet System (EPS) Optimization). Two types of communication bearer optimization are specified. One optimization is based on the user plane (UP) transmission of user data and is called UP CIoT EPS optimization. Another optimization is called control plane (CP) CIoT EPS optimization, which reduces the total number of control plane messages when processing short data transactions by encapsulating user data or short message service (SMS) messages in the non-access layer (NAS) and transmitting user data or short message service (SMS) messages via the mobility management element (MME in LTE or AMF in 5G). NAS is a functional layer in the UMTS and LTE wireless telecommunications protocol stacks between the core network and the user equipment. This layer is used to manage the establishment of communication sessions and maintain continuous communication with the user equipment when the user equipment is roaming.
[0064] When the UE attaches to the network, the UE includes in the preferred network behavior indication the network behaviors that the UE can support and what it prefers to use, such as whether CP CIoT EPS optimization is supported or whether UP CIoT EPS optimization is supported.
[0065] When CP CIoT EPS optimization is supported, CIoT UE can send and receive small data packets through the NAS signaling control plane. There are some benefits when CIoT UE uses the control plane for communication because the control plane is not always busy and has a relatively low packet rate.
[0066] A key requirement for IoT devices is battery life. Both Long Term Evolution (LTE) Category M1 (Cat-M1) and NB-IoT require significant reductions in power consumption over broadband cellular technology. Battery life can be important for a variety of low-cost sensor and metering type IoT devices. For example, in NB-IoT, a maximum battery life of 10 years is expected even in extreme coverage conditions. Ideally, the battery of such an IoT device should last throughout the expected lifecycle of the device to avoid expensive maintenance.
[0067] In an example embodiment, consider a case where a 5G UE 302 communicates with a control plane (e.g., Figure 3 304 (shown by the dotted line in FIG. 305 ) transmits user data to a data network 314 (e.g., a packet data network (PDN), such as the Internet) through an N6 interface in a 5G communication system. UE 302 is connected to AMF 308 via a 3GPP access point 304 and an NG radio access network (NG-RAN) 306 and provides user data through an N1 interface. AMF 308 provides user data to SMF 310 through an N11 interface, and SMF provides user data to UPF 312 through an N4 interface. UPF 312 provides data to data network 314 through an N6 interface. Figure 3 Also shown is the communication and interface between AMF 308 and authentication entity 316, which is assumed to include AUSF 318, UDM 320, and User Data Repository (UDR) 322. As shown, SMF 310 and UDR 322 also communicate with PCF 324.
[0068] Data packet size can have a significant impact on IoT device battery life. For 5G CIoT, it is necessary to support the transmission of infrequent "small" data on the control plane. As described in further detail below, the communication system can be configured to define "small" data sizes, such as based on the size of typical messages expected to be sent in 5G CIoT using a specific type of IoT device. User-defined thresholds can be used to specify an appropriate size range for "small" data, as the term is used in this article. When transmitting small data on the control plane, it is important to minimize the overhead involved in the transmission, thereby reducing the energy consumption of the IoT device to save battery life.
[0069] The illustrative embodiments provide an effective method for transmitting infrequent small data for IoT devices, thereby advantageously extending the battery life of IoT devices. In some embodiments, effective transmission of infrequent small data is provided by non-access layer (NAS) signaling. To this end, some embodiments define a dedicated container for such small data transmission, referred to herein as a "CIoT small data container". The CIoT small data container is regarded as a special type of payload container type, and UE 302 and AMF 308 are configured with a program for processing CIoT small data containers. In some embodiments, a mechanism is provided to support the configuration of the maximum small data size and the logic for processing small data transmission and "large" data transmission. In this context, "large" data transmission refers to the transmission of data exceeding the user-defined threshold for "small" data as described above and elsewhere in this article. Additional user-defined thresholds can be used to specify the maximum size of "large" data transmission carried out by the control plane (larger data is transmitted through the user plane).
[0070] Techniques for protecting and encrypting the content of data transmitted over the control plane are also provided.
[0071] Figure 4 An uplink small data transfer procedure 400 for a UE 302 in idle mode is shown. A UE 302 in idle mode on a 3GPP access may have pending uplink user data, and the UE may use 5G System (5GS) services with control plane CIoT 5GS optimization. As a prerequisite, it is assumed that the UE 302 registers 401 with the AMF 308 for CIoT control plane optimization (CP-CIoT) for establishing a NAS security context 402, and that encryption and integrity protection mechanisms 403 are provided. In addition, it is assumed that the UE 302 is in idle mode 404 and has uplink user data to send.
[0072] In step 405, UE 302 sets the control plane service type of the control plane service request message to "mobile initiated request". In addition, UE 302 sets the payload container information element (IE) type to "CIoT small data container". UE302 formats the protocol data unit (PDU) session identifier (ID) and publishes auxiliary information and data in the CIoT small data container. In some embodiments, the PDU session ID is 4 bits and the publishing auxiliary information is 2 bits. When UE 302 wishes to notify the network of one of the two conditions, including publishing auxiliary information. The first condition is that after the current uplink data transmission, no further uplink and further downlink data transmission (e.g., confirmation, response, etc.) is expected. In other words, the first condition occurs when the upper layer indicates that data exchange has been completed through the current uplink data transmission. The second condition is that after the current uplink data transmission, only a single downlink data transmission is expected and no further uplink data transmission is no longer expected. In other words, the second condition occurs when the upper layer indicates that data exchange will be completed through the next downlink data transmission. It should be understood that in other embodiments, different conditions or more generally different release assistance information may be utilized. In step 405, UE 302 also sets the payload container IE to a CIoT small data container.
[0073] The control plane service request message sent by the UE 302 in step 405 includes the payload container type and the payload container formatted as described above. If additional information such as PDU session status for PDU session synchronization or CP to UP switching indication (e.g., via uplink data status) is required, such information may be included as a separate IE in the control plane service request message in step 405. The UE 302 then sends the control plane service request message in step 405 to the AMF 308 (e.g., via the NG-RAN 306). The UE 302 also starts a retransmission timer (e.g., T3517) and enters state "5GMM-SERVICE-REQUEST-INITIATED".
[0074] Upon receiving the step 405 control plane service request message with the control plane service type indicating "mobile originated request", and after completing the 5GS Mobility Management (5GMM) common procedures, the AMF 308 sends a service acceptance message 409 to the UE 302. If the payload container IE is included in the step 405 control plane service request message and the payload container type IE is set to "CIoT small data container", and if the payload container IE successfully passes the integrity check, the AMF 308 extracts the PDU session ID and release assistance information in step 406. In step 407, the AMF 308 forwards the data content to the SMF 310 via the Nsmf_PDU session_data transfer request message in step 408. This request message includes data and the PDU session ID.
[0075] As described above, the AMF 308 sends a service accept message 409 to the UE 302. The service accept message 409 indicates the PDU session status and the UE 302 is now in connected mode 410. At this point, a radio resource control (RRC) connection has been established 411. If the PDU Session Status IE was included in the control plane service request message in step 405, or if the AMF 308 needs to perform PDU Session Status synchronization, the AMF 308 includes the PDU Session Status IE in the service accept message 409 to indicate which PDU sessions associated with the access type in the service accept message 409 are active in the AMF 308.
[0076] In step 412, the SMF 310 selects the UPF 312 (or NEF) for user data delivery from the UE 302 based on the configuration. Then, the SMF 310 generates a PFCP_DATA_FORWARD message 413 and sends it to the UPF 312. The PFCP_DATA_FORWARD message 413 is a Packet Forwarding Control Protocol (PFCP) message and includes a tunnel ID and a payload container (e.g., user data) from the control plane service request message of step 405.
[0077] If the Release Assistance Indication IE is included in the control plane service request message in step 405, and if the Payload Container Type IE is set to "CIoT Small Data Container", the AMF 308 will act based on the conditions indicated by the Release Assistance Indication in step 414. If the Release Assistance Indication indicates that no further uplink or downlink data transmission is expected after the uplink data transmission (e.g., the first condition described above), the AMF 308 releases the RRC connection (e.g., NAS signaling connection). If the Release Assistance Indication indicates that only a single downlink data transmission is expected after the uplink data transmission and no further uplink data transmission is expected (e.g., the second condition described above), the AMF 308 releases the RRC connection after delivering the next received downlink data transmission to the UE 302.
[0078] Upon successful completion of the above procedure, the UE 302 resets the service request attempt counter, stops timer T3517, and enters the "5GMM-Restricted" state. The UE 302 also regards the indication of a published RRC connection from the lower layer as a successful completion of the procedure. If the PDU session state information element is included in the service acceptance message 409, the UE 302 performs a local release of all those PDU sessions that are active on the UE side associated with the 3GPP access, but are indicated as inactive by the AMF 308.
[0079] Figure 5 An uplink small data transfer procedure 500 is shown for a UE 302 in connected mode. A UE 302 in idle mode on a 3GPP access may have pending uplink user data, and the UE may use 5GS services with control plane CIoT 5GS optimization. Figure 4 , it is assumed that the UE 302 registers 501 with the AMF 308 for CP-CIoT for establishing a NAS security context 502, and provides encryption and integrity protection mechanisms 503. In addition, it is assumed that the UE 302 is in connected mode 504 and has uplink user data to send.
[0080] In step 505, UE 302 generates an uplink NAS data transfer (UL_NAS_transfer) message. UE 302 sets the payload container type IE to "CIoT small data container" and formats the PDU session ID and the release auxiliary information and the data in the CIoT small data container. Similarly, the PDU session ID can be 4 bits and the release auxiliary information is 2 bits. Release auxiliary information is combined with the above Figure 4The UE 302 may be configured to transmit the auxiliary information to the network in a manner similar to that described above and may be used by the UE 302 to notify the network of a first condition (e.g., no further uplink data transmission and no further downlink data transmission are expected after the current uplink data transmission) or a second condition (e.g., only a single downlink data transmission and no further uplink data transmission are expected after the current uplink data transmission). It should be understood that in other embodiments, different conditions or more generally different release assistance information may be utilized. The UE 302 also sets the payload container IT to a CIoT small data container.
[0081] The UE 302 includes the payload container type and payload container formatted as described above in the uplink NAS data transfer message in step 505. If additional information such as PDU session status for PDU session synchronization or CP to UP switching indication (e.g., via uplink data status) is required, such information may be included as a separate IE in the uplink NAS data transfer message in step 505. Then, the UE 302 sends the step 505 uplink NAS data transfer message to the AMF 308.
[0082] Upon receiving the uplink NAS data transfer message in step 505, if the payload container IE is included and the payload container type IE is set to "CIoT small data container", and if the payload container IE successfully passes the integrity check, the AMF 308 extracts the PDU session ID and release assistance information in step 506. In step 507, the AMF 308 forwards the data to the SMF 310 associated with the UE, such as via a method similar to that described above in conjunction with Figure 4 The Nsmf_PDU session_data transfer request message 508 of the message 408 is described.
[0083] If applicable, possible downlink data is provided to the UE 302 in step 509. The AMF 308 processes the NAS signaling connection release (e.g., RRC release) in step 510 based on the release assistance information included in the uplink NAS data transmission message in step 505. If the release assistance indication indicates that no further uplink or downlink data transmission is expected after the uplink data transmission (e.g., the first condition described above), the AMF 308 releases the RRC connection (e.g., NAS signaling connection). If the release assistance indication indicates that only a single downlink data transmission is expected after the uplink data transmission and no further uplink data transmission is expected (e.g., the second condition described above), the AMF 308 releases the RRC connection after delivering the next received downlink data transmission to the UE 302. The RRC connection is released in step 511, and the UE 302 enters the idle mode in step 512.
[0084] In step 513, SMF 310 selects UPF 312 (or NEF) for user data delivery from UE 302 based on the configuration. SMF 310 then generates and sends a PFCP_DATA_FORWARD message 514 to UPF 312. PFCP_DATA_FORWARD message 514 is similar to that described above with respect to PFCP_DATA_FORWARD message 413.
[0085] Figure 4 and Figure 5 Mobile initiated NAS transfer procedures 400 and 500 are shown for a UE 302 in idle and connected modes, respectively. Figure 6 A network initiated downlink small data transfer procedure 600 for UE 302 is shown, where CIoT user data is provided from AMF 308 to UE 302 via the control plane in a 5G MM message (e.g., via the N6 interface in a 5G system). Figure 4 and Figure 5 , it is assumed that UE 302 registers 601 with AMF 308 for CP-CIoT for establishing NAS security context 602, and provides encryption and integrity protection mechanism 603. In addition, it is assumed that UE 302 is in connected mode 604 and AMF 308 has downlink user data to be sent to UE 302.
[0086] The AMF 308 and the SMF 310 have an association established with each other in step 605, and the SMF 310 and the UPF 312 have a PFCP association established with each other in step 606. In step 607, the UPF 312 provides a PFCP_Data_Forward message to the SMF 310. The message includes a tunnel ID and a payload container with user data to be sent to the UE 302. In step 608, the SMF 310 generates and sends a Nsmf_PDU Session_Data Transfer Notification message including the data and the PDU Session ID.
[0087] In step 609, the AMF 308 generates a downlink NAS transfer message and sends it to the UE 302. The AMF 308 sets the payload container type IE to "CIoT small data container" and formats the PDU session ID and the downlink data of the UE 302 in the CIoT small data container. Similarly, the PDU session ID can be formatted as 4 bits. The AMF 308 includes the payload container type and payload container formatted into the downlink NAS data transfer message as described above. If additional information such as PDU session status for PDU session synchronization or CP to UP switching indication (e.g., via uplink data status) is required, such information can be included in the downlink NAS data transfer message as a separate IE.
[0088] After receiving the downlink NAS data transfer message in step 609, if a payload container IE is included, if the payload container type IE is set to "CIoT small data container", and if the payload container IE successfully passes the integrity check, UE 302 extracts the PDU session ID and data content from the payload container IE and forwards the data content to the upper layer application.
[0089] Figure 7 700 shows the structure of the CIoT small data container IE. The CIoT small data container IE is used to encapsulate user data transmitted between the UE 302 and the AMF 308. The CIoT small data container IE is as follows: Figure 7 Encoded as shown. In some embodiments, the CIoT small data container is a type 4 information element with a minimum length of 3 octets and a maximum length of 257 octets. Octet 1 includes the CIoT small data container IE identifier (IEI), and octet 2 includes the length of the CIoT small data container contents. Octets 3 to n include the CIoT small data container contents. The value of n is 257, corresponding to the maximum length of the CIoT small data container content 255 (e.g., 257 minus octet 1 for the CIoT small data container IEI and octet 2 for indicating the length of the CIoT small data container contents). As described below with respect to Figure 8 As described in further detail, octet 3 is also reserved in some embodiments, so the user data to be transmitted may occupy up to 254 octets.
[0090] Figure 8 The CIoT small data container contents are shown (e.g., octets 3 to n in structure 700). Octet 3 includes PDU session identity information encoded in 4 bits and expected downlink data (DDX) encoded in 2 bits. Octet 3 also includes two spare bits. Octets 4 to n include data content. Fig. 9900 shows the contents of a CIoT small data container IE, more specifically showing an example of the information in octets 3 to n. For example, Fig. 9 It shows how PDU session data is encoded in 4 bits and how DDX data is encoded in 2 bits.
[0091] Assume that the CIoT small data container is "small" in size or limited to 255 octets of data content, such as Fig. 9 As shown. The CIoT user data container can be used to encapsulate up to 65,531 octets of "large" user data transmitted between UE 302 and AMF 308. Figures 10 to 12 As shown, the CIoT user data container IE is encoded.
[0092] Fig.10 The structure 1000 of the CIoT User Data Container IE is shown. In some embodiments, the CIoT User Data Container is a Type 6 Information Element with a minimum length of 5 octets and a maximum length of 65,535 octets. Octet 1 includes the CIoT User Data Container IEI, and octets 2 and 3 include the length of the CIoT User Data Container contents. Octets 4 to n include the CIoT User Data Container contents. 65,531 octets are available for user data to be transmitted because there are three overhead octets (e.g., octet 1 includes the CIoT User Data Container IEI, and octets 2 and 3 include the length of the CIoT User Data Container contents) plus octet 4 which is reserved in some embodiments as described in further detail below.
[0093] Fig.11 The CIoT user data container contents are shown (e.g., octets 4 to n in structure 1000). Octet 4 includes PDU session identity information encoded in 4 bits and DDX encoded in 2 bits. Octet 4 also includes two spare bits. Octets 5 to n include data content. Fig.12 The contents of the CIoT User Data Container IE 1200 are shown, more specifically an example of the information in octets 4 to n. For example, Fig.12 It shows how PDU session data is encoded in 4 bits and how DDX data is encoded in 2 bits.
[0094] When in idle or connected mode, the UE 302 decides whether to send data via a CIoT user data container or via a CIoT small data container based on the data size to be transmitted, the configured maximum small data size (e.g., configured as a NAS management object (MO) or configured in a Universal Subscriber Identity Module (USIM) Elementary File (EF) CP-CIoT_Maximum Small Data Size parameter), and the configured maximum data size (e.g., configured as a NAS MO or configured in a USIM EF CP-CIoT_Maximum Data Size). When in connected mode, the AMF 308 decides whether to send data to the UE 302 via a CIoT user data container or via a CIoT small data container based on the data size to be transmitted, the configured maximum small data size, and the configured maximum data size.
[0095] More specifically, from the UE 302 side, the decision of whether to use a CIoT user data container or a CIoT small data container can use the following algorithm. If the user data size is less than the configured maximum small data size (e.g., less than CP-CIoT_maximum small data size), the UE 302 uses the CIoT small data container to send data. If the user data size is greater than the configured maximum small data size (e.g., greater than CP-CIoT_maximum small data size) and less than 254 octets, the UE 302 uses the CIoT small data container to send data. If the user data size is greater than 254 octets but less than the configured maximum data size (e.g., less than CP-CIoT_maximum data size), the UE 302 uses the CIoT user data container to send data. If the user data size is greater than the configured maximum data size (e.g., greater than CP-CIoT_maximum data size), the UE 302 switches from CP-CIoT optimization to UP-CIoT optimization and uses the user plane instead of sending data from the control plane via NAS signaling.
[0096] From the network side (e.g., from AMF 308), the decision whether to use a CIoT user data container or a CIoT small data container can use the following algorithm. If the user data size is less than the configured maximum small data size (e.g., less than CP-CIoT_maximum small data size), AMF 308 uses the CIoT small data container to send data. If the user data size is greater than the configured maximum small data size (e.g., greater than CP-CIoT_maximum small data size) and less than 254 octets, AMF308 uses the CIoT small data container to send data. If the user data size is greater than 254 octets but less than the configured maximum data size (e.g., less than CP-CIoT_maximum data size), AMF 308 uses the CIoT user data container to send data. If the user data size is greater than the configured maximum data size (e.g., greater than CP-CIoT_maximum data size), AMF 308 switches from CP-CIoT optimization to UP-CIoT optimization and uses the user plane instead of the control plane to send data via NAS signaling.
[0097] Fig.13 Tables 1301, 1302, and 1303 show messages and IE usage for (e.g., Figure 5 505 in step 506) uplink NAS transmission message, (e.g., Figure 6 ) used in step 609 of the downlink NAS transmission message and (for example, as Figure 4 The message content of the control plane service request message (used in step 405 in ). The payload container of each of Tables 1301, 1302, and 1303 is one of the payload container types shown in Table 1304 (e.g., one of a CIoT small data container and a CIoT user data container). Tables 1305 and 1306 show the structures of these payload container types. More specifically, Table 1305 shows the structure of a CIoT small data container and Table 1306 shows the structure of a CIoT user data container.
[0098] The payload container IE is used to transmit one or more payloads. If multiple payloads are transmitted, the associated information of each payload is also transmitted together with the payload. Fig.14 The payload container IE is encoded as shown. In some embodiments, Fig.14 The Payload Container IE 1400 is a Type 6 Information Element with a minimum length of 4 octets and a maximum length of 65,538 octets. The maximum value of the Payload Container content (octet 4 to octet n) is 65,535 octets.
[0099] If the payload container type is set to "CIoT Small Data Container" and is included in (e.g. Figure 4 In the control plane service request message used in step 405), the encoding method of the payload container content is the same as the encoding method of the content of the CIoT small data container IE, except that the first two octets are not included.
[0100] If the payload container type is set to "CIoT Small Data Container" and is included in (e.g. Figure 5 In the uplink NS transmission message used in step 505 in the example above, the encoding method of the payload container content is the same as the encoding method of the content of the CIoT small data container IE, except that the first two octets are not included.
[0101] If the payload container type is set to "CIoT Small Data Container" and is included in (e.g. Figure 6 In the downlink NS transmission message used in step 609 in the example above, the encoding method of the payload container content is the same as the encoding method of the content of the CIoT small data container IE, except that the first two octets are not included.
[0102] If the payload container type is set to "CIoT User Data Container" and is included in (e.g. Figure 5 In the uplink NAS transmission message used in step 505 in the example above, the encoding method of the payload container content is the same as the encoding method of the content of the CIoT user data container IE, except that the first three octets are not included.
[0103] If the payload container type is set to "CIoT User Data Container" and is included in (e.g. Figure 6 In the downlink NAS transmission message used in step 609 in the example above, the encoding method of the payload container content is the same as the encoding method of the content of the CIoT user data container IE, except that the first three octets are not included.
[0104] If the payload container type is set to "CIoT User Data Container" and is included in (e.g. Figure 4 In the control plane service request message used in step 405 in the example above, the encoding method of the payload container content is the same as the encoding method of the content of the CIoT user data container IE, except that the first three octets are not included.
[0105] In some embodiments, new payload container types are defined for "CIoT Small Data Container" and "CIoT User Data Container". The purpose of the Payload Container Type IE is to indicate the type of payload included in the Payload Container IE. Fig.15 The structure 1500 of a Payload Container Type IE is shown, where bits 1 through 4 in octet 1 are used to provide a Payload Container Type value and bits 5 through 8 in octet 1 are used to provide a Payload Container Type IE. Fig.16 An encoding 1600 of a payload container type value in bits 1 to 4 of octet 1 of a payload container type IE 1500 is shown. As shown, a short message service (SMS) message may be encoded in bits 4 3 2 1 and 0 0 1 0, a CIoT user data container may be encoded in bits 4 3 2 1 and 1 0 0 0, and a CIoT small data container may be encoded as 1 0 0 1 in bits 4 3 21.
[0106] Fig.17 A control plane data size configuration 1700 is shown. More specifically, the control plane data size configuration 1700 is provided in a NAS MO having a maximum data size parameter (e.g., CP-CIoT_MaxDataSize) and a maximum small data size parameter (e.g., CP-CIoT_MaxSmallDataSize).
[0107] The CP-CIoT Maximum Data Size leaf of the NAS MO indicates the configured maximum user data size that can be transmitted on the control plane via NAS signaling when in the Home Public Land Mobile Network (HPLMN) or Equivalent HPLMN (EHPLMN), as described in 3GPP TS23.122. The number of occurrences of this leaf is zero or one, the format is int, the access type is "Get" and "Replace" and the value range is 0 to 65,531. If not provided, this leaf uses a default value of 65,531 octets.
[0108] The CP-CIoT_MaximumSmallDataSize leaf of the NAS MO indicates the configured maximum small data size that can be transmitted on the control plane via NAS signaling when in the HPLMN or EHPLMN. This leaf has zero or one occurrences, the format is int, the access type is "Get" and "Replace" and the value range is 0 to 254. If not provided, this leaf uses a default value of 254.
[0109] (For example, Fig.17The NAS MO) configuration parameters shown in the NAS MO can be set by the device's home network operator (HNO) based on the device class and mode (e.g., including typical data size and transmission frequency) and the device physical layer transport block size. eMTC Cat-M1 type devices have a downlink (DL) transport block size (TBS) of 1000 bits (e.g., 125 octets) and an uplink (UL) TBS of 1000 bits (in 3GPP Release 13) and a ULTBS of 2984 bits in 3GPP Release 14. eMTC Cat-M2 type devices have a DL TBS of 4008 bits and a UL TBS of 2984 bits for 1.4 megahertz (MHz) and a UL TBS of 6968 bits for 5MHz. NB-IoT Cat-NB1 type devices have a DL TBS of 860 bits (e.g., approximately 110 octets) and a UL TBS of 1000 bits (e.g., approximately 125 octets). NB-IoT Cat-NB2 type devices have a DL TBS of 2536 bits and a UL TBS of 2536 bits. Therefore, CIoT small data container is sufficient for NB-IoT Cat-NB1 type devices and is also applicable to eMTC Cat-M1 type devices. For other types of devices, CIoT user data container may be required because it can support data transfer of up to 65,531 octets.
[0110] When UE 302 is in idle mode (e.g., Figure 4 When UE 302 is in connected mode (e.g., Figure 5 and Figure 6 A secure NAS connection is already established and no additional protection for small data is required.
[0111] In order to reduce the overall message overhead, in some embodiments, instead of encrypting the entire message, only the non-plaintext IE is encrypted. After UE 302 formats the payload container, UE 302 includes the payload container type IE, the payload container IE, and other non-plaintext IEs in the NAS message container IE, and encrypts the value portion of the NAS message container IE using the encryption key from the NAS security context of UE 302. This is done in Fig.18 The example control plane service request message content is shown in 1800. UE 302 sets the security header type of the control plane service request message in step 405 to "integrity protection" and sends the control plane service request message containing the plain text IE and the NAS message container IE to the network (for example, to AMF 308).
[0112] When AMF 308 receives the integrity-protected control plane service request message including the NAS message container IE, AMF 308 performs an integrity check on the network side. Once the integrity check succeeds, AMF 308 decrypts the value portion of the NAS message container IE and extracts the payload container type IE, payload container IE, and other non-plaintext IEs.
[0113] If the control plane service request message fails the integrity check on the network side and the UE 302 has only established a non-emergency PDU session, the AMF 308 sends a service reject message with 5GMM cause #9 ("UE identity cannot be derived from the network") and keeps the 5GMM content and 5G NAS security context unchanged.
[0114] like Fig.18 As shown, the plain text IE of the control plane service request message includes: extended protocol discriminator; security header type; spare half octet; ngKSI (ng key set identifier); control plane service request message identity; and control plane service type. Fig.18 The remaining IEs shown in are non-plaintext IEs, including: payload container type; payload container IE; PDU session ID; PDU session status; uplink status; release assistance information IE; and so on.
[0115] If the data to be transmitted exceeds the CIoT_MaximumSmallDataSize parameter, a larger CIoTUserDataContainer is used to buffer the user data. The processing logic for transmitting large IoT data when the UE 302 is in both idle mode and connected mode is the same as described above, except that the PayloadContainerTypeIE is set to "CIoTUserDataContainer" and the PayloadContainerIE is set to the value portion of the CIoTUserDataContainer. The logic for encrypting large IoT data when the UE 302 is in idle mode (e.g., Figure 4 As shown) can be the same as the logic described above for small IoT data.
[0116] Fig.19A control plane based user data transmission method 1900 according to an illustrative embodiment is shown. As shown, at step 1902, the method includes determining the size of user data to be transmitted between a user device (e.g., UE 302) and a data network (e.g., data network 314). At step 1904, in response to determining that the size of the user data to be transmitted is at least below a small data transmission threshold, a control plane message is generated. The generated control plane message includes the user data to be transmitted and specifies a specified payload container type reserved for transmitting user data between the user device and at least one network entity (e.g., AMF 308) of a communication system that couples the user device to the data network via a control plane. At step 1906, the generated control plane message is transmitted between the user device and at least one network entity of the communication system.
[0117] The method 1900 may be performed by a user equipment, which may be part of an IoT device.
[0118] If the user equipment is in idle mode, the generated control plane message may include a control plane service request message with a control plane service type set to indicate that the user equipment initiated the request, and step 1906 may include transmitting the generated control plane message from the user equipment to at least one network entity of the communication system. Method 1900 may also include applying transport protection to the generated control plane message, the transport protection including providing one or more IEs including user data content of a specified payload container type in a separate NAS message container, and applying encryption to the separate NAS message container using a NAS security context of the user equipment. The one or more IEs provided in the separate NAS message container may include at least one of a payload container type IE, a payload container IE, a PDU session identifier IE, a PDU session status IE, an uplink status IE, and a release assistance indication IE.
[0119] If the user equipment is in connected mode, the generated control plane message may include an uplink NAS data transfer message, and step 1906 may include transmitting the generated control plane message from the user equipment to at least one network entity of the communication system. Alternatively, in the case where the user equipment is in connected mode, the generated control plane message includes a downlink NAS data transfer message, and step 1906 includes transmitting the generated control plane message from at least one network entity of the communication system to the user equipment.
[0120] Step 1904 may include generating a payload container type information element, the information element including a payload container information element identifier associated with a specified payload container type, an indication of a length of user data to be transmitted, a PDU session identifier, a publication assistance indication specifying when at least one network entity of the communication system should issue a NAS signaling connection (e.g., an RRC connection) to transmit user data between the at least one network entity and the user equipment, and the user data to be transmitted. The publication assistance indication may include one of: an indication that the NAS signaling connection should be issued after an uplink transmission of the user data in the generated control plane message; and an indication that the NAS signaling connection should be issued after an uplink transmission of the user data in the generated control plane message and after a next downlink transmission to the user equipment.
[0121] Step 1904 may include generating a payload container information element in a first format in response to determining that the size of the user data to be transmitted is below the large data transfer threshold and above the small data transfer threshold, and generating a payload container information element in a second format in response to determining that the size of the user data to be transmitted is below the large data transfer threshold and below the small data transfer threshold. The large data transfer threshold and the small data transfer threshold may be defined in the NAS MO. The payload container information element in the first format includes: a first octet including a payload container information element identifier associated with a specified payload container type; a second octet and a third octet including an indication of the length of the user data to be transmitted; a fourth octet including a PDU session identifier and a release assistance indication; and a plurality of additional octets including the user data to be transmitted. The payload container information element in the second format includes: a first octet including a payload container information element identifier associated with a specified payload container type; a second octet including an indication of the length of the user data to be transmitted; a third octet including a PDU session identifier and a release assistance indication; and one or more additional octets including the user data to be transmitted.
[0122] In response to determining that the size of the user data is at or above the large data transfer threshold, payload data may be transmitted on a user plane between the user equipment and at least one network entity of the communication system.
[0123] The communication system includes a 5G communication system, and the data network includes a PDN. At least one network entity of the communication system may include an AMF of the 5G communication system. Method 1900 may be performed by the AMF. If the user data to be transmitted originates from a user device, the AMF may initiate a data transfer request to the SMF of the 5G communication system to forward it to at least one of the UPF and the NEF of the 5G communication system. The data transfer request forwarded to the UPF or the NEF may include a PFCP message.
[0124] Combination Figures 1 to 19 The specific processing operations and other system functions described in the block diagrams are presented only by way of illustrative examples and should not be construed as limiting the scope of the present disclosure in any way. Alternative embodiments may use other types of processing operations and message passing protocols. For example, in other embodiments, the order of the steps may be changed, or certain steps may be performed at least partially simultaneously with each other rather than continuously. In addition, one or more steps may be repeated periodically, or multiple instances of the method may be performed in parallel with each other.
[0125] Therefore, it should be emphasized again that the various embodiments described herein are presented by way of example only and should not be construed as limiting the scope of the claims. For example, alternative embodiments may utilize communication system configurations, user equipment configurations, base station configurations, authentication and key agreement protocols, key pair provision and use processes, messaging protocols, and message formats that are different from those described above in the context of the illustrative embodiments. These and numerous other optional embodiments that fall within the scope of the appended claims will be apparent to those skilled in the art.
[0126] Example
[0127] The following examples relate to further embodiments:
[0128] Example 1 relates to a device, comprising:
[0129] at least one processor;
[0130] at least one memory, the at least one memory comprising computer program code;
[0131] The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least:
[0132] determining the size of user data to be transmitted from the user device to the data network;
[0133] generating, in response to determining that the size of the user data to be transmitted is at least below a first size threshold, a control plane message including the user data to be transmitted and specifying a specified payload container type reserved for communicating user data via a control plane from the user equipment to at least one network entity of a communication system coupling the user equipment to the data network; and
[0134] The generated control plane message is transmitted from the user equipment to the at least one network entity of the communication system.
[0135] Example 2 relates to the apparatus of Example 1, wherein the apparatus is part of a user equipment.
[0136] Example 3 relates to the apparatus of Example 2, wherein the user equipment is part of an Internet of Things (IoT) device.
[0137] Example 4 relates to the apparatus of Example 2, wherein the user equipment is in an idle mode and the generated control plane message includes a control plane service request message with a control plane service type set to indicate that the user equipment initiates the request.
[0138] Example 5 relates to the device of Example 4, further comprising applying transport protection to the generated control plane message, the transport protection comprising providing one or more information elements including the user data content of the specified payload container type in a separate non-access stratum (NAS) message container, and applying encryption to the separate NAS message container using the NAS security context of the user device.
[0139] Example 6 relates to the device of Example 5, wherein the one or more information elements provided in the separate NAS message container include at least one of a payload container type information element, a payload container information element, a protocol data unit (PDU) session identifier information element, a PDU session status information element, an uplink status information element, and a release assistance indication information element.
[0140] Example 7 relates to the apparatus of Example 2, wherein the user equipment is in connected mode and the generated control plane message comprises an uplink non-access stratum (NAS) data transfer message.
[0141] Example 8 relates to the apparatus of Example 1, wherein generating the control plane message comprises generating a payload container type information element, the payload container type information element comprising:
[0142] a payload container information element identifier associated with the specified payload container type;
[0143] an indication of the length of said user data to be transmitted;
[0144] Protocol Data Unit (PDU) session identifier;
[0145] issuing an auxiliary indication, the issuing auxiliary indication specifying when the at least one network entity of the communication system should issue a non-access stratum (NAS) signaling connection for transmitting the user data between the at least one network entity and the user equipment; and
[0146] The user data to be transmitted.
[0147] Example 9 relates to the apparatus of Example 8, wherein the issuing of the auxiliary indication comprises one of:
[0148] an indication that the NAS signalling connection should be issued following uplink transmission of the user data in the generated control plane message; and
[0149] An indication of the NAS signalling connection shall be issued after uplink transmission of the user data in the generated control plane message and after the next downlink transmission to the user equipment.
[0150] Example 10 relates to the device of Example 1, wherein generating the control plane message comprises:
[0151] In response to determining that the size of the user data to be transmitted is below the first size threshold and above a second size threshold, generating a payload container information element in a first format; and
[0152] In response to determining that the size of the user data to be transmitted is below the first size threshold and above a second size threshold, a payload container information element in a second format is generated.
[0153] Example 11 relates to the apparatus of Example 10, wherein the first size threshold and the second size threshold are defined in a non-access stratum (NAS) management object (MO).
[0154] Example 12 relates to the apparatus of Example 10, wherein the payload container information element in the first format includes:
[0155] a first octet comprising a payload container information element identifier associated with said specified payload container type;
[0156] a second octet and a third octet comprising an indication of the length of said user data to be transmitted;
[0157] a fourth octet comprising a protocol data unit (PDU) session identifier and a release assistance indication; and
[0158] A plurality of additional octets comprising said user data to be transmitted.
[0159] Example 13 relates to the apparatus of Example 10, wherein the payload container information element in the second format comprises:
[0160] a first octet comprising a payload container information element identifier associated with said specified payload container type;
[0161] a second octet comprising an indication of the length of said user data to be transmitted;
[0162] a third octet including a protocol data unit (PDU) session identifier and a release assistance indication; and
[0163] One or more additional octets comprising said user data to be transmitted.
[0164] Example 14 relates to the device of Example 1, wherein the at least one memory and the computer program code are further configured to, together with the at least one processor, cause the device to transmit the payload data on a user plane between the user equipment and the at least one network entity of the communication system in response to determining that the size of the user data is at or above the first size threshold.
[0165] Example 15 relates to the apparatus of Example 1, wherein the communication system comprises a 5G communication system and the data network comprises a packet data network (PDN).
[0166] Example 16 relates to the apparatus of Example 15, wherein the at least one network entity of the communication system includes an access and mobility management function (AMF) of the 5G communication system.
[0167] Example 17 relates to a method comprising:
[0168] determining the size of user data to be transmitted from the user device to the data network;
[0169] responsive to determining that the size of the user data to be transmitted is at least below a first size threshold, generating a control plane message, the control plane message including the user data to be transmitted and specifying a specified payload container type reserved for communicating user data via a control plane from the user equipment to at least one network entity of a communication system coupling the user equipment to the data network; and
[0170] The generated control plane message is transmitted from the user equipment to the at least one network entity of the communication system.
[0171] Example 18 relates to an article of manufacture, the article comprising a non-transitory computer-readable storage medium having executable program code embodied therein, the executable program code, when executed by a processor operatively coupled to the computer-readable storage medium, causing the processor to perform the following steps:
[0172] determining the size of user data to be transmitted from the user device to the data network;
[0173] responsive to determining that the size of the user data to be transmitted is at least below a first size threshold, generating a control plane message, the control plane message including the user data to be transmitted and specifying a specified payload container type reserved for communicating user data via a control plane from the user equipment to at least one network entity of a communication system coupling the user equipment to the data network; and
[0174] The generated control plane message is transmitted from the user equipment to the at least one network entity of the communication system.
[0175] Example 19 relates to a device, comprising:
[0176] at least one processor;
[0177] at least one memory, the at least one memory comprising computer program code;
[0178] The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least:
[0179] determining the size of user data to be transferred from the data network to the user device;
[0180] generating, in response to determining that the size of the user data to be transmitted is at least below a first size threshold, a control plane message, the control plane message including the user data to be transmitted and specifying a specified payload container type reserved for communicating user data to the user equipment via a control plane from at least one network entity of a communication system coupling the user equipment to the data network; and
[0181] The generated control plane message is transmitted from the at least one network entity of the communication system to the user equipment.
[0182] Example 20 relates to the apparatus of Example 19, wherein the user equipment is in a connected mode and the generated control plane message comprises a downlink non-access stratum (NAS) data transfer message.
[0183] Example 21 relates to the apparatus of Example 19, wherein the communication system comprises a 5G communication system and the data network comprises a packet data network (PDN).
[0184] Example 22 relates to the apparatus of Example 21, wherein the at least one network entity of the communication system includes an access and mobility management function (AMF) of the 5G communication system.
[0185] Example 23 relates to the device of Example 22, wherein the device provides the AMF of the 5G communication system.
[0186] Example 24 relates to the device of Example 23, wherein the at least one memory and the computer program code are further configured to, together with the at least one processor, cause the device to initiate a data transfer request from the AMF of the 5G communication system to a session management function (SMF) for forwarding to at least one of a user plane function (UPF) and a network open function (NEF) of the 5G communication system.
[0187] Example 25 relates to the apparatus of Example 24, wherein the data transfer request forwarded to the at least one of the UPF and the NEF comprises a Packet Forwarding Control Protocol (PFCP) message.
[0188] Example 26 relates to a method comprising:
[0189] determining the size of user data to be transferred from the data network to the user device;
[0190] generating, in response to determining that the size of the user data to be transmitted is at least below a first size threshold, a control plane message, the control plane message including the user data to be transmitted and specifying a specified payload container type reserved for communicating user data to the user equipment via a control plane from at least one network entity of a communication system coupling the user equipment to the data network; and
[0191] The generated control plane message is transmitted from the at least one network entity of the communication system to the user equipment.
[0192] Example 27 relates to an article of manufacture, the article comprising a non-transitory computer-readable storage medium having executable program code embodied therein, the executable program code, when executed by a processor operatively coupled to the computer-readable storage medium, causing the processor to perform the following steps:
[0193] determining the size of user data to be transferred from the data network to the user device;
[0194] generating, in response to determining that the size of the user data to be transmitted is at least below a first size threshold, a control plane message, the control plane message including the user data to be transmitted and specifying a specified payload container type reserved for communicating user data to the user equipment via a control plane from at least one network entity of a communication system coupling the user equipment to the data network; and
[0195] The generated control plane message is transmitted from the at least one network entity of the communication system to the user equipment.
Claims
1. A user equipment, comprising: at least one processor; at least one memory, the at least one memory comprising program code; The at least one memory and the program code are configured to, together with the at least one processor, cause the user equipment to at least perform operations, the operations comprising: determining a size of user data to be transmitted from the user equipment to at least one network entity of a communication system, wherein the user equipment is in an idle mode; generating a control plane message based on the determination, wherein based on the size of the user data to be transmitted being at or below a threshold of 254 octets, the control plane message includes the user data to be transmitted in a small data container information element, one octet of which includes an indication of a length of the user data to be transmitted; and wherein based on the size of the user data being above the threshold of 254 octets and below a maximum size, the control plane message comprises the user data to be transmitted in a user data container information element, wherein two octets comprise the indication of the length of the user data to be transmitted; and The control plane message is transmitted from the user equipment to the at least one network entity of the communication system over a control plane, wherein the control plane message comprises a control plane service request message in which a control plane service type is set to indicate a mobile originated request.
2. The user equipment of claim 1, wherein transmitting the control plane message from the user equipment to the at least one network entity of the communication system to transmit the user data is via the at least one network entity to a data network.
3. The user equipment of claim 1, wherein the user equipment is part of an Internet of Things (IoT) device.
4. The user equipment of claim 1 , the operations further comprising applying transport protection to one or more non-plaintext information elements of the control plane message, the applying the transport protection comprising providing the one or more non-plaintext information elements including the user data in a separate non-access stratum (NAS) message container, and applying encryption to a value portion of the separate NAS message container using a NAS security context of the user equipment.
5. The user equipment of claim 4, wherein the one or more non-plaintext information elements provided in the separate NAS message container include at least one of a payload container type information element, a payload container information element, a protocol data unit (PDU) session identifier information element, a PDU session status information element, an uplink status information element, and a publication assistance indication information element.
6. The user equipment of claim 1, wherein the generating the control plane message comprises generating a payload container type information element, the payload container type information element comprising: a payload container information element identifier associated with the small data container; said indication of said length of said user data to be transmitted; Protocol Data Unit (PDU) session identifier; issuing an auxiliary indication, the issuing auxiliary indication specifying when the at least one network entity of the communication system should issue a non-access stratum (NAS) signaling connection for transmitting the user data between the at least one network entity and the user equipment; as well as The user data to be transmitted.
7. The user equipment of claim 9, wherein the issuing assistance indication comprises one of the following: an indication that the NAS signalling connection should be issued following uplink transmission of the user data in the control plane message; and An indication of the NAS signalling connection shall be issued after uplink transmission of the user data in the control plane message and after the next downlink transmission to the user equipment.
8. The user device of claim 1, wherein the user data container information element is a "CIoT user data container", and wherein the small data container information element is a "CIoT small data container" information element.
9. The user equipment of claim 1, wherein the maximum size and the threshold of 254 octets are defined in a Non-Access Stratum (NAS) Management Object (MO).
10. The user equipment of claim 1, wherein the user data container information element comprises one or more of the following: a first octet comprising a payload container information element identifier associated with said large data container; a second octet and a third octet comprising said two octets of said indication of said length of said user data to be transmitted; a fourth octet, which includes a protocol data unit (PDU) session identifier and a release assistance indication; as well as A plurality of additional octets comprising said user data to be transmitted.
11. The user equipment according to claim 1, wherein the small data container information element comprises: a first octet comprising a payload container information element identifier associated with said small data container; a second octet comprising said one octet comprising said indication of said length of said user data to be transmitted; a third octet including a protocol data unit (PDU) session identifier and a release assistance indication; as well as One or more additional octets comprising said user data to be transmitted.
12. The user equipment of claim 1, wherein the communication system comprises a 5G communication system, and the data network comprises a packet data network (PDN).
13. The user equipment of claim 12, wherein the at least one network entity of the communication system comprises an access and mobility management function (AMF) of the 5G communication system.
14. The user equipment of claim 1, wherein the transmitting the control plane message comprises starting a retransmission timer and entering a state "5GMM-SERVICE-REQUEST-INITIATED".
15. A method comprising: determining a size of user data to be transmitted from a user equipment to at least one network entity of a communication system, wherein the user equipment is in an idle mode; generating a control plane message based on the determination, wherein in case the size of the user data to be transmitted is at or below a threshold of 254 octets, the control plane message comprises the user data to be transmitted in a small data container information element, one octet of which comprises an indication of the length of the user data to be transmitted; and wherein in case said size of said user data is above said threshold of 254 octets and below a maximum size, said control plane message comprises said user data to be transmitted in a user data container information element, wherein two octets comprise said indication of said length of said user data to be transmitted; and The control plane message is transmitted from the user equipment to the at least one network entity of the communication system over a control plane, wherein the control plane message comprises a control plane service request message in which a control plane service type is set to indicate a mobile originated request.
16. A computer program product comprising a non-transitory computer readable storage medium having program code embodied therein, the program code, when executed by a processor operatively coupled to the computer readable storage medium, causing the processor to perform the following steps: determining a size of user data to be transmitted from a user equipment to at least one network entity of a communication system, wherein the user equipment is in an idle mode; generating a control plane message based on the determination, wherein based on the size of the user data to be transmitted being at or below a threshold of 254 octets, the control plane message including the user data to be transmitted in a small data container information element, wherein one octet includes an indication of a length of the user data to be transmitted; and based on the size of the user data being above the threshold of 254 octets and below a maximum size, the control plane message including the user data to be transmitted in a user data container information element, wherein two octets comprise the indication of the length of the user data to be transmitted; and The control plane message is transmitted from the user equipment to the at least one network entity of the communication system via a control plane, wherein the generated control plane message comprises a control plane service request message in which a control plane service type is set to indicate a mobile originated request.
Citation Information
Patent Citations
Systems and methods for regulating user data traffic in a wireless network
CN107925908A
Small data transmission techniques in a wireless communication network
US20130083726A1
METHOD AND APPARATUS FOR CIoT DEVICE DATA TRANSFER
US20190037441A1
Control plane based small data service
US20190090123A1
Expedited release of a user equipment
US20190200414A1
