US20050197098A1 - Method and apparatus to provide charging for ad-hoc service provisioning between trusted parties and between untrusted parties - Google Patents
Method and apparatus to provide charging for ad-hoc service provisioning between trusted parties and between untrusted parties Download PDFInfo
- Publication number
- US20050197098A1 US20050197098A1 US10/792,181 US79218104A US2005197098A1 US 20050197098 A1 US20050197098 A1 US 20050197098A1 US 79218104 A US79218104 A US 79218104A US 2005197098 A1 US2005197098 A1 US 2005197098A1
- Authority
- US
- United States
- Prior art keywords
- wireless network
- service
- user device
- service provider
- bridging
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1403—Architecture for metering, charging or billing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/24—Accounting or billing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/02—Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/40—Security arrangements using identity modules
- H04W12/43—Security arrangements using identity modules using shared identity modules, e.g. SIM sharing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/02—Terminal devices
- H04W88/04—Terminal devices adapted for relaying to or from another terminal or user
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/02—Terminal devices
- H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
Definitions
- This invention relates generally to data communications conducted over data communications networks and, more specifically, relates to techniques for charging for services that are provided in an ad-hoc fashion between possibly untrusted parties.
- FIG. 1 illustrates a conventional gaming scenario where a group of users, physically located in a room, play a multi-player game using terminals 1 A via a local access technology such as a wireless BluetoothTM network 2 .
- the terminals 1 A may be mobile terminals, such as cellular telephones or gaming devices per se, and their users are referred to herein for convenience also as originating users.
- another, remotely located player having a terminal 1 B also referred to herein for convenience as a correspondent user, may wish to participate in the game through another access technology, such as a cellular link made through a cellular network 3 , via one of terminals 1 A′ of the local game participants.
- the game participant associated with terminal 1 A′ also referred to herein for convenience as a bridging user, is providing the use of his or her cellular link 3 for a common purpose, i.e., the connection to the game server or a point-to-point connection to the remote participant 1 B.
- the mobile terminal 1 A′ functions as a bridge or router between the Bluetooth local network 2 and the cellular network 3 .
- the usage of the cellular link 3 results in charging the cellular account of the bridging user, while the other game participants (the originating users) are not charged for the usage of the cellular link 3 , even though they are also using the link 3 .
- the terminals 1 A may all be sending data packets through the bridging terminal 1 A′, via the Bluetooth access network 2 , to the remote participant 1 B, or when contacting a remote game server (not shown) through the Internet.
- a remote game server not shown
- the user's laptop may connect via the Bluetooth interface to the mobile terminal of some nearby user, such as by using conventional Bluetooth service discovery procedures in order to connect to an appropriate mobile terminal.
- the nearby user's mobile terminal's cellular connectivity is then used, possibly unbeknownst to the nearby user, to route the laptop's packets appropriately to the Internet (assuming that an IP profile for Bluetooth is present).
- this user's cellular account would be charged for the services that are actually consumed by the laptop user, who may be unknown to the bridging mobile station user.
- a first mobile station is caused to function, perhaps unwittingly, as a service provider for a second mobile station whose user may be totally unknown to the user of the first mobile station. This situation may be referred to generally as ad-hoc service provisioning.
- One result of providing ad-hoc service provisioning is that there may be a desire of the bridging mobile station user to also charge for the consumption of the mobile station's resources, in addition for the cellular connectivity costs.
- This invention both addresses and solves the foregoing problems by the use of a method and a system that enables charging for ad-hoc service provisioning, between trusted parties and also between untrusted parties.
- the bridging user can be associated with any mobile station, or mobile terminal, or computer, collectively referred to for convenience as a wireless device, that has bridging and charging capability in an ad hoc environment. While it is assumed that the originating user has a trusted relationship with a service provider, such as an Internet Service Provider (ISP), a trusted relationship between the originating user and the bridging user is not required.
- ISP Internet Service Provider
- the bridging user may be any person equipped with a wireless device that engages in ad-hoc networking.
- the service provider such as an ISP
- the service provider provides trusted and protected code that runs on the bridging user's wireless device, and the originating user is responsible for negotiating and communicating the negotiation result to the ISP, as well as for metering and logging the usage of the resource(s), such as the cellular link, by the originating user.
- the originating user's logged usage on the bridging user's wireless device is communicated as accounting information to the ISP in an authenticated manner, i.e., without the possibility of a rogue bridging user altering or spoofing the provided accounting information.
- the service provider such as the ISP, bills the originating user for his usage based on the received accounting information, and may pay or credit the bridging user a commission fee for acting as agent of the ISP.
- a method and a system of this invention provide a service for a user device with a service provider.
- the method includes establishing a service provisioning relationship between the user device, also referred to as an originating user device, and a bridging user device through a first wireless network (e.g., a Bluetooth network); providing a desired service for the user device with the service provider via the bridging user device and the first wireless network, and through a second wireless network (e.g., a cellular network) that couples the bridging user device to the service provider; while providing the service, recording charging data for the service provisioning relationship between the user device and the bridging user device; and reporting the charging data from the bridging user device to the service provider.
- at least the establishing and recording functions use service provider trusted software running on the user device and on the bridging user device.
- Embodiments of mobile devices and mobile terminal, such as cellular telephones, that are suitably constructed and operated for realizing the originating user device and the bridging user device are also described.
- FIG. 1 is a simplified block diagram of a conventional usage scenario, specifically one involving local game participants and at least one remote game participant;
- FIG. 2 is a block diagram that illustrates an embodiment of a system architecture in accordance with this invention.
- FIG. 3 is a signal flow diagram in accordance with the system architecture embodiment shown in FIG. 2 .
- each user is assumed to be associated with a wireless device 10 , 12 .
- the wireless devices could be, as non-limiting examples: a mobile station or a mobile terminal, such as a cellular telephone, a personal communicator, or a gaming device; an Internet appliance; or a desktop or a portable computer.
- the users will be mobile users, although this is not a restriction on the practice of this invention.
- the wireless device has a first wireless interface to a local, typically restricted range communications network or access technology 2 , such as WLAN or a Bluetooth network (shown as Access Technology A).
- a local, typically restricted range communications network or access technology 2 such as WLAN or a Bluetooth network (shown as Access Technology A).
- WLAN Wireless Local Area Network
- a Bluetooth network shown as Access Technology A
- a typical operating range between devices for a Bluetooth network is about 10 meters.
- the wireless device 12 associated with the bridging user has a second wireless interface 3 (shown as Access Technology B), such as a cellular interface that could be, as non-limiting examples only, a cdma2000 interface or a GSM/UMTS interface, or any suitable interface enabling the wireless device 12 of the bridging user to contact and establish a connection with a service provider 16 and/or with a remote user, the correspondent user or node 14 , that may be associated with another wireless device.
- Typical ranges for cellular links are kilometers and tens of kilometers.
- the cellular network operator will typically provide access to global data communications networks, such as the Internet.
- the service provider 16 may be the cellular network operator, or it may be an ISP.
- the correspondent node 14 is considered to be the endpoint of the communication with the originating user 10 via the bridging user 12 .
- the correspondent node 14 can be any node in the Internet, or a peripheral, or another mobile device, depending on the Access Technology B and the application scenario in which the invention is used. Note that the Access Technologies A and B do not necessarily have to be different for certain services. Further, certain service usage scenarios do not require the correspondent node 14 , such as a service that uses transcoding services at the bridging user 12 .
- a third party is used to establish a trusted relationship between possibly unknown users.
- the third party which in many cases will be the service provider 16 , provides a certified unit of code (TS o 11 A) for the originating user 10 , as well as for the bridging user 12 (TS B 11 B).
- the provided third party code monitors and accounts for particular service usage based on at least one predetermined usage metric.
- suitable usage metrics include bytes, packets and transaction counts.
- the third party code monitors the service usage, such as IP forwarding, according to the agreed upon usage metrics.
- the bridging user 12 may request that the current metric instance to be sent by the third party code for payment at any time during the transactions, preferably though at the end of the transactions.
- the invention also provides a method to agree upon the charging with third party that is used for billing the originating user 10 .
- the originating user 10 and the bridging user 12 have a subscription with the service provider 16 .
- both mobile devices have installed the unit of code 11 , provided by the service provider 16 , that performs the charging and monitoring functions. These units of code are those depicted as TS o and TS B .
- both users 10 and 12 have a charging relationship with the service provider 16 in the sense that they provide appropriate billing information, such as credit card information, to the service provider 16 .
- the service provider 16 maintains an appropriate set of credential information for either user 10 or 12 in order to perform a negotiation during the establishment of the charged session, as described below.
- This set of credentials typically includes necessary key information as well as mobile device identifiers.
- FIG. 3 shows an example of the signalling that is involved. It should be noted that the communication between the originating user 10 and the bridging user 12 occurs via Access Technology A (e.g., through the Bluetooth network 2 ), while the communication between the bridging user 12 and the service provider 16 occurs via Access Technology B (e.g., through the cdma2000 cellular network).
- Access Technology A e.g., through the Bluetooth network 2
- Access Technology B e.g., through the cdma2000 cellular network
- FIG. 3 it is assumed that the software units for TS o and TS B have been previously installed on the mobile devices 10 and 12 . This can occur by the service provider 16 downloading the software units over-the-air to at least the mobile device 12 , which then transfers TS o in an authenticated manner over the Access Technology A to the mobile device of the originating user 10 , or by any suitable technique.
- TS o of the originating user 10 sends a message (message 1 ) to TS B of the bridging user 12 .
- the addressing of this and other messages between the mobile devices can be realized by any suitable means.
- a presently preferred, but non-limiting addressing technique is one known as “application layer addressing”. This technique can be implemented through, for example, addressing particular IP ports, or by using Uniform Resource Identifier (URI) addressing.
- URI Uniform Resource Identifier
- the service request message sent from TS o includes at least a description of the service that is desired to be used at the bridging user 12 . This service description is sufficient to initiate appropriate monitoring at the bridging user 12 , as discussed below.
- the message 1 of TS o also includes a description of the metric to be used for charging, such as byte or transaction count. Additionally, the message 1 may include cost information related to the originating user 10 , for example, the cost that the originating user 10 would pay for a particular service.
- TS B Upon reception of message 1 at the bridging user 12 , TS B extracts the information and either accepts or rejects the request. For example, the request may be rejected if the requested service is not supported by TS B with respect to an appropriate monitoring technique. If the request is accepted, TS B determines usage costs for the particular requested metric and sends a response (message 2 in FIG. 3 ) back to TS o of the originating user 10 . The determination of the costs may be based upon information in configuration files, stored at the bridging user 12 and configured through the user prior to engaging in the particular session.
- the user may be requested by TS B (e.g., in form of a dialog box) to establish a particular cost metric for the session upon the reception of message, at the bridging user 12 .
- the costs typically, but not necessarily, depend on the actual costs for provisioning the service at the bridging user 12 , e.g., the cost for transfer of bytes within Access Technology B.
- charges may be added for the use of local resources, such as processing and/or battery power.
- information made available in message 1 regarding cost expectations of the originating user 10 may be incorporated in the decision as well.
- the specified costs for provisioning the requested service at the bridging user 12 can be accepted or rejected. This acceptance can be similar to the determination of the costs at the bridging user 12 , e.g., based upon certain pre-configured information, or a dialog box that requests the confirmation of the originating user 10 regarding the cost(s).
- the second instance of message 1 can include revised cost information related to the originating user 10 , for example, a revised cost that the originating user 10 is willing to pay for the requested service.
- the revised proposed cost may be greater than what was indicated in the first instance of message 1 , but less than the cost that the bridging user 12 indicated that he was willing to accept in the first instance of message 2 .
- This mechanism thus implements an offer-counteroffer model of negotiation between the originating user 10 and the bridging user 14 , and can continue automatically or with user input until both the originating user 10 and the bridging user 12 are satisfied.
- TS o of the originating user 10 sends message 3 to TS 3 of the bridging user 12 .
- Message 3 contains the service charge information that was agreed upon in the sequence of message, and message 2 , and preferably also contains appropriate credential information required at the service provider 16 , such as a mobile device or terminal identifier and also possibly an encrypted password.
- the TS B 11 B of the bridging user 12 Upon reception of message 3 in FIG. 3 , the TS B 11 B of the bridging user 12 forwards the information to the service provider 16 as message 4 .
- one of the charging records 16 A is created by the service provider 16 , using the received service charge and the mobile terminal identifier. After creating one of the charging records 16 A, the service provider further generates a locally unique session identifier for this charging record that is used in future communications to uniquely identify the charged session. If used, the encrypted password is employed to authenticate and authorize the service charge to be made.
- the service provider 16 acknowledges (ACKs) the creation of the charged session by sending message 5 to the bridging user 12 .
- the TS B 11 B of the bridging user 12 extracts the enclosed session identifier for future use.
- the system is equipped to begin metering and charging the originating user 10 . More specifically, after the establishment of the charging record information at the service provider 16 , in response to receiving message 4 , the TS B 11 B at the bridging user 12 initiates an appropriate monitoring function to meter the agreed upon service usage. For example, for a service such as “IP routing”, appropriate byte counters may be instantiated that are increased based on monitoring the IP forwarding functionality at the bridging user 12 .
- Suitable monitoring functions include the use of a packet counter, a transaction counter in a browser, and one or more resource consumption recorders such as one that keeps track of the bridging user mobile device data processing cycles devoted to servicing the originating user, or some other data processing metric, and/or primary power (e.g., battery power) consumption recorders.
- resource consumption recorders such as one that keeps track of the bridging user mobile device data processing cycles devoted to servicing the originating user, or some other data processing metric, and/or primary power (e.g., battery power) consumption recorders.
- the TS B 11 B of the bridging user 12 performs the appropriate metering of the service usage, such as counting forwarded IP packets. It should be noted that the specifics of the actual underlying service are not within the scope of the invention.
- the metering information can be sent as message 6 from the TS B 11 B of the bridging user 12 to the service provider 1 .
- the message 6 includes at least the session identifier, as well as the current meter value.
- the service provider 16 stores the metering information accordingly within the appropriate charging record (identified through the session identifier) and acknowledges the reception by sending message 7 back to the TS B 11 B of the bridging user 12 .
- message 6 and message 7 is optional, as only the final meter value need be sent at session termination (message 9 ), as described below.
- the session can be terminated explicitly through the TS o 11 A of the originating user 10 by sending an appropriate session termination message 8 to the TS B 11 B of the bridging user 12 .
- a local decision at the bridging user 12 may be used to terminate the session.
- the TS B 11 B of the bridging user 12 sends a terminate charging message 9 to the service provider 16 .
- the terminate charging message 9 contains at least the current meter value(s), the session identifier, and an indication to terminate the session.
- an appropriate billing record for the originating user 10 is created, based on the available meter information as well as the agreed service charge.
- the operation is then confirmed towards the TS B 11 B of the bridging user 12 by sending message 10 .
- the TS B 11 B of the bridging user 12 tears down the metering and monitoring functions for the terminated session.
- this invention significantly improves on the conventional approaches by providing a generic solution that can be used for a number of different service usage scenarios, such as bridging between access technologies, and does not rely on scenario-specific solutions.
- the inherent lack of trust between possibly unknown mobile users is overcome through the use of certified and trusted metering and monitoring software (TS o and TS B ) that is offered through a common service provider 16 with which both the originating and the bridging users have a subscription.
- TS o and TS B certified and trusted metering and monitoring software
- the use of this invention permits a charging negotiation process to occur through the offer-counteroffer negotiation model during the establishment phase of the charged session (via the message 1 /message 2 interchange).
- the service provider-based solution can be totally independent of a particular wireless network operator, as it does not require extensions to the operator networks, nor does it rely on any specific operator functionality. Therefore, it enables mobile device based services that are charged on the application level rather than on an access network subscription level.
- the trusted software (TS B and TS o ) maybe pre-loaded on and integrated with the software of the mobile devices, thereby providing uniformity and a common trusted charging standard that can be used across various network operators and service providers.
- the trusted software (TS B and TS o ) can be integrated into mobile devices provided by a mobile device manufacturer, for performing the charging and metering functions, while the service provider 16 software functions can be provided by the mobile device manufacturer as well or by or through a third party.
- this invention further minimizes the overhead to the bridging user's device 12 with respect to metering, as relatively simple metric operations, such as implementing a simple byte or packet counter, can be used.
- a user brings a cellular telephone, PDA or a laptop having a Bluetooth interface, and the software TS o already installed or installable, to an airport and, while waiting for a flight, decides to surf the Internet.
- the software TS o already installed or installable
- no Internet access company services the airport.
- the user discovers through ad-hoc Bluetooth networking that some nearby person with an Internet connection will serve as the bridging user 12 to access the Internet.
- This person is also assumed to be functioning in the role of an agent for the user's ISP, i.e., this person has some trusted and protected code from the user's ISP that enables the user to access the Internet, as well as to meter and charge the user appropriately and securely for the user's Internet usage (TS B ).
- the user who in this scenario functions as the originating user 10 , is subsequently billed by the ISP for his or her Internet usage while located at the airport, while the ISP directly pays the bridging user 12 , or otherwise compensates the bridging user (e.g., with free usage minutes).
- the use of other similar or equivalent messages, numbers of messages and message contents may be attempted by those skilled in the art.
- the bridging user 12 may simply advertise a fixed charging amount that is either accepted or rejected by potential originating users 10 .
- the bridging user 12 may have multiple instances of the software TS B , each customized for use with a different instance of the service provider 16 . In this case, and depending on the specifics of the Access Technology B, the bridging user 12 may provide simultaneous connections to two or more service providers 16 for two or more originating users 10 .
- the originating user 10 may have multiple instances of the software TS o , each customized for use with a different service provider 16 . Also, the originating user 10 may be connected at one time to a plurality of service providers 16 though one instance or through multiple instances of bridging users 12 .
Abstract
Description
- This invention relates generally to data communications conducted over data communications networks and, more specifically, relates to techniques for charging for services that are provided in an ad-hoc fashion between possibly untrusted parties.
- The background of, and the problems solved by, this invention can be most conveniently illustrated through the use of examples.
- For example,
FIG. 1 illustrates a conventional gaming scenario where a group of users, physically located in a room, play a multi-playergame using terminals 1A via a local access technology such as a wireless Bluetooth™ network 2. Theterminals 1A may be mobile terminals, such as cellular telephones or gaming devices per se, and their users are referred to herein for convenience also as originating users. In addition to the physically present players another, remotely located player having aterminal 1B, also referred to herein for convenience as a correspondent user, may wish to participate in the game through another access technology, such as a cellular link made through acellular network 3, via one ofterminals 1A′ of the local game participants. - A problem that arises is that the game participant associated with
terminal 1A′, also referred to herein for convenience as a bridging user, is providing the use of his or hercellular link 3 for a common purpose, i.e., the connection to the game server or a point-to-point connection to theremote participant 1B. Typically, themobile terminal 1A′ functions as a bridge or router between the Bluetoothlocal network 2 and thecellular network 3. In most cases the usage of thecellular link 3 results in charging the cellular account of the bridging user, while the other game participants (the originating users) are not charged for the usage of thecellular link 3, even though they are also using thelink 3. For example, theterminals 1A may all be sending data packets through thebridging terminal 1A′, via the Bluetoothaccess network 2, to theremote participant 1B, or when contacting a remote game server (not shown) through the Internet. Hence, there is likely to be a lack of incentive for the user of thebridging terminal 1 A′ to provide the other users access to his or hercellular link 3 for the purpose of gaming, without having the other participants charged appropriately. - As a further example, consider a user with a laptop computer who wishes to connect when in a public place to the Internet. Assume that the user's laptop does not provide cellular access, that there is no hotspot available in order to use a wireless local area network (WLAN), but that the laptop computer does have a Bluetooth interface providing Bluetooth access.
- In this case the user's laptop may connect via the Bluetooth interface to the mobile terminal of some nearby user, such as by using conventional Bluetooth service discovery procedures in order to connect to an appropriate mobile terminal. The nearby user's mobile terminal's cellular connectivity is then used, possibly unbeknownst to the nearby user, to route the laptop's packets appropriately to the Internet (assuming that an IP profile for Bluetooth is present). However, since the cellular link of the nearby bridging mobile station is used, this user's cellular account would be charged for the services that are actually consumed by the laptop user, who may be unknown to the bridging mobile station user.
- In addition to the aforementioned problems related to the charging the bridging user's cellular account, a further problem arises in the context of the use of resources. That is, the use of the
cellular link 3 not only adds costs to the bridging user's cellular account, but also consumes mobile station resources, most importantly the battery power of the mobile station of the bridging user. Other resources that can be consumed include the decoding functionality of the mobile station, as well as connectivity to certain peripherals. The result is that a first mobile station is caused to function, perhaps unwittingly, as a service provider for a second mobile station whose user may be totally unknown to the user of the first mobile station. This situation may be referred to generally as ad-hoc service provisioning. One result of providing ad-hoc service provisioning is that there may be a desire of the bridging mobile station user to also charge for the consumption of the mobile station's resources, in addition for the cellular connectivity costs. - In U.S. Published patent application Ser. No.: US 2002/0071416, Jun. 13, 2002, “Ad Hoc Wide area Network Access Method and System”, G. Carlson et al. describe a method and system for providing a non-connected wireless device with access to a wide area network through a wireless device having a connection facility such as a wireless connection provider or a wireless portal. The non-connected wireless device first employs a short-range wireless communication link to negotiate with at least one wireless connection provider for connection services. Once the non-connected wireless device has selected a particular connection provider, the connection provider provides access to the wide area network resource through the connection facility and measures the usage. The wireless connection provider then bills the non-connected wireless device for the provided connection services, and the non-connected wireless device provides payment information to the wireless connection provider for enabling payment.
- The foregoing technique appears to assume that a trusted relationship exists between the originating user and the bridging user. However, in many cases this will not be the case, and in fact the bridging user may be unaware that his mobile terminal is providing a bridging service for another, possibly unknown user.
- The foregoing and other problems are overcome, and other advantages are realized, in accordance with the presently preferred embodiments of these teachings.
- This invention both addresses and solves the foregoing problems by the use of a method and a system that enables charging for ad-hoc service provisioning, between trusted parties and also between untrusted parties.
- In the preferred embodiments of this invention the bridging user can be associated with any mobile station, or mobile terminal, or computer, collectively referred to for convenience as a wireless device, that has bridging and charging capability in an ad hoc environment. While it is assumed that the originating user has a trusted relationship with a service provider, such as an Internet Service Provider (ISP), a trusted relationship between the originating user and the bridging user is not required. The bridging user may be any person equipped with a wireless device that engages in ad-hoc networking.
- In accordance with the presently preferred embodiment of this invention the service provider, such as an ISP, provides trusted and protected code that runs on the bridging user's wireless device, and the originating user is responsible for negotiating and communicating the negotiation result to the ISP, as well as for metering and logging the usage of the resource(s), such as the cellular link, by the originating user. The originating user's logged usage on the bridging user's wireless device is communicated as accounting information to the ISP in an authenticated manner, i.e., without the possibility of a rogue bridging user altering or spoofing the provided accounting information. The service provider, such as the ISP, bills the originating user for his usage based on the received accounting information, and may pay or credit the bridging user a commission fee for acting as agent of the ISP.
- A method and a system of this invention provide a service for a user device with a service provider. The method includes establishing a service provisioning relationship between the user device, also referred to as an originating user device, and a bridging user device through a first wireless network (e.g., a Bluetooth network); providing a desired service for the user device with the service provider via the bridging user device and the first wireless network, and through a second wireless network (e.g., a cellular network) that couples the bridging user device to the service provider; while providing the service, recording charging data for the service provisioning relationship between the user device and the bridging user device; and reporting the charging data from the bridging user device to the service provider. In the preferred embodiment at least the establishing and recording functions use service provider trusted software running on the user device and on the bridging user device.
- Embodiments of mobile devices and mobile terminal, such as cellular telephones, that are suitably constructed and operated for realizing the originating user device and the bridging user device are also described.
- The foregoing and other aspects of these teachings are made more evident in the following Detailed Description of the Preferred Embodiments, when read in conjunction with the attached Drawing Figures, wherein:
-
FIG. 1 is a simplified block diagram of a conventional usage scenario, specifically one involving local game participants and at least one remote game participant; -
FIG. 2 is a block diagram that illustrates an embodiment of a system architecture in accordance with this invention; and -
FIG. 3 is a signal flow diagram in accordance with the system architecture embodiment shown inFIG. 2 . - Described below, in accordance with preferred embodiments of this invention, is a method and a system to charge for the service provisioning by a user of another, possibly untrusted, user. Referring to
FIG. 2 , each user is assumed to be associated with awireless device access technology 2, such as WLAN or a Bluetooth network (shown as Access Technology A). For example, a typical operating range between devices for a Bluetooth network, assuming normal operating power levels, is about 10 meters. In general, at least thewireless device 12 associated with the bridging user has a second wireless interface 3 (shown as Access Technology B), such as a cellular interface that could be, as non-limiting examples only, a cdma2000 interface or a GSM/UMTS interface, or any suitable interface enabling thewireless device 12 of the bridging user to contact and establish a connection with aservice provider 16 and/or with a remote user, the correspondent user ornode 14, that may be associated with another wireless device. Typical ranges for cellular links are kilometers and tens of kilometers. Furthermore, the cellular network operator will typically provide access to global data communications networks, such as the Internet. - Note that the
service provider 16 may be the cellular network operator, or it may be an ISP. Thecorrespondent node 14 is considered to be the endpoint of the communication with the originatinguser 10 via thebridging user 12. Thecorrespondent node 14 can be any node in the Internet, or a peripheral, or another mobile device, depending on the Access Technology B and the application scenario in which the invention is used. Note that the Access Technologies A and B do not necessarily have to be different for certain services. Further, certain service usage scenarios do not require thecorrespondent node 14, such as a service that uses transcoding services at thebridging user 12. - A third party is used to establish a trusted relationship between possibly unknown users. The third party, which in many cases will be the
service provider 16, provides a certified unit of code (TS o 11A) for the originatinguser 10, as well as for the bridging user 12 (TS B 11B). The provided third party code monitors and accounts for particular service usage based on at least one predetermined usage metric. Non-limiting examples of suitable usage metrics include bytes, packets and transaction counts. The third party code monitors the service usage, such as IP forwarding, according to the agreed upon usage metrics. - The bridging
user 12 may request that the current metric instance to be sent by the third party code for payment at any time during the transactions, preferably though at the end of the transactions. For this purpose the invention also provides a method to agree upon the charging with third party that is used for billing the originatinguser 10. - It is assumed that the originating
user 10 and the bridginguser 12 have a subscription with theservice provider 16. As a consequence of this subscription both mobile devices have installed the unit of code 11, provided by theservice provider 16, that performs the charging and monitoring functions. These units of code are those depicted as TSo and TSB. Also as a consequence of the subscription bothusers service provider 16 in the sense that they provide appropriate billing information, such as credit card information, to theservice provider 16. Also as a consequence of the subscription theservice provider 16 maintains an appropriate set of credential information for eitheruser - In order to implement a charged session in accordance with the teachings of this invention, appropriate information is established in order to initiate and conduct the session.
FIG. 3 shows an example of the signalling that is involved. It should be noted that the communication between the originatinguser 10 and the bridginguser 12 occurs via Access Technology A (e.g., through the Bluetooth network 2), while the communication between the bridginguser 12 and theservice provider 16 occurs via Access Technology B (e.g., through the cdma2000 cellular network). - In
FIG. 3 it is assumed that the software units for TSo and TSB have been previously installed on themobile devices service provider 16 downloading the software units over-the-air to at least themobile device 12, which then transfers TSo in an authenticated manner over the Access Technology A to the mobile device of the originatinguser 10, or by any suitable technique. - TSo of the originating
user 10 sends a message (message1) to TSB of the bridginguser 12. The addressing of this and other messages between the mobile devices can be realized by any suitable means. A presently preferred, but non-limiting addressing technique is one known as “application layer addressing”. This technique can be implemented through, for example, addressing particular IP ports, or by using Uniform Resource Identifier (URI) addressing. As a result, the trusted units of code TSo and TSB exchange messages on the application layer. - The service request message, sent from TSo includes at least a description of the service that is desired to be used at the bridging
user 12. This service description is sufficient to initiate appropriate monitoring at the bridginguser 12, as discussed below. The message1 of TSo also includes a description of the metric to be used for charging, such as byte or transaction count. Additionally, the message1 may include cost information related to the originatinguser 10, for example, the cost that the originatinguser 10 would pay for a particular service. - Upon reception of message1 at the bridging
user 12, TSB extracts the information and either accepts or rejects the request. For example, the request may be rejected if the requested service is not supported by TSB with respect to an appropriate monitoring technique. If the request is accepted, TSB determines usage costs for the particular requested metric and sends a response (message2 inFIG. 3 ) back to TSo of the originatinguser 10. The determination of the costs may be based upon information in configuration files, stored at the bridginguser 12 and configured through the user prior to engaging in the particular session. Or the user may be requested by TSB (e.g., in form of a dialog box) to establish a particular cost metric for the session upon the reception of message, at the bridginguser 12. The costs typically, but not necessarily, depend on the actual costs for provisioning the service at the bridginguser 12, e.g., the cost for transfer of bytes within Access Technology B. In addition, charges may be added for the use of local resources, such as processing and/or battery power. In addition, information made available in message1 regarding cost expectations of the originatinguser 10 may be incorporated in the decision as well. - Upon reception of message2 at the TSo of the originating
user 10, the specified costs for provisioning the requested service at the bridginguser 12 can be accepted or rejected. This acceptance can be similar to the determination of the costs at the bridginguser 12, e.g., based upon certain pre-configured information, or a dialog box that requests the confirmation of the originatinguser 10 regarding the cost(s). - If the service charge is rejected by the originating
user 10, the sequence of message, and message2 may occur again. In this case the second instance of message1 can include revised cost information related to the originatinguser 10, for example, a revised cost that the originatinguser 10 is willing to pay for the requested service. The revised proposed cost may be greater than what was indicated in the first instance of message1, but less than the cost that the bridginguser 12 indicated that he was willing to accept in the first instance of message2. This mechanism thus implements an offer-counteroffer model of negotiation between the originatinguser 10 and the bridginguser 14, and can continue automatically or with user input until both the originatinguser 10 and the bridginguser 12 are satisfied. - Assuming now that the originating
user 10 and the bridginguser 12 finally agree on an acceptable service charge, TSo of the originatinguser 10 sends message3 to TS3 of the bridginguser 12. Message3 contains the service charge information that was agreed upon in the sequence of message, and message2, and preferably also contains appropriate credential information required at theservice provider 16, such as a mobile device or terminal identifier and also possibly an encrypted password. - Upon reception of message3 in
FIG. 3 , theTS B 11B of the bridginguser 12 forwards the information to theservice provider 16 as message4. Upon reception of message4 at theservice provider 16, one of the chargingrecords 16A is created by theservice provider 16, using the received service charge and the mobile terminal identifier. After creating one of the chargingrecords 16A, the service provider further generates a locally unique session identifier for this charging record that is used in future communications to uniquely identify the charged session. If used, the encrypted password is employed to authenticate and authorize the service charge to be made. Theservice provider 16 acknowledges (ACKs) the creation of the charged session by sending message5 to the bridginguser 12. Upon reception of the message5, theTS B 11B of the bridginguser 12 extracts the enclosed session identifier for future use. - Having thus established the charging record, the system is equipped to begin metering and charging the originating
user 10. More specifically, after the establishment of the charging record information at theservice provider 16, in response to receiving message4, theTS B 11B at the bridginguser 12 initiates an appropriate monitoring function to meter the agreed upon service usage. For example, for a service such as “IP routing”, appropriate byte counters may be instantiated that are increased based on monitoring the IP forwarding functionality at the bridginguser 12. Other types of suitable monitoring functions include the use of a packet counter, a transaction counter in a browser, and one or more resource consumption recorders such as one that keeps track of the bridging user mobile device data processing cycles devoted to servicing the originating user, or some other data processing metric, and/or primary power (e.g., battery power) consumption recorders. - During the lifetime of the session the
TS B 11B of the bridginguser 12 performs the appropriate metering of the service usage, such as counting forwarded IP packets. It should be noted that the specifics of the actual underlying service are not within the scope of the invention. - At any time during the session, the metering information can be sent as message6 from the
TS B 11B of the bridginguser 12 to theservice provider 1. The message6 includes at least the session identifier, as well as the current meter value. Theservice provider 16 stores the metering information accordingly within the appropriate charging record (identified through the session identifier) and acknowledges the reception by sending message7 back to theTS B 11B of the bridginguser 12. Note that the use of message6 and message7 is optional, as only the final meter value need be sent at session termination (message9), as described below. - The session can be terminated explicitly through the
TS o 11A of the originatinguser 10 by sending an appropriate session termination message8 to theTS B 11B of the bridginguser 12. Alternatively, a local decision at the bridginguser 12 may be used to terminate the session. In either case, theTS B 11B of the bridginguser 12 sends a terminate charging message9 to theservice provider 16. The terminate charging message9 contains at least the current meter value(s), the session identifier, and an indication to terminate the session. Upon reception at theservice provider 16, an appropriate billing record for the originatinguser 10 is created, based on the available meter information as well as the agreed service charge. The operation is then confirmed towards theTS B 11B of the bridginguser 12 by sending message10. Upon reception of message10, theTS B 11B of the bridginguser 12 tears down the metering and monitoring functions for the terminated session. - Note that it is not within the scope of the invention to specify exactly how the foregoing information is actually described, although XML (Extended Markup Language) or RDF (Resource Description Format) techniques are well suited for this purpose.
- Based on the foregoing description it should be apparent that this invention significantly improves on the conventional approaches by providing a generic solution that can be used for a number of different service usage scenarios, such as bridging between access technologies, and does not rely on scenario-specific solutions. The inherent lack of trust between possibly unknown mobile users is overcome through the use of certified and trusted metering and monitoring software (TSo and TSB) that is offered through a
common service provider 16 with which both the originating and the bridging users have a subscription. Further, the use of this invention permits a charging negotiation process to occur through the offer-counteroffer negotiation model during the establishment phase of the charged session (via the message1/message2 interchange). - The service provider-based solution can be totally independent of a particular wireless network operator, as it does not require extensions to the operator networks, nor does it rely on any specific operator functionality. Therefore, it enables mobile device based services that are charged on the application level rather than on an access network subscription level.
- Further, the trusted software (TSB and TSo) maybe pre-loaded on and integrated with the software of the mobile devices, thereby providing uniformity and a common trusted charging standard that can be used across various network operators and service providers. In this case the trusted software (TSB and TSo) can be integrated into mobile devices provided by a mobile device manufacturer, for performing the charging and metering functions, while the
service provider 16 software functions can be provided by the mobile device manufacturer as well or by or through a third party. - The use of this invention further minimizes the overhead to the bridging user's
device 12 with respect to metering, as relatively simple metric operations, such as implementing a simple byte or packet counter, can be used. - In one exemplary use case of this invention, assume that a user brings a cellular telephone, PDA or a laptop having a Bluetooth interface, and the software TSo already installed or installable, to an airport and, while waiting for a flight, decides to surf the Internet. Assume further that no Internet access company services the airport. However, the user discovers through ad-hoc Bluetooth networking that some nearby person with an Internet connection will serve as the bridging
user 12 to access the Internet. This person is also assumed to be functioning in the role of an agent for the user's ISP, i.e., this person has some trusted and protected code from the user's ISP that enables the user to access the Internet, as well as to meter and charge the user appropriately and securely for the user's Internet usage (TSB). The user, who in this scenario functions as the originatinguser 10, is subsequently billed by the ISP for his or her Internet usage while located at the airport, while the ISP directly pays the bridginguser 12, or otherwise compensates the bridging user (e.g., with free usage minutes). - The foregoing description has provided by way of exemplary and non-limiting examples a full and informative description of the best method and apparatus presently contemplated by the inventors for carrying out the invention. However, various modifications and adaptations may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings and the appended claims.
- As but some examples, the use of other similar or equivalent messages, numbers of messages and message contents may be attempted by those skilled in the art. Further, in some embodiments of this invention there may be no provision for the charging negotiations to occur between the originating and bridging users, e.g., the bridging
user 12 may simply advertise a fixed charging amount that is either accepted or rejected by potential originatingusers 10. In addition, the bridginguser 12 may have multiple instances of the software TSB, each customized for use with a different instance of theservice provider 16. In this case, and depending on the specifics of the Access Technology B, the bridginguser 12 may provide simultaneous connections to two ormore service providers 16 for two or more originatingusers 10. In a similar manner the originatinguser 10 may have multiple instances of the software TSo, each customized for use with adifferent service provider 16. Also, the originatinguser 10 may be connected at one time to a plurality ofservice providers 16 though one instance or through multiple instances of bridgingusers 12. - However, all such and similar modifications of the teachings of this invention will still fall within the scope of this invention.
- Furthermore, some of the features of the present invention could be used to advantage without the corresponding use of other features. As such, the foregoing description should be considered as merely illustrative of the principles of the present invention, and not in limitation thereof.
Claims (44)
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/792,181 US7415268B2 (en) | 2004-03-02 | 2004-03-02 | Method and apparatus to provide charging for ad-hoc service provisioning between trusted parties and between untrusted parties |
EP05708644A EP1728379B1 (en) | 2004-03-02 | 2005-03-01 | Method and apparatus to provide charging for ad-hoc service provisioning between trusted parties and between untrusted parties |
CN200580012905XA CN1947408B (en) | 2004-03-02 | 2005-03-01 | Method and apparatus to provide charging for ad-hoc service provisioning between trusted parties and between untrusted parties |
PCT/IB2005/000533 WO2005086468A1 (en) | 2004-03-02 | 2005-03-01 | Method and apparatus to provide charging for ad-hoc service provisioning between trusted parties and between untrusted parties |
JP2007501375A JP2007528162A (en) | 2004-03-02 | 2005-03-01 | Method and apparatus for billing ad hoc service provided between reliable communication partners and between unreliable communication partners |
AT05708644T ATE521192T1 (en) | 2004-03-02 | 2005-03-01 | METHOD AND APPARATUS FOR COLLECTION OF FEES FOR AD HOC SERVICE PROVISION BETWEEN RECOGNIZED PARTIES AND BETWEEN UNRECOGNIZED PARTIES |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/792,181 US7415268B2 (en) | 2004-03-02 | 2004-03-02 | Method and apparatus to provide charging for ad-hoc service provisioning between trusted parties and between untrusted parties |
Publications (2)
Publication Number | Publication Date |
---|---|
US20050197098A1 true US20050197098A1 (en) | 2005-09-08 |
US7415268B2 US7415268B2 (en) | 2008-08-19 |
Family
ID=34911788
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/792,181 Expired - Fee Related US7415268B2 (en) | 2004-03-02 | 2004-03-02 | Method and apparatus to provide charging for ad-hoc service provisioning between trusted parties and between untrusted parties |
Country Status (6)
Country | Link |
---|---|
US (1) | US7415268B2 (en) |
EP (1) | EP1728379B1 (en) |
JP (1) | JP2007528162A (en) |
CN (1) | CN1947408B (en) |
AT (1) | ATE521192T1 (en) |
WO (1) | WO2005086468A1 (en) |
Cited By (69)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050222858A1 (en) * | 2004-03-31 | 2005-10-06 | Fujitsu Limited | Sending method of pay contents, radio terminal and carrier |
US20060067316A1 (en) * | 2004-09-30 | 2006-03-30 | Johnson Mark W | Method and apparatus for tracking costs associated with propagating a data packet |
US20070111189A1 (en) * | 2005-11-17 | 2007-05-17 | Mark Nelson | Method and tool for surveying an individual or a plurality of individuals and collecting and displaying survey responses |
US20070133710A1 (en) * | 2005-12-06 | 2007-06-14 | Shabbir Khan | Digital object title and transmission information |
WO2008044983A1 (en) | 2006-10-11 | 2008-04-17 | Belleshill Ab | Charging in ad-hoc communication networks |
US20090047964A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | Handoff in ad-hoc mobile broadband networks |
US20090046644A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | Service set manager for ad hoc mobile service provider |
US20090046861A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | Security for a heterogeneous ad hoc mobile broadband network |
US20090049158A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | Ad hoc service provider topology |
US20090047930A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | Method for a heterogeneous wireless ad hoc mobile service provider |
US20090047966A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | Method for a heterogeneous wireless ad hoc mobile internet access service |
US20090198797A1 (en) * | 2008-02-05 | 2009-08-06 | Microsoft Corporation | Network device provisioning using documents |
US20090307354A1 (en) * | 2008-06-06 | 2009-12-10 | Jian-Jun Qian | Wireless Communication System and Related Method Capable of Sharing System Resource |
US20100093342A1 (en) * | 2008-10-09 | 2010-04-15 | Padmaja Ramachandra Rao | System and method for temporarily accessing another user's service |
US20100107236A1 (en) * | 2007-03-09 | 2010-04-29 | Shozo Fujino | Network system, communication method, communication terminal, and communication program |
US20100150052A1 (en) * | 2007-09-03 | 2010-06-17 | Fujitsu Limited | Wireless Communications Node Used In AD HOC Network And Method Thereof |
US20100229229A1 (en) * | 2006-02-06 | 2010-09-09 | Matsushita Electric Industrial Co., Ltd. | Method, system and apparatus for indirect access by communication device |
US20110014898A1 (en) * | 2009-07-20 | 2011-01-20 | Qualcomm Incorporated | Wireless provisioning solution for target devices |
US20110117914A1 (en) * | 2009-11-12 | 2011-05-19 | Electronics And Telecommunications Research Institute | Method and apparatus for deregistration of personal network element(pne) in 3gpp personal network(pn) |
US20110212773A1 (en) * | 2008-11-05 | 2011-09-01 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and Arrangement for Enabling Games in a Communication Network |
US8014389B2 (en) | 2005-12-06 | 2011-09-06 | Lippershy Celestial Llc | Bidding network |
WO2011064433A3 (en) * | 2009-11-25 | 2011-11-24 | Telefonica, S.A. | Service provision system, method and repeater |
US8194701B2 (en) | 2005-12-06 | 2012-06-05 | Lippershy Celestial Llc | System and/or method for downstream bidding |
US20130294327A1 (en) * | 2012-05-04 | 2013-11-07 | Qualcomm Incorporated | Charging over a user-deployed relay |
US20140235239A1 (en) * | 2013-02-19 | 2014-08-21 | Verizon Patent And Licensing, Inc. | Service creation using mobile device |
US20140274032A1 (en) * | 2013-03-14 | 2014-09-18 | Sprint Communications Company L.P. | System for Activating and Customizing a Mobile Device via Near Field Communication |
FR3007601A1 (en) * | 2013-06-25 | 2014-12-26 | France Telecom | CONTROL OF CONNECTION TO AN EXTENDED NETWORK ON A TERMINAL FORMING GATEWAY WITH A LOCAL NETWORK |
US9042877B1 (en) | 2013-05-21 | 2015-05-26 | Sprint Communications Company L.P. | System and method for retrofitting a branding framework into a mobile communication device |
US9098368B1 (en) | 2011-05-31 | 2015-08-04 | Sprint Communications Company L.P. | Loading branded media outside system partition |
US9100769B2 (en) | 2013-02-08 | 2015-08-04 | Sprint Communications Company L.P. | System and method of storing service brand packages on a mobile device |
US9100819B2 (en) | 2013-02-08 | 2015-08-04 | Sprint-Communications Company L.P. | System and method of provisioning and reprovisioning a mobile device based on self-locating |
US9125037B2 (en) | 2013-08-27 | 2015-09-01 | Sprint Communications Company L.P. | System and methods for deferred and remote device branding |
US9143924B1 (en) | 2013-08-27 | 2015-09-22 | Sprint Communications Company L.P. | Segmented customization payload delivery |
US9161209B1 (en) | 2013-08-21 | 2015-10-13 | Sprint Communications Company L.P. | Multi-step mobile device initiation with intermediate partial reset |
US9161325B1 (en) | 2013-11-20 | 2015-10-13 | Sprint Communications Company L.P. | Subscriber identity module virtualization |
US9170870B1 (en) | 2013-08-27 | 2015-10-27 | Sprint Communications Company L.P. | Development and testing of payload receipt by a portable electronic device |
US9179367B2 (en) | 2009-05-26 | 2015-11-03 | Qualcomm Incorporated | Maximizing service provider utility in a heterogeneous wireless ad-hoc network |
US9198027B2 (en) | 2012-09-18 | 2015-11-24 | Sprint Communications Company L.P. | Generic mobile devices customization framework |
US9204286B1 (en) | 2013-03-15 | 2015-12-01 | Sprint Communications Company L.P. | System and method of branding and labeling a mobile device |
US9204239B1 (en) | 2013-08-27 | 2015-12-01 | Sprint Communications Company L.P. | Segmented customization package within distributed server architecture |
US9208513B1 (en) | 2011-12-23 | 2015-12-08 | Sprint Communications Company L.P. | Automated branding of generic applications |
US9226133B1 (en) | 2013-01-18 | 2015-12-29 | Sprint Communications Company L.P. | Dynamic remotely managed SIM profile |
US9280483B1 (en) | 2013-05-22 | 2016-03-08 | Sprint Communications Company L.P. | Rebranding a portable electronic device while maintaining user data |
US9301081B1 (en) | 2013-11-06 | 2016-03-29 | Sprint Communications Company L.P. | Delivery of oversized branding elements for customization |
US9307400B1 (en) | 2014-09-02 | 2016-04-05 | Sprint Communications Company L.P. | System and method of efficient mobile device network brand customization |
EP2911419A4 (en) * | 2012-10-19 | 2016-04-27 | Sony Corp | Communication apparatus, service providing apparatus, server and storage medium |
US9357378B1 (en) | 2015-03-04 | 2016-05-31 | Sprint Communications Company L.P. | Subscriber identity module (SIM) card initiation of custom application launcher installation on a mobile communication device |
US9363622B1 (en) | 2013-11-08 | 2016-06-07 | Sprint Communications Company L.P. | Separation of client identification composition from customization payload to original equipment manufacturer layer |
US9392395B1 (en) | 2014-01-16 | 2016-07-12 | Sprint Communications Company L.P. | Background delivery of device configuration and branding |
US9398462B1 (en) | 2015-03-04 | 2016-07-19 | Sprint Communications Company L.P. | Network access tiered based on application launcher installation |
US9420496B1 (en) | 2014-01-24 | 2016-08-16 | Sprint Communications Company L.P. | Activation sequence using permission based connection to network |
US9426649B2 (en) * | 2014-01-30 | 2016-08-23 | Intel IP Corporation | Apparatus, system and method of securing communications of a user equipment (UE) in a wireless local area network |
US9426641B1 (en) | 2014-06-05 | 2016-08-23 | Sprint Communications Company L.P. | Multiple carrier partition dynamic access on a mobile device |
US9451446B2 (en) | 2013-01-18 | 2016-09-20 | Sprint Communications Company L.P. | SIM profile brokering system |
US9532211B1 (en) | 2013-08-15 | 2016-12-27 | Sprint Communications Company L.P. | Directing server connection based on location identifier |
US9549009B1 (en) | 2013-02-08 | 2017-01-17 | Sprint Communications Company L.P. | Electronic fixed brand labeling |
US9603009B1 (en) | 2014-01-24 | 2017-03-21 | Sprint Communications Company L.P. | System and method of branding a device independent of device activation |
EP3147843A1 (en) * | 2015-09-25 | 2017-03-29 | Cartadis | Enhanced management of data communication of a transaction between a service terminal and a telephone terminal |
US9681251B1 (en) | 2014-03-31 | 2017-06-13 | Sprint Communications Company L.P. | Customization for preloaded applications |
US9686183B2 (en) | 2005-12-06 | 2017-06-20 | Zarbaña Digital Fund Llc | Digital object routing based on a service request |
US9743271B2 (en) | 2013-10-23 | 2017-08-22 | Sprint Communications Company L.P. | Delivery of branding content and customizations to a mobile communication device |
US9913132B1 (en) | 2016-09-14 | 2018-03-06 | Sprint Communications Company L.P. | System and method of mobile phone customization based on universal manifest |
US9992326B1 (en) | 2014-10-31 | 2018-06-05 | Sprint Communications Company L.P. | Out of the box experience (OOBE) country choice using Wi-Fi layer transmission |
US10021240B1 (en) | 2016-09-16 | 2018-07-10 | Sprint Communications Company L.P. | System and method of mobile phone customization based on universal manifest with feature override |
US10306433B1 (en) | 2017-05-01 | 2019-05-28 | Sprint Communications Company L.P. | Mobile phone differentiated user set-up |
US10455071B2 (en) | 2012-05-09 | 2019-10-22 | Sprint Communications Company L.P. | Self-identification of brand and branded firmware installation in a generic electronic device |
US10506398B2 (en) | 2013-10-23 | 2019-12-10 | Sprint Communications Company Lp. | Implementation of remotely hosted branding content and customizations |
US10747685B2 (en) * | 2009-01-31 | 2020-08-18 | International Business Machines Corporation | Expiring virtual content from a cache in a virtual universe |
US11729594B2 (en) | 2013-03-13 | 2023-08-15 | Huawei Device Co., Ltd. | Network access method, device, and system |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7894447B2 (en) * | 2005-12-06 | 2011-02-22 | Lippershy Celestial Llc | Digital object routing |
US7710932B2 (en) * | 2005-12-14 | 2010-05-04 | Motorola, Inc. | Method and apparatus for encouraging routing in a network |
JP5781719B2 (en) * | 2008-03-28 | 2015-09-24 | 京セラ株式会社 | Portable wireless terminal device and wireless communication network system |
KR101285113B1 (en) * | 2008-10-31 | 2013-07-17 | 에스케이플래닛 주식회사 | A system, a method, a service server, a mobile terminal and a storage means for contents transmission |
US8977232B2 (en) | 2009-01-29 | 2015-03-10 | Qualcomm Incorporated | Certified device-based accounting |
US20100261473A1 (en) * | 2009-04-08 | 2010-10-14 | Motorola, Inc. | cellular communication system and a base station and method therefor |
US20120203824A1 (en) | 2011-02-07 | 2012-08-09 | Nokia Corporation | Method and apparatus for on-demand client-initiated provisioning |
US8913587B2 (en) * | 2011-05-19 | 2014-12-16 | Qualcomm Incorporated | Infrastructure-unassisted inter-device wireless wide area network handoff |
EP3683637B1 (en) * | 2019-01-16 | 2023-03-22 | Siemens Aktiengesellschaft | Method for producing a bidirectional connection between a device, in particular a field device, and an application in a central device |
Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US220074A (en) * | 1879-09-30 | Improvement in devices for bending hooks | ||
US20020052824A1 (en) * | 2000-04-21 | 2002-05-02 | Sriketan Mahanti | Method and apparatus for electronic trading |
US20020071416A1 (en) * | 2000-12-13 | 2002-06-13 | Greg Carlson | Ad hoc wide area network access method and system |
US20030054796A1 (en) * | 2001-09-17 | 2003-03-20 | Hitachi, Ltd. | Charging method and terminal equipment in the information and communication network system |
US20030061358A1 (en) * | 2001-08-28 | 2003-03-27 | Yolande Piazza | Method and system for presenting charge related data on a worldwide basis through a network |
US20040117358A1 (en) * | 2002-03-16 | 2004-06-17 | Von Kaenel Tim A. | Method, system, and program for an improved enterprise spatial system |
US20040123118A1 (en) * | 2002-01-16 | 2004-06-24 | Dahan Franck B. | Secure mode indicator for smart phone or PDA |
US20040142686A1 (en) * | 2002-11-08 | 2004-07-22 | Kirkup Michael G. | System and method of connection control for wireless mobile communication devices |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2375920A (en) | 2000-12-20 | 2002-11-27 | Motorola Inc | Method of billing for communications which rewards users for operating their communications devices in relay operating mode |
JP2002209028A (en) * | 2001-01-10 | 2002-07-26 | Mitsubishi Electric Corp | Charging method in adhoc network |
US7373103B2 (en) * | 2001-10-03 | 2008-05-13 | Ntt Docomo, Inc. | Relay terminal, base station, charging server, communication system, charging method, program computer data signal, and storage medium |
US8027635B2 (en) | 2002-05-22 | 2011-09-27 | Hewlett-Packard Development Company, L.P. | Relaying third party wireless communications through a portable wireless system |
EP1563641A1 (en) | 2002-11-06 | 2005-08-17 | Koninklijke Philips Electronics N.V. | Mobile ad-hoc internet sharing |
-
2004
- 2004-03-02 US US10/792,181 patent/US7415268B2/en not_active Expired - Fee Related
-
2005
- 2005-03-01 AT AT05708644T patent/ATE521192T1/en not_active IP Right Cessation
- 2005-03-01 EP EP05708644A patent/EP1728379B1/en not_active Not-in-force
- 2005-03-01 CN CN200580012905XA patent/CN1947408B/en not_active Expired - Fee Related
- 2005-03-01 WO PCT/IB2005/000533 patent/WO2005086468A1/en active Application Filing
- 2005-03-01 JP JP2007501375A patent/JP2007528162A/en active Pending
Patent Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US220074A (en) * | 1879-09-30 | Improvement in devices for bending hooks | ||
US20020052824A1 (en) * | 2000-04-21 | 2002-05-02 | Sriketan Mahanti | Method and apparatus for electronic trading |
US20020071416A1 (en) * | 2000-12-13 | 2002-06-13 | Greg Carlson | Ad hoc wide area network access method and system |
US20030061358A1 (en) * | 2001-08-28 | 2003-03-27 | Yolande Piazza | Method and system for presenting charge related data on a worldwide basis through a network |
US20030054796A1 (en) * | 2001-09-17 | 2003-03-20 | Hitachi, Ltd. | Charging method and terminal equipment in the information and communication network system |
US20040123118A1 (en) * | 2002-01-16 | 2004-06-24 | Dahan Franck B. | Secure mode indicator for smart phone or PDA |
US20040117358A1 (en) * | 2002-03-16 | 2004-06-17 | Von Kaenel Tim A. | Method, system, and program for an improved enterprise spatial system |
US20040142686A1 (en) * | 2002-11-08 | 2004-07-22 | Kirkup Michael G. | System and method of connection control for wireless mobile communication devices |
Cited By (98)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7366502B2 (en) * | 2004-03-31 | 2008-04-29 | Fujitsu Limited | Sending method of pay contents, radio terminal and carrier |
US20050222858A1 (en) * | 2004-03-31 | 2005-10-06 | Fujitsu Limited | Sending method of pay contents, radio terminal and carrier |
US20060067316A1 (en) * | 2004-09-30 | 2006-03-30 | Johnson Mark W | Method and apparatus for tracking costs associated with propagating a data packet |
US7586869B2 (en) * | 2004-09-30 | 2009-09-08 | Rockwell Collins, Inc. | Method and apparatus for tracking costs associated with propagating a data packet |
US20070111189A1 (en) * | 2005-11-17 | 2007-05-17 | Mark Nelson | Method and tool for surveying an individual or a plurality of individuals and collecting and displaying survey responses |
US8055897B2 (en) | 2005-12-06 | 2011-11-08 | Lippershy Celestial Llc | Digital object title and transmission information |
US10892975B2 (en) | 2005-12-06 | 2021-01-12 | Zarbaña Digital Fund Llc | Digital object routing based on a service request |
US9686183B2 (en) | 2005-12-06 | 2017-06-20 | Zarbaña Digital Fund Llc | Digital object routing based on a service request |
US11539614B2 (en) | 2005-12-06 | 2022-12-27 | Zarbaña Digital Fund Llc | Digital object routing based on a service request |
US8194701B2 (en) | 2005-12-06 | 2012-06-05 | Lippershy Celestial Llc | System and/or method for downstream bidding |
US8014389B2 (en) | 2005-12-06 | 2011-09-06 | Lippershy Celestial Llc | Bidding network |
US20070133710A1 (en) * | 2005-12-06 | 2007-06-14 | Shabbir Khan | Digital object title and transmission information |
US8276189B2 (en) * | 2006-02-06 | 2012-09-25 | Panasonic Corporation | Method, system and apparatus for indirect access by communication device |
US20100229229A1 (en) * | 2006-02-06 | 2010-09-09 | Matsushita Electric Industrial Co., Ltd. | Method, system and apparatus for indirect access by communication device |
EP2074742A4 (en) * | 2006-10-11 | 2018-01-03 | Belleshill Ab | Charging in ad-hoc communication networks |
WO2008044983A1 (en) | 2006-10-11 | 2008-04-17 | Belleshill Ab | Charging in ad-hoc communication networks |
US20100107236A1 (en) * | 2007-03-09 | 2010-04-29 | Shozo Fujino | Network system, communication method, communication terminal, and communication program |
US20090049158A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | Ad hoc service provider topology |
US20090047930A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | Method for a heterogeneous wireless ad hoc mobile service provider |
US20090047964A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | Handoff in ad-hoc mobile broadband networks |
US8644206B2 (en) | 2007-08-17 | 2014-02-04 | Qualcomm Incorporated | Ad hoc service provider configuration for broadcasting service information |
JP2010537561A (en) * | 2007-08-17 | 2010-12-02 | クゥアルコム・インコーポレイテッド | Methods for heterogeneous wireless ad hoc mobile service providers |
US9167426B2 (en) | 2007-08-17 | 2015-10-20 | Qualcomm Incorporated | Ad hoc service provider's ability to provide service for a wireless network |
US9398453B2 (en) | 2007-08-17 | 2016-07-19 | Qualcomm Incorporated | Ad hoc service provider's ability to provide service for a wireless network |
US20090046644A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | Service set manager for ad hoc mobile service provider |
US20090047966A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | Method for a heterogeneous wireless ad hoc mobile internet access service |
US20090046676A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | Ad hoc service provider configuration for broadcasting service information |
US9392445B2 (en) | 2007-08-17 | 2016-07-12 | Qualcomm Incorporated | Handoff at an ad-hoc mobile service provider |
US20090046861A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | Security for a heterogeneous ad hoc mobile broadband network |
US20090046591A1 (en) * | 2007-08-17 | 2009-02-19 | Qualcomm Incorporated | Ad hoc service provider's ability to provide service for a wireless network |
US8355366B2 (en) * | 2007-09-03 | 2013-01-15 | Fujitsu Limited | Wireless communications node used in AD HOC network and method thereof |
US20100150052A1 (en) * | 2007-09-03 | 2010-06-17 | Fujitsu Limited | Wireless Communications Node Used In AD HOC Network And Method Thereof |
US20090198797A1 (en) * | 2008-02-05 | 2009-08-06 | Microsoft Corporation | Network device provisioning using documents |
US20090307354A1 (en) * | 2008-06-06 | 2009-12-10 | Jian-Jun Qian | Wireless Communication System and Related Method Capable of Sharing System Resource |
US20100093342A1 (en) * | 2008-10-09 | 2010-04-15 | Padmaja Ramachandra Rao | System and method for temporarily accessing another user's service |
US8380188B2 (en) * | 2008-10-09 | 2013-02-19 | Kyocera Corporation | System and method for temporarily accessing another user's service |
US20110212773A1 (en) * | 2008-11-05 | 2011-09-01 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and Arrangement for Enabling Games in a Communication Network |
US10747685B2 (en) * | 2009-01-31 | 2020-08-18 | International Business Machines Corporation | Expiring virtual content from a cache in a virtual universe |
US9179367B2 (en) | 2009-05-26 | 2015-11-03 | Qualcomm Incorporated | Maximizing service provider utility in a heterogeneous wireless ad-hoc network |
US8594624B2 (en) * | 2009-07-20 | 2013-11-26 | Qualcomm Incorporated | Wireless provisioning solution for target devices |
US20110014898A1 (en) * | 2009-07-20 | 2011-01-20 | Qualcomm Incorporated | Wireless provisioning solution for target devices |
US8331923B2 (en) * | 2009-07-20 | 2012-12-11 | Qualcomm Incorporated | Wireless provisioning solution for target devices |
US20110117914A1 (en) * | 2009-11-12 | 2011-05-19 | Electronics And Telecommunications Research Institute | Method and apparatus for deregistration of personal network element(pne) in 3gpp personal network(pn) |
WO2011064433A3 (en) * | 2009-11-25 | 2011-11-24 | Telefonica, S.A. | Service provision system, method and repeater |
US9098368B1 (en) | 2011-05-31 | 2015-08-04 | Sprint Communications Company L.P. | Loading branded media outside system partition |
US9208513B1 (en) | 2011-12-23 | 2015-12-08 | Sprint Communications Company L.P. | Automated branding of generic applications |
US20130294327A1 (en) * | 2012-05-04 | 2013-11-07 | Qualcomm Incorporated | Charging over a user-deployed relay |
US10051686B2 (en) * | 2012-05-04 | 2018-08-14 | Qualcomm Incorporated | Charging over a user-deployed relay |
US10455071B2 (en) | 2012-05-09 | 2019-10-22 | Sprint Communications Company L.P. | Self-identification of brand and branded firmware installation in a generic electronic device |
US9198027B2 (en) | 2012-09-18 | 2015-11-24 | Sprint Communications Company L.P. | Generic mobile devices customization framework |
US9420399B2 (en) | 2012-09-18 | 2016-08-16 | Sprint Communications Company L.P. | Generic mobile devices customization framework |
US10026071B2 (en) | 2012-10-19 | 2018-07-17 | Sony Corporation | Communication device, service providing device, and communication server |
EP2911419A4 (en) * | 2012-10-19 | 2016-04-27 | Sony Corp | Communication apparatus, service providing apparatus, server and storage medium |
US9451446B2 (en) | 2013-01-18 | 2016-09-20 | Sprint Communications Company L.P. | SIM profile brokering system |
US9226133B1 (en) | 2013-01-18 | 2015-12-29 | Sprint Communications Company L.P. | Dynamic remotely managed SIM profile |
US9100769B2 (en) | 2013-02-08 | 2015-08-04 | Sprint Communications Company L.P. | System and method of storing service brand packages on a mobile device |
US9549009B1 (en) | 2013-02-08 | 2017-01-17 | Sprint Communications Company L.P. | Electronic fixed brand labeling |
US9100819B2 (en) | 2013-02-08 | 2015-08-04 | Sprint-Communications Company L.P. | System and method of provisioning and reprovisioning a mobile device based on self-locating |
US8971886B2 (en) * | 2013-02-19 | 2015-03-03 | Verizon Patent And Licensing Inc. | Service creation using mobile device |
US20140235239A1 (en) * | 2013-02-19 | 2014-08-21 | Verizon Patent And Licensing, Inc. | Service creation using mobile device |
US11729594B2 (en) | 2013-03-13 | 2023-08-15 | Huawei Device Co., Ltd. | Network access method, device, and system |
US9026105B2 (en) * | 2013-03-14 | 2015-05-05 | Sprint Communications Company L.P. | System for activating and customizing a mobile device via near field communication |
US20140274032A1 (en) * | 2013-03-14 | 2014-09-18 | Sprint Communications Company L.P. | System for Activating and Customizing a Mobile Device via Near Field Communication |
US9204286B1 (en) | 2013-03-15 | 2015-12-01 | Sprint Communications Company L.P. | System and method of branding and labeling a mobile device |
US9042877B1 (en) | 2013-05-21 | 2015-05-26 | Sprint Communications Company L.P. | System and method for retrofitting a branding framework into a mobile communication device |
US9280483B1 (en) | 2013-05-22 | 2016-03-08 | Sprint Communications Company L.P. | Rebranding a portable electronic device while maintaining user data |
FR3007601A1 (en) * | 2013-06-25 | 2014-12-26 | France Telecom | CONTROL OF CONNECTION TO AN EXTENDED NETWORK ON A TERMINAL FORMING GATEWAY WITH A LOCAL NETWORK |
WO2014207363A1 (en) * | 2013-06-25 | 2014-12-31 | Orange | Control of connection to an extended network on a terminal forming a gateway with a local network |
US9532211B1 (en) | 2013-08-15 | 2016-12-27 | Sprint Communications Company L.P. | Directing server connection based on location identifier |
US9439025B1 (en) | 2013-08-21 | 2016-09-06 | Sprint Communications Company L.P. | Multi-step mobile device initiation with intermediate partial reset |
US9161209B1 (en) | 2013-08-21 | 2015-10-13 | Sprint Communications Company L.P. | Multi-step mobile device initiation with intermediate partial reset |
US9170870B1 (en) | 2013-08-27 | 2015-10-27 | Sprint Communications Company L.P. | Development and testing of payload receipt by a portable electronic device |
US9143924B1 (en) | 2013-08-27 | 2015-09-22 | Sprint Communications Company L.P. | Segmented customization payload delivery |
US9204239B1 (en) | 2013-08-27 | 2015-12-01 | Sprint Communications Company L.P. | Segmented customization package within distributed server architecture |
US9125037B2 (en) | 2013-08-27 | 2015-09-01 | Sprint Communications Company L.P. | System and methods for deferred and remote device branding |
US10382920B2 (en) | 2013-10-23 | 2019-08-13 | Sprint Communications Company L.P. | Delivery of branding content and customizations to a mobile communication device |
US10506398B2 (en) | 2013-10-23 | 2019-12-10 | Sprint Communications Company Lp. | Implementation of remotely hosted branding content and customizations |
US9743271B2 (en) | 2013-10-23 | 2017-08-22 | Sprint Communications Company L.P. | Delivery of branding content and customizations to a mobile communication device |
US9301081B1 (en) | 2013-11-06 | 2016-03-29 | Sprint Communications Company L.P. | Delivery of oversized branding elements for customization |
US9363622B1 (en) | 2013-11-08 | 2016-06-07 | Sprint Communications Company L.P. | Separation of client identification composition from customization payload to original equipment manufacturer layer |
US9161325B1 (en) | 2013-11-20 | 2015-10-13 | Sprint Communications Company L.P. | Subscriber identity module virtualization |
US9392395B1 (en) | 2014-01-16 | 2016-07-12 | Sprint Communications Company L.P. | Background delivery of device configuration and branding |
US9603009B1 (en) | 2014-01-24 | 2017-03-21 | Sprint Communications Company L.P. | System and method of branding a device independent of device activation |
US9420496B1 (en) | 2014-01-24 | 2016-08-16 | Sprint Communications Company L.P. | Activation sequence using permission based connection to network |
US9426649B2 (en) * | 2014-01-30 | 2016-08-23 | Intel IP Corporation | Apparatus, system and method of securing communications of a user equipment (UE) in a wireless local area network |
US9681251B1 (en) | 2014-03-31 | 2017-06-13 | Sprint Communications Company L.P. | Customization for preloaded applications |
US9426641B1 (en) | 2014-06-05 | 2016-08-23 | Sprint Communications Company L.P. | Multiple carrier partition dynamic access on a mobile device |
US9307400B1 (en) | 2014-09-02 | 2016-04-05 | Sprint Communications Company L.P. | System and method of efficient mobile device network brand customization |
US9992326B1 (en) | 2014-10-31 | 2018-06-05 | Sprint Communications Company L.P. | Out of the box experience (OOBE) country choice using Wi-Fi layer transmission |
US9794727B1 (en) | 2015-03-04 | 2017-10-17 | Sprint Communications Company L.P. | Network access tiered based on application launcher installation |
US9357378B1 (en) | 2015-03-04 | 2016-05-31 | Sprint Communications Company L.P. | Subscriber identity module (SIM) card initiation of custom application launcher installation on a mobile communication device |
US9398462B1 (en) | 2015-03-04 | 2016-07-19 | Sprint Communications Company L.P. | Network access tiered based on application launcher installation |
EP3147843A1 (en) * | 2015-09-25 | 2017-03-29 | Cartadis | Enhanced management of data communication of a transaction between a service terminal and a telephone terminal |
FR3041854A1 (en) * | 2015-09-25 | 2017-03-31 | Cartadis | PERFECTED MANAGEMENT OF A DATA COMMUNICATION OF A TRANSACTION BETWEEN A SERVICE TERMINAL AND A TELEPHONE TERMINAL |
US9913132B1 (en) | 2016-09-14 | 2018-03-06 | Sprint Communications Company L.P. | System and method of mobile phone customization based on universal manifest |
US10021240B1 (en) | 2016-09-16 | 2018-07-10 | Sprint Communications Company L.P. | System and method of mobile phone customization based on universal manifest with feature override |
US10306433B1 (en) | 2017-05-01 | 2019-05-28 | Sprint Communications Company L.P. | Mobile phone differentiated user set-up |
US10805780B1 (en) | 2017-05-01 | 2020-10-13 | Sprint Communications Company L.P. | Mobile phone differentiated user set-up |
Also Published As
Publication number | Publication date |
---|---|
EP1728379A1 (en) | 2006-12-06 |
CN1947408A (en) | 2007-04-11 |
CN1947408B (en) | 2012-05-23 |
ATE521192T1 (en) | 2011-09-15 |
US7415268B2 (en) | 2008-08-19 |
WO2005086468A1 (en) | 2005-09-15 |
JP2007528162A (en) | 2007-10-04 |
EP1728379B1 (en) | 2011-08-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7415268B2 (en) | Method and apparatus to provide charging for ad-hoc service provisioning between trusted parties and between untrusted parties | |
JP5280447B2 (en) | Heterogeneous wireless ad hoc network | |
JP5307836B2 (en) | Method and apparatus for virtual Wi-Fi service with authentication and accounting control | |
CA2481578C (en) | Real-time tiered rating of communication services | |
US7720960B2 (en) | Method and apparatus providing prepaid billing for network services using explicit service authorization in an access server | |
US8005218B2 (en) | Authorization and authentication of user access to a distributed network communication system with roaming feature | |
US20090017789A1 (en) | Point of presence on a mobile network | |
US20060031515A1 (en) | Mobile ad-hoc internet sharing | |
EP2377090B1 (en) | Providing ubiquitous wireless connectivity and a marketplace for exchanging wireless connectivity using a connectivity exchange | |
WO2017059064A1 (en) | Authentication and authorization of mobile devices for usage of access points in an alternative network | |
RU2253187C2 (en) | System and method for local provision of meeting specified regulations for internet service providers | |
JP5631890B2 (en) | Method and apparatus for joining and accessing a connection exchange | |
EP1320236A1 (en) | Access control for network services for authenticating a user via separate link | |
EP2066072B1 (en) | Method and apparatus for facilitating the remuneration for sharing connection resources in multihop networks | |
Tsakountakis et al. | A generic accounting scheme for next generation networks |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: NOKIA CORPORATION, FINLAND Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:TROSSEN, DIRK;REEL/FRAME:015073/0823 Effective date: 20040302 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
AS | Assignment |
Owner name: NOKIA TECHNOLOGIES OY, FINLAND Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NOKIA CORPORATION;REEL/FRAME:035567/0073 Effective date: 20150116 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20200819 |