Communication device, communication method, and program
By using area representative routers and SRv6 encapsulation, the scalability issues in LISP-based IP mobility are addressed, improving communication efficiency and reducing routing table sizes and database inquiries for IoT devices.
Patent Information
- Application Number
- JP2023500468
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-02-19
- Publication Date
- 2024-11-13
- Estimated Expiration
- 2041-02-19
AI Technical Summary
LISP-based IP mobility solutions face scalability issues due to the increase in the number of devices, particularly in IoT scenarios like connected cars, leading to excessive routing table sizes and bottlenecks in network communication efficiency.
Implementing area representative routers (ARs) that maintain EID-RLOC correspondence and reduce the need for cloud-side terminal devices to manage extensive routing tables by limiting communication partners to a single AR, using SRv6 encapsulation and reducing database inquiries.
This approach enhances communication efficiency by minimizing routing table sizes and database inquiries, allowing for a larger number of devices to be accommodated without network congestion.
Smart Images

Figure 0007582436000001 
Figure 0007582436000002 
Figure 0007582436000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a communication device, a communication method, and a program. [Background technology]
[0002] The IP mobility function is necessary to connect physically moving devices such as connected cars to the network and continue to provide connectivity. IP mobility is a function that allows device applications to continue communication without being affected even if the device's IP address changes.
[0003] A representative example of a technology that realizes IP mobility is LISP (Locator / ID Separation Protocol) (Non-Patent Document 1). In LISP, an IP address used by an application for communication is defined as an EID (End Point ID), and an IP address used by a device when communicating with an external network is defined as an RLOC (Routing Locator). The RLOC changes when the network to which the device is connected is changed or when an IP address is reassigned as the device moves. In general, the RLOC is an IP address that is assigned when the device connects to a cellular network or Wi-Fi (registered trademark), etc. On the other hand, the EID is always the same value. In LISP, an external database holds the EID-RLOC correspondence, and the correspondence is always kept up to date. A device realizes IP mobility by querying the RLOC using the EID of the application to be communicated as a key, encapsulating an IP packet in the destination RLOC, and transmitting the encapsulated IP packet to the network. [Prior art documents] [Non-patent literature]
[0004] [Non-Patent Document 1] "The Locator / ID Separation Protocol (LISP)", IETF RFC6830, [online],<URL:https: / / tools.ietf.org / html / rfc6830> Summary of the Invention [Problem to be solved by the invention]
[0005] LISP can realize IP mobility between all terminals participating in LISP, but in general IoT (Internet of Things) use cases, such as collecting data from devices such as connected cars and sensors to the cloud, scalability becomes an issue as the number of devices increases. For example, in the case of connected cars, the number of devices can reach millions or tens of millions.
[0006] Specifically, the size of the routing table (number of routes) of the device on the cloud side with which the device communicates becomes an issue.
[0007] The routing table of a device holds information for encapsulating the corresponding RLOC using the EID, which is the destination of communication by the device, as a key. When a certain device communicates with many devices and applications at the same time, the amount of data in the routing table (the number of routes) increases according to the number of EIDs. For example, assuming an application that periodically collects sensor information from moving IoT devices, the IoT device communicates only with the application on the cloud side, but the device on the cloud side (the terminal device equivalent to the device) needs to communicate with a large number of IoT devices. In the case of an application that transmits small amounts of data such as sensor information intermittently, the amount of data in the routing table of the cloud side device (the number of routes) may become a bottleneck before the network bandwidth.
[0008] The present invention has been made in consideration of the above-mentioned points, and has an object to improve the efficiency of communication regarding a communication device whose IP address changes. [Means for solving the problem]
[0009] In order to solve the above problem, a communication device that moves between a plurality of areas and communicates with a predetermined information processing device notifies a corresponding accommodation device, among a plurality of accommodation devices each corresponding to one of the plurality of areas, corresponding to an area to which the communication device belongs, of a first IP address that is changed due to the movement of the communication device and a second IP address that is not changed due to the movement, thereby: A third IP address for each area and a fourth IP address independent of the area. a registration unit that registers, in the accommodating device, information for encapsulating a packet destined for the second IP address from the predetermined information processing device using the first IP address and transmitting the encapsulated packet; a resolution unit that acquires the third IP address corresponding to the fourth IP address specified as a destination of a packet from the communication device and an area to which the communication device belongs from a controller that stores the third IP address for each combination of the fourth IP address and the area; Decapsulating a packet encapsulated by the first IP address into a packet destined for the second IP address. and encapsulating the packet using the third IP address acquired by the resolution unit. A packet processing unit. Effect of the Invention
[0010] This makes it possible to make communications regarding communication devices whose IP addresses change more efficient. [Brief description of the drawings]
[0011] [Figure 1] 1 is a diagram illustrating an example of a configuration of a communication system according to an embodiment of the present invention. [Diagram 2] 1 is a diagram illustrating an example of a hardware configuration of a device 10 according to an embodiment of the present invention. [Diagram 3] FIG. 2 is a diagram illustrating an example of a functional configuration of a CPE 50. [Figure 4] 1 is a diagram illustrating an example of the functional configuration of an area representative router (AR40). [Diagram 5] 1 is a diagram showing an example of the configuration of a routing table 54 of each CPE 50. FIG. [Figure 6] 1 is a diagram showing an example of the configuration of a routing table 43 of an area representative router (AR 40). [Figure 7]FIG. 2 illustrates an example of a functional configuration of a controller 30. [Figure 8] FIG. 2 is a diagram showing an example of the configuration of an EID-RLOC database 33. [Figure 9] 13 is a sequence diagram for explaining the connection of the CPE 50 on the device 10 side to the AR 40 and the registration of the CPE 50 on the cloud side to the controller 30, which are executed prior to communication. [Figure 10] FIG. 11 is a sequence diagram illustrating an example of a processing procedure when a packet is transmitted from a host 60-11 under a CPE 50-11 to a host 60-3 under a CPE 50-31. [Figure 11] FIG. 11 is a sequence diagram for explaining the flow of communication from host 60-3 to host 60-11. [Figure 12] 11 is a flowchart illustrating an example of a processing procedure executed when the area to which the CPE 50-11 belongs changes. [Figure 13] 11 is a flowchart illustrating an example of a processing procedure executed when the area to which the CPE 50-11 belongs changes. [Figure 14] 11A and 11B are diagrams illustrating an example of changes in each routing table when the area to which the CPE 50-11 belongs changes. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0012] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
[0013] [Outline of this embodiment] In this embodiment, the problem is solved by adopting a configuration in which (1) an area representative router (AR40) that accommodates devices 10 that move between multiple areas is installed in each area, and (2) there is a one-to-one correspondence between the terminal device on the cloud side and the area representative router.
[0014] Regarding (1), an area representative router is installed for each physical area (for example, per prefecture), and a moving device 10 connects to the nearest area representative router before communication. The area representative router holds the EID-RLOC correspondence of the devices 10 connected under it as a routing table. Note that an EID (End Point ID) refers to an IP address used by an application for communication in LISP (Locator / ID Separation Protocol), a representative technology for realizing IP mobility, and is independent of the movement of the device 10 (does not change with the movement of the device 10). On the other hand, an RLOC (Routing Locator) refers to an IP address used by a terminal such as the device 10 when communicating with an external network in LISP, and changes with the movement of the device 10.
[0015] (2) reduces the routing table of the cloud-side terminating device. The cloud-side terminating device is implemented in the form of a VM (Virtual Machine) or container using virtualization technology, and multiple terminating devices can be launched within the limits of computing resources. This makes it possible to install one terminating device for one area representative router, and from the perspective of the terminating device, the communication partner is limited to the corresponding area representative router. In other words, only the information of the corresponding one area representative router is registered in the routing table of the cloud-side terminating device. Therefore, the cloud-side terminating device does not need to hold the EID-RLOC correspondence, so there is no need to query the database, and it is expected that the amount of database query processing will be reduced.
[0016] [System Configuration] In this embodiment, the IP address held by the communication destination terminal or application is assumed to be an EID (Endpoint ID), and SRv6 (Segment Routing for IPv6) is used as a means for encapsulating and transmitting IP packets between CPEs (Customer Premises Equipment) that connect (accommodate) each device 10 and cloud base (data center 20) to the core network N1. The core network N1 only needs to be compatible with IPv6. However, the protocol for encapsulation between CPEs is not limited to SRv6, and may be substituted by other means capable of encapsulating IP packets.
[0017] FIG. 1 is a diagram showing a configuration example of a communication system according to an embodiment of the present invention. In FIG. 1, a plurality of devices 10 (device 10-11, device 10-12, device 10-21) and a data center 20 have a CPE 50 and a host 60 as terminating devices, and are connected to a core network N1 via the CPE 50. In the device 10 or the data center 20, the CPE 50 and the host 60 are connected by a LAN in the device 10 or the data center 20. The CPE 50 of each device 10 belongs to any area, and is connected to the AR 40, which is an area representative router that has jurisdiction over that area, via an SRv6 tunnel. In addition, a controller 30 is disposed in a location accessible from the CPE 50 via the core network N1.
[0018] In FIG. 1, character strings indicating the IP address of each device or host 60 are shown in parentheses. A character string beginning with "IP" is the IP address (RLOC) of the CPE 50 or AR 40, and is an address that is reachable via the core network N1. Communications via the core network N1 are encapsulated with this IP address. On the other hand, a character string beginning with "EID" is an IP address assigned to the host 60 or application present in the LAN under the CPE 50. The EID is assigned fixedly and does not change even if the device 10 moves or the network to which it is connected is changed (i.e., it does not depend on the location of the device 10). Applications can always continue to communicate using this EID.
[0019] [Hardware configuration of device 10, etc.] Fig. 2 is a diagram showing an example of a hardware configuration of a device 10 according to an embodiment of the present invention. The device 10 in Fig. 2 includes a drive device 100, an auxiliary storage device 102, a memory device 103, a CPU 104, and an interface device 105, which are all connected to each other via a bus B.
[0020] A program for realizing processing in device 10 is provided by a recording medium 101 such as a CD-ROM. When recording medium 101 storing the program is set in drive device 100, the program is installed from recording medium 101 to auxiliary storage device 102 via drive device 100. However, the program does not necessarily have to be installed from recording medium 101, but may be downloaded from another computer via a network. Auxiliary storage device 102 stores the installed program as well as necessary files, data, and the like.
[0021] When an instruction to start a program is received, the memory device 103 reads out the program from the auxiliary storage device 102 and stores it. The CPU 104 executes functions related to the device 10 in accordance with the program stored in the memory device 103. The interface device 105 is used as an interface for connecting to a network.
[0022] The data center 20, the controller 30, the AR 40, and the like may also have the same hardware configuration as that in FIG.
[0023] [Functional configuration of each device] FIG. 3 is a diagram showing an example of the functional configuration of the CPE 50. The CPE 50 has the same configuration both on the device 10 side (CPE50-11, 12, 21) and on the data center 20 side (CPE50-31, 32). In FIG. 3, the CPE 50 has a forwarding unit 51, an RLOC resolution unit 52, and a CPE registration unit 53. These units are realized by a process in which one or more programs installed in the device 10 or the data center 20 cause the CPU of the device 10 or the data center 20 to execute the program. The CPE 50 also uses a routing table 54. The routing table 54 can be realized, for example, by using a memory device or an auxiliary storage device of the device 10 or the data center 20.
[0024] The forwarding unit 51 encapsulates a packet from the host 60 under its own CPE 50 to the data center 20 and sends it to the core network N1, and when it receives an encapsulated packet from the data center 20 or the like to the host 60 under its own CPE 50 from the core network N1, it decapsulates the packet and delivers the decapsulated packet to the host 60. In this embodiment, since SRv6 is used as the encapsulation protocol, the forwarding unit 51 of the CPE 50 executes SRv6 encapsulation and decapsulation.
[0025] The routing table 54 is a storage unit that holds a route table required when the forwarding unit 51 executes packet forwarding, packet encapsulation, and packet decapsulation. A specific example of the routing table 54 will be described later.
[0026] When the forwarding unit 51 sends out a packet, if the RLOC corresponding to the destination EID is not registered in the routing table 54, the RLOC resolution unit 52 resolves the RLOC corresponding to the destination EID. Specifically, the RLOC resolution unit 52 queries the controller 30 about the RLOC corresponding to the destination EID, and upon obtaining an RLOC in response, registers the destination EID-RLOC correspondence relationship (correspondence information between the destination EID and the RLOC) in the routing table 54.
[0027] When the CPE 50 is started, the CPE registration unit 53 notifies a pre-specified area representative router (AR 40) of the IP address (RLOC) of the CPE 50 itself and the EID under control. The CPE registration unit 53 also receives an area ID from the AR 40 as a response to the notification of the RLOC and EID, and registers information in the routing table 54 to enable reception (decapsulation) of encapsulated packets from the AR 40. The area ID is area identification information.
[0028] Fig. 4 is a diagram showing an example of the functional configuration of an area representative router (AR40). In Fig. 4, the AR40 has a forwarding unit 41 and a CPE connection unit 42. These units are realized by processing in which one or more programs installed in the AR40 are executed by the CPU of the AR40. The AR40 also uses a routing table 43. The routing table 43 can be realized, for example, by using a memory device or auxiliary storage device of the AR40.
[0029] The forwarding unit 41 decapsulates a packet from the data center 20, searches the routing table 43 using the destination EID (EID under the destination CPE 50) of the original IP packet as a key, and obtains the RLOC of the CPE 50 corresponding to the destination EID. After that, the forwarding unit 41 reencapsulates the original packet with the RLOC, and transmits the reencapsulated packet to the destination CPE 50. Note that the AR 40 does not need to be involved in communication in the direction from the CPE 50 on the device 10 side to the CPE 50 on the cloud side, but may play a role of forwarding an IPv6 packet encapsulated in SRv6 or the like as a normal router. In this case, the forwarding unit 41 has a standard IPv6 forwarding function.
[0030] When the CPE connection unit 42 receives a connection request from the CPE 50, it executes a process for connecting the CPE 50. Specifically, the CPE connection unit 42 receives the IP address (RLOC) and EID of the CPE 50 included in the connection request from the CPE 50, and registers, in the routing table 43 of its own AR 40, route information for encapsulating and sending the EID of the CPE 50 in the corresponding RLOC. Thereafter, the CPE connection unit 42 notifies the CPE 50 of the area ID of the area under the jurisdiction of its own AR 40 as a connection response. This enables the forwarding unit 41 to deliver the packet transmitted from the cloud side to the destination CPE 50.
[0031] The routing table 43 is a storage unit that holds a route table required when the forwarding unit 41 forwards, encapsulates, and decapsulates a packet. A specific example of the routing table 43 will be described later.
[0032] Fig. 5 is a diagram showing an example of the configuration of the routing table 54 of each CPE 50. Fig. 5 shows a specific example of the routing table 54 in the case of the network configuration example of Fig. 1.
[0033] The routing table 54 of the CPE 50 is composed of destination addresses (destination prefixes) and corresponding processing contents. The forwarding unit 51 searches the routing table 54 using the destination address of the received IP packet as a key, and performs the processing described in the record. A specific description will be given based on an example of the routing table 54-11 of the CPE 50-11.
[0034] The record "Destination=EID#3, Processing=Encap(IP#31)" is used when CPE50-11 on the device 10 side communicates with CPE50-31 (RLOC:IP#31) on the cloud side. "EID#3" in the destination column is an address used by the host 60 or application on the cloud side, and if the destination address of the packet received by CPE50-11 corresponds to this, the forwarding unit 51 executes the processing of "Encap(IP#31)". "Encap(IP#31)" indicates that the destination IP address is IP#31, and the packet is encapsulated with SRv6 and sent. In other words, the forwarding unit 51 encapsulates the packet received by CPE50-11 from the host 60 under its control with IP#31, which is the RLOC of CPE50-31 that has reachability within the core network N1, and sends it out. The routing table 54 of the CPE 50 on the device 10 side holds such a record for each cloud-side host 60 with which the device 10 communicates.
[0035] The record "Destination = IP#11, Processing = Decap->Lookup" indicates that if the destination IP address is "IP#11", the packet is decapsulated (Decap) and the routing table 54-11 is searched again (Lookup). Since IP#11 is the IP address (RLOC) of CPE 50-11, this record indicates the processing of "decapsulating the (encapsulated) packet addressed to itself and searching the routing table 54-11 again."
[0036] The record "Destination = EID#11, Processing = Direct" indicates that if the destination address of the IP packet is "EID#11", it will be delivered directly. Direct delivery means that the destination address is within the same LAN and the IP packet will be sent directly to the destination. This record is intended to enable direct delivery if the destination is host 60 under its own control when the routing table 54-11 is searched again as a result of the above "Destination = IP#11, Processing = Decap->Lookup".
[0037] The routing table 54-21 of CPE50-21 is almost the same as the routing table 54-11 of CPE50-11, but since CPE50-21 belongs to Area 2, the corresponding CPE50 on the cloud side is CPE50-32. Therefore, the processing of the first record is "Encap (IP#32)". In addition, since the RLOC of CPE50-21 is IP#21 and the subordinate EID is EID#21, the "destination" of the third and fourth records of the routing table 54-21 is different from that of the routing table 54-11 of CPE50-11.
[0038] The CPE 50-31 and the CPE 50-32 are the cloud-side CPEs 50. The routing tables 54 of these CPEs 50-31 and 50-32 are basically the same as those of the CPE 50 on the device 10 side.
[0039] The first record in the routing table 54-31 of CPE50-31, "Destination=Default, Processing=Encap(IP#A1)", indicates that packets that do not match the destinations of other records are encapsulated and sent to IP#A1, i.e., the area representative router AR40-1. In this embodiment, the cloud side has a corresponding CPE50 for each area, and all packets from the cloud side CPE50 to the CPE50 on the device 10 side are sent to the area representative router (AR40-1 in this case) of the area that the cloud side CPE50 corresponds to. This record fulfills this role, and this one record alone can handle all communications from the cloud side to the device 10 side. The first record in the routing table 54-32 of CPE50-32 is similar, but the processing is "Encap(IP#A2)" because CPE50-32 sends to the area representative router AR40-2 corresponding to area 2.
[0040] The second and third records in the routing table 54 of CPE50-31 or CPE50-32 are records for processing packets from the device 10 side to the cloud side, and indicate that if the destination is itself, the packet is decapsulated (record "Destination = IP#31, Processing = Decap->Lookup") and delivered directly to the destination host 60 ("Destination = EID#3, Processing = Direct").
[0041] 6 is a diagram showing an example of the configuration of the routing table 43 of the area representative router (AR 40). A specific description will be given by taking the routing table 43-1 of the AR 40-1 as an example.
[0042] The “Destination = IP#A1, Processing = Decap->Lookup” in the first record (line (1)) indicates that when a packet addressed to itself (addressed to IP#A1) is received from CPE50 on the cloud side, it is decapsulated and the routing table 43 is searched again.
[0043] The second record's "Destination = EID#11, Processing = Encap (IP#11)" indicates that if the destination is EID#11, i.e., an EID under CPE50-11, the packet is encapsulated in IP#11, which is the RLOC of CPE50-11, and sent out. Similarly, the third record indicates that a packet addressed to an EID (IP#12) under CPE50-12 is encapsulated in IP#12, which is the RLOC of CPE50-12, and sent out. These processes (processing of row (2)) are performed on packets decapsulated as a result of processing the first record (row (2)). The same applies to the routing table 43-2 of AR40-2.
[0044] Fig. 7 is a diagram showing an example of the functional configuration of the controller 30. In Fig. 7, the controller 30 has a CPE inquiry unit 31 and a CPE registration / update unit 32. These units are realized by processing in which one or more programs installed in the controller 30 are executed by the CPU of the controller 30. The controller 30 also uses an EID-RLOC database 33. The EID-RLOC database 33 can be realized by using, for example, a memory device or an auxiliary storage device of the controller 30.
[0045] The EID-RLOC database 33 is a storage unit that stores the correspondence between the EIDs assigned under the CPE 50 and the RLOCs currently assigned to the CPE 50. In this embodiment, only the correspondence between the EIDs and the RLOCs of the cloud side CPE 50 is registered in the EID-RLOC database 33. The configuration of the EID-RLOC database 33 will be described later.
[0046] In response to a query for an RLOC corresponding to an EID from CPE 50, CPE inquiry unit 31 searches EID-RLOC database 33 and returns an RLOC corresponding to the EID. An area ID is registered in each entry of EID-RLOC database 33, and CPE inquiry unit 31 returns an RLOC of the area to which CPE 50, the source of the query, belongs.
[0047] The CPE registration and update unit 32 executes new registration and update of the EID-RLOC correspondence relationship registered in the EID-RLOC database 33. Specifically, when the CPE 50 is newly connected to the network, the CPE registration and update unit 32 adds a new record to the EID-RLOC database 33, and when the CPE 50 moves and the RLOC changes, the CPE registration and update unit 32 changes the existing EID-RLOC correspondence relationship.
[0048] FIG. 8 is a diagram showing an example of the configuration of the EID-RLOC database 33. The EID-RLOC database 33 holds the area ID of the area to which each CPE 50 belongs (corresponding to each CPE 50) in addition to the correspondence between the EID and the RLOC of each CPE 50. In other words, the EID-RLOC database 33 stores the RLOC for each combination of the EID and the area ID of each CPE 50. FIG. 8 shows an example of the EID-RLOC database 33 corresponding to FIG. 1. As described above, in this embodiment, the EID-RLOC database 33 holds only the information of the CPE 50 on the cloud side, so that the EID-RLOC database 33 in FIG. 8 holds only the information of CPE 50-31 (first record) and the information of CPE 50-32 (second record). The EID-RLOC correspondence of the CPEs 50 (CPEs 50-11, 50-12, and 50-21 in FIG. 1) on the device 10 side is held in the routing table 43 (FIG. 6) of the area representative router AR 40.
[0049] [Processing Procedure] The following describes the processing procedure executed in the communication system of Fig. 1. Fig. 9 is a sequence diagram for explaining the connection of the CPE 50 on the device 10 side to the AR 40 and the registration of the CPE 50 on the cloud side to the controller 30, which are executed prior to communication.
[0050] First, a process procedure when the CPE 50 (CPE 50-11) on the device 10 side connects to the AR 40 will be described.
[0051] When CPE50-11 is connected to the network and assigned an IP address (RLOC), the CPE registration unit 53 of CPE50-11 transmits a CPE connection request to the nearest AR 40 (AR40-1 in this case) (the area to which CPE50-11 belongs) (S11). The CPE connection request includes an EID (EID#11) assigned under CPE50-11 and an RLOC (IP#11) assigned by the network. The RLOC of CPE50-11 is a global IP address or the like assigned by the network to which CPE50-11 is connected. It is assumed that the EID under CPE50 is set in advance in CPE50.
[0052] When the CPE connection unit 42 of the AR 40-1 receives a CPE connection request from the CPE 50-11, it registers information required for packet transfer from the AR 40-1 to the CPE 50-11 in the routing table 43-1 of the AR 40-1 (S12). In this case, the information "Destination=EID#11, Processing=Encap(IP#11)" is registered (see FIG. 6). This means that when the AR 40-1 receives a packet with a destination IP address of EID#11, i.e., a packet addressed to the host 60 under the control of the CPE 50-11, it will encapsulate the packet with destination address=IP#11, i.e., the IP address of the RLOC of the CPE 50-11, and transmit the packet.
[0053] Next, the CPE connection unit 42 of the AR 40-1 transmits a CPE connection response (connection=OK, area ID=#1) to the CPE 50-11 (S13). When the CPE registration unit 53 of the CPE 50-11 receives the CPE connection response, the CPE 50-11 recognizes that the area ID to which it belongs is #1.
[0054] Next, a process for registering information about the CPE 50 (CPE 50-31) on the cloud side in the controller 30 will be described.
[0055] After the startup of the CPE 50 (CPE 50-31) on the cloud side, the CPE registration unit 53 of the CPE 50-31 transmits a CPE registration request to the controller 30 (S21). The CPE registration request includes the EID (EID#3) under the CPE 50-31, the RLOC (IP#31) of the CPE 50-31, and the area ID (#1) of the area managed by the CPE 50-31. The RLOC of the CPE 50-31 is also assumed to be a global IP address, similar to the RLOC of the CPE 50-11. Various methods are assumed for the assignment of IP addresses in a cloud environment, but this embodiment does not depend on the assignment method. It is sufficient that the CPE 50-31 is ultimately assigned a global IP address that is reachable from the outside.
[0056] When the CPE registration and update unit 32 of the controller 30 receives the CPE registration request, it registers (stores) the information included in the CPE registration request in its own EID-RLOC database 33 (S22). In this case, a record of "EID=EID#3, RLOC=IP#31, area ID=#1" is registered in the EID-RLOC database 33 (see FIG. 8). Next, the CPE registration and update unit 32 transmits a CPE registration response (registration=OK) to the CPE 50-31 (S23).
[0057] FIG. 10 is a sequence diagram for explaining an example of a processing procedure when a packet is transmitted from the host 60-11 under the CPE 50-11 to the host 60-3 under the CPE 50-31.
[0058] Host 60-11 transmits a packet to host 60-3 (S31). Host 60-11 recognizes its own EID, EID#11, as its own IP address and assigns it to the source address of the packet (denoted as SA in FIG. 10), and recognizes host 60-3's EID#3 as host 60-3's IP address and assigns it to the destination address of the packet (denoted as DA in FIG. 10). In other words, host 60-11 and host 60-3 operate by recognizing the EID as an IP address as it is. Therefore, it is sufficient for them to operate as normal IP hosts, and functions specific to this embodiment are not necessary.
[0059] When the forwarding unit 51 of the CPE 50-11 receives a packet from the host 60-11, the destination EID of the packet is not listed in the routing table 54-11, so the RLOC resolution unit 52 transmits an RLOC resolution request to the controller 30 (S32). The RLOC resolution request includes EID#3, which is the destination address of the packet received from the host 60-11, and #1, which is the area ID to which the CPE 50-11 itself belongs.
[0060] When the CPE inquiry unit 31 of the controller 30 receives the RLOC resolution request from the CPE 50-11, it searches the EID-RLOC database 33 using the EID=EID#3 and area ID=#1 included in the RLOC resolution request as keys (S33). As a result of the search, it is found that the RLOC corresponding to EID=EID#3 and area ID=#1 is IP#31, which is the RLOC of the CPE 50-31. Note that this record was registered in the controller 30 by the CPE 50-31 in S21 to S23.
[0061] Next, the CPE inquiry unit 31 transmits an RLOC resolution response (RLOC=IP#31) to the RLOC resolution unit 52 of the CPE 50-11 (S34).
[0062] When the RLOC resolution unit 52 of the CPE 50-11 receives the RLOC resolution response, it registers "Destination=EID#3, Processing=Encap(IP#31)" in the routing table 54-11 of the CPE 50-11 (S35) (see the routing table 54-11 in FIG. 5). This indicates that when a packet with a destination address of EID#3 is received, it is encapsulated with destination=IP#31 and transmitted (because EID#3 exists under the control of the CPE 50-31 and the RLOC of the CPE 50-31 is IP#31).
[0063] Next, the forwarding unit 51 of the CPE 50-11 refers to the routing table 54-11, encapsulates the packet received from the host 60-11 with destination address = IP#31 and source address = IP#11 (RLOC of the CPE 50-11 itself), and transmits it to the CPE 50-31 (S36).
[0064] When the forwarding unit 51 of the CPE 50-31 receives a packet from the CPE 50-11, it processes the packet based on the routing table 54-31 (see FIG. 5). Here, since the destination address of the packet (encapsulated packet) is IP#31, the forwarding unit 51 executes the corresponding process, Decap->Lookup. That is, the forwarding unit 51 decapsulates the packet and searches the routing table 54-31 again (S37). Since the destination address of the packet (decapsulated packet) in the re-search is EID#3, the corresponding process becomes Direct, and the forwarding unit 51 directly delivers the packet to the host 60 of EID#3 (S38). As a result, the host 60-3 receives the packet from the CPE 50-31.
[0065] FIG. 11 is a sequence diagram for explaining the flow of communication from host 60-3 to host 60-11.
[0066] In step S41, host 60-3 transmits a packet (hereinafter referred to as the "target packet") to host 60-11 (S41). At this time, the destination address of the target packet is set to EID#11, which is the EID of host 60-11, and the source address of the target packet is set to EID#3, which is the EID of host 60-3.
[0067] In addition, the destination (next hop) to which the host 60-3 transmits the target packet can be CPE50-31 and CPE50-32, but there are several possible methods for selecting one of them. Since the host 60-3 receives a packet from the host 60-11 from the CPE50-31, the target packet serving as a response (reply) may be transmitted to the CPE50-31, or the forwarding unit 51 of the CPE50-31 may perform SNAT (Source NAT) to change the source address of the packet to CPE50-31 when transmitting a packet from the CPE50-31 to the host 60-3. In the latter case, the host 60-3 determines that it has received a packet from the CPE50-31, so the destination address of the target packet serving as the response is addressed to the CPE50-31, but the destination address is converted to the original address (EID#11, which is the address of the host 60-11) by SNAT in the CPE50-31.
[0068] When the forwarding unit 51 of the CPE 50-31 receives the target packet from the host 60-3, it refers to the routing table 54-31 (S42). Since there is no specific record matching the destination=EID#11 in the routing table 54-31 (see FIG. 5), it matches the destination=Default. Since the processing for the destination=Default is Encap(IP#A1), the forwarding unit 51 encapsulates the target packet with the destination=IP#A1 and transmits it to the AR 40-1 (area representative router for area #1) (S43). Due to this destination=Default record, the CPE 50-31 encapsulates and transmits all packets received from the host 60 on the cloud side to the AR 40-1, which is the area representative router for area 1, and the CPE 50-31 does not need to hold individual route information for the CPE 50 on the device 10 side.
[0069] When the forwarding unit 41 of the AR 40-1 receives the encapsulated target packet from the CPE 50-31, it refers to the routing table 43-1 (see FIG. 6) (S44). Since the destination address of the encapsulated target packet is IP#A1, which is the RLOC of the AR 40-1 itself, the record of "Destination=IP#A1, Processing=Decap->Lookup" in the routing table 43-1 corresponds to the target packet. Therefore, the forwarding unit 41 decapsulates the target packet and searches the routing table 43-1 again. Since the destination address of the decapsulated packet is EID#11, it corresponds to "Destination=EID#11, Processing=Encap(IP#11)" in the routing table 43-1. Therefore, the forwarding unit 41 sets the destination address of the target packet to IP#11, encapsulates it, and transmits the target packet to the CPE 50-11 (RLOC=IP#11) (S45).
[0070] When the forwarding unit 51 of the CPE 50-11 receives the encapsulated target packet from the AR 40-1, it refers to the routing table 54-11 (S46). Specifically, the forwarding unit 51 searches the routing table 54-11 of the CPE 50-11 using the destination address of the target packet=IP#11 (RLOC of the CPE 50-11, i.e., addressed to itself) as a key. As a result, since the record of "Destination=IP#11, Processing=Decap->Lookup" is found to match, the forwarding unit 51 decapsulates the target packet and searches the routing table 54-11 again. Since the destination address of the decapsulated target packet is EID#11, it matches the record of "Destination=EID#11, Processing=Direct". Therefore, the forwarding unit 51 directly delivers the target packet to EID#11, i.e., to the host 60-11 (S47). As a result, the host 60-11 receives the target packet.
[0071] Next, a process procedure executed when CPE 50-11 moves from under AR 40-1 to under AR 40-2 will be described with reference to Fig. 12 to Fig. 14. Fig. 12 and Fig. 13 are sequence diagrams, and Fig. 14 is a diagram showing changes in the routing table of CPE 50-11 and the routing tables of AR 40-1 and AR 40-2.
[0072] When CPE50-11 (device 10-11 having CPE50-11) moves from under AR40-1 to under AR40-2, CPE50-11 reconnects to the access network, and the IP address assigned by the network, i.e., the RLOC of CPE50-11 changes (S51). In this example, it is assumed that the RLOC of CPE50-11 has changed from IP#11 to IP#22. Therefore, the CPE registration unit 53 of CPE50-11 changes the record of "Destination=IP#11, Processing=Decap->Lookup" to "Destination=IP#22, Processing=Decap->Lookup" in the routing table 54-11 of CPE50-11 (see FIG. 14). This record is for performing the process of decapsulating the packet and searching the routing table 54-11 again if the packet is addressed to the AR 40 (to the RLOC of the CPE 50-11) when the packet is sent from the AR 40 to the CPE 50-11.
[0073] When the CPE 50-11 is connected to the network, the CPE registration unit 53 transmits a CPE connection request to the nearest AR 40 (in this case, AR 40-2) (S52). The CPE connection request includes EID=EID#11 and RLOC=IP#22. The EID remains the same as before the movement, but the RLOC becomes IP#22, which is a newly assigned IP address, as described above.
[0074] When the CPE connection unit 42 of the AR 40-2 receives a CPE connection request from the CPE 50-11, it registers a record for transmitting a packet to the CPE 50-11 in the routing table 43-2 (S53). Specifically, the CPE connection unit 42 registers a record of "Destination=EID#11, Processing=Encap(IP#22)" in the routing table 43-2 of the AR 40-2 in Fig. 14. This indicates a process in which, if the destination address is a packet addressed to EID#11 under the control of the CPE 50-11, the packet is encapsulated in IP#22, which is the new RLOC of the CPE 50-11, and the packet is transmitted.
[0075] When the CPE connection unit 42 of the AR 40-2 has successfully registered the AR 40-2 in the routing table 43-2, the CPE connection unit 42 transmits a CPE registration response to the CPE 50-11 (S54). The CPE registration response includes the area ID=#2 as the area ID to which the AR 40-2 belongs.
[0076] This completes the connection procedure when CPE50-11 moves from under AR40-1 to under AR40-2.
[0077] The information (destination=EID#11, processing=Encap(IP#11)) registered in the routing table 43-1 of AR 40-1 before the movement of CPE 50-11 is deleted by the CPE connection unit 42 of CPE 50-11 because it will no longer be necessary. As a method of deletion, a timeout may be set when a state in which no packets arrive at CPE 50-11 continues for a certain period of time (deletion may be performed if a specific entry in the routing table 43-1 is not referenced for a certain period of time), or the CPE 50-11 or AR 40-2 may explicitly notify AR 40-1 that the movement of CPE 50-11 has been completed, and the CPE connection unit 42 of CPE 50-11 may delete the information that is no longer necessary in the routing table 43-1 of AR 40-1.
[0078] Next, the flow of packets from the host 60-11 to the host 60-3 will be described.
[0079] The host 60-11 transmits a packet to the host 60-3 (S55).
[0080] When the forwarding unit 51 of the CPE 50-11 receives the packet, the RLOC resolution unit 52 of the CPE 50-11 transmits an RLOC resolution request to the controller 30 to obtain an RLOC corresponding to EID#3, which is the destination address of the packet (S56). The RLOC resolution request includes EID=#3, which is the EID to be resolved, and area ID=#2, which is the ID of the area to which the CPE 50-11 belongs.
[0081] When the CPE inquiry unit 31 of the controller 30 receives the RLOC resolution request, it searches the EID-RLOC database 33 using the EID (EID#3) and area ID (#2) included in the RLOC resolution request as keys (S57). Since IP#32 (RLOC of CPE 50-32) is registered as the RLOC corresponding to EID=EID#3 and area ID=#2 in the EID-RLOC database 33 (FIG. 8), the CPE inquiry unit 31 transmits an RLOC resolution response including RLOC=IP#32 (S58). Note that when CPE 50-11 was connected under AR 40-1, area ID=#1 was used and RLOC=IP#31 was returned, but when CPE 50-11 is connected under AR 40-2, area ID=#2 is used and RLOC=IP#32 is returned. With this mechanism, each CPE 50 (CPE 50-31 and CPE 50-32) on the cloud side receives packets only from CPEs 50 under a specific AR 40 (i.e., in a specific area).
[0082] When the RLOC resolution unit 52 of the CPE 50-11 receives the RLOC resolution response from the controller 30, it can resolve RLOC=IP#32 as the RLOC corresponding to EID=EID#3, and therefore registers a record of "Destination=EID#3, Processing=Encap(IP#32)" in the routing table 54-11 (S59). This record means that packets addressed to EID#3 are encapsulated with the destination address set to IP#32, and the packets are sent toward IP#32 (i.e., CPE 50-32).
[0083] When the registration in the routing table 54-11 is completed, the forwarding unit 51 of the CPE 50-11 sends the packet encapsulated with the destination address = IP#32 to the CPE 50-32 (S60).
[0084] When the forwarding unit 51 of the CPE 50-32 receives the packet, it refers to the routing table 54-32 (S61). The packet corresponds to "Destination=IP#32, Processing=Decap->Lookup" in the routing table 54-32 in Fig. 5. This means that when a packet addressed to IP#32 (i.e., addressed to the CPE 50-32 itself) is received, it is decapsulated and the routing table 54-32 is searched again.
[0085] Therefore, the forwarding unit 51 of the CPE 50-32 decapsulates the packet and searches the routing table 54-32 again. Since the record of "Destination=EID#3, Processing=Direct" in Fig. 5 matches, the forwarding unit 51 delivers the packet directly to EID#3 (i.e., host 60-3) (S62). As a result, host 60-3 receives the packet from host 60-11.
[0086] On the other hand, the flow of packets from the host 60-3 to the host 60-11 is as shown in FIG.
[0087] In step S64, host 60-3 sends a packet to host 60-11 (S64).
[0088] When the forwarding unit 51 of the CPE 50-32 receives a packet from the host 60-3, it refers to the routing table 54-32 (S65). Since the packet corresponds to "Destination=Default, Processing=Encap(IP#A2)" in Fig. 5, the forwarding unit 51 encapsulates the packet with destination address=IP#A2 (RLOC of AR 40-2) and transmits the packet to AR 40-2 (S66).
[0089] When the forwarding unit 41 of the AR 40-2 receives the packet, it refers to the routing table 43-2 (see FIG. 14) (S67). Since the packet corresponds to the record of "Destination=IP#A2, Processing=Decap->Lookup" in the routing table 43-2 of FIG. 14, the forwarding unit 41 decapsulates the packet and searches the routing table again. Since the destination of the decapsulated packet (original packet) is EID#11, the next search corresponds to the record of "Destination=EID#11, Processing=Encap(IP#22)". Therefore, the forwarding unit 41 encapsulates the packet with destination address=IP#22 and transmits the packet to IP#22, i.e., to CPE 50-11 (S68).
[0090] When the forwarding unit 51 of the CPE 50-11 receives a packet from the AR 40-2, it refers to the routing table 54-11 (S69). Since the packet matches "Destination=IP#22, Processing=Decap->Lookup" in the routing table 54-11 of the CPE 50-11 after the movement in FIG. 14, the forwarding unit 51 decapsulates the packet and searches the routing table 54-11 again. Then, since the next record that matches is "Destination=EID#11, Processing=Direct", the forwarding unit 51 delivers the packet directly to EID#11, that is, to the host 60-11 (S70). As a result, the host 60-11 receives the packet from the host 60-3.
[0091] In this way, when CPE50-11 moves from under AR40-1 to under AR40-2, only AR40-1, AR40-2, and CPE50-11 change their routing tables, and no changes occur in CPE50-31 or CPE50-32 on the cloud side. This shows that an increase or decrease in the number of devices 10 or the movement of devices 10 does not change the routing table 54 of the cloud-side CPE50, and the cloud-side CPE50 is not affected by the amount of routing table or the amount of processing required to change the routing table.
[0092] As described above, according to the present embodiment, it is possible to reduce the number of routes to be held in the routing table of the cloud-side CPE 50. Therefore, it is possible to improve the efficiency of communication regarding devices whose IP addresses change.
[0093] In addition, in the conventional technology, the amount of queries (transactions) to the database that holds the EID-RLOC correspondence information is also an issue. Specifically, a query to the database that holds the EID-RLOC correspondence information occurs every time a device starts communication with an application that has a new EID. Although it is possible to cache information queried once on the device side, as described above, the EID-RLOC correspondence information held in the database is constantly updated. If the time for which the cache is held is increased, the number of queries can be reduced, but if the time is increased too much, a discrepancy occurs between the cache and the latest information, and if the EID-RLOC correspondence relationship changes due to device movement, etc., there is a possibility that normal communication will not be possible.
[0094] According to this embodiment, by reducing (making unnecessary) inquiries (RLOC resolution requests) from the cloud-side CPE 50 to the controller 30, it is possible to eliminate bottlenecks in existing technologies and increase the number of devices 10 (number of CPEs 50) that can be accommodated in the system.
[0095] In this embodiment, the device 10 is an example of a communication device. The data center 20 is an example of a predetermined information processing device. The AR 40 is an example of an accommodating device. The RLOC is an example of a first IP address. The EID is an example of a second IP address. The CPE registration unit 53 is an example of a registration unit. The forwarding unit 51 is an example of a packet processing unit. The RLOC resolution unit 52 is an example of a resolution unit. The RLOC of CPE 50-31 or CPE 50-32 is an example of a third IP address. The EID of the host 60-3 is an example of a fourth IP address.
[0096] Although the embodiment of the present invention has been described in detail above, the present invention is not limited to such specific embodiment, and various modifications and variations are possible within the scope of the gist of the present invention described in the claims. [Explanation of symbols]
[0097] 10 Devices 20 Data Center 30 Controller 31 CPE Inquiry Department 32 CPE Registration and Renewal Department 33 EID-RLOC Database 40 AR 41 Forwarding Department 42 CPE connection 43 Routing Table 50 CPE 51 Forwarding Department 52 RLOC Solution Department 53 CPE Registration Department 54 Routing Table 100 Drive device 101 Recording media 102 Auxiliary storage 103 Memory device 104 CPU 105 Interface device B Bus N1 Core Network
Claims
1. A communication device that moves between a plurality of areas and communicates with a predetermined information processing device, a registration unit that notifies a accommodating device corresponding to an area to which the communication device belongs, among a plurality of accommodating devices each corresponding to one of the plurality of areas, of a first IP address that is changed due to movement of the communication device and a second IP address that is not changed due to the movement, thereby causing the accommodating device to register information for encapsulating a packet addressed to the second IP address from the predetermined information processing device having a third IP address for each area and a fourth IP address that is independent of the area, in the accommodating device and transmitting the packet; a resolution unit that acquires the third IP address corresponding to the fourth IP address designated as a destination of a packet from the communication device and an area to which the communication device belongs from a controller that stores the third IP address for each combination of the fourth IP address and the area; a packet processing unit that decapsulates the packet encapsulated by the first IP address into a packet destined for the second IP address, and encapsulates the packet by the third IP address acquired by the resolution unit; A communication device comprising:
2. The registration unit receives identification information of an area to which the communication device belongs from the accommodation device corresponding to the area.
2. The communication device according to claim 1.
3. A communication device that moves between a plurality of areas and communicates with a predetermined information processing device, a registration procedure for notifying a accommodating device corresponding to an area to which the communication device belongs, among a plurality of accommodating devices each corresponding to one of the plurality of areas, of a first IP address that is changed due to movement of the communication device and a second IP address that is not changed due to the movement, thereby causing the accommodating device to register information for encapsulating a packet addressed to the second IP address from the predetermined information processing device having a third IP address for each area and a fourth IP address independent of the area, in the accommodating device and transmitting the packet; a resolution procedure for acquiring the third IP address corresponding to the fourth IP address designated as a destination of a packet from the communication device and an area to which the communication device belongs from a controller that stores the third IP address for each combination of the fourth IP address and the area; a packet processing step of decapsulating the packet encapsulated by the first IP address into a packet destined for the second IP address, and encapsulating the packet by the third IP address obtained by the resolution step; A communication method comprising:
4. The registration step includes receiving, from the accommodation device corresponding to an area to which the communication device belongs, identification information of the area.
4. The communication method according to claim 3.
5. 5. A program for causing a communication device to execute the communication method according to claim 3 or 4.
Citation Information
Patent Citations
Method for mobile node to dynamically acquire location identifier, and lisp network
EP2775674A1
Source-aware technique for facilitating lisp host mobility
US20160065531A1
