Enhanced node B and method for RRC connection establishment for small data transfers

• US 9,191,178 B2
• Filed: 12/26/2013
• Issued: 11/17/2015
• Est. Priority Date: 04/04/2013
• Status: Active Grant

• Current Assignee: Intel Corporation
• Original Assignee: Intel IP Corporation (Intel Corporation)
• Inventors: Koc, Ali, Gupta, Maruti, Vannithamby, Rath, Jha, Satish Chandra
• Primary Examiner(s): Zhou, Yong
• Application Number:
  US14/140,932
• Publication Number:
  US 20140301288A1
• Time in Patent Office: 691 Days
• US Class Current: 1/1
• CPC Class Codes: H04B 1/38 Transceivers, i.e. devices in which transmitter and receiver form a structural unit and in which at least one part is used for functions of transmitting and receiving
• CPC Class Codes: H04B 7/024 Co-operative use of antennas of several sites, e.g. in co-ordinated multipoint or co-operative multiple-input multiple-output [MIMO] systems
• CPC Class Codes: H04B 7/0456 Selection of precoding matrices or codebooks, e.g. using matrices antenna weighting
• CPC Class Codes: H04B 7/0639 Using selective indices, e.g. of a codebook, e.g. pre-distortion matrix index [PMI] or for beam selection
• CPC Class Codes: H04L 1/1854 Scheduling and prioritising arrangements
• CPC Class Codes: H04L 12/18 for broadcast or conference , e.g. multicast
• CPC Class Codes: H04L 43/0823 Errors, e.g. transmission errors
• CPC Class Codes: H04L 5/0007 the frequencies being orthogonal, e.g. OFDM(A), DMT
• CPC Class Codes: H04L 5/0053 Allocation of signaling, i.e. of overhead other than pilot signals
• CPC Class Codes: H04L 5/0055 Physical resource allocation for ACK/NACK for physical mapping arrangements in ARQ protocols H04L1/1861
• CPC Class Codes: H04L 5/0094 Indication of how sub-channels of the path are allocated
• CPC Class Codes: H04L 5/14 Two-way operation using the same type of signal, i.e. duplex
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/1045 Proxies, e.g. for session initiation protocol [SIP]
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 65/611 for multicast or broadcast systems for broadcast or conference H04L12/18; arrangements for broadcast or distribution combined with broadcast H04H20/00; arrangements for broadcast applications with a direct linkage to broadcast information or to broadcast space-time H04H60/00; selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS], H04W4/06
• CPC Class Codes: H04L 65/613 for the control of the source by the destination control signals issued by the client directed to the server or network components specially adapted for selective content distribution H04N21/637
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1076 Resource dissemination mechanisms or network resource keeping policies for optimal resource availability in the overlay network
• CPC Class Codes: H04W 24/02 Arrangements for optimising operational condition
• CPC Class Codes: H04W 24/08 : Testing, supervising or monitoring using real traffic
• CPC Class Codes: H04W 36/0088 : Scheduling hand-off measurements
• CPC Class Codes: H04W 36/0094 : Definition of hand-off measurement parameters
• CPC Class Codes: H04W 36/14 : Reselecting a network or an air interface
• CPC Class Codes: H04W 36/30 : by measured or perceived connection quality data
• CPC Class Codes: H04W 36/36 : by user or terminal equipment
• CPC Class Codes: H04W 36/38 : by fixed network equipment
• CPC Class Codes: H04W 4/70 : Services for machine-to-machine communication [M2M] or machine type communication [MTC]
• CPC Class Codes: H04W 56/001 : Synchronization between nodes
• CPC Class Codes: H04W 68/02 : Arrangements for increasing efficiency of notification or paging channel
• CPC Class Codes: H04W 72/0446 : Resources in time domain, e.g. slots or frames
• CPC Class Codes: H04W 72/1215 : for collaboration of different radio technologies
• CPC Class Codes: H04W 72/1263 : Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
• CPC Class Codes: H04W 72/21 : in the uplink direction of a wireless link, i.e. towards the network
• CPC Class Codes: H04W 72/23 : in the downlink direction of a wireless link, i.e. towards a terminal
• CPC Class Codes: H04W 72/51 : based on terminal or device properties
• CPC Class Codes: H04W 72/52 : based on load
• CPC Class Codes: H04W 74/0808 : using carrier sensing, e.g. carrier sense multiple access [CSMA]
• CPC Class Codes: H04W 76/00 : Connection management
• CPC Class Codes: H04W 76/10 : Connection setup
• CPC Class Codes: H04W 76/11 : Allocation or use of connection identifiers
• CPC Class Codes: H04W 76/12 : Setup of transport tunnels
• CPC Class Codes: H04W 76/15 : Setup of multiple wireless link connections
• CPC Class Codes: H04W 76/20 : Manipulation of established connections
• CPC Class Codes: H04W 76/22 : Manipulation of transport tunnels
• CPC Class Codes: H04W 76/27 : Transitions between radio resource control [RRC] states
• CPC Class Codes: H04W 76/28 : Discontinuous transmission [DTX]; Discontinuous reception [DRX]
• CPC Class Codes: H04W 76/30 : Connection release
• CPC Class Codes: H04W 76/38 : triggered by timers
• CPC Class Codes: H04W 8/005 : Discovery of network devices, e.g. terminals
• CPC Class Codes: H04W 84/045 : using private Base Stations, e.g. femto Base Stations, home Node B
• CPC Class Codes: H04W 84/12 : WLAN [Wireless Local Area Networks]
• CPC Class Codes: H04W 88/02 : Terminal devices
• CPC Class Codes: H04W 88/06 : adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
• CPC Class Codes: H04W 88/08 : Access point devices
• CPC Class Codes: H04W 92/20 : between access points
• CPC Class Codes: Y02D 30/70 : in wireless communication networks

Abstract

Embodiments of an enhanced Node B (eNB) and method for RRC connection establishment for small-data transfers in a 3GPP LTE network are generally described herein. The eNB may receive a small-data RRC connection request message from user equipment (UE) that may include an establishment clause value indicating small-data traffic either with or without mobility. The eNB may send an initial UE setup request message to inform the mobility management entity (MME) that a small-data RRC connection is being established. The eNB may receive an acceptance message from the MME for the small-data RRC connection which may include a reduction of an RRC inactivity timer for fast connection release. The eNB may send an RRC connection reconfiguration message to the UE in response to receipt of the acceptance to establish the small-data RRC connection, the RRC connection reconfiguration message including a measurement information element (IE) when mobility is to be supported.

Claims

1. A method performed by an enhanced node B (eNB) for small-data radio-resource control (RRC) connection establishment in a 3GPP LTE network, the method comprising:

receiving a small-data RRC connection request message from user equipment (UE), the small-data RRC connection request message including an establishment clause value indicating small-data traffic either with or without mobility;

sending an initial UE setup request message to inform a mobility management entity (MME) that a small-data RRC connection for the UE is being established;

indicating to the MME whether or not the small-data RRC connection is to be established with mobility;

receiving an acceptance message from the MME for the small-data RRC connection, the acceptance message including a reduction of an RRC inactivity timer for fast connection release; and

sending an RRC connection reconfiguration message to the UE in response to receipt of the acceptance to establish the small-data RRC connection, the RRC connection reconfiguration message including a measurement information element (IE) when mobility is to be supported.

2. The method of claim 1 wherein indicating whether or not the small-data RRC connection is being established with mobility is part of the initial UE setup request message.

3. The method of claim 1 further comprising adding a field to an attach request message received from the UE to generate the initial UE setup request message, the added field to indicate small data in a dedicated non-access spectrum (NAS) information element (IE), and

wherein the attach request message with the added field is forwarded by the eNB to the MME.

4. The method of claim 1 further comprising communicating small-data packets with the UE over the established small-data RRC connection prior to expiration of the reduced RRC inactivity timer,

wherein the small-data packets have a predetermined maximum size for small-data transfer.

5. The method of claim 4 wherein the UE is machine-type communications (MTC) device.

6. The method of claim 4 wherein the small-data RRC connection request message includes an establishment clause value indicating small-data traffic without mobility.

7. The method of claim 4 wherein the UE is a mobile device including a smart phone.

8. The method of claim 4 wherein the small-data RRC connection request message includes an establishment clause value indicating small-data traffic with mobility.

9. The method of claim 4 wherein the predetermined maximum size for small-data transfer is 1-Kbyte.

10. The method of claim 1 further comprising refraining from including an establishment clause value indicating small-data traffic for RRC connection requests that are not for small-data traffic.

11. An enhanced node B (eNB) arranged for small-data radio-resource control (RRC) connection establishment, the eNB having network interface circuitry arranged to:

receive a small-data RRC connection request message from user equipment (UE), the small-data RRC connection request message including an establishment clause value indicating small-data traffic either with or without mobility;

send an initial UE setup request message to inform a mobility management entity (MME) that a small-data RRC connection for the UE is being established;

indicate to the MME whether or not the small-data RRC connection is to be established with mobility;

receive an acceptance message from the MME for the small-data RRC connection, the acceptance message including a reduction of an RRC inactivity timer for fast connection release; and

send an RRC connection reconfiguration message to the UE in response to receipt of the acceptance to establish the small-data RRC connection, the RRC connection reconfiguration message including a measurement information element (IE) when mobility is to be supported.

12. The eNB of claim 11 wherein the eNB is arranged to indicate whether or not the small-data RRC connection is being established with mobility as part of the initial UE setup request message.

13. The eNB of claim 11 wherein the eNB is further arranged to a field to an attach request message received from the UE to generate the initial UE setup request message, the added field to indicate small data in a dedicated non-access spectrum (NAS) information element (IE), and

wherein the attach request message with the added field is forwarded by the eNB to the MME.

14. The eNB of claim 11 wherein the eNB is further arranged to communicate small-data packets with the UE over the established small-data RRC connection prior to expiration of the reduced RRC inactivity timer,

wherein the small-data packets have a predetermined maximum size for small-data transfer.

15. The eNB of claim 14 wherein the UE is machine-type communications (MTC) device.

16. The eNB of claim 14 wherein the small-data RRC connection request message includes an establishment clause value indicating small-data traffic without mobility.

17. The eNB of claim 14 wherein the UE is a mobile device including a smart phone.

18. The eNB of claim 14 wherein the small-data RRC connection request message includes an establishment clause value indicating small-data traffic with mobility.

19. The eNB of claim 14 wherein the predetermined maximum size for small-data transfer is 1-Kbyte.

20. A non-transitory computer-readable storage medium that stores instructions for execution by one or more processors to perform operations for small-data radio-resource control (RRC) connection establishment, the operations to configure an enhanced node B (eNB) to:

receive a small-data RRC connection request message from user equipment (UE), the small-data RRC connection request message including an establishment clause value indicating small-data traffic either with or without mobility;

send an initial UE setup request message to inform a mobility management entity (MME) that a small-data RRC connection for the UE is being established;

indicate to the MME whether or not the small-data RRC connection is to be established with mobility;

receive an acceptance message from the MME for the small-data RRC connection, the acceptance message including a reduction of an RRC inactivity timer for fast connection release; and

send an RRC connection reconfiguration message to the UE in response to receipt of the acceptance to establish the small-data RRC connection, the RRC connection reconfiguration message including a measurement information element (IE) when mobility is to be supported.