WO2011121445A1

WO2011121445A1 - Mobile virtual network operator system and method of operation thereof

Info

Publication number: WO2011121445A1
Application number: PCT/IB2011/000932
Authority: WO
Inventors: Satya Mallya; John Benko; Subash Mandanapu
Original assignee: France Telecom
Priority date: 2010-03-30
Filing date: 2011-03-30
Publication date: 2011-10-06

Abstract

A method of obtaining content over a network, the method comprising acts of obtaining information related to an identity module of a mobile station (MS), the information related to the identity module comprising one or more of subscriber identity module (9M) information, device key (DK) information, and service key (SK) information; determining whether the information related to the identity module comprises one or more of the DK information, and SK information; determining whether one or more of the DK information and the SK information are valid; and transmitting a service request, when it is determined that one or more of the DK information and the SK information are valid.

Description

M OBI LE VI RTUAL NETWORK OFERATOR SYSTEM AND METHOD OF OPERATION THE EROF

FIELD OF THE PRESENT SYSTEM :

The present system relates to at least one of a system, method, device, computer program, user interface, and apparatus for providing services to mobile stations (MSs) and, more particularly, to a system for providing mobile virtual network operator (MVNO) servicesto one or more MSs.

BACKGROUND OF THE PRESET SYSTE :

Typically, to consume mobile data services such as, mobile browsing, email, video or multimedia data services, etc., users of mobile devices must have a mobile data plan service subscription with a mobile network operator (MNO) who operates the physical network that providesthe mobile services or provides access to the mobile services. In these systems, a user is required to establish mobile data plan service subscription with the MNO which may inconvenience the user and may limit the type of services available to those listed in the service subscription. Thus, user'sof voice only data plans are not able to consume content such as multimedia content using their MNO's network.

Recently, services known as mobile virtual network operator (MVNO) services have become commonplace. MVNO services do not typically require users or subscribers to the MVNO services to establish service plan subscriptions with MNOs in order to obtain the MVNO services. Rather, the MVNO service providers establish accessto physical networks provided by MNOs for consumption of the MVNO services. Accordingly, mobile network cost arrangements are contractually arranged between MVNO service providers and MNOs in a manner which istransparent to userswho consume the MVNO services. Although conventional MVNOs are convenient, they are difficult to establish and may be cost prohibitive to product companies which desire to offer mobile broadband as part of a service.

Accordingly, there is a need for a system and method to provide MVNO servicesto mobile devicesand variousapplications on these devices. The present system addressessuch problems by providing a system which has not been previously proposed.

SUM MARYOFTHE PRESENT SYSTEM :

It is an object of the present system to overcome disadvantages and/or make improvements in the prior art. Accordingly, the system, device(s), method, user interface, etc., described herein address problems in prior art systems. In accordance with embodiments of the present system, a system, method, device, computer program, and interface (hereinafter each of which will be referred to as system for the sake of clarity) for obtaining content over a network. T e method may include acts of obtaining information related to an identity module of a mobile station (MS), the information related to the identity module comprising one or more of subscriber identity module (9M) information, device key (DK) information, and service key (SK) information; determining whether the information related to the identity module comprises one or more of the DK information, and SK information; determining whether one or more of the DK information and the SKinformation are valid; and delivering a service request for a service in accordance with one or more of the DK information and the SKinformation when it is determined that one or more of the DKinformation and the SKinformation are valid. In accordance with embodiments of the present system, it may be determined whether user identification (UID) information is required. Adevice service user ID (DSUID) information may be formed when it is determined that user identification (UID) information is required. The method may include associating the DSUID information with the content, and transmitting the DSUID information with the content .A cost based may be determined in accordance with a device service user ID (DSUID) or (SD9D) information associated with the content. A service request may be transmitted with a DSpair, when it isdetermined that one or more of the SKinformation and the DK information are valid. The act of determining whether one or more of the DK information and the SKinformation are valid, may be performed when it is determined that the information related to the identity module includes one or more of the DK information, and SK information. In addition, a service may be configured in accordance with the delivered service request.

BREEFDEH IPTION OFTHEDFAWINGS

The present system is explained in further detail, and by way of example, with reference to the accompanying drawings wherein:

FIG 1 shows a block diagram of a system in accordance with embodiments of the present system;

FIG 2 shows a block diagram of a system in accordance with embodiments of the present system;

FIG 3 is flow diagram that illustrates a process in accordance with embodiments of the present system;

FIG 4 shows a flow diagram in accordance with embodimentsof the present system; and FIG 5 shows a portion of a system (e.g., peer, server, etc.) in accordance with embodiments of the present system.

DETAIUED DESIHI^O^

The following are descriptions of illustrative embodiments that when taken in conjunction with the following drawings will demonstrate the above noted features and advantages, as well as further ones. In the following description, for purposes of explanation rather than limitation, illustrative details are set forth such as architecture, interfaces, techniques, element attributes, etc. However, it will be apparent to those of ordinary skill in the art that other embodiments that depart from these details would still be understood to be within the scope of the appended claims. Moreover, for the purpose of clarity, detailed descriptions of well known devices, circuits, tools, techniques and methods are omitted so as not to obscure the description of the present system. It should be expressly understood that the drawings are included for illustrative purposes and do not represent the scope of the present system. In the accompanying drawings, like reference numbers in different drawings may designate similar elements.

For purposesof simplifying a description of the present system, the terms "operatively coupled", "coupled" and formatives thereof as utilized herein refer to a connection between devices and/or portions thereof that enables operation in accordance with the present system. For example, an operative coupling may include one or more of a wired connection and/or a wireless connection between two or more devices that enables a one and/or two-way communication path between the devices and/or portionsthereof.

The term rendering and formatives thereof as utilized herein refer to providing content, such as digital media which may include, for example, audio visual content, applications (games, etc.), movies, songs, e-books, notifications, etc., such that it may be perceived by at least one user sense, such as a sense of sight and/or a sense of hearing. In some embodiments, the content may be interacted with by a user. For example, the present system may render a user interface on a display device so that it may be seen and interacted with by a user. Further, the present system may render audio visual content on both of a device that renders audible output (e.g., a speaker, such as a loudspeaker) and a device that renders visual output (e.g., a display). To simplify the following discussion, the term content and formatives thereof will be utilized and should be understood to include audio content, visual content, audio visual content, textual content and/or other content types, unless a particular content type is specifically intended, as may be readily appreciated.

The user interaction with and manipulation of the computer environment may be achieved using any of a variety of types of human-processor interface devices that are operationally coupled to a processor or processors controlling the rendered environment. A common interface device for a user interface (Ul), such as a graphical user interface (QUI) is a mouse, trackball, keyboard, touch-sensitive display, a pointing device (e.g., a pen), etc. An example of such a GUI in accordance with embodiments of the present system is a GUI that may be provided by a special purpose processor programmed by computer program to enable a user to interact with the mobile device.

FIG 1 shows a block diagram of a system 100 in accordance with embodiments of the present system. The system 100 may include one or more of a service provider 102, a network operator 104, mobile stations (MSs) 106-1 through 106-N (generally 106-x), and a network 108.

The service provider 102 may include one or more servers which may provide one or more services via the network 108 to the mobile stations 106. Accordingly, the service provider may include a services portion 114 to provide the one or more services. The service provider 102 may include one or more memories which may hold information related to the one or more services and may be located at one or more locations which may be local or remote from each other. Accordingly, the one or more memories may include any suitable memory. The one or more services may include, for example, content 120 such as songs, movies, games, news, etc. (e.g., ITUNES™ etc.), social networking services (e.g., FACEBOOK™ etc.), location or map services (e.g., GOOGLE MAPS™), health services (e.g., ACCUHEALTH™ etc.), electronic books (e.g., e-books, AMAZON KINDLE™ iPad™ etc.), browsing services (e.g., GOOGLE CHROMF" etc.), mail services (e.g., email, webmail, etc.), applications, and/or other services or content which may be accessed via network 108. To simplify the discussion, the terms service and content may be utilized herein to indicate data that is provided to a user that is perceived and in some embodiments, that may be interacted with by the user. The service provider 102 may include one or more servers which may be located locally or remotely from each other and may be coupled to the network 108 using a suitable wired or wireless connection. Thus, the service provider 102 may include an online service provider, an application store, a device vendor, a device store, etc. The service provider 102 may include a billing application 118 to provide cost services for each MS 106-x. Further, the service provider 102 may include an authentication application 118 to authorize access to the services provided by the service provider 102. The network operator 104 may include one or more servers which may, at least in part, provide, control, and/or operate one or more wired and/or wireless mobile networks which may form one or more parts of the network 108. One or more of the MSs 106-x may communicate with the network 108 to exchange information using a suitable communication technology (e.g., WiR, GSM, etc.). The network operator 104 may include one or more of an authentication authorization, and accounting (AAA) proxy 110 and a billing application 112. The AAA proxy 110 may authenticate and authorize MSs 106-x to access the network 108 and/or to receive services such as content provided by the service provider 102. The AAA proxy 110 may also perform accounting functions to account for costs incurred by the MSs 106- x when they access the system 100 and/or receive content. Further, the billing application 112 may receive information from the AAA proxy 110 and may provide billing services for access to the network 108 and/or service provider 102.

Each MS 106-x may include a processor, a reception/transmission (RX TX) portion (discussed further herein below), a user interface (e.g., one or more of a speaker, a display, keys, user input/output device, etc.) and an identification module 122. The MSs 106-x may include for example, one or more wireless devices such as, for example, personal digital assistants (PDAs), cellular telephones, iPHO F^ type devices, ELACKBERRY™type devices, laptop computers, notebook computers, net book computers, dumb terminals, pad-type computers (e.g., iPAD™J, cameras, electronic book readers (e.g., AMAZON KINDLE™), MPEG-1 Audio Layer 3 (MP3) players, health monitors, and/or other electronic devices with a wired and/or wireless communication function which may communicate with the network 108. The MSs 106-x may include functionality to read an identity (ID) module 122 such as, for example, a Subscriber Identity Module (9M), an Elastic 9M (E-9M) or other identity module to obtain authentication information. The description contained herein is intended to cover any type of identity module that operates in accordance with the present system although illustrative identity modules are discussed herein to facilitate a discussion of the present system. However, it should be expressly understood that these illustrative descriptions are not intended to limit the scope of the present system as represented by the claims that follow. The authentication information may be used to form, for example, a device service user ID (DSUID) as will be discussed below. The authentication information may be based upon information obtained from identity module 122 such as, for example, the 9M/IM9 (international mobile subscriber identity), device key (DK), service key (SK), and service user ID (SUID)). In particular, the present system defines the DKand the SK which may be included in an authentication tuple (DSUID) with DSUID= function f(9M, DK, SK SUID). For example, the DSUID is an authentication that may have a number of different parts, such as 4 part salt hough in some embodimantsof the present system, some of these parts may be "null" or blank parts. To give an example in a case wherein a game console manufacturer wants to provide consumers who by a mobile gaming device with 3G, that heretofore is technologically infeasible, including 3G connectivity with certain games such as internet connected games. In this example, in accordance with the present system, the following parts may be provided:

1) SM : An operator that supportsthis E-9M model will provide a 9M card to the game console manufacturer.

2) DK The device key will be provided (by the system - or operator in our case) specifically to identify this particular game console model. In accordance with embodiments of the present system, using the identity of the console model, services may be billed differently based on the device that isconsuming the services.

3) S May be used in accordance with present systemsto identify the service provider, such as in this case, the online game service (e.g., Electronic Arts™). In accordance with embodiments of the present system, the SK may be utilized toto identify a particular game (service) from Electronic Arts™.

4) 9UID: In accordance with present systems is used to identify a user, such as to identify the user in the game, in the online service, etc. In accordance with embodiments of the present system, the SUID may be a username/ password that is associated to the user, such as associated with the users subscription with a gaming provider such as Electronic Arts™. In accordance with embodiments of the present system, such as in a case wherein the service is email, the SUID may be an email address (e.g.,. xx@yahoo.com, and password).

Accordingly, the authentication information which is based upon information included in the identity module 122 may include the authentication tuple and may thus, include information related to one or more of a user 9M, a Device fey (DK), a Service fey (SK), and a Service User ID (SUID)) as will be described below. After obtaining the authentication information, the MSs 106 may transmit information corresponding to authentication information to one or more of the network operator 104 to obtain access to the network 108 and/or to the service provider 102 (either directly or indirectly) to gain access to one or more services offered by the service provider 102. The processor may include one or more processors (e.g., a microcontroller) which, when suitably programmed to become a special purpose processor, may control the overall operation of a corresponding MS 106-x.

The F&/Tx portion may include one or more of a transmitter and a receiver which may, for example, transit and/or receive information to, or from, the MS 106-x using a suitable wired and/ or wireless communication method such as, for example, Global System for Mobile Cbmmunications(GSM), etc., to couple the MS 106-x to the service provider 102 and the network operator 104 through the network 108.

The user interface (IE) 124 may include, for example, a display (e.g., a touch sensitive display), a speaker, one or more keys, a pointing device, etc., with which a user may utilize to interact with the corresponding MS 106-x.

Accordingly, the present system may provide for the consumption of services provided via mobile networks such as, for example, broadband mobile networks, without subscribing to a mobile data plan on an MS Thus, MSs such as, for example, non phone based consumer electronics (e.g., a camera as opposed to a camera phone) which are not typically serviced by mobile network operators or providers may access a mobile network to transmit and/or receive data (e.g., image information, etc.). Further, when consuming various services, the present system may determine costs and perform corresponding billing functions.

The network 108 may include any suitable network or networks such as, for example, a wired and/or wireless network. Accordingly, the network 108 may include one or more of a cellular network, a telephony network, a wireless network, a local area network (LAN), a broadband network, a wireless broadband network, a wide area network (WAN), the Internet, an intranet, etc. which may be operably coupled with (e.g., to enable communication) one or more of the MSs 106-x, the network operator 104, and/or the service provider 102, using, for example, wired and/or wireless communication techniques. Accordingly, one or more of the MSs 106-x may communicate to one or more of the service provider 102 and the network operator 104 via the network 108. Further, one or more of the MSs 106-x may communicate with another of the MSs 106-x and or other devices via the network. The network may also include, for example, one or more access points which may communicate with one or more of the MS31060-X.

With respect to each of the MSs 106-x, each MS 106-x may include a structure to read and/ or write to the ID module (e.g., SM, E-9M, etc.) of each corresponding MS 106-x and obtain information for forming the authentication information. A format of the authentication information may be known as (DSUID or) E-SMAuthentication and may be defined as:

wherein the UserSM corresponds with conventional 9M information; the Device hfey (DK) includes information which may identify the device (e.g., the MS106-x; the Service hfey (SK) may include information related to a service which the MS 106-x may obtain as described herein; and the Service User ID (SUID) includes information associated with the user asdescribed herein.

FIG 2 shows a block diagram of a system 200 in accordance with embodiments of the present system. T e system 200 may include one or more of a mobile station (MS) 206, an access point 208, a gateway 210, a billing gateway 212, a service portion 214, and adevice store portion 216.

The MS 206 may be similar to one or more of the MSs 106-x and may run one or more applications such as, for example, an application 218 and a device service application 220 to suitably program a processor as may be readily appreciated. The MS206 may include authorization information which may be used by the gateway 210 to perform authentication, authorization, and accounting (AAA) functions as will be described below. Accordingly, the authentication information may be based upon information read from a 9M or E-9M coupled to the MS 206. The MS 206 may transmit the authentication information to gateway 210 via the QGSN Node 208 for AAA processing. The 9M or E- 9M may be a prepaid, concurrent paid or post paid-type 9M. Additionally, the MS206 may include one or more of a 9M and/or an E-9M which may be selected by the MS206 for use.

The application 218 may include a service application which may, for example, provide a multimedia function (e.g., play content such as, for example audio and/or video content such as, for example, movies), an email or simple mail service (SMS) function, an image capture function (e.g., a camera function), an e-book function, a health monitoring function, a computer application (e.g., MSWORD™ etc., as desired. Accordingly, in the present example, the application 218 may suitably program a processor to render content such as, for example, movies provided from a network service such as the service 214 (e.g., HULU™ etc.) on a GUI of the MS206.

The device store application 220 may include a device service provided from a device store such as, for example, device store 216. For example, in accordance with embodiments of the present system, the device store 216 may be an application marketplace where the user may search, browse and see all applications offered and stored on a server, such asa server accessible through usof the internet and/or other coupling device. In accordance with embodiments of the present system, the device store owner or operator of the application marketplace, may be considered as an application/service provider that would require an SK to allow operation of an application offered by the device store 216 including an ability to enable marketplace data to pass thru the network. In accordance with embodiments of the present system, a method, device, object, service provides an ability to access, download and purchase services, applications, etc.

The access point 208 may include any suitable access point which may provide the MS206 with wired and/or wireless communication access (an operable coupling) to a network. Accordingly, in the present example, the access point 208 may include a gateway GPRS support node (QG3M)/Node 208 which may provide wired and/or wireless communication access to the MS206 such that the MS206 may transmit data to/from one or more of the gateway 210, billing gateway 212, service portion 214, and device store 216 using any suitable communication protocol (e.g., a mobile IPprotocol, etc.).

The gateway 210 may include, for example, an E-9M AAA proxy which may provide authentication, authorization, and accounting (AAA) functions to the system 200. Accordingly, the gateway 210 may include an authentication function to determine whether to authenticate MS206, and authenticate the MS206 in the affirmative. The gateway 210 may also provide an authorization function which may determine whether the MS 206 is authorized to perform certain activities such as, for example, logging into one or more of the service portion 214 or device store 216 and to authorize the MS 206 in the affirmative. Further, the gateway 210 may determine what types of services and/ or quality of service (QoS) may be provided to the MS206 (e.g., when it is authorized and authenticated). The types of services, QoS and/or costs may be based upon type of device, time, location, network, service, network congestion, application, billing data, service agreement, etc. and may be set in accordance with cost rules. The gateway 210 may also provide accounting functions by tracking consumption of services and generating corresponding accounting information. The gateway 210 may transmit information related to one or more of the authentication function, the authorization function, and the accounting functions to the billing gateway 212 for various purposes such as, for example, obtaining services (e.g., from the service 214 or device store 216, etc.) billing and/or analysis. Further, the gateway 210 may determine whether the authorization information corresponds with a pre- or postpaid 9M, and perform AAA functionsin accordance with predetermined AAA rules.

The billing gateway 212 may include any suitable billing gateway which may provide accounting services to one or more clients using billing information. Accordingly, the billing gateway 212 may determine and apportion charges between one or more of the servicing network (e.g., a wireless or wired network provider), the service 214, the device store 216, and the MS206 according to cost rules. Further, the billing gateway 212 may receive incentivesto be applied to the MS206 such as, for example, advertising incentives, and apply these incentives towards the MS206 and/or one or more of the service providers.

The service portion 214 may provide a service such as a multi-media service, etc., to the MS206 to be consumed via a communication network. For example, the service portion 214 may include an application which may provide video content to the MS 206 such as a HULU™ television service. According to the present system, the service portion 214 may assume costs for related mobile broadband usage when the MS206 consumes a service from the service portion 214. Accordingly, the device store portion 216 may operate under a cost model which may determine costs for related mobile broadband access by the MS206. There may be one or more cost models base upon recognition of a device. Thus, if adevice (e.g., the MS206) isrecognized as a device which followsafirst cost model (e.g., using an E-9M), services may be advertised and/or set at a first cost. Smilarly, if the deice (e.g., the MS 206) is recognized as a device which follows a different cost model (e.g., a device which obtains its own broadband access), the services may be advertised and/or set at another cost. Accordingly, the service portion 214 may include costs for the related mobile broadband into a cost of an application, service, etc., which isconsumed by the MS206.

The device store portion 214 may provide broadband access to the MS 206 which may use broadband access to obtain services from the device store 216. The broadband access may include wireless and/or wired broadband access and may be included on devices which are offered from a device provider such as, for example, SONY™ Smilarly to the service portion 214, the device store portion 216 may operate under a cost model which may determine costs for related mobile broadband access by the MS206. Accordingly, a user may purchase a device such as, for example, the MS206 (e.g., from a device provider) and obtain broadband access in accordance with embodiments of the present system without having to obtain a wireless subscription plan with a wireless service access provider.

Thus, using an MVNO relationship according to the present system, service providers (e.g., HULU™ etc.) and/or device providers (e.g., SONY™ etc.) may provide wireless broadband access with services and devices, respectively, in a manner which istranslucent to a user. Further, the MVNO system may operate in accordance with a tiered cost system for wholesale sessions (e.g., consumption of services by a plurality of users or MSs) based upon volume and/or congestion patterns (e.g., primetime vs. early morning hours for wireless access) for wireless broadband access for services and devices, respectively, in a manner which is translucent to a user. Accordingly, billing gateways of the present system may determine costs based upon predetermined cost rules.

To establish an MVNO relationship, an operator (e.g., a network operator) may emulate an API subscription approach and may offer/sell and/or manage mobile data MVNO sessions. Accordingly, service providers may register to use mobile broadband by: 1 requesting to register with a mobile operator or an authorized clearing house; 2. receiving on approval of the request, an assigned service id key such as SK (different from service user key (SUK)); 3. setting cost rules; and 4. following the cost rules. The cost rules may be set in accordance with data usage such as data sessions which may be defined by, for example, one or more of block size and time of usage; and specified plans per device id DK In accordance with embodiments of the present system, the Dk operates not as a serial number but rather like an id/key that may be utilized to identify the model number of such a device) such that services consumed on, for example, one type of device (e.g., netbooks) may have a different pricing/billing than on another type of device (e.g., smartphones). The cost rules may be followed by making post- or pre-paid commitments to the mobile operator (or other network operator) in accordance with the cost rules.

Operative steps which may be performed by the gateway 210 and the billing gateway 212 are described below with reference to FIG 3.

FIG 3 isflow diagram that illustratesa process 300 that together with reference to FIG. 4, which shows a flow diagram 400, will be utilized to illustrate the present system. The process 300 may be performed using one or more computers communicating over a network. The process 300 may include one of more of the following acts. Further, one or more of these acts may be combined and/or separated into sub-acts, if desired. In operation, the process may start at act 301 and then proceed to act 303.

During act 303, the process may receive a service request such as to launch a Hulu application, go to the Hulu website, etc., from an MS The service request may also include authorization information which may correspond with an authorization tuple, e.g., (SM, SK D SUID, as described above), and, as such, may include, information base upon the SM such as, for example, an IMS and DK corresponding with a SM of the MS The service request may be generated by an MS and may be generated in response to a request of the MSor the user of the MS For example, the service request may be generated in response to a user of the MSrequesting service via an application such as a browser when visiting a service website such as HULU™or when using an application such as, for example, an MP3 player. Tlie request may be transmitted from the MSto the gateway. After performing act 303, the process may continue to act 305.

During acts 305 and 307, the process may process the authorization information to obtain the SM and corresponding IMS information as is typical of a convention SM. However, in accordance with embodiments of the present system, the authorization information may also include an authorization tuple asdescribed above. The process may then continue to act 309.

During act 309, the process may use the IMS to determine whether SM information corresponds with information obtained from a SM or an E-SM (e.g., wherein the information obtained from an E-SM may include the authorization tuple). Accordingly, if it isdetermined that the information obtained from the SM information correspondswith E-SM information, the process may continue to act 31 1. However, if it isdetermined that the SM information correspondswith information obtained from a SM, the process may continue to act 333.

Alternatively, it is envisioned that the process may use an IMS to determine a type of account used by the MS For example, the IMS may be used to determine whether the MSis a prepaid account (e.g., voice only account corresponding with a SM (i.e., non E-SM)) or a no data plan user (e.g., corresponding with an E-SM). It is also envisioned that the process may determine whether a valid data plan exists. Accordingly, if it is determined that a valid data plan does not exist, the process may continue to act 311. However, if it isdetermined that a valid data plan exists, the process may continue to act 333. In accordance with embodiments of the present system, certain IMSs (identify numbers on SM cards) are associated to the E-SM model. The operator may check the IMS to see if it is "normal" (e.g., pre-paid, post-paid, etc.) or E-SM. In accordance with embodiments of the present system, the operator may define in the AAA center that IMSs from range XXXX-YYYY are E-SM, and should be handled differently than other SMs (which could use the currently implemented pre-paid, post-paid, MVNO systems).

During act 333, the process may use a data subscription model corresponding with a traditional SM and thereafter continue to act 335 where the process ends.

During act 311 , the process may obtain one or more of S< and DK information from the processed authentication information. During act 313, the process may determine whether the S< information is valid. Accordingly, if it is determined that the S< information is valid, the process may continue to act 315. However, if it is determined that the S< information is not valid, the process may continue to act 331. For example, in accordance with embodiments of the present system, a valid SK may be provided in a storage device (e.g., memory device) as a table. In a case wherein an SK is not found in an associated application table, the SK may be determined to be invalid. In accordance with embodiments of the present system, the SK may be present in the table but labeled invalid, in which case, the SKis invalid.

During act 315, the process may determine whether the DKinformation is valid. Accordingly, if it is determined that the DK information is valid, the process may continue to act 317. However, if it is determined that the DK information is not valid, the process may continue to act 331. In accordance with embodimentsof the present system, the validity of the DKmay be determined in variousways. For example, given SKs may allow select DKs, e.g., hulu service, to be accessible only via an identified E-9M model, such as from an identified mobile gaming console, but not another identified gaming console or not from any other gaming console. In accordance with embodiments of the present system, service providers (with the SK utilized as an identifier) may not require a DK, in which case all DKs are valid or a DKisn't required.

With reference to acts313 and 315, the processmaydeterminewhether the service request was generated in accordance with a valid authorization tuple, e.g., an SDSID (9M, SK, DK) tuple. For example, the process may be performed by first checking for a valid SKduring act 313, and based upon the determination of act 313, determining whether the DK corresponds with the particular service requested by the MS Thus, if the process determines that the SD9D tuple is valid, the process may continue to act 317. In accordance with embodiments of the present system, the SD9D may be the service key, device key, 9M ID, which isalso the DSUIDwithout the service user ID (e.g., the SUID may be eg. username/ password for yahooTM mail). In a case wherein a SUID is not required/implemented in the service (e.g., a GPSapplication) the metering may be based on SD9D and not DSUID.

During act 331 , the process may output other data rate information to the MS Accordingly, the MSmay render this information on a display of the MSfor the convenience of the user. The other data rate information may include information which may be used by the MSto inform the user of other data rates such as a credit card (OQ data rate that, for example, corresponding hourly, daily, and weekly, network access rates Accordingly, the process may output information which, when rendered on a display of the M¾ would suggest use of one or more of an hourly, daily, and weekly access rates for the convenience of the user. After completing act 331 , the process may continue to act 335 wherein the process ends. During act 317, the process may send the user request to the requested service (e.g., see, 214) and/or device (e.g., see, store 214) with the DSpair (9<and DK). Thereafter the process may continue to act 319.

During act 319, the process may determine whether a user ID (UID) is required. Accordingly, if it isdetermined that the UID is required, the process may continue to act 321. However, if it isdetermined that the UID is not required, the process may continue to act 337. For example, this act may be implemented on the service provider side. If a UID is implemented by the service provider, the service provider must provide the authenticated user information to the operator/clearinghouse so that the DSUID may be formed.

During act 321 , the process may form a Device Service user ID (DSUID) by, for example, appending (at any location) an authenticated UID to the SDSservicelD (SDSID). After completing act 321 , the process may continue to act 323.

During act 323, the process may provide for access of the MSto the requested service (e.g., see, 214) and/or device (e.g., see, store 214). After completing act 323, the process may continue to act 325. During act 325, the process may transmit the DSUID with or without other MS related traffic. After completing act 325, the process may continue to act 327. During act 327, the process may determine cost (e.g., using an AAA portion) in accordance with the DSUID for the requested service (e.g., see, 214) and/or device (e.g., see, store 214) and corresponding cost rules. After completing act 327, the process may continue to act 329 where the process ends.

During act 337, the process may obtain the SDSID. After completing act 337, the process may continue to act 339. During act 339, the process may provide for access of the MS to the requested service (e.g., see, 214) and/or device (e.g., see, store 214). After completing act 339, the process may continue to act 341. During act 341 , the process may transmit the SD9D with or without traffic. After completing act 341 , the process may continue to act 343. During act 343, the process may determine cost (e.g., using an AAA portion) in accordance with the SDSID for the requested service (e.g., see, 214) and/or device (e.g., see, store 214) and cost rules. After completing act 343, the process may continue to act 329 where the process may end. FIG 5 shows a portion of a system 500 in accordance with embodiments of the present system. For example, a portion of the present system may include a device 590 including a processor 510 operationally coupled to a memory 520, a display 530, a user input device 570 and a network 580. The memory 520 may be any type of device for storing application data as well as other data related to the described operation. The application data and other data are received by the processor 410 for configuring (e.g., programming) the processor 510 to perform operation acts in accordance with the present system. The processor 510 so configured becomes a special purpose machine particularly suited for performing in accordance with the present system.

The operation acts may include requesting, providing, and/or rendering of content. The user input 570 may include a keyboard, mouse, trackball or other device, including touch sensitive displays, which may be stand alone or be a part of a system, such as part of a personal computer, personal digital assistant, mobile phone, set top box, television or other device for communicating with the processor 510 via any operable link. The user input device 570 may be operable for interacting with the processor 510 including enabling interaction within a Ul as described herein. The network 580 may correspond to the network 108 shown in FIG. 1 and provides an operable coupling to the device 590 for operation in accordance with the present system. Qearly the processor 510, the memory 520, display 530 and/or user input device 570 may all or partly be a portion of a computer system or other device such asa client (e.g., M¾ etc.), service provider device (e.g., server, etc.) and/or other server asdescribed herein.

The methods of the present system are particularly suited to be carried out by a computer software program, such program containing modules corresponding to one or more of the individual steps or acts described and/or envisioned by the present system. Such program may of course be embodied in a computer-readable medium, such as an integrated chip, a peripheral device or memory, such asthe memory 520 or other persistent memory coupled to the processor 510.

The program and/or program portions contained in the memory 520 configure the processor 510 to implement the methods, operational acts, and fund ions disclosed herein. The memories may be distributed, for example between the clients and/or servers, or local, and the processor 510, where additional processors may be provided, may also be distributed or may be singular. The memories may be implemented as electrical, magnetic or optical memory, or any combination of these or other types of storage devices. Moreover, the term "memory", "persistent memory", and formatives thereof should be construed broadly enough to encompass any information able to be read from or written to an address in an addressable space accessible by the processor 510. With this definition, information accessible through a network is still within the memory, for instance, because the processor 510 may retrieve the information from the network for operation in accordance with the present system.

The processor 510 is operable for providing control signals and/or performing operations in response to input signals from the user input device 570 as well as in response to other devices of a network and executing instructions stored in the memory 520. The processor 510 may be an application-specific or general-use integrated circuit(s). Further, the processor 510 may be a dedicated processor for performing in accordance with the present system or may be a general-purpose processor wherein only one of many functions operates for performing in accordance with the present system. The processor 510 may operate utilizing a program portion, multiple program segments, or may be a hardware device utilizing a dedicated or multi-purpose integrated circuit.

Further variations of the present system would readily occur to a person of ordinary skill in the art and are encompassed by the following claims.

Finally, the above-discussion is intended to be merely illustrative of the present system and should not be construed as limiting the appended claims to any particular embodiment or group of embodiments. Thus, while the present system has been described with reference to exemplary embodiments, it should also be appreciated that numerous modifications and alternative embodiments may be devised by those having ordinary skill in the art without departing from the broader and intended spirit and scope of the present system as set forth in the claims that follow. In addition, the section headings included herein are intended to facilitate a review but are not intended to limit the scope of the present system. Accordingly, the specification and drawings are to be regarded in an illustrative manner and are not intended to limit the scope of the appended claims.

In interpreting the appended claims, it should be understood that:

a) the word "comprising" does not exclude the presence of other elements or acts than those listed in a given claim;

b) the word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements;

c) any reference signs in the claimsdo not limit their scope;

d) several "means" may be represented by the same item or hardware or software implemented structure or function; e) any of the disclosed elements may be comprised of hardware portions (e.g., including discrete and integrated electronic circuitry), software portions (e.g., computer programming), and any combination thereof;

f) hardware portions may be comprised of one or both of analog and digital portions; g) any of the disclosed devicesor port ions thereof may be combined together or separated into further portions unless specifically stated otherwise;

h) no specific sequence of acts or steps is intended to be required unless specifically indicated; and

i) the term "plurality of" an element includes two or more of the claimed element, and does not imply any particular range of number of elements; that is, a plurality of elements may be as few as two elements, and may include an immeasurable number of elements.

Claims

Qaims What isclaimed is:

1. A method of obtaining a service over a network, the method comprising actsof :

obtaining information related to an identity module of a mobile station (MS), the information related to the identity module comprising one or more of subscriber identity module (9M) information, device key (DK) information, and service key (SK) information;

determining whether the information related to the identity module comprises one or more of the DKinformation, and SKinformation;

determining whether one or more of the DKinformation and the SKinformation are valid; and delivering a service request for the service in accordance with one or more of the DK information and the SK information when it is determined that one or more of the DK information and the SKinformation are valid.

2. The method of claim 1 , further comprising an act of determining whether user identification (UID) information is required.

3. The method of claim 2, further comprising an act of forming device service user ID (DSUID) information when it is determined that user identification (UID) information isrequired.

4. The method of claim 2, further comprisingactsof:

associating the DSUID information with the content; and

transmitting the DSUID information with the content.

5. The method of claim 1 , further comprising an act of determining cost based in accordance with a device service user ID (DSUID) or (SD9D) information associated with the content.

6. The method of claim 1 , further comprising an act of transmitting a service request with a DSpair, when it isdetermined that one or more of the SKinformation and the DKinformation are valid.

7. The method of claim 1 , wherein the act of determining whether one or more of the DK information and the SK information are valid, is only performed when it is determined that the information related to the identity module comprises one or more of the DKinformation, and SKinformation.

8. The method of claim 1 , comprising an act of configuring a service in accordance with the delivered service request.

9. The method of claim 8, comprising an act of providing networked access to the service in accordance with a service agreement between a distributer of the identity module and a network provider.

10. The program portion of claim 8, comprising an act of providing networked accessto the service in accordance with a service agreement between a provider of the service and a network provider.

11. The program portion of claim 8, comprising actsof:

monitoring network access usage by the service; and

providing an indication of the network access usage to at least one of a distributer of the identity module, a network provider and a provider of the service.

12. A system to obtain a service over a network, the system comprising:

a controller which:

obtains information related to an identity module of a mobile station (MS), the information related to the identity module comprising one or more of subscriber identity module (9M) information, device key (DK) information, and service key (SK) information;

determines whether the information related to the identity module comprises one or more of the DKinformation, and SKinformation;

determines whether one or more of the DKinformation and the SKinformation are valid; and transmits a service request for a service, when it is determined that one or more of the DK information and the SKinformation are valid.

13. The system of claim 12, wherein the controller determines whether user identification (UID) information is required.

14. The system of claim 13, wherein the controller forms device service user ID (D9UID) information when it isdetermined that user identification (UID) information is required.

15. The system of claim 13, wherein the controller:

associates the D9UID information with the content ; and

transmitsthe DSUID information with the content.

16. The system of claim 12, wherein the controller determines cost based in accordance with a device service user ID (DSUID) or (SDSID) information associated with thecontent.

17. The system of claim 12, wherein the controller transmits a service request with a DSpair, when it is determined that one or more of the SKinformation and the DKinformation are valid.

18. The system of claim 12, wherein the controller determines whether one or more of the DK information and the SK information are valid, is only when it isdetermined that the information related to the identity module comprises one or more of the DKinformation, and SKinformation.

19. A computer program stored on a persistent computer readable memory medium, the computer program configured to provide a service to a mobile station (MS), the computer program comprising: a program portion configured to:

obtain information related to an identity module of the MS, the information related to the identity module comprising one or more of subscriber identity module (SM) information, device key (DK) information, and service key (SK) information;

determine whether the information related to the identity module comprises one or more of the DKinformation, and SKinformation;

determine whether one or more of the DKinformation and the SKinformation are valid; and transmit a service request for the service, when it is determined that one or more of the DKinformation and the SKinformation are valid.

20. The program portion of claim 19, wherein the program portion is configured to determine whether user identification (UID) information is required.

21. The program portion of claim 20, wherein the program portion is configured to form device service user ID (DSUID) information when it isdetermined that user identification (UID) information isrequired.

22. The program portion of claim 20, wherein the program portion isconf igured to:

associate the DSUID information with the content; and

transmit the DSUID information with the content.

23. The program portion of claim 19, wherein the program portion determinescost based in accordance with a device service user ID (DSUID) or (SD9D) information associated with the content.

24. The program portion of claim 19, wherein the program portion transmits a service request with a DS pair, when it isdetermined that one or more of the SKinformation and the DKinformation are valid.

25. The program portion of claim 19, wherein the program portion configures a service in accordance with the delivered service request.

26. The program portion of claim 25, wherein the program portion provides networked access to the service in accordance with a service agreement between a distributer of the identity module and a network provider.

27. The program portion of claim 25, wherein the program portion provides networked access to the service in accordance with a service agreement between a provider of the service and a network provider.

28. The program portion of claim 25, wherein the program portion monitors network access usage by the service and provides an indication of the network access usage to at least one of a distributer of the identity module, a network provider and a provider of the service.