WO2016149624A1

WO2016149624A1 - Systems and methods for authorizing content and/or features based on detection of a radio device

Info

Publication number: WO2016149624A1
Application number: PCT/US2016/023150
Authority: WO
Inventors: Petri Vesikivi
Original assignee: Pcms Holdings,Inc.
Priority date: 2015-03-18
Filing date: 2016-03-18
Publication date: 2016-09-22

Abstract

Methods, systems, and apparatuses are disclosed for detecting, at a wireless transmit/receive unit (WTRU), a beacon transmitted by a proximate device and determining identifying data associated with the beacon. A request for a token that included the identifying data associated with the beacon may be sent from the WTRU to an authentication device. A token may be received from the authentication device and used to executing an application on the WTRU based on the token. For example, particular content or features may be enabled at the application based on the token.

Description

SYSTEMS AND METHODS FOR AUTHORIZING CONTENT AND/OR FEATURES BASED ON DETECTION OF A RADIO DEVICE

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Patent Application No. 62/135,067, filed on March 18, 2015, which is hereby incorporated by reference as if fully set forth herein.

BACKGROUND

[0002] In recent years, mobile devices of various types (e.g. , smart phones, tablets, etc.) have proliferated as the cost of such devices has steadily been reduced and access to wireless networks that can fully support providing content to such devices has become commonplace. Such mobile devices are often used to access content and/or features, such as webpages, video files, audio files, games, local information (e.g., weather, traffic, flight status, etc.), and other content and features. A content distributor may wish to limit access to content and/or features by mobile devices based on various criteria.

SUMMARY

[0003] Methods, systems, and apparatuses are disclosed for detecting a beacon transmitted by a proximate device and determining identifying data associated with the beacon. A request for a token that included the identifying data associated with the beacon may be sent from the WTRU to an authentication device. A token may be received from the authentication device and used to executing an application on the WTRU based on the token. For example, particular content or features may be enabled at the application based on the token. A token may expire when associated beacons are no longer received and/or when an expiration date or time associated with the token is reached.

BRIEF DESCRIPTION OF THE DRAWINGS

[0004] FIG. 1 is a block diagram of a non-hmiting, exemplary system in which the disclosed subject matter may be implemented.

[0005] FIG. 2 is a block diagram of non-limiting, exemplary data structures that may be used in the disclosed subject matter. [0006] FIG. 3 is a non-limiting, exemplary signal flow diagram that may represent the disclosed subject matter.

[0007] FIG. 4 is a block diagram illustrating a non-limiting, exemplary mobile device in which the disclosed subject matter may be implemented.

[0008] FIG. 5 is a block diagram illustrating exemplary components that may be included in a device in which the disclosed subject matter may be implemented.

[0009] FIG. 6A is a system diagram of an exemplary communications system in which the disclosed subject matter may be implemented.

[0010] FIG. 6B is a system diagram of an exemplary radio access network and an exemplar}' core network that each may be used within a communications system such as that illustrated in FIG. 6A.

[0011] FIG. 6C is a system diagram of another exemplary radio access network and another exemplary core network that each may be used within a communications system such as that illustrated in FIG. 6A.

[0012] FIG. 6D is a system diagram of another exemplary radio access network and another exemplary core network that each may be used within a communications system such as that illustrated in FIG. 6A.

DETAILED DESCRIPTION

[0013] A detailed description of illustrative examples will now be described with reference to the various figures. Although this description provides a detailed example of possible implementations, it should be noted that the details are intended as illustrative examples only and in no way limit the scope of the application.

[0014] Because many, if not most, people now have access to a mobile device on a routine basis, in any setting that includes one or more people, each person present is likely to have at least one mobile device, such as a smart phone and/or a tablet. In some situations, a content provider may desire to provide content and/or access to certain resources to operators of mobile devices that are within a particular geographic area. For example, a content provider may wish to provide Internet access to mobile devices within an area that is limited to attendees of a meeting or conference. In another example, a content provider may wish to provide content to mobile devices within an area mat is accessible only to paid or approved participants, such as within an airplane or at an airport.

[0015] In an embodiment, information that is transmitted wirelessly within a geographical area and detectable by a mobile device may be used to facilitate access to content and/or resources. For example, information provided via a beacon (e.g. , a beacon transmitted by a wireless device, such as a beacon transmitted by a wireless hub or router), a wireless tag transmission (e.g., a radio frequency identification (RFID) tag transmission), and a Bluetooth® device transmission are contemplated as means of providing information wirelessly within a geographical area. Such information may include a Bluetooth® identifier (BHD) (which may be a unique address assigned to a Bluetooth® device, and which may be included in a Bluetooth Low Energy (BLE) beacon), a service set identifier (SSID) associated with a wireless local area network (WLAN) or any other network or network device, an SSID associated with any other wireless device or network, and any other identifier or data that may be detected within a wireless transmission. Any means of providing information wirelessly are contemplated as within the scope of the instant disclosure. For the purposes of this disclosure, any such means of providing information via wireless transmission may be referred to as a 'beacon".

[0016] In an example, content, application features (e.g. , an in-app feature), and/or access to a system and/or data (all of which may be referred to herein as "content") may be provided to a mobile device that may be at a particular location. For example, coupons associated with a particular geographical location (e.g. , a shopping center or shopping mall, an airport, an airplane, etc.) may be provided to a user via an application executing on a mobile device when such a mobile device may be such a geographical location.

[0017] In an embodiment, a token may be used to authorize the presentation and/or access to content and/or features. FIG. 1 illustrates an exemplary system 200 illustrating various devices and elements that may be included in one or more of the disclosed embodiments. In an example, application and/or content provider 250 may register, store, or otherwise provide information to authentication server 240 mat authentication server 240 may associate with identifying information associated with beacon transmission device 210 and/or location information that may be associated with beacon transmission device 210. Other information, such as user identifiers, mobile device identifiers, or any other data that may be associated with mobile device 230 or the like may also, or instead, be provided to authentication server 240. Information regarding particular content, features, etc. that may be provided for a particular location and/or device(s) may also, or instead, be provided, as well as, or instead of, token characteristic information (e.g., lifespan, expiry date/time, etc.). Any combination of such information may be used to generate a token as described herein.

[0018] Beacon transmission device 210, which may be any network device, Bluetooth® device, RFID tag, or any other device capable of wireless communication, may transmit, broadcast, or otherwise make available beacon 220. Beacon 220 may be received or otherwise detected by mobile device 230. In an embodiment, mobile device 230 may operate proximity radio front end 232 to receive or otherwise detect wireless signals, such as a signal that may include beacon 220. Proximity radio front end 232 may represent any number and type of transceivers and/or other components capable of receiving wireless signals.

[0019] Upon receipt or detection of beacon 220, beacon 220 or data contained therein may be provided to aumorization proxy 234. Authorization proxy 234 may be a software component of mobile device 230, a hardware component of mobile device 230, or a combination thereof, and may track and/or otherwise maintain records associated with detected beacons and/or data associated wi th detected beacons, as well as application and/or token data. Such data may include any identifying data as described herein, such as identifying data associated with beacon transmission device 210, data associated with application 236, data associated with application/content provider 250, and/or any other data that may be used to implement a disclosed embodiment.

[0020] Authorization proxy 234 may communicate with authentication server 240, for example, via one or more transceivers and/or other components configured at mobile device 230, such as wireless interface 238. Such communication may be initiated upon execution of an application such as application 236, (e.g., by a user of mobile device 230), in response to receipt of beacon 220 and/or data contained therein, and/or in response to any other criteria that may be detected by authorization proxy 234. Autiiorization proxy 234 may transmit or otherwise provide beacon 220 and/or information associated therewith to authentication server 240, in an example, coupled with or otherwise associated with a request to register application 236 or otherwise allow application 236 to receive, render, or otherwise access content, features, etc., associated with application/content provider 250. In an example, information associated with mobile device 230 and/or a user thereof may also be provided to authentication server 240.

[0021] In response to receiving a request from mobile device 230 for access to content, features, etc., associated with application/content provider 250, in an embodiment originating at authorization proxy 234, authentication server 240 may determine if identifying data (e.g., associated with beacon 220 and/or mobile device 230) provided with such a request is associated with a token stored or otherwise obtainable by authentication server 240.

Alternatively, authentication server 240 may determine if such identifying is associated with a data stored or otherwise obtainable by authentication server 240 that permits authentication server 240 to generate a token that may be used by mobile device 230 to access content, features, etc.

[0022] Note that tokens as contemplated herein may grant, or restrict, access to any portion or all of any content and/or features that may be provided by application/content provider 250. For example, a token provided by authentication server 240 may grant access to a particular portion of content that may be associated with a particular location (e.g., that may be associated with identifying information contained within or represented by beacon 220).

[0023] If authentication server 240 determines that information associated with a request received from mobile device 230 permits authentication server 240 to generate or otherwise provide a token that may be used to access content, features, etc. provided by application/content provider 250, authentication server 240 may respond by transmitting or otherwise providing such a token to mobile device 230.

[0024] Upon receipt or detection of such a token, mobile device 230, in an example using authorization proxy 234 configured at mobile device 230, may store the token or data associated therewith.

[0025] Mobile device 230, upon determining a user intention to access content, features, etc. provided by or otherwise associated with application/content provider 250, may query authorization proxy 234 to determine whether such access is permitted. For example, upon initiation of execution of application 236, mobile device 230 may query authorization proxy 234 to determine whether access to content available via application 236 is permitted. In another example, authorization proxy 234 may automatically determine whether access to content available via application 236 is permitted in response to detecting beacon 220 and/or information associated therewith, and may provide authorizing data (e.g., a token) to application 236 upon determination that such access is permitted.

[0026] If application 236 determines, via a query to authorization proxy 234, an evaluation of a token, or otherwise, that the user-requested content, features, etc. are permitted, application 236 may provide such content, features, etc. to the user, for example by rendering content on a display of mobile device 230, playing audio on mobile device 230, enabling features of application 236 on mobile device 230, otherwise providing access to content, features, etc. associated with application/content provider 250, or any combination thereof.

[0027] Note that tokens as disclosed herein may include various parameters and/or data that may affect their use. For example, a token may include an expiration time, after which the token may not be used to access content, features, etc. A token may include a lifespan indicating how long a token may be active after a specified time (such as time of receipt of the token), which, after an application determines that such a lifespan has expired, may render the token unable to access content, features, etc.

[0028] Various data, such as "flags", may also be used to indicate to an authorization proxy and/or an application that a token has certain characteristics or limitations. For example, a token may include a "transient flag" or other transience indicator that may indicate to an authorization proxy and/or an application to determine periodically and/or upon detection of an event whether the identifying information associated with the token remains valid. For example, a token may include a flag mat, upon detection, causes an authorization proxy and/or an application to periodically determine whether identifying information associated with the token is still being detected by the mobile device (e.g., whether a beacon with such identifying information is currently being detected), hi another example, a token may include a flag that, upon detection, causes an authorization proxy and/or an application to determine whether identifying information associated with the token is still being detected by the mobile device when the user attempts to access additional content (e.g., whether a beacon with such identifying information is being detected when the user requests access to additional content).

[0029] FIG. 2 illustrates non-limiting exemplary entity relationship diagram 300 (e.g., a data model) that may represent a relationship between content, features, etc. and information that may be used to determine whether to generate a token and association with tokens. An authentication server (e.g., authentication server 240 of FIG. 1) may include a database and/or a storage component that may store and/or organize data in a manner that may be represented by diagram 300.

[0030] For example, an aumentication server may include a table mat may be represented by diagram 300. Such a table may include application information entity 320 that may include application data 322 associated with one or more application (e.g., application name, application description, etc.). Application data 322 may include entries for one or more applications, where each entry includes information associated with an application.

[0031] One or more tokens may be represented at token information entity 330 that may be include tokens 332 representing one or more tokens. Each of tokens 332 may be associated with one or more of application data entries of application data 322.

[0032] Each of tokens 332 may be associated with one or more entries of beacon data 342 represented by beacon information entity 340. Such relationships may be associated with device and/or network identifiers associated with beacons and/or the transmitters thereof, and/or any other beacon transmitter characteristics.

[0033] Each entry of beacon data 342 may be associated with location data 352 represented by location information entity 350. Each entry of location data 352 may be associated with a particular location, which may be specified using any location-identifying means. In an example, locations may be fixed, such as where a beacon is transmitted by a device that is affixed to a physical location. In another example, locations may vary, and may be updated periodically or as appropriate, such as where a beacon is transmitted by a mobile device. Any combination of these is contemplated by the instant disclosure.

[0034] FIG. 3 illustrates exemplary signal flow 400 that may represent a signal flow used in an example for authorizing and/or authenticating access to content, features, etc. At 451, application/content provider 440 may send a message, request, or other indication of desired registration of an application, feature, or content, and/or generation of a token associated therewith, to authentication server 430. Request 451 may include data indicating the permitted features, content, and/or other access that may be permitted by use of the requested token as well as any associated application(s). Request 451, and any other associated communications, may include any of a {e.g., unique) token identifier, identifier(s) of associated content, application, features, etc., a token expiration time, date, and/or condition, and any other information that may be associated with a token and/or associated content, application, features, etc.

[0035] Authentication server 430, may, e.g. , upon deteimining that

application/content provider 440 may be permitted to initiate the generation of a token, transmit 452 a token to application/content provider 440 that may be used to confirm that mobile devices are permitted to access content, features, etc.

[0036] In an example, appUcation/content provider 440 may not be capable of detennining tokens and/or associated data because application/content provider 440, for example, may not have access to identifying information associated with beacon transmission device 410. In such an example, a token may not be provided to application/content provider 440.

[0037] A token may include a token identifier, a token name, an application name, an expiry date and/or time, a lifespan, and/or the like.

[0038] In an example where authentication server 430 may provide a token to application/content provider 440, apphcation/content provider 440 may indicate to authentication server 430 {e.g., in a subsequent message) content and/or one or more features that

application/content provider 440 desires to authorize for use at an application that provides an appropriate token.

[0039] In an example, a token may be associated with an identifier of a device or entity configured at a particular geographical location. For example, a token may be associated with a BTID (in an embodiment, that may be provided by a BLE beacon), an SSID associated with a WLAN or other network device, an RFID, etc. Such an association may be indicated and/or stored at either or both of application/content provider 440 and authentication server 430. [0040] In an example, a beacon and/or associated data may be transmitted 453 by beacon transmission device 410, which may be any device or entity capable of transmitting or causing the transmission of a beacon. Such a beacon may be detected by authorization proxy 422 that may be configured at mobile device 420. A request for a token may be sent 454 by authorization proxy 422 to authentication server 430. Such a request may include any information determined from or otherwise associated with the beacon detected at 453, such as identifying information associated with a ΒΉϋ, an SSID associated with a WLAN or other network device, an RFID, etc. Authorization proxy 422 may request a token 454 in response to user manipulation of an application executing on mobile device 420, such as application 424, in response to detecting a beacon 453, or based on any other trigger, mechanism, or instruction. Request 454 may include any type of beacon identification information or data associated with beacon transmission device 410 as described herein, as well as any device, user, application, content, or feature data, or any other data or information associated therewith that authentication server 430 may use to determine a response to request 454. Authentication server 430 may, in response to token request 454, generate or otherwise determine token data, for example, by determining a token that is associated with beacon identification information or data associated with beacon transmission device 410. Any other criteria may also, or instead, by used to determine appropriate token data in response to token request 454. Token data may be transmitted 455 by authentication server 430 to authorization proxy 422. Authorization proxy 422 may store token data, in an example, until some expiration criteria is met or until some other mechanism instructs authorization proxy 422 to delete token data.

[0041] Application 424 may be initiated or otherwise manipulated, e.g. , by a user, and may request 455 token data. Such a request may include information that may be used by authorization proxy to determine if a token is available, such as an application identifier, feature identifier, content identifier, etc. Authorization proxy 422 may determine whether an appropriate token(s) or token data is available based on the request received at 456, and if so, may response 457 with a token(s) or token data. Having the appropriate token or token, application 424 may provide the associated content, features, etc. at 470, for example by accessing or unlocking content, features, etc. using data based on the received token or token data.

[0042] In an example, access to content, features, etc. may be limited by time, location, or any other criteria. At 458, authorization proxy 422 may determine whether the token or token data provided at 457 has expired or is no longer valid for any reason. For example, a time limit may have been reached or authorization proxy 422 may be no longer receiving beacons associated with the token or token data (which may indicate that mobile device 420 has moved outside of a geographical area within which access to the token's associated content, features, etc. is permitted). If authorization proxy 422 determines that the token or token data has expired or is otherwise no longer valid, authorization proxy 422 may transmit 459 an instruction to application 424 to remove or otherwise disable the token or token data, thereby preventing application 424 from continuing to provide access to the content, features, etc.

associated with the token or token data. Authorization proxy 422 may delete any token data associated with a token that has expired or is otherwise no longer valid.

[0043] In an example, authorization proxy 422 may periodically, or contingent on some criteria (e.g., receipt of a subsequent beacon), query authentication server 430 to determine if a token is still valid, and if not send instruction 459 to application 424 to disable access to the content, features, etc. associated with the token or token data. Such a query may also, or instead, query autiientication server 430 regarding any changes to a token or token data, or whether a new token or token data may be needed. If any such changed exist, authorization proxy 422 may adjust the token or data provided to application 424 accordingly.

[0044] In an example, application/content provider 440 may alter a token and/or data associated therewith such that the token or token data may allow different access or authorization than the previously provided token or token data. Such alterations may include changes to associated content, features, etc. Altered or replacement token or token data may be provided 461 to authentication server 430, application 424, and/or authorization proxy 422.

[0045] In an example, a token or token data may be generated or created based on information such as a user identifier, a device identifier, a beacon identifier, or other data such that the token or token data may linked or otherwise associated with one or more particular beacons or devices that transmit beacons. As such, a token may contain any such data.

[0046] FIG. 4 depicts exemplary WTRU 802. WTRU 802 may be used in one or more of the communications systems described herein. As shown in FIG. 4, WTRU 802 may include processor 818, transceiver 820, transmit/receive element 822, speaker/microphone 824, keypad 826, display/touchpad 828, non-removable memory 830, removable memory 832, power source 834, global positioning system (GPS) chipset 836, and other peripherals 838. It should be appreciated that the WTRU 802 may include any sub-combination of the foregoing elements while remaining consistent with the disclosed subject matter.

[0047] Processor 818 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of

microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. Processor 818 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables WTRU 802 to operate in a wireless environment. Processor 818 may be coupled to transceiver 820, which may be coupled to transmit/receive element 822. While FIG. 4 depicts processor 818 and transceiver 820 as separate components, it should be appreciated that processor 818 and transceiver 820 may be integrated together in an electronic package or chip.

[0048] Transmit/receive element 822 may be configured to transmit signals to, or receive signals from, a base station (e.g. , base station 114a or 114b of FIG. 6A) over air interface 115/116/117 (described in more detail in regard to FIGs. 10A-10D). For example, in one example, transmit/receive element 822 may be an antenna configured to transmit and/or receive RF signals. In another example, transmit/receive element 822 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example. In yet another example, transmit/receive element 822 may be configured to transmit and receive both RF and light signals. It should be appreciated that transmit/receive element 822 may be configured to transmit and/or receive any combination of wireless signals.

[0049] In addition, although transmit/receive element 822 is depicted in FIG. 4 as a single element, WTRU 802 may include any number of transmit/receive elements 822. More specifically, WTRU 802 may employ MIMO technology. Thus, in one example, WTRU 802 may include two or more transmit/receive elements 822 (e.g., multiple antennas) for transmitting and receiving wireless signals over air interface 115/116/117.

[0050] Transceiver 820 may be configured to modulate the signals that are to be transmitted by transmit/receive element 822 and to demodulate the signals that are received by transmit/receive element 822. As noted above, WTRU 802 may have multi-mode capabilities. Thus, transceiver 820 may include multiple transceivers for enabling WTRU 802 to

communicate via multiple RATs, such as UTRA and IEEE 802.11, for example.

[0051] Processor 818 of WTRU 802 may be coupled to, and/or may receive user input data from, speaker/microphone 824, keypad 826, and/or display/touchpad 828 (e.g., a liquid crystal display (LCD) display unit or an organic light-emitting diode (OLED) display unit). Processor 818 may also output user data to speaker/microphone 824, keypad 826, and/or display/touchpad 828. In addition, processor 818 may access information from, and/or store data in, any type of suitable memory, such as non-removable memory 830 and/or removable memory 832. Non-removable memory 830 may include random-access memory (RAM), read-only memory (ROM), a hard disk, and/or any other type of memory storage device. Removable memory 832 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and/or the like. In other examples, processor 818 may access information from, and store data in, memory that is not physically located on WTRU 802, such as on a server or a home computer.

[0052] Processor 818 may receive power from power source 834, and may be configured to distribute and/or control power to other components in WTRU 802. Power source 834 may be any suitable device for powering WTRU 802. For example, power source 834 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and/or the like.

[0053] Processor 818 may also be coupled to GPS chipset 836, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of WTRU 802. In addition to, or in lieu of, information from GPS chipset 836, WTRU 802 may receive location information over air interface 115/116/117 from a base station (e.g., base station 114a or 114b of FIG. 6A) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It should be appreciated that WTRU 802 may acquire location information by way of any suitable location-determination method while remaining consistent with an example.

[0054] Processor 818 may further be coupled to other peripherals 838, which may include one or more software and/or hardware modules that provide additional features, functionality, and/or wired or wireless connectivity. For example, peripherals 838 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, and/or the like.

[0055] FIG. 5 depicts a block diagram of one or more components or additional components that may be included in device/computing system 900 that may be a device such as a mobile device, a tablet, an authentication server, a group server, and/or the like as described herein. The components of device/computing system 900 may be capable of executing a variety of computing applications represented in FIG. 5 as application 980. Application 980 may be stored in storage component 975 (and/or RAM or ROM described herein). Application 980 may include a computing application, a computing applet, a computing program and/or other instruction set operative on device/computing system 900 to perform at least one function, operation, and/or procedure as described herein. According to an example, computing applications may include the methods and/or applications described herein. Device/computing system 900 may be controlled primarily by computer-readable instructions that may be in the form of software. Such computer-readable instructions may include instructions for storing and/or accessing computer-readable instructions. Such computer-readable instructions may be executed within processor 910, which may be one or more central processing units (CPUs) and/or one or more other processors, such as a coprocessor to cause the device to perform the processes or functions associated therewith. Processor 910 may be implemented by microelectronic chip CPUs that may be referred to as microprocessors. In operation, processor 910 may fetch, decode, and/or execute instructions and/or may transfer information to and from other resources via interface 905, which may be, e.g., a main data transfer path or a system bus. Such an interface or system bus may connect components in a device and may define the medium for data exchange. Device/computing system 900 may include memory devices coupled to interface 905. According to an exemplary embodiment, memory devices may include random access memory (RAM) 925 and/or read only memory (ROM) 930. RAM 925 and ROM 930 may include circuitry that allows information to be stored and retrieved. ROM 930 may include stored data that cannot be modified. Data stored in the RAM 925 may be read and/or changed by processor 910 and/or other hardware devices. Access to the RAM 925 and/or ROM 930 may be controlled by memory interface/controller 920. Memory interface/controller 920 may provide an address translation function mat translates virtual addresses into physical addresses as instructions are executed.

[0056] Device 900 may include peripheral/interface controller 935 that may be responsible for communicating instructions from processor 910 to peripherals such as a printer, a keypad, a keyboard, a mouse, and/or a storage component. Device/computing system 900 may further include display and display interface/controller 965 (shown as a combined component in FIG. 5 that includes both a display and a display interface/controller, but is contemplated in other embodiments to be any number of separate components). Display and display

interface/controller 965 may be used to display visual output generated by device/computing system 900. Such visual output may include text, graphics, animated graphics, video, and the like. A display controller associated with a display may include electronic components that generate a video signal that may be sent to a display. De\ice/∞mputing system 900 may include network interface/controller 970 (e.g., a network adapter) that may be used to connect device/computing system 900 to an external communication network and/or other devices.

[0057] FIG. 6A is a diagram of example communications system 100 in which one or more disclosed features may be implemented. For example, a wireless network (e.g., a wireless network comprising one or more components of the communications system 100) may be configured such that bearers that extend beyond the wireless network (e.g. , beyond a walled garden associated with the wireless network) may be assigned QoS characteristics.

[0058] The communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the conununications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), and the like.

[0059] As shown in FIG. 6A, the communications system 100 may include at least one wireless transmit/receive unit (WTRU), such as a plurality of WTRUs, for instance WTRUs 102a, 102b, 102c, and 102d, a radio access network (RAN) 104, a core network 106, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it should be appreciated that the disclosed subject matter contemplates any number of WTRUs, base stations, networks, and/or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals and may include user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, consumer electronics, and the like.

[0060] The communications systems 100 may also include a base station 114a and a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the core network 106, the Internet 110, and/or the networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it should be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.

[0061] The base station 114a may be part of the RAN 104, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and/or the base station 1 14b may be configured to transmit and/or receive wireless signals within a particular geographic region, which may be referred to as a cell (not shown). The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one example, the base station 114a may include three transceivers, e.g., one for each sector of the cell. In another example, the base station 114a may employ multiple-input multiple output (MIMO) technology and, therefore, may utilize multiple transceivers for each sector of the cell.

[0062] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0063] More specifically, as noted above, the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station 114a in the RAN 104 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 116 using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink Packet Access (HSDPA) and/or High-Speed Uplink Packet Access (HSUPA).

[0064] In another example, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and/or LTE- Advanced (LTE- A).

[0065] In other examples, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.16 (e.g., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

[0066] The base station 114b in FIG. 6A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, and the like. In one example, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In another example, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another example, the base station 114b and the WTRUs 102c, 102d may utilize a cellular- based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or femtocell. As shown in FIG. 6A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 1 14b may not be required to access the Internet 110 via the core network 106.

[0067] The RAN 104 may be in communication with the core network 106, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. For example, the core network 106 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high- level security functions, such as user authentication. Although not shown in FIG. 6A, it should be appreciated that the RAN 104 and/or the core network 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT. For example, in addition to being connected to the RAN 104, which may be utilizing an E- UTRA radio technology, the core network 106 may also be in communication with another RAN (not shown) employing a GSM radio technology.

[0068] The core network 106 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or other networks 112. The PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and the internet protocol (IP) in the TCP/IP internet protocol suite. The networks 112 may include wired or wireless

communications networks owned and/or operated by other service providers. For example, the networks 112 may include another core network connected to one or more RANs, which may employ the same RAT as the RAN 104 or a different RAT.

[0069] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities, e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links. For example, the WTRU 102c shown in FIG. 6A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0070] FIG. 6B depicts a system diagram that includes RAN 103 and core network 106. RAN 103 may employ a UTRA radio technology to communicate with WTRUs 102a, 102b, 102c over air interface 115. RAN 103 may be in communication with core network 106. As shown in FIG. 6B, RAN 103 may include Node-Bs 140a, 140b, and/or 140c, each of which may include one or more transceivers for communicating with t WTRUs 102a, 102b, 102c over air interface 115. Node-Bs 140a, 140b, 140c may each be associated with a particular cell within RAN 103. RAN 103 may also include RNCs 142a and/or 142b. It will be appreciated that RAN 103 may include any number of Node-Bs and RNCs while remaining consistent with an embodiment.

[0071] Node-Bs 140a and 140b may be in communication with RNC 142a while Node-B 140c may be in communication with RNC142b. Node-Bs 140a, 140b, and/or 140c may communicate with the respective RNCs 142a and 142b via an Iub interface. RNCs 142a, 142b may be in communication with one another via an Iur interface. Each of RNCs 142a, 142b may be configured to control Node-Bs 140a, 140b, and/or 140c to which it is connected. Each of RNCs 142a, 142b may be configured to carry out or otherwise support other functionality, such as outer loop power control, load control, admission control, packet scheduling, handover control, macrodiversity, security functions, data encryption, and the like.

[0072] Core network 106 shown in FIG. 6B may include media gateway (MGW) 144, mobile switching center (MSC) 146, serving GPRS support node (SGSN) 148, and/or gateway GPRS support node (GGSN) 150. While each of the foregoing elements are depicted as part of the core network 106, it will be appreciated that any one of these elements may be owned and/or operated by an entity other than a core network operator.

[0073] RNC 142a in RAN 103 may be connected to the MSC 146 in core network 106 via an IuCS interface. MSC 146 may be connected to MGW 144. MSC 146 and MGW 144 may provide WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as PSTN 108, to facilitate communications between WTRUs 102a, 102b, 102c and traditional land-line conununications devices.

[0074] RNC 142a in RAN 103 may also be connected to SGSN 148 in core network 106 via an IuPS interface. SGSN 148 may be connected to GGSN 150. SGSN 148 and GGSN 150 may provide WTRUs 102a, 102b, 102c with access to packet-switched networks, such as Internet 110, to facilitate communications between WTRUs 102a, 102b, 102c and IP-enabled devices.

[0075] Core network 106 may also be connected to other networks 112 that may include other wired and/or wireless networks that may be owned and/or operated by other service providers.

[0076] FIG. 6C depicts a system diagram of RAN 104 and core network 107. RAN 104 may employ an E-UTRA radio technology to communicate with WTRUs 102a, 102b, 102c over air interface 116. RAN 104 may be in communication with core network 107.

[007η RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that RAN 104 may include any number of eNode-Bs while remaining consistent with the contemplated embodiments. eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over air interface 116.

eNode-Bs 160a, 160b, 160c may implement MIMO technology. eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, WTRU 102a.

[0078] Each of eNode-Bs 160a, 160b, 160c may be associated with a particular cell and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink and/or downlink, and the like. eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.

[0079] Core network 107 may include mobility management gateway (MME) 162, serving gateway 164, and/or packet data network (PDN) gateway 166. While each of these elements are depicted as part of core network 107, it will be appreciated that any or all of these elements may be owned and/or operated by an entity other than the core network operator.

[0080] MME 162 may be connected to each of eNode-Bs 160a, 160b, 160c in RAN 104 via an SI interface and may serve as a control node. For example, MME 162 may be responsible for authenticating users of WTRUs 102a, 102b, 102c, bearer

activatiori/deactivation, selecting a particular serving gateway during an initial attach of WTRUs 102a, 102b, 102c, and the like. MME 162 may provide control plane functions for switching between RAN 104 and other RANs mat may employ other radio technologies, such as GSM or WCDMA.

[0081] Serving gateway 164 may be connected to each of eNode-Bs 160a, 160b, 160c in RAN 104 via an S 1 interface. Serving gateway 164 may route and/or forward user data packets to/from WTRUs 102a, 102b, 102c. Serving gateway 164 may perform functions such as anchoring user planes during inter-eNode-B handovers, triggering paging when downlink data is available for WTRUs 102a, 102b, 102c, managing and storing contexts ofWTRUs 102a, 102b, 102c, and the like.

[0082] Serving gateway 164 may also be connected to PDN gateway 166, which may provide WTRUs 102a, 102b, 102c with access to packet-switched networks, such as Internet 110, to facilitate communications between WTRUs 102a, 102b, 102c and IP-enabled devices.

[0083] Core network 107 may facilitate communications with other networks. For example, core network 107 may provide WTRUs 102a, 102b, 102c with access to circuit- switched networks, such as PSTN 108, to facilitate communications between WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, core network 107 may include, and/or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that may serve as an interface between core network 107 and PSTN 108. Core network 107 may provide WTRUs 102a, 102b, 102c with access to networks 112, which may include other wired and/or wireless networks that may be owned and/or operated by other service providers.

[0084] FIG. 6D depicts a system diagram of RAN 105 and core network 109. RAN 105 may be an access service network (ASN) that may employ IEEE 802.16 radio technology to communicate with WTRUs 102a, 102b, 102c over air interface 117. The communication links between the different functional entities of WTRUs 102a, 102b, 102c, RAN 105, and core network 109 may be defined as reference points.

[0085] RAN 105 may include base stations 180a, 180b, and/or 180c and ASN gateway 182, though it will be appreciated that RAN 105 may include any number of base stations and/or ASN gateways while remaining consistent with the contemplated embodiments.

[0086] Base stations 180a, 180b, 180c may each be associated with a particular cell in RAN 105 and/or may each include one or more transceivers for communicating with WTRUs 102a, 102b, 102c over air interface 117. Base stations 180a, 180b, and/or 180c may implement MIMO technology. Thus, base station 180a, for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, WTRU 102a. Base stations 180a, 180b, 180c may also provide mobility management functions, such as handoff triggering, tunnel establishment, radio resource management, traffic classification, quality of service (QoS) policy enforcement, and the like. ASN gateway 182 may serve as a traffic aggregation point and/or may be responsible for paging, caching of subscriber profiles, routing to core network 109, and the like.

[008η Air interface 117 between WTRUs 102a, 102b, 102c and RAN 105 may be defined as an Rl reference point that may implement the IEEE 802.16 specification. Each of WTRUs 102a, 102b, 102c may establish a logical interface with core network 109 that may be defined as an R2 reference point. Such an R2 reference point may be used for authentication, authorization, IP host configuration management, and/or mobility management.

[0088] A communication link between each of base stations 180a, 180b, 180c may be defined as an R8 reference point that may include protocols for facilitating WTRU handovers and/or the transfer of data between base stations. The communication link between base stations 180a, 180b, 180c and ASN gateway 182 may be defined as an R6 reference point. An R6 reference point may include protocols for facilitating mobility management based on mobility events associated with each of WTRUs 102a, 102b, 102c.

[0089] RAN 105 may be connected to core network 109. A communication link between RAN 105 and core network 109 may defined as an R3 reference point that may include protocols for facilitating data transfer and mobility management capabilities, for example. Core network 109 may include mobile IP home agent (MIP-HA) 184, authentication, authorization, accounting (AAA) server 186, and/or gateway 188. While each of the foregoing elements are depicted as part of core network 109, it will be appreciated that any one of these elements may be owned and/or operated by an entity other than the core network operator.

[0090] MIP-HA 184 may be responsible for IP address management and may enable WTRUs 102a, 102b, 102c to roam between different ASNs and/or different core networks. MIP- HA 184 may provide WTRUs 102a, 102b, 102c with access to packet-switched networks, such as Internet 110, to facilitate communications between WTRUs 102a, 102b, 102c and IP-enabled devices. AAA server 186 may be responsible for user authentication and for supporting user services. Gateway 188 may facilitate interworking with other networks. For example, gateway 188 may provide WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as PSTN 108, to facilitate communications between WTRUs 102a, 102b, 102c and traditional land- line communications devices. Gateway 188 may provide WTRUs 102a, 102b, 102c with access to networks 112, which may include other wired and/or wireless networks that may be owned and/or operated by other service providers.

[0091] It will be appreciated by those skilled in the art that RAN 105 may be connected to one or more other ASNs and core network 109 may be connected to one or more other core networks. A communication link between RAN 105 other ASNs may be defined as an R4 reference point, which may include protocols for coordinating the mobility of WTRUs 102a, 102b, 102c between RAN 105 and other ASNs. A communication link between core network 109 and other core networks may be defined as an R5 reference, which may include protocols for facilitating interworking between home core networks and visited core networks. [0092] Although the terms device, server, and/or the like may be used herein, it may and should be understood that the use of such terms may be used interchangeably and, as such, may not be distinguishable.

[0093] Further, although features and elements are described above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor.

Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

[0094] Although the features and elements described this disclosure are described using particular examples in particular combinations, each feature and element set forth herein may be used alone without the other features and/or elements of any of die disclosed examples. Each feature and element set forth herein may also be used with any one or more of the other features and/or elements of any of the disclosed examples.

[0095] While the instant disclosure may refer to an IEEE 802.11 specification and/or a subset thereof, the disclosed examples and description are not limited to systems, methods, or applications that implement, or are otherwise associated with, any aspect of the IEEE 802.11 specification.

Claims

CLAIMS What is claimed is:

1. A method comprising:

detecting, at a wireless transmit/receive unit (WTRU), a beacon transmitted by a proximate device;

determining, at the WTRU, identification data associated with the beacon;

transmitting, from the WTRU, a request for a token to an authentication device, wherein the request for the token comprises the identification data associated with the beacon;

receiving the token from the authentication device at the WTRU; and

executing an application on the WTRU based on the token.

2. The method of claim 1, wherein executing the application based on the token comprises enabling presentation of content by the application based on the token.

3. The method of claim 1, wherein executing the application based on the token comprises enabling an application feature of the application based on the token.

4. The method of claim 1, wherein the proximate device is one of a wireless local area network (WLAN) device, a Bluetooth® device, or a radio frequency identification (RFID) tag.

5. The method of claim 1, further comprising:

determining that the token has expired; and

ceasing execution of the application based on the token.

6. The method of claim 1, further comprising:

determining that the token has expired; and

deleting the token from the WTRU.

7. The method of claim 1, wherein the token comprises at least one of an expiration date, an expiration time, a transience indicator, a lifespan, a content identifier, an application identifier, or a feature identifier.

8. The method of claim 1 , wherein transmitting the request for the token to the authentication device comprises:

detecting execution of the application on the WTRU; and

in response to detecting the execution of the application on the WTRU, transmitting the request for the token to the authentication device comprises.

9. The method of claim 1 , wherein transmitting the request for the token to the authentication device comprises:

detecting a selection of content at the application executing on the WTRU; and in response to detecting the selection of the content at the application executing on the WTRU, transmitting the request for the token to the authentication device comprises.

10. The method of claim 1 , wherein transmitting the request for the token to the authentication device comprises:

detecting a selection of a feature at the application executing on the WTRU; and in response to detecting the selection of the feature at the application executing on the WTRU, transmitting the request for the token to the authentication device comprises.

11. A wireless transmit/receive unit (WTRU) comprising:

a transceiver configured to:

detect a beacon transmitted by a proximate device,

transmit a request for a token to an authentication device, wherein the request for the token comprises identification data associated with the beacon, and

receive the token from the authentication device; and

a processor configured:

determine the identification data associated with the beacon, and execute an application based on the token.

12. The WTRU of claim 11, wherein the processor configured to execute the application based on the token comprises the processor configured to enable presentation of content by the application based on the token.

13. The WTRU of claim 11 , wherein the processor configured to execute the application based on the token comprises the processor configured to enable an application feature of the application based on the token.

14. The WTRU of claim 11, wherein the proximate device is one of a wireless local area network (WLAN) device, a Bluetooth® device, or a radio frequency identification (RFID) tag.

15. The WTRU of claim 11, wherein the processor is further configured to:

determine that the token has expired; and

cease execution of the application based on the token.

16. The WTRU of claim 11, wherein the processor is further configured to:

determine that the token has expired; and

delete the token from the WTRU.

17. The WTRU of claim 11 , wherein the token comprises at least one of an expiration date, an expiration time, a transience indicator, a lifespan, a content identifier, an application identifier, or a feature identifier.

18. The WTRU of claim 11 , wherein the transceiver configured to transmit the request for the token to the authentication device comprises:

the processor configured to detect execution of the application; and

in response to detecting the execution of the application, the transceiver configured to transmit the request for the token to the authentication device.

19. The WTRU of claim 11, wherein the transceiver configured to transmit the request for the token to the authentication device comprises:

the processor configured to detect a selection of content at the application; and in response to detecting the selection of the content at the application, the transceiver configured to transmit the request for the token to the authentication device.

20. The WTRU of claim 11 , wherein the transceiver configured to transmit the request for the token to the authentication device comprises:

the processor configured to detect a selection of a feature at the application; and in response to detecting the selection of the feature at the application, the transceiver configured to transmit the request for the token to the authentication device.