Source: https://patents.google.com/patent/US8875274B2/en
Timestamp: 2019-08-20 19:35:17
Document Index: 487466982

Matched Legal Cases: ['application No. 61', 'Application No. 2009313216', 'Application No. 2009313216', 'Application No. 200980144826', 'art 11', 'art 11', 'art 16', 'art 16', 'art 20', 'art 20', 'Application No. 2011', 'Application No. 10']

US8875274B2 - Methods and apparatus for providing indirect alternative paths to obtain session policy - Google Patents
Methods and apparatus for providing indirect alternative paths to obtain session policy Download PDF
US8875274B2
US8875274B2 US12/615,532 US61553209A US8875274B2 US 8875274 B2 US8875274 B2 US 8875274B2 US 61553209 A US61553209 A US 61553209A US 8875274 B2 US8875274 B2 US 8875274B2
US12/615,532
US20100154031A1 (en
2008-11-10 Priority to US11287308P priority Critical
2009-11-10 Priority to US12/615,532 priority patent/US8875274B2/en
2010-02-17 Assigned to RESEARCH IN MOTION CORPORATION reassignment RESEARCH IN MOTION CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BUCKLEY, ADRIAN, ALLEN, ANDREW
2010-02-17 Assigned to RESEARCH IN MOTION LIMITED reassignment RESEARCH IN MOTION LIMITED ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MONTEMURRO, MICHAEL
2010-06-17 Publication of US20100154031A1 publication Critical patent/US20100154031A1/en
2014-10-28 Publication of US8875274B2 publication Critical patent/US8875274B2/en
A method for a user agent to access a session policy in a network is provided. The method comprises sending, from the user agent, a single session policy request to a single network component, the single network component contacting a plurality of network components, wherein sending the single session policy request to the single network component utilizes a lower layer protocol. The lower layer protocol is at least one of Extensible Authentication Protocol (EAP), Point to Point Protocol (PPP), and General Packet Radio Service (GPRS) Activate Packet Data Protocol (PDP) context. The method further comprises aggregating policy information and providing the aggregated policy information to the user agent.
The present application claims priority to U.S. provisional patent application No. 61/112,873, filed Nov. 10, 2008, by Michael Montemurro, et al, entitled “Method and System for Supporting SIP Session Policy Using Existing Authorization”, which is incorporated by reference herein as if reproduced in its entirety.
At event 20, the first UAA 110 A sends an INVITE message containing an SDP offer to a second UAB 110 6 via the first proxyA 120 A and a second proxyB 120 6. At event 22, the second UAB 110 E sends a PolicyChannel message containing an InfoOffer and an InfoAnswer to a second policy serverB 130 6. At event 24, the second policy serverB 130 8 sends a PolicyChannel message containing a PolicyOffer and a PolicyAnswer to the second UAB 110 B. At event 26, the second UAB 110 8 sends a SIP 200OK answer to the first UAA 110 A via the second proxyB 120 6 and the first proxyA 120 A. The first UAA 110 A then returns a SIP Acknowledgement (ACK) message to the second UAB 110 B. At event 28, the first UAA 110 A sends a PolicyChannel message containing an InfoAnswer to the first proxyA 120 A. At event 30, the first proxyA 120 A sends a PolicyChannel message containing a PolicyAnswer to the first UAA 120 A.
The policy server 130 is a separate logical entity that can be physically colocated with the proxy 120. The role of the policy server 130 is to deliver session policies to the UA 110. The policy server 130 receives session information from the UA 110, uses this information to determine the policies that apply to the session, and returns these policies to the UA 110.
In an embodiment, instead of SIP or SIPS URIs, where a 3GPP PCC or similar AM infrastructure has been deployed, AM URIs or similar URIs are provided in the Policy-Contact header. That is, a communication path that is at a lower layer than the SIP messaging layer is created between a UA and a policy server and is used as a policy channel. The UA can send the policy server a session policy request over this policy channel using a lower layer protocol. In some cases, the lower layer protocol might be the DIAMETER protocol or the RADIUS protocol using the Extensible Authentication Protocol (EAP). Whereas EAP is described, one of ordinary skill may choose other protocols such as, but not limited to, Point to Point Protocol (PPP), etc. In other cases, the lower layer protocol creates a data bearer channel between the wireless device and the network. For example, the wireless device might send a message to the network containing information to create a data channel. This might be a General Packet Radio Service (GPRS) Activate Packet Data Protocol (PDP) which is communication from the wireless device to a network node called SGSN. In an LTE environment, the lower layer protocol in the ESM messages might be, but is not limited to, a PDN_CONNECTIVITY_REQUEST or a BEARER_RESOURCE_MODIFICATION_REQUEST that could be tunneled and/or piggy-backed in an ATTACH message from the wireless device to the MME or as separate default messages. As per RFC 3588 the following are examples of valid DIAMETER or RADIUS host identities:
FIG. 12 depicts an example of how session policy requests might be handled when the UE uses TISPAN NASS/RACS. TISPAN NGN does not use 3GPP PCC. In TISPAN NGN there is the NASS (Network Attachment Sub-System) and RACS (Resource and Admission Control System). The RACS is responsible for elements of policing control, including resource reservation and admission control in the access and aggregation networks. The RAGS provides policy-based transport control services to applications. These services enable applications to request and reserve transport resources from the transport networks within the scope of the RACS. RAGS consists of the SPDF and the A-RACF.
The IP Edge Router, which is equivalent to the gateway in 3GPP PCC, contains the ACEF (Access Control Enforcement Function), which performs equivalent functions to the PCEF in 3GPP PCC. The Re interface between RAGS and the ACEF is not yet standardized. The IP Edge Router also contains the AMF (Access Management Function), which is a RADIUS client that interfaces to the NASS (technically the AMF is part of the NASS). The AMF translates the network access requests sent by UE, forwards the requests for allocation of an IP address and network, and forwards the user authentication requests to the User Access Authorization Function (UAAF). In the reverse direction, AMF forwards the response from the UAAF (User Access Authorization Function) within the NASS to the UE.
A parameter (shown here as the alt-uri parameter) indicates, by containing the hostname contained in the SIP URI of the same policy server, that it is an alternate URI of the same policy server in the other policyContactURI (sip:host.example.com). Assuming that existing SIP UAs will ignore policyContactURI URI schemes that they do not understand, as mandated in draft-ietf-sip-session-policy-framework-05, all UAs that support Session Policy might need to support the SIP and SIPS schemes for obtaining policy documents. The UAs that only support SIP and SIPS URI schemes will ignore the policyContactURIs that use other URI schemes. SIP UAs that understand and support the new URI scheme and the alt-uri tag will understand that aaa://perf.example.com is an alternate URI or address of the same policy server at sip:host.example.com.
[ SEMI “non-cacheable” ] *( SEMI generic-
param )
In the above example, the SIP Proxy for domain example1.com has included its policy server URI, “aaa://host1.example1.com:1813”. Then the SIP proxy for domain example2.com adds its policy server URI, “aaa://host2.example2.com:3868”, and determines that the Policy Server for example1.com can be reached via its policy server and so adds the parameter “proxy-to” set equal to the hostname of the policy server for example1.com (host1.example1.com). Likewise, the SIP proxy for domain example3.com adds its policy server URI, “aaa://host3.example3.com:1727”, and determines that the policy server for example1.com and the policy server for example2.com can be reached via its policy server and so adds the parameter “proxy-to” set equal to the hostname of the policy server for example1.com and a second “proxy-to” parameter set equal to the hostname of the policy server for example2.com.
When the UA receives the SIP Invite request or SIP 488 response containing the above Policy-Contact header, it scans the list of URIs. If a URI in the list has associated one or more proxy-to parameters containing one or more hostnames or domain names appearing in other URIs in the Policy-Contact header, the UA can, when formatting the EAP infoOffer or InfoAnswer message, include parameters such as an Also-Contact parameter containing the AAA URIs of the policy servers from the Policy-Contact header whose hostname or domain name appears in proxy-to parameters associated with that URI listed in the Policy-Contact header. The EAP InfoOffer or InfoAnswer messages also include the intended offer or answer as defined in draft-ietf-sipping-media-policy-dataset-06.
In yet another embodiment, the S-CSCF/Registrar may return in the SIP 200OK to the REGISTER a Policy-Contact header containing a policyContactURI to the policy document. Other SIP proxies such as the P-CSCF on the path of the SIP REGISTER may include their own Policy-Contact headers containing the policyContactURI of their own policy server in the SIP 200OK to the SIP REGISTER directly or directly in the SIP REGISTER itself. If the policyContactURI is included in the SIP REGISTER, the 8-CSCF/Registrar or other proxy can then either obtain the policy document directly and provide it to its own policy server to produce an aggregated policy document or provide the policyContactURI of the other policy server(s) so that an aggregated policy document can be produced by the policy server using the mechanisms described above. The Policy-Contact headers received in the SIP REGISTER may also be provided to the SIP UA in the SIP 200OK to the SIP REGISTER.
The first authorization type message can be received by a network node that could be, but is not limited to, an AAA server, a GGSN, or a CSCF. This network node can take a set of the first authorization type information and put it into a second authorization type message that could be, but is not limited to, RADIUS, DIAMETER, or SIP REGISTER. The first lower layer message could be placed in its entirety into the second one. This second lower layer message can be sent to a second network node that can return the necessary policy information to the first network node. The first network node can do a reverse translation and send back an acknowledgement of the first authorization type to the UA containing the policy information. The following is an example of such a message from the network to the UA:
Policy offer, policy answer, info offer, and info answer are defined in http://www.ietf.org/internet-drafts/draft-ietf-sipping-media-policy-dataset-06.txt
http://www.ietf.org/internet-drafts/draft-ietf-sip-session-policy-framework-05.txt
http://www.ietf.org/internet-drafts/draft-ietf-sipping-media-policy-dataset-06.txt
http://www.ietf.org/internet-drafts/draft-ietf-sipping-config-framework-15.txt
In an embodiment, a method for a user agent to access a session policy in a network is provided. The method comprises sending, from the user agent, a single session policy request to a single network component, the single network component contacting a plurality of network components, wherein sending the single session policy request to the single network component utilizes a lower layer protocol. The lower layer protocol is at least one of Extensible Authentication Protocol (EAP), Point to Point Protocol (PPP), and General Packet Radio Service (GPRS) Activate Packet Data Protocol (PDP) context. The method further comprises aggregating policy information and providing the aggregated policy information to the user agent.
In an alternative embodiment, a user agent is provided. The user agent comprises a processor configured to receive aggregated policy information regarding a plurality of network components responsive to sending a single session policy request, wherein the user agent sends the session policy request to a single network component utilizing a lower layer protocol. The lower layer protocol is at least one of Extensible Authentication Protocol (EAP), Point to Point Protocol (PPP), and General Packet Radio Service (GPRS) Activate Packet Data Protocol (PDP) context.
In an alternative embodiment, a network component is provided. The network component comprises a processor configured to receive a single session policy request and in response to aggregate policy information from a plurality of network components, and further configured to transmit the aggregated policy information. The network component receives the session policy request from a user agent via a lower layer protocol that is at least one of Extensible Authentication Protocol (EAP), Point to Point Protocol (PPP), and General Packet Radio Service (GPRS) Activate Packet Data Protocol (PDP) context.
1. A method for enabling a user agent to access a session policy in a network, the method comprising:
responsive to a network component in a first domain receiving a single session policy request from the user agent, the network component contacting a plurality of network components in different respective domains than the first domain, wherein the single session policy request is sent by the user agent using a lower layer protocol, and wherein the lower layer protocol is at least one of:
General Packet Radio Service (GPRS) Activate Packet Data Protocol (PDP) context;
aggregating policy information received from network component in the different respective domains; and
providing the aggregated policy information to the user agent.
2. The method of claim 1, wherein the aggregated policy information is aggregated the network component in the first domain, wherein the aggredated policy information reflects policies for sessions in the first domain and each of the different domains.
3. The method of claim 1, wherein the network component receives the session policy request via an intermediate component, wherein EAP is the at least one lower layer protocol used for transporting the session policy request between the user agent and the intermediate component, and at least one EAP frame transports the session policy request from the intermediate component to the network component using at least one other lower layer protocol selected from:
4. The method of claim 1, wherein the session policy request is an infoOffer of InfoAnswer message that includes an Also-Contact parameter, wherein the Also-Contact parameter includes at least one URI indicative of one or more of the plurality of the network components.
5. The method of claim 4, further comprising transmitting the aggregated policy information to the user agent in a Policy Offer of PolicyAnswer message utilizing one of the EAP and PPP protocols.
6. The method of claim 1, wherein the network component is at least one of:
7. A user agent, comprising: a hardware processor configured to
receive aggregated policy information responsive to sending a single session policy request to a network component in a first domain, wherein the aggregated policy information includes policy information associated with a plurality of network components in different respective domains than the first domain,
wherein the user agent sends the single session policy request to the network component utilizing a lower layer protocol, and
wherein the lower layer protocol is at least one of:
8. The user agent of claim 7, wherein the session policy request is sent to the network component via an intermediate component, wherein EAP is the at least one lower layer protocol used for transporting the session policy request between the user agent and the intermediate component, and at least one EAP frame transports the session policy request from the intermediate component to the network component using at least one other lower layer protocol selected from:
9. The user agent of claim 7, wherein the session policy request is an InfoOffer of InfoAnswer message that includes an Also-Contact parameter, wherein the Also-Contact parameter includes at least one URI indicative of the plurality of the network components.
10. The user agent of claim 9, wherein the aggregated policy information is transmitted top the user agent in a PolicyOffer or policyAnswer message using one of the EAP and PPP protocols.
11. A network component in a first domain, the network component comprising: a hardware processor configured to:
receive, from a user agent via a lower layer protocol, a single session policy request, wherein the lower layer protocol is at least one of:
contact, in response to receiving the single session policy request, a plurality of network components in different respective domains than the first domain;
aggregate policy information received from the plurality of network components; and
transmit the aggregated policy information to the user agent.
12. The network component of claim 11, wherein the network component receives the session policy request via an intermediate component, wherein EAP is the at least one lower layer protocol used for transporting the session policy request between the user agent and the intermediate component, and at least one EAP frame transports the session policy request from the intermediate component to the network component using at least one other lower layer protocol selected from:
13. The network component of claim 11, wherein the network component is at least one of:
14. The user agent of claim 7, wherein the policy information associated with the plurality of network components comprises a plurality of policy documents requested by the network component in the first domain, and the aggregated policy information comprises a composite policy document reflecting session policies for the first domain and each of the different domains.
15. The network component of claim 11, wherein the policy information received from the plurality of network components comprises a plurality of respective policy documents, and the aggregated policy information comprises a composite policy document reflecting session policies for the first domain and each of the different domains.
US12/615,532 2008-11-10 2009-11-10 Methods and apparatus for providing indirect alternative paths to obtain session policy Active 2031-05-08 US8875274B2 (en)
US11287308P true 2008-11-10 2008-11-10
US12/615,532 US8875274B2 (en) 2008-11-10 2009-11-10 Methods and apparatus for providing indirect alternative paths to obtain session policy
US20100154031A1 US20100154031A1 (en) 2010-06-17
US8875274B2 true US8875274B2 (en) 2014-10-28
US12/615,532 Active 2031-05-08 US8875274B2 (en) 2008-11-10 2009-11-10 Methods and apparatus for providing indirect alternative paths to obtain session policy
US12/615,531 Active 2031-08-14 US8537822B2 (en) 2008-11-10 2009-11-10 Methods and apparatus for providing alternative paths to obtain session policy
US12/615,536 Active 2031-09-25 US9154399B2 (en) 2008-11-10 2009-11-10 Methods and apparatus for providing session policy during a registration of a device
US12/615,528 Abandoned US20100142517A1 (en) 2008-11-10 2009-11-10 Method and System for Supporting SIP Session Policy Using Existing Authorization Architecture and Protocols
US14/839,161 Active US9491243B2 (en) 2008-11-10 2015-08-28 Methods and apparatus for providing session policy during a registration of a device
US15/339,426 Active US9967348B2 (en) 2008-11-10 2016-10-31 Methods and apparatus for providing session policy during a registration of a device
AU (1) AU2009313216B2 (en)
MX (1) MX2011004885A (en)
WO (1) WO2010054354A2 (en)
CN102387081B (en) * 2011-11-18 2014-04-02 华为技术有限公司 Communication service QoS assurance method, device and system in NAT scene
JP5337889B2 (en) * 2012-02-24 2013-11-06 株式会社エヌ・ティ・ティ・ドコモ Mobile station and a communication method
CN109511115A (en) * 2017-09-14 2019-03-22 华为技术有限公司 A kind of authorization method and network element
US20030103457A1 (en) 2001-10-23 2003-06-05 Moran Timothy L. Method and packet switched communication network with enhanced session establishment
WO2004077742A1 (en) 2003-02-28 2004-09-10 Siemens Aktiengesellschaft Method for transmitting data in a wlan network
JP2005260571A (en) 2004-03-11 2005-09-22 Nec Corp Communication relay device, communication relay method, and communication relay program
US20060045067A1 (en) 2004-08-30 2006-03-02 Rockwell Electronic Commerce Technologies, Llc Method of collecting communication system information
US20070250569A1 (en) 2006-04-25 2007-10-25 Nokia Corporation Third-party session modification
US20080022354A1 (en) 2006-06-27 2008-01-24 Karanvir Grewal Roaming secure authenticated network access method and apparatus
WO2009049684A1 (en) 2007-10-19 2009-04-23 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatuses for notifying an application function of resource restrictions relating to a communication session
US20090113067A1 (en) 2007-10-30 2009-04-30 Flemming Andreasen Communicating a selection of a potential configuration
US20090154451A1 (en) 2007-12-12 2009-06-18 At&T Knowledge Ventures, Lp Method and System to Provide Contact Services in a Communication Network
US20090238358A1 (en) 2008-03-21 2009-09-24 Microsoft Corporation Communicating information pertaining to cancelling of forked call requests
US20090320094A1 (en) 2008-02-14 2009-12-24 Nokia Corporation System and Method for Implementing a Publication
US20100157985A1 (en) 2007-03-30 2010-06-24 Kazuhiko Nakada System and method for indicating circuit switched access at ims registration
2009-11-10 US US12/615,532 patent/US8875274B2/en active Active
2009-11-10 AU AU2009313216A patent/AU2009313216B2/en active Active
2009-11-10 US US12/615,531 patent/US8537822B2/en active Active
2009-11-10 US US12/615,536 patent/US9154399B2/en active Active
2009-11-10 US US12/615,528 patent/US20100142517A1/en not_active Abandoned
2009-11-10 CN CN200980144826.2A patent/CN102210132B/en active IP Right Grant
2009-11-10 JP JP2011535754A patent/JP2012508525A/en active Pending
2009-11-10 MX MX2011004885A patent/MX2011004885A/en active IP Right Grant
2009-11-10 KR KR1020117013105A patent/KR101242995B1/en active IP Right Grant
2009-11-10 CA CA2743010A patent/CA2743010C/en active Active
2009-11-10 WO PCT/US2009/063811 patent/WO2010054354A2/en active Application Filing
2009-11-10 EP EP09761071.1A patent/EP2353273B1/en active Active
2015-08-28 US US14/839,161 patent/US9491243B2/en active Active
2016-10-31 US US15/339,426 patent/US9967348B2/en active Active
CN1757198A (en) 2003-02-28 2006-04-05 西门子公司 Method for transmitting data in a wlan network
3GPP TS 23.203 V7.7.0; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Policy and Charging Control Architecture; Release 7; Jun. 2008; 73 pgs.
3GPP TS 23.228 v8.5.0; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; IP Multimedia Subsystem (IMS) Stage 2; Release 8; Jun. 2008; 240 pgs.
3GPP TS 24.229 V8.4.1; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; IP Multimedia Call Control Protocol Based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3; Release 8; Jun. 2008; 518 pgs.
Aboba, B., et al., "Extensible Authentication Protocol (EAP) Key Management Framework," Network Working Group, RFC 5247, Aug. 2008, 89 pgs.
Aboba, B., et al., "The Network Access Identifier," Network Working Group, RFC 4282, Dec. 2005, 18 pgs.
Advisory Action dated Aug. 30, 2013; U.S. Appl. No. 12/615,536, filed Nov. 10, 2009; 7 pages.
Advisory Action dated Nov. 5, 2012; U.S. Appl. No. 12/615,528, filed Nov. 10, 2009; 3 pages.
Allen, Andrew, et al, U.S. Appl. No. 12/388,381, filed Feb. 18, 2009; Title: System and Method for Indicating Supported Session Policy URI Schemes Extensions.
Australian Examination Report; Application No. 2009313216; Feb. 4, 2013; 3 pages.
Australian Notice of Allowance; Application No. 2009313216; Dec. 10, 2013; 2 pages.
Bakker, John-Luc, et al.; U.S. Appl. No. 12/388,386, filed Feb. 18, 2009; Title: System and Method for Resolving Extensions for the SIP Session Policy Framwork.
Berners-Lee, T., et al.; "Uniform Resource Identifier (URI): Generic Syntax", RFC 3986; Jan. 2005; 62 pages.
Blunk, L., et al., "PPP Extensible Authentication Protocol (EAP)," Network Working Group, RFC 2284, Mar. 1998, 17 pgs.
Calhoun, P., et al., "Diameter Base Protocol," Network Working Group, RFC 3588, Sep. 2003, 165 pgs.
Camarillo, G., et al., "Integration of Resource Management and Session Initiation Protocol (SIP)," Network Working Group, RFC 3312, Oct. 2002, 34 pgs.
Chinese Office Action; Application No. 200980144826.2; Jun. 28, 2013; 23 pages.
Final Office Action dated Aug. 9, 2012; U.S. Appl. No. 12/615,528, filed Nov. 10, 2009; 17 pages.
Final Office Action dated Feb. 4, 2013; U.S. Appl. No. 12/615,531, filed Nov. 10, 2009; 9 pages.
Final Office Action dated Jun. 19, 2013; U.S. Appl. No. 12/615,536, filed Nov. 10, 2009; 24 pages.
Final Office Action dated Nov. 2, 2012; U.S. Appl. No. 12/615,531, filed Nov. 10, 2009; 20 pages.
Handley, M., et al., "SDP: Session Description Protocol," Network Working Group, RFC 4566, Jul. 2006, 55 pgs.
Hilt, V., et al., "A Framework for Session Initiation Protocol (SIP) Session Policies," draft-ietf-sip-session-policy-framework-05; Sipping Working Group, Internet-Draft, Nov. 1, 2008, 36 pgs.
Hilt, V., et al.; "A Framework for Session Initiation Protocol (SIP) Session Policies"; draft-ietf-sip-session-policy-framework-03; Apr. 27, 2008; 36 pages.
Hilt, V., et al.; "A Framework for Session Inititation Protocol (SIP) Session Policies"; draft-hilt-sipping-session-policy-framework-00; Oct. 16, 2005; 18 pages.
IEEE Standard, 802.11(TM), "IEEE Standard for Information Technology-Telecommunications and Information Exchange Between Systems-Local and Metropolitan Area Networks-Specific Requirements, Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications," IEEE Computer Society, Jun. 12, 2007, 48 pages.
IEEE Standard, 802.11™, "IEEE Standard for Information Technology—Telecommunications and Information Exchange Between Systems—Local and Metropolitan Area Networks—Specific Requirements, Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications," IEEE Computer Society, Jun. 12, 2007, 48 pages.
IEEE Standard, 802.16(TM), "IEEE Standard for Local and Metropolitan Area Networks, Part 16: Air Interface for Broadband Wireless Access Systems," IEEE Computer Society and IEEE Microwave Theory and Techniques Society, May 29, 2009, 77 pages.
IEEE Standard, 802.16™, "IEEE Standard for Local and Metropolitan Area Networks, Part 16: Air Interface for Broadband Wireless Access Systems," IEEE Computer Society and IEEE Microwave Theory and Techniques Society, May 29, 2009, 77 pages.
IEEE Standard, 802.20(TM), "IEEE Standard for Local and Metropolitan Area Networks, Part 20: Air Interface for Mobile Broadband Wireless Access Systems Supporting Vehicular Mobility-Physical and Media Access Control Layer Specification," IEEE Computer Society, Aug. 29, 2008, 13 pages.
IEEE Standard, 802.20™, "IEEE Standard for Local and Metropolitan Area Networks, Part 20: Air Interface for Mobile Broadband Wireless Access Systems Supporting Vehicular Mobility—Physical and Media Access Control Layer Specification," IEEE Computer Society, Aug. 29, 2008, 13 pages.
Japanese Office Action; Application No. 2011-535754; Jan. 8, 2014; 8 pages.
Kempf, J., et al., "Distributing a Symmetric Fast Mobile IPv6 (FMIPv6) Handover Key Using Secure Neighbor Discovery (SEND)," Network Working Group, RFC 5108, Jan. 2008, 16 pgs.
Khartabil, H., et al.; "Conveying a Session Policy Uniform Resource Identifier (URI) in the Session Initiation Protocol (SIP)", draft-khartbil-sip-policy-uri-call-info-purpose-00; Feb. 5, 2004; 8 pages.
Korean Office Action; Application No. 10-2011-7013105; Jul. 20, 2012; 7 pages.
Mexican Office Action; Application No. MX/a/2011/004885; Feb. 24, 2012; 4 pages.
Montemurro, Michael, et al.; U.S. Appl. No. 12/615,528, filed Nov. 10, 2009; Title: Method and System for Supporting SIP Session Policy Using Existing Authorization Architecture and Protocols.
Montemurro, Michael, et al.; U.S. Appl. No. 12/615,531, filed Nov. 10, 2009; Title: Methods and Apparatus for Providing Alternative Paths to Obtain Session Policy.
Montemurro, Michael, et al.; U.S. Appl. No. 12/615,536, filed Nov. 10, 2009; Title: Methods and Apparatus for Providing Session Policy During a Registration of a Device.
Notice of Allowance dated Apr. 16, 2013; U.S. Appl. No. 12/615,531, filed Nov. 10, 2009; 16 pages.
Office Action date Jun. 18, 2014; U.S. Appl. No. 12/615,536, filed Nov. 10, 2009; 17 pages.
Office Action dated Jul. 17, 2012; U.S. Appl. No. 12/615,636, filed Nov. 10, 2009; 33 pages.
Office Action dated Jun. 4, 2012; U.S. Appl. No. 12/615,531, filed Nov. 10, 2009; 15 pages.
Office Action dated Mar. 23, 2012; U.S. Appl. No. 12/615,528, filed Nov. 10, 2009; 20 pages.
PCT International Search Report; PCT Application No. PCT/US2009/063811, Nov. 12, 2010; 4 pgs.
PCT Written Opinion of the International Searching Authority; CT Application No. PCT/US2009/063811, Nov. 12, 2010; 6 pgs.
Petrie, D., et al.; "A Schema and Guidelines for Defining Session Inititation Protocol User Agent Profile Data Sets"; draft-petrie-sipping-profile-datasets-03.txt; Oct. 23, 2005; 37 pages.
Roach, A., "Session Initiation Protocol (SIP)-Specific Event Notification," Network Working Group, RFC 3265, Jun. 2002, 43 pgs.
Roach, A., "Session Initiation Protocol (SIP)—Specific Event Notification," Network Working Group, RFC 3265, Jun. 2002, 43 pgs.
Rosenberg, J., et al., "An Offer/Answer Model with the Session Description Protocol (SDP)," Network Working Group, RFC 3264, Jun. 2002, 29 pgs.
Rosenberg, J., et al., "SIP: Session Initiation Protocol," Network Working Group, RFC 3261, Jun. 2002, 302 pgs.
Schulzrinne, H., et al., "CIPID: Contact Information for the Presence Information Data Format," Network Working Group, RFC 4482, Jul. 2006, 13 pgs.
Townsley, W., et al., "Layer Two Tunneling Protocol ‘L2TP’," Network Working Group, RFC 2661, Aug. 1999, 90 pgs.
Townsley, W., et al., "Layer Two Tunneling Protocol 'L2TP'," Network Working Group, RFC 2661, Aug. 1999, 90 pgs.
US9154399B2 (en) 2015-10-06
AU2009313216A1 (en) 2010-05-14
KR101242995B1 (en) 2013-03-12
KR20110082620A (en) 2011-07-19
US20170048330A1 (en) 2017-02-16
US20100146130A1 (en) 2010-06-10
EP2353273B1 (en) 2018-05-02
CA2743010A1 (en) 2010-05-14
CN102210132B (en) 2014-09-24
US8537822B2 (en) 2013-09-17
US9491243B2 (en) 2016-11-08
CN102210132A (en) 2011-10-05
US9967348B2 (en) 2018-05-08
MX2011004885A (en) 2011-05-30
WO2010054354A3 (en) 2010-12-29
US20100154031A1 (en) 2010-06-17
CA2743010C (en) 2018-04-03
US20100142517A1 (en) 2010-06-10
JP2012508525A (en) 2012-04-05
US20150373125A1 (en) 2015-12-24
EP2353273A2 (en) 2011-08-10
WO2010054354A2 (en) 2010-05-14
AU2009313216B2 (en) 2013-12-19
US20100154030A1 (en) 2010-06-17
JP5298203B2 (en) 2013-09-25 Correlation of token-based control session for policy and charging control of data session through Nat
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ALLEN, ANDREW;BUCKLEY, ADRIAN;SIGNING DATES FROM 20091211 TO 20100211;REEL/FRAME:023949/0492
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MONTEMURRO, MICHAEL;REEL/FRAME:023949/0561
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:RESEARCH IN MOTION CORPORATION;REEL/FRAME:025941/0344