Determining a policy output for a communication session

Information

  • Patent Grant
  • 8719895
  • Patent Number
    8,719,895
  • Date Filed
    Tuesday, March 6, 2007
    17 years ago
  • Date Issued
    Tuesday, May 6, 2014
    10 years ago
Abstract
Determining a policy output includes facilitating a communication session for an access terminal at a visited network. The access terminal is associated with a home network. A policy is received at a visited policy server of the visited network. The policy has facets that include an application facet that identifies an application deployable in the home network. The application is identified from the application facet, and the policy output is determined in accordance with the application.
Description
TECHNICAL FIELD

This invention relates generally to the field of telecommunications and more specifically to determining a policy output for a communication session.


BACKGROUND

An endpoint, such as an access terminal, may use a system of communication networks to communicate packets with other endpoints during communication sessions. For example, an access terminal may subscribe to a home network that maintains subscription information for the access terminal. If the access terminal is outside of the serving area of the home network, the access terminal may use a visited network to communicate packets.


Certain known techniques may be used to make policy decisions, such as accounting or quality of service decisions, for these communication sessions. These known techniques, however, are not efficient in certain situations. In certain situations, it is generally desirable to be efficient.


SUMMARY OF THE DISCLOSURE

In accordance with the present invention, disadvantages and problems associated with previous techniques for communicating packets may be reduced or eliminated.


According to one embodiment of the present invention, determining a policy output includes facilitating a communication session for an access terminal at a visited network. The access terminal is associated with a home network. A policy is received at a visited policy server of the visited network. The policy has facets that include an application facet that identifies an application deployable in the home network. The application is identified from the application facet, and the policy output is determined in accordance with the application.


Certain embodiments of the invention may provide one or more technical advantages. A technical advantage of one embodiment may be that a home policy server of a home network may provide a policy to a visited policy server of a visited network. The policy may include application facets that allow the visited network to make policy decisions for an application without having to execute or otherwise support the application.


Another technical advantage of one embodiment may be that the visited policy server may negotiate with the home policy server to establish policy facets acceptable to the policy servers. The visited policy server need not be forced to use unacceptable policy facets.


Another technical advantage of one embodiment may be that one or more policy facets may be installed on a network element in the home network and/or the visited network. The policy facets may allow the network element to make policy decisions.


Another technical advantage of one embodiment may be that a deep packet inspection (DPI) facet may be dynamically installed on an edge router. The DPI facet may have a scope and rules based on a particular application invocation. The DPI facet may allow the edge router to perform deep packet inspection of the relevant packets at the edge router.


Certain embodiments of the invention may include none, some, or all of the above technical advantages. One or more other technical advantages may be readily apparent to one skilled in the art from the figures, descriptions, and claims included herein.





BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present invention and its features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:



FIG. 1 illustrates one embodiment of a system that communicates packets for an access terminal;



FIG. 2 illustrates an example of a policy model that may be used with the system of FIG. 1;



FIG. 3 illustrates an example of a call flow for establishing policy facets that may be used by the system of FIG. 1;



FIG. 4 illustrates an example of a call flow for determining a policy output that may be used by the system of FIG. 1; and



FIG. 5 illustrates an example of a call flow for implementing a deep packet inspection policy that may be used by the system of FIG. 1.





DETAILED DESCRIPTION OF THE DRAWINGS

Embodiments of the present invention and its advantages are best understood by referring to FIGS. 1 through 5 of the drawings, like numerals being used for like and corresponding parts of the various drawings.



FIG. 1 illustrates one embodiment of a system 10 that communicates packets for an access terminal 20. According to the embodiment, system 10 includes a visited network 24 and a home network 28. Visited network 24 includes a radio access network (RAN) 32, an Internet Protocol (IP) gateway (IPGW) 36, a visited bearer manager (V-bearer manager) 40a, and a visited policy server (V-policy server) 44a coupled as shown. Home network 28 includes a home bearer manager (H-bearer manager) 40b, a home policy server (H-policy server) 44b, a services data manager 52, and an application manager 56 coupled as shown.


According to certain examples, home policy server 44b may provide a policy to visited policy server 44a. The policy may include application facets that allow visited network 24 to make policy decisions for an application without having to execute or otherwise support the application. Application facets may comprise a set of one or more tokens (such as text-strings) that identify an application and/or components of the application. The tokens are understood by home policy server 44b and visited network policy server 44a. In one example, visited policy server 44a may negotiate with home policy server 44b to establish acceptable policy facets, so visited policy server 44a need not be forced to use unacceptable policy facets. In another example, a policy facet may be installed on a network element to allow the network element to make policy decisions. For example, a deep packet inspection (DPI) facet may be installed on an edge router to allow the edge router to perform deep packet inspection of the packets at the edge router.


According to the illustrated embodiment, system 10 provides services such as communication sessions to endpoints such as access terminal 20. A communication session refers to an active communication between endpoints. Information may be communicated during a communication session. Information may include voice, data, text, audio, video, multimedia, control, signaling, and/or other information. Information may be communicated in packets, each comprising a bundle of data organized in a specific way for transmission.


System 10 may utilize communication protocols and technologies to provide communication sessions. Examples of communication protocols and technologies include those set by the Institute of Electrical and Electronics Engineers, Inc. (IEEE) standards, the International Telecommunications Union (ITU-T) standards, the European Telecommunications Standards Institute (ETSI) standards, the Internet Engineering Task Force (IETF) standards (for example, IP such as mobile IP), or other standards.


According to the illustrated embodiment, access terminal 20 represents any suitable device operable to communicate with a communication network. For example, a subscriber may use access terminal 20 to communicate with a communication network. Access terminal 20 may comprise, for example, a personal digital assistant, a computer such as a laptop, a cellular telephone, a mobile handset, and/or any other device operable to communicate with system 10.


System 10 includes communication networks such as visited network 24 and home network 28. In general, a communication network may comprise at least a portion of a public switched telephone network (PSTN), a public or private data network, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a local, regional, or global communication or computer network such as the Internet, a wireline or wireless network, an enterprise intranet, other suitable communication links, or any combination of any of the preceding.


In the illustrated embodiment, visited network 24 represents a communication network that facilitates a communication session for access terminal 20 within the serving area of visited network 24. Home network 28 represents a communication network that maintains a subscription for the subscriber using access terminal 20. The subscription for a subscriber may have subscriber identifier that uniquely identifies the subscriber, and may include an account that is charged based upon usage by access terminal 20. Visited network 24 and home network 28 may be part of the same or different communication networks.


Radio access network 32 provides access services to access terminal 20. For example, radio access network 32 may provide Layer 2 mobile access, mobility, and/or handoff services within its area of coverage.


IP gateway 36 operates as a gateway between radio access network 32 and an IP network. IP gateway 36 may perform operations such as authenticating access terminal 20, assigning a bearer manager 40 to access terminal 20, performing handoff functions between IP gateway 36 and radio access network 32, and/or facilitating registration of access terminal 20 to the IP network.


Bearer managers 40 provide bearer paths that communicate packets to and/or from access terminal 20. According to one embodiment, a bearer manager 40 operates as an anchor for a bearer path. Bearer manager 40 may operate as a home or foreign agent that authorizes use of a network address that allows access terminal 20 to use the bearer path anchored by bearer manager 40.


Bearer managers 40 may perform other suitable operations to provide services to access terminal 20. Examples of other suitable operations include processing signaling, committing resources, and maintaining gateways for access terminal 20. A bearer manager 40 may comprise any suitable device, for example, a Serving General Packet Radio Services (GPRS) Support Node (SGSN), a GPRS Gateway Support Node (GGSN), a home/foreign agent, a mobile gateway, a mobile IPv6 node, or a Packet Data Serving Node (PDSN). A bearer manager 40 may use any suitable protocol, for example, an IP Multimedia Subsystem (IMS) protocol.


Policy servers 44 manage policies. A policy may include one or more policy rules, where a policy rule specifies an action to be taken if one or more conditions are satisfied. A policy may include facets, which are policy rules that may be installed and executed on a network element. A facet may allow a network element to make policy decisions.


In one embodiment, a deep packet inspection (DPI) facet 60 may be installed on any suitable edge router to allow the edge router to perform deep packet inspection on packets. DPI facet 60 may specify packets to be inspected and rules to be applied to the packets. DPI facet 60 may be used to find SIP packets, verify media (such as Real-Time Transport Protocol (RTP) media) of the media packets, and otherwise inspect the packets sent through the edge router. In one example, DPI facet 60 may be installed on visited bearer manager 40a. Policy and facets are described in more detail with reference to FIG. 2.


Services data manager (SDM) 52 stores subscriber data for access terminals 20. According to one embodiment, services data manager 52 may store policy documents that define policies. One or more subscribers may be associated with a particular policy document that defines the policies for those subscribers.


Application manager 56 manages applications, such as SIP applications and/or other suitable applications. The applications may be used to perform SIP operations (such as SIP registration, authorization, and routing), voice features (such as call routing and call forwarding), services (such as push-to-talk (PTT) and IP Centrex), Service Capabilities Interaction Management (SCIM), user presence services, and/or other operations. A non-SIP application manager may be used to perform non-SIP operations, such as Real-Time Streaming Protocol (RTSP) media operations, proprietary gaming operations, and/or other operations. Application manager 56 may communicate with policy server 44 to request a policy to be implemented on its behalf for a particular access terminal 20.


A component of system 10 may include any suitable arrangement of elements, for example, an interface, logic, memory, other suitable element, or combination of any of the preceding. An interface receives input, sends output, processes the input and/or output, and/or performs other suitable operation. An interface may comprise hardware and/or software.


Logic performs the operations of the component, for example, executes instructions to generate output from input. Logic may include hardware, software, and/or other logic. Certain logic, such as a processor, may manage the operation of a component. Examples of a processor include one or more computers, one or more microprocessors, one or more applications, and/or other logic.


A memory stores information. A memory may comprise computer memory (for example, Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (for example, a hard disk), removable storage media (for example, a Compact Disk (CD) or a Digital Video Disk (DVD)), database and/or network storage (for example, a server), other computer-readable medium, or a combination of any of the preceding.


Modifications, additions, or omissions may be made to system 10 without departing from the scope of the invention. The components of system 10 may be integrated or separated according to particular needs. Moreover, the operations of system 10 may be performed by more, fewer, or other modules. Additionally, operations of system 10 may be performed using any suitable logic. As used in this document, “each” refers to each member of a set or each member of a subset of a set.



FIG. 2 illustrates an example of a policy model 110 that may be used with system 10 of FIG. 1. In one embodiment, policy model 110 includes a policy 114, one or more inputs 116 (such as a policy context 118 and a question 122), and one or more outputs 123 (such as application facets 124, network facets 128, and a decision 132). Network facets 128 may include deep packet inspection (DPI) facets 136.


Policy 114 may be embodied by logic that may be executed by policy server 44. Policy 114 may include one or more policy rules, where a policy rule specifies an action to be taken if one or more conditions are satisfied. Inputs 116 are used to determine whether conditions are satisfied, and outputs 123 describe the actions to be taken.


In the illustrated embodiment, inputs 116 include policy context 118 and question 122. Policy context 118 represents information that may be used to obtain an output 123 from a policy rule. Policy context 118 may include the identity of a subscriber, the application that a subscriber is trying to invoke, the network in which a subscriber is present, and/or other information to which a policy rule may be applied.


Question 122 invokes application of a policy 114. Question 122 may have the form, “Subscriber X has sent a request Y, with policy context Z”. In response to question 122, policy server 44 applies policy 114 to the request Y for subscriber X with policy context Z to yield an output 123.


In the illustrated embodiment, outputs 123 include application facets 124, network facets 128, and a decision 132. Decision 132 specifies one or more actions to be taken and are determined in accordance with the application of policy 114. Decision 132 may be determined according to any suitable factor, for example, the requesting provider, current resource usage, and/or other suitable factor.


A facet is itself a policy that may be installed and executed (for example, enforced) on any suitable network component, for example, IP gateway 36, bearer manager 40, and/or application manager 56. In one embodiment, a facet may allow a network element to make policy decisions for a subscriber. For example, bearer manager 40 may be used to make accounting, DPI, roaming, and/or other suitable policy decisions. IP gateway 36 may be used to make quality of service, accounting, and/or other suitable policy decisions.


Facets may be installed in a push or pull mode. In the push mode, policy server 44 actively pushes a facet to a network element, for example, bearer manager 40. The network element may decide whether the installation can succeed, and either rejects or accepts the installation.


In the pull mode, the network component receives a request from a subscriber. The component asks policy server 44 whether the request can be granted. Policy server 44 provides an output 123, which may include facets. In certain cases, policy server 44 may not be able to provide an immediate response. For example, approval of a request may require additional information that needs to be obtained. In this case, policy server 44 may answer with a pending response.


A facet may include tokens that specify the conditions and actions of the facet. Tokens for the conditions may specify a subscriber identifier and a packet classifier. Tokens for the actions specify actions to be taken for the subscriber with the subscriber identifier and packets that match the packet classifier. In one embodiment, the tokens may be generic, in that home network 28 and visited network 24 agree upon the usage of the tokens.


In one embodiment, a packet may match a packet classifier if characteristics of the packet satisfy conditions of the packet classifier. For example, a packet classifier may include an IP address and/or port range. A packet that has the IP address and uses a port in the port range may be regarded as matching the packet classifier.


Application facets 124 govern the processing of application requests. Application facets 124 may include a policy decision and one or more tokens. The policy decision may specify whether an application should proceed or terminate, and the tokens may specify actions that the application should perform. Application facets 124 may be installed any suitable network component, for example, application manager 56 and/or bearer manager 44 acting as a application proxy. An application facet 124 may identify an application and application parameters.


Network facets 128 perform network functions such as mobility, access, quality of service, transcoding, accounting, DPI, and/or other functions. A network facet 128 may request network resources for performing the functions. Examples of network facets 128 include mobility, access, quality of service, accounting, transcoding, DPI, and/or other suitable facets.


Mobility facets include rules for mobility decisions. Examples of mobility facets include roaming, handoff, active/dormant reporting, paging filter, and/or other suitable mobility facets. A roaming facet specifies whether roaming is permitted. A handoff facet specifies how handoff is to operate between the same and/or different access technologies. The handoff facet may specify whether handoff is permitted across different network technologies and whether handoff should retrigger authentications. An active/dormant reporting facet indicates whether to report the active/dormant state of access terminal 20 to policy server 44. A paging filter facet specifies packets that initiate paging of client 20.


Access facets include rules for access decisions. A permitted correspondents facet is an example of an access facet. A permitted correspondents facet specifies a set of packets that client 20 is allowed to send or receive. A permitted correspondents facet may be provided to a network element, such as bearer manager 20, statically during mobile IP registration or dynamically in response to a request.


Quality of service facets include rules for quality of service decisions. Examples of quality of service facets include bandwidth reservation, packet marker, traffic shaper/policer, authorization envelope, and/or other suitable quality of service facets. A bandwidth reservation facet specifies the amount of bandwidth for a set of packets. A packet marker facet sets a differential service code point for a set of packets. A traffic shaper/policer facet indicates packets to be dropped, marked, and/or shaped. An authorization envelope facet indicates a maximum authorized bandwidth for an access terminal 20. If access terminal 20 requests more, an authorization request is sent to policy server 44.


Transcoding facets include rules for transcoding decisions. A transcoder facet is an example of a transcoding facet. A transcoder facet identifies a stream, for example, a Real-Time Transport Protocol (RTP) stream, that requires transcoding.


Accounting facets include rules for accounting decisions. Examples of accounting facets include packet counter, threshold, time trigger, and/or other suitable accounting facet. A packet counter facet counts a particular type of packet. A threshold facet specifies a maximum and/or minimum value for a specific counter. If the threshold is exceeded, then policy server 44 may be notified. A time trigger facet specifies a timer value for a specific packet counter. When the time value is reached, policy server 44 may be notified.


Deep packet inspection (DPI) facets include rules for deep packet inspection decisions. A DPI facet specifies packets to inspect, what to inspect or detect, and actions to take if packets with certain features are detected. An application detection facet is an example of a DPI facet. An application detection facet may be used to inspect packets to detect the presence of an application, and may specify actions to take if the application is detected.


A DPI facet may include a subscriber identifier, application identifier, and/or packet classifiers. The subscriber identifier and application identifier may identify the subscriber and application, respectively, for which packets are to be inspected. The packet classifiers may include the IP address and port range of packets to be inspected. The IP address and port range may be used to validate the usage of applications and their associated packets signaled through protocols such as SIP.


Packets may be inspected for any suitable feature, for example, packet signature, bandwidth used by packets, compression protocol, content, or other suitable feature. For example, packets may be inspected to determine whether the packets include what they are supposed to include, for example, whether the packets include voice and audio instead of copyrighted files. Actions may include terminating an application, allowing the application, or notifying policy server 44 of the presence of the application. Policy server 44 may then take further action.


According to one embodiment, a particular network facet may include tokens for different types of facets. The tokens may specify, for example, a packet classifier, a network facet state, a quality of service parameter, an authorized quality of service, and/or other suitable parameters. The packet classifier specifies the packets that are allowed through a network element. The network facet state specifies whether packets matching the packet classifier can flow through a gateway. The quality of service parameters specifies the granted quality of service. The authorized quality of service may specify the authorized envelope for the IP flow.


According to one embodiment, network facets 128 may be correlated with application facets 124. A network facet 128 may be correlated with an application facet 124 if a packet either matches the packet classifiers of both the network facet 128 and application facet 124 or matches the packet classifiers of neither. For example, a policy server 44 may match a network facet with a later-arriving application facet to make an application aware policy decision and install the decision on a network element.


Policies 114 may be static or dynamic. The facets of static policies are installed at a particular time, for example, when access terminal 20 registers with a network 24 or 28. Static policies typically depend on policy contexts that are fixed during the lifetime of the registration, such as the identity of the subscriber. The facets of dynamic policies are installed at the time access terminal 20 invokes an application.


Policies 114 may be shared between visited network and home network 28. Visited network 24 and home network 28 may have agreements to recognize specific facets. Accordingly, visited network 24 that receives a policy 114 from home network 28 may make application aware policy decisions based on the policy 114 without having to deploy or otherwise support the application in question. For example, visited network 24 may de-prioritize a quality of service request for one application over another application, even though visited network 24 has not deployed either application.



FIG. 3 illustrates an example of a call flow for establishing policy facets that may be used by system 10 of FIG. 1. The method begins at step 150, where visited bearer manager 40a and/or visited policy server 44a facilitate registration for access terminal 20. Facilitating registration may involve receiving and sending messages for registration. Visited policy server 44a and home policy server 44b exchange capabilities at step 154 to establish the facets that each policy server 44 may support.


Visited policy server 44a requests a policy from home policy server 44b at step 158. Home policy server 44b retrieves the requested policy from services data manager 52 at step 160. The policy may include facets, for example, network and application facets. Home policy server 44b sends the policy to visited policy server 44a at step 162.


Steps 164 through 182 describe negotiation of facets. The facets may be acceptable to visited policy server 44a at step 164. In one embodiment, facets may be acceptable if they are not unacceptable. Facets may be unacceptable to a policy server 44 if policy server 44 does not support a facet or if a facet is incompatible with policies present at policy server 44. Facets of different policies may be considered incompatible if policy server 44 cannot satisfy both facets, for example, if the facets are contradictory.


Visited policy server 44a may identify an application from an application identifier of an application facet to determine whether the facets are acceptable. If the facets are acceptable, the method proceeds directly to step 186. If the facets are not acceptable, the method proceeds to step 166, where visited policy server 44a adjusts one or more of the facets. A policy server 44 may adjust a facet by changing a parameter of a facet to make the facet acceptable to policy server 44 or by removing the facet.


Visited policy server 44a notifies home policy server 44b of the adjustment at step 174. A policy server 44 may notify another policy server 44 of an adjustment by sending the adjusted facets 44 or by sending a description of the changes that make the adjustment.


The facets may be acceptable to home policy server 44b at step 178. In one embodiment, if visited policy server 44a does not support facets that apply to particular packets, home policy server 44b may instruct access terminal 20 to tunnel these packets to home bearer manager 44a for application of the facets.


If the facets are not acceptable, the method proceeds to step 182, where home policy server 44b adjusts one or more of the facets and notifies visited policy server 44a of the adjustment. The method then returns to step 164, where facets may be acceptable to visited policy server 44a. If the facets are acceptable, the method proceeds directly to step 186.


Negotiation may continue until a stopping point is reached. A stopping point may be reached when policy servers 44 agree on the facets, that is, when the facets are acceptable to policy servers 44. A stopping point may be reached when a specified number of iterations, for example, one, two, or three iterations, have been performed. If the facets are not acceptable and a stopping point has been reached, policy servers 44 may give up.


Visited policy server 44a determines a policy output according to the policy rules of the facets, and provides the policy output to visited bearer manager 40a at step 186. The policy output may comprise facets or a policy decision. The method then ends.


Modifications, additions, or omissions may be made to the method without departing from the scope of the invention. The method may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order.



FIG. 4 illustrates an example of a call flow for determining a policy output that may be used by system 10 of FIG. 1. Access terminal 20 sends a SIP invite message to visited bearer manager 40a at step 210. The message uses the visited network address as the care-of address. The message includes Session Data Protocol (SDP) specifying that media streams use the visited network address. This indicates that policies may be exchanged between home network 28 and visited network 24. Visited bearer manager 40a forwards the SIP invite to application manager 56 through home bearer manager 40b at step 214.


Application manager 56 determines a policy associated with the subscriber of access terminal 20 at step 218. The policy may include application facets. For example, an application facet may specify a telephony application with audio and video components. Application manager 56 sends the policy with the facets at step 222.


Home policy server 44b authorizes the policy at step 226. Home policy 44b forwards the policy to visited policy server 44a at step 230. Visited policy server 44a may negotiate the facets with home policy server 44a at step 232. For example, for a video call, visited policy server 44a may inform home policy server 44b that the request may proceed only with audio capabilities, and home policy server 44b may agree. Visited policy server 44a determines policy output for visited bearer manager 40a at step 234. For example, resources are granted for audio, but not for video, capabilities.


Visited policy server 44a sends the policy output to visited bearer manager 40a at step 238. In one embodiment, the policy output may include network facets that bearer manager 40a may implement. In another embodiment, the policy output may include a policy decision such as an authorization to perform the request with only audio capabilities.


Visited bearer manager 40a installs resources according to the network facets at step 242. Visited bearer manager 40a sends an outcome message indicating success at step 246. Visited policy server 44a sends an outcome message indicating that the request was allowed at step 250. Home policy server 44b instructs application manager 56 to proceed at step 254. Application manager 56 forwards the SIP response to access terminal 20 at step 258. The method then ends.


Modifications, additions, or omissions may be made to the method without departing from the scope of the invention. The method may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order.



FIG. 5 illustrates an example of a call flow for implementing a deep packet inspection policy that may be used by system 10 of FIG. 1. Access terminal 20 sends a SIP invite message to visited bearer manager 40a at step 310. Visited bearer manager 40a forwards the SIP invite to application manager 56 at step 314.


Application manager 56 determines a DPI policy associated with the subscriber of access terminal 20 at step 318. The DPI policy includes DPI facets. The facets may, for example, be used to inspect media streams to verify that the streams are sending RTP audio media. A DPI facet may include packet classifiers that specify IP addresses and ports to identify packets to be inspected. Application manager 56 sends the DPI policy with the DPI facets at step 322. Home policy server 44b authorizes the policy at step 326. Home policy server 44b forwards the policy to visited policy server 44a at step 330. Visited policy server 44a determines a policy output that includes the DPI facets at step 334.


Visited policy server 44a sends the DPI facets to visited bearer manager 40a at step 338. In one embodiment, the policy output may include network facets that bearer manager 40a may implement. Visited bearer manager 40a performs deep packet inspection according to the DPI facets at step 242. Visited bearer manager 40a may inspect packets that match the packet classifiers of the DPI facets. The method then ends.


Modifications, additions, or omissions may be made to the method without departing from the scope of the invention. For example, the method may also be applied to access terminal 20 in home network 28. The method may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order.


Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the spirit and scope of this disclosure, as defined by the following claims.

Claims
  • 1. A method for determining a policy output for a communication session, comprising: facilitating registration for an access terminal at a visited network, the access terminal associated with a home network;receiving a policy at a visited policy server of the visited network, the policy received from the home network, the policy comprising one or more facets, the one or more facets comprising an application facet identifying an application deployable in the home network when the access terminal is at the visited network;identifying the application from the application facet;determining, by one or more tangible processors of the visited policy server, that the application is at the home network and that the visited policy server does not support the application;negotiating at least a subset of the one or more facets between the visited policy, server and a home policy server of the home network, wherein negotiating includes determining whether the at least a subset of the one or more facets is compatible with the visited policy server;establishing, by the one or more tangible processors of the visited policy server, the policy output based on the application even though the visited policy server does not support the application; andoutputting one or more instructions using the one or more tangible processors, the instructions instructing the access terminal to tunnel one or more particular packets through the visited network to the home network to allow the home network to apply the application to the particular packets.
  • 2. The method of claim 1, wherein the application facet identifies one or more application parameters.
  • 3. The method of claim 1, wherein establishing the policy output in accordance with the application further comprises: installing at least one facet of the one or more facets on a network element operable to execute the at least one facet.
  • 4. The method of claim 1, wherein establishing the policy output in accordance with the application further comprises: determining a policy decision according to the policy; andsending the policy decision to a network element.
  • 5. The method of claim 1, wherein negotiating at least a subset of the one or more facets between the visited policy server and a home policy server of the home network comprises adjusting at least one facet of the at least a subset of the one or more facets in response to determining that the at least one facet of the at least a subset of the one or more facets is incompatible with the visited policy server.
  • 6. The method of claim 1, wherein at least one facet of the one or more facets further comprises: a packet classifier identifying one or more packets; andan action to be performed in response to detecting the one or more packets.
  • 7. The method of claim 1, wherein the one or more facets further comprise: a network facet requesting one or more network resources for the application.
  • 8. The method of claim 1, wherein the one or more facets further comprise: one or more generic tokens, a generic token understood at the home network and the visited network.
  • 9. A visited policy server of a visited network, comprising: a memory operable to: store a policy; andone or more tangible processors in communication with the memory and operable to: facilitate registration for an access terminal at the visited network, the access terminal associated with a home network;receive the policy from the home network, the policy comprising one or more facets, the one or more facets comprising an application facet identifying an application deployable in the home network;identify the application from the application facet;determine that the application is at the home network and that the visited policy server does not support the application;negotiate at least a subset of the one or more facets between the visited policy server and a home policy server of the home network, wherein negotiating includes determining whether the at least a subset of the one or more facets is compatible with the visited policy server;establish a policy output based on the application even though the visited policy server does not support the application; andprovide an output comprising one or more instructions for the access terminal to tunnel one or more particular packets through the visited network to the home network to allow the home network to apply the application to the particular packets.
  • 10. The visited policy server of claim 9, wherein the application facet identifies one or more application parameters.
  • 11. The visited policy server of claim 9, the processor further operable to establish the policy output in accordance with the application by: installing at least one facet of the one or more facets on a network element operable to execute the at least one facet.
  • 12. The visited policy server of claim 9, the processor further operable to establish the policy output in accordance with the application by: determining a policy decision according to the policy; andsending the policy decision to a network element.
  • 13. The visited policy server of claim 9, wherein negotiating at least a subset of the one or more facets between the visited policy server and a home policy server of the home network comprises adjusting at least one facet of the at least a subset of the one or more facets in response to determining that the at least one facet of the at least a subset of the one or more facets is incompatible with the visited policy, server.
  • 14. The visited policy server of claim 9, wherein at least one facet of the one or more facets further comprises: a packet classifier identifying one or more packets; andan action to be performed in response to detecting the one or more packets.
  • 15. The visited policy server of claim 9, wherein the one or more facets further comprise: a network facet requesting one or more network resources for the application.
  • 16. The visited policy server of claim 9, wherein the one or more facets further comprise: one or more generic tokens, a generic token understood at the home network and the visited network.
  • 17. A non-transitory computer-readable storage medium encoded with logic, the logic operable when executed to: facilitate registration for an access terminal at a visited network, the access terminal associated with a home network;receive a policy at a visited policy server of the visited network, the policy received from the home network, the policy comprising one or more facets, the one or more facets comprising an application facet identifying an application deployable in the home network;identify the application from the application facet;determine that the application is at the home network and that the visited policy server does not support the application;negotiate at least a subset of the one or more facets between the visited policy server and a home policy server of the home network, wherein negotiating includes determining whether the at least a subset of the one or more facets is compatible with the visited policy server;establish a policy output based on the application even though the visited policy server does not support the application; andprovide an output comprising one or more instructions for the access terminal to tunnel one or more particular packets through the visited network to the home network to allow the home network to apply the application to the particular packets.
  • 18. The logic of claim 17, wherein the application facet identifies one or more application parameters.
  • 19. The logic of claim 17, further operable to establish the policy output in accordance with the application by: installing at least one facet of the one or more facets on a network element operable to execute the at least one facet.
  • 20. The logic of claim 17, further operable to establish the policy output in accordance with the application by: determining a policy decision according to the policy; andsending the policy decision to a network element.
  • 21. The logic of claim 17, wherein negotiating at least a subset of the one or more facets between the visited policy server and a home policy server of the home network comprises adjusting at least one facet of the at least a subset of the one or more facets in response to determining that the at least one facet of the at least a subset of the one or more facets is incompatible with the visited policy server.
  • 22. The logic of claim 17, wherein at least one facet of the one or more facets further comprises: a packet classifier identifying one or more packets; andan action to be performed in response to detecting the one or more packets.
  • 23. The logic of claim 17, wherein the one or more facets further comprise: a network facet requesting one or more network resources for the application.
  • 24. The logic of claim 17, wherein the one or more facets further comprise: one or more generic tokens, a generic token understood at the home network and the visited network.
RELATED APPLICATION

This application claims priority under 35 U.S.C. §119(e) of U.S. Provisional Application Ser. No. 60/780,176, entitled “VERIZON WIRELESS MULTI-MEDIA PLUS (MMD+) PROGRAM SYSTEM ARCHITECTURE DOCUMENT,”, filed Mar. 6, 2006, by Flemming Andreasen et al., which is incorporated herein by reference.

US Referenced Citations (190)
Number Name Date Kind
5602907 Hata et al. Feb 1997 A
5822411 Swale et al. Oct 1998 A
5828737 Sawyer Oct 1998 A
5905736 Ronen et al. May 1999 A
5909238 Nagashima et al. Jun 1999 A
5946670 Motohashi et al. Aug 1999 A
5956391 Melen et al. Sep 1999 A
5970477 Roden Oct 1999 A
5987498 Athing et al. Nov 1999 A
6016509 Dedrick Jan 2000 A
6035281 Crosskey et al. Mar 2000 A
6047051 Ginzboorg et al. Apr 2000 A
6070192 Holt et al. May 2000 A
6075854 Copley et al. Jun 2000 A
6131024 Boltz Oct 2000 A
6137791 Frid et al. Oct 2000 A
6141684 McDonald et al. Oct 2000 A
6175879 Shah et al. Jan 2001 B1
6208977 Hernandez et al. Mar 2001 B1
6229887 Albers et al. May 2001 B1
6282573 Darago et al. Aug 2001 B1
6295447 Reichelt et al. Sep 2001 B1
6330562 Boden et al. Dec 2001 B1
6332163 Bowman-Amuah Dec 2001 B1
6339832 Bowman-Amuah Jan 2002 B1
6434568 Bowman-Amuah Aug 2002 B1
6434628 Bowman-Amuah Aug 2002 B1
6438594 Bowman-Amuah Aug 2002 B1
6442748 Bowman-Amuah Aug 2002 B1
6466964 Leung et al. Oct 2002 B1
6477580 Bowman-Amuah Nov 2002 B1
6477665 Bowman-Amuah Nov 2002 B1
6480485 Kari et al. Nov 2002 B1
6490451 Denman et al. Dec 2002 B1
6493547 Raith Dec 2002 B1
6496850 Bowman-Amuah Dec 2002 B1
6502213 Bowman-Amuah Dec 2002 B1
6510513 Danieli Jan 2003 B1
6529909 Bowman-Amuah Mar 2003 B1
6529948 Bowman-Amuah Mar 2003 B1
6539396 Bowman-Amuah Mar 2003 B1
6549949 Bowman-Amuah Apr 2003 B1
6550057 Bowman-Amuah Apr 2003 B1
6571282 Bowman-Amuah May 2003 B1
6578068 Bowman-Amuah Jun 2003 B1
6601192 Bowman-Amuah Jul 2003 B1
6601234 Bowman-Amuah Jul 2003 B1
6606660 Bowman-Amuah Aug 2003 B1
6611821 Stahl et al. Aug 2003 B2
6615199 Bowman-Amuah Sep 2003 B1
6615253 Bowman-Amuah Sep 2003 B1
6615263 Dulai et al. Sep 2003 B2
6621820 Williams et al. Sep 2003 B1
6636242 Bowman-Amuah Oct 2003 B2
6640238 Bowman-Amuah Oct 2003 B1
6640244 Bowman-Amuah Oct 2003 B1
6647262 Demetrescu et al. Nov 2003 B1
6665537 Lioy Dec 2003 B1
6665718 Chuah et al. Dec 2003 B1
6671675 Iwamura Dec 2003 B2
6684243 Euget et al. Jan 2004 B1
6684256 Warrier et al. Jan 2004 B1
6708225 Cho et al. Mar 2004 B1
6714515 Marchand Mar 2004 B1
6715145 Bowman-Amuah Mar 2004 B1
6728266 Sabry et al. Apr 2004 B1
6728365 Li et al. Apr 2004 B1
6728884 Lim Apr 2004 B1
6742015 Bowman-Amuah May 2004 B1
6742036 Das et al. May 2004 B1
6757371 Kim et al. Jun 2004 B2
6760444 Leung Jul 2004 B1
6768726 Dorenbosch et al. Jul 2004 B2
6769000 Akhtar et al. Jul 2004 B1
6771623 Ton Aug 2004 B2
6785256 O'Neill Aug 2004 B2
6804518 Core et al. Oct 2004 B2
6826173 Kung et al. Nov 2004 B1
6829709 Acharya et al. Dec 2004 B1
6834341 Bahl et al. Dec 2004 B1
6839338 Amara et al. Jan 2005 B1
6842906 Bowman-Amuah Jan 2005 B1
6856676 Pirot et al. Feb 2005 B1
6889321 Kung et al. May 2005 B1
6907501 Tariq et al. Jun 2005 B2
6910074 Amin et al. Jun 2005 B1
6915345 Tummala et al. Jul 2005 B1
6917605 Kakemizu et al. Jul 2005 B2
6920503 Nanji et al. Jul 2005 B1
6922404 Narayanan et al. Jul 2005 B1
6925160 Stevens et al. Aug 2005 B1
6947401 El-Malki et al. Sep 2005 B2
6961774 Shannon et al. Nov 2005 B1
6967941 Roy Nov 2005 B2
6978128 Raman et al. Dec 2005 B1
6980802 Jung Dec 2005 B2
6980962 Arganbright et al. Dec 2005 B1
6981047 Hanson et al. Dec 2005 B2
6982967 Leung Jan 2006 B1
6990337 O'Neill et al. Jan 2006 B2
6993333 Laroia et al. Jan 2006 B2
7003294 Singhai et al. Feb 2006 B2
7020697 Goodman et al. Mar 2006 B1
7024687 Chaudhuri et al. Apr 2006 B2
7028311 Roach et al. Apr 2006 B2
7039027 Bridgelall May 2006 B2
7054268 Parantainen et al. May 2006 B1
7079499 Akhtar et al. Jul 2006 B1
7082301 Jagadeesan et al. Jul 2006 B2
7103359 Heinonen et al. Sep 2006 B1
7127234 Ishii Oct 2006 B2
7130286 Koodli et al. Oct 2006 B2
7133386 Holur et al. Nov 2006 B2
7151758 Kumaki et al. Dec 2006 B2
7151772 Kalmanek et al. Dec 2006 B1
7154868 Sharma et al. Dec 2006 B1
7161914 Shoaib et al. Jan 2007 B2
7171555 Salowey et al. Jan 2007 B1
7184418 Baba et al. Feb 2007 B1
7187931 Trossen Mar 2007 B2
7190793 Hsu Mar 2007 B2
7197763 Hsu Mar 2007 B2
7212821 Laroia et May 2007 B2
7213144 Faccin May 2007 B2
7230951 Mizell et al. Jun 2007 B2
7233583 Asthana et al. Jun 2007 B2
7251733 Haverinen et al. Jul 2007 B2
7263371 Das et al. Aug 2007 B2
7269727 Mukherjee et al. Sep 2007 B1
7272122 Trossen et al. Sep 2007 B2
7272123 Wall Sep 2007 B2
7275156 Balfanz et al. Sep 2007 B2
7346340 Purnadi et al. Mar 2008 B2
7389106 Dawson et al. Jun 2008 B2
8185935 Hsu May 2012 B2
20010023428 Miyazaki et al. Sep 2001 A1
20020021681 Madour Feb 2002 A1
20020023174 Garrett et al. Feb 2002 A1
20020036982 Chen Mar 2002 A1
20020059114 Cockrill et al. May 2002 A1
20020091802 Paul et al. Jul 2002 A1
20020138601 Piponius et al. Sep 2002 A1
20020151312 Bos et al. Oct 2002 A1
20030021252 Harper et al. Jan 2003 A1
20030039237 Forslow Feb 2003 A1
20030154400 Pirttimaa et al. Aug 2003 A1
20030187817 Agrawal et al. Oct 2003 A1
20030217165 Buch et al. Nov 2003 A1
20040066764 Koodli et al. Apr 2004 A1
20040114553 Jiang et al. Jun 2004 A1
20040162876 Kohavi Aug 2004 A1
20040162892 Hsu Aug 2004 A1
20040196821 Haddad et al. Oct 2004 A1
20040210524 Benenati et al. Oct 2004 A1
20040259562 Madour Dec 2004 A1
20050002407 Shaheen et al. Jan 2005 A1
20050025132 Harper et al. Feb 2005 A1
20050063352 Amara et al. Mar 2005 A1
20050108531 Swander et al. May 2005 A1
20050130659 Grech et al. Jun 2005 A1
20050147035 Sylvain et al. Jul 2005 A1
20050149651 Doak et al. Jul 2005 A1
20050176428 Gabor et al. Aug 2005 A1
20050195766 Nasielski et al. Sep 2005 A1
20050201324 Zheng Sep 2005 A1
20050213606 Huang et al. Sep 2005 A1
20050220039 Hoshino et al. Oct 2005 A1
20050271003 Devarapalli et al. Dec 2005 A1
20050278420 Hartikainen et al. Dec 2005 A1
20050286709 Horton et al. Dec 2005 A1
20060014547 Walter Jan 2006 A1
20060018272 Mutikainen et al. Jan 2006 A1
20060077924 Rune Apr 2006 A1
20060094423 Sharma et al. May 2006 A1
20060116113 Gass Jun 2006 A1
20060126630 Shirazipour et al. Jun 2006 A1
20060171310 Ahluwalia et al. Aug 2006 A1
20060235973 McBride et al. Oct 2006 A1
20060251038 Tamura et al. Nov 2006 A1
20060264207 Tamura et al. Nov 2006 A1
20060268819 Chen et al. Nov 2006 A1
20070008882 Oran Jan 2007 A1
20070036312 Cai et al. Feb 2007 A1
20070086582 Tai et al. Apr 2007 A1
20070094712 Gibbs et al. Apr 2007 A1
20070121615 Weill et al. May 2007 A1
20070121642 Battin et al. May 2007 A1
20070153720 Baglin et al. Jul 2007 A1
20070254661 Chowdhury Nov 2007 A1
20090219848 Lohmar et al. Sep 2009 A1
Foreign Referenced Citations (5)
Number Date Country
1 250 023 Oct 2002 EP
WO 9826381 Dec 1997 WO
WO 9931610 Dec 1998 WO
WO 03090041 Oct 2003 WO
WO 2005107297 Nov 2005 WO
Non-Patent Literature Citations (68)
Entry
USPTO, Office Action dated Aug. 19, 2008 for U.S. Appl. No. 11/715,073 in the name of Jonathan D. Rosenberg, 22 pages.
USPTO Office Action, U.S. Appl. No. 11/715,073, inventor Rosenberg, 9 pages, Feb. 19, 2010.
Office Action in U.S. Appl. No. 11/715,073, dated May 15, 2009, 12 pages.
USPTO Office Action, U.S. Appl. No. 11/715,073, inventor Rosenberg, 9 pages, Sep. 25, 2009.
PCT Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration with attached PCT International Search Report and Written Opinion of the International Searching Authority in International Application No. PCT/US2006/046800, dated Nov. 10, 2008, 10 pages.
Online Inc., “Apogee Releases Content Usage-Based Billing Product Annotated Title—Software allows content usage-based billing,” EContent, vol. 24, No. 5, NDN 173-0356-6509-7, 1 pg., Jul. 2001.
Centaur Communications, “Secret Bear platform allows paid-for SMS Annotated Title—Secret Bear introduced cross-network reverse billing platform allowing content providers to charge for SMS content,” New Media Age, NDN 173-0354-6130-3, 1 pg., Jun. 28, 2001.
Karsten Lüttge, “E-Charging API: Outsource Charging to a Payment Service Provider,” D-Lib Magazine, NDN 174-0708-0924-8, pp. 216-227, 2001.
A. Herzberg, “Safeguarding Digital Library Contents: Charging for Online Content,” D-Lib Magazine, NDN 174-0590-9051-8, 16 pgs., Jan. 1998.
Business Wire, “Apogee Networks Introduces Industry's First Content Usage-Based Billing Solution for Web Hosters,” NDN 219-0281-6988-1, 2 pgs., May 8, 2001.
Business Wire, “Apogee Networks Announces Investment by Cisco Systems; Combined Efforts Enhance Billing Capabilities for Content Delivery Network Providers,” NDN 219-0220-9035-0, 2 pgs., Jan. 23, 2001.
Business Wire, “Key Analysts Predict Content Billing is the Internet's New Frontier; Content is the Asset of the Industry; Apogee Networks Seen as the Leader in New Internet Industry Space,” NDN 219-0162-6934-6, 3 pgs., Oct. 10, 2000.
Business Wire, “Apogee Networks Unveils NetCountant Wireless Billing At SUPERCOMM; Company Demonstrates Industry First Wireless Content Usage Based Billing Solution,” NDN 218-0324-8075-6, 2 pgs., Jun. 5, 2001.
Business Wire, “Apogee Networks Wins 2000 Communications ASP Product of the Year Award; Apogee Networks' NetCountant Billing Takes Top Honors for Innovative Content Usage Based Billing Solutions,” NDN 218-0282-3757-7, 2 pgs., Mar. 21, 2001.
Business Wire, “Wireless Internet Content Billing and Settlement Capability Announced; Companies Announce Interoperability Between WAP Gateway and Content Billing System,” NDN 218-0220-0997-2, 2 pgs., Dec. 6, 2000.
Business Wire, “Apogee Networks Joins Content Alliance; Billing Expert to Join Industry Group Aimed at Advancing Content Networking,” NDN 218-0181-2716-7, 3 pgs., Oct. 11, 2000.
Business Wire, “Apogee Networks, Inc. And Paysys International, Inc. to Integrate Technologies to Create Advanced IP Content Billing Solutions,” NDN 218-0098-0623-9, 3 pgs., Jun. 19, 2000.
Ylitalo, et al., Re-thinking Security in IP based Micro-Mobility, downloaded from www.tcs.hut.fi/Studies/T-79.5401/2005AUT/ISCO4-Vlitalo-e-al.pdf (12 pages).
PCT Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration with attached PCT International Search Report and Written Opinion of the International Searching Authority in International Application No. PCT/US 07/05937, dated Oct. 25, 2007, 6 pages.
PCT Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration, International Application No. PCT/US07/05849, 9 pages, Nov. 14, 2007.
Draft-TR45-PN-3-4732-RV4 (to be published as TIA-835.1-D), 32 pages.
Draft-TR45-PN-3-4732-RV4 (to be published as TIA-835.2-D), 93 pages.
Draft-TR45-PN-3-4732-RV4 (to be published as TIA-835.3-D), 36 pages.
Draft-TR45-PN-3-4732-RV4 (to be published as TIA-835.4-D), 70 pages.
Draft-TR45-PN-3-4732-RV4 (to be published as TIA-835.5-D), 72 pages.
Draft-TR45-PN-3-4732-RV4 (to be published as TIA-835.6-D), 36 pages.
3GPP2 C.S0067, 3rd Generation Partnership Project 2 ‘3GPP2’, “Generic Key Exchange Protocol for cdma2000 High Rate Packet Data Air Interface,” Version 1.0, 24 pages, Nov. 2005.
3GPP2 X.S0011-001-D, 3rd Generation Partnership Project 2 ‘3GPP2’, “cdma2000 Wireless IP Network Standard: Introduction,” Version 1.0, 33 pages, Feb. 2006.
3GPP2 C.S0063-0, 3rd Generation Partnership Project 2 ‘3GPP2’, “cdma2000 High Rate Packet Data Supplemental,” Version 1.0, 127 pages, Mar. 2006.
3GPP2 A.S0008-A v.1.0, 3rd Generation Partnership Project 2 ‘3GPP2,’ Interoperability Specification (IOS) for High Rate Packet Data (HRPD) Radio Access Network Interfaces with Session Control in the Access Network, 257 pages, Mar. 2006.
3GPP2 C.S0024-A, 3rd Generation Partnership Project 2 ‘3GPP2’, “cdma2000 High Rate Packet Data Air Interface Specification,” Version 2.0, 1,223 pages, Jul. 2005.
B. Aboba, et al., “Extensible Authentication Protocol (EAP),” Network Working Group, RFC 3748, http://www.ietf.org/rfc/rfc3748.txt, 59 pages, Jun. 2004.
B. Aboba, D. Simon, “PPP EAP TLS Authentication Protocol,” Network Working Group, RFC 2716, http://www.ietf.org/rfc/rfc2716.txt, 22 pages, Oct. 1999.
W. Simpson, “PPP Challenge Handshake Authentication Protocol (CHAP),” Network Working Group, RFC 1994, http://www.ietf.org/rfc/rfc1994.txt, 12 pages, Aug. 1996.
W. Simpson, “The Point-to-Point (PPP),” Network Working Group, RFC 1661, http://www.ietf.org/rfc/rfc1661.txt, 47 pages, Jul. 1994.
P. Eronen, et al., “Diameter Extensible Authentication Protocol (EAP) Application,” Network Working Group, RFC 4072, http://www.ietf.org/rfc/rfc4072.txt, 29 pages, Aug. 2005.
P. Calhoun, et al., “Diameter Base Protocol,” Network Working Group, RFC 3588, http://www.ietf.org/rfc/rfc3588.txt, 129 pages, Sep. 2003.
3rd Generation Partnership Project 2 “3GPP2”; “All-IP Core Network Multimedia Domain: Service Based Bearer Control—Stage 2;www.3gpp2.org-”; Version 1.0. Draft Version 0.21.0, 49 pages.
PCT Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration, International Application No. PCT/US07/05847, 9 pages, Oct. 26, 2007.
Yegani et al., “System and Method for Access Authentication in a Mobile Wireless Network,” U.S. Appl. No. 11/419,382, 20 pps, 3 pps drawings, Filed May 19, 2006.
Yegani et al., “System and Method for Handover of an Access Terminal in a Communication Network,” U.S. Appl. No. 11/682,735, 24 pps, 3 pps drawings, Filed Mar. 6, 2007.
Yegani et al., “Enforcement of User Level Policies from Visited Networks in a Mobile IP Environment,” U.S. Appl. No. 11/682,817, 22 pps, 2 pps drawings, Filed Mar. 6, 2007.
Yegani et al, Authentication of Access Terminals in a Cellular Communication Network,: U.S. Appl. No. 11/682,857, 28 pps, 5 pps drawings, Filed Mar. 6, 2007.
Andreasen et al., “System and Method of Consolidating Accounting Data for a Communication Session,” U.S. Appl. No. 11/714,974, 40 pps, 3 pps drawings, Filed Mar. 6, 2007.
Panda et al., “System and Method for Capturing Accounting Data for a Communication Session,” U.S. Appl. No. 11/715,018, filed Mar. 6, 2007.
Rosenberg et al., “System and Method for Determining a Network for Processing Applications for a Communication Session,” U.S. Appl. No. 11/715,019, 40 pps, 3 pps drawings, Filed Mar. 6, 2007.
Leung et al., “Communicating Packets Using a Home Anchored Bearer Path,” U.S. Appl. No. 11/715,033, 33 pps, 4 pps drawings, Filed Mar. 6, 2007.
Andreasen et al., “Posture-Based Network Authentication,” U.S. Appl. No. 11/715,040, 23 pages, 2 pps drawings, Filed Mar. 6, 2007.
Iyer et al., “Access Terminal for Communicating Packets Using a Home Anchored Bearer Path,” U.S. Appl. No. 11/715,041, 33 pps, 4 pps drawings, Filed Mar. 6, 2007.
Rosenberg et al., “System and Method for Exchanging Policy Information in a Roaming Communications Environment,” U.S. Appl. No. 11/715,056, 42 pps, 3 pps drawings, Filed Mar. 6, 2007.
Rosenberg et al., “Establishing Facets of a Policy for a Communication Session,” U.S. Appl. No. 11/715,065, 32 pps, 4 pps drawings, Filed Mar. 6, 2007.
Rosenberg et al., “Performing Deep Packet Inspection for a Communication Session,” U.S. Appl. No. 11/715,073, 31 pps, 4 pps drawings, Filed Mar. 6, 2007.
Rosenberg et al., “Assigning a Serving—CSCF During Access Authentication,” U.S. Appl. No. 11/715,074, 22 pps, 2 pps drawings, Filed Mar. 6, 2007.
Rosenberg et al., “System and Method for Providing Emergency Services in a Visited Communications Environment,” U.S. Appl. No. 11/715,111, 39 pps, 2 pps drawings, Filed Mar. 6, 2007.
Panda et al., “Application-Aware Policy Enforcement,” U.S. Appl. No. 11/715,187, 28 pps, 2 pps drawings, Filed Mar. 6, 2007.
Andreasen et al., “System and Method for Generating a Unified Accounting Record for a Communication Session,”U.S. Appl. No. 11/715,210, 46 pps, 3 pps drawings, Filed Mar. 6, 2007.
Andreasen et al., “Network-triggered quality of service (QoS) Reservation,” U.S. Appl. No. 11/715,250, 21 pps, 2 pps drawings, Filed Mar. 6, 2007.
Andreasen et al.,; “Policy-Based Control of Content Intercept”, U.S. Appl. No. 11/715,251, 23 pps, 2 pps drawings.
Rosenberg et al., “System and Method for Network Charging Using Policy Peering,” U.S. Appl. No. 11/715,256, 43 pps, 3 pps drawings, Filed Mar. 6, 2007.
USPTO Office Action, U.S. Appl. No. 11/715,073, inventor Rosenberg, 8 pages, Jul. 29, 2010.
USPTO Office Action, U.S. Appl. No. 11/715,065, inventor Rosenberg, 11 pages, Jul. 20, 2010.
Supplementary European Search report in EPO Application No. 07752588.9-2416/ 1999618 PCT/US2007005900, dated Aug. 16, 2011, 9 pages, Aug. 16, 2011.
Thi Mai Trang Nguyen et al., COPS-SLS Usage for Dynamic Policy-Based QoS Management over Heterogeneous IP Networks, IEEE Network, May/Jun. 2003, 7 pages.
Thi Mai Trang Nguyen et al., “COPS-SLS: A Service Level Negotiation Protocol for the Internet,” IEEE Communications Magazine, May 2002, 8 pages.
USPTO Final Office Action, U.S. Appl. No. 11/715,073, inventor Rosenberg, 11 pages, mailed Mar. 31, 2011.
USPTO Final Office Action, U.S. Appl. No. 11/715,065, inventor Rosenberg, 12 pages, mailed Dec. 23, 2010.
Jonathan D. Rosenberg USPTO Office Action for U.S. Appl. No. 11/715,073, filed Mar. 6, 2007, mailed Sep. 1, 2011, 12 pages.
U.S. Patent and Trademark Office Official Action dated Sep. 7, 2012, 16 pages, Sep. 7, 2012.
Provisional Applications (1)
Number Date Country
60780176 Mar 2006 US