HK1096510A - Methods and apparatus for network initiated data services - Google Patents

Description

Method and apparatus for network initiated data services

In compliance with 35U.S.C. § 199 priority requirements

This patent application claims priority from provisional applications filed on 21/10/2003, entitled 60/513,249, Methods and Apparatus For Network Initiated Data Session and short Message Delivery, and on 14/11/2003, entitled 60/520,544, and entitled "Null-State Registration For Network-Initiated Data service," both of which are assigned to the assignee of the present patent application and are expressly incorporated herein by reference.

Technical Field

The present invention relates generally to wireless communications, and more particularly to Network Initiated Data Services (NIDS).

Acronym

The following terms, in the following description, are indicated by the following acronyms:

authentication, authorization and accounting (AAA)

Access Network ID (ANID)

Base Station (BS)

Current Access Network ID (CANID)

Challenge Handshake Authentication Protocol (CHAP)

Domain Name System (DNS)

Foreign Agent (FA)

Foreign Agent Challenge (FAC)

Home Agent (HA)

Attribute authentication, authorization and accounting (HAAA)

Home Application Gateway (HAGW)

Home Location Register (HLR)

Internet Protocol Control Protocol (IPCP)

Internet protocol reachability service (IRS)

Link Control Protocol (LCP)

Message Center (MC)

Mobile Station (MS)

Mobile Switching Center (MSC)

Mobile Station ID (MSID)

Network Access Identifier (NAI)

Network Access Server (NAS)

Network Initiated Data Session (NIDS)

NIDS Reachability Information (NRI)

Previous Access Network ID (PANID)

PPP Authentication Protocol (PAP)

Push Content Application (PCA)

Packet Control Function (PCF)

Packet Data Serving Node (PDSN)

Push Gateway (PGW, Push Gateway)

Point-to-point protocol (PPP)

Radio Access Network (RAN)

Short Message Application (SMA)

Visited authentication, authorization and accounting (VAAA)

Visited Application Gateway (VAGW)

Visited Location Register (VLR)

Wireless IP networks employing cdma2000 are being widely deployed. Many wireless data applications today take the initial action by a mobile station to establish a data session with a network and the mobile station, which is reachable by the network, sends IP packets.

Always on service

An "Always-On" capable wireless terminal may automatically establish a data session when powered On and maintain the session until powered off. For example, the IS-835-C standard for cdma2000 wireless IP networks supports constant maintenance of connectivity. In addition, 3GPP2 has developed an all-IP (all-IP) network that requires mobile stations to have constant connectivity to the IP network.

It is desirable to maintain service at all times, wherever and at any time, to allow users to push data into wireless terminals using IP push services. The network may send packets to the user for various services including email notifications such as short messaging for instant messages, interactive gaming, multimedia messaging, mobile terminal VoIP calls, IOTA data transfer, and the like.

One drawback associated with maintaining service at all times is that the network reserves resources for the wireless terminal even when the wireless terminal does not have any data activity.

For example, in order for a network to "push" data to a mobile station, the network must now maintain a dormant data session with a given mobile station when no data is active. This requires the reservation of resources such as memory space, signaling traffic, PDSN resources, air interface resources, and IP address space. For example, for a wireless terminal to maintain a dormant session in a PCF, memory space in the PCF is required. In addition, periodically updating the R-P tunnel between the PCF and the PDSN may periodically add unnecessary signaling. PDSN resources are required to maintain PPP state in the PDSN. Air interface resources associated with packet data mobility are required because the mobile terminal must leave the dormant state each time it enters a new packet zone to inform the base station of its location. If this results in an inter-PDSN handoff (handoff), a new PPP and mobile IP registration is typically necessary, which requires the use of traffic channel resources. Finally, the IP address space is required to reserve IP addresses for mobile stations, and if IPv4 is used, there is a practical limit to the number of addresses available.

cdma2000 operators want to efficiently utilize PDSN and HA resources, and because PDSN and HA resources are expensive, cdma2000 operators may not offer always-on-hold services. Thus, in the IS-835-C standard, 3GPP2 developed a solution for PDSN and HA resource management. However, if the operator does not provide always-on service, the MS may not be able to receive IP push service since the connectivity resources for the MS in the PDSN and HA may have been removed.

Network initiated data services

Network Initiated Data Services (NIDS) address network resource publications associated with always-on services. NIDS facilitates MSs that spend most of their time in a packet data dormant state. NIDS are useful when a packet data enabled device, such as an MS, is in a "packet data unconnected state" and the CN wishes to establish a data session with (i.e., "push" data to) the mobile station. NIDS is useful, for example, in applications where devices occasionally need to establish packet data communication sessions, sometimes dictated by the core network. Such applications may include, for example, email notifications, location-specific based applications, maintenance operations such as PRL downloads, and the like. NIDS are also useful, for example, with respect to services that require data to be "pushed" to the MS, such as instant Messaging (im Messaging) or multimedia Messaging (Multi-media Messaging).

The goal of NIDS is to optimize network resources by communicating IP packets to the mobile station, some of which have been recycled for use by the mobile station. Without the NIDS, a packet data connection between the network and the wireless terminal is required to reach the wireless terminal, either through an "always on" service or through a mobile-originated connection.

For various administrative reasons, the network may clear PPP sessions for simple IP and mobile IP, or clear binding records in the HA. The network can display this clearance by sending a clearance message, such as a link control protocol term request (link control protocol term request) or an Agent Advertisement (Agent Advertisement), to the wireless terminal. By receiving this clear message, the wireless terminal knows that the network has terminated IP connectivity.

However, if the wireless terminal temporarily leaves the coverage area, the wireless terminal cannot receive the clear message. When the wireless terminal returns to the coverage area, the wireless terminal is assumed to still be provided with IP connectivity until the timer expires. For example, the timer may be a mobile IP registration lifetime timer or a maximum PPP inactivity timer. In addition, when the PPP session is administratively cleared, or the packet data session in the RAN has terminated, the network may notify the wireless terminal that the packet data session is over by sending a link control protocol entry request or release command to the wireless terminal.

Depending on the implementation, the wireless terminal may retain the home address (homeaddress) of the mobile IP but enter a null-state, while the HA maintains the mobile IP binding to the MS. Thus, the HA can receive packets destined for the registered MS. However, because the network has terminated IP connectivity, packets cannot be delivered to the wireless terminal through the PDSN.

There is therefore a need in the art to address these problems.

Disclosure of Invention

Techniques are provided for conserving network resources in a network that can provide push data services and initiate such push data services by delivering push data to a dormant terminal. According to one aspect, a network-initiated data service is provided that supports push services while conserving network resources such as PPP state and a10 connections. There is no need to save IP addresses, since the dormant terminal must have an IP address in order to receive the push data. The entity pushing data to the dormant terminal needs to know the IP address of the dormant wireless terminal.

According to one embodiment, a network includes a wireless terminal, a first packet data serving node, and a first radio access network. The wireless terminal has an IP address associated with it. The first packet data service node creates reachability information for the wireless terminal in response to wireless terminal profile information, such as NIDS or IP Reachability Service (IRS). The first radio access network generates a dormancy indication when it detects that the wireless terminal is dormant.

According to one aspect of the invention, upon receiving the dormancy indication, the first packet data serving node removes the PPP state and requests the first radio access network to release the a10 connection. Likewise, selected network resources associated with the dormant terminal, such as PPP state and a10 connection, are released.

According to another aspect, information reserved for reaching the dormant terminal is updated when the point of network attachment of the dormant terminal changes. In one embodiment, the first packet data service node can retain reachability information for the dormant terminal.

Drawings

FIG. 1 is a simplified block diagram of a wireless IP network reference model;

FIG. 2 is a flow diagram of one embodiment of a method for conserving network resources in a network that delivers push data to a dormant wireless terminal authorized for NIDS;

FIG. 3 is a flow diagram of another embodiment of a method for conserving network resources in a network that delivers push data to a dormant wireless terminal authorized for NIDS;

fig. 4A is a block diagram of a network during a network-initiated packet data session;

FIG. 4B is a block diagram of the network of FIG. 4A during a handoff within the PDSN;

FIG. 4C is a block diagram of the network of FIG. 4B during an inter-PDSN handoff;

FIG. 4D is a block diagram of the network of FIG. 4C when data is pushed to the wireless terminal;

FIG. 4E is a call flow diagram of an embodiment of the invention applied to simple IP

Fig. 5A is a block diagram of another network in a network-initiated packet data session;

FIG. 5B is a block diagram of the network of FIG. 5A during a handoff within the PDSN;

FIG. 5C is a block diagram of the network of FIG. 5B during an inter-PDSN handoff;

FIG. 5D is a block diagram of the network of FIG. 5C when data is pushed to the wireless terminal; and

fig. 5E is a call flow diagram of an embodiment of the present invention as applied to mobile IPv 4.

Detailed Description

The term "packet data session" refers to a session in which a user requests and uses a packet data service.

The term "packet data unconnected state" refers to a packet data connected state in which network resources have not been allocated to allow IP packets to be sent to the wireless terminal.

The term "Correspondent Node (CN)" refers to the originator of the push IP packet to the MS.

The term "wireless terminal" refers to the recipient of the IP packet pushed by the CN. The term "wireless terminal" may be used interchangeably with the terms "mobile station," "destination station," "subscriber unit," "terminal" and "User Equipment (UE)" and refers to the hardware with which an access network communicates. For example, in a UMTS system, a User Equipment (UE) is a device that allows a user to access UMTS network services, and preferably also includes a USIM that contains all subscription (subscription) information for the user. Wireless terminals, which may be mobile or fixed, typically include any communication device, data equipment, or terminal that communicates through a wireless channel or through a wired channel, for example using fiber optic or coaxial cables. A wireless terminal may be embodied in a device including, but not limited to, a PC card, compact flash card, external or internal modem, wireless or wireline phone.

The term "dormant terminal" refers to a wireless terminal that is in a dormant state. "dormant state" refers to a state in which the wireless terminal has not been assigned an air channel, but both the wireless terminal and the network have the information needed to quickly establish connectivity between the wireless terminal and the network.

The term "terminal Profile information" refers to subscription information for each wireless terminal. Examples of such subscription information include NIDS, IRS, and the like.

The term "push" refers to sending unsolicited data to a wireless terminal at the initiation of a CN.

The term "exemplary" is meant to serve as an example, instance, or illustration. Any embodiment described as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.

Wireless IP network

The NIDS may be constructed on the basis of a Wireless IP Network reference model as defined in 3gpp2x.s0011, Wireless IP Network Standard. To illustrate the need for NIDS services, a simplified wireless IP network reference model is shown in fig. 1.

Fig. 1 is a diagram of a wireless IP network reference model 4, the wireless IP network reference model 4 including an access provider network (access provider network)6 and a home network 8. Wherein the access provider network 6 includes a wireless terminal 10, a radio access network 20, a Packet Data Serving Node (PDSN)30 and a Foreign Agent (FA)32, a RADIUS server 40, and a Mobile Switching Center (MSC) 50; the home network 8 includes an IP network 60, a CN 70, a Home Agent (HA)80, RADIUS servers 90, 100, an SS7 network 110, and a Home Location Register (HLR) 120.

The wireless terminal 10 is connected to a radio access network 20, and the radio access network 20 is connected to a Packet Data Serving Node (PDSN)30 and a Foreign Agent (FA)32 through an R-P interface including an a10 interface and an a11 interface. The Radio Access Network (RAN)20 includes a Packet Control Function (PCF) that controls packet transmission between a Base Station (BS) (not shown) that is part of the RAN 20 and the PDSN 30. The A10 interface carries user traffic (user traffic) between the PCF and the PDSN, while the A11 interface carries signaling information between the PCF and the PDSN.

The PDSN 30 is responsible for the establishment, maintenance, and termination of point-to-point protocol (PPP) sessions with Mobile Stations (MSs). Point-to-point protocols are designed to provide router-to-router and host-to-network connectivity through synchronous and asynchronous circuits. In addition to supporting MIP functionality, the PDSN 30 may also assign dynamic IP addresses. The PDSN provides similar functionality as the GPRS Support Node (GSN) in GSM and UMTS networks.

The FA is a mobile agent on the foreign network that can assist the mobile node in receiving datagrams that are delivered to a care-of address (care-of address). The FA 32 is a node in a mobile IP (mip) network that enables roaming IP users to register on foreign networks. The FA 32 communicates with a Home Agent (HA)80 to enable IP datagrams to be communicated between the home IP network 80 and roaming IP subscribers on the foreign network 6.

A Packet Data Serving Node (PDSN)30 and a Foreign Agent (FA)32 are connected to the RADIUS server 40 and the IP network 60. The RADIUS server 40 is also connected to an IP network 60.

The IP network 60 is connected to a CN 70, a Home Agent (HA)80, and RADIUS servers 90, 100. RADIUS server 90 may be a proxy network (spoke network) and RADIUS server 100 may be a home IP network.

The CN 70 may be a private network (private network) which refers to a node that transmits or receives packets to or from a wireless terminal; the correspondent node may be another mobile node or a non-mobile internet node. NIDS assumes that the CN 70 is capable of addressing and sending IP packets to the wireless terminal 10 at a specified IP address.

The Home Agent (HA)80 may be a home IP network, a private network, or a home access provider network. The HA refers to a node on the home network 8 that makes the mobile node reachable at its home address even when the mobile node is not attached to its home network 8. The HA routes data to a mobile node currently connected to a foreign network through a tunneling procedure in which the data is transmitted to the mobile node using a care-of address (CoA). That is, when the mobile node is not connected to the home network, the CoA refers to an IP address at the current point at which the mobile node is connected to the internet. The CoA may be associated with FA 32, in this case referred to as FA CoA; or it may be a co-located care-of address (CCoA), meaning that the mobile node is allocated an IP address in the foreign network. Thus, the CCoA refers to a care-of address assigned to one of the network interfaces of the mobile node, rather than the care-of address provided by the FA 32.

The RAN 20 is also connected to a Mobile Switching Center (MSC)50 through an a1 interface. An MSC is a telecommunications switch or exchange within a cellular network structure that is capable of interacting with a location database (location database). Mobile Switching Center (MSC)50 is connected to HLR 120 via SS7 network 110. The Home Location Register (HLR)120 may be a home access provider network and a database within a Home Public Land Mobile Network (HPLMN) that provides routing information for Mobile Terminated (MT) calls and Short Message Services (SMS). The HLR also retains subscriber subscription information assigned to the associated VLR or Serving GPRS Support Node (SGSN) through attach procedures and mobility management procedures such as location area and routing area updates.

In NIDS, the wireless terminal 10 performs air interface registration with the network and is assigned an IP address to enable NIDS data to be received with either a static or dynamic IP address. The wireless terminal may then be reached while the wireless terminal is in a packet data unconnected state (e.g., no PPP session exists). When the wireless IP network 60 receives an IP packet addressed to the wireless terminal 10 from the CN 70, the wireless IP network can re-establish resources and transmit the packet to the wireless terminal 10. The network provides information allowing the wireless terminal 10 to filter the data being downloaded and accept or reject NIDS data. In a wireless terminal user profile, the network maintains a subscription state for the wireless terminal with respect to network-initiated data capabilities, and also maintains an activation identity for the NIDS service for the user. NIDS may support subscriber roaming and may use existing security mechanisms. The wireless terminal may reject NIDS requests received from the network. A subscription administrator may activate or deactivate NIDS services for a user.

Fig. 2 is a flow diagram of one embodiment of a method of conserving network resources in a network that initiates a data service by delivering push data to a dormant terminal. At step 410, selected network resources associated with the dormant terminal are released. In step 430, information for reaching the dormant terminal is retained. In step 450, information for reaching the dormant terminal is updated when the network attachment point of the dormant terminal is changed.

Fig. 3 is a flow diagram of another embodiment of a method of conserving network resources in a network that initiates a data service by delivering push data to a dormant terminal. A dormant terminal may comprise a dormant wireless device such as a dormant mobile station that is authorized by the network to initiate data services. Initially, the dormant terminal is connected to the network at the first connection point that is eventually changed. For example, the methods may be applied to a wide variety of systems, such as simple IPv4, simple IPv6, mobile IPv4, mobile IPv6, 1xRTT, and 1 xEV-DO.

Before step 510, an a10 connection may be established when the terminal is powered on, and if the terminal authentication is successful, the terminal profile information is transmitted and the terminal is assigned an IP address. Terminal profile information for reaching the dormant terminal is created. The terminal profile information may include NIDS Reachability Information (NRI) including at least one of a wireless terminal Network Access Identifier (NAI), a wireless terminal IP address, a PCF address, an access network id (anid), and a wireless terminal id (msid). A wireless terminal (MS) Network Access Identifier (NAI) uniquely identifies a user. The format of the network access identifier is similar to an email address. The PCF address is the IP address of a Packet Control Function (PCF) that uniquely identifies the PCF. The access network id (anid) uniquely identifies the PCF service area. The wireless terminal id (msid) uniquely identifies the device. An example of an MSID is an IMSI. In some embodiments, the NRI is less than 100 bytes per MS. For example, in one embodiment, the network access identifier of the wireless terminal (tens of bytes), the IP address of the wireless terminal (4 bytes for IPv4 and 16 bytes for IPv 6), the IP address of the PCF (4 bytes), the IMSI (60 bits), and the current access network ID (47 bits). Sending a message comprising a terminal network access identifier, a terminal IP address, a PCF address, an access network ID (anid) and a terminal ID, and updating the terminal IP address. A mapping between the terminal network access identifier, the terminal IP address and the network access identifier IP address is maintained.

At step 510, upon receiving a dormancy indication indicating that the terminal is dormant, the PPP state and a10 connection associated with the dormant terminal are released. PPP state and a10 connections are network resources allocated for users authorized for packet data connectivity. The PPP state contains information used to maintain a (PPP) connection between the wireless terminal and the PDSN. A10 connects user traffic carried between the PCF and the PDSN. The PCF is an entity in a radio access network that controls packet transmission between a Base Station (BS) and a Packet Data Serving Node (PDSN). The PPP state may be removed without sending a termination request to the terminal.

At step 530, information, such as NRI, for reaching the dormant terminal to transfer push data to the dormant terminal is retained at the packet data serving node. The push data may include, for example, a terminal IP address and a terminal mobility binding (mobility binding). In some embodiments, the PDSN 30 retains only minimal information, referred to as NIDS Reachability Information (NRI), regarding how to reach the wireless terminal to communicate push data.

In step 550, information for reaching the dormant terminal is updated when the network attachment point of the dormant terminal is changed. For example, when a terminal experiences an intra-PDSN handoff or an inter-PDSN handoff, the network attachment point of the dormant terminal changes. When a terminal undergoes an intra-PDSN handoff, a change is detected when a dormant terminal moves to a different radio access network. The a10 connection is established through a11 signaling, where the a11 signaling includes a previous access network ID, a current access network ID, a terminal ID, and a terminal sleep indication. Based on the terminal ID, NRI presence of the terminal is determined. Based on the received previous access network ID, it may be determined that an intra-PDSN handoff is in progress. When a dormant terminal moves to another radio access network while the terminal is undergoing an inter-PDSN handoff, a change is detected. The a10 connection is established through a11 signaling, where the a11 signaling also includes a previous access network ID, a current access network ID, a terminal ID, and a terminal sleep indication. When the terminal IP address has changed, the NRI of the dormant terminal is removed and the terminal IP address is released for future allocation. When a dormant wireless terminal 10 changes its point of network attachment, network knowledge about how to reach the wireless terminal is updated. In one embodiment, upon experiencing an intra-PDSN handoff, the access network ID in the NRI is updated with the current access network ID and a release of the a10 connection to the terminal is requested. The NIDS-supporting PDSN 30 need not maintain PPP state, compression state (header and/or PPP payload compression), a10 connection, etc.

After step 550, the network initiates a push data service by transmitting push data to the dormant terminal. The push data may comprise, for example, at least one of a terminal IP address and a terminal mobility binding. According to one embodiment, a terminal IP address is obtained and packets addressed to the terminal are routed to a node that manages the terminal IP address. The packet is then buffered and the terminal ID and PCF address are obtained from the NRI based on the destination IP address of the packet. Thereafter, the establishment of an a10 connection to the terminal is requested through a11 signaling, and after the a10 connection is established, PPP negotiation with the terminal is initiated. In the internet protocol control protocol, the same terminal IP address from the NRI is specified, and packets are transmitted to the dormant terminal through another radio access network. The a10 connection and PPP state may be released while the terminal NRI is retained.

Thus, if the dormant wireless terminal 10 is authorized for NIDS, the network conserves resources by releasing the PPP state and a10 connection associated with the wireless terminal 10, while retaining knowledge of how to reach the wireless terminal to deliver the push data, such as the IP address of the MS and mobility binding information. In IS-835-D, a new PDSN behavior IS specified for supporting NIDS, and a new 3GPP2-VSA IS specified for transmitting NIDS. These embodiments do not affect the air interface and wireless terminal behavior and have minimal impact on the IOS, requiring only the support of the dormant indicator in the a11 signaling and associated PCF behavior.

Exemplary Call flow

Exemplary call flows will now be described in which aspects of the invention are applied to simple IP, mobile IPv4, and mobile IPv 6. In the following example, it is assumed that the wireless terminal has subscribed to NIDS and IP Reachability Services (IRS).

A. Simple IP

Fig. 4A-4D are block diagrams of a network during NIDS for pushing data to a terminal. Fig. 4E is a call flow diagram of an embodiment of the present invention applied to simple IP. Fig. 4E depicts a simple IP NIDS procedure and how the network provides push services while conserving network resources including PPP state and a10 connection.

Initiation of packet data sessions

Fig. 4A is a block diagram of a network in the process of a network initiating a packet data session. Fig. 4A shows a wireless terminal 10, a first radio access network (RAN1)22, a first PDSN (PDSN1)32, an authentication, authorization, and accounting (AAA) entity 72, and a Domain Name Server (DNS) 74.

Upon power-up of wireless terminal 10, wireless terminal 10 issues SO 33 or SO 59, and RAN122 selects PDSN132 and establishes an a10 connection to PDSN 132. (step 1) wireless terminal 10 and PDSN132 negotiate a link control protocol. (step 2) the AAA 72 server authenticates the wireless terminal 10 through the challenge handshake authentication protocol or PPP authentication protocol. (step 3) if the authentication is successful, the AAA 72 server transmits profile information (e.g., NIDS, IRS) of the wireless terminal 10 to the PDSN132 through RADIUS Access-Accept (Access-Accept). (step 3) the wireless terminal 10 is assigned an IPv4 address (or IPv6 address prefix) through an internet protocol control protocol (or router advertisement). (step 4) because the wireless terminal 10 profile indicates NIDS, the PDSN132 creates NIDS Reachability Information (NRI) about the wireless terminal 10. (step 5) NRI is a mapping between wireless terminal 10 network access identifier, wireless terminal 10IP address, PCF address, access network ID (anid), and wireless terminal ID. The PDSN is made available to the wireless terminal ID (e.g., IMSI) and PCF address through a11 signaling for establishing an a10 connection. The process is the same for 1xRTT and 1 xEV-DO. In 1xEV-DO, if the authentication of the access network challenge handshake authentication protocol is successful, the access network AAA 72 server specifies the interim IMSI and passes it to the PCF via RADIUS access-accept so that the PCF may include the IMSI in the a11 signaling sent to the PDSN.

PDSN132 sends a RADIUS accounting Start (Account-Start) containing the network access identifier, address, etc. of wireless terminal 10. Because the wireless terminal 10 profile indicates an IRS, the AAA 72 server updates the wireless terminal 10IP address of the DNS 74 server. (step 6) the AAA 72 server also maintains a mapping between the wireless terminal 10 network access identifier, the wireless terminal 10IP address and the network access identifier IP address. After PPP is established, wireless terminal 10 may send/receive data, otherwise wireless terminal 10 will sleep. When RAN122 detects that wireless terminal 10 is dormant, RAN122 sends a dormancy indication to PDSN132 via a11 signaling. (step 7) upon receiving the dormant indication because wireless terminal 10 is NIDS indicated by the profile, PDSN132 removes the PPP state without sending a termination request to wireless terminal 10 and requests RAN122 to release the a10 connection. (step 8) however, PDSN132 reserves the NRI for wireless terminal 10; thus, PDSN132 does not have to return the wireless terminal 10 address to the pool of available addresses. PDSN132 sends a RADIUS accounting-Stop (Account-Stop) indicating that the AAA 72 server is not updating the DNS 74 server. (step 9) the indication may be, for example, a Session-Continue attribute as defined in IS-835.

Inter PDSN handoff

Fig. 4B is a block diagram of a network during a handoff within a PDSN. Fig. 4B shows the wireless terminal 10, the second radio access network (RAN2)24, and the first PDSN (PDSN1) 32. The dormant wireless terminal 10 moves to RAN224 and detects a change in PZID/SID/NID (or subnet change in the case of 1 xEV-DO). The wireless terminal 10 sends an Origination Message (Origination Message) with DRS position zero. RAN224 and PDSN132 are reachable. In this case, RAN224 establishes an a10 connection with PDSN132 via a11 signaling, where a11 signaling also includes the previous access network ID, the current access network ID, the wireless terminal ID, and a wireless terminal 10 dormant indication. (step 10) based on the wireless terminal ID, the PDSN132 determines that it has the NRI of the wireless terminal 10. Based on the received previous access network ID, PDSN132 determines that it is an intra-PDSN handoff, updates the access network ID in the NRI with the current access network ID, and requests RAN224 to remove the a10 connection for wireless terminal 10. (step 11) there is no PPP negotiation.

inter-PDSN handoff

Fig. 4C is a block diagram of the network during an inter-PDSN handoff. Fig. 4C shows the wireless terminal 10, a third radio access network (RAN3)25, a second PDSN (PDSN2)34, a first PDSN (PDSN1)32, an authentication, authorization, and accounting (AAA) entity 72, and a Domain Name Server (DNS) 74. The dormant wireless terminal 10 moves towards the RAN325 and detects a change in PZID/SID/NID (or subnet change in the 1xEV-DO case). The wireless terminal 10 transmits an origination message with DRS position zero. Assume that RAN325 and PDSN132 are not reachable. In this case, the RAN325 selects PDSN234 and establishes an a10 connection with PDSN234 via a11 signaling, where the a11 signaling also includes the previous access network ID, the current access network ID, the wireless terminal 10ID, and a wireless terminal 10 dormant indication. (step 12) after that, the above-described steps 2 to 9 are repeated. Next, the AAA 72 server perceives that the wireless terminal 10IP address has changed. Thus, the AAA 72 server sends a RADIUS disconnect request to the PDSN132 to remove the NRI of the wireless terminal 10 and release the wireless terminal 10IP address for future assignment. (step 14)

Pushing data

Fig. 4D is a network block diagram when data is being pushed to a wireless terminal. Fig. 4D shows the wireless terminal 10, the second PDSN (PDSN2)34, the Domain Name Server (DNS)74, and the Content Server (CS) 76. The Content Server (CS) wishes to push data to the wireless terminal 10. The CS 76 obtains the wireless terminal 10IP address via DNS 74 query/response. (step 15) the CS 76 sends packets addressed to the wireless terminal 10. The packet is routed to PDSN234, which manages the IP address of wireless terminal 10. (step 16) PDSN234 buffers the packet. Based on the packet's destination IP address, the PDSN234 obtains the wireless terminal ID and PCF address from the NRI. Through a11 signaling, the PDSN234 requests the RAN325 to establish an a10 connection to the wireless terminal 10. After a10 is established, PDSN234 initiates PPP negotiation (link control protocol, challenge handshake authentication protocol or PPP authentication protocol, internet protocol control protocol) with wireless terminal 10. In the internet protocol control protocol, the PDSN234 assigns the same wireless terminal 10IP address as the NRI. (step 17) RADIUS message exchanges for authentication and accounting start are not shown in this figure. PDSN234 communicates packets to wireless terminal 10 through RAN 325. (step 18) when the wireless terminal 10 becomes dormant, the RAN325 notifies the PDSN 234. As before, the a10 connection and PPP state in the PDSN234 is released, but the PDSN234 retains the NRI of the wireless terminal 10. The RADIUS message exchange for accounting stop is not shown in this figure.

B. Mobile IPv4

Fig. 5A-5D are block diagrams of another network in the process of pushing data to a NIDS of a terminal. Fig. 5E is a call flow diagram of an embodiment of the present invention as applied to mobile IPv 4. Fig. 5E depicts the zero state registration process of mobile IPv4 and how the network provides push services while conserving network resources (PPP state and a10 connection).

Initiating a packet data session

Fig. 5A is a block diagram of a network in the process of a network initiating a packet data session. Fig. 5A shows a wireless terminal 10, a first radio access network (RAN1)22, a first PDSN (PDSN1)32, a Home Agent (HA)80, an authentication, authorization, and accounting (AAA) entity 72, and a Domain Name Server (DNS) 74. AAA 72 securely determines the identity and privileges of a user and tracks the user's behavior. For ease of illustration, this document combines authentication, authorization, and accounting (AAA) and Push Gateway (PGW) into a single entity that performs the functions of AAA and push gateway. However, it should be understood that the AAA/PGW can be implemented as a separate entity.

After the wireless terminal 10 is powered on, the wireless terminal 10 sends out either the SO 33 or the SO 59. RAN122 selects PDSN132 and establishes an a10 connection to PDSN 132. (step 1) wireless terminal 10 and PDSN132 negotiate the link control protocol and internet protocol control protocol for each IS-835. (step 2) after establishing PPP, PDSN132 sends a mobile IP agent advertisement to wireless terminal 10. (step 3) the wireless terminal 10 performs mobile IP registration. If the foreign agent challenge verification is successful, the AAA 72 server transmits wireless terminal 10 profile information (e.g., NIDS) to the PDSN132 via RADIUS Access-Accept. If the registration is successful, the HA 80 transmits the home address of the wireless terminal 10 in a Mobile IP registration reply. Since the wireless terminal 10 profile indicates the IRS, the AAA 72 server or HA 80 performs an NDS 74 update. (step 4) the start of RADIUS accounting is not shown.

Because the wireless terminal 10 profile indicates NIDS, the PDSN132 creates NIDS Reachability Information (NRI) for the wireless terminal 10. NRI is a mapping between wireless terminal 10 network access identifier, wireless terminal 10IP address (i.e., home address), PCF address, access network ID (anid), and wireless terminal ID (step 5). The wireless terminal 10 may transmit/receive data or otherwise the wireless terminal 10 will sleep. When RAN122 detects that wireless terminal 10 is dormant, RAN122 sends a dormancy indication to PDSN132 via a11 signaling. (step 6) upon receiving the dormant indication because the wireless terminal 10 profile indicates IRS, PDSN132 removes the PPP state of wireless terminal 10 and requests RAN122 to release the a10 connection. PDSN132, however, maintains the NRI and visitor list (visitor list) of wireless terminal 10. The RADIUS accounting stops are not shown in this figure. (step 7)

Inter PDSN handoff

Fig. 5B is a block diagram of the network during a handoff within a PDSN. Fig. 5B shows the wireless terminal 10, the second radio access network (RAN2)24, and the first PDSN (PDSN1) 32. The dormant wireless terminal 10 moves towards RAN224 and detects a change in PZID/SID/NID (or subnet change in the 1xEV-DO case). The wireless terminal 10 sends an origination message with DRS position zero. RAN224 and PDSN132 are assumed to be reachable. In this case, RAN224 establishes an a10 connection with PDSN132 via a11 signaling, where a11 signaling also includes the previous access network ID, the current access network ID, the wireless terminal ID, and a wireless terminal 10 dormant indication. (step 8) based on the wireless terminal ID, the PDSN132 determines that it has the NRI of the wireless terminal 10. Based on the received previous access network ID, PDSN132 determines that it is an intra-PDSN handoff, updates the access network ID in the NRI with the current access network ID, and requests RAN224 to remove the a10 connection to wireless terminal 10. (step 9)

inter-PDSN handoff

Fig. 5C is a block diagram of a network for an inter-PDSN handoff process. Fig. 5C shows the wireless terminal 10, the third radio access network (RAN3)25, the second PDSN (PDSN2)34, the Home Agent (HA)80, the first PDSN (PDSN1)32, and the authentication, authorization, and accounting (AAA) entity 72. The dormant wireless terminal 10 moves towards the RAN325 and detects a change in PZID/SID/NID (or subnet change in the case of 1 xEV-DO). The wireless terminal 10 sends an origination message with DRS position zero. Assume that RAN325 and PDSN132 are not reachable. In this case, the RAN325 selects PDSN234 and establishes an a10 connection with PDSN234 through a11 signaling, wherein the a11 signaling also includes the previous access network ID, the current access network ID, the wireless terminal ID, and a wireless terminal 10 dormant indication. (step 10) step 11 is the same as steps 2 to 7 above, except that there is no DNS 74 update, and the description will not be repeated here for simplicity. (step 11) the HA 80 notifies: the wireless terminal 10 has changed PDSN/FA. Thus, HA 80 sends a mobile IP withdrawal to PDSN132 to remove visitor list entries and NRIs for wireless terminal 10. (step 12)

Pushing data

Fig. 5D is a network block diagram when data is being pushed to the wireless terminal. Fig. 5D shows the wireless terminal 10, the second PDSN (PDSN2)34, the Home Agent (HA)80, the Domain Name Server (DNS)74, and the Content Server (CS) 76. The Content Server (CS) wishes to push data to the wireless terminal 10. The CS 76 obtains the wireless terminal 10IP address via DNS 74 query/response. (step 13) the CS 76 sends packets addressed to the wireless terminal 10. The packets are routed to PDSN234 via the HA. PDSN234 buffers the packets. (step 14) based on the destination IP address of the packet, the PDSN234 obtains the wireless terminal ID and PCF address from the NRI. Through a11 signaling, the PDSN234 requests the RAN325 to establish an a10 connection to the wireless terminal 10. PDSN234 initiates PPP negotiation (LCP and internet protocol control protocol) with wireless terminal 10. Since PDSN234 already has the visitor list entry and NRI for wireless terminal 10, PDSN234 does not need to send a mobile IP agent advertisement after PPP is established. (step 15) the PDSN234 transmits the packets to the wireless terminal 10 via the RAN 325. (step 16) when the wireless terminal 10 is dormant, the RAN325 notifies the PDSN 234. As before, the a10 connection and PPP state in PDSN234 is released, but the PDSN234 maintains the NRI and visitor list entries for the wireless terminal 10.

Those of skill in the art would understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, electromagnetic fields or particles, optical fields or particles, or any combination thereof.

Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Such functionality may be implemented as hardware or software depending on the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

The various illustrative logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. For example, in mobile IPv6, the call flow would be similar to fig. 4E, with the following differences. After step 4, the wireless terminal 10 performs mobile IPv6 registration with the HA 80 (not shown). The wireless terminal 10 sends a binding update containing the new COA. The new COA is formed by appending an IPv6 address prefix (in the router advertisement sent by the PDSN in step 4) to the interface ID of the wireless terminal 10. In step 6, the DNS 74 need not be updated because the home address of the wireless terminal 10 is unchanged. DNS 74 updates are not required during inter-PDSN handoff (step 13). In step 16, data packets sent from CS 76 are routed to PDSN234 via HA 80 (not shown).

Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (51)

1. A network for providing push services while conserving network resources including PPP state and a10 connections, comprising:

a wireless terminal having an IP address associated therewith;

a first packet data service node which creates reachability information of the wireless terminal in response to the wireless terminal profile information; and

a first radio access network which, upon detecting that the wireless terminal is dormant, generates a dormancy indication, an

Wherein, upon receiving the dormancy indication, the first packet data serving node removes the PPP state and requests the first radio access network to release the A10 connection.

2. The network of claim 1, wherein the first packet data serving node retains reachability information for the wireless terminal.

3. The network of claim 1, further comprising:

an access network authentication, authorization, and accounting (AAA) server, wherein the first packet data service node receives wireless terminal profile information from the access network authentication, authorization, and accounting (AAA) server if the wireless terminal is authenticated.

4. The network of claim 1, wherein the first radio access network initially has an a10 connection with the first packet data serving node, and wherein the first radio access network detects that the wireless terminal is dormant and sends a dormancy indication to the first packet data serving node via a11 signaling.

5. The network of claim 4, wherein the packet data serving node is provided with a wireless terminal ID and PCF address for establishing the A10 connection via A11 signaling.

6. The network of claim 1, wherein the first packet data serving node creates reachability information for the wireless terminal if the wireless terminal profile indicates NIDS, and wherein the reachability information includes a mapping between a network access identifier, a wireless terminal IP address, a PCF address, an access network ID (anid), and a wireless terminal ID of the wireless terminal.

7. The network of claim 3, further comprising:

PCF, and

wherein if the authentication of the challenge handshake authentication protocol of the access network is successful, the access network AAA server assigns a temporary IMSI and transmits the temporary IMSI to the PCF via RADIUS access-accept so that the PCF can include the IMSI in the a11 signaling transmitted to the packet data serving node.

8. The network of claim 7, further comprising:

a Domain Name Server (DNS) that updates the wireless terminal IP address of the DNS server when the wireless terminal profile indicates the IRS and maintains a mapping between the wireless terminal network access identifier, the wireless terminal IP address, and the network access identifier IP address.

9. The network of claim 1, further comprising:

a second radio access network for a second radio access network,

when the dormant wireless terminal moves towards the second radio access network, the second radio access network establishes an a10 connection with the first packet data serving node through a11 signaling, wherein the a11 signaling also includes a previous access network ID, a current access network ID, a wireless terminal ID, and a wireless terminal dormant indication.

10. The network of claim 9, wherein the first packet data serving node determines that it has reachability information for the wireless terminal based on the wireless terminal ID.

11. The network of claim 10, wherein the first packet data serving node determines that an intra-PDSN handoff is occurring based on the previous access network ID, updates the access network ID in the reachability information with the current access network ID, and requests the second radio access network to remove an a10 connection to the wireless terminal.

12. The network of claim 1, further comprising:

a third radio access network; and

a second packet data serving node for the packet data,

when the dormant wireless terminal moves towards the third radio access network, the third radio access network selects the second packet data serving node and establishes an a10 connection to the second packet data serving node through a11 signaling, wherein the a11 signaling includes a previous access network ID, a current access network ID, a wireless terminal ID, and a wireless terminal dormant indication.

13. The network of claim 12, wherein the AAA server removes reachability information for the wireless terminal when the AAA server finds that the wireless terminal IP address has changed and releases the wireless terminal IP address for future assignment.

14. The network of claim 1, further comprising:

a content server that pushes data to the wireless terminal,

wherein the content server obtains the wireless terminal IP address and routes packets addressed to the wireless terminal to a second packet data serving node that manages the wireless terminal IP address,

wherein the second packet data service node obtains the wireless terminal ID and PCF address from the reachability information based on the destination IP address of the packet.

15. The network of claim 14, further comprising:

a third radio access network, wherein the first radio access network is a cellular radio network,

wherein the second packet data serving node requests the third radio access network to establish an A10 connection to the wireless terminal through A11 signaling, and

after the a10 connection is established, the second packet data serving node initiates PPP negotiation with the wireless terminal and assigns the same wireless terminal IP address from the reachability information.

16. The network of claim 15, wherein the second packet data serving node transmits packets to the wireless terminal through the third radio access network, and

the third radio access network notifies the second packet data serving node when the wireless terminal is dormant, and wherein the second packet data serving node releases the a10 connection and PPP state and retains reachability information for the wireless terminal.

17. The network of claim 4, further comprising:

the home agent is a proxy for the home agent,

wherein the first packet data serving node sends a mobile IP agent advertisement to the wireless terminal and the wireless terminal performs mobile IP registration, an

If the foreign agent challenge verification is successful, the AAA server transmits wireless terminal profile information to the first packet data service node, an

If the registration is successful, the home agent transmits the home address of the wireless terminal in a Mobile IP registration reply.

18. The network of claim 1, wherein the first packet data serving node creates reachability information for the wireless terminal because the wireless terminal profile indicates the NIDS, and wherein the reachability information includes a mapping between a network access identifier, a wireless terminal home address, a PCF address, an access network ID (anid), and a wireless terminal ID of the wireless terminal.

19. The network of claim 2, wherein the first packet data service node retains reachability information and visitor list items of the wireless terminal.

20. The network of claim 14, further comprising:

a content server; and

the home agent is a proxy for the home agent,

when the home agent perceives that the wireless terminal has changed PDSN/FA, the home agent sends Mobile IP revocation to the first packet data serving node to remove visitor list entry and reachability information for the wireless terminal, an

Wherein the content server obtains the wireless terminal IP address and routes packets addressed to the wireless terminal to the second packet data serving node via the home agent.

21. The network of claim 16, the third radio access network notifying the second packet data serving node when the wireless terminal is dormant, and wherein the second packet data serving node releases the a10 connection and the PPP state and retains reachability information and visitor list entries for the wireless terminal.

22. The network of claim 1, further comprising:

a home agent, wherein the wireless terminal performs registration with the home agent by sending a binding update to the home agent that includes a new care-of address, wherein the new care-of address includes an IPv6 address prefix and a wireless terminal interface ID.

23. The network of claim 22, further comprising:

a content server that routes packets addressed to the wireless terminal to the home agent and then to the second packet data serving node that manages the IP address of the wireless terminal.

24. A method of providing push data services to dormant terminals in a network while conserving network resources, comprising:

releasing the selected network resources associated with the dormant terminal;

reserving terminal profile information for reaching the dormant terminal; and

updating the terminal profile information for reaching the dormant terminal when the network attachment point of the dormant terminal changes.

25. The method of claim 24, wherein releasing the selected network resources associated with the dormant terminal comprises:

removing the PPP state; and

upon receiving a sleep indication indicating that the terminal is asleep, the a10 connection is released.

26. The method of claim 24, wherein the terminal profile information includes NIDS Reachability Information (NRI) of the terminal including an access network id (anid), and wherein updating the terminal profile information for reaching the dormant terminal when a network attachment point of the dormant terminal changes comprises:

the access network ID in the NRI is updated with the current access network ID and, once an intra-PDSN handoff is experienced, a release of the a10 connection to the terminal is requested.

27. The method of claim 26, wherein reserving terminal profile information for reaching the dormant terminal comprises:

the NRI is reserved for reaching the dormant terminal.

28. The method of claim 24, wherein the terminal profile information for reaching the dormant terminal includes a mapping between at least two of a terminal network access identifier, a terminal IP address, a PCF address, an access network ID (anid), and a terminal ID.

29. The method of claim 24, wherein the terminal profile information for reaching the dormant terminal includes a mapping between at least two of a terminal network access identifier, a terminal IP address, a PCF address, an access network ID (anid), and a terminal ID.

(28, 29 the same)

30. The method of claim 26, wherein the terminal profile information for reaching the dormant terminal further includes a mapping between the ANID and a terminal IP address.

31. The method of claim 30, wherein the terminal profile information for reaching the dormant terminal further includes a mapping between the ANID, the terminal IP address, and a terminal network access identifier.

32. The method of claim 31, wherein the terminal profile information for reaching the dormant terminal further includes a mapping between the ANID, the terminal IP address, the terminal network access identifier, and a terminal ID.

33. The method of claim 24, further comprising:

the push of the data to the terminal is performed,

wherein the push data comprises at least one of a terminal IP address and a terminal mobility binding.

34. The method of claim 24, wherein the push data includes a terminal IP address and a terminal mobility binding.

35. The method of claim 24, wherein the dormant terminal is initially connected to the network at a varying first connection point.

36. The method of claim 24, further comprising:

when the terminal is powered on, an A10 connection is established;

authenticating the terminal and, if the authentication is successful, transmitting terminal profile information; and

an IP address is assigned to the terminal.

37. The method of claim 36, further comprising:

terminal profile information for reaching the dormant terminal is created in response to an indication from the terminal that the network is initiating a packet data session.

38. The method of claim 37, wherein the terminal profile information includes NIDS Reachability Information (NRI) of the terminal including a mapping between a terminal network access identifier, a terminal IP address, a PCF address, an access network ID (anid), and a terminal ID, said method further comprising:

sending a message including the terminal network access identifier, terminal IP address, PCF address, access network ID (anid), and the terminal ID;

updating the IP address of the terminal; and

a mapping between the terminal network access identifier, the terminal IP address and the network access identifier IP address is maintained.

39. The method of claim 25, wherein removing PPP state comprises:

the PPP state is removed without sending a termination request to the terminal.

40. The method of claim 26, wherein reserving NRI for reaching the dormant terminal comprises:

the NRI for reaching the dormant terminal is reserved at the packet data serving node to transmit the push data to the dormant terminal.

41. The method of claim 26, when the terminal undergoes an intra-PDSN handoff, further comprising:

detecting a change when the dormant terminal moves to a different radio access network;

establishing an a10 connection through a11 signaling including a previous access network ID, a current access network ID, a terminal ID, and a terminal sleep indication;

determining that an NRI of the terminal exists based on the terminal ID; and is

Based on the received previous access network ID, it is determined that an intra-PDSN handoff is occurring.

42. The method of claim 41, when the terminal undergoes an inter-PDSN handoff, further comprising:

a change is detected when the dormant terminal moves towards another radio access network.

43. The method of claim 42, further comprising:

the a10 connection is established through a11 signaling that also includes a previous access network ID, a current access network ID, a terminal ID, and a terminal dormant indication.

44. The method of claim 43, further comprising:

when the terminal IP address has changed, the NRI of the dormant terminal is removed and the terminal IP address is released for future assignment.

45. The method of claim 44, wherein pushing data to the terminal further comprises:

obtaining the terminal IP address and transmitting a packet addressed to the terminal;

routing packets addressed to the terminal to a node that manages the IP address of the terminal;

buffering the packet;

obtaining the terminal ID and PCF address from the NRI based on the destination IP address of the packet;

requesting the establishment of an a10 connection for the terminal through a11 signaling, and initiating PPP negotiation with the terminal after the a10 connection is established;

in an internet protocol control protocol, allocating the same terminal IP address from the NRI;

transmitting a packet to the dormant terminal through another radio access network;

releasing the a10 connection and PPP state; and

the NRI of the terminal is retained.

46. The method of claim 37, further comprising:

after PPP is established, a mobile IP agent notice is sent to the terminal; and

mobile IP registration is performed, wherein if authentication is successful, NRI is transmitted.

47. The method of claim 46, further comprising:

if the registration is successful, the terminal home address is transmitted in a Mobile IP registration reply.

48. The method of claim 27, wherein reserving NRIs for reaching the terminal comprises:

the NRI and visitor list items are reserved for reaching the terminal.

49. The method of claim 40, wherein reserving the NRI for reaching the terminal comprises:

the NRI and visitor list items are reserved for reaching the terminal.

50. The method of claim 40, when the terminal undergoes an inter-PDSN handoff, further comprising:

mobile IP revocation is sent to remove the visitor list entry and NRI for the terminal.

51. The method of claim 36, further comprising:

mobile IP registration is performed by sending a binding update.