PERSISTENT LOGICAL DATA TUNNELS

• US 20130336305A1
• Filed: 08/30/2011
• Published: 12/19/2013
• Est. Priority Date: 11/05/2010
• Status: Abandoned Application

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Jain, Puneet K., Venkatachalam, Muthaiah, Yan, Xiangying
• Application Number:
  US13/883,761
• Publication Number:
  US 20130336305A1
• Time in Patent Office: Days
• US Class Current: 370/338
• 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/0413 MIMO systems
• CPC Class Codes: H04B 7/0452 Multi-user 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/0482 Adaptive codebooks
• CPC Class Codes: H04B 7/0617 for beam forming
• 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: H04B 7/0652 Feedback error handling
• CPC Class Codes: H04L 1/009 arrangements specific to transmitters
• CPC Class Codes: H04L 1/20 using signal quality detector
• CPC Class Codes: H04L 2001/0093 Point-to-multipoint
• CPC Class Codes: H04L 2001/0097 Relays
• CPC Class Codes: H04L 5/0048 Allocation of pilot signals, i.e. of signals known to the receiver
• CPC Class Codes: H04W 40/24 Connectivity information management, e.g. connectivity discovery or connectivity update
• CPC Class Codes: H04W 52/0209 in terminal devices terminal devices per se H04W88/02
• CPC Class Codes: H04W 52/146 Uplink power control
• CPC Class Codes: H04W 52/34 TPC management, i.e. sharing limited amount of power among users or channels or data types, e.g. cell loading
• CPC Class Codes: H04W 52/365 Power headroom reporting
• CPC Class Codes: H04W 72/0473 the resource being transmission power
• CPC Class Codes: H04W 72/23 in the downlink direction of a wireless link, i.e. towards a terminal
• CPC Class Codes: H04W 76/12 : Setup of transport tunnels

Abstract

Embodiments of the present disclosure describe methods, computer-readable media and system configurations for data delivery among wireless machine-to-machine (“M2M”) and/or machine-type-communication (“MTC”) devices. A method may include receiving, from a plurality of wireless devices (e.g., user equipment or subscriber unit devices), a plurality of uplink data packets, and routing uplink data packets from a subset of the plurality of wireless devices into a logical data tunnel leading to an access gateway. The logical data tunnel may be persistent across sessions of the subset of the plurality of wireless devices. Additionally or alternatively, a method may include incorporating an M2M/MTC payload into data for establishing a connection between a wireless device and a radio access network (“RAN”), so that the wireless device may thereafter enter into an idle mode. Other embodiments may be described and/or claimed.

Claims

1. A computer-implemented method, comprising:

receiving, by a radio access network node (“

RAN node”

), from a plurality of wireless devices, a plurality of uplink data packets; and

routing, by the RAN node, uplink data packets from a subset of the plurality of wireless devices into a logical data tunnel leading to an access gateway;

wherein the logical data tunnel is persistent across sessions of the subset of the plurality of wireless devices.

2. The computer-implemented method of claim 1, wherein the RAN node is an evolved Node B (“

eNB”

), the plurality of wireless devices is a plurality of user equipment (“

UE”

) devices and the access gateway is a serving gateway (“

SGW”

).

3. The computer-implemented method of claim 2, wherein the subset of the plurality of UE is a first subset, the logical data tunnel is a first logical data tunnel, the method further comprising:

routing, by the eNB, uplink data packets from a second subset of the plurality of UE into a second logical data tunnel leading to the gateway;

wherein the second logical data tunnel is persistent across UE sessions of the second subset of the plurality of UE devices.

4. The computer-implemented method of claim 2, wherein UE devices of the first subset are machine-type communication (“

MTC”

) devices.

5. The computer-implemented method of claim 2, further comprising:

receiving, by the eNB, from the gateway through the logical data tunnel, a plurality of downlink data packets; and

routing, by the eNB, a first downlink data packet of the plurality of downlink data packets to a selected UE device.

6. The computer-implemented method of claim 5, further comprising inspecting, by the eNB, the first downlink data packet to ascertain an address of the selected UE device.

7. The computer-implemented method of claim 5, further comprising:

creating, by the eNB, a mapping between a destination network address of the first downlink data packet to an identifier of a bearer; and

routing, by the eNB, downlink data packets addressed to the selected UE device on the bearer based on the mapping.

8. The computer-implemented method of claim 7, wherein the network address is an internet protocol (“

IP”

) address and the identifier of the bearer is a radio access bearer identifier (“

RABID”

).

9. The computer-implemented method of claim 2, further comprising:

receiving, by the eNB, from a first UE device of the plurality of UE devices, data for establishing a connection with the first UE device, wherein the data includes a machine-type communication (“

MTC”

) payload; and

forwarding, by the eNB, the MTC payload through the logical data tunnel.

10. A computer-implemented method, comprising:

receiving, by an evolved Node B (“

eNB”

), from a user equipment (“

UE”

) device, data for establishing a radio resource control (“

RRC”

) connection between the UE device and the eNB, wherein the data includes a machine-type communication (“

MTC”

) payload;

extracting, by the eNB, the MTC payload and a destination from the data for establishing the RRC connection; and

forwarding, by the processor, the MTC payload through a logical data tunnel towards the destination.

11. The computer-implemented method of claim 10, further comprising:

receiving, by the processor, from a plurality of UE devices, a plurality of uplink data packets; and

routing, by the processor, uplink data packets from an MTC subset of the plurality of UE devices into the logical data tunnel;

wherein the logical data tunnel is persistent across UE sessions of the MTC subset of the plurality of UE devices.

12. The computer-implemented method of claim 11, wherein the MTC subset is a first MTC subset, the method further comprising:

routing, by the processor, uplink data packets from a second MTC subset of the plurality of UE into a second logical data tunnel leading to the gateway;

wherein the second logical data tunnel is persistent across UE sessions of the second subset of the plurality of UE devices.

13. The computer-implemented method of claim 10, further comprising:

receiving, by the processor from the gateway through the logical data tunnel, a plurality of downlink data packets; and

routing, by the processor, a first downlink data packet of the plurality of downlink data packets to a selected UE device.

14. The computer-implemented method of claim 13, further comprising:

inspecting the first downlink data packet to ascertain an address of the selected UE device;

or

creating a mapping between a destination network address of the first downlink data packet to an identifier of a bearer.

15. A computer system, comprising:

one or more processors;

a control module configured to be operated by a processor of the one or more processors to;

facilitate establishment of a logical data tunnel between a radio access network node (“

RAN node”

) and one or more access gateways, wherein uplink data packets from a subset of a plurality of wireless devices are multiplexed into the logical data tunnel;

wherein the logical data tunnel is persistent across a plurality of wireless device sessions.

16. The computer system of claim 15, wherein wireless devices of the subset are machine-type communication (“

MTC”

) UE devices.

17. The computer system of claim 15, wherein the plurality of wireless devices are UE devices, the RAN node is an eNB and the one or more access gateways are serving gateways (SGW), and the control module is further configured to receive, from a first UE device of the plurality of UE devices through a non-access stratum (“

NAS”

) signal, machine-type communication (“

MTC”

) data about the first UE device that facilitates mapping of the first UE device to the logical data tunnel between the one or more SGWs and the eNB.

18. The computer system of claim 17, wherein the MTC data about the first UE device that facilitates mapping of the first UE device to the logical data tunnel includes an MTC indication, an MTC subcategory or an MTC service.

19. A user equipment (“

UE”

) device comprising;

a wireless network adaptor; and

a control module configured to transmit, through the wireless network adaptor, to a mobility management entity (“

MME”

) of an evolved universal terrestrial radio access network (“

E-UTRAN”

), via a non-access stratum (“

NAS”

) signal, machine type communication (“

MTC”

) data about the UE device that facilitates mapping of the UE device to a logical data tunnel between an evolved Node B (“

eNB”

) and one or more serving gateways (“

SGW”

);

wherein the logical data tunnel is persistent across UE sessions of a plurality of UE devices and is shared by an MTC subset of the plurality of UE devices.

20. The UE device of claim 19, wherein the control module is further configured to:

incorporate an MTC payload into data for establishing a connection with the E-UTRAN;

transmit, through the wireless network adaptor, the data for establishing the connection to the eNB; and

after transmitting the data, enter into an idle mode.

21. The UE device of claim 19, wherein the data for establishing the connection is an RRCConnectionComplete communication.

22. The UE device of claim 19, wherein the data for establishing the connection includes an MTC UE identity, access class information, an MTC subcategory or MTC service information.

23. The UE device of claim 19, wherein the control module is further configured to encrypt the MTC payload prior to incorporating it into the data for establishing the connection with the E-UTRAN.