Wireless router apparatus, subscriber device, method for network-agnostic wireless routing and method for wireless communications

Wireless router device for cross-network wireless routing, user mobile device and method, and wireless communication method

WIRELESS ROUTER APPARATUS, SUBSCRIBER DEVICE, METHOD FOR NETWORK-AGNOSTIC WIRELESS ROUTING AND METHOD FOR WIRELESS COMMUNICATIONS

<b>priority</b>

The present application claims the benefit of commonly-owned U.S. Patent Application Serial No. 14/156,174, filed on Jan. 15, 2014, the entire disclosure of which is hereby incorporated by reference. U.S. Provisional Patent Application Serial No. 61/849,087 to Network-agnostic Wireless Router (NAWR) and 61/848,950 entitled "Wi-Fi Over LTE Network (WoLTEN)" filed on January 16, 2013. The entire contents of each of the foregoing are incorporated herein by reference.

The present invention relates generally to the field of wireless communications and data networking. More particularly, in an exemplary aspect, the present invention is directed to a method and apparatus for a wireless router across a network.

<u style="single">Related application</u>

The present application is related to co-owned and co-pending U.S. Patent Application Serial No. 14/156,339, filed on Jan. 15, 2014, entitled "METHODS AND APPARATUS FOR HYBRID ACCESS TO A CORE NETWORK", the entire contents of which is incorporated herein by reference.

<u style="single">background</u>

1. Technical field

The present invention generally relates to the field of wireless communications and data networks. More particularly, in an exemplary aspect, the present invention is directed to methods and apparatus for inter-network wireless routers.

2. Related technical description

The advent of the name "smartphone" technology has accelerated the rapid growth of mobile data services, which has led to a dramatic increase in the popularity of high-speed data transmission and mobile services. Coupled with increased penetration, customers' expectations for better, more reliable service and network performance have increased. To meet customer needs, operators have deployed new access technologies such as Long Term Evolution (LTE). However, in order to improve network reliability and coverage (POC), operators are still looking for viable solutions, especially in indoor environments. Operators have traditionally used repeaters and distributed antenna systems (DAS) to provide indoor coverage. However, as repeaters and DAS solutions do not support a variety of required functions, such as Multiple Input Multiple Output (MIMO) and high-order modulation, they are losing their commercial momentum.

Recently, the 3rd Generation Partnership Project (3GPP) community, supported by operators, began to consider and develop standards for a new class of products called "servo machines." (See example, published in March 2010 under the heading "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Relay architectures for E-UTRA (LTE-Advanced) (Release 9) TR 33.6806 V9.0.0, the entire contents of which are incorporated herein by reference.) unfortunately, due to the servo The handset typically requires twice the spectrum to relay and maintain maximum throughput for a given LTE enhanced Node B (eNB) base station, so servo performance may be limited by the available spectrum.

In an alternative scenario, a so-called "wireless router" can be used to provide Wi-Fi.^TMhot spot. Wireless routers use wireless cellular connections (eg, LTE, High Speed Packet Access (HSPA), etc.) instead of wired backhaul (eg, Digital Subscriber Line (DSL), cable modem, etc.). Compared with repeaters, fourth-generation (4G) wireless routers offer considerable advantages; in particular, Wi-Fi hotspots operate in unlicensed (license-free) bands with large amounts of spectrum (industrial science) And medical (ISM) and unlicensed National Information Infrastructure (U-NII) bands provide near 0.5 GHz spectrum).

Although wireless routers have some advantages over servos, an important issue with wireless router operation is that the cellular service terminates at the wireless router rather than the user's user mobile device (UE) (eg, a handset, or other wireless communication device). More directly, the network sees the wireless router as the destination. As described in more detail below, this mode of operation introduces new problems such as security, billing, and the like. In addition, the Wi-Fi hotspot media access control (MAC) and physical (PHY) layers are designed to operate in "self-organizing" uncoordinated networks that are not like cellular systems, where interference sources and their operation are inconsistent. Or it is not planned.

In view of these shortcomings, wireless routers need improved methods and devices. These improvements will ideally provide one or more inter-network operations, end-to-end networks, and use of different frequency bands (licensed and/or unlicensed) for radio security, flexibility, and, for example, quality of service (QoS). Consistent service performance.

More particularly, the present invention satisfies the above needs by providing an apparatus and method for improving cross-network wireless router services.

In a first aspect of the invention, a method of wireless routing across a network is disclosed. In one embodiment, the method includes receiving one or more connection requests from a respective one or more user mobile devices via a wireless local area network (WLAN), the one or more connection requests identifying the corresponding one or more a cellular network; allocating storage space to a user mobile device corresponding to the connection request; adjusting to a cellular network identified within the connection request; and transacting data received over the adjusted cellular network with the user mobile device through the access channel.

In one variation, the method includes determining that the connection request can be serviced; and based on the determining, performing an action of allocating, adjusting, and trading.

In another variation, the determining includes determining an available storage space. In an example, the determining includes successfully adjusting to the identified one or more cellular networks. In another such example, the decision includes determining if a limited set of cellular network radio components has at least one cellular network radio component available.

In yet another variation, the WLAN is configured to operate in an open mode that does not require any access control methods. Alternatively, the WLAN is used to operate in a closed mode and the closed mode is used to perform at least one access control function.

In an example implementation, the one or more cellular networks include Long Term Evolution (LTE), which is used to authenticate the user identification module (SIM) inherent to the user mobile device via a WLAN provided by the inter-network router. The Key Agreement (AKA) program performs access control.

In a second aspect of the invention, a wireless router device for providing an inter-network connection is disclosed. In an embodiment, the wireless router device includes: one or more a first radio interface, one or more first interfaces for connecting to one or more wireless data networks, each of the one or more wireless data networks for restricted access to a corresponding user mobile device group; a second radio interface for providing an open wireless network; a processor; and a non-transitory computer readable medium for communicating with the processor communication material. In this embodiment, the non-transitory computer readable medium includes one or more instructions that, when executed by a processor, cause an inter-network wireless device to: respond to a mobile device from a user connected to an open wireless network Receiving a connection request for a wireless data network; providing an access channel between the user's mobile device and the wireless data network, the access channel being capable of exchanging encrypted data payloads without modification.

In one variation, the wireless router device further includes a buffer to support multiple data pipeline instances.

In a second variant, the second interface is for providing access to a wireless local area network (WLAN) and the one or more first radio interfaces are for connecting to one or more long term evolution (LTE) cells Data network.

In another variation, the encrypted data payload includes access control information to identify the user mobile device as one of the user mobile device groups corresponding to the wireless data network.

In still other variations, at least two of the one or more first radio interfaces are used to use different radio technologies.

In a third aspect of the invention, a method of connecting to a first data network by a cross-network wireless router is disclosed. In one embodiment, the method includes: discovering an inter-network wireless router to provide an inter-network connection; transmitting a connection request; the connection request identifying the first data network; and allowing the connection through the connection in response to receiving the connection permission Identifyed access channel, start And at least one access control program of the first data network. At least one access control program includes transmitting an encrypted data payload for secure authentication with the first data network.

In one variation, the wireless network includes an open wireless local area network (WLAN) and the first data network includes a Long Term Evolution (LTE) cellular data network. In one example, the access control program includes an Authentication and Key Agreement (AKA) between a User Identity Module (SIM) of the user's mobile device and an Authentication Center (AuC) of the LTE cellular data network. In another example, the access channel is configured to receive an encrypted data payload over the WLAN and provide an encrypted data payload to the soft layer of the LET software stack. In this case, the bulk layer includes a Radio Link Control (RLC) layer of the LTE software stack.

In another variation, the connection allows for a separate buffer identifier associated with the access channel.

In a fourth aspect of the invention, a user mobile device for connecting to a first network via a cross-network wireless router is disclosed. In one embodiment, the user mobile device includes: a radio interface for connecting to an inter-network wireless router, an inter-network wireless router for connecting to the first network; a processor; and including one or more instructions Non-transitory computer readable media. In one embodiment, the one or more instructions, when executed by the processor, cause the user to move the device: to transmit a connection request to the first network to the inter-network wireless router; and in response to the connection allowed reception, by access The channel trades one or more encrypted data payloads.

In one variation, the one or more encrypted data payloads include an encryption challenge and response test to establish secure communication with the first network.

In a fifth aspect of the invention, a method for wireless communication includes first and second communication systems, describing a first communication having at least a first node and a second node in communication with each other system. In one embodiment, the method includes modifying a protocol stack of a first node, the modifying comprising splitting the protocol stack into a first partial layer and a second partial layer, the first partial layer and the second partial layer being used to trade one Or a plurality of data payloads; performing a first partial layer in the first node and causing the third intermediate node to perform a second partial layer; and communicating one or more data payloads through the second communication system. In another embodiment, the connected second access network does not modify one or more data payloads. In a third embodiment, the combination of the first partial layer and the second partial layer is performed by the third intermediate node to be able to communicate with the second node in the first communication system.

In one variation, the first node comprises a handset, the second node comprises a cellular network base station, and the second communication system is a wireless local area network (WLAN). In another variation, the handset includes a User Mobile Equipment (UE), the base station includes a Long Term Evolution (LTE) Enhanced Node B (eNB), the cellular network includes an LTE 4G system, and the WLAN includes Wi-Fi network. In a further variation, the splitting occurs between a Radio Link Control (RLC) layer and a Medium Access Control (MAC) layer of the LTE protocol stack.

In yet another variation, the communication system provides an access channel between the first partial layer and the second portion in an unsecure open mode. Alternatively, the second communication system provides an access channel between the first partial layer and the second partial layer in a secure closed mode.

In an example implementation, the key used to encrypt the data service with the third intermediate node or the certificate used to authenticate the third intermediate node of the second communication system is provided to the first node through the second node in the first communication system. Node and third intermediate node.

In another implementation, the third intermediate node is a cross-network wireless router (NAWR). In one implementation, the first node is configured to execute a NAWR software application, and/or the third node is to perform a network NAWR proxy application. In this case, in NAWR soft There is a NAWR dedicated control channel between the body application and the NAWR agent. In one such implementation, the NAWR software application includes multiplexing and demultiplexing (MUX/DeMUX) buffers; in other implementations, the NAWR proxy application includes multiplexing and demultiplexing (MUX/DeMUX) buffers.

In some variations, the NAWR is further used to communicate with one or more microphones. In other variations, the NAWR is further used to simultaneously communicate with one or more base stations, at least some of which have different Public Land Mobile Networks (PLMNs).

Other features and advantages of the present invention will be immediately apparent from the following description of the drawings and exemplary embodiments.

<p>100Network structure</p><p>102LTE coverage area</p><p>104Wi-Fi coverage</p><p>106Wireless Router</p><p>108First link</p><p>Second link of 110</p><p>112User Mobile Equipment (UE)</p><p>114eNB</p><p>106ALTE UE-R Module</p><p>106B Wi-Fi AP Router Software</p><p>106CRouter software</p><p>300Logical representation of different logical entities</p><p>302Service Gateway</p><p>304Public Data Network (PDN) Gateway (PGW)</p><p>400 logical representation</p><p>402Mobile Management Entity</p><p>500Inter-network wireless router device</p><p>502 Foundation</p><p>504Processing Subsystem</p><p>506Management subsystem</p><p>508Memory subsystem</p><p>510, 512 modem</p><p>600Inter-network wireless router device</p><p>610A, 610B Modem</p><p>700User mobile devices</p><p>702Subunit</p><p>704Processing subsystem</p><p>706Management subsystem</p><p>708Memory subsystem</p><p>710 Radio subsystem</p><p>710A, 710BModem Subsystem</p><p>712User I/O</p><p>714identification module</p><p>800 Agreement stacking</p><p>802U-NII band</p><p>804ISM band</p><p>806MAC layer</p><p>808Application software</p><p>902Communication</p><p>904 first application</p><p>906Second application</p><p>1202, 1204Two-way auxiliary control channel</p><p>1206Application</p><p>1208Agent</p><p>1210 Buffer and MUX/DeMUX</p><p>1212MU buffer and MUX/DeMUX</p><p>1300Generalized procedure for the discovery, initiation and configuration of sessions</p><p>1302User mobile devices discover enabled wireless networks</p><p>1304 Establish access channels between user mobile devices and network operators</p><p>1306NAWR agent determines if a NAWR connection can be established</p><p>1308Return to provide connection parameters to the NAWR APP</p><p>1310Connecting transaction data via NAWR</p><p>1402NAWR APP initializes and sets its internal variables and flags to default values</p><p>1404Enable LTE modem and search for available LTE eNBs and networks</p><p>1406Enable Wi-Fi modem and look for nearby Wi-Fi AP</p><p>1408 Registration</p><p>1410 Ask the AP to find out if it has the right NAWR agent</p><p>1412Determining whether a better Wi-Fi access point or LTE eNB is available</p><p>1414 Looking for NAWR-supported Wi-Fi APs</p><p>1502 Initialize and set its internal variables and flags to default values</p><p>1504NAWR agent determines if the connection request can be serviced</p><p>1506NAWR Agent Introduces NAWR Agreement Stack for New Users</p><p>1508NAWR agent check to determine if the user has terminated the connection</p><p>1510 Send message "Rejected due to overloaded access"</p>

1 is a block diagram representation of an example implementation that includes a network structure that provides network access with Long Term Evolution (LTE) cellular coverage operating in conjunction with Wi-Fi coverage.

2 is a logic block diagram of various logical software entities configured in an example implementation of a wireless router useful in accordance with various implementations described herein.

Figure 3 is a logical software diagram representation of various logical entities of a user data plane protocol stack associated with the exemplary embodiment of the network structure of Figure 1.

Figure 4 is a logical software diagram representation of various logical entities of a control plane protocol stack associated with the exemplary embodiment of the network structure of Figure 1.

Figure 5 is a logic block diagram of an example implementation of an inter-network wireless router in accordance with the different principles described herein.

Figure 6 is a logic block diagram of an example implementation of a dual user and/or dual band cross-network wireless router in accordance with various principles described herein.

Figure 7 is a logic block diagram of an example implementation of a user mobile device in accordance with various principles described herein.

Figure 8 is a logic block diagram showing an example manner of an IEEE 802.11n PHY (L1) and MAC (L2) protocol stack 800 that is useful in conjunction with various aspects of the present invention.

Figure 9 is a logical representation of an example implementation of a Wi-Fi pipe formed by an example cross-network wireless router (e.g., as shown in Figure 5) and an example user mobile device (e.g., as shown in Figure 7); Figure 10A is a logical software diagram representation of a prior art LTE software user plane protocol stack.

Figure 10B is a logical software diagram representation of a prior art LTE software control plane protocol stack.

Figure 11 is a logical software diagram representation of an example implementation of a hybrid Wi-Fi pipe protocol stack running under the Radio Link Control (RLC) layer, with Radio Link Control (RLC) replacing the LTE MAC and L1 layers.

Figure 12 is a logical software representation of the overall protocol stack structure (including the user plane and control plane) for the user mobile device and the inter-network wireless router.

Figure 13 is a logic flow diagram for the discovery, start and structure, and generalized methods of a mobility management session.

Figure 14 is a logic flow diagram illustrating an example implementation of a cross-network wireless router (NAWR) connection initialization of an example NAWR application (APP) executing on a user mobile device (UE-User or UE-S Shorthand).

Figure 15 is a logic flow diagram illustrating an example implementation of a cross-network wireless router (NAWR) connection initialization of an example NAWR agent executing on a cross-network wireless router.

Referring now to the drawings in which like reference numerals

The terms "cellular" and/or "wireless" as used herein are any wireless signals used to refer to voice, video, data, or any form of communication, including but not limited to Wi-Fi (IEEE 802.11 and all its derivatives, Such as "b", "a", "g", "n", "ac", etc.), Bluetooth, 3G (eg, 3GPP, 3GPP2, and UMTS), 4G (LTE, LTE-A, and other LTE derivatives) , WiMax), HSDPA/HSUPA, TDMA, CDMA (eg, IS-95A, WCDMA, etc.), FHSS, DSSS, GSM, PAN/802.15, 802.20, narrowband/FDMA, OFDM, PCS/DCS, emulated cellular, CDPD, satellite Systems, millimeter wave or microwave systems, acoustics, and infrared (ie IrDA) and proprietary wireless communication systems.

Also, the term "network" as used herein generally refers to any form of circuit-switched or packet-switched communication network, or other network, including but not limited to data networks (including Wi-Fi, MAN, PAN, WAN). , LAN, WLAN, piconet, piconet, internet and intranet), satellite networks, cellular networks, and telecommunications networks.

Overview

In an exemplary aspect of the invention, a cross-network wireless router is disclosed. In one embodiment, the inter-network wireless router is configured to provide access channels (eg, so-called "Wi-Fi pipes") over a first network (eg, a Wi-Fi network) and convert the data payload at The second network (for example, an LTE network) transmits. In one implementation, an inter-network wireless router provides access channels or tubes that allow users to connect to the appropriate network using their own identification modules. As described in more detail elsewhere herein, data or other payloads (e.g., datagrams, etc.) are channeled through Wi-Fi hotspots and replicated over a suitable cellular air interface. Since the wireless router only provides access channels (not as an end point), the authentication, authorization, and accounting mechanisms are all in the user's identity. Modules (eg, SIM, USIM, CSIM, RUIM, etc.) are processed directly in the identification module instead of the router. In fact, the present invention allows a wireless router to not require its own identity module (rather than supporting legacy mode, etc., if it exists).

The wireless router disclosed by the present invention conveniently supports a plurality of different networks freely, thereby providing "inter-network" access to the network of mobile devices that are preferentially selected by the user. In some cases, a cross-network wireless router can simultaneously establish channel access to multiple technologies (eg, LTE networks and CDMA networks), allowing multiple users of different networks to use the same hotspot. Since the inter-network router establishes a channel for the user's device transaction only through Wi-Fi access, the user mobile device maintains control plane access. The control plane specifically enables the user's mobile device to properly manage service requirements, such as quality of service (QoS) and the like.

Various other advantages of the disclosed embodiments are described in more detail below.

Detailed description of example embodiments

Example embodiments of the present invention will now be described in detail. While these embodiments are primarily discussed in the context of a fourth generation long term evolution (4G LTE) wireless network in combination with Wi-Fi hotspot (IEEE 802.11n) operation, one of ordinary skill in the art will recognize the present invention and Not limited to this. In fact, aspects of the present invention are useful for any wireless network that can benefit from the inter-network wireless routing described herein.

Example network structure

Referring now to FIG. 1, FIG. 1 depicts an example implementation of a network architecture including network access using a Long Term Evolution (LTE) cellular overlay 102 operating in conjunction with Wi-Fi coverage (eg, IEEE 802.11n) 104. A block diagram representation of the way. The LTE coverage area 102 operates within the licensed band of the network operator, while the Wi-Fi hotspot (generated by the 4G wireless router 106) In the ISM (2 GHz) and / or U-NII (5 GHz) bands. As shown, the wireless router 106 establishes a first link 108 with the LTE module through its LTE UE-R (UE-Router or UE-R Shorthand) module, and through its LTE UE-S (UE-User) mode The group maintains a second link 110 to the user mobile device (UE) 112. The UE 112 is an LTE device (such as a smart phone) that can use Wi-Fi.

As shown in FIG. 2, an example implementation of wireless router 106 includes three distinct modules: (i) LTE UE-R (UE-Router) module 106A for communicating with LTE eNB 114, (ii) A Wi-Fi AP module 106B communicating with an LTE UE-S (UE-User) module, the LTE UE-S module being part of the UE 112, and (iii) for communicating with LTE via translation, flow control, etc. The router software 106C that exchanges data between the UE-R 106A and the Wi-Fi AP 106B. In operation, wireless router 106 mediates between LTE network eNB 114 and UE 112. Wireless router 106 receives datagrams from eNB 114, and converts datagrams within hotspots 104 for transmission, and vice versa.

The advantages of the example network architecture of Figure 1 include: (i) a reduction in the number of licensed spectrum required to support coverage, (ii) a relatively low-cost deployment (for networks and users), and (iii) self-organizing deployments. , and (iv) high throughput.

As a short narration, spectrum (or bandwidth) is a rare and expensive resource cost for network operators. While most network operators have ~10-20 Hz bandwidth (maximum), Wi-Fi networks running over unlicensed bands span hundreds of MHz of spectrum. Wi-Fi systems supporting the Industrial Science and Medical (ISM 2.4GHz) and Unlicensed National Information Infrastructure (U-NII 5GHz) bands will have access to approximately 80MHz spectrum on the ISM and 450MHz on the U-NII band (no Includes outdoor band). Initially network operators were concerned about the exemption of licenses (exempt) spectrum The negative impact of usability and quality and the user experience, however, unlicensed technology (such as Wi-Fi) continues to provide a stable and efficient connection, even in crowded and hostile situations.

Unlike cellular technology, most existing Wi-Fi products are based on ad hoc deployments. Wi-Fi networks typically use carrier sense multiple access with collision avoidance (CSMA/CA) and a specially designed non-competitive (point coordination function (PCF) or distributed coordination function (DCF)) using ad hoc deployment. Media Access Control (MAC) protocol. Self-organizing deployment reduces the burden on network operators for network planning, deployment, and maintenance.

Furthermore, cellular technology was originally designed to support a more equal business model (for example, providing a large number of users with relatively low-speed voice capabilities), and Wi-Fi technology is designed to support high throughput from concepts. Existing Wi-Fi devices typically have data rates in excess of 300 Mbits/sec; future revisions promise Gbits/sec data rates.

Wi-Fi technology and devices have been manufactured for over a decade, and their components are commercially available and can be utilized at relatively low cost. Many existing consumer devices have incorporated Wi-Fi technology, so the lowest cost of the device (for network operators and users) does not present any significant barriers to deployment.

To illustrate why existing solutions that incorporate wireless routers into cellular networks are subject to certain unfavorable factors, a brief description of existing software is useful. Referring now to FIG. 3, a third diagram illustrates a logical representation 300 of different logical entities of the example network structure 100. As shown, Figure 3 includes five (5) logical entities: User UE (UE-S) 112, wireless router 106, LTE eNB 114, Serving Gateway (SGW) 302, and Public Data Network (PDN) Gateway. (PGW) 304. Each logical entity is represented by a logical software stack that represents the layering characteristics of the communication, which is well understood in the art. For example, Media Access Control (MAC) of UE-S 112 The layer communicates with the equivalent MAC entity of the wireless router 106 or the like. The layered nature of the communication stack is a universally feasible abstraction for simplifying software implementation. While the communication stack of FIG. 3 is an illustrative example of a user plane protocol stack for bidirectional transaction data, those of ordinary skill in the art will appreciate that the description herein is by no means limiting; other implementations may be used in the related art.

In the context of Figure 3, the termination point of the LTE network is the LTE UE-R module 106A of the wireless router. In particular, the LTE UE-R module 106A is associated with a Universal Subscriber Identity Module (USIM) that uniquely identifies the wireless router 106 to the LTE network. Logical components outside the endpoint (eg, Wi-Fi AP module 106B, and router software 106C) cannot affect cellular connections. More directly, the UE-S 112 is unaware of the requirements and performance of the underlying LTE connection 108 used by the wireless router 106.

Figure 4 illustrates a logical representation 400 of the different logical entities of the control plane protocol stack associated with the data plane protocol stack of Figure 3. As illustrated in FIG. 4, the control plane extends only between the LTE UE-R module 106A of the wireless router 106 and the mobility management entity (MME) 402 of the LTE network. There are no UE-S 112 logical entities associated with the LTE Control Plane Protocol.

Due to this abstraction, the LTE UE-R 106A module can be used with a generic radio bearer; this can result in an incorrect match with the requirements of the UE-S 112. For example, the LTE UE-R may configure an LTE link for web browsing that does not support the UE-S 112 streaming application. This problem is further aggravated when the wireless router serves multiple UE-Ss 112. For similar reasons, wireless routers use their own USIM to access the LTE network. Since the USIM is associated with a wireless router (not a user), the LTE service is network specific (ie, limited to the USIM-related network) and billing is associated with the wireless router USIM (which is detrimental to the public and public operations). Further deteriorating user controls, Wi-Fi hotspot security, and access control options are limited. Wi-Fi hotspots can be "open" (anyone can Free access to the network) or manual discovery, authentication and registration. Both configurations are not available for public and public operations.

Example cross-network wireless router

As used herein, the term "cross-network" refers to, but is not limited to, devices that can operate on multiple networks; it will be appreciated that the device itself may be limited by physical features (eg, physical transceivers, available software, etc.) Network set. For example, a device that supports LTE or CDMA connectivity but does not support WiMAX may be considered "inter-network" for LTE or CDMA.

In accordance with an example embodiment of the present invention, an inter-network wireless router does not require an identification module to provide a network connection (eg, a wireless router does not use a SIM/USIM connection to a 3GPP network (eg, LTE, UMTS, etc.), does not use RUIM/CSIM is connected to a CDMA network, etc.). Instead, cross-network wireless routers provide access channels or tubes that allow users to connect to the appropriate network using their own identification modules. As used herein, the term "access channel" or "tube" refers to a network technology that embeds a second access network in a network protocol stack of a first access network, through a connected second access network. The first access network protocol layer to be connected is logically connected to the subsequent layer, wherein the connected second access network does not modify, change, copy, delete, etc. the first access network protocol layer and the foregoing The data payload exchanged between subsequent layers. Access channel establishment enables the transmission of data through hybrid networks, the transmission of secure data over unsecured networks, and the like.

For an example implementation of an access channel provided by a wireless router, transactions with the user identity module are passed through a Wi-Fi hotspot and replicated on a suitable cellular air interface. Since the wireless router provides an access channel in this embodiment, the authentication, authorization, and charging mechanisms are both in the EPC network and the user identity module located on the UE-S 112 (eg, SIM, USIM, CSIM, RUIM) Wait directly). In fact, one of ordinary skill in the relevant art will recognize that the present invention allows a wireless router to not require its own identity module (rather than, for example, supporting legacy mode, etc.).

Similarly, since the inter-network wireless router does not register with any single network operator, the wireless router is simultaneously (some traditional and/or contractual restrictions can prevent devices from registering simultaneously on multiple networks) to freely support multiple different networks. Road (for example, Public Land Mobile Network (PLMN)). For example, with Wi-Fi hotspot performance, cross-network wireless routers can simultaneously establish channel access to LTE networks and CDMA networks, allowing users of different networks to use the same hotspot.

Finally, since the inter-network router only establishes an access channel to the user's device transaction, the user mobile device maintains control plane access in the illustrated embodiment. Control plane access enables user mobile devices to properly manage service requirements, such as quality of service (QoS). For example, a mobile device attempting to transmit video may correctly indicate an LTE network; in particular, it is noted that prior art wireless routers are not aware of the application conditions, and prior art routers are not able to effectively negotiate QoS requirements for their serving devices.

As described in more detail below (see, for example, the exemplary user mobile device below), various embodiments of the present invention can be used with middleware software located in the user UE (UE-S) device or other device. In some embodiments, the middleware software can be downloaded (eg, by a user, or a configuration service or a craftsman or entity), or the middleware software can be preloaded during device manufacture. In other embodiments, various embodiments of the present invention may be used with a user mobile device that includes specialized hardware to support the corresponding functionality.

Referring now to Figure 5, Figure 5 illustrates an example embodiment of an inter-network wireless router 500 for providing network connectivity.

In one embodiment, the inter-network wireless router 300 is a standalone device, but one of ordinary skill in the relevant art will appreciate that the described functionality can be incorporated in a wide variety of devices including, but not limited to, smart phones. , laptop or tablet, desktop computer, wireless dongle or USB key.

The exemplary apparatus 500 includes one or more basic (multilayer) 502 that further includes a plurality of integrated circuits, including a processing subsystem 504, such as a digital signal processor (DSP), a microprocessor, a programmable logic device (PLD) A gate array or a plurality of processing components, and a power management subsystem 506, a memory subsystem 508 and a first radio modem subsystem 510, and a second radio modem subsystem 512 that provide power to the device 500. In some embodiments, user input/output (I/O) 314 may also be present.

In some cases, the processing subsystem may also include an internal cache. The processing subsystem 504 is coupled to a memory subsystem 508 that includes non-transitory computer readable memory, which may be, for example, an SRAM, flash memory, and SDRAM component. The memory subsystem can execute one or more DMA type hardware to facilitate data access, as is known in the art. In normal operation, the processing system is operative to read one or more instructions stored in memory and perform one or more actions based on the read instructions.

The illustrated power management subsystem (PMS) 506 provides power to the inter-network wireless router 500 and may include an integrated circuit and or a plurality of discrete electrical components. Common examples of power management subsystem 506 include, but are not limited to, rechargeable battery power and/or external power sources, such as from a power outlet, an inductive (wireless) charger, and the like.

User I/O 514 includes any number of known IOs including, but not limited to, LED lights, speakers, and the like. For example, in this case, a set of LEDs can be used to indicate the connection status (eg, "Green indicates the connection status, "Red indicates a fault or connection problem, etc.). In more complex implementations, the I/O may include a keyboard, a touch screen (eg, a multi-touch interface), an LCD display, a backlight, a speaker, a microphone, or other I/O such as USB, GPIO, RS232 UART, PCI, GMII, RGMII and so on.

The first radio subsystem 510 is configured to connect to one or more first networks. In an example embodiment, the first network is used to provide a network connection to, for example, the Internet. The first radio subsystem 510 is configured to establish a link through which data can be transmitted over the cellular network. Common examples of cellular technologies that can transmit data include, but are not limited to, Long Term Evolution (LTE), LTE-Advanced (LTE-A), Universal Mobile Telecommunications System (UMTS), General Packet Radio Service (GPRS), CDMA2000, CDMA 1X- EVDO and so on. Although cellular networks are generally discussed herein, it is understood that various aspects of the invention are not limited to these networks. Common examples of other wireless networks that provide similar services include, for example, WiMAX, Wi-Fi, Bluetooth, Wireless Metropolitan Area Network (WMAN), and the like.

One of ordinary skill in the relevant art will directly appreciate that a particular wireless technology may implement access control (e.g., authentication, authorization, or billing, etc.). For example, a user mobile device for a 3GPP network (eg, LTE, LTE-A, UMTS, etc.) must successfully complete the Authentication and Key Agreement (AKA) process. The AKA program is based on a shared key, which is stored in the secure SIM card of the user's mobile device, at the Network Authentication Center (AuC). SIM and AuC perform challenge and response tests, and successful co-authentication leads to a secure association between the SIM and the service system.

The second radio subsystem 512 is configured to generate a wireless network for accepting one or more user mobile devices. In an example embodiment, the generated wireless network is an "open" network, ie the generated wireless network does not require any access control measures (eg authentication, authorization, accounting) Fees, etc.). Although this document describes open network operations, it is understood that access control schemes need not be open; restricted access (ie, partially open) and "closed" access may be used, even in different cases of mixing or combining. To achieve the same success. In fact, since the core network is a secure link, the certificate and key(s) for the wireless radio subsystem 512 can be entered and set by the cellular radio subsystem 510 existing between the UE-S and the core network. And from the core network through the LTE-R interface to the Wi-Fi portion 512 transmission, again, this is the same secure link. In one embodiment, the generated wireless network includes a Wi-Fi network. Other wireless technologies may be combined, for example, with Bluetooth, Wimax, and the like. In some cases, the open network can be combined with so-called "self-organizing" networks, (ie, unplanned or unstructured relationships between two or more entities or devices), the so-called "grid" Internet, etc. Accordingly, the present invention contemplates the use of daisy chains of polymeric or even heterogeneous and/or homogeneous network types.

In an example embodiment, the first radio subsystem 510 is only used for a communicable wireless connection to data received through the second radio subsystem 512. In "communicable" operation, the data payload received by the second radio subsystem 512 is passed to the first radio subsystem 510 for transmission without modification or the like. Similarly, the data payload received by the first radio subsystem 510 is passed to the second radio subsystem 512 for transmission without modification or the like. It should be noted that the data payload may be encrypted between the endpoint (eg, the network and the user's mobile device), so the inter-network wireless router 500 cannot intercept the information anyway. One of ordinary skill in the relevant art to which the present invention pertains can directly appreciate that the data payload is encapsulated within appropriate radio link specific control data; as a clarification, the radio link specific data is managed by a cross-network wireless router . Radio link specific information is typically used to communicate with the corresponding radio link layer in an equivalent entity, which may include, for example, physical and MAC layers, data links Layers, as well as possible units of the network and transport layers. The physical layer manages physical modulation and data transmission and may include information such as power control, frequency correction, time correction, etc., while the MAC layer formats the datagram and controls access to the physical layer medium. The data link layer manages the physical reliability of data transmission and includes, for example, error detection and correction. The network layer manages data transfers based on addresses within the network, while the transport layer ensures reliable data transfer.

Also, the security scheme for data transfer to the inter-network wireless router 500 relies on the transfer from the authentication authority by the first radio subsystem 510. Specifically, a certificate for the wireless radio subsystem 512 can be entered and set by the cellular radio subsystem 510 existing between the UE-S and the core network (which is a secure link), and the LTE-R is passed from the core network. The interface transmits (via the same secure link) the certificate to the Wi-Fi portion 512.

Referring again to processing subsystem 504 of FIG. 5, the processing system requires sufficient processing power to support both first radio subsystem 510 and second radio subsystem 512. As shown in Figure 5, there are several (2 or more) antennas to support MIMO operation of the first and second networks (e.g., LTE and IEEE 802.11n, respectively). Although not explicitly shown, it will be appreciated that each RF front end includes what the radio subsystem of the device may require, for example, filters, duplexers, RF switchers, RF signal power level monitoring, LNA (Low Noise Amplifier) ) and PA (power amplifier).

In an example embodiment, the second radio subsystem 512 includes all functions required to configure and operate an IEEE 802.11n modem, including a transceiver portion, a PHY (physical layer), and a MAC (Media Access Controller) unit, and all associated Control and run the SW. An example of this unit is the Broadcom 802.11n single-chip product, BCM4322 or BCM4323, which has achieved equivalent success with other divisions.

In an example embodiment, the processor subsystem 504 is configured to execute software for operation and control across a network wireless router. An example of this unit is the Broadcom BCM 4705 processor chip, which includes a processor core and multiple I/O functions such as GPIO, RS232 UART, PCI, GMII, RGMII, and DDR SDRAM controllers or Qualcomm's Snapdragon 800.

In an example embodiment, the first radio subsystem 510 includes all of the functionality required to configure and operate the 4G LTE modem. An example of this device is the QUALCOMM Gobi MDM9600 and its associated RF and peripheral integrated chips. In some embodiments, a SIM/USIM module can be included to also provide a choice of operation in a conventional wireless router.

Many existing chipsets (for example, QUALCOMM Gobi MDM9600) is only used to support a single user; those of ordinary skill in the relevant art will directly understand that these limitations occur in these existing chipsets and do not occur in others (ie, multiple users supporting cross-network wireless routers are not available). Inherent limitations). However, it is advantageous to support multiple users with cross-network wireless routers using existing available market chipsets. One possible solution is to implement a 1:1 ratio of chipset to supportable users. In other words, a wireless router with two (2) LTE modem units (eg, QUALCOMM Gobi MDM9600 and all its associated RF and peripheral integrated chips and components) can support up to two (2) individual users. Alternatively, more specialized hardware/software can be developed to facilitate one-to-many relationships (eg, one modem unit serving multiple discrete users).

Figure 6 shows an illustrative example of a dual-user and/or dual-band inter-network wireless router 600 with two LTE modems (610A, 610B) that can be tuned to two different LTE bands (or the same frequency band). For example, running two different LTE networks in the neighborhood The path carriers will have different frequency bands; hotspots provided by inter-network wireless routers can provide access to any network for up to two users. Similarly, even if both LTE modems (610A, 610B) are tuned to the same network, transactions with the first user may be provided on the first modem 610A, and transactions with the second user may be provided at the second modem. On the 610B. The transmissions are multiplexed and provided to hotspots utilizing Wi-Fi modem 612 via standard multiple access schemes.

In another such solution, PHY operations for different users can be modified and integrated in a single PHY implementation and connected to the virtual user MAC and higher layers. This implementation requires considerable processing power on the inter-network wireless router 500 because each individual user within the inter-network wireless router requires a separate virtual storage space (eg, protocol stack, MAC, etc.). Such an implementation combines the support of several users on a single multi-core processor, such as the Freescale QorIQ Qonverge B4420 baseband processor.

Sample user mobile device

Referring now to Figure 7, Figure 7 illustrates an example embodiment of a user mobile device 700 for connecting to the inter-network wireless router of Figure 5. In one implementation, user mobile device 700 is a dedicated device, but one of ordinary skill in the relevant art will appreciate that the described functionality can be incorporated in a variety of devices including, but not limited to, smart phones, portable computers, tablets, Desktop computers, blade servers, etc., even stand-alone devices with only one radio modem for Wi-Fi 802.11n communication.

The example device 700 includes one or more sub-units 702 that further include a plurality of integrated circuits, including a processing subsystem 704, such as a digital signal processor (DSP), a microprocessor, a programmable logic device (PLD), a gate array Or multiple processing components, and to the device 700 provides a power management subsystem 706, a memory subsystem 708, and two radio modem subsystems 710a and 710b, one for the LTE air interface and one for the Wi-Fi IEEE 802.11n air interface. In some embodiments, user input/output (I/O) 712 may also be present.

In some cases, the processing subsystem may also include an internal cache. The processing subsystem 704 is coupled to a memory subsystem 708 that includes non-transitory computer readable memory, which may be, for example, an SRAM, flash memory, and SDRAM component. The memory subsystem can execute one or more DMA type hardware to facilitate data access, as is known in the art. In normal operation, the processing system is operative to read one or more instructions stored in memory and perform one or more actions based on the read instructions.

The illustrated power management subsystem (PMS) 706 provides power to the user mobile device 700 and may include an integrated circuit and or a plurality of discrete electrical components. Common examples of power management subsystem 706 include, but are not limited to, rechargeable battery power and/or external power sources, such as from a power outlet, an inductive charger, and the like.

User I/O 712 may include any number of known IO common consumer electronic products including, but not limited to, keyboards, touch screens (eg, multi-touch interfaces), LCD displays, backlights, speakers, and/or microphones or USB and others. interface.

The radio subsystem 710 is used to establish a tunnel to the network operator through the wireless access network generated by the inter-network wireless router 500 (see, for example, FIG. 5). In an example embodiment, the resulting wireless network is an "open" network, ie, the resulting wireless network does not require any access control methods (eg, authentication, authorization, or billing, etc.). Although open network operation is described herein, it will be appreciated that the access control scheme need not be open; partial or limited access, closed access, and combinations or variations of the foregoing may be used to achieve equivalent success. In an example implementation In the formula, the generated wireless network includes a Wi-Fi network using IEEE 802.11N access technology. Other wireless technologies such as Bluetooth, WiMAX, etc. can be combined. In some cases, the open network may incorporate a so-called "self-organizing" network, mesh network, etc. as described above.

Although a radio subsystem is illustrated, it is directly understood that many commercial implementations will include additional radio subsystems (not shown for clarity). For example, in one example, the user mobile device additionally includes a cellular radio subsystem to connect to the cellular network prepared by the network operator through existing legacy cellular technologies.

In an example embodiment, the user mobile device is further associated with an identification module 714 that authenticates the user mobile device to the network operator. Typically, the identity module securely identifies the user's mobile device (or user account associated with the device) as trusted and authorized access. Common examples of identification modules include, but are not limited to, SIM, USIM, RUIM, CSIM, and the like. In some cases, the recognition module 714 can be removable (eg, a SIM card) or be an integrated portion of the device (eg, an embedded unit having an identification module programming therein).

In an example embodiment, the radio subsystem 710 is used for data payloads in conjunction with the operation of a wireless connection (as provided in the example, the inter-network wireless router 500 described in FIG. 5 above). In a "passable" operation, the received datagram includes an "establish access channel" data payload that is addressed to the logical entity of the user's mobile device. In an example embodiment, the data payload establishing the access channel includes communication from an authentication center (AuC) of an LTE network (encapsulated within a Wi-Fi hotspot of a cross-network wireless router), the data payload being used for And the operation of a logical entity placed on the SIM card of the user's mobile device (such as the aforementioned Authentication and Key Agreement (AKA) program).

One of ordinary skill in the relevant art will appreciate that the user mobile device can have multiple other components (e.g., multiple additional radio subsystems, graphics processors, etc.), the foregoing being merely illustrative.

Example "Wi-Fi Tube"

Figure 8 is a logic block diagram showing one embodiment of an IEEE 802.11n PHY (L1) and MAC (L2) protocol stack 800 useful in conjunction with various aspects of the present invention. As shown, application software 808 runs directly above MAC layer 806. It will be appreciated that other variations may be combined with other software layers (eg, logical link control (LLC) and/or IP layers) based on design considerations. The illustrative PHY can operate simultaneously on the U-NII band 802 or the ISM band 804, or both.

The MAC layer 806 can be set to operate in "contention" or "contention free" mode. In the contention-free operation, the MAC uses the Point Coordination Function (PCF); during the contention mode operation, the MAC uses the Distributed Coordination Function (DCF). Other Wi-Fi MAC features include registration, handoff, power management, security, and quality of service (QoS). Existing Wi-Fi components and functions are known in the related art, if not otherwise specified, without further discussion.

Referring now to Figure 9, consider an example cross-network wireless router 500 (e.g., as discussed in Figure 5 and discussed above) and an example user mobile device 700 (e.g., as described in Figure 7 and discussed above). Once the example user mobile device 700 enters the coverage area of the example cross-network wireless router 500 and registers with the open network, the end-to-end MAC connection between the user mobile device 700 and the wireless router 500 forms a "transparent" connection (or Take the channel), which is hereinafter referred to as "Wi-Fi pipe" 900. In some embodiments, the Wi-Fi pipe channel itself is unsecure (eg, where the hotspot behaves as an "open" Wi-Fi network), and the underlying data payload can be based on existing The encryption scheme is used to protect the end-to-end for cellular (LTE) networks and/or application layers, such as those used over traditional untrusted networks. In other embodiments, the Wi-Fi tube is implemented over a closed network in conjunction with local encryption or the like (Wired Equivalent Privacy (WEP), Wi-Fi Protected Access (WPA), WPA2, etc.). U.S. Patent Application Serial No.: U.S. Patent Application Serial No.:<u style="single">14/156,339</u>The title is "METHODS AND APPARATUS FOR HYBRID ACCESS TO A CORE NETWORK", which is described in more detail in the patent, the entire contents of which is incorporated herein by reference.

An example implementation of the Wi-Fi pipe causes two logical endpoints to run the first application 904 and the second application 906 (respectively) to translate communications directly (ie, without modifying the data transmission) without any intervention. The logical endpoints are unaware of the underlying physical and data link transactions, which occur in their respective Wi-Fi interfaces. In an example embodiment, the first application 904 is coupled to a UE-S software stack and the second application 906 is coupled to a UE-R stack (not shown). In other words, the example Wi-Fi tube causes the UE-S stack (SIM/USIM card on the user mobile device 700) to directly connect to the logic of the UE-R protocol stack (on the inter-network wireless router 500).

Referring again to the Wi-Fi tube, in one implementation, the Wi-Fi tube is embedded in the UE-S LTE protocol stack, replacing one or more layers of the UE-S LTE protocol stack, the Wi-Fi pipe is connected on one side of the UE-S LTE stack stack layer directly above the removal layer, and on the other hand, the Wi-Fi pipe is connected to UE-R LTE protocol stack, which also provides the functionality of the replaced layer in the UE-S LET protocol stack. The two LTE protocol stacks in UE-S and UE-R together provide a complete LTE protocol stack, which is required for the LTE handset to operate correctly in the LTE network. The Wi-Fi tube effectively provides wireless access channel setup between the two layers of the LTE UE protocol stack.

Figure 10A illustrates a prior art LTE software user plane protocol stack, and Figure 10B illustrates a prior art LTE software control plane protocol stack. In contrast, Figure 11 illustrates an example of a hybrid Wi-Fi pipe protocol stack operating under the Radio Link Control (RLC) layer, where Radio Link Control (RLC) replaces the LTE MAC and L1 layers. The alternate LTE MAC and L1 layers are supported by UE-R stack stacking across the network wireless router 500. In one implementation, the Wi-Fi tube couples a first-in, first-out (FIFO) data buffer on both sides (eg, at user mobile device 700 and router 500) to handle the time of arrival (eg, jitter), which may otherwise result in Scheduling problems with this Wi-Fi pipe or LTE operation. In embodiments of multiple users, the router may incorporate multiple buffers corresponding to each user, a single buffer divided into multiple partitions for each user, and the like.

There are RLC entities for each radio bearer, which allows multiple radio bearers to carry the performance of separate radio bearers. The LTE RLC is used to decompose (and reassemble) datagrams from the (and) Packet Data Convergence Protocol (PDCP) layer into manageable sizes for Wi-Fi pipes. The LTE RLC is further configured to ensure that all received packets are in order before being passed to the PDCP layer. In the event that the datagram is lost, the LTE RLC layer may perform a retransmission to recover the lost datagram by initiating an automatic repeat request (ARQ) procedure.

Each radio bearer has a PDCP entity (to ensure isolated radio bearer performance). The LTE PDCP entity is used to provide encryption (and integrity) protection (via untrusted connections, such as Wi-Fi pipes). The LTE PDCP is also used to provide reliable header compression (ROHC), which may reduce the overhead of transmitting small datagrams (further improving Wi-Fi pipe performance). Finally, the PDCP entity can provide reordering and retransmission of datagrams during the handoff operation.

While the previous discussion and FIG. 11 depict Wi-Fi pipe functionality on the MAC and L1 layers, it will be appreciated that other implementations may be present on any layer of the user's mobile device and/or inter-network wireless router device. Perform an equivalent access channel type run.

The above discussion is based on Wi-Fi pipe data throughput, which is much larger than the data throughput required by LTE networks to support all users in the coverage area. Although the foregoing assumptions are generally true, it should be understood that wherein the LTE network operates at a faster hot point, the Wi-Fi pipe should indicate the available capacity of the LTE network, so that the LTE network can be wireless. The bearer is appropriately adjusted (eg, limiting resource and bandwidth allocation for each UE-S MAC). Such a situation can occur when a cross-network wireless router provides both cellular network connectivity and where traditional wireless routers operate; both functions may be "overwritten" by a certain percentage of router bandwidth to ensure that these two functions are Fully supported.

Referring now to Figure 12, an overall protocol stacking structure (user plane and control plane) for user mobile devices and inter-network wireless routers is presented. The two-way auxiliary control channel (1202, 1204) and supporting applications and agents (1206, 1208) are referred to as cross-network wireless router (NAWR) protocol stacks.

As shown, the NAWR APP (Application) 1206 resides in the user's mobile device and includes an LTE stack that includes Radio Link Control (RLC) to a Non-Access Stratum (NAS) for control plane operation, and for the user. The RLC that runs on the plane to the Internet Protocol (IP). The NAWR APP also includes buffers and MUX/DeMUX, as well as NAWR control channels and control and running software. The counterpart NAWR agent 1208 resides in a cross-network wireless router and includes an LTE UE-S MAC, PHY entity, which is now supported on the UE-R, moving to one or more users The mobile device handles the control plane, user plane, SRB, DRB, and NAWR control channel packets. The NAWR APP and the NAWR agent communicate bidirectionally through the NAWR control channel.

In one embodiment, the NAWR APP is a downloadable application (eg, for purchase) and/or included in the user's mobile device during the manufacturing process. Depending on the nature of the software implementation for the local LTE software and the accessibility of third party support, the NAWR APP may replace the local LTE protocol stack in whole or in part during operation. For example, due to security considerations, the NAWR APP may have its own associated LTE protocol stack copy; in other embodiments, the NAWR APP may be used to interface with a supported LTE protocol stack.

Referring now to the buffer and MUX/DeMUX 1210, the buffer and MUX/DeMUX 1210 are used to route different signaling radio bearers (SRBs), data radio bearers (DRBs), control planes, user planes through Wi-Fi pipes in the uplink. The RLC datagram and the NAWR control channel datagram are multiplexed into a single data stream for delivery. On the downlink, the buffer and MUX/DeMUX 1210 are used to buffer incoming data and demultiplexed datagrams to the appropriate SRB, DRB, control plane, user plane, and NAWR control channels.

Similarly, multiple user (MU) buffers and MUX/DeMUX 1212 of the NAWR agent are used to multiplex different users' MAC packets (including SRB and DRB) and packets from their respective NAWR control channels into a single data stream. Before buffering and transporting it to the Wi-Fi tube for transmission to the user. In the uplink, the MUX/DeMUX 1212 is used to buffer and multiplex datagrams (from multiple users) that are transported over the Wi-Fi pipe before being passed to the respective LTE MAC and PHY entities corresponding to the user. Each user connected to the network through the NAWR proxy has a unique instance of the corresponding NAWR protocol stack.

method

An exemplary Wi-Fi pipe between the NAWR APP 1206 and the NAWR agent 1208 is self-contained. This Wi-Fi link is not managed from the input of an external entity. In addition, some aspects of LTE radio links (inter-network wireless routers and eNBs) can affect some aspects of hotspot operation (between network wireless routers and user mobile devices). For this reason, link management is divided into three (3) logical functions: a) When the Wi-Fi pipe is managed in the coverage area of the AP 300, it may also include: a. Wi-Fi pipe configuration, according to the wireless chain Road performance monitoring and maintenance of Wi-Fi pipe operation; and b. Acquisition and configuration of LTE sessions with Evolved Packet Core (EPC) networks to provide adequate throughput for Wi-Fi pipes; b) LTE link management , which generally includes: a. system information decoding; b. paging channel operation; c. battery measurement and response cell reselection and handover procedures; d. radio resource control (RRC); e. security, integrity Sex, access control (eg via SIM card); f. call control; g. mobility control; and c) NAWR session initiation; a. discovery, initiation and configuration of NAWR sessions (eg for simultaneous support of NAWR and legacy operations) hot spot).

In more detail, Wi-Fi management manages the wireless connection between the user's mobile device and the inter-network wireless router. In one embodiment, the Wi-Fi hotspot function is based on, for example, Existing components of the existing IEEE 802.11n specification operate, and in other embodiments, Wi-Fi hotspot functionality can be integrated with the NAWR APP and/or NAWR agent to optimize performance specific to Wi-Fi pipes. For example, the NAWR agent can monitor the performance of the LTE link and use this monitoring capability to inform the Wi-Fi pipe to operate. By coordinating channel and bandwidth allocation, the NAWR agent can reduce the amount of buffering and/or provide better quality (eg, low latency and low jitter) for links that serve services such as VoLTE (LTE voice) or VoIP (voice over IP). . It can be understood that some operations may not directly affect wireless links (such as Wi-Fi positioning, internal Wi-Fi handover, Wi-Fi power management, Wi-Fi QoS, etc.); Features can be processed within legacy components and/or NAWR APP/Proxy.

As for LTE link management, the NAWR proxy and/or APP manages the network connection between the user mobile device (UE-S) and the evolved datagram core (EPC) of the network operator. In one embodiment, the LTE network connection is based on legacy components operating according to, for example, existing LTE specifications; in other embodiments, the LTE link function can be integrated with the NAWR APP and/or NAWR agent to optimize specific use Wi-Fi tube performance. As mentioned earlier, the performance of the LTE link can be monitored to improve the operation of the Wi-Fi pipe. Likewise, operations that may not directly affect LTE performance may be handled by legacy components or incorporated into the NAWR agent and/or NAWR APP. Common examples include, but are not limited to, LTE network acquisition (selection and reselection), authentication, encryption, integrity protection, call control (call/session setup/clear), mobility (internet and intra-LTE handover) )Wait.

As for mobility management, Figure 13 depicts an implementation of a generalized process for discovery, initiation, and configuration of a session. As shown, the NAWR APP and/or NAWR agent is used to discover, launch, and configure NAWR sessions and Wi-Fi pipes.

In step 1302 of process 1300, the user mobile device discovers an enabled wireless network. The user mobile device determines whether the inter-network wireless network supports cross-network operation. Common examples of discovery include, but are not limited to, decoding control broadcasts, direct queries, and the like.

In some variations, the wireless network is an "open" network. Open networks do not have strict access controls (such as authentication, authorization, etc.). In other networks, the network may be turned off, partially restricted, and so on. For example, the user's mobile device may need to prompt the user for a password or press a button on the wireless router. In other cases, the user's mobile device may be allowed access by an out-of-band program (eg, by an administrator, etc.). Various other suitable solutions will be apparent to those of ordinary skill in the art in view of this disclosure.

In step 1304, when the user mobile device determines that the wireless network supports inter-network operation, the NAWR APP attempts to establish an access channel (or NAWR session) between the user mobile device and the network operator through the inter-network wireless router. . In one embodiment, the access channel includes a Wi-Fi pipe between a UE-User (UE-S) and a cross-network wireless router. In one such example, the NAWR APP (or NAWR Agent) transmits a NAWR Connection Request via the NAWR Control Channel; the connection request includes connection establishment related information. Common examples of information include, for example, software versions, user mobile device network operator identification and frequency (e.g., one or more LTE networks configured by user SIM), Wi-Fi and LTE neighbor lists, and the like.

In step 1306 of process 1300, in response to the received connection request, the NAWR agent determines if the NAWR connection can be established. In some cases, due to resource limitations (such as insufficient memory, insufficient processing power, inability to access network operators, etc.), the NAWR agent may not be able to support connection requests. NAWR if the NAWR agent can support connection requests The proxy configures the radio front end based on the connection request; otherwise the connection request fails. In an example embodiment, the NAWR agent configures the LTE RF operating frequency.

In addition, the NAWR agent allocates or reserves storage for the data stream corresponding to the user's mobile device. In one embodiment, a portion or partition of the MU buffer and MUX/DeMUX buffer of the NAWR agent is reserved and a buffer ID (processor) is issued. The buffer ID is provided to the NAWR APP, and then the UE-S NAWRAPP will use the buffer ID to access/modify its corresponding NAWR connection (the NAWR agent can also handle multiple different users simultaneously).

In step 1308, if the NAWR connection request is successful, the NAWR agent is allowed to return to provide the connection parameters to the NAWR APP via the NAWR connection. In one implementation, the connection parameters include a buffer ID. Other common examples of connection parameters may include, for example, connections, maximum data transmission rate and/or throughput, minimum data rate and/or throughput, delay, quality of other connection restrictions (eg, QoS), and the like.

In step 1310, the user mobile device can thereafter connect to the transaction data via NAWR. More generally, the user mobile device can perform "establish access channel" LTE operations, such as system acquisition, connection setup, initiation, establishment of radio bearers, and data flow.

Figure 14 illustrates an exemplary logic flow for a NAWR connection of an exemplary embodiment of a NAWR APP executing on a User Mobile Equipment (UE-S) platform.

In step 1402, when the user mobile device is first powered on or reset, the NAWR APP initializes and sets its internal variables and flags to default values (eg, "LTE Flag" is reset to "0", indicating that there is no LTE network. The road is currently available).

In step 1404, after initialization, the NAWR APP enables the LTE modem and searches for available LTE eNBs and networks. By detecting the required network and eNB, the NAWR APP sets the "LTE Flag" to "1" to indicate that LTE network access is available.

Before connecting to the LTE network, the NAWR APP tried to find a Wi-Fi network. In general, Wi-Fi is better than LTE access because Wi-Fi operation consumes less power and/or supports higher data rates and the like. It will be appreciated that certain other implementations may incorporate different priority schemes.

In step 1406, the NAWRAPP enables the Wi-Fi modem and looks for nearby Wi-Fi APs. In some cases, the NAWR APP may have a better access mode, which is specifically used to find a cross-network wireless router or "4G router."

In step 1408, if a Wi-Fi access point (AP) is found, the NAWR APP will be registered thereon. In a simple implementation, the Wi-Fi AP operates in an "open" mode. If the NAWR APP cannot register with the Wi-Fi AP, NAWRAPP does not seem to find Wi-FiAP. A closed Wi-Fi access point can also be accessed by another access method (described later).

In step 1410, if the NAWR APP has successfully registered with the Wi-Fi AP, the NAWRAPP will ask the AP to find out if it has the appropriate NAWR agent. In one embodiment, the query includes a NAWR Connection Request/NAWR Connection Allow transaction. If the NAWR query is successful, the "NAWR APP" can continue the LTE network acquisition through the Wi-Fi pipe using the NAWR LTE front end.

Periodically during the NAWR connection, the NAWR APP will measure performance to determine if a better Wi-Fi access point or LTE eNB is available. These measurements are reported to the LTE network; the LTE network can responsively cause a handoff (HO). Useful example for HO Measurements may include, but are not limited to, signal level measurements of received signal strength indicators (RSSI), signal to noise ratio (SNR), bit error rate (BER), and the like. Other useful information may include, for example, a neighbor list for the LTE eNB based on measurements made by the UE-S LTE PHY now residing within the UE-R.

Returning to step 1414, when no Wi-Fi network is available but one or more LTE networks are available, the NAWRAPP will continue to use the LTE network while constantly looking for NAW-supported Wi-Fi APs.

Figure 15 illustrates the logic flow of a NAWR connection for initiating an example implementation of a NAWR proxy executing on a cross-network wireless router.

In step 1502, when the inter-network wireless router is powered on or reset for the first time, the NAWR APP initializes and sets its internal variables and flags to default values (for example, "user" is set to "0", indicating that there is currently no The user of the service, while MAX_USER is set to "1" for single-user operation), and proceeds to the modem that turns on Wi-Fi.

In step 1504, in response to receiving the NAWR Connection Request message, the NAWR agent determines if the connection request is available for service. In an example embodiment, the NAWR agent increments the USER register and verifies that the number of users has not exceeded the maximum number allowed by the user. If the maximum number allowed by the user is not reached, the NAWR agent proceeds to allocate buffer space on the MU buffer and MUX/DeMUX buffer and allocates a buffer ID to the NAWR APP, which is to allow communication to the NAWR APP using the NAWR connection. In subsequent transactions, the NAWR APP expects to use the buffer ID each time a message is sent; in some implementations, the buffer ID can be associated with the Wi-F user's ID (eg, the MAC address of the incoming datagram). extract.

Otherwise, if the connection request cannot be serviced (eg, the maximum number of users is reached), the new user will be denied access. In some cases, an informational message is sent to inform them of a failure (eg, system overload).

In step 1506, the NAWR agent introduces an instance of a NAWR protocol stack for new users (each NAWR APP requires an instance of a NAWR protocol stack).

Periodically, the NAWR agent checks to determine if the user has terminated the connection (step 1508). When the user has terminated the connection, the NAWR agent decrements the user register and stops the instance of the corresponding NAWR protocol stack associated with the corresponding NAWR APP.

The incoming handoff (HO) also has a similar process to add new users (see step 1504), while the outgoing handoff is similar to the user terminal (see step 1508).

Numerous other solutions for implementing inter-network wireless routing will be considered by those of ordinary skill in the art in view of the present disclosure.

It will be appreciated that while certain aspects of the invention are described in terms of specific sequences of method steps, these descriptions are merely illustrative of the broader methods of the invention and may be modified by the particular application as needed. Some steps may be unnecessary or optional in some cases. In addition, certain steps or functions may be added to the disclosed embodiments, or in the order of performance of two or more of the steps. All such variations are considered to be included in the invention disclosed and claimed herein.

While the above detailed description has illustrated, described and illustrated the embodiments of the invention Those skilled in the art can make without departing from the invention. The foregoing description is the best mode contemplated for carrying out the invention. This description is never intended The taste is limiting, but should be considered as an illustrative general principle of the invention. The scope of the invention should be determined with reference to the claims.