Communication service usage transfer

Systems, methods, and apparatuses may allow a host device to facilitate communication from a guest device to a network, wherein the service usage charges that would ordinarily be charged against the host device account may be transferred to the guest device account. A method may include a host device connecting to a network. The host device may be associated with a first account. The host device may receive a connection from a guest device. The guest device may be associated with a second account. The host device may facilitate communication from the guest device to the network, wherein the facilitated communication from the guest device to the network may be a charge against the first account. The host device may provide instruction to the network to transfer the charge against the first account to the second account.

TECHNICAL FIELD

The technical field generally relates to wireless communications and more specifically to service usage.

BACKGROUND

An agreement between a consumer and a communication service provider, such as an Internet service provider (ISP) or a wireless service provider, typically involves a limitation on the usage of the consumer. For example, the use of a cell phone may be limited in the number of minutes, texts, or amount of data used on the cell phone. Similarly, a home ISP subscriber may be limited in the amount of data downloaded to or uploaded from the subscriber's home network.

Many modern mobile devices are capable of wirelessly connecting to a second device, such as a wireless router or another mobile device, and take advantage of the connections of the second device to perform communication operations. For example, a guest with a smart phone may connect to a wireless router at a host's home and browse the Internet or stream a movie over the wireless router's Internet connection instead of over the smart phone's cellular connection.

SUMMARY

As an example, a device may include a processor and a memory coupled to the processor. The memory may have instructions that effectuate the operations of connecting with a network entity. The device may be associated with a first account associated with the network entity. The operations may also include connecting with a second device. The second device may be associated with a second account associated with the network entity. The operations may include facilitating communication from the second device to the network entity. The facilitated communication from the second device to the network entity may cause a charge against the first account. Additionally, the operations may include providing an instruction to the network entity to facilitate a transfer of the charge against the first account to the second account.

As another example, a system may include a first device and a network entity. The network entity may include a processor and a memory coupled to the processor. The memory may have instructions that effectuate the operations of receiving a request for a connection. The request may be indicative of being provided by the first device. The first device may be associated with a first account associated with the network entity. The operations may include receiving an account identifier from the first device. The account identifier may be associated with a second device connected to the first device. The second device may be associated with a second account associated with the network entity. The operations may additionally include providing a communication service to the second device. The communication service may be facilitated by the first device and may comprise a charge against the first account. The operations may include facilitating a transfer of the charge against the first account to the second account.

As another example, a method may include receiving, by a network entity, a request for a connection to the network entity. The request may be indicative of being provided by a first device. The first device may be associated with a first account associated with the network entity. The method may include receiving, by the network entity, an account identifier from the first device. The account identifier may be associated with a second device connected to the first device. The second device may be associated with a second account associated with the network entity. The method may include providing, by the network entity, a communication service to the second device. The communication service may be facilitated by the first device and may comprise a charge against the first account. The method may additionally include facilitating, by the network entity, a transfer of the charge against the first account to the second account.

DETAILED DESCRIPTION

As described herein, usage of a communication service by a guest device via a host device may be charged against the communication service account associated with the guest device instead of the account associated with the host device. For example, a guest device, such as a smart phone, may connect to the mobile hotspot of a host device, such as a second smart phone. The guest device may access a communication service, such as the Internet, through the connection with the host device. The guest device may then proceed to browse the Internet and thus incur data usage charges which would ordinarily count against the account associated with the host device. However, by utilizing the systems and methods of communication service usage transfer disclosed herein, the data usage incurred may be charged against the account associated with the guest device.

FIG. 1illustrates an example communication system100in which one or more disclosed examples may be implemented. Connections within communication system100may be wireless or wireline. Communication system100may include a guest device103, a host device105, a communication service provider107, and a network, such as an Internet109, a public switched telephone network (PSTN)110, or other network111. The communication service provider107may include an account server113and a gateway106. The disclosed examples contemplate any number of guest devices103, host devices105, communication service providers107, gateways106, account servers113, and networks. The account server113may be communicatively connected to the gateway106. The guest device103may be communicatively connected to a network via the host device105and the communication service provider107, as discussed further herein. The host device105may be communicatively connected to a network via the communication service provider107, also discussed further herein.

The guest device103or host device105may include a mobile device, such as a cell phone, smart phone, tablet computer, personal digital assistant (PDA), personal gaming device, or laptop computer, or a networking device, such as a router (wireless or wireline), mobile broadband modem, data over cable service interface specification (DOCSIS) modem, digital subscriber line (DSL) modem, fiber optic modem, a satellite modem paired with a satellite dish, or any combination thereof. The guest device103or host device105may include a consumer device, such as a gaming console, television, stereo, or the like. Further, the guest device103or host device105may refer to a communication device integrated within another device, including a vehicle. For example, a vehicle may include an integrated communication device that connects to a cellular or other wireless network. Similarly, a consumer device, such as a coffee maker, washing machine, or refrigerator, may include an integrated communication device that may connect, for example, to a cellular network or WiFi network. The guest device103or host device105may also refer to the device itself with the integrated communication device (e.g., the car or the refrigerator). Additionally, the host device105may include a computer or server with a mobile device or networking device incorporated within or with software that is capable of performing the function of a mobile device or a networking device (e.g., a software router).

The host device105or the guest device103may each be associated or linked with an account of a communication service provider107and a user that is responsible for the account with the communication service provider107. It will be appreciated that the association may be pre-determined (e.g., the account owner is the owner of the guest device103or host device105) or may arise concurrently or near concurrently with the service usage (e.g., the account owner logs onto a shared workstation serving as the guest device103or the host device105or the account owner identifies his or her self on a host's television set serving as the guest device103or the host device105). An account with a communication service provider107may include a set allocation of units for a particular service. For example, an account may include an allocation of call minutes, number of text messages, or data bandwidth (e.g., the number of megabytes (MB) of data sent to or received from the host device105or guest device103). An account may also include a rate for a particular service, instead of or in addition to an allocation of units. As examples, an account may have a rate for each minute of a phone call (e.g., $0.10 per minute), a rate for each text (e.g., $0.05 per text), a rate for each MB of bandwidth used (e.g., $0.25 per MB of data sent or received), or a rate for each pay-per-view movie played.

Conventionally, the service usage of a mobile device or a networking device may each be charged against an account of the communication service provider107associated with that device. For instance, a smart phone may be associated with an account with a cellular service provider. When the smart phone is used to make a phone call, the minutes of the phone call may be charged against the account with the cellular service provider that is associated with the smart phone. When the smart phone is used to browse the Internet or download a song with the smart phone, the bandwidth usage (e.g., the number of megabytes (MB) of data sent to or received from the smart phone) may be charged against the account. Similarly, a DSL modem may be associated with an account with an Internet service provider (ISP). When the DSL modem accesses the Internet, the data bandwidth usage incurred may be charged against the account associated with the DSL modem. In both the smart phone and DSL modem examples, the service usage charge may comprise a deduction from a set allocation of units (e.g., call minutes, text messages, or MB of data) or a monetary charge (e.g., based on a rate) which must be paid.

The communication service provider107may include a network entity. A network entity may include a collection of devices owned by, leased to, or otherwise recognized to be part of a telecommunication provider's network. The devices may function to provide a telecommunication service such as cellular service, Internet service, satellite phone service, or satellite Internet service. The devices may also function to provide media delivery, such as a movie, a show, or music under a pay-per-view or subscription model. A device may include the gateway106, through which the host device105may connect to the communication service provider107, or the account server113. The functions of account server113, account system115, account database117, and gateway106may be in a single device or distributed to more than one device.

The gateway106may include a device that provides access to the communication service provider107. For example, where the host device105is a cellular device, the gateway106may include a base transceiver station (BTS), a base station controller (BSC), and a home subscriber server (HSS). The BTS, BSC, and HSS, along with other elements described further herein, may act in conjunction to authenticate the host device105and provide access to the communication service provider107(comprising a cellular service provider in this case). As another example, where the host device105is a router incorporating or connected to a DSL modem, the gateway106may include a digital subscriber line access multiplexer (DSLAM), which authenticates the DSL modem and allows the DSL modem access to the communication service provider107. As yet another example, where the host device105is a router incorporating or connected to a DOCSIS modem, the gateway106may include a cable modem termination system (CMTS), which authenticates the DOCSIS modem and provides access to the communication service provider107for the DOCSIS modem.

A network to which the communication service provider107may be connected may include the Internet109, the PSTN110, or other type of network111(e.g., local area network (LAN), wide area network (WAN), or intranet), or a combination thereof. It will be appreciated that the Internet109, the PSTN110, and other networks111may be interconnected. For example, a device connected to the PSTN110may be able to access the Internet109via the connection with the PSTN110.

The account server113may include a computing device, such as a server. An exemplary account server113may include a mainframe computer, a computer with a reduced instruction set computing (RISC) architecture, a computer with a complex instruction set computing (CISC) architecture, or a computer running a Unix (e.g. Advanced Interactive eXecutive (AIX), Berkeley Software Distribution (BSD), Solaris, Linux, Hewlett-Packard UniX (HP-UX)), Windows, or OS/390 operating system. The account server113may be a single device or may be comprised of multiple interconnected devices, such as a server cluster or a server with external peripherals (e.g., distributed storage server or database server).

The account server113may include an account system115. The account system115may comprise a software system that maintains the accounts associated with the guest device103or the host device105. The account server113may include an account database117, which may interact with the account system115. The account database117may store information on the accounts associated with the guest device103and the host device105. Such information may include information on a user or owner of the guest device103or host device105(e.g., name, address, or phone number), a credential or identifier associated with an account (e.g., user id, password, or account number), or an identifier associated with the guest device103or the host device105(e.g., media access control (MAC) address, international mobile subscriber identity (IMSI), or phone number of the guest device103or host device105). Account information stored in the account database117may also include information on an allocation of service units for an account or a rate for services for an account.

The account system115may interact with the gateway106to charge communication service usage provided by the communication service provider107. For example, if a host device105accesses the Internet109through the communication service provider107, the gateway106may communicate the data usage incurred by the host device105to the account system115on the account server113. Conventionally, the account system115may then charge the incurred data usage of the host device105to the account associated with the host device105.

The account system115may include a user interface in which information on an account may be viewed. Information on an account may include allocated service usage units, remaining service usage units, or rate. The user interface may also display usage details, such as details on a phone call (e.g., the number of minutes of the call, the start and stop times of the call, or the recipient or source of the call), details on a text message (e.g., the time of the text message or the recipient or source of the text message), or details on a data usage (e.g., the time of the data usage, the amount of data uploaded or downloaded, or the recipient or source of the data usage). As discussed further herein, the user interface may also present information on usage that was incurred while the host device105was serving as a host for the guest device103to access the communication service provider107.

At block202, a host device105may connect to a communication service provider107. A communication service provider107may provide access to a network, such as the PSTN110, the Internet109, or other network111.

In connecting to the communication service provider107, the host device105may connect to a gateway106of the communication service provider107. For example and as discussed elsewhere herein, the gateway106of a cellular service provider may be comprised of a base transceiver station (BTS), a base station controller (BSC), and a home subscriber server (HSS). As another example, the gateway106of a communication service provider107that provides Internet service may include a digital subscriber line access multiplexer (DSLAM) or a cable modem termination system (CMTS). The host device105may connect to the gateway106over a wireless (e.g., radio wave) or wireline (e.g. fiber optic, ethernet, DSL, or cable television infrastructure) connection. The host device105may provide an identifier, such as a media access control (MAC) address or international mobile subscriber identity (IMSI), or user id and password, to the gateway106in order for the gateway106, which may operate in conjunction with the account system115, to allow the connection. Once the host device105is connected to the gateway106of the communication service provider107, the host device105may then be free to access a network. For example, once the host device105, such as a cellular mobile device, connects to the gateway106, such as a BTS, the host device105may then place a call to another device with in the PSTN110. It should be appreciated that the host device105may or may not use the services offered by the communication service provider107and the network (such as placing a call within PSTN110or browsing the Internet109); the host device105may merely be connected to the gateway106and, thereby, the communication service provider107.

At block204, a guest device103may connect to the host device105. The guest device103may connect to the host device105over, for example, a wireless interface or a wireline interface. A wireless interface may include a WiFi or Bluetooth connection. In connecting over WiFi or Bluetooth, a wireless ad hoc network (WANET) or mobile ad hoc network (MANET) may be formed. If the host device105is a mobile device, the host device105may operate as a mobile hotspot, thus acting as a wireless access point (WAP) and router for the guest device103. A wireline interface may include a connection over a universal serial bus (USB) cable or an ethernet cable. As an illustration, the guest device103, such as a smart phone, may connect over a Bluetooth connection to the mobile hotspot offered by the host device105, such as another smart phone. As another illustration, the guest device103, such as a tablet computer, may connect over a WiFi connection to the host device105, such as a wireless router paired with a DSL modem. The guest device103may connect to the host device105based on limited connectivity of the guest device103, no connectivity of the guest device103, or relatively high-cost connectivity of the guest device103, such as when a cellular mobile device is out of its normal service area (e.g., roaming). As another example, the guest device103, such as a tablet computer having WiFi capability, but not cellular capability, may connect to the host device105that is capable of connecting to the communication service provider107over a cellular connection (e.g., where the host device105is a cellular mobile device) or a wired network connection (e.g., where the host device105is a wireless router paired with a modem). These are a few example instances in which the present disclosure may allow the guest device103access to a communication service which the guest device103might not otherwise have been able to access.

At block206, the guest device103may provide an account identifier to the host device105. The account identifier may identify the guest device103or the owner or user of the guest device103so that the account identifier may be cross-referenced in the account system115to identify the account in the account system115associated with the guest device103or the owner or user of the guest device103. The account identifier may include a device identifier, such as a device ID number (e.g., an international mobile subscriber identity (IMSI) stored on the subscriber identity module (SIM) within the guest device103). The device identifier may be included in the communication session or header information and may later be cross-referenced in the account system115to identify, for example, a mobile station international subscriber directory number (MSISDN) associated with the guest device103. The account identifier may also be in the form of an account number, a user name (which may be paired with a password), a phone number, or any other means of linking the guest device103or guest device103with an associated account. Providing an account identifier may also include more advanced security features. For example, the guest device103may transmit a token to the host device105for the host device105to present to the guest device's103account system115or funding source. The token may be a value, such as a number, letter, or combination of numbers and letters, that, when presented, confirms authorization to access services or access information. The token may contain embedded and tamperproof limitations to protect against overbilling (e.g., a time interval, a total amount to transfer, the types of destination traffic to be transferred, and the like).

The provision of the account identifier by the guest device103to the host device105may occur automatically or may involve an input to the guest device103which is then provided by the guest device103to the host device105. The provision of the account identifier may also be in response to a prompt from the host device105. For example, after the guest device103connects to the host device105, the host device105may provide or cause a user interface, such as a webpage, to be displayed on the guest device103. A user interface may also be provided using a protocol, such as session initiation protocol (SIP), to exchange structured data that the guest device103may then interpret and present upon the guest device103. Referring toFIG. 4, the user interface400displayed on the guest device103may display a selectable option404to authorize the guest device's103usage of a communication service to be charged to the guest device103account. The user interface400may include an input field402in which an account identifier may be collected. In this example, the input field402includes a space to enter an account ID and password.

Such a prompt may be performed upon the guest device103connecting to the host device105, upon the guest device103hitting a threshold usage level, or may not occur until the guest device103attempts to use a communication service through the host device105(and thus incur a usage charge which would ordinarily be charged against the account associated with the host device105). For example, if a guest device103attempts to use a web browser to access the Internet109, the web browser may be redirected to a webpage in which an account identifier may be input. A prompt for the authorization that the service usage incurred may be charged to the guest device103account may also include a conditional authorization. For example, the transfer of service usage charges may only take effect if the guest device103incurs more than a pre-specified amount of service usage (e.g., no service usage will be transferred for up to 10 MB of data usage, but service usage beyond 10 MB of data usage will be transferred). As another example, it may be authorized that the transfer of service usage charges may only take effect if the host device105account includes service usage charges above a pre-specified threshold. To illustrate, the transfer may only take effect if the host device105account exceeded a monthly allocation of data usage.

In another example, the host device105may provide a selectable option for the authorization of an arrangement or provide a choice of arrangements in which the guest device103may use a communication service through the host device105for a pre-specified period of time and during which all service usage charges would be transferred to the guest device103account. An arrangement may also include where the guest device103may use a communication service through the host device105for a pre-specified period of time and a pre-specified flat fee (e.g., $10.00) or pre-specified amount of usage (e.g., 15 minutes of phone call time or 10 MB of data usage) will be transferred to the guest device103account. An arrangement may also include where the guest device103may use a communication service through the host device105for up to a pre-specified amount of usage. For example, the guest device103may use up to 25 MB of data usage. The pre-specified amount of service usage will then be transferred to the guest device103account, whether or not the guest device103actually consumes the pre-specified amount of service usage.

In another example, the guest device103may provide the account information associated with the guest device103to the communication service provider107. This may occur automatically, for example, by virtue of the communication service provider107being aware of devices connected to the communication service provider107, even those connected via an intermediate device (e.g., the host device105).

At block208, the guest device103may utilize a communication service of the communication service provider107via the host device105. Recalling that the host device105is connected to the communication service provider107and that the guest device103is connected to the host device105, the host device105may allow the guest device103to utilize a communication service through the host device105. For example, using mobile hotspot technology, the host device105, such as a smart phone, may allow the connected guest device103, such as a tablet computer, to take advantage of the host device's105connection to browse the Internet109through the communication service provider107. As another example, the host device105, such as a wireless router paired with a DSL modem, may allow a connected guest device103, such as a smart phone, access to the Internet109, via the communication service provider107, so that the guest device103may stream a video from the Internet109. In the absence of the present disclosure, the usage for the services used by the guest device103via the host device105would be charged to the host device105account, even though the ultimate destination of, for example, downloaded data or a text message is the guest device103.

While the guest device103is using the communication services through the host device105, the host device105may log information on the guest device's103service usage. For example, such information may include the start and stop time of the usage, the number of minutes of a phone call, or the amount of data downloaded or uploaded. The communication service provider107, such as the gateway106or the account system115, may also log similar information on the service usage. It will be appreciated by one skilled in the art that exact (e.g., per byte) logging of service usage may be difficult to achieve. Accordingly, service usage may be approximated or rounded up or down to the nearest service usage unit (e.g., MB of data usage).

When the guest device103completes its service usage session, the host device105may provide an end-of-session service usage transfer acknowledgement which may contain information on the service usage logged by the host device105and which the host device105plans to transmit to the account system115for transfer. This may afford an opportunity for the guest device103or the guest device103user to compare the host device's105logged service usage information with service usage information for the session logged by the guest device103. The end-of-session service usage transfer acknowledgement may be in the form of a user interface, such as a webpage, which the host device105causes to be displayed on the guest device103, or in the form of raw service usage data (e.g., number of MB of data usage). Further, the guest device103may automatically compare the service usage information logged by and transmitted from the host device105against service usage information logged by the guest device103. If the two service usages reflected in the two sets of service usage information are different or differ by a pre-specified threshold (e.g., percent difference or absolute difference), a message or warning may be generated on the guest device103. Conversely, the guest device103may transmit service usage information logged on the guest device103to the host device105so that the host device105may compare the host device's105logged service usage information against that from the guest device103. If the host device105detects a difference or difference beyond a pre-specified threshold, the host device105may cause a message to display on the host device105communicating the discrepancy. In addition, if the host device105detects a discrepancy, it may transmit to or cause to display a user interface or message on the guest device103that communicates the discrepancy. In a similar fashion, the communication service provider107may log service usage information pertaining to the service usage of the guest device103facilitated by the host device105. In turn, when the service usage session ends, either by volition of the guest device103, the host device105, or the communication service provider107, the communication service provider107may transmit an end-of-session service usage transfer acknowledgement, including service usage information, to the host device105which may then be transmitted to the guest device103. The guest device103may compare the communication service provider107service usage data with its own logged data and provide a message, as described herein.

At block210, the host device105may instruct the communication service provider107to transfer service usage charges incurred by the guest device's103service usage via the host device105to the guest device103account. The host device105may perform the instruction to transfer the service usage charges by communicating information, such as the account identifier provided by the guest device103in block206and the logged information on the guest device's103usage, to the account system115. The account system115may then use the account identifier to identify an account associated with the guest device103. The identification may be performed by cross-referencing the account identifier in the account database117.

FIG. 6provides an exemplary illustration of the account system115with the host device105connected. The account system115includes a host device105account, depicted as account A602, and a guest device103account, depicted as account B604. Account A602may include one or more service usage charges, depicted inFIG. 6as service usage606, service usage608, and service usage610. The host device105may communicate to the account system115an account identifier identifying the guest device103account as account B604. The host device105may also communicate logged information on the guest device's103service usage, which may identify the service usage610(shown in a dotted circle) in account A602as the guest device's103service usage. The service usage610may be flagged or labeled to identify it as a service usage that is eligible to be transferred. A service usage charge, such as service usage610, may also exist in the account system115as a anticipatory service usage charge (e.g., it is a service usage charge that is not yet charged to the account but will be after some pre-specified period of time if the service usage charge is not transferred).

It should be appreciated that a user associated with the host device105may also perform the instruction to transfer service usage charges, such as via a user interface which is part of the account system115. As an illustration, if the guest device103had provided an account number as the account identifier and downloaded 10 MB of data through the host device105, the host device105user may log in to a user interface of the account system115and provide the account number and the 10 MB of data service usage to the account system115and instruct the account system115to charge the 10 MB of data service usage to the account associated with the account number.

The host device105may perform the instruction to transfer the service usage charges automatically at the time the service usage charges are incurred. Alternatively, the host device105may instruct the account system115to transfer the service usage charges at a later, pre-specified period of time, such as at the end of a billing cycle. The information pertaining to the service usage may be communicated to the account system115at the time of service usage or also at a later pre-specified period of time. For example, a user associated with the host device105may view his or her account, via a user interface of the account system115, for a billing period in which a guest device103had incurred a service usage charge against the host device105account. The host device105user may see that he or she exceeded his or her service usage allocation for the billing period. At that point, the user may instruct the account system115to transfer the service usage charge incurred by the guest device103to the guest device103account.

At block212, the account system115of the communication service provider107may transfer the service usage charges incurred in block208from the account associated with the host device105to the account associated with the guest device103.

Referring again toFIG. 6, the account system115may transfer the service usage charge identified in block210(e.g., service usage610) to the guest device103account identified in block210(e.g., account B604). The transfer is represented inFIG. 6by the dotted arrow and the transferred location in account B604of the service usage610is shown as service usage610′. The account system115may perform the transfer of service usage charges by crediting account A602with the service usage610and deducting the service usage610′ from the account B604. For example, if the service usage610is 10 MB of data, account A602has 800 MB of data remaining in its allocation of data charges, and account B604has 1000 MB of data remaining in its allocation of data charges, the account system115would credit account A602with 10 MB of data charges (leaving it with 810 MB) and deduct the 10 MB of data charges from account B604(leaving it with 990 MB). This example assumes that the service usage610has already been charged against account A602. In another example, a service usage charge may not yet be charged against account A602, but may merely be pending. In this case, the account system115would cancel the pending service usage charge against account A602and then deduct the service usage charge from account B604.

Continuing to referenceFIG. 6, if account A602or account B604include a rate for a service (e.g., $0.10 per MB of data usage) instead of an allocation of service usage units, the account system115may multiply the service usage charge of block208by the rate for that service and then credit and deduct or charge the resulting amount from the host device105account and the guest device103account, respectively.

In one example, the account system115may automatically transfer the service usage charge from the host device105account to the guest device103account. The account system115may automatically perform the transfer based on a setting or rule. The setting or rule may be previously provided or set by the user of the host device105. The setting or rule may relate to threshold amount of service usage available, service usage already consumed, or rate. For example, at a previous time, the host device105user may use a user interface of the account system115to specify that all service usage charges incurred by all guest devices103that may be connected to the host device105are to be automatically transferred to the guest device103account. The host device105user may also specify that if a certain percentage or more of an allocated service usage is consumed (e.g., more than 50% of an allocated 1000 MB of data usage), then the account system115is to automatically transfer service usage charges incurred by guest devices103to the guest device103account. Similarly, the guest device103user may use a user interface of the account system115to provide a setting or rule pertaining to the service usage charges incurred by the guest device103while connected to the host device105. For example, the guest device103user may specify that all service usage charges should be transferred to the guest device103account. The guest device103user may specify a rule that service usage charges should only be transferred if a service usage allocation in the guest device103account has exceeded a certain threshold. Or the guest device103user may specify a rule that service usage charges should only be transferred if a service usage allocation in the host device105account has exceeded a certain threshold.

FIG. 3illustrates an exemplary method200for communication service usage transfer. At block302, a host device105may connect to a communication service provider107, such as via a gateway106. At block304, a guest device103may connect to the host device105, such as via a Bluetooth or WiFi connection. At block306, the guest device103may provide an account identifier, such as an account number or international mobile subscriber identity (IMSI), to the host device105.

At block308, the host device105may retrieve account information associated with the guest device103. For example, the host device105may communicate with an account system115associated with the guest device103and provide the account identifier for the guest device103. The account system115may retrieve account information on the guest device103account by cross-referencing the provided account identifier and communicate the account information back to the host device105. Account information may include a rate for services ordinarily used by the guest device103(e.g., phone calls are billed at $0.10 per minute, data usage is billed at $0.25 per MB). Account information may also include information on service usage allocations, such as the total units allocated, units consumed, and units remaining. For examples, the account information may indicate that the guest device103account is allocated 100 MB of data usage per billing period and has 50 MB of data usage remaining for the current billing period. The account information may also include a combination of the aforementioned examples such that the account information indicates an allocation of service usage allocation and also a billing rate for service usage beyond that allocation.

At block310, the host device105may present an option, based on the account information of the guest device103, to transfer service usage charges to the guest device103account. Referring toFIG. 5, the host device105may cause a user interface (shown as user interface500) to be presented on the guest device103. The user interface500may display information about the guest device103account (shown as account information502), such as a service billing rate from the guest device103account or an amount of service usage remaining of a service usage allocation for the billing period. The user interface500may also display one or more conditions for an option of not transferring service usage charges to the guest device103account (shown as condition504). For instance, if service usage charges are not transferred, then a fee to a person or entity associated with the host device105may have to be paid. Such a fee may include a one-time fee, a per-service-usage-unit fee, or a fee for a pre-specified period of time. The user interface500may provide a selectable option (shown as option506) to authorize the service usage charges incurred by the guest device103to be transferred to the guest device103account. The user interface500may provide a selectable option (shown as option508) to decline the service usage charge transfer and authorize the condition504. By displaying billing and usage information from the guest device103account and an alternative billing option for not transferring service usage charges, the user interface500may allow an informed decision to be made to most efficiently use a communication service.

As an illustration, the user interface500on the guest device103may show that the guest device103account would be charged $0.25 per MB of data usage and that if an election was not made to transfer the service usage charge for a contemplated file download, a fee at a rate of $0.35 per MB of data usage would have to be paid to the host device105owner. In this case, an election would likely be made on the user interface500to transfer the service usage charge to the guest device103account since it would be cheaper. As another illustration, the user interface500may show that the guest device103account has only 5 MB of data usage remaining of the billing period allocation and that an overage would result in a $10 penalty and charge at the rate of $1 per MB. The user interface500may also show that if an election was not made to transfer the service usage charge, a flat $5 fee would have to be paid to the host device105owner. Since it likely would be desirable to avoid the larger overage penalty and per-MB rate on the guest device103account, an election to decline the option to transfer changes to the guest device103account and instead pay the fee to the host device105owner would be likely. In another example, the guest device103may show on user interface500a likelihood (e.g., 90%, “very likely”, etc.) of an overage charge (e.g., $0, $0.10, $1.00, etc.) or any other charge based on a past usage of bandwidth associated with host device105. For instance, host device105may allow connections from multiple devices that are associated with different accounts. The host device105, itself, may be charged a flat rate for a threshold bandwidth usage and additional charges for amounts over the threshold bandwidth usage. The likelihood may be determined based on the historical bandwidth usage of the host device105alone or in combination with the guest device103, or other devices or associated accounts. The likelihood may be continuously updated and displayed on the user interface500over the course of the session by the guest device103.

At block312, the guest device103may utilize a communication service of the communication service provider107via the host device105, such as browsing the Internet109. At block314, if transfer is elected in block310, the host device105may instruct the communication service provider107to transfer the service usage charge, such as that incurred in block312, to the guest device103account. If transfer is declined in block310, then the host device105or a person or entity associated with the host device105may impose a fee upon the guest device103for the service usage charge incurred. In block316, the communication service provider107may transfer the service usage charge from the host device105account to the guest device103account.

FIG. 7illustrates an example wireless device710(e.g., WTRU) that may be used in connection with communication service usage transfer. References will also be made to other figures of the present disclosure as appropriate. For example, the guest device103and the host device105may include a wireless device of the type described in regard toFIG. 7, and may have some, all, or none of the components and modules described in regard toFIG. 7. It will be appreciated that the components and modules of wireless device710illustrated inFIG. 7are illustrative, and that any number and type of components and/or modules may be present in wireless device710. In addition, the functions performed by any or all of the components and modules illustrated inFIG. 7may be performed by any number of physical components. Thus, it is possible that in some configurations the functionality of more than one component and/or module illustrated inFIG. 7may be performed by any number or types of hardware or hardware and software.

Processor721may be any type of circuitry that performs operations on behalf of wireless device710. Such circuitry may include circuitry and other components that enable processor721to perform any of the functions and methods described herein. Such circuitry and other components may also enable processor721to communicate and/or interact with other devices and components, for example any other component of wireless device710, in such a manner as to enable the guest device103and the host device105and such other devices and/or components to perform any of the disclosed functions and methods. In an example configuration, processor721executes software (e.g., computer readable instructions stored in a computer readable medium) that may include functionality related to communication service usage transfer, for example. User interface module722may be any type or combination of hardware and software that enables a user to operate and interact with wireless device710, and, in an example configuration, to interact with a system enabling the user to place, request, and/or receive calls, text communications of any type, voicemail, voicemail notifications, voicemail content and/or data, and/or a system. For example, user interface module722may include a display, physical and/or “soft” keys, voice recognition software, a microphone, a speaker and the like. Wireless communication module723may be any type of transceiver including any combination of hardware and software that enables wireless device710to communicate with wireless network equipment. Memory724enables wireless device710to store information, such as an alert or information associated with a region. Memory724may take any form, such as internal random access memory (RAM), an SD card, a microSD card and the like. Power supply725may be a battery or other type of power input (e.g., a charging cable that is connected to an electrical outlet, etc.) that is capable of powering wireless device710. SIM726may be any type Subscriber Identity Module (SIM) and may be configured on a removable or non-removable SIM card that allows wireless device710to store data on SIM726.

FIG. 8is a block diagram of an example processor858in which communication service usage transfer may be implemented. Processor858may be employed in any of the examples described herein, including as one or more components of the guest device103, the host device105, the gateway106, the communication service provider107, the account server113, the account system115, the account database117, and/or as one or more components of any third party system or subsystem that may implement any portion of the subject matter described herein. It is emphasized that the block diagram depicted inFIG. 8is exemplary and not intended to imply a specific implementation. Thus, the processor858may be implemented in a single processor or multiple processors. Multiple processors may be distributed or centrally located. Multiple processors may communicate wirelessly, via hard wire, or a combination thereof. Processor858may include circuitry and other components that enable processor858to perform any of the functions and methods described herein. Such circuitry and other components may also enable processor858to communicate and/or interact with other devices and components, for example any other component of any device disclosed herein or any other device, in such a manner as to enable processor858and such other devices and/or components to perform any of the disclosed functions and methods.

As depicted inFIG. 8, the processor858comprises a processing portion860, a memory portion862, and an input/output portion864. The processing portion860, memory portion862, and input/output portion864are coupled together (coupling not shown inFIG. 8) to allow communications between these portions. The input/output portion864is capable of providing and/or receiving components, commands, and/or instructions, utilized to, for example, establish and terminate communications sessions, transmit and receive service requests and data access request data and responses, transmit, receive, store and process text, data, and voice communications, execute software that efficiently receives and processes media requests, transmit media, and/or perform any other function described herein.

The processor858may be implemented as a client processor and/or a server processor. In a basic configuration, the processor858may include at least one processing portion860and memory portion862. The memory portion862may store any information utilized in conjunction with establishing, transmitting, receiving, and/or processing text, data, media, and/or voice communications, communications-related data and/or content, voice calls, other telephonic communications, etc. For example, the memory portion is capable of storing media content, such as video media files, audio media files, and text media files. Depending upon the exact configuration and type of processor858, the memory portion862may be volatile (such as RAM)866, non-volatile (such as ROM, flash memory, etc.)868, or a combination thereof. The processor858may have additional features/functionality. For example, the processor858may include additional storage (removable storage870and/or non-removable storage872) including, but not limited to, magnetic or optical disks, tape, flash, smart cards or a combination thereof. Computer storage media, such as memory and storage elements862,870,872,866, and868, may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data. Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, universal serial bus (USB) compatible memory, smart cards, or any other medium that can be used to store the desired information and that can be accessed by the processor858. Any such computer storage media may be part of the processor858and is not a transient signal.

The processor858may also contain the communications connection(s)880that allow the processor858to communicate with other devices, for example through a radio access network (RAN). Communications connection(s)880is an example of communication media. Communication media typically embody computer-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection as might be used with a land line telephone, and wireless media such as acoustic, RF, infrared, cellular, and other wireless media. The term computer-readable media as used herein includes both storage media and communication media, wherein storage media is not a transient or propagated signal. A computer-readable storage medium, as described herein is an article of manufacture having a concrete, tangible, physical structure, and thus, not to be construed as a propagating signal. Any computer-readable storage medium described herein is not to be construed as a signal. Any computer-readable storage medium described herein is to be construed as an article of manufacture having a concrete, tangible, physical structure. The processor858also may have input device(s)876such as keyboard, keypad, mouse, pen, voice input device, video input device, touch input device, etc. Output device(s)874such as a display, speakers, printer, etc. also may be included.

A RAN as described herein may comprise any telephony radio network, or any other type of communications network, wireline or wireless, or any combination thereof. The following description sets forth some exemplary telephony radio networks, such as the global system for mobile communications (GSM), and non-limiting operating environments. The below-described operating environments should be considered non-exhaustive, however, and thus the below-described network architectures merely show how communication service usage transfer may be implemented with stationary and non-stationary network structures and architectures in order to enable communication service usage transfer. It can be appreciated, however, that communication service usage transfer as described herein may be incorporated with existing and/or future alternative architectures for communication networks as well.

The GSM is one of the most widely utilized wireless access systems in today's fast growing communication environment. The GSM provides circuit-switched data services to subscribers, such as mobile telephone or computer users. The General Packet Radio Service (GPRS), which is an extension to GSM technology, introduces packet switching to GSM networks. The GPRS uses a packet-based wireless communication technology to transfer high and low speed data and signaling in an efficient manner. The GPRS attempts to optimize the use of network and radio resources, thus enabling the cost effective and efficient use of GSM network resources for packet mode applications.

The exemplary GSM/GPRS environment and services described herein also may be extended to 3G services, such as Universal Mobile Telephone System (UMTS), Frequency Division Duplexing (FDD) and Time Division Duplexing (TDD), High Speed Packet Data Access (HSPDA), cdma2000 1 Evolution Data Optimized (EVDO), Code Division Multiple Access-2000 (cdma2000 3), Time Division Synchronous Code Division Multiple Access (TD-SCDMA), Wideband Code Division Multiple Access (WCDMA), Enhanced Data GSM Environment (EDGE), International Mobile Telecommunications-2000 (IMT-2000), Digital Enhanced Cordless Telecommunications (DECT), 4G Services such as Long Term Evolution (LTE), etc., as well as to other network services that become available in time. In this regard, communication service usage transfer may be applied independently of the method of data transport and does not depend on any particular network architecture or underlying protocols.

FIG. 9depicts an overall block diagram of an exemplary packet-based mobile cellular network environment, such as a GPRS network, in which apparatuses, systems, and methods for communication service usage transfer such as those described herein may be practiced. In an example configuration, any RAN as described herein may be encompassed by or interact with the network environment depicted inFIG. 9. Similarly, wireless-enabled devices, such as the guest device103or the host device105may communicate or interact with a network environment such as that depicted inFIG. 9. In such an environment, there may be a plurality of Base Station Subsystems (BSS)900(only one is shown), each of which comprises a Base Station Controller (BSC)902serving a plurality of Base Transceiver Stations (BTS) such as BTSs904,906, and908. BTSs904,906,908, etc. are the access points where users of packet-based mobile devices (e.g., the guest device103or the host device105) become connected to the wireless network. In exemplary fashion, the packet traffic originating from user devices (e.g., the guest device103or the host device105) may be transported via an over-the-air interface to a BTS908, and from the BTS908to the BSC902. Base station subsystems, such as BSS900, may be a part of internal frame relay network910that can include Service GPRS Support Nodes (SGSN) such as SGSN912and914. Each SGSN may be connected to an internal packet network920through which a SGSN912,914, etc. may route data packets to and from a plurality of gateway GPRS support nodes (GGSN)922,924,926, etc. As illustrated, SGSN914and GGSNs922,924, and926may be part of internal packet network920. Gateway GPRS serving nodes922,924and926may provide an interface to external Internet Protocol (IP) networks, such as Public Land Mobile Network (PLMN)950, corporate intranets940, or Fixed-End System (FES) or the public Internet930. As illustrated, subscriber corporate network940may be connected to GGSN924via firewall932, and PLMN950may be connected to GGSN924via border gateway router934. The Remote Authentication Dial-In User Service (RADIUS) server942may be used for caller authentication when a user of a mobile cellular device calls corporate network940.

Generally, there can be four different cell sizes in a GSM network, referred to as macro, micro, pico, and umbrella cells. The coverage area of each cell is different in different environments. Macro cells may be regarded as cells in which the base station antenna is installed in a mast or a building above average roof top level. Micro cells are cells whose antenna height is under average roof top level. Micro-cells may be typically used in urban areas. Pico cells are small cells having a diameter of a few dozen meters. Pico cells may be used mainly indoors. On the other hand, umbrella cells may be used to cover shadowed regions of smaller cells and fill in gaps in coverage between those cells.

FIG. 10illustrates an example architecture of a GPRS network in which one or more disclosed examples of communication service usage transfer may be implemented. The GPRS network depicted inFIG. 10comprises four groups: users1050, radio access network1060, core network1070, and interconnect network1080. Users1050may comprise a plurality of end users (though only mobile subscriber1055is shown inFIG. 10). In an example, the device depicted as mobile subscriber1055may comprise any of the guest device103or the host device105. Radio access network1060comprises a plurality of base station subsystems such as BSSs1062, which include BTSs1064and BSCs1066. Core network1070comprises a host of various network elements. As illustrated here, core network1070may comprise Mobile Switching Center (MSC)1071, Service Control Point (SCP)1072, gateway MSC1073, SGSN1076, Home Location Register (HLR)1074, Authentication Center (AuC)1075, Domain Name Server (DNS)1077, and GGSN1078. Interconnect network1080may also comprise a host of various networks and other network elements. As illustrated inFIG. 10, interconnect network1080comprises Public Switched Telephone Network (PSTN)1082, Fixed-End System (FES) or Internet1084, firewall1088, and Corporate Network1089.

A mobile switching center may be connected to a large number of base station controllers. At MSC1071, for instance, depending on the type of traffic, the traffic may be separated in that voice may be sent to Public Switched Telephone Network (PSTN)1082through Gateway MSC (GMSC)1073, and/or data may be sent to SGSN1076that may send the data traffic to GGSN1078for further forwarding.

When MSC1071receives call traffic, for example, from BSC1066, it may send a query to a database hosted by SCP1072. The SCP1072may process the request and may issue a response to MSC1071so that it may continue call processing as appropriate.

The HLR1074may be a centralized database for users to register to the GPRS network. In some examples, HLR1074may be a device such as HSSs. HLR1074may store static information about the subscribers such as the International Mobile Subscriber Identity (IMSI), APN profiles as described herein, subscribed services, and a key for authenticating the subscriber. HLR1074may also store dynamic subscriber information such as dynamic APN profiles and the current location of the mobile subscriber. HLR1074may also serve to intercept and determine the validity of destination numbers in messages sent from a device, such as mobile subscriber1055, as described herein. Associated with HLR1074may be AuC1075. AuC1075may be a database that contains the algorithms for authenticating subscribers and may include the associated keys for encryption to safeguard the user input for authentication.

In the following, depending on context, the term “mobile subscriber” sometimes refers to the end user and sometimes to the actual portable device, such as the guest device103or the host device105, used by an end user of a mobile cellular service or a wireless provider. When a mobile subscriber turns on his or her mobile device, the mobile device may go through an attach process by which the mobile device attaches to an SGSN of the GPRS network. InFIG. 10, when mobile subscriber1055initiates the attach process by turning on the network capabilities of the mobile device, an attach request may be sent by mobile subscriber1055to SGSN1076. The SGSN1076queries another SGSN, to which mobile subscriber1055was attached before, for the identity of mobile subscriber1055. Upon receiving the identity of mobile subscriber1055from the other SGSN, SGSN1076may request more information from mobile subscriber1055. This information may be used to authenticate mobile subscriber1055to SGSN1076by HLR1074. Once verified, SGSN1076sends a location update to HLR1074indicating the change of location to a new SGSN, in this case SGSN1076. HLR1074may notify the old SGSN, to which mobile subscriber1055was attached before, to cancel the location process for mobile subscriber1055. HLR1074may then notify SGSN1076that the location update has been performed. At this time, SGSN1076sends an Attach Accept message to mobile subscriber1055, which in turn sends an Attach Complete message to SGSN1076.

After attaching itself to the network, mobile subscriber1055may then go through the authentication process. In the authentication process, SGSN1076may send the authentication information to HLR1074, which may send information back to SGSN1076based on the user profile that was part of the user's initial setup. The SGSN1076may then send a request for authentication and ciphering to mobile subscriber1055. The mobile subscriber1055may use an algorithm to send the user identification (ID) and password to SGSN1076. The SGSN1076may use the same algorithm and compares the result. If a match occurs, SGSN1076authenticates mobile subscriber1055.

Next, the mobile subscriber1055may establish a user session with the destination network, corporate network1089, by going through a Packet Data Protocol (PDP) activation process. Briefly, in the process, mobile subscriber1055may request access to an Access Point Name (APN), for example, UPS.com, and SGSN1076may receive the activation request from mobile subscriber1055. SGSN1076may then initiate a Domain Name Service (DNS) query to learn which GGSN node has access to the UPS.com APN. The DNS query may be sent to the DNS server within the core network1070, such as DNS1077, which may be provisioned to map to one or more GGSN nodes in the core network1070. Based on the APN, the mapped GGSN1078may access the requested corporate network1089. The SGSN1076may then send to GGSN1078a Create Packet Data Protocol (PDP) Context Request message that contains necessary information. The GGSN1078may send a Create PDP Context Response message to SGSN1076, which may then send an Activate PDP Context Accept message to mobile subscriber1055.

Once activated, data packets of the call made by mobile subscriber1055may then go through radio access network1060, core network1070, and interconnect network1080, in a particular fixed-end system, or Internet1084and firewall1088, to reach corporate network1089.

Thus, network elements that can invoke the functionality of apparatuses, systems, and methods for communication service usage transfer such as those described herein may include, but are not limited to, Gateway GPRS Support Node tables, Fixed End System router tables, firewall systems, VPN tunnels, and any number of other network elements as required by the particular digital network.

FIG. 11illustrates another exemplary block diagram view of a GSM/GPRS/IP multimedia network architecture1100in which the apparatuses, systems, and methods for communication service usage transfer such as those described herein may be incorporated. As illustrated, architecture1100ofFIG. 11includes a GSM core network1101, a GPRS network1130and an IP multimedia network1138. The GSM core network1101includes a Mobile Station (MS)1102, at least one Base Transceiver Station (BTS)1104and a Base Station Controller (BSC)1106. The MS1102is physical equipment or Mobile Equipment (ME), such as a mobile telephone or a laptop computer (e.g., the guest device103or the host device105) that is used by mobile subscribers, in one example with a Subscriber Identity Module (SIM). The SIM includes an International Mobile Subscriber Identity (IMSI), which is a unique identifier of a subscriber. The SIM may also include APNs. The BTS1104may be physical equipment, such as a radio tower, that enables a radio interface to communicate with the MS. Each BTS may serve more than one MS. The BSC1106may manage radio resources, including the BTS. The BSC may be connected to several BTSs. The BSC and BTS components, in combination, are generally referred to as a base station (BSS) or radio access network (RAN)1103.

The GSM core network1101may also include a Mobile Switching Center (MSC)1108, a Gateway Mobile Switching Center (GMSC)1110, a Home Location Register (HLR)1112, Visitor Location Register (VLR)1114, an Authentication Center (AuC)1118, and an Equipment Identity Register (EIR)1116. The MSC1108may perform a switching function for the network. The MSC may also perform other functions, such as registration, authentication, location updating, handovers, and call routing. The GMSC1110may provide a gateway between the GSM network and other networks, such as an Integrated Services Digital Network (ISDN) or Public Switched Telephone Networks (PSTNs)1120. Thus, the GMSC1110provides interworking functionality with external networks.

The HLR1112may be a database that may contain administrative information regarding each subscriber registered in a corresponding GSM network. Such information may include APNs and APN profiles. The HLR1112may also contain the current location of each MS. The VLR1114may be a database that contains selected administrative information from the HLR1112. The VLR may contain information necessary for call control and provision of subscribed services for each MS currently located in a geographical area controlled by the VLR. The HLR1112and the VLR1114, together with the MSC1108, may provide the call routing and roaming capabilities of GSM. The AuC1116may provide the parameters needed for authentication and encryption functions. Such parameters allow verification of a subscriber's identity. The EIR1118may store security-sensitive information about the mobile equipment.

A Short Message Service Center (SMSC)1109allows one-to-one short message service (SMS), or multimedia message service (MMS), messages to be sent to/from the MS1102. A Push Proxy Gateway (PPG)1111is used to “push” (e.g., send without a synchronous request) content to the MS1102. The PPG1111acts as a proxy between wired and wireless networks to facilitate pushing of data to the MS1102. A Short Message Peer to Peer (SMPP) protocol router1113may be provided to convert SMS-based SMPP messages to cell broadcast messages. SMPP is a protocol for exchanging SMS messages between SMS peer entities such as short message service centers. The SMPP protocol is often used to allow third parties, e.g., content suppliers such as news organizations, to submit bulk messages.

To gain access to GSM services, such as voice, data, short message service (SMS), and multimedia message service (MMS), the MS may first register with the network to indicate its current location by performing a location update and IMSI attach procedure. MS1102may send a location update including its current location information to the MSC/VLR, via BTS1104and BSC1106. The location information may then be sent to the MS's HLR. The HLR may be updated with the location information received from the MSC/VLR. The location update may also be performed when the MS moves to a new location area. Typically, the location update may be periodically performed to update the database as location updating events occur.

GPRS network1130may be logically implemented on the GSM core network architecture by introducing two packet-switching network nodes, a serving GPRS support node (SGSN)1132, a cell broadcast and a Gateway GPRS support node (GGSN)1134. The SGSN1132may be at the same hierarchical level as the MSC1108in the GSM network. The SGSN may control the connection between the GPRS network and the MS1102. The SGSN may also keep track of individual MS's locations and security functions and access controls.

Cell Broadcast Center (CBC)1133may communicate cell broadcast messages that are typically delivered to multiple users in a specified area. Cell Broadcast is one-to-many geographically focused service. It enables messages to be communicated to multiple mobile telephone customers who are located within a given part of its network coverage area at the time the message is broadcast.

GGSN1134may provide a gateway between the GPRS network and a public packet network (PDN) or other IP networks1136. That is, the GGSN may provide interworking functionality with external networks, and set up a logical link to the MS through the SGSN. When packet-switched data leaves the GPRS network, it may be transferred to an external TCP-IP network1136, such as an X.25 network or the Internet. In order to access GPRS services, the MS first attaches itself to the GPRS network by performing an attach procedure. The MS then activates a packet data protocol (PDP) context, thus activating a packet communication session between the MS, the SGSN, and the GGSN.

In a GSM/GPRS network, GPRS services and GSM services may be used in parallel. The MS may operate in one three classes: class A, class B, and class C. A class A MS may attach to the network for both GPRS services and GSM services simultaneously. A class A MS may also support simultaneous operation of GPRS services and GSM services. For example, class A mobiles may receive GSM voice/data/SMS calls and GPRS data calls at the same time.

A class B MS may attach to the network for both GPRS services and GSM services simultaneously. However, a class B MS does not support simultaneous operation of the GPRS services and GSM services. That is, a class B MS can only use one of the two services at a given time. A class C MS can attach for only one of the GPRS services and GSM services at a time. Simultaneous attachment and operation of GPRS services and GSM services is not possible with a class C MS.

GPRS network1130may be designed to operate in three network operation modes (NOM1, NOM2and NOM3). A network operation mode of a GPRS network may be indicated by a parameter in system information messages transmitted within a cell. The system information messages may direct an MS where to listen for paging messages and how to signal towards the network. The network operation mode represents the capabilities of the GPRS network. In a NOM1network, a MS may receive pages from a circuit switched domain (voice call) when engaged in a data call. The MS may suspend the data call or take both simultaneously, depending on the ability of the MS. In a NOM2network, a MS may not receive pages from a circuit switched domain when engaged in a data call, since the MS may be receiving data and may not be listening to a paging channel. In a NOM3network, a MS may monitor pages for a circuit switched network while receiving data and vice versa.

The IP multimedia network1138was introduced with 3GPP Release 5, and may include IP multimedia subsystem (IMS)1140to provide rich multimedia services to end users. A representative set of the network entities within IMS1140are a call/session control function (CSCF), a media gateway control function (MGCF)1146, a media gateway (MGW)1148, and a master subscriber database, called a home subscriber server (HSS)1150. HSS1150may be common to GSM core network1101, GPRS network1130as well as IP multimedia network1138. HSS1150may include multiple HSSs.

IP multimedia system1140may be built around the call/session control function, of which there are three types: an interrogating CSCF (I-CSCF)1143, a proxy CSCF (P-CSCF)1142, and a serving CSCF (S-CSCF)1144. The P-CSCF1142is the MS's first point of contact with the IMS1140. The P-CSCF1142may forward session initiation protocol (SIP) messages received from the MS to an SIP server in a home network (and vice versa) of the MS. The P-CSCF1142may also modify an outgoing request according to a set of rules defined by the network operator (for example, address analysis and potential modification).

I-CSCF1143forms an entrance to a home network and hides the inner topology of the home network from other networks and provides flexibility for selecting an S-CSCF. I-CSCF1143may contact subscriber location function (SLF)1145to determine which HSS1150to use for the particular subscriber, if multiple HSSs1150are present. S-CSCF1144may perform the session control services for MS1102. This includes routing originating sessions to external networks and routing terminating sessions to visited networks. S-CSCF1144may also decide whether an application server (AS)1152is required to receive information on an incoming SIP session request to ensure appropriate service handling. This decision may be based on information received from HSS1150(or other sources, such as application server1152). AS1152may also communicate to location server1156(e.g., a Gateway Mobile Location Center (GMLC)) that provides a position (e.g., latitude/longitude coordinates) of MS1102.

HSS1150may contain a subscriber profile and keep track of which core network node is currently handling the subscriber. It may also support subscriber authentication and authorization functions (AAA). In networks with more than one HSS1150, a subscriber location function provides information on the HSS1150that contains the profile of a given subscriber.

MGCF1146may provide interworking functionality between SIP session control signaling from the IMS1140and ISUP/BICC call control signaling from the external GSTN networks (not shown.) It may also control the media gateway (MGW)1148that provides user-plane interworking functionality (e.g., converting between AMR- and PCM-coded voice.) MGW1148may also communicate with other IP multimedia networks1154.

Push to Talk over Cellular (PoC) capable mobile telephones may register with the wireless network when the telephones are in a predefined area (e.g., job site, etc.) When the mobile telephones leave the area, they may register with the network in their new location as being outside the predefined area. This registration, however, does not indicate the actual physical location of the mobile telephones outside the pre-defined area.

FIG. 12illustrates a PLMN block diagram view of an exemplary architecture in which communication service usage transfer may be incorporated. Mobile Station (MS)1301is the physical equipment used by the PLMN subscriber. In one illustrative example, the guest device103or the host device105may serve as Mobile Station1301. Mobile Station1301may be one of, but not limited to, a cellular telephone, a cellular telephone in combination with another electronic device or any other wireless mobile communication device.

Mobile Station1301may communicate wirelessly with Base Station System (BSS)1310. BSS1310contains a Base Station Controller (BSC)1311and a Base Transceiver Station (BTS)1312. BSS1310may include a single BSC1311/BTS1312pair (Base Station) or a system of BSC/BTS pairs which are part of a larger network. BSS1310is responsible for communicating with Mobile Station1301and may support one or more cells. BSS1310is responsible for handling cellular traffic and signaling between Mobile Station1301and Core Network1340. Typically, BSS1310performs functions that include, but are not limited to, digital conversion of speech channels, allocation of channels to mobile devices, paging, and transmission/reception of cellular signals.

Additionally, Mobile Station1301may communicate wirelessly with Radio Network System (RNS)1320. RNS1320contains a Radio Network Controller (RNC)1321and one or more Node(s) B1322. RNS1320may support one or more cells. RNS1320may also include one or more RNC1321/Node B1322pairs or alternatively a single RNC1321may manage multiple Nodes B1322. RNS1320is responsible for communicating with Mobile Station1301in its geographically defined area. RNC1321is responsible for controlling the Node(s) B1322that are connected to it and is a control element in a UMTS radio access network. RNC1321performs functions such as, but not limited to, load control, packet scheduling, handover control, security functions, as well as controlling Mobile Station1301's access to the Core Network (CN)1340.

The evolved UMTS Terrestrial Radio Access Network (E-UTRAN)1330is a radio access network that provides wireless data communications for Mobile Station1301and User Equipment1302. E-UTRAN1330provides higher data rates than traditional UMTS. It is part of the Long Term Evolution (LTE) upgrade for mobile networks and later releases meet the requirements of the International Mobile Telecommunications (IMT) Advanced and are commonly known as a 4G networks. E-UTRAN1330may include of series of logical network components such as E-UTRAN Node B (eNB)1331and E-UTRAN Node B (eNB)1332. E-UTRAN1330may contain one or more eNBs. User Equipment1302may be any user device capable of connecting to E-UTRAN1330including, but not limited to, a personal computer, laptop, mobile device, wireless router, or other device capable of wireless connectivity to E-UTRAN1330. The improved performance of the E-UTRAN1330relative to a typical UMTS network allows for increased bandwidth, spectral efficiency, and functionality including, but not limited to, voice, high-speed applications, large data transfer and IPTV, while still allowing for full mobility.

An exemplary mobile data and communication service that may be implemented in the PLMN architecture described inFIG. 12is the Enhanced Data rates for GSM Evolution (EDGE). EDGE is an enhancement for GPRS networks that implements an improved signal modulation scheme known as 9-P SK (Phase Shift Keying). By increasing network utilization, EDGE may achieve up to three times faster data rates as compared to a typical GPRS network. EDGE may be implemented on any GSM network capable of hosting a GPRS network, making it an ideal upgrade over GPRS since it may provide increased functionality of existing network resources. Evolved EDGE networks are becoming standardized in later releases of the radio telecommunication standards, which provide for even greater efficiency and peak data rates of up to 1 Mbit/s, while still allowing implementation on existing GPRS-capable network infrastructure.

Typically Mobile Station1301may communicate with any or all of BSS1310, RNS1320, or E-UTRAN1330. In an illustrative system, each of BSS1310, RNS1320, and E-UTRAN1330may provide Mobile Station1301with access to Core Network1340. The Core Network1340may include of a series of devices that route data and communications between end users. Core Network1340may provide network service functions to users in the Circuit Switched (CS) domain, the Packet Switched (PS) domain or both. The CS domain refers to connections in which dedicated network resources are allocated at the time of connection establishment and then released when the connection is terminated. The PS domain refers to communications and data transfers that make use of autonomous groupings of bits called packets. Each packet may be routed, manipulated, processed or handled independently of all other packets in the PS domain and does not require dedicated network resources.

The Circuit Switched—Media Gateway Function (CS-MGW)1341is part of Core Network1340, and interacts with Visitor Location Register (VLR) and Mobile-Services Switching Center (MSC) Server1360and Gateway MSC Server1361in order to facilitate Core Network1340resource control in the CS domain. Functions of CS-MGW1341include, but are not limited to, media conversion, bearer control, payload processing and other mobile network processing such as handover or anchoring. CS-MGW1340may receive connections to Mobile Station1301through BSS1310, RNS1320or both.

Serving GPRS Support Node (SGSN)1342stores subscriber data regarding Mobile Station1301in order to facilitate network functionality. SGSN1342may store subscription information such as, but not limited to, the International Mobile Subscriber Identity (IMSI), temporary identities, or Packet Data Protocol (PDP) addresses. SGSN1342may also store location information such as, but not limited to, the Gateway GPRS Support Node (GGSN)1344address for each GGSN where an active PDP exists. GGSN1344may implement a location register function to store subscriber data it receives from SGSN1342such as subscription or location information.

Serving Gateway (S-GW)1343is an interface which provides connectivity between E-UTRAN1330and Core Network1340. Functions of S-GW1343include, but are not limited to, packet routing, packet forwarding, transport level packet processing, event reporting to Policy and Charging Rules Function (PCRF)1350, and mobility anchoring for inter-network mobility. PCRF1350uses information gathered from S-GW1343, as well as other sources, to make applicable policy and charging decisions related to data flows, network resources and other network administration functions. Packet Data Network Gateway (PDN-GW)1345may provide user-to-services connectivity functionality including, but not limited to, network-wide mobility anchoring, bearer session anchoring and control, and IP address allocation for PS domain connections.

Home Subscriber Server (HSS)1363is a database for user information, and stores subscription data regarding Mobile Station1301or User Equipment1302for handling calls or data sessions. Networks may contain one HSS1363or more if additional resources are required. Exemplary data stored by HSS1363include, but is not limited to, user identification, numbering and addressing information, security information, or location information. HSS1363may also provide call or session establishment procedures in both the PS and CS domains.

The VLR/MSC Server1360provides user location functionality. When Mobile Station1301enters a new network location, it begins a registration procedure. A MSC Server for that location transfers the location information to the VLR for the area. A VLR and MSC Server may be located in the same computing environment, as is shown by VLR/MSC Server1360, or alternatively may be located in separate computing environments. A VLR may contain, but is not limited to, user information such as the IMSI, the Temporary Mobile Station Identity (TMSI), the Local Mobile Station Identity (LMSI), the last known location of the mobile station, or the SGSN where the mobile station was previously registered. The MSC server may contain information such as, but not limited to, procedures for Mobile Station1301registration or procedures for handover of Mobile Station1301to a different section of the Core Network1340. GMSC Server1361may serve as a connection to alternate GMSC Servers for other mobile stations in larger networks.

Equipment Identity Register (EIR)1362is a logical element which may store the International Mobile Equipment Identities (IMEI) for Mobile Station1301. In a typical example, user equipment may be classified as either “white listed” or “black listed” depending on its status in the network. In one example, if Mobile Station1301is stolen and put to use by an unauthorized user, it may be registered as “black listed” in EIR1362, preventing its use on the network. Mobility Management Entity (MME)1364is a control node which may track Mobile Station1301or User Equipment1302if the devices are idle. Additional functionality may include the ability of MME1364to contact an idle Mobile Station1301or User Equipment1302if retransmission of a previous session is required.

While communication service usage transfer has been described in connection with the various examples of the various figures, it is to be understood that other similar examples may be used or modifications and additions may be made to the described examples for performing the same function of communication service usage transfer without deviating therefrom. For example, one skilled in the art will recognize that communication service usage transfer as described in the present application may apply to any environment, whether wired or wireless, and may be applied to any number of such devices connected via a communications network and interacting across the network. Therefore, communication service usage transfer should not be limited to any single example, but rather should be construed in breadth and scope in accordance with the appended claims.