Patent Application
20200344675
The present disclosure relates generally to roaming partner prioritization.
In computer networking, a wireless access point (AP) is a networking hardware device that allows a Wi-Fi compliant client device to connect to a wired network. The AP usually connects to a router (directly or indirectly via a wired network) as a standalone device, but it can also be an integral component of the router itself. Several APs may also work in coordination, either through direct wired or wireless connections, or through a central system, commonly called a wireless local area network (WLAN) controller.
Prior to wireless networks, setting up a computer network in a business, home or school often required running many cables through walls and ceilings in order to deliver network access to all of the network-enabled devices in the building. With the creation of the wireless access point, network users are able to add devices that access the network with few or no cables. An AP normally connects directly to a wired Ethernet connection and the AP then provides wireless connections using radio frequency links for other devices to utilize that wired connection. Most APs support the connection of multiple wireless devices to one wired connection. Modern APs are built to support a standard for sending and receiving data using these radio frequencies.
The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate various embodiments of the present disclosure. In the drawings:
Dynamic roaming partner prioritization based on service quality feedback may be provided. First, a server associated with an enterprise may receive performance data and location data for each of a plurality of service provider networks from a plurality of end use devices associated with the enterprise. Next, the server may assign a ranking to a plurality of service providers by location based upon information. The information may comprise the received performance data and the location data corresponding to each of the plurality of service provider networks. The server may then push the ranking to a first end use device.
Both the foregoing overview and the following example embodiments are examples and explanatory only, and should not be considered to restrict the disclosure's scope, as described and claimed. Furthermore, features and/or variations may be provided in addition to those described. For example, embodiments of the disclosure may be directed to various feature combinations and sub-combinations described in the example embodiments.
The following detailed description refers to the accompanying drawings. Wherever possible, the same reference numbers are used in the drawings and the following description to refer to the same or similar elements. While embodiments of the disclosure may be described, modifications, adaptations, and other implementations are possible. For example, substitutions, additions, or modifications may be made to the elements illustrated in the drawings, and the methods described herein may be modified by substituting, reordering, or adding stages to the disclosed methods. Accordingly, the following detailed description does not limit the disclosure. Instead, the proper scope of the disclosure is defined by the appended claims.
Similarly, the enterprise may have a partnership with more than one service provider (i.e., service partner) for providing connectivity services for its users when they are outside the enterprise premises. However, this may be based on pricing with no ability to consider the performance aspects of the network that the users are experiencing based on the location. Even though Embedded Subscriber Identification Modules (eSIMs) may provide the capability to hold multiple profiles and Remote Subscriber Identification Module (RSIM) architecture may allow for remote provisioning of SIM profiles, conventional processes may not provide a way for the enterprise to influence the profile suitable to its users and activate it depending on the performance of the network based on service quality feedback.
Server 205 may comprise, but is not limited to, a computing device 400 as described in more detail below with respect to
Open roaming identity federation 220 may comprise the open roaming identity federation as described above with respect to
In addition, operating environment 250 may further comprise, a Subscription Manager-Data Preparation+ (SM-DP+) device 255, a cellular network 260, a node 265, and a Subscription Manager-Discovery Server (SM-DS) device 270. SM-DP+ device 255 and SM-DS device 270 may be a part of a Global System for Mobile communications Association (GSMA) consumer solution controlled by a service provider to manage end use devices including RSIM provisioning. SM-DP+ device 255 may create, download, remotely management (e.g., enable, disable, update, and delete) and protect user credentials (i.e., a profile). SM-DS device 270 may allow SM-DP+255 to reach an Embedded Universal Integrated Circuit Card (eUICC) on first end use device 210 without having to know which network first end use device 210 is connected to. This feature may be important because end use devices (e.g., first end use device 210) may be connected using different access networks with different addresses. SM-DS device 270 may overcome this issue by allowing SM-DP+ device 255 to post alerts to a secure noticeboard and by allowing users devices to extract those alerts.
Cellular network 260 may comprise, but is not limited to, a Long-Term Evolution (LTE) broadband cellular network, a Fourth Generation (4G) broadband cellular network, or a Fifth Generation (5G) broadband cellular network, operated by a service provider. Node 265 may comprise a device that may be connected to cellular network 260 that may communicate directly and wirelessly with end use devices (e.g., first end use device 210). Node 265 may comprise, but is not limited to, an eNodeB (eNB) or an eNodeG (eNG).
The elements described above of operating environment 200 and operating environment 250 may be practiced in hardware and/or in software (including firmware, resident software, micro-code, etc.) or in any other circuits or systems. The elements of operating environment 200 and operating environment 250 may be practiced in electrical circuits comprising discrete electronic elements, packaged or integrated electronic chips containing logic gates, a circuit utilizing a microprocessor, or on a single chip containing electronic elements or microprocessors. Furthermore, the elements of operating environment 200 and operating environment 250 may also be practiced using other technologies capable of performing logical operations such as, for example, AND, OR, and NOT, including but not limited to, mechanical, optical, fluidic, and quantum technologies. As described in greater detail below with respect to
Method 300 may begin at starting block 305 and proceed to stage 310 where server 205 may receive performance data and location data for each of a plurality of service provider networks from a plurality of end use devices associated with the enterprise. For example, an enterprise application may be installed by the enterprise on the plurality of end use devices. The plurality of end use devices may include first end use device 210.
The enterprise application on first end use device 210 may be configured to measure and collect detailed Key Performance Indicators (KPIs) for each access network that first end use device 210 attaches too (e.g., Wi-Fi hot spot 230 of
From stage 310, where server 205 may receive the performance data and the location data for each of the plurality of service provider networks from the plurality of end use devices associated with the enterprise, method 300 may advance to stage 320 where server 205 may assign a ranking to a plurality of service providers by location based upon information. The information may comprise, but is not limited to, the received performance data and the location data corresponding to each of the plurality of service provider networks. For example, server 205 may assign weights to reported metrics from the performance data and may factor pricing agreements with different vendors (e.g., service providers) into the ranking process to determine a preferred ranking of service providers for the enterprise's users.
Consequently, embodiments of the disclosure may tie together the enterprise with the service providers (e.g., for both Wi-Fi roaming and cellular roaming) to provide the user devices with preferred networks dynamically. For example, the enterprise may want its employees (e.g., users) to be on a first service provider network in the San Jose area based on the performance data, but while in New York, the enterprise may want its employees (e.g., users) to be on a second service provider network based on the performance data. Furthermore, the enterprise may want its employees (e.g., users) to associate to a first SSID when walking inside a certain environment (e.g., a mall) based on the performance data.
Once server 205 assigns the ranking to the plurality of service providers by location based upon the information in stage 320, method 300 may continue to stage 330 where server 205 may push the ranking to first end use device 210. For example, when roaming in a service partner's Wi-Fi coverage (i.e., the open roaming identity federation example of
When roaming in a service partner's cellular coverage (i.e., the cellular coverage example of
Consistent with embodiments of the disclosure, using the above process, the preferred roaming partner's ranking may be signaled to first user device 210 over a secure link from server 205 or open roaming identity federation 220 and may be updated on first user device 205 to be used for future connections (i.e.,
Computing device 400 may be implemented using a Wireless Fidelity (Wi-Fi) access point, a cellular base station, a tablet device, a mobile device, a smart phone, a telephone, a remote control device, a set-top box, a digital video recorder, a cable modem, a personal computer, a network computer, a mainframe, a router, a switch, a server cluster, a smart TV-like device, a network storage device, a network relay device, or other similar microcomputer-based device. Computing device 400 may comprise any computer operating environment, such as hand-held devices, multiprocessor systems, microprocessor-based or programmable sender electronic devices, minicomputers, mainframe computers, and the like. Computing device 400 may also be practiced in distributed computing environments where tasks are performed by remote processing devices. The aforementioned systems and devices are examples and computing device 400 may comprise other systems or devices.
Embodiments of the disclosure, for example, may be implemented as a computer process (method), a computing system, or as an article of manufacture, such as a computer program product or computer readable media. The computer program product may be a computer storage media readable by a computer system and encoding a computer program of instructions for executing a computer process. The computer program product may also be a propagated signal on a carrier readable by a computing system and encoding a computer program of instructions for executing a computer process. Accordingly, the present disclosure may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.). In other words, embodiments of the present disclosure may take the form of a computer program product on a computer-usable or computer-readable storage medium having computer-usable or computer-readable program code embodied in the medium for use by or in connection with an instruction execution system. A computer-usable or computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
The computer-usable or computer-readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. More specific computer-readable medium examples (a non-exhaustive list), the computer-readable medium may include the following: an electrical connection having one or more wires, a portable computer diskette, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, and a portable compact disc read-only memory (CD-ROM). Note that the computer-usable or computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted, or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.
While certain embodiments of the disclosure have been described, other embodiments may exist. Furthermore, although embodiments of the present disclosure have been described as being associated with data stored in memory and other storage mediums, data can also be stored on or read from other types of computer-readable media, such as secondary storage devices, like hard disks, floppy disks, or a CD-ROM, a carrier wave from the Internet, or other forms of RAM or ROM. Further, the disclosed methods' stages may be modified in any manner, including by reordering stages and/or inserting or deleting stages, without departing from the disclosure.
Furthermore, embodiments of the disclosure may be practiced in an electrical circuit comprising discrete electronic elements, packaged or integrated electronic chips containing logic gates, a circuit utilizing a microprocessor, or on a single chip containing electronic elements or microprocessors. Embodiments of the disclosure may also be practiced using other technologies capable of performing logical operations such as, for example, AND, OR, and NOT, including but not limited to, mechanical, optical, fluidic, and quantum technologies. In addition, embodiments of the disclosure may be practiced within a general purpose computer or in any other circuits or systems.
Embodiments of the disclosure may be practiced via a system-on-a-chip (SOC) where each or many of the element illustrated in
Embodiments of the present disclosure, for example, are described above with reference to block diagrams and/or operational illustrations of methods, systems, and computer program products according to embodiments of the disclosure. The functions/acts noted in the blocks may occur out of the order as shown in any flowchart. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved.
While the specification includes examples, the disclosure's scope is indicated by the following claims. Furthermore, while the specification has been described in language specific to structural features and/or methodological acts, the claims are not limited to the features or acts described above. Rather, the specific features and acts described above are disclosed as example for embodiments of the disclosure.
