Machine-type communication subscription control

• US 9,955,340 B2
• Filed: 11/28/2014
• Issued: 04/24/2018
• Est. Priority Date: 07/27/2010
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Garcia Azorero, Fuencisla
• Primary Examiner(s): Nguyen, Hanh N
• Application Number:
  US14/555,879
• Publication Number:
  US 20150087304A1
• Time in Patent Office: 1,243 Days
• Field of Search: 709224, 709225, 4554323
• CPC Class Codes: H04L 69/24 Negotiation of communication capabilities
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]
• CPC Class Codes: H04W 60/00 Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
• CPC Class Codes: H04W 8/18 Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
• CPC Class Codes: H04W 8/22 Processing or transfer of terminal data, e.g. status or physical capabilities

Abstract

An apparatus is configured to operate as a subscriber server. The apparatus comprises a memory for storing the subscription information of one or more Machine Type Communications, MTC, subscribers, the subscription information of a MTC subscriber including one or more MTC Features and information regarding the MTC subscriber'"'"'s subscribed services, a processor for assessing which of the one or more subscribed MTC Features are supported, assessing any interaction that may occur between each of the supported subscribed MTC Features and between each of the supported subscribed MTC Features and the subscribed services, and determining the subscription information that should be sent to the serving node based on the outcome of the assessments, and a transmitter for sending the determined subscription information to the serving node.

Claims

1. An apparatus configured to operate as a network node of a telecommunications network, the apparatus comprising:

a processor configured to;

identify unsupported Machine Type Communications (MTC) Features, wherein an unsupported MTC Feature is an MTC Feature that at least one of an MTC Device belonging to an MTC Subscriber and the network node is not enabled to implement or execute; and

implement or execute an MTC Feature for the MTC Device; and

a transmitter configured to send to a Home Location Register (HLR) separate from the network node indications of the unsupported MTC Features that the at least one of the MTC Device and the network node is not enabled to implement or execute, wherein the processor is further configured to;

for an unsupported MTC Feature that requires an indication of being supported by the MTC Device and the network node, exclude such indication of the unsupported MTC Feature from a message to be sent to the Home Location Register; and

for an unsupported MTC Feature that does not require an indication of being supported by the MTC Device and the network node, include an indication of the MTC Feature that does not require an indication of being supported by the MTC Device and the network node in a message to be sent to the Home Location Register.

2. The apparatus as claimed in claim 1, and further comprising:

a receiver configured to receive subscription information for the MTC Subscriber from the Home Location Register, the subscription information including supported MTC Features and subscribed services information for the MTC Subscriber; and

the processor being further configured to use the received subscription information to establish a data session for the MTC Device.

3. A method of operating a subscriber server handling subscription information of one or more Machine Type Communications (MTC) subscribers, the subscription information of an MTC subscriber including one or more MTC Features and information regarding the subscriber'"'"'s subscribed services, the method comprising:

when it is required that subscription information for an MTC subscriber be sent to a network node configured to implement or execute an MTC Feature for an MTC device of the MTC subscriber;

determining, by the subscriber server, amongst one or more subscribed MTC Features, supported MTC Features that the MTC Device and the network node are enabled to implement or execute and unsupported MTC Features that at least one of the MTC Device and the network node is not enabled to implement or execute;

determining, by the subscriber server, interactions between the supported MTC Features and the subscribed services;

determining, by the subscriber server, the subscription information that should be sent to the network node based on the supported MTC Features and the determined interactions; and

sending, by the subscriber server, the determined subscription information to the network node.

4. The method as claimed in claim 3, wherein determining the supported and unsupported MTC Features comprises:

determining, for each of the one or more subscribed MTC Features, whether both the MTC Device and the network node are enabled to implement or execute the subscribed MTC Feature.

5. The method as claimed in claim 4, wherein the unsupported MTC Features are excluded from the subscription information that is to be sent to the network node.

6. The method as claimed in claim 4, wherein determining the unsupported MTC Features comprises one or more of:

determining whether an indication has been received from the network node indicating one or more MTC Features that at least one of the MTC Device and the network node is not enabled to implement or execute; and

for any MTC Feature that requires an indication of being supported by the MTC Device and the network node, determining whether an indication has been received from the network node indicating one or more MTC Features that the MTC Device and the network node are enabled to implement or execute.

7. The method as claimed in claim 3, wherein determining the interactions between the supported MTC Features and the subscribed services comprises:

determining any of the supported MTC Features that interact or conflict with any other supported MTC Feature.

8. The method as claimed in claim 7, wherein, in response to the determination that any of the supported MTC Features interact or conflict with any other supported MTC Feature, including a relative precedence of these supported MTC Features in the subscription information that is to be sent to the network node.

9. The method as claimed in claim 3, wherein determining interactions between the supported MTC Features and the subscribed services comprises:

determining any of the supported MTC Features that imply restrictions on the subscribed services.

10. The method as claimed in claim 9, wherein, in response to the determination that any of the supported MTC Features imply restrictions on the subscribed services, excluding the subscribed services that are not allowed by the restrictions of the supported MTC Features from the subscription information that is to be sent to the network node.

11. The method as claimed in claim 3, and further comprising:

determining any of the supported MTC Features to be enabled only upon an instruction received from the MTC Device.

12. The method as claimed in claim 11, wherein, in response to the determination that any of the supported MTC Features to be enabled only upon an instruction received from the MTC Device, including an indication that these supported MTC Features are to be enabled only upon an instruction received from the MTC Device, in the subscription information that is to be sent to the network node.