SERVICE BASED BEARER CONTROL AND TRAFFIC FLOW TEMPLATE OPERATION WITH MOBILE IP

Description

[0001] This application claims benefit under 35 U.S.C §119(e) of provisional application No. 60/576,406, filed on June 3, 2004 and provisional application No. 60/588,347, filed on July 16, 2004.

BACKGROUND OF THE INVENTION:

Field of the Invention:

[0002] The present invention relates to method for solving Mobile IP related filtering issues and more particularly to a method for creating filters that allow for the use of care-of-address by a mobile station and a correspondent node.

Description of the Related Art:

[0003] US 2002/0080752 discloses a route optimization technique requiring no awareness of the Mobile IP protocol by a Correspondent Node when forwarding traffic using the shortest path between a Mobile Node and the Correspondent Node in a visiting domain. The management of route entries, network address translations and firewall filters is disclosed. A Foreign Agent (FA) includes a filter state table for filtering traffic. The mobile node filters are distributed to FA as part of mobile-IP registration.

[0004] In cdma2000 networks, a Packet Data Serving Node (PDSN) acts as an access node for a mobile station and creates a number of filters for active sessions associated with the mobile station. Specifically, there are two types of filters in the PDSN. The first type includes Service Based Local Policy (SBLP) filters that are set up by the network for Multimedia Messaging Service (MMS). These filters are based on the subscriber profile of the mobile station and are set up by a Policy Decision Function (PDF) associated with the PDSN. The second type includes Traffic Flow Template (TFT) that is set up by the mobile station for traffic flows. These filters provide specific flow treatment to each session between the mobile station and the PDSN. As such, the PDSN does not allow any un-authorized traffic that does not match any of the filters to be forwarded to or from the mobile station. Typically, the filters have source and destination addresses/ports as selectors in order to be able to identify the flows.

[0005] When using Mobile IP, the mobile station uses its home address during Session Initiation Protocol (SIP) negotiation for a session between the mobile station and a correspondent node. Thus, the SBLP filters set up by Proxy Call Session Control Function (P-CSCF) and PDF include the home addresses of the mobile station and the correspondent node. However, the mobile station is assigned a care-of-address from a visited network in addition to its home address when the mobile station is using Mobile IP. Thereafter, all traffic sent by the mobile station has the care-of-address as the source address. Similarly, traffic from the correspondent node includes the mobile station's care-of-address as the destination address. As such, the information in the packets from the mobile station does not match any of the filters set up at the PDSN and the packets are dropped by the PDSN.

[0006] The problem described above becomes worse when the correspondent node is also a mobile node and uses its care-of-address as the source address. In addition to packets from the mobile station being dropped by the PDSN, when the correspondent node uses its care-of-address as the source address, packets from the correspondent node also do not match any of the filters at the PDSN that have the correspondent node's home address. Moreover, even in solutions where the PDSN somehow updates the filters with the correspondent node's care-of-address, if the correspondent node moves and attaches to a new IP subnet, then its care-of-address changes in the middle of a session causing packets with the new care-of-address to not match the source address in the filters of the PDSN and the PDSN to drop the packets.

[0007] In one example that further describes the problem outlined above, during the session between the correspondent node and the mobile station, the correspondent node performs return routablility and route optimization functions and sends a Care-of-Test init message to the mobile station. The message includes the correspondent node's care-of-address in the source field. As such, the source address for the correspondent node in the message does not match the information in the SBLP filters that was established during SIP negotiation, causing the PDSN to drop the packet. Hence, the mobile station will not receive the message and the return routablility and route optimization functions will fail.

[0008] One solution to the problem identified above is to map the packet to a default service instance at the PDSN. This causes the packet to reach the mobile station so that the return routablility and route optimization functions can proceed as normal. If the route optimization function succeeds, all subsequent packets from the correspondent node to the mobile station will have the correspondent node's care-of-address in the source field. This solution, however, causes a permanent failure of the SBLP filter and makes the mobile station vulnerable to Denial-of-Service attacks because any sender with a malicious intent can flood the mobile station with junk IP packets using any source address. Furthermore, destination packets will also have the correspondent node's care-of-address instead of its home address. However, if packets from the mobile station to the correspondent node do not include the correspondent node's home address, the PDSN will not allow the packets to be forwarded to the correspondent node.

[0009] The problem is slightly different with TFT filters. When the mobile station sets up TFT filters, it uses the correspondent node's home address. When the correspondent node sends packets using its care-of-address as the source address, these packets will not match the TFT filters at the PDSN and hence will not get the right flow treatment.

SUMMARY OF THE INVENTION

[0010] There is provided a method, a Packet Data Serving Node and a mobile station as defined by the appended claims.

[0011] According to one aspect of the invention, there is provided a method for updating filters, at a Packet Data Serving Node, with a care-of-address associated with at least one of a mobile station or a correspondent node. The method includes the steps of implementing a soft filtering rule at a Packet Data Serving Node and receiving, by the Packet Data Serving Node, a care-of-address that is associated with at least one the mobile station and a correspondent node. The method also includes updating, by the Packet Data Serving Node, filters with the care-of-address to correctly identify flows belonging to a particular session during Mobile IP use. The method further includes filtering, by the Packet Data Serving Node, packets including a care-of-address that is associated with one of the mobile station and the correspondent node.

[0012] According to another aspect of the invention there is provided a network node for updating filters with a care-of-address associated with at least one of a mobile station or a correspondent node. The network node includes implementing means for implementing a soft filtering rule and receiving means for receiving a care-of-address that is associated with at least one a mobile station and a correspondent node. The network node also includes updating means for updating filters with the care-of-address to correctly identify flows belonging to a particular session during Mobile IP use. The network node further includes filtering means for filtering packets including a care-of-address that is associated with one of the mobile station and the correspondent node.

[0013] According to another aspect of the invention, there is provided an apparatus for updating filters, at a Packet Data Serving Node, with a care-of-address associated with at least one of a mobile station or a correspondent node. The apparatus includes implementing means for implementing a soft filtering rule at a Packet Data Serving Node. The apparatus also includes receiving means for receiving, by the Packet Data Serving Node, a care-of-addresses associated with at least one of the mobile station and a correspondent node. The apparatus further includes updating means for updating, by the Packet Data Serving Node, filters with the care-of-address to correctly identify flows belonging to a particular session during Mobile IP use. The method also includes filtering means for filtering, by the Packet Data Serving Node, packets including the care-of-address that is associated with one of the mobile station and the correspondent node.

BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention that together with the description serve to explain the principles of the invention, wherein:

Figure 1 illustrates a wireless network 100 that can be used in an embodiment of the invention; and

Figure 2 illustrates the steps implemented in an embodiment of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT(S)

[0015] Reference will now be made to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings.

[0016] Figure 1 illustrates a wireless network 100 that can be used in an embodiment of the invention. Network 100 includes a mobile station 102, a correspondent node 104, a Packet Data Serving Node (PDSN) 106 and a Policy Decision Function 108. Mobile station 102 is a part of a wireless network that is running Internet Protocol version 6 (IPv6) and mobile station 102 configures its IPv6 address with a prefix from PDSN 106. During SIP negotiation for a session between mobile station 102 and correspondent node 104, correspondent node 104 uses its home address as the connection address and the mobile station uses its IPv6 address as the connection address. Policy Decision Function 108 then sends a Service Based Local Policy (SBLP) filter set to PDSN 106 for PDSN 106 to apply the SBLP filter on bearer flows associated with the negotiated session. As such the SBLP filter set includes correspondent node's home address as its source and destination address. Additionally, mobile station 102 send a Traffic Flow Template (TFT) to PDSN 106 to map the resulting flow(s) to desired service instances. The TFT also includes the correspondent node's home address as its source address.

[0017] To resolve issues relating to matching filters in PDSN 106 with care-of-addresses associated with mobile station 102 and correspondent node 104 during Mobile IP, one embodiment of the invention requires PDSN 106 to be aware of the home addresses and care-of-address of mobile station 102 and correspondent node 104 at all times to be able to match the IP flows with the filters. Specifically, PDSN 106 is required to know the mobile station's home address, the mobile station's care of address, the correspondent node's home address and the correspondent node's care of address, if the correspondent node is also a mobile node, at all times. This embodiment therefore requires that the PDSN's filters be updated once mobile station 102 knows its care-of-address and its home address. The filters also need to be updated every time correspondent node 104 moves and acquires a new care of address.

[0018] An embodiment of the invention provides a generic solution to solve Mobile IP related SBLP and TFT operation issues. A soft filtering rule has been installed in PDSN 106 to allow Mobility Header messages.

[0019] Specifically, the soft rule installed in the PDSN allows one message every 400 seconds per Mobility Header message type. If Mobility Header messages are sent more often, they are dropped by the PDSN. The 400 seconds is based on the fact that the maximum binding lifetime for return routability mechanisms is 420 seconds. However, the embodiment of the invention allows for a configurable parameter in place of the 400 seconds on PDSN 106. Therefore, as is apparent to one of ordinary skill in the art an operator may use different values.

[0020] According to another embodiment of the invention, if mobile station 102 and correspondent node 104 already have an active route optimised session, the soft rule can be modified to allow one message every one minute per Mobility Header message type per mobile station 102 care-of-address. This is based on the assumption that mobile nodes do not move more often than one minute. This soft rule allows Route Optimization and Mobile IP signalling messages to be initiated by mobile nodes from outside the CDMA network. The invention limits mobility header messages to avoid dropping by PDSN 106.

[0021] In addition to the soft rule outlined above, once mobile station 102 knows the set of possible addresses that might appear on its IP sessions, mobile station 102 sends a care-of-address update message to PDSN 106 for PDSN 106 to update the filters specific to mobile station 102. Mobile station 102 also informs PDSN 106 whenever the care-of-address of correspondent node 104 changes. Specifically, if correspondent node 104 is also a mobile node and acquires a new care of address, correspondent node 104 updates mobile station 102 with its new care-of-address as part of Mobile IP operation. The soft rule described in an embodiment of the invention allows return routability messages from the new care-of-address of correspondent node 104 to reach mobile station 102. Mobile station 102 then sends a message to PDSN 106 to update the filters. The invention therefore allows for the use of a care-of-address update message to update filters which are specific to mobile station 102. PDSN 106 uses the care-of-address information, in addition to available SBLP parameters, to match packets against the filters. This allows PDSN 106 to correctly identify the flows belonging to a particular session when Mobile IP is used. Specifically, PDSN 106 uses the care-of-address information for matching the filters against incoming and outgoing packets when Mobile IP is used.

[0022] In cdma2000 networks, mobile station 102 and PDSN 106 always establish a PPP link. According to embodiments of the invention, the care-of-address update message can utilize vendor specific extensions, RSVP messages, or other update message types which are appropriate for a particular application. In one embodiment, mobile station 102 uses a PPP Vendor Specific Packet to update the filters at PDSN 106. According to another embodiment of the invention, mobile station 102 uses Resv and ResvConf messages for TFT filter establishment at PDSN 106. These messages may be reused to send the Filter Update message that is defined in the TFT. Specifically, mobile station 102 may use the Resv message to send the filter update to PDSN 106. When PDSN 106 receives a care-of-address update message from mobile station 102, it updates the care-of-address information, if any, attached to both SBLP and TFT filters specific to mobile station 102. According to an embodiment, PDSN 106 never replaces the IP address found in the filters with the care-of-address address.

[0023] The discussion above is based on the assumption that PDSN 106 accepts the filter update messages from mobile station 102. In some cases, however, PDSN 106 might refuse to update filters created by PDF 108 without explicit authorization from PDF 108 prior to updating the filters. In these cases, mobile station 102 sends a filter update RSVP message along with a token that identifies mobile station 102 to PDF 108. PDSN 106 sends an authorization request that includes the token sent by mobile station 102 in the RSVP message. PDF 108 determines that the authorization request from mobile station 102 is for filters associated with the care-of-address of correspondent node 104. Thereafter, PDF 108 sends an authorization response to PDSN 106, which enables PDSN 106 to update the filters with the care-of-address of correspondent node 104.

[0024] The invention may also include a configuration wherein after correspondent node 104 starts using a new care-of-address, PDSN 106 checks the data packets to observe a change of care-of-address. In an embodiment, PDSN 106 may observe a predefined number of packets with the new care-of-address / home address association before it updates the care-of-address information attached to the filters.

[0025] The invention may also include a configuration wherein PDSN 106 creates a temporary state upon detecting a binding update message from correspondent node 104. In such a configuration, mobile station 102 may then send a binding acknowledgement to assure the network that a valid binding update was received. PDSN can then update the care-of-address information attached to the packet filters. Specifically, PDSN 106 creates a temporary state upon detecting a Binding Update message from correspondent node 104. Thereafter, when mobile station 102 sends a Binding Acknowledgement message with an indication of success, the network is assured that the Binding Update message was a valid, and PDSN 106 can update the care-of-address information attached to the packet filters.

[0026] The invention can also include a configuration wherein filter matching is performed at the PDSN 106. The SBLP and TFT are initially set to match the home addresses of mobile station 102 and correspondent node 104. When correspondent node 104 (or the mobile station 102) starts using a care of address, packets from mobile station 102 and correspondent node 104 will not match the filters set at the PDSN. If the correspondent node moves, it initiates return routability signaling to update mobile station 102. After return the routability signaling is complete, correspondent node 104 starts using the new care of address. Correspondent node 104 uses the care-of-address to communicate with mobile station 102, whenever Mobile IP is used, and PDSN 106 performs the appropriate filter matching. Specifically, in the downlink direction, the source IP address part of a filter is considered a match with a packet in the downlink direction when the IP address matches the source field of the IP packet; or the IP address matches the home address field of the Destination Options extension header and the care-of-address of correspondent node 104 matches the source field of the packet. In the uplink direction, the destination IP address part of a filter is considered a match with a packet in the uplink direction when the IP address matches the destination field of the IP packet or the IP address matches the home address field of the routing extension header and the care-of-address of the correspondent node matches the destination field of the packet. Note that the care-of-address of correspondent node 104 is available at the PDSN and updated by mobile station 102 as described above. As is apparent to one skilled in the art, other matching configurations may be within the scope of the invention as defined by the appended claims.

[0027] Figure 2 illustrates the steps implemented in an embodiment of the present invention. In Step 2010, PDSN 106 implements the soft filtering mechanism of the present invention. In Step 2020, when mobile station 102 knows its home address and care-of-address and correspondent node's home address and care-of-address, mobile station 102 implements the filter update message. In Step 2030, mobile station 102 may have to implement the token authorization mechanism if PDSN 106 does not accept un-authorized updates to SPLP filters. In Step 2040, when PDSN 106 receives the filter update message from mobile station 102, PDSN 106 updates the filters that correspond to mobile station 102 if PDSN 106 does not require authorization from the PDF 108. In Step 2050, if updating the filters requires PDF 108 authorization, PDSN 106 sends a RADIUS message to PDF 108 to verify that mobile station 102 is allowed to update the filters. In Step 2060, PDF 108 verifies the token presented by mobile station 102 and sends an authorization message to PDSN 106 in order for PDSN 106 to update the filters that correspond to mobile station 102.

[0028] One having ordinary skill in the art will readily understand that the invention as discussed above may be practiced with steps in a different order, and/or with hardware elements in configurations which are different than those which are disclosed. Therefore, although the invention has been described based upon these preferred embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the scope of the invention. In order to determine the metes and bounds of the invention, therefore, reference should be made to the appended claims.

Claims

1. A method for updating filters with a care-of-address associated with at least one of a mobile station (102) or a correspondent node (104), wherein the filters are at a Packet Data Serving Node (106) of a wireless network (100), and said Packet Data Serving Node acts as an access node for the mobile station (102) of the wireless network (100) wherein said filters are for filtering traffic to or from the mobile station (102) at the Packet Data Serving Node (106), and the method comprises the steps of:

implementing a soft filtering rule at the filters of the Packet Data Serving Node (106), wherein the step of implementing comprises allowing at least one Mobility header message at a predetermined time, wherein the predetermined time is a configurable parameter;

receiving, by a Packet Data Serving Node (106) from the mobile station (102), a care-of-address associated with at least one of the mobile station (102) and a correspondent node (104); and

updating, by the Packet Data Serving Node (106), filters with the care-of-address to correctly identify flows belonging to a particular session during Mobile IP use.

2. The method of claim 1, wherein the filtering comprises providing specific flow treatment to each session between the mobile station (102) and the Packet Data Serving Node (106).

3. The method of claim 1, wherein the predetermined time is 400 seconds.

4. The method of claim 1, wherein the step of implementing comprises allowing one message at a predetermined time per Mobility header message type for each mobile station's (102) care-of-address, if the mobile station (102) and the correspondent node (104) have an active route optimized session.

5. The method of claim 1 wherein the step of implementing comprises initiating route optimization and Mobile IP signaling messages by mobile nodes outside of a CDMA network.

6. The method of claim 1, wherein the step of receiving comprises receiving, from the mobile station (102), a care-of-address update message when the mobile station (102) knows a set of possible addresses that might appear on an IP session that is associated with the mobile station (102).

7. The method of claim 6, wherein the step of receiving comprises receiving the care-of-address update message in one of vendor specific extensions, RSVP messages or other message types from the mobile station (102).

8. The method of claim 7, wherein the step of receiving comprises informing the mobile station (102) of a newly acquired care-of-address by the correspondent node (104).

9. The method of claim 1, wherein the step of receiving comprises receiving a token that identifies the mobile station (102), wherein if the Packet Data Serving Node (106) requires authorization prior to performing the step of updating, the Packet Data Serving Node (106) forwards the token to a Policy Decision Function (108) which uses the token to determine if authorization is appropriate and provides an appropriate response to the Packet Data Serving Node (106).

10. The method of claim 1, wherein the step of updating comprises updating a Service Based Local Policy and a Traffic Flow Template.

11. The method of claim 1, comprising, after the correspondent node (104) starts using a new care-of-address, checking a predefined number of data packets, by the Packet Data Serving Node (106), to observe a change of the care-of-address, prior to the step of updating.

12. The method of claim 1, comprising:

creating a temporary state, by the Packet Data Serving Node (106), upon detecting a binding update message from the correspondent node (104); and

receiving a binding acknowledgement message from the mobile station (102) to verify that the binding update message is valid, prior to the step of updating.

13. The method of claim 1, wherein the step of filtering comprises matching a source IP address part of a filter with a packet in a downlink direction when at least one of the source IP address matches a source field of an IP packet or the source IP address matches a home address of a Destination Options extension header and the care-of-address of the correspondent node (104) matches the source field of the packet.

14. The method of claim 1, wherein the step of filtering comprises matching a destination IP address part of a filter with a packet in a uplink direction when at least one of a IP address matches a destination field of an IP packet or the IP address matches a home address of a routing extension header and the care-of-address of the correspondent node (104) matches the destination field of the packet.

15. A Packet Data Serving Node (106) for updating filters with a care-of-address associated with at least one of a mobile station (102) or a correspondent node (104), wherein the filters are at the Packet Data Serving Node (106) of a wireless network (100), and said Packet Data Serving Node (106) acts as an access node for the mobile station (102) of the wireless network (100) wherein said filters are for filtering traffic to or from the mobile station (102) at the Packet Data Serving Node (106), and the apparatus (106) comprises:

implementing means for implementing a soft filtering rule at the filters of the Packet Data Serving Node (106), wherein the implementing means comprises allowing means for allowing at least one Mobility header message at a predetermined time, wherein the predetermined time is a configurable parameter;

receiving means for receiving, by the Packet Data Serving Node (106) from a mobile station (102), a care-of-address that is associated with at least one of the mobile station (102) and a correspondent node (104);

updating means for updating, by the Packet Data Serving Node (106), filters with the care-of-address to correctly identify flows belonging to a particular session during Mobile IP use.

16. A Packet Data Serving Node of claim 15, wherein the filtering comprises providing specific flow treatment to each session between the mobile station (102) and the Packet Data Serving Node (106).

17. A Packet Data Serving Node according to claim 15 comprising:

filtering means for filtering packets, by the Packet Data Serving Node, including a care-of-address that is associated with one of the mobile station (102) and the correspondent node (104).

18. A Packet Data Serving Node of claim 17, wherein the implementing means comprises allowing means for allowing one message at a predetermined time per Mobility header message type for each mobile station's (102) care-of-address, if the mobile station (102) and the correspondent node (104) have an active route optimized session.

19. A Packet Data Serving Node of claim 17, wherein the implementing means comprises initiating means for initiating route optimization and Mobile IP signaling messages by mobile nodes outside of a CDMA network.

20. A Packet Data Serving Node of claim 17, wherein the receiving means receives, from the mobile station (102), a care-of-address update message when the mobile station (102) knows a set of possible addresses that might appear on an IP session that is associated with the mobile station (102).

21. A Packet Data Serving Node of claim 17, wherein the receiving means receives a care-of-address update message in one of vendor specific extensions, RSVP messages or other message types.

22. A Packet Data Serving Node of claim 17, wherein the receiving means receives a newly acquired care-of-address sent by the correspondent node (104) to the mobile station (102).

23. A Packet Data Serving Node of claim 17, wherein the receiving means receives a token that identifies the mobile station (102), wherein if the Packet Data Serving Node (106) requires authorization prior to performing the step of updating, the Packet Data Serving Node (106) forwards the token to a Policy Decision Function (108) which uses the token to determine if authorization is appropriate and provides an appropriate response to the Packet Data Serving Node (106).

24. A Packet Data Serving Node of claim 17, wherein the updating means updates a Service Based Local Policy and a Traffic Flow Template.

25. A Packet Data Serving Node of claim 17, further comprising checking means for checking, after the correspondent node (104) starts using a new care-of-address, a predefined number of data packets to observe a change of the care-of-address, prior to the step of updating.

26. A Packet Data Serving Node of claim 17, further comprising creating means for creating a temporary state upon detecting a binding update message from the correspondent node (104); and receiving means for receiving a binding acknowledgement message from the mobile station (102) to verify that the binding update message is valid, prior to the step of updating.

27. A Packet Data Serving Node of claim 17, wherein filtering means comprises matching means for matching a source IP address part of a filter with a packet in a downlink direction when at least one of the source IP address matches a source field of an IP packet or the source IP address matches a home address of a Destination Options extension header and the care-of-address of the correspondent node (104) matches the source field of the packet.

28. A Packet Data Serving Node of claim 17, wherein filtering means comprises matching means for matching a destination IP address part of a filter with a packet in a uplink direction when at least one of a IP address matches a destination field of an IP packet or the IP address matches a home address of a routing extension header and the care-of-address of the correspondent node (104) matches the destination field of the packet.

29. A mobile station (102) for updating filters of a Packet Data Serving Node (106) of a wireless network with a care-of-address associated with at least one of the mobile station (102) or a correspondent node (104), wherein the mobile station (102) comprises means for:

receiving a care-of-address associated with at least one Internet Protocol session of the mobile station (102) in a Mobility header message filtered by the Packet Data Serving Node using the filters implemented to allow at least one Mobility header message at a predetermined time;

determining on the basis of the received care-of-address a set of possible addresses of the mobile station and the correspondent node that might appear on the at least one Internet Protocol session that is associated with the mobile station (102); and

sending a care-of-address update message to update the filters specific to the mobile station at the PDSN, when the set of possible addresses is changed by the received care-of-address, for updating the filters with the care-of-address to correctly identify flows belonging to the at least one Internet protocol session during Mobile IP use.

Ansprüche

1. Verfahren zum Aktualisieren von Filtern mit einer Care-of-Adresse, die einer mobilen Station (102) und/oder einem entsprechenden Knoten (104) zugeordnet ist, wobei sich die Filter bei einem Paketdatendienstknoten (106) eines drahtlosen Netzes (100) befinden und der Paketdatendienstknoten als ein Zugriffsknoten für die mobile Station (102) des drahtlosen Netzes (100) wirkt, wobei die Filter zum Filtern von Verkehr zu oder von der mobilen Station (102) bei dem Paketdatendienstknoten (106) dienen und das Verfahren die folgenden Schritte umfasst:

Implementieren einer schwachen Filterregel an den Filtern des Paketdatendienstknotens (106), wobei der Schritt des Implementierens umfasst, mindestens eine Mobilitätsdateikopfnachricht zu einer vorgegebenen Zeit zuzulassen, wobei die vorgegebene Zeit ein konfigurierbarer Parameter ist;

Empfangen durch einen Paketdatendienstknoten (106) von der mobilen Station (102) einer Care-of-Adresse, die der mobilen Station (102) und/oder einem entsprechenden Knoten (104) zugeordnet ist; und

Aktualisieren durch den Paketdatendienstknoten (106) von Filtern mit der Care-of-Adresse, um Flüsse, die zu einer bestimmten Sitzung während der Verwendung der mobilen IP gehören, korrekt zu identifizieren.

2. Verfahren nach Anspruch 1, wobei das Filtern umfasst, eine bestimmte Flussbehandlung für jede Sitzung zwischen der mobilen Station (102) und dem Paketdatendienstknoten (106) bereitzustellen.

3. Verfahren nach Anspruch 1, wobei die vorgegebene Zeit 400 Sekunden beträgt.

4. Verfahren nach Anspruch 1, wobei der Schritt des Implementierens umfasst, eine Nachricht zu einer vorgegebenen Zeit pro Mobilitätsdateikopfnachrichtentyp für die Care-of-Adresse einer jeden mobilen Station (102) zuzulassen, wenn die mobile Station (102) und der entsprechende Knoten (104) eine Sitzung mit einer optimierten aktiven Route haben.

5. Verfahren nach Anspruch 1, wobei der Schritt des Implementierens umfasst, Routenoptimierungsnachrichten und Signalisierungsnachrichten der mobilen IP durch mobile Knoten außerhalb eines CDMA-Netzes einzuleiten.

6. Verfahren nach Anspruch 1, wobei der Schritt des Empfangens umfasst, von der mobilen Station (102) eine Care-of-Adressen-Aktualisierungsnachricht zu empfangen, wenn die mobile Station (102) eine Gruppe von möglichen Adressen kennt, die auf einer IP-Sitzung auftreten können, die der mobilen Station (102) zugeordnet ist.

7. Verfahren nach Anspruch 6, wobei der Schritt des Empfangens umfasst, die Care-of-Adressen-Aktualisierungsnachricht in herstellerspezifischen Erweiterungen und/oder RSVP-Nachrichten und/oder anderen Nachrichtentypen von der mobilen Station (102) zu empfangen.

8. Verfahren nach Anspruch 7, wobei der Schritt des Empfangens umfasst, die mobile Station (102) über eine durch den entsprechenden Knoten (104) neu erfasste Care-of-Adresse zu unterrichten.

9. Verfahren nach Anspruch 1, wobei der Schritt des Empfangens umfasst, ein Zeichen zu empfangen, das die mobile Station (102) identifiziert, wobei dann, wenn der Paketdatendienstknoten (106) eine Autorisierung vor dem Ausführen des Schritts des Aktualisierens benötigt, der Paketdatendienstknoten (106) das Zeichen an eine Strategieentscheidungsfunktion (108) weiterleitet, die das Zeichen verwendet, um zu bestimmen, ob eine Autorisierung angemessen ist und eine angemessene Antwort an den Paketdatendienstknoten (106) liefert.

10. Verfahren nach Anspruch 1, wobei der Schritt des Aktualisierens umfasst, eine dienstbasierte lokale Strategie- und eine Verkehrsflussvorlage zu aktualisieren.

11. Verfahren nach Anspruch 1, das umfasst, nachdem der entsprechende Knoten (104) beginnt, eine neue Care-of-Adresse zu verwenden, eine vordefinierte Anzahl von Datenpaketen durch den Paketdatendienstknoten (106) zu überprüfen, um eine Änderung der Care-of-Adresse vor dem Schritt des Aktualisierens zu überwachen.

12. Verfahren nach Anspruch 1, das Folgendes umfasst:

Erzeugen eines vorübergehenden Zustands durch den Paketdatendienstknoten (106) bei Detektieren einer Bindungsaktualisierungsnachricht von dem entsprechenden Knoten (104); und

Empfangen einer Bindungsbestätigungsnachricht von der mobilen Station (102), um zu überprüfen, das die Bindungsaktualisierungsnachricht gültig ist, vor dem Schritt des Aktualisierens.

13. Verfahren nach Anspruch 1, wobei der Schritt des Filterns umfasst, einen Quell-IP-Adressenteil eines Filters an ein Paket in einer Abwärtsstreckenrichtung anzupassen, wenn die Quell-IP-Adresse mit einem Quellfeld eines IP-Pakets übereinstimmt und/oder die Quell-IP-Adresse mit einer Heimadresse eines Bestimmungsoptionenerweiterungsdateikopfes übereinstimmt und/oder die Care-of-Adresse des entsprechenden Knotens (104) mit dem Quellfeld des Pakets übereinstimmt.

14. Verfahren nach Anspruch 1, wobei der Schritt des Filterns umfasst, einen Bestimmungs-IP-Adressenteil eines Filters an ein Paket in einer Aufwärtsstreckenrichtung anzupassen, wenn eine IP-Adresse mit einem Bestimmungsfeld eines IP-Pakets übereinstimmt und/oder die IP-Adresse mit einer Heimadresse eines Weiterleitungserweiterungsdateikopfes übereinstimmt und/oder die Care-of-Adresse des entsprechenden Knotens (104) mit dem Bestimmungsfeld des Pakets übereinstimmt.

15. Paketdatendienstknoten (106) zum Aktualisieren von Filtern mit einer Care-of-Adresse, die einer mobilen Station (102) und/oder einem entsprechenden Knoten (104) zugeordnet ist, wobei sich die Filter bei dem Paketdatendienstknoten (106) eines drahtlosen Netzes (100) befinden und der Paketdatendienstknoten (106) als ein Zugriffsknoten für die mobile Station (102) des drahtlosen Netzes (100) wirkt, wobei die Filter zum Filtern des Verkehrs zu oder von der mobilen Station (102) bei dem Paketdatendienstknoten (106) dienen und die Vorrichtung (106) Folgendes umfasst:

Implementierungsmittel zum Implementieren einer schwachen Filterregel bei den Filtern des Paketdatendienstknotens (106), wobei die Implementierungsmittel Zulassungsmittel umfassen, um mindestens eine Mobilitätsdateikopfnachricht zu einer vorgegebenen Zeit zuzulassen, wobei die vorgegebene Zeit ein konfigurierbarer Parameter ist;

Empfangsmittel zum Empfangen durch den Paketdatendienstknoten (106) von einer mobilen Station (102) einer Care-of-Adresse, die der mobilen Station (102) und/oder einem entsprechenden Knoten (104) zugeordnet ist;

Aktualisierungsmittel zum Aktualisieren durch den Paketdatendienstknoten (106) von Filtern mit der Care-of-Adresse, um Flüsse, die zu einer bestimmten Sitzung während der Verwendung der mobilen IP gehören, korrekt zu identifizieren.

16. Paketdatendienstknoten nach Anspruch 15, wobei das Filtern umfasst, eine bestimmte Flussbehandlung für jede Sitzung zwischen der mobilen Station (102) und dem Paketdatendienstknoten (106) bereitzustellen.

17. Paketdatendienstknoten nach Anspruch 15, der Folgendes umfasst:

Filtermittel zum Filtern von Paketen durch den Paketdatendienstknoten, die eine Care-of-Adresse enthalten, die der mobilen Station (102) und/oder dem entsprechenden Knoten (104) zugeordnet ist.

18. Paketdatendienstknoten nach Anspruch 17, wobei die Implementierungsmittel Zulassungsmittel umfassen, um eine Nachricht zu einer vorgegebenen Zeit pro Mobilitätsdateikopfnachrichtentyp für die Care-of-Adresse einer jeden mobilen Station (102) zuzulassen, wenn die mobile Station (102) und der entsprechende Knoten (104) eine Sitzung mit einer optimierten aktiven Route haben.

19. Paketdatendienstknoten nach Anspruch 17, wobei die Implementierungsmittel Einleitungsmittel umfassen, um Routenoptimierungsnachrichten- und Signalisierungsnachrichten der mobilen IP durch mobile Knoten außerhalb eines CDMA-Netzes einzuleiten.

20. Paketdatendienstknoten nach Anspruch 17, wobei die Empfangsmittel von der mobilen Station (102) eine Care-of-Adressenaktualisierungsnachricht empfangen, wenn die mobile Station (102) eine Gruppe von möglichen Adressen kennt, die auf einer IP-Sitzung auftreten können, die der mobilen Station (102) zugeordnet ist.

21. Paketdatendienstknoten nach Anspruch 17, wobei die Empfangsmittel eine Care-of-Adressenaktualisierungsnachricht in herstellerspezifischen Erweiterungen, RSVP-Nachrichten oder anderen Nachrichtentypen empfangen.

22. Paketdatendienstknoten nach Anspruch 17, wobei die Empfangsmittel eine durch den entsprechenden Knoten (104) an die mobile Station (102) gesendete neu erfasste Care-of-Adresse empfangen.

23. Paketdatendienstknoten nach Anspruch 17, wobei die Empfangsmittel ein Zeichen empfangen, das die mobile Station (102) identifiziert, wobei dann, wenn der Paketdatendienstknoten (106) eine Autorisierung vor dem Ausführen des Schritts des Aktualisierens benötigt, der Paketdatendienstknoten (106) das Zeichen an eine Strategieentscheidungsfunktion (108) weiterleitet, die das Zeichen verwendet, um zu bestimmen, ob eine Autorisierung angemessen ist und eine angemessene Antwort an den Paketdatendienstknoten (106) liefert.

24. Paketdatendienstknoten nach Anspruch 17, wobei die Aktualisierungsmittel eine dienstbasierte lokale Strategie- und eine Verkehrsflussvorlage aktualisieren.

25. Paketdatendienstknoten nach Anspruch 17, der ferner Überprüfungsmittel umfasst, um, nachdem der entsprechende Knoten (104) beginnt, eine neue Care-of-Adresse zu verwenden, eine vordefinierte Anzahl von Datenpaketen zu überprüfen, um eine Änderung der Care-of-Adresse vor dem Schritt des Aktualisierens zu überwachen.

26. Paketdatendienstknoten nach Anspruch 17, der ferner umfasst: Erzeugungsmittel, um einen vorübergehenden Zustand bei Detektieren einer Bindungsaktualisierungsnachricht von dem entsprechenden Knoten (104) zu erzeugen; und Empfangsmittel, um eine Bindungsbestätigungsnachricht von der mobilen Station (102) zu empfangen, um zu überprüfen, dass die Bindungsaktualisierungsnachricht gültig ist, vor dem Schritt des Aktualisierens.

27. Paketdatendienstknoten nach Anspruch 17, wobei die Filtermittel Anpassungsmittel umfassen, um einen Quell-IP-Adressenteil eines Filters an ein Paket in einer Abwärtsstreckenrichtung anzupassen, wenn die Quell-IP-Adresse mit einem Quellfeld eines IP-Pakets übereinstimmt und/oder die Quell-IP-Adresse mit einer Heimadresse eines Bestimmungsoptionenerweiterungsdateikopfes übereinstimmt und/oder die Care-of-Adresse des entsprechenden Knotens (104) mit dem Quellfeld des Pakets übereinstimmt.

28. Paketdatendienstknoten nach Anspruch 17, wobei die Filtermittel Anpassungsmittel umfassen, um einen Bestimmungs-IP-Adressenteil eines Filters an ein Paket in einer Aufwärtsstreckenrichtung anzupassen, wenn eine IP-Adresse mit einem Bestimmungsfeld eines IP-Pakets übereinstimmt und/oder wenn die IP-Adresse mit einer Heimadresse eines Weiterleitungserweiterungsdateikopfes übereinstimmt und die Care-of-Adresse des entsprechenden Knotens (104) mit dem Bestimmungsfeld des Pakets übereinstimmt.

29. Mobile Station (102) zum Aktualisieren von Filtern eines Paketdatendienstknotens (106) eines drahtlosen Netzes mit einer Care-of-Adresse, die der mobilen Station (102) und/oder einem entsprechenden Knoten (104) zugeordnet ist, wobei die mobile Station (102) Mittel umfasst zum
Empfangen einer Care-of-Adresse, die mindestens einer Internetprotokollsitzung der mobilen Station (102) zugeordnet ist, in einer Mobilitätsdateikopfnachricht, die durch den Paketdatendienstknoten unter Verwendung der Filter gefiltert wurde, die implementiert wurden, um mindestens eine Mobilitätsdateikopfnachricht zu einer vorgegebenen Zeit zuzulassen;
Bestimmen anhand der empfangenen Care-of-Adresse einer Gruppe von möglichen Adressen der mobilen Station und des entsprechenden Knotens, die auf der mindestens einen Internetprotokollsitzung auftreten können, die der mobilen Station (102) zugeordnet ist; und
Senden einer Care-of-Adresse-Aktualisierungsnachricht, um die Filter spezifisch für die mobile Station bei dem PDSN zu aktualisieren, wenn die Gruppe der möglichen Adressen durch die empfangene Care-of-Adresse geändert wird, zum Aktualisieren der Filter mit der Care-of-Adresse, um Flüsse, die zu der mindestens einen Internetprotokollsitzung während der Verwendung der mobilen IP gehören, korrekt zu identifizieren.

Revendications

1. Procédé d'actualisation de filtres avec une adresse temporaire associée à au moins l'un d'une station mobile (102) ou d'un noeud de correspondant (104), dans lequel les filtres sont situés au niveau d'un noeud de desserte de données par paquets (106) d'un réseau sans fil (100), et ledit noeud de desserte de données par paquets fait office de noeud d'accès pour la station mobile (102) du réseau sans fil (100), dans lequel lesdits filtres servent à filtrer le trafic allant à, ou venant de, la station mobile (102) au niveau du noeud de desserte de données par paquets (106), et le procédé comprenant les étapes suivantes :

la mise en oeuvre une règle de filtrage souple au niveau des filtres du noeud de desserte de données par paquets (106), dans lequel l'étape de mise en oeuvre comprend l'autorisation d'au moins un message d'en-tête de mobilité à un temps prédéterminé, le temps prédéterminé étant un paramètre configurable ;

la réception, par un noeud de desserte de données par paquets (106) depuis la station mobile (102), d'une adresse temporaire associée à au moins l'un de la station mobile (102) et d'un noeud correspondant (104) ; et

l'actualisation, par le noeud de desserte de données par paquets (106), de filtres avec l'adresse temporaire pour identifier correctement les flux appartenant à une session particulière durant l'utilisation de l'IP mobile.

2. Procédé selon la revendication 1, dans lequel le filtrage comprend la fourniture d'un traitement de flux spécifique à chaque session entre la station mobile (102) et le noeud de desserte de données par paquets (106).

3. Procédé selon la revendication 1, dans lequel le temps prédéterminé est de 400 secondes.

4. Procédé selon la revendication 1, dans lequel l'étape de mise en oeuvre comprend l'autorisation d'un message à un temps prédéterminé par type de message d'en-tête de mobilité pour chaque adresse temporaire de station mobile (102), si la station mobile (102) et le noeud de correspondant (104) ont une session optimisée de route active.

5. Procédé selon la revendication 1, dans lequel l'étape de mise en oeuvre comprend le lancement de messages d'optimisation de route et de signalisation IP mobile par les noeuds mobiles en dehors d'un réseau CDMA.

6. Procédé selon la revendication 1, dans lequel l'étape de réception comprend la réception, depuis la station mobile (102), d'un message d'actualisation d'adresse temporaire quand la station mobile (102) connaît un ensemble d'adresses possibles susceptibles d'apparaître sur une session IP qui est associée à la station mobile (102).

7. Procédé selon la revendication 6, dans lequel l'étape de réception comprend la réception du message d'actualisation d'adresse temporaire dans l'un d'extensions spécifiques au vendeur, de messages RSVP ou d'autres types de messages depuis la station mobile (102).

8. Procédé selon la revendication 7, dans lequel l'étape de réception comprend la notification à la station mobile (102) d'une adresse temporaire nouvellement acquise par le noeud de correspondant (104) .

9. Procédé selon la revendication 1, dans lequel l'étape de réception comprend la réception d'un jeton qui identifie la station mobile (102), dans lequel si le noeud de desserte de données par paquets (106) nécessite une autorisation avant d'exécuter l'étape d'actualisation, le noeud de desserte de données par paquets (106) renvoie le jeton à une fonction de décision de stratégie (108) qui utilise le jeton pour déterminer si l'autorisation est appropriée et fournit une réponse appropriée au noeud de desserte de données par paquets (106).

10. Procédé selon la revendication 1, dans lequel l'étape d'actualisation comprend l'actualisation d'une stratégie locale basée sur les services et d'un modèle de flux de trafic.

11. Procédé selon la revendication 1, comprenant, après que le noeud de correspondant (104) commence à utiliser une nouvelle adresse temporaire, la vérification d'un nombre prédéfini de paquets de données, par le noeud de desserte de données par paquets (106), pour observer un changement de l'adresse temporaire, avant l'étape d'actualisation.

12. Procédé selon la revendication 1, comprenant :

la création d'un état temporaire, par le noeud de desserte de données par paquets (106), à la détection d'un message d'actualisation liant depuis le noeud de correspondant (104) ; et

la réception d'un message d'acquittement liant depuis la station mobile (102) pour vérifier que le message d'actualisation liant est valable,

avant l'étape d'actualisation.

13. Procédé selon la revendication 1, dans lequel l'étape de filtrage comprend la concordance d'une partie d'adresse IP source d'un filtre avec un paquet dans un sens de liaison descendante quand au moins l'une de l'adresse IP source concorde avec un champ source d'un paquet IP ou de l'adresse IP source concorde avec une adresse de rattachement d'un en-tête d'extension d'options de destination et l'adresse temporaire du noeud de correspondant (104) concorde avec le champ source du paquet.

14. Procédé selon la revendication 1, dans lequel l'étape de filtrage comprend la concordance d'une partie d'adresse IP destinataire d'un filtre avec un paquet dans un sens de liaison montante quand au moins l'une d'une adresse IP concorde avec un champ destinataire d'un paquet IP ou de l'adresse IP concorde avec une adresse de rattachement d'un en-tête d'extension d'options de routage et l'adresse temporaire du noeud de correspondant (104) concorde avec le champ destinataire du paquet.

15. Noeud de desserte de données par paquets (106) pour actualiser des filtres avec une adresse temporaire associée à au moins l'un d'une station mobile (102) ou d'un noeud de correspondant (104), dans lequel les filtres sont situés au niveau d'un noeud de desserte de données par paquets (106) d'un réseau sans fil (100), et ledit noeud de desserte de données par paquets (106) fait office de noeud d'accès pour la station mobile (102) du réseau sans fil (100), dans lequel lesdits filtres servent à filtrer le trafic allant à, ou venant de, la station mobile (102) au niveau du noeud de desserte de données par paquets (106), et l'appareil (106) comprend :

un moyen de mise en oeuvre pour mettre en oeuvre une règle de filtrage souple au niveau des filtres du noeud de desserte de données par paquets (106), dans lequel le moyen de mise en oeuvre comprend un moyen d'autorisation pour autoriser au moins un message d'en-tête de mobilité à un temps prédéterminé, le temps prédéterminé étant un paramètre configurable ;

un moyen de réception pour recevoir, par le noeud de desserte de données par paquets (106) depuis une station mobile (102), une adresse temporaire associée à au moins l'un de la station mobile (102) et d'un noeud de correspondant (104) ; et

un moyen d'actualisation pour actualiser, par le noeud de desserte de données par paquets (106), des filtres avec l'adresse temporaire pour identifier correctement les flux appartenant à une session particulière durant l'utilisation de l'IP mobile.

16. Noeud de desserte de données par paquets selon la revendication 15, dans lequel le filtrage comprend la fourniture d'un traitement de flux spécifique à chaque session entre la station mobile (102) et le noeud de desserte de données par paquets (106).

17. Noeud de desserte de données par paquets selon la revendication 15, comprenant :

un moyen de filtrage pour filtrer des paquets, par le noeud de desserte de données par paquets, comportant une adresse temporaire qui est associée à l'une de la station mobile (102) et du noeud de correspondant (104).

18. Noeud de desserte de données par paquets selon la revendication 17, dans lequel le moyen de mise en oeuvre comprend un moyen d'autorisation d'un message à un temps prédéterminé par type de message d'en-tête de mobilité pour chaque adresse temporaire de station mobile (102), si la station mobile (102) et le noeud de correspondant (104) ont une session optimisée de route active.

19. Noeud de desserte de données par paquets selon la revendication 17, dans lequel le moyen de mise en oeuvre comprend un moyen de lancement pour lancer des messages d'optimisation de route et de signalisation IP mobile par des noeuds mobiles en dehors d'un réseau CDMA.

20. Noeud de desserte de données par paquets selon la revendication 17, dans lequel le moyen de réception reçoit, depuis la station mobile (102), un message d'actualisation d'adresse temporaire quand la station mobile (102) connaît un ensemble d'adresses possibles qui pourraient apparaître sur une session IP qui est associée à la station mobile (102).

21. Noeud de desserte de données par paquets selon la revendication 17, dans lequel le moyen de réception reçoit un message d'actualisation d'adresse temporaire dans l'un d'extensions spécifiques au vendeur, de messages RSVP ou d'autres types de messages.

22. Noeud de desserte de données par paquets selon la revendication 17, dans lequel le moyen de réception reçoit une adresse temporaire nouvellement acquise envoyée par le noeud de correspondant (104) à la station mobile (102).

23. Noeud de desserte de données par paquets selon la revendication 17, dans lequel le moyen de réception reçoit un jeton qui identifie la station mobile (102), dans lequel si le noeud de desserte de données par paquets (106) nécessite une autorisation avant d'exécuter l'étape d'actualisation, le noeud de desserte de données par paquets (106) renvoie le jeton à une fonction de décision de stratégie (108) qui utilise le jeton pour déterminer si l'autorisation est appropriée et fournit une réponse appropriée au noeud de desserte de données par paquets (106).

24. Noeud de desserte de données par paquets selon la revendication 17, dans lequel le moyen d'actualisation actualise une stratégie locale basée sur les services et un modèle de flux de trafic.

25. Noeud de desserte de données par paquets selon la revendication 17, comprenant en outre un moyen de vérification pour vérifier, après que le noeud de correspondant (104) commence à utiliser une nouvelle adresse temporaire, un nombre prédéfini de paquets de données pour observer un changement de l'adresse temporaire, avant l'étape d'actualisation.

26. Noeud de desserte de données par paquets selon la revendication 17, comprenant en outre un moyen de création pour créer un état temporaire à la détection d'un message d'actualisation liant depuis le noeud de correspondant (104) ; et un moyen de réception pour recevoir un message d'acquittement liant depuis la station mobile (102) pour vérifier que le message d'actualisation liant est valable, avant l'étape d'actualisation.

27. Noeud de desserte de données par paquets selon la revendication 17, dans lequel le moyen de filtrage comprend un moyen de concordance pour faire concorder une partie d'adresse IP source d'un filtre avec un paquet dans un sens de liaison descendante quand au moins l'une de l'adresse IP source concorde avec un champ source d'un paquet IP ou de l'adresse IP source concorde avec une adresse de rattachement d'un en-tête d'extension d'options de destination et l'adresse temporaire du noeud de correspondant (104) concorde avec le champ source du paquet.

28. Noeud de desserte de données par paquets selon la revendication 17, dans lequel le moyen de filtrage comprend un moyen de concordance pour faire concorder une partie d'adresse IP destinataire d'un filtre avec un paquet dans un sens de liaison montante quand au moins l'une d'une adresse IP concorde avec un champ destinataire d'un paquet IP ou de l'adresse IP concorde avec une adresse de rattachement d'un en-tête d'extension d'options de routage et l'adresse temporaire du noeud de correspondant (104) concorde avec le champ destinataire du paquet.

29. Station mobile (102) pour actualiser des filtres d'un noeud de desserte de données par paquets (106) d'un réseau sans fil avec une adresse temporaire associée à au moins l'un d'une station mobile (102) ou d'un noeud de correspondant (104), la station mobile (102) comprenant des moyens pour :

recevoir une adresse temporaire associée à au moins une session de protocole Internet de la station mobile (102) dans un message d'en-tête de mobilité filtré par le noeud de desserte de données par paquets en utilisant les filtres mis en oeuvre pour permettre au moins un message d'en-tête de mobilité à un temps prédéterminé ;

déterminer en fonction de l'adresse temporaire reçue un ensemble d'adresses possibles de la station mobile et du noeud de correspondant qui sont susceptibles d'apparaître sur l'au moins une session de protocole Internet qui est associée à la station mobile (102) ; et

envoyer un message d'actualisation d'adresse temporaire pour actualiser les filtres spécifiques à la station mobile au niveau du PSDN, quand l'ensemble d'adresses possibles est changé par l'adresse temporaire reçue, pour actualiser les filtres avec l'adresse temporaire pour identifier correctement les flux appartenant à l'au moins une session particulière durant l'utilisation de l'IP mobile.

Drawing