WO2009110224A1 - 移動端末 - Google Patents
移動端末 Download PDFInfo
- Publication number
- WO2009110224A1 WO2009110224A1 PCT/JP2009/000953 JP2009000953W WO2009110224A1 WO 2009110224 A1 WO2009110224 A1 WO 2009110224A1 JP 2009000953 W JP2009000953 W JP 2009000953W WO 2009110224 A1 WO2009110224 A1 WO 2009110224A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- communication
- packet
- binding cache
- mobile terminal
- communication terminal
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/08—Mobility data transfer
- H04W8/082—Mobility data transfer for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/28—Timers or timing mechanisms used in protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/08—Mobility data transfer
- H04W8/14—Mobility data transfer between corresponding nodes
-
- 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]
Definitions
- the present invention relates to a mobile terminal that performs packet communication with a communication partner via a communication network.
- a mobile node (hereinafter also referred to as MN) using mobile IP (see Non-Patent Document 1) uses a care-of address (hereinafter also referred to as CoA: Care-of Address) as a destination address as its home address. It registers with a home agent (hereinafter also referred to as HA) that manages (hereinafter also referred to as HoA: Home Address) or a communication partner (hereinafter also referred to as CN: Correspondent Node), and requests transfer of the packet to the HoA.
- HA home agent
- HoA Home Address
- CN Correspondent Node
- Non-Patent Document 2 discloses a technique in which a MN uses a binding ID (hereinafter also referred to as BID: BindingBindIdentifier) as a technique for registering a plurality of CoAs in association with a single HoA.
- BID BindingBindIdentifier
- the location information of the MN registered (entry) in the HA and CN is called a binding cache (hereinafter also referred to as BC: Binding Cache), and a lifetime indicating its valid period is set in each entry.
- BC Binding Cache
- BU Binding-Update
- the MN sets the CoA registered in the binding cache as the destination for the packet to be transmitted to the CN and the packet. Send.
- the transmitted packet is directly delivered to the CN at the destination without going through the CN home agent.
- the CN determines that it is not necessary to maintain the binding cache registered with the MN. Thereby, since a BU message for extending the lifetime of the binding cache is not transmitted, the binding cache registered in the MN is automatically deleted after the lifetime expires.
- the MN uses the CoA registered in the binding cache as a destination address to send a packet. Can be sent. D. Johnson, C. Perkins, J. Arkko, "Mobility Support in IPv6", RFC3775, June 2004. R.Wakikawa, T.Ernst, K.Nagami, V.Devarapalli "Multiple Care-of Addresses Registration", draft-ietf-monami6-multiplecoa-05.txt, January 2008.
- the CN determines that it is not necessary to maintain the binding cache registered with the MN. Thereby, since the BU message for extending the lifetime is not transmitted, even if the CN moves to another network and acquires another CoA, the binding cache registered in the MN is not updated.
- the binding cache held by the MN may have a state in which the registered CoA no longer points to the correct destination of the CN even though the lifetime is valid.
- the MN transmits a packet using the CoA registered in the binding cache whose lifetime is still valid as the destination address. Therefore, the packet is not transferred to the CN at the new movement destination, and packet loss occurs.
- a state may occur in which the MN holds a binding cache in which the lifetime of the CN is valid.
- the MN transmits a packet using the CoA registered in the CN's binding cache as a destination. For this reason, the packet is not transferred to the CN at the new destination, and packet loss occurs.
- an object of the present invention is to provide a mobile terminal capable of preventing packet loss and preventing communication delay. It is another object of the present invention to provide a mobile terminal that can reduce processing load and traffic associated with transmission of useless BU messages.
- the mobile terminal performs packet communication using a binding cache including address information of the communication terminal via a communication network with a communication terminal that is a communication partner of the mobile terminal.
- a measuring means for measuring an elapsed time from the end of the last communication with the communication terminal until a new communication is started; a storage means for storing information on the valid time of the binding cache;
- a determination means for determining whether or not the measured elapsed time exceeds an effective time of the binding cache when communication with the communication terminal is started; and the elapsed time exceeds an effective time of the binding cache If it is determined, the home address of the communication terminal is set as the destination address of the packet to be transmitted, and the packet is A packet generator for generating the door, and transmitting means for transmitting the generated said packet to the communication terminal, the mobile terminal comprising is provided.
- the valid time of the binding cache corresponds to a BC usable period described later.
- the elapsed time corresponds to an elapsed time timer after the end of communication, which will be described later.
- the packet generation unit adds the address information of the communication terminal of the binding cache to the packet.
- the mobile terminal further comprises receiving means for receiving from the communication terminal a message including valid time information of the binding cache, and the storage means includes the binding cache included in the received message. Acquiring and storing valid time information is a preferred aspect of the present invention. With this configuration, it is possible to acquire information on whether or not the binding cache is valid.
- the measurement means starts measuring the elapsed time when communication with the communication terminal is completed.
- the elapsed time for determining whether or not the binding cache is valid can be acquired.
- the mobile terminal performs packet communication using a binding cache including address information of the communication terminal via a communication network with a communication terminal that is a communication partner of the mobile terminal, A measuring means for measuring an elapsed time from the end of the last communication with the communication terminal until a new communication is started; a storage means for storing information on the valid time of the binding cache; and When a plurality of address information of the communication terminal is included, the elapsed time measured when starting communication with the communication terminal, and the elapsed time corresponding to each address information, is valid for the binding cache.
- a determination means for determining whether or not the time is exceeded, and the address information corresponding to each address information
- the address information of the communication terminal in the binding cache is address information that has already passed the valid time of the binding cache.
- the mobile terminal performs packet communication using a binding cache including address information of the communication terminal via a communication network with a communication terminal that is a communication partner of the mobile terminal,
- Receiving means for receiving a packet from a communication terminal; determining means for determining whether or not the received packet is a packet encapsulated by a home agent of the mobile terminal; and encapsulated by the home agent
- a packet generation unit configured to generate a packet with a home address option including a home address of the mobile terminal set by setting address information of the mobile terminal itself in a source address when it is determined to be a packet; Transmitting means for transmitting the packet to the communication terminal;
- a mobile terminal is provided that. With this configuration, packet loss can be prevented and communication delay can be prevented.
- address information of the mobile terminal is added to the encapsulated packet. With this configuration, it is possible to reduce processing load and traffic associated with transmission of useless BU messages.
- the apparatus when communication with the mobile terminal is completed, the measurement of elapsed time from the end of the communication to the start of new communication is started. It is a preferable aspect of the present invention that the apparatus further includes first message generation means for generating a message including an instruction to do so, and the transmission means transmits the generated message to the communication terminal. With this configuration, it is possible to acquire the elapsed time for determining whether or not the binding cache is valid. As described in the embodiment of the present invention, the first message generation unit and the second message generation unit may be the same unit (component).
- the mobile terminal further includes second message generating means for generating a message including information on an effective time of the binding cache of the mobile terminal of the communication terminal, and the transmitting means Sending a message to the communication terminal is a preferred aspect of the present invention.
- the communication stored in the mobile terminal itself it is a preferable aspect of the present invention to further include processing means for resetting an elapsed time measured from when communication with the terminal is completed until when communication is newly started. With this configuration, new communication can be started.
- the processing means resets the elapsed time corresponding to the address information of each interface. With this configuration, new communication can be started.
- the mobile terminal performs packet communication using a binding cache including address information of the communication terminal via a communication network with a communication terminal that is a communication partner of the mobile terminal, Receiving means for receiving a packet transmitted from a communication terminal; determining means for determining whether the received packet is a packet transmitted via a home agent of the mobile terminal; and Selection means for selecting processing information relating to predetermined processing performed on the binding cache, which is information stored together with the binding cache in a predetermined storage area when it is determined that the packet has passed through a home agent And the binding cache based on the selected processing information. And processing means for performing processing for the Interview, mobile terminal provided is provided. With this configuration, packet loss can be prevented and communication delay can be prevented.
- the mobile terminal performs packet communication using a binding cache including address information of the communication terminal via a communication network with a communication terminal that is a communication partner of the mobile terminal, A determination means for determining whether or not communication with the communication terminal is completed; and when it is determined that communication with the communication terminal is completed, information stored together with the binding cache in a predetermined storage area,
- a mobile terminal comprising selection means for selecting processing information relating to predetermined processing performed on the binding cache, and processing means for performing processing on the binding cache based on the selected processing information.
- the predetermined processing includes the deletion of the binding cache, the suspension of use of the binding cache, and the start of measurement of the elapsed time from when the packet is received to when communication is newly started.
- at least one treatment is a preferred embodiment of the present invention. With this configuration, it is possible to prevent the use of an invalid binding cache.
- the processing information is information included in a message transmitted from the communication terminal in advance. With this configuration, it is possible to determine which process should be performed.
- the mobile terminal performs packet communication using a binding cache including address information of the communication terminal via a communication network with a communication terminal that is a communication partner of the mobile terminal,
- a binding cache including address information of the communication terminal via a communication network with a communication terminal that is a communication partner of the mobile terminal.
- the mobile terminal performs packet communication using a binding cache including address information of the communication terminal via a communication network with a communication terminal that is a communication partner of the mobile terminal,
- a mobile terminal comprising message generation means for generating the message and transmission means for transmitting the generated message to the communication terminal.
- the predetermined processing includes the deletion of the binding cache, the suspension of use of the binding cache, and the start of measurement of the elapsed time from when the packet is received to when communication is newly started.
- at least one treatment is a preferred embodiment of the present invention. With this configuration, it is possible to prevent the use of an invalid binding cache.
- the mobile terminal of the present invention has the above-described configuration, can suppress the occurrence of packet loss, and suppress communication delay. In addition, it is possible to reduce processing load and traffic associated with transmission of useless BU messages.
- the block diagram which shows an example of the structure of the network in the 1st Embodiment of this invention The block diagram which shows an example of a structure of MN which concerns on the 1st Embodiment of this invention
- the flowchart which shows an example of the processing flow in the reception packet processing part of MN which concerns on the 3rd Embodiment of this invention The figure which shows an example of the binding cache of CN which the position information holding part of MN which concerns on the 3rd Embodiment of this invention hold
- the figure which shows an example of the format of BC confirmation message at the time of using BU message in the 3rd Embodiment of this invention The block diagram which shows an example of a structure of CN which concerns on the 3rd Embodiment of this invention
- the flowchart which shows an example of the processing flow in the transmission packet generation part of CN which concerns on the 3rd Embodiment of this invention
- the block diagram which shows an example of a structure of MN which concerns on the 4th Embodiment of this invention
- FIG. 1 is a block diagram showing an example of a network configuration in the first embodiment of the present invention.
- a home network 1 a home network 2, and external networks 11, 12, and 13.
- the MN 10 is managed by the HA 14 of the home network 1, and HoA1 is assigned as a home address. Further, the interface of the MN 10 is connected to the external network 11 and is assigned CoA1.
- the CN 20 is managed by the HA 15 of the home network 2, and HoA 2 is assigned as a home address. Furthermore, the interface of the CN 20 is connected to the external network 12 and is assigned CoA2.
- the HA 14 retains the CoA 1 as a movement destination address for the HoA 1 in association with the MN 10 as a binding cache. Further, the HA 15 holds the CoA 2 in association with the movement destination address for the HoA 2 as a binding cache of the CN 20.
- the home network and HA of the MN 10 and the CN 20 may be the same home network and HA.
- a node that communicates with the MN 10 is referred to as a CN in the sense of a communication partner, but the actual situation in the present invention is a mobile node as with the MN 10. That is, the communication partner for the CN 20 is the MN 10, and the MN 10 can also be called the CN.
- the network configuration shown in FIG. 1 can also be applied to a mobile phone network such as 3GPP (Third Generation Partnership Project).
- the HA function is realized as a function on a network node called a PDN gateway (Packet Data Network Gateway), and the AR function is a reliable network (Trusted Network) such as a serving gateway (Serving Gateway) or WiMAX in the cellular network.
- PDN gateway Packet Data Network Gateway
- AR function is a reliable network (Trusted Network) such as a serving gateway (Serving Gateway) or WiMAX in the cellular network.
- ePDG evolved Packet Data Gateway
- the MN and CN are called UE (User Equipment).
- FIG. 2 is a configuration diagram showing an example of the configuration of the MN in the first embodiment of the present invention.
- the MN 10 includes the components shown in FIG. 2, for example.
- the transmission unit 21 has a function of transmitting a packet to a node on the connected network (external network 11) through the interface 22.
- the receiving unit 23 has a function of receiving a packet from a node on the connected network (external network 11) through the interface 22.
- the location information registration message processing unit 24 performs processing related to the location information registration message received from the communication partner, associates the CoA of the communication partner included in the location information registration message with the HoA, and stores the location information holding unit 25 as a binding cache. To hold. Further, the BC usable period (BC valid period) included in the location information registration message is acquired and stored in the binding cache. If the BC usable period is not included in the location information registration message, the MN 10 itself may generate an appropriate BC usable period.
- FIG. 3 shows an example of the configuration of a location information registration message when a BU message is used.
- a BC usable period 32 is included together with CoA 31 to be registered.
- the BC usable period may be generated on the MN 10 side without being included in this message.
- the elapsed time from the end of communication to the MN 10 after the end of communication with the CN 20 (the elapsed time from the end of communication to the start of new communication) Information (elapsed time timer use request flag 33 after completion of communication) may be added to start measurement of an elapsed time timer (hereinafter also simply referred to as a timer).
- This information may be indicated by including the BC usable period, and when the BC usable period is not included, it is requested to use an elapsed time timer after the end of communication by a flag or the like. You may show that it is doing.
- the location information holding unit 25 holds a binding cache (including information on a BC usable period) registered from a communication partner.
- the reception packet processing unit 26 or the upper layer 28 receives an instruction to start measurement of the elapsed time timer after the end of the communication of the binding cache.
- FIG. 4 shows an example of the binding cache of the CN 20 held by the position information holding unit 25.
- a lifetime 41, an elapsed time timer after communication end, and a BC usable period 43 are managed for CoA2 associated with HoA2.
- the lifetime is the lifetime of BC.
- the BC usable period may be held as the lifetime of the normal binding cache.
- the BC usable period 32 is set in the lifetime field of the BU message.
- a flag or the like may be included in the BU message.
- the transmission packet generation unit 27 generates a packet for transmitting the data passed from the upper layer 28 to the communication partner, and instructs the transmission unit 21 to transmit the packet.
- the transmission packet generation unit 27 searches the position information holding unit 25 to check whether or not a binding cache related to the communication partner exists.
- step S501 it is first determined whether or not a binding cache (BC) relating to the CN 20 of the communication partner exists (step S501). If not, the communication partner HoA is set to the destination address of the packet (step S502), and the transmission unit 21 is instructed to transmit the packet (step S503). On the other hand, if it exists, an elapsed time timer after the end of communication of the binding cache is checked, and it is determined whether or not timer measurement has started (step S504).
- BC binding cache
- the CoA registered in the binding cache is set to the destination address of the packet (step S505), and the transmission unit 21 is instructed to transmit the packet (step S503).
- the CoA registered in the binding cache is set as the destination address of the packet (step S505), and the transmission unit 21 is instructed to transmit the packet (step S503).
- the packet in which CoA is set as the destination address is a packet when route optimization in Mobile IP is used, and therefore includes a routing header including HoA.
- a destination option defined in IPv6 is preferably used as an option including CoA.
- BID may be used instead of CoA.
- the MN 10 may arbitrarily set the BC usable period, and may further notify the CN 20 of the value.
- the BC usable period for the MN 10 is not included in the location information registration message from the CN 20.
- an operator-side entity such as HA or a gateway server (ePDG, PDN gateway) may set the MN 10 and the CN 20.
- the MN 10 may check with the operator entity whether or not to use the BC usable period and the elapsed time timer after the end of communication.
- the BC usable period and the elapsed time timer after the communication are used. You may judge that you should.
- the upper layer 28 represents the entire layer located above the IP layer, and includes the ton transport layer (TCP / UDP) and further upper applications.
- the reception packet processing unit 26 has a function of performing processing related to the packet received by the reception unit 23. Data in the packet processed by the reception packet processing unit 26 is sent to the upper layer 28 or the transmission packet generation unit 27.
- the reception packet processing unit 26 and the upper layer 28 start measuring the elapsed time timer after the end of communication of the binding cache of the CN 20 held in the position information holding unit 25 when the communication with the CN 20 is completed. Instruct. Note that the position information holding unit 25 may start measuring an elapsed time timer after the end of communication when communication with the CN 20 is not performed for a certain period of time.
- packets are transmitted and received for a certain period of time without inquiring of the upper layer 28 and the received packet processing unit 26 whether or not the communication has ended, or without receiving a notification from the upper layer 28 and the received packet processing unit 26. It can be predicted that the communication has ended, and the timer measurement can be efficiently started.
- step S601 When a packet is received from the CN 20, it is first determined whether or not a home address option including the HoA of the CN 20 of the communication partner is added to the received packet (step S601). It is determined that the packet has been transferred, and the binding cache (BC) of CN 20 is deleted (step S602), and reception processing of data included in the packet is performed (step S603).
- BC binding cache
- the CN 20 can prepare for the case where the packet is transmitted again using the route optimization.
- the elapsed time timer after the end of communication is started without deleting the binding cache.
- the timer measures the time during which the packet from the CN 20 is being sent without using route optimization.
- the CN 20 does not need to register location information with the MN 10, and after the location information of the CN 20 exceeds the BC valid period, the MN 10 Can be prevented from using the location information of CN20.
- the timer is reset in step S605, so that the binding cache of the CN 20 held by the MN 10 can be used again. Note that the absence of the home address option means that the packet does not use route optimization.
- step S604 it is determined whether or not the source address of the packet matches the CoA registered in the binding cache. If they match, the elapsed time timer after the end of communication in the binding cache is reset (step S605). As a result, when the MN 10 transmits a packet to the CN 20, since the value of the elapsed time timer after the communication is larger than the BC usable period, the packet is transmitted without using route optimization. When the timer is reset, route optimization using the binding cache can be used again when a packet is transmitted to the CN 20. On the other hand, if they do not match in step S604, it is determined that the packet is from an unregistered CoA, the binding cache is deleted (step S606), and the received packet is discarded (step S607).
- FIG. 7 is a configuration diagram showing an example of the configuration of the CN according to the first embodiment of the present invention.
- the CN 20 includes the components shown in FIG. 7, for example.
- the transmission unit 71 has a function of transmitting a packet to a node on the connected network (external network 12) through the interface 72.
- the receiving unit 73 has a function of receiving a packet from a node on the connected network (external network 12) through the interface 72.
- the registered location information holding unit 74 holds information indicating that the binding cache has been registered with the communication partner (for example, the MN 10).
- the reception packet processing unit 75 or the upper layer 78 receives an instruction to start measurement of the elapsed time timer after the communication of the registered position information.
- the registered location information holding unit 74 may start measuring the elapsed time timer after the end of communication when communication with the MN 10 is not performed for a certain period of time. This makes it possible to send and receive packets for a certain period of time without inquiring of the upper layer 78 and the received packet processing unit 75 as to whether or not the communication has ended, or without receiving notification from the upper layer 78 and the received packet processing unit 75. It can be predicted that communication has ended, and timer measurement can be efficiently started. Further, when the lifetime of the binding cache registered in the MN 10 is about to end, the location information registration message generation unit 76 is instructed to generate a location information registration message for updating the lifetime.
- the location information registration message generation unit 76 receives an instruction from the transmission packet generation unit 77 or the reception packet processing unit 75 and generates a location information registration message for registering the binding cache with respect to the communication partner. Further, the BC usable period for the binding cache to be registered is included in the location information registration message, and the transmission unit 71 is instructed to transmit.
- the BC usable period is a communication state (a small value is set when the communication state is bad, a large value is set when the communication state is good), a connection state (a small value is set when the connection state is bad), and the connection state is good. If the handover frequency is high, set a small value, and if the handover frequency is low, set a large value.)
- Type of communication data real-time data such as audio data and video data, control
- the value may be arbitrarily determined by the CN as the communication partner.
- the value may be arbitrarily determined depending on whether the CNs belong to the same operator.
- the BC usable period held by the MN 10 is preferably longer than the BC usable period held by the CN 20.
- the location information registration message generation unit 76 receives an instruction from the registered location information holding unit 74 and updates the lifetime of the MN 10 when the lifetime of the binding cache registered in the MN 10 is likely to end. A location information registration message is generated.
- the transmission packet generation unit 77 generates a packet for transmitting the data passed from the upper layer 78 or the reception packet processing unit 75 to the communication partner, and instructs the transmission unit 71 to transmit the packet.
- the transmission packet generation unit 77 searches the registered location information holding unit 74 and determines whether or not the binding cache has been registered for the node of the destination address of the packet.
- step S801 When instructed to transmit a packet, it is first determined whether or not a binding cache (BC) is registered for a destination node (step S801). If not registered, the packet to be transmitted is encapsulated to the HA (step S802), and the transmission unit 71 is instructed to transmit the encapsulated packet (step S803). On the other hand, if registered, the elapsed time after completion of communication of the registered position information is checked, and it is determined whether or not timer measurement has started (step S804).
- BC binding cache
- Step S803 If the timer measurement has not started, CoA is set to the source address for the packet, a home address option including HoA is added (step S805), and the transmission unit 71 is instructed to transmit the packet. (Step S803). On the other hand, if the timer measurement has already started, it is determined whether or not the timer is longer than the BC usable period (step S806). If it is larger, it is determined whether it is necessary to reset the elapsed time timer after the end of communication of the binding cache of the CN 20 held by the MN 10 and release the use of the binding cache (step S807). , CoA is set as the transmission source address, a home address option including HoA is added (step S805), and the transmission unit 71 is instructed to transmit the packet (step S803).
- the BC valid period of the MN 10 is longer than the BC valid period held by the CN 20, even if the elapsed time timer after the end of communication of the CN 20 becomes larger than the BC valid period, the elapsed time timer after the end of communication of the MN 10 is still BC. Since it is not longer than the valid period, when the MN 10 receives the packet generated in S805, the elapsed time timer after the end of communication of the binding cache is reset, and the use of route optimization is started.
- step S807 if it is not necessary to reset the elapsed time timer after the end of communication in the binding cache of the CN 20 held by the MN 10 in step S807, the packet to be transmitted is encapsulated to the HA (step S809), and the encapsulated packet is The transmission unit 71 is instructed to transmit (step S803).
- step S806 the elapsed time timer after the end of communication is reset (step S808), CoA is set to the source address for the packet, and a home address option including HoA is added ( In step S805, the transmission unit 71 is instructed to transmit the packet (step S803).
- the elapsed time timer after the end of communication in the binding cache of the MN 10 is reset.
- the received packet processing unit 75 has a function of performing processing related to the packet received by the receiving unit 73.
- Data in the packet processed by the reception packet processing unit 75 is sent to the upper layer 78 or the transmission packet generation unit 77.
- the received packet processing unit 75 and the upper layer 78 measure the elapsed time timer after the end of communication of the location information registered in the MN 10 held in the registered location information holding unit 74 when the communication with the MN 10 is completed. Start it.
- the received packet processing unit 75 when the received packet processing unit 75 receives a packet from the MN 10, the received packet processing unit 75 refers to the registered location information holding unit 74 to determine whether or not the binding cache is registered for the transmission source node of the received packet. If it is determined and not registered, the location information registration message generator 76 is instructed to generate a location information registration message and transmit it to the MN 10.
- a packet is received from the MN 10, it is first determined whether or not the received packet is a packet encapsulated by the HA and transferred (step S901). If it is an encapsulated packet, decapsulation is performed in order to receive it as a packet addressed to HoA (step S902). Then, it is determined whether or not a CoA designation option including CoA is added to the packet after decapsulation (step S903).
- the MN 10 When the CoA designation option is added, the MN 10 has a binding cache, but since the elapsed time timer after completion of communication is larger than a predetermined value (BC usable period), it is directly transmitted to the CoA. It is determined that it has not been performed, and the elapsed time timer after completion of communication of the registered position information is reset (step S904).
- the MN 10 determines that it does not hold the binding cache, and deletes the registered location information (step S905). After deleting the registered location information, it is determined whether there is a packet to be transmitted to the MN 10 (step S906). If there is a packet to be transmitted, the packet when the binding cache is not registered in the MN 10 As a transmission method, it encapsulates to the HA (step S907), and instructs the transmission unit 71 to transmit the packet (step S908).
- a predetermined value BC usable period
- the received packet is not a packet encapsulated by HA but a packet to which a routing header including HoA is added, HoA in the routing header is received in order to receive the packet as addressed to HoA.
- the destination address is set (step S909), and the elapsed time timer after the communication of the registered position information is reset (step S904).
- step S910 After resetting the elapsed time timer after the end of communication, it is determined whether there is a packet to be transmitted to the MN 10 (step S910), and if there is a packet to be transmitted, the binding cache is registered in the MN 10 As a packet transmission method, CoA is set in the transmission source address, a home address option including HoA is added (step S911), and the transmission unit 71 is instructed to transmit the packet (step S908). Note that the transmission method in the case where there is a packet to be transmitted to the transmission source of the received packet has the same result as when the process shown in FIG. 8 is executed.
- the CN 20 receives from the MN 10 a packet encapsulated by the HA and having the CoA designation option added to the internal packet. .
- CoA2 included in the CoA designation option indicates the current destination address of CN20
- CN20 can deliver a packet to be transmitted to MN10 using a path optimized path that does not pass through HA.
- CN20 indicates that CoA2 included in the CoA designation option indicates the current destination address of CN20, it can be determined that MN10 still has a correct binding cache, so a new binding cache is registered. It is determined that there is no need to transmit a location information registration message to the MN 10.
- the CN 20 receives from the MN 10 a packet encapsulated by the HA and includes the CoA designation option in the internal packet. .
- CoA2 included in the CoA designation option does not indicate the current destination address of CN20, CN20 must deliver a packet to be transmitted to MN10 using a path via HA. Further, it is determined that a location information registration message needs to be transmitted to the MN 10 in order to update the location information of the MN 10 with a correct destination address.
- the MN 10 transmits a BU message including a BC usable period as shown in FIG.
- the HA 14 sets the BC usable period in the BU message received from the MN 10 in the binding cache of the MN 10.
- the timer is started. The timer is reset when the MN 10 resumes communication with the CN using the CoA registered in the binding cache again.
- the binding cache is not used as a transfer destination but is put on use.
- the HA 14 uses the other binding cache as the next transfer destination. Select and use.
- the timer of the binding cache also exceeds the BC valid period, the timer elapsed time or the excess time from the BC usable period is selected. If there is no other binding cache, the HA 14 cancels the use suspension of the binding cache, and transfers the received packet to the registered CoA. Thereby, it is possible to select a binding cache that is highly likely to be valid. In addition, instead of packet loss in the HA 14, it is possible to expect the effect of retransmission and buffering by a gateway in the network to which the MN 10 is connected.
- the HA 14 transfers the packet to the HoA without encapsulating. Even when there is no other binding cache of the MN 10, if it is known that the MN 10 is connected to the home network, it may be transferred to the HoA.
- the elapsed time after the communication end of the CN 20 binding cache held by the MN 10 itself is confirmed, Whether or not to use the CoA of the binding cache for a packet to be actually transmitted can be determined based on the size of the elapsed time.
- the CN 20 when the value of the timer is larger than the BC usable period (indicating that a certain time or more has passed since the previous (last) communication), the CN 20 has already moved and its binding It is determined that there is a possibility that the cache is not valid, and the packet to be transmitted is transmitted to the HoA of the CN 20. As a result, even when the CN 20 has already moved and is using a new CoA, since the packet is transferred to the CoA after movement, it is possible to prevent the packet from being lost.
- the MN 10 adds a CoA designation option including the CoA held in the binding cache to the packet 20 to indicate to the CN 20 that the binding cache is still registered, the CN 20 Knows that it still has a valid binding cache, so there is no need to send a location information registration message to register a new binding cache, reducing the processing load and traffic associated with sending the message. The effect that it can be made is acquired.
- the CN 20 sets the BC usable period value notified to the MN 10 to the communication state, connection state, frequency of occurrence of handover, communication data type, interface type (cellular, IEEE802.a / b / g / n, etc.
- the CN 20 sets the BC usable period value notified to the MN 10 to the communication state, connection state, frequency of occurrence of handover, communication data type, interface type (cellular, IEEE802.a / b / g / n, etc.
- FIG. 10 is a configuration diagram illustrating an example of a network configuration according to the second embodiment of the present invention. The difference between FIG. 1 and FIG. 10 is that the CN 20 holds two interfaces. IF1 is connected to the external network 12 and CoA2 is assigned, and IF2 is connected to the external network 13 and CoA3 is assigned.
- the HA 14 holds information associated with the CoA 1 as the destination address for the HoA 1 as a binding cache of the MN 10. Further, the HA 15 holds information in which CoA 2 and CoA 3 are associated as a destination address for the HoA 2 as a binding cache of the CN 20. Note that the home network and HA of the MN 10 and the CN 20 may be the same home network and HA. Further, the CN 20 may be a mobile node like the MN 10.
- FIG. 11 shows an example of the structure of a BU message (position information registration message) when a plurality of CoAs are registered.
- BU usable times 113 and 114 are designated for CoA 111 and 112 to be registered.
- FIG. 12 shows an example of the binding cache of the CN 20 held by the position information holding unit 25. Lifetimes 121 and 124, communication end elapsed time timers 122 and 125, and BC usable periods 123 and 126 are managed for CoA2 and CoA3 associated with HoA2, respectively.
- the location information holding unit 25 holds a binding cache in which a plurality of CoAs are associated with one HoA as the location information of the CN 20.
- the transmission packet generation unit 27 searches the position information holding unit 25 to check whether or not a binding cache related to the communication partner exists.
- step S1301 it is determined whether or not the binding cache (BC) of the communication partner CN 20 exists (step S1301). If there is, a plurality of CoAs are registered therein. Is determined (step S1302). If a plurality of CoAs are registered, the elapsed time timer after the end of communication of each CoA is checked, and it is determined whether or not there is an entry whose timer is smaller than the BC usable period (step S1303).
- BC binding cache
- step S1304 it is determined whether or not there are a plurality of entries (step S1304). If there are a plurality of entries, the entry having the largest difference between the BC usable period and the elapsed time timer after the end of communication is selected ( In step S1305, the CoA of the entry is set as the destination address to generate a packet (step S1306), and the transmission unit 21 is instructed to transmit the packet (step S1307). If there is one such entry, the CoA of that entry is set as the destination address to generate a packet (step S1306), and the transmission unit 21 is instructed to transmit the packet (step S1307).
- the generated packet is a packet in which CoA is set as the destination address and a routing header including HoA is added.
- step S1303 information indicating that the CoA of the binding cache registered (held) is a CoA that has already passed the BC usable period is added to the packet. (Step S1308), the transmission unit 21 is instructed to transmit a packet (Step S1307).
- This information may be CoA or BID, or may be indicated as a flag in the CoA designation option.
- step S1301 If there is no binding cache in step S1301, the HoA of the communication partner CN 20 is set to the destination address of the packet (step S1309), and the transmission unit 21 is instructed to transmit the packet (step S1307). If a plurality of CoAs are not registered in step S1302, the processing after step S504 in FIG. 5 described in the first embodiment is performed.
- the MN 10 can select a CoA that is most likely to correctly indicate the current destination address of the CN 20 among a plurality of registered CoAs of the CN 20 and transmit a packet. .
- the configuration of the CN 20 in the second embodiment of the present invention is the same as that in the first embodiment, and will be described with reference to FIG.
- the difference between the first embodiment and the second embodiment is mainly the processing in the reception packet processing unit 75 and the transmission packet generation unit 77.
- the received packet processing unit 75 has a function of performing processing related to the packet received by the receiving unit 73.
- Data in the packet processed by the reception packet processing unit 75 is sent to the upper layer 78 or the transmission packet generation unit 77.
- the received packet processing unit 75 starts measurement of an elapsed time timer after completion of communication of the location information registered in the MN 10 and held in the registered location information holding unit 74.
- the received packet processing unit 75 receives a packet from the MN 10
- the received packet processing unit 75 refers to the registered location information holding unit 74 to determine whether or not the binding cache is registered for the transmission source node of the received packet. If it is determined and not registered, the location information registration message generator 76 is instructed to generate a location information registration message and transmit it to the MN 10.
- the received packet processing unit 75 performs substantially the same processing as the processing shown in FIG. 9, but since the CoA designation option includes a plurality of CoAs, the elapsed time after the end of communication corresponding to each CoA. Reset the timer.
- a third embodiment of the present invention will also be described with reference to FIG.
- the home network and HA of the MN 10 and the CN 20 may be the same home network and HA.
- a node that communicates with the MN 10 is referred to as a CN in the sense of a communication partner, but the actual situation in the present invention is a mobile node as with the MN 10. That is, the communication partner for the CN 20 is the MN 10, and the MN 10 can also be called the CN.
- FIG. 14 is a configuration diagram showing an example of the configuration of the MN according to the third embodiment of the present invention.
- the MN 10 includes components shown in FIG.
- the transmission unit 1401 has a function of transmitting a packet to a node on the connected network (external network 11) through the interface 1402.
- the receiving unit 1403 has a function of receiving a packet from a node on the connected network (external network 11) through the interface 1402.
- the location information registration message processing unit 1404 performs processing related to the location information registration message received from the communication partner, associates the CoA of the communication partner included in the location information registration message with HoA, and stores the location information holding unit 1405 as a binding cache. To hold. Further, when the location information registration message includes information (BC type information) indicating the handling of the binding cache by the receiving node, the location information registration message is instructed to store the information in the binding cache.
- information BC type information
- Information indicating the handling of the binding cache is information indicating one of (1), (2), and (3) described later.
- the BC valid period BC usable period
- the value of the BC valid period is acquired and stored in the binding cache to be registered with the location information holding unit 1405.
- the MN 10 itself may generate an appropriate BC validity period, or obtain an appropriate value from an arbitrary server. Also good.
- FIG. 15 is an example of the configuration of a location information registration message when a BU message is used.
- a CoA / BID 1501 to be registered BC type information 1502, and a field of BC valid period (BC usable period) 1503 are included.
- the BC valid period is included when the BC type is (3).
- the received packet processing unit 1406 has a function of performing processing related to the packet received by the receiving unit 1403. Data in the packet processed by the reception packet processing unit 1406 is sent to the upper layer 1407 or the transmission packet generation unit 1408.
- step S1601 when a packet is received from the CN 20 (step S1601), it is confirmed whether or not the packet is a packet transmitted using route optimization (step S1602). As a confirmation method, it is confirmed whether or not the home address option is added to the packet, whether or not the transmission source address is the address of the CN 20 and the like. If route optimization is not used, the location information holding unit 1405 is referred to and it is confirmed whether or not the binding cache related to the CN 20 that is the transmission source node of the packet is held (step S1603). If the binding cache is held, the BC type information is confirmed (step S1604), and one of the following (1) to (3) is selected and executed.
- step S1605 When CN 20 receives a packet not using route optimization from CN 20 while holding CN 20's binding cache, CN 20 deletes the binding cache of CN 20 . In this case, the packet transmitted by the MN 10 after the binding cache is deleted is transmitted to the home address instead of the CoA of the CN 20. Further, when the binding cache is deleted, a BC invalidity notification message for notifying that the binding cache registered by the CN 20 has become invalid may be transmitted to the CN 20. In step S1605, the elapsed time after communication end time timer described in the first embodiment of the present invention is referred to, and when the elapsed time after communication end time timer is larger than the BC valid period, it is determined to delete the binding cache. May be.
- step S1606 When a packet not using route optimization is received from CN 20 while holding binding cache of CN 20, binding cache of CN 20 Use of is suspended. In this case, the packet transmitted by the MN 10 after the use of the binding cache is suspended is transmitted to the home address instead of the CoA of the CN 20. Further, the BC confirmation message generation unit 1409 may be instructed to transmit a BC confirmation message for confirming the validity of the binding cache of the CN 20 that is put on hold to the CN 20. If a packet from the CN 20 is transmitted using route optimization while the binding cache is on hold, the hold is canceled and the use of the binding cache is resumed.
- step S1606 when the post-communication elapsed time timer described in the first embodiment of the present invention is referred to and the post-communication elapsed time timer is larger than the BC valid period, the binding cache is put on hold. You may judge.
- step S1607 Start timer (step S1607).
- the elapsed time timer is started after communication is started.
- the process (2) described above is performed, and the use of the binding cache is suspended (step S1608).
- step S1602 If it is determined in step S1602 that the packet is a packet transmitted using route optimization, the binding cache of CN 20 is held (step S1611), and the binding cache is suspended. It is confirmed whether or not (step S1612). If the use is not suspended in step S1612, processing associated with route optimization is performed (step S1613), and then reception processing of data included in the packet is performed (step S1615). On the other hand, if the use is suspended in step S1612, the use suspension of the binding cache is canceled (step S1614), and the packet reception process for route optimization is performed (step S1613), and then included in the packet. Data reception processing is performed (step S1615). If it is determined in step S1603 that the binding cache related to the CN 20 that is the packet transmission source node is not held, reception processing of data included in the packet is performed (step S1615).
- the binding cache may be usable as long as the elapsed time of the timer is smaller than the BC valid period without suspending the use of the binding cache when the timer is started.
- either (2) or (3) described above may be selected and executed, or one of the processes may be performed. You may make it always perform.
- the BC type information included in the location information registration message from the CN 20 is used. Note that (1), (2), and (3) do not have to be used simultaneously as BC type information. For example, when only (1) is used, a flag is added to the location information registration message. If the flag is set, use (1). If it is not set, indicate that the BC is managed in the usual way without using (1). Also good.
- the use of the flag can be similarly notified to the receiving node using the flag.
- CN 20 requests to use the elapsed time timer after starting communication, (3) is selected, and when use of the timer is not requested, (1) or (2) is selected.
- the method may be used. In this case, it can be identified by BC type information when (3-1) is executed in the case of (3) and (1) is executed, and (3-2) is executed in the case of (3) and (2) is executed. You may do it.
- the location information holding unit 1405 holds a binding cache (including BC type information and BC valid period information) registered from a communication partner.
- a binding cache including BC type information and BC valid period information
- the received packet processing unit 1406 instructs to delete the BC or put it on hold
- the binding cache of the corresponding CN is deleted or put on use.
- the timer in the binding cache corresponding to the communication partner is started.
- FIG. 17 shows an example of the CN 20 binding cache held by the location information holding unit 1405.
- a lifetime 1701 an elapsed time after communication start timer 1702, and a BC valid period (BC usable period) 1703 are associated and managed with respect to CoA 2 associated with HoA 2.
- a lifetime 1701 indicates the lifetime of the BC.
- the transmission packet generation unit 1408 receives an instruction from the upper layer 1407 or the reception packet processing unit 1406, generates a packet to be transmitted to the CN 20, and determines whether or not the packet should be transmitted using the binding cache for the packet. To do.
- step S1801 when a packet is transmitted to the CN 20 to start communication with the CN 20, it is confirmed whether or not the binding cache related to the CN 20 that is the transmission destination of the packet is held (step S1801). In this case, the packet is transmitted to the CN 20 without using route optimization. That is, the HoA of CN 20 is set as the destination address (step S1802).
- step S1803 it is checked whether the entry is pending use. If the use is suspended, the packet is transmitted to the CN 20 without using the binding cache. In this case, the destination address is the home address of CN 20 and the source address is the home address of MN 10 (the route optimization is not used). On the other hand, if it is not pending use, using the retained binding cache, the CoA of CN 20 retained in the binding cache is set as the destination address (step S1804), and the routing header including the HoA of CN 20 Is added to the packet and transmitted (using route optimization) (step S1805).
- FIG. 19 shows an example of the format of a BC confirmation message when a BU message is used.
- a type of mobility header 1901 indicating that this message is a BC confirmation message may be used, or in the mobility header 1901, It may be included as a flag in an option including the CoA to be confirmed.
- the BC confirmation message it is desirable to use a message configured with a mobility header of Mobile IPv6. However, any message may be used as long as it can be transmitted to the CN 20. Further, it may be realized as an option (a destination option header or the like) added to a data packet to be transmitted to the CN 20.
- the BC confirmation response message processing unit 1410 performs processing related to the BC confirmation response message received from the CN 20.
- the held BC is deleted.
- a packet transmitted from the MN 10 to the CN 20 thereafter is transmitted via the HA of the CN 20 without using route optimization.
- the holding of the BC is continued, and a packet is transmitted using route optimization for the packet transmitted to the CN 20.
- FIG. 20 is a configuration diagram showing an example of the configuration of the CN 20 in the third embodiment of the present invention.
- the CN 20 includes the components shown in FIG. 20, for example.
- the transmission unit 2001 has a function of transmitting a packet to a node on the connected network (external network 12) through the interface 2002.
- the receiving unit 2003 has a function of receiving a packet from a node on the connected network (external network 12) through the interface 2002.
- the registered location information holding unit 2004 holds information indicating that the binding cache has been registered with the communication partner (for example, the MN 10).
- the timer is started when an instruction to start measurement of the elapsed time timer after the start of communication of the registered location information is received from the received packet processing unit 2005 or the upper layer 2008. That is, when a packet for which route optimization is not used is received from the communication partner, the elapsed time timer after the start of communication is started. Further, when the lifetime of the binding cache registered in the MN 10 is about to end, the location information registration message generation unit 2006 is instructed to generate a location information registration message for updating the lifetime.
- the location information registration message generation unit 2006 receives an instruction from the transmission packet generation unit 2007 or the reception packet processing unit 2005, and generates a location information registration message for registering the binding cache with respect to the communication partner. Further, the location information registration message generation unit 2006 receives an instruction from the registered location information holding unit 2004, and updates the lifetime of the MN 10 when the lifetime of the binding cache registered in the MN 10 is likely to end. A location information registration message is generated.
- BC type information indicating the handling of the binding cache to be registered may be added.
- the BC valid period is included in the location information registration message, and the transmission unit 2001 is instructed to transmit.
- the BC valid period is a communication state (a small value is set when the communication state is bad, a large value is set when the communication state is good), a connection state (a small value is set when the connection state is bad, and a connection state is good) Is set to a large value), the occurrence frequency of handover (a small value is set when the handover frequency is high, a large value is set when the handover frequency is low), the type of communication data (real-time data such as voice data and video data, control messages, etc. It is desirable to set an appropriate value for the CN 20 and the MN 10 according to the interface type (cellular, WiMAX, WLAN). Further, the value may be arbitrarily determined depending on the type of protocol (TCP, UDP, SIP, RTP, etc.). Further, the value may be arbitrarily determined by the CN as the communication partner. For example, the value may be arbitrarily determined depending on whether the CNs belong to the same operator.
- the transmission packet generation unit 2007 generates a packet for transmitting data passed from the upper layer 2008 or the reception packet processing unit 2005 to the communication partner, and instructs the transmission unit 2001 to transmit the packet.
- the transmission packet generation unit 2007 searches the registered position information holding unit 2004 and determines whether or not the binding cache has been registered for the node of the destination address of the packet.
- the BC confirmation message processing unit 2009 performs processing related to the BC confirmation message received from the MN 10, refers to the registered location information holding unit 2004, and determines whether the BC of the CN 20 indicated by the information included in the BC confirmation message is valid. To check. If the corresponding BC is stored in the registered location information, it is determined that the BC is valid, and a BC confirmation response message indicating that the notified BC is still valid is sent to the MN 10.
- the BC confirmation response message generation unit 2010 is instructed to generate and transmit.
- Whether the BC is valid may be determined based on whether the notified CoA of the BC is valid, that is, whether the CoA is assigned to the interface. Thereby, even if the BC is not registered in the MN 10, it is possible to respond to the confirmation request from the MN 10.
- the transmission packet generation unit 2007 When instructing to perform packet transmission, the transmission packet generation unit 2007 generates a packet to be transmitted to the MN 10, and further determines whether route optimization should be used for transmission of the packet. In order to make the determination, first, the registered location information holding unit 2004 is referred to, and it is confirmed whether or not the BC related to the current location information is registered in the MN 10 (step S2101). When the registered location information indicating that it is registered in the MN 10 is held, it is confirmed as which BC type information the binding cache registered in the MN 10 is registered (step S2102).
- step S2103 It is determined whether or not the BC type is (1) or (2) (step S2103). If the BC type is (1) or (2), whether or not the BC of the MN 10 is to be deleted or suspended. Is determined (step S2104).
- the BC type is (1), if the packet is transmitted to the MN 10 without using the route optimization, the MN 10 deletes the binding cache. Therefore, when the binding cache of the MN 10 is not deleted, route optimization is used (step S2105), and the packet is transmitted (step S2106). On the other hand, when deleting the binding cache of the MN 10, the packet is transmitted without using route optimization (step S2107) (step S2106).
- the BC type is (2)
- the MN 10 puts the use of the binding cache on hold. Therefore, if the binding cache of the MN 10 is not to be suspended, the packet is transmitted using route optimization (step S2105) (step S2106). On the other hand, when the binding cache of the MN 10 is put on hold, the packet is transmitted without using route optimization (step S2107) (step S2106).
- step S2103 If it is determined in step S2103 that the BC type is not (1) or (2), it is determined whether the BC type is (3) (step S2108), and the BC type is (3). In this case, the elapsed time after the communication start of the registered position information is checked, and it is determined whether or not the value is larger than the BC valid time (step S2109).
- step S2107 a normal packet is transmitted (step S2106). If the timer value becomes longer than the BC valid time, the registered location information for the MN 10 may be deleted. In this case, the MN 10 that receives the packet also checks the elapsed time timer after the start of communication, and deletes the binding cache related to the CN 20 because the value is longer than the BC valid period.
- a normal packet is a packet whose source address is the CN20 HoA and whose destination address is the MN10 HoA, and whose header address is the CN20 CoA and the destination address is the HA2 address.
- the packet is encapsulated with. This packet is decapsulated by HA2 and transferred to MN10.
- the BC type information notified to the MN 10 is (3-1)
- the MN 10 that has received a packet that is not route optimized from the CN 20 deletes the binding cache, so the CN 20 also deletes the registered location information. To do.
- the BC type information is (3-2)
- the MN 10 that has received a packet that is not route-optimized from the CN 20 puts the binding cache on hold. Therefore, when the CN 20 cancels the binding cache hold, , Send a route-optimized packet.
- the timer when the timer is smaller than the BC valid period, it may be transmitted using route optimization or may be transmitted without being used.
- CoA is set as the source address, and a home address option including HoA is added.
- the packet is transmitted (Step S2106).
- the elapsed time timer after the start of communication in the binding cache of the MN 10 is reset, and the use of route optimization is started.
- the packet is transmitted (step S2106) without using route optimization (step S2106).
- route optimization is used, the packet is a packet with the CoA of the CN 20 as the source address, the HoA of the MN 10 as the destination address, and the home address option including the HoA of the CN 20 added.
- step S2101 if the registered location information indicating that it is registered in the MN 10 is not held, it is encapsulated to the HA (step S2110) and the packet is transmitted (step S2106).
- the CN 20 when the CN 20 is connected to the external network 12 and uses CoA2, the CN 20 starts communication with the MN 10 that has registered the BC of the BC type (3).
- the CN 20 transmits a normal packet to the MN 10 without using route optimization.
- the MN 10 starts the elapsed time timer after the start of communication in order to receive a packet for which route optimization is not used even though it holds the BC related to the CN 20.
- the BC type is (1)
- the packet is transmitted using the CoA registered in the MN 10. Even if possible, it may choose to send the packet without using route optimization. Thereby, since the MN 10 deletes the binding cache at the time of receiving a packet from the CN 20, it is not necessary to transmit a message for deleting the binding cache or a message for updating the binding cache to the MN 10 after handover. Can do.
- the binding cache is not registered with the MN 10, that is, if the CN 20 moves and uses a CoA different from the CoA registered with the MN 10, the new CoA is not registered until the new CoA is registered with the MN 10. Since the used packet cannot be transmitted to the MN 10, the packet is transmitted via the HA. Similarly, when the CN 20 moves to the home network and does not have a CoA, the packet is transmitted via the HA.
- the packet received by the MN 10 from the CN 20 is transmitted without being route-optimized by the MN 10 and the CN 20 in the third embodiment of the present invention even though the MN 10 holds the binding cache of the CN 20.
- the CN20 binding cache is deleted, suspended, or the elapsed time timer after the start of communication is started to prevent packet loss due to the MN 10 using an invalid binding cache. Can do.
- CN 20 when CN 20 notifies the BC type information in the location information registration message, it is possible to instruct MN 10 to perform a process preferable for CN 20, and to cause MN 10 to perform an appropriate process according to the situation of CN 20 Can do. For example, even if the binding cache registered with the MN 10 as the BC type (1) remains after the communication with the MN 10 ends, the CN 20 does not use route optimization when resuming the communication with the MN 10. If the packet is transmitted, the old binding cache is deleted by the MN 10, so that it can be prevented from being misused by the MN 10, and the processing load associated with the use of route optimization can be reduced.
- the CN 20 communicating with the MN 10 is handed over from the external network to the home network, it is requested to delete the binding cache registered in the MN 10. Since it is not necessary to send a message to the MN 10 and the binding cache can be deleted simply by performing normal packet transmission, the processing load associated with message transmission can be reduced.
- the MN 10 transmits a BU message including the BC type as shown in FIG.
- the HA 14 sets the BC type in the BU message received from the MN 10 in the binding cache of the MN 10.
- the HA 14 determines the handling of the binding cache according to the BC type. For example, if the BC type is (1), the HA 14 deletes the binding cache. If the BC type is (2), the HA 14 puts the binding cache on use.
- the timer is started before the binding cache is deleted or put on hold, and the timer value exceeds the BC valid period. Delete or hold. In this case, the timer value is reset when the MN 10 resumes communication with the CN using the CoA registered in the binding cache again. For this reason, when the MN 10 does not communicate for a while and the timer exceeds the BC valid period, the binding cache is not used as a transfer destination but is put on use.
- the HA 14 uses other binding cache as the next transfer destination. Select and use. On the other hand, even if there is another binding cache, if the timer of the binding cache also exceeds the BC valid period, the shorter of the timer elapsed time or the excess time from the BC usable period is selected. If there is no other binding cache, the HA 14 deletes the binding cache or cancels the use suspension, and transfers the received packet to the registered CoA. Thereby, it is possible to select a binding cache that is highly likely to be valid.
- the HA 14 transfers the packet to the HoA without encapsulating. Even when there is no other binding cache of the MN 10, if it is known that the MN 10 is connected to the home network, it may be transferred to the HoA.
- BC which is location information registered from the CN 20 to the MN 10
- communication session, flow
- one of (1), (2), and (3) described in the third embodiment of the present invention is selected and executed.
- (1), (2), and (3) do not need to be used simultaneously as BC type information.
- position information is used.
- a flag is added to the registration message, and if the flag is set, (1) is used, and if it is not set, (1) is not used and BC is managed in a normal manner. You may make it show that it does.
- the use of the flag can be similarly notified to the receiving node.
- CN 20 requests to use an elapsed time timer after starting communication
- (3) is selected, and (1) or (2) is selected when use of the timer is not requested.
- Good it can be identified by BC type information when (3-1) is executed in the case of (3) and (1) is executed, and (3-2) is executed in the case of (3) and (2) is executed. You may do it.
- FIG. 22 is a configuration diagram illustrating an example of the configuration of the MN 10 according to the fourth embodiment of the present invention.
- the MN 10 includes components shown in FIG.
- the transmission unit 2201 has a function of transmitting a packet to a node on the connected network (external network 11) through the interface 2202.
- the receiving unit 2203 has a function of receiving a packet from a node on the connected network (external network 11) through the interface 2202.
- the location information registration message processing unit 2204 acquires the location information included in the location information registration message received from the CN 20 and holds it in the location information holding unit 2205. Further, when BC type information is included, BC type information is also acquired and held. In this case, particularly when (3) is specified, if the value of the BC valid period (BC usable period) is also included, that value is also acquired and held.
- registered location information is different from CN 20.
- the process is triggered by the end of the communication associated with the communication (session).
- communication association information (such as a flag) is included in the position information registration message as information for requesting this processing, the information is acquired and held in the position information holding unit 2205.
- the communication association information may be notified as one of the BC type information in the third embodiment of the present invention.
- the location information registration message processing unit 2204 notifies the communication end determination unit 2206 of information related to the CN 20 in order to detect the end of communication, and when the communication (session) with the CN 20 ends, Is requested to notify the location information registration message processing unit 2204 that the communication (session) has been completed.
- information for specifying communication associated with the registered binding may be included in the location information registration message.
- information for specifying communication is notified to the communication end determination unit 2206 together with information related to the CN 20.
- Information identifying communication includes a session ID indicating a specific session, a flow ID indicating a specific flow, an address (destination address, transmission source address), a port number, a protocol ID, and the like between CN 20 and MN 10.
- Arbitrary information can be used as long as the information can represent a part or the whole of the communication (session, flow). If the flow information has already been registered, only the flow ID indicating the information needs to be included.
- the communication end determination unit 2206 monitors the state of communication with the communication partner, and if the communication with the CN 20 is detected to end, notifies the position information registration message processing unit of the end of communication.
- the location information registration message processing unit that has received the notification of the end of communication refers to the location information holding unit 2205 and deletes the binding cache if the communication association information is held in the binding cache of the CN 20.
- the process may be performed according to the BC type information of the binding cache of the CN 20. If the BC type information is (1), the binding cache of the CN 20 is deleted when notified that the communication with the CN 20 has ended. In this case, as described above, the binding cache type is the same as the case of the communication association information type.
- the BC type information is (2)
- the use of the binding cache of CN 20 is suspended.
- the BC type information is (3)
- an elapsed time timer after the end of communication is started when the communication with the CN 20 ends.
- the processing that is performed by comparing the elapsed time timer after the end of communication with the BC valid period is as follows. Since it is the same as the processing performed by comparing the elapsed time timer after communication end and the BC valid period described in the first and second embodiments, the description is omitted.
- the BC type information is (3)
- the elapsed time timer after the communication is compared with the BC valid period, and the timer value is larger than the BC valid period. If the binding cache is deleted, on the other hand, it may be determined that the binding cache is not deleted.
- the communication end determination unit 2206 makes an inquiry to the upper layer 2207 to check whether the communication has ended, or notifies the upper layer 2207 of the notification.
- packets sent to and received from the CN 20 are monitored, and packets indicating the end of communication of the protocol used by the upper layer 2207 (for example, TCP FIN message, ACK message, SIP BYE message, ACK
- the end of communication may be recognized. It can also be determined that communication with the CN 20 has ended when communication for a certain period of time (the lifetime has expired) has not been performed.
- the location information registration message processing unit 2204 may confirm with the communication end determination unit 2206 or the upper layer 2207 whether communication with the CN 20 of the stored BC has ended. As a result of the confirmation, if it is found that the communication is completed, the processing is performed according to the BC type information of the binding cache of the communication partner. Note that the timing for confirming whether or not the communication has ended is based on the remaining time of the lifetime of the binding cache, the elapsed time since the start of communication with the CN 20, or the occurrence of a handover is imminent. May be judged.
- the above processing may be executed when the designated communication is completed in communication with the CN 20.
- the processing of the communication end determination unit 2206 may be realized by the upper layer 2207, and the upper layer 2207 may notify the position information registration message processing unit 2204 that communication with the CN 20 has ended.
- the upper layer 2207 When the upper layer 2207 receives an inquiry from the position information registration message processing unit 2204 or the communication end determination unit 2206 as to whether or not the communication with the CN 20 has ended, the upper layer 2207 displays the result of whether or not the communication has ended. return. Also, when information related to communication with the CN 20 is received and the communication is completed, the communication is notified.
- the location information holding unit 2205 executes processing upon receiving an instruction from the location information registration message processing unit 2204 to register, hold, or delete the binding cache of the CN 20.
- the MN 10 deletes, holds, or sets an elapsed time timer after the start of the communication. By starting, it is possible to prevent packet loss caused by using a binding cache in which the MN 10 is invalid. Also, even if CN 20 chooses not to use route optimization temporarily by putting the binding cache on hold and deleting the binding cache when the timer value becomes longer than the BC valid period, it is unnecessary. It is possible to prevent the binding cache from being deleted.
- CN 20 when CN 20 notifies the BC type information in the location information registration message, it is possible to instruct MN 10 to perform a process preferable for CN 20, and to cause MN 10 to perform an appropriate process according to the situation of CN 20 Can do.
- the BC type information as (1) in the MN 10
- the binding cache of the CN 20 is deleted by the MN 10, so that it can be prevented from being misused by the MN 10.
- the MN 10 transmits a BU message including communication association information and flow information to the HA 14.
- the HA 14 sets the communication association information in the BU message received from the MN 10 and the flow information in the binding cache of the MN 10.
- the packet addressed to CN received by HA 14 from MN 10 or the packet addressed to MN 10 received from CN matches the communication (session, flow) associated with the binding cache, and the communication has been terminated. If it is detected, the binding cache is deleted.
- the BC type is designated, the handling of the binding cache is determined according to the BC type.
- the HA 14 deletes the binding cache as described above. If the BC type is (2), the HA 14 puts the binding cache on use.
- the BC type is (3-1) or (3-2)
- the timer is started before the binding cache is deleted or put on hold, and the timer value exceeds the BC valid period. Delete or hold.
- the timer value is reset when the MN 10 resumes communication with the CN using the CoA registered in the binding cache again. For this reason, when the MN 10 does not communicate for a while and the timer exceeds the BC valid period, the binding cache is not used as a transfer destination but is put on use.
- the HA 14 uses other binding cache as the next transfer destination. Select and use. On the other hand, even if there is another binding cache, if the timer of the binding cache also exceeds the BC valid period, the shorter one of the timer elapsed time or the excess time from the BC usable period is selected. If there is no other binding cache, the HA 14 deletes the binding cache or cancels the use suspension, and transfers the received packet to the registered CoA. Thereby, it is possible to select a binding cache that is highly likely to be valid.
- the HA 14 transfers the packet to the HoA without encapsulating. Even when there is no other binding cache of the MN 10, if it is known that the MN 10 is connected to the home network, it may be transferred to the HoA.
- each functional block used in the above description of the embodiment of the present invention is typically realized as an LSI (Large Scale Integration) which is an integrated circuit. These may be individually made into one chip, or may be made into one chip so as to include a part or all of them.
- LSI Large Scale Integration
- IC Integrated Circuit
- system LSI super LSI
- ultra LSI ultra LSI depending on the degree of integration.
- the method of circuit integration is not limited to LSI, and may be realized by a dedicated circuit or a general-purpose processor.
- An FPGA Field Programmable Gate Array
- a reconfigurable processor that can reconfigure the connection and setting of circuit cells inside the LSI may be used.
- the mobile terminal according to the present invention can prevent occurrence of packet loss, prevent communication delay, and reduce processing load and traffic associated with transmission of useless BU messages. This is useful for mobile terminals that perform packet communication with communication partners.
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
D.Johnson, C.Perkins, J.Arkko, "Mobility Support in IPv6", RFC3775, June 2004. R.Wakikawa, T.Ernst, K.Nagami, V.Devarapalli "Multiple Care-of Addresses Registration", draft-ietf-monami6-multiplecoa-05.txt, January 2008.
図1は本発明の第1の実施の形態におけるネットワークの構成の一例を示す構成図である。図1には、ホームネットワーク1とホームネットワーク2、及び外部ネットワーク11、12、13があり、MN10はホームネットワーク1のHA14によって管理され、ホームアドレスとしてHoA1が割り当てられている。さらに、MN10のインタフェースは外部ネットワーク11に接続されており、CoA1が割り当てられている。
図10は、本発明の第2の実施の形態におけるネットワークの構成の一例を示す構成図である。図1と図10の違いは、CN20が2つのインタフェースを保持しているという点である。IF1は外部ネットワーク12に接続しCoA2が割り当てられており、IF2は外部ネットワーク13に接続しCoA3が割り当てられている。
本発明の第3の実施の形態においても図1を用いて説明する。なお、MN10及びCN20のホームネットワーク及びHAは、同一のホームネットワーク及びHAであってもよい。また、以下の説明では、MN10と区別するために、MN10と通信を行うノードを通信相手という意味でCNと呼んでいるが、本発明におけるその実態はMN10と同様にモバイルノードである。つまり、CN20にとっての通信相手はMN10となり、MN10をCNと呼ぶこともできる。
本発明の第4の実施の形態は、CN20からMN10へ登録される位置情報であるBCが、CN20とMN10との間で行われる通信(セッション、フロー)と関連付けられており、MN10は、CN20との通信が終了した際に、本発明の第3の実施の形態で述べた(1)、(2)、(3)のいずれかを選択し実行する。なお、第3の実施の形態と同様に、BCタイプ情報として(1)、(2)、(3)が同時に使用される必要はなく、例えば(1)だけを使用する場合には、位置情報登録メッセージの中にフラグを付加し、そのフラグがセットされている場合には(1)を使用し、セットされていない場合には、(1)を使用せずに通常のやり方でBCを管理する、ということを示すようにしてもよい。また(2)だけを使用する場合、あるいは(3)だけを使用する場合などにおいても、同様にフラグを用いて、使用の有無を受信ノードに対して通知することができる。
Claims (18)
- 移動端末の通信相手である通信端末と通信ネットワークを介して、前記通信端末のアドレス情報を含むバインディングキャッシュを利用してパケット通信を行う前記移動端末であって、
前記通信端末との最後の通信が終了してから新たに通信を開始するまでの経過時間を計測する計測手段と、
前記バインディングキャッシュの有効時間の情報を記憶する記憶手段と、
前記通信端末と通信を開始する際、計測された前記経過時間が前記バインディングキャッシュの有効時間を超えているか否かを判断する判断手段と、
前記経過時間が前記バインディングキャッシュの有効時間を超えていると判断された場合、送信するパケットの宛先アドレスに前記通信端末のホームアドレスを設定して前記パケットを生成するパケット生成手段と、
生成された前記パケットを前記通信端末へ送信する送信手段とを、
備える移動端末。 - 前記パケット生成手段は、前記バインディングキャッシュの前記通信端末のアドレス情報を前記パケットに付加する請求項1に記載の移動端末。
- 前記バインディングキャッシュの有効時間の情報を含むメッセージを前記通信端末から受信する受信手段を更に備え、
前記記憶手段は、受信された前記メッセージに含まれる前記バインディングキャッシュの有効時間の情報を取得し記憶する請求項1又は2に記載の移動端末。 - 前記計測手段は、前記通信端末との通信が終了した際に前記経過時間の計測を開始する請求項1に記載の移動端末。
- 移動端末の通信相手である通信端末と通信ネットワークを介して、前記通信端末のアドレス情報を含むバインディングキャッシュを利用してパケット通信を行う前記移動端末であって、
前記通信端末との最後の通信が終了してから新たに通信を開始するまでの経過時間を計測する計測手段と、
前記バインディングキャッシュの有効時間の情報を記憶する記憶手段と、
前記バインディングキャッシュ内に前記通信端末の複数のアドレス情報が含まれる場合、前記通信端末と通信を開始する際、計測された前記経過時間であって、それぞれの前記アドレス情報に対応する前記経過時間が、前記バインディングキャッシュの有効時間を超えているか否かを判断する判断手段と、
それぞれの前記アドレス情報に対応する前記経過時間のすべてが前記バインディングキャッシュの有効時間を超えていると判断された場合に、前記バインディングキャッシュ内の前記通信端末のアドレス情報が既に前記バインディングキャッシュの有効時間を経過しているアドレス情報である旨を含めてパケットを生成するパケット生成手段と、
生成された前記パケットを前記通信端末へ送信する送信手段とを、
備える移動端末。 - 移動端末の通信相手である通信端末と通信ネットワークを介して、前記通信端末のアドレス情報を含むバインディングキャッシュを利用してパケット通信を行う前記移動端末であって、
前記通信端末からのパケットを受信する受信手段と、
受信された前記パケットが前記移動端末のホームエージェントによってカプセル化されたパケットであるか否かを判断する判断手段と、
前記ホームエージェントによってカプセル化されたパケットであると判断された場合、送信元アドレスに前記移動端末自身のアドレス情報を設定し、前記移動端末自身のホームアドレスを含むホームアドレスオプションを付加したパケットを生成するパケット生成手段と、
生成された前記パケットを前記通信端末へ送信する送信手段とを、
備える移動端末。 - 前記カプセル化された前記パケットには、前記移動端末のアドレス情報が付加されている請求項6に記載の移動端末。
- 前記通信端末に対して、前記移動端末との通信が終了した際に、前記通信が終了してから新たに通信を開始するまでの経過時間の計測を開始するべき旨の指示を含むメッセージを生成する第1のメッセージ生成手段を更に備え、
前記送信手段は、生成された前記メッセージを前記通信端末へ送信する請求項6又は7に記載の移動端末。 - 前記通信端末が有する前記移動端末のバインディングキャッシュの有効時間の情報を含むメッセージを生成する第2のメッセージ生成手段を更に備え、
前記送信手段は、生成された前記メッセージを前記通信端末へ送信する請求項6に記載の移動端末。 - 前記受信手段によって受信されたパケットが前記移動端末のホームエージェントによってカプセル化されたパケットであると判断された場合に、
前記移動端末自身に格納された、前記通信端末との通信が終了してから新たに通信が開始されるまでに計測される経過時間をリセットする処理手段を更に備える請求項6に記載の移動端末。 - 前記移動端末自身が複数のインタフェースを有し、前記受信手段によって受信されたパケットが前記移動端末のホームエージェントによってカプセル化されたパケットであると判断された場合、
前記処理手段は、各インタフェースのアドレス情報に対応する前記経過時間をリセットする請求項10に記載の移動端末。 - 移動端末の通信相手である通信端末と通信ネットワークを介して、前記通信端末のアドレス情報を含むバインディングキャッシュを利用してパケット通信を行う前記移動端末であって、
前記通信端末から送信されるパケットを受信する受信手段と、
受信された前記パケットが前記移動端末のホームエージェントを経由して送信されたパケットであるか否かを判断する判断手段と、
前記パケットが前記ホームエージェントを経由したパケットであると判断された場合、所定の記憶領域に前記バインディングキャッシュとともに格納された情報であって、前記バインディングキャッシュに対して行われる所定の処理に関する処理情報を選択する選択手段と、
選択された前記処理情報に基づいて前記バインディングキャッシュに対する処理を行う処理手段とを、
備える移動端末。 - 移動端末の通信相手である通信端末と通信ネットワークを介して、前記通信端末のアドレス情報を含むバインディングキャッシュを利用してパケット通信を行う前記移動端末であって、
前記通信端末との通信が終了したか否かを判断する判断手段と、
前記通信端末との通信が終了したと判断された場合、所定の記憶領域に前記バインディングキャッシュとともに格納された情報であって、前記バインディングキャッシュに対して行われる所定の処理に関する処理情報を選択する選択手段と、
選択された前記処理情報に基づいて前記バインディングキャッシュに対する処理を行う処理手段とを、
備える移動端末。 - 前記所定の処理は、前記バインディングキャシュの削除、前記バインディングキャッシュの使用の保留、前記パケットを受信してから新たに通信を開始するまでの経過時間の計測の開始のうち、少なくとも1つの処理である請求項12又は13に記載の移動端末。
- 前記処理情報は、あらかじめ前記通信端末から送信されたメッセージに含まれている情報である請求12に記載の移動端末。
- 移動端末の通信相手である通信端末と通信ネットワークを介して、前記通信端末のアドレス情報を含むバインディングキャッシュを利用してパケット通信を行う前記移動端末であって、
前記通信端末に前記バインディングキャッシュの登録をさせるためのメッセージを生成する際に、前記移動端末から受信した前記パケットが前記通信端末のホームエージェントを経由したパケットである場合に前記バインディングキャッシュに対して行わせる所定の処理に関する処理情報を含めて前記メッセージを生成するメッセージ生成手段と、
生成された前記メッセージを前記通信端末へ送信する送信手段とを、
備える移動端末。 - 移動端末の通信相手である通信端末と通信ネットワークを介して、前記通信端末のアドレス情報を含むバインディングキャッシュを利用してパケット通信を行う前記移動端末であって、
前記通信端末に前記バインディングキャッシュの登録をさせるためのメッセージを生成する際に、前記移動端末との通信が終了したと判断された場合に前記バインディングキャッシュに対して行わせる所定の処理に関する処理情報を含めて前記メッセージを生成するメッセージ生成手段と、
生成された前記メッセージを前記通信端末へ送信する送信手段とを、
備える移動端末。 - 前記所定の処理は、前記バインディングキャシュの削除、前記バインディングキャッシュの使用の保留、前記パケットを受信してから新たに通信を開始するまでの経過時間の計測の開始のうち、少なくとも1つの処理である請求項16又は17に記載の移動端末。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2010501795A JPWO2009110224A1 (ja) | 2008-03-06 | 2009-03-03 | 移動端末 |
US12/867,131 US20110013602A1 (en) | 2008-03-06 | 2009-03-03 | Mobile terminal |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2008056756 | 2008-03-06 | ||
JP2008-056756 | 2008-03-06 | ||
JP2008194938 | 2008-07-29 | ||
JP2008-194938 | 2008-07-29 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2009110224A1 true WO2009110224A1 (ja) | 2009-09-11 |
Family
ID=41055789
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2009/000953 WO2009110224A1 (ja) | 2008-03-06 | 2009-03-03 | 移動端末 |
Country Status (3)
Country | Link |
---|---|
US (1) | US20110013602A1 (ja) |
JP (1) | JPWO2009110224A1 (ja) |
WO (1) | WO2009110224A1 (ja) |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2006157454A (ja) * | 2004-11-29 | 2006-06-15 | Sharp Corp | 通信装置及びゲートウェイ装置 |
WO2006093288A1 (ja) * | 2005-03-04 | 2006-09-08 | Matsushita Electric Industrial Co., Ltd. | 通信ノード及び通信制御方法 |
-
2009
- 2009-03-03 JP JP2010501795A patent/JPWO2009110224A1/ja not_active Withdrawn
- 2009-03-03 US US12/867,131 patent/US20110013602A1/en not_active Abandoned
- 2009-03-03 WO PCT/JP2009/000953 patent/WO2009110224A1/ja active Application Filing
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2006157454A (ja) * | 2004-11-29 | 2006-06-15 | Sharp Corp | 通信装置及びゲートウェイ装置 |
WO2006093288A1 (ja) * | 2005-03-04 | 2006-09-08 | Matsushita Electric Industrial Co., Ltd. | 通信ノード及び通信制御方法 |
Also Published As
Publication number | Publication date |
---|---|
US20110013602A1 (en) | 2011-01-20 |
JPWO2009110224A1 (ja) | 2011-07-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP5072864B2 (ja) | 通信システム及びドメイン管理装置 | |
US8477685B2 (en) | Enhanced mobility management at a mobile access gateway | |
KR100847167B1 (ko) | 단말기 및 통신 시스템 | |
US8175057B2 (en) | Method and system for fast handovers using dynamic router advertisements | |
WO2009153943A1 (ja) | バインディングキャッシュ生成方法、バインディングキャッシュ生成システム、ホームエージェント及びモバイルノード | |
JP5371987B2 (ja) | 移動端末及びネットワークノード | |
US20070189218A1 (en) | Mpa with mobile ip foreign agent care-of address mode | |
JP4945530B2 (ja) | ホームエージェント、通信システム、及び通信方法 | |
KR101216081B1 (ko) | 이종망 간 핸드오버 시의 ip 주소 재설정 방법 | |
US20100034170A1 (en) | Network Node and Mobile Terminal | |
KR101323016B1 (ko) | 신속한 확립전-단절 매체 독립 핸드오버를 위한 방법 및 장치 | |
JPWO2005067228A1 (ja) | 通信システム及び移動端末並びにアクセスルータ | |
CN114731557A (zh) | 报文传输方法、通信装置和通信系统 | |
JPWO2009054127A1 (ja) | 通信システム及び移動端末並びにネットワークノード | |
KR101533027B1 (ko) | 소프트웨어 정의 네트워크 기반 프록시 모바일 IPv6에서 핸드오버를 지원하는 오픈플로우 컨트롤러 및 그 제어 방법 | |
US8077660B2 (en) | Base station apparatus, access gateway apparatus, communication control system and communication control method | |
WO2009110224A1 (ja) | 移動端末 | |
JP4945529B2 (ja) | 移動端末、通信システム、及び通信方法 | |
JP5685992B2 (ja) | 移動通信システムにおける代理配信サーバおよび通信制御方法 | |
JP2008160665A (ja) | 異種通信インタフェース間の切替方法、移動端末および管理装置 | |
WO2014205832A1 (zh) | 传输数据的方法、边界网关和控制面装置 | |
US8995390B1 (en) | Method and apparatus for increasing the speed of handover in a wireless communications network | |
JP3765491B2 (ja) | ネットワークアーキテクチャ、並びに、ネットワークアーキテクチャを構成するサーバおよびノード | |
KR20170027045A (ko) | 이동통신망에서 핸드오버 동안에 전송 처리량 유지 기법 | |
KR101430245B1 (ko) | 네트워크 기반 이동성 감지 방법 및 이에 대응한 데이터처리 방법 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 09718445 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 12867131 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2010501795 Country of ref document: JP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 09718445 Country of ref document: EP Kind code of ref document: A1 |