EP2129059B1 - Mobiles kommunikationsendgerät und positionsverwaltungsvorrichtung - Google Patents

Mobiles kommunikationsendgerät und positionsverwaltungsvorrichtung Download PDF

Info

Publication number
EP2129059B1
EP2129059B1 EP08738692.6A EP08738692A EP2129059B1 EP 2129059 B1 EP2129059 B1 EP 2129059B1 EP 08738692 A EP08738692 A EP 08738692A EP 2129059 B1 EP2129059 B1 EP 2129059B1
Authority
EP
European Patent Office
Prior art keywords
address
network
communication
mobile
communication route
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP08738692.6A
Other languages
English (en)
French (fr)
Other versions
EP2129059A1 (de
EP2129059A4 (de
Inventor
Masafumi Aramoto
Shohei Yamada
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Sharp Corp
Original Assignee
Sharp Corp
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 Sharp Corp filed Critical Sharp Corp
Publication of EP2129059A1 publication Critical patent/EP2129059A1/de
Publication of EP2129059A4 publication Critical patent/EP2129059A4/de
Application granted granted Critical
Publication of EP2129059B1 publication Critical patent/EP2129059B1/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • H04W64/003—Locating users or terminals or network equipment for network management purposes, e.g. mobility management locating network equipment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/20—Communication route or path selection, e.g. power-based or shortest path routing based on geographic position or location
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/005—Multiple registrations, e.g. multihoming
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
    • H04W80/045—Network layer protocols, e.g. mobile IP [Internet Protocol] involving different protocol versions, e.g. MIPv4 and MIPv6

Definitions

  • the present invention relates to a communication system or the like, including: a mobile communication terminal that includes a plurality of transceivers and connects through the transceivers to a home link that is constructed of a network performing network-basedmobile management and a foreign link; and a position managing apparatus for managing the position of the mobile communication terminal.
  • network-based mobility see non-patented document 1, for instance
  • host-basedmobility see non-patented document 2, for instance
  • IP-layer mobility of a node to permit its continuation of communication with another node at the opposite communication end even if the node changes its connection from one link to another as it moves.
  • Proxy Mobile IPv6 (PMIPv6, hereinbelow) as the network-based mobility disclosed in non-patented document 1 sets up a PMIP network for the network, to which a mobile node is connected, and in which an access gateway (PMA: Proxy Mobile Agent) as a default router for the mobile node and a position managing apparatus (HA: Home Agent) for managing the PMA to which the mobile node attaches itself are defined.
  • PMA Proxy Mobile Agent
  • HA Home Agent
  • the HA assumes the PMA to which the mobile node is connected as the positional information of the mobile node and manages the identification information on the mobile node in association with the identification information on the PMA.
  • the PMA to which the mobile node is connected is continuously updated as the mobile node moves so as to maintain the positional information.
  • the mobile node has a unique IP address which identifies itself and transmits a packet to the PMIP network by designating the IP address for the receiver and sender of the packet to be communicated between mobile nodes.
  • the PMA to be the point of connection of the mobile node in the core network forwards the packet to the HA.
  • the HA determines the PMA to which the destination mobile node is attached, based on the positional information and forwards the packet.
  • a forwarding route is established between the HA and the PMA so that the packet is conveyed between mobile nodes by packet forwarding.
  • the mobile node continues communication by only changing the PMA as a default router as the mobile node moves.
  • the positional information is updated in the PMAs and HA so as to perform packet forwarding to thereby realize communication between mobile nodes.
  • the mobile node continues communication by changing PMAs as it moves, but it can continue using the unique address if it connects to any PMA. This makes it possible to minimize the movement process to be effected by the mobile node and brings about the advantage that the number of control signals can be reduced in the wireless section.
  • MIPv6 Mobility Support in IPv6
  • HA Home Agent
  • a mobile node holds a unique and unvaried IP address that identifies itself on the network, and uses it as the receiver and sender of a transmitted/received packet in communication between mobile nodes. Further, the mobile node acquires an address on a visited network and the acquired address is registered as its positional information to the HA. In the HA, the IP address that identifies the mobile node and the IP address acquired at the visited site for identifying the position are managed in association with each other.
  • the packet which the mobile node sends out to another mobile node is forwarded by the HA based on the address acquired at the visited site.
  • the packet which mobile node 1 transmits to mobile node 2 is forwarded to the HA by tunneling the IP packet having the address of mobile node 1 acquired at the visited site set as the sender and the HA set as the receiver.
  • the HA solves the positional information of mobile node 2 on the receiver side and forwards the transmission packet to the address of mobile node 2 acquired at the visited site, by tunneling the IP packet having the HA set as the sender and the address of mobile node 2 acquired at the visited site set as the receiver.
  • the packets between mobile nodes are delivered in the above way.
  • the mobile node includes a plurality of transmitter-receivers, which each register an address obtained from the networks to which they connect, as their positional information, to the HA.
  • a series of registering procedures is expanded based on MIPv6. The difference from MIPv6 is that the mobile node registers plural positional information addresses to the HA and that the HA and the mobile node have a plurality of packet delivery routes.
  • the HA and the mobile node can transmit a packet using a delivery route selected based on the type of the packet or preferences when the packet is delivered.
  • MobiSplit a Scalable Approach to Emerging Mobility Networks
  • XP002491899 presents a novel architecture, MobiSplit, to manage mobility in future IP-based networks.
  • the proposed architecture separates mobility management in two levels, local and global, that are managed in completely independent ways.
  • the architecture brings flexibility advantages to operators, and is appropriate for the current trend to multiple and very different access providers and operators.
  • One of the features of a MobiSplit terminal is the use of several interfaces concurrently being active.
  • MobiSplit exploits an enhanced version of the MIPv6 stack, allowing i) registration of multiple CoAs associated to the same HoA for the mobility of single flows and ii) assignment of specific flows to interfaces. This implies that single flows are bound to a CoA, which is strictly related to the assigned interface.
  • XP015050112 is related to an architecture overview, packet filter and bindings, and protocol definitions of a filter rule mechanism for multi-access mobile IPv6. When a new filter rule has been created this information must be sent to the filtering peers to make sure that these nodes know which destination address to use if there exist multiple local addresses associated with the mobile node's identity tag.
  • the timing of events that causes changes to the filter rules and the transmission of new filter rules to the filtering peers does not necessarily correspond to a handover event and vice versa.
  • a mobile node has both a WLAN and a 3G interface activated and uses mobile IPv6 with support for multiple simultaneous home registrations.
  • the system is constructed of PMIPv6 and MIPv6 schemes in combination, as shown in FIG. 20 .
  • the HA for PMIPv6 and the HA for MIPv6 are provided in an identical apparatus so that the movement between the PMIP network and the foreign network is managed based on MIPv6 and the movement inside the PMIP is managed based on PMIPv6.
  • the mobile node moves changing its PMA inside the PMIP network, the mobile node performs communication using the MIPv6 home address .
  • the mobile node registers its position to the HA using its care-of address obtained in the foreign network to continue communication.
  • a PMIP network is characterized in that a mobile node receives the same network information if it connects to any of the PMAs on the PMIP network, so as to continue communication using a single address. In other words, this is a method of managing movement of a mobile node inside the PMIP network so as to hide movement to a terminal.
  • a PMIP network can be made large in scale by a trader that manages networks. For example, a communication carrier constructs a large-scale PMIP network that covers all over Japan, and the subscriber terminal can continue communication by connecting to any of the PMAs using a single address.
  • a hot spot that uses an access system such as a WLAN or the like implemented by a trader different from the communication carrier that operates the PMIP network can be presumed.
  • a mobile node can connect to them by including both the transmitter-receiver for accessing the communication carrier network and the transmitter-receiver for accessing the hot spot.
  • the PMIP network is the home link defined based on MIPv6. That is, the HA of PMIPv6 enables the mobile node to perform communication with the home address by managing the PMA which the mobile node connects to, as its positional information.
  • the mobile node moves from the PMIP network to the foreign network, it moves from the home link defined by MIPv6 to the foreign link. Movement management is performed by the HA, which manages correspondence between the home address of the mobile node and its care-of address, to continue communication.
  • the mobile node when the mobile node includes a plurality of transceivers and connects to both the PMIP network and the foreign network simultaneously through respective transceivers, the mobile node realizes simultaneous connection to the home link defined by MIPv6 and the foreign link.
  • a method for a mobile node based on MIPv6 including a plurality of transceivers to perform simultaneous connection to the networks through respective transceivers is defined byMCoA.
  • this method could permit only the connection shown below and could not permit simultaneous connection to both the home link and the foreign link.
  • the HA has a position managing function and also serves as a border router in the home link so as to be connected to the foreign network.
  • the HA has a position managing function but a separate border router for home link is installed to be connected to the foreign network.
  • a packet transmitted to a mobile node from a communication terminal connected to the foreign network is transmitted to the boarder router of the home link by the routing scheme of the conventional internet.
  • the HA receives the packet in place of the mobile node and forwards it to the visited site.
  • the mobile node in the home link receives the packet without intermediary of the HA.
  • ProxyNDP is a HA's function which announces the fact that HA will receive a packet addressed to the mobile node to the home link so as to receive the packet.
  • the HA receives packets by ProxyNDP only when the mobile node is out and makes the ProxyNDP function invalid when the mobile node has returned to the home link so that the mobile node can receive the packets.
  • the HA can initially receive the packet addressed to the mobile node, which the boarder router routed to the home link and can forward it to the visited site.
  • the communication system including: the mobile communication terminal including the plurality of transceivers and connecting through the transceivers to the home link that is constructed of the network performing network-based mobile management and the foreign link; and the position managing apparatus for managing the position of the mobile communication terminal
  • the position managing apparatus when receiving a packet, determines the position of the receiver of the packet based on the positional information storing means stored in the position managing apparatus and sends the packet.
  • the position managing apparatus when a PMIP network is employed as the home link, the position managing apparatus will be able to transmit the packet appropriately to the receiver terminal either by way of the PMIP network or by way of the foreign network.
  • the mobile communication terminal it is possible for the mobile communication terminal to connect to the home link and the foreign link, at the same time. Accordingly, the mobile communication terminal is able to perform communication at any time by way of either of the networks.
  • the address of the router to which the mobile communication terminal connects in the home link and the address acquired by the mobile communication terminal in the foreign link are stored in association with the home address assigned to the mobile communication terminal.
  • one address that is associated with the home address of the mobile communication terminal is selected in accordance with the network that the communication route passes through, to perform communication.
  • the mobile communication terminal is connected to the home link by way of one transceiver and connected to the foreign link by way of another transceiver, to achieve simultaneous connect to the home link and the foreign link.
  • the position managing apparatus stores the plurality of positional information for the mobile communication terminal into the positional information storing means. Accordingly, when a packet is transmitted to the mobile communication terminal, it is possible to determined the route based on the positional information stored in the positional information storingmeans and transmit the packet.
  • the packet communication system in the present exemplary embodiment is constructed of networks conforming to network-based mobility and host-based mobility, and has a configuration that can connect to a PMIP network as the home link and a foreign network as the foreign link at the same time, as shown in FIG. 1 .
  • the position managing apparatus (Home Agent: HA) for performing positional management of mobile nodes in each network is comprised of a single apparatus.
  • PMIP network as a network-based mobility network
  • PMAs Proxy Mobile Agents
  • ARs Access Routers
  • a PMA 30 is provided in the PMIP network and an AR 10 is provided in the foreign network. Further, in the PMIP network, an HA 40 is provided as the position managing apparatus. Connected to the foreign network is a communication device to be the opposite end from the mobile node.
  • a mobile node 20 shown in FIG. 1 is assigned with "HoA (P1::MN1)” as its home address. It is also assigned with "CoA(P2::MN1)” as its care-of address when it connects to the foreign network.
  • FIG. 1 shows only one AR 10, mobile node 20 and PMA 30 as each device, but multiple devices may, of course, be deployed.
  • one example of the network-based mobility network may be a cellular network which a communication carrier that operates to connect cellular phones, a carrier' s network for operating an ISP, or the like.
  • one example of the foreign network for supporting movement based on host-based mobility may be a WLAN, home network, or a carrier network operated by another carrier.
  • Mobile node 20 is a mobile terminal that makes simultaneous connection to a plurality of network accesses such as a cellular mobile terminal, PDA, etc. having mobile node functionality conforming to PMIPv6, MIPv6 and MCoA. It also has the function of establishing simultaneous connection to its home link which is a network-based mobility network and a foreign link which is a host-based mobility network.
  • mobile node 20 includes, as shown in FIG. 2 , a processor 200, a first transceiver 202, a second transceiver 204, a storage 206, a PMIPv6 processor 208, an MIPv6 processor 210 and a packet transmitter 212.
  • Processor 200 is a functional part for controlling mobile node 20, or the functional part executing processes based on a predetermined program to transmit commands and data to diverse functional parts.
  • processor 200 is constructed of a CPU (Central Processing Unit) and the like.
  • First transceiver 202 and second transceiver 204 are each connected to an external antenna, and transceivers for establishing wireless connection to a network.
  • the transceivers perform transmission and reception of packets via respective networks.
  • any technology such as a wireless access system used in wireless LANs, cellular networks, a short-distance wireless access system such as Bluetooth (registered trademark) etc., and the like can be used.
  • Storage 206 is a functional part for storing various kinds of data and programs, in particular, includes an address management table 2062.
  • Address management table 2062 is a table for storing default data for connection based on PMIPv6. It also stores the care-of address as connection information for connection to a foreign network based on MIPv6, the HA address and default router information.
  • FIG. 3 shows one example of the data configuration of address management table 2062.
  • an address as positional information, a default router and a position managing apparatus are stored in a related manner.
  • HoA home address
  • PMA 30 is associated as the default router for connection based on PMIPv6
  • a care-of address (CoA)"P2::MN1” is associated to connect based on MIPv6.
  • CAA care-of address
  • AR 10 is stored as the default router
  • HA 40 is stored as the position managing apparatus.
  • Packet transceiver 212 selects either first transceiver 202 or second transceiver 204 based on address management table 2062 stored in storage 206 and sends out a packet therethrough. Further, it receives a received packet from each transceiver.
  • MIPv6processor 210 is a functional part for performing an MIPv6 process when connection from the PMIP network to the foreign network is implemented. Further, PMIPv6 processor 208 is a functional part for performing transmission and reception of an attachment request and reply when connection to the PMIP network is performed.
  • PMA 30 is an apparatus constructed conforming to PMIPv6.
  • PMA 30 includes a processor 300, a wireless transceiver 302, a wired transceiver 304, a storage 306, a PMIPv6 processor 308 and a packet forwarder 310. Further, an external antenna for communications is connected to wireless transceiver 302.
  • Processor 300 is a functional part for controlling PMA 30, or the functional part executing processes based on a predetermined program to transmit commands and data to diverse functional parts.
  • processor 300 is constructed of a CPU (Central Processing Unit) and the like.
  • Wireless transceiver 302 is a transceiver for establishing wireless connection to mobile node 20 and performs transmission and reception of packets.
  • any of a wireless LAN, a wireless access system used in cellular networks and a short-distance wireless access system such as Bluetooth (registered trademark) etc. can be used.
  • Wired transceiver 304 is a transceiver that is connected by wire to a router or a switch inside the PMIP network, and is a functional part for performing transmission and reception of packets .
  • As the accessing technique for wired connection widely used Ethernet (registered trademark) or the like can be used.
  • Storage 306 is a functional part for storing various kinds of data and programs, in particular, includes an attachment node management table 3062.
  • Attachment node management table 3062 stores attachment mobile nodes and their correspondent forwarding positions (addresses).
  • FIG. 5 shows one example of the data configuration of attachment node management table 3062.
  • attachment nodes are stored in association with forwarding positions.
  • “mobile node 30" and the forwarding position of mobile node 30, "HoA(P1::MN1)" are stored in association with each other.
  • the forwarding designation of nodes that have not been registered in attachment node management table 3062 are registered as "the others". For example, in the case of FIG. 5 , a packet of a node that has not been registered in attachment node management table 3062 will be forwarded to "HA 40".
  • PMIPv6processor 308 is a functional part that notifies HA 40 of the identification information on mobile node 20 and the identification information on PMA 30. Further, the PMA registers into attachment node management table 3062 in storage 306 the fact that the mobile node has attached to itself. Further, the PMA makes a reply to the attachment request to the mobile node.
  • the mobile node can register its position to HA 40 when the mobile node has attached to PMA 30. Further, it is possible to determine the delivery address of the packet addressed to the attached mobile node.
  • Packet forwarder 310 is a functional part for forwarding packets based on attachment node management table 3062. For example, based on the attachment node management table 3062 shown in FIG. 5 , a packet to mobile node 30 will be forwarded to the address of "HoA(P1::MN1)".
  • HA 40 in the present embodiment will be described. As shown in FIG. 6 , HA 40 includes: a processor 400; a PMIP network transceiver 402 for connection to the PMIP network; a foreign network transceiver 404 for connection to a foreign network; a storage 406; a PMIPv6 processor 408; an MIPv6 processor 410; and a packet forwarder 412.
  • Processor 400 is a functional part for controlling HA 40, or the functional part executing processes based on a predetermined program to transmit commands and data to diverse functional parts.
  • processor 400 is constructed of a CPU (Central Processing Unit) and the like.
  • PMIP network transceiver 402 or foreign network transceiver 404 is a transceiver that is connected by wire to a router or a switch and performs transmission and reception of packets.
  • any of the technologies that are widely used in networks, such as Ethernet (registered trademark) and the like can be used.
  • Storage 406 is a functional part for storing various kinds of data and programs, in particular, includes a positional information management table 4062.
  • Positional information management table 4062 stores a mobile node in association with the position (address) of the correspondent mobile node.
  • the MIPv6positional information contains identification information on a mobile node and a care-of address gained on the foreign network to which the mobile node connects.
  • FIG. 7 shows one example of the data configuration of positional information management table 4062.
  • positional information management table 4062 stores a mobile node and the position (address) of the correspondent mobile node.
  • the position of mobile node 20 (HoA(P1::MN1)) is stored as to be PMA 30 and CoA(P2::MN1).
  • PMIPv6 processor 408 is a functional part that, when receiving a position registration signal from PMA 30, registers the positional information into positional information management table 4062 and transmits a reply to PMA 30.
  • MIPv6 processor 410 is a functional part that, when receiving a position registration signal from mobile node 20, registers the position into positional information management table 4062 and transmits a reply to mobile node 20.
  • the packet forwarder is a functional part for forwarding a packet based on positional information management table 4062 stored in storage 406. This controls packet forwarding via PMIP network transceiver 402 or foreign network transceiver 404.
  • mobile node 20 When detection connection to the PMIP network as a network-based mobility network, mobile node 20 makes an attachment request (procedure (a) in FIG. 8 ).
  • mobile node 20 when it is started to operate, or power is turned on, sends an Association Request message for RRC (Radio Resource control) to PMA 30 to which it is going to attach, to make an attachment request.
  • RRC Radio Resource control
  • mobile node 20 receives announcing information from neighboring PMAs and selects PMA 30 based on the result of performing cell search. Specifically, the mobile node notifies the identification information for itself to be identified, such as the global IP address, MAC address or UE-ID defined by specifications such as 3GPP TS23.003V5.2.0 , by the Association Request message so as to make an attachment request.
  • RRC Radio Resource control
  • wireless transceiver 302 receives the Association Request and registers the identification information of mobile node 20 and the fact that mobile node 20 has attached to PMA 30, into attachment node management table 3062 of storage 306.
  • PMA 30 solves HA 40 at the destination to register based on the attachment request from mobile node 20 and transmits a position registering request to HA 40 (procedure (b) in FIG. 8 ) .
  • the method of solving HA 40 may be acquired from the apparatus for managing the correspondence between mobile node 20 and HA 40, such as an AAA server etc. , to which PMA 30 is connected, for example, or it is possible to solve it by storing the receiver management table that previously holds management information of the correspondence between mobile node 20 and HA 40 into storage 306, in advance.
  • PMA 30 notifies the identification information for identifying mobile node 20, such as the global IP address, MAC address or UE-ID, and an IP address for identifying PMA 30 that can be routed inside the PMIP network, as the positional information.
  • HA 40 receives the position registering request from PMA 30, and registers the identification information of mobile node 20 associated to its positional information into positional information management table 4062.
  • the reply message includes the global IP address to be assigned to mobile node 20, or network prefix information of the global IP address to be assigned to the mobile node.
  • HA 40 When HA 40 registers the information on mobile node 20 into positional information management table 4062, then it transmits a position registration reply to PMA 30 (procedure (c) in FIG. 8 ).
  • PMA 30 makes a response to the attachment request from mobile node 20 using RCC Association Response message or the like to the mobile node (procedure (d) in FIG. 8 ) .
  • the reply to the attachment request includes identification information such as the IP address or MAC address of PMA 30 so that mobile node 20 can set PMA 30 as the default router.
  • Mobile node 20 receives the attachment reply from first transceiver 202 and registers PMA 30 as the attachment destination into address management table 2062.
  • This identification information on PMA 30 does not need to be identical with the identification information on PMA 30 registered in HA 40.
  • the IP address notified to HA 40 is the IP address to be used for routing within the PMIP network, whereas the IP address notified to the mobile node is the IP address which the mobile node identifies as the default router.
  • mobile node 20 performs connection to the PMIP network network, in accordance with the procedures defined by PMIPv6 . Further, a forwarding route is established between PMA 30 and HA 40, so that mobile node 20 can perform communications by way of the forwarding route established in the PMIP network.
  • mobile node 20 while keeping connection to the PMIP network, performs connection to the foreign network using another transceiver.
  • Mobile node 20 makes another transceiver or second transceiver 204 receive announcing information from the access router (AR 10) on the network connected to it, to detect connection to the foreign network (procedure (e) in FIG. 8 ) .
  • the announcing information transmitted from AR 10 is IPv6 router announcing information or the like, including information on the network prefix of the connected network in addition to the MAC address and IP address of the access router.
  • Mobile node 20 generates its care-of address based on the network prefix information of the connected network of the received announcing information and transmits a position registering request to HA 40 (procedure (f) in FIG. 8 ).
  • the position registering request to be transmitted should include identification information of the mobile node such as the home address, MAC address or UE-ID etc. , and the care-of address to be the positional information.
  • HA 40 receives the position registering request from mobile node 20 and registers it into positional information management table 4062.
  • Registered into positional information management table 4062 is identification information of the mobile node such as the home address, MAC address or UE-ID etc. , of mobile node 20 in assoication with the positional information, i.e., the care-of address.
  • the aforementioned positional information management table 4062 the same one that is used at the time of position registration in the PMIP network may be used.
  • HA 40 can handle mobile node 20 having a single home address by managing a plurality of positional information at the same time, the care-of address as the positional information in the foreign network and PMA 30 as the positional information in the home link or the PMIP network.
  • HA40 after registration into positional information management table 4062, transmits a position registration reply to mobile node 20 (procedure (g) in FIG. 8 ).
  • Mobile node 20 receives the position registration reply from HA 40 and manages the care-of address or home address and the address of HA 40 as the position managing apparatus, with address management table 2062.
  • the positional information of the PMIP network and the positional information based on the MIPv6 are registered simultaneously in the positional information management table.
  • the HA 40 that manages connection to the home link as the PMIP network receives a connection request from the foreign link, the HA cuts connection to the home link and permits connection to the foreign link.
  • the HA 40 of the present embodiment manages both the connection information without cutting connection to the home link.
  • mobile node 20 connected to the packet communication system in the present embodiment will perform positional registration from the foreign link without cutting off the connection with the home link to manage both connection information.
  • HA 40 which has received the positional registration to the foreign network can keep both the positional information on the home link and on the foreign link.
  • information that indicates either disconnection or simultaneous connection may be newly included to the position registration information in the foreign link, whereby it is possible for HA 40 to determine whether HA 40 manages a plurality of positional information for the mobile node or whether it deletes the holding information and performs new registration, in accordance with the request from mobile node 20.
  • the position registering request in procedure (f) in FIG. 8 is added with a flag and is transmitted.
  • the flag is to be used to determine whether the connection information in the home link should be deleted.
  • HA 40 can perform a plurality of position registration in accordance with the request from PMA 30 as stated above.
  • mobile node 20 transmits an attachment request including the information that shows either cutoff or simultaneous connection, to PMA 30. Further, PMA 30 transmits a position registering request including the information indicating whether the cutoff has been done or simultaneous connection is being established, to HA40. HA 40 is able to determine whether it manages a plurality of positional information for mobile node 20 or whether it deletes the holding information and performs new registration, in accordance with the request from mobile node 20.
  • the attachment request in procedure (a) in FIG. 8 is added with a flag and is transmitted. This flag is used to determine whether the connection information on the foreign network should be deleted.
  • PMA 30 adds the flag included in the attachment request to the position registering request to be transmitted to HA 40 and sends it.
  • connection to the foreign network is achieved after connection with the PMIP network
  • connection to the PMIP network may be achieved after connection with the foreign network
  • FIGS. 9 and 10 are charts for illustrating the process related to position registering at mobile node 20
  • Step S102 When mobile node 20 detects the fact that it has moved from one network to another (Step S102; Yes), it is checked whether the packet received at the time of detection is one based on PMIPv6 or one based on MIPv6 (Step S104) .
  • Step S106 when it is determined that the received packet is one that is based on PMIPv6 (Step S106; Yes), it is checked whether updating should be done by registering a plurality of positional information (Step S108).
  • Step S108 if updating is performed by registering the plurality of positional information (Step S108; Yes), a flag that indicates that updating needs to be done by the plurality of registration is added (Step S110). Then, an attachment request to the PMIP network is transmitted to PMA 30 (Step S112).
  • Step S106 when it is determined that the packet detected at the time of detection of movement is one that is not based on PMIPv6 (Step S106; No), it is determined that the packet is one based on MIPv6. Further, if updating is performed by registering the plurality of positional information (Step S120; Yes), a flag that indicates that updating needs to be done by the plurality of registration is added (Step S122) . Then, a position registering request for the position in the foreign network is transmitted to HA 40 (Step S124).
  • Step S202 it is checked whether there has been reception of an attachment reply from the PMIP network or PMA 30(Step S202) or whether there has been reception of a reply based on MIPv6 from HA 30 (Step S204).
  • Step S202 when reception of an attachment reply has been received (Step S202; Yes/procedure (d) in FIG. 8 ) or when reception of a position registration reply has been received (Step S202; No->Step S204; Yes/procedure (g) in FIG. 8 ), it is checked whether the received attachment reply reception or position registration reply reception includes the flag so as to determine whether a plurality of positional information (addresses) are registered (Step S206). Here, if it has been determined that updating is performed by registering the plurality of positional information (addresses) thanks to inclusion of the flag (Step S206; Yes), positional information (address) is added to address management table 2062.
  • Step S206 if it has been determined that updating is not performed by registering the plurality of positional information (addresses) thanks to non-inclusion of the flag (Step S206; No), positional information (address) in address management table 2062 is updated and stored.
  • HA 40 receives a position registering request (Step S302).
  • the position registering request is demanded from PMA 30 (procedure (b) in FIG. 8 ) and in which it is demanded from mobile node 20 (procedure (f) in FIG. 8 ).
  • HA40 determines whether it is necessary to register a plurality of positional information that is demanded to be registered (Step S304). That is, it is determined whether there is the predetermined flag in the position registering request signal. If there is the flag, it is determined that the plurality of positional information should be registered, so that the position is additionally registered into positional information management table 4062 (Step S304; Yes ->Step S306). On the other hand, if there is no flag in the position registering request signal, the positional information stored in positional information management table 4062 is updated (Step S304; No->Step S308) .
  • HA40 When completing position registering, HA40 transmits a position registration reply (StepS310) .
  • the position registration reply is transmitted to PMA 30 (procedure (c) in FIG. 8 ) and mobile node 20 (procedure (g) in FIG. 8 ).
  • FIG. 12 is a diagram showing the scheme of a mobile communication system.
  • mobile node 20 includes a plurality of transceivers, one connecting to the PMIP network and the other to the foreign link.
  • the PMIP network is the home link for mobile node 20, and movement of mobile node 20 changing PMAs inside PMIP network is done based on PMIPv6.
  • the node is connected to the foreign network by the other transceiver, and movement of the node by changing ARs in the foreign network is done based on MIPv6 .
  • Position registering for simultaneous use to both is realized in the method described above.
  • FIG. 13 is a chart for illustrating the overall flow of the packet forwarding procedure.
  • FIG. 14 is a diagram schematically showing how packets are forwarded.
  • a forwarding route has been established between PMA 30 and HA 40.
  • This forwarding route is a forwarding path by way of the PMIP network.
  • Established further between HA 40 and mobile node 20 is a forwarding route by way of AR 10.
  • This forwarding route is a forwarding path by way of the foreign network .
  • HA 40 is the point of connection between the PMIP network and the foreign network, and is the only gateway router that announces the routing information on the home network prefix of the mobile node. Specifically, HA 40 announces the routing information to the foreign network so that any packet addressed to the home prefix of the mobile node can be delivered to itself, and any packet addressed from the communication terminal connected to the foreign network to the mobile node is delivered to HA 40.
  • HA 40 determines whether the packet is forwarded by way of the PMIP network or by way of the foreign network, and forwards the packet.
  • the packet is forwarded to PMA 30 (procedure (b) in FIG. 13 ).
  • the sender in the IP header of the forwarded packet is "HA 40" and the receiver is "PMA 30" ( FIG. 14(b) ).
  • the packet data shown in FIG. 14(a) is stored as the payload.
  • PMA 30 transmits the packet received from HA 40 to the receiver or mobile node 20 (procedure (c) in FIG. 13 ).
  • PMA 30 forwards the packet data received from mobile node 20 to HA 40 (procedure (e) in FIG. 13 ).
  • the sender in the IP header of the forwarded packet is "PMA 30" and the receiver is "HA 40" ( FIG. 14(d) ).
  • the packet data shown in FIG. 14(c) is stored as the payload.
  • HA 40 transmits the received packet to communication terminal 50 (procedure (f) in FIG. 13 ).
  • HA 40 determines whether the packet is delivered by way of the PMIP network or by way of the foreign network, and forwards the packet.
  • the packet is transmitted to mobile node 20 by way of AR 10 (procedure (h) in FIG. 13 ) .
  • AR 10 procedure (h) in FIG. 13 )
  • the sender in the IP header of the transmitted packet is "HA 40" and the receiver is "mobile node 20".
  • a care-of address (CoA) is set for mobile node 20.
  • the packet is transmitted to HA 40 first by way of AR 10 (procedure (i) in FIG. 13 ).
  • the sender in the IP header of the transmitted packet is "mobile node 20" and the receiver is "communication terminal 50" ( FIG. 15(c) ), but when it is sent to HA 40, the original IP packet is stored as the payload. That is, the packet is transmitted by setting the care-of address (CoA) of "mobile node 20" as the sender and HA 40 as the receiver.
  • HA 40 transmits the received packet to communication terminal 50 (procedure (j) in FIG. 13 ).
  • FIG. 16 is a chart for illustrating the process when a packet in mobile node 20 is transmitted.
  • packet transmitter 212 creates a transmission packet (Step S402).
  • processor 200 checks the positional information stored in address management table 2062 (Step S404). In this case, when a plurality of positional information have been registered in address management table 2062 (Step S406; Yes), one transmission route is selected based on the positional information among them (Step S408).
  • a transmission route is determined from the selected transmission route or one transmission route defined as the positional information (Step S406; No) (Step S410).
  • Step S410 if transmission is carried out based on MIPv6 (Step S412; Yes), the packet is subjected to an MIPv6 process and then transmitted (Step S414).
  • a method of determining it using the routing protocol based on prefixes can be considered as an example.
  • FIG. 17 is a chart for illustrating the process when a packet is forwarded in HA 40.
  • the packet is received by PMIP network transceiver 402 or foreign network transceiver 404 of HA 40 (Step S502) .
  • processor 400 determines whether the receiver of the received packet is addressed to a mobile node that the HA 40 manages (Step S504).
  • Step S504 If the packet is addressed to a mobile node that the HA 40 manages (Step S504; Yes), it checks the position of mobile node 20 (Step S506). At this point, if a plurality of positional information on mobile node 20 have been registered in positional information management table 4062 (Step S508; Yes), the forwarding route is selected based on one of the positional information (Step S510). Then, the HA determines a forwarding route (Step S512) based on the selected forwarding route or the one forwarding route defined as the positional information (Step S508; No) so as to forward the packet (Step S514).
  • a method for determining a transmission route at Step S410 a method of determining it using the routing protocol in the network can be considered as an example.
  • mobile node 20 includes a plurality of transceivers so that it is possible to connect to the PMIP network as the home link through one transceiver and connect to a foreign network through the other transceiver at the same time.
  • HA 40 manages PMA 30 as its positional information on the PMIP network, and at the same time, manages its care-of address on the foreign network as the foreign network positional information.
  • Application of the present invention enables construction of a large-scale PMIP network operated by a carrier or the like as its home link while permitting mobile node 20 to connect the carrier network and a WLAN as a hot spot or the like at the same time. Further, the mobile node can perform communications using a single IP address in both networks. As a result, it is possible for the carrier, for example to achieve control such that an application that the carrier wants to be communicated through its own PMIP network is communicated by way of the PMIP network while an application that is regarded to be able to achieve a higher throughput if it is distributed through access networks such as WLAN etc. , is entrusted to communication by way of a foreign network.
  • communicationbetween mobile node 1 and mobile node 2 connected to the PMIP network can be performed within the PMIP network using the transmission route between the HA and PMA 1 and the transmission route between the HA and PMA 2 while communication between a communication terminal and mobile node 1 connected to the foreign network can be realized through the foreign network using the transmission route designated by the care-of address which is used by the HA and mobile node 1 to connect to the foreign network.
  • This enables an application such as voice communication between the subscribers of the carrier that operates the PMIP network to be executed by performing communication through the PMIP network, and a case when mobile node 1 acquires contents from WEB servers connected to the foreign network by FTP or HTTP access, to be achieved by performing communication by way of a foreign network.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Telephonic Communication Services (AREA)
  • Telephone Function (AREA)

Claims (12)

  1. Kommunikationssteuerungsverfahren, das von einem Mobilkommunikations-Endgerät (20) durchgeführt wird, wobei das Mobilkommunikations-Endgerät (20) eine Vielzahl von Transceivern (202, 204) aufweist, die einen ersten Transceiver (202) und einen zweiten Transceiver (204) enthält, wobei das Mobilkommunikations-Endgerät (20) über die Transceiver (202, 204) mit einem Mobilkommunikations-System verbunden ist, wobei das Kommunikationssteuerungsverfahren aufweist:
    ein Starten, durch den ersten Transceiver (202), einer Prozedur zur Einrichtung einer ersten Kommunikationsstrecke, wobei die Prozedur zur Einrichtung einer ersten Kommunikationsstrecke aufweist:
    ein Verbinden des Mobilkommunikations-Endgeräts (20) mit einem Home-Link mittels Einrichtung einer ersten Kommunikationsstrecke über eine Mobil-Agent-Vorrichtung (30), die eine Datenweiterleitung in einem Netzwerk, das eine netzwerkbasierte mobile Verwaltung ausführt, durchführt, wobei die Prozedur zur Einrichtung einer ersten Kommunikationsstrecke ferner umfasst, dass eine Positionsverwaltungseinrichtung (40) eine Adresse der Mobil-Agent-Vorrichtung (30) als erste Identifikation registriert, wobei
    die erste Identifikation ein erstes Datenübertragungs-Ziel angibt, zu dem die Positionsverwaltungseinrichtung (40) an eine erste IP-Adresse adressierte Daten überträgt, und
    die erste IP-Adresse für Kommunikationen durch das Mobilkommunikations-Endgerät (20) verwendet wird;
    ein Starten, durch den zweiten Transceiver (204), einer Prozedur zur Einrichtung einer zweiten Kommunikationsstrecke, wobei
    der zweite Transceiver (204) eine Steuerungsinformation zur Positionsverwaltungseinrichtung (40) überträgt, die eine Einrichtung einer zweiten Kommunikationsstrecke anfordert und eine Adresse, die von dem Mobilkommunikations-Endgerät (20) in einem fremden Netzwerk erlangt wird, das eine Host-basierte mobile Verwaltung durchführt, als zweite Identifikation enthält, und wobei die Prozedur zur Einrichtung einer zweiten Kommunikationsstrecke ferner eine Registrierung bei der Positionsverwaltungseinrichtung (40) der zweiten Identifikation ohne Entfernen der Registrierung der ersten Identifikation aufweist;
    die zweite Identifikation ein zweites Datenübertragungs-Ziel angibt, zu dem die Positionsverwaltungseinrichtung (40) an die erste IP-Adresse adressierte Daten überträgt;
    ein Einrichten der zweiten Kommunikationsstrecke mit der Positionsverwaltungseinrichtung (40) über einen fremden Link im fremden Netzwerk basierend auf der Prozedur zur Einrichtung einer zweiten Kommunikationsstrecke; wobei
    die erste Kommunikationsstrecke und die zweite Kommunikationsstrecke, die beide für die Kommunikationen unter Verwendung der ersten IP-Adresse verwendet werden, gleichzeitig aufrechterhalten werden; und
    die Kommunikationen über entweder die erste Kommunikationsstrecke oder die zweite Kommunikationsstrecke oder beide durchgeführt werden, und wobei
    alle Daten für die Kommunikationen zu einem beliebigen einzelnen Zeitpunkt über eine ausgewählte Kommunikationsstrecke weitergeleitet werden.
  2. Kommunikationssteuerungsverfahren nach Anspruch 1, wobei die erste Identifikation eine IP-Adresse der Mobil-Agent-Vorrichtung (30) ist, die als Zugangs-Gateway im Netzwerk fungiert.
  3. Kommunikationssteuerungsverfahren nach Anspruch 1, wobei für jedes Kommunikationspaket der Kommunikationen eine Streckenauswahl aus entweder der ersten Kommunikationsstrecke oder der zweiten Kommunikationsstrecke durchgeführt wird.
  4. Kommunikationssteuerungsverfahren, das von einer Positionsverwaltungseinrichtung (40) durchgeführt wird, wobei das Kommunikationssteuerungsverfahren aufweist:
    basierend auf einer Prozedur zur Einrichtung einer ersten Kommunikationsstrecke, die durch ein Mobilkommunikations-Endgerät (20) initiiert wird, ein Registrieren einer Adresse einer Mobil-Agent-Vorrichtung (30), die eine Datenweiterleitung in einem Netzwerk, das eine netzwerkbasierte mobile Verwaltung ausführt, durchführt, als eine erste Identifikation, wobei
    die erste Identifikation ein erstes Datenübertragungs-Ziel angibt, zu dem die Positionsverwaltungseinrichtung (40) an eine erste IP-Adresse adressierte Daten überträgt, und
    die erste IP-Adresse für Kommunikationen durch das Mobilkommunikations-Endgerät (20) verwendet wird;
    ein Verbinden des Mobilkommunikations-Endgeräts (20) mit einem Home-Link durch Einrichten einer ersten Kommunikationsstrecke über die Mobil-Agent-Vorrichtung (30), die eine Datenweiterleitung in dem Netzwerk, das eine netzwerkbasierte mobile Verwaltung ausführt, durchführt, in der Prozedur zur Einrichtung einer ersten Kommunikationsstrecke;
    für eine Prozedur zur Einrichtung einer zweiten Kommunikationsstrecke, die durch das Mobilkommunikations-Endgerät (20) initiiert wird, ein Registrieren einer Adresse, die im fremden Netzwerk durch das Mobilkommunikations-Endgerät (20) erlangt wird, als eine zweite Identifikation ohne Entfernen der Registrierung der ersten Identifikation, wobei die zweite Identifikation ein zweites Datenübertragungs-Ziel angibt, zu dem die Positionsverwaltungseinrichtung (40) an die erste IP-Adresse adressierte Daten überträgt;
    ein Einrichten einer zweiten Kommunikationsstrecke mit dem Mobilkommunikations-Endgerät (20) über das fremde Netzwerk basierend auf der Prozedur zur Einrichtung einer zweiten Kommunikationsstrecke; wobei
    Registrierungen für die erste Kommunikationsstrecke und die zweite Kommunikationsstrecke, die beide für die Kommunikationen unter Verwendung der ersten IP-Adresse verwendet werden, gleichzeitig aufrechterhalten werden; und
    die Kommunikationen über entweder die erste Kommunikationsstrecke oder die zweite Kommunikationsstrecke oder beide durchgeführt werden, wobei
    alle Daten für die Kommunikationen zu einem beliebigen einzelnen Zeitpunkt über eine ausgewählte Kommunikationsstrecke weitergeleitet werden.
  5. Kommunikationssteuerungsverfahren nach Anspruch 4, wobei die erste Identifikation eine IP-Adresse der Mobil-Agent-Vorrichtung (30) ist, die als Zugangs-Gateway im Netzwerk fungiert.
  6. Kommunikationssteuerungsverfahren nach Anspruch 4, wobei für jedes Kommunikationspaket der Kommunikationen eine Streckenauswahl aus entweder der ersten Kommunikationsstrecke oder der zweiten Kommunikationsstrecke durchgeführt wird.
  7. Mobilkommunikations-Endgerät (20), aufweisend:
    eine Vielzahl von Transceivern (202, 204), die einen ersten Transceiver (202) und einen zweiten Transceiver (204) enthält, wobei
    das Mobilkommunikations-Endgerät (20) über die Transceiver (202, 204) mit dem Mobilkommunikations-System verbunden ist,
    der erste Transceiver (202) dafür konfiguriert ist, eine Prozedur zur Einrichtung einer ersten Kommunikationsstrecke zu starten; und
    das Mobilkommunikations-Endgerät (20) für die Prozedur zur Einrichtung einer ersten Kommunikationsstrecke dafür konfiguriert ist:
    das Mobilkommunikations-Endgerät (20) mit einem Home-Link mittels Einrichtung einer ersten Kommunikationsstrecke über eine Mobil-Agent-Vorrichtung (30) zu verbinden, die eine Datenweiterleitung in einem Netzwerk, das eine netzwerkbasierte mobile Verwaltung ausführt, durchführt, wobei die Prozedur zur Einrichtung einer ersten Kommunikationsstrecke ferner umfasst, dass eine Positionsverwaltungseinrichtung (40) eine Adresse der Mobil-Agent-Vorrichtung (30) als erste Identifikation registriert, wobei
    die erste Identifikation ein erstes Datenübertragungs-Ziel angibt, zu dem die Positionsverwaltungseinrichtung (40) an eine erste IP-Adresse adressierte Daten überträgt, und
    die erste IP-Adresse für Kommunikationen durch das Mobilkommunikations-Endgerät (20) verwendet wird;
    der zweite Transceiver (204) dafür konfiguriert ist, für eine Prozedur zur Einrichtung einer zweiten Kommunikationsstrecke eine Steuerungsinformation zur Positionsverwaltungseinrichtung (40) zu übertragen, die eine Einrichtung einer zweiten Kommunikationsstrecke anfordert und eine Adresse, die von dem Mobilkommunikations-Endgerät (20) in einem fremden Netzwerk erlangt wird, das eine Host-basierte mobile Verwaltung ausführt, als zweite Identifikation enthält, und wobei die Prozedur zur Einrichtung einer zweiten Kommunikationsstrecke ferner eine Registrierung bei der Positionsverwaltungseinrichtung (40) der zweiten Identifikation ohne Entfernen der Registrierung der ersten Identifikation aufweist;
    die zweite Identifikation ein zweites Datenübertragungs-Ziel angibt, zu dem die Positionsverwaltungseinrichtung (40) an die erste IP-Adresse adressierte Daten überträgt;
    das Mobilkommunikations-Endgerät (20) dafür konfiguriert ist, die zweite Kommunikationsstrecke mit der Positionsverwaltungseinrichtung (40) über einen fremden Link im fremden Netzwerk basierend auf der Prozedur zur Einrichtung einer zweiten Kommunikationsstrecke einzurichten; wobei
    das Mobilkommunikations-Endgerät (20) dafür konfiguriert ist, die erste Kommunikationsstrecke und die zweite Kommunikationsstrecke, die beide für Kommunikationen unter Verwendung der ersten IP-Adresse verwendet werden, gleichzeitig aufrechtzuerhalten,
    das Mobilkommunikations-Endgerät (20) dafür konfiguriert ist, Kommunikationen über entweder die erste Kommunikationsstrecke oder die zweite Kommunikationsstrecke oder beide durchzuführen, wobei
    alle Daten für die Kommunikationen zu einem beliebigen einzelnen Zeitpunkt über eine ausgewählte Kommunikationsstrecke weitergeleitet werden.
  8. Mobilkommunikations-Endgerät (20) nach Anspruch 7, wobei die erste Identifikation eine IP-Adresse der Mobil-Agent-Vorrichtung (30) ist, die als Zugangs-Gateway im Netzwerk fungiert.
  9. Mobilkommunikations-Endgerät (20) nach Anspruch 7, wobei für jedes Kommunikationspaket der Kommunikationen eine Streckenauswahl aus entweder der ersten Kommunikationsstrecke oder der zweiten Kommunikationsstrecke durchgeführt wird.
  10. Positionsverwaltungseinrichtung (40), aufweisend:
    einen ersten Transceiver (402), der dafür konfiguriert ist, mit einem Netzwerk, das eine netzwerkbasierte mobile Verwaltung ausführt, zu verbinden;
    einen zweiten Transceiver (404), der dafür konfiguriert ist, mit einem fremden Netzwerk, das eine Host-basierte mobile Verwaltung ausführt, zu verbinden, und
    einen Speicher (406), wobei
    für eine Prozedur zur Einrichtung einer ersten Kommunikationsstrecke, die durch ein Mobilkommunikations-Endgerät (20) initiiert wird, die Positionsverwaltungseinrichtung (40) dafür konfiguriert ist, eine Adresse einer Mobil-Agent-Vorrichtung, die eine Datenweiterleitung in dem eine netzwerkbasierte mobile Verwaltung ausführenden Netzwerk durchführt, als eine erste Identifikation in den Speicher zu registrieren, wobei
    die erste Identifikation ein erstes Datenübertragungs-Ziel angibt, zu dem die Positionsverwaltungseinrichtung (40) an eine erste IP-Adresse adressierte Daten überträgt, und wobei
    die erste IP-Adresse für Kommunikationen durch das Mobilkommunikations-Endgerät (20) verwendet wird;
    die Positionsverwaltungseinrichtung (40) dafür konfiguriert ist, das Mobilkommunikations-Endgerät (20) mit einem Home-Link durch Einrichten einer ersten Kommunikationsstrecke über die Mobil-Agent-Vorrichtung (30) in dem Netzwerk, das eine netzwerkbasierte mobile Verwaltung ausführt, in der Prozedur zur Einrichtung einer ersten Kommunikationsstrecke zu verbinden;
    für eine Prozedur zur Einrichtung einer zweiten Kommunikationsstrecke, die durch das Mobilkommunikations-Endgerät (20) initiiert wird, die Positionsverwaltungseinrichtung (40) dafür konfiguriert ist, eine Adresse, die durch das Mobilkommunikations-Endgerät (20) im fremden Netzwerk erlangt wird, als eine zweite Identifikation in den Speicher ohne Entfernen der Registrierung der ersten Identifikation aus dem Speicher zu registrieren, wobei
    die zweite Identifikation ein zweites Datenübertragungs-Ziel angibt, zu dem die Positionsverwaltungseinrichtung (40) an die erste IP-Adresse adressierte Daten überträgt;
    die Positionsverwaltungseinrichtung (40) dafür konfiguriert ist, eine zweite Kommunikationsstrecke mit dem Mobilkommunikations-Endgerät (20) über das fremde Netzwerk basierend auf der Prozedur zur Einrichtung einer zweiten Kommunikationsstrecke einzurichten; wobei
    die Positionsverwaltungseinrichtung (40) dafür konfiguriert ist, Registrierungen für die erste Kommunikationsstrecke und die zweite Kommunikationsstrecke, die beide für Kommunikationen unter Verwendung der ersten IP-Adresse verwendet werden, gleichzeitig aufrechtzuerhalten,
    die Positionsverwaltungseinrichtung (40) dafür konfiguriert ist, Kommunikationen über entweder die erste Kommunikationsstrecke oder die zweite Kommunikationsstrecke oder beide durchzuführen, wobei
    alle Daten für die Kommunikationen zu einem beliebigen einzelnen Zeitpunkt über eine ausgewählte Kommunikationsstrecke weitergeleitet werden.
  11. Positionsverwaltungseinrichtung (40) nach Anspruch 10, wobei die erste Identifikation eine IP-Adresse der Mobil-Agent-Vorrichtung (30) ist, die als Zugangs-Gateway im Netzwerk fungiert.
  12. Positionsverwaltungseinrichtung (40) nach Anspruch 10, wobei für jedes Kommunikationspaket der Kommunikationen eine Streckenauswahl aus entweder der ersten Kommunikationsstrecke oder der zweiten Kommunikationsstrecke durchgeführt wird.
EP08738692.6A 2007-03-23 2008-03-21 Mobiles kommunikationsendgerät und positionsverwaltungsvorrichtung Active EP2129059B1 (de)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2007077908 2007-03-23
PCT/JP2008/055269 WO2008123138A1 (ja) 2007-03-23 2008-03-21 通信システム、移動通信端末及び位置管理装置

Publications (3)

Publication Number Publication Date
EP2129059A1 EP2129059A1 (de) 2009-12-02
EP2129059A4 EP2129059A4 (de) 2014-10-15
EP2129059B1 true EP2129059B1 (de) 2020-05-20

Family

ID=39830635

Family Applications (1)

Application Number Title Priority Date Filing Date
EP08738692.6A Active EP2129059B1 (de) 2007-03-23 2008-03-21 Mobiles kommunikationsendgerät und positionsverwaltungsvorrichtung

Country Status (6)

Country Link
US (6) US9113435B2 (de)
EP (1) EP2129059B1 (de)
JP (4) JP5122557B2 (de)
KR (4) KR101031979B1 (de)
CN (3) CN107182104B (de)
WO (1) WO2008123138A1 (de)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110191494A1 (en) * 2008-05-27 2011-08-04 Turanyi Zoltan Richard System and method for backwards compatible multi-access with proxy mobile internet protocol
JP5155899B2 (ja) * 2009-02-03 2013-03-06 Ｋｄｄｉ株式会社 モバイルｉｐネットワークにおける非ｉｐネットワークを介した経路制御方法及びシステム
CN102025608B (zh) * 2009-09-17 2013-03-20 中兴通讯股份有限公司 通信方法、通信过程中的数据报文转发方法及通信节点
JP5621622B2 (ja) * 2011-01-26 2014-11-12 日本電気株式会社 通信システム、通信端末、ゲートウェイ、通信方法及びプログラム
US8824395B2 (en) * 2011-10-25 2014-09-02 Verizon Patent And Licensing Inc. Dynamic selection of host-based or network-based mobility protocol
US9611126B2 (en) 2013-08-12 2017-04-04 Abb Schweiz Ag Method and system for automatically landing containers on a landing target using a container crane
US9640005B2 (en) 2014-02-11 2017-05-02 Gentex Corporation Systems and methods for adding a trainable transceiver to a vehicle
US9652907B2 (en) 2014-05-08 2017-05-16 Gentex Corporation Fixed location based trainable transceiver for the control of remote devices systems and methods
WO2016004119A1 (en) * 2014-06-30 2016-01-07 Interdigital Patent Holdings, Inc. Network-based flow mobility for multi connectivity devices
CN111034255B (zh) * 2019-09-24 2024-01-12 北京小米移动软件有限公司 资源处理方法、装置及计算机存储介质

Family Cites Families (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5898839A (en) * 1997-03-17 1999-04-27 Geonet Limited, L.P. System using signaling channel to transmit internet connection request to internet service provider server for initiating and internet session
BR9914646A (pt) * 1998-10-20 2001-10-16 Ajay Deo Método e aparelho para o fornecimento de serviços de processamento de chamadas em tempo real dentro de uma rede inteligente
JP4345565B2 (ja) * 2003-05-13 2009-10-14 パナソニック株式会社 移動ルータ、位置管理サーバ、移動ネットワーク管理システム、及び移動ネットワーク管理方法
CN1762132A (zh) * 2003-05-13 2006-04-19 松下电器产业株式会社 移动路由器、位置管理服务器、移动网络管理系统以及移动网络管理方法
JP4466296B2 (ja) * 2003-10-17 2010-05-26 パナソニック株式会社 ハンドオーバ方法および移動通信システム
CA2541572C (en) * 2003-10-22 2013-04-02 Leica Geosystems Ag Method and apparatus for managing information exchanges between apparatus on a worksite
US7609687B2 (en) * 2003-12-15 2009-10-27 Panasonic Corporation Home agent apparatus, mobile router communication system, and communication method
US7088608B2 (en) 2003-12-16 2006-08-08 Freescale Semiconductor, Inc. Reducing power consumption during MRAM writes using multiple current levels
JP4176655B2 (ja) * 2004-02-24 2008-11-05 株式会社エヌ・ティ・ティ・ドコモ アドレス動的割当てシステム、中継装置、及び、アドレス動的割当方法
CN1926817B (zh) 2004-03-09 2011-07-06 艾利森电话股份有限公司 通过非许可无线电接入网络的分组无线电传输
JP4703238B2 (ja) * 2004-12-15 2011-06-15 パナソニック株式会社 無線網制御装置、無線ｌａｎ中継装置、無線通信システム及び無線通信システムの通信方法
CN100421509C (zh) * 2005-02-01 2008-09-24 华为技术有限公司 移动网络中均衡家乡代理负载的实现方法
WO2006106712A1 (ja) * 2005-03-31 2006-10-12 Matsushita Electric Industrial Co., Ltd. 通信制御方法及び通信ノード並びにモバイルノード
JP4644033B2 (ja) * 2005-05-16 2011-03-02 株式会社エヌ・ティ・ティ・ドコモ アクセスルータ装置、モビリティ制御システム、モビリティ制御方法
EP1764970A1 (de) * 2005-09-19 2007-03-21 Matsushita Electric Industrial Co., Ltd. Mobile Mehrfachschnittstellen Knoten mit gleichzeitiger Heim und Fremdnetzwerksverbindung
CN100341296C (zh) * 2005-11-21 2007-10-03 西安交通大学 一种用于MIPv6实验的移动节点切换控制方法
JP4592611B2 (ja) 2006-02-03 2010-12-01 富士通株式会社 パケット通信システム
US8073956B2 (en) * 2006-11-07 2011-12-06 Microsoft Corporation Multimedia communications using preferred devices
JPWO2008126357A1 (ja) 2007-03-16 2010-07-22 パナソニック株式会社 移動端末及び通信管理装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LARSSON H LEVKOWETZ H MAHKONEN T KAUPPINEN ERICSSON C: "A Filter Rule Mechanism for Multi-access Mobile IPv6; draft-larsson-monami6-filter-rules-02.txt", A FILTER RULE MECHANISM FOR MULTI-ACCESS MOBILE IPV6; DRAFT-LARSSON-MONAMI6-FILTER-RULES-02.TXT, INTERNET ENGINEERING TASK FORCE, IETF; STANDARDWORKINGDRAFT, INTERNET SOCIETY (ISOC) 4, RUE DES FALAISES CH- 1205 GENEVA, SWITZERLAND, no. 2, 5 March 2007 (2007-03-05), XP015050112 *

Also Published As

Publication number Publication date
US20200359352A1 (en) 2020-11-12
KR101065958B1 (ko) 2011-09-19
KR101126471B1 (ko) 2012-03-29
CN103179546B (zh) 2017-09-29
EP2129059A1 (de) 2009-12-02
US20150327211A1 (en) 2015-11-12
KR20100095471A (ko) 2010-08-30
JP5079866B2 (ja) 2012-11-21
JP2011103670A (ja) 2011-05-26
EP2129059A4 (de) 2014-10-15
US10728874B2 (en) 2020-07-28
JP5209020B2 (ja) 2013-06-12
JP5122557B2 (ja) 2013-01-16
KR101031979B1 (ko) 2011-04-29
KR101065920B1 (ko) 2011-09-19
US20100061304A1 (en) 2010-03-11
KR20090125830A (ko) 2009-12-07
US20180338296A1 (en) 2018-11-22
US10064157B2 (en) 2018-08-28
JP5059181B2 (ja) 2012-10-24
JP2011050108A (ja) 2011-03-10
KR20110060974A (ko) 2011-06-08
JPWO2008123138A1 (ja) 2010-07-15
US9820257B2 (en) 2017-11-14
WO2008123138A1 (ja) 2008-10-16
CN101641974B (zh) 2013-02-13
KR20110063594A (ko) 2011-06-10
US11356973B2 (en) 2022-06-07
JP2011050086A (ja) 2011-03-10
US9113435B2 (en) 2015-08-18
US20170070972A1 (en) 2017-03-09
CN103179546A (zh) 2013-06-26
US20180041986A1 (en) 2018-02-08
CN101641974A (zh) 2010-02-03
CN107182104A (zh) 2017-09-19
CN107182104B (zh) 2021-03-12

Similar Documents

Publication Publication Date Title
US11356973B2 (en) Communication system, mobile communication terminal and position managing apparatus
JP4794520B2 (ja) ネットワーク主導型移動管理プロトコルにおける通信経路を最適化するシステム、アクセスゲートウェイ、ホームエージェント、およびプログラム
JP5072864B2 (ja) 通信システム及びドメイン管理装置
JP4971468B2 (ja) 移動体ネットワークにおけるインタフェース選択
US20060140177A1 (en) Method and device for setting a route for communication connection
JP2003526297A (ja) 無線ネットワークのための階層移動性管理
US8320332B2 (en) IP handoff process method and system for connection of internet protocols between mobile agents in heterogeneous network
US20100208663A1 (en) Communication system, mobile terminal, and network node
Hsu et al. Design and implementation of two-tier MANETs with seamless roaming and load-balancing routing capability

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20090922

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MT NL NO PL PT RO SE SI SK TR

DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20140911

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 40/20 20090101AFI20140908BHEP

17Q First examination report despatched

Effective date: 20160908

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 80/04 20090101ALN20190213BHEP

Ipc: H04W 60/00 20090101AFI20190213BHEP

INTG Intention to grant announced

Effective date: 20190301

GRAJ Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20190719

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 60/00 20090101AFI20190709BHEP

Ipc: H04W 80/04 20090101ALN20190709BHEP

GRAJ Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602008062740

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0012560000

Ipc: H04W0060000000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTC Intention to grant announced (deleted)
INTG Intention to grant announced

Effective date: 20191211

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 60/00 20090101AFI20191129BHEP

Ipc: H04W 80/04 20090101ALN20191129BHEP

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MT NL NO PL PT RO SE SI SK TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602008062740

Country of ref document: DE

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1273491

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200615

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20200520

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200920

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200921

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200520

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200821

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200820

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200520

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200520

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200820

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200520

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200520

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1273491

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200520

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200520

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200520

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200520

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200520

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200520

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200520

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200520

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200520

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602008062740

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200520

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200520

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20210223

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200520

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200520

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20210331

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210321

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210321

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210331

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210331

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210331

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20080321

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200520

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20240320

Year of fee payment: 17

Ref country code: GB

Payment date: 20240320

Year of fee payment: 17

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20240322

Year of fee payment: 17

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200520

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200520