A communications manager is disclosed that is provided on a telecommunications network and a terminal registered with that network. The communications manager comprises in the network and on the terminal a service manager; a data manager and a connection manager. The service manager and data manager collect and store data from a plurality of sources. The connection manager prioritises and schedules delivery of the data from the network to the terminal (or vice versa), and selects a communication method to provide the data in accordance with the priority of that data. The communication method may be SMS for high priority data or an activated packet data connection for lower priority data.
Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A communications manager for managing communications between a telecommunications network core and a terminal registered with the network core, the communications manager including: a collecting component that collects data from a plurality of sources, wherein the data are generated by at least one of: a change event, a request message or a control message occurring in relation to an application with which a user of the terminal has made an association; a delivery component that prioritizes and schedules delivery of the data to the terminal; and a selecting component that selects a communication method to provide the data to the terminal in accordance with the priority of the data.
A communications manager handles communication between a telecommunications network and a registered terminal. It includes a data collector that gathers data from various sources, triggered by events, requests, or control messages related to an application the user is using. A delivery component prioritizes and schedules this data for delivery to the terminal. A selection component chooses the communication method (e.g., SMS, packet data) based on the data's priority. The overall system ensures timely and appropriate delivery of application-related data to the user's terminal.
2. The communications manager of claim 1 , wherein the data are prioritised according to at least one of an origin of the data or a type of the data.
The communications manager from the previous description, which collects, prioritizes, schedules, and delivers data to a terminal, prioritizes the data based on its origin (e.g., which application generated it) or its type (e.g., notification, update, error message). This origin or type is used as criteria when deciding priority.
3. The communications manager of claim 1 , wherein the selecting component selects one of a plurality of bearers to deliver the data to the terminal.
The communications manager from the initial description, which collects, prioritizes, schedules, and delivers data to a terminal, chooses one of several communication channels ("bearers") to send the data. Instead of just one method, it dynamically selects the appropriate bearer for delivery.
4. The communications manager of claim 3 , wherein the bearers include at least one of: SMS or an activated packet data connection.
The communications manager from the original claim selecting communication bearers uses either SMS (Short Message Service) or an activated packet data connection (like 3G or 4G) as a method for delivering data to the terminal. It chooses between SMS for high-priority and packet data for lower-priority information.
5. The communications manager of claim 1 , wherein the delivery component is operable to adjust the prioritising and scheduling of delivery of the data in dependence upon the network communication conditions.
The communications manager from the first description, which collects, prioritizes, schedules, and delivers data to a terminal, adjusts the data prioritization and scheduling based on current network conditions. For example, when network is congested, lower priority notifications may be delayed.
6. The communications manager of claim 5 , wherein the network communication conditions include the level of available network capacity.
The communications manager that adjusts prioritization and scheduling based on network conditions specifically considers the available network capacity. When network capacity is low, non-critical updates might be deferred to preserve bandwidth for urgent communications.
7. The communications manager of claim 1 , wherein the delivery component is operable to adjust the prioritising and scheduling of delivery of the data in dependence upon the type of subscription between the user of the terminal and the network.
The communications manager that prioritizes and schedules data delivery adjusts this process depending on the user's subscription type with the network. Different subscription levels may receive different priority levels.
8. The communications manager of claim 7 , wherein the type of subscription includes at least one of a type of tariff of the user of the terminal or whether the user of the terminal is roaming in the network.
The communications manager, whose delivery component is subscription-aware, considers the user's tariff plan or whether the user is roaming. A user on a premium tariff may get higher priority than one on a basic plan. Roaming users could have different priorities to manage network usage.
9. The communications manager of claim 1 , further comprising: a storing component that stores details of contacts used by the user of the terminal, which details of contacts are also stored on the terminal, wherein the data includes updates to the contacts from third parties, and wherein the delivery component and the selecting component are operable to synchronise the details of the contacts on the terminal with the details of the contacts on the network.
The communications manager from the first description, which collects, prioritizes, schedules, and delivers data to a terminal, also stores the user's contacts, similar to what's on the phone. When contacts are updated (e.g., a friend changes their number), the updates are sent to the phone. This synchronizes contacts on both the network and the terminal using the delivery and selection components.
10. The communications manager of claim 1 , wherein the terminal is a mobile terminal that communicates with the network core via a radio access network.
The communications manager, described previously, interacts with a mobile terminal (e.g., a smartphone) that communicates with the network via a radio access network (e.g., 4G LTE).
11. The communications manager of claim 1 , wherein the network core is the network core of at least one of: a GSM, a UMTS or a SAE/LTE network.
The communications manager, described previously, interfaces with the network core of GSM, UMTS (3G), or SAE/LTE (4G) networks. These are standard mobile telecommunications network technologies.
12. A method of managing communications between a telecommunications network core and a terminal registered with the network, the method comprising: collecting data from a plurality of sources, wherein the data are generated by at least one of: a change event, a request message or a control message occurring in relation to an application with which a user of the terminal has made an association; prioritising and scheduling delivery of the data to the terminal; and selecting a communication method to provide the data to the terminal in accordance with the priority of the data.
A method for managing communications between a telecommunications network and a registered terminal involves collecting data from various sources, triggered by events, requests, or control messages related to an application the user is using. The method prioritizes and schedules this data for delivery to the terminal, then selects a communication method (e.g., SMS, packet data) based on the data's priority.
13. The method of claim 12 , wherein prioritizing and scheduling of delivery of the data depends upon a type of subscription between the user of the terminal and the network.
The communication management method from the previous description, involving collecting, prioritizing, scheduling, and delivering data, prioritizes and schedules data depending on the user's subscription type with the network. Different subscriptions can receive different priorities.
14. The method of claim 13 , wherein the type of subscription includes at least one of: a type of tariff of the user of the terminal or whether the user of the terminal is roaming in the network.
The communication management method that tailors prioritization to the user's subscription type considers the user's tariff plan or whether the user is roaming. Higher-paying customers or users in home networks could receive prioritization.
15. Computer software, provided in a non-transitory computer-readable medium, that manages communications between a telecommunications network core and a terminal registered with the network core, the software comprising: executable code that collects-data from a plurality of sources, wherein the data are generated by at least one of: a change event, a request message or a control message occurring in relation to an application with which a user of the terminal has made an association; executable code that prioritizes and schedules delivery of the data from the terminal to the telecommunications network core; and executable code that selects a communication method to provide the data to the telecommunications network core in accordance with the priority of the data.
Software (in non-transitory form) manages communication between a telecommunications network and a registered terminal. It contains code that collects data from multiple sources, triggered by events or messages relating to applications the user interacts with. Additional code prioritizes and schedules data delivery, and chooses the appropriate communication method (e.g., SMS, data connection) based on data priority.
16. The computer software of claim 15 , wherein the data are prioritized according to at least one of: an origin of the data or a type of the data.
The software managing communication, which collects, prioritizes, schedules, and delivers data, prioritizes the data based on either its origin or its type. This criteria drives decisions on delivery method and timing.
17. The computer software of claim 15 , wherein prioritizing and scheduling of delivery of the data depends upon a type of subscription between the user of the terminal and the network.
The communication management software, which collects, prioritizes, schedules, and delivers data, adjusts the prioritization and scheduling of data delivery based on the user's subscription type with the network.
18. The computer software of claim 17 , wherein the type of subscription includes at least one of: a type of tariff of the user of the terminal or whether the user of the terminal is roaming in the network.
The communication management software that prioritizes based on subscription type considers the user's tariff or roaming status. This impacts the delivery method and scheduling.
19. The computer software of claim 15 , wherein the terminal is a mobile terminal that communicates with the network core via a radio access network.
The communication management software interfaces with a mobile terminal (like a smartphone) that uses a radio access network (like 4G LTE) to communicate with the network core.
20. The computer software of claim 15 , wherein the network core is the network core of at least one of: a GSM, a UMTS or a SAE/LTE network.
The communication management software connects to network cores like GSM, UMTS (3G), and SAE/LTE (4G) infrastructure.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
June 1, 2009
September 10, 2013
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.