US20150237543A1 - Methods And Apparatus For Use In Facilitating The Communication Of Neighboring Network Information To A Mobile Terminal With Use Of A Radius Compatible Protocol - Google Patents
Methods And Apparatus For Use In Facilitating The Communication Of Neighboring Network Information To A Mobile Terminal With Use Of A Radius Compatible Protocol Download PDFInfo
- Publication number
- US20150237543A1 US20150237543A1 US14/699,793 US201514699793A US2015237543A1 US 20150237543 A1 US20150237543 A1 US 20150237543A1 US 201514699793 A US201514699793 A US 201514699793A US 2015237543 A1 US2015237543 A1 US 2015237543A1
- Authority
- US
- United States
- Prior art keywords
- network
- mobile terminal
- request
- neighboring
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000000034 method Methods 0.000 title claims abstract description 72
- 238000004891 communication Methods 0.000 title claims description 97
- 230000004044 response Effects 0.000 claims abstract description 72
- 230000000875 corresponding effect Effects 0.000 description 24
- 230000006870 function Effects 0.000 description 16
- 230000001413 cellular effect Effects 0.000 description 8
- 230000008569 process Effects 0.000 description 8
- 238000000060 site-specific infrared dichroism spectroscopy Methods 0.000 description 8
- 239000000523 sample Substances 0.000 description 7
- 238000006243 chemical reaction Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 238000013475 authorization Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 3
- 238000004590 computer program Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 238000010295 mobile communication Methods 0.000 description 3
- 230000003321 amplification Effects 0.000 description 2
- 238000001914 filtration Methods 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000003199 nucleic acid amplification method Methods 0.000 description 2
- 206010001438 Affect alterations Diseases 0.000 description 1
- 241000597800 Gulella radius Species 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000002596 correlated effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 208000014674 injury Diseases 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 230000001105 regulatory effect Effects 0.000 description 1
- 230000005236 sound signal Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
- H04W48/14—Access restriction or access information delivery, e.g. discovery data delivery using user query or user detection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0055—Transmission or use of information for re-establishing the radio link
- H04W36/0061—Transmission or use of information for re-establishing the radio link of neighbour cell information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0892—Network architectures or network communication protocols for network security for authentication of entities by using authentication-authorization-accounting [AAA] servers or protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
- H04W36/00835—Determination of neighbour cell lists
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
- H04W36/0085—Hand-off measurements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/14—Reselecting a network or an air interface
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/10—Small scale networks; Flat hierarchical networks
- H04W84/12—WLAN [Wireless Local Area Networks]
Definitions
- the present disclosure relates generally to communication techniques for assisting wireless mobile terminals for wireless communications, and more particularly to techniques for facilitating the communication of neighboring network information to mobile terminals for handover purposes.
- Mobile terminals may be adapted to operate in one or more of a variety of different types of wireless networks, such as wireless local area networks (WLANs), WiMAX networks, cellular telecommunication networks, etc.
- WLANs wireless local area networks
- WiMAX networks cellular telecommunication networks
- the mobile terminal may lose radio coverage with the network or otherwise need to switch to an alternative neighboring wireless network to continue communications.
- the mobile terminal could scan using its one or more wireless transceivers to identify available wireless networks in its coverage region. Excessive scanning by the mobile terminal, however, may consume too much time and power of the mobile terminal. It may be helpful, on the other hand, if the identifications of the available wireless networks could be obtained by the mobile terminal via the current wireless network before the switching occurs. Given the new network components and modules which could be required to achieve this goal, however, deployment could become burdensome and difficult, especially given the many diverse wireless networks already in existence today.
- FIG. 1 is an illustrative representation of a communication system which includes a radio access network (RAN), which may be a wireless local area network (WLAN) such as an IEEE 802.11-based wireless network, and a wireless wide area network (WWAN) such as a public land mobile network (PLMN), within which a mobile terminal may operate;
- RAN radio access network
- WLAN wireless local area network
- WWAN wireless wide area network
- PLMN public land mobile network
- FIG. 2 is a schematic diagram of the mobile terminal which may operate in both the WLAN and the PLMN of FIG. 1 ;
- FIG. 3 is a top down view showing the mobile terminal moving in accordance with a travel path through coverage regions of the WLAN and the PLMN of FIG. 1 ;
- FIG. 4 is a general illustrative representation of the communication system of FIG. 1 which may be utilized for facilitating the communication of neighboring network information to the mobile terminal;
- FIG. 5 is a process flow diagram for describing a technique for use in facilitating communication of neighboring network information to the mobile terminal in the environments described in relation to FIGS. 1-4 ;
- FIG. 6 is another process flow diagram for describing another technique for use in facilitating communication of neighboring network information to the mobile terminal in the environments described in relation to FIGS. 1-4 ;
- FIG. 7 is an illustrative representation of the communication system of FIG. 1 , where the mobile terminal is shown to perform communication operations in the WLAN;
- FIG. 8 is an illustrative representation of the communication system of FIG. 1 , where the mobile terminal switches from communication operations in the WLAN to the PLMN.
- a radio access network such as a wireless local area network (WLAN).
- This technique involves the steps of receiving, from the mobile terminal, a request for neighboring network information; producing, in response to receiving the request, a corresponding request for the neighboring network information in accordance with a remote access dial-in user server (RADIUS) compatible protocol; sending the corresponding request to an information server (e.g. an authentication, authorization, and accounting (AAA) server) of a core network of a public land mobile network (PLMN) associated with the mobile terminal; receiving, from the information server, in response to the corresponding request, the neighboring network information in accordance with the RADIUS compatible protocol; and sending, in response to the request, the neighboring network information to the mobile terminal.
- an information server e.g. an authentication, authorization, and accounting (AAA) server
- PLMN public land mobile network
- the request/response for the neighboring network information may be an IEEE 802.21 information request/response.
- the radio access network is a WLAN adapted in accordance with IEEE 802.11
- the request/response may be communicated in accordance with IEEE 802.11u (e.g. generic access service or GAS) or an extensible authentication protocol (EAP).
- IEEE 802.11u e.g. generic access service or GAS
- EAP extensible authentication protocol
- the radio access network is a WiMAX network adapted in accordance with IEEE 802.16, the request/response may be communicated in accordance with IEEE 802.16g.
- Another illustrative technique is employed in the information server of the core network of the PLMN and involves receiving, from the radio access network, a request for neighboring network information in accordance with the RADIUS compatible protocol; retrieving, in response to receiving the request, neighboring network information corresponding to an indication provided in the request; and sending, to the network access server, in response to receiving the request, the retrieved neighboring network information in accordance with the RADIUS compatible protocol.
- FIG. 1 is an illustrative representation of a communication system 100 which includes a wireless local area network (WLAN) 102 and a public land mobile network (PLMN) 104 .
- WLAN 102 may be or be referred to as one type of radio access network (RAN) utilized by a mobile terminal 106 .
- RAN radio access network
- PLMN 104 may be or be referred to as a wireless wide area network (WWAN) or a mobile telecommunications network which may be further utilized by mobile terminal 106 .
- WWAN wireless wide area network
- WLAN 102 is an IEEE 802.11-based wireless network.
- WLAN 102 may be part of a communication network such as a local area network (LAN) 110 .
- LAN 110 is part of a private communication network, which may be an enterprise network of an enterprise having a gateway including a firewall 116 .
- LAN 110 may be a public communication network which may not require any gateway.
- Terminals may connect to LAN 110 through any suitable means, such as through a plurality of wireless access points (APs) (e.g. APs 112 and 114 ) of WLAN 102 .
- APs wireless access points
- Such mobile terminals and wireless APs can operate in accordance with IEEE 802.11 standards.
- each wireless AP may include or cooperate with a network access server (NAS) function of WLAN 102 .
- NAS network access server
- a NAS serves as a gateway for a network to guard access to a protected resource; typically, when a mobile terminal connects to a NAS, the NAS communicates with another network resource to identify whether credentials of the mobile terminal are valid for granting/denying access.
- PLMN 104 includes a core network 136 , a plurality of base station controllers such as a base station controller (BSC) 138 coupled to core network 136 , and a plurality of base stations such as a base station (BS) 140 coupled to associated BSCs 138 .
- BSC base station controller
- BS base station
- Core network 136 , BSC 138 , and base station 140 operate in a conventional fashion as well-documented.
- PLMNs in the environment have a similar or the same architecture as PLMN 104 , such as a PLMN 105 having a core network 146 , a plurality of base station controllers such as a base station controller (BSC) 148 , a plurality of base stations such as a base station (BS) 150 coupled to associated BSCs 148 , and a gateway/controller 144 provided between the Internet 101 and core network 146 .
- BSC base station controller
- BS base station
- gateway/controller 144 provided between the Internet 101 and core network 146 .
- mobile terminal 106 of LAN 110 is shown as a mobile communication device/wireless handset (WH) of the dual-mode type, having both WLAN and WWAN radio interfaces.
- mobile terminal 106 is shown to have one or more processors 120 , a WLAN radio interface 122 , a WWAN radio interface 124 , and antenna components 125 and 126 coupled to radio interfaces 122 and 124 .
- mobile terminal 106 may access services of core network 136 of PLMN 104 with use of WWAN radio interface 124 , as well as access services of LAN 110 with use of WLAN radio interface 122 .
- Communications between LAN 110 and core network 136 of PLMN 104 may be facilitated through a suitable connecting network such as a broadband, wide-area IP communication network (e.g. the Internet 101 ) or any suitable public or private wide area network.
- Gateway/controller 142 is provided between the Internet 101 and core network 136 of PLMN 104 in order to facilitate access to core network 136 by terminals through alternative links (e.g. radio links wireless APs 112 and 114 ) different than those conventional radio links offered in the PLMN 104 (e.g. radio links of base station 140 ).
- mobile terminal 106 may also access services of core network 136 of PLMN 104 via WLANs, such as WLAN 102 , through use of WLAN radio interface 122 .
- gateway/controller 142 and mobile terminal 106 are adapted to establish and maintain a (secure) tunnel connection between each other through the intervening networks.
- WLAN 102 may be operator-controlled or provided (e.g. controlled or provided by the operator associated with PLMN 104 ), user-controlled or provided (e.g. controlled or provided by the end user of mobile terminal 106 ), or third-party-controlled or provided.
- Core network 136 also has an authentication, authorization, and accounting (AAA) server 180 .
- core network 146 has an AAA server 182 .
- AAA servers 180 and 182 may operate in accordance with a Remote Authentication Dial-In User Service (RADIUS) protocol (e.g. RFC 2865) or RADIUS compatible protocol.
- RADIUS Remote Authentication Dial-In User Service
- AAA servers 180 and 182 may be or be referred to as RADIUS servers.
- the idea behind a central AAA server is that, instead of requiring every NAS to maintain a list of authorized usernames and passwords, RADIUS Access-Requests are forwarded to the AAA server.
- AAA servers and protocols are already widely deployed and in use in a variety of different networks.
- AAA server 180 When mobile terminal 106 connects, the NAS typically sends a RADIUS Access-Request message to AAA server 180 , relaying information such as the user's name and password, type of connection (port), NAS identity, and a message Authenticator.
- AAA server 180 uses the packet source, NAS identity, and Authenticator to determine whether the NAS is permitted to send requests. If so, AAA server 180 attempts to identify the user's name in its database. It then applies the password and perhaps other attributes carried in the Access-Request to decide whether access should be granted to this user.
- AAA server 180 may return a RADIUS Access-Challenge message that carries a random number.
- the NAS relays the challenge to mobile terminal 106 , which must respond with the correct value to prove its asserted identity (e.g. encrypting the challenge with its password), which the NAS relays to AAA server 180 inside another RADIUS Access-Request message. If AAA server 180 is satisfied that mobile terminal 106 is authentic and authorized to use the requested service, it returns a RADIUS Access-Accept message. If not, AAA server 180 returns a RADIUS Access-Reject message and the NAS disconnects mobile terminal 106 . When an Access-Accept message is received and RADIUS Accounting is enabled, the NAS sends a RADIUS Accounting-Request (Start) message to AAA server 180 .
- RADIUS Accounting-Request Start
- AAA server 180 adds an accounting record to its log and acknowledges the request, whereupon the NAS activates the user's session.
- NAS activates the user's session.
- a similar RADIUS Accounting-Request (Stop) message is exchanged so that accounting records will reflect the actual session duration and disconnect reason.
- AAA servers 180 and 182 may operate in accordance with a different (but nonetheless RADIUS compatible) protocol, such as a Diameter protocol.
- a Diameter NASREQ (network access server requirements) application provides for AAA services.
- the Diameter NASREQ application uses existing RADIUS attributes where possible to carry data objects, to ease migration of existing RADIUS servers to Diameter, and to reduce the protocol conversion work required for a server that acts as a RADIUS/Diameter gateway.
- Diameter is defined in terms of a base protocol and a set of applications, which allows the protocol to be extended to new access technologies.
- the base protocol provides basic mechanisms for reliable transport, message delivery, and error handling.
- the base protocol is used in conjunction with a Diameter application. Each application relies on the services of the base protocol to support a specific type of network access.
- the two major applications are Mobile IPv4 and NASREQ.
- the base protocol defines the basic Diameter message format. Data is carried within a Diameter message as a collection of Attribute-Value Pairs (AVPs), which are similar to RADIUS attributes.
- An AVP consists of multiple fields including an AVP Code, a Length, Flags, and Data.
- RFC 3169 Criteria for Evaluating Network Access Server Protocols, defines a number of requirements for AAA protocols used by NASs, addressing transport requirements, scalability, server failover, AVP requirements, security, authentication, authorization, policy, resource management, accounting, and more.
- RFC 2477 Criteria for Evaluating Roaming Protocols, similarly addresses the needs of AAA protocols supporting a roaming environment.
- the Diameter NASREQ application (combined with the base protocol) satisfies the requirements of both of these specifications. Even further, the NASREQ application, with native Extensible Authentication Protocol (EAP), offers secure authentication.
- EAP Extensible Authentication Protocol
- the NASREQ application defines the Diameter-EAP-Request and Diameter-EAP-Answer messages that allow the EAP payload to be encapsulated within the Diameter protocol.
- the NASREQ application's AA-Request message corresponds to the RADIUS Access-Request.
- the AA-Answer message corresponds to the RADIUS Access-Accept and Access-Reject messages.
- the NASREQ application has guidelines to be used by a server that acts as a RADIUS-Diameter protocol gateway, i.e. a server that receives a RADIUS message that is to be translated and transmitted as a Diameter message, and vice versa.
- the WLAN may be a WiMAX-based network (i.e. IEEE 802.16), a Ultra-WideBand (UWB)-based network (i.e. IEEE 802.15), a Bluetooth-based network, as a few examples.
- the WWAN may be a Long-Term Evolution (LTE)-based network, an EVolution-Data Only (EV-DO)-based network, or a UMTS-based network, as a few examples.
- LTE Long-Term Evolution
- EV-DO EVolution-Data Only
- Mobile terminal 106 e.g. a wireless handset, a mobile station
- Mobile terminal 106 which operates in a wireless network environment which includes both WLANs (represented in FIG. 2 by AP 112 ) and WWANs/PLMNs (represented in FIG. 2 by cellular base stations 200 which include base stations 140 and 150 for its associated PLMNs)
- WLANs represented in FIG. 2 by AP 112
- WWANs/PLMNs represented in FIG. 2 by cellular base stations 200 which include base stations 140 and 150 for its associated PLMNs
- Mobile terminal 106 may be representative of one or more terminals which operate in communication system 100 of FIG. 1 .
- Mobile terminal 106 can be a two-way communication device having at least voice and advanced data communication capabilities, including the capability to communicate with other computer systems.
- mobile terminal 106 it may be referred to as a data messaging device, a two-way pager, a cellular telephone with data messaging capabilities, a wireless Internet appliance, or a data communication device (with or without telephony capabilities).
- mobile terminal 106 is adapted to wirelessly communicate with base stations 200 .
- mobile terminal 106 utilizes a communication subsystem 211 which includes RF transceiver circuitry.
- Communication subsystem 211 includes a receiver 212 , a transmitter 214 , and associated components, such as one or more (embedded or internal) antenna elements 216 and 218 , local oscillators (LOs) 213 , and a digital signal processor (DSP) 220 .
- the specific design of communication subsystem 211 depends on the communication network in which mobile terminal 106 is intended to operate.
- communication subsystem 211 (including its associated processor/processing components) are operative in accordance with a cellular or other suitable WWAN standards (i.e. a standard other than IEEE 802.11), such as GSM/GPRS standards.
- Mobile terminal 106 may send and receive communication signals through the network after required network procedures have been completed.
- Signals received by antenna 216 through the network are input to receiver 212 , which may perform such common receiver functions as signal amplification, frequency down conversion, filtering, channel selection, and like, and in example shown in FIG. 2 , analog-to-digital (A/D) conversion.
- A/D conversion of a received signal allows more complex communication functions such as demodulation and decoding to be performed in DSP 220 .
- signals to be transmitted are processed, including modulation and encoding, for example, by DSP 220 .
- DSP 220 not only processes communication signals, but may also provide for receiver and transmitter control. Note that receiver 212 and transmitter 214 may share one or more antennas through an antenna switch (not shown in FIG. 2 ), instead of having two separate dedicated antennas 216 and 218 as shown.
- Mobile terminal 106 also has a communication subsystem 291 which includes RF transceiver circuitry operative in accordance with a suitable WLAN standard, such as the IEEE 802.11 standard, for communications with WLANs (e.g. represented by AP 112 in FIG. 2 ).
- Communication subsystem 291 is similar in structure and functionality to communication subsystem 211 , where DSP 220 may be replaced with a processing module referred to as a baseband (BB) and media access control (MAC) module.
- BB baseband
- MAC media access control
- mobile terminal 106 may have separate and independent subsystems for these purposes, at least some portions or components of these otherwise different subsystems may be shared where possible.
- mobile terminal 106 operates in accordance with both a cellular network interface standard (e.g. GSM/GPRS standard) and the IEEE 802.11 standard, it may be referred to as a “dual mode” mobile terminal.
- mobile terminal 106 may be a handheld, portable, battery-powered device, it also includes a battery interface 254 for receiving one or more rechargeable batteries 256 .
- a battery 256 provides electrical power to most if not all electrical circuitry in mobile terminal 106 , and battery interface 254 provides for a mechanical and electrical connection for it.
- Battery interface 254 is coupled to a regulator (not shown in FIG. 2 ) that provides a regulated voltage V to all of the circuitry.
- Mobile terminal 106 includes a microprocessor 238 (one type of processor or controller) that controls overall operation of mobile terminal 106 .
- This control includes the communication techniques of the present disclosure. Communication functions, including at least data and voice communications, are performed through communication subsystem 211 .
- Microprocessor 238 also interacts with additional device subsystems such as a display 222 , a flash memory 224 , a random access memory (RAM) 226 , auxiliary input/output (I/O) subsystems 228 , a serial port 230 , a keyboard (or keypad) 232 , a speaker 234 , a microphone 236 , a short-range communications subsystem 240 , and any other device subsystems generally designated at 242 .
- additional device subsystems such as a display 222 , a flash memory 224 , a random access memory (RAM) 226 , auxiliary input/output (I/O) subsystems 228 , a serial port 230 , a keyboard (
- Some of the subsystems shown in FIG. 2 perform communication-related functions, whereas other subsystems may provide “resident” or on-device functions.
- some subsystems such as keyboard 232 and display 222 , for example, may be used for both communication-related functions, such as entering a text message for transmission over a communication network, and device-resident functions such as a calculator or task list.
- Operating system software used by microprocessor 238 can be stored in a persistent store such as flash memory 224 , which may alternatively be a read-only memory (ROM) or similar storage element (not shown). Specific device applications, or parts thereof, may be temporarily loaded into a volatile store such as RAM 226 .
- Microprocessor 238 in addition to its operating system functions, enables execution of software applications on mobile terminal 106 .
- a predetermined set of applications that control basic device operations, including at least data and voice communication applications, will normally be programmed and/or installed on mobile terminal 106 during its manufacture (including the network selection control techniques of the present disclosure).
- An application that may be loaded onto mobile terminal 106 may be a personal information manager (PIM) application having the ability to organize and manage data items relating to user such as, but not limited to, e-mail, calendar events, voice mails, appointments, and task items.
- PIM personal information manager
- memory 262 such as “mem” in FIG. 2
- SIM subscriber identity module
- the PIM application has the ability to send and receive data items via the wireless network.
- PIM data items are seamlessly integrated, synchronized, and updated via the wireless network, with the wireless device user's corresponding data items stored and/or associated with a host computer system thereby creating a mirrored host computer on mobile terminal 106 with respect to such items. This can be especially useful where the host computer system is the wireless device user's office computer system.
- Additional applications may also be loaded onto mobile terminal 106 through network, an auxiliary I/O subsystem 228 , serial port 230 , short-range communications subsystem 240 , or any other suitable subsystem 242 , and installed by a user in RAM 226 or a non-volatile store (not shown) for execution by microprocessor 238 .
- Such flexibility in application installation increases the functionality of mobile terminal 106 and may provide enhanced on-device functions, communication-related functions, or both.
- secure communication applications may enable electronic commerce functions and other such financial transactions to be performed using mobile terminal 106 .
- a received signal such as a text message, an e-mail message, or web page download will be processed by communication subsystem 211 and input to microprocessor 238 .
- Microprocessor 238 will further process the signal for output to display 222 or alternatively to auxiliary I/O device 228 .
- a user of mobile terminal 106 may also compose data items, such as e-mail messages, for example, using keyboard 232 in conjunction with display 222 and possibly auxiliary I/O device 228 .
- Keyboard 232 is a complete alphanumeric keyboard and/or telephone-type keypad. These composed items may be transmitted over a communication network through communication subsystem 211 .
- mobile terminal 106 For voice communications, the overall operation of mobile terminal 106 is substantially similar, except that the received signals would be output to speaker 234 and signals for transmission would be generated by microphone 236 .
- Alternative voice or audio I/O subsystems such as a voice message recording subsystem, may also be implemented on mobile terminal 106 .
- voice or audio signal output is accomplished primarily through speaker 234
- display 222 may also be used to provide an indication of the identity of a calling party, duration of a voice call, or other voice call related information, as some examples.
- Serial port 230 in FIG. 2 is normally implemented in a personal digital assistant (PDA)-type communication device for which synchronization with a user's desktop computer is a desirable, albeit optional, component.
- Serial port 230 enables a user to set preferences through an external device or software application and extends the capabilities of mobile terminal 106 by providing for information or software downloads to mobile terminal 106 other than through a wireless communication network. The alternate download path may, for example, be used to load an encryption key onto mobile terminal 106 through a direct and thus reliable and trusted connection to thereby provide secure device communication.
- Short-range communications subsystem 240 of FIG. 2 is an additional optional component that provides for communication between mobile terminal 106 and different systems or devices, which need not necessarily be similar devices.
- subsystem 240 may include an infrared device and associated circuits and components, or a BLUETOOTH® communication module to provide for communication with similarly enabled systems and devices.
- BLUETOOTH® is a registered trademark of Bluetooth SIG, Inc.
- any suitable mobile communication device or terminal may be part of the disclosed methods and apparatus which will be described in fuller detail below.
- FIG. 3 is a top down view of a geographic region 300 , which shows mobile terminal 106 moving in accordance with a travel path 310 through a coverage region 350 of PLMN 105 (e.g. a GSM/GPRS based network) and a coverage region 304 of WLAN 102 .
- Coverage region 350 of PLMN 105 may be defined by one or more base stations of the network, whereas coverage region 304 of WLAN 102 may be defined by one or more wireless APs 112 and 114 of the network.
- Another coverage region 306 may be that of another wireless network, such as another WLAN or, alternatively, a WiMAX network. As shown, coverage regions 304 and 306 may overlap in whole or in part with coverage region 350 of PLMN 105 .
- mobile terminal 106 may have different transceiver portions (e.g. WLAN radio interface 122 and WWAN radio interface 124 of FIG. 1 , or communication subsystems 211 and 291 of FIG. 2 ) associated with the two different types of networks (WLAN and WWAN).
- Mobile terminal 106 may generally have wireless access to only one of the networks for services at any given time. As it moves along travel path 310 , in order to maintain continuity in service when losing coverage with its current wireless network, mobile terminal 106 is required to switch its communication operations to a different wireless network. For example, mobile terminal 106 may switch communication operations from WLAN 102 to PLMN 105 .
- FIG. 7 an illustrative representation of the communication system of FIG. 1 is shown, where mobile terminal 106 performs communication operations in WLAN 102 over a wireless link 702 .
- FIG. 8 mobile terminal 106 is shown to switch from communication operations in WLAN 102 to PLMN 105 over a wireless link 802 .
- the general methodology for switching may be based on processing of a received signal strength indicator (RSSI) of a radio frequency (RF) signal from the wireless AP of the WLAN (e.g.
- RSSI received signal strength indicator
- RF radio frequency
- the switching operation may be initiated by mobile terminal 106 itself, or with the assistance or instruction from the network.
- FIG. 4 a general illustrative representation of the communication system of FIG. 1 which may be utilized for facilitating the communication of neighboring network information to the mobile terminal is shown.
- mobile terminal 106 while operating in WLAN 102 , mobile terminal 106 sends a request for neighboring network information to WLAN 102 .
- the NAS associated with wireless AP 112 of WLAN 102 receives and identifies such request and, in response, produces and sends a corresponding request for the neighboring network information in accordance with a RADIUS compatible protocol.
- the corresponding request may be sent to AAA server 180 of core network 136 of (e.g. the home) PLMN 104 associated with mobile terminal 106 .
- AAA server 180 has access to and retrieves the neighboring network information in response to the corresponding request.
- the neighboring network information may be correlated based on NAS location or the like, and may be stored either locally or at a mobility server. For example, the neighboring network information may be stored in a database based on an identification of the NAS.
- the neighboring network information includes one or more network identifications of one or more wireless networks (e.g. other surrounding PLMNs, WLANs in the figure) located within the vicinity of WLAN 102 .
- the wireless networks identified may be any suitable type of wireless networks, including GSM, GPRS/EDGE, UMTS, WLANs, WiMAX, etc.
- AAA server 180 replies, in accordance with the RADIUS compatible protocol, to the NAS of wireless AP 112 with a response which includes the retrieved neighboring network information.
- the NAS of wireless AP 112 then sends the neighboring network information to mobile terminal 106 . Thereafter, mobile terminal 106 may make a handover decision for handover from the WLAN 102 to a selected one of the other wireless networks identified from the received network identifications. Note that, in some embodiments, the communications for obtaining the neighboring network information are facilitated via proxy server 190 of LAN 110 , which is described in more detail later below.
- the procedures are performed in accordance with Media Independent Handover (MIH) defined by IEEE 802.21.
- MIH Media Independent Handover
- IEEE 802.21 defines a transport agnostic protocol for MIH and three services: a command service to co-ordinate handover between mobile terminals and networks; an event server to exchange link state information between mobile terminals and networks; and an information service to exchange information on neighboring network handover candidates.
- the request/response for the neighboring network information may be an IEEE 802.21 information request/response.
- the request/response may be communicated in accordance with IEEE 802.11u or an extensible authentication protocol (EAP).
- EAP extensible authentication protocol
- a mobile terminal requests information from the WLAN in order to obtain network service information using the defined generic access service (GAS) procedures.
- GAS generic access service
- IEEE 802.11u specifies two mechanisms to obtain the information, one for unicast and one for multicast. In both mechanisms, the mobile terminal initiates service discovery by sending a GAS Initial Request frame. The mobile terminal sends a GAS Initial Request frame since the service information is not included in the beacon or probe response(s).
- the request/response may be communicated in accordance with IEEE 802.16g.
- FIG. 5 is a process flow diagram for describing a technique for use in facilitating communication of neighboring network information to a mobile terminal, which may be utilized in the environment described above in relation to FIGS. 1-4 .
- the technique of the present disclosure may be embodied in a server (e.g. a network access server, an information server which may be an AAA server, RADIUS server, etc.) having one or more processors.
- Other techniques may be embodied in a mobile terminal having one or more processors adapted to execute the technique.
- the technique may be further embodied in a computer program product having a computer readable medium and computer instructions stored in the computer readable medium, where the one or more processors are operative to execute the computer instructions in accordance with the method.
- the NAS is part of AP 112 , even though it may be an entity in WLAN 102 that is separate from AP 112 .
- the method of FIG. 5 begins where mobile terminal 106 performs a discovery and attachment procedure with AP 112 of WLAN 102 (step 502 of FIG. 5 ).
- the discovery procedure with AP 112 involves scanning to identifying available wireless networks in the coverage region of mobile terminal 106 .
- the discovery procedure may include the mobile terminal's sending of a probe request and the receiving of a probe response. If the probe request/response is successful, an authentication request and response is exchanged. Successful authentication permits further specified data exchange, for example, to the attachment procedure.
- an association request and response is exchanged. Successful association permits further specified data exchange such as data frames, management frames, and control frame.
- the association request data frame may, for example, include capability information, listen interval, SSID of WLAN 102 , and supported rates.
- the association response data frame may, for example, include capability information, status codes, association ID, and supported rates.
- mobile terminal 106 After its association with AP 112 , mobile terminal 106 produces and causes a request for neighboring network information to be transmitted via WLAN 102 (step 504 of FIG. 5 ).
- the request may include various information including an identification of mobile terminal 106 (e.g. telephone number, personal identification number or PIN, e-mail address, etc.) and an identification of WLAN 102 (e.g. set service identification or SSID, extended SSID or ESSID, etc.).
- This request may be or include an IEEE 802.21 information request for the neighboring network information.
- the request may be communicated in accordance with IEEE 802.11u or, more specifically, IEEE 802.11u generic access service (GAS).
- GAS IEEE 802.11u generic access service
- the request may be communicated in accordance with IEEE 802.16g.
- AP 112 identifies this request to be for obtaining neighboring network information (e.g. it may identify it as an IEEE 802.21 information request). In response, AP 112 performs certain processing to obtain this information on behalf of mobile terminal 106 . In particular, AP 112 produces a corresponding request for the neighboring network information in accordance with a remote access dial-in user server (RADIUS) compatible protocol.
- the RADIUS compatible protocol utilized may be a RADIUS protocol.
- the RADIUS compatible protocol may be a Diameter NASREQ protocol, which is backward-compatible with RADIUS. Note that, as a NAS function may be part of AP 112 , this NAS function may include a RADIUS or RADIUS compatible (e.g.
- AP 112 sends the corresponding request in accordance with the RADIUS compatible protocol to AAA server 180 of core network 136 (step 506 of FIG. 5 ), which receives it.
- AP 112 addresses the corresponding request to AAA server 180 based on a network access identifier (NAI) of mobile terminal 106 and a NAS Port of the NAS in AP 112 , which are supplied in the request.
- NAI network access identifier
- a RADIUS type-length value may be utilized in the communication of the corresponding request.
- the TLV may include a type indicative of “interworking-request”, a length which is variable, and a value which is the string containing the request in accordance with IEEE 802.21 MIH or IEEE 802.11u GAS.
- AAA server 180 retrieves neighboring network information corresponding to an indication provided in the request.
- the indication is provided to AAA server 180 by the identification of WLAN 102 (e.g. SSID or ESSID), and/or cell identifications (Cell IDs), and/or the NAS ID of the AAA client, as supplied from the request.
- the neighboring network information includes one or more network identifications corresponding to one or more wireless communication networks neighboring or within the coverage region of WLAN 102 .
- the wireless networks identified may be any type of suitable wireless networks, including GSM, GPRS/EDGE, UMTS, WLANs, WiMAX, etc.
- AAA server 180 may selectively retrieve neighboring network information that is unique to each given location as indicated in such requests.
- At least some of the networks indicated by the neighboring network information are networks that mobile terminal 106 may be handed over to in the event mobile terminal 106 exits from WLAN 102 .
- the one or more neighboring wireless communication networks may be compatible with cellular telecommunications, IEEE 802.11, or IEEE 802.16 standards, as examples.
- AAA server 180 may retrieve the neighboring network information from a locally-stored table, or a database, using a request/response protocol with the indication or location from the request as an input or key. In one embodiment, AAA server 180 may retrieve the neighboring network information from a different server, such as an outside, external mobility server. In this example, AAA server 180 may submit a request to the mobility server with the indication or location (step 508 of FIG. 5 ) and, in response, receive a response which includes the neighboring network information (step 510 of FIG. 5 ).
- the mobility server may be adapted to receive and serve requests from many different similarly-situated servers (one of which is AAA server 180 ) deployed in different networks at different locations.
- the mobility server may have access to one or more databases which store local, regional, or global network information (such as a global network map), information which may be retrieved request/response protocol which utilizes an indication or location as an input or key, for example.
- AAA server 180 sends the neighboring network information to AP 112 in accordance with the RADIUS compatible protocol, and AP 112 receives this information in response (step 512 of FIG. 5 ).
- AP 112 then suitably formats and sends, to mobile terminal 106 , a response to the initial request which includes the neighboring network information (step 514 of FIG. 5 ).
- the response may be or include an IEEE 802.21 information response having the neighboring network information.
- IEEE 802.11 for example, the response may be communicated in accordance with IEEE 802.11u.
- IEEE 802.16 for example, the response may be communicated in accordance with IEEE 802.16g.
- the neighboring network information includes one or more network identifications of one or more wireless networks located within the coverage region of WLAN 102 .
- the neighboring network information may thereafter be utilized by mobile terminal 106 to perform a handover to another neighboring network different from and neighboring the coverage region of mobile terminal 106 or WLAN 102 , without the need to perform exhausting scanning operations to locate various different neighboring networks.
- FIG. 6 is another process flow diagram for describing another technique for use in facilitating communication of neighboring network information to the mobile terminal, which also may be utilized in the environment described above in relation to FIGS. 1-4 .
- the technique of the present disclosure may be embodied in a server (e.g. a network access server, an information server such as an AAA server, etc.) having one or more processors.
- Other techniques may be embodied in a mobile terminal having one or more processors adapted to execute the technique.
- the technique may be further embodied in a computer program product having a computer readable medium and computer instructions stored in the computer readable medium, where the one or more processors are operative to execute the computer instructions in accordance with the method.
- the NAS is part of AP 112 , even though it may be an entity in WLAN 102 that is separate from AP 112 .
- the method of FIG. 6 begins where mobile terminal 106 performs a discovery and attachment procedure with AP 112 of WLAN 102 (step 602 of FIG. 6 ).
- the discovery procedure with AP 112 involves scanning to identify available wireless networks in the coverage region of mobile terminal 106 .
- the discovery procedure may include the mobile terminal's sending of a probe request and the receiving of a probe response.
- An authentication request and response is exchanged once the probe request/response is successful.
- Successful authentication permits further specified data exchange, for example, to the attachment procedure.
- an association request and response is exchanged.
- Successful association permits further specified data exchange such as data frames, management frames, and control frame.
- the association request data frame may, for example, include capability information, listen interval, SSID of WLAN 102 , and supported rates.
- the association response data frame may, for example, include capability information, status codes, association ID, and supported rates.
- mobile terminal 106 After its association with AP 112 , mobile terminal 106 performs an authentication procedure with the network.
- the authentication procedure may be performed in accordance with an extensible authentication protocol (EAP).
- EAP extensible authentication protocol
- mobile terminal 112 causes a request for neighboring network information to be transmitted to AP 112 in an EAP frame (step 604 of FIG. 6 ).
- the request may include various information including an identification of mobile terminal 106 (e.g. telephone number, personal identification number or PIN, e-mail address, etc.) and an identification of WLAN 102 (e.g. set service identification or SSID, extended SSID or ESSID, etc.).
- This request may be or include an IEEE 802.21 information request for the neighboring network information.
- AP 112 identifies this request to be for obtaining neighboring network information (e.g. it may identify it as an IEEE 802.21 information request) and, in response, performs certain processing to obtain this information on behalf of mobile terminal 106 .
- AP 112 produces a corresponding request for the neighboring network information in accordance with a RADIUS compatible protocol.
- the RADIUS compatible protocol utilized may be a RADIUS protocol or a Diameter NASREQ protocol (which is backward-compatible with RADIUS), as examples.
- this NAS function may include a RADIUS or RADIUS compatible client (e.g. Diameter NASREQ client) to serve these purposes.
- AP 112 encapsulates the EAP request for the neighboring network information into the corresponding RADIUS-compatible request and sends it to AAA server 180 of core network 136 (step 606 of FIG. 6 ), which receives it.
- AP 112 addresses the corresponding request to AAA server 180 based on a network access identifier (NAI) of mobile terminal 106 and a NAS Port of the NAS in AP 112 , which are supplied in the request.
- NAI network access identifier
- the request is embedded as a type-length value (TLV) in an EAP frame from mobile terminal 106 , and the corresponding request includes a RADIUS attribute set to an EAP-message (e.g. value of 79).
- this messaging may be viewed as an EAP TLV embedded in a RADIUS TLV.
- Any suitable implementation or protocol may be utilized for such messaging, such as EAP-FAST TLV based on RFC 4851, Protected EAP Protocol (PEAP) (e.g. Palekar et al., “Protected EAP Protocol (PEAP) Version 2”, EAP Working Group, 15 Oct. 2004, Internet-Draft: draft-josefsson-pppext-eap-tls-eap-10.txt), or EAP-TTLS described as AVPs in RFC 5281, as examples.
- PEAP Protected EAP Protocol
- AAA server 180 decapsulates the message to reveal the underlying EAP request for the neighboring network information. Then, AAA server 180 retrieves neighboring network information corresponding to an indication provided in the request.
- the indication provided to AAA server 180 by the identification of WLAN 102 (e.g. SSID or ESSID), and/or cell identifications (Cell IDs), and/or the NAS ID of the AAA client, as supplied in the request.
- the neighboring network information of FIG. 6 includes one or more network identifications corresponding to one or more wireless communication networks neighboring the WLAN 102 .
- the wireless networks identified may be any type of suitable wireless networks, including GSM, GPRS/EDGE, UMTS, WLANs, WiMAX, etc.
- AAA server 180 may retrieve the neighboring network information from the locally-stored table or the database using the request/response protocol, or from a different server such as the mobility server, where AAA server 180 submits a request to the mobility server with the indication of the location (step 608 of FIG. 6 ) and receives a response which includes the neighboring network information (step 610 of FIG. 6 ).
- AAA server 180 produces an EAP response which includes the neighboring network information.
- the EAP response is encapsulated in the RADIUS compatible protocol and sent to AP 112 ; AP 112 receives this information in response (step 612 of FIG. 6 ).
- AP 112 decapsulates the message to reveal the underlying EAP response having the neighboring network information.
- AP 112 sends, to mobile terminal 106 in response to the EAP request of step 604 , the EAP response which includes the neighboring network information (step 614 of FIG. 6 ).
- the EAP response may be or include an IEEE 802.21 information response having the neighboring network information.
- the neighboring network information may thereafter be utilized by mobile terminal 106 to perform a handover to another neighboring network different from and neighboring the coverage region of mobile terminal 106 or WLAN 102 (e.g. based on RSSI, SNR, or other signal conditions or events), without the need to perform exhausting scanning operations to locate various different neighboring networks.
- AAA proxying in WLAN 102 may be required for the communications.
- mobile terminal 106 may be identified by and associated with the NAI of “user@abc.com”
- WLAN 102 may be an “ABC” hotspot
- AAA server 180 may be addressable or identifiable by the domain of “abc.com”.
- communications between the NAS of WLAN 102 and AAA server 180 of core network 136 may be direct without the need for proxying.
- a first service provider may manage PLMN 104 /core network 136 and mobile terminal 106
- a second different service provider may manage WLAN 102
- AAA “proxy” server 190 is provided in LAN 110 , for proxying the communications between the NAS and AAA server 180 (see FIGS. 1 and 4 ).
- mobile terminal 106 may be identified by and associated with the NAI of “user@abc.com”, AAA server 180 of core network 136 may be addressable or identifiable at “abc.com”, WLAN 102 may be a “DEF” hotspot, and proxy server 190 of LAN 110 may be addressable or identifiable at the domain of “def.com”.
- mobile terminal 106 submits its request to the NAS, providing its NAI which includes the realm of “abc.com”.
- the NAS provides the request to proxy server 190 , which identifies the realm of “abc.com” in the request and directs the request to AAA server 180 of core network 136 associated with “abc.com”.
- AAA server 180 processes the request accordingly and submits a response back to proxy server 190 , which provides it back to the NAS of WLAN 102 and thereafter to mobile terminal 106 .
- proxy server 190 provides it back to the NAS of WLAN 102 and thereafter to mobile terminal 106 .
- NAIs and realms may be utilized to facilitate the communication of proper neighboring network information for mobile terminals.
- mobile terminal 106 may cause the request to be transmitted to the proper AAA server in different ways.
- the communication of neighboring network information to mobile terminals is efficiently facilitated for handover purposes, without requiring excessive scanning by the mobile terminal, and without burdensome and difficult deployment of network components or modules in existing networks.
- a technique in a radio access network involves receiving, from a mobile terminal, a request for neighboring network information; producing, in response to receiving the request, a corresponding request for the neighboring network information in accordance with a remote access dial-in user server (RADIUS) compatible protocol; sending the corresponding request to an information server (e.g.
- a radio access network e.g. in a network access server or NAS
- a technique in a radio access network involves receiving, from a mobile terminal, a request for neighboring network information; producing, in response to receiving the request, a corresponding request for the neighboring network information in accordance with a remote access dial-in user server (RADIUS) compatible protocol; sending the corresponding request to an information server (e.g.
- RADIUS remote access dial-in user server
- the request/response for the neighboring network information may be an IEEE 802.21 information request/response. If the radio access network is a wireless local area network (WLAN) adapted in accordance with IEEE 802.11, the request/response may be communicated in accordance with IEEE 802.11u or an extensible authentication protocol (EAP). If the radio access network is a WiMAX network adapted in accordance with IEEE 802.16, the request/response may be communicated in accordance with 802.16g.
- WLAN wireless local area network
- EAP extensible authentication protocol
- a technique in the information server of the core network of the PLMN involves receiving, from the radio access network, a request for neighboring network information in accordance with a RADIUS compatible protocol (e.g. RADIUS or Diameter NASREQ); retrieving, in response to receiving the request, neighboring network information corresponding to an indication provided in the request; and sending, to the radio access network, in response to receiving the request, the retrieved neighboring network information in accordance with the RADIUS compatible protocol.
- a RADIUS compatible protocol e.g. RADIUS or Diameter NASREQ
- the techniques of the present disclosure may be embodied in a server (e.g. a network access server, an information server such as an AAA server, etc.) having one or more processors.
- Other techniques may be embodied in a mobile terminal having one or more processors adapted to execute the technique.
- the technique may be further embodied in a computer program product having a computer readable medium and computer instructions stored in the computer readable medium, where the one or more processors are operative to execute the computer instructions in accordance with the method.
- the technique described assumes that the mobile terminal is a mobile communication device of the dual-mode type, having both WLAN and WWAN radio interfaces.
- mobile terminal 106 may have only a single (radio) interface for access (e.g. only WLAN radio interface 122 ) and operates accordingly without the other interface.
- the embodiments of the present disclosure are generally directed to an example where the WLAN is an IEEE 802.11-based network and the WWAN is a cellular telecommunications network.
- the WLAN and WWAN may be networks different from those networks.
- the WLAN may be a WiMAX-based network (i.e. IEEE 802.16), an Ultra-WideBand (UWB)-based network (i.e. IEEE 802.15), a Bluetooth-based network, as a few examples.
- the WWAN may be a Long-Term Evolution (LTE)-based network, an EVolution-Data Only (EV-DO)-based network, or a UMTS-based network, as a few examples.
- LTE Long-Term Evolution
- EV-DO EVolution-Data Only
- UMTS Universal Mobile Telecommunications
- the embodiments described herein in the recited claims intend to cover and embrace all suitable changes in technology.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Mobile Radio Communication Systems (AREA)
- Small-Scale Networks (AREA)
Abstract
Description
- This patent claims the benefit of U.S. Provisional Patent Application No. 61/184,116, filed on Jun. 4, 2009, which is hereby incorporated herein by reference in its entirety.
- The present disclosure relates generally to communication techniques for assisting wireless mobile terminals for wireless communications, and more particularly to techniques for facilitating the communication of neighboring network information to mobile terminals for handover purposes.
- Mobile terminals may be adapted to operate in one or more of a variety of different types of wireless networks, such as wireless local area networks (WLANs), WiMAX networks, cellular telecommunication networks, etc. When operating in a WLAN or WiMAX network, the mobile terminal may lose radio coverage with the network or otherwise need to switch to an alternative neighboring wireless network to continue communications.
- To do this, the mobile terminal could scan using its one or more wireless transceivers to identify available wireless networks in its coverage region. Excessive scanning by the mobile terminal, however, may consume too much time and power of the mobile terminal. It may be helpful, on the other hand, if the identifications of the available wireless networks could be obtained by the mobile terminal via the current wireless network before the switching occurs. Given the new network components and modules which could be required to achieve this goal, however, deployment could become burdensome and difficult, especially given the many diverse wireless networks already in existence today.
- Embodiments of present disclosure will now be described by way of example with reference to attached figures, wherein:
-
FIG. 1 is an illustrative representation of a communication system which includes a radio access network (RAN), which may be a wireless local area network (WLAN) such as an IEEE 802.11-based wireless network, and a wireless wide area network (WWAN) such as a public land mobile network (PLMN), within which a mobile terminal may operate; -
FIG. 2 is a schematic diagram of the mobile terminal which may operate in both the WLAN and the PLMN ofFIG. 1 ; -
FIG. 3 is a top down view showing the mobile terminal moving in accordance with a travel path through coverage regions of the WLAN and the PLMN ofFIG. 1 ; -
FIG. 4 is a general illustrative representation of the communication system ofFIG. 1 which may be utilized for facilitating the communication of neighboring network information to the mobile terminal; -
FIG. 5 is a process flow diagram for describing a technique for use in facilitating communication of neighboring network information to the mobile terminal in the environments described in relation toFIGS. 1-4 ; -
FIG. 6 is another process flow diagram for describing another technique for use in facilitating communication of neighboring network information to the mobile terminal in the environments described in relation toFIGS. 1-4 ; -
FIG. 7 is an illustrative representation of the communication system ofFIG. 1 , where the mobile terminal is shown to perform communication operations in the WLAN; and -
FIG. 8 is an illustrative representation of the communication system ofFIG. 1 , where the mobile terminal switches from communication operations in the WLAN to the PLMN. - What are described herein are methods and apparatus for use in facilitating the communication of neighboring network information to a mobile terminal. The communication of neighboring network information to mobile terminals for handover purposes as described herein does not require excessive scanning by the mobile terminal, and does not require burdensome and difficult deployment of network components or modules.
- One illustrative technique is employed in a radio access network, such as a wireless local area network (WLAN). This technique involves the steps of receiving, from the mobile terminal, a request for neighboring network information; producing, in response to receiving the request, a corresponding request for the neighboring network information in accordance with a remote access dial-in user server (RADIUS) compatible protocol; sending the corresponding request to an information server (e.g. an authentication, authorization, and accounting (AAA) server) of a core network of a public land mobile network (PLMN) associated with the mobile terminal; receiving, from the information server, in response to the corresponding request, the neighboring network information in accordance with the RADIUS compatible protocol; and sending, in response to the request, the neighboring network information to the mobile terminal. The request/response for the neighboring network information may be an IEEE 802.21 information request/response. If the radio access network is a WLAN adapted in accordance with IEEE 802.11, the request/response may be communicated in accordance with IEEE 802.11u (e.g. generic access service or GAS) or an extensible authentication protocol (EAP). If the radio access network is a WiMAX network adapted in accordance with IEEE 802.16, the request/response may be communicated in accordance with IEEE 802.16g.
- Another illustrative technique is employed in the information server of the core network of the PLMN and involves receiving, from the radio access network, a request for neighboring network information in accordance with the RADIUS compatible protocol; retrieving, in response to receiving the request, neighboring network information corresponding to an indication provided in the request; and sending, to the network access server, in response to receiving the request, the retrieved neighboring network information in accordance with the RADIUS compatible protocol.
- To help further illustrate these techniques,
FIG. 1 is an illustrative representation of acommunication system 100 which includes a wireless local area network (WLAN) 102 and a public land mobile network (PLMN) 104. WLAN 102 may be or be referred to as one type of radio access network (RAN) utilized by amobile terminal 106. Having one or more base stations and base station controllers, PLMN 104 may be or be referred to as a wireless wide area network (WWAN) or a mobile telecommunications network which may be further utilized bymobile terminal 106. - In the embodiment described, WLAN 102 is an IEEE 802.11-based wireless network.
WLAN 102 may be part of a communication network such as a local area network (LAN) 110. In this embodiment, LAN 110 is part of a private communication network, which may be an enterprise network of an enterprise having a gateway including afirewall 116. Alternatively, LAN 110 may be a public communication network which may not require any gateway. Terminals may connect toLAN 110 through any suitable means, such as through a plurality of wireless access points (APs) (e.g. APs 112 and 114) ofWLAN 102. Such mobile terminals and wireless APs can operate in accordance with IEEE 802.11 standards. - LAN 110, which includes WLAN 102, provides various local data and communication services to its terminals. For example, LAN 110 may provide for voice telephony communication services for its terminals with use of Voice over IP (VoIP) communications. For such services, LAN 110 may utilize servers such as a
VoIP type server 118 or at least one session server which is a session initiation protocol (SIP) server. Communication applications, such as VoIP applications, may require the use of SIP. SIP is well-documented in standard documents such as Request For Comments (RFC) 3261. In some embodiments,LAN 110 also includes an AAA proxy server (or “proxy server”) 190, the purpose and use of which will be described in more detail below. - Note that each wireless AP may include or cooperate with a network access server (NAS) function of
WLAN 102. In general, a NAS serves as a gateway for a network to guard access to a protected resource; typically, when a mobile terminal connects to a NAS, the NAS communicates with another network resource to identify whether credentials of the mobile terminal are valid for granting/denying access. - PLMN 104 includes a
core network 136, a plurality of base station controllers such as a base station controller (BSC) 138 coupled tocore network 136, and a plurality of base stations such as a base station (BS) 140 coupled to associatedBSCs 138. Corenetwork 136, BSC 138, andbase station 140 operate in a conventional fashion as well-documented. Other PLMNs in the environment have a similar or the same architecture as PLMN 104, such as a PLMN 105 having acore network 146, a plurality of base station controllers such as a base station controller (BSC) 148, a plurality of base stations such as a base station (BS) 150 coupled to associatedBSCs 148, and a gateway/controller 144 provided between the Internet 101 andcore network 146. - In this example,
mobile terminal 106 ofLAN 110 is shown as a mobile communication device/wireless handset (WH) of the dual-mode type, having both WLAN and WWAN radio interfaces. In particular,mobile terminal 106 is shown to have one ormore processors 120, aWLAN radio interface 122, a WWANradio interface 124, andantenna components radio interfaces mobile terminal 106 may access services ofcore network 136 of PLMN 104 with use of WWANradio interface 124, as well as access services ofLAN 110 with use ofWLAN radio interface 122. - Communications between
LAN 110 andcore network 136 of PLMN 104 may be facilitated through a suitable connecting network such as a broadband, wide-area IP communication network (e.g. the Internet 101) or any suitable public or private wide area network. Gateway/controller 142 is provided between the Internet 101 andcore network 136 of PLMN 104 in order to facilitate access tocore network 136 by terminals through alternative links (e.g. radio linkswireless APs 112 and 114) different than those conventional radio links offered in the PLMN 104 (e.g. radio links of base station 140). Thus,mobile terminal 106 may also access services ofcore network 136 of PLMN 104 via WLANs, such as WLAN 102, through use ofWLAN radio interface 122. For such communications, gateway/controller 142 andmobile terminal 106 are adapted to establish and maintain a (secure) tunnel connection between each other through the intervening networks. Note that WLAN 102 may be operator-controlled or provided (e.g. controlled or provided by the operator associated with PLMN 104), user-controlled or provided (e.g. controlled or provided by the end user of mobile terminal 106), or third-party-controlled or provided. -
Core network 136 also has an authentication, authorization, and accounting (AAA)server 180. Similarly,core network 146 has anAAA server 182.Such AAA servers AAA servers - When
mobile terminal 106 connects, the NAS typically sends a RADIUS Access-Request message toAAA server 180, relaying information such as the user's name and password, type of connection (port), NAS identity, and a message Authenticator. Upon receipt,AAA server 180 uses the packet source, NAS identity, and Authenticator to determine whether the NAS is permitted to send requests. If so,AAA server 180 attempts to identify the user's name in its database. It then applies the password and perhaps other attributes carried in the Access-Request to decide whether access should be granted to this user. Depending upon the authentication method being used,AAA server 180 may return a RADIUS Access-Challenge message that carries a random number. The NAS relays the challenge tomobile terminal 106, which must respond with the correct value to prove its asserted identity (e.g. encrypting the challenge with its password), which the NAS relays toAAA server 180 inside another RADIUS Access-Request message. IfAAA server 180 is satisfied thatmobile terminal 106 is authentic and authorized to use the requested service, it returns a RADIUS Access-Accept message. If not,AAA server 180 returns a RADIUS Access-Reject message and the NAS disconnectsmobile terminal 106. When an Access-Accept message is received and RADIUS Accounting is enabled, the NAS sends a RADIUS Accounting-Request (Start) message toAAA server 180.AAA server 180 adds an accounting record to its log and acknowledges the request, whereupon the NAS activates the user's session. At the end of the session, a similar RADIUS Accounting-Request (Stop) message is exchanged so that accounting records will reflect the actual session duration and disconnect reason. - Alternatively,
AAA servers - Diameter is defined in terms of a base protocol and a set of applications, which allows the protocol to be extended to new access technologies. The base protocol provides basic mechanisms for reliable transport, message delivery, and error handling. The base protocol is used in conjunction with a Diameter application. Each application relies on the services of the base protocol to support a specific type of network access. The two major applications are Mobile IPv4 and NASREQ. The base protocol defines the basic Diameter message format. Data is carried within a Diameter message as a collection of Attribute-Value Pairs (AVPs), which are similar to RADIUS attributes. An AVP consists of multiple fields including an AVP Code, a Length, Flags, and Data. RFC 3169, Criteria for Evaluating Network Access Server Protocols, defines a number of requirements for AAA protocols used by NASs, addressing transport requirements, scalability, server failover, AVP requirements, security, authentication, authorization, policy, resource management, accounting, and more. RFC 2477, Criteria for Evaluating Roaming Protocols, similarly addresses the needs of AAA protocols supporting a roaming environment. The Diameter NASREQ application (combined with the base protocol) satisfies the requirements of both of these specifications. Even further, the NASREQ application, with native Extensible Authentication Protocol (EAP), offers secure authentication. The NASREQ application defines the Diameter-EAP-Request and Diameter-EAP-Answer messages that allow the EAP payload to be encapsulated within the Diameter protocol. The NASREQ application's AA-Request message corresponds to the RADIUS Access-Request. The AA-Answer message corresponds to the RADIUS Access-Accept and Access-Reject messages. The NASREQ application has guidelines to be used by a server that acts as a RADIUS-Diameter protocol gateway, i.e. a server that receives a RADIUS message that is to be translated and transmitted as a Diameter message, and vice versa.
- Note that the description of the architecture for
FIG. 1 relates to a specific example for illustration, where the WLAN is an IEEE 802.11-based network and the WWAN is a cellular telecommunications network. However, the WLAN and WWAN may be networks different from those networks. The WLAN may be a WiMAX-based network (i.e. IEEE 802.16), a Ultra-WideBand (UWB)-based network (i.e. IEEE 802.15), a Bluetooth-based network, as a few examples. The WWAN may be a Long-Term Evolution (LTE)-based network, an EVolution-Data Only (EV-DO)-based network, or a UMTS-based network, as a few examples. - Referring now to
FIG. 2 , electrical components of a typical mobile terminal 106 (e.g. a wireless handset, a mobile station) which operates in a wireless network environment which includes both WLANs (represented inFIG. 2 by AP 112) and WWANs/PLMNs (represented inFIG. 2 bycellular base stations 200 which includebase stations Mobile terminal 106 may be representative of one or more terminals which operate incommunication system 100 ofFIG. 1 .Mobile terminal 106 can be a two-way communication device having at least voice and advanced data communication capabilities, including the capability to communicate with other computer systems. Depending on the functionality provided bymobile terminal 106, it may be referred to as a data messaging device, a two-way pager, a cellular telephone with data messaging capabilities, a wireless Internet appliance, or a data communication device (with or without telephony capabilities). - As shown in
FIG. 2 ,mobile terminal 106 is adapted to wirelessly communicate withbase stations 200. For communication withbase stations 200,mobile terminal 106 utilizes acommunication subsystem 211 which includes RF transceiver circuitry.Communication subsystem 211 includes areceiver 212, a transmitter 214, and associated components, such as one or more (embedded or internal)antenna elements communication subsystem 211 depends on the communication network in whichmobile terminal 106 is intended to operate. In the present application, communication subsystem 211 (including its associated processor/processing components) are operative in accordance with a cellular or other suitable WWAN standards (i.e. a standard other than IEEE 802.11), such as GSM/GPRS standards. -
Mobile terminal 106 may send and receive communication signals through the network after required network procedures have been completed. Signals received byantenna 216 through the network are input toreceiver 212, which may perform such common receiver functions as signal amplification, frequency down conversion, filtering, channel selection, and like, and in example shown inFIG. 2 , analog-to-digital (A/D) conversion. A/D conversion of a received signal allows more complex communication functions such as demodulation and decoding to be performed inDSP 220. In a similar manner, signals to be transmitted are processed, including modulation and encoding, for example, byDSP 220. These processed signals are input to transmitter 214 for digital-to-analog (D/A) conversion, frequency up conversion, filtering, amplification and transmission through the network viaantenna 218.DSP 220 not only processes communication signals, but may also provide for receiver and transmitter control. Note thatreceiver 212 and transmitter 214 may share one or more antennas through an antenna switch (not shown inFIG. 2 ), instead of having two separatededicated antennas -
Mobile terminal 106 also has acommunication subsystem 291 which includes RF transceiver circuitry operative in accordance with a suitable WLAN standard, such as the IEEE 802.11 standard, for communications with WLANs (e.g. represented byAP 112 inFIG. 2 ).Communication subsystem 291 is similar in structure and functionality tocommunication subsystem 211, whereDSP 220 may be replaced with a processing module referred to as a baseband (BB) and media access control (MAC) module. Althoughmobile terminal 106 may have separate and independent subsystems for these purposes, at least some portions or components of these otherwise different subsystems may be shared where possible. Asmobile terminal 106 operates in accordance with both a cellular network interface standard (e.g. GSM/GPRS standard) and the IEEE 802.11 standard, it may be referred to as a “dual mode” mobile terminal. - Since
mobile terminal 106 may be a handheld, portable, battery-powered device, it also includes abattery interface 254 for receiving one or morerechargeable batteries 256. Such abattery 256 provides electrical power to most if not all electrical circuitry inmobile terminal 106, andbattery interface 254 provides for a mechanical and electrical connection for it.Battery interface 254 is coupled to a regulator (not shown inFIG. 2 ) that provides a regulated voltage V to all of the circuitry. -
Mobile terminal 106 includes a microprocessor 238 (one type of processor or controller) that controls overall operation ofmobile terminal 106. This control includes the communication techniques of the present disclosure. Communication functions, including at least data and voice communications, are performed throughcommunication subsystem 211.Microprocessor 238 also interacts with additional device subsystems such as adisplay 222, aflash memory 224, a random access memory (RAM) 226, auxiliary input/output (I/O)subsystems 228, aserial port 230, a keyboard (or keypad) 232, aspeaker 234, amicrophone 236, a short-range communications subsystem 240, and any other device subsystems generally designated at 242. Some of the subsystems shown inFIG. 2 perform communication-related functions, whereas other subsystems may provide “resident” or on-device functions. Notably, some subsystems, such askeyboard 232 anddisplay 222, for example, may be used for both communication-related functions, such as entering a text message for transmission over a communication network, and device-resident functions such as a calculator or task list. Operating system software used bymicroprocessor 238 can be stored in a persistent store such asflash memory 224, which may alternatively be a read-only memory (ROM) or similar storage element (not shown). Specific device applications, or parts thereof, may be temporarily loaded into a volatile store such asRAM 226. -
Microprocessor 238, in addition to its operating system functions, enables execution of software applications onmobile terminal 106. A predetermined set of applications that control basic device operations, including at least data and voice communication applications, will normally be programmed and/or installed onmobile terminal 106 during its manufacture (including the network selection control techniques of the present disclosure). An application that may be loaded ontomobile terminal 106 may be a personal information manager (PIM) application having the ability to organize and manage data items relating to user such as, but not limited to, e-mail, calendar events, voice mails, appointments, and task items. Naturally, one or more memory stores are available onmobile terminal 106, and memory 262 (designed as “mem” inFIG. 2 ) such as a subscriber identity module (SIM) or the like coupled via aninterface 264 is used to facilitate storage of PIM data items and other user information. - The PIM application has the ability to send and receive data items via the wireless network. In one embodiment, PIM data items are seamlessly integrated, synchronized, and updated via the wireless network, with the wireless device user's corresponding data items stored and/or associated with a host computer system thereby creating a mirrored host computer on
mobile terminal 106 with respect to such items. This can be especially useful where the host computer system is the wireless device user's office computer system. Additional applications may also be loaded ontomobile terminal 106 through network, an auxiliary I/O subsystem 228,serial port 230, short-range communications subsystem 240, or any othersuitable subsystem 242, and installed by a user inRAM 226 or a non-volatile store (not shown) for execution bymicroprocessor 238. Such flexibility in application installation increases the functionality ofmobile terminal 106 and may provide enhanced on-device functions, communication-related functions, or both. For example, secure communication applications may enable electronic commerce functions and other such financial transactions to be performed usingmobile terminal 106. - In a data communication mode, a received signal such as a text message, an e-mail message, or web page download will be processed by
communication subsystem 211 and input tomicroprocessor 238.Microprocessor 238 will further process the signal for output to display 222 or alternatively to auxiliary I/O device 228. A user ofmobile terminal 106 may also compose data items, such as e-mail messages, for example, usingkeyboard 232 in conjunction withdisplay 222 and possibly auxiliary I/O device 228.Keyboard 232 is a complete alphanumeric keyboard and/or telephone-type keypad. These composed items may be transmitted over a communication network throughcommunication subsystem 211. For voice communications, the overall operation ofmobile terminal 106 is substantially similar, except that the received signals would be output tospeaker 234 and signals for transmission would be generated bymicrophone 236. Alternative voice or audio I/O subsystems, such as a voice message recording subsystem, may also be implemented onmobile terminal 106. Although voice or audio signal output is accomplished primarily throughspeaker 234,display 222 may also be used to provide an indication of the identity of a calling party, duration of a voice call, or other voice call related information, as some examples. -
Serial port 230 inFIG. 2 is normally implemented in a personal digital assistant (PDA)-type communication device for which synchronization with a user's desktop computer is a desirable, albeit optional, component.Serial port 230 enables a user to set preferences through an external device or software application and extends the capabilities ofmobile terminal 106 by providing for information or software downloads tomobile terminal 106 other than through a wireless communication network. The alternate download path may, for example, be used to load an encryption key ontomobile terminal 106 through a direct and thus reliable and trusted connection to thereby provide secure device communication. Short-range communications subsystem 240 ofFIG. 2 is an additional optional component that provides for communication between mobile terminal 106 and different systems or devices, which need not necessarily be similar devices. For example,subsystem 240 may include an infrared device and associated circuits and components, or a BLUETOOTH® communication module to provide for communication with similarly enabled systems and devices. BLUETOOTH® is a registered trademark of Bluetooth SIG, Inc. - Although a specific
mobile terminal 106 has just been described, any suitable mobile communication device or terminal may be part of the disclosed methods and apparatus which will be described in fuller detail below. -
FIG. 3 is a top down view of ageographic region 300, which showsmobile terminal 106 moving in accordance with atravel path 310 through a coverage region 350 of PLMN 105 (e.g. a GSM/GPRS based network) and a coverage region 304 ofWLAN 102. Coverage region 350 ofPLMN 105 may be defined by one or more base stations of the network, whereas coverage region 304 ofWLAN 102 may be defined by one ormore wireless APs coverage region 306 may be that of another wireless network, such as another WLAN or, alternatively, a WiMAX network. As shown,coverage regions 304 and 306 may overlap in whole or in part with coverage region 350 ofPLMN 105. As described earlier,mobile terminal 106 may have different transceiver portions (e.g.WLAN radio interface 122 andWWAN radio interface 124 ofFIG. 1 , orcommunication subsystems FIG. 2 ) associated with the two different types of networks (WLAN and WWAN).Mobile terminal 106 may generally have wireless access to only one of the networks for services at any given time. As it moves alongtravel path 310, in order to maintain continuity in service when losing coverage with its current wireless network,mobile terminal 106 is required to switch its communication operations to a different wireless network. For example,mobile terminal 106 may switch communication operations fromWLAN 102 toPLMN 105. - This is shown in more detail with reference ahead to
FIGS. 7 and 8 . InFIG. 7 , an illustrative representation of the communication system ofFIG. 1 is shown, wheremobile terminal 106 performs communication operations inWLAN 102 over awireless link 702. On the other hand, inFIG. 8 ,mobile terminal 106 is shown to switch from communication operations inWLAN 102 to PLMN 105 over awireless link 802. The general methodology for switching may be based on processing of a received signal strength indicator (RSSI) of a radio frequency (RF) signal from the wireless AP of the WLAN (e.g. AP 112 of WLAN 102), or a signal-to-noise ratio (SNR) of the RF signal from the wireless AP, or other signal conditions or events. The switching operation may be initiated bymobile terminal 106 itself, or with the assistance or instruction from the network. - Referring now to
FIG. 4 , a general illustrative representation of the communication system ofFIG. 1 which may be utilized for facilitating the communication of neighboring network information to the mobile terminal is shown. In general, while operating inWLAN 102,mobile terminal 106 sends a request for neighboring network information toWLAN 102. The NAS associated withwireless AP 112 ofWLAN 102 receives and identifies such request and, in response, produces and sends a corresponding request for the neighboring network information in accordance with a RADIUS compatible protocol. The corresponding request may be sent toAAA server 180 ofcore network 136 of (e.g. the home)PLMN 104 associated withmobile terminal 106.AAA server 180 has access to and retrieves the neighboring network information in response to the corresponding request. The neighboring network information may be correlated based on NAS location or the like, and may be stored either locally or at a mobility server. For example, the neighboring network information may be stored in a database based on an identification of the NAS. The neighboring network information includes one or more network identifications of one or more wireless networks (e.g. other surrounding PLMNs, WLANs in the figure) located within the vicinity ofWLAN 102. The wireless networks identified may be any suitable type of wireless networks, including GSM, GPRS/EDGE, UMTS, WLANs, WiMAX, etc.AAA server 180 replies, in accordance with the RADIUS compatible protocol, to the NAS ofwireless AP 112 with a response which includes the retrieved neighboring network information. The NAS ofwireless AP 112 then sends the neighboring network information tomobile terminal 106. Thereafter,mobile terminal 106 may make a handover decision for handover from theWLAN 102 to a selected one of the other wireless networks identified from the received network identifications. Note that, in some embodiments, the communications for obtaining the neighboring network information are facilitated viaproxy server 190 ofLAN 110, which is described in more detail later below. - In one embodiment, the procedures are performed in accordance with Media Independent Handover (MIH) defined by IEEE 802.21. The IEEE 802.21 standard defines a transport agnostic protocol for MIH and three services: a command service to co-ordinate handover between mobile terminals and networks; an event server to exchange link state information between mobile terminals and networks; and an information service to exchange information on neighboring network handover candidates.
- Thus, the request/response for the neighboring network information may be an IEEE 802.21 information request/response. For a wireless network that is a WLAN, the request/response may be communicated in accordance with IEEE 802.11u or an extensible authentication protocol (EAP). Under IEEE 802.11u, a mobile terminal requests information from the WLAN in order to obtain network service information using the defined generic access service (GAS) procedures. IEEE 802.11u specifies two mechanisms to obtain the information, one for unicast and one for multicast. In both mechanisms, the mobile terminal initiates service discovery by sending a GAS Initial Request frame. The mobile terminal sends a GAS Initial Request frame since the service information is not included in the beacon or probe response(s). For a wireless network that is a WiMAX network, the request/response may be communicated in accordance with IEEE 802.16g.
-
FIG. 5 is a process flow diagram for describing a technique for use in facilitating communication of neighboring network information to a mobile terminal, which may be utilized in the environment described above in relation toFIGS. 1-4 . The technique of the present disclosure may be embodied in a server (e.g. a network access server, an information server which may be an AAA server, RADIUS server, etc.) having one or more processors. Other techniques may be embodied in a mobile terminal having one or more processors adapted to execute the technique. The technique may be further embodied in a computer program product having a computer readable medium and computer instructions stored in the computer readable medium, where the one or more processors are operative to execute the computer instructions in accordance with the method. In the present discussion, it is assumed that the NAS is part ofAP 112, even though it may be an entity inWLAN 102 that is separate fromAP 112. - The method of
FIG. 5 begins wheremobile terminal 106 performs a discovery and attachment procedure withAP 112 of WLAN 102 (step 502 ofFIG. 5 ). The discovery procedure withAP 112 involves scanning to identifying available wireless networks in the coverage region ofmobile terminal 106. The discovery procedure may include the mobile terminal's sending of a probe request and the receiving of a probe response. If the probe request/response is successful, an authentication request and response is exchanged. Successful authentication permits further specified data exchange, for example, to the attachment procedure. During the attachment procedure, an association request and response is exchanged. Successful association permits further specified data exchange such as data frames, management frames, and control frame. The association request data frame may, for example, include capability information, listen interval, SSID ofWLAN 102, and supported rates. The association response data frame may, for example, include capability information, status codes, association ID, and supported rates. - After its association with
AP 112,mobile terminal 106 produces and causes a request for neighboring network information to be transmitted via WLAN 102 (step 504 ofFIG. 5 ). The request may include various information including an identification of mobile terminal 106 (e.g. telephone number, personal identification number or PIN, e-mail address, etc.) and an identification of WLAN 102 (e.g. set service identification or SSID, extended SSID or ESSID, etc.). This request may be or include an IEEE 802.21 information request for the neighboring network information. In the case of IEEE 802.11, for example, the request may be communicated in accordance with IEEE 802.11u or, more specifically, IEEE 802.11u generic access service (GAS). In the case of IEEE 802.16, for example, the request may be communicated in accordance with IEEE 802.16g. -
AP 112 identifies this request to be for obtaining neighboring network information (e.g. it may identify it as an IEEE 802.21 information request). In response,AP 112 performs certain processing to obtain this information on behalf ofmobile terminal 106. In particular,AP 112 produces a corresponding request for the neighboring network information in accordance with a remote access dial-in user server (RADIUS) compatible protocol. The RADIUS compatible protocol utilized may be a RADIUS protocol. As another example, the RADIUS compatible protocol may be a Diameter NASREQ protocol, which is backward-compatible with RADIUS. Note that, as a NAS function may be part ofAP 112, this NAS function may include a RADIUS or RADIUS compatible (e.g. Diameter or Diameter NASREQ) client to serve these purposes.AP 112 sends the corresponding request in accordance with the RADIUS compatible protocol toAAA server 180 of core network 136 (step 506 ofFIG. 5 ), which receives it.AP 112 addresses the corresponding request toAAA server 180 based on a network access identifier (NAI) ofmobile terminal 106 and a NAS Port of the NAS inAP 112, which are supplied in the request. In one embodiment, a RADIUS type-length value (TLV) may be utilized in the communication of the corresponding request. The TLV may include a type indicative of “interworking-request”, a length which is variable, and a value which is the string containing the request in accordance with IEEE 802.21 MIH or IEEE 802.11u GAS. - In response to receiving the request of
step 506,AAA server 180 retrieves neighboring network information corresponding to an indication provided in the request. In the present example, the indication is provided toAAA server 180 by the identification of WLAN 102 (e.g. SSID or ESSID), and/or cell identifications (Cell IDs), and/or the NAS ID of the AAA client, as supplied from the request. The neighboring network information includes one or more network identifications corresponding to one or more wireless communication networks neighboring or within the coverage region ofWLAN 102. The wireless networks identified may be any type of suitable wireless networks, including GSM, GPRS/EDGE, UMTS, WLANs, WiMAX, etc.AAA server 180 may selectively retrieve neighboring network information that is unique to each given location as indicated in such requests. At least some of the networks indicated by the neighboring network information are networks thatmobile terminal 106 may be handed over to in the eventmobile terminal 106 exits fromWLAN 102. The one or more neighboring wireless communication networks may be compatible with cellular telecommunications, IEEE 802.11, or IEEE 802.16 standards, as examples. -
AAA server 180 may retrieve the neighboring network information from a locally-stored table, or a database, using a request/response protocol with the indication or location from the request as an input or key. In one embodiment,AAA server 180 may retrieve the neighboring network information from a different server, such as an outside, external mobility server. In this example,AAA server 180 may submit a request to the mobility server with the indication or location (step 508 ofFIG. 5 ) and, in response, receive a response which includes the neighboring network information (step 510 ofFIG. 5 ). - Note that the mobility server may be adapted to receive and serve requests from many different similarly-situated servers (one of which is AAA server 180) deployed in different networks at different locations. The mobility server may have access to one or more databases which store local, regional, or global network information (such as a global network map), information which may be retrieved request/response protocol which utilizes an indication or location as an input or key, for example.
- After such retrieval,
AAA server 180 sends the neighboring network information toAP 112 in accordance with the RADIUS compatible protocol, andAP 112 receives this information in response (step 512 ofFIG. 5 ).AP 112 then suitably formats and sends, tomobile terminal 106, a response to the initial request which includes the neighboring network information (step 514 ofFIG. 5 ). The response may be or include an IEEE 802.21 information response having the neighboring network information. In the case of IEEE 802.11, for example, the response may be communicated in accordance with IEEE 802.11u. In the case of IEEE 802.16, for example, the response may be communicated in accordance with IEEE 802.16g. - Again, the neighboring network information includes one or more network identifications of one or more wireless networks located within the coverage region of
WLAN 102. The neighboring network information may thereafter be utilized bymobile terminal 106 to perform a handover to another neighboring network different from and neighboring the coverage region ofmobile terminal 106 orWLAN 102, without the need to perform exhausting scanning operations to locate various different neighboring networks. -
FIG. 6 is another process flow diagram for describing another technique for use in facilitating communication of neighboring network information to the mobile terminal, which also may be utilized in the environment described above in relation toFIGS. 1-4 . Again, the technique of the present disclosure may be embodied in a server (e.g. a network access server, an information server such as an AAA server, etc.) having one or more processors. Other techniques may be embodied in a mobile terminal having one or more processors adapted to execute the technique. The technique may be further embodied in a computer program product having a computer readable medium and computer instructions stored in the computer readable medium, where the one or more processors are operative to execute the computer instructions in accordance with the method. In the present discussion, it is assumed that the NAS is part ofAP 112, even though it may be an entity inWLAN 102 that is separate fromAP 112. - Similar to that described in relation to
FIG. 5 , the method ofFIG. 6 begins wheremobile terminal 106 performs a discovery and attachment procedure withAP 112 of WLAN 102 (step 602 ofFIG. 6 ). The discovery procedure withAP 112 involves scanning to identify available wireless networks in the coverage region ofmobile terminal 106. The discovery procedure may include the mobile terminal's sending of a probe request and the receiving of a probe response. An authentication request and response is exchanged once the probe request/response is successful. Successful authentication permits further specified data exchange, for example, to the attachment procedure. During the attachment procedure, an association request and response is exchanged. Successful association permits further specified data exchange such as data frames, management frames, and control frame. The association request data frame may, for example, include capability information, listen interval, SSID ofWLAN 102, and supported rates. The association response data frame may, for example, include capability information, status codes, association ID, and supported rates. - After its association with
AP 112,mobile terminal 106 performs an authentication procedure with the network. The authentication procedure may be performed in accordance with an extensible authentication protocol (EAP). During this procedure,mobile terminal 112 causes a request for neighboring network information to be transmitted toAP 112 in an EAP frame (step 604 ofFIG. 6 ). The request may include various information including an identification of mobile terminal 106 (e.g. telephone number, personal identification number or PIN, e-mail address, etc.) and an identification of WLAN 102 (e.g. set service identification or SSID, extended SSID or ESSID, etc.). This request may be or include an IEEE 802.21 information request for the neighboring network information. -
AP 112 identifies this request to be for obtaining neighboring network information (e.g. it may identify it as an IEEE 802.21 information request) and, in response, performs certain processing to obtain this information on behalf ofmobile terminal 106. In particular,AP 112 produces a corresponding request for the neighboring network information in accordance with a RADIUS compatible protocol. The RADIUS compatible protocol utilized may be a RADIUS protocol or a Diameter NASREQ protocol (which is backward-compatible with RADIUS), as examples. Note that, as a NAS function may be part ofAP 112, this NAS function may include a RADIUS or RADIUS compatible client (e.g. Diameter NASREQ client) to serve these purposes. In the present embodiment,AP 112 encapsulates the EAP request for the neighboring network information into the corresponding RADIUS-compatible request and sends it toAAA server 180 of core network 136 (step 606 ofFIG. 6 ), which receives it.AP 112 addresses the corresponding request toAAA server 180 based on a network access identifier (NAI) ofmobile terminal 106 and a NAS Port of the NAS inAP 112, which are supplied in the request. - In one embodiment, the request is embedded as a type-length value (TLV) in an EAP frame from
mobile terminal 106, and the corresponding request includes a RADIUS attribute set to an EAP-message (e.g. value of 79). In general, this messaging may be viewed as an EAP TLV embedded in a RADIUS TLV. Any suitable implementation or protocol may be utilized for such messaging, such as EAP-FAST TLV based on RFC 4851, Protected EAP Protocol (PEAP) (e.g. Palekar et al., “Protected EAP Protocol (PEAP) Version 2”, EAP Working Group, 15 Oct. 2004, Internet-Draft: draft-josefsson-pppext-eap-tls-eap-10.txt), or EAP-TTLS described as AVPs in RFC 5281, as examples. - In response to receiving the request of
step 606,AAA server 180 decapsulates the message to reveal the underlying EAP request for the neighboring network information. Then,AAA server 180 retrieves neighboring network information corresponding to an indication provided in the request. In the present example, the indication provided toAAA server 180 by the identification of WLAN 102 (e.g. SSID or ESSID), and/or cell identifications (Cell IDs), and/or the NAS ID of the AAA client, as supplied in the request. As described above in relation toFIG. 5 , the neighboring network information ofFIG. 6 includes one or more network identifications corresponding to one or more wireless communication networks neighboring theWLAN 102. The wireless networks identified may be any type of suitable wireless networks, including GSM, GPRS/EDGE, UMTS, WLANs, WiMAX, etc.AAA server 180 may retrieve the neighboring network information from the locally-stored table or the database using the request/response protocol, or from a different server such as the mobility server, whereAAA server 180 submits a request to the mobility server with the indication of the location (step 608 ofFIG. 6 ) and receives a response which includes the neighboring network information (step 610 ofFIG. 6 ). - After such retrieval,
AAA server 180 produces an EAP response which includes the neighboring network information. The EAP response is encapsulated in the RADIUS compatible protocol and sent toAP 112;AP 112 receives this information in response (step 612 ofFIG. 6 ). Upon receipt,AP 112 decapsulates the message to reveal the underlying EAP response having the neighboring network information.AP 112 sends, tomobile terminal 106 in response to the EAP request ofstep 604, the EAP response which includes the neighboring network information (step 614 ofFIG. 6 ). The EAP response may be or include an IEEE 802.21 information response having the neighboring network information. The neighboring network information may thereafter be utilized bymobile terminal 106 to perform a handover to another neighboring network different from and neighboring the coverage region ofmobile terminal 106 or WLAN 102 (e.g. based on RSSI, SNR, or other signal conditions or events), without the need to perform exhausting scanning operations to locate various different neighboring networks. - In the processes described in relation to
FIGS. 5 and 6 , it may be assumed that a single service provider managesPLMN 104/core network 136,mobile terminal 106, andWLAN 102; therefore, no AAA proxying inWLAN 102 may be required for the communications. Here,mobile terminal 106 may be identified by and associated with the NAI of “user@abc.com”,WLAN 102 may be an “ABC” hotspot, andAAA server 180 may be addressable or identifiable by the domain of “abc.com”. Again, communications between the NAS ofWLAN 102 andAAA server 180 ofcore network 136 may be direct without the need for proxying. - In alternate embodiments, however, different service providers may be involved where proxying in
WLAN 102 is utilized. For example, a first service provider may managePLMN 104/core network 136 andmobile terminal 106, whereas a second different service provider may manageWLAN 102. In such alternate embodiment, AAA “proxy”server 190 is provided inLAN 110, for proxying the communications between the NAS and AAA server 180 (seeFIGS. 1 and 4 ). Here,mobile terminal 106 may be identified by and associated with the NAI of “user@abc.com”,AAA server 180 ofcore network 136 may be addressable or identifiable at “abc.com”,WLAN 102 may be a “DEF” hotspot, andproxy server 190 ofLAN 110 may be addressable or identifiable at the domain of “def.com”. In the technique,mobile terminal 106 submits its request to the NAS, providing its NAI which includes the realm of “abc.com”. The NAS provides the request toproxy server 190, which identifies the realm of “abc.com” in the request and directs the request toAAA server 180 ofcore network 136 associated with “abc.com”.AAA server 180 processes the request accordingly and submits a response back toproxy server 190, which provides it back to the NAS ofWLAN 102 and thereafter tomobile terminal 106. As apparent, NAIs and realms may be utilized to facilitate the communication of proper neighboring network information for mobile terminals. Also as apparent,mobile terminal 106 may cause the request to be transmitted to the proper AAA server in different ways. - Thus, according to the present disclosure, the communication of neighboring network information to mobile terminals is efficiently facilitated for handover purposes, without requiring excessive scanning by the mobile terminal, and without burdensome and difficult deployment of network components or modules in existing networks.
- As described herein, a technique in a radio access network (e.g. in a network access server or NAS) involves receiving, from a mobile terminal, a request for neighboring network information; producing, in response to receiving the request, a corresponding request for the neighboring network information in accordance with a remote access dial-in user server (RADIUS) compatible protocol; sending the corresponding request to an information server (e.g. an AAA server, a RADIUS server, a Diameter NASREQ server, etc.) of a core network of a public land mobile network (PLMN) associated with the mobile terminal; receiving, from the information server, in response to sending the corresponding request, the neighboring network information in accordance with the RADIUS compatible protocol; and sending, in response to the request, the neighboring network information to the mobile terminal. The request/response for the neighboring network information may be an IEEE 802.21 information request/response. If the radio access network is a wireless local area network (WLAN) adapted in accordance with IEEE 802.11, the request/response may be communicated in accordance with IEEE 802.11u or an extensible authentication protocol (EAP). If the radio access network is a WiMAX network adapted in accordance with IEEE 802.16, the request/response may be communicated in accordance with 802.16g.
- As further described herein, a technique in the information server of the core network of the PLMN involves receiving, from the radio access network, a request for neighboring network information in accordance with a RADIUS compatible protocol (e.g. RADIUS or Diameter NASREQ); retrieving, in response to receiving the request, neighboring network information corresponding to an indication provided in the request; and sending, to the radio access network, in response to receiving the request, the retrieved neighboring network information in accordance with the RADIUS compatible protocol.
- As described, the techniques of the present disclosure may be embodied in a server (e.g. a network access server, an information server such as an AAA server, etc.) having one or more processors. Other techniques may be embodied in a mobile terminal having one or more processors adapted to execute the technique. The technique may be further embodied in a computer program product having a computer readable medium and computer instructions stored in the computer readable medium, where the one or more processors are operative to execute the computer instructions in accordance with the method. Further, the technique described assumes that the mobile terminal is a mobile communication device of the dual-mode type, having both WLAN and WWAN radio interfaces. In an alternative embodiment, however,
mobile terminal 106 may have only a single (radio) interface for access (e.g. only WLAN radio interface 122) and operates accordingly without the other interface. - The above-described embodiments of the present application are intended to be examples only. Those of skill in the art may affect alterations, modifications and variations to the particular embodiments without departing from the scope of the application. For example, the embodiments of the present disclosure are generally directed to an example where the WLAN is an IEEE 802.11-based network and the WWAN is a cellular telecommunications network. However, the WLAN and WWAN may be networks different from those networks. The WLAN may be a WiMAX-based network (i.e. IEEE 802.16), an Ultra-WideBand (UWB)-based network (i.e. IEEE 802.15), a Bluetooth-based network, as a few examples. The WWAN may be a Long-Term Evolution (LTE)-based network, an EVolution-Data Only (EV-DO)-based network, or a UMTS-based network, as a few examples. The embodiments described herein in the recited claims intend to cover and embrace all suitable changes in technology.
Claims (21)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/699,793 US20150237543A1 (en) | 2009-06-04 | 2015-04-29 | Methods And Apparatus For Use In Facilitating The Communication Of Neighboring Network Information To A Mobile Terminal With Use Of A Radius Compatible Protocol |
US15/611,604 US20170272986A1 (en) | 2009-06-04 | 2017-06-01 | Methods and apparatus for use in facilitating the communication of neighboring network information to a mobile terminal with use of a radius compatible protocol |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US18411609P | 2009-06-04 | 2009-06-04 | |
US12/793,977 US9629038B2 (en) | 2009-06-04 | 2010-06-04 | Methods and apparatus for use in facilitating the communication of neighboring network information to a mobile terminal with use of a radius compatible protocol |
US14/699,793 US20150237543A1 (en) | 2009-06-04 | 2015-04-29 | Methods And Apparatus For Use In Facilitating The Communication Of Neighboring Network Information To A Mobile Terminal With Use Of A Radius Compatible Protocol |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/793,977 Continuation US9629038B2 (en) | 2009-06-04 | 2010-06-04 | Methods and apparatus for use in facilitating the communication of neighboring network information to a mobile terminal with use of a radius compatible protocol |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/611,604 Continuation US20170272986A1 (en) | 2009-06-04 | 2017-06-01 | Methods and apparatus for use in facilitating the communication of neighboring network information to a mobile terminal with use of a radius compatible protocol |
Publications (1)
Publication Number | Publication Date |
---|---|
US20150237543A1 true US20150237543A1 (en) | 2015-08-20 |
Family
ID=43297226
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/793,977 Active 2030-06-29 US9629038B2 (en) | 2009-06-04 | 2010-06-04 | Methods and apparatus for use in facilitating the communication of neighboring network information to a mobile terminal with use of a radius compatible protocol |
US14/699,793 Abandoned US20150237543A1 (en) | 2009-06-04 | 2015-04-29 | Methods And Apparatus For Use In Facilitating The Communication Of Neighboring Network Information To A Mobile Terminal With Use Of A Radius Compatible Protocol |
US15/611,604 Abandoned US20170272986A1 (en) | 2009-06-04 | 2017-06-01 | Methods and apparatus for use in facilitating the communication of neighboring network information to a mobile terminal with use of a radius compatible protocol |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/793,977 Active 2030-06-29 US9629038B2 (en) | 2009-06-04 | 2010-06-04 | Methods and apparatus for use in facilitating the communication of neighboring network information to a mobile terminal with use of a radius compatible protocol |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/611,604 Abandoned US20170272986A1 (en) | 2009-06-04 | 2017-06-01 | Methods and apparatus for use in facilitating the communication of neighboring network information to a mobile terminal with use of a radius compatible protocol |
Country Status (11)
Country | Link |
---|---|
US (3) | US9629038B2 (en) |
EP (1) | EP2438780B1 (en) |
JP (1) | JP5389259B2 (en) |
KR (1) | KR20120013421A (en) |
CN (1) | CN102450056B (en) |
AU (1) | AU2010256311B2 (en) |
CA (1) | CA2763988A1 (en) |
ES (1) | ES2957533T3 (en) |
MX (1) | MX2011012802A (en) |
SG (1) | SG176293A1 (en) |
WO (1) | WO2010139058A1 (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130054763A1 (en) * | 2011-08-31 | 2013-02-28 | Jacobus Van Der Merwe | Methods and apparatus to configure virtual private mobile networks with virtual private networks |
US20160323735A1 (en) * | 2015-04-28 | 2016-11-03 | Arris Enterprises Llc | Service set determination based upon device type identifier |
US20170104758A1 (en) * | 2014-06-25 | 2017-04-13 | Huawei Technologies Co., Ltd. | Method for establishing network connection, gateway, and terminal |
US10069799B2 (en) | 2011-06-21 | 2018-09-04 | At&T Intellectual Property I, L.P. | Methods and apparatus to configure virtual private mobile networks for security |
US10419992B2 (en) | 2011-06-06 | 2019-09-17 | At&T Intellectual Property I, L.P. | Methods and apparatus to migrate a mobile device from a first virtual private mobile network to a second virtual private mobile network to reduce latency |
Families Citing this family (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
AU2010256311B2 (en) | 2009-06-04 | 2014-07-10 | Blackberry Limited | Methods and apparatus for use in facilitating the communication of neighboring network information to a mobile terminal with use of a radius compatible protocol |
CN102656845B (en) * | 2009-10-16 | 2015-04-01 | 泰克莱克股份有限公司 | Methods, systems, and computer readable media for providing diameter signaling router with integrated monitoring and/or firewall functionality |
US9020467B2 (en) * | 2010-11-19 | 2015-04-28 | Aicent, Inc. | Method of and system for extending the WISPr authentication procedure |
JP5661207B2 (en) * | 2011-03-18 | 2015-01-28 | テケレック・インコーポレイテッドTekelec, Inc. | Method, system, and computer-readable medium for diameter-based guidance of mobile device network access |
US8520583B2 (en) * | 2011-05-03 | 2013-08-27 | Nokia Corporation | Method, apparatus, and computer program product for roaming partner discovery |
CN103535080B (en) | 2011-05-06 | 2017-07-18 | 泰科来股份有限公司 | Method, system and computer-readable media for changing user between access networks |
US8942088B2 (en) * | 2011-10-07 | 2015-01-27 | Telefonaktiebolaget L M Ericsson (Publ) | BNG to PCRF mediation entity for BBF and 3GPP access interworking |
US9178893B2 (en) * | 2012-04-11 | 2015-11-03 | Motorola Solutions, Inc. | Secure AD HOC communication systems and methods across heterogeneous systems |
EP2875662B1 (en) | 2012-07-20 | 2017-12-27 | Tekelec, Inc. | Methods, systems and computer readable media for distributing policy rules to the mobile edge |
CN103781154B (en) * | 2012-10-19 | 2017-08-29 | 华为技术有限公司 | A kind of method and apparatus that inquiry Cellular Networks information is indicated in non-cellular net |
WO2014063095A1 (en) | 2012-10-19 | 2014-04-24 | Huawei Technologies Co., Ltd. | System and method for efficient communications system scanning |
US9622156B2 (en) * | 2012-10-19 | 2017-04-11 | Futurewei Technologies, Inc. | System and method for efficient access network query protocol (ANQP) discovery of multiple access points (APs) |
WO2014106434A1 (en) * | 2013-01-03 | 2014-07-10 | Huawei Technologies Co., Ltd. | System and method for efficient access network query protocol (anqp) discovery of multiple access points (aps) |
KR102060373B1 (en) | 2013-02-21 | 2019-12-30 | 삼성전자주식회사 | Method and apparatus for connecting short-distance wireless communication in terminal |
US9980213B2 (en) | 2013-08-29 | 2018-05-22 | Interdigital Patent Holdings, Inc. | Methods, apparatus and systems for wireless network selection |
KR102143441B1 (en) | 2013-11-15 | 2020-08-11 | 삼성전자주식회사 | Electronic device and method for updating authentication information in electronic device |
KR102226520B1 (en) | 2014-03-07 | 2021-03-11 | 삼성전자주식회사 | Method and apparatus for updating advertising information |
KR102265658B1 (en) * | 2014-07-23 | 2021-06-17 | 삼성전자주식회사 | Electronic device and method for discovering network in electronic device |
US9949314B2 (en) * | 2014-09-23 | 2018-04-17 | Qualcomm Incorporated | Support blacklisting devices on WLAN access |
CN105812337A (en) * | 2014-12-31 | 2016-07-27 | 中兴通讯股份有限公司 | Radius and Diameter combined authentication authorization method and method |
US20160302144A1 (en) | 2015-04-08 | 2016-10-13 | Nokia Technologies Oy | Method, apparatus, and computer program product for efficient use of frequency bands and channels in wireless environment |
WO2017011091A1 (en) * | 2015-07-10 | 2017-01-19 | Symbol Technologies, Llc | Method of, and arrangement for, enhancing scan and roam performance of a mobile client by retrieving scan and roam parameters of access points connected to a distribution system |
EP3349497A4 (en) | 2015-09-11 | 2019-02-06 | Sony Corporation | Communication control device, and device and method for determining communication control |
Citations (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040029580A1 (en) * | 2002-01-18 | 2004-02-12 | Nokia Corporation | Method, system and device for service selection via a wireless local area network |
US20050154774A1 (en) * | 2002-03-28 | 2005-07-14 | Raffaele Giaffreda | Method of data transfer in mobile and fixed telecommunications systems |
US20060077986A1 (en) * | 2004-10-08 | 2006-04-13 | Johan Rune | Enhancement of AAA routing originated from a local access network involving intermediary network preferences |
US20060217147A1 (en) * | 2005-01-18 | 2006-09-28 | Interdigital Technology Corporation | Method and system for system discovery and user selection |
US20060240832A1 (en) * | 2005-03-24 | 2006-10-26 | Lg Electronics Inc. | Method of executing handover in broadband wireless access system |
US20070025298A1 (en) * | 2005-08-01 | 2007-02-01 | Samsung Electronics Co., Ltd. | Method and system for providing roaming service in mobile communication system |
US20070242637A1 (en) * | 2006-04-14 | 2007-10-18 | Rick Dynarski | Pseudo wires for mobility management |
US20080151796A1 (en) * | 2006-12-22 | 2008-06-26 | Nokia Corporation | Apparatus, method, and computer program product providing improved network service information delivery |
US20080233951A1 (en) * | 2007-03-19 | 2008-09-25 | Hitachi, Ltd. | Wireless communication system and monitoring apparatus selectable optimum wireless communication method |
US20090046682A1 (en) * | 2006-02-01 | 2009-02-19 | Yong Ho Kim | Method for transmitting information in wireless local area network system |
US20100035578A1 (en) * | 2008-08-07 | 2010-02-11 | Futurewei Technologies, Inc. | Method and System for Interworking Between Two Different Networks |
US20100146272A1 (en) * | 2007-03-08 | 2010-06-10 | Angelo Centonza | Method of controlling information requests |
US20100177737A1 (en) * | 2009-01-12 | 2010-07-15 | Qualcomm Incorporated | Context fetching after inter-system handover |
US20110058550A1 (en) * | 2008-04-30 | 2011-03-10 | Huailong Gu | Method, apparatus and system for allocating iptv resources |
US20120096520A1 (en) * | 2006-10-21 | 2012-04-19 | Telcordia Technologies, Inc. | Key Cashing, QoS and Multicast Extensions to Media-Independent Pre-Authentication |
US20130064222A1 (en) * | 2006-06-23 | 2013-03-14 | Nokia Siemens | Network selection |
US8730908B2 (en) * | 2006-11-07 | 2014-05-20 | Electronics And Telecommunications Research Institute | Method of selecting target network for hand-over and method thereof |
US20150016609A1 (en) * | 2003-10-13 | 2015-01-15 | Nokia Corporation | Authentication In Heterogeneous IP Networks |
US20150244876A1 (en) * | 2009-03-03 | 2015-08-27 | Mobilitie, Llc | Billing engine and method of use |
Family Cites Families (86)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6018030A (en) * | 1986-11-04 | 2000-01-25 | Protein Polymer Technologies, Inc. | Peptides comprising repetitive units of amino acids and DNA sequences encoding the same |
US5611016A (en) * | 1996-06-07 | 1997-03-11 | Lucent Technologies Inc. | Dispersion-balanced optical cable |
JP3577916B2 (en) | 1997-10-24 | 2004-10-20 | 松下電器産業株式会社 | Image display device |
FI980085A0 (en) | 1998-01-16 | 1998-01-16 | Finland Telecom Oy | Encryption in card form and annulling in encryption |
AU5280299A (en) * | 1999-07-02 | 2001-01-22 | Nokia Corporation | Authentication method and system |
US20020136226A1 (en) | 2001-03-26 | 2002-09-26 | Bluesocket, Inc. | Methods and systems for enabling seamless roaming of mobile devices among wireless networks |
KR100385136B1 (en) | 2001-05-07 | 2003-05-23 | 엘지전자 주식회사 | MAP Message Processing System And Method For Heterogenous Network Interworking |
CA2450434A1 (en) | 2001-06-18 | 2002-12-27 | Tatara Systems, Inc. | Method and apparatus for converging local area and wide area wireless data networks |
US7900242B2 (en) | 2001-07-12 | 2011-03-01 | Nokia Corporation | Modular authentication and authorization scheme for internet protocol |
US7068631B2 (en) | 2001-08-06 | 2006-06-27 | Telefonaktiebolaget Lm Ericsson (Publ) | Training sequence hopping in a radio communication system |
FI114276B (en) | 2002-01-11 | 2004-09-15 | Nokia Corp | Arranging online visits |
US20040240669A1 (en) * | 2002-02-19 | 2004-12-02 | James Kempf | Securing neighbor discovery using address based keys |
US7440573B2 (en) * | 2002-10-08 | 2008-10-21 | Broadcom Corporation | Enterprise wireless local area network switching system |
US6775444B1 (en) * | 2003-02-28 | 2004-08-10 | Corning Cable Systems Llc | Fiber optic assemblies and methods of making the same |
US8606885B2 (en) * | 2003-06-05 | 2013-12-10 | Ipass Inc. | Method and system of providing access point data associated with a network access point |
CN1271822C (en) * | 2003-07-04 | 2006-08-23 | 华为技术有限公司 | Method of interactive processing of user terminal network selection information in WLAN |
CN1277380C (en) * | 2003-08-07 | 2006-09-27 | 华为技术有限公司 | User terminal definite network selective information interacting method in wireless LAN |
US7260393B2 (en) * | 2003-09-23 | 2007-08-21 | Intel Corporation | Systems and methods for reducing communication unit scan time in wireless networks |
ATE435580T1 (en) | 2003-10-30 | 2009-07-15 | Research In Motion Ltd | METHOD FOR SENDING (RECEIVING) INFORMATION OF A CELLULAR NETWORK (E.G. MNC, NCC) THROUGH (FROM A) WIRELESS LAN IN AN EAP PROTOCOL |
US7395083B2 (en) | 2003-10-30 | 2008-07-01 | Research In Motion Limited | Methods and apparatus for the communication of cellular network information between a wireless local area network and a mobile station |
WO2005053304A2 (en) | 2003-11-19 | 2005-06-09 | Research In Motion Limited | Methods and apparatus for providing network broadcast information to wlan enabled wireless communication devices |
WO2005076564A1 (en) * | 2004-02-06 | 2005-08-18 | Telecom Italia S.P.A. | Method and system for the secure and transparent provision of mobile ip services in an aaa environment |
US7010206B1 (en) * | 2004-09-08 | 2006-03-07 | Corning Incorporated | Coated optical fiber and optical fiber coating system including a fast-gelling primary coating |
US8081759B2 (en) * | 2004-09-15 | 2011-12-20 | Nokia Corporation | Apparatus, and an associated method, for facilitating fast transition in a network system |
EP1638261A1 (en) | 2004-09-16 | 2006-03-22 | Matsushita Electric Industrial Co., Ltd. | Configuring connection parameters in a handover between access networks |
EP1646189A1 (en) | 2004-10-06 | 2006-04-12 | Matsushita Electric Industrial Co., Ltd. | WLAN radio access network to UMTS radio access network handover with network requested packet data protocol context activation |
US7292592B2 (en) * | 2004-10-08 | 2007-11-06 | Telefonaktiebolaget Lm Ericsson (Publ) | Home network-assisted selection of intermediary network for a roaming mobile terminal |
US20060092890A1 (en) * | 2004-11-01 | 2006-05-04 | Gupta Vivek G | Global network neighborhood: scheme for providing information about available networks in a geographical location |
KR100638590B1 (en) * | 2004-11-02 | 2006-10-26 | 한국전자통신연구원 | Amethod for terminal authenticating in portable internet system |
CN101176293A (en) * | 2004-11-05 | 2008-05-07 | 株式会社东芝 | Network discovery mechanism |
US7738871B2 (en) * | 2004-11-05 | 2010-06-15 | Interdigital Technology Corporation | Wireless communication method and system for implementing media independent handover between technologically diversified access networks |
KR100643763B1 (en) * | 2005-02-17 | 2006-11-10 | 삼성전자주식회사 | Mobile node for discovering neibor network in the heterogeneous network environment, and method thereof |
JP4615345B2 (en) * | 2005-03-25 | 2011-01-19 | Okiセミコンダクタ株式会社 | Handover method in wireless LAN |
US7715842B2 (en) * | 2005-04-09 | 2010-05-11 | Lg Electronics Inc. | Supporting handover of mobile terminal |
KR101080965B1 (en) * | 2005-04-09 | 2011-11-08 | 엘지전자 주식회사 | Method of receiving and transmitting information service for Media Independent Handover |
US20060274743A1 (en) * | 2005-06-06 | 2006-12-07 | Alper Yegin | System and method for a mobile device to learn information about the access networks within its neighborhood |
DE102005043364B4 (en) * | 2005-09-12 | 2007-07-05 | Siemens Ag | Telecommunication system and method for controlling a change of a subscriber terminal between two networks |
US8315626B2 (en) * | 2005-09-16 | 2012-11-20 | Cisco Technology, Inc. | Smart wireless station for identifying a preferred access point |
KR100801283B1 (en) * | 2005-11-11 | 2008-02-04 | 한국전자통신연구원 | Apparatus and method for providing service for media independent handover |
WO2007062004A2 (en) * | 2005-11-22 | 2007-05-31 | The Trustees Of Columbia University In The City Of New York | Methods, media, and devices for moving a connection from one point of access to another point of access |
US7580701B2 (en) * | 2005-12-27 | 2009-08-25 | Intel Corporation | Dynamic passing of wireless configuration parameters |
US20070160049A1 (en) * | 2006-01-09 | 2007-07-12 | Motorola, Inc. | Method and apparatus for effecting a handoff in a mobile internet protocol communication system |
US8023478B2 (en) * | 2006-03-06 | 2011-09-20 | Cisco Technology, Inc. | System and method for securing mesh access points in a wireless mesh network, including rapid roaming |
WO2007116337A2 (en) * | 2006-04-07 | 2007-10-18 | Nokia Corporation | 802.11k neighbor report enhancement |
US7930734B2 (en) * | 2006-04-28 | 2011-04-19 | Cisco Technology, Inc. | Method and system for creating and tracking network sessions |
US10225788B2 (en) * | 2006-05-25 | 2019-03-05 | Truconnect Technologies, Llc | Method and system for selecting a wireless network for offloading |
US8359061B2 (en) * | 2006-06-06 | 2013-01-22 | Panasonic Corporation | Radio communication system, radio terminal, base station, and base station search method |
EP1871065A1 (en) * | 2006-06-19 | 2007-12-26 | Nederlandse Organisatie voor Toegepast-Natuuurwetenschappelijk Onderzoek TNO | Methods, arrangement and systems for controlling access to a network |
EP2050286B1 (en) * | 2006-07-31 | 2018-09-05 | Mitel Networks, Inc. | System to facilitate handover |
US7804807B2 (en) * | 2006-08-02 | 2010-09-28 | Motorola, Inc. | Managing establishment and removal of security associations in a wireless mesh network |
EP2074755A4 (en) * | 2006-08-31 | 2012-07-11 | Telcordia Tech Inc | Methods of mitigation of trombone routing in an ims/mmd network |
FI121560B (en) * | 2006-11-20 | 2010-12-31 | Teliasonera Ab | Authentication in a mobile communication system |
ES2363389B1 (en) | 2006-12-29 | 2012-06-13 | Bsh Electrodomésticos España, S.A. | FASTENING ELEMENT OF A TUBULAR HEATER, FIXING SYSTEM WITH SAID FIXING ELEMENT AND WASHING MACHINE WITH SUCH FASTENING SYSTEM. |
US8811349B2 (en) | 2007-02-21 | 2014-08-19 | Qualcomm Incorporated | Wireless node search procedure |
PT2119189E (en) | 2007-03-12 | 2015-06-01 | Nokia Corp | System and method for authentication for wireless emergency services |
FI20075297A0 (en) | 2007-04-27 | 2007-04-27 | Nokia Siemens Networks Oy | Method, radio system and base station |
KR101402255B1 (en) * | 2007-05-07 | 2014-06-02 | 재단법인서울대학교산학협력재단 | Apparatus and method for handover in wireless communication system |
KR20100038123A (en) * | 2007-05-25 | 2010-04-12 | 인터디지탈 테크날러지 코포레이션 | Protocol architecture for access mobility in wireless communications |
EP2037652A3 (en) * | 2007-06-19 | 2009-05-27 | Panasonic Corporation | Methods and apparatuses for detecting whether user equipment resides in a trusted or a non-trusted access network |
CN101779417B (en) | 2007-07-04 | 2013-02-06 | Lg电子株式会社 | Interworking procedure with external network in wireless lan and message format for the same |
KR101490243B1 (en) * | 2007-07-10 | 2015-02-11 | 엘지전자 주식회사 | A Method of establishing fast security association for handover between heterogeneous radio access networks |
EP2015535A1 (en) * | 2007-07-10 | 2009-01-14 | Panasonic Corporation | Detection of mobility functions implemented in a mobile node |
US8230490B2 (en) * | 2007-07-31 | 2012-07-24 | Keycorp | System and method for authentication of users in a secure computer system |
KR101375540B1 (en) * | 2007-08-22 | 2014-03-19 | 삼성전자주식회사 | Method and Apparatus for performing neighbor discovery in a heterogeneous network |
US7826427B2 (en) * | 2007-08-22 | 2010-11-02 | Intel Corporation | Method for secure transfer of data to a wireless device for enabling multi-network roaming |
US8335490B2 (en) * | 2007-08-24 | 2012-12-18 | Futurewei Technologies, Inc. | Roaming Wi-Fi access in fixed network architectures |
ATE518397T1 (en) * | 2007-09-14 | 2011-08-15 | Huawei Tech Co Ltd | METHOD, APPARATUS AND SYSTEM FOR OBTAINING MIH SERVICE INFORMATION |
KR101467780B1 (en) | 2007-10-17 | 2014-12-03 | 엘지전자 주식회사 | Method for handover between heterogeneous radio access networks |
KR100933238B1 (en) * | 2007-10-29 | 2009-12-22 | 포항공과대학교 산학협력단 | Device and method for updating network information based on terminal |
US8620321B2 (en) * | 2007-11-07 | 2013-12-31 | Electronics And Telecommunications Research Institute | Method and apparatus for the handover |
US8855007B2 (en) * | 2007-11-19 | 2014-10-07 | Qualcomm Incorporated | Configuring an identifier for an access point |
KR20090053279A (en) * | 2007-11-23 | 2009-05-27 | 삼성전자주식회사 | Method, apparatus and system for internet protocol address assignment in communication system based media independent handover |
US20090213795A1 (en) * | 2008-02-22 | 2009-08-27 | Futurewei Technologies, Inc. | Communication of Access Information in Wireless Communication System |
KR101370914B1 (en) * | 2008-03-10 | 2014-03-10 | 엘지전자 주식회사 | Method for transmitting subframe grouping information and decoding subframe grouped frames |
JP2009218929A (en) * | 2008-03-11 | 2009-09-24 | Toshiba Corp | Base station, mobile terminal and communication program |
US20090245133A1 (en) * | 2008-03-31 | 2009-10-01 | Intel Corporation | Broadcast/multicast based network discovery |
PL2258126T3 (en) * | 2008-04-02 | 2012-12-31 | Nokia Solutions & Networks Oy | Security for a non-3gpp access to an evolved packet system |
US9717042B2 (en) * | 2008-06-04 | 2017-07-25 | Nokia Solutions And Networks Oy | Network discovery and selection |
ES2398799T3 (en) * | 2008-07-28 | 2013-03-21 | France Telecom | Procedure for obtaining information from a local environment of a terminal |
US8379512B2 (en) * | 2008-09-18 | 2013-02-19 | Qualcomm Incorporated | Using identifier mapping to resolve access point identifier ambiguity |
US20100141400A1 (en) * | 2008-11-19 | 2010-06-10 | Qualcomm Incorporated | Lower power discovery and wake up using service set identifier probabilistic scanning synchronization verification and optional sensor |
KR101015665B1 (en) * | 2009-03-16 | 2011-02-22 | 삼성전자주식회사 | Method and system for conneting between mobile communication terminal and access point |
US8903413B2 (en) * | 2009-03-20 | 2014-12-02 | Qualcomm Incorporated | Hybrid cell management in wireless networks |
EP2417789B1 (en) * | 2009-04-07 | 2014-07-30 | Togewa Holding AG | Method and system for authenticating a network node in a uam-based wlan network |
US8505076B2 (en) * | 2009-05-03 | 2013-08-06 | Kabushiki Kaisha Toshiba | Proactive authentication |
AU2010256311B2 (en) | 2009-06-04 | 2014-07-10 | Blackberry Limited | Methods and apparatus for use in facilitating the communication of neighboring network information to a mobile terminal with use of a radius compatible protocol |
-
2010
- 2010-06-04 AU AU2010256311A patent/AU2010256311B2/en active Active
- 2010-06-04 SG SG2011088556A patent/SG176293A1/en unknown
- 2010-06-04 US US12/793,977 patent/US9629038B2/en active Active
- 2010-06-04 ES ES10782861T patent/ES2957533T3/en active Active
- 2010-06-04 KR KR1020117028729A patent/KR20120013421A/en not_active Application Discontinuation
- 2010-06-04 CA CA2763988A patent/CA2763988A1/en not_active Abandoned
- 2010-06-04 WO PCT/CA2010/000824 patent/WO2010139058A1/en active Application Filing
- 2010-06-04 EP EP10782861.8A patent/EP2438780B1/en active Active
- 2010-06-04 JP JP2012513421A patent/JP5389259B2/en active Active
- 2010-06-04 CN CN201080023863.0A patent/CN102450056B/en active Active
- 2010-06-04 MX MX2011012802A patent/MX2011012802A/en active IP Right Grant
-
2015
- 2015-04-29 US US14/699,793 patent/US20150237543A1/en not_active Abandoned
-
2017
- 2017-06-01 US US15/611,604 patent/US20170272986A1/en not_active Abandoned
Patent Citations (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040029580A1 (en) * | 2002-01-18 | 2004-02-12 | Nokia Corporation | Method, system and device for service selection via a wireless local area network |
US20050154774A1 (en) * | 2002-03-28 | 2005-07-14 | Raffaele Giaffreda | Method of data transfer in mobile and fixed telecommunications systems |
US20150016609A1 (en) * | 2003-10-13 | 2015-01-15 | Nokia Corporation | Authentication In Heterogeneous IP Networks |
US20060077986A1 (en) * | 2004-10-08 | 2006-04-13 | Johan Rune | Enhancement of AAA routing originated from a local access network involving intermediary network preferences |
US20060217147A1 (en) * | 2005-01-18 | 2006-09-28 | Interdigital Technology Corporation | Method and system for system discovery and user selection |
US20060240832A1 (en) * | 2005-03-24 | 2006-10-26 | Lg Electronics Inc. | Method of executing handover in broadband wireless access system |
US20070025298A1 (en) * | 2005-08-01 | 2007-02-01 | Samsung Electronics Co., Ltd. | Method and system for providing roaming service in mobile communication system |
US20090046682A1 (en) * | 2006-02-01 | 2009-02-19 | Yong Ho Kim | Method for transmitting information in wireless local area network system |
US20070242637A1 (en) * | 2006-04-14 | 2007-10-18 | Rick Dynarski | Pseudo wires for mobility management |
US20130163562A1 (en) * | 2006-04-14 | 2013-06-27 | Qualcomm Incorporated | Pseudo wires for mobility management |
US20130064222A1 (en) * | 2006-06-23 | 2013-03-14 | Nokia Siemens | Network selection |
US20120096520A1 (en) * | 2006-10-21 | 2012-04-19 | Telcordia Technologies, Inc. | Key Cashing, QoS and Multicast Extensions to Media-Independent Pre-Authentication |
US8730908B2 (en) * | 2006-11-07 | 2014-05-20 | Electronics And Telecommunications Research Institute | Method of selecting target network for hand-over and method thereof |
US20080151796A1 (en) * | 2006-12-22 | 2008-06-26 | Nokia Corporation | Apparatus, method, and computer program product providing improved network service information delivery |
US20100146272A1 (en) * | 2007-03-08 | 2010-06-10 | Angelo Centonza | Method of controlling information requests |
US20080233951A1 (en) * | 2007-03-19 | 2008-09-25 | Hitachi, Ltd. | Wireless communication system and monitoring apparatus selectable optimum wireless communication method |
US20110058550A1 (en) * | 2008-04-30 | 2011-03-10 | Huailong Gu | Method, apparatus and system for allocating iptv resources |
US20100035578A1 (en) * | 2008-08-07 | 2010-02-11 | Futurewei Technologies, Inc. | Method and System for Interworking Between Two Different Networks |
US20100177737A1 (en) * | 2009-01-12 | 2010-07-15 | Qualcomm Incorporated | Context fetching after inter-system handover |
US20150244876A1 (en) * | 2009-03-03 | 2015-08-27 | Mobilitie, Llc | Billing engine and method of use |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10419992B2 (en) | 2011-06-06 | 2019-09-17 | At&T Intellectual Property I, L.P. | Methods and apparatus to migrate a mobile device from a first virtual private mobile network to a second virtual private mobile network to reduce latency |
US10069799B2 (en) | 2011-06-21 | 2018-09-04 | At&T Intellectual Property I, L.P. | Methods and apparatus to configure virtual private mobile networks for security |
US20130054763A1 (en) * | 2011-08-31 | 2013-02-28 | Jacobus Van Der Merwe | Methods and apparatus to configure virtual private mobile networks with virtual private networks |
US10044678B2 (en) * | 2011-08-31 | 2018-08-07 | At&T Intellectual Property I, L.P. | Methods and apparatus to configure virtual private mobile networks with virtual private networks |
US20170104758A1 (en) * | 2014-06-25 | 2017-04-13 | Huawei Technologies Co., Ltd. | Method for establishing network connection, gateway, and terminal |
US10432632B2 (en) * | 2014-06-25 | 2019-10-01 | Huawei Technologies Co., Ltd. | Method for establishing network connection, gateway, and terminal |
US20160323735A1 (en) * | 2015-04-28 | 2016-11-03 | Arris Enterprises Llc | Service set determination based upon device type identifier |
US9848319B2 (en) * | 2015-04-28 | 2017-12-19 | Arris Enterprises Llc | Service set determination based upon device type identifier |
Also Published As
Publication number | Publication date |
---|---|
WO2010139058A1 (en) | 2010-12-09 |
EP2438780B1 (en) | 2023-09-20 |
SG176293A1 (en) | 2012-01-30 |
EP2438780A4 (en) | 2017-03-29 |
CA2763988A1 (en) | 2010-12-09 |
EP2438780A1 (en) | 2012-04-11 |
CN102450056A (en) | 2012-05-09 |
CN102450056B (en) | 2015-11-25 |
US20170272986A1 (en) | 2017-09-21 |
US20100313020A1 (en) | 2010-12-09 |
JP2012529197A (en) | 2012-11-15 |
US9629038B2 (en) | 2017-04-18 |
AU2010256311A1 (en) | 2011-12-22 |
AU2010256311B2 (en) | 2014-07-10 |
EP2438780C0 (en) | 2023-09-20 |
KR20120013421A (en) | 2012-02-14 |
MX2011012802A (en) | 2012-03-29 |
JP5389259B2 (en) | 2014-01-15 |
ES2957533T3 (en) | 2024-01-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20170272986A1 (en) | Methods and apparatus for use in facilitating the communication of neighboring network information to a mobile terminal with use of a radius compatible protocol | |
US9730150B2 (en) | Methods and apparatus for use in facilitating access to aggregator services for mobile communication devices via wireless communication networks | |
US8594628B1 (en) | Credential generation for automatic authentication on wireless access network | |
US8036192B2 (en) | Autonomous and heterogeneous network discovery and reuse | |
CA2854947C (en) | Caching network discovery responses in wireless networks | |
EP2337312B1 (en) | Methods and apparatus for use in facilitating access to aggregator services for mobile communication devices via wireless communication networks | |
EP2145500B1 (en) | Systems and methods for currency querying | |
EP3504906A2 (en) | Wlan assisted cellular network discovery and selection | |
KR20050041975A (en) | Methods and apparatus for the communication between a wireless local area network and a mobile station | |
BRPI1011976B1 (en) | METHOD FOR REQUESTING A NEIGHBORING NETWORK INFORMATION, METHOD OF AN AP WITHIN A WLAN, MOBILE TERMINAL, WIRELESS AP AND COMPUTER-READABLE NON TRANSIENTAL MEDIUM |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: BLACKBERRY LIMITED, ONTARIO Free format text: CHANGE OF NAME;ASSIGNOR:RESEARCH IN MOTION LIMITED;REEL/FRAME:037893/0239 Effective date: 20130709 |
|
AS | Assignment |
Owner name: RESEARCH IN MOTION LIMITED, CANADA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MONTEMURRO, MICHAEL;REEL/FRAME:040174/0994 Effective date: 20100719 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: OT PATENT ESCROW, LLC, ILLINOIS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BLACKBERRY LIMITED;REEL/FRAME:064007/0061 Effective date: 20230320 Owner name: MALIKIE INNOVATIONS LIMITED, IRELAND Free format text: NUNC PRO TUNC ASSIGNMENT;ASSIGNOR:OT PATENT ESCROW, LLC;REEL/FRAME:064015/0001 Effective date: 20230511 |