SYSTEM FOR SUPPORTING MULTI-TENANT BASED ON PRIVATE IP ADDRESS IN VIRTUAL PRIVATE CLOUD NETWORKS AND OPERATING METHOD THEREOF

• US 20150188802A1
• Filed: 11/24/2014
• Published: 07/02/2015
• Est. Priority Date: 12/26/2013
• Status: Abandoned Application

• Current Assignee: Electronics and Telecommunications Research Institute
• Original Assignee: Electronics and Telecommunications Research Institute
• Inventors: YOON, Hyeon-Sik, PARK, Hea-Sook, JUNG, Boo-Geum
• Application Number:
  US14/551,400
• Publication Number:
  US 20150188802A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 45/64 using an overlay routing layer

Abstract

A system includes: a map-server storing EID-RLOC mapping information; an ITR receiving RLOC information on a corresponding EID from an ETR designated by the map-server based on a destination EID and a tenant identifier of a corresponding enterprise network when receiving packets for requesting allocation of computing resources from a terminal within the enterprise networks, generating an LISP data packet based on the received RLOC information and the RLOC information of the corresponding enterprise network, and transmitting the generated LISP data packet to a backbone network; and an ETR requesting the computing resources to a corresponding server within a cloud center based on the received LISP data packet to receive information on the computing resources from the server as an answer to the request when receiving the LISP data packet through the backbone network and providing the received information on the computing resources to the ITR

Claims

1. A system for supporting multi-tenant based on a private IP address, comprising:

a map-server configured to store endpoint identifier-routing locator (EID-RLOC) mapping information;

an ingress tunnel router (ITR) configured to receive RLOC information on a corresponding EID from an ETR designated by the map-server based on a destination EID and a tenant identifier of a corresponding enterprise network when receiving packets for requesting allocation of computing resources from a terminal within the enterprise networks, generate an LISP data packet based on the received RLOC information and the RLOC information of the corresponding enterprise network, and transmit the generated LISP data packet to a backbone network; and

an egress tunnel router (ETR) configured to request the computing resources to a corresponding server within a cloud center based on the received LISP data packet to receive information on the computing resources from the server as an answer to the request when receiving the LISP data packet through the backbone network, and provide the received information on the computing resources to the ITR.

2. The system of claim 1, wherein the ITR constructs an IP header including the RLOC information on the destination EID received from the ETR designated by the map-server which is set as a destination IP address and the RLOC information of the corresponding enterprise network which is set as a source IP address and encapsulates the packet with the constructed IP header to generate the LISP data packet.

3. The system of claim 2, wherein the ITR drops the packet received from the terminal or processes the packet according to a previously configured policy when the ITR does not receive the RLOC information on the destination EID.

4. The system of claim 1, wherein when recognizing an HD of the server within the cloud center requesting a connection setting, the ETR generates an LISP control message including the recognized EID of the server and the RLOC of the cloud center and transmits the generated LISP control message to the map-server to register the EID-RLOC mapping information on the server.

5. The system of claim 1, wherein when receiving the LISP data packet through the backbone network, the ETR decapsulates the IP header in the received LISP data packet and adds a VLAN ID previously allocated to the corresponding tenant to the packet for requesting the allocation of the computing resources and then transmits the packet to the destination EID.

6. The system of claim 1, wherein the ETR receives the packet including the information on the computing resources from the server, constructs an IP header including the RLOC information on the enterprise network which is set as a destination IP address and the RLOC information on an EID of the server which is set as a source IP address, encapsulates the packet with the constructed IP header to generate the LISP data packet, and provides the generated LISP data packet to the ITR.

7. The system of claim 1, wherein the EID-RLOC mapping information includes an EID for identifying an individual terminal, a RLOC for identifying a position of a network to which the corresponding terminal belongs, and an identifier for identifying each tenant in the entire network.

8. An operating method for supporting multi-tenant based on a private IP address, comprising:

constructing, by a map-server, endpoint identifier-routing locator (EID-RLOC) mapping information;

receiving, by an ingress tunnel router (ITR), RLOC information on a corresponding EID from an ETR designated by the map-server based on a destination EID and a tenant identifier of a corresponding enterprise network when the ITR receives packets for requesting allocation of computing resources from terminals within the enterprise networks, generating an LISP data packet based on the received RLOC information and the RLOC information of the corresponding enterprise network, and transmitting the generated LISP data packet to a backbone network; and

requesting, by an egress tunnel router (ETR), the computing resources to a corresponding server within a cloud center based on the received LISP data packet to receive information on the computing resources from the server as an answer to the request when the ETR receives the LISP data packet through the backbone network and provide the received information on the computing resources to the ITR.

9. The operating method of claim 8, wherein in the constructing, when an EID of the terminal within the enterprise network requesting a connection setting is recognized, an LISP control message including the recognized EID of the terminal and the RLOC of the enterprise network to which the terminal belongs is generated and the generated LISP control message is transmitted to the map-server to register the EID-RLOC mapping information on the terminal.

10. The operating method of claim 8, wherein in the transmitting, an IP header includes the RLOC information on the destination EID received from the ETR designated by the map-server which is set as a destination IP address and the RLOC information of the corresponding enterprise network which is set as a source IP address and the packet is encapsulated with the IP header to generate the LISP data packet.

11. The operating method of claim 10, wherein in the transmitting, when the RLOC information on the destination EID is not received, the packet received from the terminal is dropped or the packet is processed according to a previously configured policy.

12. The operating method of claim 8, wherein in the constructing, when an EID of the server within the cloud center requesting a connection setting is recognized, an LISP control message including the recognized EID of the server and the RLOC of the cloud center is generated and the generated LISP control message is transmitted to the map-server to register the EID-RLOC mapping information on the server.

13. The operating method of claim 8, wherein in the providing, when the LISP data packet is received through the backbone network, the IP header in the received LISP data packet is decapsulated and a VLAN ED previously allocated to the corresponding tenant is added to the packet for requesting the allocation of the computing resources and then the packet is transmitted to the destination EID.

14. The operating method of claim 8, wherein in the providing, the packet including the information on the computing resources is received from the server, an IP header includes the RLOC information on the enterprise network which is set as a destination IP address and the RLOC information on an EID of the server which is set as a source IP address, the packet is encapsulated with the constructed IP header to generate the LISP data packet, and the generated LISP data packet is provided to the ITR.

15. The operating method of claim 8, wherein the EID-RLOC mapping information includes an EID for identifying an individual terminal, a RLOC for identifying a position of a network to which the corresponding terminal belongs, and an identifier for identifying each tenant in the entire network.