Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W8/00—Network data management
  • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
  • H04W8/183—Processing at user equipment or user record carrier
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W48/00—Access restriction; Network selection; Access point selection
  • H04W48/02—Access restriction performed under specific conditions
  • H04W48/04—Access restriction performed under specific conditions based on user or terminal location or mobility data, e.g. moving direction, speed
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W48/00—Access restriction; Network selection; Access point selection
  • H04W48/18—Selecting a network or a communication service

Definitions

• the present technology pertains in general to providing a dynamic selection process for selecting an identity for a mobile device to connect to a wireless access provider based on a geographical location of the mobile device among other factors.
• FIG. 1 illustrates an example of network architecture and associated components, according to an aspect of the present disclosure
• FIG. 2 describes an example process for generation a database to be used for geo-location based identity selection for wireless connections, according to an aspect of the present disclosure
• FIG. 3 describes an example process for geo -location based identity selection for wireless connections, according to an aspect of the present disclosure.
• FIG. 4 illustrates an example system including various hardware computing components, according to an aspect of the present disclosure.
• Reference to“one embodiment” or“an embodiment” means that a particular feature, structure, or characteristic described in connection widi die embodiment is included in at least one embodiment of the disclosure.
• the appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments.
• various features are described which may be exhibited by some embodiments and not by others.
• a client can include a device and/or application seeking to execute a function on an Execution Endpoint.
• Non-limiting examples of a client can include a mobile phone, a laptop, a tablet, etc.
• a method includes determining, by one or more processors, a location of a mobile device; identifying, by the one or more processors, an access provider having a network for the mobile device to connect to; selecting, by the one or more processors, one of a plurality of identities associated with the mobile device for authorizing connection to the network of the access provider, the selection being based on the location of the mobile device and connection parameters specified by the access provider; and establishing, by the one or more processors, the connection of the mobile device to the network of the access provider using the one of the plurality of identities.
• a network component has one or more identity providers and one or more access providers registered therewith.
• the network component includes memory having computer-readable instructions stored therein and one or more processors.
• the one or more processors configured to execute the computer-readable instructions to determine a location of a mobile device; identify an access provider from the one or more access providers having a network for the mobile device to connect to; select an identity provided by one of the one or more identity providers, the identity being associated with the mobile device for authorizing connection to the network and being selected based on the location of the mobile device and connection parameters specified by the access provider and connect the mobile device to the network using the selected identity.
• one or more non- transitory computer- readable medium have computer-readable instructions stored therein, which when executed by one or more processors of a network component, cause the one or more processors to determine a location of a mobile device; identify a plurality of access providers each having a network for the mobile device to connect to; based on corresponding connection parameters associated with each of the plurality of access providers and the location of the mobile device, select one of the plurality of access providers and an identity associated with the mobile device for attaching the mobile device to a network of the one of the plurality of access providers; and attaching the mobile device to the network of the one of the plurality of access providers.
• roaming exchange there may be a centralized service provider referred to as a roaming identity federation provider (ID federation provider) to which various service providers and identity providers can subscribe/register with.
• ID federation provider a roaming identity federation provider
• Examples of service providers can include, but are not limited to, entities providing internet access (e.g., a WiFi access). This can be any known or to be developed access provider. For example, a business entity may provide a WiFi access for its patrons and customers to connect to. A wireless carrier can be another example of an access provider.
• entities providing internet access e.g., a WiFi access
• This can be any known or to be developed access provider.
• a business entity may provide a WiFi access for its patrons and customers to connect to.
• a wireless carrier can be another example of an access provider.
• Examples of identity providers can include, but is not limited to, any known or to be developed social service provider with which users can set up accounts having associated user names and passwords (user credentials). Examples include email service providers, social platform providers (e.g., Google and Facebook), etc. Other examples of identity providers include businesses that provide user credentials to their employees. Such identities may be referred to as business identities.
• a user having an associated mobile device may have multiple registered identities each provided by a different identity provider when roaming, whenever the user and the associated mobile device is detected within a coverage area of a service provider that is part of the consortium (roaming exchange), the ID federation provider may retrieve various identities associated the user, present the available identities to the user on the mobile device, receive a selection of one of the identities via the mobile device, authenticate the user's selected identity with a corresponding identity provider and enable the mobile device to roam on the service provider's access network.
• the ID federation provider simplifies the process of mobile devices eStablishing a connection to a nearby access provider, there is still a level of interaction and user intervention required, as described above (e.g., the user needs to select an identity to be used for authenticating user’s access to the access provider’s network).
• example embodiments will be described that further simplify the above process by providing a geo-location based identity selection for connecting to an access point, w'hich eliminates any need for user intervention and provides a seamless (from the user perspective) process for connecting to an access provider’s network.
• the disclosure begins with a description of a setting in which geo-location based identity selection for seamless connection to an access network can be implemented.
• FIG. 1 illustrates an example of network architecture and associated components, according to an aspect of the present disclosure.
• architecture 100 includes a cloud hosted open roaming identity federation provider 102 (ID federation provider 102).
• ID federation provider 102 may be hosted on or more servers operated by a provider such as Cisco Technology, Inc. of San Jose, CA.
• FIG. 1 further shows identity providers 104 and 106.
• Identity providers 104 and 106 may be different private or public platforms, outlets or organizations which users regLster and have a profile and associated authentication credentials. Examples of identity providers include, but are not limited to, those described above.
• FIG. 1 also shows service providers 108, 110 and 112, examples of which include, but are not limited to, those described above.
• service provider 108 and 112 may be different WiFi Access providers while service provider 1 10 is a wireless carrier access provider.
• service provider 110 can be an LTE nodeB, to which a mobile device may attach.
• Service provider 110 can provide any known or to be developed wireless technology to its subscribers including, but not limited to, Long Term Evolution (LTE) access network, a 5 th Generation (5G) network, etc.
• LTE Long Term Evolution
• 5G 5 th Generation
• all or some of access providers 108, 110 and 112 can be part of the same 5G network.
• a single entity can be both an identity provider and an access provider.
• FIG. 1 further shows a user 114 having an associated mobile device 116. Furthermore, user 114 and mobile device 116 are shown to be present within coverage area of access provider 112.
• access provider 112 provides wireless access to devices within a physical building, location, etc.
• the present disclosure Ls not limited to mobile device 116 being in the coverage area of only a single access provider at any time but may be within coverage areas of multiple access providers, simultaneously.
• Examples of mobile device 116 include, but are not limited to, any portable device capable of establishing a wireless connection with a service provider such as a smart phone, a mobile device, a laptop, a tablet, a personal digital assistant (PDA), etc.
• a service provider such as a smart phone, a mobile device, a laptop, a tablet, a personal digital assistant (PDA), etc.
• architecture 100 Communications between various components of architecture 100 described above, can be based on any known, or to be developed, method of wireless (and/or wired) communication scheme. Furthermore, while certain components have been shown and described with reference to architecture 100, architecture 100 Is not limited thereto. Architecture 100 and its components may include any additional component or element necessary and ordinary to their operations and functionalities.
• FIG. 1 illustrates a certain number of access providers, identity providers and mobile devices, the present disclosure is not limited thereto. There can be more or less identity providers and access providers registered with ID federation provider 102. Furthermore, there can be more than one user and associated mobile devices attempting to gain access to an access provider’s network
• access provider 112 when mobile device 116 is present in the coverage area of access provider 112 and assuming that user 1 14 has multiple identities (e.g., one identity with each of identity providers 104 and 106), a list of two identities will be presented to user 114 on mobile device 116. User 114 then selects one of the presented identities. Upon receiving the selected identity, access provider 112 authenticates user 114, using known or to be developed authentication procedures, via ID federation provider 102 and the corresponding identity provider (e.g., one of identity providers 104 and 106) before providing mobile device 116 access to access provider 112’s network
• the identity selected on mobile device 1 16 by user 1 14 will be used as the default identity for user 114 whenever an access provider’s network that is associated with ID federation provider 102 is detected on mobile device 116 until user 114 selects another identity.
• This default use of a selected identity and die still existing level of interaction required from user 114 presents two challenges.
• user 114 may not want to use one identity to gain access to all different access providers’ networks. For example, when user 114 Is within coverage area of a WiFi network provided by a coffee shop, user 114 may not wish and/or be allowed to use his or her business identity to connect to the coffee shop’s WiFi network.
• user 114 may not wish to use a particular identity provided by a social media platform such as Facebook at the coffee shop but may instead wish to use another identity of user 114.
• the identity selection process can be made more seamless by eliminating the need for selection of an identity on a user’s mobile device.
• geo-location based identity selection addresses the above described challenges.
• FIG. 2 describes a process for generation a database to be used for geo- location based identity selection for wireless connections, according to an aspect of the present disclosure.
• FIG. 2 will be described from the perspective of ID federation provider 102. However, it will be understood that ID federation provider 102 has one or more processors execution computer-readable instructions stored on one or more memories thereof to perform the process of FIG. 2.
• FIG. 2 described an example process according to which ID federation provider 102 constructs (generates) databases, which will be used for geo-location based identity selection as will be described below with reference to FIG. 3.
• ID federation provider 102 receives a registration request from an access provider (which can also be an identity provider).
• the registration request can include information such as, but not limited to, access providers identification information and connection parameters.
• Connection parameters can specify conditions according to which a mobile device may attach or connect to access provider’s network.
• access provider can be a corporation or a business entity that only allows access to its network when a business identity issued by the corporation is used.
• access provider can also specify other business identities (3 rd party business identities) that may be used for attachment to its network. This can, for example, be business identities issued by business partners of the corporation, a client of the corporation, etc.
• an access provider can specify a category of identities that may be used to for attachment to its network (e.g., any registered social network provided identity, any registered business identity, etc., where the registration is with ID federation provider 102 as part of the roaming exchange mentioned above).
• Connection parameters can also specify times and days according to which certain identities can be used to attach to its network.
• the corporation in this example can specify that 3 ld party business identities can access its network during business hours (e.g., SAM to 5PM) from Monday to Friday but not on Saturdays and Sundays.
• Connection parameters can also specify different privileges for different identities. For example, devices that attach to the corporation’s network using business identities issued by die corporation can be allowed to access a different network (e.g., with more access privileges) than devices that attach using 3 rd party business identities (with less access privileges).
• the corporation of example above can allow limited access to any valid identity during certain times (e.g., outside business hours). This will also be specified as a connection parameter.
• Connection parameters can also specify one or more geo-locations where roaming or access to provider’s network is permitted. For example, access to those logging in with 3 rd party business identities may be limited to within a certain distance (e.g., 200ft, a mile, etc.) of physical promises of the corporation. In another example, access to all valid identities outside business hours can be limited to a different geographical location (e.g., one corresponding to a parking lot of the corporation or a certain distance outside the physical premise of the corporation such as a perimeter of 100ft to half a mile surrounding the corporation’s building.
• a certain distance e.g. 200ft, a mile, etc.
• access to all valid identities outside business hours can be limited to a different geographical location (e.g., one corresponding to a parking lot of the corporation or a certain distance outside the physical premise of the corporation such as a perimeter of 100ft to half a mile surrounding the corporation’s building.
• connection parameters which are non- limiting of the scope of the present disclosure.
• ID federation provider 102 process the registration request and registers the access/identity provider.
• ID federation provider 102 stores connection parameters and the identification of the access provider from which the request is received at S200 in a database associated with ID federation provider 102.
• the registration request and example connection parameters described with reference to S200. S202 and S204 have been described with respect to a request received from an access provider.
• the request received at S200 can also be a registration request received from an identity provider.
• ID federation provider 102 receives information regarding credentials of particular user, information identifying user's associated devices such a mobile device 116, etc.
• ID federation provider 102 completes the registration of an identity provider and stores the data in the database in the same manner as described above with reference to S202 and S204.
• FIG. 3 describes an example process for geo -location based identity selection for wireless connections, according to an aspect of the present disclosure.
• FIG. 3 will be described from the perspective of ID federation provider 102.
• ID federation provider 102 can have one or more processors executing computer-readable instructions stored on one or more memories thereof to perform die process of FIG. 3.
• FIG. 3 will be described with reference to example embodiments of FIG. 1
• ID federation provider 102 determines/detects that mobile device 116 is within coverage area of access provider 112. This determination may be based on any known or to be developed method. For example, access provider 112 may detect the presence of mobile device 116 in its coverage area based on exchange of beacon information, a response to a“hello” message transmitted by one or more access points of service provider 116, etc. More specifically, access provider 112 may detect MAC address of mobile device 1 16 and transmit the same to ID federation 102. At S300, ID federation provider 102 may detect that mobile device 116 is within the coverage area of multiple access providers (e.g., access provider 110 and 112).
• multiple access providers e.g., access provider 110 and 112
• ID federation provider 102 determines, by referencing a table of identity providers stored as described with reference to FIG. 2, identities of user 114 associated with mobile device 116 (using mobile device 116’s MAC address).
• ID federation provider 112 determines geo-location of mobile device 116.
• a geo-location of mobile device 116 may be determined according to any- known, or to be developed method such as using Global Positioning System (GPS) signals, cell tower triangulation as well as WiFi positioning systems.
• GPS can offer position accuracy of between 8 and 3 meters, subject to a number of known variables.
• Cell towers triangulation accuracy can vary widely, subject to the density of cell towers and features within the landscape.
• Cell tower accuracies can vary between, for example, 400 to 1400 meters.
• Some device operating systems used on devices include background location services that can collect W'iFi access point details along w'ith the GPS or cell tower triangulation-derived location, send the collected information to the operating system vendor or another operating entity to derive location information of a mobile device.
• the accuracy of such methods can vary widely, subject to the coverage of WiFi access points. Such variation can be between 10 to 100 meters.
• mobile device 116 can have known or to be developed on-board accelerometers, gyroscopes, magnetometers, etc. which can record, at a finer grain, movement of mobile device 116, which can then be used to augment location information derived from GPS signals, cell tower triangulation, etc.
• a device’s IP address assignment can also be used in further refining a device’s location information.
• ID federation provider 102 determines if mobile device 116 is attempting to connect to access provider 112’s network for the first time. For example, ID federation provider 102 determines if, in a database described with reference to FIG. 2, there is a record of past connections/attachments of mobile device 116 to access provider 112’s network. If there is, the answer in S304 is no. If there is none, the answer in S304 is yes. [0060] If at S304, ID federation provider 102 determines that mobile device 116 is attempting to connect to access provider 112’s network for the first time, then at S306, ID federation provider 102 selects one of the identities associated with user 1 14 of mobile device 116 determined at S302.
• ID federation provider 102 makes this determination, in part based on connection parameters specified by access provider 102 and stored in the database of ID federation provider 102, as described above.
• access provider 112 may be that of Company X and at the time of registering with ID federation provider 102, Company X may have specified several connection parameters.
• user identities associated with customers e.g., Company Y
• Another connection parameter may be that mobile devices seeking access to access provider 112’s network should be within 100 feet of access provider 112' s physical location(s).
• ID federation provider 102 determines that user 114 has an identity provided by Company Y and is at the location of Company X (service provider 112) at 11 AM on a Tuesday. Accordingly, ID federation provider 102 selects user 114' s business identity with Company Y as the identity to attach to access provider 112’s network.
• ID federation provider 102 determines if an identity is selected at S306. For example, user 114 may not have any identity that matches connection parameters of access provider 112. If not, at S310, ID federation provider 102 generates and sends a notification to mobile device 116 indicating that mobile device 116 cannot access/attach to access provider 112’s network (access denial).
• ID federation provider 102 determines that an identity is selected, then at S312, ID federation provider 102 authenticates/eonfirms user 114’s selected identity with a corresponding identity provider (e.g., one of identity providers 104 and 106 of FIG. 1). For example, ID federation provider 102 communicates with Company Y’s database that has provided user 114’s business identity selected at S306 to confirm user 114’s identity (according to any known, or to be developed, authentication process). [0064] At S314, ID federation provider 102 determines if user 114’s selected identity is confirmed. If not, the process reverts back to S310, where ID federation provider 102 denies mobile device 116’s attempted access to access provider 112’s network and sends a notification of denial to mobile device 116.
• ID federation provider 102 determines if user 114’s selected identity is confirmed. If not, the process reverts back to S310, where ID federation provider 102
• ID federation provider 102 determines that user 114’s identity has been confirmed, then at S316.
• ID federation provider 102 attaches mobile device 1 16 in access provider 112’s network and records details on mobile device 116’s connection to access provider 112’s network. Details can include, but are not limited to, geo-location information of mobile device 116, time stamp and duration of attachment to access provider 112’s network, etc.
• ID federation provider 102 determines that mobile device 116’s attempt to attach to access provider 112’s network is mi a first attempt to do so, at S320, ID federation provider 102, retrieves connection parameters of access provider 112 stored in a database.
• ID federation provider 102 selects an identity for attaching mobile device 116 to access provider 112's network. For example, ID federation provider 102 determines if geo-location information of mobile device 116 matches those specified by connection parameters of access provider 112 and/or corresponds to (e.g., within a margin of error of/deviates from) a record of previous geo-location of mobile device 116 during a prior attachment to the network of access provider 112.
• the margin of error may be a configurable parameter determined based on empirical studies and can be for example +/- 10%.
• access provider 112 may specify connection parameters that limit access to its network based on a geographical location of a mobile device. For example, while access provider 112’s network coverage may extend out from a physical location of access provider 112 to its surrounding areas or adjacent roads, streets, parking lots, adjacent buildings, etc., access provider 112 may wish to only allow access to its network when a mobile device is within access provider 112’s building and not, for example, in the parking lot. [0069] Therefore, even if user 114 of device 116 has a business identity that matches corresponding connection parameters specified by access provider 112, if mobile device 116 is not within the specified geographical location, access provider 112 would deny mobile device 116 access to its network.
• ID federation provider 102 determines if an identity is selected at S324. For example, user 114 may not have any identity that matches connection parameters and specified geo-location limitations of access provider 112. If not, at S326, ID federation provider 102 generates and sends a notification to mobile device 116 indicating that mobile device 116 cannot access/attach to access provider 112’s network (access denial message).
• ID federation provider 102 determines that an identity is selected, then at S328, ID federation provider 102 authenticates/confirms the selected identity with a corresponding identity provider (e.g., one of identity providers 104 and 106 of FIG. 1), in a similar manner as described above with reference to S312.
• a corresponding identity provider e.g., one of identity providers 104 and 106 of FIG. 1.
• ID federation provider 102 determines if user 114’s selected identity is confirmed. If not, the process reverts to S326, where ID federation provider 102 denies mobile device 116’s attempted access to access provider 112’s network and sends a notification of access denial to mobile device 116.
• ID federation provider 102 determines that user 1 14’ s identity has been confirmed, then at S332, ID federation provider 102 attaches mobile device 116 to access provider 112’s network and records details on mobile device 116’s connection to access provider 112’s network. Details can include, but are not limited to, geo-location information of mobile device 116. time stamp and duration of attachment to access provider 112’s network, etc. Thereafter, the process ends.
• ID federation provider 102 to select an identity for network connection based on geo-location information of mobile device 116.
• identity provided by an identity provider that is also registered with ID federation provider 102
• federation provider 102 seamlessly establishes a connection to said access provider’s network using the appropriate identity associated with mobile device 1 16.
• Company X As another example, assume that after visiting Company X’s physical site and connecting to access provider 112's network using the identity provided by Company Y, as described above, user 114 exits Company X’s physical site and proceeds to a local restaurant.
• the local restaurant may be another example of an access provider providing WiFi access to its patrons and customers, who is registered with ID federation provider 102.
• user 114 had previously visited the local restaurant and used one of user’s social/public identities to gain access to the local restaurant’s WiFi network.
• connection parameters specified by the local restaurant and stored in a database by ID federation provider 102 indicates that all verified identities (e.g., registered with ID federation provider 102) can be used to access its WiFi network as long as a customer is physically- located inside the local restaurant.
• the WiFi access network of the local restaurant may be detected by mobile device 116 as soon as mobile device 1 16 enters a perimeter around the local restaurant.
• ID federation provider 102 would not select any of user 114’s identities to connect to local restaurant’s WiFi network, because geo-location information of mobile device 116 indicates that it is currently close to but still outside of the local restaurant.
• ID federation provider 102 upon entering the local restaurant’s building and given that ID federation provider 102 has a record of user 114 having previously used a social/public identity at the local restaurant, ID federation provider 102 automatically selects die same social/public identity of user 114, authenticates user 114’s credentials with the corresponding identity provider (e.g., identity provider 104) and allows mobile device 116 to be seamlessly connected to the local restaurant’s WiFi network.
• identity provider 104 e.g., identity provider 104
• user 114 may be given a notification of the established connection and may have an option on a screen of mobile device 116 to reject (override) or modify (e.g., select another identity for connecting) the connection.
• the option to reject or modify may be time limited. For example, if no input is received on mobile device 1 16 to reject or modify the established connection, then ID federation provider 102 assumes that the connection is acceptable and records information about the connection in a database as described above.
• example devices that can be used as components such as ID federation provider 102, mobile device 116, any one of access providers 108, 110 and 112 and/or any one of identity providers 104 and 106.
• FIG. 4 illustrates an example system including various hardware computing components, according to an aspect of the present disclosure. The more appropriate embodiment will be apparent to those of ordinary skill in the art when practicing the present technology. Persons of ordinary skill in the art will also readily appreciate that other system embodiments are possible.
• FIG. 4 illustrates a system bus computing system architecture 400 wherein the components of the system are in electrical communication with each other using a connection 406.
• Exemplary system 400 includes a cache 402 and a processing unit (CPU or processor) 404 and a system connection 406 that couples various system components including the system memory 420, such as read only memory (ROM) 418 and random access memory (RAM) 416, to the processor 404.
• the system 400 can include a cache of high- speed memory connected directly with, in close proximity to, or integrated as part of the processor 404.
• the system 400 can copy data from the memory 420 and/or the storage device 408 to the cache 402 for quick access by the processor 404.
• die cache can provide a performance boost that avoids processor 404 delays while waiting for data.
• These and other modules can control or be configured to control the processor 404 to perform various actions.
• Other system memory 420 may be available for use as well.
• the memory 420 can include multiple different types of memory with different performance characteristics.
• the processor 404 can include any general purpose processor and a service component, such as service 1 410, service 2 412, and service 3 414 stored in storage device 408, configured to control the processor 404 as well as a special-purpose processor where software instructions are incorporated into the actual processor design.
• the processor 404 may essentially be a completely self-contained computing system, containing multiple cores or processors, a bus, memory controller, cache, etc.
• a multi-core processor may be symmetric or asymmetric.
• an input device 422 can represent any number of input mechanisms, such as a microphone for speech, a touch-sensitive screen for gesture or graphical input, keyboard, mouse, motion input, speech and so forth.
• An output device 424 can also be one or more of a number of output mechanisms known to those of skill in the an.
• multimodal systems can enable a user to provide multiple types of input to communicate with the computing device 400.
• the communications interface 426 can generally govern and manage the user input and system output There is no restriction on operating on any particular hardware arrangement and therefore the basic features here may easily be substituted for improved hardware or firmware arrangements as they are developed.
• Storage device 408 is a non-volatile memory and can be a hard disk or other types of computer readable media which can store data that are accessible by a computer, such as magnetic cassettes, flash memory cards, solid state memory devices, digital versatile disks, cartridges, random access memories (RAMs) 416, read only memory (ROM) 418, and hybrids thereof.
• the system 400 can include an integrated circuit 428, such as an application-specific integrated circuit (ASIC) configured to perform various operations.
• the integrated circuit 428 can be coupled with the connection 406 in order to communicate with other components in the system 400.
• the storage device 408 can include software services 410, 412, 414 for controlling die processor 404. Other hardware or software modules are contemplated.
• the storage device 408 can be connected to the system connection 406.
• a hardware module that performs a particular function can include the software component stored in a computer-readable medium in connection w'ith the necessary hardware components, such as the processor 404, connection 406, output device 424, and so tbrdi, to carry out die function.
• the computer-readable storage devices, mediums, and memories can include a cable or wireless signal containing a bit stream and die like.
• non-transitory computer-readable storage media expressly exclude media such as energy, carrier signals, electromagnetic waves, and signals per se.
• Methods according to the above-described examples can be implemented using computer-executable instructions that are stored or otherwise available from computer readable media.
• Such instructions can comprise, for example, instructions and data which cause or otherwise configure a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. Portions of computer resources used can be accessible over a network.
• the computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, firmware, or source code.
• Examples of computer-read able media that may be used to store instructions, information used, and/or information created during methods according to described examples include magnetic or optical disks, flash memory, USB devices provided with non-volatile memory, networked storage devices, and so on.
• Devices implementing methods according to these disclosures can comprise hardware, firmware and/or software, and can take any of a variety of form factors. Typical examples of such form factors include laptops, smart phones, small form factor personal computers, personal digital assistants, rackmount devices, standalone devices, and so on. Functionality described herein also can be embodied in peripherals or add-in cards. Such functionality can also be implemented on a circuit board among different chips or different processes executing in a single device, by way of further example.
• the instructions, media for conveying such instructions, computing resources for executing them, and other structures for supporting such computing resources are means for providing the functions described in these disclosures.
• Claim language reciting "at least one of' a set indicates that one member of the set or multiple members of the set satisfy the claim
• claim language reciting“at least one of A and B” means A, B, or A and B.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Computer Security & Cryptography (AREA)
• Databases & Information Systems (AREA)
• Mobile Radio Communication Systems (AREA)

Applications Claiming Priority (1)

Publications (2)

Family

ID=69645320

Family Applications (1)

Country Status (2)

Families Citing this family (6)

Family Cites Families (10)

• 2018
  • 2018-08-30 EP EP18932096.3A patent/EP3845003A4/de active Pending
  • 2018-08-30 WO PCT/US2018/048923 patent/WO2020046348A1/en not_active Ceased

Also Published As

Similar Documents

Legal Events