+

WO2011055525A1 - Système de communication, terminal mobile et noeud de gestion de mobilité - Google Patents

Système de communication, terminal mobile et noeud de gestion de mobilité Download PDF

Info

Publication number
WO2011055525A1
WO2011055525A1 PCT/JP2010/006444 JP2010006444W WO2011055525A1 WO 2011055525 A1 WO2011055525 A1 WO 2011055525A1 JP 2010006444 W JP2010006444 W JP 2010006444W WO 2011055525 A1 WO2011055525 A1 WO 2011055525A1
Authority
WO
WIPO (PCT)
Prior art keywords
filter
handoff
filter rule
mobility management
mobile terminal
Prior art date
Application number
PCT/JP2010/006444
Other languages
English (en)
Japanese (ja)
Inventor
モハナ ダマヤンティ ジャヤタラン
チャン ワー ンー
啓吾 阿相
チュン キョン ベンジャミン リム
純 平野
Original Assignee
パナソニック株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by パナソニック株式会社 filed Critical パナソニック株式会社
Publication of WO2011055525A1 publication Critical patent/WO2011055525A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0019—Control or signalling for completing the hand-off for data sessions of end-to-end connection adapted for mobile IP [MIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H04W36/144—Reselecting a network or an air interface over a different radio air interface technology
    • H04W36/1446—Reselecting a network or an air interface over a different radio air interface technology wherein at least one of the networks is unlicensed

Definitions

  • the present invention relates to a remote communication technique in a packet exchange data communication network. Specifically, the present invention relates to a technique for setting a filter rule in a local mobility management domain that manages mobility of a mobile terminal.
  • IP Internet Engineering Task Force
  • IETF Internet Engineering Task Force
  • IPv6 Internet Engineering Task Force
  • IETF Internet Engineering Task Force
  • each mobile node has a permanent home domain.
  • HoA home address
  • the mobile node is assigned a primary global address known as a home address (HoA).
  • the mobile node is away from the home network, that is, when connected to another foreign network, the mobile node usually has a care-of address as a care-of address (CoA).
  • a known temporary global address is assigned.
  • the idea of mobility support is that even when a mobile node is connected to another foreign network, the mobile node can be reached with its own home address.
  • Non-Patent Document 1 Such an idea is realized in Non-Patent Document 1 by introducing an entity called a home agent (HA) into a home network.
  • the mobile node registers a care-of address with the home agent using a message called binding update (BU).
  • BU binding update
  • the home agent can generate a binding between the home address and the care-of address of the mobile node.
  • the home agent receives (intercepts) a message addressed to the mobile node's home address, and uses packet encapsulation (which makes a packet a new packet payload, also called packet tunneling) It is responsible for forwarding packets to the mobile node's care-of address.
  • packet encapsulation which makes a packet a new packet payload, also called packet tunneling
  • One of the problems is that the mobile node needs to send a BU message to the home agent. For example, when the mobile node is moving at a high speed, the number of BU messages generated and transmitted becomes considerably large.
  • the distance from the mobile node to the home agent becomes long, and it may take time for the BU message to reach the home agent.
  • the home agent starts forwarding packets to the mobile node's updated care-of address, the mobile node may not be at that location.
  • Non-Patent Document 2 proposes network-based local mobility management as disclosed in Non-Patent Document 2 below.
  • PMIPv6 proxy mobile IPv6
  • a mobile node is a local network domain or a PMIPv6 domain (hereinafter sometimes simply referred to as a local domain). It is possible to continue using the same address when the connection point is changed. This eliminates the need for the mobile node to frequently send BU messages to the home agent.
  • PMIPv6 mobility is completely processed by the network entity, so that the load on the mobile terminal is reduced when the protocol is operating.
  • LMA Local Mobility Anchor
  • MAG Mobile Access Gateway
  • AAA Authentication, Authorization, and Accounting
  • the MAG functions as an access router to which mobile nodes connect.
  • the MAG first checks the reliability of the mobile node with the AAA server and checks whether the mobile node is authorized to use the service of the local network domain.
  • the AAA server can inform the MAG about the prefix of the address to be assigned to the mobile node. Thereby, the MAG can notify the mobile node of the same prefix (called home network prefix (HNP)) in the local network domain.
  • HNP home network prefix
  • the MAG needs to update the LMA so that packets addressed to the prefix assigned to the mobile node are tunneled to an appropriate MAG to which the mobile node is currently connected.
  • This update is performed by the MAG sending a proxy binding update (PBU) message that associates the prefix used by the mobile node and the address of the MAG to the LMA.
  • PBU proxy binding update
  • the LMA may assign a prefix to the mobile node instead of the AAA server. In this way, regardless of which MAG is currently connected to the mobile node, the mobile node always checks the same home network prefix and does not need to change the address, so the mobile node sends a BU message to the home agent. Need not be sent frequently.
  • a global home agent Does not need to exist or the mobile node does not need to send a BU message.
  • PMIPv6 described in Non-Patent Document 2 also provides a basic multihoming support mechanism. This allows the mobile node to connect to the local network domain via multiple interfaces and receive one or more unique prefixes by each connected interface.
  • a plurality of LMAs may be arranged for load balancing.
  • Each deployed LMA will handle one or more PDNs (Packet Data Network) connected to the local network domain.
  • PDNs Packet Data Network
  • multiple LMA and multiple PDN scenarios as described above, multiple LMAs are arranged or one LMA handles multiple PDNs), there are generally two load balance models. .
  • the first load balance model is a model in which a plurality of LMAs managing one or more PDNs are arranged in the local network domain and support a plurality of PDNs.
  • the second load balance model is a model in which one or more PDNs are managed by an LMA farm (farm of LMAs) and a plurality of such LMA farms exist in the local network domain.
  • LMA farm model all LMAs in the farm manage the connected PDN.
  • a PDN service or a prefix provided to a mobile node for accessing the PDN service is managed by a plurality of LMAs.
  • only one LMA is in charge of service, and control is passed to multiple LMAs in the farm while the mobile node moves within the local network domain.
  • a mobile node may be able to obtain a home PDN connection service from a visited local network domain via a proxy local mobility anchor (proxy LMA).
  • proxy LMA functions as a proxy for the home LMA existing in the home local network domain.
  • the home LMA can be called a global LMA
  • the proxy LMA can be called a local LMA.
  • a hierarchical structure having a global LMA and a local LMA has various advantages.
  • the main advantage is that even when the connection state of the mobile node to the MAG in the visited local network domain changes, it is not necessary to notify the global LMA of the change. Therefore, such a hierarchical mobility management model is very beneficial for mobile nodes in terms of handoff delay, handoff signaling cost, filter signaling delay, filter signaling cost, etc.
  • the arrangement configuration of the LMA in which the mobile node is connected to the global LMA in addition to the local LMA is called a chaining architecture in 3GPP, and is described in Non-Patent Document 3 below. . In this specification, this chaining architecture is called a chain structure, and a scenario in the chain structure is described as a chain scenario.
  • the first usage purpose is for balancing the load
  • the second usage purpose is for performing efficient mobility management.
  • the mobile node may attempt to set a filter rule to receive the flow associated with the home network prefix on a suitable interface.
  • Non-Patent Document 5 the simultaneous connection by associating a plurality of care-of addresses with a single home address or home prefix is described in Non-Patent Document 5 below, and setting a filter rule for a home agent is described below.
  • communication network elements such as WiMax wireless base stations (BS: Base Station) cooperate with each other to communicate communication traffic in a wireless network such as a wireless mesh network or a wireless ad hoc network.
  • BS WiMax wireless base stations
  • a mechanism for realizing the transfer control function is disclosed.
  • each BS can form a part of a cooperative network by exchanging traffic control rules with other BSs.
  • BSs in a cooperative relationship can perform communication traffic transfer control according to this rule.
  • the BS can perform filtering of received packets based on rules presented from subordinate mobile stations or rules received from other BSs.
  • CMTS Cable Modem Termination System
  • CMTS Cable Modem Termination System
  • Patent Document 3 discloses a network device having a transmission module that transmits access point name signaling including protocol information (information indicating a mobility protocol supported by the network device).
  • the receiving module receives signaling including the address of a PDN gateway that supports the mobility protocol.
  • the control module establishes a tunnel related to communication with the PDN gateway based on the address of the PDN gateway.
  • a mobile node in a local network domain can, for example, notify a filter setting preference to an MAG in an access-specific manner and receive a flow for one interface via another interface.
  • FIG. 1A is a diagram illustrating a first example of a network configuration for explaining an operation in the related art.
  • the mobile node (user terminal: UE) 10 has three different types of interfaces (ie, lower layer protocol modules).
  • the three lower layer protocol modules are, for example, a LTE (Long Term Evolution) module, a WiMax (Worldwide Interoperability for Microwave Access) module, and a WLAN (Wireless Local Area Network) (802.11 a / b) module.
  • LTE Long Term Evolution
  • WiMax Worldwide Interoperability for Microwave Access
  • WLAN Wireless Local Area Network
  • the UE 10 is connected to the local network domain 17 via the LTE interface and the WLAN interface as an initial state.
  • the LTE interface of the UE 10 is connected to the access network 11 and is managed by an S-GW (Serving Gateway) 15 having a MAG function.
  • S-GW Serving Gateway
  • WLAN interface of the UE 10 is connected to the access network 13 and is managed by an ePDG (evolved packet data gateway) 16 having a MAG function.
  • the UE 10 receives a service from a PDN (packet data network) 20 and the mobility of the UE 10 is managed by the P-GW 19.
  • PDN packet data network
  • Signaling messages 21 and 22 indicate connection establishment signaling related to the UE 10 from each of the S-GW 15 and the ePDG 16 to the P-GW 19. Further, it is assumed that the prefix P1 is notified via LTE access and the prefix P2 is notified via WLAN access.
  • the UE 10 notifies the filter rule to the MAG entity (for example, S-GW 15 or ePDG 16), and the filter rule is carried via the local domain (local area network) 17 and stored in the P-GW 19. Is done.
  • the UE 10 may have set a filter rule that a flow (F2) associated with the prefix P2 should be transmitted via a path (ie, LTE interface) associated with the prefix P1.
  • this flow (F2) may be any type of flow including video, audio or data.
  • a flow is specified by one or more parameters. A detailed description of the flow is described in Non-Patent Document 6, for example.
  • each P-GW is configured to assume a different access technology type.
  • the P-GW 19 is in charge of the LTE access network
  • the P-GW 18 is in charge of the WiMax access network. Therefore, when the UE 10 performs a radio access technology (RAT) handoff (inter-RAT handoff), it is generally considered that the P-GW in charge of the UE 10 is changed.
  • RAT radio access technology
  • the UE 10 performs the inter-RAT handoff 21 for switching from LTE access to WiMax access.
  • the UE 10 detects the access network (WiMax access) 12 and decides to move the flow of the prefix P1 via the WiMax interface.
  • the UE 10 notifies the connection by handoff to the AGW 14, and further, vertical handoff establishment signaling by the PBU and PBA signaling message 23 is executed between the AGW 14 and the P-GW 18.
  • the P-GW 18 confirms that the value of the handoff indicator (HI) option in the PBU signaling message 23 is “2” (that is, vertical handoff), the UE 10 has previously been connected to the P-GW 19. It is estimated that the UE 10 has acquired the context of the UE 10 from the P-GW 19. Since the P-GW 18 has not acquired the context of the UE 10 before receiving the vertical handoff signaling message 23, it can be easily estimated that the context of the UE 10 may be stored in the P-GW 19.
  • the P-GW 18 confirms that the value of the handoff indicator (HI) option in the PBU signaling message 23 is “2” (that is, vertical handoff)
  • the UE 10 has previously been connected to the P-GW 19. It is estimated that the UE 10 has acquired the context of the UE 10 from the P-GW 19. Since the P-GW 18 has not acquired the context of the UE 10 before receiving the vertical handoff signaling message 23, it can be easily estimated that the context of the UE 10 may be stored in the P-GW 19.
  • the P-GW 18 After processing the signaling message 23, the P-GW 18 makes an inquiry to the P-GW 19 using the signaling message 27, and acquires all contexts of the UE 10 using the signaling message 28. In addition, the P-GW 19 also passes the filter rules associated with the UE 10 via the signaling message 28.
  • the address of the P-GW 18 is notified to the ePDG 16. This allows the ePDG 16 to initiate the PBU signaling message 24 and to receive the same prefix P2.
  • the UE 10 may change the filter rule related to the flow 2 (F2) described above after completing the handoff connection signaling to the 3GPP core network via the WiMax access.
  • the change of the filter rule of the UE 10 depending on the access network type usually occurs due to a difference in the type of access network characteristics, a traffic state in the access network, and the like.
  • the UE 10 may decide not to transmit the flow 2 (F2) via the prefix P1 after vertical handoff and to delete this filter rule.
  • the filter rule (change filter rule) changed in relation to the flow 2 (F2) of the UE 10 may be transmitted by an access-specific method.
  • the signaling message 25 indicates the setting of the change filter rule related to the UE 10 after the vertical handoff.
  • the AGW 14 When the AGW 14 receives the change filter rule of the UE 10, the AGW 14 transmits the filter rule to the P-GW 18 by the signaling message 26. As a result, the P-GW 18 can change the filter rule acquired from the P-GW 19 at the time of the vertical handoff of the UE 10 by the filter rule received from the AGW 14.
  • the scenario described with reference to FIG. 1A has a problem that the network entity (P-GW 19) does not know the intention of the UE 10 regarding the filter rule after the vertical handoff and passes the old filter rule of the UE 10.
  • the network entity P-GW 19
  • F2 the old filter rule related to the flow 2
  • the local network domain maintains state for a large number of UEs 10, and network bottlenecks can occur due to excessive network signaling that carries old or extra filter rules for a large number of UEs 10, and the network can go down There is also sex. Such a situation should be avoided.
  • This scenario also shows that when the UE performs a vertical handoff to WiMax, the old filter rule passed from P-GW 19 is passed to P-GW 18 after the change filter rule arrives at P-GW 18 via WiMax access. It also has the problem that it may arrive.
  • the P-GW 18 When the P-GW 18 receives the filter rule (the updated correct filter rule) from the AGW 14 and then receives the filter rule (the old filter rule before the update) from the P-GW 19, the correct filter rule is overwritten with the old filter rule. There is a possibility that. As a result, an incorrect filter rule setting is performed for the flow 2 (F2) in the P-GW 18.
  • the problem illustrated in FIG. 1A is that when a filter rule change occurs, the network entity must pass which filter rule to another network entity and which filter rule must be passed to another network entity. By not knowing whether there is any. This is the first problem associated with setting filter rules in a multiple LMA scenario.
  • FIG. 1B is a diagram illustrating a second example of a network configuration for explaining the operation in the related art.
  • the UE 40 is connected to the LTE access network 41 and the WLAN access network 42 via the interface. Furthermore, when the UE 40 is simultaneously connected to the local domain (local access network) 45, it is assumed that the S-GW 43 and the ePDG 44 provide the MAG function. Further, it is assumed that the UE 40 receives services from two packet data networks (for example, PDN 48 and PDN 49). It is assumed that the PDN 48 is managed by the P-GW 46 and the PDN 49 is managed by the P-GW 47.
  • PDN 48 packet data networks
  • the UE 40 receives two home network prefixes (prefix P3 and prefix P1) in order to access the service from the PDN 48.
  • the prefix P3 is obtained using the PBU signaling message 50
  • the prefix P1 is obtained using the PBU signaling message 51.
  • the prefix P2 is used to access a service from the PDN 49 and is obtained using the PBU signaling message 52.
  • the UE 40 transmits filter rule signaling message 53 to ePDG 44.
  • the filter rule indicates that the flow 1 related to the prefix P3 is transferred via the prefix P1.
  • the ePDG 44 examines the forwarding prefix (prefix P3) of the filter rule, checks the binding update list, and tries to identify the P-GW related to the prefix P3 (ie, P-GW 46). However, when the ePDG 44 scrutinizes the binding update list, the ePDG 44 specifies P-GW information related to the prefixes P1 and P2, but cannot specify P-GW information related to the prefix P3.
  • the ePDG 44 may transmit a filter rule pass signaling message (filter rule passing signaling message) including this filter rule to the P-GW 47, as shown as the signaling message 55.
  • the signaling message 55 may be a PBU signaling message in which a filter rule is inserted into a new mobility option.
  • the signaling message 55 may be rejected by the P-GW 47.
  • ePDG 44 receives a negative acknowledgment (NACK) for signaling message 55
  • ePDG 44 transmits a filter rule path signaling message to P-GW 46 as indicated in signaling message 54. Since the filter rule is related to the transfer prefix of the prefix P3 belonging to the P-GW 46, the ePDG 44 receives the ACK for the signaling message 54, and the transfer of the filter rule is completed.
  • NACK negative acknowledgment
  • the problem in the scenario illustrated in FIG. 1B is that unnecessary filter rule path signaling is transmitted to the P-GW 47.
  • the ePDG 44 since the ePDG 44 does not grasp the validity of the transfer prefix P3, it may be regarded as a flooding attack to the network and the filter rule may be discarded.
  • the MAG when the filter rule forwarding prefix is not associated with the P-GW, the MAG passes the filter rule (such as a partner to which the filter rule should be passed). I can't figure out.
  • FIG. 1C is a diagram illustrating a third example of the network configuration for explaining the operation in the related art.
  • the UE 60 is connected to the visited local network domain 65 using the WiMax interface and the WLAN interface.
  • the visited local network domain is VPLMN (VisitedsitePLMN)
  • the home local network domain is HPLMN (Home PLMN).
  • S-GW 67 functions as a local LMA or proxy LMA
  • P-GW 66 functions as a global LMA.
  • the P-GW 66 is connected to a packet data network (PDN) 68.
  • the UE 60 is connected to the AGW 62 via the access network 70 and is connected to the ePDG 63 via the access network 71. Further, the UE 60 acquires the prefix P1 by the PBU signaling messages 75 and 73, and acquires the prefix P2 by the PBU signaling messages 76 and 74. Note that details of signaling for creating a binding related to the home network prefix in the local LMA and the global LMA are disclosed in, for example, Non-Patent Document 3, for the PMIPv6 chain mechanism in which such LMAs are connected.
  • the filter rule is set when the UE 60 exists in the VPLMN, if the forwarding prefix of the filter rule is represented by the S-GW 67, the S- It can be assumed that the GW 67 holds the filter rule.
  • the S-GW 67 holds the routing state of the transfer prefix P2 in the binding cache. Therefore, the filter rule is held in the S-GW 67.
  • the S-GW 67 detects that one of the interfaces of the UE 60 is not connected to the S-GW 67, the S-GW 67 only performs an operation of returning the filter rule to the P-GW 66. If concurrent connections are not maintained at the proxy LMA (here, S-GW 67), it is reasonable to assume that the filter rules are passed to the global LMA (here, P-GW 66).
  • the UE 60 decides to perform a vertical handoff from the WiMax access to the LTE access, and performs a vertical handoff process to the S-GW 61 via the access network 69. This vertical handoff switching process is shown at 80.
  • the S-GW 67 may detect that the WiMax access binding is completely deleted, and may return the filter rule to the P-GW 66.
  • the operation of returning the filter rule by the vertical handoff of the UE 10 is indicated by a signaling message 79.
  • the signaling message 79 may be a PBU signaling message in which a filter rule is inserted in the mobility option.
  • a PBU signaling message 72 is transmitted from the S-GW 61, and the handoff PBU signaling message 72 starts a transfer related to the prefix P1 via the LTE access.
  • the UE 60 decides to change a filter rule and transmits a change filter rule related to the flow (F2) after the vertical handoff.
  • the modified filter rules are passed to the P-GW 66 by signaling messages 77 and 78.
  • the problem in this case is that the S-GW 67 does not know that the filter rule is changed depending on the HPLMN or the access technology type, and the old filter rule is transferred to the P-GW 66. It is in the point to return.
  • the old filter rule transferred via the signaling message 79 will eventually be overwritten by the modified filter rule inserted in the signaling message 78. Therefore, it is not necessary to transfer the old filter rule from the S-GW 67 to the P-GW 66 as a result, and the signaling message 79 for transferring the old filter rule causes signaling overhead in the network.
  • the S-GW 67 delays the old filter rule due to a delay in detecting the interface disconnection.
  • the old filter rule that was sent may overwrite the modified filter rule (filter rule suitable for the state after the vertical handoff) sent by the signaling message 78.
  • Patent Document 1 a method for delivering a packet filter to BSs forming a cooperative network is provided.
  • efficient filter passing is not performed in a cooperative network having a plurality of BSs.
  • the mechanism disclosed in Patent Document 1 does not deal with the problem of specifying an ideal BS to hold a filter.
  • Patent Document 3 inserts a supported mobility management mode type into access point name (APN) information.
  • APN access point name
  • the technique described in Patent Document 3 does not deal with a method of using APN information for efficient filter setting in a multiple LMA scenario, and does not solve the above-described problem related to the efficiency of filter setting. .
  • the present invention provides efficient filter rule setting (i.e., less signaling) in a network implementing a network-based local mobility management protocol in which a plurality of mobility management nodes are installed.
  • the purpose is to be able to set the exact filter rule by message).
  • the communication system of the present invention is a communication system having a network-based local mobility management domain in which a plurality of mobility management nodes that perform mobility management of mobile terminals are arranged,
  • the mobile terminal is Regarding the filter rule for filtering the communication flow of the mobile terminal by the local mobility management domain, when handoff is performed in the local mobility management domain, the filter rule is valid after the handoff and invalid after the handoff
  • the mobility management node is Means for storing the filter rule and the additional information; Means for identifying a filter rule that is effective even after the handoff with reference to the additional information and notifying another mobility management node of the filter rule that is also effective after the handoff when the handoff of the mobile terminal is detected; , Have.
  • efficient filter rules can be set in a network in which a network-based local mobility management domain
  • the mobile terminal of the present invention communicates using a communication system having a network-based local mobility management domain in which a plurality of mobility management nodes that perform mobility management of the mobile terminal are arranged.
  • the mobility management node of the present invention is a mobility management node in a communication system having a network-based local mobility management domain in which a plurality of mobility management nodes for performing mobility management of mobile terminals are arranged.
  • the filter rule for filtering the communication flow of the mobile terminal by the local mobility management domain is a filter rule that is effective even after the handoff when the mobile terminal performs a handoff in the local mobility management domain.
  • efficient filter rules can be set in a network in which a network-based local mobility management protocol in which a plurality of mobility management nodes are installed is implemented.
  • the present invention has the above-described configuration so that efficient filter rule setting can be performed in a network in which a network-based local mobility management protocol in which a plurality of mobility management nodes are installed is implemented. It has the effect of becoming.
  • movement in a prior art The figure which shows the 2nd example of the network structure for demonstrating operation
  • movement in embodiment of this invention The figure which shows the 2nd example of the network structure for demonstrating the operation
  • movement in embodiment of this invention The figure which shows the 3rd example of the network configuration for demonstrating the operation
  • movement in embodiment of this invention The figure which shows the 1st example of operation
  • the figure which shows an example of a structure of UE in embodiment of this invention The figure which shows an example of a structure of LMA in embodiment of this invention
  • the first idea relates to a method in which the UE determines whether or not tagging of a filter rule is necessary in order to efficiently set a filter rule.
  • Tagging means that filter rules are grouped and additional parameters are added.
  • the UE In order for the UE to set up an efficient filter rule based on information statically configured in the UE in the UE learning process, information provided from the network, etc., the UE has some information in the filter rule. Determine that it needs to be tagged.
  • the second device relates to a method in which the UE actually executes tagging processing using appropriate tag information and passes the tagged filter rule to the network entity.
  • the tag attached to the filter rule indicates, for example, the effectiveness of the filter rule at the time of handoff, the associated APN, and the like.
  • the second contrivance is correct by tagging information to the filter rule without causing extra network signaling transmission, extra filter rule signaling transmission by the UE, filter rule conflict (wrong overwriting), etc.
  • the goal is to be able to pass filter rules to network entities.
  • the UE determines which group's filter rule is to be changed or invalidated after the vertical handoff, performs tagging processing on the filter rule, and notifies the network entity in advance. If the network entity has filter rule validity information for a group of filter rules, then when the UE performs a vertical handoff, the network entity will filter after the vertical handoff Process to pass only rules to another network entity. Tagging the filter rules associated with being valid in a vertical handoff allows a network entity to pass only valid filter rules to other network entities, resulting in extra filter rules. The problem of passing and the problem of conflicting filter rules can be solved.
  • FIG. 2A is a sequence chart showing a first example of the operation according to the embodiment of the present invention.
  • the tagging process performed by UE 200a identifies which filter rules are valid after vertical handoff, which filter rules are not valid after vertical handoff, and sets the filter rules at the network entity. This information is added to the filter rule.
  • the UE 200a has a plurality of interfaces and is connected to the S-GW 201a and the ePDG 203a as an initial state.
  • the UE 200a determines the necessity of tagging the filter, performs filter classification or filter tagging, and sets filter rules for two filter groups, for example, the filter group FG1 and the filter group FG2, in the P-GW 204a. To do.
  • the filter group FG1 is all filter rules classified by the UE 200a as filter rules that are not changed after the vertical handoff
  • the filter group FG2 is all filter rules classified by the UE as filter rules that are changed after the vertical handoff. It is.
  • All filter rules that are not changed after a vertical handoff are grouped and a tag or flag (ie, a filter rule) that indicates that these filter rules are valid and not changed (ie, can be used as is) after a vertical handoff (Information indicating the validity of) is added and transmitted.
  • all changed filter rules are also grouped and sent with a tag or flag indicating that these filter rules are invalid and will be changed after a vertical handoff.
  • a tag or flag may be added to both the filter rule that is changed after vertical handoff and the filter rule that is not changed, or a tag or flag is added by adding a tag or flag to only one of them.
  • the filter rule that is changed after the vertical handoff and the filter rule that is not changed may be identified.
  • the UE 200a can determine whether the filter rule is valid after vertical handoff based on some information.
  • Information for determining the validity of the filter rule may be provided from a fixed server located in the local network domain. For example, ANDSF (Access
  • ANDSF Access
  • server may provide the UE200a with the information regarding the state of the target access network (here, WiMax access network).
  • the UE 200a Based on the information provided by the server on the network (the characteristics of the target access network (access type, etc.), the access network conditions such as the appropriateness of the target access network regarding the transport of the UE 200a flow, the UE 200a It is possible to determine the validity appropriately, and instead of making a determination of the validity of the filter rule based on the information provided from the ANDSF, the UE 200a may determine the validity based on the measurement value regarding the condition of the target access network. In addition, the UE 200a can use the pre-configured information or static information set in the UE 200a to perform filtering rule validity after the vertical handoff processing. Whether changes are required It may be determined whether.
  • the UE 200a determines which flows need the filter rules to be changed and which flows need not be changed. Can be determined. For example, if the WiMax access network is congested and the QoS (Quality of Service) required for a flow cannot be provided via WiMax access, the flow affected by vertical handoff is After vertical handoff, it is necessary to move from LTE access to WLAN access. On the other hand, for flows where the required QoS can be guaranteed via the target access network, it may be determined that the filter rules need not be changed after a vertical handoff.
  • QoS Quality of Service
  • the UE 200a basically makes such a determination, classifies the filter rule into either the filter group FG1 or the filter group FG2, and performs an appropriate tagging process.
  • the UE 200a After the filter rule tagging process, the UE 200a notifies the P-GW 204a (steps S206a and S207a). That is, when the UE 200a determines appropriate tagging for the filter rule based on the validity after the vertical handoff, the UE 200a transmits the filter group FG1 and FG2 of the tagged filter rule via the ePDG 203a to the P-GW 204a. Send to.
  • the UE 200a first transmits a signaling message including filter groups FG1 and FG2 of the tagged filter rule to ePDG 203a (step S206a).
  • the signaling message may be a layer 3 (L3) message or a layer 2 (L2) message.
  • L3 layer 3
  • L2 layer 2
  • the signaling message sent in step S206a may be sent to the P-GW 204a via LTE access.
  • the UE 200a transmits a message including a filter rule tagged in an arbitrary message that can be transmitted from the LTE access.
  • the tagged filter rule may be included in a PCO (Protocol Configuration Option) and added to the message.
  • PCO Protocol Configuration Option
  • the signaling message transmitted in step S206a includes a tag related to the filter group FG1 (a tag indicating that the filter group FG1 of the filter rule is valid after the vertical handoff) and a tag related to the filter group FG2 (the filter after the vertical handoff). A tag indicating that the rule filter group FG2 is valid).
  • the signaling message sent in step S206a can be configured to include both filter groups (FG1 and FG2) and tagging information.
  • the signaling message transmitted in step S207a indicates that the tagged filter rule message is passed from the ePGG 203a to the P-GW 204a. The exact packet structure of the signaling message transmitted in steps S206a and S207a will be described later (FIGS. 6A to 6D described later).
  • Another added filter rule may be transmitted.
  • the UE 200a After transmitting the tagged filter rule message to the P-GW 204a, the UE 200a performs a vertical handoff process, connects to the WiMax access, and connects to the AGW 202a. After confirming the prefix P1 transferred via WiMax access, the UE 200a makes a determination regarding a new filter rule with respect to the filter group FG2. When a new filter rule is determined for the filter group FG2, the UE 200a transmits a new filter rule message to the AW 202a (step S208a).
  • the signaling message transmitted in step S208a is composed of only changed filter rules related to the filter group FG2. Note that the change filter rule message transmitted in step S208a may include a flow identifier and a filter rule related to the flow.
  • the AGW 202a transmits a change filter rule signaling message to the P-GW 205a (step S209a).
  • the signaling message transmitted in step S209a indicates that the change filter rule is passed to the P-GW 205a.
  • the P-GW 205a is a new LMA that manages the UE 200a.
  • the P-GW 204a detects that the binding relating to the prefix P1 has been deleted from the P-GW 204a, the P-GW 204a transmits the filter rule related to the filter group FG1 (the filter rule that remains valid after the vertical handoff) to the P-GW 205a ( Step S210a).
  • FIG. 2A illustrates as signaling message 210a that signaling of filter rules associated with filter group FG1 is transferred between P-GWs 204a, 205a.
  • the UE 200a notifies the P-GW 204a by tagging that the filter rule of the filter group FG1 is not changed after the vertical handoff, so the P-GW 204a only passes the filter rule related to the filter group FG1. (Furthermore, it is not necessary to pass a filter rule related to the filter group FG2).
  • the UE 200a explicitly provides to the P-GW 204a which filter group filter rules need to be passed to the P-GW 205a when a vertical handoff occurs. By such an instruction, only necessary filter rules are passed, and notification of extra filter rules and conflict (overwriting) of filter rules are not performed.
  • FIG. 2B is a second example of the network configuration for explaining the operation in the embodiment of the present invention
  • FIG. 2C is a sequence chart showing the second example of the operation in the embodiment of the present invention. .
  • the UE 200b is connected to the local domain (VPLMN) 217b using the WiMax interface and the WLAN interface, and is receiving service from the PDN 209b connected to the local domain (HPLMN) 216b.
  • the WiMax interface of the UE 200b is connected to the AGW 202b through the access network 207b.
  • the WLAN interface of the UE 200b is connected to the ePDG 203b through the access network 208b.
  • S-GW 205b is a local LMA in the chain scenario
  • P-GW 204b is a global LMA.
  • the UE 200b first classifies the filter rules into two groups. This grouping is performed based on a filter rule (filter group FG2) that the UE 200b predicts if it is changed after the vertical handoff and a filter rule (filter group FG1) that the UE 200b predicts that it is not changed after the vertical handoff.
  • filter group FG2 a filter rule that the UE 200b predicts if it is changed after the vertical handoff
  • filter group FG1 filter rule that the UE 200b predicts that it is not changed after the vertical handoff.
  • the UE 200b transmits a signaling message (filter tagging message) to the ePDG 203b in step S206c, so that two filter rule filter groups (filter groups FG1 and FG2) with appropriate tags inserted into the S-GW 205b.
  • a tag indicating that the filter rule of this filter group is changed after the vertical handoff is inserted into the filter group FG2 of the filter rule.
  • the ePDG 203b processes the filter tagging message received in step S206c, and transmits a signaling message (filter tagging message) in step S207c, thereby passing the filter rule and tag to the S-GW 205b.
  • the filter tagging message transmitted in step S207c is protected using an appropriate security association established between ePDG 203b and S-GW 205b, for example.
  • the UE 200b When the UE 200b performs vertical handoff from WiMax to LTE access as shown in the vertical handoff switching process 209b in FIG. 2B, the prefix confirmed via WiMax access is transferred via LTE access.
  • the AGW 202b detects that the connection via the WiMax interface has been disconnected, and transmits a PBU signaling message for deregistration to the S-GW (local LMA) 205b (step S208c). .
  • the S-GW 205b Upon confirming the deregistration PBU signaling message transmitted in step S208c, the S-GW 205b transmits the filter rule of the filter group FG1 to the P-GW 204b by a signaling message (filter rule message not changed) 209c (step S209c). ).
  • the signaling message sent in step S209c may be a PBU signaling message with some new options for transmitting unaltered filter rules, or may be a completely new message.
  • the S-GW 205b when receiving the signaling message in step S208c, transmits a PBU signaling message for deregistration to the P-GW 204b. Upon receiving the PBA signaling message from the P-GW 204b, the S-GW 205b transmits a PBA signaling message (not shown in FIG. 2C) to the AGW 202b.
  • the UE 200b When executing the vertical handoff, the UE 200b first transmits a handoff connection signaling message to the S-GW 201b via the access network 206b (step S210c).
  • the S-GW 201b processes the signaling message received in step S210c, and transmits a handoff PBU signaling message to the P-GW 204b (step S211c).
  • the handoff PBU signaling message transmitted in step S211c has a handoff indicator (HI) option set with the value “2”.
  • the P-GW 204b moves the prefix from WiMax access to LTE access, updates the binding cache, and returns an appropriate PBA signaling message (not shown in FIG. 2C) to the S-GW 201b.
  • the UE 200b After performing the above-mentioned vertical handoff process, the UE 200b sets a change filter rule related to the filter group FG2 of the filter rule.
  • the UE 200b predicts that it is no longer a chain scenario, and estimates that the filter group FG2 of the changed filter rule needs to be set to the P-GW 204b.
  • the UE 200b may infer from the information provided from the network that it has moved from the chain state to the non-chain state, or the HPLMN supports the mobility anchor chain state, while the HPLMN supports the mobility anchor chain state. It may be understood that the state is not supported.
  • the UE 200b When the UE 200b is connected to the local domain (HPLMN) 216b, the mobility anchor in the chain state is not used in the general operation of the 3GPP architecture.
  • the UE 200b in order to set a modified filter rule related to the filter group FG2, the UE 200b selects an interface suitable for efficient filter rule setting, and selects an interface connected to the local domain (HPLMN) 216b. To do. Since the UE 200b knows that the filter group FG2 related to the changed filter rule is to be set in the P-GW 204b, the use of the interface connected to the local domain (HPLMN) can quickly set the filter rule. Can be predicted. The UE 200b transmits a change filter rule signaling message related to the filter group FG2 (step S212c), and is transferred from the S-GW 201b to the P-GW 204b (step S213c).
  • the filter rule related to the filter group FG1 is transmitted from the S-GW 205b to the P-GW 204b by the signaling message in step S209c.
  • the changed filter rule related to the filter group FG2 and the unmodified filter rule related to the filter group FG1 are finally managed by the P-GW 204b after the vertical handoff switching process 209b.
  • the filter rule related to the UE 200b is stored in the P-GW 204b.
  • the filter rule indicating whether or not it is valid after the vertical handoff is tagged, and the filter rule that is not changed is transferred from the local LMA (S-GW 205b) to the global LMA (P-GW 204b).
  • the correct filter rule is set in the P-GW 204b without extra network signaling.
  • APN is an identifier related to a specific service of 3GPP, that is, an identifier related to PDN.
  • the MAG entity can identify the address of the P-GW by analyzing the APN.
  • FIG. 2D is a diagram illustrating a third example of the network configuration for explaining the operation in the embodiment of the present invention
  • FIG. 2E is a sequence illustrating the third example of the operation in the embodiment of the present invention. It is a chart. 2D illustrates a network configuration that requires tagging of filter rules related to APN
  • FIG. 2E illustrates efficient filter rule setting in the network configuration illustrated in FIG. 2D. , Signaling messages used to transmit the APN are illustrated.
  • the UE 200d is connected to the local network domain 205d via the LTE interface and the WLAN interface.
  • the UE 200d is connected to the S-GW 203d via the access network 201d, and is connected to the ePDG 204d via the access network 202d.
  • the UE 200d receives services from two different PDNs (for example, a PDN 211d connected to the P-GW 209d and a PDN 212d connected to the P-GW 210d).
  • UE 200d receives a service from PDN 211d through both interfaces.
  • PBU signaling to PDN 211d for PDN connection setup is indicated by signaling messages 206d and 207d.
  • the ePDG 204d sends a PBU signaling message 208d for PDN connection setup to the P-GW 210d.
  • the UE 200d has acquired the prefixes P3, P1, and P2 through the PBU signaling messages 206d, 207d, and 208d, respectively.
  • the UE 200d may be trying to set a filter rule in order to receive better QoS for the flow, or to obtain low cost and high security.
  • the UE 200d determines the setting of filter rules such as P2 (transfer prefix) ⁇ P3, P1 (transfer prefix) ⁇ P3, P3 (transfer prefix) ⁇ P1, and the like.
  • the above filter rule means that the flow associated with a prefix with a destination address (forwarding prefix) should be sent via an access that handles the second prefix in the filter rule.
  • the filter rule: P2 (forwarding prefix) ⁇ P3 means that it is desirable that the flow related to the prefix P2 is sent via the LTE interface (related to the prefix P3).
  • the above filter rule is an example, and various filter rules can be set depending on the intention of the UE 200d.
  • the forwarding mechanism between P-GWs works for data packet forwarding when the filter rules are set to the correct P-GW.
  • P2 transfer prefix
  • the data packet arrives at the P-GW 210d and is passed to the P-GW 209d to receive the correct interface (LTE interface of the UE 200d) Sent to.
  • the UE 200d has two main devices in the optimization process.
  • the first contrivance is to determine whether a filter rule can be transmitted by one or a reduced filter rule signaling message in order to reduce a plurality of filter rule signaling messages transmitted from the UE 200d.
  • a second idea is to determine additional information to be inserted when the filter rule signaling message is combined as one filter rule signaling message. The additional information is information necessary for the MAG to transfer the filter rule to the correct P-GW.
  • the UE 200d predicts whether the prefix of the filter rule to be transferred is managed by a different P-GW.
  • the UE 200d can grasp this by various means. For example, it can be grasped from the fact that a different APN is associated with the prefix assigned to the UE 200d. Moreover, UE200d can be grasped
  • the UE 200d confirms whether or not the three filter rules can be transmitted as one filter rule signaling. This is the first contrivance regarding the reduction of signaling related to the filter rule.
  • the UE 200d confirms whether or not the transfer prefix related to the three filter rules is notified from the same MAG entity. If the forwarding prefix associated with all three filter rules is known by one MAG, the filter rules can be combined and sent to the MAG as one filter rule signaling message. If it can be sent to the MAG as a single filter rule signaling message, no additional filter rules need to be tagged in connection with the APN.
  • the UE 200d determines the filter rules of P2 (transfer prefix) ⁇ P3 and P1 (transfer prefix) ⁇ P3. As a result, the ePDG 204d recognizes the P-GW related to the transfer prefixes P1 and P2. Similarly, since the transfer prefix P3 has been notified via the LTE access, the UE 200d recognizes that the filter rule P3 (transfer prefix) ⁇ P1 can be transmitted via the LTE interface.
  • the three filter rules need to be transmitted via different interfaces, and as a result, a plurality of filter rule signaling is performed, so that the UE 200d can optimize the three filter rule signaling at a finer level. It is possible to correctly predict that it will be necessary.
  • an example of an optimization method in this case is to check whether a plurality of forwarding prefixes related to three filter rules belong to a single APN but are notified by different interfaces. . If it can be confirmed that multiple forwarding prefixes belong to a single APN but are advertised by different interfaces, the filter rules signaling of forwarding prefixes belonging to the same APN are combined into a single group. They can be grouped and transmitted over a single interface. After grouping based on APN, the UE informs the MAG to send to the P-GW filter rules associated with known forwarding prefixes in the filter group.
  • the UE 200d adds APN information to the filter rule to be transmitted.
  • the APN related to the prefix is also notified to the UE 200d, so the UE 200d knows the APN related to the prefix. Then, the UE 200d specifies whether or not a single interface can be used to transmit all three filter rules based on the APN information.
  • the UE 200d concludes that the filter rules can be transferred via the WLAN or LTE interface with respect to the filter rules P1 ⁇ P3.
  • prefix P3 is related to APN1, and APN1 can be confirmed in the LTE and WLAN interfaces
  • UE 200d concludes that the filter rules can be transferred via the WLAN or LTE interface also regarding filter rules P3 ⁇ P1. It is done.
  • the prefix P2 is related to the APN2, and the APN2 can be confirmed only by the WLAN interface, the UE 200d concludes that the filter rule can be transferred only via the WLAN interface with respect to the filter rule P2 ⁇ P3.
  • a single interface in this case, a WLAN interface
  • the UE 200d determines that the filter rule P3 (forwarding prefix) ⁇ P1 and Filter rule P1 (forward prefix) ⁇ P3 is classified into one group. Since the transfer prefixes of these filter rules belong to the same APN1, they are classified into one group. Furthermore, the UE 200d classifies the filter rule P2 (forward prefix) ⁇ P3 into the second group. However, since the UE 200d has specified that all filter rules can be transmitted via the WLAN interface, in the second step of the optimization process, the UE 200d converts the two filter groups of the filter rule into one filter rule signaling message. To join.
  • a filter group of filter rules inserted in a single signaling message will forward all filter rules in the filter group to the P-GW corresponding to the APN associated with the known forwarding prefix in that filter group.
  • Information for notifying the ePDG 204d to be tagged is tagged.
  • the ePDG 204d knows only the forwarding prefix P1, but the tags related to the filter rule of the first filter group are the same in the filter rule P3 ⁇ P1 and the filter rule P1 ⁇ P3. It means to transfer to P-GW.
  • the second filter group includes only one element (one filter rule), and the ePDG 204d can correctly specify the P-GW related to the forwarding prefix.
  • UE200d transmits the single signaling message shown by FIG. 2E, if two groups are identified and tagged (step S205e).
  • the signaling message having the filter group and the tag transmitted in step S205e is received by the ePDG 204d.
  • the ePDG 204d When the ePDG 204d specifies the P-GW, it passes the filter rule to each P-GW. The ePDG 204d specifies that the filter rule P1 ⁇ P3 and the filter rule P3 ⁇ P1 should be transmitted to the P-GW 209d, and that the filter rule P2 ⁇ P3 should be transmitted to the P-GW 210d. Then, the ePDG 204d transmits a filter path signaling message to the P-GWs 209d and 210d (Steps S206e and S207e). Note that the filter path signaling message transmitted in steps S206e and S207e has a filter rule that is not tagged with an APN.
  • efficient filter rule setting is performed by preventing unnecessary filter rule path signaling.
  • the main advantage of this method is that the ePDG 204d can specify the address of the P-GW to which the filter rule is transferred only by referring to the binding update list.
  • the forwarding prefix P1 exists in the binding update list of the ePDG 204d, for example, when the first filter group is scrutinized, the ePDG 204d is stored in the binding update list and is associated with the prefix P1. -The address of the GW 209 can be easily specified. Similarly, for the second filter group, the ePDG 204d can identify the P-GW 210d associated with the prefix P2. In this way, the ePDG 204d can identify the correct P-GW without analyzing the APN, so the processing load on the MAG is reduced. Note that the method according to this embodiment is applicable not only to the above-described configuration but also to other configurations.
  • the UE After identifying a single interface that transmits all filter rules, the UE predicts whether the MAG knows the forwarding prefix of the filter rule and selectively adds an APN tag. Furthermore, in the method according to the present invention, if the MAG does not have the forwarding prefix of the filter rule in the binding update list, the UE uses the APN tagging to pass the filter rule to the P-GW. Specify the address. Also, assuming that a single P-GW manages a given PDN, it is possible to correctly identify the P-GW address by an APN analysis mechanism performed at the MAG entity.
  • the network configuration shown in FIG. 2D and the signaling message shown in FIG. 2E will be used.
  • the UE 200d in FIG. 2D performs the selective addition or tagging of explicit APN information to the filter rules, Even if it is determined by the filter rule message that, for example, three filter rules of P2 (forwarding prefix) ⁇ P3, P1 (forwarding prefix) ⁇ P3, P3 (forwarding prefix) ⁇ P1 are transmitted via the same interface. Good.
  • the purpose of the UE to identify the appropriate interface and select explicit APN tagging is to reduce multiple filter rule signaling messages over the radio access medium. It is in.
  • An APN attached to a PLMN or a local network domain can be easily analyzed, and a P-GW address is specified by a MAG entity in a given PLMN.
  • the HPLMN MAG can analyze an APN belonging to the domain.
  • the MAG in the VPLMN can analyze the APN of the HPLMN and identify the P-GW address of the P-GW existing in the HPLMN. is there.
  • the service via the home means providing a prefix belonging to the P-GW derived from the HPLMN when the UE passes through the VPLMN.
  • the UE 200d first searches for an appropriate interface through which all filter rule signaling can be transmitted. Since APN tagging is required when the MAG does not know the forwarding prefix of the filter rule, the UE 200d passes through the combined filter rule signaling before inserting explicit APN information in the filter rule. The MAG confirms whether it can perform the APN analysis. Basically, the UE 200d selects an interface connected to the MAG that can understand the APN associated with the forwarding prefix of the filter rule.
  • FIG. 2D understands that the UE 200d in FIG. 2D is connected to the local domain (HPLMN) 206d, so that the MAG (S-GW 203d) knows all the APNs and can correctly analyze the APNs.
  • UE 200d determines that S-GW 203d may not have established a tunnel with P-GW 210d because APN1 and APN2 are confirmed via WLAN access and only APN1 is confirmed via LTE access. To do.
  • UE 200d may decide not to send the combined filter rule signaling message via LTE access and will select the WLAN interface to send the combined filter rule signaling message.
  • the UE 200d can predict that the S-GW 203d in the local domain (HPLMN) 206d cannot analyze the APN2. This is because it is possible that APN2 is received via an external (foreign) connection interface and that APN2 represents the PDN of the VPLMN.
  • the UE 200d knows that the APN 2 is related to the local breakout service acquired by the VPLMN. The UE 200d may grasp this from information provided from the network, or may grasp this from information statically configured in the UE.
  • the S-GW 203d of the local domain (HPLMN) 206d may not be able to identify the P-GW address even if the APN is analyzed. Therefore, it is important for the UE 200d to select an interface connected to the MAG that knows the APN associated with all the forwarding prefixes of the filter rule. Furthermore, it is assumed that the UE 200d knows each APN managed by a different P-GW from information provided from the network or information statically configured in the UE. From such information, when the filter rule needs to be set correctly, the UE 200d determines to perform APN tagging.
  • the UE 200d After identifying the appropriate interface (WLAN interface), the UE 200d prepares to send the combined filter rule message to the ePDG 204d. After identifying the WLAN interface for setting all three filter rules, the UE 200d identifies the correct tag for the filter rule. The tagging is for the MAG to know where to send the filter rule. For example, regarding the filter rules P1 ⁇ P3, since the ePDG 204d knows the prefix P1, no explicit APN tagging is necessary. On the other hand, regarding the filter rule P3 ⁇ P1, since the ePDG 204d does not know the prefix P3, it is necessary to explicitly tag the APN1 related to the prefix P3.
  • the UE 200d transmits the combined filter rule signaling to the ePDG 204d (step S205e).
  • the ePDG 204d identifies the P-GW address using the forwarding prefix in the filter rule. In this case, the ePDG 204d checks the binding update list and finds the P-GW address related to the forwarding prefix of the filter rule. On the other hand, if the explicit APN information is tagged, the ePDG 204d analyzes the APN or searches the binding update list to identify the P-GW address related to the APN.
  • the ePDG 204d when the ePDG 204d specifies the address of the P-GW, it transmits the filter rules P1 ⁇ P3 and P3 ⁇ P1 to the P-GW 209d by a single signaling message (step S206e). Then, the filter rule P2 ⁇ P3 is transmitted to the P-GW 210d by another signaling message (step 207e).
  • FIG. 3A is a diagram illustrating a first example of operation of a UE in the embodiment of the present invention.
  • the UE confirms or predicts whether there is a change in the network entity that handles the filter state of the UE after the vertical handoff process. For example, as described in the above embodiment, after the vertical handoff, the network entity that handles the filter rule may be changed. The UE predicts network entity changes based on information provided from the network or based on information statically stored in the UE.
  • Step S303a the UE determines that it is not necessary to tag a valid filter rule after the vertical handoff.
  • the UE sets the current filter rule (that is, the filter rule before the vertical handoff) in the local network domain without performing tagging.
  • step S302a the UE predicts whether the current filter rule associated with a flow will remain or be changed after a vertical handoff.
  • the UE may predict a change related to the filter rule by using ANDSF information, a policy stored in the UE, or the like.
  • step S303a the UE configures the current filter rule without tagging and sets the current filter rule in the network entity.
  • step S304a the UE first groups the filter rules that are valid after the vertical handoff, and sets the appropriate filter rule to the filter group. Assign tags and add tags, and send tagged filter rules to network entities.
  • step S304a after identifying the current filter rule, the UE groups the current filter rule that is not changed after the vertical handoff into one filter group, and the filter rule that is changed after the vertical handoff is changed to another filter group. Group. After classification of the filter rules, the UE adds an appropriate tag to the grouped filter rules for effectiveness after vertical handoff and after tagging notifies the network entity of the tagged filter rules.
  • step S304a a more detailed example will be described.
  • the UE has flows indicated by flow identifiers (FID) F1, F2, F3, and F4 and predicts whether the filter rules for these flows will be changed after vertical handoff.
  • the UE may not know the exact filter rules after vertical handoff for these flows, but at least it can predict in advance whether the filter rules will change after vertical handoff.
  • the UE In the prediction of the UE, if the filter rules related to the flows F1 and F4 are not changed after the vertical handoff, the UE groups the filter rules related to the flows F1 and F4 and adds a tag indicating no change. Similarly, the UE groups the filter rules associated with flows F2 and F3 as filter rules that are changed after a vertical handoff and adds a tag indicating the change. After grouping and tagging the current filter rule to be set in the local network domain, the UE notifies the network entity of the filter group of the tagged filter rule. When the tag is indicated by a flag, whether or not the flow is changed after the vertical handoff may be indicated by whether or not the flag is set.
  • Step S304a After performing the vertical handoff, the UE checks in step 305a whether the tagging of the filter rules prior to completion of the vertical handoff is correct. When Step S305a is “Yes”, the UE sets only the changed filter rule for the tagged group (the group classified as the changed filter rule) in Step S306a.
  • step S305a is “No”
  • the UE knows in step S307a that the prediction that the filter rule is valid after the vertical handoff was not correct, and all the filter rules to be changed after the vertical handoff. Set the modified filter rule for.
  • the condition for tagging is not limited thereto.
  • the handover destination network is a network managed by an operator different from the network before the handover, that is, if the roaming is performed, the filter rule is changed.
  • Tagging may be performed by determining that it is necessary.
  • the handover destination network is a network of an access type different from that before the handover, tagging may be performed by determining that the filter rule needs to be changed.
  • the filter rule is changed when a handover is performed from a reliable network to an untrusted network (or vice versa). You may decide that it is necessary.
  • both a path directly accessible to an external network (such as the Internet) via the home eNB and a path connected to the 3GPP core network via the home eNB Assume a UE that can be established. Such a UE determines whether or not the flow information registered in the P-GW when connected to the macro eNB is valid even after handover from the macro eNB to the home eNB. You may go. In this case, when the P-GW detects that the UE has handed over from the macro eNB to the home eNB, the P-GW transfers the flow information tagged as valid even after handing over to the home eNB to the home eNB.
  • HeNB home eNB
  • the UE can switch the transfer destination to a path that can be directly accessed from the Non-3GPP network to the external network after handover to the home eNB. If it is determined that the flow information is valid even after handover to the home eNB, the information may be added to the P-GW and registered. When the P-GW holding this flow information detects that the UE has handed over from the macro eNB to the home eNB, the P-GW designates the transfer destination of the flow information designated as valid even after handing over to the home eNB.
  • the home eNB may change the transfer destination of the acquired flow information to a path directly connected to the external network.
  • UE does not need to register the flow information applied to the path
  • the flow information can be applied to transfer the flow.
  • the flow information registered in the home eNB is tagged based on the determination as to whether or not it is valid even after handover to the macro eNB. You may attach In this case, only valid flow information is notified from the home eNB to the P-GW even after the UE has handed over to the macro eNB.
  • the home eNB may determine whether the flow information is valid even after handover to the macro eNB. For example, when the flow transferred from the UE via the path connected to the 3GPP core network is switched to the path directly connected to the external network, the home eNB indicates that the path for transferring the flow is switched. P-GW or ANDSF server). As a result, the P-GW can know that the flow that has been transferred through the 3GPP core network has started to be transferred on the path that does not pass through the 3GPP core network.
  • FIG. 3B is a diagram illustrating a second example of operation of the UE in the embodiment of the present invention.
  • the UE first predicts in step S300b whether this is a multiple PDN and multiple P-GW scenario. Similar to the above example, the UE can predict multiple PDNs and multiple P-GWs from information provided from the network or information statically configured in the UE.
  • Step S300b When Step S300b is “No”, the UE performs the process of Step S301b.
  • the UE In the case of not a multiple P-GW environment, there is no problem even if a filter rule whose forwarding prefix is related to multiple APNs is set in a single filter rule signaling message. Therefore, when transmitting a filter rule as a single signaling message in step S301b, the UE does not add APN related information.
  • Step S300b the UE performs the optimization process described in the above-described embodiment in Step S302b.
  • the UE confirms whether the forwarding prefix of the filter rule belongs to the same APN.
  • the UE can group the filter rules into one group. Note that the filter rules of one filter group all have transfer prefixes belonging to the same APN. As long as the grouping performed by the UE knows the forwarding prefix of the filter rule included in the APN or its group, the MAG can specify the P-GW address.
  • the UE specifies a single interface for transmitting a plurality of filter rule signaling.
  • the UE classifies the interfaces that a filter group of a given filter rule can transmit, and identifies a common (single) interface for transmitting the filter groups of all filter rules.
  • This specification is performed by specifying a network that grasps all APNs corresponding to each filter group.
  • step S304b a tag indicating whether or not the filters are grouped in step S302b is added and then inserted into a single filter rule signaling message and passed to the network entity.
  • Tagging is a trigger to a network entity, which treats all filter rules in the tagged group as belonging to the same APN.
  • the UE When tagging by such non-explicit APN (grouping filter groups based on APN and adding information indicating that each group belongs to the same APN) is performed, the UE performs grouping. Pass the filtered filter rule signaling message to the network entity.
  • FIG. 3C is a diagram illustrating a second example of operation of the UE in the embodiment of the present invention.
  • step S300c the UE predicts whether the UE is a multiple PDN and multiple P-GW scenario. Similar to the above description, the UE can predict the multiple P-GW and multiple PDN environments from information provided from the network or information statically preconfigured in the UE.
  • Step S301c is executed by the UE.
  • the UE does not add the APN related information when transmitting the filter rule as a single signaling message in step S301c.
  • Step S300c if Step S300c is “Yes”, the control moves to Step 302c.
  • a method in which explicit APN information is added when multiple filter rule signaling is transmitted together is used, so that the UE relates to the forwarding prefix of the filter rule in step S302c.
  • Step S303c is executed by the UE. If a single MAG is not identified in step S302c, the filter rules need to be grouped to transmit using multiple filter rule signaling. Furthermore, the APN associated with a given group needs to be analyzed by the MAG entity through which the filter group of the filter rule passes.
  • step S304c basically represents that the UE decides to combine all the filter rules with selective and explicit APN tags in one signaling message. Also, this step S304c represents that the UE decides to transmit a single filter rule signaling message through the MAG specified in step S302c.
  • step S305c the UE checks whether the transfer prefix of the filter rule is stored in the MAG specified in step S302c. If it is not stored in the MAG, “NO” is determined in the step S305c. In this case, the UE knows that APN tagging is necessary, and in step S307c, the filter rule is tagged with explicit APN information related to the forwarding prefix of the filter rule.
  • step S305c is “Yes”
  • step S306c the filter is not subjected to explicit APN tagging
  • step S308c is performed.
  • the UE combines all filter rules. Some filter rules are APN-tagged and others are not APN-tagged, and are transmitted via a MAG entity that knows all tagged APNs.
  • the functional architecture of the UE has a decision function that determines the necessity of tagging a filter rule, a tagging function that tags the filter rule with appropriate information, and a notification function that notifies the network of the tagged filter rule. is doing.
  • the functional modules in the functional architecture of the UE will be described with reference to FIG.
  • FIG. 4 is a diagram illustrating an example of a configuration of the UE in the embodiment of the present invention.
  • the functional architecture 400 of the UE shown in FIG. 4 has one or more lower layer protocol modules 403, a layer 3 protocol module 402, and an upper layer protocol module.
  • Each lower layer protocol module 403 is a functional block including all hardware and software necessary for the UE to communicate with other nodes via a communication medium.
  • the lower layer protocol module represents components of layer 1 (physical layer) and layer 2 (data link layer), firmware, driver, and communication protocol.
  • the functional architecture 400 will include one or more lower layer protocol modules 403, each associated with each UE interface (eg, WiMAX, LTE, etc.). Let's go.
  • the layer 3 protocol module 402 further includes an IPv6 routing unit 406, a PMIP multihoming support unit 407, a filter rule tagging determination unit 408, and a filter rule tagging unit 409. Furthermore, these units have an appropriate interface for passing signaling messages and data messages between the units.
  • the IPv6 routing unit 406 realizes a neighbor search, an address configuration, and a basic IPv6 routing mechanism. Further, the PMIP multihoming support unit 407 has functions such as determination of filter rules, configuration of filter rule signaling messages, and actual notification of filter rule signaling. Further, the PMIP multihoming support unit 407 has a data packet reception function in the multihoming operation. Basically, the PMIP multihoming support unit 407 can receive a data packet through an interface having a global IPv6 address different from the destination address of the data packet. The PMIP multihoming support unit 407 has a function of notifying an access router connected to the UE that the UE is capable of multihoming.
  • the interface 410 represents an interconnection between the PMIP multihoming support unit 407 and the IPv6 routing unit 406, and a filter rule signaling message is exchanged between these two units. Further, the interface 410 is used to make an inquiry about the validity of the destination address existing in the data packet from the IPv6 routing unit 406 to the PMIP multihoming support unit 407.
  • the filter tagging determination unit 408 is a determination function for specifying the necessity of tagging the filter rules. As described in the above embodiments, when the UE predicts that the filter rule is changed after the vertical handoff, and when the UE predicts that the filter rule is passed between the network entities after the vertical handoff. It is determined that tagging is necessary. The tagging determination unit 408 executes tagging determination based on such prediction. Furthermore, in a multiple P-GW environment, when multiple APN related filter rules need to be set as a single signaling message, the UE filter tagging determination unit 408 needs to tag the filter rules. Determine whether or not.
  • the filter tagging unit 409 of the UE has a function of actually performing tagging.
  • the filter tagging unit 409 determines an actual parameter inserted as a tag in the filter rule.
  • the filter tagging unit 409 indicates a tag indicating the effectiveness after the vertical handoff Is added to the filter rule.
  • the filter tagging unit 409 Add an appropriate APN tag to the filter rule.
  • the filter tagging unit 409 determines whether to use explicit or non-explicit APN tagging. In addition, the determination regarding tagging of APN which is not explicit or not explicit is made based on rules set in advance in the UE, or based on the capability of the MAG to which the UE is connected.
  • a combined filter rule signaling message is sent to the PMIP multihoming support unit 407 through the signaling interface 411.
  • the filter tagging unit 409 When the filter rule is set by the layer 3 signaling message, the filter tagging unit 409 passes the tagged filter rule signaling message to the PMIP multihoming unit 407. When the tagged filter rule is transmitted by a method specific to layer 2, the filter tagging unit 409 passes the filter rule to the lower layer protocol module 403 through the signaling interface 405.
  • the upper layer protocol module 401 includes upper layer protocols such as a transport layer protocol and an application layer protocol, for example.
  • the upper layer protocol module also cooperates with the layer 3 module 402 through the interface 404. Note that each of the above functional modules is merely an example for realizing the function of the UE according to the present invention, and there are many methods for realizing the function of the UE according to the present invention without departing from the scope of the present invention. .
  • FIG. 5 illustrates an LMA architecture 500 in accordance with the present invention.
  • FIG. 5 is a diagram showing an example of the configuration of the LMA in the embodiment of the present invention. Note that the LMA function described here is applicable to the proxy LMA and may be implemented in the proxy LMA.
  • the LMA functional architecture 500 includes one or more lower layer protocol modules 502 and a layer 3 protocol module 501.
  • An appropriate interface 503 exists between these modules 501 and 502.
  • the layer 3 functional module 501 further includes an IPv6 routing unit 504, a PMIP protocol support unit 505, a PMIP multihoming unit 506, a filter tagging processing unit 508, and a filter tagging management unit 507.
  • the above units work together using appropriate interfaces. These interfaces are also illustrated in FIG.
  • Each lower layer protocol module 502 is a functional block including all hardware and software necessary for the UE to communicate with other nodes via a communication medium.
  • the lower layer protocol module represents components of layer 1 (physical layer) and layer 2 (data link layer), firmware, driver, and communication protocol.
  • the functional architecture 500 will include one or more lower layer protocol modules 502, each associated with each LMA interface (eg, WiMAX, LTE, etc.).
  • the IPv6 routing unit 504 has a basic routing mechanism within one hop, an address configuration of a local mobility anchor associated with the ingress and egress interfaces, a normal packet routing, and a neighbor search mechanism.
  • the PMIP protocol support unit 505 is responsible for all pure LMA type functions. Note that the above LMA type function means that the PMIPv6 cache related to the prefix associated with the UE is maintained, the packet is tunneled to the UE interface via the MAG, and the PBU is processed to generate the PBA.
  • the PMIP protocol support unit 505 has an interface 509 with the IPv6 routing unit 504. This interface 509 is used to process and send signaling packets and data packets using the PMIPv6 cache.
  • the PMIP multihoming unit 506 in particular, realizes a multi-homing function in the local network domain, PMIPv6-related filter rule processing, generation and maintenance of a PMIPv6 multi-homing-related binding cache (that is, use of a single prefix via multiple interfaces) It deals with providing the validity of one UE's prefix to multiple MAG entities.
  • the PMIP protocol support unit 505 communicates with the PMIP multihoming unit 506 via the interface 510.
  • This interface 510 is used for passing a filter rule related message between the two units described above.
  • the PMIP multihoming unit 506 receives the tagged filter rule from the PMIP protocol support unit 505 through the interface 510. If the filter rule tag is not related to the APN, the PMIP multihoming unit 506 passes the filter rule to the filter rule tagging processing unit 508 via the interface 512.
  • the filter tagging processing unit 508 processes the received message with the filter tag added.
  • tags indicating that the filter rules are changed after the vertical handoff are attached to the filter rules, these filter rules are not passed from the filter tagging processing unit 508 to the filter tagging management unit 507. Instead, the filter tagging processing unit 508 passes the filter rule to the PMIP multihoming unit 506 through the interface 512 after the vertical handoff.
  • the filter tagging processing unit 508 passes, to the filter tagging management unit 507, the tagged file rules classified as not changed after the filter rule processing. Further, the filter tagging processing unit 508 uses the interface 513 to pass the filter rule classified as not changed.
  • the filter tagging management unit 507 When a vertical handoff is performed and the LMA PMIP protocol support unit 505 detects this vertical handoff, the filter tagging management unit 507 is notified of this vertical handoff event by an appropriate trigger transmitted through the interfaces 510 and 511. The When receiving the vertical handoff event, the filter tagging management unit 507 transmits a filter rule that is not changed to the PMIP multihoming unit 506 through the interface 511. Upon receiving unchanged filter rules from the filter tagging manager 507, the PMIP multihoming unit 506 knows that these filter rules need to be passed to another gateway entity. The PMIP multihoming unit 506 passes a filter rule that is not changed to the PMIP protocol support unit 505 and further instructs the global LMA to pass a filter rule that is not changed.
  • filter rule signaling composed of filter rules that are not changed is configured and transmitted to the lower layer via the interface 503, and packet encapsulation, processing, and transmission are performed.
  • the LMA can also be realized by another method.
  • the MAG entity receives tagged filter rule signaling from the UE and embeds the received signaling content in a new message.
  • the filter rule signaling message used between the UE and the access network can be realized by using a layer 2 signaling message, for example, as illustrated in a frame 607 of FIG. 6A.
  • FIG. 6A is a diagram showing a first example of a format of a filter rule signaling message transmitted from the UE to the access network in the embodiment of the present invention.
  • the first field is a flag field 600 indicating the start of the frame
  • the second field has a media access control (MAC) address field 601.
  • the MAC address field 601 includes a frame source and destination address.
  • the third field is a control field 602 indicating that a specific type of frame is used
  • the fourth field is a protocol identifier (ID) field 603.
  • the protocol identifier field 603 is a value related to a packet generated at a higher layer. If the filter rule tagging signaling is generated at L2, the contents of the protocol identifier field 603 will be NULL. Note that the tagged filter rule signaling can be generated at layer 2, but the decision to transmit the tagged filter rule and related parameters to be inserted needs to be specified from layer 3.
  • the field following the protocol identifier field 603 is an information field 604.
  • This information field 604 is used to transmit all filter rules with appropriate tags as disclosed in the present invention.
  • the information field 604 can be composed of a first part that transmits a tag and a second part that transmits all tagged filter rules. There may be a plurality of information fields 604.
  • FIG. 6B shows a combined filter rule signaling 614 with a tag that is realized as an ICMPv6 (Internet Control Message Protocol) version 6 message. Note that an ICMPv6 message with a new type value is considered to be used to represent the signaling message 614.
  • FIG. 6B is a diagram showing a second example of a format of a filter rule signaling message transmitted from the UE to the access network in the embodiment of the present invention.
  • the first field of the filter rule signaling message 614 indicates an IPv6 header.
  • the source address field in the IPv6 header field 615 includes the IPv6 address of the interface through which the mobile node transmits the filter rule signaling message, and the destination address field is the IPv6 address of the MAG.
  • the first subfield is a type field 617 containing type information.
  • the filter rule signaling message is preferably transmitted using a new type value, and the structure of the ICMPv6 message is determined by the used type value.
  • the subsequent second field is a code type field 618, and the difference in message information is indicated by the code value included in this field.
  • the code value can indicate that the type of tagging (eg, whether tagging is associated with an APN or whether it is a valid type after vertical handoff) is being used. .
  • Field 620 includes a filter rule with a tag, and its internal structure may have a first part that transmits a tag and a second part that transmits a filter rule associated with the tag.
  • FIG. 6C is a diagram showing a first example of a format of a filter rule signaling message transmitted from the MAG to the LMA in the embodiment of the present invention.
  • the signaling message 608 illustrated in FIG. 6C has an IPv6 header 609.
  • the source address field of the IPv6 header 609 is an MAG address
  • the destination address field is an address of a gateway node such as an LMA or a proxy LMA.
  • an authentication header 610 Following the IPv6 header 609, there is an authentication header 610.
  • the authentication header 610 has information for providing the required signaling validity information to the LMA.
  • the data field 613 includes a tagged filter rule.
  • the data field 613 includes a first part that carries a tag and a second part that carries a filter rule associated with the tag.
  • the filter rule signaling message generated by MAG may be a normal PMIPv6 mobility header (for example, PBU: Proxy Binding Update). In this case, a new flag or a new mobility option is added. .
  • a message 621 in FIG. 6D is illustrated as message 621 in FIG. 6D.
  • FIG. 6D is a diagram showing a second example of the format of the filter rule signaling message transmitted from the MAG to the LMA in the embodiment of the present invention.
  • the message 621 in FIG. 6D has an IPv6 field 622, an authentication header 623, and a PMIPv6 mobility header 624.
  • the PMIPv6 mobility header 624 includes a standard field 625 and a field 626 for transmitting a tagged filter rule.
  • the field 626 may be a new mobility option or a PMIPv6 mobility header field.
  • the structure of this field 626 may also include a first part that transmits a tag and a second part that transmits a filter rule associated with the tag.
  • FIG. 7 is a diagram showing an example of the configuration of the MAG in the embodiment of the present invention.
  • the functional architecture of the MAG has one or more lower layer protocol modules 702 and a layer 3 protocol module 701.
  • Each lower layer protocol module 702 is a functional block including all hardware and software necessary for the UE to communicate with other nodes via a communication medium.
  • the lower layer protocol module represents components of layer 1 (physical layer) and layer 2 (data link layer), firmware, driver, and communication protocol.
  • the functional architecture 700 will include one or more lower layer protocol modules 702 that are each associated with each MAG interface (eg, WiMAX, LTE, etc.).
  • the layer 3 protocol module 701 includes an IPv6 routing unit 704, a PMIP protocol support unit 705, a PMIP multihoming unit 706, a tagged filter group analysis unit 708, and an APN analysis unit 708.
  • IPv6 routing unit 704 includes an IPv6 routing unit 704, a PMIP protocol support unit 705, a PMIP multihoming unit 706, a tagged filter group analysis unit 708, and an APN analysis unit 708.
  • PMIP protocol support unit 705 includes a PMIP protocol support unit 705, a PMIP multihoming unit 706, a tagged filter group analysis unit 708, and an APN analysis unit 708.
  • the IPv6 routing unit 704 handles all mechanisms such as neighbor search, address configuration, and basic IPv6 routing, and adds, deletes, and examines standard IPv6 headers for messages. Further, the PMIP protocol support unit 705 has a function of creating a PBU and processing a PBA.
  • the PMIP protocol support unit 705 holds a binding update list for a plurality of UEs, and also processes data packets related to PMIPv6-related tunneling.
  • the PMIP protocol support unit 705 and the IPv6 routing unit 704 cooperate using an interface 709. This interface 709 is indispensable for realizing PMIPv6 functions related to signaling messages and data messages.
  • the PMIP multihoming unit 706 performs processing for the filter rule received from the UE, and further performs processing for transmitting a filter rule signaling message to the LMA.
  • the PMIP multihoming unit 706 extracts the filter rule inserted in the filter rule signaling message received from the UE, and further constructs an appropriate container into which the filter rule information is inserted.
  • the PMIP multihoming unit 706 constructs an information element that holds an appropriate filter rule, and passes the information element that holds an appropriate filter rule to the PMIP protocol support unit 705 through the interface 710.
  • the filter rule container or information element may be a mobility option or a protocol configuration option.
  • the PMIP protocol support unit 705 inserts the mobility option or protocol configuration option received from the PMIP multihoming unit 706 into the PBU, and passes the filter rule to the LMA. Furthermore, the PMIP multihoming unit 706 stores prefixes related to other interfaces of the UE that are not directly connected to a predetermined MAG. Prior to storing prefixes associated with other interfaces, the PMIP multihoming unit 706 processes prefix validity signaling obtained from the LMA.
  • the tagged filter group analysis unit 708 is used to identify and process the implicit APN tag added to the filter rule.
  • the PMIP multihoming unit 706 passes only the filter rule tagged with the APN related information to the tagged filter group analysis unit 708.
  • the tagged filter group analysis unit 708 processes a filter rule having an APN tag that is not explicit, and passes the filter rule having an explicit APN tag to the APN analysis unit 707 through the interface 713. Then, the tagged filter group analysis unit 708 identifies an APN tagged filter group that is not explicit.
  • the filter group analysis unit 708 searches for a forwarding prefix of the filter rule in a group classified by a predetermined APN tag, and identifies a known forwarding prefix.
  • a known prefix is found during the search process, filter rules belonging to the same filter group as the identified prefix are returned to the PMIP multihoming unit 706 through the interface 712.
  • the PMIP multihoming unit 706 inserts a filter rule passed via the interface 712 into a container such as a mobility option. After inserting the filter rule in the mobility option, the PMIP multihoming unit 706 passes the mobility option and the transfer prefix to the PMIP protocol support unit 705 via the interface 710.
  • the PMIP protocol support unit 705 searches the binding update list, identifies the transfer prefix, and identifies the associated P-GW address. When the PMIP protocol support unit 705 identifies the address of the related P-GW, the PMIP protocol support unit 705 constructs a PBU, inserts a filter, and prepares for transmission.
  • the tagged filter group analysis unit 708 finds an explicit APN tag in relation to the filter rule, it passes the filter rule to the APN analysis unit 707 via the interface 713.
  • the APN analysis unit 707 analyzes the APN and specifies the P-GW address. Note that the APN analysis unit 707 checks the binding update list stored in the PMIP protocol support unit 705 to identify the P-GW address related to a predetermined APN. When the P-GW address is specified, the filter rule and the P-GW address related to the filter rule are returned to the PMIP multihoming unit 706 via the interface 711 for further processing and transmission.
  • the PBU having the filter rule is constructed by the layer 3 protocol module 701, passed to the lower layer protocol module 702, further processed, and transmitted via the interface 703.
  • the MAG may be realized by another method without departing from the scope of the present invention.
  • the present invention has been described here using an embodiment that seems to be the most practical and suitable, those skilled in the art can change the design and parameters without departing from the scope of the present invention. Obviously it may be.
  • a network-based local mobility management domain in which a plurality of mobility management nodes for performing mobility management of a mobile terminal is arranged, and a plurality of packet data networks served by the mobile terminal are connected to the local mobility management domain Communication system
  • the mobile terminal is Means for adding an access point name corresponding to a prefix of the filter rule to a filter rule for the local mobility management domain to filter a communication flow of the mobile terminal; Means for notifying the local mobility management domain of a filter rule to which the access point name is added, and an access node to which the mobile terminal is connected, Means for receiving a filter rule with the access point name attached thereto;
  • a communication system having means for notifying the filter rule to a mobility management node corresponding to the access point name can be provided.
  • a network-based local mobility management domain in which a plurality of mobility management nodes for performing mobility management of a mobile terminal is arranged, and a plurality of packet data networks served by the mobile terminal are connected to the local mobility management domain Communication system
  • the mobile terminal is Means for adding an access point name corresponding to the prefix to a filter rule related to a prefix that is not known by an access node connected via a specific interface; A filter rule to which the access point name is added, and a means for notifying the local mobility management domain via the specific interface of a filter rule to which the access point name is not added.
  • each functional block used in the description of the embodiment of the present invention is typically realized as an LSI (Large Scale Integration) which is an integrated circuit. These may be individually made into one chip, or may be made into one chip so as to include a part or all of them.
  • LSI Large Scale Integration
  • IC Integrated Circuit
  • system LSI super LSI
  • ultra LSI ultra LSI depending on the degree of integration.
  • the method of circuit integration is not limited to LSI, and may be realized by a dedicated circuit or a general-purpose processor.
  • An FPGA Field Programmable Gate Array
  • a reconfigurable processor that can reconfigure the connection and setting of circuit cells inside the LSI may be used.
  • the present invention has the effect of enabling efficient setting of filter rules in a network in which a network-based local mobility management protocol in which a plurality of mobility management nodes are installed is implemented.
  • the present invention can be applied to a telecommunications technology in a network, particularly a technology for setting a filter rule in a local mobility management domain that manages mobility of a mobile terminal.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention porte sur une technique permettant d'établir efficacement une règle de filtrage dans un réseau dans lequel un protocole de gestion de mobilité locale est mis en œuvre sur la base d'un réseau dans lequel une pluralité de nœuds de gestion de mobilité sont placés. Selon la technique, un équipement utilisateur (UE) (200a) qui est connecté à une passerelle de réseau de données par paquets (P-GW) (204a) et réalise une communication détermine une règle de filtrage qui n'est pas modifiée après un transfert vertical et une règle de filtrage qui est modifiée après le transfert vertical et attache une étiquette qui indique le résultat de détermination pour établir une règle de filtrage (étapes S206a, S207a). Dans le cas où l'UE réalise réellement le transfert, l'UE établit une règle de filtrage qui est modifiée après le transfert pour une P-GW (205a) à laquelle l'UE est nouvellement connecté (étapes 208a, 209a), et la P-GW (204a) transfère seulement la règle de filtrage qui n'est pas modifiée après le transfert à la P-GW (205a) à laquelle l'UE est nouvellement connecté (étape S210a).
PCT/JP2010/006444 2009-11-09 2010-11-01 Système de communication, terminal mobile et noeud de gestion de mobilité WO2011055525A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2009-255819 2009-11-09
JP2009255819 2009-11-09

Publications (1)

Publication Number Publication Date
WO2011055525A1 true WO2011055525A1 (fr) 2011-05-12

Family

ID=43969768

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2010/006444 WO2011055525A1 (fr) 2009-11-09 2010-11-01 Système de communication, terminal mobile et noeud de gestion de mobilité

Country Status (1)

Country Link
WO (1) WO2011055525A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2016502315A (ja) * 2012-10-26 2016-01-21 クアルコム，インコーポレイテッド Ｓａｍｏｇベアラ管理のためのシステムおよび方法

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"Multi Access PDN connectivity and IP flow mobility (Release 9)", 3GPP TR 23.861 VL.2.0, May 2009 (2009-05-01), Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Specs/archive/23-series/23.861/23861-120.zip> [retrieved on 20110124] *
H. SOLIMAN: "Flow Bindings in Mobile IPv6 and Nemo Basic Support", DRAFT-IETF-MEXT-FLOW- BINDING-02.TXT, 28 April 2009 (2009-04-28), Retrieved from the Internet <URL:http://tools.ietf.org/html/draft-ietf-mext-flow-binding-02> [retrieved on 20110124] *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2016502315A (ja) * 2012-10-26 2016-01-21 クアルコム，インコーポレイテッド Ｓａｍｏｇベアラ管理のためのシステムおよび方法

Similar Documents

Publication Publication Date Title
US11082852B2 (en) Mobile terminal
US8774039B2 (en) Communication system, mobile terminal, network node, and base station apparatus
US8553689B2 (en) Home agent acting as a proxy for a Mobile Node
US20110103260A1 (en) Binding cache creating method, binding cache creating system, home agent, and mobile node
US20120063428A1 (en) Interface Switching System, Mobile Node, Proxy Node, and Mobile Management Node
US8169966B2 (en) Method and a network node for managing handovers in a packet data communication environment
US20110134869A1 (en) Prefix allocation administration system and mobile terminal, and prefix allocation administration device
KR20140026569A (ko) 셀룰러 네트워크와 ｗｌａｎ을 통합하는 네트워크 조건 하에서의 통신 방법
JPWO2009066438A1 (ja) アドレス割り当て方法、アドレス割り当てシステム、モバイルノード及び代理ノード
US20100208663A1 (en) Communication system, mobile terminal, and network node
WO2011055525A1 (fr) Système de communication, terminal mobile et noeud de gestion de mobilité
US20110116475A1 (en) Vertical handoff method, vertical handoff system, home agent, and mobile node

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10828086

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10828086

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载