Method and system for detecting and minimizing harmful network device and application behavior on cellular networks

A computer-implemented method and system for detecting and minimizing harmful network device and application behavior on a cellular network are disclosed. The method and system comprise providing predefined rules of behavior for a deployed device on a cellular network, wherein the deployed device is a device with cellular connectivity deployed with an application; and monitoring network behavior of the deployed device based upon self certification of the application and testing of the deployed device to detect harmful behavior of the deployed device.

FIELD OF THE INVENTION

The present invention relates generally to cellular networks and more particularly to the behavior on cellular networks of devices connected to the network and the applications operating in conjunction with such devices.

BACKGROUND

Industry experts predict that over 50 billion devices will be connected in the Internet of Things (IoT), and many of those devices will use cellular networks for connectivity. Similar to the Internet itself, innovation fueled by low device cost, very low barriers to application development and deployment of solutions containing such applications operating the devices will drive this massive explosion of devices. Unfortunately, absorbing this growth poses challenges for cellular networks, which are fundamentally different from the networks supporting the internet for a number of reasons. Devices deployed on cellular networks must connect to and disconnect from those networks more frequently than devices connected to wired internet networks. Network elements that authenticate devices trying to connect are highly concentrated, and access to network resources, such as cell towers, is geographically concentrated and restricted. Accordingly, cellular devices and applications that are poorly designed or operating improperly can impact other users of the cellular network much more directly than in the normal internet, especially in the case of connected machines whose behavior is controlled by algorithms rather than random action of individuals. For example, it is unlikely that every human in proximity to a given cell tower will choose to initiate a data session at precisely the same moment in time, but a group of machines programmed to operate in a particular way could do so, overloading network resources.

This creates a conflict between people developing integrated service solutions, where devices are connected with specific service oriented applications, who want unrestricted access to cellular networks, and cellular network carriers who want to limit network access to service solutions that do not behave in a harmful manner. In an ideal circumstance, cellular network carriers would approve service solutions before permitting them to access the network. While it is possible for a party intending to deploy service solutions on a cellular network to request that the cellular network carrier verify and certify that the devices deployed as service solutions operate in conformance with that carrier's rules, such certification is both time-consuming and costly. Publication by the carrier of guidelines for device and application behavior, while informative, does not prove compliance to the carrier or allow the party intending to deploy such service solutions to test actual operation and confirm conformance prior to commercial deployment.

Hence, it is desirable to provide a system and method which address the above identified issues. The system and method should be easy to implement, cost effective and adaptable to existing systems. The present invention addresses such a need.

SUMMARY

A computer-implemented method and system for enabling persons intending to deploy integrated service solutions, where devices are connected with specific service oriented applications on cellular networks, to determine on a self-service basis if such devices (and applications operating with respect to such devices) behave in conformance with the cellular carrier's requirements and for detecting and minimizing harmful behavior of devices and applications deployed as integrated service solutions on a cellular network are disclosed. The computer-implemented method and system comprise providing predefined rules of behavior for a deployed device on a cellular network, wherein the deployed device is a device with cellular connectivity deployed with an application; and monitoring network behavior of the deployed device based upon self certification of the application and testing of the deployed device to detect harmful behavior of the deployed device.

DETAILED DESCRIPTION

The present invention relates generally to cellular networks and more particularly to the behavior of applications and devices with cellular connectivity deployed as integrated service solutions. The following description is presented to enable one of ordinary skill in the art to make and use the invention and is provided in the context of a patent application and its requirements. Various modifications to the preferred embodiments and the generic principles and features described herein will be readily apparent to those skilled in the art. Thus, the present invention is not intended to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features described herein.

A computer-implemented method and system for enabling persons intending to deploy integrated service solutions, where devices are connected with specific service oriented applications on cellular networks, to determine on a self-service basis if such devices (and applications operating with respect to such devices) behave in conformance with the cellular carrier's requirements and for detecting and minimizing harmful behavior of devices and applications deployed as integrated service solutions on a cellular network are disclosed. The method and system comprise a way for a device manufacturer, integrated solution provider, device user or other party (referred to for convenience as a “device owner”), on a self-service basis, to test, verify and certify that a service solution to be deployed on a cellular network operates in conformance with the predefined rules for device and application behavior established by a cellular network carrier. The method includes soliciting information from the device owner about the device and application and analyzing such information for conformance to a carrier's predefined rules, allowing devices believed to conform to access the network and interact with applications that conform, monitoring the actual behavior of deployed devices during a testing process to detect instances where such behavior does not conform with the carrier's predefined rules; allowing devices that conform during a testing process to access the network; and monitoring the actual behavior of the devices deployed as self-certified service solutions to detect instances where such behavior does not conform with the carrier's predefined rules.

In an embodiment, there are two aspects, Phase I and Phase II, to the solution described herein. Phase I includes an automated method and system whereby a device owner can obtain a certification from a cellular network operator that its devices and the applications with respect to those devices that are part of the integrated service solution conform to the requirements of a cellular network, including testing of the device and its applications in a production environment. Phase II includes an automated method and system for monitoring actual behavior of the devices deployed as self-certified service solution on the cellular network and, when behavior of the device is out of compliance, implementing various actions to notify responsible parties and to minimize network disruption.

The primary advantage of the self-service process for certifying integrated service solutions is to eliminate the need to engage the cellular network operator or another party to perform this certification, which is both time consuming and costly. The primary advantage of the continuous monitoring is that it enables, in an automated way, real time analysis of the behavior of devices deployed as service solutions with respect to conformance with the rules established by a cellular network operator for behavior of deployed devices and applications, delivery of warnings to device owners, solution providers and/or network providers when devices or applications are out of compliance, and execution of a series of actions to minimize or end harmful device or application behavior that has not been corrected. To describe the features of the present invention in more detail refer now to the following description in conjunction with the accompanying Figures.

FIG. 1is an overview diagram illustrating a process and system for determining conformance of devices and applications that are part of the integrated service solutions with cellular network requirements, testing devices and applications, and certifying service solutions according to an embodiment of the invention. The starting point for this system is a self-service conformance function for an integrated service solution containing an application to be used in conjunction with network devices, comprising application and device behavior rules stored in a database121and a rules engine131. The application and device behavior rules are defined by a network carrier for behavior of devices deployed as service solutions that use the network operated by that carrier. These rules are entered by the network carrier into the rules engine131which is used to determine if the device and application to be used in conjunction with the device conforms to application and device behavior rules.

Typical application and device behavior rules comprise two components: one is to fulfill compliance requirements with government regulation such as Federal Communications Commission (FCC) rules or PTCRB (a pseudo-acronym originally created for Personal Communication Service Type Certification Review Board) certification, and the other component is rules for proper network behavior such as but not limited to proper initiation of data sessions, proper transmission of data, as either Internet Protocol (IP) data or Short messaging Service (SMS), proper closure of IP data sessions, timing and duration of packet sessions, algorithms governing re-try attempts that include intervals for retries, backing off of retries, and avoidance of any activity that would have an infinite number of attempts to accomplish something, programming delays and randomness into device behavior across a deployed fleet of devices.

To fulfill compliance requirements with government regulations such as FCC rules or PTCRB certification, a device owner (customer)101can generally obtain documentation through their device manufacturer and can simply submit documentation of proper approvals via step102through a self service web portal111. To ensure proper initiation of data sessions such as establishing a data session, the device working in conjunction with the application must request network access for a data session from the carrier's core network authentication elements151. Behavior of the device or application161would be considered harmful when multiple requests for data sessions are made rapidly from many devices, or multiple requests for data sessions are made by the same device but through different sources such as radio modules and applications working in conjunction with that device.

To begin self certification, a device owner101enters expected behavior of a device and application working in conjunction with that device for which certification is requested across key areas such as connection methodologies and parameters, retry methodologies etc. in response to a questionnaire into a web portal111operated by a cellular network operator or other party via step102. The web portal111stores these responses in a device behavior database121via step104. These responses are then checked by the rules engine131against rules for application and device behavior established by the cellular network operator via step106, and a pass/fail response is issued to the self-service portal111via step108and to the device owner101via step110. In the event of pass, authorization is triggered in a core cellular network151to allow the devices and applications a limited access to the network for the purpose of testing. This is done by an automated trigger on the service profile for that device owner's rate plan which enables the services to be used by the device owner101.

For automated device and application testing, device owner101with a device161would test to confirm that the device and application working in conjunction with that device161is operating as designed, and is in conformance with the application and device behavior rules also known as carrier rules. To accomplish this, the device owner101goes to the web portal111and enters the device identification number (for example, International Mobile Subscriber Identity (IMSI), Mobile Equipment Identifier (MEID), Mobile Identification Number (MIN) etc.) of the device they would like to test and initiate a test via step114. Once the device161is powered on, its network registration is seen by the cellular network151, indicating on the portal111that the device161is visible, and testing begins. The device owner101is then requested to perform specific steps, which may include, but are not limited to, some or all of powering the device161on, establishing a data session, ending a data session, sending an SMS, making a voice call and establishing a data session and keeping it active.

As the data is transmitted through the network during testing, network authentication and accounting records are examined for each of the above mentioned events to determine success or failure for conformance with the rules for the behavior of the devices and applications. In addition, functionality is determined, depending on the device and application being tested, by sending one or more of Mobile Terminating (MT) voice and SMS calls. Finally, retry attempts by the device and application161for both network access and data sessions are tested by forcing a break in the connection and capturing device behavior for retries. Once the tests are complete, a pass/fail analysis is provided to the device owner101along with a summary of performance statistics. In the event of pass, authorization is triggered in core cellular network151to allow production access to the cellular network for deployment of now certified integrated service solution.

Analytics engine141monitors real world performance of the device161which is now deployed as an integrated service solution (deployed devices) that is on the cellular network by using information it naturally generates regarding performance of the device161via step116by comparing live streaming transaction data against known device transaction anomalies. Authentication/signaling and transmission of data by the deployed devices generate network statistics. Some of the key information that is captured and logged into database151constituting “real world performance” includes, but is not limited to, time stamp of every network registration event from Home Location Register (HLR), underlying carrier of every network registration event from HLR, success or failure of network registration from HLR, time stamp of every IP session authentication request from Authentication, Authorization and Accounting (AAA), data records of amount of data sent during an IP Session, IP address assigned to each individual IP session, time stamp of every SMS attempt, success or failure for every SMS attempt, IP address for outbound IP session attempts. This “real world performance” of device161is compared against known device transaction anomalies of the deployed devices operating over the cellular network via step118. If an anomaly or a rule violation is detected, the device owner101is notified via step124.

Rule violations or anomalous behavior by deployed devices are grouped into three categories depending on their impact on the device161as well as overall network performance. Violations that are low impact generate a notice via step124to the device owner101with a defined time frame for resolution and escalation. For example, network carrier/operator logs the total byte count of each data session. If a device161or a group of devices were establishing multiple IP sessions, but not sending data, resulting in usage of limited network resources that does not relate to any successful transfer of data, the event is noted as a “zero byte session”. The analytics engine141monitors for such ‘zero byte sessions’ and when they are noted, the analytics engine141pushes a notification to inform the device owner101of the issue.

Violations that are of high impact generate a notice to the device owner101with a very short window for correction via step124before taking corrective actions to modify the behavior. For example, if the device owner101had incorrectly programmed their device161and Point To Point (PPP) stack in both the radio module as well as in the application were trying to establish an IP session, the database of authentication information would contain multiple authentication requests from the same device161. The analytics engine141sees this in real time from the database, identifies it as anomalous behavior of the device by comparing against known device transaction anomalies, and generates a notice to the device owner101to resolve the issue within 24 hours. If the issue remains or continues to occur after 24 hours have elapsed, the analytics engine141would automatically update IP session authentication elements to block IP session access for those devices via step126.

Violations that are severe generate a notice to the device owner101via step124as well as automated actions by the carrier to resolve the issue via step126. For example, if the device161began attempting several IP sessions at the exact same time, and retried every 3 seconds infinitely, it could potentially cause an outage of the network it is operating on. In such case, the analytics engine141sees the activity in the database, identifies it as anomalous behavior of the device and takes an automated action to block access to the device161via step126.

This is also observed in case of potential malicious behavior. For example, if a large group of deployed devices suddenly started pinging a new IP address outside of their normal profile, potentially causing a Denial of Service (DOS) attack, that activity is noted by the analytics engine141and automated action is taken in response to the malicious activity to block that outbound activity via step126.

Automated corrective action depends on the individual case and could be customized in analytics engine141. For example, IP access inbound to device161, or outbound from device161could be blocked by the network operator or by the device owner, by refusing authentication for IP services or network registration. Devices can also be proactively shut down by over the air clearing of the Preferred Roaming List (PRL) or the Public Land Mobile Network (PLMN) list, or the deployed device161is prevented from accessing the network at device level.

FIGS. 2aand 2billustrate Phase I and Phase II of a system for automated self-service certification, testing and real time monitoring of the service solution according to an embodiment of the invention. Phase I further includes two steps, step 1 includes analysis of expected behavior of devices and their applications as integrated service solutions with respect to conformance with network rules and step 2 includes automated testing of the device and its applications and the device deployed as a self-certified service solution to determine actual behavior in a production environment. Phase II includes continuous real-time monitoring and analysis of actual behavior on the cellular network of devices deployed as self-certified service solutions in accordance with an embodiment of the present invention.

Phase I, step 1 includes self-service certification of integrated service solutions containing devices and applications. This aspect of the invention consists of a method and system in accordance with an embodiment that allows for a rapid, automated and self-service process by which a device owner, application developer, integrated solution provider or other party (collectively referred to as “device owner” for convenience) may receive certification for a device or application to be deployed as an integrated service solution. This process will enable device owners to complete development including certification of service solutions quickly, at lower cost than seeking manual certification by the cellular network operator and with a higher level of certainty for both device owner and network operator that the service solution will not cause network issues, thereby enabling device owners to launch commercial integrated service solutions with minimum barriers while minimizing disruptions to access to network resources for all customers of that network operator.

As illustrated inFIG. 2a, a self-service web portal211operated by a cellular network operator or other party enables a device owner201to complete the certification process. First, the device owner201enters information into a system on self-service web portal211in response to queries relevant to the device or application to be deployed as a service solution for which certification is requested. The information includes the design and expected behavior of the device or application across key areas such as connection methodologies and parameters, retry methodologies and the like and to store that information in device behavior database221for future reference. The self-reported information is collected and compared by a rules engine231against rules for device and application behavior established and stored in device conformance rules database241by the cellular network operator to determine conformance, with a pass/fail response provided to the device owner201.

If the device or application receives a pass response, the carrier provisioning database251and HLR281are instructed to permit the service solution271′ to access the network production environment for the limited purpose of completing an automated test sequence, and the device owner201is notified that it should initiate an automated test sequence run by a test application261that will see how the device or application to be deployed as a service solution271′ functions in certain situations (which may consist of one or more of initial session startup, session terminated, server busy, message not delivered, etc.). The behavior of the device or application271′ during this test process is collected by the cellular core network281then compared to the expected device behavior stored in device behavior database221and device conformance rules241for compliance with the cellular network operator's rules by rules engine231. Feedback on such performance is provided to the device owner201.

If actual behavior during test sequence is not in conformance with the rules, the device owner201will be notified and provided information about test results and areas of deficiency, allowing the device owner201to modify the device or application and initiate the certification process again after completing modifications. If the actual behavior during the test sequence conforms both to expected behavior and to the rules, the device owner201and the carrier provisioning database251and HLR281are notified that such service solution will be permitted access to the network in a commercial production environment (i.e., the service solution will be “certified”).

FIG. 2billustrates Phase II of the solution which includes monitoring behavior of devices and applications deployed as service solutions and correction of problems. In this aspect of the invention, the behavior of devices and applications deployed as service solutions271on the network are monitored on a continuous basis, and data about actual network behavior of the devices and applications is collected by the carrier's traffic and signaling database291. This data is analyzed by an analytics engine2101to determine ongoing compliance with network operator rules such as rules in device conformance rules database241and may also be compared with any other rules engines or databases operated by the cellular network operator or a service provider, similar to the operation of a common malware program, for purposes of detecting known causes of aberrant device or application behavior or network disruption, both unintentional and malicious. The method and system also allows for the analytics engine2101to automatically initiate notification procedures and corrective actions if the devices or applications are not in conformance with network rules. The corrective actions would range from blocking network access to non-conforming devices to, in extreme cases, rendering a device inoperable by instructions issued Over The Air (OTA).

The monitoring process has configurable actions so that negative behavior of the devices and applications deployed on cellular network can be prevented and addressed automatically in a timely manner instead of utilizing time consuming manual procedures. The method and system enable the device owners and other parties such as network operators to eliminate network outages which are very costly. It can be used as a standard methodology by which malicious malware and attacks through devices and applications deployed on cellular networks are prevented or reduced in the future.

As illustrated inFIG. 2b, as data is transmitted over the air between a server and a device, each and every transaction is recorded in traffic and signaling database291containing control plane and transaction accounting records. An analytics engine2101analyzes the control plane and transaction accounting records to determine if behavior of the device and application271deployed as a service solution is violating device conformance rules241which are carrier defined performance standards for the device271. This analytics engine2101also incorporates an alert/action engine to send out of compliance push notification to device owner201or to correct behavior of the device and/or application271if the harmful or aberrant behavior of the devices and/or applications satisfies the predefined parameters for such an action. Such continuous monitoring provides a higher level of confidence to the cellular network operator that out-of-conformance devices and applications will be identified quickly, along with increased security and access to network resources for all customers using services of that cellular network carrier.

FIG. 3illustrates a flow chart describing a method for detecting and minimizing harmful application and device behavior on cellular networks for the system shown inFIGS. 2aand 2b. In self-service certification aspect of Phase I, also known as conformance self declaration301of an application and device, a device owner logs into a web portal provided by a network operator or other party and completes traffic profile questionnaire via step302. The device owner enters how their application performs as a response to the questionnaire into the web portal via step302. Data from the questionnaire populates device behavior database by storing answers to the questionnaire in the device behavior database via step304. These responses are checked against carrier defined rules also known as device conformance rules for behavior by a rules engine which examines traffic profile data and determines pass/fail by comparing the traffic profile data entered by the device owner with the device conformance rules via step306. Typical carrier rules include but are not limited to compliance with government regulation such as FCC rules or PTCRB certification, proper initiation of data sessions, proper transmission of data, as either IP data or as an SMS, proper closure of IP sessions, timing and duration of packet sessions, algorithms governing re-try attempts and programming delays and randomness into device behavior across a deployed fleet of devices.

Once the rules engine determines pass/fail by comparing data entered by the device owner with the application and device behavior database, a pass/fail is issued to the device owner via step308in the form of push notification from cloud database to portal. In the event of a pass, authorization is then triggered in the core network to allow that device owner's devices a limited access to the network for the purpose of testing the device and the application as an integrated service solution. This is done by an automated trigger on the service profile for that device owner's rate plan which enables the services the device owner will be using for testing.

For conformance self test311of the application, a device owner enters test device and application information into web portal and initiates test sequence via step310. The device owner connects the test device to the provider's network and follows test instructions via step312. To accomplish this, the device owner goes to the web portal to enter device identification number, for example, IMSI, MEID, MIN, etc. for the device they would like to test and initiate a test. As cellular network provider sees the network registration, it indicates on the portal that the deployed device is visible, and the testing begins. A request is sent to the device owner to take specific steps, which may include, but is not limited to, one or more of power the device on, establish a data session, end a data session, send an SMS, make a voice call, establish a data session and keep it active. Network authentication and accounting records are examined for each of these events to determine success or failure. In addition, depending on the device and application being tested, MT voice and SMS calls are sent to determine functionality. Finally, retry attempts by the device for both network access and data sessions are tested by forcing a break in the connection and capturing device behavior for retries. As the device interacts with cellular network infrastructure via step312, a rules engine determines if the actual test behavior in key areas for example, retry algorithms conforms to the self-described behavior and/or is in conformance with carrier policy. This automated test functionality enables the device owner to perform network tests in an automated way and receive feedback on performance. The device behavior under test conditions is then compared to the device conformance rules by the rules engine to determine pass/fail via step314. A test report with pass/fail and performance statistics is provided to the device owner via step316and the device owner can then begin deployment of devices as a service solution in the event of “pass” as shown in step318.

Phase II of the solution, real time monitoring and analysis321of network behavior of deployed device and applications, allows carriers to determine if the deployed devices and applications are performing outside of their self-described profile and/or in violation of carrier performance rules. An analytics engine compares live streaming transaction data against known device transaction anomalies. This is done by using authentication and traffic information populated into certification database via step322as the deployed device starts interacting with cellular network infrastructure via step320. Some key information that is captured and logged into a database in this solution is, time stamp of every network registration event from the HLR, underlying carrier of every network registration event from the HLR, success or failure of network registration from the HLR, time stamp of every IP session authentication request from the AAA, data records of amount of data sent during an IP session, IP address assigned to each individual IP session, time stamp of every SMS attempt, success or failure for every SMS attempt, IP address for outbound IP session attempts. User and control plane data is examined by the analytics engine to ensure that the usage is in line with certification via step324. Operation in violation of device conformance rules profile or anomalous behavior by the device results in push notification directly to the device owner and the core network via step326.

The action based analytics engine automatically escalates corrective actions if the deployed devices are not performing correctly via steps326and328. This would range from a notification via step326to blocking network access, to OTA rendering a deployed device inoperable via step328. For example, if the issue is not rectified, aberrant behavior is blocked or the deployed device is bricked as shown in step328. The process has configurable actions so that negative behavior of the deployed device can be prevented and addressed automatically in a timely manner instead of utilizing time consuming manual procedures.

FIG. 4illustrates a data processing system400suitable for storing the computer program product and/or executing program code in accordance with an embodiment of the present invention. The data processing system400includes a processor402coupled to memory elements404a-bthrough a system bus406. In other embodiments, the data processing system400may include more than one processor and each processor may be coupled directly or indirectly to one or more memory elements through a system bus.

Memory elements404a-bcan include local memory employed during actual execution of the program code, bulk storage, and cache memories that provide temporary storage of at least some program code in order to reduce the number of times the code must be retrieved from bulk storage during execution. As shown, input/output or I/O devices408a-b(including, but not limited to, keyboards, displays, pointing devices, etc.) are coupled to the data processing system400. I/O devices408a-bmay be coupled to the data processing system400directly or indirectly through intervening I/O controllers (not shown).

InFIG. 4, a network adapter410is coupled to the data processing system402to enable data processing system402to become coupled to other data processing systems or remote printers or storage devices through communication link412. Communication link412can be a private or public network. Modems, cable modems, and Ethernet cards are just a few of the currently available types of network adapters.

Embodiments of the process described herein can take the form of an entirely software implementation, or an implementation containing both hardware and software elements. Embodiments may be implemented in software, which includes, but is not limited to, application software, firmware, resident software, microcode, etc.

The steps described herein may be implemented using any suitable controller or processor, and software application, which may be stored on any suitable storage location or computer-readable medium. The software application provides instructions that enable the processor to cause the receiver to perform the functions described herein.

The medium may be an electronic, magnetic, optical, electromagnetic, infrared, semiconductor system (or apparatus or device), or a propagation medium. Examples of a computer-readable medium include a semiconductor or solid state memory, magnetic tape, a removable computer diskette, a random access memory (RAM), a read-only memory (ROM), a rigid magnetic disk, and an optical disk. Current examples of optical disks include DVD, compact disk-read-only memory (CD-ROM), and compact disk-read/write (CD-RAN).

Any theory, mechanism of operation, proof, or finding stated herein is meant to further enhance understanding of the present invention and is not intended to make the present invention in any way dependent upon such theory, mechanism of operation, proof, or finding. It should be understood that while the use of the words “preferable”, “preferably” or “preferred” in the description above indicates that the feature so described may be more desirable, it nonetheless may not be necessary and embodiments lacking the same may be contemplated as within the scope of the invention, that scope being defined by the claims that follow. In addition, it should be understood that while the use of words indicating a sequence of events such as “first” and “then” shows that some actions may happen before or after other actions, embodiments that perform actions in a different or additional sequence should be contemplated as within the scope of the invention as defined by the claims that follow.

As used herein, the term “cellular communication” is understood to include various methods of connecting any type of computing or communications devices, servers, clusters of servers, using wired and/or wireless communications networks to enable processing and storage of signals and information, and where these services may be accessed by applications available through a number of different hardware and software systems, such as but not limited to a web browser terminal, mobile application (i.e., app) or similar, and regardless of whether the primary software and data is located on the communicating device or are stored on servers or locations apart from the devices.

As used herein the terms “device”, “appliance”, “terminal”, “remote device”, “wireless asset”, etc. are intended to be inclusive, interchangeable, and/or synonymous with one another and other similar communication-based equipment for purposes of the present invention, even though one will recognize that functionally each may have unique characteristics, functions and/or operations which may be specific to its individual capabilities and/or deployment.

Similarly, it is envisioned by the present invention that the term “cellular network” includes networks using one or more communication architectures or methods, including but not limited to: Code division multiple access (CDMA), Global System for Mobile Communications (GSM) (“GSM” is a trademark of the GSM Association), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), 4G LTE, wireless local area network (WIFI), and one or more wired networks.