WO2005076548A1 - 通信ハンドオーバ方法及び通信メッセージ処理方法並びにこれらの方法をコンピュータにより実行するためのプログラム - Google Patents
通信ハンドオーバ方法及び通信メッセージ処理方法並びにこれらの方法をコンピュータにより実行するためのプログラム Download PDFInfo
- Publication number
- WO2005076548A1 WO2005076548A1 PCT/JP2005/001691 JP2005001691W WO2005076548A1 WO 2005076548 A1 WO2005076548 A1 WO 2005076548A1 JP 2005001691 W JP2005001691 W JP 2005001691W WO 2005076548 A1 WO2005076548 A1 WO 2005076548A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- message
- communication
- information
- access point
- route
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 92
- 230000006854 communication Effects 0.000 title claims description 292
- 238000004891 communication Methods 0.000 title claims description 292
- 238000003672 processing method Methods 0.000 title claims description 55
- 230000004044 response Effects 0.000 claims abstract description 26
- 238000002360 preparation method Methods 0.000 claims description 27
- 230000005540 biological transmission Effects 0.000 claims description 15
- 238000012546 transfer Methods 0.000 claims description 4
- 238000012545 processing Methods 0.000 description 56
- 238000011144 upstream manufacturing Methods 0.000 description 56
- 238000010586 diagram Methods 0.000 description 24
- 230000008859 change Effects 0.000 description 13
- 238000005516 engineering process Methods 0.000 description 10
- 230000011664 signaling Effects 0.000 description 9
- 230000002457 bidirectional effect Effects 0.000 description 8
- 230000008569 process Effects 0.000 description 8
- 230000007175 bidirectional communication Effects 0.000 description 6
- 238000004590 computer program Methods 0.000 description 4
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 101100454361 Arabidopsis thaliana LCB1 gene Proteins 0.000 description 1
- 101000852224 Mus musculus THO complex subunit 5 homolog Proteins 0.000 description 1
- 101100171146 Oryza sativa subsp. japonica DREB2C gene Proteins 0.000 description 1
- 102100036436 THO complex subunit 5 homolog Human genes 0.000 description 1
- 240000004543 Vicia ervilia Species 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 238000007796 conventional method Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000000449 premovement Effects 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
- 235000002020 sage Nutrition 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
- H04W40/34—Modification of an existing route
- H04W40/36—Modification of an existing route due to handover
-
- 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]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
- H04W28/26—Resource reservation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/08—Reselecting an access point
Definitions
- the present invention relates to a communication handover method and a communication message processing method relating to a handover of a mobile terminal (mobile node) performing wireless communication, and a program for executing these methods by a computer.
- the present invention relates to a communication handover method and a communication message processing method relating to a handover in a mopile node performing wireless communication using a mobile Internet Protocol version 6 (IPv6) protocol, and a program for executing these methods by a computer.
- IPv6 mobile Internet Protocol version 6
- Mobile terminal power MoPILE IPv6 a next-generation Internet protocol, is a technology that can provide users accessing a communication network such as the Internet via a wireless network seamlessly while moving. Those that have been used are becoming popular. This wireless communication system using Mopile IPv6 will be described with reference to FIG. The technology of Mopile IPv6 described below is disclosed, for example, in Non-Patent Document 1 below.
- the wireless communication system shown in FIG. 9 includes an IP network (communication network) 15 such as the Internet, a plurality of subnets (also called sub-networks) 20 and 30 connected to the IP network 15, and a plurality of these networks. It includes a mobile terminal (MN: Mobile Node) 10 that can be connected to one of the subnets 20 and 30. In FIG. 9, two subnets 20 and 30 are illustrated as the plurality of subnets 20 and 30.
- IP network communication network
- MN Mobile Node
- the subnet 20 includes a plurality of access routers (AR: Access Router) 21 for routing IP packets (packet data) and a plurality of wireless communication areas (communicable areas) 28 and 29, respectively.
- Access Point (AP) 22 and 23 are connected to AR21, and AR21 is connected to IP network. Connected to work 15.
- two APs 22 and 23 are illustrated as the plurality of APs 22 and 23.
- the subnet 30 is also configured by the AR 31 and the plurality of APs 32 and 33 in the same connection manner as the subnet 20 described above.
- AR21 which is a component of the subnet 20 and AR31 which is a component of the subnet 30 can communicate via the IP network 15, that is, the subnet 20 and the subnet 30 It is connected through an IP network 15.
- the MN 10 obtains a CoA by a method of stateful allocation from a DHCP server by a method such as DHCPv6, or by obtaining a network prefix status and a prefix length of the subnet 20 from the AR 21,
- a method that automatically generates a stateless CoA by combining the network prefix and prefix length obtained from AR21 with the link layer address of MN10, etc.
- MN 10 registers the acquired CoA with a router (home agent) on its own home network or a specific communication partner (Correspondent Node: CN) (Binding Update: BU), thereby obtaining subnet 20 Within the network, transmission or reception of packet data can be performed.
- a router home agent
- CN Correspondent Node
- the packet data transmitted to the MN 10 with a predetermined communication partner power is transmitted to the MN 10 via the AR 21 and the AP 23 based on the CoA of the MN 10, while the MN 10 Is transmitted to the desired communication partner via the AP23 and the AR21.
- the packet data sent to the home network to MN10 is also sent to AR21 on subnet 20 based on the CoA of MN10 registered in the home agent, and transmitted to MN10 via AP23.
- the wireless communication system using Mopile IPv6 shown in FIG. Even when a handover is performed from one subnet to another subnet, the MN 10 is configured to continue wireless communication using the CoA.
- a fast handover technique disclosed in Non-Patent Document 2 below is known.
- the MN 10 obtains a new (New) CoA (hereinafter, referred to as NCoA) used in the subnet 30 in advance, and transmits the NCoA to the AR 21.
- NCoA new CoA
- the MN 10 obtains a new (New) CoA (hereinafter, referred to as NCoA) used in the subnet 30 in advance, and transmits the NCoA to the AR 21.
- NCoA new CoA
- a protocol for guaranteeing QoS includes, for example, RSVP (Resource Reservation Protocol) (for example, see Non-Patent Document 3 below).
- RSVP Resource Reservation Protocol
- RSVP establishes a bandwidth reservation on a path (flow) from a transmitting communication terminal that transmits data to a receiving communication terminal that receives data, thereby allowing the transmitting communication terminal to transmit to the receiving communication terminal. The data is to be transmitted smoothly.
- a QoS route is set in an end-to-end path to a communication partner terminal (CN: Correspondent Node) 60 of the MN10 to the MN10, and based on the addresses of the MN10 and the CN60.
- CN Correspondent Node
- data transfer is performed by a plurality of relay nodes 61 connecting between the two-point routes. Therefore, for example, when the MN 10 performs a handover between the subnets 20 and 30 and the CoA of the MN 10 is changed, the power required to perform the process related to the address change in addition to the flow change in the QoS route RSVP Cannot respond to such a change, resulting in a failure of QoS guarantee (first problem: it is difficult to change the QoS route).
- NSIS Next Step in Signaling
- FIG. 11 illustrates NSIS and a protocol stack of a lower layer thereof in order to explain a protocol configuration of NSIS in the related art.
- the NSIS protocol layer sits just above the IP and lower layers.
- the NSIS protocol layer generates NSLP (NSIS Signaling Layer Protocol), which is a protocol for generating and processing signaling messages for providing each additional service, and NTLP (NTLP, which routes NSLP signaling messages).
- NSLP ⁇ is NSLP for QoS (QoS NSLP) and other adjunct services (Service A
- QoS NSLP QoS
- Service A There are various NSLPs, including NSLP for service B) (NSLP for service A, NSLP for service B).
- FIG. 12 is a schematic diagram for explaining the concept that NEs and QNEs which are NSIS nodes in the conventional technology are “adjacent”. As shown in Fig. 12, all nodes (NE: NSIS Entity) having the NSIS function have at least NTLP implemented. The NSLP does not necessarily need to exist on the NTLP, and one or more NSLPs may exist. Here, in particular, an NE having an NSLP for QoS will be referred to as a QNE (QoS NSIS Entity). Note that terminals and routers can be NEs. In addition, there may be multiple non-NE routers between adjacent NEs, and multiple non-NE routers and NEs without QoS NSLP may exist between adjacent QNEs. Can be.
- the MN10 connected to the AR21 on the subnet 20 is planning to receive or is receiving (receiving) data from the CN60 for a certain purpose (session).
- the MN 10 transmits a RESERVE message for establishing the QoS route to the CN 60.
- the RESERVE message contains information (Qspec) of the QoS desired for receiving data from CN60.
- the transmitted RESERVE message arrives at QNE63 via AR21, NE62 and other routers without NSIS function.
- the QNE63 NSLP reserves the QoS resources described in the Qspec included in the RESERVE message for this session.
- the RESERVE message passing through QNE 63 reaches QNE65 via NE64 and other routers without NSIS functions.
- QNE65 the same processing as in QNE63 is performed, and QoS resources are reserved. This operation is repeated, and finally a RESERVE message is delivered to CN60, so that a QoS path is established between MN10 and CN60.
- a flow identifier and a session identifier are used.
- the flow identifier depends on the CoA of MN10 and the IP address of CN60. By confirming the IP address of this data packet, it is possible to know whether there is a resource reservation for this data packet.
- the flow identifier also changes according to the change in the CoA of the MN 10.
- the session identifier is for identifying a series of data transmission for the session, and does not change with movement of the terminal like the flow identifier.
- Q UERY there is a method called Q UERY as a method of checking availability of QoS resources for an arbitrary route.
- This method is, for example, a method for checking in advance whether a desired Qspec can be reserved in each QNE when a QoS path is established from the MN 10 to the CN 60, and the desired Qspec is A QUERY message is sent to check whether the reservation is available at QNE, and the result can be received by the RES PONSE message that is a response to this QUREY message.
- This QUERY and RESPONSE message does not change the current resource reservation status.
- a NOTIFY message can be used by a QNE to send some notification to other QNEs. This NOTIFY message is used, for example, for error notification.
- RESERVE, QUERY, RESPONSE, and NOTIFY messages are all NSLP messages for guaranteeing QoS, and are described in Non-Patent Document 6.
- the MN 10 is receiving data from the CN 60 and the QoS route (route 24) is established, the QoS resources desired by the MN 10 are reserved in the QNE 63, QNE 65, and QNE 66, respectively.
- the flow identifier and session identifier at this time are X and Y, respectively. In fact, the flow identifier
- X includes the current IP address of the MN 10 and the IP address of the CN 60.
- the session identifier Y is set to a sufficiently large arbitrary number. In this state, after MN 10 moves to subnet 30, it sends a RESERVE message to CN 60 to establish a new QoS route. Note that the old route (route 24) is not released immediately after MN10 moves.
- the flow identifier X is different from the flow identifier on the route 34 (the flow identifier on the route 34 is Z). Since QNE67 has no resource reservation for session identifier Y at any interface, it determines that a new route has been established and reserves resources for flow identifier Z and session identifier Y. On the other hand, QNE65 and QNE66 have a resource reservation for the session identifier Y.
- QNE65 and QNE66 compare the flow identifiers here and confirm that the flow identifiers have changed from X to Z, and determine that this is a new route establishment accompanying the movement of MN10, and double resource reservation To avoid this, take steps such as updating old reservations instead of reserving new resources.
- the QNE where the old route and the new route begin to intersect is called CRN (crossover node).
- CRN crossover node
- the CRN refers to the old route (route 24) and the new route (route 34).
- One adjacent QNE (QNE66 in Figure 14) has the same force.
- the other adjacent QNE QNE63 and QNE67 in Figure 14) refers to a different QNE (QNE65 in Figure 14).
- Non-Patent Document 6 and Non-Patent Document 9 such a RESERVE message, a QU ERY message, and a NOTIFY message are transmitted to a terminal terminal (MN10 or CN60) that is a transmission destination or a transmission source of a data packet. Any QNE is not the only source.
- NSIS covers not only the mopile environment but also various functions in a normal static network.
- one of the functions of NSIS is mobility support. Focusing on the function of realizing the establishment of a casino-like service, it is assumed that the implementation of NSIS will realize the establishment of a mobility-supported casino-like service.
- Non-Patent Document 1 D. Johnson, C. Perkins and J. Arkko, “Mobility Support in IPv6", draft-iet— mobileip-ipv6-24, June 2003
- Non-Patent Document 2 Rajeev Koodli "Fast Handovers for Mobile IPv6"
- Non-Patent Document 3 R. Braden, L. Zhang, S. Berson, S. Herzog and S. Jamin, "Resource ReSerVation Protocol-Version 1 Functional Specification", RFC 2205, September
- Non-patent document 4 NSIS WG (http://www.ietf.org/html.charters/nsis-charter.html)
- Non-patent document 5 H. shi haskar, Ed, "Requirements of a Quality of service (QoS) boiution for Mobile IP ", RFC3583, September 2003
- Non-Patent Document 6 Sven Van den Bosch, Georgios Karagiannis and Andrew McDonald "NSLP for Quality-of-Service signaling", draft-ietf-nsis-qos-nslp-01.txt, October 2003
- Patent Document 7 X. Fu, H. Schulzrinne, H. Tschofenig, "Mobility issues in Next Step signaling", draft-fu-nsis- mobility- 01.txt, October 2003
- Non-Patent Document 8 Roland Bless, et.AL, "Mobility and Internet Signaling Protocol", draft—many folks—signaling—protocol—mobility—00.txt, January 2004
- Non-Patent Document 9 R. Hancock (editor), Next Steps in Signaling: Framework ", draft-ietf-nsis-lw-05.txt, October 2003
- a handover is performed to a subnet 30 connected to the MN 10 that has received QoS guarantee in the subnet 20 connected before the handover, and received before the handover in the subnet 30 connected after the handover. Consider continuing to receive QoS assurance.
- the MN 10 after the MN 10 performs a handoff with the subnet 20 connected before the handover, the MN 10 receives a supplementary service (here, QoS guarantee) in the subnet 30 connected after the handover.
- QoS guarantee a supplementary service
- This time is a time during which the MN 10 cannot receive the QoS guarantee, and the MN 10 cannot receive the QoS guarantee at all, or the default QoS transfer processing is performed, resulting in QoS catastrophe.
- the present invention provides a mobile terminal that performs a handover, even after a handover, before and after the handover, so that the mobile terminal can quickly and continuously receive an additional service. It is an object of the present invention to provide a communication handover method, a communication message processing method, and a program for executing these methods by a computer.
- the communication handover method of the present invention forms a unique communicable area in which a plurality of access routers each constituting a subnet are connected via a communication network.
- the access point is connected through wireless communication with the access point within the communicable area.
- the mobile terminal can communicate from an access point currently communicating to another access point.
- the mobile terminal Based on the information of the another access point received in the receiving step, when the communication is switched to the another access point, the mobile terminal prepares for an additional service after the communication switching desired by the mobile terminal.
- Information acquisition step for acquiring information on routers that can
- a message containing information on a service similar to a service received during the current communication is generated, and the communication switching is performed based on information of a router capable of preparing for an additional service after the communication switching.
- the communication handover method of the present invention may further include a step of storing the information of the access point in the predetermined information storage means of the mobile terminal and the additional information after the communication switching. It has a storing step of storing correspondence information describing a correspondence relationship with information of a router capable of preparing for a service.
- the mobile terminal can hold information of a router that can make preparations for additional services after communication switching in association with information of an access point.
- the communication handover method of the present invention further comprises, in said information acquiring step, based on said information of said another access point received in said receiving step, From the information, information of a router that can make preparations for the additional service after the communication switching associated with the another access point is obtained.
- the communication handover method of the present invention provides a unique communicable area in which a plurality of access routers each constituting a subnet are connected via a communication network.
- the access point is connected through wireless communication with the access point within the communicable area.
- the mobile terminal transmits, to a predetermined server capable of acquiring information of a router capable of preparing for the additional service after communication switching, information on the additional service currently received.
- Providing the mobile terminal allows the mobile terminal performing the handover to continue to receive the additional services that it is currently receiving even after the access point switches communication. As a result, you will be able to receive quick and continuous services.
- the communication handover method of the present invention includes: In a communication system in which a plurality of access routers constituting a subnet are connected via a communication network and an access point forming a unique communicable area is connected to at least one of the plurality of access routers, respectively.
- a communication handover method in a mobile terminal wherein the access point is connected to the access router through wireless communication with the access point in the communicable area and communicates with the access router.
- the mobile terminal generates a message containing information on a service similar to a current service received during the current communication, and when the mobile terminal switches communication from the currently communicating access point to another access point, An information transmitting step of transmitting the message to all the predetermined routers selected by the mobile terminal through the currently communicating access point, which can realize an additional service after communication switching. Te ru.
- information on an additional service received during the communication is included for a predetermined router having a function of realizing a supplementary service that the mobile terminal grasps at a glance.
- the mobile terminal performing the handover process can continue to receive the additional service currently received even after the access point switches communication. You will be able to receive quick and continuous services such as those received before handover.
- the communication handover method of the present invention further includes, under the mobile terminal, the another access point based on the information of the another access point received in the receiving step. Identifying an access router;
- the mobile terminal can perform the stateless automatic setting of the address information.
- the communication handover method according to the present invention in addition to the above configuration, further comprises the information transmission In the step, the address information generated in the address generation step is included in the message, and the message is transmitted.
- the mobile terminal can transmit, as one message, the address information generated by the stateless automatic configuration together with the information on the additional service currently being received.
- the additional service is QoS guarantee.
- the mobile terminal that performs the handover can quickly and continuously receive the QoS guarantee that was received before the handover.
- a communication handover program for causing a computer to execute the above communication handover method.
- the communication message processing method of the present invention comprises a plurality of access routers each constituting a subnet connected via a communication network to form a unique communicable area. At least one access point is connected to each of the plurality of access routers, and the access point is connected to a mobile terminal existing in the communicable area through wireless communication with the access point. The mobile terminal switches communication with the access point when the mobile terminal switches communication with the access point.
- a communication message processing method in a router capable of preparing for a dynamic service
- the communication message processing method of the present invention may be such that, in the second information receiving step, the communication terminal is present on the partner terminal or on a path of the message to the partner terminal.
- the router that has received the message containing the information on the additional service that the mobile terminal is currently receiving during communication receives the information on the route to the partner terminal, and retains the information. It is possible to do.
- the second information receiving step in addition to the above-described configuration, a preparation for the additional service after the communication switching received by the other terminal is received. Generating a message containing information enabling the message to be transmitted and transmitting the message to the mobile terminal.
- the router that has received the message containing information on the additional service that the mobile terminal is currently receiving during communication can receive the message and perform the preparation for the additional service after the communication is switched. After acquiring the information, it is possible to notify the mobile terminal.
- the communication message processing method of the present invention may further comprise, in the first information receiving step, the mobile terminal power not present in the subnet to which the access router belongs. Among the services to which the access router belongs. Verifying the validity of the address information, if the address information usable by the mobile terminal is included in the subnet.
- the establishment of a route for additional services requires address information of the mobile terminal.
- address information of the mobile terminal For example, the validity of the address information generated by stateless automatic configuration is grasped by the mobile terminal. In such a case, it becomes possible to establish a route for additional services related to the mobile terminal as much as possible.
- a communication message processing method provides an access point in which a plurality of access routers each constituting a subnet are connected via a communication network and form a unique communicable area. Is connected to at least one of each of the plurality of access routers, and a mobile terminal existing in the communicable area is connected to the access point through wireless communication with the access point. Communication in a node or router that is arranged in a communication system configured to perform communication with a router and that constitutes a route for an additional service when the mobile terminal communicates with a predetermined communication terminal.
- a message processing method comprising a flow identifier and a session identifier related to a predetermined route. When a message for checking whether or not the predetermined route has been established is received, the resource reservation for the flow identifier and the session identifier included in the message is performed.
- the node or router that has received the message including the flow identifier and the session identifier related to the predetermined route uses this flow identifier. And a resource reservation for the session identifier is made. Can be returned to the destination.
- the communication message processing method of the present invention comprises a plurality of access routers, each constituting a subnet, connected via a communication network to form a unique communicable area. At least one access point is connected to each of the plurality of access routers, and the access point is connected to a mobile terminal existing in the communicable area through wireless communication with the access point.
- the mobile terminal is disposed in a communication system configured to perform communication with the access router, and a node or a node configuring a route related to an additional service when the mobile terminal performs communication with a predetermined communication terminal.
- a communication message processing method in a router wherein a flow identifier and a session identifier related to a predetermined route are In the case where a message for checking whether or not the predetermined route is established is received, the resource reservation for the flow identifier and the session identifier included in the message is performed.
- the resource is used for the resource reservation in a predetermined portion of the message.
- the node or router that has received the message including the flow identifier and the session identifier related to the predetermined route transmits the flow identifier and It is determined whether or not the resource reservation for the session identifier has been made. If the resource reservation has been made, the address information of the interface of the own device relating to the resource reservation is inserted into the message, and this message is For example, by referring to the contents of the message, it becomes possible to specify the node or router that has made the resource reservation for the route.
- the order in which the address information of the interface is added is represented by the predetermined location.
- the communication message processing method of the present invention comprises a plurality of access routers, each constituting a subnet, connected via a communication network to form a unique communicable area.
- the access point to which the access point is connected through wireless communication with the access point within the communicable area.
- a communication that communicates with a mobile terminal that is configured to communicate with a router and that can establish a route for an additional service when communicating with the mobile terminal.
- a flow identifier and a session identifier related to a predetermined route are included, and when a message for searching for the predetermined route is received, a new message including the search result of the predetermined route in the message is received. And transmitting the same as a response to the message.
- a message for searching for a route of the additional service established between the mobile terminal and the partner terminal is transmitted to the partner terminal, and the search collected by the message is performed.
- a message containing the result can be returned as a response.
- the communication message processing method of the present invention may include a message for checking whether or not the predetermined route is set or a message for searching for the predetermined route.
- a message for checking whether or not the predetermined route is set or a message for searching for the predetermined route Is a QUERY message or a RESPONSE message having an area that can include the flow identifier and the session identifier related to the path.
- the communication message processing method of the present invention may further include a message for checking whether the predetermined route is set or a message for searching for the predetermined route. It has an area that can include information on available resources.
- the information of free resources (for example, resource Release status) can be grasped.
- a plurality of access routers each constituting a subnet are connected via a communication network, and an access point forming a unique communicable area includes the plurality of access routers.
- At least one or more mobile terminals are connected to each of the routers, and mobile terminals existing in the communicable area communicate with the access router to which the access point is connected through wireless communication with the access point.
- Message processing method in a node or a router which is arranged in a communication system configured to perform communication with a predetermined communication terminal and configures a path for an additional service when the mobile terminal performs communication with a predetermined communication terminal.
- the session identifier When a message for checking whether or not the predetermined route is set and the V is set is received when the predetermined route is set, the session identifier has a state corresponding to the session identifier.
- the transmission step includes transmitting the message to the predetermined communication terminal.
- the mobile terminal transmits a message for searching for a route of the additional service established between the mobile terminal and the partner terminal toward the partner terminal, and the message is transmitted to the partner terminal. It is possible to discover a crossover node without reaching the terminal, and it is possible to find a crossover node more quickly.
- a plurality of access routers each forming a subnet are connected via a communication network, and an access point forming a unique communicable area includes the plurality of access routers.
- At least one or more mobile terminals are connected to each of the routers, and mobile terminals existing in the communicable area communicate with the access router to which the access point is connected through wireless communication with the access point.
- Message processing method in a node or a router which is arranged in a communication system configured to perform communication with a predetermined communication terminal and configures a path for an additional service when the mobile terminal performs communication with a predetermined communication terminal.
- a session identifier related to a predetermined route is included, and the predetermined route is set.
- the identification information and the session identifier for specifying the flow relating to the predetermined route are included. If the predetermined route is set and a message for checking whether or not the flow is received is received, the flow is specified.
- the state has the state for the session identifier, it is determined whether or not different adjacent nodes or routers are designated in each of the state and the message.
- the mobile terminal transmits a message for searching for a route of the additional service established between the mobile terminal and the partner terminal toward the partner terminal, and the message is transmitted to the partner terminal. It is possible to discover a crossover node without reaching the terminal, and it is possible to find a crossover node more quickly.
- the communication message processing method of the present invention is adapted to the above configuration, and when it is determined in the CRN determination step that it is a cross quano node, the predetermined message is transmitted to a predetermined node. Has a notification step of notifying that it is a crossover node.
- the node or the router configuring the path related to the additional service includes the resources and the information specifying the flow.
- a node or a router which is a component of a route relating to an additional service, can grasp the correspondence between resources and information that specifies a flow.
- the communication message processing method of the present invention is adapted to the above configuration, and when it is determined in the CRN determination step that it is a crossover node, the receiving node or router receives the message.
- a communication message processing program for causing a computer to execute the above communication handover method.
- the present invention provides a communication handover method and a communication message processing method having the above-described configuration, and a program for executing these methods by a computer, in advance (before a nodeover or immediately after a handover).
- a communication handover method and a communication message processing method having the above-described configuration, and a program for executing these methods by a computer, in advance (before a nodeover or immediately after a handover).
- the CRN By finding the CRN, there is an effect that the mobile terminal performing the handover can quickly and continuously receive the additional service received before the handover even after the handover.
- a QUERY is performed in order to obtain information on a new route
- the MN must perform the pre-movement between the CRN and the CN.
- the information can be correctly returned in consideration of the resource reservation status.
- FIG. 1 is a schematic diagram showing a configuration of a communication system according to an embodiment of the present invention.
- FIG. 2 is a block diagram showing a configuration of an MN according to the embodiment of the present invention.
- FIG. 3 is a block diagram showing a configuration of a proxy according to the embodiment of the present invention.
- FIG. 4 is a block diagram showing a configuration of a QNE according to the embodiment of the present invention.
- FIG. 5 is a block diagram showing a configuration of a CN according to the embodiment of the present invention.
- FIG. 6 is a schematic diagram showing an example of how information processed by a QNE is stored in a message exchanged between a proxy and a CN in the embodiment of the present invention.
- the MN requests the proxy to prepare for establishment of a QoS route, and illustrates an example of an operation when the preparation is performed.
- FIG. 8 is a second sequence chart showing an example of an operation when the MN requests the proxy to prepare for establishing a QoS route in the communication system according to the embodiment of the present invention, and the preparation is performed.
- FIG. 10 Schematic diagram for explaining that RSVP in the conventional technology cannot cope with MN movement
- FIG. 11 Schematic diagram for explaining the NSIS protocol configuration in the conventional technology
- FIG.12 Schematic diagram for explaining the concept of NEs and QNEs, which are NSIS nodes in the conventional technology, being “adjacent”
- FIG. 14 A schematic diagram for explaining how to avoid double resource reservation in NSIS in the conventional technology.
- FIG. 15 is a schematic diagram showing an example of proxy information stored in the MN according to the embodiment of the present invention.
- FIG. 16 is a schematic diagram showing an example of AP-AR correspondence information stored in the MN according to the embodiment of the present invention.
- an MN requests a proxy to prepare for establishment of a QoS route, and a RESPONSE message used in the conventional NSIS is used as a message used for the preparation.
- Sequence chart showing an example of the operation in the case
- an MN requests a proxy to prepare for establishment of a QoS route, and a RESPONSE message used in the conventional NSIS is used as a message used for the preparation.
- Sequence chart showing an example of the operation in the case
- FIG. 19 is a block diagram showing a configuration of a proxy that implements another processing method after receiving message C in the embodiment of the present invention.
- FIG. 20 is a block diagram showing a configuration of a CN that implements another processing method after receiving message B in the embodiment of the present invention.
- FIG. 21 is a sequence chart showing an example of an operation when a proxy requests a CRN to establish a QoS route in the communication system according to the embodiment of the present invention.
- FIG. 22 In the communication system according to the embodiment of the present invention, the first sequence chart showing an example of the operation when the MN requests the proxy to prepare for establishment of the QoS route and the preparation is performed.
- FIG. 23 is a second sequence chart showing an example of an operation when the MN requests the proxy to prepare for establishment of a QoS route and the preparation is performed in the communication system according to the embodiment of the present invention.
- FIG. 24 is a sequence chart showing an example of an operation for finding a CRN without sending an MN message to the CN in the communication system according to the embodiment of the present invention.
- FIG. 25 is a flowchart showing an example of a method in which a QNE that has received a message determines whether or not it is a CRN in the communication system according to the embodiment of the present invention.
- FIG. 1 is a schematic diagram illustrating a configuration of a communication system according to an embodiment of the present invention.
- the QoS path (path 24) established between the MN 10 and the CN 60 before the handover is connected to the subnet 20 before handover is shown by a solid line! .
- AR21, AR62, QNE63, ⁇ 64, QNE65, and QNE66 are present on this route 24 toward MN10 and CN60.
- the QoS route (route 34) established with the CN 60 is shown by a dotted line.
- FIG. 2 is a block diagram showing a configuration of the MN according to the embodiment of the present invention.
- each function of MN10 is Each of these functions can be implemented by hardware and z or software.
- main processing of the present invention processing of each step shown in FIG. 7 described later
- the MN 10 shown in FIG. 2 includes a handover destination candidate determining unit 101, a wireless receiving unit 102, a radio transmitting unit 103, a proxy determining unit 104, a message generating unit 105, and a message receiving unit 106. Also, as an option, an NCoA generation means 107 and a proxy information storage means 108 may be provided. In FIG. 2, the option part is indicated by a dotted line.
- the handover destination candidate determining means 101 is, for example, a means for receiving signals from a plurality of different APs and searching for a list of APs capable of L2 handover. Note that the MN 10 can also perform the processing by the proxy determining means 104 described later directly without determining the L2 handover destination candidate by the handover destination candidate determining means 101.
- the wireless receiving means 102 and the wireless transmitting means 103 are means for performing data reception and data transmission by wireless communication, respectively, and include various functions necessary for performing wireless communication. I have.
- the proxy determining means 104 is a means for finding a proxy.
- the proxy discovered by the proxy determination means 104 is a proxy for the MN 10 so that the MN 10 can receive additional services (here, QoS) after handover without interruption.
- QNE NSIS node
- QNE NSIS node
- the proxy information 40 stored locally in the MN 10 proxy information 40 stored in the proxy information storage means 108 based on the AP-list information acquired by the handover destination candidate determination means 101
- a method of transmitting the information related to the most suitable proxy described above, or a method of selecting all the proxies stored in the proxy information 40 is cited.
- the hand The AR of the over destination candidate is the QNE itself and may become a proxy.
- the proxy information 40 shown in FIG. 15 illustrates an example of the content of the proxy information 40.
- the proxy information 40 shown in FIG. 15 is an example created with reference to the network configuration in FIG.
- the proxy information 40 shown in FIG. 15 has the IP address of a node that can be selected as a proxy when the MN is connected to each AP, and the MN refers to the proxy information 40 to It becomes possible to select and specify a proxy.
- As a proxy it is desirable to set a QNE near the AR that has each AP under its control (near the AR on the network configuration).
- Message generating means 105 is a means for generating, in the proxy, a message including information necessary for preparation in advance so that MN 10 can receive QoS without being interrupted after handover.
- the information necessary for the MN 10 to be able to receive the QoS after the handover without being interrupted includes, for example, a flow identifier and a session identifier currently used, and a data flow direction (MN1 0 force, etc.
- Direction force of CN60 Direction force of CN60 to MN10, bidirectional communication force, etc. Note that the above message generated by message generation means 105 is message A.
- the message receiving means 106 is for receiving, when the proxy performs the above-mentioned preparation, whether or not the preparation was successful, a message containing information such as! This is a means and can be omitted depending on the method of establishing a new QoS route. This message D is intended to include information obtained when the proxy performs the above preparation.
- MN 10 can specify the destination, generate NCo A to be used there, and send it to the proxy of the destination.
- the means for generating the NCoA is the NCoA generation means 107, and the generated NCoA is stored in the message A together with the flow identifier in the message generation means 105.
- the MN 10 has the AP-AR correspondence information 41 as shown in FIG. 16 (an example created with reference to FIG. 9 similarly to FIG. 15) and determines the handover destination candidate. Based on the AP information obtained by the means 101, the AP-AR correspondence information 41 is searched, and the AP to which the AP is connected is searched.
- a method is conceivable in which NCoA is automatically generated in a stateless manner by obtaining AR information (eg, AR link layer address, network prefix and prefix length of the subnet to which the AR belongs).
- the message A can also include other information (for example, information such as the IP address of the current neighboring Q NE (QNE 63) of the MN 10).
- FIG. 3 is a block diagram showing a configuration of the proxy according to the embodiment of the present invention. Note that, similarly to the MN 10 shown in FIG. 2, each function of the proxy 68 shown in FIG. 3 can be realized by hardware and Z or software. In particular, main processing of the present invention (processing of each step shown in FIG. 7 described later) can be executed by a computer program.
- the proxy 68 shown in FIG. 3 has a receiving unit 681, a transmitting unit 682, message processing units 683 and 684, and message generating units 685 and 686. Further, a message generating means 687 and a route information storing means 688 may be optionally provided. In FIG. 3, the option part is shown by a dotted line. [0069]
- the receiving means 681 and the transmitting means 682 are means for performing data reception and data transmission.
- the message processing means 683 is a means for receiving and processing a message (message A) generated by the message generation means 105 of the MN 10 shown in FIG. 2 and transmitted by the wireless transmission means 103. For example, the information of the data flow included in message A is confirmed, and it is determined how it is desirable to establish a QoS route. The change of the QoS route establishment method due to the data flow will be explained together with the function of the intermediate QNE described later.
- the message generating means 685 outputs the flow identifier (for example, the flow identifier X of the path 24) and the session identifier (for example, the session identifier Y common to the paths 24 and 34) received by the message processing means 683.
- the message B generated by the message generating means 685 is a message for discovering a CRN, and is transmitted to the CN 60 via the transmitting means 682.
- the flow identifier includes the IP address information of CN60.
- the message processing means 684 receives the message generated by the message generating means 685 and transmitted from the CN 60 that has received the message B via each QNE on the route 34 (hereinafter referred to as message C). ) Is received and processed.
- This message C contains the information of CRN.
- the message processing means 684 performs processing for the MN 10 to quickly establish a QoS path at the time of handover based on the CRN information. There are several ways to do this. For example, this information is passed to the route information storage unit 688, and any processing may be performed at the time when the MN 10 performs a handover.
- Message (message D mentioned above). However, in this case, the MN 10 needs to be provided with the message receiving means 106 shown in FIG. As described above, the message D may include information indicating whether the preparation is successful. Further, the message D may include other information.
- the message processing means 683 If the message processing means 683 has received the information of the NCoA of the MN 10, the message generation means 687 generates a new flow identifier based on the NCoA, and the message processing means 684 receives the new flow identifier.
- RESERVE message based on CRN information A new QoS route may be created on route 34 by sending to CN 60. In this case, however, another function is required, such as providing the CRN information in the RESERVE message and making sure that the corresponding CRN does not double the resource reservation up to CN60. It should be noted that information on QSpec, which is necessary for establishing a QoS route and should be included in the RESERVE message, can be obtained from this CRN by referring to, for example, information on the CRN included in message C.
- the message A contains information of the current adjacent QNE (QNE63) of the MN 10, it can be obtained from the QNE 63. If it is necessary to check the validity of the NCoA sent as described above, the check must be performed. If this proxy does not have the NCoA validity check function, or if the result of the validity check is not valid, for example, an error message for notifying MN10 of an error is sent. Must be returned. This error notification can be included in message D or can be returned as another message (eg, FBAck message in FMIP).
- the message B generated by the message generation means 685 includes information other than the above (for example, NCoA that has been confirmed to be valid, or the current adjacent QNE of MN10 included in message A). (QNE63) etc.).
- FIG. 4 is a block diagram showing a configuration of an intermediate QNE on route 34 in the embodiment of the present invention. Note that, similarly to the MN 10 shown in FIG. 2, each function of the QNE 65 shown in FIG. 4 can be realized by hardware and Z or software. In particular, main processing of the present invention (processing of each step shown in FIG. 7 described later) can be executed by a computer program.
- the QNE 65 shown in FIG. 4 includes a receiving unit 651, a transmitting unit 652, a message processing unit 653, and a message generating unit 654.
- the receiving unit 651 and the transmitting unit 652 have the same functions as the receiving unit 681 and the transmitting unit 682 of the proxy 68 shown in FIG.
- the message processing means 653 upon receiving the above-mentioned message B or message C, the message processing means 653 checks whether there is already a resource reservation in the QNE 65 based on the pair of the flow identifier and the session identifier included in the message B or the message C. Means. If you cannot make a reservation, In step 654, nothing is performed, and message B or message C is transferred to the next QNE via transmission means 652.
- the IP address of the interface is stored in the message in the message generating means 654, and the message is transmitted via the new message transmitting means 652 generated by the message generating means 654. Sent to the next QNE. However, if message B or message C requests the QNE to do some other processing, for example, if it is an extension of the QUERY message or the RESPONSE message to it, processing specific to these messages is performed. Is performed.
- Whether to perform the above-described processing using message or message C depends on the direction of data flow and other NSIS functions. As an example, if the data flow is only from the CN60 to the MN10, according to the concept of the QoS route determination method of RSVP (see Non-Patent Document 3), when the message C sent from the CN60 is received, It is appropriate to perform the above processing.
- route through which data and signaling pass may differ in the direction from MN10 to CN60 (upstream) and the direction from CN60 to MN10 (downstream). It is possible that message B does not go through route 34, although route 34 can be determined. Therefore, each QNE on route 34 may receive only one of message B and message C.
- message C can be a message that is only used by each QNE to return the processed result when proxy B receives message B to proxy 68.
- NSIS does not always apply the concept of the RSVP route determination method. For example, it may be possible for message B to gather the necessary information for the downstream data flow along route 34.
- FIG. 5 is a block diagram showing a configuration of the CN according to the embodiment of the present invention. Note that, like MN10 shown in FIG. 2, CN6 shown in FIG. Each function of o can be realized by hardware and Z or software. In particular, main processing of the present invention (processing of each step shown in FIG. 7 described later) can be executed by a computer program.
- the CN 60 shown in FIG. 5 includes a receiving unit 601, a transmitting unit 602, a message processing unit 603, a message generating unit 604, and a route information storage unit 605.
- the receiving means 601 and the transmitting means 602 have the same functions as the receiving means 681 and the transmitting means 682 of the proxy 68 shown in FIG. 3, and the receiving means 651 and the transmitting means 652 shown in FIG.
- the message processing means 603 has a function of receiving and processing the message B. For example, in the message processing means 603, it is determined whether the message B has been issued to the upstream or the message B has been issued to the downstream.
- the message processing unit 603 can also pass the information of the CRN to the route information storage unit 605 to hold the information.
- the CN 60 can perform the QoS route establishment process using the RESE RVE message when the NCoA information of the MN 10 is obtained.
- the NCoA information of MN10 is included in message B, it can be obtained simultaneously with reception of message B, or can be obtained from the BU message from MN10. .
- the message generating means 604 generates the message C, and transmits the message C through the transmitting means 602. If message B contains routing information (which QNE had a resource reservation), it can be included in message C and transmitted. Further, the message C may include information other than the above.
- CN60 proxy 68 can obtain CRN information by transmitting and receiving message B and message C.
- bidirectional communication is being performed using MN10 and CN60, for example, IP telephony.
- MN10 and CN60 for example, IP telephony.
- these two-way data does not always pass through the same route (the same router). It is thought that each side is different.
- FIG. 1 it is assumed that the bidirectional data passes through the same route.However, even when the bidirectional data passes through a different route, the same method as described later is used.
- the CRN for each of the two-way communications can be determined.
- a flow identifier and a session identifier exist for the communication path in each direction, and the proxy receives a pair of the two-way flow identifier and the session identifier from the MN10. Just embed it in message B and send it to CN60!
- FIG. 6 illustrates an example of information that can be obtained by the proxy by transmitting and receiving the messages B and C.
- the IP address of the interface that has a resource reservation for the upstream flow identifier and session identifier (information 81: IP address of the upper interface (QNE66 side) of QNE65)
- the IP address of the interface that has a resource reservation for the upstream flow identifier and session identifier within QNE66 (information 82: IP address of the upper interface (CN60 side) of QNE66) ) Is attached.
- the CN60 or the proxy 68 sends the QNE having the IP address of the interface attached first (IP address of the information 81) to the upstream CRN. Can be determined.
- the proxy 68 determines that the QNE having the IP address of the interface attached last (the IP address of the information 84) in the information 83 and the information 84 You can judge it as CRN.
- the QoS route may change due to factors such as the state of the network, and the CRN may also change according to the change in the QoS route.
- an expiration date is set for the CRN information held by CN60 or proxy 68, and before the expiration date, CN60 or proxy 68 Maintain accurate CRN information by checking for changes and obtaining the latest CRN information It is also possible to do it.
- the expiration date can be set by CN60 or proxy 68 that receives the CRN information.When sending MN10 message A, the expiration date is notified to CN60 or proxy 68. You can.
- FIGS. 7 and 8 show that, in the embodiment of the present invention, MN 10 sends information of an identifier (flow identifier and session identifier) to proxy 68, and proxy 68 and CN 60 transmit a message via intermediate QNE 65-67.
- a sequence chart showing an example of the operation of finding upstream and downstream CRNs by exchanging data is shown. Note that the sequence charts shown in FIGS. 7 and 8 are for the case where the proxy 68 is selected as one of the proxies by the MN 10 in the network system shown in FIG. 1. After obtaining the information of, the information is returned to MN10. Further, a sequence of operations is shown in the sequence charts shown in FIGS. 7 and 8, and the process of step S523 shown in the sequence charts of FIGS. 7 and 8 is the same.
- the MN 10 that has received the L2 information from the neighboring L2 signal reachable AP first determines a subnetwork that can perform a handover based on the information (step S501: handover destination candidate is determined). Decision), and then determine a handover candidate proxy based on the L2 information of the AP (Step S503: QNE68 is determined as one of the proxies (proxy 68)).
- the MN 10 that has determined the proxy sets the upstream flow identifier and the session identifier, the downstream flow identifier and the session identifier on route 24 in message A, and also sets the information indicating two-way communication in message A.
- Step S505 Set flow identifier, session identifier, and "two-way communication" for upstream and downstream in route 24 to message A), and send message A to selected proxies (multiple proxies) (Step S507).
- message A may include information on the destination of message B (such as an IP address).
- the destination of message B is CN60 in the examples of FIGS. 7 and 8, for example, CRN search of QoS route for communication using triangular route in Mopile IPv6 is performed.
- the destination of message B can be the home agent of MN10.
- the proxy 68 generates a message B based on the information of the message A received from the MN 10. Since bidirectional communication is considered here, parameters are set so that upstream information can be obtained in message B, downstream information can be obtained in a reply message (message C), and parameters can be obtained from a router on the way.
- the flow identifier and the session identifier are set in message B (step S509: parameters are set in message B so that upstream information can be obtained in message B, and downstream information can be obtained in message B).
- the identifier and the session identifier are also set in message B), and message B is transmitted to CN60 (step S511). At this time, the proxy 68 needs to obtain the address of the CN 60 from the information of the flow identifier.
- Each QNE 65-67 on the route from the proxy 68 to the CN 60 checks the content of the message B and checks whether the resource reservation for the upstream flow identifier and the session identifier in the message B exists in the QNE. Confirm. If there is a resource reservation for the upstream flow identifier and session identifier, each QNE attaches the IP address of the interface where the node reservation exists to message B and sends it to CN60. send. On the other hand, if there is no resource reservation for the upstream flow identifier and session identifier, the message B is forwarded without adding information.
- step S513 received upstream Since there is no resource reservation for the use flow identifier and the session identifier, it is transmitted next as it is, step S515).
- step S513 a resource reservation for the upstream flow identifier and the session identifier exists.
- step S517 After the IP address of the interface where the resource reservation exists is added to message B, message B is transferred (step S517). : Set the IP address of the interface with resource reservation for the received upstream flow identifier and session identifier, step S519).
- QNE66 also has resource reservations for upstream flow identifiers and session identifiers, and those resource reservations do not exist.
- the message B is forwarded after being added to the message B.
- Step S521 Set the IP address of the interface that has the resource reservation for the received upstream flow identifier and session identifier. Step S523 ).
- message B arrives at CN60, and CN60, which has received message B, adds the information added to message B by each QNE65-67 (added to message B by each QNE65-67). Information) in Message C and
- Step S525 Set the contents of message B in message C and set parameters to collect downstream information in message C) and direct it to proxy 68 And send it (step S527). Also, each QNE 65-67 on the route from CN 60 to proxy 68 performs the same processing for message B described above for downstream message C.
- step S529 set the IP address of the interface with resource reservation for the received downstream flow identifier and session identifier, step S531).
- step S533 set the IP address of the interface with the resource reservation for the received downstream flow identifier and session identifier, step S535.
- step S537 The received downstream flow identifier and Since there is no resource reservation for the session identifier, it is transmitted next as it is, step S539).
- the proxy 68 that has received the message C in this way can refer to the message C to specify the information of the upstream and downstream CRNs, and the information of the upstream and downstream CRNs.
- message D step S5 41: The CRN information for upstream and downstream is set in message D
- message D is transmitted to MN10 (step S543).
- the proxy 68 can take various means other than sending the CRN information to the MN 10 after collecting the CRN information.
- the MN 10 can transmit the CRN information included in the RESERVE message when, for example, reserving resources after moving the subnet.
- the corresponding CRN can perform processing to prevent double reservation of the resources up to CN60.
- the corresponding CRN can perform processing such as renewing the reservation rather than reserving a new resource.
- the CRN is specified in advance in this way, even if the resource reservation is made after the handover of the MN10, the resource reservation while searching for the CRN will not be performed as in the conventional technology. It is possible to quickly establish a QoS route. Also, as described above, the proxy 68 that has obtained the information of the CRN can make a resource reservation before returning the information to the MN 10, so that a quicker QoS path establishment can be realized.
- message B and message C can be rewritten into existing messages, for example, a QUERY message, a RESPONSE message, and a NOTIFY message.
- FIGS. 17 and 18 show sequence charts in the case where the QUERY message has the function of message B and the RESPONSE message has the function of message C.
- the functions of the original QUERY and RESPONSE messages such as the function of acquiring information on available resources. Steps S551-S593 in Figs. 17 and 18 correspond to steps S501-S543 in Figs. 7 and 8, respectively, and the QUERY message and message C and the RESPONSE message and message D correspond to each other. It is in.
- the mobile terminal such as MN10 has no way of knowing the information on the resources reserved in the current communication with the communication partner, so the current communication between the CRN and CN60 is not possible.
- the resource information reserved by the communication cannot be determined as resource information that can be used when the MN 10 moves.
- the QUERY and RESPONSE messages contain information on the current flow identifier and session identifier of the MN10, so that the resource information reserved for the current communication can be used when the MN10 moves. Information can be determined.
- Non-Patent Document 6 resource availability information can be obtained only by the RESPONSE message.
- the QUERY message is transmitted from the proxy 68 to the CN 60 and the RESPONSE message is returned from the CN 60 to the proxy 68, the information on the availability of downstream resources can be obtained. Yes, there is a possibility. Therefore, if information on free resources in both directions is required, it is possible that the CN60 receives the QUERY Y message from the proxy 68 and returns a RESPONSE message to the MN10, and at the same time, sends another QUERY message to the proxy 68. .
- the proxy 68 processes the CRN information (the CRN information included in the message C) obtained by the message processing means 684 of Fig. 3 and the CN60 obtains the information by the message processing means 603 of Fig. 5.
- a method of processing the CRN information (the CRN information included in the message B) a method other than the above may be considered. These methods will be described with reference to FIGS. 19 and 20.
- FIG. 19 is a block diagram showing a configuration of a proxy that implements a processing method after receiving message C in the embodiment of the present invention.
- each function of the proxy 68 shown in FIG. 19 can be realized by hardware and Z or software.
- the receiving means 6811, the transmitting means 6812, the message processing means 6813, 6814, the message generating means 6815, 6816, 6817, and the route information storing means 6818 in FIG. 19 correspond to the receiving means 681, the transmitting means 682, and the message processing means in FIG.
- the means 683 and 684, the message generating means 685, 686, 687, and the route information storage means 688 have the same functions, respectively, and a description thereof will be omitted.
- the message generation means 6819 in Fig. 19 is used to request the generation of a QoS route to another node.
- the message has a function of generating a message (hereinafter referred to as a message E) and passing the message to the transmitting means 6812.
- a message E As the transmission destination of the message E, for example, the CRN specified by the processing related to the message B of the message processing means 6814 is considered.
- message E contains the information needed to generate the CRN-powered SQoS path (eg, the validated MCoA of MN10 or the IP address of CN60).
- the CRN that has received the message E transmitted by the proxy 68 transmits the RESERVE message to both the CN60 and the proxy 68, thereby updating the QoS route between the CRN and the CN60. It is possible to generate a new QoS route between the two.
- FIG. 20 is a block diagram showing a configuration of a CN that implements another processing method after receiving message B in the embodiment of the present invention.
- each function of the CN60 shown in FIG. 20 can be realized by hardware and Z or software.
- the receiving unit 6011, the transmitting unit 6012, the message processing unit 6013, the message generating unit 6014, and the route information storing unit 6015 in FIG. 20 are the receiving unit 601, the transmitting unit 602, the message processing unit 603, and the message generating unit 603 in FIG.
- the functions are the same as those of the means 604 and the path information storage means 605, and the description is omitted here.
- the message generating means 6016 in FIG. 20 has a function of generating a message (referred to as message E) for requesting another node to generate a QoS route, and passing it to the transmitting means 6012.
- message E As the transmission destination of the message E, for example, the CRN specified by the processing for the message B of the message processing means 6013 can be considered.
- message E contains the information needed to generate the CRN-powered SQoS route (e.g., the validated NCoA of MN10 obtained by the method described above, or the proxy that is the source of message B). 68 IP addresses).
- the CRN that has received the message E updates the QoS route between the CRN and the CN60, and updates the QoS route between the CRN and the proxy 68, for example, by transmitting a RESERVE message to both the CN60 and the proxy 68. It is possible that the rule generation is performed.
- FIG. 21 shows that, in the embodiment of the present invention, proxy 68, which has received a message including NCoA (message A) from MN 10, specifies a proxy by exchanging messages (message B and message C) with CN60.
- NCoA messages A
- message B messages B
- message C messages
- a sequence chart showing an operation example of requesting the created downstream CRN to create a new QoS route is illustrated. Note that the sequence chart shown in FIG. 21 is for the case where the proxy 68 is selected as one of the proxies by the MN 10 in the network system shown in FIG.
- step S5005 in FIG. 21 and step S5007 the power for performing the same processing as in step S511 to step S523 in FIG. 7 and steps S525 to S539 in FIG. 8 is omitted here. .
- the proxy 68 generates a message B based on the information of the message A received from the MN10. Since bidirectional communication is considered here, the proxy 68 sets parameters so that information on upstream in message B and information on downstream in reply message (message C) can be obtained from the midway generator, and sends it via message A.
- the received flow identifier and session identifier are set in message B (step S5001: message A is received and message B is ready to be sent), and message B is sent to CN60 (step S5005: message B is sent to CN60). Sent to). At this time, the proxy 68 needs to obtain the address of the CN 60 from the information of the flow identifier.
- the proxy 68 checks the validity of the MCo of the MN10 included in the message A together with the preparation for transmission of the message B in step S5001 (step S5003: The NCoA of the MN10 included in the message A). Validity check).
- the proxy 68 which has received the message C, which is the reply message of the message B transmitted in step S5005, refers to the message C, Identify the downstream CRN information (Step S5007: Receive message C and obtain downstream and upstream CRN (QNE65) information).
- the proxy 68 sets the information necessary for these CRNs to establish a new QoS route in message E (step S5009: CRN (QNE65) is new! /, The information needed to generate the QoS route). Is set in the message E), and the message E is transmitted to each of the upstream and downstream CRNs obtained in step S5007 (step S5011 and step S5013).
- the upstream CRN and downstream CRN are both QNE65, but it is possible that the interface addresses of the upstream CRN and downstream CRN obtained in step S5007 are different from each other (separate addresses in QNE65).
- the interface address is obtained as the upstream CRN and downstream CRN in step S5007), and the message E is transmitted separately for upstream and downstream.
- the information required for the CRN to establish a new QoS route includes, for example, a flow identifier used in the new QoS route. This new flow identifier can be generated based on the NCoA of MN10 validated in step S5003.
- the information required for the CRN to establish a new QoS route may include the IP address of the CN60 and the session identifier.
- QNE65 Upon receiving message E, QNE65 sends a RESERVE message for updating the QoS route to CN60 (step S5015), and sends a RESERVE message for generating a new QoS route to proxy 68. Send it (step 5017).
- a case is shown in which both the upstream and downstream QoS routes are updated in step S5015, and both the upstream and downstream QoS routes are newly generated in step S5017! / Puru.
- the same method can be used when a request for generating a new QoS route is made to the upstream CRN after acquiring the information of the CN60 force Upstream CRN.
- the message E is transmitted to the upstream CRN after acquiring the information of the CRN for CN60 upstream shown in FIG. 20 and the appropriate NCoA of MN10.
- the message E may include the information of the IP address of the proxy 68.
- the proxy determining means 104 of the MN 10 shown in Fig. 2 the MN 10 can also select the CN60 as a proxy.
- the CN60 can have the same function as the proxy 68 shown in FIG. 3 in combination with the function of the CN60 shown in FIG.
- the proxy 68 has the same function as the CN60 shown in FIG. This function can be combined with the function of the proxy 68 shown in FIG. In this case, the CRN information can be obtained by transmitting / receiving the message B and the message C to / from the CN 60 proxy 68 that has received the message A from the MN 10.
- the operation when CN60 is selected as proxy 68 will be described with reference to the sequence charts shown in FIGS. 22 and 23.
- the sequence charts shown in FIGS. 22 and 23 show a series of operations, and step S5043 shown in the sequence charts of FIGS. 22 and 23 is the same processing.
- the sequence charts shown in FIGS. 22 and 23 are for the case where the subnet 30 is selected as a candidate for the destination sub-network of the MN 10 in the network system shown in FIG. 1. After obtaining the information of the CRN, the case where the information is returned to the MN 10 is shown.
- the MN 10 that has received the L2 information from a neighboring L2 signal reachable AP first determines a subnetwork that can perform a handover based on the information (step S 5021: handover).
- QN adjacent to the MN 10 on the QoS route established when the MN 10 moves to its subnetwork based on the L2 information of the AP (moving subnet 30 in Fig. 1) If it is earlier, determine the QNE closest to AR31 on route 34 (Step S5023: QNE68 is determined as the QNE closest to AR31 on route 34). For this determination, a method similar to the method in which MN 10 determines a proxy in the above-described embodiment can be used.
- MN10 sets the information of the QNE (QNE68) determined in step S5023 in message A (step S5025: sets the information of QNE68 in message A).
- step S5025 sets the information of QNE68 in message A.
- message A contains the flow identifier for upstream and the session identifier, the flow identifier for downstream, and the A session identifier and information indicating two-way communication can also be set.
- the MN 10 sends this message A to the CN 60 (step S5027).
- CN60 generates message B based on the information of message A received from MN10.
- parameters are set so that downstream information is obtained in message B and upstream information is returned in a reply message (message C) from a router on the way, and the flow identifier and session identifier are set in the message.
- Set to B (Step S5029: Set parameters in message B, and set flow identifier and session identifier in message B so that downstream information can be obtained in message B and upstream information can be obtained in message C).
- the message B is transmitted (step S5031).
- the CN 60 sets the information of the flow identifier and the session identifier used in the current communication with the MN 10 in the message B. It is possible.
- Each QNE65-67 existing on the route from CN60 to QNE68 checks the content of message B, and determines whether resource reservation for the downstream flow identifier and session identifier in QNE65-67 exists in QNE65-67. Check if. Then, if there is a resource reservation for the downstream flow identifier and the session identifier, each QNE 65-67 adds the IP address of the interface where the resource reservation exists to message B, and then adds that message B to QNE68. Send to On the other hand, if there is no resource reservation for the downstream flow identifier and the session identifier, the message B is forwarded without adding information.
- QNE66 has a resource reservation for the downstream flow identifier and the session identifier, and the IP address of the interface where the resource reservation exists.
- Step S5033 Set IP address of interface with resource reservation for received downstream flow identifier and session identifier, step S5035).
- QNE65 also has resource reservations for downstream flow identifiers and session identifiers.
- the message B is transferred after being added to the IP address of the interface where the resource reservation exists S Message B (Step S5037: There is a resource reservation for the received downstream flow identifier and session identifier. Set the IP address of the interface, step S5039).
- step S5041 the received downstream flow identifier and Since there is no resource reservation for the session identifier, it is transmitted next as it is, step S5043).
- Step S5045 Set the contents of message B in message C, and use message C to set the upstream information in message C).
- the parameter is set to obtain the information ( ⁇ ) and transmitted to CN60 (step S5047).
- the QNE 65-67 performs the same processing on the message C for the upstream as the processing for the message B described above.
- step S5049 The received upstream Since there is no resource reservation for the use flow identifier and the session identifier, it is transmitted next as it is, step S5051). Also, QNE 65 has resource reservations for the upstream flow identifier and the session identifier, and message C is forwarded after being added to the IP address message of the interface where the resource reservations exist ( Step S5053: Set the IP address of the interface with resource reservation for the received upstream flow identifier and session identifier, step S5055).
- QNE66 also has resource reservations for the upstream flow identifier and session identifier, and the message C is added after the IP address of the interface where the resource reservation exists is added to message C.
- the C is forwarded (step S5057: set the IP address of the interface with resource reservation for the received upstream flow identifier and session identifier, step S5059).
- the CN60 that has received the message C can specify the information of the upstream and downstream CRNs by referring to the message C.
- the information is set in message D (step S5061: information of CRN for upstream and downstream is set in message D), and message D is transmitted to MN10 (step S5063).
- the CN 60 can take various means other than sending the CRN information to the MN 10 after collecting the CRN information.
- the data is bidirectional communication, and that the bidirectional data passes through the same route.However, even when the bidirectional data passes through different routes, the same method as described above is used. By doing so, the CRN can be determined for each of the two-way communications.
- destination described in this specification, for example, "t" to be transmitted to CN60, does not necessarily mean that the address of CN60 is specified as the destination address of the IP header and transmitted.
- the meaning of the partner is SCN60, which ultimately receives the message.
- the CRN can be found without sending the message to CN60. Such an example will be described with reference to FIGS. 1, 24, and 25.
- FIG. 24 is a sequence chart showing an example of an operation for finding a CRN without sending an MN force message to the CN in the communication system according to the embodiment of the present invention.
- the message includes a QUERY message and a RESPONSE message. The method using is shown.
- QNE68 receives a trigger for establishing a predicted route (step S2401: receives a trigger for establishing a predicted route).
- This trigger is, for example, the message A sent from the MN 10 to the proxy 68 described above.
- this trigger includes information necessary for preparing a predicted route, such as MN10 and CN60. Are used on the current communication route (route 24), and include information on a session identifier.
- identification information for example, current flow identifier, etc.
- identifying which flow has the ability to prepare for establishing a predicted route is provided. ⁇ It is also possible to include it in sage A.
- the message A includes the flow identifier used in the route 24.
- the message A may include information for specifying the CN 60 (for example, the IP address of the CN 60).
- message A may include destination information of message B (eg, IP address).
- destination information of message B eg, IP address.
- CRN search for QoS route for mobile IPv6 triangular route communication it is also possible to set the destination of message B to be the home agent of MN10 instead of CN60.
- the proxy 68 Upon receiving the trigger, the proxy 68 transmits a message (for example, a QUERY message can be used) to the CN 60 (step S2403).
- a message for example, a QUERY message can be used
- the proxy 68 may generate the flow identifier using its own IP address as the source address.
- the QUERY message includes information such as the session identifier used by the MN 10 and the CN 60 on the current communication route (route 24). It should be noted that it is also possible to include identification information (for example, a current flow identifier or the like) for specifying a flow identifier for preparing a predicted route establishment for any flow identifier.
- FIG. 25 is a flowchart illustrating an example of a method of determining whether or not a QNE that has received a message is a CRN in the communication system according to the embodiment of the present invention.
- QNE67 After receiving the QUERY message (step S2501: receiving the message), QNE67 checks whether or not the state (resource reservation) for the session identifier included in the QUERY message is! / (Step S2502: QUERY) Do you have a state for the session identifier included in the message?).
- QNE 67 determines that it is not a CRN because it does not have this state.
- QNE67 transmits a QUERY message to CN60 (step S2405).
- the determination shown in FIG. 25 is made.
- the QNE65 checks whether it has a state (resource reservation) for the session identifier included in the QUERY message after receiving the QUERY message (step S2501: QUERY) (step S2502: QUERY). Do you have a state for the session identifier included in the message?).
- the QNE65 has this state, next, it is checked whether or not the identification information for specifying the flow for preparing the predicted route establishment is included in the QUERY message.
- Step S2503 Does the QUERY message include an identifier that identifies the flow of the old route?)
- the flow identifier used in route 24 is included as an identifier for identifying the flow of the old route! /
- So QNE67 checks the session identifier checked in step S2501. It is checked whether or not this flow identifier is included in the state (step S2504: state for specified flow?). If this flow identifier is not included in the state corresponding to the session identifier, it is determined that it is not a CRN, and a QUERY message is transferred.
- QNE65 belongs to route 24, and the given flow identifier is included in the state. Next, QNE65 sends information on the neighboring QNE that sent the QUERY message (SII: Source Identification Information). ) (Step S250
- the state of QNE65 includes the information of SII on path 24 (that is, the information that QNE63 is SII), and QNE65 transmits this information and QUERY in step S2405. Compare with the information on QNE that sent the message (that is, the information on QNE67). If the information is determined to be different, it is determined that it is a CRN, while if it is the same, it is determined that it is not a CRN.
- step S2407 compares the session identifier and S ⁇ and recognizes that it is a cross quano node
- it proxies that it is the CRN.
- a RESPONSE message is sent to the proxy 68 to notify the QNE 68) (steps S2409 and S2411).
- QNE 65 force proxy 68 that recognizes itself as a CRN
- various usages of the CRN are conceivable besides notifying that it is the CRN. . For example, if the messages sent in step S2403 and step S2405 include the NCoA of MN10 and the flow identifier!
- the QN E65 that recognizes itself as a CRN will not return a RESPONSE message. It is also possible to transmit a RESERVE message for establishing a new route in the direction of the MN 10 and a RESERVE message for updating in the direction of the CN 60 to perform an operation related to resource reservation.
- a flow identifier When resource reservation is performed, it is not always necessary to use a flow identifier to identify the packet data to which the reserved resource is assigned.
- another identifier here, called a filter
- a filter may be included in the message (QUERY message, RESE RVE message, or the like).
- a filter instead of a flow identifier as an identifier used to find a CRN or reserve resources for a new route.
- a plurality of identifiers for identifying to which packet data the reserved resource is to be provided may exist for one resource reservation.
- the QNE has the same content as any identifier in the list (flow identifier list or filter list).
- this list can be used, for example, when updating a reservation between CRN (QNE65) and CN60.
- CRN QNE65
- filter list a list for identifying which packet data is to be given a reserved resource
- the list is a flow identifier list.
- QNE65 issues a RESERVE (update)
- RESERVE update
- the QNE 66 that has received the RES ERVE (update) message adds the new flow identifier to the list of flow identifiers to which the resources for the route 24 are allocated, and sends the RESER VE (update) message to the CN 60.
- QNE65 and QNE66 have resource reservations for both path 24 and path 34. It should be noted that the route 24 and the route 34 are not separately reserved, so that the resources are shared between the route 24 and the route 34! /, So that double resource reservation is avoided. Will be done.
- the flow identifier of the route 24 may be deleted from the flow identifier list of the QNE 65 and the QNE 66 after the MN 10 moves to the subnet 30 and starts transmitting and receiving data.
- the deletion method is, for example, to provide a timer so that when this timer exceeds a predetermined period, it is automatically deleted, or it is explicitly deleted by a message for deletion. A little.
- a communication handover method and a communication message processing method according to the present invention and a program for executing these methods by a computer include a mobile terminal that performs a handover, even after a handover. It enables the service to be received quickly and continuously, and is applied to the technical field related to the handover of mobile terminals that perform wireless communication.
- the mobile IPv6 protocol which is the next-generation Internet protocol, is used. It is applicable to the technical fields related to handover of mobile terminals that perform wireless communication and QoS guarantee using NSIS.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Quality & Reliability (AREA)
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP05709756A EP1715633A4 (en) | 2004-02-06 | 2005-02-04 | A COMMUNICATION TRANSMISSION PROCESS, COMMUNICATION METHOD PROCESSING METHOD AND PROGRAM FOR CARRYING OUT THESE PROCEDURES BY USING A COMPUTER |
JP2005517746A JPWO2005076548A1 (ja) | 2004-02-06 | 2005-02-04 | 通信ハンドオーバ方法及び通信メッセージ処理方法並びにこれらの方法をコンピュータにより実行するためのプログラム |
BRPI0507448-7A BRPI0507448A (pt) | 2004-02-06 | 2005-02-04 | método de transferência de passagem de comunicação para um terminal móvel, programa de transferência de passagem de comunicação, método de processamento de mensagem de comunicação para um nó ou um roteador, e, programa de processamento de mensagem de comunicação |
US10/597,712 US20070223420A1 (en) | 2004-02-06 | 2005-02-04 | Communication Handover Method, Communication Message Processing Method and Program for Executing These Methods by use of a Computer |
Applications Claiming Priority (8)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2004-031428 | 2004-02-06 | ||
JP2004031428 | 2004-02-06 | ||
JP2004-037516 | 2004-02-13 | ||
JP2004037516 | 2004-02-13 | ||
JP2004056853 | 2004-03-01 | ||
JP2004-056853 | 2004-03-01 | ||
JP2004-222521 | 2004-07-29 | ||
JP2004222521 | 2004-07-29 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2005076548A1 true WO2005076548A1 (ja) | 2005-08-18 |
Family
ID=34841841
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2005/001691 WO2005076548A1 (ja) | 2004-02-06 | 2005-02-04 | 通信ハンドオーバ方法及び通信メッセージ処理方法並びにこれらの方法をコンピュータにより実行するためのプログラム |
Country Status (6)
Country | Link |
---|---|
US (1) | US20070223420A1 (ja) |
EP (1) | EP1715633A4 (ja) |
JP (1) | JPWO2005076548A1 (ja) |
KR (1) | KR20060123601A (ja) |
BR (1) | BRPI0507448A (ja) |
WO (1) | WO2005076548A1 (ja) |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2006132281A1 (ja) * | 2005-06-09 | 2006-12-14 | Matsushita Electric Industrial Co., Ltd. | 経路設定方法及び経路管理装置 |
JP2007124643A (ja) * | 2005-10-13 | 2007-05-17 | Mitsubishi Electric Information Technology Centre Europa Bv | 移動端末のハンドオーバ手順を実行しなければならないかどうかを判断するための方法及びデバイス、移動端末のハンドオーバ手順の情報を転送するための方法及びデバイス、コンピュータプログラム、並びに第1の基地局及び第2の基地局から転送される信号 |
WO2007113621A1 (en) * | 2006-03-31 | 2007-10-11 | Telefonaktiebolaget L M Ericsson (Publ) | Updating state in edge routers |
WO2008052466A1 (fr) * | 2006-10-25 | 2008-05-08 | Huawei Technologies Co., Ltd. | Procédé, système et équipement pour une commutation parmi différents réseaux |
WO2008102547A1 (ja) * | 2007-02-19 | 2008-08-28 | Panasonic Corporation | QoS確立方法、その方法で用いられる移動端末及び中継ノード |
WO2008139705A1 (ja) * | 2007-04-27 | 2008-11-20 | Panasonic Corporation | リソース解除方法及びその方法で用いられる中継ノード |
JPWO2007119598A1 (ja) * | 2006-03-31 | 2009-08-27 | パナソニック株式会社 | 高速QoSハンドオーバ方法及びその方法で用いられる処理ノード |
US10624157B2 (en) | 2017-01-26 | 2020-04-14 | Hitachi, Ltd. | Network system, network management method and network management apparatus |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR100662885B1 (ko) * | 2005-02-04 | 2007-01-02 | 삼성전자주식회사 | FMIPv6에서 TCP 패킷의 끊김없는 전송을 보장하는핸드오프 방법 |
US8117340B2 (en) * | 2005-04-25 | 2012-02-14 | Microsoft Corporation | Trans-network roaming and resolution with web services for devices |
US7668140B2 (en) * | 2005-05-11 | 2010-02-23 | Alcatel-Lucent Usa Inc. | Roaming between wireless access point |
JP4289386B2 (ja) * | 2006-11-29 | 2009-07-01 | コニカミノルタビジネステクノロジーズ株式会社 | データ通信システム、画像形成装置、データ通信装置、プログラム及びデータ通信方法 |
KR100918388B1 (ko) * | 2006-12-05 | 2009-09-24 | 한국전자통신연구원 | 사전 자원 예약 기반의 액세스망 간의 핸드오버 방법 및 그핸드오버를 지원하는 이동 단말 |
WO2008145174A1 (en) * | 2007-05-25 | 2008-12-04 | Telefonaktiebolaget Lm Ericsson (Publ) | Route optimisation for proxy mobile ip |
US20090034472A1 (en) * | 2007-08-03 | 2009-02-05 | Research In Motion Limited | System and Method for Handing Over Sessions Between Networks |
US8798002B2 (en) * | 2010-09-30 | 2014-08-05 | Htc Corporation | Method of sending network configuration and related communication device |
JP6796604B2 (ja) * | 2018-01-19 | 2020-12-09 | 株式会社日立製作所 | ネットワーク管理システム、及び、ネットワーク管理方法 |
CN113556291B (zh) * | 2021-07-08 | 2024-04-30 | 北京奇艺世纪科技有限公司 | 流量跟踪方法、装置、设备及计算机可读介质 |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2000078165A (ja) * | 1998-09-01 | 2000-03-14 | Nec Corp | ハンドオフ制御方法、スイッチングノ―ド、移動無線端末、及び記録媒体 |
JP2002094566A (ja) * | 2000-08-31 | 2002-03-29 | Kankoku Joho Tsushin Gakuen | 無線インターネットで持続的なサービス品質を保証する方法 |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6999436B2 (en) * | 2001-04-16 | 2006-02-14 | Nokia Corporation | Method and apparatus for efficient routing of mobile node packets |
US7545754B2 (en) * | 2001-11-02 | 2009-06-09 | Ntt Docomo, Inc. | Geographically adjacent access router discovery and caching for mobile nodes |
AU2003244895A1 (en) * | 2002-06-20 | 2004-01-06 | Nokia Corporation | QoS SIGNALING FOR MOBILE IP |
-
2005
- 2005-02-04 EP EP05709756A patent/EP1715633A4/en not_active Withdrawn
- 2005-02-04 KR KR1020067017310A patent/KR20060123601A/ko not_active Application Discontinuation
- 2005-02-04 WO PCT/JP2005/001691 patent/WO2005076548A1/ja active Application Filing
- 2005-02-04 BR BRPI0507448-7A patent/BRPI0507448A/pt not_active Application Discontinuation
- 2005-02-04 JP JP2005517746A patent/JPWO2005076548A1/ja not_active Withdrawn
- 2005-02-04 US US10/597,712 patent/US20070223420A1/en not_active Abandoned
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2000078165A (ja) * | 1998-09-01 | 2000-03-14 | Nec Corp | ハンドオフ制御方法、スイッチングノ―ド、移動無線端末、及び記録媒体 |
JP2002094566A (ja) * | 2000-08-31 | 2002-03-29 | Kankoku Joho Tsushin Gakuen | 無線インターネットで持続的なサービス品質を保証する方法 |
Non-Patent Citations (1)
Title |
---|
See also references of EP1715633A4 * |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2006132281A1 (ja) * | 2005-06-09 | 2006-12-14 | Matsushita Electric Industrial Co., Ltd. | 経路設定方法及び経路管理装置 |
JP2007124643A (ja) * | 2005-10-13 | 2007-05-17 | Mitsubishi Electric Information Technology Centre Europa Bv | 移動端末のハンドオーバ手順を実行しなければならないかどうかを判断するための方法及びデバイス、移動端末のハンドオーバ手順の情報を転送するための方法及びデバイス、コンピュータプログラム、並びに第1の基地局及び第2の基地局から転送される信号 |
WO2007113621A1 (en) * | 2006-03-31 | 2007-10-11 | Telefonaktiebolaget L M Ericsson (Publ) | Updating state in edge routers |
JPWO2007119598A1 (ja) * | 2006-03-31 | 2009-08-27 | パナソニック株式会社 | 高速QoSハンドオーバ方法及びその方法で用いられる処理ノード |
US7849215B2 (en) | 2006-03-31 | 2010-12-07 | Telefonaktiebolaget L M Ericsson (Publ) | Updating state in edge routers |
CN101416448B (zh) * | 2006-03-31 | 2013-10-16 | 艾利森电话股份有限公司 | 在边缘路由器中更新状态的方法及相应的边缘路由器 |
WO2008052466A1 (fr) * | 2006-10-25 | 2008-05-08 | Huawei Technologies Co., Ltd. | Procédé, système et équipement pour une commutation parmi différents réseaux |
WO2008102547A1 (ja) * | 2007-02-19 | 2008-08-28 | Panasonic Corporation | QoS確立方法、その方法で用いられる移動端末及び中継ノード |
WO2008139705A1 (ja) * | 2007-04-27 | 2008-11-20 | Panasonic Corporation | リソース解除方法及びその方法で用いられる中継ノード |
US10624157B2 (en) | 2017-01-26 | 2020-04-14 | Hitachi, Ltd. | Network system, network management method and network management apparatus |
Also Published As
Publication number | Publication date |
---|---|
US20070223420A1 (en) | 2007-09-27 |
EP1715633A4 (en) | 2008-08-27 |
BRPI0507448A (pt) | 2007-07-10 |
JPWO2005076548A1 (ja) | 2007-08-02 |
KR20060123601A (ko) | 2006-12-01 |
EP1715633A1 (en) | 2006-10-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2005076548A1 (ja) | 通信ハンドオーバ方法及び通信メッセージ処理方法並びにこれらの方法をコンピュータにより実行するためのプログラム | |
JP4543041B2 (ja) | 新規経路設定方法及び移動端末並びに経路管理装置 | |
US11356973B2 (en) | Communication system, mobile communication terminal and position managing apparatus | |
Helmy et al. | Multicast-based mobility: A novel architecture for efficient micromobility | |
JP4971468B2 (ja) | 移動体ネットワークにおけるインタフェース選択 | |
JP4616842B2 (ja) | 通信方法及び通信メッセージ処理方法並びにこれらの方法をコンピュータにより実行するためのプログラム | |
WO2005081560A1 (ja) | 通信ハンドオーバ方法、通信メッセージ処理方法及びこれらの方法をコンピュータにより実行するためのプログラム並びに通信システム | |
JP2010521908A (ja) | プロキシ・モバイルipルーティング | |
WO2006123657A1 (ja) | アクセスルータ装置、モビリティ制御システム、モビリティ制御方法 | |
JP5655018B2 (ja) | ハンドオーバ処理システム、及びゲートウェイルータ | |
JPWO2007119598A1 (ja) | 高速QoSハンドオーバ方法及びその方法で用いられる処理ノード | |
US20090022106A1 (en) | Crossover node detection method and crossover node detection program for causing computer to execute the method | |
EP1677466A1 (en) | Communication handover method, communication message processing method, program for executing these methods by use of computer, and communication system | |
EP2252095A1 (en) | Mobile terminal and network node | |
Mavromoustakis et al. | QoS in Next generation mobile networks: an analytical study | |
WO2007015539A1 (ja) | クロスオーバノード検出前処理方法、この方法をコンピュータにより実行するためのクロスオーバノード検出前処理用プログラム、及びこの方法で用いられる移動端末 | |
Makaya et al. | Efficient handoff scheme for heterogeneous IPv6-based wireless networks | |
Jeong et al. | Low latency and cost effective handoff based on PBF scheme in hierarchical mobile IPv6 | |
KR20070018890A (ko) | 통신 핸드오버 방법, 통신 메시지 처리 방법, 및 이들방법을 컴퓨터로써 실행하기 위한 프로그램 및 통신 시스템 | |
Homnan | Possible solutions for IPv6 networks-based handover | |
Prehofer et al. | Active IP Networking: Towards Self-organized Ambient Communication |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2005517746 Country of ref document: JP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2370/KOLNP/2006 Country of ref document: IN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2005709756 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020067017310 Country of ref document: KR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 200580009034.6 Country of ref document: CN |
|
WWP | Wipo information: published in national office |
Ref document number: 2005709756 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 1020067017310 Country of ref document: KR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 10597712 Country of ref document: US Ref document number: 2007223420 Country of ref document: US |
|
ENP | Entry into the national phase |
Ref document number: PI0507448 Country of ref document: BR |
|
WWP | Wipo information: published in national office |
Ref document number: 10597712 Country of ref document: US |