US20210091977A1 - Network system, network device, and recording medium - Google Patents
Network system, network device, and recording medium Download PDFInfo
- Publication number
- US20210091977A1 US20210091977A1 US16/846,391 US202016846391A US2021091977A1 US 20210091977 A1 US20210091977 A1 US 20210091977A1 US 202016846391 A US202016846391 A US 202016846391A US 2021091977 A1 US2021091977 A1 US 2021091977A1
- Authority
- US
- United States
- Prior art keywords
- network device
- network
- address information
- information
- communication
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5007—Internet protocol [IP] addresses
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5076—Update or notification mechanisms, e.g. DynDNS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
- H04L63/0272—Virtual private networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/16—Implementing security features at a particular protocol layer
- H04L63/164—Implementing security features at a particular protocol layer at the network layer
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
Definitions
- the present disclosure relates to a network system, a network device, and a recording medium.
- a virtual private network When communication is performed between bases via the Internet, construction of a virtual private network (a VPN) is generally performed in view of security, as disclosed in JP-A-2012-039218, for example.
- the VPN may be constructed in a hub-and-spoke system in which a base with a hub function and a spoke base without the hub function are mixed in terms of network management, scale, or the like.
- the spoke base in the hub-and-spoke system communicates, via a hub base connected via VPN, with another spoke base or an external device connected to the Internet.
- next generation network (an NGN) based on an Internet Protocol (IP) technology has become widespread.
- IP Internet Protocol
- the hub base and the spoke base that are connected to the next generation network are connected to an Internet Service Provider (ISP) via the next generation network to communicate with an external device on the Internet.
- ISP Internet Service Provider
- PPPoE PPP over Ethernet
- IPoE IP over Ethernet
- the spoke base When the spoke base communicates with the external device via the Internet, the spoke base is connected to the hub base via a network termination device and an ISP as a contract destination provided in the next generation network, and further via an ISP and a network termination device provided in a hub base.
- the hub base is connected to the Internet via the network termination device provided in the next generation network and an internet service provider as the contract destination. Accordingly, the spoke base communicates with the external device via the hub base.
- traffic increases, the communication speed is not stable due to congestion in the network termination device.
- Non-limiting embodiments of the present disclosure relate to stabilizing communication speed when a spoke base communicates with an external device via the Internet as compared with a case where the spoke base communicates with a hub base via an internet service provider.
- aspects of certain non-limiting embodiments of the present disclosure address the above advantages and/or other advantages not described above. However, aspects of the non-limiting embodiments are not required to address the advantages described above, and aspects of the non-limiting embodiments of the present disclosure may not address advantages described above.
- a network system including: a hub base that includes a first network device with a hub function, the first network device being connected to an information communication network; and a spoke base that includes a second network device without the hub function, the second network device being connected to the information communication network, wherein communication between a computer provided in the spoke base and an external device connected with the computer via Internet is performed such that intra-network loopback communication is performed between the first network device and the second network device in the information communication network without an internet service provider, and communication is performed between the first network device and the external device via the internet service provider.
- FIG. 1 is an overall configuration diagram showing a network system according to an exemplary embodiment
- FIG. 2 is a schematic hardware configuration diagram of a network device according to the present exemplary embodiment
- FIG. 3 is a flowchart showing processing when a star branch base according to the present exemplary embodiment establishes communication with an external device
- FIG. 4 is an overall configuration diagram showing a network system when it is assumed that the star branch base has a subscription with an ISP;
- FIG. 5 is a flowchart showing processing when a mesh base according to the present exemplary embodiment establishes communication with the star branch base.
- FIG. 6 is an overall configuration diagram showing a network system when it is assumed that the network system is connected to the Internet by a PPPoE method.
- FIG. 1 is an overall configuration diagram showing a network system according to the present exemplary embodiment.
- FIG. 1 shows an Internet 1 , an ISP 2 b , an NGN 3 , a base 4 , a network operation center (NOC) 5 , an ISP 6 , an NGN 7 , and a base 8 .
- the ISPs 2 b and 6 are carriers that provide a service for connecting to the Internet 1 , and are also simply referred to as “providers”.
- An information communication network uses an IP network as a network and is connected to another information communication network or a network such as a PSTN network, ISDN network, an Internet, or the like.
- the information communication network has at least an end user function, a transport function, and a network attachment control function as architecture. Issuance of address information to be described below is achieved by the network attachment control function of performing a series of processing when a network device is connected to the network.
- a next generation network also referred to as an “NGN”
- NTN next generation network
- the NGNs 3 and 7 are next generation information communication networks based on an IP technology.
- the NGNs 3 and 7 include network termination devices (not shown).
- the base 4 is connected to a contract destination ISP via the network termination device.
- An IP over Ethernet (IPoE) method is a communication method capable of bypassing a network termination device that is currently a bottleneck in the PPPoE method.
- the network system according to the present exemplary embodiment is connected to the Internet 1 according to the IPoE method.
- the Next Generation Network provided by the NTT (Nippon Telegraph and Telephone Corporation) group is assumed as the NGN 3 , but the NGN 3 is not limited thereto.
- a network including the next generation network provided by the NTT group may be used.
- the NGN 3 according to the present exemplary embodiment may be the next generation network provided by the other company.
- the bases 4 a to 4 c correspond to, for example, offices of a company, respectively. Each of the bases 4 a to 4 c is provided with one or plural computers such as a personal computer (PC) or the like.
- the bases 4 a to 4 c are collectively referred to as the “base 4 ” when it is not necessary to distinguish the bases 4 a to 4 c from one another. The same applies to other components.
- the base 4 constitutes a hub-and-spoke type VPN.
- a port of the base 4 b to which the NGN 3 is connected, is provided with a network (NW) device 41 b with a hub function for connecting to the Internet 1 in another base. Therefore, the base 4 b corresponds to a hub base.
- the computer provided in the base 4 b is connected to the NGN 3 via the network device 41 b .
- ports of the bases 4 a and 4 c and to which the NGN 3 is connected are provided with network (NW) devices 41 a and 41 c without the hub function. Therefore, the bases 4 a and 4 c correspond to spoke bases.
- the computers provided at the bases 4 a and 4 c are connected to the NGN 3 via the network devices 41 a and 41 c.
- the base 4 b has a subscription with the ISP 2 b . Therefore, only the network device 41 provided at the base 4 b is connectable to the Internet 1 via the NGN 3 and the ISP 2 b .
- the bases 4 a and 4 c does not have a subscription with the ISP. Therefore, the network devices 41 a and 41 c provided in the bases 4 a and 4 c cannot be directly connected to the Internet 1 . In other words, the bases 4 a and 4 c may be connected to the Internet 1 via the base 4 b without subscription.
- Information regarding the subscription with the ISP at each base 4 corresponds to attribute information of this base 4 .
- the base 4 b constructs a mesh VPN while the bases 4 a and 4 c are branch locations configured to construct a star VPN. Therefore, the bases 4 a and 4 c are also referred to as “star branch bases” in the present exemplary embodiment.
- all communication with other bases is performed via the mesh base 4 b.
- the NOC 5 is a network operation center that is connected to the Internet 1 and is configured to manage address information of the network device connected to the Internet 1 .
- the “address information” is identification information that is specified for identifying a device on the network, and is generally represented by a number.
- the address information is an IP address, and an IPv4 format, an IPv6 format, or IPv4 over IPv6 format is used depending on the connection method (PPPoE or IPoE) with the Internet 1 , a configuration of the ISPs 2 b and 6 or NGNs 3 and 7 , and the subscription.
- the NGN 3 includes a management device 31 and a NOC 32 .
- the management device 31 has the above-described function of the information communication network, and performs general management of the NGN 3 such as issuance of the IP address in the NGN 3 or the like.
- the NOC 32 is connected so as to be referred to from the NGN 3 and has the same function as that of the NOC 5 , but a management range thereof is limited to the network device 41 directly connected to the NGN 3 .
- the network device 41 When the network device 41 is connected to the NGN 3 , the network device 41 notifies a set of a name of the network device 41 , such as identification information like a domain name, and the IP address to the NOC 32 of the NGN 3 as attribute information of the network device 41 .
- the network device 41 With the set being stored in the NOC 32 , the network device 41 becomes a network device to be managed. When the IP address is changed, the network device 41 notifies the set of its name and the changed IP address to the NOC 32 of the NGN 3 .
- the attribute information of the network device 41 also includes information regarding the subscription with the ISP.
- the NOC 32 refers to the attribute information of the network device 41 connected to the NGN 3 , and responds with the IP address of the network device 41 to be connected in response to a query from the network device 41 to which the name of the network device 41 to be connected is specified.
- the ISP 6 and the NGN 7 are provided in another network system using the Internet 1 , and the ISP 6 and the NGN 7 may have an existing function.
- the NGN 7 may have a function equivalent to that of the NGN 3 .
- the base 8 is a mesh base or a star branch base similarly to the above-described base 4 .
- a computer (not shown) provided in the base 8 corresponds to an external device connected via the Internet 1 .
- FIG. 2 is a schematic hardware configuration diagram of the network device 41 according to the present exemplary embodiment.
- the network device 41 according to the present exemplary embodiment includes a computer, and may be implemented by a general-purpose hardware configuration presenting in the related art. Accordingly, as shown in FIG. 2 , the network device 41 includes at least a CPU 21 which is a processor, storage units which are a ROM 22 , a RAM 23 , a hard disk drive (HDD) 24 , and the like, and a network interface (IF) 25 .
- the network device 41 according to the present exemplary embodiment has various functions as network devices, such as a firewall, a gateway, a router, and the like. These functions and functions that are characteristic in the present exemplary embodiment (described below) are implemented by cooperative operation of the computer mounted on the network device 41 and a program operated by the CPU 21 mounted on the computer.
- the ISPs 2 and 6 , the NOCs 5 and 32 , and the management device 31 according to the present exemplary embodiment are also implemented by a computer, so that the ISPs 2 and 6 , the NOCs 5 and 32 , and the management device 31 have at least a configuration shown in FIG. 2 .
- the program used in the present exemplary embodiment may be provided by means of any communication means as well as by being stored in a computer readable recording medium such as a CD-ROM, a USB memory, or the like.
- the program provided by means of the communication means or the recording medium is installed in the computer, and is sequentially executed by the CPU of the computer to perform various processing.
- the network device 41 a When receiving a communication request from the in-base terminal, the network device 41 a broadcasts a request to issue an IP address to the NGN 3 so as to acquire an IP address used by the network device 41 a (step 101 ).
- the management device 31 in the NGN issues the IP address.
- the ISP issues the IP address.
- the star branch base 4 a does not have a subscription with the ISP. Therefore the ISP is not an issuance source and the NGN 3 is controlled to be the issuance source.
- the ISP 2 b is provided corresponding to the mesh base 4 b
- no ISP is provided corresponding to the star branch base 4 a , which indicates that the star branch base 4 a does not have a subscription with the ISP.
- the network device 41 a When the network device 41 a acquires the IP address in response to the transmitted request to issue an IP address (step 102 ), the network device 41 a subsequently acquires the IP address of the network device 41 b by sending a request to acquire address information including a name (that is, a domain name of the network device 41 b ) of the mesh base 4 b which is known, to the NOC 32 (step 103 ).
- the network device 41 a performs VPN connection according to a security architecture for IP (IPsec) protocol, and establishes a communication path with the network device 41 b in a network of the NGN 3 (step 105 ).
- IPsec IP Security
- a method of establishing a communication path is not limited to IPsec, and may be a method of simply adding routing information or a method of constructing a tunnel by the IPsec protocol or an IPIP protocol.
- Communication between network devices, here, between the network devices 41 a and 41 b in the NGN 3 without using the ISP is referred to as “intra-network loopback communication”.
- a path by the intra-network loopback communication is schematically shown by a broken line 11 a .
- the network device 41 may identify the issuance source from an IP address system.
- the network device 41 b is connected to the Internet 1 via the ISP 2 b . Then, the network device 41 b relays communication of the in-base terminal such that the in-base terminal may communicate with the external device.
- a communication path between the network device 41 b and the external device is schematically shown by a broken line 11 b.
- the network device 41 a provided in the star branch base 4 a makes the in-base terminal communicate with the external device by the communication path via the network device 41 provided in the mesh base 4 b .
- the network device 41 a performs the intra-network loopback communication with the network device 41 b without using the ISP.
- the network device 41 a may acquire the IP address of the network device 41 b by providing the NOC 32 in the NGN 3 .
- a domain name system DNS
- the DNS is also referred to as a “name decision server”, and responds with an IP address of the network device 41 which is an IPv6 address or the like in response to a query in which the domain name of the network device 41 has been specified.
- the present exemplary embodiment describes a case in which the issuance source of the IP address is NGN 3 .
- the issuance source of the IP address may be the ISP in a case where the star branch base 4 a has a subscription with the ISP. Such a case will also be described.
- FIG. 4 is an overall configuration diagram of a network system when the star branch base 4 has a subscription with the ISP.
- FIG. 4 is different from FIG. 1 in that an ISP 2 a corresponding to the star branch base 4 a is connected to the NGN 3 in terms of the system configuration.
- the network device 41 a is connected to the ISP 2 a , and an Internet VPN is established via the ISP 2 b (step 106 ). That is, communication between bases is established between the network device 41 a and the network device 41 b via the ISPs 2 a and 2 b as indicated by a broken line 11 c , instead of the intra-network loopback communication indicated by the broken line 11 a .
- a virtual network enabler (a VNE) may have issued the IP address to the network device 41 .
- the IP address issued by the VNE is managed by the ISP, so that the network device 41 recognizes the issuance source as the ISP.
- the network device 41 a may be mainly operated to establish the intra-network loopback communication between the network device 41 a and the network device 41 b .
- the network device 41 b may also be mainly operated to establish the intra-network loopback communication. This processing will be described with reference to a flowchart shown in FIG. 5 .
- the network device 41 b connected to the Internet 1 queries, according to normal operation, to the NOC 5 connected to the Internet 1 for the IP address of the network device 41 a by transmitting a request to acquire the IP address of the network device to be communicated with (step 111 ).
- the request to acquire the IP address includes the name of the network device 41 b that identifies the network device.
- the NOC 5 identifies the network device 41 a to be communicated with from subscription information or the like.
- the NOC 5 may respond with the IP address of the network device connected to the Internet 1 in response to the request to acquire the IP address.
- the base 4 a does not have a subscription with the ISP and is not connected to the Internet 1 , so that the NOC 5 does not manage the IP address of the network device 41 a .
- the NOC 5 responds with information indicating that the IP address cannot be acquired.
- the NOC 5 responds with, as the information indicating that the IP address is unavailable, the name of the network device 41 a that includes the domain name and the like identifying the NGN 3 to which the network device 41 a to be communicated with is connected.
- the network device 41 b receives a response from the NOC 5 in response to the request to acquire the IP address (step 112 ). If the response is the name of the network device (YES in step 113 ), the NGN 3 is identified from this information, and the request to acquire the IP address of the network device 41 a is transmitted to the NOC 32 of the identified NGN 3 (step 114 ).
- the request to acquire the IP address includes the name of the network device 41 which is the domain name or the like.
- the NOC 32 manages the set including the name and the IP address of the network device 41 in the NGN 3 , so that the NOC 32 responds with the IP address of the network device 41 a in response to the request to acquire the IP address.
- the network device 41 b When the network device 41 b acquires the IP address of the network device 41 a (step 115 ), the network device 41 b establishes a path for performing the intra-network loopback communication with the network device 41 a in the NGN 3 .
- the method of establishing the communication path may be the method of simply adding routing information or the method of constructing a tunnel by the IPsec protocol or the IPIP protocol.
- the intra-network loopback communication may be performed between the network device 41 a and the network device 41 b.
- the NOC 5 responds with the IP address of the network device connected to the Internet 1 in response to the request to acquire the IP address.
- the network device 41 b acquires the IP address from the NOC 5 (NO in step 113 )
- the network device 41 b establishes the communication with the network device via the Internet 1 (step 117 ).
- the NGN 3 responds to the request to issue an IP address from the network device 41 b , so that a provider 2 a issues the IP address when the star branch base 4 a has an IPoE-type provider subscription and the NGN 3 issues the IP address when the star branch base 4 a does not have the IPoE-type provider subscription.
- the network device 41 b performs the VPN connection with the network device 41 a by an Internet VPN method.
- the network device 41 b performs the VPN connection with the network device 41 a by intra-network loopback.
- the ISPs 2 a to 2 c are respectively associated with the bases 4 a to 4 c in FIG. 6 . That is, each base 4 has a subscription with the ISP 2 to connect to the Internet 1 according to the PPPoE method.
- network termination devices 32 a to 32 c are provided in the NGN 3 corresponding to the ISPs 2 a to 2 c .
- the number of the network termination devices 32 a to 32 c provided corresponding to the ISPs 2 a to 2 c and the ISP 2 to be a contract destination are not particularly described.
- the ISP 2 a becomes the issuance source of the IP address 1 since the star branch base 4 a has a subscription with the ISP 2 a .
- the Internet VPN is established between the network device 41 a and the network device 41 b . That is, the network device 41 a is connected to the ISP 2 a via the network termination device 32 a .
- the network device 41 b is connected to the ISP 2 b via the network termination device 32 b .
- a communication path by the Internet VPN established as described above is indicated by a broken line 11 d .
- a procedure of establishing a communication path between the network device 41 b and the external device is the same as that using the IPoE method, so that a description thereof will be omitted.
- the communication path between the network device 41 b and the external device is schematically shown by a broken line 11 b.
- the in-base terminal in the star branch base 4 a communicates with the external device through paths 11 d and 11 b as shown in FIG. 6 .
- the communication by the path 11 d that is, the communication between the star branch base 4 a and the mesh base 4 b via the Internet VPN is performed
- the network termination device 32 is said to cause a decrease in communication speed and instability. However, if the intra-network loopback communication indicated by the broken line 11 a is performed between the network device 41 a and the network device 41 b , the network termination device 32 may be passed only once. That is, when the communication is performed from the in-base terminal to the external device, the decrease in communication speed and the instability may be prevented by implementing the intra-network loopback communication in the NGN 3 .
- FIG. 4 shows a configuration in which the ISPs 2 a and 2 c , and the network termination device 32 are provided.
- the intra-network loopback communication since the intra-network loopback communication is implemented, subscriptions with the ISPs 2 a and 2 c at the star branch bases 4 a and 4 c become unnecessary, and the network termination device 32 becomes unnecessary. Accordingly, the intra-network loopback communication may improve not only the communication speed but also the cost efficiency.
- processor refers to hardware in a broad sense.
- the term “processor” refers to hardware in a broad sense.
- the processor includes general processors (e.g., CPU: Central Processing Unit), dedicated processors (e.g., GPU: Graphics Processing Unit, ASIC: Application Integrated Circuit, FPGA: Field Programmable Gate Array, and programmable logic device).
- processor is broad enough to encompass one processor or plural processors in collaboration which are located physically apart from each other but may work cooperatively.
- the order of operations of the processor is not limited to one described in the exemplary embodiments above, and may be changed.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
- This application is based on and claims priority under 35 USC 119 from Japanese Patent Application No. 2019-170685 filed on Sep. 19, 2019.
- The present disclosure relates to a network system, a network device, and a recording medium.
- When communication is performed between bases via the Internet, construction of a virtual private network (a VPN) is generally performed in view of security, as disclosed in JP-A-2012-039218, for example. The VPN may be constructed in a hub-and-spoke system in which a base with a hub function and a spoke base without the hub function are mixed in terms of network management, scale, or the like. The spoke base in the hub-and-spoke system communicates, via a hub base connected via VPN, with another spoke base or an external device connected to the Internet.
- In recent years, a next generation network (an NGN) based on an Internet Protocol (IP) technology has become widespread. The hub base and the spoke base that are connected to the next generation network are connected to an Internet Service Provider (ISP) via the next generation network to communicate with an external device on the Internet.
- In a related art, there is a method of connecting to the Internet according to a protocol called PPP over Ethernet (PPPoE). In a case of a network system to which a PPPoE method is introduced, for example, when an ID and a password are specified from a computer provided at any base, the computer is connected to the Internet after being tunneled with the ISP authenticated based on the ID and the password.
- In recent years, a protocol called IP over Ethernet (IPoE) has been proposed as a protocol for connecting to the ISP. In IPoE, line authentication is performed to determine which ISP is to be connected.
- When the spoke base communicates with the external device via the Internet, the spoke base is connected to the hub base via a network termination device and an ISP as a contract destination provided in the next generation network, and further via an ISP and a network termination device provided in a hub base. The hub base is connected to the Internet via the network termination device provided in the next generation network and an internet service provider as the contract destination. Accordingly, the spoke base communicates with the external device via the hub base. However, when traffic increases, the communication speed is not stable due to congestion in the network termination device.
- Aspects of non-limiting embodiments of the present disclosure relate to stabilizing communication speed when a spoke base communicates with an external device via the Internet as compared with a case where the spoke base communicates with a hub base via an internet service provider.
- Aspects of certain non-limiting embodiments of the present disclosure address the above advantages and/or other advantages not described above. However, aspects of the non-limiting embodiments are not required to address the advantages described above, and aspects of the non-limiting embodiments of the present disclosure may not address advantages described above.
- According to an aspect of the present disclosure, there is provided a network system including: a hub base that includes a first network device with a hub function, the first network device being connected to an information communication network; and a spoke base that includes a second network device without the hub function, the second network device being connected to the information communication network, wherein communication between a computer provided in the spoke base and an external device connected with the computer via Internet is performed such that intra-network loopback communication is performed between the first network device and the second network device in the information communication network without an internet service provider, and communication is performed between the first network device and the external device via the internet service provider.
- Exemplary embodiment(s) of the present invention will be described in detail based on the following figures, wherein:
-
FIG. 1 is an overall configuration diagram showing a network system according to an exemplary embodiment; -
FIG. 2 is a schematic hardware configuration diagram of a network device according to the present exemplary embodiment; -
FIG. 3 is a flowchart showing processing when a star branch base according to the present exemplary embodiment establishes communication with an external device; -
FIG. 4 is an overall configuration diagram showing a network system when it is assumed that the star branch base has a subscription with an ISP; -
FIG. 5 is a flowchart showing processing when a mesh base according to the present exemplary embodiment establishes communication with the star branch base; and -
FIG. 6 is an overall configuration diagram showing a network system when it is assumed that the network system is connected to the Internet by a PPPoE method. - Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the drawings.
-
FIG. 1 is an overall configuration diagram showing a network system according to the present exemplary embodiment.FIG. 1 shows anInternet 1, anISP 2 b, an NGN 3, a base 4, a network operation center (NOC) 5, an ISP 6, an NGN 7, and abase 8. TheISPs 2 b and 6 are carriers that provide a service for connecting to the Internet 1, and are also simply referred to as “providers”. - An information communication network according to the present exemplary embodiment uses an IP network as a network and is connected to another information communication network or a network such as a PSTN network, ISDN network, an Internet, or the like. The information communication network has at least an end user function, a transport function, and a network attachment control function as architecture. Issuance of address information to be described below is achieved by the network attachment control function of performing a series of processing when a network device is connected to the network. In the present exemplary embodiment, a case in which a next generation network (also referred to as an “NGN”) is used as an information communication network as shown in
FIG. 1 will be described as an example. - The
NGNs 3 and 7 are next generation information communication networks based on an IP technology. TheNGNs 3 and 7 include network termination devices (not shown). When the NGN 3 is connected to the Internet by a PPPoE method, the base 4 is connected to a contract destination ISP via the network termination device. An IP over Ethernet (IPoE) method is a communication method capable of bypassing a network termination device that is currently a bottleneck in the PPPoE method. The network system according to the present exemplary embodiment is connected to the Internet 1 according to the IPoE method. - In the present exemplary embodiment, the Next Generation Network provided by the NTT (Nippon Telegraph and Telephone Corporation) group is assumed as the NGN 3, but the NGN 3 is not limited thereto. For example, a network including the next generation network provided by the NTT group may be used. When another company provides a next generation network which is an information communication network based on the IP technology and has a function equivalent to that of the next generation network provided by the NTT group, the NGN 3 according to the present exemplary embodiment may be the next generation network provided by the other company.
- The
bases 4 a to 4 c correspond to, for example, offices of a company, respectively. Each of thebases 4 a to 4 c is provided with one or plural computers such as a personal computer (PC) or the like. Thebases 4 a to 4 c are collectively referred to as the “base 4” when it is not necessary to distinguish thebases 4 a to 4 c from one another. The same applies to other components. - The base 4 according to the present exemplary embodiment constitutes a hub-and-spoke type VPN. In the base 4, a port of the
base 4 b, to which the NGN 3 is connected, is provided with a network (NW)device 41 b with a hub function for connecting to the Internet 1 in another base. Therefore, thebase 4 b corresponds to a hub base. The computer provided in thebase 4 b is connected to the NGN 3 via thenetwork device 41 b. On the other hand, ports of thebases devices bases bases network devices - In the present exemplary embodiment, only the
base 4 b has a subscription with theISP 2 b. Therefore, only thenetwork device 41 provided at thebase 4 b is connectable to the Internet 1 via the NGN 3 and theISP 2 b. Thebases network devices bases bases base 4 b without subscription. Information regarding the subscription with the ISP at each base 4 corresponds to attribute information of this base 4. - The
network device 41 b provided in thebase 4 b with the hub function and is a full mesh type device connectable to each of thenetwork devices 41 connected via the VPN. Therefore, thebase 4 b is also referred to as a “mesh base” in the present exemplary embodiment. Thebase 4 b constructs a mesh VPN while thebases bases bases mesh base 4 b. - The
NOC 5 is a network operation center that is connected to theInternet 1 and is configured to manage address information of the network device connected to theInternet 1. The “address information” is identification information that is specified for identifying a device on the network, and is generally represented by a number. For example, in a case of Internet communication as in the present exemplary embodiment, the address information is an IP address, and an IPv4 format, an IPv6 format, or IPv4 over IPv6 format is used depending on the connection method (PPPoE or IPoE) with theInternet 1, a configuration of theISPs 2 b and 6 orNGNs 3 and 7, and the subscription. - The NGN 3 according to the present exemplary embodiment includes a
management device 31 and aNOC 32. Themanagement device 31 has the above-described function of the information communication network, and performs general management of the NGN 3 such as issuance of the IP address in the NGN 3 or the like. TheNOC 32 is connected so as to be referred to from the NGN 3 and has the same function as that of theNOC 5, but a management range thereof is limited to thenetwork device 41 directly connected to the NGN 3. When thenetwork device 41 is connected to the NGN 3, thenetwork device 41 notifies a set of a name of thenetwork device 41, such as identification information like a domain name, and the IP address to theNOC 32 of the NGN 3 as attribute information of thenetwork device 41. With the set being stored in theNOC 32, thenetwork device 41 becomes a network device to be managed. When the IP address is changed, thenetwork device 41 notifies the set of its name and the changed IP address to theNOC 32 of the NGN 3. The attribute information of thenetwork device 41 also includes information regarding the subscription with the ISP. TheNOC 32 refers to the attribute information of thenetwork device 41 connected to the NGN 3, and responds with the IP address of thenetwork device 41 to be connected in response to a query from thenetwork device 41 to which the name of thenetwork device 41 to be connected is specified. - The ISP 6 and the
NGN 7 are provided in another network system using theInternet 1, and the ISP 6 and theNGN 7 may have an existing function. Of course, theNGN 7 may have a function equivalent to that of the NGN 3. - The
base 8 is a mesh base or a star branch base similarly to the above-described base 4. In terms of the base 4, a computer (not shown) provided in thebase 8 corresponds to an external device connected via theInternet 1. -
FIG. 2 is a schematic hardware configuration diagram of thenetwork device 41 according to the present exemplary embodiment. Thenetwork device 41 according to the present exemplary embodiment includes a computer, and may be implemented by a general-purpose hardware configuration presenting in the related art. Accordingly, as shown inFIG. 2 , thenetwork device 41 includes at least aCPU 21 which is a processor, storage units which are aROM 22, aRAM 23, a hard disk drive (HDD) 24, and the like, and a network interface (IF) 25. Thenetwork device 41 according to the present exemplary embodiment has various functions as network devices, such as a firewall, a gateway, a router, and the like. These functions and functions that are characteristic in the present exemplary embodiment (described below) are implemented by cooperative operation of the computer mounted on thenetwork device 41 and a program operated by theCPU 21 mounted on the computer. - The ISPs 2 and 6, the
NOCs management device 31 according to the present exemplary embodiment are also implemented by a computer, so that the ISPs 2 and 6, theNOCs management device 31 have at least a configuration shown inFIG. 2 . - The program used in the present exemplary embodiment may be provided by means of any communication means as well as by being stored in a computer readable recording medium such as a CD-ROM, a USB memory, or the like. The program provided by means of the communication means or the recording medium is installed in the computer, and is sequentially executed by the CPU of the computer to perform various processing.
- Next, in the present exemplary embodiment, processing when a computer (hereinafter referred to as an “in-base terminal”) provided in the
star branch base 4 a communicates with a computer (hereinafter, referred to as an “external device”) provided in thebase 8 will be described. Processing performed by thenetwork device 41 a in thestar branch base 4 a will be described with reference to a flowchart shown inFIG. 3 . - When receiving a communication request from the in-base terminal, the
network device 41 a broadcasts a request to issue an IP address to the NGN 3 so as to acquire an IP address used by thenetwork device 41 a (step 101). - When receiving the request to issue an IP address from the
network device 41 a, themanagement device 31 in the NGN issues the IP address. As will be described below, if thestar branch base 4 a has a subscription with the ISP, the ISP issues the IP address. However, in the present exemplary embodiment, according to the attribute information of thestar branch base 4 a, thestar branch base 4 a does not have a subscription with the ISP. Therefore the ISP is not an issuance source and the NGN 3 is controlled to be the issuance source. InFIG. 1 , theISP 2 b is provided corresponding to themesh base 4 b, whereas no ISP is provided corresponding to thestar branch base 4 a, which indicates that thestar branch base 4 a does not have a subscription with the ISP. - When the
network device 41 a acquires the IP address in response to the transmitted request to issue an IP address (step 102), thenetwork device 41 a subsequently acquires the IP address of thenetwork device 41 b by sending a request to acquire address information including a name (that is, a domain name of thenetwork device 41 b) of themesh base 4 b which is known, to the NOC 32 (step 103). - In a case where the issuance source of the IP address is NGN3 (YES in step 104), the
network device 41 a performs VPN connection according to a security architecture for IP (IPsec) protocol, and establishes a communication path with thenetwork device 41 b in a network of the NGN 3 (step 105). A method of establishing a communication path is not limited to IPsec, and may be a method of simply adding routing information or a method of constructing a tunnel by the IPsec protocol or an IPIP protocol. Communication between network devices, here, between thenetwork devices FIG. 1 , a path by the intra-network loopback communication is schematically shown by abroken line 11 a. Thenetwork device 41 may identify the issuance source from an IP address system. - Subsequently, the
network device 41 b is connected to theInternet 1 via theISP 2 b. Then, thenetwork device 41 b relays communication of the in-base terminal such that the in-base terminal may communicate with the external device. InFIG. 1 , a communication path between thenetwork device 41 b and the external device is schematically shown by abroken line 11 b. - Accordingly, as indicated by the
broken lines network device 41 a provided in thestar branch base 4 a makes the in-base terminal communicate with the external device by the communication path via thenetwork device 41 provided in themesh base 4 b. In particular, thenetwork device 41 a performs the intra-network loopback communication with thenetwork device 41 b without using the ISP. - In the present exemplary embodiment, the
network device 41 a may acquire the IP address of thenetwork device 41 b by providing theNOC 32 in the NGN 3. However, as another device configured to attain a correspondence between the name of the device and the IP address of the device instead of theNOC 32, for example, a domain name system (DNS) may be provided in the NGN 3. The DNS is also referred to as a “name decision server”, and responds with an IP address of thenetwork device 41 which is an IPv6 address or the like in response to a query in which the domain name of thenetwork device 41 has been specified. - The present exemplary embodiment describes a case in which the issuance source of the IP address is NGN3. However, the issuance source of the IP address may be the ISP in a case where the
star branch base 4 a has a subscription with the ISP. Such a case will also be described. -
FIG. 4 is an overall configuration diagram of a network system when the star branch base 4 has a subscription with the ISP.FIG. 4 is different fromFIG. 1 in that an ISP 2 a corresponding to thestar branch base 4 a is connected to the NGN 3 in terms of the system configuration. - In
FIG. 3 , when the IP address issuance source is the ISP 2 a (NO in step 104), thenetwork device 41 a is connected to the ISP 2 a, and an Internet VPN is established via theISP 2 b (step 106). That is, communication between bases is established between thenetwork device 41 a and thenetwork device 41 b via theISPs 2 a and 2 b as indicated by abroken line 11 c, instead of the intra-network loopback communication indicated by thebroken line 11 a. In a case of the IPoE (native) method, strictly speaking, a virtual network enabler (a VNE) may have issued the IP address to thenetwork device 41. However, it is understood that the IP address issued by the VNE is managed by the ISP, so that thenetwork device 41 recognizes the issuance source as the ISP. - In the present exemplary embodiment, as described above, the
network device 41 a may be mainly operated to establish the intra-network loopback communication between thenetwork device 41 a and thenetwork device 41 b. However, thenetwork device 41 b may also be mainly operated to establish the intra-network loopback communication. This processing will be described with reference to a flowchart shown inFIG. 5 . - In order to establish the communication path, it is necessary to acquire the IP address of the
network device 41 a to be a communicated with, so that thenetwork device 41 b connected to theInternet 1 queries, according to normal operation, to theNOC 5 connected to theInternet 1 for the IP address of thenetwork device 41 a by transmitting a request to acquire the IP address of the network device to be communicated with (step 111). The request to acquire the IP address includes the name of thenetwork device 41 b that identifies the network device. TheNOC 5 identifies thenetwork device 41 a to be communicated with from subscription information or the like. If the network device whose IP address is to be acquired is connected to theInternet 1, theNOC 5 may respond with the IP address of the network device connected to theInternet 1 in response to the request to acquire the IP address. However, thebase 4 a does not have a subscription with the ISP and is not connected to theInternet 1, so that theNOC 5 does not manage the IP address of thenetwork device 41 a. In this case, theNOC 5 responds with information indicating that the IP address cannot be acquired. In the present exemplary embodiment, theNOC 5 responds with, as the information indicating that the IP address is unavailable, the name of thenetwork device 41 a that includes the domain name and the like identifying the NGN 3 to which thenetwork device 41 a to be communicated with is connected. - The
network device 41 b receives a response from theNOC 5 in response to the request to acquire the IP address (step 112). If the response is the name of the network device (YES in step 113), the NGN 3 is identified from this information, and the request to acquire the IP address of thenetwork device 41 a is transmitted to theNOC 32 of the identified NGN 3 (step 114). The request to acquire the IP address includes the name of thenetwork device 41 which is the domain name or the like. TheNOC 32 manages the set including the name and the IP address of thenetwork device 41 in the NGN 3, so that theNOC 32 responds with the IP address of thenetwork device 41 a in response to the request to acquire the IP address. - When the
network device 41 b acquires the IP address of thenetwork device 41 a (step 115), thenetwork device 41 b establishes a path for performing the intra-network loopback communication with thenetwork device 41 a in the NGN 3. The method of establishing the communication path may be the method of simply adding routing information or the method of constructing a tunnel by the IPsec protocol or the IPIP protocol. After the path is established, the intra-network loopback communication may be performed between thenetwork device 41 a and thenetwork device 41 b. - If the
network device 41 b has transmitted the request to acquire the IP address of the network device connected to theInternet 1, theNOC 5 responds with the IP address of the network device connected to theInternet 1 in response to the request to acquire the IP address. When thenetwork device 41 b acquires the IP address from the NOC 5 (NO in step 113), thenetwork device 41 b establishes the communication with the network device via the Internet 1 (step 117). - The NGN 3 responds to the request to issue an IP address from the
network device 41 b, so that a provider 2 a issues the IP address when thestar branch base 4 a has an IPoE-type provider subscription and the NGN 3 issues the IP address when thestar branch base 4 a does not have the IPoE-type provider subscription. In this case, when the IP address has been issued from the provider 2 a, thenetwork device 41 b performs the VPN connection with thenetwork device 41 a by an Internet VPN method. On the other hand, when the IP address has been issued from the NGN 3, thenetwork device 41 b performs the VPN connection with thenetwork device 41 a by intra-network loopback. - In the above description, the case of connecting to the
Internet 1 according to the IPoE method has been described as an example. Here, a case of connecting to theInternet 1 according to the PPPoE method will be described. - In contrast to the configuration shown in
FIG. 1 , the ISPs 2 a to 2 c are respectively associated with thebases 4 a to 4 c inFIG. 6 . That is, each base 4 has a subscription with the ISP 2 to connect to theInternet 1 according to the PPPoE method. According to the subscription with the ISP 2,network termination devices 32 a to 32 c are provided in the NGN 3 corresponding to the ISPs 2 a to 2 c. The number of thenetwork termination devices 32 a to 32 c provided corresponding to the ISPs 2 a to 2 c and the ISP 2 to be a contract destination are not particularly described. - Here, as described with reference to the flowchart shown in
FIG. 3 , when thenetwork device 41 a broadcasts the request to issue an IP address to the NGN 3 (step 101), the ISP 2 a becomes the issuance source of the IP address1 since thestar branch base 4 a has a subscription with the ISP 2 a. In a case where the ISP 2 a is the issuance source of the IP address (NO in step 104), the Internet VPN is established between thenetwork device 41 a and thenetwork device 41 b. That is, thenetwork device 41 a is connected to the ISP 2 a via thenetwork termination device 32 a. Thenetwork device 41 b is connected to theISP 2 b via thenetwork termination device 32 b. A communication path by the Internet VPN established as described above is indicated by abroken line 11 d. A procedure of establishing a communication path between thenetwork device 41 b and the external device is the same as that using the IPoE method, so that a description thereof will be omitted. The communication path between thenetwork device 41 b and the external device is schematically shown by abroken line 11 b. - As described above, in a case of using the PPPoE method, the in-base terminal in the
star branch base 4 a communicates with the external device throughpaths FIG. 6 . At this time, when the communication by thepath 11 d, that is, the communication between thestar branch base 4 a and themesh base 4 b via the Internet VPN is performed, it is necessary to pass through thenetwork termination device 32 three times, that is, to pass through thenetwork termination device 32 a when exiting from the NGN 3 to the ISP 2 a, to pass through thenetwork termination device 32 b when entering the NGN 3 from the ISP 2 a via theISP 2 b, and to pass through thenetwork termination device 32 b when exiting from the NGN 3 to theISP 2 b. - The
network termination device 32 is said to cause a decrease in communication speed and instability. However, if the intra-network loopback communication indicated by thebroken line 11 a is performed between thenetwork device 41 a and thenetwork device 41 b, thenetwork termination device 32 may be passed only once. That is, when the communication is performed from the in-base terminal to the external device, the decrease in communication speed and the instability may be prevented by implementing the intra-network loopback communication in the NGN 3. - In order to show a difference between the communication between the base 4 a and the
base 4 b via the Internet VPN and that via the intra-network loopback communication,FIG. 4 shows a configuration in which the ISPs 2 a and 2 c, and thenetwork termination device 32 are provided. However, since the intra-network loopback communication is implemented, subscriptions with the ISPs 2 a and 2 c at thestar branch bases network termination device 32 becomes unnecessary. Accordingly, the intra-network loopback communication may improve not only the communication speed but also the cost efficiency. - In the exemplary embodiments above, the term “processor” refers to hardware in a broad sense. Examples of the processor includes general processors (e.g., CPU: Central Processing Unit), dedicated processors (e.g., GPU: Graphics Processing Unit, ASIC: Application Integrated Circuit, FPGA: Field Programmable Gate Array, and programmable logic device).
- In the exemplary embodiments above, the term “processor” is broad enough to encompass one processor or plural processors in collaboration which are located physically apart from each other but may work cooperatively. The order of operations of the processor is not limited to one described in the exemplary embodiments above, and may be changed.
- The foregoing description of the exemplary embodiments of the present invention has been provided for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Obviously, many modifications and variations will be apparent to practitioners skilled in the art. The exemplary embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, thereby enabling others skilled in the art to understand the invention for various exemplary embodiments and with the various modifications as are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the following claims and their equivalents.
Claims (12)
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2019170685A JP2021048526A (en) | 2019-09-19 | 2019-09-19 | Network system, network operations center, network device, and program |
JP2019-170685 | 2019-09-19 | ||
JPJP2019-170685 | 2019-09-19 |
Publications (2)
Publication Number | Publication Date |
---|---|
US20210091977A1 true US20210091977A1 (en) | 2021-03-25 |
US11082260B2 US11082260B2 (en) | 2021-08-03 |
Family
ID=69845915
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/846,391 Active US11082260B2 (en) | 2019-09-19 | 2020-04-12 | Network system, network device, and recording medium |
Country Status (4)
Country | Link |
---|---|
US (1) | US11082260B2 (en) |
EP (1) | EP3796602B1 (en) |
JP (1) | JP2021048526A (en) |
CN (1) | CN112532502A (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20210344591A1 (en) * | 2020-05-01 | 2021-11-04 | Cisco Technology, Inc. | Detecting and communicating with silent hosts in software-defined networks |
Family Cites Families (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP4236398B2 (en) * | 2001-08-15 | 2009-03-11 | 富士通株式会社 | Communication method, communication system, and communication connection program |
KR100485801B1 (en) * | 2002-03-07 | 2005-04-28 | 삼성전자주식회사 | Network connecting apparatus and method for offering direct connection between network devices existing different private networks |
US20050091311A1 (en) * | 2003-07-29 | 2005-04-28 | Lund Christopher D. | Method and apparatus for distributing multimedia to remote clients |
US7568047B1 (en) * | 2004-04-30 | 2009-07-28 | Nortel Networks Limited | Method and apparatus for adaptive service label management |
US7715310B1 (en) * | 2004-05-28 | 2010-05-11 | Cisco Technology, Inc. | L2VPN redundancy with ethernet access domain |
EP1782572B1 (en) * | 2004-07-29 | 2010-01-27 | Telecom Italia S.p.A. | Method and system for fault and performance recovery in communication networks, related network and computer program product therefor |
DE102006009988B4 (en) * | 2006-03-03 | 2007-12-27 | Siemens Ag | Communication system, computer and method for determining a communication protocol to be used in a communication system |
WO2007104324A1 (en) * | 2006-03-13 | 2007-09-20 | Telefonaktiebolaget Lm Ericsson (Publ) | Method of controlling packet data traffic |
US7844719B2 (en) * | 2007-02-13 | 2010-11-30 | Cisco Technology, Inc. | Tunnel availability detection with reduced control plane overhead |
US8346961B2 (en) * | 2007-12-12 | 2013-01-01 | Cisco Technology, Inc. | System and method for using routing protocol extensions for improving spoke to spoke communication in a computer network |
JP2012039218A (en) | 2010-08-04 | 2012-02-23 | Nippon Telegr & Teleph Corp <Ntt> | Rendezvous server device, and communication system, and communication method, and communication program |
JP5672154B2 (en) * | 2011-05-31 | 2015-02-18 | 株式会社バッファロー | Network system, gateway device, route determination method, program, and storage medium |
US8694674B2 (en) * | 2011-09-29 | 2014-04-08 | Mckesson Financial Holdings | Systems, methods, apparatuses, and computer program products for supporting remote hosting without using network address translation |
US8891450B2 (en) * | 2012-02-06 | 2014-11-18 | Juniper Networks, Inc. | Mobile node host route installation and withdrawal |
US9788188B2 (en) * | 2012-12-14 | 2017-10-10 | Ibasis, Inc. | Method and system for hub breakout roaming |
JP6047480B2 (en) * | 2013-12-17 | 2016-12-21 | 日本電信電話株式会社 | Session establishment method |
US9838268B1 (en) * | 2014-06-27 | 2017-12-05 | Juniper Networks, Inc. | Distributed, adaptive controller for multi-domain networks |
US10200258B2 (en) * | 2014-08-14 | 2019-02-05 | Juniper Networks, Inc. | Transaction integrity for network services configuration |
US10659349B2 (en) * | 2016-02-04 | 2020-05-19 | Twilio Inc. | Systems and methods for providing secure network exchanged for a multitenant virtual private cloud |
US10291462B1 (en) * | 2017-01-03 | 2019-05-14 | Juniper Networks, Inc. | Annotations for intelligent data replication and call routing in a hierarchical distributed system |
US11533100B2 (en) * | 2017-12-19 | 2022-12-20 | Digital Path, Inc. | Wireless internet access system and method of using the same |
EP3544310A1 (en) * | 2018-03-23 | 2019-09-25 | Deutsche Telekom AG | Method for an improved operation of a telecommunications network being operated as a multi-operator sliced network, telecommunications network, system, provider infrastructure control center, network of a service provider, program and computer-readable medium |
-
2019
- 2019-09-19 JP JP2019170685A patent/JP2021048526A/en active Pending
-
2020
- 2020-03-18 CN CN202010190509.2A patent/CN112532502A/en active Pending
- 2020-03-18 EP EP20163886.3A patent/EP3796602B1/en active Active
- 2020-04-12 US US16/846,391 patent/US11082260B2/en active Active
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20210344591A1 (en) * | 2020-05-01 | 2021-11-04 | Cisco Technology, Inc. | Detecting and communicating with silent hosts in software-defined networks |
US11316782B2 (en) * | 2020-05-01 | 2022-04-26 | Cisco Technology, Inc. | Detecting and communicating with silent hosts in software-defined networks |
US11799767B2 (en) | 2020-05-01 | 2023-10-24 | Cisco Technology, Inc. | Detecting and communicating with silent hosts in software-defined networks |
Also Published As
Publication number | Publication date |
---|---|
JP2021048526A (en) | 2021-03-25 |
CN112532502A (en) | 2021-03-19 |
US11082260B2 (en) | 2021-08-03 |
EP3796602B1 (en) | 2023-08-30 |
EP3796602A1 (en) | 2021-03-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10454879B2 (en) | Methods and systems for processing a DNS request | |
EP2499787B1 (en) | Smart client routing | |
US8548132B1 (en) | Lawful intercept trigger support within service provider networks | |
KR101341728B1 (en) | System, method and program for determining failed routers in a network | |
US10375193B2 (en) | Source IP address transparency systems and methods | |
US8543706B2 (en) | Communication module for connecting application program to virtual private network | |
KR20110098824A (en) | Secure remote access public communication environment | |
EP3576347B1 (en) | Network device snapshots | |
US10848457B2 (en) | Method and system for cross-zone network traffic between different zones using virtual network identifiers and virtual layer-2 broadcast domains | |
WO2004036831A2 (en) | Determining a path through a managed network | |
US10855733B2 (en) | Method and system for inspecting unicast network traffic between end points residing within a same zone | |
US11082260B2 (en) | Network system, network device, and recording medium | |
CN116170409B (en) | SD-WAN network address planning system based on virtual domain name | |
US20200287784A1 (en) | Priority based selection of time services | |
US20190036817A1 (en) | Transport network control apparatus, communication system, forwarding node control method, and program | |
US8285853B2 (en) | Message and system for implementing the inter-access of stack members | |
CN114268578A (en) | Data transmission method, device and equipment for switching line and storage medium | |
WO2023134350A1 (en) | Message sending method, message receiving method, information sending method, and apparatus | |
US11792718B2 (en) | Authentication chaining in micro branch deployment | |
US20230239359A1 (en) | Integrated broadband network gateway (bng) device for providing a bng control plane for one or more distributed bng user plane devices | |
US10749789B2 (en) | Method and system for inspecting broadcast network traffic between end points residing within a same zone | |
WO2018015785A1 (en) | Method and apparatus for network gateway disaggregation | |
WO2024073113A1 (en) | System and method for creating a private service access network | |
CN118353832A (en) | Stream table processing method, stream table processing device, stream table processing computer, stream table processing storage medium and stream table processing program product |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
AS | Assignment |
Owner name: FUJI XEROX CO., LTD., JAPAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:TAKEDA, KOJI;IKENAGA, HIROKI;REEL/FRAME:052374/0764 Effective date: 20200407 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
AS | Assignment |
Owner name: FUJIFILM BUSINESS INNOVATION CORP., JAPAN Free format text: CHANGE OF NAME;ASSIGNOR:FUJI XEROX CO., LTD.;REEL/FRAME:056192/0246 Effective date: 20210401 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT RECEIVED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |