Techniques to associate user data with a mobile device.
Abstract
Techniques to associate user data with a mobile device are described. In one embodiment, for example, an apparatus may comprise a service support component and a storage component. The services support component may be operative to receive a data package request from a service, the data package request comprising a network identifier for a mobile device associated with a user, and exchange a data package with the service in response to the data package request. The storage component may be operative to access the data package associated with the user based on the network identifier. Other embodiments are described and claimed. Other embodiments are described and claimed.

Term
No projected expiry on record.
- Priority
- Filed
- Granted
- Today
20 claims: 3 independent, 17 dependent
- 1CLAIMS REIVINDICACIONES 1. - Un método implementado por computadora, que comprende:one. - A method implemented by computer, comprising: receive, on a server, a request for a data packet from an entity other than the server that provides an online service to a mobile device associated with a user or an in-person service to the user associated with the mobile device, the request for a packet of data comprises a network identifier for the mobile device;recibir, en un servidor, una solicitud de paquete de datos desde una entidad distinta del servidor que proporciona un servicio en línea a un dispositivo móvil asociado con un usuario o un servicio en persona al usuario asociado con el dispositivo móvil, la solicitud de paquete de datos comprende un identificador de red para el dispositivo móvil;recuperar, por un circuito de procesador en el servidor distinto de la entidad, un paquete de datos asociado con el usuario con base en el identificador de red, el paquete de datos comprende una cookie móvil que incluye información de configuración para configurar una transacción web del Protocolo de Transporte de Hipertexto (HTTP);y transmitir, mediante el servidor distinto de la entidad, el paquete de datos a la entidad en respuesta a la solicitud de paquete de datos. retrieving, by a processor circuit on the server other than the entity, a data package associated with the user based on the network identifier, the data package comprises a mobile cookie that includes configuration information to configure a web transaction of the Hypertext Transport Protocol (HTTP);and transmit, via the server other than the entity, the data packet to the entity in response to the request for the data packet.
- 8- An apparatus, comprising:8. - Un aparato, que comprende: a processor circuit in a server device;un circuito de procesador en un dispositivo servidor;an operating services compatibility component in the processor circuit for receiving a data packet request from an entity that provides an online service to a mobile device associated with a user or an in-person service to the user associated with the mobile device, the Data packet request comprises a network identifier for the mobile device, the entity being distinct from the server device, and transmitting the data packet to the entity in response to the request for a data packet, the data packet comprises a mobile cookie that includes configuration information to configure a web transaction of the Hypertext Transport Protocol (HTTP);and an operative storage component in the processor circuit to retrieve the data packet associated with the user based on the network identifier. un componente de compatibilidad de servicios operativo en el circuito procesador para recibir una solicitud de paquete de datos desde una entidad que proporciona un servicio en línea a un dispositivo móvil asociado con un usuario o un servicio en persona al usuario asociado con el dispositivo móvil, la solicitud de paquete de datos comprende un identificador de red para el dispositivo móvil, la entidad siendo distinta del dispositivo servidor, y transmitir el paquete de datos a la entidad en respuesta a la solicitud de paquete de datos, el paquete de datos comprende una cookie móvil que incluye información de configuración para configurar una transacción web del Protocolo de Transporte de Hipertexto (HTTP);y un componente de almacenamiento operativo en el circuito de procesador para recuperar el paquete de datos asociado con el usuario con base en el identificador de red.
- 15- Un medio de almacenamiento legible por computadora que provoca que un sistema:fifteen. - A computer readable storage medium that causes a system to: receive, on a server, a request for a data packet from an entity other than the server that provides an online service to a mobile device associated with a user or an in-person service to the user associated with the mobile device, the request for a packet of data comprises a network identifier for the mobile device;reciba, en un servidor, una solicitud de paquete de datos desde una entidad distinta del servidor que proporciona un servicio en línea a un dispositivo móvil asociado con un usuario o un servicio en persona al usuario asociado con el dispositivo móvil, la solicitud de paquete de datos comprende un identificador de red para el dispositivo móvil;recupere un paquete de datos asociado con el usuario con base en el identificador de red, el paquete de datos comprende una cookie móvil que incluye información de configuración para configurar una transacción web del Protocolo de Transporte de Hipertexto (HTTP), la recuperación se realiza por un servidor distinto de la entidad;y transmita, mediante el servidor distinto de la entidad, el paquete de datos a la entidad en respuesta a la solicitud de paquete de datos. retrieve a data packet associated with the user based on the network identifier, the data packet comprises a mobile cookie that includes configuration information to configure a web transaction of the Hypertext Transport Protocol (HTTP), the recovery is performed by a server other than the entity;and transmit, through the server other than the entity, the data packet to the entity in response to the request for the data packet.
Independent claims3
178 paragraphs in 3 sections, as filed
DIVISIONAL SUB-DIRECTOR OF PATENT FUND EXAMINATION OF MECHANICAL, ELECTRICAL AND INDUSTRIAL DESIGNS AND USEFUL MODELS
PEDRO DAVID FRAGOSO LÓPEZ
<img file="MX366183B_D0001.tif" />
Original string:
PEDRO DAVID FRAGOSO LOPEZ | 00001000000405457619 | Administration Service
Tax ^ 052 || MX / 2019/60769 | MX / a / 2017/006667 | PCT patent title | 1048 | SEF | Page (s) | HI5jMaNJjHm5oA9zmB8hKU8VhmU =
Digital stamp:
bv ++ hHepPGkr1YdsATRj + LGpwAZC056Q + xkUy2oDU9OBLQ62tdgC8P78 / 1aNQ2V5i9EAUBUjapalkgWpU / oD / + AnUg
XzjHgqzoOWaZZ / XhEb4m7RVguUKVZMDNOv5WbUVnZ5vr7AeBvJD737WqzEUJZpjuswPGXrCdrdChOrOla3YPObz2CF q7teODV4HOR2nYL35cOzn6trAApfJu7XHJ¡GORBJY1 beNP7 + 8vcmBEDjcr7a1 fknME2WN4 + RloSFdft8LDnaLJb3pF
IKslu2IKNkCWHM4YKBhOuqHz5Nar5WvQZ8itZvRmDqnkuw97BOQTWPS / 5aG / kgkGSXOfKR9Q ==
MX 2019 60769
TECHNIQUES TO ASSOCIATE USER DATA WITH A
MOBILE DEVICE
Background of the invention
Users can use their mobile devices for a variety of tasks, both online and offline. Users can transport their mobile devices with them when they travel the world and when visiting places. Mobile devices may have hardware capable of determining their location through a receiver of the global positioning system (GPS), wifi triangulation, cell triangulation or other means. Mobile devices can be configured for use with various services. The services can be customized to a particular user. It is with respect to these and other considerations that current improvements have been necessary.
Brief Description of the Invention
Below is a brief simplified description to provide a basic understanding of some novel modalities described in this document. This brief description is not an extensive introduction, and is not intended to identify the critical / critical elements or delineate the scope of it. Its sole purpose is to present some concepts in simplified form as a prelude to the more detailed description presented below.
Several modalities are generally aimed at techniques for associating user data with a mobile device. Some modalities are particularly directed to techniques for associating user data with a mobile device for the adaptation of online and in-person services to the physical presence of a user as determined by the presence of their mobile device. In one embodiment, for example, an apparatus may comprise a service compatibility component and a storage component. The service compatibility component may be operational to receive a data packet request from a service, the data packet request comprises a network identifier for a mobile device associated with a user, and exchanges a data packet with the service in response to the data packet request. The storage component may be operative to access the data packet associated with the user based on the network identifier. Other modalities are described and claimed.
To achieve the above and related objectives, some illustrative aspects are described herein in relation to the following description and the accompanying drawings. These aspects are indicative of the various ways in which the principles disclosed in this document can be practiced and all aspects and equivalents thereof are intended to be within the scope of the claimed subject matter. Other and new advantages and features will become apparent from the following detailed description when considered in conjunction with the drawings.
Brief description of the drawings
Figure 1 illustrates an operating environment for a mobile cookie system.
Figure 2 illustrates a mode of a mobile cookie system.
Figure 3 illustrates the user configuration preferences for a user that is transmitted to a cookie detection server.
Figure 4 illustrates a user visit record that is received for storage from a mobile cookie detection server.
Figure 5 illustrates a mobile device configuration that is received from a mobile cookie detection server.
Figure 6 illustrates a modality of a logical flow for the system of Figure 1.
Figure 7 illustrates an embodiment of a centralized system for the system of Figure 1.
Figure 8 illustrates an embodiment of a distributed system for the system of Figure 1.
Figure 9 illustrates a modality of a computer architecture.
Figure 10 illustrates a modality of a communications architecture.
Figure 11 illustrates an embodiment of a radio device architecture.
Detailed description of the invention
Several modalities are directed to a user data repository associated with a mobile device for a user. A user can carry a mobile device, such as a smartphone, a portable digital assistant, a portable music player or other portable computing device. This mobile device may include software and hardware to access computer networks, which include wireless computer networks such as Wi-Fi, Bluetooth, cellular networks or other networks that use radio transmissions. These wireless network technologies can be used by the mobile device to identify your location and other wireless devices in your area. Similarly, these wireless network technologies can be used by other wireless devices in the area to identify the mobile device.
Computer-based services and other services that take advantage of computer technology and networking can use the information stored about a user to improve their services. User preferences that are used to customize the service can be stored. For example, user information may include media preferences for a user, with music provided by an online service (for example, website) or in person (for example, hotel, bar) customized for the user according to Stored media preferences. Information about a user device can be used to configure the user device, such as a mobile device, for interaction with the service. For example, the network settings of a device can be configured for use with a wireless service provided, such as Wi-Fi provided by a hotel. The fact that a user has visited a physical geographic location can be used to configure an online component of a service. For example, a website, email or other online contact with a user may include specific location promotions relevant to a geographic location visited by the user.
A user's mobile device can serve as any and all tools to detect the presence of a user in a geographic location, a tool for a user to communicate their presence in a geographical location, an end point to communicate information to a user relevant to the location, and a repository for storing user information. Because a mobile device is often maintained in the physical presence of a user, detecting the presence of a particular mobile device associated with the user can use a proxy device to determine that the user is present. Similarly, the mobile device that detects that it is in a particular location can serve as a proxy device for the mobile device, determines that the user is present at the location. Since users can frequently use their mobile device for network connection tasks, they can keep their mobile device in the presence and because the presence of a mobile device may have been the indicator that a user is present, the mobile device It can be valuable to communicate with a user. Because user information can be generated, customized and / or driven for storage based on the presence and / or identification of a mobile device, the mobile device can be a convenient location for storing user information. As a result, taking advantage of a mobile device to determine the generation of user information, personalizing user information and personalizing a service, can improve the services provided to a user.
Next, reference is made to the drawings, where similar reference numbers are used from beginning to end to refer to similar elements. In the following description, for the purpose of explanation, numerous specific details are set forth in order to provide a complete understanding of them. However, it may be evident that the new modalities can be put into practice without these specific details. In other cases, well-known structures and devices are shown in block diagram form to facilitate a description thereof. The intention is to cover all modifications, equivalents and alternatives according to the subject matter claimed.
Figure 1 illustrates a block diagram for a mobile cookie system 100. In one embodiment, the mobile cookie system 100 may comprise a computer-implemented system. Although the mobile cookie system 100 shown in Figure 1 has a limited number of elements in a certain topology, it can be appreciated that the mobile cookie system 100 may include more or less elements in alternative topologies as desired for a given implementation.
It is noteworthy that it is intended that aybyce similar indicators, as used herein, be variables that represent any positive integer. Thus, for example, if an implementation sets a value for a = 5, then a complete set of components 122 may include components 122-1, 1222, 122-3, 122-4 and 122-5. The modalities are not limited in this context.
The mobile cookie system 100 may comprise a mobile cookie compatibility server 110 that operates in coordination with a mobile device 120 to provide a user 125 with access to services based on location in a manner that limits the power used to provide Location updates to location-based services necessary to meet the needs for punctuality and accuracy of location-based services. In some embodiments, a particular cookie compatibility server 110 may coordinate the activities of a plurality of mobile devices used by a plurality of users. In some embodiments, a plurality of client location monitoring servers may exist within the mobile cookie system 100, where each coordinates a plurality of mobile devices.
A mobile device 120 may have access to a plurality of systems by which it can determine its location. For example, a mobile device 120 may be able to detect the signals from a global positioning system 150 using a GPS receiver. The GPS receiver, based on the signals of the global positioning system 150, may be able to detect the geographical location of a mobile device 120 with a high degree of accuracy, a few meters, particularly when the GPS receiver has a visual field unobstructed for the global positioning system 150, such as when you are outdoors. However, the GPS receiver may not be able to determine the location of the mobile device 120 in some circumstances, particularly when the mobile device 120 is in some indoor environments. In addition, the use of the GPS receiver may result in a higher energy expenditure due to the lower perceived signal strength of the GPS signals at the time they arrive at the mobile device 120, which may be undesirable to frequently monitor the location of a device, as desired to be tracked when a device enters geographic locations associated with various services.
The mobile device 120 may be able to detect the signals from one or more cell sites 130. A mobile device 120 that is capable of detecting the signals from a particular cell location provides information about the location of the mobile device 120. Cellular signals from a cell site have a limited range, which may be the consequence of the diffusion power of the cell site, local geography (both natural and artificial) and other factors. The ability of a particular mobile device 120 to detect a cell site may be influenced by the reception capacity of the mobile device 120. Similarities between the reception capabilities of several mobile devices may allow a geographic area to be associated with each cell location, with the geographic areas associated with several cell locations communicated to the mobile device 120 from a central repository. These geographic areas can be determined according to calculations based on the diffusion power of a cell site, local geography and other factors. These geographical areas can be determined according to the sampling of the areas in which the transmissions of a cell site can be detected. A combination of these techniques can be used. When a mobile device 120 can detect multiple cell sites, it may be able to refine its location to be within the area in which the geographic areas associated with the detectable cell sites overlap.
The detection of one or more cell sites 130 may use a cellular radio device (eg, cellular receiver, cellular transceiver) in the mobile device 120. The location determined using one or more cell sites 130 may be less accurate than if the global positioning system 150 was used, in particular where very little or only one cell location is detected. However, cell site triangulation may work in some environments in which Wi-Fi is not available and / or where GPS signals cannot penetrate. In addition, using the cellular radio device may use less power than using the GPS receiver in the mobile device 120 and can be performed simultaneously with the cellular radio device that is used for access to the network through a cellular network, thus reducing the additional power dedicated to determining the location of the mobile device 120. Therefore, cell triangulation may be appropriate to frequently monitor the location of a device, as may be desired for monitoring when a device enters geographic locations associated with various services.
The mobile device 120 may be able to detect the signals from one or more Wi-Fi access points 140. A mobile device 120 that is capable of detecting the signals from a particular Wi-Fi access point provides information about the location of the mobile device 120. Wi-Fi signals from a Wi-Fi access point have a limited range, which may be the consequence of the diffusion power of the Wi-Fi access point, local geography (both natural and artificial) and other factors. The ability of a particular mobile device 120 to detect a Wi-Fi access point may be influenced by the reception capacity of the mobile device 120. Similarities between the reception capabilities of several mobile devices may allow a geographic area to be associated with each Wi-Fi, with the geographic areas associated with several Wi-Fi access points communicated to the mobile device 120 from a central repository. These geographical areas can be determined according to the calculations based on the diffusion power of a Wi-Fi access point, local geography and other factors. These geographical areas can be determined according to the sampling of the areas in which the transmissions of a Wi-Fi access point can be detected. A combination of these techniques can be used. When a mobile device 120 can detect multiple Wi-Fi access points, it can refine its location so that it is within the area in which the geographic areas associated with the detectable Wi-Fi access points overlap.
The detection of one or more Wi-Fi access points 140 can use a Wi-Fi radio device (for example, a Wi-Fi receiver, a Wi-Fi transceiver) on the mobile device 120. The use of the Wi-Fi radio device can use less energy than the use of the GPS receiver in the mobile device 120 and can be carried out simultaneously with the Wi-Fi radio device used to access the network through a Wi-Fi network, thus reducing the additional power dedicated to the persistent tracking of the location of the mobile device 120. However, the location determined using one or more Wi-Fi access points 140 may be less accurate than if the global positioning system 150 was used, in particular when some or a single Wi-Fi access point is detected. As such, the use of Wi-Fi triangulation instead of GPS positioning may represent a transaction in which lower accuracy is accepted in exchange for lower energy consumption. The use of Wi-Fi triangulation may use less energy and result in greater accuracy than the use of cellular triangulation, but it may not be possible in areas without Wi-Fi hotspot or where Wi-Fi hotspots with associated geographic areas have not been registered. with a repository known by mobile device 120.
The mobile device 120 may be able to detect the signals from one or more Bluetooth transceivers 160. In various embodiments, other short-range network technologies may also be used or alternatively. A mobile device 120 that is capable of detecting signals from a particular Bluetooth transceiver provides information about the location of the mobile device 120. Bluetooth signals from a Bluetooth transceiver have a limited range, which may be the consequence of the diffusion power of the Bluetooth transceiver, local geography (both natural and artificial) and other factors. The ability of a particular mobile device 120 to detect a Bluetooth transceiver may be influenced by the reception capability of the mobile device 120. Similarities between the reception capabilities of various mobile devices may allow a geographic area to be associated with each Bluetooth transceiver, with the geographic areas associated with various Bluetooth transceivers communicated with the mobile device 120 from a central repository. These geographical areas can be determined according to calculations based on the transmission power of a Bluetooth transceiver, local geography and other factors. These geographical areas can be determined according to the sampling of the areas in which the transmissions of a Bluetooth transceiver can be detected. A combination of these techniques can be used. When a mobile device 120 can detect multiple Bluetooth transceivers, it can refine its location so that it is within the area in which the geographic areas associated with the detectable Bluetooth transceivers overlap.
The detection of one or more Bluetooth transceivers 160 may use a Bluetooth radio device (eg, Bluetooth receiver, Bluetooth transceiver) on the mobile device 120. The use of the Bluetooth radio device may use less energy than using the GPS receiver, transceiver cell phone or wifi on mobile device 120. However, the location determined using one or more Bluetooth transceivers 160 may be less accurate than if the global positioning system 150 was used, in particular when some or a single Bluetooth transceiver is detected. As such, the use of Bluetooth triangulation instead of GPS positioning may represent a transaction in which lower accuracy is accepted in exchange for lower energy consumption. The use of Bluetooth triangulation may use less energy and result in greater accuracy than the use of cellular triangulation, but it may not be possible in areas without a Bluetooth transceiver or where Bluetooth transceivers have not been registered in the geographic areas associated with a repository known by the mobile device.
In addition, one or more Wi-Fi access points 140 or Bluetooth transceivers 160 may be operative to detect the presence of the mobile device 120. A mobile device 120 may have an exclusive Wi-Fi media access control address (MAC address) and / or a Exclusive Bluetooth MAC address. A MAC address can be issued by the mobile device 120 as part of the network and device discovery. A Wi-Fi hotspot or Bluetooth transceiver may be able to perform the discovery of devices in which it requests the MAC addresses of nearby devices, inviting mobile devices, such as mobile device 120, to transmit their Wi-Fi MAC address, address MAC Bluetooth or other MAC address. In any case, a Wi-Fi access point, a Bluetooth transceiver and / or other wireless transceiver can be operative to detect a wireless MAC address for a mobile device 120 in the physical vicinity of the transceiver and, therefore, in the location of a service associated with the transceiver. In addition, by detecting and registering the MAC address for the mobile device 120, the user 125 associated with the mobile device 120 can be identified and registered as having visited the location of the service.
The mobile device 120 may communicate with the mobile cookie compatibility server 110 to update the mobile cookie compatibility server 110 as to its current location, which can be determined by the mobile device 120 according to the GPS-based location determination , location determination based on wifi, location determination based on the proximity of the cell tower or according to any other technique to determine the location of a mobile device. The mobile cookie compatibility server 110 can help coordinate location-based network services on behalf of mobile device 120 and / or can update other network services that take advantage of location information regarding the location of mobile device 120. The mobile cookie compatibility server 110 may maintain a repository of user information for use by the network services. In the location-based network services mode, the location of the mobile device 120 can be used since it is sufficiently equivalent to the location of the user 125 of the mobile device 120 in terms of the adequacy of the results of the network service according to the user location 125. As such, the location of the mobile device 120 and the location of the user 125 can be considered equal, equivalent and interchangeable.
A mobile cookie recognition server 160 may perform and coordinate both or any of the network services and services in person for a user 125 of the mobile device 120. The mobile cookie recognition server 160 may make use of mobile cookies in the performance of these services. Mobile cookies may comprise any information stored in association with a mobile device 120, which may include any information derived from the presence of a mobile device 120 at a location, any information stored on the mobile device 120, any information used in the configuration of the mobile device 120 and, in general, any information that takes advantage of the association between a mobile device 120 and a user 125 for the provision of services. Mobile cookies can be stored on a mobile device
120, can be stored on a mobile cookie compatibility server 110 and can be replicated between the mobile device 120 and the mobile cookie compatibility server 110.
Either or both of the mobile device 120 and the mobile cookie compatibility server 110 may interact with a mobile cookie recognition server 160 to receive, store and provide the mobile cookies. The mobile cookie recognition server 160 may be a network server used by a service to provide services that take advantage of network information, including mobile cookies. For example, mobile cookie recognition server 160 can be used to generate cookies that track the presence of a user 125 in a particular location. The mobile cookie recognition server 160 can be used to configure a mobile device 120 on behalf of a user 125 to interact with the specific location services. The mobile cookie recognition server 160 can be used to generate and retrieve mobile cookies that reflect the preferences of a user 125 and to use the preferences to personalize a network or in-person service according to the user 125. Mobile cookies stored on the mobile cookie compatibility server 110 Can be retrieved by the mobile cookie recognition server 160 directly from the mobile cookie compatibility server 110. The mobile cookies stored in the mobile device 120 can be retrieved directly by the mobile cookie recognition server 160 directly from the mobile device 120 or through the mobile cookie compatibility server 110, where the mobile cookie compatibility server 110 acts as a intermediary. Where mobile cookies are replicated through both mobile device 120 and mobile cookie compatibility server 110, mobile cookie recognition server 160 can store and retrieve mobile cookies with either or both, depending on the implementation. and of the circumstances.
The mobile cookie system 100 may include an authorization server (or other suitable component) that allows users to choose or not to have their location registered by the mobile cookie system 100 or shared with other systems (e.g., system of third parties), for example, when setting appropriate privacy settings. Users may be empowered to opt out or opt out of having mobile cookies stored on their mobile device or on a network server with reference to their mobile device. A privacy setting of a user 125 can determine what information associated with the user 125 can be registered, how the information associated with the user 125 can be registered, when the information associated with the user 125 can be registered, who can register the associated information with user 125, with whom you can share the information associated with user 125 and for what purposes you can register or share the information associated with user 125. For example, the privacy setting of a user 125 may specify access permissions to mobile cookies for user 125. Authorization servers or other authorization components may be used to reinforce one or more privacy settings of system users. of mobile cookies 100 by blocking, slicing, anonymization or other suitable techniques, as appropriate.
Figure 2 illustrates one embodiment of a mobile cookie system 100. As shown in Figure 2, a mobile cookie recognition server 160 interacts with a mobile device 120 and a mobile cookie compatibility server 110.
The mobile cookie compatibility server 110 may generally be arranged to be compatible with users, mobile clients and services in the use of mobile cookies. The mobile cookie compatibility server 110 can act as an intermediary between the mobile device 120 and a mobile cookie recognition server 160. The
<img file="MX366183B_D0002.tif" />
mobile cookie compatibility server 110 may exchange information with either or both of mobile device 120 and mobile cookie recognition server 160 to empower them to communicate and implement mobile cookies. The mobile cookie compatibility server 110 may comprise a service compatibility component 250 and a storage component 230. The service compatibility component 250 may be compatible with one or more services, including a mobile cookie recognition server 160 corresponding to a server for a particular service of a plurality of services.
The mobile device 120 may generally be arranged to act as a representative for the location of the user 125 and as at least one of the endpoints used by the user 125 to interact with the network services. The mobile device 120 may interact with the mobile cookie recognition server 160 and / or the mobile cookie compatibility server 110 to implement the mobile cookies. The mobile device 120 may comprise a service compatibility component 250 and a storage component 230. The service compatibility component 250 may be compatible with one or more services, including a mobile cookie recognition server 160 corresponding to a server for a particular service of a plurality of services.
A service compatibility component 250 may be operative to receive a data packet request 210 from a mobile cookie recognition server 160, the mobile cookie recognition server 160 serves as at least one network server that interacts with cookies mobile phones representing a network service. A network service can correspond to any service, operation or organized activity that provides services that includes at least one network component, such as the use of mobile cookies.
The data packet request may comprise a network identifier for a mobile device 120 associated with a user 125. The network identifier may comprise an identifier for the mobile device 120 in a wireless network. The network identifier may comprise a unique identifier for the wireless hardware used by the mobile device 120 when accessing a wireless network. The network identifier may comprise a media access control (MAC) address for a wireless network interface controller (NIC) of the mobile device 120.
A storage component 230 may be operative to store a mobile cookie repository comprising a plurality of data packets, where each data packet comprises a mobile cookie. The mobile cookie repository may comprise a database, a structured file or other form of organized storage for a plurality of mobile cookies. A mobile cookie may comprise a sequence of data specified by a service and stored in association with that service. The storage component 230 may be operative to access the data packet 210 associated with the user based on the network identifier. The storage component 230 may store a plurality of associated mobile cookies, where several subsets of the plurality of mobile cookies are uniquely associated with different mobile devices and / or different users. The storage component 230 may identify the mobile cookies for a mobile device and / or particular user based on the network identifier for the mobile device 120 associated with the user 125. The storage component 230 may perform a query in the database, index search or use any other form of recovery technique to identify one or more mobile cookies associated with a particular network identifier.
The storage component 230 may store a plurality of data packets associated with each user, each of the data packets comprises a mobile cookie associated with a particular service. For a particular user, the storage component 230 may store a plurality of data packets, each comprising a mobile cookie associated with a particular service. Each service can correspond to a service identifier, which can be represented as a unique numerical identifier, a uniform resource locator (URL) associated with the service, secure token or any other technique to uniquely identify a service. The data packet request 210 may comprise a service identifier associated with the service implemented at least in part by the mobile cookie recognition server 160. The storage component may be operative to identify a plurality of mobile cookies associated with the user based on the network identifier and to access a particular data package corresponding to the service from the plurality of data packages based on the network identifier. service.
In some embodiments, the wireless identifier may be translated into a user identifier before accessing a data packet from the storage component 230, where the identification of the data packet is based on the network identifier, but performed directly as a search. using the user id. The storage component 230 may store a translation table between network identifiers and user identifiers. The compatibility component
<img file="MX366183B_D0003.tif" />
of services 250 may be operative to use the translation table to uniquely identify the users of the services and to use the translation table to retrieve the mobile cookies of a specific user based on the user identifier after the translation into from a wireless identifier.
In some embodiments, the user identifier for a user 125 can be determined based on the presence of the user 125 in the geographic location without the use of a wireless identifier for the mobile device 120. The location of the mobile device 120 can be determined according to the global positioning system 150, cellular triangulation, wifi triangulation or any other technique for location detection by a mobile device 120. The mobile device 120 may report its location to the mobile cookie compatibility server 110 or the mobile cookie recognition server 160 together with the user identifier for the user 125. The mobile cookie recognition server 160 can make the data packet request 210 using the user identifier and exchange the data packet 220 based on the user identifier in response to the determination that the user 125 is present based in the local detection performed by the mobile device 120.
The service compatibility component 250 can
<img file="MX366183B_D0004.tif" />
be operative to exchange data packet 220 with mobile cookie recognition server 160 representing the service in response to request for data packet 210. In some cases, the mobile cookie recognition server 160 may generate a mobile cookie comprising data packet 220 and transmits data packet 220 to service compatibility component 250 for storage in storage component 230, the request of data 210 comprises a request to store a mobile cookie. In some cases, the mobile cookie recognition server 160 may retrieve a previously generated mobile cookie comprising the data packet 220 and receive the data packet 220 from the service compatibility component 250 after recovery from the storage component 230, the data request 210 comprises a request to receive a mobile cookie associated with the service.
The mobile cookie recognition server 160 may be associated with one or more wireless transceivers, such as one or more of the Wi-Fi access points 140 or one or more of the Bluetooth transceivers 160. The wireless transceivers may be operative to explore the area within the range of your wireless receiver, which can include scanning between all radio frequencies associated with the protocol to which they conform. Wireless scanning
<img file="MX366183B_D0005.tif" />
It can produce a list of a plurality of wireless identifiers corresponding to a plurality of mobile devices. The mobile cookie recognition server 160 may be operative to perform various tasks for some or all of the plurality of wireless identifiers detected. These tasks may include the generation of mobile cookies that represent the visit records for the detected devices, the request for user configuration preferences associated with the detected devices, the generation of configuration packages for the detected devices, any other technique associated with mobile cookies, and any combination of techniques associated with mobile cookies.
The mobile cookie recognition server 160 can receive one or more wireless identifiers from one or more wireless transceivers of the mobile devices detected in its vicinity. The detection of these one or more wireless identifiers can serve as a detection that mobile devices are in the vicinity of wireless transceivers. Since wireless transceivers can be associated with a particular geographic area associated with the service implemented at least in part by the mobile cookie recognition server 160, the detection of mobile devices as being in the vicinity of wireless transceivers may indicate that Mobile devices are in a geographic location associated with the service. Since the location of the mobile devices can be used as a proxy device for the location of the associated users of the mobile devices, the detection of the mobile devices may correspond to the detection of one or more users as present in the geographic location associated with the service. As such, the mobile cookie recognition server 160 may be operative to receive a list of one or more wireless identifiers detected through wireless scanning, the list of one or more wireless identifiers indicating the presence of one or more associated users as they are present in a geographical location associated with the service implemented at least in part, by the mobile cookie recognition server 160.
As shown in Figure 2, a service compatibility component 250 and a storage component 230 may reside on either or both of a mobile cookie compatibility server 110 and a mobile device 120. In some cases, the mobile cookie recognition server 160 can make a data packet request 210 with a service compatibility component 250 on the mobile device 120 and exchange the data packet 210 with the service compatibility component 250 in the mobile device 120. In other cases, the mobile cookie recognition server 160 can make a data packet request 210 with a service compatibility component 250 on the mobile cookie compatibility server 110 and exchange the data packet 210 with the compatibility component of services 250 on the mobile cookie compatibility server 110.
Mobile cookies for a user can be replicated through a storage component 230 on the mobile device 120 and a storage component 230 on the mobile cookie compatibility server 110. In some embodiments, a storage component 230 in the mobile cookie compatibility server 110 may store mobile cookies for a plurality of users, while the storage component 230 stores those and only those cookies associated with a user 125 of the mobile device 120 . As such, the storage component 230 in the mobile cookie compatibility server 110 may contain a replication of the mobile cookies for a plurality of users in a plurality of mobile devices, where the storage components in the mobile devices contain a replication of Mobile cookies specific to your particular users. The service compatibility component 250 in the mobile device 120 and the service compatibility component 250 in the mobile cookie compatibility server 110 may be operative to perform the replication of mobile cookies between the mobile device 120 and the compatibility server of 110 mobile cookies in accordance with known data replication techniques.
The mobile cookies stored in the storage component 230 in the mobile device 120 may be accessible to a local application in the mobile device 120. Local applications in the mobile device 120 may include, for example, a web browser. The web browser can be operative to use the mobile cookies in the storage component 230 in the mobile device 120 as web cookies as they are used for the web transactions of the hypertext transport protocol (HTTP). For example, the web browser can access a web page using cookies and access one of the mobile cookies in storage component 230 as a cookie for the web page.
The storage component 230 in the mobile cookie compatibility server 110 may be accessible to the network applications that implement the network services. The network applications can be run on the same device as the mobile cookie compatibility server 110 or on separate devices. Network applications
<img file="MX366183B_D0006.tif" />
they can perform the tasks on behalf of the users and request and store the mobile cookies in the storage component 230 of the mobile cookie compatibility server 110 in the implementation of their services. For example, a network application that acts as a web server can retrieve mobile cookies from the storage component 230 of the mobile cookie compatibility server 110 as part of providing a web page to a user 125 of the mobile device 120 .
Figure 3 illustrates user configuration preferences 310 for a user that is transmitted to a mobile cookie recognition server 160. As shown in Figure 3, user configuration preferences 310 can be received from either server of compatibility of mobile cookies 110 or mobile device 120.
User configuration preferences 310 may comprise at least a portion of the mobile cookies associated with a user 125 and a service. User configuration preferences 310 may be associated with the service performed at least in part by the mobile cookie recognition server 160. User configuration preferences 310 may be transmitted to the mobile cookie recognition server 160 in response to the request for package
<img file="MX366183B_D0007.tif" />
210. The user configuration preferences 310 may be stored in the storage component 230 in response to a request from the mobile cookie recognition server 160.
The mobile cookie recognition server 160 may personalize a physical service in person to the user 125 based on user configuration preferences 310. For example, the mobile cookie recognition server 160 may be operative to control the elements of a hotel room, such as thermostat settings, lighting settings, TV settings, music settings, alarm clock settings, and any other element of a housing and to specify one or more of those elements based on user configuration preferences 310. For example, user configuration preferences 310 may indicate that a user prefers a hotel room thermostat to be set at 23.3 ° C (74 ° F) and can adjust the thermostat to 23.3 ° C (74 ° F) in response to the reading of this indication from the user configuration preferences received 310.
In another example, the mobile cookie recognition server 160 may be operative to control the elements of a public accommodation, such as a bar, restaurant, or other public space. The mobile cookie recognition server 160 can be operative to specify the settings of the thermostats, lighting, music, television or any other element of the accommodation based on the individual or collective preferences of the known users present in the accommodation. For example, music playback can be selected to vary among the preferences of the people present or to jointly adapt the preferences of the people present based on the selections acceptable to all people known to be present. It will be appreciated that, in general, any element of any physical location subjected to computerized control can be configured, at least in part, based on user configuration preferences 310 for a user 1 25.
The mobile cookie recognition server 160 may customize a network service for the user 125 based on user configuration preferences 310. For example, the design or content of a website may be adjusted based on the configuration preferences User 310. The content of a streaming service can be determined based on user configuration preferences 310. In general, any aspect of a network service can be customized based on user configuration preferences 310.
Figure 4 illustrates a user visit record 410 that is received for storage on a server.
<img file="MX366183B_D0008.tif" />
recognition of mobile cookies 160. As shown in Figure 4, the user visit record 410 can be transmitted to either the mobile cookie compatibility server 110 or the mobile device 120.
The user visit record 410 may comprise at least a portion of the mobile cookies associated with a user 125 and a service. The user visit record 410 may record the presence of a user 125 in a particular geographic location associated with the service implemented, at least in part, by the mobile cookie recognition server 160. The user visit record 410 may be stored to customize or otherwise configure future services based on the knowledge of the user's previous visit to the geographic location.
The user visit record 410 may include additional information related to the user's visit to the geographic location. The user visit record 410 may comprise a particular location, such as where the service is associated with several geographic locations (for example, a department store of a plurality of physical outlets). The user visit record 410 may comprise a time of visit, which includes both a day and the time of day, or, in general, corresponds to any technique for representing a particular time. The user visit record 410 may include a record of all or some of the activities performed by the user 125 in the physical location, such as the purchase of items, the receipt of services, or any other service that may be associated with the physical activity in the geographic location.
The user visit record 410 may be subsequently retrieved by the same mobile cookie recognition server 160 or a different mobile cookie recognition server associated with the service, the user visit record 410 is transmitted to the service by means of the component of service compatibility 250. User visit record 410 may be used to modify future services in person or network services in response to user registration 125 after visiting the geographic location. For example, a web visit by the user 125 to a web page regarding the service may reflect the visit by the user 125 to the physical location of the service. Promotions related to the particular physical location visited by the user 125 may be offered to the user 125. The user 125 may be offered the opportunity to make online purchases that can be collected or performed in person, where the physical location visited more recently or more often by the user 125 it is offered as a predetermined location for the collection or performance of these services. Similarly, a web interface for the purchase of physical goods or services can show its availability, where availability at the location indicated by the user visit record 410 is shown with a greater prominence than other locations. In general, any information stored in the user visit record 410 can be used in customizing the network services for the user 125. In general, user visit record 410 can be used to customize services in person, as described with reference to user configuration preferences 310. For example, a user visit record 410 may record a user's specification for device configuration (e.g., thermostat settings), where the settings used as user setup preferences 310 for those devices after return from a user to that location or another location they offer similar customization (for example, a different hotel room).
Figure 5 illustrates a mobile device configuration 510 that is received from a mobile cookie recognition server 160. As shown in Figure 5, the mobile device configuration 510 can be transmitted directly to the mobile device 120 or through the server of compatibility of mobile cookies 110.
The service compatibility component 250 may be operative to receive a device configuration package 510 from the mobile cookie recognition server 160, the device configuration package 510 specifies the device configuration information for the configuration of the mobile device 120 associated with the user 125. The service compatibility component 250 may be operative to transmit the device configuration package 510 to a mobile device configuration component 520 for the configuration of the mobile device 120.
A mobile device configuration component 520 may be operative to receive a device confirmation package 510, to receive a device configuration package 510 from the mobile cookie recognition server 160, the device configuration package 510 specifies the information Device configuration for mobile device configuration 120. The mobile device configuration component may be operative to configure the mobile device 120 according to the device configuration information.
In some cases, the device configuration package 510 may be received from the mobile cookie recognition server 160 by the mobile cookie compatibility server 110. When device configuration package 510 is received on mobile cookie compatibility server 110, A mobile device configuration component 520 in the mobile cookie compatibility server 110 may be operative to configure the mobile device 120 using the device configuration package 510 by transmitting the device configuration package 510 to a configuration component of mobile device 520 in mobile device 120. As such, the mobile cookie compatibility server 110 can operate as an intermediary between the mobile cookie recognition server 160 and the mobile device 120 for the configuration of the mobile device 120.
In some cases, the device configuration package 510 can be received directly from the mobile cookie recognition server 160 by the mobile device 120 without the mobile cookie compatibility server 110 being used as an intermediary. In any case, upon receiving the device configuration package 510, the mobile device configuration component 520 may be operative to configure the mobile device 120 according to the device configuration information of the device configuration package 510.
The device configuration package 510 may provide the device configuration information for the configuration of any element of the mobile device 120. The device configuration information may be related to the configuration of any software or hardware element of the mobile device 120.
The device configuration information may empower the mobile device configuration component 520 to configure the mobile device 120 in order to interoperate with the service. The device configuration information 510 may specify the device configuration information that empowers the mobile device configuration component 520 to configure the mobile device 120 to interoperate with the mobile cookie recognition server 160, some other service element, or both the mobile cookie recognition server 160 and another service element.
In some cases, the device configuration information may empower the mobile device configuration component 520 to configure the mobile device 120 to access a wireless network associated with the service. For example, the service may provide Wi-Fi or other wireless network service in a geographic location associated with the service (for example, Wi-Fi connection in a hotel, cafeteria, etc.). The mobile device 120 may need to be configured to access the wireless network service, such as through the selection of a particular wireless network and the exchange of security information (eg, a password) in order to join the wireless network. Therefore, the device configuration package 510 may include a wireless network to join and the security information that
<img file="MX366183B_D0009.tif" />
It will be used to join the wireless network.
As such, a user 125 may be able to enter a geographic location with his mobile device 120 and have the mobile cookie compatibility server 110 that acts as an intermediary for the configuration of the mobile device 120 to join a wireless network provided by a service associated with the geographic location. The mobile cookie recognition server 160 may receive a wireless identifier for the mobile device 120 detected by a wireless access point that performs the wireless scan. The mobile cookie recognition server 160 may indicate to the service compatibility component 250 of the mobile cookie compatibility server 110 that a mobile device 120 with that wireless identifier entered the geographic location associated with the service. The mobile cookie recognition server 160 may then transmit the device configuration package 510 to the mobile cookie compatibility server 510 or it may have previously transmitted the device configuration package 510 to the mobile cookie compatibility server 510 with the 510 mobile cookie compatibility server that stores device configuration package 510 for future use in device configuration mobile phones such as mobile device 120.
<img file="MX366183B_D0010.tif" />
The mobile cookie compatibility server 110 can transmit the device configuration package 510 to the mobile device 120 for the configuration of the mobile device 120. The mobile cookie compatibility server 110 may contact the mobile device 120 using a network address registered with the mobile cookie compatibility server 510 by the mobile device 120, as part of a persistent or semi-persistent connection is maintained between the mobile device 120 and the mobile cookie compatibility server 510 or other services associated with the mobile cookie compatibility server 510. For example, the mobile device 120 may maintain a semi-persistent network connection with a network service used by the user 125 of the mobile device 120 for periodic reception of the relevant data (eg, email, social media information, messaging, etc). The mobile cookie compatibility server 110 may operate in conjunction with the network service to automatically transmit the device configuration package 510 to the mobile device 120.
The mobile device 120 can receive the device configuration package 510 from the mobile cookie compatibility server 110, the reliable device configuration package 510 for the mobile device 120 and the user 125 of the mobile device 120 due to the
<img file="MX366183B_D0011.tif" />
pre-existing relationship between user 125 and the network service used by user 125. User 125, therefore, can rely on mobile cookie compatibility server 110 to provide a device configuration package 510 for automatic configuration of the mobile device 120. Alternatively, a user interface dialog may be presented to the user 125 presenting the option of performing the configuration.
The mobile device 120 may then be configured using the device configuration information of the device configuration package 510. The mobile device 120 may be configured to access the wireless network provided by the service and, therefore, configured to interoperate with the service . The mobile device 102 can also be configured to directly provide additional information to the service, such as through the mobile cookie recognition server 160. For example, the device configuration package 510 may be delivered to the mobile device 120 through the mobile cookie compatibility server 110, with the user configuration preferences, or any other mobile cookie, transmitted to the mobile cookie recognition server 160 over the wireless network of the service configured using the device configuration information.
This document includes a set of representative flowcharts of exemplary methodologies for carrying out the novel aspects of the disclosed architecture. Although, for reasons of simplicity of explanation, one or more methodologies are shown herein, for example, in the form of a flowchart or flowchart, they are shown and described as a series of actions, they must be understood and appreciated. that the methodologies are not limited by the order of the actions, since some actions may, by virtue of them, occur in a different order and / or concurrently with actions other than those shown and described in this document. For example, those skilled in the art will understand and appreciate that a methodology could alternatively be represented as a series of interrelated states or events, as in a state diagram. On the other hand, not all actions illustrated in a methodology may be necessary for a novel implementation.
Figure 6 illustrates one modality of a logical flow 600. The flow logic 600 may be representative of all or some of the operations performed by one or more modalities described herein.
In the illustrated mode shown in Figure 6, the logical flow 600 can receive a data packet request 210 from a service, the data packet request 210 comprises a network identifier for a mobile device 120 associated with a user 125 , the data packet request 210 comprises a service identifier associated with the service in block 602. The data packet request 210 may be received in response to the mobile device 120 associated with the user 125 that is detected as present in a geographic location associated with the service based on a detection of the network identifier for the mobile device 120. The identifier The network may comprise a MAC address for a wireless NIC of the mobile device 120.
Logical flow 600 can identify a plurality of data packets associated with user 125 based on the network identifier in block 604. Each of the plurality of identified data packets can be associated with a particular service, where all the plurality of identified data packets is associated with user 125.
The logical flow 600 may identify a data packet 220 of the plurality of data packets based on the service identifier in block 606. The data packet 220 may be a data packet of a plurality of associated data packets only. with both the user 125 and a particular service.
Logical flow 600 can transmit data packet 220 to the service in response to request for data packet 210 in block 608. Data packet 220 may comprise one or more user configuration preferences.
310 associated with the service. The data packet 220 may comprise a user visit record 410, the user visit record 410 received from the service based on a detection by the network identifier service at a geographic location associated with the service. The data package 220 may comprise a device configuration package 510, the configuration package specifies the configuration information for the mobile device 120, the mobile device 120 is identified for receipt of the device configuration package 510 based on the network identifier The device configuration information can be used to configure the mobile device 120 to interoperate with the service.
The modalities are not limited to this example.
Figure 7 illustrates a block diagram of a centralized system 700. Centralized system 700 can implement some or all of the structures and / or operations for the mobile cookie system 100 in a single computing entity, as entirely within a single device 720.
The device 720 may comprise any electronic device capable of receiving, processing and sending the information for the mobile cookie system 100. Examples of an electronic device may include, without limitation, an ultra-mobile device, a mobile device, a digital assistant
<img file="MX366183B_D0012.tif" />
Personal (PDA), a mobile computing device, a smartphone, a telephone, a digital telephone, a cell phone, e-book readers, a handset, a one-way locator, a two-way locator, a device messaging, a computer, a personal computer (PC), a desktop computer, a laptop, a portable computer, a portable mini computer, a pocket computer, a tablet PC, a server, an array of servers or server park, a web server, a network server, an internet server, a workstation, a minicomputer, a host, a supercomputer , a network device, a web device, a distributed computing system, multiprocessor systems, processor-based systems, consumer electronics, programmable consumer electronics, gaming devices, television, digital television, connection box, wireless access point, base station, subscriber station, mobile subscriber center, radio network controller, router, hub, gateway, bridge, switch, machine, or combination thereof. The modalities are not limited in this context.
The device 720 can execute the processing operations or the logic for the mobile cookie system 100 using a processing component 730. The
<img file="MX366183B_D0013.tif" />
Processing component 730 may comprise various hardware elements, software elements, or a combination of both. Examples of hardware elements may include devices, logic devices, components, processors, microprocessors, circuits, processor circuits, circuit elements (for example, transistors, resistors, capacitors, inductors, etc.), integrated circuits, application integrated circuits specific (ASIO), programmable logic devices (PLD), digital signal processors (DSP, by its acronym in English), matrix of doors program in situ (FPGA), memory units, logic gates, registers, semiconductor devices, chips, microchips, chipsets, and so on. Examples of software elements may include software components, programs, applications, computer programs, application programs, system programs, software development programs, machine programs, operating system software, intermediate support, firmware, software modules , routines, subroutines, functions, methods, procedures, software interfaces, application program interfaces (APIs), instruction sets, computer code, code segments, computer code segments, words, values, symbols, or any combination of them. The determination of whether a modality is implemented using the hardware elements and / or the software elements may vary according to any number of factors, such as the desired calculation speed, power levels, heat tolerances, processing cycle budget , input data rates, output data speeds, memory resources, data bus speeds and other design or performance limitations, as desired for a given application.
The device 720 can execute the communication operations or the logic for the mobile cookie system 100 using the communication component 740. The communication component 740 can implement any of the well-known communication techniques and protocols, such as techniques suitable for use with packet switching networks (e.g., public networks, such as the internet, private networks, such as business intranet, etc.), circuit switching networks (for example, public switched telephone network), or a combination of packet switching networks and circuit switching networks (with appropriate gateways and translators). The communications component 740 may include several types of conventional communication elements, such as one or more communication interfaces, network interfaces, network interface cards (NICs), radios, transmitters / receivers (transceivers) wireless, wired and / or wireless media, physical connectors, and so on. By way of example, and not limitation, the communication means 712, 742 include the wired communication means and the wireless communication means. Examples of wired media may include a wire, cable, metal conductors, printed circuit boards (PCBs), backplates, switching structures, semiconductor material, twisted pair cable, coaxial cable, fiber optics, a propagated signal, etc. Examples of wireless communication media may include acoustic, radio frequency spectrum (RF), infrared and other wireless media.
The device 720 can communicate with other devices through a communication means 712, 742 using the communication signals 714, 744, respectively, through the communication component 740. The other devices can be internal or external to the device 720 as want for a particular implementation. The signals 714 sent through the communication means 712 may comprise communication between the mobile cookie compatibility server 110 and the mobile device 120 of a user 125. The signals 714 may correspond to the interaction between the mobile device 120 and the mobile cookie compatibility server 110 for the performance of the mobile cookies, which includes the replication of mobile cookies, the transmission of location information, and the transmission of Information of device configuration. The signals 744 sent through the communication means 742 may comprise communication between the mobile cookie compatibility server 110 and the mobile cookie recognition server 160 for a service. The signals 744 may correspond to the interaction between the mobile cookie compatibility server 110 and the service, such as for the transmission of data packets comprising mobile cookies, the exchange of translatable network identifiers to user identifiers, and the transmission of device configuration information.
Figure 8 illustrates a block diagram of a distributed system 800. The distributed system 800 can distribute portions of the structure and / or operations for the mobile cookie system 100 across multiple computing entities. Examples of distributed system 800 may include, without limitation, a client and server architecture, a 3-layer architecture, a N-layer architecture, a closely coupled or grouped architecture, a peer architecture, a master and slave architecture, a Shared database architecture, and other types of distributed systems. The modalities are not limited in this
<img file="MX366183B_D0014.tif" />
context.
The distributed system 800 may comprise a plurality of server devices 810. In general, the server devices 810 may be the same or similar to the device 720 as described with reference to the figure
7. For example, the server devices 810 may each comprise a processing component 830 and a communication component 840 that are the same or similar to the processing component 830 and the communication component 840, respectively, as described with reference to the figure 7. In another example, the server devices 810 can communicate through a communication medium 812 using the communication signals 814 through the communication components 840.
The server devices 810 may comprise or employ one or more client programs that operate to carry out various methodologies according to the modalities described. In one embodiment, for example, each of the server devices 810 can implement a mobile cookie compatibility server 110 that performs the described operations. Each of the server devices 810 may implement a mobile cookie compatibility server 110 in parallel, with several mobile devices and / or services assigned to a particular server device of the plurality of server devices 810. For example, mobile device 120 may be assigned to a server device
810-1, with all mobile cookie recognition servers such as mobile cookie recognition server
160 which addresses the device device may not mobile server 120.
be assigned different mobile device at times like the balance of
810-1 for
Alternatively, to a device interactions with the mobile devices particular server, with server that handle the same device different in response to concerns load.
Figure 9 illustrates an embodiment of an exemplary computer architecture 900 suitable for implementing various modalities as described above. In one embodiment, the computer architecture 900 may comprise or be implemented as part of an electronic device.
Examples of an electronic device may include those described with reference to Figure 8, among others.
The modalities are not limited in this context.
As used in this application, the terms "and component" system are intended to refer to an entity related to computing, whether hardware, a combination of hardware and software, software, or running software, the examples of which are provided by exemplary computer architecture
900. For example, a component can be, but is not limited to, a process that runs on a processor, a processor, a hard drive, multiple storage units (optical and / or magnetic storage media), an object , an executable element, an execution thread, a program, and / or a computer. As an illustration, both an application running on a server and the server can be a component. One or more components may reside within a process and / or thread, and a component may be located on a computer and / or distributed between two or more computers. In addition, the components can be communicatively connected to each other through various types of media to coordinate operations. Coordination may involve the unidirectional or bidirectional exchange of information. For example, the components can communicate the information in the form of signals communicated through the media. The information can be implemented as signals assigned to various signal lines. In such assignments, each message is a signal. Other modalities, however, may alternatively employ data messages. Such data messages can be sent through several connections. Exemplary connections include parallel interfaces, serial interfaces, and bus interfaces.
Computer architecture 900 includes several common computer elements, such as one or more processors, multi-core processors, coprocessors, memory units, chipsets, controllers, peripheral elements, interfaces, oscillating circuits, timing devices, video cards, cards audio, input / output (l / O) multimedia components, power supplies, and so on. The modalities, however, are not limited to implementation by the computer architecture 900.
As shown in Figure 9, the computer architecture 900 comprises a processing unit 904, a system memory 906 and a system bus 908. The processing unit 904 can be any of several commercially available processors, including, without limitation, AMD® Athlon®, Duron® and Opteron® processors; ARM® application, integrated and secure processors; IBM® and Motorola® DragonBall® and PowerPC® processors; IBM and Sony® Cell processors; Intel® Celeron®, Core (2) Duo®, Itanium, Pentium, Xeon, and XScale® processors; and similar processors. Dual microprocessors, multi-core processors, and other multi-processor architectures can also be used as the processing unit 904.
The system bus 908 provides an interface for the system components, which include, but is not limited to, the system memory 906 in the processing unit 904. The system bus 908 can be any of several types of
<img file="MX366183B_D0015.tif" />
bus structure that can also be connected to a bus memory (with or without a memory controller), a peripheral bus and a local bus using any of a variety of commercially available bus architectures. The interface adapters can be connected to the system bus 908 through a slot architecture. Exemplary slot architectures may include, without limitation, accelerated graphics port (AGP), card bus, standard (extended) ((E) ISA) industrial architecture, architecture Microchannel (MCA), NuBus, Peripheral Component Interconnection (Extended) (PCI (X)), PCI Express, International Personal Computer Memory Card Association (PCMCIA, by its acronym in English), and the like.
The computer architecture 900 may comprise or implement various manufacturing items. A manufacturing article may comprise a computer readable storage medium for storing the logic. Examples of a computer-readable storage medium may include any tangible medium capable of storing electronic data, including transient or permanent memory, removable or non-removable memory, erasable or non-erasable memory, recordable or rewritable memory, and so on. Logic examples may include program instructions
<img file="MX366183B_D0016.tif" />
computer executables implemented using any suitable code type, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, object-oriented code, visual code, and the like. The modalities can also at least be partially implemented as instructions contained in or through a permanent means readable by computer, which can be read and executed by one or more processors to allow the performance of the operations described in this document.
System memory 906 may include various types of computer-readable storage media in the form of one or more higher-speed memory units, such as read-only memory (ROM), random access memory (RAM) , for its acronym in English), Dynamic RAM (DRAM), DRAM of double data rate (DDRAM), synchronous DRAM (SDRAM), RAM static (SRAM, for its acronym in English), programmable ROM (PROM), programmable and erasable ROM (EPROM), programmable and electrically erasable ROM (EEPROM), flash memory , polymer memory as a ferroelectric polymer memory, ovonic memory, phase or ferroelectric change memory, silicon-oxide memory57 nitride-silicon oxide (SONOS), magnetic or optical cards, a wide variety of devices such as redundant array of independent disk drives (RAID), solid-state memory devices (for example, USB stick, solid-state drives (SSD)) and any other type of storage media suitable for storing the information In the illustrated mode shown in Figure 9, system memory 906 may include permanent memory 910 and / or transient memory 912. A basic input / output system (BIOS) can be stored in permanent memory 910.
Computer 902 may include various types of computer-readable storage media in the form of one or more lower speed memory units, including an internal (or external) hard disk drive (HDD) 914, a magnetic floppy disk drive (FDD) 916 for reading or writing on a removable magnetic disk 918, and an optical disk drive 920 for reading or writing on a removable optical disk 922 (e.g., a CD-ROM or DVD). The HDD 914, FDD 916 and the optical disk drive 920 can be connected to the system bus 908 via an HDD interface 924, an FDD interface 926 and an optical disk drive interface 928, respectively. The hard disk interface 924 for external disk implementations may include at least one or both of the universal serial bus (USB) and IEEE 1394 interface technologies.
Associated computer readable media and units provide temporary and / or permanent storage of data, data structures, computer executable instructions, and so on. For example, a number of program modules may be stored in disk drives and memory units 910, 912, which include an operating system 930, one or more application programs 932, other program modules 934, and program data 936 . In one embodiment, one or more application programs 932, other program modules 934, and program data 936 may include, for example, various applications and / or components of the mobile cookie system 100.
A user can enter orders and information into the computer 902 through one or more wired / wireless input devices, for example, a keyboard 938 and a pointing device, such as a mouse 940. Other input devices may include microphones, infrared remote controls (IR), radio frequency (RF) remote controls, game controllers, optical pencils, card readers, security devices, fingerprint readers, gloves, graphics tablets, game levers, keyboards, retina readers, touch screens (for example, capacitive, resistive, etc.), follower balls, touch panels, sensors, Stilettos, and the like. These and other input devices are often connected to the processing unit 904 through an input device interface 942 that is coupled to the system bus 908, but can be connected by other interfaces such as a parallel port, IEEE 1394 serial port , game port, USB port, IR interface, etc.
A monitor 944 or other type of display device is also connected to the system bus 908 through an interface, such as a video adapter 946. Monitor 944 can be internal or external to computer 902. In addition to monitor 944, a Computer commonly includes other peripheral output devices, such as speakers, printers, and so on.
Computer 902 can operate in a network environment using logical connections through wired and / or wireless communications to one or more remote computers, such as a remote computer 948. The remote computer 948 can be a workstation, a server computer, a router, personal computer, laptop, microprocessor-based entertainment device, peer device or other common network node, and usually includes many or all of the elements described with respect to computer 902, although, for purposes of brevity, only one memory / storage device 950 is illustrated. The logical connections represented include wired / wireless connectivity to a local area network (LAN) 952 and / or larger networks, for example, a wide area network (WAN) ) 954. Such LAN and WAN network environments are common in offices and companies, and facilitate business computer networks, such as intranets, that can be connected to a worldwide communication network, for example, the Internet.
When used in a LAN network environment, computer 902 connects to LAN 952 through a wired and / or wireless communication network interface or adapter 956. Adapter 956 can facilitate wired and / or wireless communications to LAN 952, which may also include a wireless access point disposed therethrough for communication with the wireless functionality of adapter 956.
When used in a WAN network environment, computer 902 can include a modem 958, or connects to a communications server on WAN 954, or has other means to establish communications through WAN 954, as through from Internet. The modem 958, which can be internal or external and a wired and / or wireless device, connects to the system bus 908 through the input device interface 942. In a network environment, the program modules represented with respect to the computer 902, or portions thereof, may be stored in the remote memory / storage device 950. It will be appreciated that the network connections shown are exemplary and others may be used means to establish a communication link between computers.
Computer 902 is operable to communicate with wired and wireless devices or entities that use the IEEE 802 family of standards, such as wireless devices operatively arranged in wireless communication (for example, IEEE 802.9 telecommunications waveform modulation techniques). These include, at least, Wi-Fi (or wireless fidelity), WiMax, Bluetooth ™ and wireless technologies, among others. Therefore, the communication can be a predefined structure as with a conventional network or simply a specific communication between at least two devices. Wi-Fi networks use radio technologies called IEEE 802.9x (a, b, g, n, etc.) to provide secure, reliable and fast wireless connectivity. A Wi-Fi network can be used to connect computers to each other, to the Internet, and to connect networks (using the media and functions related to IEEE 802.3).
Figure 10 illustrates a block diagram of an exemplary communication architecture 1000 suitable for implementing various modalities as described above. The communication architecture 1000 includes several common communication elements, such as a transmitter, receiver, transceiver, radio, network interface, baseband processor, antenna, amplifiers, filters, power supplies, and so on. The modalities, however, are not limited to execution by the communication architecture 1000.
As shown in Figure 10, the communication architecture 1000 includes one or more clients and servers 1002 1004. The clients 1002 can implement the client device 910. The servers 1004 can implement the server device 950. The clients 1002 and the servers 1004 are operatively connected with one or more respective client data stores 1008 and server data stores 1010 that can be used to store local information regarding the respective clients 1002 and servers 1004, such as cookies and / or associated contextual information.
The clients 1002 and the servers 1004 can communicate the information with each other through a communication structure 1006. The communication structure 1006 can implement any of the well-known communication techniques and protocols. Communication structure 1006 can be implemented as a packet switching network (for example, public networks, such as the internet, private networks, such as a corporate intranet, etc.), a circuit switching network (for example, the public switched telephone network ), or a combination of a packet switching network and a circuit switching network (with appropriate gateways and translators).
Communication structure 1006 can implement various network interfaces arranged to accept, communicate, and connect a communications network. A network interface can be considered as a specialized form of an input / output interface. Network interfaces may employ connection protocols that include, without limitation direct connection, ethernet (for example, thick, thin twisted pair, 10/100/1000 Base T, and the like), token ring, network interfaces wireless, cellular network interfaces, IEEE 802.11ax network interfaces, IEEE 802.16 network interfaces, IEEE 802.20 network interfaces, and the like. In addition, multiple network interfaces can be used to interact with various types of communication networks. For example, several network interfaces can be used to allow communication through broadcast, multicast and unicast networks. In case the processing requirements dictate greater speed and capacity, similarly distributed network controller architectures can be used for concentration, load balancing, and on the other hand increase the communication bandwidth required by customers 1002 and the servers 1004. A communications network can be any and the combination of wired and / or wireless networks, including, without limitation, a direct interconnection, a guaranteed personalized connection, a private network (for example, a corporate intranet), a public network (by eg, internet), a personal area network (PAN), a local area network (LAN), a metropolitan area network (MAN), Operation missions such as Internet nodes (OMNI), a wide area network (WAN), a wireless network, a cellular network, and other communication networks.
Figure 11 illustrates a mode of a device 1100 for use in an OFDM multi-carrier system, such as the mobile cookie system 100. The device 1100 can implement, for example, software components 1160 as described with reference to the cookie system phones 100 and / or a logic circuit 1130. The logic circuit 1130 may include physical circuits to carry out the operations described for the mobile cookie system 100. As shown in Figure 11, the device 1100 may include a radio interface 1110, baseband circuits 1120, and computer platform 1130, although the modalities are not limited to this configuration.
The device 1100 can implement some or all of the structure and / or operations for the mobile cookie system 100 and / or logical circuit 1130 in a single computing entity, as completely within a single device. Alternatively, the device 1100 may distribute the portions of the structure and / or operations for the mobile cookie system 100 and / or logical circuit 1130 across multiple computing entities using a distributed system architecture, such as a client and server architecture, a 3-tier architecture, a N-layer architecture, a closely coupled or grouped architecture, a peer architecture, a master and slave architecture, a shared database architecture, and other types of distributed systems. The modalities are not limited in this context.
In one embodiment, the radio interface 1110 may include a component or combination of components adapted to transmit and / or receive modulated single carrier or multiple carrier signals (for example, including complementary code manipulation (COK) ) and / or orthogonal frequency division multiplexing symbols (OFDM, by its abbreviations in English)) although the modalities are not limited to any scheme of interface or specific modulation through waves of telecommunications. The radio interface 1110 may include, for example, a receiver 1112, a transmitter 1116 and / or a frequency synthesizer 1114. The interface 1110 may include polarization controls, a crystal oscillator and / or one or more antennas 1118. In another embodiment, the radio interface 1110 may use voltage controlled external oscillators (VCOs), surface acoustic wave filters, intermediate frequency (IF) filters and / or frequency filters. RF, as desired. Due to the variety of potential RF interface designs a detailed description of them is omitted.
The baseband circuits 1120 can communicate with the radio interface 1110 to process, receive and / or transmit the signals and can include, for example, an analog to digital converter 1122 for subconversion of the received signals, a digital converter to analog 1124 for superconversion of signals for transmission. In addition, the baseband circuits 1120 may include a baseband or physical layer (PHY) 1156 processing circuit for processing the PHY link layer of the respective received / transmitted signals. The baseband circuits 1120 may include, for example, a processing circuit 1128 for media access control (MAC) / data link layer processing. The baseband circuits 1120 may include a memory controller 1132 for communication with the processing circuit 1128 and / or a computer platform 1130, for example, through one or more interfaces 1134.
In some embodiments, the PHY 1126 processing circuit may include a frame construction and / or detection module, in combination with additional circuitry such as a buffer, to construct and / or deconstruct communication frames, such as radio frames . In addition, or as an alternative, the MAC processing circuit 1128 may share the processing of some of these functions or perform these processes independent of the processing circuit of PHY 1126. In some modalities, MAC and PHY processing can be integrated into a single circuit.
The computing platform 1130 can provide the computing functionality for the device 1100. As shown, the computing platform 1130 may include a processing component 1140. In addition to, or as an alternative to, the baseband circuitry 1120, the device 1100 You can execute the processing operations or the logic for the mobile cookie system 100 and the logic circuit 1130 using the processing component 1140. The processing component 1140 (and / or PHY 1126 and / or MAC 1128) may comprise various hardware elements, software elements, or a combination of both. Examples of hardware elements may include devices, logic devices, components, processors, microprocessors, circuits, processor circuits, circuit elements (for example, transistors, resistors, capacitors, inductors, etc.), integrated circuits, application integrated circuits specific (ASIC), programmable logic devices (PLD), digital signal processors (DSP, by its acronym in English), matrix of doors program in situ (FPGA), memory units, logic gates, registers, semiconductor devices, chips, microchips, chipsets, and so on. Examples of software elements may include software components, programs, applications, computer programs, application programs, system programs, software development programs, machine programs, operating system software, intermediate support, firmware, software modules , routines, subroutines, functions, methods, procedures, software interfaces, application program interfaces (APIs), instruction sets, computer code, computer code, code segments, computer code segments, words, values, symbols, or any combination of them. The determination of whether a modality is implemented using hardware elements and / or software elements may vary according to any number of factors, such as desired computer speed, power levels, heat tolerances, processing cycle budget, data rates input, output data rates, memory resources, data bus speeds and other design or performance limitations, as desired for a given application.
The 1130 computing platform may also include other 1150 platform components. Other 1150 platform components include common computer elements, such as one or more processors, multi-core processors, coprocessors, memory units, chipsets, controllers, peripherals, interfaces, oscillating circuits, timing devices, video cards, cards audio, input / output (l / O) multimedia components (for example, digital displays), power supplies, and so on. Examples of memory units may include, without limitation, various types of computer-readable and computer-readable storage media in the form of one or more higher-speed memory units, such as read-only memory (ROM). English), random access memory (RAM), dynamic RAM (DRAM), double data rate DRAM (DDRAM), synchronous DRAM (SDRAM, for its acronym in English), static RAM (SRAM), programmable ROM (PROM), programmable erasable ROM (EPROM), electrically erasable programmable ROM (EEPROM) , for its acronym in English), flash memory, polymer memory such as ferroelectric polymer memory, ovonic memory, phase or ferroelectric change memory, silicon-oxidonitride-silicon oxide (SONOS) memory, magnetic or optical cards, a wide variety of devices such as redundant array of independent disk drives (RAID), solid-state memory devices (e.g., USB stick, solid-state drives (SSD) acronym in English) and any other type of storage medium suitable for storing information.
The device 1100 may be, for example, an ultra-mobile device, a mobile device, a fixed device, a machine-to-machine (M2M) device, a personal digital assistant (PDA). , a mobile computing device, a smartphone, a telephone, a digital telephone, a cell phone, user equipment, e-book readers, a handset, a unidirectional locator, a bidirectional locator, a messaging device, a computer, a personal computer (PC), a desktop computer, a laptop, a portable computer, a portable mini computer, a pocket computer, a tablet PC, a server , an array of servers or server park, a web server, a network server, an internet server, a workstation, a mini-computer, a host, a supercomputer, a network device, a web device, a distributed computer system, multiprocessor systems, processor-based systems, electronic consumer device, programmable electronic consumer device, gaming devices, television, digital television, connection box, wireless access point , base station, node B, evolved node B (eNB), subscriber station, mobile subscriber center, radio network controller, router, hub, gateway, bridge, switch, machine, or combination thereof. Accordingly, the specific functions and / or configurations of the device 1100 described herein may be included or omitted in various modalities of the device 1100, as suitably desired. In some embodiments, the device 1100 may be configured to be compatible with the protocols and frequencies associated with one or more of the 3GPP LTE specifications and / or IEEE 1102.16 standards for WMAN, and / or other wireless broadband networks, cited herein. document, although the modalities are not limited in this aspect.
<img file="MX366183B_D0017.tif" />
The modalities of the 1100 device can be implemented using single-input single-output architectures (SISO). However, certain implementations may include multiple antennas (e.g., 1118 antennas) for transmission and / or reception using adaptive antenna techniques for beam formation or multiple access spatial division (SDMA) and / or using MIMO communication techniques.
The components and features of the 1100 device can be implemented using any combination of discrete circuits, application specific integrated circuits (ASIOs), logic gates and / or single chip architectures. In addition, the features of the device 1100 can be implemented using microcontrollers, programmable logic matrices and / or microprocessors or any combination of the foregoing, where conveniently appropriate. It is noted that the hardware, firmware and / or software elements may be collectively or individually referred to herein as "logic" or "circuit."
It should be appreciated that the exemplary device 1100 shown in the block diagram of Figure 11 may represent a functionally descriptive example of many possible implementations. Consequently, the division, omission or inclusion of the block functions represented in the attached figures does not infer that the hardware components, circuits, software and / or elements for the implementation of these functions would necessarily have to be divided, omitted or included in the modalities
Some modalities can be described using the expression "any modality" or "a modality", together with their derivatives. These terms mean that a property, structure, or characteristic described in relation to the modality is included in at least one modality. The occurrences of the phrase "in one modality" in several places in the specification do not necessarily all refer to the same modality. In addition, some modalities can be described using the expression coupled and connected, together with their derivatives. These terms do not necessarily pretend to be synonymous with each other. For example, some modalities may be described by the terms "connected" and / or "coupled" to indicate that two or more elements are in direct physical or electrical contact with each other. The term coupled, however, can also mean that two or more elements are not in direct contact with each other, but still cooperate or interact with each other.
With general reference to the annotations and nomenclature used in this document, the detailed descriptions in this document may be presented in terms of program procedures executed on a computer or computer network. These descriptions and procedural representations are used by those skilled in the art to more effectively convey the essence of their work to other experts in the art.
A procedure, in this document, is proposed, and generally conceived to be a sequence consistent with the operations that lead to a desired result. These operations are those that require physical manipulations of physical quantities. Generally, but not necessarily, these quantities take the form of electrical, magnetic or optical signals capable of being stored, transferred, combined, compared and otherwise handled. Sometimes it proves to be convenient, mainly for reasons of common use, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers or the like. It should be noted, however, that all of these and similar terms will be associated with the appropriate physical quantities and are merely convenient labels applied to those amounts.
In addition, the manipulations performed are often mentioned with terms, such as adding or comparing, that are commonly associated with mental operations performed by a human operator. Such capacity of a human operator is not necessary, or desirable in most cases, in any of the operations described herein that are part of one or more modalities. Rather, operations are machine operations. The machines useful for performing the operations of various modalities of performing include general purpose digital computers or similar devices.
Various modalities also refer to devices or systems to perform these operations. This apparatus may be specially constructed for the required purposes, or it may comprise a general purpose computer activated or selectively reconfigured by a computer program stored in the computer. The procedures shown in this document are not inherently related to a particular computer or other device. Several general-purpose machines can be used with the programs written in accordance with the teachings of this document, or it may be convenient to build more specialized devices to perform the required method steps. The structure required for a variety of these machines will be apparent from the description given.
It is emphasized that the brief description is provided to allow a reader to quickly determine the nature of the technical disclosure. It is suggested in the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the above detailed description, it can be noted that various features are grouped into a single modality in order to simplify disclosure. This method of disclosure should not be construed as reflecting an intention that the claimed modalities require more features than those expressly cited in each claim. Rather, as the following claims reflect, the inventive matter lies in less than all of the features of a single modality described. Therefore, the following claims herein are incorporated in the detailed description, where each claim is maintained as a separate modality. In the appended claims, the terms include and in which they are used as simple equivalents of the respective terms to understand and where, respectively. On the other hand, the terms first, second, third, etc., are used merely as labels, and are not intended to impose numerical requirements on their objects.
What has been described above includes the examples of the architecture described. Of course, it is not possible to describe every conceivable combination of components and / or methodologies, but one skilled in the art can recognize that many additional combinations and permutations are possible. Consequently, it is intended that the novel architecture encompasses all the alterations, modifications and variations that lie within the essence and scope of the appended claims.
Contents3
28 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15 Sheet 16 Sheet 17 Sheet 18 Sheet 19 Sheet 20 Sheet 21 Sheet 22 Sheet 23 Sheet 24 Sheet 25 Sheet 26 Sheet 27 Sheet 28
28 members in 11 offices
Priority claims7
| Document | Office | Kind | Date |
|---|---|---|---|
| 14549935 | United States of America | – | |
| 201414549935 | United States of America | A | |
| 201414549935 | United States of America | A | |
| 2014067050 | United States of America | W | |
| 2014067050 | United States of America | W | |
| US201414549935 | – | – | – |
| WO2014US67050 | – | – | – |
Members28
| Document | Office | Kind | |
|---|---|---|---|
| EP3024199A1 | European Patent Office (EPO) | A1 | |
| CA2966163A1 | Canada | A1 | |
| US2016150395A1 | United States of America | A1 | |
| WO2016081014A1 | World Intellectual Property Organization (WIPO) | A1 | |
| US9554267B2 | United States of America | B2 | |
| US2017093591A1 | United States of America | A1 | |
| AU2014412031A1 | Australia | A1 | |
| IL251939D0 | Israel | D0 | |
| KR20170086530A | Republic of Korea | A | |
| MX2017006667A | Mexico | A | |
| JP2017538216A | Japan | A | |
| BR112017010456A2 | Brazil | A2 | |
| CN107534689A | China | A | |
| US9948476B2 | United States of America | B2 | |
| AU2014412031B2 | Australia | B2 | |
| US10326608B1 | United States of America | B1 | |
| MX366183BThis record | Mexico | B | |
| IL251939A | Israel | A | |
| IL251939B | Israel | B | |
| EP3024199B1 | European Patent Office (EPO) | B1 | |
| JP6626107B2 | Japan | B2 | |
| JP2020061741A | Japan | A | |
| CN107534689B | China | B | |
| CN113037847A | China | A | |
| KR102295132B1 | Republic of Korea | B1 | |
| KR20210109647A | Republic of Korea | A | |
| JP6986056B2 | Japan | B2 | |
| KR102359679B1 | Republic of Korea | B1 |
1 legal event, as the office reported them to INPADOC
Events
| Event | Code | |
|---|---|---|
| Grant or registrationFG | FG |
Numbers
- Publication
- 366183
- Publication, DOCDB
- 366183
- Publication, EPODOC
- MX366183
- Application
- 20170006667
- Application, DOCDB
- 2017006667
- Application, EPODOC
- MX20170006667
Titles2
- English
- TECHNIQUES TO ASSOCIATE USER DATA WITH A MOBILE DEVICE.
- Spanish
- TECNICAS PARA ASOCIAR DATOS DE USUARIO CON UN DISPOSITIVO MOVIL.
Classification
- CPC, 13
- H04L61/6022
- H04L67/306
- H04W8/205
- H04L12/2807
- H04L67/18
- H04W4/021
- H04W4/02
- H04L2101/622
- G06Q30/02
- H04L67/52
- H04L67/02
- H04L12/2818
- H04W4/029
- IPC, 7
- H04W4 00
- H04L12 16
- H04L29 12
- H04W4 02
- H04W4 021
- H04W4 029
- H04W8 20