KR20180019584A - Small data transmission in wireless communication systems - Google Patents

Abstract

Techniques are provided for the transmission of small data packets over a paging procedure in the MTC or the Cellular Internet System (CIoT). The core network may receive data to be transmitted to the user equipment (UE) and may determine that a small data packet transmission may be initiated for that data. The core network may format a small data packet into a paging request that includes its data and UE identification indications and send a paging request to the base station. The base station may receive the paging request and initiate a page process with the UE. The UE may receive the page message and initiate an access procedure that may be used for the transmission of small data. The UE may be in idle mode prior to small data transmission and, in some instances, may return to idle mode following transmission of small data.

Description

Small data transmission in wireless communication systems

Cross-references

This patent application is a continuation-in-part of U.S. Patent Application No. 15 / 172,110 entitled " Small Data Transmission in a Wireless Communications System "filed June 2, 2016; And U.S. Provisional Patent Application No. 62 / 182,403, entitled " Small Data Transmission in a Wireless Communications System, "filed June 19, 2015, each of which is assigned to the assignee hereof .

Field of disclosure

The following is generally related to wireless communications and more specifically to the transmission of small data packets in a machine-type-communication (MTC) or cellular internet of things (CIoT) system. will be.

Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and the like. These systems may be multi-access systems capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multi-access systems include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, and Orthogonal Frequency Division Multiple Access For example, a Long Term Evolution (LTE) system.

By way of example, a wireless multiple-access communication system may include multiple base stations that simultaneously support communication for multiple communication devices, which may otherwise be known as user equipment (UE). The base station may communicate with the UEs on the downlink channels (e.g., for transmissions from the base station to the UE) and on uplink channels (e.g., for transmissions from the UE to the base station).

Some UEs may provide automated communication. Automated UEs may include those that implement machine-to-machine (M2M) communications or machine-type communications (MTC). M2M or MTC may refer to data communication technologies that allow devices to communicate with each other or with a base station without human intervention. M2M or MTC devices may include UEs and may be used as part of a cellular internet (CIoT) network. CIoT may refer to low data rate communications with M2M or MTC devices using LTE / LTE-A networks. Some M2M or MTC devices in CIoT may include parking meters, water and gas meters, and other sensors that may communicate relatively infrequently small amounts of data.

In some cases, including in CIoT, the UE may be a power limited device, and a significant amount of power may be used to power the wireless components. However, some MTC devices may transmit or receive relatively small amounts of data in relatively infrequent cases. In these cases, the overhead associated with establishing a radio resource control (RRC) connection may consume a significant amount of resources compared to the resources required to transmit small amounts of data. Increasing power consumption from repeatedly establishing RRC connections for the communication of small amounts of data may reduce the UE ' s battery life and reduce the usability of the device. Also, the network resources used for overhead in establishing RRC connections for transmissions of small amounts of data may reduce the efficiency of the wireless communication system.

The present disclosure relates to improved systems, methods, and / or apparatus for the transmission of small data packets through a paging procedure in a machine-type communications (MTC) or cellular object Internet (CIoT) will be. In some instances, the core network may receive data to be transmitted to a user equipment (UE), such as an MTC device, and may determine that a small data packet transmission may be initiated for that data. The core network may format a small data packet into a paging request containing data and send a paging request to the base station. The base station may receive the paging request and initiate a page process with the UE. The base station may, in some instances, send a page message to the UE indicating that a small data transmission is to be transmitted. The UE may receive the page message and initiate an access procedure that may be used for the transmission of small data. The UE may send a random access request to the base station, for example, in response to a page message, and the base station may transmit data to the UE as part of a random access response message for the UE. The UE may be in an idle mode prior to small data transmissions and, in some instances, may return to idle mode following transmission of a small data packet.

A method of wireless communication is described. The method comprises the steps of receiving a small data packet to be transmitted to the UE, formatting a small data packet into a paging request, wherein the paging request includes a small data packet, Formatting into a paging request, and sending a paging request to one or more base stations.

An apparatus for wireless communication is described. The apparatus comprising: means for receiving a small data packet to be transmitted to the UE; means for formatting a small data packet into a paging request, wherein the paging request includes a small data packet, Means for formatting, and means for sending a paging request to one or more base stations.

Additional devices for wireless communication are described. The apparatus may comprise a processor, a memory in electronic communication with the processor, and instructions stored in memory, the instructions being for receiving a small data packet to be transmitted to the UE and for formatting a small data packet into a paging request, A paging request is performed by the processor to format the small data packet into a paging request, which includes UE identification information and a small data packet, and to send a paging request to one or more base stations.

A non-transient computer readable medium having stored thereon code for wireless communication is disclosed. The code is for receiving a small data packet to be sent to the UE and formatting a small data packet into a paging request wherein the paging request includes formatting the small data packet into a paging request, , And may include executable instructions to send a paging request to one or more base stations.

Some examples of the above-described methods, devices, or non-transitory computer-readable media include, but are not limited to, determining whether a confirmation of the delivery of a small data packet has been received, And retransmitting the paging request to one or more base stations.

In some examples of the above-described methods, devices, or non-transitory computer-readable media, formatting a small data packet into a paging request may include a control plane data encryption key or a control plane data integrity key ), Or both. Additionally or alternatively, in some instances, the paging request may further include header information indicating that the paging request includes a small data packet.

In some examples of the above-described method, apparatus, or non-transitory computer-readable medium, the method is performed by an entity of an evolved packet core. Additionally or alternatively, in some examples, the method is performed by a CIOt serving gateway node (C-SGN).

A method of wireless communication is described. The method includes receiving a paging request associated with a UE from a network node at a base station, the paging request comprising a small data packet for the UE, receiving the paging request, sending a page to the UE, Receiving an access request, and sending a small data packet to the UE in response to the access request.

An apparatus for wireless communication is described. The apparatus comprises means for receiving a paging request associated with a UE from a network node at a base station, the paging request comprising a small data packet for the UE, means for receiving the paging request, means for sending a page to the UE, And means for sending a small data packet to the UE in response to the access request.

Additional devices for wireless communication are described. The apparatus may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory, the instructions being for receiving a paging request associated with the UE from a network node at a base station, To send a page to the UE, to receive an access request from the UE, and to send a small data packet to the UE in response to the access request, It is executable.

A non-transient computer readable medium having stored thereon code for wireless communication is disclosed. The code is for receiving a paging request associated with a UE from a network node at a base station, the paging request comprising receiving a paging request, comprising a small data packet for the UE, sending a page to the UE, Receive access requests, and send small data packets to the UE in response to the access requests.

Some examples of the above-described methods, devices, or non-transitory computer-readable media include receiving an acknowledgment from the UE indicating the correct reception of a small data packet, Lt; RTI ID = 0.0 > network node. ≪ / RTI >

In some examples of the described methods, devices, or non-transitory computer-readable media, transmitting a small data packet to a UE may comprise transmitting a small data packet in a control plane message associated with a signaling radio bearer . Additionally or alternatively, in some examples, the control plane message comprises a message of a random access procedure comprising an access request.

Some examples of methods, apparatus, or non-transitory computer-readable media described above may further comprise, in a random access procedure, receiving an access request message comprising a small data request field. In some examples of the above-described methods, devices, or non-transitory computer-readable media, transmitting includes sending a small data packet to the UE in a connection establishment message in response to the connection request message.

In some examples of the described methods, devices, or non-transitory computer-readable media, the page for the UE includes an indication that a small data packet will be transmitted. Additionally or alternatively, in some examples, the access request is received on a set of physical random access channel (PRACH) resources associated with connectionless transfer of small data packets.

A method of wireless communication is described. The method comprises the steps of: receiving, at the UE, a page from a base station; initiating a random access procedure by sending an access request to the base station in response to the page; prior to activation of a dedicated radio bearer for data connection with the base station Receiving small data packets in a plane message, and acknowledging small data packets.

An apparatus for wireless communication is described. The apparatus comprises means for receiving a page from a base station at a user equipment (UE), means for initiating a random access procedure by sending an access request to a base station in response to a page, means for initiating a dedicated radio bearer Means for receiving a small data packet in a control plane message prior to activation, and means for acknowledging for a small data packet.

Additional devices for wireless communication are described. The apparatus may comprise a processor, a memory in electronic communication with the processor, and instructions stored in the memory, the instructions being for receiving a page from a base station at the UE and transmitting an access request to the base station in response to the page Initiates a random access procedure and is executable by the processor to receive a small data packet in a control plane message and acknowledge a small data packet prior to activation of a dedicated radio bearer for data connection with the base station.

A non-transient computer readable medium having stored thereon code for wireless communication is disclosed. This code initiates the random access procedure by receiving a page from the base station at the UE, sending an access request to the base station in response to the page, and initiating a random access procedure in the control plane message prior to activation of the dedicated radio bearer for data connection with the base station And may include executable instructions to receive small data packets and acknowledge small data packets.

In some examples of the above-described method, apparatus, or non-transitory computer-readable medium, the control plane message is part of a random access procedure. Additionally or alternatively, in some examples, the control plane message is a random access response message of the random access procedure.

Some examples of the above-described methods, devices, or non-transitory computer-readable media may further comprise transmitting, in a connection request message, a small data request field. Additionally or alternatively, in some instances, a small data packet is received in a connection establishment message sent in response to the connection request message.

In some examples of the above-described methods, devices, or non-transitory computer-readable media, an access request is transmitted on a set of physical random access channel (PRACH) resources associated with an unconnected transmission of small data packets.

The foregoing has outlined rather broadly the features and technical advantages of the examples according to this disclosure in order that the following detailed description may be better understood. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples may be readily utilized as a basis for modifying or designing other structures to accomplish the same purposes of this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The features of the concepts disclosed herein, their structure and method of operation, together with their associated advantages, will be better understood from the following description when considered in conjunction with the accompanying drawings. Each of the Figures is provided for purposes of illustration and description only and is not provided as a definition of the limits of the claims.

BRIEF DESCRIPTION OF THE DRAWINGS Embodiments of the disclosure are described with reference to the following drawings.
1 illustrates an example of a wireless communication system that supports small data transmission in a wireless communication system, in accordance with various aspects of the present disclosure.
2 illustrates an example of a wireless communication subsystem that supports small data transmission in a wireless communication system, in accordance with various aspects of the present disclosure.
3 illustrates an example of a wireless communication system that supports small data transmission in a wireless communication system, in accordance with various aspects of the present disclosure.
4 shows an example of a process flow supporting small data transmission in a wireless communication system, in accordance with various aspects of the present disclosure.
5 shows another example of a process flow supporting small data transmission in a wireless communication system, in accordance with various aspects of the present disclosure.
6 shows another example of a process flow supporting small data transmission in a wireless communication system, in accordance with various aspects of the present disclosure.
7 illustrates a block diagram of a device that supports small data transmission in a wireless communication system, in accordance with various aspects of the present disclosure.
8 illustrates a block diagram of a wireless device, such as a base station or other wireless access node, supporting small data transmissions in a wireless communication system, in accordance with various aspects of the present disclosure.
9 shows a block diagram of a system including a base station supporting small data transmission in a wireless communication system, in accordance with various aspects of the present disclosure.
10 shows a block diagram of a wireless device, such as a UE, that supports small data transmission in a wireless communication system, in accordance with various aspects of the present disclosure.
11 shows a block diagram of a system including a UE supporting small data transmission in a wireless communication system, in accordance with various aspects of the present disclosure;
Figures 12-14 illustrate methods for small data transmission in a wireless communication system, in accordance with various aspects of the present disclosure.

The described features relate generally to improved systems, methods, or devices for the transmission of small data packets through a paging procedure in an MTC or cellular Internet system (CIoT). As discussed above, some wireless systems may provide automated communications such as MTC or machine-to-machine (M2M) communications. M2M or MTC may refer to technologies that communicate without human intervention and that may operate on CIoT. In some cases, MTC devices may have limited capabilities. For example, some MTC devices may have broadband capacity while other MTC devices may be limited to narrowband communications. This narrow band limitation may hinder the ability of the MTC device to receive control channel information using, for example, the entire bandwidth served by the base station. In some wireless communication systems, such as Long Term Evolution (LTE), an MTC device with limited bandwidth capability (or other device with similar capabilities) may be referred to as a category 0 device.

As discussed above, in some cases, MTC devices may transmit or receive relatively infrequently relatively small amounts of data. In these cases, the overhead associated with establishing a radio resource control (RRC) connection may consume a significant amount of resources compared to the resources needed to transmit the small amounts of data. Increased power consumption from repeatedly establishing RRC connections for the communication of small amounts of data may reduce the UE ' s battery life and reduce the usability of the device. Also, the network resources used for overhead in establishing RRC connections for the transmission of small amounts of data may reduce the efficiency of the wireless communication system. The various aspects of the present disclosure provide for non-connected transmissions of small data, wherein relatively small amounts of data may be transmitted without establishing an RRC connection, thus allowing the UE to transmit an idle mode To be allowed to remain. These techniques may provide efficient transmission of such small data with reduced overhead and may improve the overall efficiency of the wireless communication system.

Small data transmissions or small data packets, as used in this disclosure, refer to the amount of data that may be transmitted in the payload of a random access message or other connection establishment message. For example, if the maximum random access message payload may include 144 bits, the corresponding small data transmission or small data packet may include 144 bits or fewer. The amount of data that may be included in a small data transmission or small data packet may be limited by the amount of data that may be included in the message payload used for the transmission of that small data transmission or small data packet and the amount of data that may be included in the system configuration for the particular wireless communication system It may be dependent. In some instances, if the amount of data exceeds the size limit for a small data packet or small data packet, the data may be transmitted in two or more consecutive non-connected transmissions.

In some instances, a core network component, such as a CIoT serving gateway node (C-SGN), may receive data to be transmitted to a user equipment (UE), such as an MTC device, and a small data packet transmission may be initiated for that data You may decide that you are. The core network may format the small data packet into a paging request that combines paging information and data, and may send the paging request to the base station. The base station may receive the paging request and initiate a page process with the UE. The base station may, in some instances, send a page message to the UE indicating that a small data transmission is to be transmitted. The UE may receive the page message and initiate an access procedure that may be used for the transmission of small data. The UE may send a random access request to the base station, for example, in response to a page message, and the base station may transmit the data to the UE as part of a random access response message for the UE.

In some instances, three message procedures may be used, where the base station may send a paging request with a dedicated preamble allocation. The UE may then transmit on a physical random access channel (PRACH) using dedicated preamble allocation. The base station may then provide a small data packet in a random access response (RAR) message. In other examples, five message procedures may be used, where the base station may include a small data indication and may send a paging request that may or may not include a dedicated preamble allocation. The UE may receive the paging request and perform an RRC connection establishment procedure that may correspond to an established three-message RRC connection establishment procedure. The UE may indicate a small data connection request (e.g., in MSG1 or MSG3 of established RRC connection procedures) as part of the RRC connection establishment procedure. The base station may then provide a small data packet as part of the RRC Connection message sent to the UE (e.g., in the MSG4 of the established RRC connection procedures). The UE may receive a small data packet and the base station then either maintains the established RRC connection for a predetermined time if the UE needs to send a response or releases the RRC connection and sends the UE It may be returned to the idle mode.

The following description provides examples and is not intended to limit the scope, applicability, or examples developed in the claims. Changes may be made in the function and arrangement of the elements discussed without departing from the scope of the present disclosure. Various examples may appropriately omit, replace, or append various procedures or components. For example, although the scenarios are described for MTC devices, the techniques described herein may be used with various other types of wireless communication devices and systems. Furthermore, the described methods may be performed in a different order than that described, and various steps may be added, omitted, or combined. In addition, the features described for some examples may be combined in other examples.

Aspects of the present disclosure are initially described in the context of a wireless communication system. These and other aspects of the present disclosure may additionally be incorporated into device diagrams, system diagrams, and flowcharts related to small data transmission through paging in MTC. Lt; / RTI > and are described with reference to them.

1 illustrates an example of a wireless communication system 100, in accordance with various aspects of the present disclosure. The wireless communication system 100 includes base stations 105, user equipment (UE) 115, and a core network 130. In some instances, the wireless communication system 100 may be a Long Term Evolution (LTE) / LTE-Advanced (LTE-a) network.

The base stations 105 may communicate wirelessly with the UEs 115 via one or more base station antennas. Each base station 105 may provide communication coverage for each geographic coverage area 110. [ The communication links 125 shown in the wireless communication system 100 may be used for uplink (UL) transmissions from the base station 105 or downlink (DL) transmissions from the base station 105 to the UE 115, And may include transmissions. The UEs 115 may be distributed throughout the wireless communication system 100 and each UE 115 may be stationary or mobile. The UE 115 may also be referred to as a mobile station, a subscriber station, a remote unit, a wireless device, an access terminal, a handset, a user agent, a client, or some other suitable terminology. The UE 115 may also be a cellular phone, a wireless modem, a handheld device, a personal computer, a tablet, a personal electronic device, a machine type communications (MTC) device,

The base stations 105 may communicate with the core network 130 and with each other. For example, base stations 105 may interface with core network 130 via backhaul links 132 (e.g., S1, etc.). The base stations 105 may communicate with each other directly or indirectly (e.g., via the core network 130) via the backhaul links 134 (e.g., X2, etc.). The base stations 105 may perform radio configuration and scheduling for communication with the UEs 115, or may operate under the control of a base station controller (not shown). In some instances, base stations 105 may be macro cells, small cells, hot spots, and the like. Base stations 105 may also be referred to as eNodeBs (eNBs) In some aspects of the present disclosure, small data transmissions may be provided to UEs 115 via a paging procedure where UEs 115 may transmit RRC connections to transmit small data transmissions But may remain in idle mode for receipt of small data transmissions without establishing.

As mentioned above, some types of wireless devices may provide automated communications that implement M2M communication or MTC. M2M or MTC may refer to data communication technologies that allow devices to communicate with each other or with a base station without human intervention. For example, M2M or MTC may refer to communications from devices incorporating sensors or meters to measure or capture information and relay the information to a central server or application program. The central server or application program may then use the information or present the information to a human interacting with the program or application. Some UEs 115 may be MTC devices such as those designed to collect information or enable automated behavior of the machines. Examples of applications of MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, vehicle group management and tracking, remote security sensing, Transaction-based business billing. The MTC device may also operate using hard-to-duplex (one-way) communication at a reduced peak rate. MTC devices may also be configured to enter a power saving "deep sleep" mode when not involved in active communication.

UE 115 may enter an idle mode and periodically wake up to receive a paging message. In some cases, a component of the core network 130 (e.g., C-SGN as discussed in more detail below) may receive data to be transmitted to the UE 115, and a small data packet transmission may be initiated May be determined. The core network 130 may format the small data packet into a paging request that combines the paging information and data and may send the paging request to the base station 105 and the base station 105 may receive the paging request, Lt; RTI ID = 0.0 > 115 < / RTI > In some instances, an unconnected transmission of data may be performed, where the base station 105 transmits a small data packet to the UE without completing establishment of a network attach procedure and / or an RRC connection with the UE It is possible. For example, the base station may send a page message to the UE 115 indicating that a small data transmission is to be sent. UE 115 may receive a page message and initiate an access procedure that may be used for the transmission of small data packets. UE 115 may send a random access request to base station 105 in response to, for example, a page message, and base station 105 may send data to UE 115 as part of a random access procedure It is possible. In some instances, the base station 105 may send an acknowledgment to the core network 130 that a small data packet has been delivered. In some instances, the base station 105 may send a small data packet in the transmission after the random access procedure but before any dedicated radio bearers or data session context is established (e.g., prior to completion of the network attach procedure) May be transmitted.

2 illustrates an example of a wireless communication system 200 that includes a Radio Access Network (RAN) 205 that implements machine type communication services in accordance with one aspect. The system 200 may include a plurality of MTC devices 115-a and an MTC server 210. Communications between the MTC server 210 and the MTC devices 115 may be considered as part of the RAN 205 via the core network 130-a and may be considered as a base station 105- a < / RTI > The base station 105-a may be an example of the base stations illustrated in Fig. The MTC devices 115-a may be examples of the MTC devices 115 illustrated in FIG. The MTC devices 115-a, the core networks 130-a, the RANs 205 (a), and the RANs 205-a shown in FIG. 2 are well known to those skilled in the art ), And MTC servers 210 are for illustrative purposes only and should not be construed as being so limited.

The wireless communication system 200 may be operable to facilitate machine type communication between one or more MTC devices 115-a and / or one or more MTC servers 210. [ The machine type communication may include communications between one or more devices without human intervention. In one example, machine type communication may involve automated exchange of data between a back-end IT infrastructure, such as MTC server 210, and a remote machine, such as MTC device 115-a, without user intervention. Such data may include a relatively small amount of data, as discussed above, and various aspects of the present disclosure provide efficient transmission of data to the MTC device 115 through a small, unconnected data transmission. The transmission of data from the MTC server 210 via the base station 105-a to the MTC device 115-a may be performed in some instances without requiring the establishment of an RRC connection. These techniques may enhance the efficiency of the system 200, for example, by removing certain network access layer (NAS) procedures and RRC connection establishment messages.

3 illustrates an example of a wireless communication system that implements a machine type communication service over a CIoT network 300, such as an LTE / LTE-Advanced network, in accordance with various aspects of the present disclosure. The CIoT network 300 may include a core network 130-b and an RAN 205-a, which may be examples of the core networks 130 of FIG. 1 and the RAN 205 of FIG. 2, respectively. The core network 130-b may include a packet data network gateway (PDN GW) The PDN GW 340 may be connected to one or more MTC servers 210-a either directly or through a network connection such as an Internet Protocol (IP) network (e.g., operator IP network or external IP networks).

The core network 130-b may include one or more Short Message Service (SMS) gateway mobile switching centers (SMS-GMSCs), interworking MSCs (IWMSCs), or SMS routers 355. Additionally, the core network 130-b may include a Home Subscriber Service (HSS) 350 node, which may provide service authorization and / or user authentication, for example, to the MTC devices 115-b . 3, the CIoT service gateway node (C-SGN) 310 includes a PDN GW 340, an HSS 350, an SMS-GMSC / IWMSC / SMS router 355, or a Mobility Management Entity (MME) 320, respectively. The MME 320 may provide bearer and connection management. In some instances, the C-SGN 310 may include an internal C-SGN MME 330 and may also be coupled between the base stations 105 and other network end-points (e.g., PDN GW 340, etc.) Lt; RTI ID = 0.0 > 335 < / RTI > In some instances, the C-SGN MME 330 may manage small data transmission mobility functions and the MME 320 may handle intra-radio access technology (RAT) mobility functions and / or UE tracking management . SGW 335 and C-SGN MME 330 have been illustrated as part of a C-SGN and in some instances MME 320 and C-SGN MME 330, although these core network components may be implemented in different physical nodes, (E.g., within MME 320) may be combined into a single component.

RAN 205-a may comprise one or more base stations or eNBs 105-b that are configured to communicate with the UEs (e.g., MTC devices 115) via the air interface of the LTE network, Plane protocol terminations. The base stations 105-b may be connected to the X2 interface for intra-eNB communication. The base stations 105-b may be connected to the C-SGN 310 via the S1 interface 315 to communicate data traffic and / or control plane information. Similarly, base stations 105-b may be connected to MME 320 via S1 interface 325 to communicate data traffic and / or control plane information. The MTC devices 115-b may be configured to communicate in cooperation with multiple base stations 105-b, for example, through multiple input multiple output (MIMO), co-ordinated multi-point (CoMP) .

Figure 4 illustrates an example of a process flow 400 for small data transmission in a wireless communication system, in accordance with various aspects of the present disclosure. The process flow 400 includes the UE 115 and the UE 115-N that may be examples of the C-SGN 310 described with reference to Figure 3 of the UE 115 and the base station 105 described with reference to Figures 1-3. c, a first base station 105-c, a second base station 105-d, and a C-SGN 310-a. Initially, at block 405, the UE 115-c may be registered with the C-SGN 310-a and configured for unconnected small data transmissions. For example, during a registration procedure such as an attach or registration update procedure, UE 115-c and C-SGN 310-a enable unconnected transmissions, and in both uplink and downlink And may set up the desired UE 115-c context including a security context for encryption / integrity to protect small data packets.

As used in this disclosure, small data transmissions and small data packets refer to the amount of data that may be transmitted in the payload of a random access message or other control plane message used in establishing a connection. For example, if the maximum random access message payload may include 144 bits, the corresponding small data transmission or small data packet may include 144 bits or fewer. The amount of data that may be included in a small data transmission or small data packet may be limited by the amount of data that may be included in the message payload used for the transmission of that small data transmission or small data packet and the amount of data that may be included in the system configuration for the particular wireless communication system It may be dependent. In some instances, if the amount of data exceeds the size limit for a small data packet or small data packet, the data may be transmitted in two or more consecutive non-connected transmissions.

The UE may camp at the first base station 105-c as indicated at block 410. [ In some instances, base stations 105 may be part of a network cluster (e.g., a tracking area), and when UE 115-c camps at first base station 105-c, first base station 105- c may be associated with UE 115-c. At block 415, the C-SGN may receive a small data packet to be transmitted to the UE 115-c, which may be in idle mode. The C-SGN 310-a may identify that the unconnected transmissions are configured and enabled for the UE 115-c and may select the base stations 105 to paddle to the UE 115- It is possible. As noted above, two or more base stations 105 may be part of a network cluster, and C-SGN 310-a (or an MME within C-SGN or associated with C-SGN) c) and base station 105-d (e.g., covering the tracking area for UE 115-c) as associated with base station 105-c. The C-SGN 310-a may communicate with one or more base stations (e. G., First base station 105-c and base station 105-c) that have received a small data packet or signaling from UE 115- 2 base station 105-d). Typically, data plane encryption and encryption may be performed in the RAN (e.g., between base station 105 and UE 115) using access layer security keys. However, since UE 115-c is in an idle state and no dedicated radio bearers are configured, the security context at base stations 105-c or 105-d is the protection of data transmissions to UE 115- It may not be established for integrity. The C-SGN 310-a may instead encrypt and integrity protect small data packets using control plane level encryption and integrity protection between the C-SGN 310-a and the UE 115-c . For example, C-SGN 310-a may apply a control plane encryption key (e.g., K _NASenc ) and / or a control plane integrity key (e.g., K _NASint ). The C-SGN 310-a may also add a header to the data, as indicated at block 420, indicating that the data is a small data packet for unconnected transmission, -c and / or 105-d).

The C-SGN 310-a then sends a paging request 425 to the second base station 105-d and a paging request 430 to the first base station 105-c. For example, the C-SGN 310-a transmits paging requests 430 and 425 to the base stations 105 (i. E., 105) via an S1 interface (e.g., S1 interface 315) -c and 105-d. In some instances, paging requests 425 and 430 include established paging request content such as UE identity and paging information, and small data packets (e.g., encrypted and integrity protected). In some instances, the paging requests 425 and 430 may include security information to be provided to the UE for decrypting the data and for integrity checking. At block 435, the first base station 105-c and the UE 115-c send a page to the UE 115-c, as discussed in more detail below, And a small data packet transmission procedure 435, which may include sending a response (e. G., A random access response), and transmitting a small data packet. In some instances, C-SGN 310-a may wait for a defined period for acknowledgment 440 of delivery and if no acknowledgment is received, C-SGN 310- (425, 430). The retransmission of paging requests 425 and 430 may be performed a configurable number of times. At block 445, the UE 115-c decrypts the received data, performs an integrity check, and sends an upper layer, such as an application layer, for use by one or more applications running on the UE 115- Lt; RTI ID = 0.0 > received data. ≪ / RTI >

5 illustrates an example of a process flow 500 for a small data packet transmission procedure in a wireless communication system, in accordance with various aspects of the present disclosure. The process flow 500 may include a UE 115-d and a base station 105-e which are examples of the UEs 115 and base stations 105 described with reference to Figs. It is possible. Initially, at block 505, the UE 115-d is in an idle mode. At block 510, base station 105-e may receive a small data paging request (e.g., from a C-SGN, etc.). This small data paging request may include paging information for UE 115-d and small data packets to be transmitted to UE 115-d, as discussed above. When base station 105-e receives a paging request that includes a small data packet as described above, base station 105-e pages to UE 115-d, and UE 115-d And responds to the paging, it forwards a small data packet to the UE 115-d.

In some aspects, as illustrated in the example of FIG. 5, the delivery of small data packets may be augmented through the messages of the random access procedure. In this example, at block 515, base station 105-e may identify PRACH resources for a random access request and may include PRACH resources in a page message for UE 115-d. PRACH resources may include time, frequency, and / or preamble resources for random access requests, and they may be selected from a set of available PRACH resources configured for use in an unconnected small data transmission. For example, the identified PRACH resources may be an index for a pre-defined set of PRACH resources that may be defined or semi-statically configured and broadcast in a system information block (SIB). In some instances, the PRACH resource allocation may have an expiration time, or may have a maximum number of attempts, and then, when the UE 115-d is not successful, the UE 115- Lt; RTI ID = 0.0 > PRACH < / RTI > resources.

Following identification of the PRACH resources, the base station 105-e transmits a page message 520, which in this example contains dedicated PRACH resource information. The UE 115-d transmits the random access preamble 525 using the identified PRACH resources. The base station 105-e may then transmit a random access response 530 that includes a small data packet as a payload. The small data packet may, for example, replace the timing advance, uplink acknowledgment, and / or cell radio network temporary identifier (C-RNTI) fields in the random access response 530. The UE 115-d may then remain in the idle mode or enter the connected mode (as indicated by the random access response 530), as indicated at block 535. In this way, UE 115-d utilizes dedicated resources to enforce contentionless random access, and the random access response message includes small data packets. This technique may provide for reliable reliable access response reception, and the UE 115-d may then perform a number of random access procedures until a random access response is received. In some instances, in addition to a small data packet, the random access response may also include uplink acknowledgment, which may be used to transmit data originating at the UE 115-d or to indicate the correct reception of data Lt; / RTI > may be used to send an acknowledgment to the user. In certain instances, where the base station 105-e may decide to proceed with establishing an RRC connection with the UE 115-d, the random access response also includes an indication to continue the RRC connection to the UE You may. The UE 115-d may then send an access setup message (e.g., at the resources authorized in the uplink grant). The random access response message may, in additional examples, include a connection release indication that may indicate that UE 115-d may return to idle mode upon receipt of a small data packet. This connection release indication may be based on the absence of an indication to continue other fields (e.g., timing advance, uplink acknowledgment, C-RNTI) in the RRC connection or random access response in other examples. UE 115-d may provide an acknowledgment (not shown) to base station 105-e for successful reception of a small data packet. The acknowledgment may be based on, for example, resources associated with the random access response (e.g., random access RNTI (RA-RNTI), PDSCH location, etc.) of the random access response, or on the uplink control channel , PUCCH) or uplink data channel (e.g., PUSCH). In some instances, base station 105-e may verify for a C-SGN (e.g., C-SGN 310 in Figures 3 and 4) that a small data packet has been delivered.

6 shows an example of a process flow 600 for a small data packet transmission procedure in a wireless communication system, in accordance with various aspects of the present disclosure. The process flow 600 may include a UE 115-e and a base station 105-f, which may be examples of UEs 115 and base stations 105 described with reference to Figures 1-5 . Initially, at block 605, the UE 115-e is in an idle mode. At block 610, base station 105-f may receive a small data paging request. This small data paging request may include paging information for UE 115-e and small data packets to be transmitted to UE 115-e, as discussed above. When base station 105-f receives a paging request that includes a small data packet as described above, base station 105-f paged to UE 115-e and UE 115-e In response to the paging, base station 105-f transmits a small data packet to UE 115-e.

In some aspects, as illustrated in the example of FIG. 6, the delivery of small data packets may be performed via random access request RRC connection establishment messaging. In this example, base station 105-f transmits a page message 615 that may indicate to UE 115-e that a small data transmission is to be delivered. In some examples, the page message 615 may optionally include a dedicated random access preamble allocation (which may be used to indicate a small data transmission). The UE 115-e then sends a random access response 625 from the base station 105-f, followed by a random access message 630 from the UE 115-e, ) (E.g., an RRC connection setup request). In certain instances, the random access response 625 may follow a legacy random access procedure and may include uplink acknowledgment to the random access message 630. In some instances, the random access message 630 may include a UE identification indication and an indication that the UE can receive a small data packet in the next message. In certain instances, the random access message 630 may include other data originating from the UE 115-e. In some instances, the random access preamble may include an indication that the connection is for a small data request. The base station 105-f may then transmit an access setup message 635, which may include a small data packet as a payload. The connection setup message 635 may, in some instances, also include a UE identification indication and an indication to release the connection or to complete the RRC connection. The UE 115-e may then respond with an access setup complete message 640, which may include an acknowledgment to the base station 105-f of successful reception of a small data packet. The UE 115-e may enter the RRC connected mode or resume the idle mode based on the connection setup message at 645.

Although an RRC connection is established between the UE 115-e and the base station 105-f after the connection setup complete message 640, the network associated with the base station 105-f (e.g., RAN) Such as a PDN-GW, etc.) and UE 115-f, or any dedicated radio bearers (e.g., default bearer, etc.) for transmission of data. In some instances, a small data packet may instead be sent instead in the messaging from the base station 105-f after the connection setup complete message 640 but before the attach procedure used to establish the security context and dedicated radio bearers have. For example, the base station 105-f may send a message (not shown) containing a small data packet after the connection setup complete message 640. As discussed above, since the C-SGN may apply the control plane data encryption key and / or the control plane data integrity key to the small data packets included in the small data paging request received at 610, Encryption and data integrity protection may be maintained. Thus, a small data packet may be transmitted in a control plane message associated with signaling the radio bearer prior to establishment of any dedicated radio bearers including a default radio bearer.

As mentioned above, when the UE (e.g., UE 115 in Figures 1 to 6 is paged and receives a small data packet, the UE may decrypt the small data packet and check the integrity. And the integrity checks are correct, the UE delivers a small data packet to the upper layers. In some instances, the UE sends an integrity protected acknowledgment (ACK) message to the C-SGN (E.g., C-SGN 310 in Figures 3 and 4.) If the decryption is unsuccessful, the integrity check fails, or other errors occur in the reception, the UE may resynchronize with the core network The base station 105-f may initiate a registration update (e.g., a tracking area updating procedure) to determine that a small data packet has been delivered to the UE 115-e SGN 310 (e.g., C-SGN 310 in Figures 3 and 4).

FIG. 7 illustrates a block diagram of a device 700 configured for small data transmission in a wireless communication system, in accordance with various aspects of the present disclosure. The device 700 may be an example of aspects of the C-SGN 310 described with reference to Figs. 1-6. The device 700 may include a core network paging manager 705, which may perform operations related to the small data packets discussed above. The core network paging manager 705 may receive a small data packet to be sent to the UE, format a small data packet into the paging request, and send the paging request to the base station, . The core network paging manager 705 includes a gateway (GW) interface 710, a paging request formatter 715, a radio access network (RAN) interface 720, a paging configuration manager 725, A security manager 730, a processor 760 and a memory 765 (which includes software 770), each of which may be coupled directly (e.g., via bus system 775) Or may be in a communicative state indirectly.

Memory 765 may include RAM and ROM. The memory 765 may also store computer readable, computer-executable software / firmware code 770 that includes instructions that when executed, cause the processor 760 to perform various functions described herein (E. G., Sending small data packets in paging messaging for unconnected transmissions, encrypting small data packets and / or integrity protection, etc.). Alternatively, the software 770 may not be directly executable by the processor 765, but may be configured to cause the computer to perform the functions described herein, for example, when compiled and executed. The processor 760 may include an intelligent hardware device, e.g., a CPU, microcontroller, ASIC, or the like. The processor 760 may include various special purpose processors such as encoders, queue processing modules, baseband processors, wireless head controllers, digital signal processors (DSPs), and the like.

The gateway interface 710 may receive small data packets 735 to be transmitted to the UEs as described with reference to Figures 2-6. The gateway interface 710 may be coupled to the SGW or PDN-GW as discussed, for example, with reference to FIGS. 2-6. The gateway interface 710 may pass the received small data packets 740 to the SDP security manager 730. The SDP security manager may be configured with a security context for one or more of encryption or integrity protection of small data packets as described with reference to Figures 2-6. For example, the SDP security manager may provide a control plane data encryption key (e.g., K _NASenc ) or a data integrity key (e.g., K _NASint ) for small data packets to allow UEs to acquire protected small data packets 745 ) May be applied. The paging request formatter 715 may format small data packets into paging requests 750, where each paging request includes UE identification information and each small data < RTI ID = 0.0 > Packet. The paging request formatter 715 may, in some instances, also receive confirmation (e.g., via the radio access network interface 720) that a small data packet has been delivered to the UE. In some instances, the paging request additionally provides header information indicating that the paging request includes a small data packet.

The radio access network interface 720 may send a paging request to the base station as described with reference to Figures 2-6. In some instances, a paging request may be sent to one or more base stations that may be part of a network cluster (e.g., associated with the tracking area), and at least one base station in the network cluster may be associated with the UE The wireless access network interface 720 may also determine whether a confirmation of the delivery of a small data packet is received. The paging configuration manager 725 may be configured to enable reception of small data packets in the paging requests, as described with reference to Figures 2-6. ≪ RTI ID = 0.0 > One or more UEs may be configured via the configuration packets 755. [ In some instances, the UEs may be in an idle mode and configured to receive a small data packet in a paging request.

8 shows a block diagram of a wireless device 800 configured for small data transmission in a wireless communication system, in accordance with various aspects of the present disclosure. The wireless device 800 may be an example of aspects of the base station 105 described with reference to Figures 1-6. The wireless device 800 may include a receiver 805, a base station paging manager 810, or a transmitter 815. The wireless device 800 may also include a processor. Each of these components may be in communication with each other.

Receiver 805 may receive information such as packets, user data, or control information associated with various transmissions (e.g., information related to random access requests and small data transmissions). Information may be passed to the base station paging manager 810 and to other components of the wireless device 800. [

The base station paging manager 810 may receive a paging request including a UE identification indication and a small data packet from a network node (e.g., C-SGN, etc.), send a page to the UE, receive an access request from the UE , And may transmit a small data packet to the UE in response to the access request. In certain instances, the base station paging manager 810 may determine paging resources for use in transmitting or receiving paging messages. The base station paging manager 810 may include a base station paging request manager 820, a UE transmit interface 825, and a random access coordinator 830.

The transmitter 815 may transmit signals received from other components of the wireless device 800. In some instances, the transmitter 815 may be juxtaposed with the receiver 805 in the transceiver module. The transmitter 815 may comprise a single antenna, or it may comprise a plurality of antennas.

The base station paging request manager 820 may receive a paging request 835 from a core network component, such as the C-SGN 310, as described above with reference to Figures 3 and 4. [ The UE transmit interface 825 may communicate communications 845 for the UEs handled by the base station by sending paging management information 840 to the UE transmit interface 825 (e.g., (E.g., via transmitter 815) of page (s), uplink grants, radio resource control setup messages, or connection release indications, as described above. In some examples, the page for the UE includes an indication that a small data packet is to be transmitted. The base station paging request manager 820 may also receive acknowledgments 860 (e.g., via receiver 805) to confirm that small data packets have been delivered to the UEs. The base station paging request manager 820 may verify delivery of small data packets to the core network component.

Random Access Coordinator 830 may receive an access request 850 from the UE as described with reference to FIGS. 2-6. The random access coordinator 830 may also send a small data packet to the UE in response to the access request, allocate a set of resources to the UE for use in transmitting the access request, and transmit the UE transmission interface 825 May also include an indication of an assigned set of resources on the page in communication 855 using the transmitter 815. The small data packets may, for example, replace timing advance, uplink acknowledgment, and / or C-RNTI fields in the random access response. The set of resources may be resources of a physical random access channel (PRACH) associated with an unconnected transmission of small data packets. In some examples, the set of resources includes at least one of time resources, frequency resources, or preamble resources for use in transmitting an access request. In some examples, an indication of an assigned set of resources includes an index into a plurality of available sets of preamble resources. In some instances, a plurality of available sets of resources may be pre-defined or semi-static configured. Random Access Coordinator 830 may also receive an acknowledgment from UE (not shown) indicating the correct reception of a small data packet. In some instances, the access request from the UE may include a random access preamble, and the random access coordinator 830 may initiate sending a random access response to the UE in response to the random access preamble. Random Access Coordinator 830 may also receive a data request from the UE in response to the random access response (not shown).

FIG. 9 shows a diagram of a system 900 including a base station 105-g configured for small data transmission in a wireless communication system, in accordance with various aspects of the present disclosure. The system 900 may include a base station 105-g, which may be an example of the wireless device 800 described with reference to Figs. 1-6 and Fig. The base station 105-g may include a base station paging manager 910, which may be an example of the base station paging manager 810 described with reference to FIG. The base station 105-g may also include components for two-way voice and data communications, including components for transmitting communications and components for receiving communications. For example, base station 105-g may communicate bi-directionally with UE 115-f or UE 115-g.

In some cases, base station 105-g may have one or more wired backhaul links. Base station 105-g may have a wired backhaul link (e.g., S1 interface, etc.) to core network 130-c. Base station 105-g may also communicate with other base stations 105, such as base station 105-h and base station 105-i, via inter-base station backhaul links (e.g., X2 interface). Each of the base stations 105 may communicate with the UEs 115 using the same or different wireless communication technologies. In some cases, base station 105-g may communicate with other base stations such as 105-h or 105-i using base station communication module 925. In some instances, the base station communication module 925 may provide an X2 interface within the LTE / LTE-A wireless communication network technology to provide communication between portions of the base stations 105. [ In some instances, base station 105-g may communicate with other base stations via core network 130. [ In some cases, base station 105-g may communicate with core network 130 via network communication interface 930. [

The base station 105-g may include a processor 905, a memory 915 (including software SW 1420), and antenna (s) 940, (E. G., Via system 945). ≪ / RTI > The transceiver 935 may be configured to communicate bidirectionally with the UEs 115, which may be multi-mode devices, via the antenna (s) 940. The transceiver 935 (or other components of the base station 105-g) may also be configured to bidirectionally communicate with one or more other base stations (not shown), via the antenna 940. The transceiver 935 may include a modem configured to modulate the packets and to provide the modulated packets to the antennas 940 for transmission and to demodulate the packets received from the antennas 940. [ The base station 105-g may include multiple transceivers 935 each having one or more associated antennas 940. [ The transceiver may be an example of a combined receiver 805 and transmitter 815 of FIG.

The memory 915 may include RAM and ROM. The memory 915 may also store computer readable, computer-executable software / firmware code 920 that includes instructions that when executed, cause the processor 910 to perform various functions described herein (E.g., small data transmission in a wireless communication system, etc.). Alternatively, the software 920 may not be directly executable by the processor 905, but may be configured to cause the computer to perform the functions described herein, for example, when compiled and executed. The processor 905 may include an intelligent hardware device, e.g., a CPU, microcontroller, ASIC, or the like. The processor 905 may include various special purpose processors such as encoders, cue processing modules, baseband processors, wireless head controllers, digital signal processors (DSPs), and the like.

Base station communication interface 925 may also manage communications with other base stations 105. In some cases, the communication management module may include a controller or scheduler for controlling communications with the UEs 115 in cooperation with other base stations 105. In some cases, For example, the base station communication interface 925 may coordinate the scheduling for transmissions to the UEs 115 for various interference mitigation techniques such as beamforming or joint transmission.

The components of the wireless device 800, and the base station paging administrators 810 and 910, may be implemented individually or collectively with at least one ASIC adapted to perform some or all of the applicable functions in hardware It is possible. Alternatively, the functions may be performed by one or more other processing units (or cores) on at least one IC. In other instances, other types of integrated circuits may be used (e.g., structured / platform ASICs, field programmable gate arrays (FPGAs), or other semi-custom ICs), which may be programmed in any manner known in the art . Each unit of these functions may also be implemented, in whole or in part, with instructions contained in memory, formatted to be executed by one or more general purpose or application-specific processors.

10 shows a block diagram of a wireless device 1000 configured for small data transmission in a wireless communication system, in accordance with various aspects of the present disclosure. The wireless device 1000 may be an example of the UEs 115 described with reference to Figures 1-9. The wireless device 1000 may include a receiver 1005, a UE paging manager 1010, or a transmitter 1015. The wireless device 1000 may also include a processor. Each of these components may be in communication with each other.

The transceiver 1005 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to small data transmissions in a wireless communication system) It is possible. Information may be passed to the UE paging manager 1010 and to other components of the wireless device 1000.

The UE paging manager 1010 may receive a page from the base station containing at least one of an indication that a small data packet is to be sent to the UE or a small data packet. The UE may initiate a random access channel (RACH) procedure by sending an access request to the base station in response to the page and may acknowledge a small data packet in response to an access request during the RACH procedure. The acknowledgment may be based, for example, on the resources associated with the random access response (e.g., RA-RNTI, PDSCH location of random access response, etc.) or on the uplink control channel (e.g., PUCCH) May be transmitted via uplink resources of the link data channel (e.g., PUSCH).

The UE paging manager 1010 may include a page manager 1020, a UE random access coordinator 1025, a UE configuration manager 1030, and a small data packet processor 1065. The page manager 1020 may receive the page 1035 and send an access request 1040 in response to the page via the UE random access coordinator 1025 based on an indication that a small data packet is to be sent to the UE Thereby initiating the RACH procedure. The UE random access coordinator 1025 may forward the access request 1040 to the base station from the communication 1045 via the transmitter 1015. [

The UE Random Access Coordinator 1025 may also receive a random access response in the communication 1050 in response to an access request 1040 that may or may not include a small data packet. In some instances, in addition to small data packets, the random access response may also include uplink acknowledgment, which may be used to transmit data originated at the UE 115 or to transmit an acknowledgment to indicate the correct reception of data . In certain instances, the random access response also includes an indication to continue the RRC connection to the UE 115 in those cases where the base station 105 may decide to proceed with establishing an RRC connection with the UE 115 You may. The random access coordinator 1025 may then transmit the connection setup message in the communication 1045 via the transmitter 1015 (e.g., at the resources authorized in the uplink grant).

In some examples, page message 1035 may optionally include a dedicated random access preamble allocation (which may be used to indicate a small data transmission). The UE 115 may then perform the RRC connection establishment procedure with the base station 105 using the techniques described in FIG. The RRC connection establishment procedure may include an access setup message at a communication 1050 that may include a small data packet as a payload. In some instances, a small data packet may instead be sent in messaging from the base station 105 prior to the attach procedure used to establish the security context and dedicated radio bearers after the connection setup complete message. Thus, a small data packet may be transmitted in a control plane message associated with a signaling radio bearer prior to establishment of any dedicated radio bearers, including a default radio bearer.

UE configuration manager 1030 may include configuration information 1055 for small data transmissions, such as, for example, NAS security information. UE configuration manager 1030 may also receive configuration information 1060 from a C-SGN associated with small, unconnected data transmissions. UE configuration manager 1030 may provide acknowledgment information 1055 to a small data packet processor 1065 that may process small data packets 1070 (e.g., decrypt, ) To provide the processed small data packets 1077 to higher layers (e.g., applications, etc.).

The transmitter 1015 may transmit signals received from other components of the wireless device 1000. In some instances, the transmitter 1015 may be juxtaposed with the receiver 1005 in a transceiver module. The transmitter 1015 may comprise a single antenna, or it may comprise a plurality of antennas.

FIG. 11 shows a diagram of a system 1100 including a UE 115 configured for small data transmission in a wireless communication system, in accordance with various aspects of the present disclosure. The system 1100 may include a UE 115 or a UE 115-h, which may be an example of a wireless device 1100, as described with reference to Figs. 1-6 and 8-10. The UE 115-h may include a UE paging manager 1110, which may be an example of the UE paging manager 1010 described with reference to FIG. The UE 115-h may also include components for two-way voice and data communications, including components for transmitting communications and components for receiving communications. For example, UE 115-h may communicate with base station 105-j or UE 115-i in both directions.

The UE 115-h may include a processor 1105, a memory 1115 (including software (SW) 1120), a transceiver 1135, and one or more antenna (s) 1140, Each of which may communicate directly or indirectly with each other (e.g., via buses 1145). Transceiver 1135 may communicate with one or more networks in either direction, via antenna (s) 1140 or wired or wireless links, as described above. For example, the transceiver 1135 may communicate with the base station 105 or other UE 115 in both directions. The transceiver 1135 may include a modem configured to modulate the packets and provide the modulated packets to the antenna (s) 1140 for transmission and to demodulate the packets received from the antenna (s) 1140 . The UE 115-h may also include a single antenna 1140, but the UE 115-h may also have multiple antennas 1140 capable of transmitting or receiving multiple radio transmissions simultaneously.

Memory 1115 may include random access memory (RAM) and read only memory (ROM). The memory 1115 may store computer readable, computer-executable software / firmware code 1120 that includes instructions that when executed, cause the processor 1105 to perform various functions described herein , Small data transmission in a wireless communication system, etc.). Alternatively, the software / firmware code 1120 may not be directly executable by the processor 1105, but may cause the computer to perform the functions described herein (e.g., when compiled and executed) . The processor 1105 may include an intelligent hardware device (e.g., a central processing unit (CPU), microcontroller, ASIC, etc.).

12 depicts a flowchart depicting a method 1200 for small data transmission in a wireless communication system, in accordance with various aspects of the present disclosure. The operations of method 1200 may be implemented by a core network component, such as C-SGN 310 or its components, as described with reference to Figs. 1-11. For example, operations of the method 1200 may be performed by the core network paging manager 705 as described with reference to FIG. In some instances, the core network component may execute a set of codes to control the functional elements of the component to perform the functions described below. Additionally or alternatively, the core network component may perform aspects of the functions described below using special-purpose hardware.

At block 1205, the core network component may receive a small data packet to be transmitted to the UE as described with reference to Figs. 2-6. In certain instances, the operations of block 1205 may be performed by the GW interface 710 described with reference to FIG.

At block 1210, the core network component may format a small data packet into a paging request that includes UE identification information and a small data packet, as described with reference to Figures 2-6. In certain instances, the operations of block 1210 may be performed by the paging request formatter 715 described with reference to FIG.

At block 1215, the core network component may send a paging request to one or more base stations as described with reference to Figures 2-6. In certain instances, the operations of block 1215 may be performed by the RAN interface 720 described with reference to FIG.

Figure 13 shows a flowchart depicting a method 1300 for small data transmission in a wireless communication system, in accordance with various aspects of the present disclosure. The operations of method 1300 may be implemented by base station 105 or its components as described with reference to Figs. For example, the operations of method 1300 may be performed by the base station paging manager 810 or the base station paging manager 910 as described with reference to Figs. In some instances, base station 105 may execute a set of codes to control the functional elements of base station 105 to perform the functions described below. Additionally or alternatively, base station 105 may perform aspects of the functions described below using special-purpose hardware.

At block 1305, the base station 105 may receive a paging request from a network node, as described with reference to Figures 2-6, and the paging request associated with the UE includes a small data packet. In certain instances, the operations of block 1305 may be performed by the paging request manager 820 described with reference to FIG.

At block 1310, the base station 105 may send a page to the UE as described with reference to Figs. 2-6. In certain instances, the operations of block 1310 may be performed by the UE transmission interface 825 described with reference to FIG.

At block 1315, the base station 105 may receive an access request from the UE as described with reference to Figures 2-6. In certain instances, the operations of block 1315 may be performed by random access coordinator 830 as described with reference to FIG.

At block 1320, the base station 105 may send a small data packet to the UE in response to the access request, as described with reference to Figs. 2-6. In certain instances, the operations of block 1320 may be performed by random access coordinator 830 as described with reference to FIG.

14 depicts a flowchart depicting a method 1400 for small data transmission in a wireless communication system, in accordance with various aspects of the present disclosure. The operations of method 1400 may be implemented by UE 115 or its components as described with reference to Figs. For example, operations of method 1400 may be performed by the UE paging manager 1010 or the UE paging manager 1010 as described with reference to FIGS. In some instances, the UE 115 may execute a set of codes to control the functional elements of the UE 115 to perform the functions described below. Additionally or alternatively, the UE 115 may perform aspects of the functions described below using special-purpose hardware.

At block 1405, the UE 115 may receive a page from the base station, as described with reference to Figures 2-6. In certain instances, the operations of block 1405 may be performed by page manager 1020 described with reference to FIG.

At block 1410, the UE 115 may initiate the random access procedure by sending an access request to the base station in response to the page, as described with reference to Figures 2-6. In certain instances, the operations of block 1410 may be performed by the UE random access coordinator 1025 described with reference to FIG.

At block 1415, the UE 115 may receive a small data packet in the control plane message prior to activation of the dedicated radio bearer for data connection with the base station as described with reference to Figs. 2-6. In certain instances, the operations of block 1415 may be performed by UE random access coordinator 1025 as described with reference to FIG.

At block 1420, UE 115 may acknowledge a small data packet in response to an access request during a RACH procedure, as described with reference to Figures 2-6. In certain instances, the operations of block 1420 may be performed by UE random access coordinator 1025 as described with reference to FIG.

Accordingly, methods 1200, 1300, and 1400 may provide small data transmissions in a wireless communication system. It should be noted that the methods 1200, 1300, and 1400 describe possible implementations and that operations and steps may be rearranged or otherwise modified to allow for other implementations. In some instances, aspects from two or more of the methods 1200, 1300, and 1400 may be combined.

The description herein is provided as examples and is not intended to limit the scope, applicability, or examples developed in the claims. Changes may be made in the arrangement and functioning of the elements discussed without departing from the scope of the present disclosure. Various examples may appropriately omit, substitute, or add various procedures or components. In addition, the features described for some examples may be combined in other examples.

The techniques described herein may be implemented in various systems, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC- , ≪ / RTI > and other systems. The terms "system" and "network" are often used interchangeably. CDMA systems may implement wireless technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA), and the like. CDMA2000 covers the IS-2000 standard, the IS-95 standard, and the IS-856 standard. IS-2000 releases 0 and A are commonly referred to as CDMA2000 1X, 1X, and the like. IS-856 (TIA-856) is commonly referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), and the like. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. The TDMA system may implement a radio technology such as Global System for Mobile Communications (GSM). An orthogonal frequency division multiple access (OFDMA) system is a radio technology such as UMB (Ultra Mobile Broadband), E -UTRA (Evolved UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash ^TM -OFDMA . UTRA and E-UTRA are part of Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) and Long Term Evolution (LTE) - Advanced (LTE-a) are new releases of the Universal Mobile Telecommunications System (UMTS) using E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-a and Global System for Mobile communications (GSM) are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). The techniques described herein may be used for other systems and wireless technologies as well as for the systems and wireless technologies described above. However, the description herein describes an LTE system for illustrative purposes, and LTE terminology is used more in the above description, but these techniques are applicable beyond LTE applications.

In LTE / LTE-A networks, including those networks described herein, the term evolutionary Node B (eNB) may be commonly used to describe base stations. The wireless communication systems or systems described herein may include heterogeneous LTE / LTE-a networks in which different types of Evolved Node Bs (eNBs) provide coverage for various geographic areas. For example, each eNB or base station may provide communication coverage for macro cells, small cells, or other types of cells. The term "cell" is a 3GPP term that may be used to describe a base station, a carrier or component carrier associated with a base station, or a coverage area (e.g., sector, etc.) of a carrier or base station, depending on context.

The base stations may also be referred to as a base transceiver station, a wireless base station, an access point, a wireless transceiver, a NodeB, an eNodeB (eNB), a home NodeB, a home eNodeB, or some other suitable terminology. The geographic coverage area for the base station may be divided into sectors that constitute only a portion of the coverage area. The wireless communication systems or systems described herein may include different types of base stations (e.g., macros or small cell base stations). The UEs described herein may be capable of communicating with various types of base stations and network equipment, including macro eNBs, small cell eNBs, relay base stations, and the like. There may be overlapping geographic coverage areas for different technologies.

Macro cells typically cover a relatively large geographical area (e.g., a few kilometers in radius) and may allow unrestricted access by UEs with network providers and service subscriptions. A small cell is a lower power base station compared to a macrocell, which may operate in the same or different frequency bands (e.g., permit, unauthorized, etc.) than macro cells. Small cells may include picocells, femtocells, and microcells according to various examples. For example, a picocell may cover a small geographical area and may allow unrestricted access by UEs with network providers and service subscriptions. The femtocell may also cover a small geographic area (e. G., Assumptions) and may also be associated with UEs associated with the femtocell (e.g., UEs in a closed subscriber group (CSG) ). ≪ / RTI > An eNB for a macro cell may also be referred to as a macro eNB. The eNB for a small cell may be referred to as a small cell eNB, a pico eNB, a femto eNB, or a home eNB. The eNB may support one or more (e.g., 2, 3, 4, etc.) cells (e.g., component carriers). The UE may be able to communicate with various types of base stations and network equipment, including macro eNBs, small cell eNBs, relay base stations, and the like.

The wireless communication systems or systems described herein may support synchronous or asynchronous operation. For synchronous operation, the base stations may have similar frame timing, and transmissions from different base stations may be roughly aligned in time. For asynchronous operation, the base stations may have different frame timings, and transmissions from different base stations may not be aligned in time. The techniques described herein may be used for both synchronous or asynchronous operations.

The downlink transmissions described herein may also be referred to as forward link transmissions, while uplink transmissions may also be referred to as reverse link transmissions. - Each communication link described herein, including for example the wireless communication systems 100 and 200 of FIGS. 1 and 2, may comprise one or more carriers, where each carrier comprises a plurality of sub- (E. G., Waveform signals of different frequencies). ≪ / RTI > Each modulated signal may be transmitted on different sub-carriers and may carry control information (e.g., reference signals, control channels, etc.), overhead information, user data, and so on. The communication links (e.g., communication links 125 in FIG. 1) described herein may be implemented using frequency division duplex (FDD) (e.g., using paired spectrum resources) or time division duplex It is also possible to transmit bi-directional communications using split-duplex (TDD) operation. Frame structures may be defined for frequency division duplex (FDD) (e.g., frame structure type 1) and TDD (e.g., frame structure type 2).

The descriptions developed herein in connection with the accompanying drawings illustrate exemplary configurations and not all examples that may be or may be practiced within the scope of the claims. As used herein, the term "exemplary" means "serving as an example, instance, or illustration" and is not meant to be "advantageous" or "advantageous over other examples". The detailed description includes specific details to provide an understanding of the techniques described. However, these techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

In the accompanying drawings, similar components or features may have the same reference label. Also, various components of the same type may be distinguished by a dash and a second label that distinguish among similar components following the reference label. Where only a first reference label is used in the specification, the description is applicable to any of the similar components having the same first reference label regardless of the second reference label.

The information and signals described herein may be represented using any of a variety of different techniques and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, Optical fields or optical particles, or any combination thereof.

The various illustrative blocks and modules described in connection with the disclosure herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, Or may be implemented or performed by any combination of those designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored on or transmitted over as a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of the software, the functions described above may be implemented using software, hardware, firmware, hardwiring, or any combination thereof executed by the processor. The features implementing the functions may also be physically located at various positions, including that some of the functions are distributed such that they are implemented in different physical locations. Also, as used herein, the terms used in the claims, including in the list of items (e.g., a list of items written by a phrase such as "at least one of &Quot; or "such that at least one list of A, B, or C, for example, refers to A or B or C or AB or AC or BC or ABC (i.e., A and B and C) .

Computer-readable media includes both communication media and non-transitory computer storage media, including any medium that facilitates transfer of a computer program from one place to another. Non-temporary storage media may be any available media that can be accessed by a general purpose or special purpose computer. By way of non-limiting example, the non-transitory computer readable medium can be RAM, ROM, electrically erasable programmable read only memory (EEPROM), compact disk (CD) ROM or other optical disk storage device, magnetic disk storage device, Storage devices, or desired program code means, in the form of instructions or data structures, and which can be accessed by a general purpose or special purpose computer, or any other non- And may include temporary media. Also, any connection is properly termed a computer readable medium. For example, if software is transmitted from a web site, server, or other remote source using wireless technologies such as coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or infrared, radio, and microwave, , Fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of media. Disks and discs as used herein include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disc and Blu-ray disc, wherein the disc is typically magnetically While reproducing data, a disc reproduces data optically using a laser. Combinations of the above are also included within the scope of computer readable media.

The description herein is provided to enable a person skilled in the art to make or use the present disclosure. Various modifications to the disclosure will be readily apparent to those of ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the spirit of the disclosure. Accordingly, this disclosure is not limited to the examples and designs described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (24)

CLAIMS 1. A method for wireless communication,
Receiving a small data packet to be transmitted to a user equipment (UE);
Formatting the small data packet into a paging request, the paging request including formatting the small data packet into a paging request, the mobile packet including a UE identification information and the small data packet; And
And sending the paging request to one or more base stations. The method according to claim 1,
Determining whether an acknowledgment of the delivery of the small data packet has been received; And
Further comprising retransmitting the paging request to the one or more base stations if the acknowledgment is not within a defined period of time. The method according to claim 1,
Wherein formatting the small data packet into a paging request comprises applying one or both of a control plane data encryption key or a control plane data integrity key. The method according to claim 1,
Wherein the paging request further comprises header information indicating that the paging request includes the small data packet. The method according to claim 1,
The method is performed by an entity of an evolutionary packet core. 6. The method of claim 5,
Wherein the method is performed by a Cellular Internet (CIoT) serving gateway node (C-SGN). CLAIMS 1. A method for wireless communication,
Receiving a paging request associated with a user equipment (UE) from a network node at a base station, the paging request comprising a small data packet for the UE;
Transmitting a page to the UE;
Receiving an access request from the UE; And
And sending the small data packet to the UE in response to the access request. 8. The method of claim 7,
Receiving an acknowledgment from the UE indicating an accurate reception of the small data packet; And
Further comprising transmitting to the network node a confirmation that the small data packet has been delivered to the UE. 8. The method of claim 7,
Wherein transmitting the small data packet to the UE comprises transmitting the small data packet in a control plane message associated with a signaling radio bearer. 8. The method of claim 7,
Wherein the control plane message comprises a message of the random access procedure comprising the access request. 10. The method of claim 9,
In the random access procedure, the method further comprises receiving an access request message including a small data request field,
Wherein transmitting the small data packet comprises transmitting the small data packet to the UE in a connection establishment message in response to the connection request message. 8. The method of claim 7,
Wherein the page for the UE comprises an indication that the small data packet is to be transmitted. 8. The method of claim 7,
Wherein the access request is received on a set of physical random access channel (PRACH) resources associated with an unconnected transmission of small data packets. CLAIMS 1. A method for wireless communication,
At a user equipment (UE), receiving a page from a base station;
Initiating a random access procedure by sending an access request to the base station in response to the page;
Receiving a small data packet in a control plane message prior to activation of a dedicated radio bearer for data connection with the base station; And
And acknowledging the small data packet. 15. The method of claim 14,
Wherein the control plane message is part of the random access procedure. 15. The method of claim 14,
Wherein the control plane message is a random access response message of the random access procedure. 15. The method of claim 14,
Further comprising, in the connection request message, transmitting a small data request field,
Wherein the small data packet is received in a connection establishment message sent in response to the connection request message. 15. The method of claim 14,
Wherein the access request is transmitted on a set of physical random access channel (PRACH) resources associated with an unconnected transmission of small data packets. An apparatus for wireless communication,
Means for receiving a small data packet to be transmitted to a user equipment (UE);
Means for formatting the small data packet into a paging request, the paging request including UE identification information and the small data packet; means for formatting the small data packet into a paging request; And
And means for transmitting the paging request to one or more base stations. 20. The method of claim 19,
Means for determining whether acknowledgment of the delivery of the small data packet has been received; And
And means for retransmitting the paging request to the one or more base stations if the acknowledgment is not within a defined period of time. 20. The method of claim 19,
Wherein the means for formatting the small data packet into a paging request comprises means for applying one or both of a control plane data encryption key or a control plane data integrity key. 20. The method of claim 19,
Wherein the paging request further comprises header information indicating that the paging request includes the small data packet. 20. The method of claim 19,
Wherein the device is an entity of an evolutionary packet core. 24. The method of claim 23,
Wherein the device is a cellular Internet (CIoT) serving gateway node (C-SGN).

Images