SERVICE PROVIDER CERTIFIED DEVICE POLICY MANAGEMENT

• US 20160374008A1
• Filed: 08/31/2016
• Published: 12/22/2016
• Est. Priority Date: 09/24/2013
• Status: Abandoned Application

• Current Assignee: RPX Corporation
• Original Assignee: Alcatel-Lucent Canada Incorporated (Nokia Corporation)
• Inventors: SHETH, Tiru K., SUBRAMANIAN, Ramaswamy
• Application Number:
  US15/253,292
• Publication Number:
  US 20160374008A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04M 7/0012 Details of application programming interfaces [API] for telephone networks; Arrangements which combine a telephonic communication equipment and a computer, i.e. computer telephony integration [CPI] arrangements
• CPC Class Codes: H04W 48/02 Access restriction performed under specific conditions
• CPC Class Codes: H04W 48/14 using user query or user detection
• CPC Class Codes: H04W 48/16 Discovering, processing access restriction or access information
• CPC Class Codes: H04W 8/205 Transfer to or from user equipment or user record carrier
• CPC Class Codes: H04W 8/22 Processing or transfer of terminal data, e.g. status or physical capabilities

Abstract

Various exemplary embodiments relate to a method performed by a policy server. The method includes: receiving a request for service, the request including an identification of user equipment; determining a user equipment type (TAC); evaluating a policy rule based on the user equipment type, the policy rule including a condition referencing at least one user equipment type; and responding to the request for service based on evaluation of the policy rule.

Claims

1. A method performed by a service portal, the method comprising:

receiving a request for new subscriber registration from a user equipment;

determining an IP address of the user equipment;

requesting, from a policy server, a user equipment type;

determining a set of compatible subscriptions based on the user equipment type;

receiving a selection of a compatible subscription from the user equipment;

sending new subscription information based on the selected compatible subscription to the policy server.

2. The method of claim 1, wherein the request for a new subscriber is an HTTP request for a webpage.

3. The method of claim 1, wherein requesting, from a policy server, a user equipment type further includes using an application program interface (API).

4. The method of claim 1, wherein the user equipment type is a type allocation code (TAC) extracted from a user-equipment-info attribute value pair (AVP) received in the request for service.

5. The method of claim 1, wherein the user equipment type includes a marketing name of the user equipment.

6. The method of claim 1, further comprising sending information regarding the compatible subscriptions to the user equipment.

7. The method of claim 6, wherein sending information regarding the compatible subscriptions to the user equipment includes sending a webpage displaying properties of the customized plans.

8. The method of claim 1, further comprising receiving subscriber information from the user equipment and creating a new account for the subscriber.

9. The method of claim 1, further comprising verifying the received subscriber information and charging for the selected compatible subscription.

10. The method of claim 1, further comprising sending the new subscription information to a subscriber profile repository.

11. A non-transitory machine-readable storage medium encoded with instructions executable by a processor of a service portal, the non-transitory machine-readable storage medium comprising instructions for:

receiving a request for new subscriber registration from a user equipment;

determining an IP address of the user equipment;

requesting, from a policy server, a user equipment type;

determining a set of compatible subscriptions based on the user equipment type;

receiving a selection of a compatible subscription from the user equipment;

sending new subscription information based on the selected compatible subscription to the policy server.

12. The non-transitory machine-readable storage medium of claim 11, wherein the request for a new subscriber is an HTTP request for a webpage.

13. The non-transitory machine-readable storage medium of claim 11, wherein requesting, from a policy server, a user equipment type further includes using an application program interface (API).

14. The non-transitory machine-readable storage medium of claim 11, wherein the user equipment type is a type allocation code (TAC) extracted from a user-equipment-info attribute value pair (AVP) received in the request for service.

15. The non-transitory machine-readable storage medium of claim 11, wherein the user equipment type includes a marketing name of the user equipment.

16. The non-transitory machine-readable storage medium of claim 11, further comprising instructions for sending information regarding the compatible subscriptions to the user equipment.

17. The non-transitory machine-readable storage medium of claim 11, wherein sending information regarding the compatible subscriptions to the user equipment includes sending a webpage displaying properties of the customized plans.

18. The non-transitory machine-readable storage medium of claim 11, further comprising instructions for receiving subscriber information from the user equipment and creating a new account for the subscriber.

19. The non-transitory machine-readable storage medium of claim 11, further comprising instructions for verifying the received subscriber information and charging for the selected compatible subscription.

20. The non-transitory machine-readable storage medium of claim 11, further comprising instructions for sending the new subscription information to a subscriber profile repository.