IP service authorization in wireless communications networks

Systems and methodologies are described that facilitate protocol address assignment using protocols compatible with specified domains for mobile devices. Devices can request wireless network access through a gateway, which can forward an authentication/authorization request to an authentication server. Upon successful authentication, the authentication server can transmit one or more domain identifiers related to the device or a user thereof. Using the domain identifier, compatible protocols can be determined for use in configuring the device for subsequent domain communication.

BACKGROUND

The following description relates generally to wireless communications, and more particularly to protocol service authorization in wireless communications networks.

Wireless communication systems are widely deployed to provide various types of communication content such as, for example, voice, data, and so on. Typical wireless communication systems may be multiple-access systems capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, . . . ). Examples of such multiple-access systems may include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, and the like. Additionally, the systems can conform to specifications such as third generation partnership project (3GPP), 3GPP long term evolution (LTE), ultra mobile broadband (UMB), etc.

Generally, wireless multiple-access communication systems may simultaneously support communication for multiple mobile devices. Each mobile device may communicate with one or more base stations via transmissions on forward and reverse links. The forward link (or downlink) refers to the communication link from base stations to mobile devices, and the reverse link (or uplink) refers to the communication link from mobile devices to base stations. Further, communications between mobile devices and base stations may be established via single-input single-output (SISO) systems, multiple-input single-output (MISO) systems, multiple-input multiple-output (MIMO) systems, and so forth. In addition, mobile devices can communicate with other mobile devices (and/or base stations with other base stations) in peer-to-peer wireless network configurations.

The base stations can facilitate communication between the mobile devices and core wireless network components, such as authentication, authorization, and accounting (AAA) servers, one or more gateways, or any service providing components. For example, the core network components can be utilized to authenticate and/or authorize mobile devices for communicating with other devices or components of the wireless network. Moreover, an AAA server can verify a user of the mobile device with a stored profile, and upon successful authentication/authorization, can notify a gateway. The gateway can then assign access protocol services to the mobile device to facilitate subsequent communications. However, the development of different communications protocols and different domains utilizing different combinations of protocols can impede wireless network support for multiple domains.

SUMMARY

In accordance with one or more embodiments and corresponding disclosure thereof, various aspects are described in connection with facilitating access protocol assignment following authentication/authorization based at least in part on a domain specified in a user profile for a device receiving the protocol assignment. For example, an authentication, authorization, and accounting (AAA) server can authenticate a user of a mobile device through an access gateway (AGW) or other core network component. The AAA server can provide one or more identifiers for domains available to the mobile device; this can be based on a profile, for example. The AGW or other component can utilize the domain identifier to determine one or more protocols compatible with the mobile device and/or domain. Subsequently, the AGW can establish a session with compatible protocol services with the mobile device.

According to related aspects, a method for providing protocol services based at least in part on a desired domain for a mobile device is provided. The method can include receiving a domain identifier related to a user of a mobile device and determining one or more protocols compatible with a domain according to the domain identifier. The method can additionally include configuring communication parameters related to the one or more protocols for the mobile device to facilitate subsequent communication in the domain.

Another aspect relates to a wireless communications apparatus. The wireless communications apparatus can include at least one processor configured to determine a compatible communication protocol for a mobile device based at least in part on a received domain identification as well as configure communication parameters for the mobile device pursuant to the compatible communication protocol. The wireless communications apparatus can also include a memory coupled to the at least one processor.

Yet another aspect relates to a wireless communications apparatus that establishes protocol communications with a wireless network mobile device. The wireless communications apparatus can comprise means for determining a compatible communications protocol according to a received domain identifier related to a mobile device. The wireless communications apparatus can additionally include means for configuring protocol communication parameters for the mobile device to be utilized in subsequent communication based on the compatible communications protocol.

Still another aspect relates to a computer program product, which can have a computer-readable medium including code for causing at least one computer to receive a domain identifier related to a user of a mobile device. The computer-readable medium can also comprise code for causing the at least one computer to determine one or more protocols compatible with a domain according to the domain identifier. Moreover, the computer-readable medium can comprise code for causing the at least one computer to configure communication parameters related to the one or more protocols for the mobile device to facilitate subsequent communication in the domain.

DETAILED DESCRIPTION

Furthermore, various embodiments are described herein in connection with a mobile device. A mobile device can also be called a system, subscriber unit, subscriber station, mobile station, mobile, remote station, remote terminal, access terminal, user terminal, terminal, wireless communication device, user agent, user device, or user equipment (UE). A mobile device can be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device having wireless connection capability, computing device, or other processing device connected to a wireless modem. Moreover, various embodiments are described herein in connection with a base station. A base station can be utilized for communicating with mobile device(s) and can also be referred to as an access point, Node B, evolved Node B (eNode B or eNB), base transceiver station (BTS) or some other terminology.

Referring now toFIG. 1, a wireless communication system100is illustrated in accordance with various embodiments presented herein. System100comprises a base station102that can include multiple antenna groups. For example, one antenna group can include antennas104and106, another group can comprise antennas108and110, and an additional group can include antennas112and114. Two antennas are illustrated for each antenna group; however, more or fewer antennas can be utilized for each group. Base station102can additionally include a transmitter chain and a receiver chain, each of which can in turn comprise a plurality of components associated with signal transmission and reception (e.g., processors, modulators, multiplexers, demodulators, demultiplexers, antennas, etc.), as will be appreciated by one skilled in the art.

Base station102can communicate with one or more mobile devices such as mobile device116and mobile device122; however, it is to be appreciated that base station102can communicate with substantially any number of mobile devices similar to mobile devices116and122. Mobile devices116and122can be, for example, cellular phones, smart phones, laptops, handheld communication devices, handheld computing devices, satellite radios, global positioning systems, PDAs, and/or any other suitable device for communicating over wireless communication system100. As depicted, mobile device116is in communication with antennas112and114, where antennas112and114transmit information to mobile device116over a forward link118and receive information from mobile device116over a reverse link120. Moreover, mobile device122is in communication with antennas104and106, where antennas104and106transmit information to mobile device122over a forward link124and receive information from mobile device122over a reverse link126. In a frequency division duplex (FDD) system, forward link118can utilize a different frequency band than that used by reverse link120, and forward link124can employ a different frequency band than that employed by reverse link126, for example. Further, in a time division duplex (TDD) system, forward link118and reverse link120can utilize a common frequency band and forward link124and reverse link126can utilize a common frequency band.

Each group of antennas and/or the area in which they are designated to communicate can be referred to as a sector of base station102. For example, antenna groups can be designed to communicate to mobile devices in a sector of the areas covered by base station102. In communication over forward links118and124, the transmitting antennas of base station102can utilize beamforming to improve signal-to-noise ratio of forward links118and124for mobile devices116and122. Also, while base station102utilizes beamforming to transmit to mobile devices116and122scattered randomly through an associated coverage, mobile devices in neighboring cells can be subject to less interference as compared to a base station transmitting through a single antenna to all its mobile devices. Moreover, mobile devices116and122can communicate directly with one another using a peer-to-peer or ad hoc technology as depicted.

According to an example, system100can be a multiple-input multiple-output (MIMO) communication system. Further, system100can utilize substantially any type of duplexing technique to divide communication channels (e.g., forward link, reverse link, . . . ) such as FDD, TDD, and the like. Moreover, the base station102can provide the mobile devices116and/or122with access to the wireless network via core network components. For example, the base station102can facilitate communications between the mobile devices116and/or122and a core network to provide services, such as authentication and/or authorization. For example, the base station102can be coupled to a radio network controller (RNC) (not shown) that is connected to one or more core network devices, such as a gateway. In one example, a core network authorization, authentication, and accounting (AAA) server (not shown), or other core network component, can authenticate the mobile devices116and/or122upon receiving a request from the gateway. Upon successful authentication and/or authorization, the AAA server can provide one or more domain identifiers related to the mobile device116and/or122to the gateway. Based at least in part on the domain identifier, the gateway can utilize a compatible access protocol service and establish a session using a compatible access protocol with the mobile device116and/or122via base station102. Subsequently, the mobile device116and/or122can communicate with the core wireless network through the base station102, in one example.

Turning toFIG. 2, illustrated is a wireless communication system200that facilitates device authentication/authorization and subsequent protocol establishment in wireless networks. A device202, such as a mobile device, can communicate with an access gateway (AGW)206through an RNC204as described. The AGW206can facilitate device202communication with core network components of a wireless network. In one example, as shown, the AGW206can provide device202access to an AAA server208to authenticate/authorize the device202on the underlying wireless network. Moreover, the device202can access different RNCs over time; in some cases, the source and target RNC can utilize the same access gateway206. While previous protocol utilization required a new protocol address be assigned to the device202at each RNC (e.g., simple internet protocol (IP)), technologies have developed where the protocol address can be anchored at the AGW206(e.g., mobile IP) such that transferring to a new RNC need not necessarily require a new protocol address.

As shown, device202can request lower layer connection establishment and authentication/authorization from AGW206through RNC204. It is to be appreciated that the RNC204can connect to the device202via one or more base stations (not shown). Following the lower layer establishment, the device202can communicate with the AAA server208through the AGW206to authenticate and/or authorize the device202and/or user thereof at an upper-layer with the AAA server208of the wireless network. In this regard, the AAA server208can store parameters related to the device202and/or user thereof that can be compared with those provided by the device202upon authentication/authorization request. In one example, where the AAA server208successfully authenticates/authorizes the device202, it can send the success (e.g., service-authorized parameter, as shown) along with one or more domain identifiers related to the device202or user thereof, to the AGW206.

According to an example, the domain identifier can be a portion of a profile transmitted by the AAA server208to the AGW206on successful authentication and/or authorization. The domain identifier can indicate compatible protocols that can be utilized by the device202to communicate in the domain. In one example, the AGW206can associate the domain with one or more of the compatible protocols and establish a session with compatible access protocol services with the device202using the protocol. For example, the protocols compatible with a specified domain can include one or more of simple IP protocols, such as simple IPv4 and IPv6, mobile protocols, such as mobile IPv4 and IPv6, and/or other protocols. Thus, upon receiving indication of the domain from the AAA server208, the AGW206can determine the one or more compatible protocols and configure a protocol for the device202and/or establish a protocol session with the device202. For example, this can include receiving requests from the device202to establish a session based on one or more protocols and denying establishment if the requested protocol is not compatible with the domain, or the AGW206can specify one or more available protocols to the device202, in one example.

As described, the type of protocol used to establish communication with the device202can define subsequent communications with the device202. For example, where a mobile IP protocol is compatible with the domain specified by the AAA server208to the AGW206, if the device202transfers communication between radio network controllers, the same communication session can still be utilized if the new radio network controller uses the same AGW206, for example. In addition, the protocol compatible with the domain related to the device202or user can be a simple IP, for example, that is anchored at the RNC204. Thus, if the device202moves to a new RNC, another protocol session can be established.

Now referring toFIG. 3, illustrated is a wireless communication system300that facilitates multiple level device authorization/authentication and subsequent protocol services establishment. As described, a device302can communicate with an AGW306through an RNC304as described. The AGW306can facilitate device302communications with core network components of a wireless network, such as an AAA server308to authenticate/authorize the device302on the underlying wireless network. Once the AAA server308authentication/authorization is successful, a domain indicator can be sent to the AGW306(e.g., automatically or in response to an access request). Moreover, another layer of authentication/authorization can be desired for the user of the device302via a disparate AAA server310. Thus, a protocol can be determined to be compatible with the domain of the disparate AAA server310, and user authentication and/or authorization can be appropriately requested using the protocol in this regard.

Accordingly, in this example, lower layer connection establishment and authentication/authorization can occur between the device302and AGW306(via RNC304). Following connection establishment, the device306can be authenticated and/or authorized by the AAA server308as described. Further, the AAA server308can send a domain identifier to the AGW306on successful authentication/authorization, which can be utilized to determine one or more appropriate protocols that can be utilized for communication with the domain. It is to be appreciated that this can be part of a user profile transmission, an explicit identification of the domain and/or compatible protocols, etc. However, another layer of authentication/authorization can be desired for the user of the device302. In this regard, the device302can request user authentication/authorization with the disparate AAA server310via the AGW306, and the AGW306can ensure an appropriate protocol is utilized for the communication as determined above. Thus, the AGW306can configure a protocol and assign a protocol address to the device302depending on the protocol authorization information provided by AAA server308.

As mentioned previously, the protocol authorization information can comprise a domain identifier, from which the AGW306can determine compatible protocols. It is to be appreciated that the AAA server308can determine the compatible protocols and communicate the information to the AGW306. Moreover, the protocol authorization information can include, in one example, a user profile for the mobile device and/or user thereof comprising the desired domain. Once the AGW306has determined compatible protocols, it can receive a request for protocol address assignment from the device302. In one example, the device302can request a type of protocol, and the AGW306can grant or deny the request based on whether the requested protocol is one of the determined compatible protocols. In an alternate or additional example, the AGW306can transmit one or more of the compatible protocols to the device302.

Referring now toFIG. 4, illustrated is a communications apparatus400for employment within a wireless communications environment. The communications apparatus400can be an AGW, AAA, other core network component, a base station, a mobile device, and/or a portion thereof, or substantially any communications apparatus that receives data transmitted in a wireless communications environment. The communications apparatus400can include a domain identifier receiver402that can obtain a domain identification for a mobile device from one or more disparate sources, a compatible protocol specifier404that can determine one or more protocols useable with the domain identified in the domain identification, and a communications protocol configurer406that can establish a protocol for communication with a device (including determining an address, such as an IP address to utilize in communicating with the mobile device, domain name system (DNS) configuration, etc.) based at least in part on the one or more useable protocols.

According to an example, the domain identifier receiver402can receive an identification of one or more domains useable by a mobile device. The identification can come from one or more core network components, the mobile device, one or more related base stations, etc. The domain identification can be related to one or more services requested by the mobile device or those available to the mobile device, and can be transmitted, in one example, from an AAA server following authentication of the mobile device and/or a user thereof. The compatible protocol specifier404can determine one or more protocols compatible with the domain identified. For example, the protocols can be internet protocols as described, such as a simple IP or mobile IP, or disparate versions thereof, and/or the like. This can come from a stored lookup table indicating protocols available for given domains, a query to one or more devices, an inference made from other domain compatible protocols, and/or the like.

The communications protocol configurer406can configure a protocol for the mobile device based at least in part on the determined compatible protocol(s) for the domain. This can include assigning a protocol address to the mobile device, setting DNS server parameters, and/or the like. In this regard, the communications apparatus400can establish connection with the mobile device utilizing the protocol configuration, which can entail responding to a connection request from the mobile device and/or offering the mobile device available protocols specified by the compatible protocol specifier404. In the former example, where the mobile device requests a protocol not supported by the related domain, the communications apparatus can require the mobile device to specify a different protocol and/or provide the list of available protocols. Moreover, in this regard, underlying network components need not provide substantially all possible service authorization information to the AGW when mobile device authentication is completed; rather, the communication apparatus400can simply operate with the protocols compatible for the identified domain.

Now referring toFIG. 5, illustrated is a wireless communications system500that facilitates compatible IP service utilization based at least in part on a domain identifier. The system500includes an AGW502that communicates with an AAA server504(and/or any number of mobile devices (not shown) or RNCs (not shown), for example to access the mobile devices). The AGW502can provide core wireless network access to one or more devices, and the AAA server504can authenticate and/or authorize the devices on the wireless network, in one example. Also, the components and functionalities shown and described below in the AGW502can be present in the AAA server504and vice versa, in one example.

The AGW502can comprise a user profile receiver506that can obtain a user profile related to an authenticated mobile device, a domain identifier508that can determine a domain related to the user profile, and a communications protocol configurer510that can determine a protocol to use in communicating with the mobile device based at least in part on the related domain and configure parameters for the protocol, such as a device address (e.g., IP address), DNS server settings, and/or the like. For example, as described, the domain can be compatible with one or more types of protocols; thus, once the domain is determined, the AGW502can receive communication requests from a related mobile device and configure the protocol based at least in part on the compatible domain protocols and/or a protocol specified by the device.

The AAA server504comprises an authentication/authorization function512that can authenticate and/or authorize a mobile device, or user thereof, for communication with an underlying network as well as a user profile transmitter514that can send a user profile to the AGW502upon successful authentication/authorization. Thus, in one example, the AGW502can request authentication/authorization for a mobile device from the AAA server504. The authentication/authorization function512can perform the authentication/authorization; in one example, this can entail comparing parameters specified by the mobile device to those stored in an underlying network and/or the like. If authentication and/or authorization are successful at the AAA server504, the user profile transmitter514can transmit a profile related to the mobile device or user thereof to the AGW502.

In one example, the user profile can be provided in response to an access request to the AGW502from the AAA server504as well. The user profile receiver506can receive the profile and/or domain indicator transmitted from the AAA server504, which can specify one or more domains compatible with the mobile device and/or user. The domain identifier508can determine the one or more domains and compatible protocols for the domain(s). Thus, the AGW502determines possible protocols for desired communication without exposing substantially all protocols for communicating with the mobile device. The communications protocol configurer510can configure protocol parameters for the mobile device to utilize in subsequent communications, such as a protocol address, etc., to facilitate valid protocol service access in the specified domain. Subsequently, the AGW502can facilitate proper domain communication in the wireless network for the mobile device utilizing compatible protocols. It is to be appreciated that the authentication can have multiple phases, for example where the AAA server504is not of the same service provider as the mobile device. In this regard, the AGW502can facilitate device communication with the disparate AAA server to receive additional user authentication and/or authorization using the compatible protocol, in one example.

Turning toFIG. 6, a methodology600that facilitates transmitting domain identifiers following device and/or user authentication/authorization for wireless networks is displayed. At602, a user authentication/authorization request can be received for a mobile device or user thereof. As described, the request can be made to allow the mobile device to access additional wireless network resources, for example. At604, the user can be authenticated/authorized to the wireless network. As described, this can also relate to a mobile device utilized by the user. At606, a domain identifier can be transmitted to an access gateway upon successful authentication/authorization. As mentioned, the domain identifier can be transmitted as part of a user profile, in one example, and can identify one or more domains to be utilized. This can be used, in one example, to determine compatible protocols for establishing communications with the user and/or device.

Turning toFIG. 7, illustrated is a methodology700that facilitates establishing protocol communications with a mobile device based at least in part on domain identification. At702, a domain identifier for a user of a mobile device can be received along with network authentication. Thus, as described, a mobile device or user thereof can be authenticated on a wireless network. This can involve utilizing an AAA server, in one example. Once authenticated/authorized, a profile for the user or device can be received. At704, compatible protocols can be determined from the domain identifier. As mentioned, the protocols can be IP protocols, such as simple IP, mobile IP, versions thereof, etc., and different domains can support different protocols. Thus, by determining the domain for a user or device, compatible protocols can be determined, and at706, communication can be established with the mobile device using a compatible protocol.

FIG. 8shows an example wireless communication system800. The wireless communication system800depicts one base station810and one mobile device850for sake of brevity. However, it is to be appreciated that system800can include more than one base station and/or more than one mobile device, wherein additional base stations and/or mobile devices can be substantially similar or different from example base station810and mobile device850described below. In addition, it is to be appreciated that base station810and/or mobile device850can employ the systems (FIGS. 1-5) and/or methods (FIGS. 6-7) described herein to facilitate wireless communication there between.

At base station810, traffic data for a number of data streams is provided from a data source812to a transmit (TX) data processor814. According to an example, each data stream can be transmitted over a respective antenna. TX data processor814formats, codes, and interleaves the traffic data stream based on a particular coding scheme selected for that data stream to provide coded data.

The modulation symbols for the data streams can be provided to a TX MIMO processor820, which can further process the modulation symbols (e.g., for OFDM). TX MIMO processor820then provides NTmodulation symbol streams to NTtransmitters (TMTR)822athrough822t. In various embodiments, TX MIMO processor820applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.

Each transmitter822receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission over the MIMO channel. Further, NTmodulated signals from transmitters822athrough822tare transmitted from NTantennas824athrough824t, respectively.

At mobile device850, the transmitted modulated signals are received by NRantennas852athrough852rand the received signal from each antenna852is provided to a respective receiver (RCVR)854athrough854r. Each receiver854conditions (e.g., filters, amplifies, and downconverts) a respective signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding “received” symbol stream.

An RX data processor860can receive and process the NRreceived symbol streams from NRreceivers854based on a particular receiver processing technique to provide NT“detected” symbol streams. RX data processor860can demodulate, deinterleave, and decode each detected symbol stream to recover the traffic data for the data stream. The processing by RX data processor860is complementary to that performed by TX MIMO processor820and TX data processor814at base station810.

A processor870can periodically determine which precoding matrix to utilize as discussed above. Further, processor870can formulate a reverse link message comprising a matrix index portion and a rank value portion.

The reverse link message can comprise various types of information regarding the communication link and/or the received data stream. The reverse link message can be processed by a TX data processor838, which also receives traffic data for a number of data streams from a data source836, modulated by a modulator880, conditioned by transmitters854athrough854r, and transmitted back to base station810.

At base station810, the modulated signals from mobile device850are received by antennas824, conditioned by receivers822, demodulated by a demodulator840, and processed by a RX data processor842to extract the reverse link message transmitted by mobile device850. Further, processor830can process the extracted message to determine which precoding matrix to use for determining the beamforming weights.

Processors830and870can direct (e.g., control, coordinate, manage, etc.) operation at base station810and mobile device850, respectively. Respective processors830and870can be associated with memory832and872that store program codes and data. Processors830and870can also perform computations to derive frequency and impulse response estimates for the uplink and downlink, respectively.

It is to be understood that the embodiments described herein can be implemented in hardware, software, firmware, middleware, microcode, or any combination thereof. For a hardware implementation, the processing units can be implemented within one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, other electronic units designed to perform the functions described herein, or a combination thereof.

With reference toFIG. 9, illustrated is a system900that establishes compatible protocol connections with mobile devices in wireless networks. For example, system900can reside at least partially within an AGW, AAA server, base station, mobile device, etc. It is to be appreciated that system900is represented as including functional blocks, which can be functional blocks that represent functions implemented by a processor, software, or combination thereof (e.g., firmware). System900includes a logical grouping902of electrical components that can act in conjunction. For instance, logical grouping902can include an electrical component for determining a compatible communications protocol according to a received domain identifier related to a mobile device904. For example, as described, a domain identifier can be received following successful authentication/authorization of a device. It can be received in a user profile, in one example, and can define one or more domains related to the mobile device or user thereof. Thus, compatible protocols can be determined related to the domains to ensure compatible communication protocols are utilized in further communicating in the domain of the wireless network. Further, logical grouping902can comprise an electrical component for configuring protocol communication parameters for the mobile device to be utilized in subsequent communication based on the compatible communications protocol906. Thus, an IP address can be assigned, DNS server settings can be configured, etc., in response to a communications request from the mobile device. In this case, a protocol specified in the request can have been verified with those compatible with the domain. In another example, a list of compatible protocols can be sent to the device to facilitate requesting a compatible protocol. Additionally, system900can include a memory908that retains instructions for executing functions associated with electrical components904and906. While shown as being external to memory908, it is to be understood that one or more of electrical components904and906can exist within memory908.