US20090207843A1 - System and method for providing network address translation control in a network environment - Google Patents

System and method for providing network address translation control in a network environment Download PDF

Info

Publication number
US20090207843A1
US20090207843A1 US12/371,516 US37151609A US2009207843A1 US 20090207843 A1 US20090207843 A1 US 20090207843A1 US 37151609 A US37151609 A US 37151609A US 2009207843 A1 US2009207843 A1 US 2009207843A1
Authority
US
United States
Prior art keywords
flow
network
nat
request
network element
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US12/371,516
Inventor
Flemming S. Andreasen
Frank Brockners
Vojislav Vucetic
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Cisco Technology Inc
Original Assignee
Cisco Technology Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US2917708P priority Critical
Application filed by Cisco Technology Inc filed Critical Cisco Technology Inc
Priority to US12/371,516 priority patent/US20090207843A1/en
Assigned to CISCO TECHNOLOGY, INC. reassignment CISCO TECHNOLOGY, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ANDREASEN, FLEMMING S., VUCETIC, VOJISLAV, BROCKNERS, FRANK
Publication of US20090207843A1 publication Critical patent/US20090207843A1/en
Application status is Abandoned legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24Accounting or billing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/14Metering, charging or billing arrangements specially adapted for data wireline or wireless communications
    • H04L12/1403Architecture for metering, charging or billing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic regulation in packet switching networks
    • H04L47/10Flow control or congestion control
    • H04L47/14Flow control or congestion control in wireless networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic regulation in packet switching networks
    • H04L47/10Flow control or congestion control
    • H04L47/20Policing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements or protocols for real-time communications
    • H04L65/10Signalling, control or architecture
    • H04L65/1013Network architectures, gateways, control or user entities
    • H04L65/1016IMS

Abstract

A method is provided in one example embodiment and includes receiving packets at a network element for a communications flow from an end user, the network element receiving the packets if the flow is initiated through a wireless network and through a wireline network. A network address translation (NAT) binding occurs for the end user at the network element, the NAT binding including an Internet Protocol (IP) address for the end user, the NAT binding being controlled by policy infrastructure coupled to the network element. The network element can be provided along a routing path for the flow (e.g., the IP session), irrespective of whether mobility services are used by the end user. The policy infrastructure can also support NAT control between home and visited networks with the visited network retaining control and privacy over the actual NAT elements being used.

Description

    CLAIMING PRIORITY ON A PROVISIONAL
  • This application claims priority under 35 U.S.C. §119 of provisional application Ser. No. 61/029,177, filed Feb. 15, 2008 and entitled System and Method for Providing Telecommunication and Internet Converged Services and Protocols for Advanced Networking.
  • TECHNICAL FIELD OF THE INVENTION
  • This invention relates in general to the field of communications and, more particularly, to providing network address translation control in a network environment.
  • BACKGROUND OF THE INVENTION
  • Networking architectures have grown increasingly complex in communications environments. In addition, the augmentation of clients or end users wishing to communicate in a network environment has caused many networking configurations and systems to respond by adding elements to accommodate the increase in networking traffic. As the subscriber base of end users increases, proper routing and efficient management of communication sessions and data flows become even more critical.
  • As service providers increasingly move towards fixed-mobile convergence, there is a significant challenge in having a single architecture and associated infrastructure defined that can optimally support wireless and wireline networks.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • To provide a more complete understanding of example embodiments and features and advantages thereof, reference is made to the following description, taken in conjunction with the accompanying figures, wherein like reference numerals represent like parts, in which:
  • FIG. 1 is a simplified block diagram of a communication system in a network environment in accordance with one embodiment;
  • FIG. 2 is a simplified block diagram of an alternative example of the communication system, where roaming occurs in accordance with one embodiment;
  • FIG. 3 is a simplified block diagram of another alternative example of the communication system, where roaming occurs in accordance with one embodiment;
  • FIG. 4 is a simplified flowchart illustrating an example authentication flow in accordance with one embodiment;
  • FIG. 5 is a simplified block diagram of an example implementation, which is illustrative of certain network functions;
  • FIG. 6 is a simplified block diagram of an example implementation for an originating and terminating roaming scenario;
  • FIG. 7 is a simplified block diagram of an example implementation for an originating, roaming, and terminating home scenario;
  • FIG. 8 is a simplified block diagram of an example implementation for an originating home, terminating home network scenario; and
  • FIG. 9 is a simplified block diagram of an example implementation for an originating home, terminating home in the same home network scenario.
  • DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS Overview
  • A method is provided in one example embodiment and includes receiving packets at a network element for a communications flow from an end user, the network element receiving the packets if the flow is initiated through a wireless network and through a wireline network. A network address translation (NAT) binding occurs for the end user at the network element, the NAT binding including an Internet Protocol (IP) address for the end user, the NAT binding being controlled by policy infrastructure coupled to the network element. The network element is provided along a routing path for the flow (e.g., an IP session), irrespective of whether mobility services are used. The policy infrastructure can also support NAT control between home and visited networks with the visited network retaining control and privacy over the actual NAT elements being used. In more specific embodiments, a request is received for the NAT binding and information related to the NAT binding is returned to an entity that initiated the request, the information associated with a port number and an IP version associated with the flow. In still other embodiments, a request for the NAT binding request includes media parameters for a remote source and a destination for the flow. A request for the NAT binding request can also include the port latching for specific terminations for the flow.
  • Turning to FIG. 1, FIG. 1 is a simplified block diagram of a communication system 10 that can provide a unified way of supporting wireless and wireline networks. This particular configuration may be tied to the 3rd Generation Partnership Project (3GPP) Evolved Packet System architecture, but may also be applicable to other environments equally.
  • Note that before proceeding, it is important to identify some of the acronyms that may be used herein in this Specification. These include: Terminal Equipment (TE), Profile Database Function (PDBF), User Access Authentication Function (UAAF), Network Access Control Function (NACF), Customer Network Gateway (CNG), Connectivity Session Location and Repository Function (CSLRF), Access Management Function(AMF), Resource Control Enforcement Function (RCEF), Border Gateway Function (BGF), Interconnect-BGF (I-BGF), Core-BGF (C-BGF), Service Policy Decision Function (SPDF), Proxy Call Session Control Function (PCSCF), Serving Call Session Control Function (SCSCF), User Profile Serving Function (UPSF), Basic Transport Function (BTF), Packet Data Network (PDN), Authentication, Authorization, and Accounting (AAA), Application Function (AF), Home Subscriber Server (HSS), Mobile Access Gateway (MAG), and a Policy and Charging Rules Function (PCRF).
  • Each of the elements of FIG. 1 may couple to one another through simple interfaces (as illustrated) or through any other suitable connection (wired or wireless), which provides a viable pathway for network communications. Additionally, any one or more of these elements may be combined or removed from the architecture based on particular configuration needs.
  • Communication system 10 may include a configuration capable of transmission control protocol/internet protocol (TCP/IP) communications for the transmission or reception of packets in a network. Communication system 10 may also operate in conjunction with a user datagram protocol/IP (UDP/IP) or any other suitable protocol where appropriate and based on particular needs.
  • The example architecture of FIG. 1 includes a TE element 12, a network element 14, a PCRF 18, a PDN gateway 20, a 3GPP AAA server 24, a AAA server 26, a serving gateway 28, an AF 30, an interconnect-BGF 32 [I-BGF], and an HSS 36. Note that many of the functions inherent in these devices are explained in detail below. In terms of the components within network element 14, a MAG function is provided for deployment dependent network-based mobility support. A Foreign Agent (FA) can support client-based MIPv4. An RCEF is also provided, which can be integrated with the C-BGF for non-mobile data, where the deployment tied to NAT support in network element 14. Coupled to network element 14 is AAA server 26, which obtains user profile data. If the user is authorized for mobility, then a Proxy Mobile IP (PMIP) service can be invoked from the MAG (in the case of no local IP). Otherwise, the local IP address assignment can be from a Dynamic Host Configuration Protocol (DHCP) server.
  • Also provided in the architecture of FIG. 1 is the S7a, Rq, Ia interface, which offers an integrated policy control and charging interface for network element 14. This interface can be used to exchange location and access data for one or more end users. Resource and NAT control can be done using DIAMETER (or other suitable protocols), along with location and access network information. For PDN gateway 20, there could be an integrated C-BGF for mobility. PCRF 18 can be enhanced to relay location information, access network information, support NAT/NAT-traversal, Rx+/Gq′-operations, etc. I-BGF 32 can reside between PDNs and alternatively be integrated with other elements within the architecture. For the S9 interface, there is policy peering to support NAT control, location-information, and access network information transfer.
  • In accordance with the techniques and teachings of example embodiments, the tendered system defines a converged and consolidated architecture that covers the requirements provided by both wireless and wireline access networks with further enhancements to cover femto-cells and Wi-Fi access. The Telecommunication and Internet converged Services and Protocols for Advanced Networking (TISPAN) is a body of the European Telecommunication Standards Institute (ETSI). In one example embodiment, the architecture is based on 3GPP Evolved Packet System and the ETSI TISPAN with various functional and interface enhancements.
  • In particular, the proffered architecture provides for a consolidated and enhanced policy infrastructure based on 3GPP Policy and Charging Control (PCC) and ETSI TISPAN, where the PCRF and SPDF functions can be merged and the Access Resource and Admission Control Function (A-RACF) function is kept in a single element (e.g., an edge router). Further policy enhancements involve universal support for location, access network information, and NAT control and definition of network element 14 to include the conditionally invoked evolved packet system (EPS) MAG function, as well as the TISPAN Connectivity Session Location and Repository Function (CLF) and the BGF functions.
  • Note that 3GPP (e.g., Release 8) defines the Evolved Packet System (EPS) as specified in TS 23.401, TS.23.402, TS 23.203, etc. The EPS consists of IP access networks and an Evolved Packet Core (EPC). Access networks may be 3GPP access networks, such a GERAN, UTRAN, and E-UTRAN (LTE) or they may be non-3GPP IP access networks such as eHRPD, DSL, Cable, or the Internet. Non-3GPP IP access networks can be divided into trusted and untrusted segments. Trusted IP access networks support mobility, policy, and AAA interfaces to the EPC, whereas untrusted do not. Instead, access from untrusted networks is done via the evolved Packet Data Gateway (ePDG), which provides for IPSec security associations to the user equipment over the untrusted IP access network. The ePDG in turn supports mobility, policy, and AAA interfaces to the EPC, similar to the trusted IP access networks.
  • The EPC provides several services of general use to IP access networks such as mobility, policy and charging control, authentication and authorization, accounting, lawful Intercept, secure access over untrusted network, etc. 3GPP does not specify any details with respect to the non-3GPP IP access networks and, in particular, 3GPP does not specify any details for wireline IP access networks. ETSI TISPAN has defined a next generation network (NGN) architecture for wireline networks, which addresses many of the same issues the 3GPP EPC is addressing, namely: policy and charging control, authentication and authorization, accounting, and lawful intercept. ETSI TISPAN does not address all the services and features provided by the EPC (e.g. mobility and secure access), but conversely, TISPAN defines a few services and features not covered by the EPC, namely: network address translation (NAT) traversal and location information.
  • As service providers increasingly move toward fixed-mobile convergence, it is desirable to have a single architecture and associated infrastructure defined that can support both wireless and wireline networks. To date, NGN architectures have focused on either the wireless or the wireline side. Although these NGN architectures generally allow both wireless and wireline networks to be supported, they tend to focus on the features required by the primary type of access network they are developed for and, hence, these NGN architectures do not provide a single comprehensive architecture that fully address both wireline and wireless networks.
  • An example embodiment provides a unified architecture with a common core infrastructure that supports both wireline and wireless access networks. This infrastructure includes addressing relevant wireline requirements in the wireless access network portion and relevant wireless requirements in the wireline access network portion. At a high level, the combined architecture provides a single converged policy and charging infrastructure, and a single AAA infrastructure for the wireline and the wireless access network. Mobility services are supported on the wireline side, location information is provided for both the wireline and wireless access networks, and NAT traversal functionality in the form of the ETSI TISPAN BGF functions are provided for the wireless networks as well. [Roaming aspects and peering interface enhancements are also considered and are further detailed below.] Part of the architecture combines functions and interfaces of the 3GPP wireless architecture with elements from the ETSI TISPAN wireline architecture to form a single consolidated architecture that service providers (having both wireline and wireless infrastructure) can use. The architecture provides a unified and single solution to the combined requirements from wireline and wireless.
  • Additionally, the enhanced architecture covers femto-cells and Wi-Fi access points and can potentially use the same interfaces and functional elements as provided by the combined wireless/wireline architecture. In addition, there can be a merger of the 3GPP Policy and Charging Control (PCC) architecture and the ETSI TISPAN policy model, whereby the 3GPP PCRF function incorporates the ETSI TISPAN Service Policy Decision Function (SPDF). The A-RACF function can be placed in an edge element (e.g., network element 14) to align the wireline access network with the wireless access network. The admission control decision can be handled by the PDN gateway (in its capacity as a Policy and Charging Enforcement Function (PCEF)) and/or other elements, but not necessarily the PCRF. This provides for a consistent and distributed policy management solution to all access networks in the architecture. An alternative solution would be to keep the A-RACF with the PCRF, however this may imply inconsistent behavior between the wireless and wireline networks from a PCC point of view. In a general sense, the proffered architecture can offer an evolved broadband network gateway (eBNG) (e.g., network element 14), which includes a mobile access gateway that can be invoked conditionally so that only devices or services that actually need mobility services incur the associated cost and overhead of providing mobility services. Associated with this are:
  • a) Enhancements to both the 3GPP PCC and ETSI TISPAN policy model by universally providing location and access network information on all policy interfaces, and incorporating the TISPAN Connectivity Session Location and Repository Function (CLF) into the eBNG to enable this universal consolidation. This provides for distributed session state management in the wireline access network in a manner that is consistent with the wireless access network.
  • b) Enhancements to the 3GPP PCC architecture to include TISPAN Border Gateway Function (BGF) functionality, and an integrated and consolidated approach to enable BGF control for NAT traversal using the policy infrastructure for both wireless and wireline access.
  • In an example flow, network element 14 can receive packets for a communications flow from an end user, who can conduct the flow through a wireless network and a wireline network. The end user can elect either network option and yet have packets for the flow processed at a single location. More specifically, network element 14 can provide policy control for the end user at a single node in the network. This can include policy-based resource control, which provides mediation between applications and the underlying network layer to intelligently manage network resources (e.g., dynamically and in real time). For operators, policy control is important for delivering a wide variety of high-value services with guaranteed quality of service across fixed, wireless, and cable access technologies. This policy control could further involve resource reservation requests (QoS and bandwidth reservations/allocations) to the appropriate gateway function for a session admission control decision based on defined policies for the subscriber and network resource limits. Then, based on the response received, resources can be assured and bandwidth guaranteed (e.g., on a per session basis).
  • Network element 14 can resolve admission control decisions for the end user in both the wireless network and the wireline network. Subscriber specific policy decisions can be executed by the PCRF (or other elements in FIG. 1), where policy enforcement can one by network element 14. This could include, for example, billing and quality of service (QoS) applications for the end user. Network element 14 can also provide access network information that indicates the type of access network being used by the end user. For example, if an end user is on a DSL connection, then it would be acceptable to allow the end user to download video, but this may not be the case with all access networks.
  • In terms of advantages, such a solution satisfies both the requirements from the wireless and the wireline side by having each side add the missing pieces to the other (e.g., NAT control for wireless and mobility for wireline). It also provides for consistent interfaces and operations to the elements in both the wireless and the wireline access network. Further, such a solution supports these consistent interfaces in both roaming and non-roaming scenarios: some of which are discussed in detail below with reference to FIGS. 2 and 3. The system also supports an efficient and scalable implementation of a converged wireline/wireless architecture by distributing key functions into network elements (and defining the concepts and associated interface enhancements, which support such a distribution).
  • In terms of some of the operational aspects of the proposed architecture, the following features are subsequently detailed: 1) session handling; 2) service insertion; 3) flexible service layer; 4) network address translation (NAT); 5) location information and network attachment sub-system (NASS) bundled authentication; and 6) charging. Turning first to session handling, access session AAA and address assignment can be handled by the AMF in conjunction with the NACF (e.g., the DHCP-server) and the UAAF (e.g., the AAA-Server) with corresponding enforcement functions for authorization data (e.g., the A-RACF and the RCEF). In one example, several access session types are supported (e.g., PPP, IP-Sessions, etc.). In addition, models such as PPP/L2TP model are enabled. The access session establishment also includes distribution of service layer access point/application manager (e.g., proxy-call session control function (P-CSCF) address). Note that the AMF, RCEF, A-RACF, and CLF could be supplied as a single physical device (potentially even including DHCP-Server (NACF)). The configuration could also be simplified to a new gateway function in the converged architecture (e.g., network element 14 of FIG. 1).
  • In one example, the BGF serves as an anchor point for service-layer (e.g., IMS) controlled services in the access/aggregation network. NAT can be used as “anchoring technology,” where traffic to be controlled is directed/routed to the BGF, rather than tunneled to the BGF. In some implementations, not all traffic needs to go through the BGF (e.g., non-service-layer-controlled traffic, multicast traffic, traffic that does not require NAT-traversal operations, etc.). The BGF fulfills additional service layer functions (e.g., service-layer QoS, but is not necessarily involved in endpoint address assignment and authentication). At a concept level, the BGF and the PDN-gateway can fulfill similar roles in the network architecture, though individual functions could differ.
  • In regards to service insertion, multiple service insertion points can be driven by service economics (e.g., aggregation density, bandwidth, session counts, addressing requirements, traffic management (e.g. shaping) requirements, etc.). In such configurations, different PoPs/locations exist for different applications. Note that there is an evolution from one gateway to potentially multiple (i.e., not every packet is required to go through the same gateway). This can result in different service edges/service anchors. TISPAN allows for distributed service control points and even chained service control points, where there are multiple RCEFs and the RCEF placement is not restricted.
  • For the next mechanism, which is the flexible service layer feature, unicast and multicast is equally supported by TISPAN functional elements. The BTF is added in R2 to represent traffic forwarding and the interaction with policy enforcement (e.g., RCEF). TISPAN supports “push” and “pull” models for resource reservation and admission control. In terms of “push,” the connection admission control (CAC) request is originated from the service layer (e.g., P-CSCF originated request during SIP call setup). For “pull,” the CAC request is originated from the transport layer. The request could be originated from a network element within the network. The request could also be originated from the user equipment. There could also be combined models (service layer triggered transport signaling) in TISPAN. The SPDF is not necessarily involved in the pull-mode. For enhanced performance, co-location of the RCEF and the A-RACF on a single device is possible.
  • For the network address translation (NAT) mechanism, NAT on the customer premise equipment (CPE) (called the CNG in TISPAN) is used in wireline deployments. The TE can be deployed behind a routed CNG, where local addressing of the TE is handled by the CNG. NAT traversal can use the application layer gateway (ALG) in the P-CSCF. The NAT could be incorporated into RCEF (i.e., the PCEF), when combined with the C-BGF. Note that S7 has been replaced by Gx and, thus, can be thought of as interchangeable as used herein.
  • For location information and network attachment sub-system (NASS) bundled authentication (NBA), one objective is to support SIP-endpoints that do not necessarily support authentication (SIP-digest) and to provide location information for emergency calls. During registration or call-setup, the P-CSCF can query the access network to retrieve location information on the access session. The P-CSCF inserts the information into SIP P-A-N-I (P-Access-Network-Info) header. Information can be leveraged to skip authentication for the TE (at the SIP-level), or to provide location information in case of an emergency call.
  • Location information and event notification service can be offered via the e2 Interface to the CLF. The CLF represents a database of currently active access sessions: data typically available on a BNG. The CLF does not have an immediate counterpart in 3GPP. NASS services available at the e2 reference point can be provided to the AF and to the Customer Network Gateway Configuration Function (CNGCF).
  • For information query service, the AF can query the access network to receive information on the state of a particular access session. The AF can register to receive a particular event occurring within the access network (e.g., subscriber logs onto the access network). If a particular event occurs, the access network sends a notification message to all AFs, which registered to receive the event.
  • In certain embodiments, the subscriber has a bundled subscription for network access and application/IMS services (e.g., voice). In some instances, the user's handheld does not support IMS authentication procedures. A provider trusts the authentication/authorization of the access session. Once the access session is established, the user can register for application services as well, without additional authentication requirements. For simplicity reasons, the use-case assumes that the access provider trusts the physical line towards the subscriber (i.e., no explicit authentication used in the example). There can be two different user data repositories (AAA databases): one for the access user profile and one for the application user profile. The access provider trusts the physical line towards the subscriber (i.e., no explicit authentication used in the example). Addresses can be assigned using DHCP.
  • Note that in many implementations, the HSS knows the current MME, SGSN, or AAA server, the serving gateway (for 3GPP access), and the PDN gateway. Also, the MME/SGSN knows the initial location information/cell-ID (upon attach or handover), the tracking area, the serving gateway, and PDN gateway. The PCRF knows the initial location information/cell-ID (upon attach or handover) (e.g., provided via S7). The AAA server knows the PDN gateway assigned and [potentially] the initial location information from non-3GPP IP access.
  • In terms of design choices, the AMF, A-RACF, RCEF, and CLF are typically co-located in a single physical platform. For a multi-edge wireline architecture, with multiple A-RACF (where the A-RACF function resides on the network elements), this allows for multiple gateways and, further, allows traffic to bypass the PDN gateway for sessions that do not need its services (i.e., add a direct link from a wireline access at network element 14 of FIG. 1 to the core network). The PCRF and SPDF functionality can also be merged such that the PCRF includes service policy management (network policies), at a single point of contact for policy and control of BGF functions. The subscriber specific application-aware policy decisions can be done by the PCRF.
  • In TISPAN, the user profile information can be handled by the A-RACF and not the SPDF. The PCRF function still includes user profile information, although network element 14 of FIG. 1 can contain the A-RACF functionality (static and application-unaware policies). Resource admission control can be supported in “push” and “pull” mode. “Pull” operations mainly involve A-RACF and RCEF for TISPAN. NAT support is added for both wireless and wireline cases.
  • In one example implementation, the BGF functional concept is a service gateway (service session anchor) and the C-BGF is a superset of the RCEF (i.e., RCEF plus NAT). The C-BGF and RCEF are integrated and are request dependent. For Mobility Services, the C-BGF can be used upstream of the mobility anchor (PDN gateway), where the C-BGF is configured on the PDN gateway as well. Alternatively, the C-BGF function can be kept separate. Also, a separate I-BGF function can be provided for inter-provider peering. Alternatively, the I-BGF function can be part of the PDN gateway. A single consolidated policy and NAT control interface can be used that is DIAMETER based, which enables optimized message flows when the BGF is integrated with the gateway(s). Note that with this flow, as with the others detailed herein, RADIUS, TACACS, and DIAMETER protocols can be implemented or substituted with other protocols that can achieve the intended communications.
  • Note that the TISPAN architecture differentiates devices in the home network. The CNG is usually fixed to an access network, where no mobility is assumed for the CNG. Example embodiments include terminal equipment that is assumed to be mobile. It is desired to do handover between different access networks (e.g., to provide seamless connectivity throughout a house). A routed CNG typically does NAT operations and is generally represented by a single IP address in the access network. Multiple TEs can be “hidden” behind a single IP address. TE addressing can be subscriber controlled (e.g., where the CNG serves as a local DHCP server). One approach is to assume a bridged CNG/CPE for TEs that require mobility. Note that the CNG could be a hybrid (i.e., routed for some services, bridged for others). Alternatively, endpoint MIP support (host-based mobility) could be used.
  • In terms of the C-BGF and I-BGF functions, these represent packet-to-packet gateway elements (e.g., controlled by the SPDF; SPDF may be relaying AF instructions (from service layer)). These elements can also provide usage metering, allocation and translation of IP addresses and port numbers (network address port translation (NAPT)), and interworking between IPv4 and IPv6 networks (NAPT-PT). For the RCEF functions, these may include gate control (open/close gates), packet marking, resource allocation (per flow), policing of uplink/downlink traffic, and transcoding (optional). For C-BGF specific functions, these elements sit at boundaries between the access network and the core network and can offer hosted NAT traversal (latching).
  • For the I-BGF specific functions, these sit at a boundary between core networks and, further, may behave autonomously or under the control of the service layer (e.g., via RACS). The BGF functions can include packet marking, usage metering, and policing functions, which benefit from being provided by the I-BGF in the downlink direction, and the C-BGF in the uplink direction. Hosted NAT traversal can be provided by C-BGF. Functions that can be provided by either the C-BGF or the I-BGF include gate control, IPv4, and IPv6 interworking, transcoding (optional). While the home network can use BGF functions in the visited network (and ask the visited network to use them), the visited network could decide when to actually use these (and which C-BGF and I-BGF) for a flow (e.g., depending on where a flow originates and terminates (which networks)).
  • The CLF in the visited network (e.g., part of network element 14) could convey location information to the home network. The policy peering interface can be used for this. Peering can include the business relationship where ISPs reciprocally provide connectivity to each other's transit customers. The access network information can also easily be provided in this manner. Alternatively, the existing DIAMETER based e2 interface (TISPAN) can be used, however this could require an additional peering interface and infrastructure.
  • As noted earlier, network element 14 of FIG. 1 is enhanced to provide optional mobility and handover support. The MAG function can be added to this network element for network-based mobility (PMIPv6). Also, the MIPv4 foreign agent function is added to the network element for MIPv4 FA CoA operation. The client-based mobile IPv6 can be supported by IPv6 Home Agent (e.g., PDN gateway). The system can also acknowledge a multi-edge wireline architecture with multiple A-RACFs, where the A-RACF function can reside on network elements. The system can allow for multiple gateways and, further, allow traffic to bypass the PDN gateway (i.e., add a direct link from a wireline access network element to the core network) when mobility services are not needed. For network-based mobility, this can be invoked for devices (users) that subscribe to it (otherwise, allocate a non-mobile IP address on the network element). The BGF functionality can be enabled in the visited network to be used by the AF or policy function in the home network. In addition, policy peering can be extended with BGF control.
  • In terms of interfaces in the architecture, for the AF to PCRF interface, there is an Rx+Gq′ harmonization. For policy peering (PCRF to PCRF), the S9 (Gx/Rx and Ri′) interface is enhanced. For policy enforcement and delegation (PCRF to gateway), the S7 and S7a (Gx and Gxa) interface is enhanced. For AAA server peering (the AF/P-CSCF to PCRF), the Rx+Gq′ interface is enhanced.
  • The main additions to the Rx interface include binding information (NAT), latching indication (NAT), authorization lifetime support, IPTV package authorization, location Information transfer, and access network information transfer. In regards to the PCRF to PCRF [S9→S9+NAT+Location+Access S9], the S9 is an evolution of the Gx and/or Rx interface. There is a transfer of PCC information at the service data flow (SDF) level for the local breakout. There is also a transfer of QoS parameters and related packet filters for all other cases. There is also a transfer of control information. For the main additions to the S9 interface, there is NAT control (binding information and latching), transfer of location information, and transfer of access network information.
  • For the PCRF to PDN-gateway [S7→S7+NAT], the S7 interface is based on the Gx interface. There is also a transfer of PCC information at the SDF level and a transfer of access network and location information. The main additions to S7 include NAT control (binding information and latching). For the PCRF to the enhanced PDN gateway, there is an S7a→S7a+NAT+events+location+access. The S7a/b/c interface is based on the Gx interface. There is also a transfer of QoS parameters and related packet filters and a transfer of control information. The additions may include a transfer of network access and location information, location information query/response, and event notification (for P-CSCF interaction optimization for NASS bundled authentication and compatibility with e2). Also included are binding information (NAT) and related addressing information and address latching (NAT).
  • For the PCRF to I-BGF exchanges, there is a new S7d reference point similar to the evolved S7 interface (PCRF-PDN gateway). This can be based on the Gx interface and there is a transfer of PCC information at the SDF level. Also provided is NAT control (binding information and latching). Contrary to S7, there is no need for a transfer of access network and location information.
  • For AAA interactions [Ta* considerations], the Ta* connects the trusted non-3GPP IP access with the 3GPP AAA server/proxy and transports access authentication, authorization, mobility parameters and charging-related information in a secure manner. The Ta* resembles the TISPAN e5 (UAAF to UAAF) reference point from a functional point of view (AAA-proxy interface).
  • Typically, the PCRF may use the subscription information as a basis for the policy and charging control decisions. The subscription information may apply for both session-based and non-session based services. The PCRF can maintain session linking to the sessions where the assigned care of address (CoA) and user equipment (UE) identity (if available over Gxx) are equal. The AF can be an element offering applications that require dynamic policy and/or charging control. The AF can communicate with the PCRF to transfer dynamic session information. The AF may receive an indication that the service information is not accepted by the PCRF together with service information that the PCRF would accept. In that case, the AF can reject the service establishment towards the UE. If possible, the AF forwards the service information to the UE that the PCRF would accept.
  • An AF may communicate with multiple PCRFs. The AF can contact the appropriate PCRF based on either: 1) the end user IP address; and/or 2) a user equipment (UE) identity for which the AF is aware. In case of a private IP address being used for the end user, the AF may send additional PDN information (e.g., PDN ID) over the Rx interface. This PDN information can be used by the PCRF for session binding, and it can be used to help select the correct PCRF. For certain events related to policy control, the AF can be able to give instructions to the PCRF to act on its own. The AF may use bearer level information in the AF session signaling or adjust the bearer level event reporting. The AF may request the PCRF to report on the signaling path status for the AF session. The AF can cancel the request when the AF ceases handling the user.
  • Both network element 14 and PCRF 18 are network elements that facilitate service flows between endpoints and a given network (e.g., for networks such as those illustrated in FIGS. 1-3). As used herein in this Specification, the term ‘network element’ is meant to encompass routers, switches, gateways, bridges, loadbalancers, firewalls, servers, or any other suitable device, component, element, or object operable to exchange information in a network environment. Moreover, these network elements may include any suitable hardware, software, components, modules, interfaces, or objects that facilitate the operations thereof. This may be inclusive of appropriate algorithms and communication protocols that allow for the effective exchange of data or information.
  • In one example implementation, network element 14 is an edge gateway that includes software for achieving some or all of the functionalities outlined herein. Network element 14 may include A-RACF and, further, provide the control and general processing mechanisms as outlined herein. The SPDF, which can reside in PCRF 18, can send instructions to network element 14 (C-BGF) for setting up the NAT traversal. The C-BGF informs the PCRF about the NAT binding to use and the PCRF can tell the AF about this activity. From an enforcement perspective, network element 14 can control those activities. In one example, PCRF 18 is a network element that includes software to achieve the control and general processing mechanisms outlined herein in this document. In other embodiments, this feature may be provided external to the network elements or included in some other network device to achieve these intended functionalities. Alternatively, both network element 14 and PCRF 18 include this software (or reciprocating software) that can coordinate in order to achieve the operations outlined herein. In still other embodiments, one or both of these devices may include any suitable algorithms, hardware, software, components, modules, interfaces, or objects that facilitate the operations thereof.
  • Each of these components (network element 14 and PCRF 18) can also include memory elements for storing information to be used in achieving the control and general processing mechanisms outlined herein. Additionally, each of these devices may include a processor that can execute software (e.g., logic) or an algorithm to perform the activities discussed in this Specification. These components may further keep information in any suitable memory element such as a random access memory (RAM), read only memory (ROM), erasable programmable ROM (EPROM), electronically erasable PROM (EEPROM), application specific integrated circuit (ASIC), software, hardware, or in any other suitable component, device, element, or object where appropriate and based on particular needs.
  • FIG. 2 is a simplified block diagram of an alternative example 50 of communication system 10, where roaming occurs in accordance with one embodiment. This example includes a local breakout for a Home Public Land Mobile Network (HPLMN) for 3GPP and a Visited Public Land Mobile Network (VPLMN) for TISPAN. The architecture further includes a network element 48, a PDN gateway 52, a 3GPP AAA server 54, an AAA Proxy (UAAF) 56, a set of PCRFs 58, 60, an AF 62, and an HSS 64. FIG. 3 is a simplified block diagram of another alternative example 70 of communication system 10, where roaming occurs in a home routed case for one embodiment. The architecture includes a network element 68, a PDN gateway 72, a 3GPP AAA server 74, an AAA Proxy (UAAF) 76, a set of PCRFs 78, 80, an AF 82, and an HSS 84. Note in this example, the PDN gateway has shifted its location.
  • FIG. 4 is a simplified example flow 100 that highlights some of the operational aspects of the proffered architecture. On the 3GPP access side, nominal changes are made, and the focus of this flow is on the wireline segment of the configuration. Consider an example where an end-user initiates a flow and asks for an IP address. This could be in the form of a DHCP request. The authentication can be integrated with DHCP: DHCP-AUTH. Note that for many IP-sessions, DHCP is chosen over PPP because of multiple gateway support (PPP's nature of providing an integrated solution [transport, authentication, etc.] imposes too many restrictions on the architecture). Note that there is a desire to authenticate the end device prior to assigning an IP address. For DHCP-AUTH, a first alternative is based on an existing DHCP message set (it provides PPP such as authorization (PAP/CHAP)). For a second alternative, this supports advanced authentication types (e.g., extensible authentication protocol (EAP)) using an expanded DHCP message set.
  • Returning to the flow of FIG. 4, a number of components are illustrated and they include user equipment (UE)/terminal equipment (TE) 150, a customer premise equipment/customer network gateway (CNG) 160, an access relay function (ARF) element 170 [which could include a switch, DSLAM, etc.], a network element 180, and an AAA server 190. The flow begins at step 102, where a DHCP Discover message is sent from the terminal equipment to network element 180. At step 104, network element 180 returns an ID request to the user equipment. At step 106, the user equipment sends an ID response to network element 180. A number of RADIUS messages are subsequently exchanged at steps 108 and 110. EAP messages are then exchanged in subsequent steps (112 and 114). At steps 116 and 118, RADIUS messages are once again exchanged until there is a success or a failure. Upon EAP success, at step 120, network element 180 returns a response to the user equipment. From this point, normal DHCP operations would continue. At step 122, a DHCP offer is made from network element 180 to the user equipment. At step 124, there is a DHCP request that propagates to network element 180. Finally, at step 124. There is an acknowledged message sent back to the terminal equipment.
  • In regards to example embodiments that offer a visited network BGF control using policy peering, this could involve extending the policy peering interface (e.g., S9) between the home and visited network with a BGF control. In particular, this could involve NAT control. Dynamically created mapping entries (or “bindings”) are typically maintained by a NAT element with a timer. If no packets that use the mapping are received by the NAT within a certain time window, then the binding is removed from the NAT element and the address is returned to a NAT pool. NAT elements can manage address mapping in numerous ways such as outlined herein.
  • From a protocol point of view, the 3GPP S9 interface could include the following example NAT control functionalities (similar to the Gx enhancements proposed herein). The first functionality could involve a request of the NAT binding (two endpoints/terminations, each containing an IP address, port, and IP version) to receive and to transmit the media flows (where information about the allocated bindings could be returned to the requester). The second functionality could indicate, in the NAT binding request, the remote source and destination media parameters for each media flow, including possible wildcarding of specific media parameters (in case the information is not known by the controlling node). The third example functionality could indicate, in the NAT binding request, the IP address/port latching for specific terminations (if the information cannot be retrieved from signaling data, the data is known to be incorrect, etc.).
  • The fourth example functionality could indicate, in the NAT binding request, the media transport protocol (RTP, T.38, MSRP, etc.) for each media flow in order for the BGF to be able to perform protocol specific functions (e.g., dual-port reservation for RTP/RTCP, proper statistics collection, etc.). The fifth example functionality could indicate, in the NAT binding request, if the media flow is uni- or bidirectional (in case of unidirectional, also indicate the specific direction). The sixth example functionality could request mid-session modification of media parameters, including a possible request for new IP address/port latching.
  • Additionally, in certain examples, resource state synchronization features provided by the la interface parts of the S9 interface enhancements could include reporting of the BGF state change (due to rebooting, network failure, hardware failure, etc.), and requesting and reporting of the current BGF resource state. The S9 enhancements enable the policy infrastructure in the home network to communicate with (and control) the BGF functions in the visited network and, in particular, to have the visited network perform NAT control and interconnect using an I-BGF. This can enable the efficient use of a local breakout of traffic in the visited network, while gaining access to services such as v4/v6 translation in the visited network. It can also allow for interconnect scenarios that involve I-BGF elements in the networks, where the users actually are currently. Furthermore, when the users are in the same networks, it allows for bypassing of those (unnecessary) I-BGF elements and usage of the local C-BGF functions.
  • A second example implementation involves selecting a C-BGF and/or I-BGF function to use when the originating and/or terminating user is roaming and a local breakout is being used. The visited network PCRF can control the use and selection of BGF functions in the visited network, which shields the home network from not only which C-BGF and possibly I-BGF is being used, but also whether one, both, or none of these elements will actually be used. The home PCRF can request use of the NAT features from the visited PCRF and the visited PCRF, in turn, decides which C-BGF and/or I-BGF element(s) to use. In the example case where the C-BGF is combined with the access router, optimal C-BGF selection from a routing point of view is simplistic.
  • Fundamentally, the PCRFs can decide whether the originating and terminating users reside in the same network. If they do not, the I-BGF functionality may be invoked in the originating and terminating network (e.g., for a distributed Session Border Controller (SBC), where the I-BGF represents the data path part). If the users reside in the same network, the I-BGF functionality would not be invoked. This problem can be alleviated as follows. First, on the terminating side, the PCRF can examine the IP address information received from the originating side and decide whether the originating and terminating user reside in the same network. If they do, the I-BGF functionality is not used. Otherwise, it is used and the I-BGF selection can be based on the IP addressing information received coupled with the IP routing information. Second, on the originating side, the PCRF does not know where the terminating user resides and, hence, whether to use I-BGF functionality or not for the call (let alone which I-BGF to actually use). The policy exchange can be enhanced between the Application Function (e.g., P-CSCF) and the PCRF with an indication as to whether a single stage exchange is performed, or if a two-stage, policy exchange can be used. In a single stage exchange, it is difficult to change the addressing information provided initially and, hence, an I-BGF can be inserted initially as a cautionary measure.
  • The I-BGF could then be chosen to be close to the user equipment in order to minimize the effect of using it if not ultimately needed. An example use case for this would be a regular Session Initiation Protocol (SIP) setup that does not involve SIP preconditions (i.e., there is a single offer/answer exchange). In a two-stage exchange, it is possible to change the IP addressing information after the first exchange. Once the originating side receives the terminating side IP addressing information, it can follow a similar approach as the terminating side in deciding whether to use an I-BGF, and which I-BGF to select for the call.
  • Example embodiments can offer several advantages such as allowing for local breakout in the visited network while supporting use of hosted NAT functions such as v4/v6 translation services. It can further allow the visited network to completely control whether C-BGF and/or I-BGF is to be used, as well as which BGF elements to actually use. Further, certain embodiments can avoid the need for the home provider network to have to know about the internal BGF structure and elements in the visited network ahead of time. This can enable the visited network to maintain some privacy/confidentiality in terms of how many BGF elements it has, where they reside, and whether they are C-BGFs or I-BGFs. Example arrangements can also enable optimal use of BGF elements by only using them when they are needed. Moreover, example embodiments can enable the AF to assist the PCC infrastructure with deciding whether to use a BGF, rather than being overly cautious and blindly using an I-BGF on the originating side.
  • In regards to the NAT traversal support aspect of example embodiments, on the mobile side, the C-BGF functionality can be added to the PDN GW, where the existing S7/Gx policy interface can be expanded to include the NAT control functions provided by the la interface. There are several advantages to such an implementation. For example, by having the PDN GW and the C-BGF in the same element, use of the NAT functions (e.g., for v4/v6 translation) does not introduce unnatural routing paths since the traffic will traverse the PDN GW. Additionally, with the PDN GW and C-BGF [potentially] in the same element, the number of message interactions can be minimized by providing the policy and NAT control functionality over a single interface.
  • In more specific examples, the DIAMETER-based Gx PCC interface can be extended with the NAT features provided by the la interface. The interface can request (e.g., via NAT binding) [two endpoints/terminations, each containing an IP address, port and IP version] the information outlined above. On the wireline side, the C-BGF can leverage the evolved interfaces defined for the mobile side, where the C-BGF could be included in network element 14. This could include using the same 3GPP Gx/Gxa PCC interface enhanced with the NAT features defined for a combined PDN GW/BGF when mobility services provided by the PDN GW are not used. This provides a similar set of benefits as for the mobile side in terms of avoiding unnatural routing paths and more efficient interactions via a single consolidated interface. Furthermore, from a wireless/wireline converged architecture point of view, there is the benefit of having the same functions and interfaces to the wireline and the wireless access networks.
  • Note that the C-BGF function can be provided on both the wireline side as well as in the PDN GW to allow for routing in the network. Wireline devices that do not use mobility services will not have their traffic traverse the PDN GW. For full convergence, the I-BGF functional element can be introduced. In terms of strategic interfaces, in example embodiments, the same strategy with a single consolidated policy interface (S7d) based on the 3GPP Gx PCC interface, can be employed with enhancements for the NAT features provided by the la interface.
  • In regards to a selective network-based mobility invocation, one example embodiment involves defining network element 14 to include a mobile access gateway (MAG) function (e.g., as defined by PMIPv6). The network element could further include (or be coupled to) a foreign agent [FA]. In one example, the MAG is invoked selectively based on the device requesting an IP address, as opposed to unconditionally for all devices requesting an IP address. Devices that require the IP mobility services can therefore invoke the MAG, which in turn will interact with the PDN gateway (GW) in order to obtain an IP address for the device and, further, establish the IP mobility binding and tunneling with the PDN GW. Devices that do not require IP mobility services will not invoke the MAG and, hence, an IP address will be assigned locally on network element 14, where IP mobility overhead is avoided.
  • The decision as to whether IP mobility services are even needed can be performed in several different ways. For example, network element 14 may interact with an AAA infrastructure (or policy infrastructure) when the device (or user) requests an IP address, and the decision of whether mobility services are required can be based on the authorization data received back from the AAA server (or PCRF). Alternatively, the decision of whether mobility services are required can be based on identifiers derived from the access network (e.g., physical line-ID, NAS-port-ID, etc.). These could be received, for example, via DHCP-Option-82 or through a PPPoE tag. In still other examples, the device itself may indicate whether it requires mobility services. For example, if the device uses DHCP to obtain an IP address, then a DHCP option could be used to indicate whether IP mobility services are needed. If PPP is being used, then a PPP option may be used instead.
  • Other examples, where multiple service gateways are available to the access device over a single layer-2 access domain (e.g., one gateway supports IP-mobility services, while another gateway provides access to the local IPTV service network) and DHCP is used, the DHCP server could send down option-121 information as part of the IP address assignment procedure. This information identifies the IP address ranges, subnets, and next-hop IP gateways for each service to which that user has access. Hence, the access device could select the appropriate exit point/gateway using a routing decision and implicitly decide whether to use a mobility enabled service or not (i.e., using local breakout to access an IPTV service). Note that this scenario assumes that the address of the access device is assigned by the PDN GW, and address-ranges are partitioned as service specific.
  • The approaches outlined above can provide several advantages such as offering a more efficient use of overall network resources, which includes reduced overall usage of the IP mobility infrastructure by only invoking the MAG and PDN GW for devices that truly need and/or can use IP mobility. The architecture also offers less overall bandwidth usage by not routing packets to the PDN GW and by avoiding tunnel overhead between the MAG and PDN GW for devices that do not need IP mobility. It can also offer less delay for devices that do need IP mobility by avoiding routing to the PDN GW (which can serve as the Local Mobility Anchor [LMA]).
  • One assumption in example scenarios is that when the mobile device requests an IP address, it is actually provided by network element 14. This is not automatically the case. In particular, when a Network Address Translator (NAT) is deployed between user equipment and network element 14, then the IP address will be assigned by the NAT instead (e.g., customer network gateway), and network-based IP mobility services for that user equipment will not be invoked. In order to address this and still allow for efficient use of IPv4 addresses provided by the service provider, hybrid NATs could be used. A hybrid NAT can operate in routed mode for some devices and bridged mode for other devices. In routed mode, the NAT assigns a local IP address to the user equipment, whereas in bridged mode, the NAT allows the IP address to be assigned externally. The hybrid NAT can make this determination based on: 1) provisioned device information; and 2) a DHCP option, which informs the hybrid NAT of whether a local (routed mode) or remote (bridged mode) IP address could be assigned. The DHCP option used could be the same as that used by network element 14 to determine whether IP mobility services are needed.
  • An alternative solution to some of these challenges is to use an evolved Packet Data Gateway (ePDG) function. User equipment could establish an IPSec Security Association (possibly through a NAT) with the ePDG, and the ePDG would in turn invoke network-based mobility (PMIPv6) to the PDN GW. This could provide the IP mobility services for that particular user equipment. Such a solution would also work through NATs (provided IPSec is run on top of UDP) and, it would be an easy way to ensure that only devices that need mobility services would get them. In terms of the IPv4, UDP, IPSec ESP, IPv4, and payload issues, in one example implementation the following overhead is incurred: IPv4 header (20 bytes), UDP header (8 bytes), and IPSec ESP (12+bytes) for each packet (40+bytes).
  • FIG. 5 is a simplified block diagram of an example implementation 500, which is illustrative of certain BGF functions. FIG. 5 depicts an access network 502, a core network 504 (along with other core networks 510), where core network 504 includes a C-BGF 506 and an I-BGF 508. The C-BGF and I-BGF elements can function as a packet-to-packet gateway, which can be controlled by the PCRF/SPDF. The PCRF/SPDF may be relaying AF instructions (e.g., from a service layer). Other functions include usage metering for end users, along with allocation and translation activities for IP addresses and port numbers.
  • The RCEF functions can include gate control (open/close gates), packet marking, resource allocation (per flow), policing of uplink/downlink traffic, and transcoding (which may be optional). The C-BGF can sit at the boundary between the access network and the core network and perform hosted NAT Traversal (latching). The I-BGF can sit at a boundary between core networks and, further, it may behave autonomously or under the control of the service layer (via RACS).
  • FIG. 6 is a simplified block diagram of an example implementation 600 for an originating and terminating roaming scenario. In this example, there is a network 610, which includes a number of I-BGF elements, which are located in the home or visited networks. As depicted in the illustrated pathway, the user equipment can access the PDN GWs and I-BGFs, as illustrated in the context of initiating and terminating a communication session. FIG. 7 is a simplified block diagram of an example implementation 700 for an originating, roaming, and terminating home scenario. In this example, there is a network 710, which includes a number of I-BGF elements, which are located in the home or visited networks. As depicted in the illustrated pathway, the user equipment can access the PDN GWs and I-BGFs, as illustrated in the context of initiating a communication session. FIG. 8 is a simplified block diagram of an example implementation 800 for an originating home, terminating home network scenario. In this example, there is a network 810, which includes a number of I-BGF elements, which are located in the home network. As depicted in the illustrated pathway, the user equipment can access the PDN GWs and I-BGFs, as illustrated in the context of initiating and terminating a communication session in the home network. FIG. 9 is a simplified block diagram of an example implementation 900 for an originating home, terminating home in the same home network scenario. In this example, there is a network 910, which includes a number of PDN GWs, which are located in the home network. A home PCRF (h-PCRF) is also illustrated in this example. As depicted in the illustrated pathway, the user equipment can access the PDN GWs and the h-PCRF, as illustrated in the context of initiating and terminating a communication session in the same home network.
  • Note that with the examples provided herein, interaction may be described in terms of two, three, four, or more network elements. However, this has been done for purposes of clarity and example only. In certain cases, it may be easier to describe one or more of the functionalities of a given set of flows by only referencing a limited number of network elements. It should be appreciated that communication system 10 (and its teachings) are readily scalable and can accommodate a large number of components, as well as more complicated or sophisticated arrangements and configurations. Accordingly, the examples provided should not limit the scope or inhibit the broad teachings of communication system 10 as potentially applied to a myriad of other architectures. Note also that the teachings discussed herein can readily be applied to wireless and femto access points and their respective environments.
  • It is also important to note that the steps described with reference to the preceding FIGURES illustrate only some of the possible scenarios that may be executed by, or within, communication system 10. Some of these steps may be deleted or removed where appropriate, or these steps may be modified or changed considerably without departing from the scope of the discussed concepts. In addition, a number of these operations have been described as being executed concurrently with, or in parallel to, one or more additional operations. However, the timing of these operations may be altered considerably. The preceding operational flows have been offered for purposes of example and discussion. Substantial flexibility is provided by communication system 10 in that any suitable arrangements, chronologies, configurations, and timing mechanisms may be provided without departing from the teachings of the discussed concepts.
  • Numerous other changes, substitutions, variations, alterations, and modifications may be ascertained to one skilled in the art and it can be intended that the discussed concept encompass all such changes, substitutions, variations, alterations, and modifications as falling within the scope of the appended claims. In order to assist the United States Patent and Trademark Office (USPTO) and, additionally, any readers of any patent issued on this application in interpreting the claims appended hereto, Applicant wishes to note that the Applicant: (a) does not intend any of the appended claims to invoke paragraph six (6) of 35 U.S.C. section 112 as it exists on the date of the filing hereof unless the words “means for” or “step for” are specifically used in the particular claims; and (b) does not intend, by any statement in the specification, to limit this invention in any way that is not otherwise reflected in the appended claims.

Claims (25)

1. A method, comprising:
receiving packets at a network element for a communications flow from an end user, the network element receiving the packets if the flow is initiated through a wireless network and through a wireline network, wherein a network address translation (NAT) binding occurs for the end user at the network element, the NAT binding including an Internet Protocol (IP) address for the end user.
2. The method of claim 1, further comprising:
reporting a state change associated with a border gateway function that is coupled to the network element.
3. The method of claim 1, further comprising:
reporting resource state information associated with a border gateway function that is coupled to the network element.
4. The method of claim 1, wherein a request is received for the NAT binding where information related to the NAT binding is returned to an entity that initiated the request, the information associated with a port number and an IP version associated with the flow.
5. The method of claim 1, wherein a request for the NAT binding request includes media parameters for a remote source and a destination for the flow.
6. The method of claim 1, wherein a request for the NAT binding request includes port latching for specific terminations for the flow.
7. The method of claim 1, wherein a request for the NAT binding request includes media transport protocol data for the flow, and wherein the media transport protocol data is used to perform dual-port reservations and statistics collection for the flow.
8. The method of claim 1, wherein a request for the NAT binding request includes whether the flow is unidirectional or bidirectional, and wherein if the flow is unidirectional a specific direction is included in the NAT binding request.
9. The method of claim 1, further comprising:
modifying one or more media parameters for the flow once the flow is active, wherein the parameters include a new IP address and new port latching.
10. An apparatus, comprising:
a network element operable to receive packets at a network element for a communications flow from an end user, the network element receiving the packets if the flow is initiated through a wireless network and through a wireline network, wherein a network address translation (NAT) binding occurs for the end user at the network element, the NAT binding including an Internet Protocol (IP) address for the end user, the network element being provided along a routing path for the flow regardless of whether mobility services are used by the end user.
11. The apparatus of claim 10, wherein a request is received for the NAT binding where information related to the NAT binding is returned to an entity that initiated the request, the information associated with a port number and an IP version associated with the flow.
12. The apparatus of claim 10, wherein a request for the NAT binding request includes media parameters for a remote source and a destination for the flow.
13. The apparatus of claim 10, wherein a request for the NAT binding request includes port latching for specific terminations for the flow.
14. The apparatus of claim 10, wherein a request for the NAT binding request includes media transport protocol data for the flow, and wherein the media transport protocol data is used to perform dual-port reservations and statistics collection for the flow.
15. The apparatus of claim 10, wherein a request for the NAT binding request includes whether the flow is unidirectional or bidirectional, and wherein if the flow is unidirectional a specific direction is included in the NAT biding request.
16. Logic encoded in one or more tangible media for execution and when executed by a processor operable to:
receive packets for a communications flow from an end user at a network element, the network element receiving the packets if the flow is initiated through a wireless network and through a wireline network, wherein a network address translation (NAT) binding occurs for the end user at the network element, the NAT binding including an Internet Protocol (IP) address for the end user, the network element being provided along a routing path for the flow regardless of whether mobility services are used by the end user.
17. The logic of claim 16, wherein the code is further operable to:
report a state change associated with a border gateway function element that is coupled to the network element.
18. The logic of claim 16, wherein the code is further operable to:
report resource state information associated with a border gateway function element that is coupled to the network element.
19. The logic of claim 16, wherein a request is received for the NAT binding and information related to the NAT binding is returned to an entity that initiated the request, the information associated with a port number and an IP version associated with the flow.
20. The logic of claim 16, wherein a request for the NAT binding request includes media parameters for a remote source and a destination for the flow.
21. A system, comprising:
means for receiving packets for a communications flow from an end user at an interface of a network element, the network element receiving the packets if the flow is initiated through a wireless network and through a wireline network; and
means for executing a network address translation (NAT) binding for the end user at the network element, the NAT binding including an Internet Protocol (IP) address for the end user.
22. The system of claim 21, wherein a request is received for the NAT binding and information related to the NAT binding is returned to an entity that initiated the request, the information associated with a port number and an IP version associated with the flow.
23. The system of claim 21, wherein a request for the NAT binding request includes media parameters for a remote source and a destination for the flow.
24. The system of claim 21, wherein a request for the NAT binding request includes port latching for specific terminations for the flow.
25. The system of claim 21, wherein a request for the NAT binding request includes media transport protocol data for the flow, and wherein the media transport protocol data is used to perform dual-port reservations and statistics collection for the flow.
US12/371,516 2008-02-15 2009-02-13 System and method for providing network address translation control in a network environment Abandoned US20090207843A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US2917708P true 2008-02-15 2008-02-15
US12/371,516 US20090207843A1 (en) 2008-02-15 2009-02-13 System and method for providing network address translation control in a network environment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US12/371,516 US20090207843A1 (en) 2008-02-15 2009-02-13 System and method for providing network address translation control in a network environment

Publications (1)

Publication Number Publication Date
US20090207843A1 true US20090207843A1 (en) 2009-08-20

Family

ID=40955020

Family Applications (5)

Application Number Title Priority Date Filing Date
US12/371,524 Abandoned US20090207759A1 (en) 2008-02-15 2009-02-13 System and method for providing a converged wireline and wireless network environment
US12/371,511 Active 2030-06-24 US8942112B2 (en) 2008-02-15 2009-02-13 System and method for providing selective mobility invocation in a network environment
US12/371,509 Active US7899039B2 (en) 2008-02-15 2009-02-13 System and method for providing location and access network information support in a network environment
US12/371,516 Abandoned US20090207843A1 (en) 2008-02-15 2009-02-13 System and method for providing network address translation control in a network environment
US12/987,311 Active 2030-07-28 US8711847B2 (en) 2008-02-15 2011-01-10 System and method for providing location and access network information support in a network environment

Family Applications Before (3)

Application Number Title Priority Date Filing Date
US12/371,524 Abandoned US20090207759A1 (en) 2008-02-15 2009-02-13 System and method for providing a converged wireline and wireless network environment
US12/371,511 Active 2030-06-24 US8942112B2 (en) 2008-02-15 2009-02-13 System and method for providing selective mobility invocation in a network environment
US12/371,509 Active US7899039B2 (en) 2008-02-15 2009-02-13 System and method for providing location and access network information support in a network environment

Family Applications After (1)

Application Number Title Priority Date Filing Date
US12/987,311 Active 2030-07-28 US8711847B2 (en) 2008-02-15 2011-01-10 System and method for providing location and access network information support in a network environment

Country Status (1)

Country Link
US (5) US20090207759A1 (en)

Cited By (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090207759A1 (en) * 2008-02-15 2009-08-20 Andreasen Flemming S System and method for providing a converged wireline and wireless network environment
US20090303924A1 (en) * 2008-06-10 2009-12-10 Nokia Siemens Networks Oy Packet data network selection
US20090303973A1 (en) * 2008-06-10 2009-12-10 Nokia Siemens Networks Oy Packet data network selection
US20090313378A1 (en) * 2008-08-06 2009-12-17 Futurewei Technologies, Inc. Remote Media IMS Sessions
US20100290086A1 (en) * 1998-01-19 2010-11-18 Brother Kogyo Kabushiki Kaisha Network System, Terminal and Recording Medium
US8195778B1 (en) 2009-12-19 2012-06-05 Cisco Technology, Inc. System and method for providing mobility across access technologies in a network environment
US20130007286A1 (en) * 2011-06-29 2013-01-03 Juniper Networks, Inc. User session routing between mobile network gateways
US20130016677A1 (en) * 2010-03-05 2013-01-17 Nec Europe Ltd. Method for operating a network and a network
US20130272163A1 (en) * 2012-04-13 2013-10-17 Zu Qiang Non-seamless offload indicator
US20130346629A1 (en) * 2012-06-26 2013-12-26 Cisco Technology, Inc. Determining the type of upstream network address translation from a home gateway
US8650279B2 (en) 2011-06-29 2014-02-11 Juniper Networks, Inc. Mobile gateway having decentralized control plane for anchoring subscriber sessions
US20140204947A1 (en) * 2010-11-29 2014-07-24 Telefonaktiebolaget L M Ericsson (Publ) Identification of a private device in a public network
US20140269740A1 (en) * 2011-02-01 2014-09-18 Telefonaktiebolaget L M Ericsson (Publ) Method for pcc support for scenarios with nat in the gw
US20140351590A1 (en) * 2013-05-23 2014-11-27 Sercomm Corporation Network device, ipsec system and method for establishing ipsec tunnel using the same
US9215588B2 (en) 2010-04-30 2015-12-15 Cisco Technology, Inc. System and method for providing selective bearer security in a network environment
EP2654262A3 (en) * 2012-04-18 2016-09-14 Telefonaktiebolaget LM Ericsson (publ) Media plane optimization for voice over LTE
US20160344664A1 (en) * 2015-05-22 2016-11-24 Qualcomm Innovation Center, Inc. Direct client-to-client internet relay chat for softap clients
US9635581B2 (en) * 2008-11-21 2017-04-25 At&T Intellectual Property I, L.P. Femtocell local breakout mechanisms

Families Citing this family (113)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101399699B (en) 2007-09-30 2011-10-05 华为技术有限公司 Addressing method, network element device and network system for policy determination functional entity
BRPI0822731A2 (en) * 2008-05-30 2015-07-14 Alcatel Lucent Usa Inc Online upload architecture in lte / epc communication networks
US9565707B2 (en) 2009-01-28 2017-02-07 Headwater Partners I Llc Wireless end-user device with wireless data attribution to multiple personas
US9647918B2 (en) 2009-01-28 2017-05-09 Headwater Research Llc Mobile device and method attributing media services network usage to requesting application
US9270559B2 (en) 2009-01-28 2016-02-23 Headwater Partners I Llc Service policy implementation for an end-user device having a control application or a proxy agent for routing an application traffic flow
US9351193B2 (en) 2009-01-28 2016-05-24 Headwater Partners I Llc Intermediate networking devices
US8793758B2 (en) 2009-01-28 2014-07-29 Headwater Partners I Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US9557889B2 (en) 2009-01-28 2017-01-31 Headwater Partners I Llc Service plan design, user interfaces, application programming interfaces, and device management
US9980146B2 (en) 2009-01-28 2018-05-22 Headwater Research Llc Communications device with secure data path processing agents
US8745191B2 (en) 2009-01-28 2014-06-03 Headwater Partners I Llc System and method for providing user notifications
US9755842B2 (en) 2009-01-28 2017-09-05 Headwater Research Llc Managing service user discovery and service launch object placement on a device
US9609510B2 (en) 2009-01-28 2017-03-28 Headwater Research Llc Automated credential porting for mobile devices
US10057775B2 (en) 2009-01-28 2018-08-21 Headwater Research Llc Virtualized policy and charging system
US9955332B2 (en) 2009-01-28 2018-04-24 Headwater Research Llc Method for child wireless device activation to subscriber account of a master wireless device
US9858559B2 (en) 2009-01-28 2018-01-02 Headwater Research Llc Network service plan design
US9578182B2 (en) 2009-01-28 2017-02-21 Headwater Partners I Llc Mobile device and service management
US9571559B2 (en) 2009-01-28 2017-02-14 Headwater Partners I Llc Enhanced curfew and protection associated with a device group
US8577998B2 (en) * 2008-07-08 2013-11-05 Cisco Technology, Inc. Systems and methods of detecting non-colocated subscriber devices
CN101677437B (en) * 2008-09-18 2012-02-29 华为技术有限公司 Method and system for implementing strategy and charge control under scene of multi-grouping data network
US8359644B2 (en) 2008-11-17 2013-01-22 At&T Intellectual Property I, L.P. Seamless data networking
WO2010081554A1 (en) * 2009-01-15 2010-07-22 Telefonaktiebolaget Lm Ericsson (Publ) PROXY MOBILE IPv6 SUPPORT IN RESIDENTIAL NETWORKS
US8340634B2 (en) 2009-01-28 2012-12-25 Headwater Partners I, Llc Enhanced roaming services and converged carrier networks with device assisted services and a proxy
US8548428B2 (en) 2009-01-28 2013-10-01 Headwater Partners I Llc Device group partitions and settlement platform
US8275830B2 (en) 2009-01-28 2012-09-25 Headwater Partners I Llc Device assisted CDR creation, aggregation, mediation and billing
US8589541B2 (en) 2009-01-28 2013-11-19 Headwater Partners I Llc Device-assisted services for protecting network capacity
US8406748B2 (en) 2009-01-28 2013-03-26 Headwater Partners I Llc Adaptive ambient services
US9392462B2 (en) 2009-01-28 2016-07-12 Headwater Partners I Llc Mobile end-user device with agent limiting wireless data communication for specified background applications based on a stored policy
US9954975B2 (en) 2009-01-28 2018-04-24 Headwater Research Llc Enhanced curfew and protection associated with a device group
US10248996B2 (en) 2009-01-28 2019-04-02 Headwater Research Llc Method for operating a wireless end-user device mobile payment agent
US8391834B2 (en) * 2009-01-28 2013-03-05 Headwater Partners I Llc Security techniques for device assisted services
US9706061B2 (en) 2009-01-28 2017-07-11 Headwater Partners I Llc Service design center for device assisted services
US8635335B2 (en) 2009-01-28 2014-01-21 Headwater Partners I Llc System and method for wireless network offloading
US8346225B2 (en) 2009-01-28 2013-01-01 Headwater Partners I, Llc Quality of service for device assisted services
US8402111B2 (en) 2009-01-28 2013-03-19 Headwater Partners I, Llc Device assisted services install
US9253663B2 (en) 2009-01-28 2016-02-02 Headwater Partners I Llc Controlling mobile device communications on a roaming network based on device state
US9572019B2 (en) 2009-01-28 2017-02-14 Headwater Partners LLC Service selection set published to device agent with on-device service selection
US10264138B2 (en) 2009-01-28 2019-04-16 Headwater Research Llc Mobile device and service management
US10237757B2 (en) 2009-01-28 2019-03-19 Headwater Research Llc System and method for wireless network offloading
US10064055B2 (en) 2009-01-28 2018-08-28 Headwater Research Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US10200541B2 (en) 2009-01-28 2019-02-05 Headwater Research Llc Wireless end-user device with divided user space/kernel space traffic policy system
US8626115B2 (en) 2009-01-28 2014-01-07 Headwater Partners I Llc Wireless network service interfaces
US20100188993A1 (en) 2009-01-28 2010-07-29 Gregory G. Raleigh Network tools for analysis, design, testing, and production of services
US10326800B2 (en) 2009-01-28 2019-06-18 Headwater Research Llc Wireless network service interfaces
US8832777B2 (en) 2009-03-02 2014-09-09 Headwater Partners I Llc Adapting network policies based on device service processor configuration
US8331384B2 (en) * 2009-05-12 2012-12-11 Cisco Technology, Inc. System and method for femto coverage in a wireless network
EP2454846B1 (en) * 2009-07-17 2018-02-28 Koninklijke KPN N.V. Information transmission in a machine-to-machine telecommunications network
US8743696B2 (en) * 2009-08-07 2014-06-03 Cisco Technology, Inc. Mobile transport solution for offloading to an alternate network
US8693367B2 (en) * 2009-09-26 2014-04-08 Cisco Technology, Inc. Providing offloads in a communication network
CN102045680B (en) * 2009-10-13 2013-08-21 中兴通讯股份有限公司 Method and system for realizing policy control based on position information
US9015318B1 (en) 2009-11-18 2015-04-21 Cisco Technology, Inc. System and method for inspecting domain name system flows in a network environment
US9009293B2 (en) 2009-11-18 2015-04-14 Cisco Technology, Inc. System and method for reporting packet characteristics in a network environment
US9148380B2 (en) 2009-11-23 2015-09-29 Cisco Technology, Inc. System and method for providing a sequence numbering mechanism in a network environment
KR101478418B1 (en) 2009-12-04 2014-12-31 인터디지탈 패튼 홀딩스, 인크 Extended local ip access for a converged gateway in a hybrid network
US8792495B1 (en) 2009-12-19 2014-07-29 Cisco Technology, Inc. System and method for managing out of order packets in a network environment
US20110176486A1 (en) * 2010-01-19 2011-07-21 Futurewei Technologies, Inc. System and Method for Reporting Trusted Access Network Information
CN101969627B (en) * 2010-04-21 2013-06-12 中兴通讯股份有限公司 Method and system for realizing service continuity of single-standby terminal
CN102244899B (en) * 2010-05-13 2015-08-12 中兴通讯股份有限公司 A data access network to the Internet access method and apparatus offload
FR2961647B1 (en) * 2010-06-16 2014-09-05 Actility Method for managing an object using a management bridge using a telecommunications network
WO2011162644A1 (en) * 2010-06-21 2011-12-29 Telefonaktiebolaget L M Ericsson (Publ) Methods and apparatuses for handling time zone information in an internet protocol multimedia subsystem, ims, network
CN102340757B (en) * 2010-07-23 2015-08-12 中兴通讯股份有限公司 One strategy control method and system
US20120030331A1 (en) * 2010-07-30 2012-02-02 Interdigital Patent Holdings, Inc. Method and apparatus for managing and processing policy profile restrictions
JP5356331B2 (en) * 2010-08-04 2013-12-04 株式会社エヌ・ティ・ティ・ドコモ Mobile communication method and priority control node
US20120195196A1 (en) * 2010-08-11 2012-08-02 Rajat Ghai SYSTEM AND METHOD FOR QoS CONTROL OF IP FLOWS IN MOBILE NETWORKS
CN102378280B (en) * 2010-08-12 2015-01-28 中兴通讯股份有限公司 Policy control method and system for realizing BBF (Broadband Forum) access
US20120054323A1 (en) * 2010-08-30 2012-03-01 Microsoft Corporation Regulating media quality using a session bandwidth limit
US8396976B2 (en) 2010-08-31 2013-03-12 Microsoft Corporation Admitting calls based on endpoint locations
US8787303B2 (en) 2010-10-05 2014-07-22 Cisco Technology, Inc. Methods and apparatus for data traffic offloading at a router
WO2012048753A1 (en) * 2010-10-15 2012-04-19 Nokia Siemens Networks Oy Connection control with b2bua located behind nat gateway
US9565117B2 (en) 2010-12-22 2017-02-07 Cisco Technology, Inc. Adaptive intelligent routing in a communication system
US8509148B2 (en) * 2010-12-29 2013-08-13 Industrial Technology Research Institute System and method for application layer gateway assisted local IP access at a femto base station by network address translation
US8477730B2 (en) 2011-01-04 2013-07-02 Cisco Technology, Inc. Distributed load management on network devices
US9003057B2 (en) 2011-01-04 2015-04-07 Cisco Technology, Inc. System and method for exchanging information in a mobile wireless network environment
EP2664192B1 (en) * 2011-01-13 2016-06-15 Telefonaktiebolaget LM Ericsson (publ) Roaming control for ims apn
CN102647700B (en) * 2011-02-22 2016-03-02 阿尔卡特朗讯 A method for obtaining and using location information method and apparatus
US9071611B2 (en) 2011-02-23 2015-06-30 Cisco Technology, Inc. Integration of network admission control functions in network access devices
US9084281B2 (en) * 2011-03-30 2015-07-14 Dexi Lu Open wireless architecture (OWA) mobile cloud infrastructure and method
US9479890B2 (en) * 2012-07-31 2016-10-25 Michael Lu Open wireless architecture (OWA) mobile cloud infrastructure and method
US8948013B1 (en) 2011-06-14 2015-02-03 Cisco Technology, Inc. Selective packet sequence acceleration in a network environment
US8737221B1 (en) 2011-06-14 2014-05-27 Cisco Technology, Inc. Accelerated processing of aggregate data flows in a network environment
US8743690B1 (en) 2011-06-14 2014-06-03 Cisco Technology, Inc. Selective packet sequence acceleration in a network environment
US8792353B1 (en) 2011-06-14 2014-07-29 Cisco Technology, Inc. Preserving sequencing during selective packet acceleration in a network environment
JP5760736B2 (en) * 2011-06-22 2015-08-12 富士通株式会社 communication device
CN102857892B (en) * 2011-07-01 2018-09-25 南京中兴新软件有限责任公司 Urgent call cut-in method and system
CN102905390B (en) * 2011-07-26 2017-12-01 中兴通讯股份有限公司 Session association methods, devices and systems
US9319938B2 (en) 2011-08-05 2016-04-19 Lg Electronics Inc. Inter-APN routing flow distribution
CN102932767B (en) * 2011-08-11 2017-02-01 中兴通讯股份有限公司 Information transmission method, packet data network gateway as well as policy and charging rules function
WO2013027124A1 (en) 2011-08-22 2013-02-28 Telefonaktiebolaget L M Ericsson (Publ) Virtual access point using single service set identifiers
US8942088B2 (en) * 2011-10-07 2015-01-27 Telefonaktiebolaget L M Ericsson (Publ) BNG to PCRF mediation entity for BBF and 3GPP access interworking
US9066284B2 (en) 2011-10-14 2015-06-23 Microsoft Technology Licensing, Llc System, method and device for call policy enforcement and routing based on user location
US9906887B2 (en) * 2011-10-18 2018-02-27 Alcatel Lucent PCRN home network identity
KR20130070308A (en) 2011-12-19 2013-06-27 삼성전자주식회사 Method and apparatus for dynamic policy interworking between pcrf and nat
CN103297353A (en) * 2012-02-22 2013-09-11 华为技术有限公司 Access method and system of customer premise equipment and broadband network gateway
US10123368B2 (en) 2012-02-23 2018-11-06 Cisco Technology, Inc. Systems and methods for supporting multiple access point names for trusted wireless local area network
US20130252578A1 (en) * 2012-03-22 2013-09-26 Zte (Usa) Inc. Single operator managed policy and charging function for fixed mobile convergence networks
CN103379512A (en) * 2012-04-20 2013-10-30 中兴通讯股份有限公司 WLAN network user strategy distribution device and method
TW201409986A (en) * 2012-06-04 2014-03-01 Interdigital Patent Holdings Lawful interception for local selected IP traffic offload and local IP access performed at a non-core gateway
US9336501B2 (en) 2012-10-25 2016-05-10 Motorola Solutions, Inc. Method and apparatus for supporting cross jurisdictional mutual aid requests
CN108235270A (en) * 2013-01-22 2018-06-29 华为技术有限公司 A kind of method, counting equipment and system for carrying out strategic decision-making
US9986103B2 (en) * 2013-05-17 2018-05-29 Telefonaktiebolaget Lm Ericsson (Publ) Advanced policy and charging control methods, network nodes and computer programs for sponsored data connectivity by peers
CN104254071B (en) * 2013-06-28 2017-12-15 中国电信股份有限公司 PCC control methods and system in eHRPD network
US9479298B2 (en) 2013-07-08 2016-10-25 Intel IP Corporation Demodulation reference signals (DMRS)for side information for interference cancellation
US9838858B2 (en) 2014-07-08 2017-12-05 Rapidsos, Inc. System and method for call management
WO2016044540A1 (en) 2014-09-19 2016-03-24 Rapidsos, Inc. Method and system for emergency call management
JP6510062B2 (en) * 2015-03-27 2019-05-08 インテル アイピー コーポレイション Location Information for Voice Emergency Call on WLAN
WO2017008004A1 (en) * 2015-07-08 2017-01-12 Convida Wireless, Llc Service layer anycast and somecast
JP2018538645A (en) 2015-11-02 2018-12-27 ラピッドエスオーエス,インク. Method and system for situational awareness for emergency response
US9736670B2 (en) 2015-12-17 2017-08-15 Rapidsos, Inc. Devices and methods for efficient emergency calling
WO2017112820A1 (en) * 2015-12-22 2017-06-29 Rapidsos, Inc. Systems and methods for robust and persistent emergency communications
US9986404B2 (en) 2016-02-26 2018-05-29 Rapidsos, Inc. Systems and methods for emergency communications amongst groups of devices based on shared data
EP3449653A4 (en) 2016-04-26 2019-09-18 Rapidsos Inc Systems and methods for emergency communications
CN109716358A (en) * 2016-12-30 2019-05-03 同济大学 A method of using WI-FI probe in detecting pedestrian's flow
US10375558B2 (en) 2017-04-24 2019-08-06 Rapidsos, Inc. Modular emergency communication flow management system
US10305774B2 (en) 2017-06-05 2019-05-28 At&T Mobility Ii Llc Enhanced U-verse / DSL internet services

Citations (98)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US57458A (en) * 1866-08-28 Improvement in horse-collars
US67417A (en) * 1867-08-06 Improvement in pump-pistons
US165145A (en) * 1875-06-29 Improvement in compounds for preserving beer
US307487A (en) * 1884-11-04 moore
US5403567A (en) * 1989-12-05 1995-04-04 Smith; James W. Dual impeller method and apparatus for effecting chemical conversion
US6181935B1 (en) * 1996-09-27 2001-01-30 Software.Com, Inc. Mobility extended telephone application programming interface and method of use
US20030091013A1 (en) * 2001-11-07 2003-05-15 Samsung Electronics Co., Ltd. Authentication method between mobile node and home agent in a wireless communication system
US6587882B1 (en) * 1997-08-01 2003-07-01 Kabushiki Kaisha Toshiba Mobile IP communication scheme using visited site or nearby network as temporal home network
US6603761B1 (en) * 1999-09-17 2003-08-05 Lucent Technologies Inc. Using internet and internet protocols to bypass PSTN, GSM map, and ANSI-41 networks for wireless telephone call delivery
US20040003241A1 (en) * 2002-06-27 2004-01-01 Nokia, Inc. Authentication of remotely originating network messages
US20040008627A1 (en) * 2002-07-12 2004-01-15 Sachin Garg Method and apparatus for performing admission control in a communication network
US20040077341A1 (en) * 2002-10-17 2004-04-22 Chandranmenon Girish P. Multi-interface mobility client
US20040213260A1 (en) * 2003-04-28 2004-10-28 Cisco Technology, Inc. Methods and apparatus for securing proxy Mobile IP
US20040219905A1 (en) * 2003-05-02 2004-11-04 Steven Blumenthal Authentication of mobile devices via proxy device
US20040225895A1 (en) * 2003-05-05 2004-11-11 Lucent Technologies Inc. Method and apparatus for providing adaptive VPN to enable different security levels in virtual private networks (VPNs)
US6910074B1 (en) * 2000-07-24 2005-06-21 Nortel Networks Limited System and method for service session management in an IP centric distributed network
US20050135375A1 (en) * 2003-12-19 2005-06-23 Nokia Corporation Control decisions in a communication system
US20050159181A1 (en) * 2004-01-20 2005-07-21 Lucent Technologies Inc. Method and apparatus for interconnecting wireless and wireline networks
US6934274B2 (en) * 1998-02-20 2005-08-23 Kabushiki Kaisha Toshiba Mobile IP communication scheme using dynamic address allocation protocol
US6937597B1 (en) * 1999-02-26 2005-08-30 Lucent Technologies Inc. Signaling method for internet telephony
US20050238002A1 (en) * 2003-02-10 2005-10-27 Rasanen Juha A Mobile network having IP multimedia subsystem (IMS) entities and solutions for providing simplification of operations and compatibility between different IMS entities
US6970909B2 (en) * 2001-10-11 2005-11-29 The Trustees Of Columbia University In The City Of New York Multi-protocol data communication system supporting wireless telephony and content delivery
US20050278532A1 (en) * 2004-05-28 2005-12-15 Zhi Fu Method and apparatus for mutual authentication at handoff in a mobile wireless communication network
US20060041761A1 (en) * 2004-08-17 2006-02-23 Neumann William C System for secure computing using defense-in-depth architecture
US20060063517A1 (en) * 2004-09-22 2006-03-23 Yeonjoo Oh Intelligent system for identifying visitor and providing communication service using mobile terminal and method thereof
US7020090B2 (en) * 2004-06-21 2006-03-28 Cisco Technology, Inc. System and method for loadbalancing in a network environment using feedback information
US20060092963A1 (en) * 2004-10-28 2006-05-04 Ajay Bakre Architecture and method for efficient application of QoS in a WLAN
US20060104308A1 (en) * 2004-11-12 2006-05-18 Microsoft Corporation Method and apparatus for secure internet protocol (IPSEC) offloading with integrated host protocol stack management
US20060111112A1 (en) * 2004-10-22 2006-05-25 Santera Systems, Inc. Mobility management apparatus and methods
US7079499B1 (en) * 1999-09-08 2006-07-18 Nortel Networks Limited Internet protocol mobility architecture framework
US20060251043A1 (en) * 2005-04-18 2006-11-09 Lila Madour Method for controlling the quality of service in an IP multimedia system
US20060251229A1 (en) * 2005-05-03 2006-11-09 Sbc Knowledge Ventures, L.P. System and method for configuring and operating a network based telephone system
US20060250956A1 (en) * 2005-04-04 2006-11-09 Alfano Frank M Telecommunication network support for service based policy in roaming configurations
US20060268901A1 (en) * 2005-01-07 2006-11-30 Choyi Vinod K Method and apparatus for providing low-latency secure session continuity between mobile nodes
US20060268845A1 (en) * 2005-05-31 2006-11-30 Santera Systems, Inc. Methods and systems for unlicensed mobile access realization in a media gateway
US7170863B1 (en) * 2001-02-12 2007-01-30 Nortel Networks Limited Push-to-talk wireless telecommunications system utilizing a voice-over-IP network
US7170887B2 (en) * 1996-11-26 2007-01-30 Lucent Technologies Inc. Methods and apparatus for providing voice communications through a packet network
US20070127500A1 (en) * 2005-04-14 2007-06-07 Joon Maeng System, device, method and software for providing a visitor access to a public network
US20070133574A1 (en) * 2005-12-01 2007-06-14 Tekelec Methods, systems, and computer program products for using an E.164 number (ENUM) database for message service message routing resolution among 2G and subsequent generation network systems
US20070140255A1 (en) * 2005-12-21 2007-06-21 Motorola, Inc. Method and system for communication across different wireless technologies using a multimode mobile device
US20070160034A1 (en) * 2006-01-06 2007-07-12 D.S.P. Group Ltd Dual-protocol dual port telephone and method to connect another dual-protocol dual port telephone via IP network directly and without installation
US20070189255A1 (en) * 2006-01-11 2007-08-16 Mruthyunjaya Navali Systems and methods for mobility management on wireless networks
US20070202871A1 (en) * 2006-02-27 2007-08-30 Alvarion Ltd. Method of paging a mobile terminal
US20070207818A1 (en) * 2006-03-06 2007-09-06 Rosenberg Jonathan D System and method for exchanging policy information in a roaming communications environment
US20070266174A1 (en) * 2006-05-12 2007-11-15 Caitlin Bestler Method and system for reliable multicast datagrams and barriers
US20070291733A1 (en) * 2004-03-04 2007-12-20 Outsmart Ltd. Integration of Packet and Cellular Telephone Networks
US20080026692A1 (en) * 2006-07-28 2008-01-31 Fujitsu Limited Relay apparatus and relay method
US20080046963A1 (en) * 2006-08-18 2008-02-21 Cisco Technology, Inc. System and method for implementing policy server based application interaction manager
US20080046979A1 (en) * 2004-07-09 2008-02-21 Rachid Oulahal System for Controlled Access to Information Contained in a Terminal
US20080049648A1 (en) * 2006-08-28 2008-02-28 Motorola, Inc. Method and apparatus for policy management for an internet protocol multimedia subsystem based wireless communication system
US20080070619A1 (en) * 2004-07-30 2008-03-20 Jun Yu Communication Network System Converging Wireless Mobile Network and Wired Discontinuous Mobile Network and Method Thereof
US20080075114A1 (en) * 2006-09-25 2008-03-27 Zte Corporation System and Method for IPv4 and IPv6 Migration
US20080089251A1 (en) * 2005-02-17 2008-04-17 Motorola, Inc. Packet Data Transmission
US20080101291A1 (en) * 2002-05-28 2008-05-01 James Jiang Interworking Mechanism Between Wireless Wide Area Network and Wireless Local Area Network
US20080127297A1 (en) * 2006-11-29 2008-05-29 Red Hat, Inc. Method and system for sharing labeled information between different security realms
US20080137541A1 (en) * 2006-12-07 2008-06-12 Kaitki Agarwal Providing dynamic changes to packet flows
US20080144615A1 (en) * 2006-12-14 2008-06-19 Nortel Networks Limited Pinning the route of ip bearer flows in a next generation network
US20080207206A1 (en) * 2007-02-23 2008-08-28 Kenichi Taniuchi MEDIA INDEPENDENT PRE-AUTHENTICATION SUPPORTING FAST-HANDOFF IN PROXY MIPv6 ENVIRONMENT
US20080225806A1 (en) * 2007-03-15 2008-09-18 Adc Telecommunication Israel Ltd. System and method for enabling mobility in internet protocol networks
US20080229403A1 (en) * 2007-03-16 2008-09-18 Redback Networks Inc. Method and apparatus for providing wireless services to mobile subscribers using existing broadband infrastructure
US20080256237A1 (en) * 2005-03-08 2008-10-16 Huawei Technologies Co., Ltd. Method for Implementing Resources Reservation in a Proxy-Requested Mode in Next Generation Network
US20080285492A1 (en) * 2007-05-18 2008-11-20 Seppo Vesterinen System and Method for Providing Local IP Breakout Services Employing Access Point Names
US20090016364A1 (en) * 2007-07-12 2009-01-15 Telefonaktiebolaget Lm Ericsson (Publ) Proxy Mobility Optimization
US20090022126A1 (en) * 2007-07-20 2009-01-22 Ameya Damle Multiple packet data network support over trusted access
US20090040964A1 (en) * 2007-08-06 2009-02-12 Fan Zhao Dynamic internet protocol addressing solutions with network-based mobility
US20090061869A1 (en) * 2007-08-30 2009-03-05 Sprint Spectrum L.P. Policy Based Mobile-IP Address Selection and Assignment
US20090129380A1 (en) * 2007-11-20 2009-05-21 Arindam Paul Determining packet forwarding information for packets sent from a protocol offload engine in a packet switching device
US7548756B2 (en) * 2004-05-20 2009-06-16 Cellco Partnership Method and system for mobile instant messaging using multiple interfaces
US20090198996A1 (en) * 2008-02-04 2009-08-06 Contineo Systems System and method for providing cellular access points
US20090207759A1 (en) * 2008-02-15 2009-08-20 Andreasen Flemming S System and method for providing a converged wireline and wireless network environment
US20090207808A1 (en) * 2008-02-15 2009-08-20 Motorola, Inc. Method and apparatus for inter-technology handoff of a multi-mode mobile station
US7606191B1 (en) * 2006-05-01 2009-10-20 Sprint Spectrum L.P. Methods and systems for secure mobile-IP traffic traversing network address translation
US20090270064A1 (en) * 2006-01-09 2009-10-29 Motorola, Inc. Method and system architecture for establishing a specific communication session in a communication network
US20100027509A1 (en) * 2006-12-15 2010-02-04 Genadi Velev Local mobility anchor relocation and route optimization during handover of a mobile node to another network area
US20100061309A1 (en) * 2003-07-14 2010-03-11 Buddhikot Milind M Method and system for mobility across heterogeneous address spaces
US20100071055A1 (en) * 2004-03-02 2010-03-18 Advanced Micro Devices, Inc. Two Parallel Engines for High Speed Transmit IPSEC Processing
US7710923B2 (en) * 2004-05-07 2010-05-04 Interdigital Technology Corporation System and method for implementing a media independent handover
US20100131829A1 (en) * 2008-11-22 2010-05-27 Qualcomm Incorporated Scheduling data with time diversity in flow systems
US20100131621A1 (en) * 2004-12-10 2010-05-27 Jerker Zetterlund Session Controller and Method of Operating a Session Controller
US20100135279A1 (en) * 2007-03-05 2010-06-03 Telefonaktiebolaget Lm Ericsson (Publ) Method and Arrangement for Remotely Controlling Multimedia Communication Across Local Networks
US20100191829A1 (en) * 2007-01-18 2010-07-29 Cagenius Torbjoern Method and apparatus for remote access to a home network
US20100235620A1 (en) * 2007-10-17 2010-09-16 Tomas Nylander Method and Arrangement for Deciding a Security Setting
US20100250753A1 (en) * 2008-01-07 2010-09-30 Lg Electronics Inc. Partial session transfer method and user equipment for the same
US20100260105A1 (en) * 2007-12-07 2010-10-14 Ralf Keller Domain transfer service continuity provision to a mobile terminal
US20100272053A1 (en) * 2007-12-20 2010-10-28 Jianjie You Method for Realizing Resource Admission Control at Push Mode in Nomadism Scene of NGN
US7831701B2 (en) * 2007-10-27 2010-11-09 At&T Mobility Ii Llc Cascading policy management deployment architecture
US7835275B1 (en) * 2006-09-08 2010-11-16 Sprint Communications Company L.P. Dynamic assignment of quality of service (QoS) to an active session in an ipsec tunnel
US20100309846A1 (en) * 2007-11-26 2010-12-09 Johan Rune Method and apparatus for use in a communications network
US7881262B2 (en) * 2005-07-07 2011-02-01 Alvarion Ltd. Method and apparatus for enabling mobility in mobile IP based wireless communication systems
US7886027B2 (en) * 2006-04-14 2011-02-08 International Business Machines Corporation Methods and arrangements for activating IP configurations
US20110069673A1 (en) * 2009-09-21 2011-03-24 Starent Networks, Corp Local routing of voice calls by a femto gateway
US20110214166A1 (en) * 2008-10-29 2011-09-01 Nokia Corporation Connection management
US8032940B1 (en) * 2006-10-25 2011-10-04 Chaperon, LLC Method and system for generating and employing a secure integrated development environment
US8036191B2 (en) * 2005-12-16 2011-10-11 Siemens Aktiengesellschaft Mobile station as a gateway for mobile terminals to an access network, and method for registering the mobile station and the mobile terminals in a network
US8105366B2 (en) * 2002-05-30 2012-01-31 Warsaw Orthopedic, Inc. Laminoplasty plate with flanges
US20120046037A1 (en) * 2007-06-26 2012-02-23 John Diachina System and method for providing voice service in a multimedia mobile network
US8195778B1 (en) * 2009-12-19 2012-06-05 Cisco Technology, Inc. System and method for providing mobility across access technologies in a network environment
US8223635B2 (en) * 2007-06-19 2012-07-17 Zte Corporation Metropolitan area network resource control system and method, access resource admission and control device

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6403567B1 (en) * 1999-06-22 2002-06-11 Cv Therapeutics, Inc. N-pyrazole A2A adenosine receptor agonists
KR100415117B1 (en) * 2002-03-04 2004-01-13 삼성전자주식회사 Apparatus and method for called compulsive on multi call into internet protocol phone in an internet protocol telephony system
KR100474706B1 (en) * 2002-09-11 2005-03-10 삼성전자주식회사 Apparatus of inter processor communication using tcp/ip in communication system
US7343158B2 (en) * 2003-04-16 2008-03-11 Nortel Networks Limited Home agent redirection for mobile IP
BRPI0711170A2 (en) * 2006-05-02 2011-08-23 Ntt Docomo Inc Mobile terminal and mobile communication system
US7742487B2 (en) * 2006-08-22 2010-06-22 Embarq Holdings Company Llc System and method for integrated service access
CN101163091B (en) 2006-10-10 2011-05-11 华为技术有限公司 Resource admission control system and method
US7836497B2 (en) 2006-12-22 2010-11-16 Telefonaktiebolaget L M Ericsson (Publ) Apparatus and method for resilient IP security/internet key exchange security gateway
US9871872B2 (en) * 2007-04-13 2018-01-16 Nokia Technologies Oy Mechanism for executing server discovery
US8191106B2 (en) * 2007-06-07 2012-05-29 Alcatel Lucent System and method of network access security policy management for multimodal device
US20090016334A1 (en) 2007-07-09 2009-01-15 Nokia Corporation Secured transmission with low overhead
WO2009012187A2 (en) * 2007-07-14 2009-01-22 Tatara Systems, Inc. Method and apparatus for supporting sip/ims-based femtocells
US7892894B2 (en) * 2007-09-20 2011-02-22 Stats Chippac Ltd. Method of manufacturing integrated circuit package system with warp-free chip

Patent Citations (103)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US57458A (en) * 1866-08-28 Improvement in horse-collars
US67417A (en) * 1867-08-06 Improvement in pump-pistons
US165145A (en) * 1875-06-29 Improvement in compounds for preserving beer
US307487A (en) * 1884-11-04 moore
US5403567A (en) * 1989-12-05 1995-04-04 Smith; James W. Dual impeller method and apparatus for effecting chemical conversion
US6181935B1 (en) * 1996-09-27 2001-01-30 Software.Com, Inc. Mobility extended telephone application programming interface and method of use
US7170887B2 (en) * 1996-11-26 2007-01-30 Lucent Technologies Inc. Methods and apparatus for providing voice communications through a packet network
US6587882B1 (en) * 1997-08-01 2003-07-01 Kabushiki Kaisha Toshiba Mobile IP communication scheme using visited site or nearby network as temporal home network
US6934274B2 (en) * 1998-02-20 2005-08-23 Kabushiki Kaisha Toshiba Mobile IP communication scheme using dynamic address allocation protocol
US6937597B1 (en) * 1999-02-26 2005-08-30 Lucent Technologies Inc. Signaling method for internet telephony
US7079499B1 (en) * 1999-09-08 2006-07-18 Nortel Networks Limited Internet protocol mobility architecture framework
US6603761B1 (en) * 1999-09-17 2003-08-05 Lucent Technologies Inc. Using internet and internet protocols to bypass PSTN, GSM map, and ANSI-41 networks for wireless telephone call delivery
US6910074B1 (en) * 2000-07-24 2005-06-21 Nortel Networks Limited System and method for service session management in an IP centric distributed network
US7170863B1 (en) * 2001-02-12 2007-01-30 Nortel Networks Limited Push-to-talk wireless telecommunications system utilizing a voice-over-IP network
US6970909B2 (en) * 2001-10-11 2005-11-29 The Trustees Of Columbia University In The City Of New York Multi-protocol data communication system supporting wireless telephony and content delivery
US20030091013A1 (en) * 2001-11-07 2003-05-15 Samsung Electronics Co., Ltd. Authentication method between mobile node and home agent in a wireless communication system
US20080101291A1 (en) * 2002-05-28 2008-05-01 James Jiang Interworking Mechanism Between Wireless Wide Area Network and Wireless Local Area Network
US8105366B2 (en) * 2002-05-30 2012-01-31 Warsaw Orthopedic, Inc. Laminoplasty plate with flanges
US20040003241A1 (en) * 2002-06-27 2004-01-01 Nokia, Inc. Authentication of remotely originating network messages
US20040008627A1 (en) * 2002-07-12 2004-01-15 Sachin Garg Method and apparatus for performing admission control in a communication network
US20040077341A1 (en) * 2002-10-17 2004-04-22 Chandranmenon Girish P. Multi-interface mobility client
US20050238002A1 (en) * 2003-02-10 2005-10-27 Rasanen Juha A Mobile network having IP multimedia subsystem (IMS) entities and solutions for providing simplification of operations and compatibility between different IMS entities
US20040213260A1 (en) * 2003-04-28 2004-10-28 Cisco Technology, Inc. Methods and apparatus for securing proxy Mobile IP
US20040219905A1 (en) * 2003-05-02 2004-11-04 Steven Blumenthal Authentication of mobile devices via proxy device
US20040225895A1 (en) * 2003-05-05 2004-11-11 Lucent Technologies Inc. Method and apparatus for providing adaptive VPN to enable different security levels in virtual private networks (VPNs)
US20100061309A1 (en) * 2003-07-14 2010-03-11 Buddhikot Milind M Method and system for mobility across heterogeneous address spaces
US20050135375A1 (en) * 2003-12-19 2005-06-23 Nokia Corporation Control decisions in a communication system
US20050159181A1 (en) * 2004-01-20 2005-07-21 Lucent Technologies Inc. Method and apparatus for interconnecting wireless and wireline networks
US20100071055A1 (en) * 2004-03-02 2010-03-18 Advanced Micro Devices, Inc. Two Parallel Engines for High Speed Transmit IPSEC Processing
US20070291733A1 (en) * 2004-03-04 2007-12-20 Outsmart Ltd. Integration of Packet and Cellular Telephone Networks
US7710923B2 (en) * 2004-05-07 2010-05-04 Interdigital Technology Corporation System and method for implementing a media independent handover
US7548756B2 (en) * 2004-05-20 2009-06-16 Cellco Partnership Method and system for mobile instant messaging using multiple interfaces
US20050278532A1 (en) * 2004-05-28 2005-12-15 Zhi Fu Method and apparatus for mutual authentication at handoff in a mobile wireless communication network
US7020090B2 (en) * 2004-06-21 2006-03-28 Cisco Technology, Inc. System and method for loadbalancing in a network environment using feedback information
US20080046979A1 (en) * 2004-07-09 2008-02-21 Rachid Oulahal System for Controlled Access to Information Contained in a Terminal
US20080070619A1 (en) * 2004-07-30 2008-03-20 Jun Yu Communication Network System Converging Wireless Mobile Network and Wired Discontinuous Mobile Network and Method Thereof
US20060041761A1 (en) * 2004-08-17 2006-02-23 Neumann William C System for secure computing using defense-in-depth architecture
US20060063517A1 (en) * 2004-09-22 2006-03-23 Yeonjoo Oh Intelligent system for identifying visitor and providing communication service using mobile terminal and method thereof
US20060111112A1 (en) * 2004-10-22 2006-05-25 Santera Systems, Inc. Mobility management apparatus and methods
US20060092963A1 (en) * 2004-10-28 2006-05-04 Ajay Bakre Architecture and method for efficient application of QoS in a WLAN
US20060104308A1 (en) * 2004-11-12 2006-05-18 Microsoft Corporation Method and apparatus for secure internet protocol (IPSEC) offloading with integrated host protocol stack management
US20100131621A1 (en) * 2004-12-10 2010-05-27 Jerker Zetterlund Session Controller and Method of Operating a Session Controller
US20060268901A1 (en) * 2005-01-07 2006-11-30 Choyi Vinod K Method and apparatus for providing low-latency secure session continuity between mobile nodes
US20080089251A1 (en) * 2005-02-17 2008-04-17 Motorola, Inc. Packet Data Transmission
US20080256237A1 (en) * 2005-03-08 2008-10-16 Huawei Technologies Co., Ltd. Method for Implementing Resources Reservation in a Proxy-Requested Mode in Next Generation Network
US20060250956A1 (en) * 2005-04-04 2006-11-09 Alfano Frank M Telecommunication network support for service based policy in roaming configurations
US20070127500A1 (en) * 2005-04-14 2007-06-07 Joon Maeng System, device, method and software for providing a visitor access to a public network
US20060251043A1 (en) * 2005-04-18 2006-11-09 Lila Madour Method for controlling the quality of service in an IP multimedia system
US20060251229A1 (en) * 2005-05-03 2006-11-09 Sbc Knowledge Ventures, L.P. System and method for configuring and operating a network based telephone system
US20060268845A1 (en) * 2005-05-31 2006-11-30 Santera Systems, Inc. Methods and systems for unlicensed mobile access realization in a media gateway
US7881262B2 (en) * 2005-07-07 2011-02-01 Alvarion Ltd. Method and apparatus for enabling mobility in mobile IP based wireless communication systems
US20070133574A1 (en) * 2005-12-01 2007-06-14 Tekelec Methods, systems, and computer program products for using an E.164 number (ENUM) database for message service message routing resolution among 2G and subsequent generation network systems
US8036191B2 (en) * 2005-12-16 2011-10-11 Siemens Aktiengesellschaft Mobile station as a gateway for mobile terminals to an access network, and method for registering the mobile station and the mobile terminals in a network
US20070140255A1 (en) * 2005-12-21 2007-06-21 Motorola, Inc. Method and system for communication across different wireless technologies using a multimode mobile device
US20070160034A1 (en) * 2006-01-06 2007-07-12 D.S.P. Group Ltd Dual-protocol dual port telephone and method to connect another dual-protocol dual port telephone via IP network directly and without installation
US20090270064A1 (en) * 2006-01-09 2009-10-29 Motorola, Inc. Method and system architecture for establishing a specific communication session in a communication network
US20070189255A1 (en) * 2006-01-11 2007-08-16 Mruthyunjaya Navali Systems and methods for mobility management on wireless networks
US20070202871A1 (en) * 2006-02-27 2007-08-30 Alvarion Ltd. Method of paging a mobile terminal
US20070207818A1 (en) * 2006-03-06 2007-09-06 Rosenberg Jonathan D System and method for exchanging policy information in a roaming communications environment
US7886027B2 (en) * 2006-04-14 2011-02-08 International Business Machines Corporation Methods and arrangements for activating IP configurations
US7606191B1 (en) * 2006-05-01 2009-10-20 Sprint Spectrum L.P. Methods and systems for secure mobile-IP traffic traversing network address translation
US20070266174A1 (en) * 2006-05-12 2007-11-15 Caitlin Bestler Method and system for reliable multicast datagrams and barriers
US20080026692A1 (en) * 2006-07-28 2008-01-31 Fujitsu Limited Relay apparatus and relay method
US20080046963A1 (en) * 2006-08-18 2008-02-21 Cisco Technology, Inc. System and method for implementing policy server based application interaction manager
US20080049648A1 (en) * 2006-08-28 2008-02-28 Motorola, Inc. Method and apparatus for policy management for an internet protocol multimedia subsystem based wireless communication system
US7835275B1 (en) * 2006-09-08 2010-11-16 Sprint Communications Company L.P. Dynamic assignment of quality of service (QoS) to an active session in an ipsec tunnel
US20080075114A1 (en) * 2006-09-25 2008-03-27 Zte Corporation System and Method for IPv4 and IPv6 Migration
US8032940B1 (en) * 2006-10-25 2011-10-04 Chaperon, LLC Method and system for generating and employing a secure integrated development environment
US20080127297A1 (en) * 2006-11-29 2008-05-29 Red Hat, Inc. Method and system for sharing labeled information between different security realms
US20080137541A1 (en) * 2006-12-07 2008-06-12 Kaitki Agarwal Providing dynamic changes to packet flows
US20080176582A1 (en) * 2006-12-07 2008-07-24 Rajat Ghai Providing location based services for mobile devices
US20080144615A1 (en) * 2006-12-14 2008-06-19 Nortel Networks Limited Pinning the route of ip bearer flows in a next generation network
US20100027509A1 (en) * 2006-12-15 2010-02-04 Genadi Velev Local mobility anchor relocation and route optimization during handover of a mobile node to another network area
US20100191829A1 (en) * 2007-01-18 2010-07-29 Cagenius Torbjoern Method and apparatus for remote access to a home network
US20080207206A1 (en) * 2007-02-23 2008-08-28 Kenichi Taniuchi MEDIA INDEPENDENT PRE-AUTHENTICATION SUPPORTING FAST-HANDOFF IN PROXY MIPv6 ENVIRONMENT
US20100135279A1 (en) * 2007-03-05 2010-06-03 Telefonaktiebolaget Lm Ericsson (Publ) Method and Arrangement for Remotely Controlling Multimedia Communication Across Local Networks
US20080225806A1 (en) * 2007-03-15 2008-09-18 Adc Telecommunication Israel Ltd. System and method for enabling mobility in internet protocol networks
US20080229403A1 (en) * 2007-03-16 2008-09-18 Redback Networks Inc. Method and apparatus for providing wireless services to mobile subscribers using existing broadband infrastructure
US20080285492A1 (en) * 2007-05-18 2008-11-20 Seppo Vesterinen System and Method for Providing Local IP Breakout Services Employing Access Point Names
US8223635B2 (en) * 2007-06-19 2012-07-17 Zte Corporation Metropolitan area network resource control system and method, access resource admission and control device
US20120046037A1 (en) * 2007-06-26 2012-02-23 John Diachina System and method for providing voice service in a multimedia mobile network
US20090016364A1 (en) * 2007-07-12 2009-01-15 Telefonaktiebolaget Lm Ericsson (Publ) Proxy Mobility Optimization
US20090022126A1 (en) * 2007-07-20 2009-01-22 Ameya Damle Multiple packet data network support over trusted access
US20090040964A1 (en) * 2007-08-06 2009-02-12 Fan Zhao Dynamic internet protocol addressing solutions with network-based mobility
US20090061869A1 (en) * 2007-08-30 2009-03-05 Sprint Spectrum L.P. Policy Based Mobile-IP Address Selection and Assignment
US20100235620A1 (en) * 2007-10-17 2010-09-16 Tomas Nylander Method and Arrangement for Deciding a Security Setting
US7831701B2 (en) * 2007-10-27 2010-11-09 At&T Mobility Ii Llc Cascading policy management deployment architecture
US20090129380A1 (en) * 2007-11-20 2009-05-21 Arindam Paul Determining packet forwarding information for packets sent from a protocol offload engine in a packet switching device
US20100309846A1 (en) * 2007-11-26 2010-12-09 Johan Rune Method and apparatus for use in a communications network
US20100260105A1 (en) * 2007-12-07 2010-10-14 Ralf Keller Domain transfer service continuity provision to a mobile terminal
US20100272053A1 (en) * 2007-12-20 2010-10-28 Jianjie You Method for Realizing Resource Admission Control at Push Mode in Nomadism Scene of NGN
US8379519B2 (en) * 2007-12-20 2013-02-19 Zte Corporation Method for realizing resource admission control at push mode in nomadism scene of NGN
US20100250753A1 (en) * 2008-01-07 2010-09-30 Lg Electronics Inc. Partial session transfer method and user equipment for the same
US20090198996A1 (en) * 2008-02-04 2009-08-06 Contineo Systems System and method for providing cellular access points
US20090207759A1 (en) * 2008-02-15 2009-08-20 Andreasen Flemming S System and method for providing a converged wireline and wireless network environment
US20110103266A1 (en) * 2008-02-15 2011-05-05 Cisco Technology, Inc., A California Corporation System and method for providing location and access network information support in a network environment
US20090207823A1 (en) * 2008-02-15 2009-08-20 Andreasen Flemming S System and method for providing selective mobility invocation in a network environment
US7899039B2 (en) * 2008-02-15 2011-03-01 Cisco Technology, Inc. System and method for providing location and access network information support in a network environment
US20090207808A1 (en) * 2008-02-15 2009-08-20 Motorola, Inc. Method and apparatus for inter-technology handoff of a multi-mode mobile station
US20110214166A1 (en) * 2008-10-29 2011-09-01 Nokia Corporation Connection management
US20100131829A1 (en) * 2008-11-22 2010-05-27 Qualcomm Incorporated Scheduling data with time diversity in flow systems
US20110069673A1 (en) * 2009-09-21 2011-03-24 Starent Networks, Corp Local routing of voice calls by a femto gateway
US8195778B1 (en) * 2009-12-19 2012-06-05 Cisco Technology, Inc. System and method for providing mobility across access technologies in a network environment

Cited By (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8554905B2 (en) * 1998-01-19 2013-10-08 Brother Kogyo Kabushiki Kaisha Network system, terminal and recording medium
US20100290086A1 (en) * 1998-01-19 2010-11-18 Brother Kogyo Kabushiki Kaisha Network System, Terminal and Recording Medium
US20090207759A1 (en) * 2008-02-15 2009-08-20 Andreasen Flemming S System and method for providing a converged wireline and wireless network environment
US20110103266A1 (en) * 2008-02-15 2011-05-05 Cisco Technology, Inc., A California Corporation System and method for providing location and access network information support in a network environment
US8711847B2 (en) 2008-02-15 2014-04-29 Cisco Technology, Inc. System and method for providing location and access network information support in a network environment
US20090303924A1 (en) * 2008-06-10 2009-12-10 Nokia Siemens Networks Oy Packet data network selection
US20090303973A1 (en) * 2008-06-10 2009-12-10 Nokia Siemens Networks Oy Packet data network selection
US9294111B2 (en) * 2008-08-06 2016-03-22 Futurewei Technologies, Inc. Remote media IMS sessions
US20090313378A1 (en) * 2008-08-06 2009-12-17 Futurewei Technologies, Inc. Remote Media IMS Sessions
US8370500B2 (en) 2008-08-06 2013-02-05 Futurewei Technologies, Inc. Remote session control
US9843519B2 (en) 2008-11-21 2017-12-12 At&T Intellectual Property I, L.P. Femtocell local breakout mechanisms
US9635581B2 (en) * 2008-11-21 2017-04-25 At&T Intellectual Property I, L.P. Femtocell local breakout mechanisms
US9918248B2 (en) 2008-11-21 2018-03-13 At&T Intellectual Property I, L.P. Service continuity during local breakout in a femtocell
US8195778B1 (en) 2009-12-19 2012-06-05 Cisco Technology, Inc. System and method for providing mobility across access technologies in a network environment
US20130016677A1 (en) * 2010-03-05 2013-01-17 Nec Europe Ltd. Method for operating a network and a network
US8824410B2 (en) * 2010-03-05 2014-09-02 Nec Europe Ltd. Method for operating a network and a network
US9215588B2 (en) 2010-04-30 2015-12-15 Cisco Technology, Inc. System and method for providing selective bearer security in a network environment
US9015346B2 (en) * 2010-11-29 2015-04-21 Telefonaktiebolaget L M Ericsson (Publ) Identification of a private device in a public network
US20140204947A1 (en) * 2010-11-29 2014-07-24 Telefonaktiebolaget L M Ericsson (Publ) Identification of a private device in a public network
US9537821B2 (en) * 2011-02-01 2017-01-03 Telefonaktiebolaget Lm Ericsson (Publ) Method for PCC support for scenarios with NAT in the GW
US20140269740A1 (en) * 2011-02-01 2014-09-18 Telefonaktiebolaget L M Ericsson (Publ) Method for pcc support for scenarios with nat in the gw
US8650279B2 (en) 2011-06-29 2014-02-11 Juniper Networks, Inc. Mobile gateway having decentralized control plane for anchoring subscriber sessions
US20130007286A1 (en) * 2011-06-29 2013-01-03 Juniper Networks, Inc. User session routing between mobile network gateways
US20130272163A1 (en) * 2012-04-13 2013-10-17 Zu Qiang Non-seamless offload indicator
EP2654262A3 (en) * 2012-04-18 2016-09-14 Telefonaktiebolaget LM Ericsson (publ) Media plane optimization for voice over LTE
US9191362B2 (en) * 2012-06-26 2015-11-17 Cisco Technology, Inc. Determining the type of upstream network address translation from a home gateway
US20130346629A1 (en) * 2012-06-26 2013-12-26 Cisco Technology, Inc. Determining the type of upstream network address translation from a home gateway
US20140351590A1 (en) * 2013-05-23 2014-11-27 Sercomm Corporation Network device, ipsec system and method for establishing ipsec tunnel using the same
US9602470B2 (en) * 2013-05-23 2017-03-21 Sercomm Corporation Network device, IPsec system and method for establishing IPsec tunnel using the same
US20160344664A1 (en) * 2015-05-22 2016-11-24 Qualcomm Innovation Center, Inc. Direct client-to-client internet relay chat for softap clients
US9967214B2 (en) * 2015-05-22 2018-05-08 Qualcomm Incorporated Direct client-to-client internet relay chat for softap clients

Also Published As

Publication number Publication date
US8942112B2 (en) 2015-01-27
US8711847B2 (en) 2014-04-29
US20090207823A1 (en) 2009-08-20
US7899039B2 (en) 2011-03-01
US20110103266A1 (en) 2011-05-05
US20090207759A1 (en) 2009-08-20
US20090207757A1 (en) 2009-08-20

Similar Documents

Publication Publication Date Title
US7649881B2 (en) Pinning the route of IP bearer flows in a next generation network
EP1282995B1 (en) Policy server and architecture providing radio network resource allocation rules
US7940722B1 (en) System and method for determining a network for processing applications for a communication session
US7826353B2 (en) Method, system and network element for authorizing a data transmission
ES2290131T3 (en) Common rate identifier for communications networks.
EP1382214B1 (en) Binding information for ip media flows
EP2689567B1 (en) Network node and method to route through or around traffic detection function nodes
US9762580B2 (en) Policy control in a network
US7911943B2 (en) Optimization of PDP context usage
US10291529B2 (en) Adaptive intelligent routing in a communication system
AU2009313216B2 (en) Method and system for supporting SIP session policy using existing authorization architecture and protocols
EP1974560B1 (en) Policy enforcement within an ip network
US7855982B2 (en) Providing services to packet flows in a network
US9326181B2 (en) System and method for managing congestion in a network environment
CN101060367B (en) A mobile communication system for matching resource amount of core network bearer and resource amount of visited network bearer
Faccin et al. IP multimedia services: analysis of mobile IP and SIP interactions in 3G networks
EP1741264B1 (en) Telecommunications system
EP1374494B1 (en) Method and apparatus for establishing a protocol proxy for a mobile host terminal in a multimedia session
US9210728B2 (en) System and method for resource management for operator services and internet
JP2008527798A (en) VOIP network infrastructure components and methods
EP2359572B1 (en) Token-based correlation of control sessions for policy and charging control of a data session through a nat.
US20020036983A1 (en) Application influenced policy
US20010027490A1 (en) RSVP handling in 3G networks
US20020165966A1 (en) Method and apparatus for coordinating end-to-end quality of service requirements for media flows in a multimedia session
US8353000B2 (en) System and charging control method of network convergence policy and charging control architecture

Legal Events

Date Code Title Description
AS Assignment

Owner name: CISCO TECHNOLOGY, INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ANDREASEN, FLEMMING S.;BROCKNERS, FRANK;VUCETIC, VOJISLAV;REEL/FRAME:022342/0160;SIGNING DATES FROM 20090211 TO 20090213

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION