WO2008072660A1 - ホームネットワークシステム及び該ホームネットワークシステムに用いられるモビリティアンカー割当て方法 - Google Patents
ホームネットワークシステム及び該ホームネットワークシステムに用いられるモビリティアンカー割当て方法 Download PDFInfo
- Publication number
- WO2008072660A1 WO2008072660A1 PCT/JP2007/073949 JP2007073949W WO2008072660A1 WO 2008072660 A1 WO2008072660 A1 WO 2008072660A1 JP 2007073949 W JP2007073949 W JP 2007073949W WO 2008072660 A1 WO2008072660 A1 WO 2008072660A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- mobile node
- anchor
- communication load
- mobility
- load prediction
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/12—Avoiding congestion; Recovering from congestion
- H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/08—Load balancing or load distribution
- H04W28/088—Load balancing or load distribution among core entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
-
- 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/04—Registration at HLR or HSS [Home Subscriber Server]
-
- 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
-
- 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 home network system and a mobility anchor assignment method used for the home network system, for example, a home network system suitable for use when the cellular phone network is IP (Internet Protocol) and the like.
- the present invention relates to a mobility anchor assignment method used in a home network system.
- FIG. 13 is a schematic view illustrating an environment in which mopile IP is used.
- the care-of address (CoA, Care of Address) assigned to the network interface in the external network to which the mobile node 1 is connected at the move destination and the mobile node 1 belong.
- the home address (Home Address, HoA), which is the address of the home network in which the mobile node 1 is connected
- the home network is the network to which home agent 2 belongs, and mobile agent 1 is located in an external network where mobile node 1 is located.
- the link layer address for the HoA is required on behalf of the same mobile node 1, it responds with its own link layer address.
- Packets addressed to oA are sent to home agent 2 by a general routing process.
- the home agent 2 transmits the source as the home agent 2 address HA-addr and the destination address based on the stored correspondence information between HoA and CoA. Encapsulates with the CoA of mobile node 1 and transfers the packet to the same mobile node 1.
- a packet when a packet is sent from the mobile node 1 to the communication node 3, if the source address does not belong to the existing network address of the mobile node 1, the packet is discarded by the ingress filter. Therefore, a packet whose source address is the HoA of mobile node 1 and whose destination address is the address of correspondent node 3 (CN-addr) is sent, source address is CoA of mobile node 1, and destination address is home. It is forced to be the Agent 2 address (HA_addr) and sent to the Home Agent 2 once. The home agent 2 forwards the packet to the communication node 3 after decapsulating the packet.
- CN-addr correspondent node 3
- the mobile node 1 transmits a registration request for updating the correspondence between the HoA and the CoA each time to the home agent 2.
- the CoA associated with the HoA is updated by the above registration request.
- Patent Document 1 Conventionally, as this type of technology, for example, there is one described in Patent Document 1.
- the mobile node when communication load information is periodically exchanged among a plurality of home agents, and one home agent exceeds a predetermined load, the mobile node receives another load with a smaller load. Load is distributed by sending a registration request to the home agent.
- each home agent device In the home agent device described in Patent Document 2, in the IP network in which a plurality of home agent devices are provided, each home agent device When the load information of BC (binding cache) is measured and one home agent device 1S requests other home agent devices to transfer BC, the requested home agent device power S, BC at the corresponding device at that time Based on the load and the transferred BC load, it is judged whether or not to accept the BC, and the load is distributed based on this judgment result.
- BC binding cache
- the load processing state of the packet processing device is grasped by the packet processing representative device, and the establishment of communication from the mobile or to the mobile is at present. Based on the load status of the! /, The load distribution of the packet processing device is planned, and the system operation efficiency is improved.
- Patent Document 1 Japanese Patent Application Laid-Open No. 2005-027315 (abstract, FIG. 2)
- Patent Document 2 Reclaimed WO 2004-105329 (abstract, FIG. 2)
- Patent Document 3 Japanese Patent Laid-Open No. 2004-207851 (abstract, FIG. 2)
- Patent Documents 1 to 3 are incorporated herein by reference.
- this home agent may already accommodate many mobile nodes. If the communication timing is similar, the communication load of the home agent may be exceeded at the time of actual communication. For this reason, when the mobile node communicates only for a part of a powered-on period, such as a mobile phone, a momentary communication load information such as when the mobile node is powered on. However, there is a problem that it is not possible to assign an appropriate home agent.
- the value obtained by dividing the allowable communication load of the home agent by the maximum communication load per mobile node is estimated as the number of mobile nodes that can be accommodated
- the number of mobile nodes that can be accommodated per home agent is Since the number of home agents is reduced and the number of home agents installed is increased, there is a problem that the hardware configuration of the device, the installation cost and the management cost increase.
- the present invention has been made in view of the above-described circumstances, and is used for a home network system in which the number of mobility anchors is reduced while allocating an appropriate mobility anchor to a mobile node, and for the home network system.
- To provide mobility anchor assignment method is a goal!
- each mobile node registers the correspondence with the care-of address assigned to each mobile node on the foreign network connected at the movement destination, and when each mobile node is connected to the foreign network
- each packet is moved according to the correspondence of each address.
- a home network system is provided having a plurality of mobility anchors for forwarding to a node, and an anchor assignment means for dynamically assigning any one of the plurality of mobility anchors to each mobile node.
- the home network system comprises: mobile node information storage means for storing first communication load prediction data representing communication load prediction values at a plurality of time points of each mobile node; and a plurality of the plurality of mobility anchors. And anchor information storage means for storing second communication load prediction data representing a communication load prediction value at a time point, wherein the anchor allocation means comprises the first communication load prediction data and the second communication load prediction data.
- Third communication load prediction data representing prediction values of communication loads at the plurality of points in time of the mobility anchor when the mobile node is accommodated based on the communication load prediction data of the plurality of mobility anchors; Among them, the third communication load prediction data is less than or equal to the predetermined load upper limit value at all time points, and the maximum value of the second communication load prediction data is the maximum. Select a small mobility anchor assigned to those the mobile node.
- the mobile node information storage means relates to the above-mentioned home network system, wherein the mobile node information storage means corresponds to the first communication load corresponding to the communication tendency of the subscriber of each mobile node.
- the anchor information storage means comprises a subscriber information storage server for storing prediction data
- the anchor information storage means comprises an anchor information storage server for storing the second communication load prediction data
- the anchor allocation means comprises
- the first communication load prediction data is added to each of the second communication load prediction data to obtain the third communication load prediction data
- the plurality of mobility Among the anchors the third communication load prediction data becomes equal to or less than the load upper limit value at all times, and the maximum of the second communication load prediction data
- the home network system is provided that the value selects the smallest mobility anchor is constituted by an anchor allocation server to be allocated to the mobile node.
- the subscriber information storage server relates to the home network system described above, wherein the subscriber information storage server is a member of each mobile node for the first communication load prediction data.
- the anchor information storage server is configured to set an initial value according to the communication tendency of the person and to sequentially update according to the actual communication load history, and the anchor information storage server is configured to set the second communication load.
- a home network system configured to sequentially update predicted data according to an actual communication load history is provided.
- the subscriber information storage server communicates with the subscriber of each mobile node at high frequency.
- a mobile node ID is recorded, and each of the mobility anchors is based on the mobile node ID of the high frequency communication counterpart and an actual communication load history corresponding to the mobile node ID V, a high communication frequency,
- a home network system is provided which is configured to select and accommodate nodes.
- the home network system described above is connected via a plurality of networks, and the anchor allocation unit of each home network system is the home network system.
- the mobility anchor of the home network system is assigned to the mobile node in which the first communication load prediction data is stored in the mobile node information storage means of another home network system
- a home network system configured to access another home network system and refer to the first communication load prediction data corresponding to the mobile node.
- the home network system described above is connected via a plurality of networks, and the anchor allocation unit of each home network system is the same as the home network system.
- the mobility anchor of the home network system is assigned to the mobile node in which the first communication load prediction data is stored in the mobile node information storage means of another home network system
- a home network system configured to access another home network system and reflect the communication performance of the mobile node in the home network system in the first communication load prediction data.
- a mobility anchor assignment method is provided for use in a home network system having an anchor and anchor assignment means for dynamically assigning any one of the plurality of mobility anchors to each mobile node.
- mobile node information storage processing for storing first communication load prediction data representing predicted values of communication loads at a plurality of times of each mobile node, and communication loads at each of the plurality of times of each mobility anchor
- anchor information storing processing for storing second communication load prediction data representing a predicted value of the second communication load prediction data
- the anchor allocation unit is configured to calculate the second communication load prediction data based on the first communication load prediction data and the second communication load prediction data.
- third communication load prediction data representing prediction values of communication loads at the plurality of points in time of the respective mobility anchors when storing the mobile node, and from among the plurality of mobility anchors, the third communication load prediction data is calculated Select the mobility anchor with the smallest third communication load forecast data being less than or equal to the specified upper load limit at all times, and with the smallest maximum value of the second communication load forecast data. Allocated to the mobile node Te.
- a plurality of mobility anchors for forwarding packets addressed to each mobile node to each mobile node, and any one of the plurality of mobility anchors are used for each mobile node.
- a home network system having anchor allocation means for dynamically allocating, wherein: first communication load prediction data representing an estimated value of communication load at each of a plurality of points in time of each mobile node; and a plurality of said plurality of said mobility anchors A second communication load prediction data representing a communication load prediction value at a time point, the communication load prediction value at each of the plurality of time points of the mobility anchor when the mobile node is accommodated; Of the third communication load prediction data among the plurality of time points among the plurality of means for obtaining the communication load prediction data and the plurality of mobility anchors.
- an anchor assignment server functioning as the anchor assignment means is also provided.
- Each mobile node registers the correspondence with the care-of address assigned to each mobile node on the foreign network connected at the movement destination, and when the packet addressed to each mobile node is received, the correspondence between each address
- a home having: a plurality of mobility anchors for transferring the packet to the mobile nodes based on the mobile station; and an anchor assignment unit for dynamically assigning any one of the plurality of mobility anchors to the mobile nodes.
- a network system a second communication load forecast representing a predicted value of communication load at a predetermined time of each of said mobility anchors;
- An anchor information storage unit for storing data is provided, and the anchor allocation unit is configured to calculate the second communication load prediction data out of the plurality of mobility anchors based on the second communication load prediction data.
- the present invention provides a home network system which selects a mobility anchor having a predetermined load limit value or less at any time and assigns it to the mobile node, and a mobility anchor assignment method implemented by this home network system. Further, according to an eleventh aspect of the present invention, there is provided a home address assigned to each of the mobile nodes on the home network to which the plurality of mobile nodes are accommodated and to which each of the accommodated mobile nodes belongs.
- Each mobile node registers the correspondence with the care-of address assigned to each mobile node on the foreign network connected at the movement destination, and when the packet addressed to each mobile node is received, the correspondence between each address
- a home having: a plurality of mobility anchors for transferring the packet to the mobile nodes based on the mobile station; and an anchor assignment unit for dynamically assigning any one of the plurality of mobility anchors to the mobile nodes.
- first communication load prediction data representing a communication load prediction value at a predetermined time of each mobile node
- Mobile node information storage means for storing is provided, and the anchor allocation means is configured to calculate the first communication load prediction data out of the plurality of mobility anchors based on the first communication load prediction data.
- a home network system characterized by assigning to the mobile node and a mobility anchor assignment method implemented by the home network system.
- the first communication load prediction data representing the communication load prediction values at each of a plurality of time points of each mobile node by the anchor allocation means and each of the mobility anchors at the plurality of time points.
- a third communication load prediction representing communication load prediction values at each of the plurality of points in time of the mobility anchor when the mobile node is accommodated based on second communication load prediction data representing the communication load prediction value.
- the third communication load prediction data is equal to or less than a predetermined load upper limit value at all times, and the maximum value of the second communication load prediction data is Since the smallest mobility anchor is selected and assigned to the mobile node, appropriate mobility anchor can be assigned.
- each mobility anchor is allocated based on the third communication load prediction data calculated at each time, mobile nodes of subscribers having different communication time zones are accommodated in each mobility anchor, and it is possible to allocate in the time direction. Because the load is distributed, the number of mobile nodes that can be accommodated in each mobility anchor can be increased, and as a result, the number of mobility anchors can be reduced.
- the subscriber information storage server records the mobile node ID of the high frequency communication partner communicating with the subscriber of the mobile node at high frequency, and the mobility anchor is used to move the high frequency communication partner. Since mobile nodes with high communication frequency are selected and accommodated based on the node ID and the actual communication load history corresponding to the same mobile node ID, communication via multiple mobility anchors is avoided, and communication efficiency is improved. Can improve
- the anchor allocation unit of each home network system can be used in the mobile node in which the first communication load prediction data is stored in the mobile node information storage unit of the home network system other than the home network access system.
- the mobility anchor of the network system is assigned, the first communication load prediction data corresponding to the mobile node is accessed through the network and is accessed to the other home network system. For example, when receiving a roaming service, the same effect as above is obtained.
- the anchor assignment means of each home network system allows the mobile node for which the first communication load prediction data is stored in the mobile node information storage means of the home network system different from the home network system
- the other home network system is accessed through the network, and the communication history of the mobile node in the home network system is reflected in the first communication load prediction data. For example, when receiving roaming service, the same effect as above is obtained.
- FIG. 1 is a schematic view showing an environment in which a home network system according to a first embodiment of the present invention is used.
- FIG. 2 is a view showing an example of a subscriber information table held in a subscriber information storage server 14;
- FIG. 3 is a diagram showing communication load prediction data of each mobile node.
- FIG. 4 A diagram showing initial values of communication load prediction data.
- FIG. 5 is a diagram showing an example of an anchor information table held in the anchor information accumulation server 15.
- FIG. 6 is a diagram showing the result of addition of communication load prediction data shown in FIG. 4 (a) and FIG. 4 (b).
- FIG. 7 is a sequence diagram for explaining the operation of the home network system 10.
- FIG. 8 is a flow chart for explaining a mobility anchor determination procedure in FIG. 7;
- FIG. 9 is a view showing a subscriber information table for implementing a mobility anchor assignment method according to a second embodiment of the present invention.
- FIG. 10 is a flowchart showing a procedure of determining a mobility anchor of the home network system of this example.
- FIG. 11 is a schematic view showing an environment in which a home network system according to a third embodiment of the present invention is used.
- FIG. 12 is a sequence diagram for explaining the operation of the home network system of FIG.
- FIG. 13 is a schematic view illustrating an environment in which a mopile IP is used. Explanation of sign
- Anchor information storage server (Anchor information storage means)
- the first communication load prediction data representing the communication load prediction value for each predetermined time of the mobile node and the second communication load prediction data representing the communication load prediction value for each predetermined time of each mobility anchor is determined based on the above, and among the plurality of mobility anchors, the third communication load prediction data is obtained.
- a home network system which selects a mobility anchor having a communication load prediction data of No. 3 at a predetermined time or less and at which the maximum value of the second communication load prediction data is the smallest and which is allocated to the mobile node Provides a mobility anchor assignment method used for home network system.
- FIG. 1 is a schematic view showing an environment in which a home network system according to a first embodiment of the present invention is used.
- the home network system 10 in this example is connected to the network 20 as shown in the figure. Also, an external network 30 and a communication node 40 are connected to the network 20.
- a plurality of mobility anchors 11 ie, mobility anchors 11a, 11b, 11c, ⁇
- an accessorator al 2 an anchor damage ij, the server 13, and a subscriber Information storage server 14 and anchor information storage server 15 are provided. And they are connected to each other.
- Mobility anchor 11 is an address (ie, home address, Home Address, HoA) in the home network to which mobile node 32 belongs, and the same external network 30 when mobile node 32 has moved to foreign network 30. Holds a correspondence table showing the correspondence with the addresses assigned (ie, Care of Address, Core of Address, CoA), and based on this correspondence table, the packet sent to the HoA of the mobile node 32. On the other hand, the source node encapsulates it as the mobility anchor 11 own address and the destination end as the CoA of the mobile node 32, and transfers them to the mobile node 32.
- the addresses assigned ie, Care of Address, Core of Address, CoA
- the mobility anchor 11 decapsulates the packet sent from the mobile node 32 by encapsulating the CoA of the mobile node 32 and the endpoint of the mobility anchor 11 as the source, and then de-encapsulating the packet. Forward to the final destination of.
- any other mobile station may be used as long as it functions as a mobility management server that provides the above service to a mobile node using the name “mobility anchor”.
- the mobility anchor 11 corresponds to Mobile IPv4 defined in IETF (Internet Engineering Task Force) RFC 3344 or Home Agent (Home Agent, HA) in Mobile IPv6 defined in RFC 3775.
- IETF Internet Engineering Task Force
- HA Home Agent
- the mobility anchor 11 is to the mobile node 32.
- mobility anchor 11 particularly has, in this embodiment, information possessed by the same mobility anchor 11 (the relevant mobility anchor 11 a, l ib, ⁇ ⁇ ⁇ ⁇ ). / / Has a function to send to the subscriber information storage server 14 and anchor information storage server 15!
- a mobile node ID of a mobile node accommodated by the mobility anchor 11 ie, providing a mobility service
- communication load information associated with time information It is fixed.
- the mobility anchor ID of the mobility anchor 11 the address, the upper limit of the allowable load, the communication load information associated with the time, and the movement during accommodation.
- the node's move node ID is assumed.
- the information transmitted to the subscriber information storage server 14 and the anchor information storage server 15 may include part of the above information or other information.
- the mobile node ID may be substituted by the mobile node HoA.
- anchor assignment server 13 When there is a “mobility anchor assignment request” from mobile node 32, anchor assignment server 13 receives a mobile node ID for identifying a mobile node included in this “mobility anchor assignment request”, a subscriber information storage server The communication load of the mobile node 32 is added based on the communication load prediction data for the mobile node 32 stored in 14 and the information on the mobility anchor 11 as an allocation candidate stored in the anchor information storage server 15. Even at all times, the mobile node 32 transmits to the mobile node 32 a “mobility anchor assignment response” which stores the IP address of the mobility anchor which is below the predetermined load limit value and which is predicted to be serviceable.
- the subscriber information storage server 14 holds a subscriber information table in which information of a subscriber who has contracted with a mobility service provider in order to enjoy the mobility service is recorded, and communication load prediction data of each mobile node.
- FIG. 2 is a view showing an example of a subscriber information table held in the subscriber information storage server 14.
- a subscriber ID for uniquely identifying a subscriber a mobile node ID for uniquely identifying a mobile node used by the subscriber, and a mobile node are assigned. It includes HoA, subscriber's rate plan, subscriber's occupation, and subscriber's age information. However, the subscriber information may be added with other information such as gender. In addition, part of the above information may be omitted.
- When assigning a fixed HoA as a HoA to a mobile node record the HoA in the subscriber information table at the time of joining, as well as other information (charge plan, occupation, age) of the subscriber. Can.
- the HoA when the HoA is dynamically assigned, the HoA can be notified from the mobility anchor 11 when the HoA is determined, and can be recorded in the subscriber information table.
- HoA may be an address corresponding to IPv4 or an address corresponding to IPv6. like this
- the anchor assignment server 13 or the like searches the HoA instead of the mobile node ID when acquiring information of a specific mobile node. It can be used as a key.
- FIG. 3 is a diagram showing communication load prediction data of each mobile node.
- the communication load prediction data of each mobile node is a value obtained by predicting how much communication each mobile node will perform at which time of the day, as shown in FIG.
- the communication load information of each mobile node notified from is averaged in a predetermined time unit.
- the communication load is an average data rate in one-hour units, but may be other indicators such as the number of packets, total data size, etc.
- the communication load prediction data is improved in the accuracy of the value indicating the time and the number of communications performed by the subscriber as the subscriber's number of days of subscription elapses.
- the communication load prediction data is calculated by equation (1).
- PLn is the communication load forecast data when the joining date and n days have passed
- Ln is the actual communication loading data of the mobile node of the joining date, the nth day
- the mobility anchor 1 1 It is a value notified from.
- a is a weighting parameter that is greater than or equal to zero and less than one.
- the communication load prediction data PLn and the communication load data Ln are represented as a two-dimensional array of mobile node ID and time. The initial value of the communication load prediction data at the time of joining shall be generated based on the information in the subscriber information table of FIG.
- FIG. 4 is a diagram showing initial values of communication load prediction data.
- the figure (a) shows the initial value of the communication load forecast data (night type) of the mobile node of the subscriber who has selected the communication plan (night gain plan) for which the communication charge is low at night, and the figure (b In), the communication charge during the daytime is low! /, Select the communication plan (daytime plan)! /,
- the initial value of the communication load forecast data (daytime type) of the mobile node of the subscriber is shown I see.
- information ability such as "Fee plan", "Occupation” and "Age” of the subscriber information table, classify the subscriber, and similar categories.
- the initial value of the communication load prediction data of the subscriber may be determined based on the communication load prediction data of the subscriber belonging to Gori.
- FIG. 5 is a diagram showing an example of the anchor information table held in the anchor information storage server 15.
- the anchor information storage server 15 holds the anchor information table shown in FIG. 5 and the mobility anchor communication load prediction data, and based on the information notified from the mobility anchor 11, the above anchor information table. And update the communication load forecast data one by one.
- the mobility anchor ID is used.
- the mobility anchor communication load prediction data is calculated by equation (2).
- PLancn is the communication load forecast data when n days have passed on the mobility anchor installation date force
- Lancn is the actual communication load data of the mobility anchor notified from each mobility anchor.
- ⁇ is a weighting parameter and is “0 or more and less than“.
- communication load prediction data PLancn and communication load data Lancn are represented as a two-dimensional array of mobility anchor ID and time.
- the information storage server 15 also transmits the anchor information table and the information on the mobility anchor communication load prediction data to the anchor allocation server 13 in response to a request from the anchor allocation server 13.
- the number of mobile nodes accommodated in each mobility anchor shown in is, for example, hundreds to thousands.
- the network 20 is a network managed by the Internet or an operator who manages the home network 10, and in any case, is configured as a general IP network.
- the external network 30 is a network connected to the network 20 via the access router b 31 and has a network address different from that of the home network 10. For this reason, the physical network interface of the mobile node 32 connected to the external network 30 is not limited to Dynamic Host Configuration Protocol (DHCP) or An address having the network address of the external network 30 is given by RA (Router Advertisement) of the set router b31 or the like.
- DHCP Dynamic Host Configuration Protocol
- RA Ra (Router Advertisement) of the set router b31 or the like.
- Mobile node 32 has the same function as a general mobile node defined in Mobile IPv4 or Mobile IPv6, and when connecting to external network 30, connecting to another external network, or connecting to home network 10.
- the operation at the time of feedback is also similar to that of a general mobile node.
- the difference between mobile node 32 and a general mobile node is that, when the mobile node 32 is powered on, the anchor allocation server 13 is inquired of a mobility anchor that should make a registration request for correlating CoA and HoA. is there. After this, the mobile node 32 transmits a registration request to the address of the mobility anchor that has been responded from the anchor assignment server 13, and the target mobility anchor accepts it, whereby the mobility for the mobile node 32 is received. The service is started. Note that the “mobility anchor assignment request” to the anchor assignment server 13 may be transmitted at an opportunity other than immediately after the power is turned on.
- access router b 31 detects that the mobile node 32 is connected to the network, such as when the access router b 31 receives an IP address setting request called a DHCP request from the mobile node 32.
- the router b 31 queries the mobility anchor to be assigned to the anchor assignment server 13 on behalf of the mobile node 32, and returns information such as the IP address of the resulting mobility anchor to the mobile node 32.
- the mobility anchor address can be stored. Can be set in the mobile node 32 by a DHCP response. This simplifies the processing of mobile node 32.
- the access router b 31 will perform an operation of acquiring the mobility anchor address of the mobile node 32 on behalf of the access router b 31.
- This is equivalent to Mobile IPv4 'Registration Request' or Mobile IPv6 'Binding Update', so that the access router b31 can also transmit on the mobility anchor a signal requesting the association between HoA and CoA. Also good Yes.
- the access router b 31 does not have to transmit the acquired address of the mobility anchor 11 to the mobile node 32.
- Netlmm Network-based Localized Mobility Management
- the mobile node 32 itself is required to return mobility anchor allocation request or the information of the resulting allocated mobility anchor!
- the mobility anchor assignment method of the embodiment can be applied similarly.
- the “mobility anchor assignment request” transmitted by the mobile node 32 may be in the form of storing information included in the “mobility anchor assignment request” in the “Registration Request” of Mobile IPv4 or the “Binding Update” of Mobile IPv6.
- the “mobility anchor assignment response” transmitted by the anchor assignment server 13 is “mobility anchor assignment in the“ Registration Reply and “Binding A acknowledgment” that is the response of the “Registration Ratio Request and Binding Update”. It may be in the form of storing the information contained in the response.
- the destination to which the mobile node 32 transmits the “mobility anchor assignment request” is the mobility anchor having the above configuration. If it is 11, it will be advantageous from the viewpoint of load distribution which is good.
- Communication node 40 is a general server or terminal having a communication function corresponding to general IPv4, IPv6, or both, and a mobile node having the same function as mobile node 32. It may be In home network 10, mobility anchor 11, access router al 2, anchor assignment server 13, and anchor information storage server 15 are connected in the same link, that is, Ethernet (registered trademark) without passing through a router. It may be connected via one or more routers. Also, for the external network 30, the access router b31 and the mobile node 32 are connected by the same link via a wireless LAN, Ethernet (registered trademark), etc. It may be configured to be connected via a router.
- FIG. 6 is a diagram showing the result of addition of communication load prediction data shown in FIG. 4 (a) and FIG. 4 (b),
- FIG. 7 is a sequence diagram illustrating the operation of the home network system 10
- FIG. 8 is a flowchart illustrating the mobility anchor determination procedure in FIG. The processing contents of the mobility anchor assignment method used for the home network system of this example will be described with reference to these figures.
- the subscriber information storage server 14 displays predicted values of communication load at a plurality of time points (for example, every predetermined time) corresponding to the communication tendency of the mobile node 32 subscriber.
- the communication load prediction data of 1 is stored (mobile node information storage processing), and the second communication load prediction data representing the communication load prediction value for each predetermined time of each mobility anchor 11 is stored by the anchor information storage server 15. Accumulated (Anchor information accumulation processing).
- anchor assignment server 13 transmits the first communication load prediction data and the respective second communication load prediction data.
- the third communication load prediction data is added to obtain the third communication load prediction data, and among the plurality of mobility anchors 11, the third communication load prediction data becomes equal to or less than the load upper limit value at all times, and the second communication load prediction.
- the mobility anchor with the smallest maximum data value is selected and assigned to mobile node 32. That is, when the mobile node 32 is powered on in the foreign network 30 (step A1), the mobile node 32 determines a mobility anchor for registering the association between the HoA and the CoA in the foreign network 30.
- a “mobility anchor assignment request” to send is sent to the anchor assignment server 13 (step A2).
- the anchor assignment server 13 When the anchor assignment server 13 receives the “mobility anchor assignment request” from the mobile node 32, it is stored in the mobile node ID, the subscriber information storage server 14 and the anchor information storage server 15 included in the “mobility anchor assignment request”. Based on the obtained data, the mobility anchor to be assigned to the mobile node 32 is determined (step A3), and the “mobility anchor assignment response” storing the IP address of the determined mobility anchor is transmitted to the same mobile node 32. (Step A4). When the mobile node 32 receives the “mobility anchor assignment and response” from the anchor assignment server 13, the mobile node 32 communicates with the mobility anchor having the mobility anchor address included in it, performs HoA acquisition, and performs security related initialization (step A5). ).
- IKEv2 Internet Key Function version 2, defined in RFC 4306, key data exchange protocol used on the Internet
- RFC 4306 key data exchange protocol used on the Internet
- other protocols may be used.
- the mobile node 32 upon receiving the “mobility anchor assignment response” from the anchor assignment server 13, the mobile node 32 transmits a “registration request” for associating the HoA with the CoA with respect to the address of the mobility anchor included therein. Do it (Step A6).
- the mobility anchor that has received this "registration request” sends a "registration response" to the mobile node 32 indicating acceptance of the "registration request” (but refusing if the registration request is improperly configured, etc.) (step A7).
- the mobile node 32 decides to transmit the “mobility anchor assignment request” upon power on as long as the mobile node 32 is not in communication by itself, the power is continuously turned on. Even if it is medium, "mobility anchor assignment request” may be sent periodically, and the mobility anchor that sends "registration request” may be updated. This "registration request” is periodically transmitted to the mobility anchor based on the conditions for transmission of the registration request defined in the above Mobile IPv4 or Mobile IPv6, in addition to the trigger for transmitting the "registration request". Note that the feature of this embodiment is the procedure of determining the mobility anchor in step A3, and the other procedures may be procedures other than those shown in FIG.
- the access router b31 is a mobility anchor obtained by the mobility anchor determination procedure (step A3) on behalf of the mobile node 32.
- the "registration request” is sent to the ", and the" registration response "is received as the response, but in this case, the mobility anchor determination procedure in step A3 is similar.
- the anchor assignment server 13 communicates with the subscriber information storage server 14, and as shown in FIG. 8, the “mobility anchor assignment request” from the mobile node 32.
- the communication load prediction data corresponding to the mobile node ID included in is acquired (step Bl). For example, in the case of mobile node ID strength MNID_A ′ ′, communication load prediction data PLn [MNID ⁇ A] [time] is obtained using equation (1).
- anchor assignment server 13 receives anchor information Communicate with storage server 15, store the same anchor information
- One of the plurality of pieces of mobility anchor information stored in the product server 15 is acquired (step B2).
- the acquired mobility anchor information is the information shown in the anchor information table of FIG.
- the anchor assignment server 13 also acquires communication load prediction data of the mobility anchor. For example, if the mobility anchor ID is "AncID-A”, get PLancn [AncID-A] [time].
- the anchor information storage server 15 transmits a notification indicating “completion” to the anchor allocation server 13 .
- step B4 communication load prediction data when the mobility anchor corresponding to the mobility anchor information read in step B2 is assigned to the mobile node 32 is calculated by equation (3).
- PL ⁇ anc ′ [time] is communication load prediction data of the mobility anchor at the time (time) when the mobile node 32 is accommodated.
- PL- mn [time] is the communication load prediction data of the mobile node 32 obtained from the subscriber information storage server 14 in step B1 (PLn [MNID_A] [time] in the above example)
- PL- anc [time] is mobility anchor communication load prediction data at time (time) acquired from the anchor information storage server 15 (in the above example, PLancn [AncID_A] [time]).
- the subscriber information storage server 14 Communication load prediction data of each mobile node may be acquired and calculated by summing them. For the latter, more accurate values can be obtained if the mobile node accommodated by the force mobile anchor, which is expensive for communication and calculation, changes frequently.
- the communication load prediction data obtained by equation (3), and the load upper limit of the mobility anchor Whether or not the mobile node 32 can be accommodated is determined by comparing MaxLoad (obtained from the “load upper limit” of the anchor information table in FIG. 5) based on the equation (4) (step B5). Specifically, if the communication load prediction data is data for one hour, formula (4) holds for all when the time is 1 o'clock, 2 o'clock, 2 o'clock, and 2 o'clock. For example, it is determined that the mobile node 32 can be accommodated, otherwise it is determined that the mobile node 32 can not be accommodated. The above time is not limited to 1 o'clock, 2 o'clock, ⁇ ⁇ ⁇ , 24 o'clock.
- step B5 If it is determined in step B5 that the mobile node 32 can be assigned to the mobility anchor, the number of mobility anchors “Capable Anchor Cnt” that can be assigned to the mobile node 32 is counted up (step B6). On the other hand, if it is determined in step B5 that allocation can not be made to the mobility anchor, “Capable Anchor Cnt” is not counted up. Note that “Capable Anchor Cnt” is taleed to "0" at the beginning of the anchor determination procedure.
- the communication load upper limit per mobility anchor is, for example, 5 [Mbps]
- the load is distributed in the time direction, so that ten mobility nodes can be accommodated in one mobility anchor, and the mobility nodes are efficiently accommodated in one mobility anchor.
- the communication load predicted value when the mobile node 32 calculated by equation (3) is assigned to the mobility anchor PL ⁇ an c ′ [time] force
- the identifier of the mobility anchor, and the value determined in step B5 It is recorded in anchor assignment server 13 in association with assignment availability information of the mobility anchor (step B7). Thereafter, the process returns to step B2 and the processes from step B2 to step B7 are repeated until there are no mobility anchors to be evaluated.
- anchor assignment server 13 is the anchor information storage server. If the notification indicating “completion” is received from 15 and the determination as to whether or not all the mobility anchors can be assigned to the mobile node 32 has been completed, the process proceeds to step B8.
- the anchor assignment server 13 determines whether or not there is an assignable mobility anchor by determining whether "Capable Anchor Cnt" is greater than "0" (ie, "1" or more) (step B8). If it is determined in step B8 that there is an assignable mobility anchor, the mobility anchor force S that minimizes the maximum value of the communication load prediction data recorded in step B7 is the mobility anchor as a candidate for assignment to the mobile node 32. Is selected (step B9).
- the selected mobility anchor is assigned in the same manner as in step B9.
- an alarm indicating that the capacity of the mobility anchor is insufficient may be notified to the manager of the mobility anchor by an e-mail format or a method compatible with the system.
- the communication load information of the mobility anchor 11 (11a, l ib,%) At that time is compared. Compared with the method of allocating a mobility anchor with a smaller load, it may not be possible to assign an appropriate mobility anchor even in such a case, the communication load prediction data for each time of the mobile node 32 or mobility anchor 11 is considered. Appropriate allocation of mobility anchors.
- each mobility anchor 11 based on the communication load prediction data calculated for each time, subscriber mobility nodes of different time zones for communication are accommodated in each mobility anchor 11, and in the time direction, As load distribution is realized, the number of mobile nodes that can be accommodated in each mobility anchor 11 can be increased, and as a result, the number of mobility anchors 11 is reduced.
- the communication load prediction data is generated by adding the respective communication load prediction data using two of the subscriber information storage server 14 and the anchor information storage server 15 has been described.
- the subscriber information storage server 14 is not limited, or The communication load prediction data of any of the anchor information storage server 15 may be used.
- communication load prediction data is created based on the information table stored in the anchor information storage server 15. Further, when the anchor information storage server 15 is not arranged, communication load prediction data is created based on the information table stored in the subscriber information storage server 14.
- FIG. 9 is a diagram showing a subscriber information table for implementing the mobility anchor assignment method according to the second embodiment of the present invention.
- the mobility anchor determination procedure is further devised in the case where the correspondent node of the mobile node 32 is also the same mobile node. That is, when the correspondent of the mobile node 32 is a similar mobile node, the communication path is, for example, “mobile node A ⁇ mobility anchor accommodating mobile node A”> mobility anchor accommodating mobile node B ”> Communication efficiency is reduced because the mobility anchor that accommodates each mobile node is passed as in mobile node B ". For this reason, it is more efficient to accommodate mobile nodes with high communication frequency in the same mobility anchor as possible.
- the subscriber information table of the subscriber information storage server 14 includes “friends” (as shown in FIG. 9) for the configuration of FIG. 2 showing the first embodiment.
- High frequency communication partner item is added.
- the mobile node ID (UID-X, UID-Y, ⁇ ⁇ ⁇ ) of the subscriber specified as the other party with whom the subscriber frequently communicates is considered at the time of service subscription etc. It is recorded.
- each mobility anchor 11 selects and accommodates mobile nodes with high communication frequency based on the mobile node ID of the high frequency communication partner and the actual communication load history corresponding to the mobile node ID.
- the high frequency communication partner may be, for example, "family".
- FIG. 10 is a flowchart showing the procedure of determining the mobility anchor of the home network system of this example.
- the mobility network used for the home network system of this example is The processing content of the car assignment method will be described.
- step A3 processing is performed in consideration of the mobile node of the other party whose communication frequency is predicted to be high.
- steps C1 to C8 are processed in the same manner as steps B1 to B8 of FIG. 8 of the first embodiment.
- step C7 in addition to the information on the communication load prediction data recorded in step B7, whether the mobility anchor is the mobility anchor in which the mobile node of the other party of communication set in the item of “friend” is accommodated? A flag indicating whether or not it is also recorded.
- the mobile node ID of the subscriber designated as "friend” is obtained from the subscriber information table of the subscriber information storage server 14, and based on the above flag, this mobile node ID is "accommodated in the anchor information table".
- this mobile node ID is "accommodated in the anchor information table”.
- Step C8 if "Capable Anchor Cnt" is larger than "0", that is, it is determined that there is an assignable mobility anchor, assignment is possible using the information (flag) recorded in Step C7.
- the mobility anchors it is determined whether or not there is a mobility anchor in which the "friend" -designated mobile node is accommodated (step C9).
- the mobility anchor is selected as a mobility anchor to be assigned to the mobile node 32 (step C10). ).
- step C9 when there is no mobility anchor in which the mobile node designated “friend” is accommodated among the assignable mobility anchors ( ⁇ in step C9), the maximum value of the communication load prediction data of each mobility anchor is compared. And the mobility anchor for which it is the smallest is selected as the mobility anchor to assign to mobile node 32, and the mobility anchor determination procedure ends (step Cl l).
- Step C8 when "Capable Anchor Cnt" is "0", that is, when it is determined that there is no assignable mobility anchor (N in Step C8), the mobility anchor is determined. No response to the assignable mobility anchor after Force that can also be transmitted to the road 32
- the mobility anchor is selected in the same way as step C11.
- an alarm indicating that the capacity of the mobility anchor is insufficient may be notified to the manager of the mobility anchor by an e-mail format or a method suitable for the system.
- a log indicating that is left in the anchor assignment server 13 it is good! / ⁇ (step C12).
- a single “friend” in FIG. 9 may be a force S or a plurality of people. Also, if the amount of communication between mobile nodes is recorded using a mobility anchor or the like, and the amount of communication is greater than a predetermined threshold, both of them are regarded as the same as “friend” designation, and the same mobility Good, even if you assign an anchor.
- FIG. 11 is a schematic view showing an environment in which a home network system according to a third embodiment of the present invention is used, and elements common to elements in FIG. 1 showing the first embodiment may be shared. Common symbols are attached.
- a home network system 50 is newly provided and connected to the network 60, as shown in FIG. Also, an external network 70 is connected to the network 60, and the network 60 is connected to the network 20.
- a plurality of mobility anchors 51 ie, mobility anchors 51a, 51b, 51c, ⁇ ⁇ ⁇
- a subscriber information storage server 54 and an anchor information storage server 55 are provided, and an address management server 56 is newly provided, and these are mutually connected.
- Network 60 is, like network 20, the Internet or a home network.
- the external network 70 is a network connected to the network 60 via the access router b71, and is different from the home network 50. I have a dress. Also, in this embodiment, the mobile node 32 in FIG. 1 is moved to and connected to this external network 70.
- second home network system In this home network system (hereinafter, referred to as “second home network system” to distinguish from home network systems 10 and 50), the mobile node 32 is joined by the user of the mobile node 32. It is used when assigning a mobility anchor operated by an operator (or provider etc.) different from the operator (or provider etc.).
- the operator a operates the home network 10
- the network 20 and the external network 30 and the operator b operates the home network system 50, the network 60 and the external network 70.
- the mobility anchor operated by the operator b is assigned.
- the network 20 and the network 60 are connected, communication is possible between the above-mentioned networks operated by the operators a and b.
- anchor allocation server 53 additionally has a function of accessing subscriber information storage servers belonging to different home network systems to determine a mobility anchor to be allocated. It is done. That is, when there is a “mobility anchor assignment request” from the mobile node 32, the anchor assignment server 53 judges the operator (in this case, the operator a) to which the user of the same mobile node 32 subscribes. , The function of communicating with the subscriber information storage server 14 operated by the operator a through the network 60 and the network 20 is further added, and the communication load prediction data of the user is read from the subscriber information storage server 14, It has a function of assigning the mobility anchor 51 belonging to the home network system 50 based on this.
- the “mobility anchor assignment request” from the mobile node 32 includes an operator identifier for determining the operator to which the mobile node 32 has joined.
- the operator identifier is, for example, a domain name such as "operator—a. Sample, net”, but is not limited to this.
- anchor assignment server 53 receives a “mobility anchor assignment request” including an operator identifier from mobile node 32, “subscriber information including the same operator identifier” is received. It has a function of acquiring the IP address of the subscriber information storage server 14 by transmitting the information storage server address request to the address management server 56.
- the subscriber information storage server 14 Even if the IP address is acquired directly in the form of FQDN (Fully Qualified Domain Name) based on the power S, which is determined to acquire the IP address directly, and the domain name and IP address managed by a general DNS (Domain Name System) server.
- FQDN Full Qualified Domain Name
- the anchor allocation server 53 has the acquired IP address of the subscriber information storage server 14 Alternatively, it has a function of associating the FQDN with the mobile node ID of the mobile node 32 and notifying the subscriber information storage server 54.
- subscriber information storage server 54 associates the communication load data of mobile node 32 with time information, accesses a different home network system, and transmits it to subscriber information storage server belonging to the home network system. Functions are added. That is, in addition to the mobility anchor 11, the subscriber information storage server 54 is a subscriber information operated by the operator a through the network 60 and the network 20, with the communication load data of the mobile node notified of the mobility anchor 51, etc. It has a function of transmitting to the accumulation server 14. When acquiring the address of the subscriber information storage server 14 to be the transmission destination, the mobile node ID and the operator identifier of the mobile node 32 sent from the anchor assignment server 53 are used. With this function of the subscriber information storage server 54, even when the user of the mobile node 32 receives roaming service in the network operated by another operator b, the communication load data of the mobile node 32 can be updated. Become.
- Address management server 56 stores the address of subscriber information storage server 14 of operator a permitted to roam, and, in response to the “subscriber information storage server address request” of anchor assignment server 53, the same request is received. Based on the included operator identifier, the IP address of the subscriber information storage server 14 of the network operated by the operator a is returned. In this case, it may be possible to respond in the form of FQDN instead of responding directly to the IP address.
- the home network system 50 is the same as the home network system 50. A home network system of various configurations may be provided.
- FIG. 12 is a sequence diagram for explaining the operation of the home network system of FIG. 11. With reference to this figure, the processing content of the mobility anchor assignment method used for the home network system of this example will be described.
- subscriber information is stored in the subscriber information storage server 14 of the home network system 10 different from the home network system 50 (ie, contracted with an operator who manages the home network system 10) )
- the mobility anchor 51 of the home network system 50 is assigned to the mobile node 32
- the first communication load prediction data corresponding to the mobile node 32 is accessed by accessing the home network system 10 via the networks 60 and 20.
- the communication performance of the mobile node 32 in the home network system 50 is reflected in the first communication load prediction data.
- a "mobility anchor assignment request” is sent to the anchor assignment server 53 (step C2).
- This "mobility anchor assignment request” includes, in addition to the mobile node ID similar to that of the first embodiment, an operator identifier for determining the operator a who has joined the mobile node 32! ! /.
- the anchor assignment server 53 receives the "mobility anchor assignment request" from the mobile node 32, the anchor assignment server 53 sends the "subscriber information storage server address request" including the operator identifier included in the "mobility anchor assignment request” to the address management server 56. Send (step D3).
- address management server 56 When receiving the “subscriber information storage server address request” sent from anchor assignment server 53, address management server 56 records the same address management server 56 with the operator identifier included in the request as a search key. When the correspondence between the registered operator identifier and the address of the subscriber information storage server 14 operated by the operator a corresponding to the operator identifier is searched, and an entry matching the operator identifier to be searched is found
- the anchor assignment server 53 responds to the address of the subscriber information storage server 14 associated with the operator identifier (step D4).
- a subscriber information storage server; a force S that responds to the address of L4; and an F QDN indicating the subscriber information storage server 14 may be transmitted.
- the address management server 56 records the correspondence between the operator identifier and the FQDN of the subscriber information storage server operated by the operator a indicated by the operator identifier.
- the address management server 56 If the address management server 56 does not have an entry matching the operator identifier to be retrieved, the address management server 56 indicates that the anchor assignment server 53 has no matching entry. Make a response. When the anchor assignment server 53 receives the response, the anchor assignment server 53 may notify the mobile node 32 of “impossible of mobility anchor assignment” but may not do anything. In any case, the process ends in step D5.
- the anchor assignment server 53 makes correspondence information between the mobile node ID obtained at the time of receiving the “mobility anchor assignment request” at step D2 and the address of the subscriber information storage server 14 obtained at step D4. , Notify the subscriber information storage server 54.
- the subscriber information accumulation server 54 transmits the communication load information of the mobile node 32 at the roaming time to the subscriber information accumulation server 14 of the operator a as the roaming source, using the correspondence information.
- anchor assignment server 53 uses the information stored in subscriber information storage server 14 and anchor information storage server 55 having the mobile node ID of mobile node 32 and the address of the subscriber information storage server obtained in step D4. Then, determine the mobility anchor to be assigned to the mobile node 32 (step D6).
- the mobility anchor determination procedure of this step D6 is the mobility anchor determination shown in FIG. 8 (embodiment 1) or FIG. 10 (embodiment 2) except that the subscriber information storage server 14 operated by another operator is used. It is similar to the procedure.
- the anchor assignment server 53 acquires the address of the subscriber information storage server 14 from the FQDN using a general DNS mechanism.
- the mobile node 32 After the mobility allocation anchor to be allocated to the mobile node 32 is determined by the anchor allocation server 53 in step D6, the "mobility storing the address of the mobility anchor concerned" The anchor assignment response is transmitted to the mobile node 32 (step D7).
- the mobile node 32 receives the "mobility anchor assignment response" from the anchor assignment server 53, the mobile node 32 and the mobility anchor having the mobility anchor address included therein are Communicate, obtain HoA, and perform security-related initial settings (Step D8)
- IETF standard protocol IKEv2 specified in Internet Key Exchange version 2, RFC 4306) is used. Other protocols may be used.
- the mobile node 32 transmits a "registration request” for associating the HoA with the CoA to the harmed IJ assigned mobility anchor (step D9).
- the mobility anchor that has received this "registration request” sends a "registration response" to the mobile node 32 indicating acceptance of the "registration request” (but refusing if the registration request is improperly configured, etc.) (step D10).
- these "registration request” and “registration response” respectively correspond to "Registration ion Request” and "Registration R mark 1" of Mobile IPv4, and also to Binding Update and Binding Acknowledgment of Mobile IPv6.
- the mobile node 32 can communicate with the communication node 40 using the HoA (step D1 l).
- a power S showing an example of using a subscriber information storage server operated by another operator, as a case where the (second) home network system of this embodiment is effectively used, User power of terminals subscribed to domestic operators It is possible that roaming service may be received in the network of overseas operators affiliated with the domestic operators.
- the mobile node 32 in which subscriber information is stored in the subscriber information storage server 14 of the home network system 10 different from the home network system 50 In the state where the mobility anchor 51 of the home network system 50 is assigned, the same advantages as the first embodiment can be obtained.
- mobility protocol for realizing mobile communication is mopile IPv4 or mopile IPv6, mobility anchors 11 and 51 correspond to HA (Home Agent) and the mobility protocol is Netlmm (Proxy MIPv6).
- the mobility anchors 11 and 51 correspond to the LMA (Local Mobility Anchor), and the access router b (a configuration of the access router a is also conceivable) is mapped to the MAG (Mobility Access Gate). Also, in the case of ProxyMIP (ProxyMIPv4) under consideration in Mobility Protocol Force SIETF, mobility anchors 11 and 51 correspond to HA, and access router b (can be configured as access router a) is MPA (Mobile Proxy Agent) Is associated with In this way, there is a difference in the name of each mobility protocol, and if the node that performs registration processing to the mobility anchor when connected and moved to the network is a terminal power or an access router, there is a difference between the power subscriber and the user subscriber.
- the characteristic elements of the present invention of allocating mobility anchors based on information and communication performance can be applied to any mobility protocol.
- the present invention is effective when applied to the case where the cellular phone network is made IP.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
- Computer And Data Communications (AREA)
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2008549336A JP5120262B2 (ja) | 2006-12-13 | 2007-12-12 | ホームネットワークシステム及び該ホームネットワークシステムに用いられるモビリティアンカー割当て方法 |
CN200780046410.8A CN101601204B (zh) | 2006-12-13 | 2007-12-12 | 归属网络系统及该归属网络系统中使用的移动锚点分配方法 |
US12/518,151 US8238930B2 (en) | 2006-12-13 | 2007-12-12 | Home network system and mobility anchor allocation method used in the home network system |
US13/539,981 US9113363B2 (en) | 2006-12-13 | 2012-07-02 | Home network system and mobility anchor allocation method used in the home network system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2006336058 | 2006-12-13 | ||
JP2006-336058 | 2006-12-13 |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/518,151 A-371-Of-International US8238930B2 (en) | 2006-12-13 | 2007-12-12 | Home network system and mobility anchor allocation method used in the home network system |
US13/539,981 Continuation US9113363B2 (en) | 2006-12-13 | 2012-07-02 | Home network system and mobility anchor allocation method used in the home network system |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2008072660A1 true WO2008072660A1 (ja) | 2008-06-19 |
Family
ID=39511677
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2007/073949 WO2008072660A1 (ja) | 2006-12-13 | 2007-12-12 | ホームネットワークシステム及び該ホームネットワークシステムに用いられるモビリティアンカー割当て方法 |
Country Status (4)
Country | Link |
---|---|
US (2) | US8238930B2 (ja) |
JP (1) | JP5120262B2 (ja) |
CN (1) | CN101601204B (ja) |
WO (1) | WO2008072660A1 (ja) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2012123999A1 (ja) * | 2011-03-15 | 2012-09-20 | 日本電気株式会社 | 移動管理システム、移動管理方法、アクセスgw装置、移動管理制御装置、及びコンピュータ可読媒体 |
JP2015159567A (ja) * | 2010-03-04 | 2015-09-03 | インターデイジタル パテント ホールディングス インコーポレイテッド | インターネットプロトコルマルチメディアサブシステム協調セッションにおける識別および移転のための方法および装置 |
US9602555B2 (en) | 2009-11-10 | 2017-03-21 | Interdigital Patent Holdings, Inc. | Collaborative session control transfer and inter-device transfer in internet protocol multimedia subsystem |
US9674833B2 (en) | 2010-03-18 | 2017-06-06 | Interdigital Patent Holdings, Inc. | Authorizing IUT replication and distinguishing requests for replication from transfers |
Families Citing this family (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2091204A1 (en) | 2008-02-18 | 2009-08-19 | Panasonic Corporation | Home agent discovery upon changing the mobility management scheme |
CN101534501B (zh) * | 2008-03-13 | 2012-06-06 | 华为技术有限公司 | 本地移动锚点注册的方法、系统及设备 |
US8782211B1 (en) * | 2010-12-21 | 2014-07-15 | Juniper Networks, Inc. | Dynamically scheduling tasks to manage system load |
CN102752335B (zh) * | 2011-04-22 | 2017-08-08 | 中兴通讯股份有限公司 | 对等叠加网中节点过负荷信息订阅方法及系统 |
US20130007286A1 (en) * | 2011-06-29 | 2013-01-03 | Juniper Networks, Inc. | User session routing between mobile network gateways |
US8650279B2 (en) | 2011-06-29 | 2014-02-11 | Juniper Networks, Inc. | Mobile gateway having decentralized control plane for anchoring subscriber sessions |
CN103313233B (zh) * | 2012-03-08 | 2017-03-22 | 电信科学技术研究院 | 一种传输网关地址的方法、装置及系统 |
JP6105056B2 (ja) * | 2012-06-11 | 2017-03-29 | インテル コーポレイション | 選択−保持−解放・電子デバイス・ナビゲーション・メニュー・システムのための技術 |
US8817707B2 (en) * | 2012-07-20 | 2014-08-26 | Intel Corporation | Mechanisms for roaming between 3GPP operators and WLAN service providers |
CN103249025B (zh) * | 2013-05-23 | 2016-07-06 | 中国科学院计算机网络信息中心 | 一种PMIPv6环境中LMA动态发现方法 |
KR20150129510A (ko) * | 2014-05-12 | 2015-11-20 | 삼성전자주식회사 | 이동통신 시스템에서 이동성 앵커 선택 방법 및 장치 |
CN105208588A (zh) * | 2014-06-24 | 2015-12-30 | 北京信威通信技术股份有限公司 | 一种更换终端锚基站的方法 |
CN105208586A (zh) * | 2014-06-24 | 2015-12-30 | 北京信威通信技术股份有限公司 | 一种基于锚基站池的锚基站管理方法 |
CN105208587A (zh) * | 2014-06-24 | 2015-12-30 | 北京信威通信技术股份有限公司 | 一种基于锚基站池的锚基站管理系统 |
CN105307198A (zh) * | 2014-06-24 | 2016-02-03 | 北京信威通信技术股份有限公司 | 实现更换终端锚基站的系统及装置 |
JP6597823B2 (ja) * | 2018-03-23 | 2019-10-30 | 日本電気株式会社 | ロードバランシング装置、通信システム、制御方法及びプログラム |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH10105500A (ja) * | 1996-09-09 | 1998-04-24 | Lucent Technol Inc | ネットワーク・サーバの動的再構成 |
JP2004207851A (ja) * | 2002-12-24 | 2004-07-22 | Mitsubishi Electric Corp | パケット処理代表装置使用移動体通信システム |
JP2005027315A (ja) * | 2003-07-01 | 2005-01-27 | Hitachi Ltd | 多数個の分布式回帰エージェントを有するモバイルIPv6ネットワークおよびその多数個の回帰エージェントの負荷バランス方法 |
JP2006228115A (ja) * | 2005-02-21 | 2006-08-31 | Ntt Comware Corp | 負荷分散予測装置及び負荷分散制御方法並びにそのプログラム、負荷分散制御システムおよび当該システムにおける負荷分散制御方法 |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6728536B1 (en) * | 2000-05-02 | 2004-04-27 | Telefonaktiebolaget Lm Ericsson | Method and system for combined transmission of access specific access independent and application specific information over public IP networks between visiting and home networks |
US7260638B2 (en) * | 2000-07-24 | 2007-08-21 | Bluesocket, Inc. | Method and system for enabling seamless roaming in a wireless network |
JP4051064B2 (ja) | 2003-05-19 | 2008-02-20 | 富士通株式会社 | ホームエージェント装置,移動通信システムおよび負荷分散方法 |
CN1894893A (zh) * | 2003-12-16 | 2007-01-10 | 株式会社Ntt都科摩 | 通信系统、通信方法、网络负载预测节点以及网络结构管理节点 |
EP1703712B1 (en) * | 2005-03-08 | 2008-01-23 | Alcatel Lucent | Method and server for a push-to-talk service |
US7590420B1 (en) * | 2006-06-21 | 2009-09-15 | Sprint Communications Company L.P. | Intelligent home agent selection mechanism (IHASM) for dynamic home agent (HA) assignment |
-
2007
- 2007-12-12 JP JP2008549336A patent/JP5120262B2/ja not_active Expired - Fee Related
- 2007-12-12 CN CN200780046410.8A patent/CN101601204B/zh active Active
- 2007-12-12 US US12/518,151 patent/US8238930B2/en active Active
- 2007-12-12 WO PCT/JP2007/073949 patent/WO2008072660A1/ja active Application Filing
-
2012
- 2012-07-02 US US13/539,981 patent/US9113363B2/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH10105500A (ja) * | 1996-09-09 | 1998-04-24 | Lucent Technol Inc | ネットワーク・サーバの動的再構成 |
JP2004207851A (ja) * | 2002-12-24 | 2004-07-22 | Mitsubishi Electric Corp | パケット処理代表装置使用移動体通信システム |
JP2005027315A (ja) * | 2003-07-01 | 2005-01-27 | Hitachi Ltd | 多数個の分布式回帰エージェントを有するモバイルIPv6ネットワークおよびその多数個の回帰エージェントの負荷バランス方法 |
JP2006228115A (ja) * | 2005-02-21 | 2006-08-31 | Ntt Comware Corp | 負荷分散予測装置及び負荷分散制御方法並びにそのプログラム、負荷分散制御システムおよび当該システムにおける負荷分散制御方法 |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9602555B2 (en) | 2009-11-10 | 2017-03-21 | Interdigital Patent Holdings, Inc. | Collaborative session control transfer and inter-device transfer in internet protocol multimedia subsystem |
US9832236B2 (en) | 2009-11-10 | 2017-11-28 | Interdigital Patent Holdings, Inc. | Collaborative session control transfer and inter-device transfer in internet protocol multimedia subsystem |
JP2015159567A (ja) * | 2010-03-04 | 2015-09-03 | インターデイジタル パテント ホールディングス インコーポレイテッド | インターネットプロトコルマルチメディアサブシステム協調セッションにおける識別および移転のための方法および装置 |
US9560147B2 (en) | 2010-03-04 | 2017-01-31 | Interdigital Patent Holdings, Inc. | Method and apparatus for identification and transfer in internet protocol multimedia subsystem collaborative sessions |
US9674833B2 (en) | 2010-03-18 | 2017-06-06 | Interdigital Patent Holdings, Inc. | Authorizing IUT replication and distinguishing requests for replication from transfers |
WO2012123999A1 (ja) * | 2011-03-15 | 2012-09-20 | 日本電気株式会社 | 移動管理システム、移動管理方法、アクセスgw装置、移動管理制御装置、及びコンピュータ可読媒体 |
KR101488312B1 (ko) | 2011-03-15 | 2015-01-30 | 닛본 덴끼 가부시끼가이샤 | 이동 관리 시스템, 이동 관리 방법, 액세스 gw 장치, 이동 관리 제어 장치, 및 컴퓨터 가독 매체 |
US9344874B2 (en) | 2011-03-15 | 2016-05-17 | Nec Corporation | Mobility management system, mobility management method, access GW apparatus, mobility management control apparatus, and computer-readable medium |
US9693218B2 (en) | 2011-03-15 | 2017-06-27 | Nec Corporation | Mobility management system, mobility management method, access GW apparatus, mobility management control apparatus, and computer-readable medium |
Also Published As
Publication number | Publication date |
---|---|
JP5120262B2 (ja) | 2013-01-16 |
US20130170356A1 (en) | 2013-07-04 |
US8238930B2 (en) | 2012-08-07 |
CN101601204A (zh) | 2009-12-09 |
JPWO2008072660A1 (ja) | 2010-04-02 |
US9113363B2 (en) | 2015-08-18 |
US20100008319A1 (en) | 2010-01-14 |
CN101601204B (zh) | 2014-01-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2008072660A1 (ja) | ホームネットワークシステム及び該ホームネットワークシステムに用いられるモビリティアンカー割当て方法 | |
US7436843B2 (en) | Method for access selection | |
CA2514424C (en) | Arrangement for establishing a bidirectional tunnel between a mobile router and a correspondent node | |
US8601127B2 (en) | Method for selective service updates for communication networks | |
US20040246933A1 (en) | Arrangements and method in mobile internet communications systems | |
US20050003822A1 (en) | Method and apparatus for automatically selecting a bearer for a wireless connection | |
US7515590B2 (en) | Mobile communication system and method thereof | |
Choi et al. | Implementation and evaluation of proxy mobile IPv6 in NS-3 network simulator | |
US8849983B2 (en) | Method and system for updating and retrieving state information for mobile nodes in a communication network | |
CN101268670A (zh) | 通过多归属移动节点使得能够同时使用归属网络和外部网络 | |
CN101589601B (zh) | 用于网络间检索用户相关数据的方法和装置 | |
US7366145B2 (en) | Fast recovery from unusable home server | |
CN101310484A (zh) | 分层移动管理系统、接入路由器、锚定节点、移动通信系统和路由设置方法 | |
Andersson et al. | Optimized access network selection in a combined WLAN/LTE environment | |
Zhang et al. | Support mobility in the global internet | |
WO2003067836A2 (en) | Optimization of point-to-point sessions | |
US20090154422A1 (en) | Method of providing seamless qos guarantees in internet protocol (ip) network when ip-based mobility service is provided | |
US7929506B1 (en) | Method of resource management for a mobile node | |
US20120179803A1 (en) | Enhancing network-based ip mobility management protocol to provide multihoming support | |
WO2008069397A1 (en) | Ip handoff method in mobile agent platform environment | |
CN1770780B (zh) | 移动终端管理系统,移动终端,代理,和程序 | |
CN105612774A (zh) | 近距离业务的控制方法、装置及系统 | |
Islam et al. | A novel scheme for PMIPv6 based Wireless Sensor Network | |
Sofia et al. | Mobility estimation in the context of distributed mobility management | |
Kim et al. | On PMIPv6-based Cost-Effective Function-distributed Mobility Management Scheme for Industrial Future Internet |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 200780046410.8 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 07850500 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 12518151 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2008549336 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: 07850500 Country of ref document: EP Kind code of ref document: A1 |