The present application relates to mobile routers, in particular mobile routers that enable message routing between a mobile communication network and wireless devices connected to the mobile router.
An existing function today is the “Routing behind MS” feature supported by the Ericsson GGSN-MPG (Gateway GPRS Support Node-Mobile Packet Gateway), where a single UE (User Equipment) acts as a router for several devices and where the Radius served assigns a subnet to this UE/router instead of a single IP address. The subnet is used by the devices connecting to the UE/router. There are also devices that act as gateways with NAT (Network Address Translation) capabilities, where a northbound interface connects with a mobile communication network through HSPA (High Speed Packet Access) or LTE (long term evolution) and a southbound interface is WiFi based and connects with wireless devices. Such a gateway hides the existence of the southbound connected devices, and is seen by the mobile network as a single mobile.
The implementations described above make use of the subscription of the UE router that is connecting to the LTE base station. If a mobile router is used, all the users located on the southbound interface share the subscription of the mobile router.
As another separate concept, EPS (3GPP Evolved Packet System) can support the concept of a donor eNB (donor enhanced NodeB or DeNB for short) supporting the LTE relay. The DeNB has a modified version of the E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) radio interface, the modified version referred to as the Un interface. This allows 3GPP LTE based devices to connect to the eNB through the DeNB.
If Relay model is used instead for UEs connecting via another mobile device, the model assumes that the mobile devices use the E-UTRAN radio interface. As such, it is desirable to achieve the relay function, where each device connects through its own subscription, but uses a different radio interface such as WiFi.
A mobile router is provided with at least two different types of interfaces. One interface is a radio access network interface such as an E-UTRAN interface on its northbound link for connecting the mobile router to a radio access network such as an LTE network. The mobile router also has a non-radio access network interface such as an 802.1x interface on its southbound link. The mobile router acts e.g. as an 802.1x access point (AP) for UEs which connect to the southbound link of the mobile router via WiFi or another radio technology such as Zigbee, or even LTE. The mobile router enables the attached devices to be uniquely authenticated and served by the radio access network. As such, devices connected to the mobile router on its southbound interface (i.e. the non-radio access network interface) are seen as individual devices attaching to the mobile router by the radio access network, and are accessible through respective network-assigned IP addresses. The devices connected to the southbound interface of the mobile router are therefore individually identifiable and serviceable by the radio access network.
According to one embodiment of a method of enabling message routing between a mobile communication network and wireless devices, the method includes: establishing a communication session between a mobile router and the mobile communication network which includes the mobile router being assigned an IP address; authenticating a wireless device to the mobile communication network through the mobile router so that the wireless device is uniquely identifiable to the mobile communication network; and establishing a new packet data network (PDN) connection between the wireless device and the mobile communication network over the communication session established with the mobile communication network, based on an IP address uniquely assigned to the wireless device by the mobile communication network.
According to one embodiment of a mobile router for enabling message routing between a mobile communication network and wireless devices, the mobile router includes one or more processing circuits operable to: establish a communication session with the mobile communication network which includes the mobile router being assigned an IP address; authenticate a wireless device to the mobile communication network so that the wireless device is uniquely identifiable to the mobile communication network; and establish a new packet data network (PDN) connection between the wireless device and the mobile communication network over the communication session based on an IP address uniquely assigned to the wireless device by the mobile communication network.
Those skilled in the art will recognize additional features and advantages upon reading the following detailed description, and upon viewing the accompanying drawings.
The elements of the drawings are not necessarily to scale relative to each other. Like reference numerals designate corresponding similar parts. The features of the various illustrated embodiments can be combined unless they exclude each other. Embodiments are depicted in the drawings and are detailed in the description which follows.
The processing circuit(s) 102 included in the mobile router 110 can include any type of hardware and/or software suitable for implementing these procedures. For example, the processing circuit(s) 102 may include one or more baseband processors, microprocessors, microcomputers, digital signal processors (DSPs), special-purpose hardware, such as an application specific integrated circuit (ASIC) and programmable logic devices, controllers, memory, firmware, software, and/or any combination thereof.
Providing access to the mobile communication network 110 via the mobile router 100 puts a minimum requirement on the client wireless devices 120 in terms of authentication and encryption of the traffic. The mobile router 100 has at least two different types of interfaces to provide such access. One interface is a non-radio access network interface such as an 802.1x interface (e.g. WiFi) on its southbound link i.e. the link between the mobile router 100 and the wireless devices 120. The mobile router 100 also has a radio access network interface such as an E-UTRAN interface on its northbound link i.e. the link between the mobile router 100 and the mobile communication network 110. According to this embodiment, the mobile router 100 acts as an 802.1x access point (AP) for the wireless devices 120 which connect to the mobile router 100 via WiFi or other radio technology such as Zigbee or even LTE.
The wireless device attach and authentication procedures enabled by the mobile router 100 permit the attached wireless devices 120 to be uniquely authenticated and served by the mobile communication network 110. As such, wireless devices 120 connected to the mobile router 100 on the router southbound interface (i.e. the non-radio access network interface) are seen as individual devices attaching to the mobile router 100 by the mobile communication network 110, and are reachable through respective network-assigned IP addresses. In one embodiment, the IP addresses uniquely assigned to the respective wireless devices 120 are derived from a subnet allocated to the mobile router 100 by the mobile communication network 110.
The mobile router 100 can serve different types of wireless devices 120. For example, the mobile router 100 can serve wireless devices 120 such as regular computing devices which use WiFi access technology, including mobile phones with WiFi interfaces. Another type of wireless device 120 served by the mobile router 100 are low power and/or limited functionality devices which attach to the mobile router 100 using WiFi or another radio access technology, including MTC (machine-type communication) devices. Each device 120 connected to the mobile router 110 on the southbound interface of the router 100 is visible at the network level, and the mobile communication network 110 provides a set of services associated with the subscription of the corresponding individual device 120.
Operation of the mobile router 100 is described next in more detail in the context of an LTE radio access network 110, but can be readily applied to any radio access technology. As such, the mobile router 100 is also referred to as MLR (mobile LTE router). The MLR 100 handles the radio link toward the LTE radio network 110, including e.g. physical layer, layer-2 and RRC (radio resource control) functionality, in order to wirelessly connect to a base station 112 such an eNB (enhanced NodeB) of the LTE radio network 110. The MLR 100 also terminates the EPS bearers, keeping the TFTs (traffic flow templates) for mapping different IP flows from different wireless devices 120 connected to the MLR 100 on the southbound interface to the correct EPS bearer.
In
The MLR 100 provides network connectivity to the wireless devices 120 through its northbound (e.g. LTE based) interface. For Wi-Fi based UE devices 120 such as mobile phones with Wi-Fi access, the MLR 100 acts as a relay/inter-working function with the mobile core network 110. In one embodiment, the MLR 100 creates sub-sessions in addition to the main session the MLR 100 created with the LTE network 110. These sub-sessions represent or correspond to new PDN connections established between the UE devices 120 and the LTE network 110 over the communication session established with the LTE network 110.
UE A connects to the southbound interface of the MLR 100 using LTE radio access technology and the MLR 100 performs authentication through the use of a SIM (subscriber identity module) card, or a soft SIM for example (Step 2 in
After a UE is authenticated, the MLR 100 sends a PDN connectivity request to the MME 114 via the eNB 112. The MME 114 generates a create session request which is forwarded to the PGW 118 via the SGW 116. The SGW 116 routes and forwards user data packets and acts as a mobility anchor for the user plane during inter-eNodeB handovers and as an anchor for mobility between LTE and other 3GPP technologies. The PGW 118 provides connectivity from UEs to external PDNs 130 by acting as a point of exit and entry of traffic for the UEs.
In response to the create session request, the PGW 118 and PCRF 120 establish an IP-CAN (IP Connectivity Access Network) session which enables a UE to begin a session such as voice telephony, streaming, etc. The PGW 118 sends a create session response to the SGW 116, which in turn forwards the response to the MME 114. The MME 114 generates a PDN connectivity accept message which indicates the IP-CAN session has been established, and sends the accept message to the eNB 112. In response, the eNB 112 performs bearer setup and initiates RRC connection reconfiguration with the MLR 100. The MLR 100 likewise initiates RRC connection reconfiguration with the corresponding UE. Upon completion of the RRC connection reconfiguration, direct transfer of messages is permitted from the UE to the MLR 100 on the router southbound interface and between the MLR 100 and the eNB 112 on the router northbound interface. The eNB 112 notifies the MME 114 that PDN connectivity is complete. In each case, sub-sessions associated with each LTE UE are anchored to the main MLR session. The MME 114 and SGW 116 can perform bearer modification if desired, and bearer enforcement and mapping may be different depending on the particular device.
Devices connecting to the MLR 100 through Wi-Fi can perform authentication through the use of a SIM (subscriber identity module) card, or a soft SIM for example. The MLR 100 can authenticate these devices using 802.1x, e.g. as illustrated by the sequence of requests and responses shown in region 510 of
In general, IP-CAN establishment and PDN connectivity between the MLR 100 and the LTE network 110 can be handled as previously described herein with reference to
Features related to QoS mapping are performed at the MLR level. Different traffic flows are assigned different QoS based on policies associated with the device/user. The MLR 100 still carries and relays sub-session NAS messages, belonging to multiple devices attached to the southbound interface of the MLR 100.
The embodiments described herein provide inter-working functions which allow a mobile router to initiate on behalf of an attached device sub-session NAS messages which result in a session being created for the device in the mobile communication network. When a southbound device wants to establish a connection to a different PDN, the mobile router first establishes a connection to that PDN, as the sub-sessions are anchored to the main router session with the mobile network as previously described herein. Individual LTE and/or Wi-Fi devices can therefore access an LTE or other mobile communication network using a Wi-Fi or similar link with their respective subscription credentials. These devices therefore do not need to use the main gateway subscription associated with the mobile router. All subscription policies are available to the individual devices, mapped to the WiFi link characteristics.
Spatially relative terms such as “under”, “below”, “lower”, “over”, “upper” and the like, are used for ease of description to explain the positioning of one element relative to a second element. These terms are intended to encompass different orientations of the device in addition to different orientations than those depicted in the figures. Further, terms such as “first”, “second”, and the like, are also used to describe various elements, regions, sections, etc. and are also not intended to be limiting. Like terms refer to like elements throughout the description.
As used herein, the terms “having”, “containing”, “including”, “comprising” and the like are open ended terms that indicate the presence of stated elements or features, but do not preclude additional elements or features. The articles “a”, “an” and “the” are intended to include the plural as well as the singular, unless the context clearly indicates otherwise.
It is to be understood that the features of the various embodiments described herein may be combined with each other, unless specifically noted otherwise.
Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that a variety of alternate and/or equivalent implementations may be substituted for the specific embodiments shown and described without departing from the scope of the present invention. This application is intended to cover any adaptations or variations of the specific embodiments discussed herein. Therefore, it is intended that this invention be limited only by the claims and the equivalents thereof.
This application claims priority from U.S. Provisional Patent Application No. 61/444,584 filed on 18 Feb. 2011, the content of said application incorporated herein by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
20100103845 | Ulupinar et al. | Apr 2010 | A1 |
Entry |
---|
Thubert P. et al: “Mobile Network Prefix Delegation; draft-ietf-nemo-prefix-delegation-02. txt”, Internet Engineering Task Force (IETF), Aug. 21, 2007, whole document. |
“Relay architectures for E-UTRA (LTE-Advanced) (Release 9) 3GPP TR 36.806”, 3RD Generation Partnership Project (3GPP), Mar. 2010,, sections 4.2.2; 4.2.4.1; 4.2.4.4. |
3GPP TS 23.402 version 9.7.0 Release 9 (Dec. 2010) 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements for non-3GPP accesses, the whole document. |
Number | Date | Country | |
---|---|---|---|
20120215931 A1 | Aug 2012 | US |
Number | Date | Country | |
---|---|---|---|
61444584 | Feb 2011 | US |