RU2788399C1 - Transmission of user data through the control plane in the communication system using designated types of payload containers - Google Patents

Abstract

FIELD: communication technology.

SUBSTANCE: invention relates to the field of communication systems, in particular, to communications in the control plane in such systems. The size of user data to be transmitted through the control plane between the user equipment and at least one network object of the communication system is determined. In this case, a control plane message containing user data to be transmitted in a small data container is generated for transmitting user data through the control plane in response to determining that the size of user data to be transmitted is below at least the threshold value for transmitting small data. The method also includes the transmission of the generated control plane message between the user equipment and at least one network object of the communication system.

EFFECT: providing the possibility of transmitting user data through the control plane in the communication system.

18 cl, 19 dwg

Description

The art relates generally to communication systems, and in particular, but not exclusively, to control plane communications in such systems.

BACKGROUND OF THE INVENTION

This section presents aspects that may contribute to a better understanding of these inventions. Accordingly, the statements made in this section are to be read in that light and should not be understood as statements about what is and what is not in the prior art.

Fourth generation (4G) mobile wireless technology, also known as Long Term Evolution (LTE), has been developed to provide high-capacity, high-speed mobile multimedia communication, particularly for human interaction. . The next or fifth generation (5G) technology is intended to be used not only for human interaction, but also for machine-type communications in so-called Internet of Things (IoT; Internet of Things) networks.

While 5G networks are designed to provide mass IoT services (for example, a very large number of devices with limited bandwidth) and mission-critical IoT services (for example, those requiring high reliability), improvements over existing mobile services are supported in the form of enhanced mobile broadband services. access (eMBB; enhanced mobile broadband), providing mobile devices with improved wireless access to the Internet.

In the exemplary communication system, a user equipment (5G UE (user equipment) in a 5G network or, more broadly, a UE) such as a mobile communication terminal (subscriber) communicates via an air interface with a base station or access point called gNB in 5G network. By way of illustration, an access point (eg, gNB) is part of an access network of a communication system. For example, in a 5G network, the access network is called a 5G system and is described in the Technical Specification (TS; Technical Specification) 5G 23.501, V16.0.2, entitled "Technical Specification Group Services and System Aspects; System Architecture for the 5G System, the description of which is incorporated herein by reference in its entirety. Typically, an access point (eg, gNB) provides UE access to a core network (CN; core network), which then provides UE access to other UEs and/or a data network such as a packet data network (eg, Internet).

TS 23.501 defines a 5G Service-Based Architecture (SBA) that models services as network functions (NF; network functions) that interact with each other using representative view state passing APIs (view state passing applications). ).

In addition, Technical Standard (TS) 5G 33.501, V15.4.0, titled “Technical Specification Group Services and System Aspects; Security Architecture and Procedures for the 5G System”, the description of which is incorporated herein by reference in its entirety, provides additional detailed description of security management in connection with the 5G network.

Network performance is an important factor in any communication system. Network performance can be significantly affected, for example, by the processing of control plane messages received by the core network from user equipment. However, managing such links presents some challenges in current 5G approaches.

SUMMARY OF THE INVENTION

Exemplary embodiments provide improved methods for transmitting user data across a control plane in a communications system using designated payload container types.

For example, in one illustrative embodiment, the method includes determining the size of user data to be transmitted across the control plane from the user equipment to at least one network entity of the communication system. In response to determining that the size of the user data to be transmitted is below at least a small data transmission threshold, the method also includes generating a control plane message containing the user data to be transmitted in a payload container to be transmitted. small user data through the control plane, hereinafter referred to as the 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.

In another illustrative embodiment, the method includes determining the size of user data to be transmitted from at least one network entity of the communication system via the control plane to the user equipment. In response to determining that the size of the user data to be transmitted is below at least a small data transmission threshold, the method also includes generating a control plane message containing the user data to be transmitted in the small data container. In addition, the method includes transmitting the generated control plane message to the user equipment from at least one network entity of the communication system.

Other illustrative embodiments are provided in a non-volatile computer-readable storage medium that implements executable program code that, when executed by a processor, causes the processor to perform the above steps. Yet other exemplary embodiments include an apparatus with a processor and storage device configured to perform the above steps.

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

In FIG. 1 illustrates a communication system with which one or more exemplary embodiments are implemented.

In FIG. 2 illustrates processing system architectures for user equipment and a network entity that implement one or more exemplary embodiments.

In FIG. 3 illustrates a portion of a communications system that implements one or more exemplary embodiments in which user equipment transmits data via a control plane to a data network.

In FIG. 4 illustrates uplink small data transmission for idle mode user equipment in accordance with one exemplary embodiment.

In FIG. 5 illustrates uplink small data transmission for user equipment in connected mode, in accordance with one exemplary embodiment.

In FIG. 6 illustrates downlink small data transmission for user equipment in accordance with one exemplary embodiment.

In FIG. 7 illustrates the structure of a small data container information element in accordance with one exemplary embodiment.

In FIG. 8 illustrates the contents of a small data container in accordance with one exemplary embodiment.

In FIG. 9 illustrates the contents of a small data container information element in accordance with one exemplary embodiment.

In FIG. 10 illustrates the structure of a user data container information element in accordance with one exemplary embodiment.

In FIG. 11 illustrates the contents of a user data container according to one exemplary embodiment.

In FIG. 12 illustrates the contents of a user data container information element in accordance with one exemplary embodiment.

In FIG. 13 illustrates the use of a message and information element for small data containers in accordance with one illustrative embodiment.

In FIG. 14 illustrates the payload container information element structure according to one exemplary embodiment.

In FIG. 15 illustrates the structure of a payload container type information element in accordance with one exemplary embodiment.

In FIG. 16 illustrates the contents of a payload container information element in accordance with one exemplary embodiment.

In FIG. 17 illustrates a control plane data size configuration according to one exemplary embodiment.

In FIG. 18 illustrates data protection for small data containers for idle user equipment in accordance with one exemplary embodiment.

In FIG. 19 illustrates a control plane based user data transmission methodology using assigned payload container types, in accordance with one exemplary embodiment.

DETAILED DESCRIPTION OF THE INVENTION

Embodiments will be illustrated herein along with exemplary communication systems and related technologies for transmitting user data across a control plane in a communication system using designated payload container types. However, it should be understood that the scope of the claims is not limited to the specific types of communication systems and/or processes disclosed. Embodiments may be implemented in many other types of communication systems using alternative processes and operations. For example, although the disclosed embodiments are illustrated in the context of cellular wireless systems using system elements from 3GPP, such as 3GPP's next generation (5G) system, the disclosed embodiments can be easily adapted to many other types of communication systems. It should be noted that 3GPP stands for 3rd Generation Partnership Project, which is a standards organization that develops protocols for mobile telephony and the like.

In accordance with exemplary embodiments implemented in a 5G communication system environment, one or more technical specifications (TS; technical specification) and technical reports (TR; technical report) from 3GPP provide additional explanation of user equipment and network entities (e.g., network elements, network functions, etc.) and/or operations that interact with one or more exemplary embodiments, such as the aforementioned 3GPP TS 23.501 and 3GPP TS 33.501. Other TS/TRs from 3GPP provide other detailed exemplary information that is understandable to those of ordinary skill in the art. For example, 5G Technical Specification (TS) 23.401, V16.2.0, titled “Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) Enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Access, the disclosure of which is incorporated herein by reference in its entirety, describes the general principles of Cellular IoT (CIoT; Cellular IoT) optimization, an optimization with which one or more illustrative embodiments will be described below. However, while the exemplary embodiments are well suited to implementation related to the aforementioned 5G-related 3GPP standards, alternative embodiments are not necessarily intended to be limited to any particular standards.

In addition, exemplary embodiments may be explained herein in the context of an Open Systems Interconnection (OSI) model, which is a model that conceptually characterizes the communication functions of a communication system such as, for example, a 5G network. The OSI model is usually conceptualized as a hierarchical stack with a given layer serving the layer above and being served by the layer below. Typically, the OSI model contains seven layers, with the top layer of the stack being 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), data link layer (layer 2) and physical layer (layer 1). The person skilled in the art will understand the functions and interactions of the various layers, and therefore, additional details of each layer are not described in this document. However, it should be appreciated that while the exemplary embodiments are well suited to implementations that use the OSI model, alternative embodiments are not necessarily limited to any particular communication function model.

Exemplary embodiments relate to control plane message management associated with Service Oriented Architecture (SBA) for 5G networks. Before describing such exemplary embodiments, a general description of the major components of a 5G network will be described below in the context of FIG. 1 and 2.

In FIG. 1 shows a communication system 100 in which exemplary embodiments are implemented. It should be understood that the elements shown in the communication system 100 are intended to represent the main functions provided in the system, such as UE access functions, mobility management functions, authentication functions, serving gateway functions, etc. Thus, the blocks shown in FIG. . 1 refer to specific elements in 5G networks that provide these basic functions. However, other network elements may be used in other embodiments to implement some or all of the core functions presented. It should also be understood that not all 5G network functions are depicted in FIG. 1. Rather, functions are presented that facilitate the explanation of exemplary embodiments. The following figures may show some additional elements/functions.

Accordingly, as shown, communication system 100 includes user equipment (UE) 102 that communicates via air interface 103 with access point (gNB) 104. UE 102 in some embodiments is a mobile communication terminal, and such mobile communication terminal may comprise, for example , mobile phone, computer or any other type of communication device. Therefore, the term "user equipment" as used herein is intended to be interpreted broadly to encompass many different types of mobile communication terminals, user terminals, or, more generally, communication devices, including examples such as a combination of data cards, inserted into a laptop or other equipment such as a smartphone or other cellular device. In one or more illustrative embodiments, the user equipment is related to an IoT device, and more specifically, supports CIoT optimization as mentioned above and as will be further explained herein. In such embodiments where the UE is an IoT device, non-limiting examples of such devices may include sensors, monitors, actuators, robotic devices, and/or other machine devices. Such communication devices are also intended to include devices commonly referred to as access terminals.

In one embodiment, the UE 102 consists of a Universal Integrated Circuit Card (UICC) part and a Mobile Equipment (ME) part. The UICC is an autonomous part of the UE and contains at least one Universal Subscriber Identity Module (USIM) and associated application software. USIM securely stores a persistent subscriber ID and associated key, which are used to identify and authenticate subscribers to access networks. ME is an autonomous part of the UE and contains the functions of terminal equipment (TE; terminal equipment) and various functions of mobile subscriber equipment (MT; mobile termination).

It should be noted that in one example, the Permanent Subscriber Identity is the International Mobile Subscriber Identity (IMSI) of the UE. In one embodiment, the IMS has a fixed 15-character length and consists of a 3-character Mobile Country Code (MCC), a 3-character Mobile Network Code (MNC), and a 9-character identification number. mobile communication terminal (MSIN; Mobile Station Identification Number). In the 5G communication system, the IMSI is called the Subscription Permanent Identifier (SUPI). In the case of using the IMSI as the SUPI, the MSIN provides the subscriber ID. Thus, only the MSIN portion of the IMSI is usually required to be encrypted. The MNC and MCC parts of the IMSI provide the routing information used by the serving network to route to the correct home network. When the SUPI MSIN is encrypted, it is called a Subscription Concealed Identifier (SUCI).

By way of illustration, the access point 104 is part of the access network of the communication system 100. Such an access network comprises, for example, a 5G system comprising a plurality of base stations and one or more associated radio network control functions. Base stations and radio network control functions are logically separate entities in some embodiments, while in other embodiments they are implemented in the same physical network element such as, for example, a base station router or a cellular access point.

The access point 104 in this illustrative embodiment is operatively linked to the mobility management functions 106 . In the 5G network, the mobility management function is implemented using the Access and Mobility Management Function (AMF). The Security Anchor Function (SEAF) in some embodiments is also implemented with an AMF connecting the UE to the mobility management function. The mobility management function used herein is an element or function (i.e., entity) in the core network (CN) part of a communication system that manages or otherwise deals with, among other network operations, access and mobility (including authentication/ authorization) operations with the UE (via the access point 104). An AMF may also be referred to more generally herein as an Access and Mobility Control Entity.

Although exemplary embodiments will be described below in terms of control plane communication between UEs and AMFs in a 5G system environment, it should be understood that the control plane message management techniques described herein can be directly applied to communication systems other than 5G systems only in as an example, LTE or other 3GPP systems, as well as any relevant non-3GPP systems. By way of example only, in an alternative embodiment in which the communication system is an LTE system, the mobility management function is performed by a mobility management node (MME; Security Anchor Function).

Again in accordance with FIG. 1, the AMF 106 in this exemplary embodiment is operatively linked to base station subscriber functions 108, that is, one or more functions that reside in the subscriber's home network. As shown, some of these functions include a Unified Data Management (UDM) function as well as an Authentication Server Function (AUSF). AUSF and UDM (separately or jointly) are also referred to herein more generally as an authentication entity. In addition, base station subscriber functions include, but are not limited to, Network Slice Selection Function (NSSF), Network Exposure Function (NEF), Network Repository Function (NRF) and policy control function (PCF; Policy Control Function).

It should be noted that a UE such as UE 102 is generally referred to as a Home Public Land Mobile Network (HPLMN) in which some or all of the base station subscriber functions 108 reside. If the UE is roaming (not in the HPLMN), it is typically connected to a visited public land mobile network (VPLMN; Visited Public Land Mobile Network), also called a visited or serving network. Some or all of the mobility management functions 106 may reside in the VPLMN, in which case the functions in the VPLMN are associated with the functions in the HPLMN as needed. However, in a non-roaming scenario, the mobility management functions 106 and the base station subscriber functions 108 may be in the same communication network.

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 the network packet data, such as the Internet 114. As is known in 5G and other communication networks, the user plane (UP; user plane) or data plane, as a rule, transmits network user traffic (user data), and the control plane (CP; control plane ) typically carries control traffic (control data). SMF 110 supports functionality related to UP subscriber sessions, such as establishing, changing, and releasing PDU sessions. UPF 112 supports functionality to facilitate UP operations such as packet routing and forwarding, data network interconnection (eg, 114 in FIG. 1), policy enforcement, and data buffering.

It should be understood that FIG. 1 is a simplified illustration because not all communication channels and connections between network functions (NF) and other system elements are illustrated in FIG. 1. Those skilled in the art, given the various TS/TRs from 3GPP, will understand various channels and connections that are not explicitly shown or that can be summarized in FIG. 1.

Other typical activities and functions of certain network elements are not described in detail herein when they are not the focus of illustrative embodiments, but they may be found in the relevant 5G documentation from 3GPP. It should be understood that the particular arrangement of the system elements in FIG. 1 is only an example, and other types and arrangements of additional or alternative elements may be used to implement the communication system in other embodiments. For example, in other embodiments, system 100 may include other elements/functions not explicitly shown herein. Also, although in the embodiment of FIG. 1 shows only individual elements/functions, this is done only for simplicity and clarity of illustration. This alternative embodiment may include more of these system elements, as well as additional or alternative elements of the type typically associated with conventional system implementations.

It should also be noted that although FIG. 1 system elements are illustrated as separate functional blocks, the various subnetworks that make up the 5G network are divided into so-called network segments. Network segments (network partitions) contain a series of network function (NF; network function) sets (ie functional chains) for each respective service type using network function virtualization (NFV; network function virtualization) in a common physical infrastructure. Network segment instances are created as needed for a given service, such as eMBB service, IoT bulk service, and critical IoT service. Thus, a segment or network function is instantiated when that segment or network function is instantiated. In some embodiments, this includes installing or otherwise executing a network segment 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 may also access the services of other NFs.

Exemplary embodiments provide improved methods for transmitting user data across the control plane of a communication system, particularly including CIoT optimization. In FIG. 2 is a block diagram of architectures 200 for handling two subscribers, ie, a user equipment and a network function/element (eg, AMF), in a control plane based user data transfer methodology in an exemplary embodiment. It should be understood that more than two subscribers may be involved in the control plane based user data transmission methodology in accordance with exemplary embodiments. Thus, in FIG. 2 illustrates the processing architectures associated with any two parties that communicate directly and/or indirectly. Therefore, in exemplary embodiments, each subscriber in the control plane based user data transmission methodology is understood to be configured with the processing architecture shown in FIG. 2.

As shown, user equipment 202 includes a processor 212 coupled to memory 216 and interface circuit 210. The processor 212 of the user equipment 202 includes a control plane communication processing module 214, which may be implemented at least in part in software executable by the processor. The processing module 214 performs user data transmission based on the control plane, as well as other operations described in connection with the following figures and otherwise herein. The memory 216 of the user equipment 202 includes a control plane data transmission storage module 218 that stores data generated or otherwise used during control plane based user data transmission and other operations.

As further shown, network function/element 204 includes a processor 222 coupled to memory 226 and interface circuit 220. The processor 222 of the function/network element 204 includes a control plane data transfer processing module 224, which may be implemented at least in part as software executable by the processor 222. The processing module 224 performs user data transfer based on the control plane, as well as other operations described in connection with the following figures and otherwise in this document. The function/network element 204 memory 226 includes a control plane data transmission storage module 228 that stores data generated or otherwise used during control plane based user data transmission and other operations.

The processors 212 and 222 of the respective user equipment 202 and the network function/element 204 may include, for example, microprocessors, application-specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), field programmable gate array (FPGA) processors, digital signals (DSP; digital signal processor) or other types of processing devices or integrated circuits, as well as parts or combinations of such elements. Such integrated circuit devices, as well as parts or combinations thereof, are examples of "circuit" in the context of the use of this term in this document. A wide variety of other hardware arrangements and associated software or firmware may be used in the implementation of these illustrative embodiments.

Memories 216 and 226 of respective user equipment 202 and network function/element 204 may be used to store one or more programs that are executed by respective processors 212 and 222 to implement at least a portion of the functionality described herein. For example, control plane-based user data transfer operations and other functionality described in connection with the following figures and otherwise herein may be implemented in a simple manner using software code executed by processors 212 and 222.

Thus, this one of the memories 216 or 226 may be considered as an example of what is referred to more broadly herein as a computer program product, or more generally as a processor-readable storage medium that contains executable program code implemented in him. Other examples of processor-readable storage media may include disks or other types of magnetic or optical media in any combination. Exemplary embodiments may include commercial products containing such computer program products or other processor-readable storage media.

The storage device 216 or 226 in particular may include, for example, electronic random-access memory (RAM; random-access memory), such as static RAM (SRAM; static RAM), dynamic RAM (DRAM; dynamic RAM), or others. types of volatile or non-volatile electronic storage device. The latter may include, for example, non-volatile storage devices such as flash memory, magnetoresistive RAM (MRAM; magnetic RAM), phase-coded RAM (PC-RAM; phase-change RAM) or ferroelectric RAM (FRAM; ferroelectric RAM) . The term “memory device” as used herein is intended to be interpreted broadly and may additionally or alternatively encompass, for example, read-only memory (ROM), disk storage, or other type of storage device, as well as parts or combinations of such devices.

By way of illustration, the interface circuits 210 and 220 of the respective user equipment 202 and network functions/element 204 comprise transceivers or other communication hardware or firmware that allow related system elements to communicate with each other in the manner described herein.

In FIG. 2, the user equipment 202 is configured to communicate with the network function/element 204 and vice versa through the respective interface circuits 210 and 220. This communication includes sending data by the user equipment 202 to the network function/element 204 and sending the data by the network function/element 204 to the user equipment 202. However, in alternative embodiments, other network elements or other components may be operatively connected between the user equipment 202 and/or the network. function/element 204 as well as to them. The term "data" as used in this document is intended to be interpreted broadly to encompass any type of information that may be sent between control plane message control subscribers, including, but not limited to, messages, access rights, identifiers, keys, indicators, user data, control data, etc.

It should be understood that the particular arrangement of components shown in FIG. 2 is only an example, and numerous alternative configurations are used in other embodiments. For example, any given element/function may be configured to include additional or alternative components and support other communication protocols.

In view of the exemplary architectures above, exemplary embodiments of control plane based user data transfer methodologies will be further described below in the context of IoT connectivity in networks from 3GPP.

The 3GPP has defined a set of technologies to enable IoT connectivity in 3G and 4G deployments, including through the IoT of the Global System for Mobile Communications Extended Coverage (GSM) (EC-GSM-IoT; Extended Coverage Global System for Mobile Communications). IoT), narrowband IoT (NB-IoT; Narrowband IoT) and enhanced machine type communications (eMTC; enhanced Machine Type Communication). NB-IoT and eMTC radio technologies will be used to deploy 5G CIoT.

As mentioned above, general principles for optimizing CIoT are described in the aforementioned TS 23.401 (eg clause 4.10: Introduction of Evolved Packet System (EPS) C-IoT optimization). Two types of communication information transfer optimization are defined. One optimization is based on the transfer of user data in the user plane (UP) and is called EPS CIoT UP optimization. Another optimization, known as EPS CIoT optimization in the control plane (CP), transmits user data or short message service (SMS; Short Message Service) messages through a mobility management element (MME (mobility management element) in LTE or AMF in 5G) by Non-Access Stratum (NAS) encapsulation, reducing the total number of control plane messages when processing short data transfer operations. NAS is a functional layer in the UMTS and LTE wireless telecommunication protocol stacks between the core network and the user equipment. This layer is used to control the establishment of communication sessions and to maintain continuous communication with the user equipment when it is roaming.

When the UE joins the network, the UE includes in the preferred network capability indication the network features that the UE can support and would prefer to use, such as whether CIoT CP EPS optimization is supported or CIoT UP EPS optimization is supported.

When CIoT CP EPS optimization is supported, CIoT UEs can send and receive small data packets via the NAS signaling control plane. There are some advantages when CIoT UEs use the control plane for communication since the control plane is not always busy and has a relatively low packet rate.

A key requirement for IoT devices is battery life. Both Long Term Evolution (LTE) Category M1 (Cat-M1) and NB-IoT are needed to significantly reduce the power consumption of broadband cellular technologies. Battery life can be an important consideration for various low cost sensors and meter-type IoT devices. In NB-IoT, for example, the maximum battery life is expected to be 10 years even under extreme coverage conditions. Ideally, battery life for such IoT devices should last the entire expected life of the device to avoid costly maintenance.

In one exemplary embodiment, a scenario is considered in which a 5G UE 302 transmits user data via a control plane (eg, as shown in dotted line in FIG. 3) to a data network 314 (eg, a Packet Data PDN). Network) such as the Internet) through the N6 interface in a 5G communication system. UE 302 connects to AMF 308 via 3GPP access point 304 and NG radio access network (NG-RAN; NG Radio Access Network) 306 and provides user data via N1 interface. AMF 308 provides user data to SMF 310 via N11 interface, and SMF provides user data to UPF 312 via N4 interface. The UPF 312 provides data to the data network 314 via the N6 interface. In FIG. 3 also illustrates the communication and interfaces between AMF 308 and authentication entity 316, which is assumed to contain AUSF 318, UDM 320, and User Data Repository (UDR) 322. As illustrated, SMF 310 and UDR 322 are also associated with PCF. 324.

The data packet size can significantly affect the battery life of an IoT device. For 5G CIoT, there is a need to support the transmission of infrequent "small" data across the control plane. As described in more detail below, the communication system may be configured to determine the size of "small" data, for example, based on the size of typical messages expected to be sent using a particular type of IoT device in 5G CIoT. User-defined thresholds can be used to determine an appropriate range of sizes for "small" data, as the term is used in this document. When transmitting small data across the control plane, it is important to minimize the overhead associated with said transmission, thereby reducing the power consumption of the IoT device to conserve battery life.

Exemplary embodiments provide efficient methods for transmitting infrequent small data for IoT devices, advantageously extending the battery life of IoT devices. In some embodiments, efficient transmission of infrequent small data is provided through non-access layer (NAS) signaling. To do this, in some embodiments, a dedicated container, referred to herein as a "CIoT small data container", is defined for such small data transmission. The CIoT small data container is considered as a special type of payload container type, and the UE 302 and AMF 308 are configured with procedures for handling the CIoT small data container. In some embodiments, mechanisms are provided to support the small data maximum size configuration along with logic to handle both small data transmission and large data transmission. In this context, the transmission of "large" data refers to the transmission of data that exceeds user-defined thresholds for "small" data, as described above and elsewhere in this document. Additional user-defined thresholds can be used to determine the maximum size for transferring "large" data through the control plane (with even more data being transferred through the user plane).

Techniques are also provided to protect and encrypt the content of data that is transmitted through the control plane.

In FIG. 4 shows an uplink small data transmission procedure 400 for UE 302 in idle mode. UE 302 in idle mode via 3GPP access may have pending uplink user data, and the UE may use 5G system (5GS) services with 5GS CIoT control plane optimization. As a prerequisite, it is assumed that the UE 302 is registered 401 with the AMF 308 to optimize the CIoT control plane (CP-CIoT; CIoT control plane), that the NAS security context 402 is established, and that encryption and integrity protection mechanisms 403 are provided. In addition, it is assumed that UE 302 is in idle mode 404 and has uplink user data to send.

In step 405, the UE 302 sets the control plane service type for the control plane service request message to "mobile-initiated request". In addition, the UE 302 sets the information element type (IE; information element) of the payload container as "CIoT small data container". The UE 302 formats the Protocol Data Unit (PDU) session ID and release assistance information along with the data in the CIoT small data container. In some embodiments, the PDU session ID is 4 bits and the release assistance information is 2 bits. The release assistance information is turned on when the UE 302 is about to inform the network of one of two conditions. The first condition is that after the current uplink data transmission, no further uplink transmission and no further downlink transmission (eg, acknowledgments, responses, etc.) are expected. In other words, the first condition occurs when the upper layers indicate that the communication has ended with the current uplink data transmission. The second condition is that after the current uplink data transmission, only one downlink data transmission is expected and no further uplink data transmission is expected. In other words, the second condition occurs when the upper layers indicate that the data exchange will be completed with the next downlink data transmission. It should be understood that in other embodiments, other conditions or, more generally, different release assistance information may be used. At step 405, the UE 302 also sets the payload container IE as a CIoT small data container.

The UE 302 includes a payload container type and a payload container formatted as described above in the control plane service request message that is sent at step 405. UP (eg, via the uplink data state), such information may be included in the control plane service request message in step 405 as separate IEs. UE 302 then sends a control plane service request message at step 405 to AMF 308 (eg, via NG-RAN 306). UE 302 also starts a retransmission timer (eg, T3517) and transitions to the "5GMM-SERVICE-REQUEST-INITIATED" state.

After receiving the control plane service request message in step 405 with the control plane service type indicating "mobile initiated request", and after completing the 5GS general mobility management (5GMM; 5GS Mobility Management) procedures, the AMF 308 sends a service receive message 409 to the UE 302. If the payload container IE is included in the control plane service request message in step 405 and the payload container type IE is set to "CIoT small data container", and if the payload container IE passes the integrity check, the AMF 308 retrieves the PDU session ID and information release assistance at step 406. The AMF 308 forwards the data content to the SMF 310 at step 407 via an Nsmf_PDUSession_DataTransfer request message at step 408. This request message contains the PDU session data and identifier.

As noted above, the AMF 308 sends a service accept message 409 to the UE 302. The service receive message 409 indicates the state of the PDU session, and then the UE 302 is in connected mode 410. At this point, a Radio Resource Control (RRC) connection 411 is established. If the PDU session state IE is included in the control plane service request message in step 405, or if the AMF 308 needs to synchronize the PDU session state, the AMF 308 includes the PDU session state IE in the service accept message 409 to indicate which session PDUs associated with the access type in service acceptance message 409 are active in AMF 308.

SMF 310 selects UPF 312 (or NEF) to deliver user data from UE 302 based on the configuration at step 412. SMF 310 then generates and sends a PFCP data forwarding (PFCP_data_forwarding) message 413 to UPF 312. PFCP_data_forwarding message 413 is a forward control protocol message Packet Forwarding Control Protocol (PFCP) and contains the tunnel identifier and payload container (e.g., user data) from the control plane service request message in step 405.

If the release assistance indication IE is included in the control plane service request message at step 405 and if the payload container type IE is set to "CIoT small data container", the AMF 308 will act at step 414 based on the condition specified in the release assistance indication. If the release assistance indication indicates that no further uplink or downlink data transmission is expected after uplink data transmission (eg, the first condition described above), AMF 308 releases the RRC connection (eg, NAS signaling connection). If the release assistance indication indicates that only one downlink data transmission is expected after an 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 on subsequent delivery of the next received downlink data transmission to UE 302.

Upon successful completion of the above procedure, UE 302 resets the service request attempt counter, stops timer T3517, and enters the 5GMM-REGISTERED state. The UE 302 also processes an indication from the lower layers that the RRC connection has been released as a successful completion of the procedure. If the PDU session state information element is included in the service accept message 409, then the UE 302 locally releases all those session PDUs that are active on the 3GPP access side of the UE, but are designated as inactive by the AMF 308.

In FIG. 5 shows an uplink small data transmission procedure 500 for UE 302 in connected mode. UE 302 in idle mode via 3GPP access may have pending uplink user data, and the UE may use 5GS services with 5GS CIoT optimization of the control plane. Similarly in FIG. 4, it is assumed that the UE 302 has registered 501 with an AMF 308 for CP-CIoT, that a NAS security context 502 has been established, and that encryption and integrity protection mechanisms 503 are provided. In addition, it is assumed that UE 302 is in connected mode 504 and has uplink user data to send.

In step 505, UE 302 generates an uplink NAS data transfer (UL_NAS_TRANSPORT) message. The UE 302 sets the payload container type IE as "CIoT small data container" and formats the PDU session ID and release assistance information along with the data in the CIoT small data container. Again, the session ID of the PDU may be 4 bits and the release assistance information is 2 bits. The release assistance information is the same as described above with reference to FIG. 4 and is used by the UE 302 to inform the network of a first condition (eg, no further uplink transmission and no further downlink data transmission after the current uplink data transmission) or a second condition (eg, that after the current uplink data transmission, only one downlink data transmission is expected and no further uplink data transmission is expected). It should be understood that in other embodiments, other conditions or, more generally, different release assistance information may be used. The UE 302 also sets the payload container IE as a CIoT small data container.

The UE 302 includes the payload container type and the payload container formatted as described above in the uplink NAS data transfer message at step 505. eg, via the uplink data state), such information may be included in the uplink NAS data transfer message in step 505 as separate IEs. Then, the UE 302 sends an uplink NAS data transfer message in step 505 to the AMF 308.

After receiving the uplink NAS data transfer message in step 505, if the payload container IE is enabled 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 in step 506 retrieves session ID of the PDU and releases the help information. The AMF 308 forwards the data to the SMF 310 associated with the UE in step 507, for example, via an Nsmf_PDUSession_DataTransfer request message 508, similar to the message 408 described above in connection with FIG. four.

If applicable, at step 509, downlink candidate data is provided to UE 302. AMF 308 processes NAS signaling connection release (e.g., RRC release) at step 510 based on the release assistance information that is included in the uplink NAS data transfer message at step 505. If the release assistance indication indicates that no further uplink or downlink data is expected after the uplink data transmission (eg, the first condition described above), AMF 308 releases the RRC connection (eg, NAS signaling connection). If the release assistance indication indicates that only one downlink data transmission is expected after an 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 on subsequent delivery of the next received downlink data transmission to UE 302. The RRC connection is released at step 511 and UE 302 transitions to idle mode at step 512.

The SMF 310 selects the UPF 312 (or NEF) to deliver user data from the UE 302 based on the configuration in step 513. The SMF 310 then generates and sends a PFCP_data_forwarding message 514 to the UPF 312. The PFCP_data_forwarding message 514 is similar to the message described above with respect to the PFCP_data_forwarding message 413.

In FIG. 4 and 5 show mobile-initiated NAS handover procedures 400 and 500 for UE 302 in idle mode and connected mode, respectively. In FIG. 6 shows a network-initiated downlink small data transmission procedure 600 for UE 302 providing CIoT user data via the control plane from AMF 308 to UE 302 in a 5GMM message (eg, via the N6 interface in a 5G system). Similarly to FIG. 4 and 5, it is assumed that the UE 302 has registered 601 with an AMF 308 for CP-CIoT, that a NAS security context 602 has been established, and that encryption and integrity protection mechanisms 603 have been provided. Furthermore, it is assumed that UE 302 is in connected mode 604 and that AMF 308 has downlink user data to be sent to UE 302.

AMF 308 and SMF 310 have an association established between them at block 605, and SMF 310 and UPF 312 have a PFCP association established between them at block 606. UPF 312 provides a PFCP_data_forwarding message to SMF 310 at block 607. This message includes a tunnel identifier and a container payload with user data to be sent to UE 302. SMF 310 generates and sends an Nsmf_PDUSession_DataTransfer Notify message at 608, including the PDU session data and ID.

In step 609, AMF 308 generates and sends a downlink NAS transport message to UE 302. AMF 308 sets the payload container type IE as "CIoT small data container" and formats the session ID of the downlink data PDU for UE 302 in the CIoT small data container. Again, the PDU session ID may be formatted as 4 bits. The AMF 308 includes the payload container type and the payload container formatted as described above in the NAS data transfer message on the downlink. If additional information is needed, such as PDU session state for PDU session synchronization, or indication of CP switch to UP (eg, via uplink data state), such information can be included in the downlink NAS data transfer message as separate IEs.

Upon receiving the downlink NAS data transfer message in step 609, if the payload container IE is enabled, if the payload container type IE is set to "CIoT small data container", and if the payload container IE passes the integrity check, the UE 302 retrieves the session ID PDU and data content from the IE payload container and forwards the data content to the top level application.

In FIG. 7 shows an IE structure 700 of a CIoT small data container. The CIoT small data container IE is used to encapsulate user data transmitted between UE 302 and AMF 308. The CIoT small data container IE is encoded as illustrated in FIG. 7. The CIoT small data container, in some embodiments, is a type 4 information element with a minimum length of 3 octets and a maximum length of 257 octets. Octet 1 includes the IE identifier of the CIoT small data container, and octet 2 includes the length of the contents of the CIoT small data container. Octets 3 to n include the contents of the CIoT small data container. The value of n is 257, which corresponds to a maximum CIoT small data container content length of 255 (for example, 257 minus octet 1 used for the CIoT small data container IEI and octet 2 used to specify the length of the CIoT small data container content). As described in more detail below with reference to FIG. 8, octet 3 is also reserved in some embodiments, so the user data to be transmitted may be up to 254 octets.

In FIG. 8 shows the contents of the CIoT small data container (eg, octets 3 to n in structure 700). Octet 3 contains the session identification of the PDU encoded with 4 bits and the downlink data expected (DDX) encoded with 2 bits. Octet 3 also includes two spare bits. Octets 4 through n include the content of the data. In FIG. 9 shows the contents of a 900 IE of a CIoT small data container, more specifically illustrating examples of the information in octets 3 through n. For example, in FIG. 9 illustrates how PDU session data is encoded with 4 bits and how DDX data is encoded with 2 bits.

The CIoT small data container is assumed to be "small" in size, or limited to a data content of 255 octets, as noted in FIG. 9. The CIoT User Data Container can be used to encapsulate "large" user data that is transmitted between UE 302 and AMF 308, up to 65,531 octets in size. The CIoT user data container IE is encoded as illustrated in FIG. 10-12.

In FIG. 10 shows an IE structure 1000 of a CIoT user data container. The CIoT User Data Container, in some embodiments, 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 IEI of the CIoT User Data Container, and octets 2 and 3 include the length of the contents of the CIoT User Data Container. Octets 4 through n include the contents of the CIoT user data container. 65,531 octets are available to carry user data since there are three overhead octets (e.g., octet 1 including the IEI of the CIoT user data container, and octets 2 and 3 including the length of the contents of the CIoT user data container) plus, as described in more detail below , octet 4 is reserved in some embodiments.

In FIG. 11 shows the contents of the CIoT user data container (for example, octets 4 to n in structure 1000). Octet 4 contains the session identification information of the PDU encoded with 4 bits and the DDX encoded with 2 bits. Octet 4 also includes two spare bits. Octets 5 to n include the content of the data. In FIG. 12 shows the contents of a CIoT user data container IE 1200, more specifically illustrating examples of the information in octets 4 through n. For example, in FIG. 12 illustrates how PDU session data is encoded with 4 bits and how DDX data is encoded with 2 bits.

While in the idle mode or in the connected mode, the UE 302 decides whether to send data via the CIoT user data container or the CIoT small data container, depending on the size of the data to be transmitted, the configured maximum small data size (for example, the CP-CIoT_MaxSmallDataSize parameter, which configured as a NAS Management Object (MO; Management Object) or in an elementary file (EF; Elementary File) of a Universal Subscriber Identity Module (USIM) and a configured maximum data size (for example, CP-CIoT_MaxDataSize configured as a NAS MO or in EF USIM.) In connected mode, the AMF 308 decides whether to send data to the UE 302 via the CIoT User Data Container or the CIoT Small Data Container, depending on the size of the data to be transmitted, the configured maximum small data size, and the configured maximum data size.

More specifically, from the UE 302 side, in deciding whether to use a CIoT user data container or a CIoT small data container, the following algorithm can be used. If the user data size is smaller than the configured maximum small data size (eg, smaller than CP-CIoT_MaxSmallDataSize), the UE 302 sends the data using the CIoT small data container. If the user data size is greater than the configured maximum small data size (eg, greater than CP-CIoT_MaxSmallDataSize) and less than 254 octets, the UE 302 sends the data using the CIoT small data container. If the user data size is greater than 254 octets but less than the configured maximum small data size (eg, less than CP-CIoT_MaxDataSize), the UE 302 sends the data using the CIoT user data container. If the user data size is larger than the configured maximum data size (eg, larger than CP-CIoT_MaxDataSize), UE 302 switches from CP-CIoT optimization to UP-CIoT optimization and sends data using the user plane rather than the control plane via NAS signaling .

On the network side (eg, AMF 308), the following algorithm can be used to decide whether to use a CIoT user data container or a CIoT small data container. If the user data size is less than the configured maximum small data size (eg, less than CP-CIoT_MaxSmallDataSize), the AMF 308 sends the data using the CIoT small data container. If the user data size is greater than the configured maximum small data size (eg, greater than CP-CIoT_MaxSmallDataSize) and less than 254 octets, the AMF 308 sends the data using the CIoT small data container. If the user data size is greater than 254 octets but less than the configured maximum small data size (eg, less than CP-CIoT_MaxDataSize), the UE 308 sends the data using the CIoT user data container. If the user data size is larger than the configured maximum data size (e.g., larger than CP-CIoT_MaxDataSize), the AMF 308 switches from CP-CIoT optimization to UP-CIoT optimization and sends data using the user plane instead of the control plane via NAS signaling .

In FIG. 13 shows the use of messages and IE for CIoT small data containers and CIoT user data containers. Tables 1301, 1302, and 1303 illustrate message content for uplink NAS transport messages (eg, used at step 505 in FIG. 5), downlink NAS transport messages (eg, used at step 609 in FIG. 6), and plane service request messages. controls (eg, used at step 405 in FIG. 4), respectively. The payload container of each of tables 1301, 1302, and 1303 is one of the payload container types shown in table 1304 (eg, one of a CIoT small data container and a CIoT user data container). Tables 1305 and 1306 illustrate the structures of these payload container types. In particular, table 1305 illustrates the structure of a CIoT small data container, and table 1306 illustrates the structure of a CIoT user data container.

The payload container IE is used to carry one or more payloads. When multiple payloads are transmitted, associated information about each payload is also transmitted along with the payload. The IE of the payload container is encoded as shown in FIG. 14. The payload container IE 1400 shown in FIG. 14, in some embodiments, is a type 6 information element with a minimum length of 4 octets and a maximum length of 65,538 octets. The content of the payload container (octet 4 to octet n) has a maximum value of 65,535 octets.

If the payload container type is set to "CIoT small data container" and included in the control plane service request message (eg, used at step 405 in FIG. 4), the content of the payload container is encoded the same as the content of the CIoT small data container IE. , except that the first two octets are not included.

If the payload container type is set to "CIoT small data container" and included in the uplink NAS transport message (eg, used at step 505 in FIG. 5), the content of the payload container is encoded the same as the content of the CIoT small data container IE. , except that the first two octets are not included.

If the payload container type is set to "CIoT small data container" and included in the downlink NAS transport message (eg, used in step 609 in FIG. 6), the contents of the payload container are encoded in the same way as the contents of the CIoT small data container IE. , except that the first two octets are not included.

If the payload container type is set to "CIoT user data container" and included in the uplink NAS transport message (eg, used at step 505 in FIG. 5), the content of the payload container is encoded in the same way as the content of the IE of the CIoT user data container. , except that the first three octets are not included.

If the payload container type is set to "CIoT user data container" and is included in the downlink NAS transport message (e.g., used in step 609 in FIG. 6), the content of the payload container is encoded in the same way as the content of the CIoT user data container IE. , except that the first three octets are not included.

If the payload container type is set to "CIoT User Data Container" and included in the control plane service request message (eg, used in step 405 in FIG. 4), the content of the payload container is encoded the same as the content of the CIoT User Data Container IE. , except that the first three octets are not included.

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 payload type included in the Payload Container IE. In FIG. 15 shows a payload container type IE structure 1500, with bits 1-4 in octet 1 used to provide the payload container type value, and bits 5-8 in octet 1 used to provide the payload container type IE. In FIG. 16 shows the encoding 1600 of the payload container type value in bits 1-4 of IE 1500 octet 1 of the payload container type. As illustrated, 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 in bits 4 3 2 1 as 1 0 0 1.

In FIG. 17 shows a control plane data size configuration 1700. More specifically, the control plane data size configuration 1700 is provided in the MO NAS with a maximum data size setting (eg, CP-CIoT_MaxDataSize) and a maximum small data size setting (eg, CP-CIoT_MaxSmallDataSize).

The CP-CIoTMaxDataSize MO NAS leaf indicates the configured maximum user data size that can be transmitted over the control plane by NAS signaling in the Home Public Land Mobile Network (HPLMN) or equivalent HPLMN (EHPLMN; Equivalent HPLMN) as described in TS 23.122 from 3GPP. The occurrence of this leaf is zero or one, with format int (an integer), access types Get and Replace, and a value in the range 0 to 65531. If not provided, the default value of 65531 octets is used for this leaf. .

The leaf CP-CIoT_MaxSmallDataSize MO NAS indicates the configured maximum size of small data that can be transmitted through the control plane via NAS signaling when it is in HPLMN or EHPLMN. The occurrence of this leaf is zero or one, with format int, access types Get and Replace, and a value in the range 0 to 254. If not provided, the default value of 254 is used for this leaf.

Configuration parameters (e.g., in the MO NAS shown in FIG. 17) can be set by the device's Home Network Operator (HNO) based on the category and pattern of the device (e.g., including typical data size and sending frequency) as well as the size transport block of the physical layer of the device. eMTC Cat-M1 type devices have a transport block size (TBS; Transport Block Size) of the downlink (DL; Transport Block Size) of 1000 bits (for example, 125 octets) and TBS of the uplink (UL; uplink) of 1000 bits (in the version 13 from 3GPP) and 2984 in version 14 from 3GPP. Cat-M2 eMTC type devices have TBS DL of 4008 bits and TBS UL of 2984 for 1.4 megahertz (MHz) and 6968 for 5 MHz. Cat-NB1 NB-IoT type devices have a DL TBS of 860 bits (eg about 110 octets) and a UL TBS of 1000 bits (eg about 125 octets). Cat-NB2 NB-IoT type devices have TBS DL 2536 bits and TBS UL 2536 bits. Thus, a CIoT small data container is sufficient for Cat-NB1 NB-IoT type devices, and it is also suitable for Cat-M1 eMTC type devices. Other device types may require a CIoT User Data Container as it can support up to 65,531 octets of data transfer.

Protection of the small data sent in the control plane service request message in step 405 when the UE 302 is in the idle mode (eg, as in FIG. 4) can be achieved as described below. When UE 302 is in connected mode (eg, as in FIGS. 5 and 6), a secure NAS connection has already been established and no additional small data protection is required.

To reduce the overall message overhead, instead of encrypting the entire message, some embodiments encrypt only the plaintext IEs. After the UE 302 formats the payload container, the UE 302 includes the payload container type IE, payload container IE, and other plaintext IEs in the NAS message container IE, and encrypts the value part of the NAS message container IE using the encryption key from the NAS security context of the UE 302. This is illustrated in exemplary control plane service request message content 1800 shown in FIG. 18. The UE 302 sets the security header type of the control plane service request message in step 405 to "integrity protected", and sends the control plane service request message containing the clear text IE and the NAS message container IE to the network (eg, to the AMF 308).

When the AMF 308 receives an integrity-protected control plane service request message that contains the NAS message container IE, the AMF 308 performs a network-side integrity check. After a successful integrity check, the AMF 308 decrypts the value part of the NAS message container IE and extracts the payload container type IE, payload container IE, and other plain text IEs.

If the control plane service request message fails the network-side integrity check and only non-emergency PDU sessions are established for the UE 302, the AMF 308 sends a service reject message with reason #9 5GMM ("UE ID cannot be obtained by the network") and stores unchanged 5GMM content and 5G NAS security context.

As illustrated in FIG. 18, the clear text IE of the control plane service request message includes: an extended protocol discriminator; security header type; spare semi-octet; key set identifier (ngKSI; ng Key Set Identifier); identifying a control plane service request message; and the control plane service type. The remaining IEs shown in FIG. 18 are plain text IEs including: payload container type; payload container IE; session ID of the PDU; PDU session state; uplink state; release assistance information IE; etc.

If the amount of data to be transferred exceeds the CIoT_MaxSmallDataSize parameter, a larger CIoT user data container is used to buffer user data. The IoT big data transmission handling logic for UE 302 in both idle and connected modes is the same as described above, except that the payload container type IE is set to "CIoT user data container" and the payload container IE is set to load is set as part of the CIoT user data container value. The logic for encrypting IoT big data for UE 302 in idle mode (eg, as in FIG. 4) may be the same as described above for IoT small data.

In FIG. 19 illustrates a methodology 1900 for transmitting user data based on a control plane, in accordance with an exemplary embodiment. As shown, at 1902, the method includes determining the size of user data to be transmitted between the user equipment (eg, UE 302) and a data network (eg, data network 314). In response to determining that the size of user data to be transmitted is below at least a threshold for transmitting small data, a control plane message is generated in step 1904. The generated control plane message contains the user data to be transmitted and specifies the assigned payload container type reserved for transferring user data across the control plane between the user equipment and at least one network entity (e.g., AMF 308) of a communication system connecting the user equipment to data network. At step 1906, the generated control plane message is transmitted between the user equipment and at least one network entity of the communication system.

Methodology 1900 may be performed by user equipment, which may be part of an IoT device.

If the user equipment is idle, the generated control plane message may comprise a control plane service request message with the control plane service type set to indicate a user equipment initiated request, and step 1906 may include transmitting the generated control plane message from the user equipment to the at least one network entity of the communication system. The methodology 1900 may further include applying transfer security to the generated control plane message, wherein transfer security includes providing one or more IEs including user data content of a designated payload container type in a separate NAS message container, and applying encryption to the separate message container. NAS using the user equipment's NAS security context. The one or more IEs provided in a separate NAS message container may include at least one of a Payload Container Type IE, a Payload Container IE, a PDU Session ID IE, a PDU Session Status IE, an Uplink Status IE, and a Help Indication IE. upon release.

If the user equipment is in connected mode, the generated control plane message may include an uplink NAS data transfer message, step 1906 may include transmitting the generated control plane message from the user equipment to at least one communication system network entity. Alternatively, in cases 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 communication system network entity to the user equipment .

Step 1904 may include generating a payload container type information element containing a payload container information element identifier associated with the assigned payload container type, an indication of the length of user data to be transmitted, a PDU session identifier, a release assistance indication determining when at least one network entity of the communication system needs to release a NAS signaling connection (eg, an RRC connection) to transfer user data between at least one network entity and the user equipment, as well as user data to be transferred. The release assistance indication may include one of: an indication that the NAS signaling connection should be released after uplink user data transmission in the generated control plane message; and indicating that the NAS signaling connection is to be released after the uplink user data transmission in the generated control plane message and after the next downlink transmission to the user equipment.

Step 1904 may include generating a first format payload container information element in response to determining that the size of user data to be transmitted is below a threshold for transmitting large data and above a threshold for transmitting small data, and generating a payload container information element. loads of the second format in response to determining that the size of the user data to be transmitted is below the threshold for the transmission of large data and below the threshold for the transmission of small data. The threshold for the transmission of large data and the threshold for the transmission of small data may be defined in the NAS MO. The payload container information element of the first format contains the first octet containing the payload container information element identifier associated with the assigned payload container type, the second and third octets containing an indication of the length of the user data to be transmitted, the fourth octet containing the PDU session identifier and the indication release assistance, and a set of additional octets containing the user data to be transmitted. The payload container information element of the second format contains the first octet containing the payload container information element identifier associated with the assigned payload container type, the second octet containing an indication of the length of the user data to be transmitted, the third octet containing the PDU session identifier and the assistance indication. release, and one or more additional octets containing the user data to be transmitted.

In response to determining that the size of the user data is equal to or greater than the threshold for big data transmission, the payload data may be transmitted across the user plane between the user equipment and at least one communication system network entity.

The communication system contains a 5G communication system, and the data network contains a PDN. At least one communication system network entity may comprise a 5G communication system AMF. Methodology 1900 may be performed by AMF. If the user data to be transmitted originates from the user equipment, the AMF may initiate a data transmission request to the SMF of the 5G communication system to be forwarded to at least one of the UPFs and NEFs of the 5G communication system. A data transfer request forwarded to UPF or NEF may contain a PFCP message.

Specific processing operations and other system functionality described in conjunction with the graphs in FIG. 1-19 are provided by way of illustration only and should not be construed as limiting the scope of the present invention in any way. In alternative embodiments, other types of processing operations and messaging protocols may be used. For example, the order of the steps may be changed in other embodiments, or certain steps may be performed at least partially simultaneously with each other rather than sequentially. In addition, one or more of the steps may be repeated periodically, or several example methods may be performed in parallel with each other.

Therefore, it should be re-emphasized that the various embodiments described herein are presented by way of illustrative example only and should not be construed as limiting the scope of the claims. For example, alternative embodiments may use other communication system configurations, user equipment configurations, base station configurations, authentication and key distribution protocols, key pair provisioning and use processes, messaging protocols, and message formats than those described above in the context of exemplary embodiments. These and numerous other alternative embodiments falling within the scope of the appended claims will be apparent to those skilled in the art.

Examples

Additional embodiments include the following examples:

Example 1 refers to an apparatus containing:

at least one processor;

at least one storage device containing a computer program code;

wherein the at least one storage device and the computer program code are configured, by means of at least one processor, to prescribe to said apparatus at least:

determining the size of user data to be transmitted from the user equipment to the data network;

generating a control plane message containing user data to be transmitted and indicating an assigned payload container type reserved for transmitting user data via the control plane from the user equipment to at least one network entity of the communication system connecting the user equipment to the data network, in response determining that the size of the user data to be transmitted is below at least a first size threshold; and

transmitting the generated control plane message from the user equipment to at least one network entity of the communication system.

Example 2 refers to the apparatus of Example 1, characterized in that the apparatus is part of a user equipment.

Example 3 refers to the apparatus of Example 2, characterized in that the user equipment is part of an Internet of Things (IoT) device.

Example 4 refers to the apparatus of Example 2, wherein the user equipment is in idle mode and the generated control plane message contains a control plane service request message with the control plane service type set to indicate a user equipment initiated request.

Example 5 relates to the apparatus of Example 4 further comprising applying transmission protection to a generated control plane message, wherein transmission protection comprises providing one or more information elements, including user data content of a designated payload container type, in a separate non-access stratum (NAS) message container. ), and applying encryption to a separate NAS message container using the user equipment's NAS security context.

Example 6 relates to the apparatus of Example 5, characterized in that one or more information elements provided in a separate NAS message container contain at least one of a payload container type information element, a payload container information element, a block session identifier information element Protocol Data (PDU), PDU Session Status Information Element, Uplink Status Information Element, and Release Assistance Indication Information Element.

Example 7 refers to the apparatus of Example 2, characterized in that the user equipment is in connected mode and the generated control plane message contains an uplink non-access layer (NAS) data transfer message.

Example 8 refers to the apparatus of Example 1, wherein generating a control plane message includes generating a payload container type information element containing:

payload container information element identifier associated with the assigned payload container type;

an indication of the length of the user data to be transmitted;

protocol data unit (PDU) session identifier;

a release assistance indication indicating when at least one network entity of the communication system is to release a non-access stratum (NAS) signaling connection for transferring user data between the at least one network entity and the user equipment; and

user data to be transferred.

Example 9 refers to the apparatus of example 8, characterized in that the release assistance indication includes one of:

indicating that the NAS signaling connection should be released after uplink user data transmission in the generated control plane message; and

indicating that the NAS signaling connection should be released after the uplink user data transmission in the generated control plane message and after the next downlink transmission to the user equipment.

Example 10 refers to the apparatus of Example 1, wherein generating a control plane message includes:

generating a first format payload container information element in response to determining that the size of the user data to be transmitted is below a first size threshold and above a second size threshold; and

generating a second format payload container information element in response to determining that the size of the user data to be transmitted is below the first size threshold and below the second size threshold.

Example 11 relates to the apparatus of Example 10, characterized in that the first size threshold and the second size threshold are defined in a Non-Access Layer (NAS) Managed Entity (MO).

Example 12 refers to the apparatus of Example 10, characterized in that the payload container information element of the first format contains:

the first octet containing the payload container information element identifier associated with the assigned payload container type;

second and third octets containing an indication of the length of the user data to be transmitted;

a fourth octet containing a protocol data unit (PDU) session identifier and a release assistance indication; and

a collection of additional octets containing the user data to be transmitted.

Example 13 refers to the apparatus of Example 10, characterized in that the payload container information element of the second format contains:

the first octet containing the payload container information element identifier associated with the assigned payload container type;

a second octet containing an indication of the length of the user data to be transmitted;

a third octet containing a protocol data unit (PDU) session identifier and a release assistance indication; and

one or more additional octets containing the user data to be transmitted.

Example 14 relates to the apparatus of Example 1, characterized in that the at least one storage device and the computer program code are further configured, by means of at least one processor, to direct the apparatus, in response to determining that the size of the user data is the first threshold value or higher thereof, the transmission of payload data through the user plane between the user equipment and at least one network entity of the communication system.

Example 15 refers to the apparatus of Example 1, characterized in that the communication system comprises a 5G communication system and the data network comprises a packet data network (PDN).

Example 16 relates to the apparatus of Example 15, characterized in that at least one network entity of the communication system comprises an Access and Mobility Management Function (AMF) of a 5G communication system.

Example 17 relates to a method including:

determining the size of user data to be transmitted from the user equipment to the data network;

generating a control plane message containing user data to be transmitted, and indicating an assigned payload container type reserved for transmitting user data through the control plane from the user equipment to at least one network entity of a communication system connecting the user equipment to the data network, in a response to determining that the size of the user data to be transmitted is below at least a first size threshold; and

transmitting the generated control plane message from the user equipment to at least one network entity of the communication system.

Example 18 relates to an article of manufacture containing a non-volatile computer-readable storage medium containing executable program code embodied therein, which, when executed by a processor operatively connected to the computer-readable storage medium, causes the processor to perform the steps:

determining the size of user data to be transmitted from the user equipment to the data network;

generating a control plane message containing user data to be transmitted, and indicating an assigned payload container type reserved for transmitting user data through the control plane from the user equipment to at least one network entity of the communication system connecting the user equipment to the data network, in a response to determining that the size of the user data to be transmitted is below at least a first size threshold; and

transmitting the generated control plane message from the user equipment to at least one network entity of the communication system.

Example 19 refers to an apparatus containing:

at least one processor;

at least one storage device containing a computer program code;

wherein the at least one storage device and the computer program code are configured, via at least one processor, to cause the apparatus to at least:

determining the size of user data to be transmitted from the data network to the user equipment;

generating a control plane message containing user data to be transmitted, and indicating an assigned payload container type reserved for transmitting user data through the control plane to the user equipment from at least one network entity of the communication system connecting the user equipment to the data network, in a response to determining that the size of the user data to be transmitted is below at least a first size threshold; and

transmitting the generated control plane message to the user equipment from at least one network entity of the communication system.

Example 20 refers to the apparatus of Example 19, characterized in that the user equipment is in connected mode and the generated control plane message contains a downlink non-access layer (NAS) data transfer message.

Example 21 refers to the apparatus of Example 19, characterized in that the communication system comprises a 5G communication system and the data network comprises a packet data network (PDN).

Example 22 relates to the apparatus of Example 21, characterized in that at least one network entity of the communication system comprises an Access and Mobility Management Function (AMF) of a 5G communication system.

Example 23 refers to the apparatus of Example 22, characterized in that the apparatus provides the AMF of a 5G communication system.

Example 24 relates to the apparatus of Example 23, characterized in that the at least one storage device and the computer program code are further configured, via at least one processor, to cause the apparatus to initiate a data transfer request from an AMF to a session management function (SMF). ) a 5G communication system for forwarding to at least one of a user plane function (UPF) and a network impact function (NEF) of a 5G communication system.

Example 25 relates to the apparatus of Example 24, wherein the data transfer request forwarded to at least one of the UPF and NEF contains a Packet Forward Control Protocol (PFCP) message.

Example 26 relates to a method including:

determining the size of user data to be transmitted from the data network to the user equipment;

generating a control plane message containing user data to be transmitted, and indicating an assigned payload container type reserved for transmitting user data through the control plane to the user equipment from at least one network entity of the communication system connecting the user equipment to the data network, in a response to determining that the size of the user data to be transmitted is below at least a first size threshold; and

transmitting the generated control plane message to the user equipment from at least one network entity of the communication system.

Example 27 relates to an article of manufacture containing a non-volatile computer-readable storage medium containing executable program code embodied therein, which, when executed by a processor operatively connected to the computer-readable storage medium, causes the processor to perform the steps:

determining the size of user data to be transmitted from the data network to the user equipment;

generating a control plane message containing user data to be transmitted, and indicating an assigned payload container type reserved for transmitting user data through the control plane to the user equipment from at least one network entity of the communication system connecting the user equipment to the data network, in a response to determining that the size of the user data to be transmitted is below at least a first size threshold; and

transmitting the generated control plane message to the user equipment from at least one network entity of the communication system.

Claims (58)

1. User equipment (202), containing: at least one processor (212); and at least one storage device (216) containing the executable program code; wherein said at least one storage device (216) and said executable program code are configured, by means of said at least one processor (212), to prescribe to said user equipment (202) at least: determining the size of user data to be transmitted through the control plane from said user equipment to at least one network entity of the communication system; generating a control plane message containing said user data to be transmitted in a small data container via said control plane in response to determining that said size of said user data to be transmitted is below at least a threshold value for transmitting small data, wherein the small data threshold is configured to have a value of 254 octets; generating a control plane message containing said user data to be transmitted and indicating a large data container allocated for transmitting large user data through said control plane in response to determining that said size of said user data exceeds said threshold for transmitting small data, and below the threshold for transferring big data; and transmitting said generated control plane message from said user equipment to said at least one network entity of said communication system, whereby generating said control plane message includes: generating a first format payload container information element in response to determining that the specified size of the specified user data to be transmitted is below the specified large data transmission threshold and above the specified small data transmission threshold, wherein the specified payload container information element of the specified first format contains two octets containing an indication of the length of the specified user data to be transmitted, and generating a second format payload container information element in response to determining that the specified size of the specified user data to be transmitted is below the specified large data transmission threshold and below the specified small data transmission threshold, wherein the specified payload container information element of the specified second format contains one octet containing an indication of the length of the specified user data to be transmitted. 2. The user equipment according to claim 1, characterized in that said at least one storage device and said executable program code are configured to transmit said generated control plane message from said user equipment to said at least one network entity of said communication system for transmitting said user data through said at least one network entity to a data network. 3. User equipment according to claim 1, characterized in that said user equipment is part of an Internet of Things (IoT) device. 4. The user equipment of claim 1, wherein said user equipment is in idle mode and said generated control plane message comprises a control plane service request message with the control plane service type set to indicate a user equipment initiated request. 5. The user equipment of claim 4, further comprising applying transmission protection to one or more clear text information elements of said generated control plane message, said transmission protection comprising providing one or more clear text information elements including said user data content of said data container. in a separate non-access stratum (NAS) message container, and applying encryption to said part of the value of the separate NAS message container using the NAS security context of said user equipment. 6. The user equipment of claim 5, wherein said one or more information elements provided in said separate NAS message container comprise at least one of a payload container type information element, a payload container information element, an identifier information element a protocol data unit (PDU) session, a PDU session status information element, an uplink status information element, and a release assistance indication information element. 7. The user equipment of claim 1, wherein said user equipment is in connected mode and said generated control plane message contains an uplink non-access layer (NAS) data transfer message. 8. The user equipment according to claim 1, wherein generating said control plane message includes generating a payload container type information element containing: payload container information element identifier associated with said small data container; indicating the length of said user data to be transmitted; protocol data unit (PDU) session identifier; a release assistance indication indicating when said at least one network entity of said communication system needs to release a Non-Access Layer (NAS) signaling connection to transfer said user data between said at least one network entity and said user equipment; and specified user data to be transferred. 9. User equipment according to claim 8, characterized in that said release assistance indication includes one of: indicating that said NAS signaling connection is to be released after said uplink user data has been transmitted in said generated control plane message; and indicating that the specified NAS signaling connection is to be released after the transmission of the specified uplink user data in the specified generated control plane message and after the next downlink transmission to the specified user equipment. 10. The user equipment of claim 1, wherein said payload container information element of said first format is a "CIoT user data container" and said payload container information element of said second format is a "small container" information element. CIoT data. 11. The user equipment according to claim. 1, characterized in that the specified threshold for transmission of large data and the specified threshold for transmission of small data are defined in the control object (MO) layer without access (NAS). 12. The user equipment of claim 1, wherein said payload container information element of said first format contains one or more of the following: a first octet containing the payload container information element identifier associated with the specified big data container; the specified two octets as the second and third octets; a fourth octet containing the protocol data unit (PDU) session identifier and release assistance indication; and a set of additional octets containing the specified user data to be transmitted. 13. User equipment according to claim. 1, characterized in that the specified information element of the payload container of the specified second format contains: the first octet containing the payload container information element identifier associated with the specified small data container; the specified one octet as the second octet; a third octet containing a protocol data unit (PDU) session identifier and a release assistance indication; and one or more additional octets containing the specified user data to be transmitted. 14. The user equipment according to claim 1, characterized in that said communication system comprises a 5G communication system, and said data communication network comprises a Packet Data Network (PDN). 15. The user equipment according to claim 14, characterized in that said at least one network entity of said communication system contains an access and mobility management function (AMF) of said 5G communication system. 16. User equipment according to claim 1, characterized in that said at least one storage device and said executable program code are additionally configured, using said at least one processor, to prescribe to said user equipment, in response to determining whether that the specified size of the specified user data to be transmitted is up to 254 octets, determining that the specified size of the specified user data to be transmitted is below the specified small data transmission threshold. 17. A method for transmitting user data through a control plane in a communication system, including: determining the size of user data to be transmitted through the control plane from the user equipment to at least one network entity of the communication system; generating a control plane message containing said user data to be transmitted in a small data container via said control plane in response to determining that said size of said user data to be transmitted is below at least a threshold value for transmitting small data, wherein said the small data threshold is configured to have a value of 254 octets; generating a control plane message containing said user data to be transmitted and indicating a big data container dedicated to transmitting large user data through said control plane in response to determining that said size of said user data is above said threshold for transmitting small data, and below the threshold for transferring big data; and transmitting said generated control plane message from said user equipment to said at least one network entity of said communication system, whereby generating said control plane message includes: generating a first format payload container information element in response to determining that the specified size of the specified user data to be transmitted is below the specified large data transmission threshold and above the specified small data transmission threshold, wherein the specified payload container information element of the specified first format contains two octets containing an indication of the length of the specified user data to be transmitted, and generating a second format payload container information element in response to determining that the specified size of the specified user data to be transmitted is below the specified large data transmission threshold and below the specified small data transmission threshold, wherein the specified payload container information element of the specified second format contains one octet containing an indication of the length of the specified user data to be transmitted. 18. A non-volatile computer-readable storage medium containing an executable program code implemented therein, which, when executed by a processor operatively connected to the specified computer-readable storage medium, instructs the specified processor to perform the steps: determining the size of user data to be transmitted through the control plane from the user equipment to at least one network entity of the communication system; generating a control plane message containing the specified user data to be transmitted in the small data container via said control plane in response to determining that said size of said user data to be transmitted is below at least a small data transmission threshold, said small data transmission threshold being configured to have a value of 254 octets; generating a control plane message containing said user data to be transmitted and specifying a big data container dedicated to transmitting large user data through said control plane in response to determining that said size of said user data is above said threshold for transmitting small data, and below the threshold for transferring big data; and transmitting said generated control plane message from said user equipment to said at least one network entity of said communication system, whereby generating said control plane message includes: generating a first format payload container information element in response to determining that the specified size of the specified user data to be transmitted is below the specified large data transmission threshold and above the specified small data transmission threshold, wherein the specified payload container information element of the specified first format contains two octets containing an indication of the length of the specified user data to be transmitted, and generating a second format payload container information element in response to determining that the specified size of the specified user data to be transmitted is below the specified large data transmission threshold and below the specified small data transmission threshold, wherein the specified payload container information element of the specified second format contains one octet containing an indication of the length of the specified user data to be transmitted.

Images