System and method for exchanging policy information in a roaming communications environment

• US 20070207818A1
• Filed: 03/06/2007
• Published: 09/06/2007
• Est. Priority Date: 03/06/2006
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Andreasen, Flemming S., Rosenberg, Jonathan D.
• Granted Patent: US 8,295,242 B2
• Time in Patent Office: Days
• US Class Current: 455/461
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: H04L 12/14 Charging , metering or billing arrangements for data wireline or wireless communications
• CPC Class Codes: H04L 12/1403 Architecture for metering, charging or billing
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/0894 Policy-based network configuration management
• CPC Class Codes: H04L 41/5029 Service quality level-based billing, e.g. dependent on measured service level customer is charged more or less
• CPC Class Codes: H04L 41/5061 characterised by the interaction between service providers and their network customers, e.g. customer relationship management
• CPC Class Codes: H04L 45/50 using label swapping, e.g. multi-protocol label switch [MPLS]
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/15 in relation to multipoint traffic arrangements for broadcast or multicast in data networks H04L12/18
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 47/724 at intermediate nodes, e.g. resource reservation protocol [RSVP]
• CPC Class Codes: H04L 47/805 QOS or priority aware
• CPC Class Codes: H04L 47/824 Applicable to portable or mobile terminals
• CPC Class Codes: H04L 61/5014 using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
• 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/0892 by using authentication-authorization-accounting [AAA] servers or protocols
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 63/162 at the data link layer
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/1104 : Session initiation protocol [SIP]
• CPC Class Codes: H04L 67/141 : Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 69/14 : Multichannel or multilink protocols
• CPC Class Codes: H04L 69/24 : Negotiation of communication capabilities
• CPC Class Codes: H04W 12/06 : Authentication
• CPC Class Codes: H04W 12/08 : Access security
• CPC Class Codes: H04W 28/18 : Negotiating wireless communication parameters
• CPC Class Codes: H04W 36/0033 : with transfer of context information
• CPC Class Codes: H04W 36/12 : Reselecting a serving backbone network switching or routing node
• CPC Class Codes: H04W 36/14 : Reselecting a network or an air interface
• CPC Class Codes: H04W 48/14 : using user query or user detection
• 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/04 : Registration at HLR or HSS [Home Subscriber Server]
• CPC Class Codes: H04W 8/26 : Network addressing or numbering for mobility support
• CPC Class Codes: H04W 80/04 : Network layer protocols, e.g. mobile IP [Internet Protocol]
• CPC Class Codes: H04W 80/10 : adapted for application session management, e.g. SIP [Session Initiation Protocol] connection management H04W76/00; arrangements for session management H04L67/14
• CPC Class Codes: H04W 92/02 : Inter-networking arrangements

Abstract

An apparatus for optimizing roaming in a network environment is provided that includes a bearer manager operable to receive a registration request from a user. An identity of a visited network and access network information is included with the request, a bearer manager consulting the policy server for a policy decision as part of an IP-address assignment or mobile IP registration process. The policy server providing the assigned IP-address, a visited network provider identity and access network information to a home policy server via policy peering. The policy server authorizing the registration and remembering the identity of the visited network provider and the access network information, whereby when the user performs registration, an application manager can request authorization from the policy sever, which checks the identity of the visited network and possible the access network and determines whether to authorize the registration.

Claims

1. An apparatus for optimizing roaming in a network environment, comprising:

a policy server being consulted by a bearer manager for a policy decision as part of an IP-address assignment, Proxy Mobile IP, or mobile IP registration process, the policy server providing both the assigned IP-address and a visited network provider to a home policy server via policy peering, the bearer manager being operable to receive a registration request from a user, wherein an identity of a visited network is included with the request, the policy server authorizing the registration and remembering the identity of the visited network provider for the user, whereby when the user performs application level registration, an application manager, or other SIP and non-SIP applications, can request authorization from the policy server, which checks the identity of the visited network and determines whether to authorize the registration.

2. The apparatus of claim 1, wherein the registration request is via simple IP, Proxy Mobile IP, or Mobile IP on a Bearer Manager in the visited network or in a home network.

3. The apparatus of claim 1, wherein in a visited bearer manager scenario, the bearer manager includes the assigned IP-address with a policy request to the policy server.

4. The apparatus of claim 1, wherein in a home bearer manager scenario, a Mobile IP Registration Request has visited network information appended by a visited bearer manager, which passes it to a home bearer manager, which contacts the policy server for a policy decision, wherein the request to the policy server includes the visited network information and assigned IP-address.

5. The apparatus of claim 1, wherein the authorization can also occur at time of call setup.

6. The apparatus of claim 5, wherein the authorization allows emergency calls only.

7. The apparatus of claim 1, wherein the authorization occurs when an application contacts the policy server for authorization to allow only some applications to be used when the user is roaming in certain provider networks.

8. The apparatus of claim 1, wherein access network information is provided using the policy peering, and wherein the access network information is passed from the IP gateway to the bearer manager via PMIP or policy, and from the bearer manager to the policy manger via policy.

9. The apparatus of claim 8, wherein instead of using SIP signaling, information is passed as part of MIP registration requests or MIP binding updates from a visited to a home network, and also through policy events from the visited network to the home network.

10. The apparatus of claim 1, wherein through policy server peering, a home network can install policy facets into a visited network, which requests notifications on change in access network technologies or on location.

11. The apparatus of claim 1, wherein a home network can track access network information without requiring SIP signaling.

12. A method for optimizing roaming in a network environment, comprising:

providing a policy decision, via a policy manager, to a bearer manager that consults the policy server for the policy decision as part of an IP-address assignment, proxy mobile IP, or mobile IP registration process, and the policy server providing both the assigned IP-address and a visited network provider to a home policy server via policy peering, the bearer manager receiving a registration request from a user, wherein an identity of a visited network is included with the request; and

authorizing the registration and remembering the identity of the visited network provider for the user, whereby when the user performs application level registration, an application manager, or other SIP and non-SIP applications, can request authorization from the policy server, which checks the identity of the visited network and determines whether to authorize the registration.

13. The method of claim 12, wherein the registration request is via simple IP, Proxy Mobile IP or Mobile IP on a Bearer Manager in the visited network or in a home network.

14. The method of claim 12, wherein in a visited bearer manager scenario, the bearer manager includes the assigned IP-address with a policy request to the policy server.

15. The method of claim 12, wherein in a home bearer manager scenario, a Mobile IP Registration Request or Mobile IP Binding Update has visited network information appended by a visited bearer manager, which passes it to a home bearer manager, which contacts the policy server for a policy decision, and where the request to the policy server includes the visited network information and assigned IP-address.

16. The method of claim 12, wherein the authorization can also occur at time of call setup.

17. The method of claim 16, wherein the authorization allows emergency calls only.

18. The method of claim 12, wherein the authorization occurs when an application contacts the policy server for authorization to allow only some applications to be used when the user is roaming in certain provider networks.

19. The method of claim 12, wherein access network information is provided using the policy peering, and wherein the access network information is passed from the IP gateway to the bearer manager via PMIP or policy, and from the bearer manager to the policy manger via policy.

20. The method of claim 19, wherein instead of using SIP signaling, information is passed as part of MIP registration requests or MIP binding updates from a visited to a home network, and also through policy events from the visited network to the home network.

21. The method of claim 12, wherein through policy server peering, a home network can install policy facets into a visited network, which requests notifications on change in access network technologies or on location.

22. The method of claim 12, wherein a home network can track access network information without requiring SIP signaling.

23. Software for optimizing roaming in a network environment, the software being embodied in a computer readable medium and comprising code such that when executed is operable to:

provide a policy decision, via a policy manager, to a bearer manager that consults the policy server for the policy decision as part of an IP-address assignment, proxy mobile IP, or mobile IP registration process, and the policy server providing both the assigned IP-address and a visited network provider to a home policy server via policy peering, the bearer manager receiving a registration request from a user, wherein an identity of a visited network is included with the request; and

authorize the registration and remembering the identity of the visited network provider for the user, whereby when the user performs application level registration, an application manager, or other SIP and non-SIP applications, can request authorization from the policy server, which checks the identity of the visited network and determines whether to authorize the registration.

24. The medium of claim 23, wherein the registration request is via simple IP, Proxy Mobile IP, or Mobile IP on a Bearer Manager in the visited network or in a home network.

25. The medium of claim 23, wherein in a visited bearer manager scenario, the bearer manager includes the assigned IP-address with a policy request to the policy server.

26. The medium of claim 23, wherein in a home bearer manager scenario, a Mobile IP Registration Request or MIP Binding Update has visited network information appended by a visited bearer manager, which passes it to a home bearer manager, which contacts the policy server for a policy decision, and where the request to the policy server includes the visited network information and assigned IP-address.

27. The medium of claim 23, wherein the authorization can also occur at time of call setup, and wherein the authorization allows emergency calls only.

28. The medium of claim 23, wherein the authorization occurs when an application contacts the policy server for authorization to allow only some applications to be used when the user is roaming in certain provider networks.

29. The medium of claim 23, wherein access network information is provided using the policy peering, and wherein the access network information is passed from the IP gateway to the bearer manager via PMIP or policy, and from the bearer manager to the policy manger via policy.

30. The medium of claim 29, wherein instead of using SIP signaling, information is passed as part of MIP registration requests or binding updates from a visited to a home network, and also through policy events from the visited network to the home network.

31. The medium of claim 23, wherein through policy server peering, a home network can install policy facets into a visited network, which requests notifications on change in access network technologies or on location.

32. The medium of claim 23, wherein a home network can track access network information without requiring SIP signaling.