EFFICIENT SUBSCRIBER DEVICE MANAGEMENT USING PROFILE IDENTIFIERS

• US 20150350884A1
• Filed: 05/28/2014
• Published: 12/03/2015
• Est. Priority Date: 05/28/2014
• Status: Active Grant

• Current Assignee: Cellco Partnership, Inc. (Verizon Communications Inc.)
• Original Assignee: Cellco Partnership, Inc. (Verizon Communications Inc.)
• Inventors: Kolanowski, Stephen J.
• Granted Patent: US 9,277,397 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04W 8/20 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

A system may be configured to receive profile identifiers from a set of user devices; identify, based on the profile identifiers, one or more user devices, of the set of user devices, for which updated parameters should be provided, the parameters relating to operation of the one or more user devices with respect to a telecommunications network; and provide, to the identified one or more user devices, the updated parameters.

Claims

1. A method, comprising:

receiving, by a server device, profile identifiers from a set of user devices that are configured to attach to a wireless telecommunications network;

identifying, by the server device and based on the profile identifiers, one or more user devices, of the set of user devices, for which updated parameters should be provided, the parameters relating to operation of the one or more user devices with respect to the telecommunications network; and

providing, by the server device and to the identified one or more user devices, the updated parameters.

2. The method of claim 1, wherein identifying the one or more user devices includes:

comparing the profile identifiers, received from the one or more user devices, with an up-to-date profile identifier; and

determining that the profile identifiers, received from the one or more user devices, do not match the up-to-date profile identifier.

3. The method of claim 2, wherein the up-to-date profile identifier includes a first alphanumeric string, and wherein a particular profile identifier, associated with a particular user device, of the one or more user devices, comprises a second alphanumeric string,

wherein determining that the profile particular profile identifier, associated with the particular user device, does not match the up-to-date profile identifier, includes:

determining that the first alphanumeric string does not match the second alphanumeric string.

4. The method of claim 1, wherein the providing causes the one or more user devices to modify a set of parameters, associated with the user device, based on the updated parameters.

5. The method of claim 4, wherein the one or more user devices and the server device implement an Open Mobile Alliance Device Management (“

OMA DM”

) standard.

6. The method of claim 5, wherein receiving the profile identifier, associated with a particular user device, includes receiving at least one of:

an OMA DM DevDetail object that includes the profile identifier associated with the particular user device, or

an OM ADM DevInfo object that includes the profile identifier associated with the particular user device.

7. The method of claim 1, wherein the updated parameters include parameters regarding at least one of a timer, or a quantity of retry attempts for a particular type of communication.

8. A server device, comprising:

a memory device storing a set of processor-executable instructions; and

a processor configured to execute the processor-executable instructions, wherein executing the computer-executable instructions causes the processor to;

receive profile identifiers from a set of user devices that are configured to attach to a wireless telecommunications network;

identify, based on the profile identifiers, one or more user devices, of the set of user devices, for which updated parameters should be provided, the parameters relating to operation of the one or more user devices with respect to the telecommunications network; and

provide, to the identified one or more user devices, the updated parameters.

9. The server device of claim 8, wherein executing the processor-executable instructions, to identify the one or more user devices, further causes the processor to:

compare the profile identifiers, received from the one or more user devices, with an up-to-date profile identifier; and

determine that the profile identifiers, received from the one or more user devices, do not match the up-to-date profile identifier.

10. The server device of claim 9, wherein the up-to-date profile identifier includes a first alphanumeric string, and wherein a particular profile identifier, associated with a particular user device, of the one or more user devices, comprises a second alphanumeric string,

wherein executing the processor-executable instructions, to determine that the profile particular profile identifier, associated with the particular user device, does not match the up-to-date profile identifier, further causes the processor to:

determine that the first alphanumeric string does not match the second alphanumeric string.

11. The server device of claim 8, wherein the providing causes the one or more user devices to modify a set of parameters, associated with the user device, based on the updated parameters.

12. The server device of claim 11, wherein the one or more user devices and the server device implement an Open Mobile Alliance Device Management (“

OMA DM”

) standard.

13. The server device of claim 12, wherein executing the processor-executable instructions, to receive the profile identifier, associated with a particular user device, further causes the processor to receive at least one of:

an OMA DM DevDetail object that includes the profile identifier associated with the particular user device, or

an OM ADM DevInfo object that includes the profile identifier associated with the particular user device.

14. The server device of claim 8, wherein the updated parameters include parameters regarding at least one of a timer, or a quantity of retry attempts for a particular type of communication.

15-20. -20. (canceled)

21. A system, comprising:

a user device, configured to;

receive and store a set of parameters related to communicating with a telecommunications network,

store an identifier associated with the set of parameters, and

output the identifier to a server device; and

a server device, configured to;

receive the identifier from the user device,

determine, based on the received identifier, whether the user device has stored up-to-date parameters, and

provide, to the user device, a set of updated parameters based on a determination that the user device has not stored up-to-date parameters.

22. The system of claim 21, wherein the user device and the server device implement an Open Mobile Alliance Device Management (“

OMA DM”

) standard, wherein outputting the identifier to the server device includes outputting an OMA DM DevDetail object that includes the identifier.

23. The system of claim 21, wherein, the set of parameters include parameters regarding at least one of a timer, or a quantity of retry attempts for a particular type of communication.

24. The system of claim 21, wherein, outputting the identifier to the server device is performed based on a request, by the server device, for the identifier.

25. The system of claim 21, wherein outputting the identifier to the server device is performed independent of a request, by the server device, for the identifier.

26. The system of claim 21, wherein storing the set of parameters includes overwriting a previously received set of stored parameters.