WO2015029418A1 - Appareil et procédé de communication dans un système de communication, et appareil et procédé de commande de voies de communication - Google Patents

Appareil et procédé de communication dans un système de communication, et appareil et procédé de commande de voies de communication Download PDF

Info

Publication number
WO2015029418A1
WO2015029418A1 PCT/JP2014/004364 JP2014004364W WO2015029418A1 WO 2015029418 A1 WO2015029418 A1 WO 2015029418A1 JP 2014004364 W JP2014004364 W JP 2014004364W WO 2015029418 A1 WO2015029418 A1 WO 2015029418A1
Authority
WO
WIPO (PCT)
Prior art keywords
communication
communication path
virtual
gateway
plane
Prior art date
Application number
PCT/JP2014/004364
Other languages
English (en)
Japanese (ja)
Inventor
一平 秋好
Original Assignee
日本電気株式会社
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 日本電気株式会社 filed Critical 日本電気株式会社
Priority to JP2015533991A priority Critical patent/JP6500777B2/ja
Publication of WO2015029418A1 publication Critical patent/WO2015029418A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers

Definitions

  • the present invention relates to a communication system that communicates between communication devices via a communication path, and more particularly to control of a communication path.
  • a communication terminal such as a mobile phone can communicate with a base station and access the Internet via a core network.
  • the communication terminal communicates with a device (for example, a gateway) provided in the core network via a communication path (for example, a bearer) established.
  • a device for example, a gateway
  • a communication path for example, a bearer
  • a core network node for example, a gateway
  • a core network node for example, a gateway
  • the procedure for establishing a communication path is described in, for example, Chapter 5.3.2 of Non-Patent Document 1.
  • GPRS General Packet Packet Radio Service
  • a core network node such as a gateway is assigned to the established communication path. Therefore, when switching the path of a communication path, it is assumed that a communication path re-establishment procedure is executed in order to reassign a core network node to a new communication path.
  • a communication path re-establishment procedure is executed, various influences on the communication service are assumed, for example, the communication executed on the communication path before switching is interrupted.
  • an object of the present invention is to provide a communication technique and a communication path control technique capable of suppressing the influence on the communication service when switching the communication path route.
  • the communication device of the present invention is a communication device that communicates through a communication path set in a network, and is identified by an identification rule for identifying a communication flow based on information including a communication path identifier, and the identification rule.
  • a first processing unit capable of receiving a processing rule including a processing rule indicating that the received packet is transferred to a gateway corresponding to the communication path identifier; and a communication path identifier of the received packet based on the processing rule.
  • second means capable of transferring the received packet to the corresponding gateway.
  • the control device of the present invention is a control device capable of controlling a communication device communicating via a communication path set in a network, and a first means capable of managing a correspondence relationship between the communication path and the gateway; An identification rule for identifying a communication flow based on information including a communication path identifier, and a processing rule indicating that a packet identified by the identification rule is transferred to a gateway corresponding to the communication path identifier And a second means capable of notifying the communication device of the processing rule.
  • the communication method of the present invention is a communication method for communicating via a communication path set in a network, and is identified by an identification rule for identifying a communication flow based on information including a communication path identifier, and the identification rule.
  • the reception packet is transferred.
  • the control method of the present invention is a control method for controlling a communication device that communicates via a communication path set in a network, and manages a correspondence relationship between the communication path and the gateway, and includes information including a communication path identifier
  • the present invention it is possible to suppress the influence on the communication service when switching the communication path, and it is possible to provide a technology capable of various communication quality control.
  • FIG. 1 is a system configuration diagram showing an example of a communication system to which the first embodiment of the present invention is applied.
  • FIG. 2 is a schematic diagram showing an example of a communication path in the communication system shown in FIG.
  • FIG. 3 is a block diagram showing a first example of a communication system according to the first embodiment of the present invention.
  • FIG. 4 is a block diagram showing a second example of the communication system according to the first embodiment of the present invention.
  • FIG. 5 is a block diagram showing a third example of the communication system according to the first embodiment of the present invention.
  • FIG. 6 is a sequence diagram showing an operation example of the communication apparatus according to the first embodiment of the present invention.
  • FIG. 7 is a block diagram showing a configuration of a control device according to the second embodiment of the present invention.
  • FIG. 1 is a system configuration diagram showing an example of a communication system to which the first embodiment of the present invention is applied.
  • FIG. 2 is a schematic diagram showing an example of a communication path in the communication system shown
  • FIG. 8 is a block diagram showing an example of the route information DB in the control device according to the second embodiment of the present invention.
  • FIG. 9 is a block diagram showing an example of a communication apparatus according to the second embodiment of the present invention.
  • FIG. 10 is a schematic configuration diagram for explaining a functional configuration of a communication device according to the third embodiment of the present invention.
  • FIG. 11 is a system configuration diagram showing a first example of a communication system according to the third embodiment of the present invention.
  • FIG. 12 is a system configuration diagram showing a second example of the communication system according to the third embodiment of the present invention.
  • FIG. 13 is a system configuration diagram showing a third example of the communication system according to the third embodiment of the present invention.
  • FIG. 14 is a block diagram showing a first example of the route information DB in the control device according to the third embodiment of the present invention.
  • FIG. 15 is a block diagram showing a first example of the route information DB in the communication device according to the third embodiment of the present invention.
  • FIG. 16 is a schematic system configuration diagram for explaining a first operation example of the communication system according to the third embodiment of the present invention.
  • FIG. 17 is a block diagram showing a second example of the route information DB in the control device according to the third embodiment of the present invention.
  • FIG. 18 is a block diagram showing a second example of the route information DB in the communication apparatus according to the third embodiment of the present invention.
  • FIG. 19 is a schematic system configuration diagram for explaining a second operation example of the communication system according to the third embodiment of the present invention.
  • FIG. 20 is a schematic system configuration diagram for explaining a third operation example of the communication system according to the third embodiment of the present invention.
  • FIG. 21 is a sequence diagram showing a first operation example of the communication system according to the fourth exemplary embodiment of the present invention.
  • FIG. 22 is a sequence diagram showing a second operation example of the communication system according to the fourth exemplary embodiment of the present invention.
  • FIG. 23 is a sequence diagram showing a third operation example of the communication system according to the fourth embodiment of the present invention.
  • FIG. 24 is a sequence diagram showing a fourth operation example of the communication system according to the fourth exemplary embodiment of the present invention.
  • FIG. 25 is a sequence diagram showing a fifth operation example of the communication system according to the fourth embodiment of the present invention.
  • FIG. 21 is a sequence diagram showing a first operation example of the communication system according to the fourth exemplary embodiment of the present invention.
  • FIG. 22 is a sequence diagram showing a second operation example of the communication system according to the fourth exemplary embodiment of the present invention.
  • FIG. 26 is a sequence diagram showing a seventh operation example of the communication system according to the fourth exemplary embodiment of the present invention.
  • FIG. 27 is a sequence diagram showing an eighth operation example of the communication system according to the fourth exemplary embodiment of the present invention.
  • FIG. 28 is a sequence diagram showing a ninth operation example of the communication system according to the fourth exemplary embodiment of the present invention.
  • FIG. 29 is a sequence diagram showing a tenth operation example of the communication system according to the fourth exemplary embodiment of the present invention.
  • FIG. 30 is a system configuration diagram showing a first example of a communication system according to a fifth embodiment of the present invention.
  • FIG. 31 is a block diagram showing a configuration of a control device according to the fifth embodiment of the present invention.
  • FIG. 32 is a block diagram showing an example of a flow entry DB in the control device according to the fifth embodiment of the present invention.
  • FIG. 33 is a block diagram showing a configuration of a communication apparatus according to the fifth embodiment of the present invention.
  • FIG. 34 is a schematic system configuration diagram for explaining the operation of the communication system according to the sixth embodiment of the present invention.
  • FIG. 35 is a block diagram showing a first example of the route information DB in the control device according to the sixth embodiment of the present invention.
  • FIG. 36 is a block diagram showing a second example of the route information DB in the control device according to the sixth embodiment of the present invention.
  • FIG. 37 is a block diagram showing a third example of the route information DB in the control device according to the sixth embodiment of the present invention.
  • FIG. 38 is a block diagram showing a fourth example of the route information DB in the control device according to the sixth embodiment of the present invention.
  • FIG. 39 is a block diagram showing a fifth example of the route information DB in the control device according to the sixth embodiment of the present invention.
  • FIG. 40 is a schematic system configuration diagram for explaining a first example of the operation of the communication system according to the seventh embodiment of the present invention.
  • FIG. 41 is a block diagram showing a configuration of a control device according to the seventh embodiment of the present invention.
  • FIG. 42 is a block diagram showing an example of a policy DB of the control device according to the seventh embodiment of the present invention.
  • FIG. 43 is a schematic system configuration diagram for explaining a second example of the operation of the communication system according to the seventh embodiment of the present invention.
  • FIG. 40 is a schematic system configuration diagram for explaining a first example of the operation of the communication system according to the seventh embodiment of the present invention.
  • FIG. 41 is a block diagram showing a configuration of a control device
  • FIG. 44 is a block diagram showing an example of a policy DB of the control device in the communication system shown in FIG.
  • FIG. 45 is a schematic system configuration diagram for explaining a third example of the operation of the communication system according to the seventh embodiment of the present invention.
  • 46 is a block diagram showing an example of a policy DB of the control device in the communication system shown in FIG.
  • FIG. 47 is a block diagram showing a first example of a management apparatus according to the eighth embodiment of the present invention.
  • FIG. 48 is a block diagram showing a second example of the management apparatus according to the eighth embodiment of the present invention.
  • FIG. 49 is a schematic diagram showing an example of a user interface of the management device according to the eighth embodiment of the present invention.
  • FIG. 50 is a block diagram showing a third example of the management apparatus according to the eighth embodiment of the present invention.
  • FIG. 51 is a schematic diagram showing a first example of a user interface of the management device according to the ninth embodiment of the present invention.
  • FIG. 52 is a block diagram showing a first example of the route information DB in the management device according to the ninth embodiment of the present invention.
  • FIG. 53 is a schematic diagram showing a second example of the user interface of the management device according to the ninth embodiment of the present invention.
  • FIG. 54 is a block diagram showing a second example of the route information DB in the management device according to the ninth embodiment of the present invention.
  • FIG. 55 is a schematic diagram showing a third example of the user interface of the management device according to the ninth embodiment of the present invention.
  • FIG. 56 is a block diagram showing a third example of the path information DB in the management apparatus according to the ninth embodiment of the present invention.
  • LTE Long Term Evolution
  • UMTS Universal Mobile Telecommunication System
  • the communication system includes a mobile phone, a PC (Personal Computer), a mobile router terminal (Mobile Terminal) 1, a base station (eNB) 2, and a gateway 3.
  • the base station 2 provides a radio access function to the terminal 1.
  • the gateway 3 is a network node such as S-GW (Serving Gateway) or P-GW (Packet Data Network Gateway).
  • the gateway 3 may be SGSN (Serving GPRS Support Node) or GGSN (Gateway GPRS Support Node).
  • the gateway 3 provides, for example, a function for terminating a communication path (for example, bearer) set in a network and a function as a connection point with an external network (for example, the Internet).
  • the terminal 1 transmits and receives data via a communication path (for example, a bearer) established between the terminal 1 and the gateway 3.
  • the communication path includes, for example, a wireless channel established between the terminal 1 and the base station and a GTP (GPRS Tunneling Protocol) tunnel that terminates at the gateway 3 (endpoint).
  • GTP GPRS Tunneling Protocol
  • a communication device 4 capable of switching the path of a communication path between the base station 2 and the gateway 3 or between the S-GW and the P-GW. Is placed.
  • the communication device 4 can switch the packet transfer path so that the packet belonging to the communication path passes through the switched gateway 3.
  • the communication device 4 By switching the packet transfer path on the path of the communication path by the communication device 4, it becomes possible to conceal the switching of the gateway from the terminal 1. Therefore, even if the gateway 3 corresponding to the communication path is switched, the communication system can avoid executing the communication path re-establishment procedure.
  • the communication device 4 can switch a plurality of gateways, a case where three gateways are switched will be described as an example in order to avoid complication of the following description.
  • the communication device 4 includes a communication path identification unit 40 and a switching unit 41, and can switch between the gateways 3 (a), 3 (b), and 3 (c) according to the communication path. And
  • the communication path identification unit 40 identifies the communication path to which the received packet belongs. For example, the communication path identification unit 40 identifies a communication path to which a received packet belongs based on a communication path identifier such as a TEID (Tunnel Endpoint Identifier) or a GRE (Generic Routing Encapsulation) key.
  • a communication path identifier such as a TEID (Tunnel Endpoint Identifier) or a GRE (Generic Routing Encapsulation) key.
  • the switching unit 41 transfers the received packet to the gateway 3 corresponding to the communication path identified by the communication path identifier.
  • the switching unit 41 has a function of managing the correspondence relationship between the communication path and the gateway 3, and transfers the received packet to the corresponding gateway 3 based on the correspondence relationship.
  • the switching unit 41 sets the received packet (A) to the gateway 3 (a), the received packet (B) to the gateway 3 (b), and the received packet (C) to the gateway (c). Forward.
  • a gateway 3A can be configured on the server 33 by software such as a virtual machine (VM), and the communication device 4 can transfer a received packet to the gateway 3A.
  • the server 33 can construct a plurality of virtual gateways 3A according to, for example, the load on the communication system.
  • the switching unit 41 transfers the received packet to the corresponding virtual gateway based on the correspondence relationship between the communication path and the virtual gateway.
  • the above-described functions of the communication device 4 can be realized by a virtual switch 4 ⁇ / b> A constructed on the server 33. That is, in the example of FIG. 5, the server 33 can operate as the communication device 4. That is, the virtual switch 4A and the virtual gateway (gateway 3A) can be configured by software such as VM on the control unit (not shown) of the server 33.
  • the communication path identifying unit 40 of the virtual switch 4A identifies the communication path to which the received packet belongs, and the switching unit 41 of the virtual switch 4A transfers the received packet to the virtual gateway 3A corresponding to the identified communication path.
  • FIGS. 3 to 5 Although only one communication device 4 (virtual switch 4A) is shown in FIGS. 3 to 5, a plurality of communication devices 4 may be used. Further, the communication device 4 and the virtual switch 4A may be used in combination.
  • the communication path identification unit 40 identifies the communication path to which the received packet belongs (operation S2). For example, the communication path identifying unit 40 identifies the communication path to which the received packet belongs based on a communication path identifier such as TEID or GRE Key.
  • the switching unit 41 of the communication device 4 transfers the received packet to the gateway 3 corresponding to the identified communication path (operation S3).
  • the communication apparatus 4 switches the packet transfer path on the path of the communication path, so that the communication system conceals the switching of the gateway 3 corresponding to the communication path from the terminal 1. It becomes possible. Therefore, even if the gateway 3 corresponding to the communication path is switched, the communication system can avoid executing the communication path re-establishment procedure.
  • Second Embodiment A second embodiment of the present invention is applicable to the communication system illustrated in FIG.
  • the communication device 4 in the communication system according to the second embodiment can switch the communication path according to the instruction notified from the control device 5 as in the first embodiment described above. Since the control device 5 can centrally control the operation of the communication device 4, the operation efficiency of the system is improved.
  • the control device 5 includes a route information DB (database) 50, a control unit 51, and a communication interface 52.
  • the communication interface 52 has a function of communicating with the communication device 4.
  • the communication interface 52 can communicate with the communication device 4 using a protocol such as OpenFlow, ForCES (Forwarding and Control Element Separation), or I2RS (Interface to Routing System).
  • the route information DB 50 is a database for managing the correspondence between the communication path and the gateway 3.
  • the control unit 51 has a function of generating information stored in the route information DB 50 and a function of controlling the communication device 4 via the communication interface 52 based on information stored in the route information DB 50.
  • the route information DB 50 stores correspondence information between each communication path and the corresponding gateway.
  • a communication path identifier such as TEID or GRE Key can be used, and the corresponding gateway 3 can be managed based on each communication path identifier.
  • the control unit 51 controls the communication device 4 based on information managed by the route information DB 50. For example, the control unit 51 notifies the correspondence between the communication path and the gateway 3 to the switching unit 41 of the communication device 4 based on the route information DB 50.
  • the communication device 4 may be provided with a route information DB 42 to store the route information notified from the control device 5.
  • the communication path identifying unit 40 and the switching unit 41 of the communication device 4 refer to the route information DB 42 and transfer the packet to the gateway 3 corresponding to the communication path to which the packet belongs.
  • the control unit 51 of the control device 5 notifies the communication device 4 of the changed correspondence information.
  • the communication device 4 stores the notified information in the route information DB 42.
  • the control unit 51 of the control device 5 can also operate the gateway 3A (illustrated in FIG. 5), which is a virtual gateway, on the server 33 illustrated in FIG. That is, in response to the activation instruction from the control unit 51, the server 33 activates an application having a function corresponding to the gateway 3 on the virtual machine.
  • the gateway 3A illustrated in FIG. 5
  • the server 33 activates an application having a function corresponding to the gateway 3 on the virtual machine.
  • the control device 5 can be configured by using, for example, a PCRF (Policy and Charging Rule Function), an MME (Mobility Management Entity), or an NMS (Network Management System) of the LTE communication system.
  • the MME has a function of controlling the establishment and deletion of bearers, a mobility control such as a handover of the terminal 1, and a user authentication of the terminal 1.
  • the PCRF has functions such as policy control such as QoS and charging control for data transfer.
  • the gateway executes policy control based on the notification information from the PCRF.
  • the NMS has functions such as network traffic monitoring and network device alive monitoring.
  • a third embodiment of the present invention is applicable to any technique disclosed in the first embodiment or the second embodiment described above.
  • the function of the gateway 3 is virtually configured by software such as VM.
  • the communication system is usually designed so as to have a capability to withstand a peak load. Therefore, there is a possibility that a dedicated appliance (for example, a gateway device or the like) constituting the communication system becomes redundant with respect to the non-peak traffic.
  • a dedicated appliance for example, a gateway device or the like
  • One solution to this problem is to configure the functions of a dedicated appliance such as a gateway device by software such as a virtual machine. For example, it is possible to construct a system according to the state of the communication system by adding a virtual machine having a function of a dedicated appliance according to the communication amount of the communication system.
  • the gateway 3 when the function of the gateway 3 is dynamically scaled out, it is possible to switch the gateway 3 corresponding to the communication path.
  • the communication device 4 switches the packet transfer path on the communication path, the communication device 4 can conceal the switching of the gateway 3 corresponding to the communication path from the terminal 1. Therefore, even if the gateway 3 corresponding to the communication path is switched, the communication system can avoid executing the communication path re-establishment procedure.
  • the third embodiment of the present invention will be described below with reference to the examples of FIGS.
  • the gateway 3 has a control plane (C-Plane) and a user plane (U-Plane).
  • C-Plane has a function of processing a control signal transmitted in the communication system.
  • U-Plane has a function of processing data transmitted in a communication system.
  • C-Plane and U-Plane can communicate with each other via different interfaces 32.
  • an IP address is assigned to each interface.
  • a communication path (for example, a bearer) is established between the gateway 3 and the terminal 1.
  • the gateway 3 communicates using, for example, an IP address assigned to the interface 32.
  • the gateway 3 constructs a tunnel (for example, a GTP tunnel or a GRE tunnel) for establishing a communication path.
  • the gateway 3 described above is configured as a virtual gateway 3A by software such as VM.
  • the virtual gateway 3A is constructed on the server 33, for example.
  • C-Plane and U-Plane are configured by software such as VM.
  • the functions corresponding to C-Plane and U-Plane are labeled “virtual C-plane 30” and “virtual U-plane 31”, respectively.
  • the virtual C-plane 30 and the virtual U-plane 31 can communicate with each other through an internal interface.
  • the operator of the communication system can add a virtual C-plane 30 and a virtual U-plane 31 according to the load of the communication system, for example. Since the virtual C-plane 30 and the virtual U-plane 31 are configured by software, the operator can add gateways more easily and at a lower cost than when the gateway 3 of the hardware device is added.
  • the virtual C-Plane 30 and the virtual U-Plane 31 each operate as a network node that provides a function for terminating a communication path and a function as a connection point with an external network.
  • the virtual gateway 3A when an IP address is assigned to each interface 32 like the gateway 3, a virtual C-plane or a virtual U-plane is added.
  • communication path reconstruction occurs.
  • the virtual U-plane 31 when the virtual U-plane 31 is added, a new IP address is assigned to the interface 32 of the added virtual U-plane 31.
  • the IP address corresponding to the communication path is changed to the IP address assigned to the added virtual U-plane 31.
  • communication path reconstruction occurs.
  • each function constituting the communication system such as eNB, SGW, or PGW executes a communication path reconstruction procedure. Therefore, it is assumed that the communication path is reconstructed every time the virtual C-plane 30 or the virtual U-plane 31 is added, and the influence on the performance of the communication system is increased.
  • addresses commonly assigned to a plurality of virtual C-Planes and a plurality of virtual U-Planes are not limited to IP addresses, and may be MAC addresses, for example.
  • the first example of the communication system according to the third embodiment of the present invention includes a virtual gateway 3A, a communication device 4, and a control device 5.
  • the virtual gateway 3A can configure a virtual C-plane 30 and a virtual U-plane 31 by software such as VM.
  • a virtual C-plane 30 and a virtual U-plane 31 are configured on the server by software such as VM.
  • the control device 5 manages the correspondence between the communication path and the virtual gateway 3A.
  • the control device 5 has a function of managing the correspondence between the communication path and the virtual U-plane 31.
  • the control device 5 has a function of managing the correspondence between the communication path and the virtual C-Plane 30.
  • the control device 5 has a function of controlling the operation of the communication device 4. As already described, the control device 5 identifies the communication path to which the received packet belongs, and instructs the communication device 4 to transfer the received packet to the virtual U-Plane 31 corresponding to the identified communication path.
  • the control device 5 can also operate the virtual gateway 3A (or virtual C-Plane 30 or virtual U-Plane 31) on the server 33.
  • the control device 5 can instruct the server 33 to start the virtual gateway 3A.
  • the server 33 activates an application having a function corresponding to the gateway 3 on the virtual machine in response to an activation instruction from the control device 5.
  • the control device 5 can also control the virtual U-Plane 31 in parallel with the communication device 4. For example, in order to switch the virtual U-Plane 31 corresponding to the communication path, the control device 5 controls the communication device 4 to switch the packet transfer path on the path of the communication path, and also switches the virtual U-Plane 31 of the switching destination. -Perform control for terminating the communication path in Plane 31. For example, the control unit 51 of the control device 5 notifies the virtual U-Plane 31 of information (for example, a communication path identifier) related to a communication path in which the virtual U-Plane 31 is newly terminated by route switching.
  • information for example, a communication path identifier
  • the function of the communication device 4 is configured on the server 33 by software such as VM. That is, in the example of FIG. 12, the server 33 can operate as the communication device 4.
  • the server 33 includes, for example, a control unit (not shown in FIG. 12) that can activate the virtual gateway 3A on the server 33.
  • the virtual gateway 3A the virtual C-Plane 30, the virtual U-Plane 31, and the virtual switch 4A are built on the server 33, and the function of the communication device 4 is built on the server 33 as the virtual switch 4A.
  • the server 33 includes a virtual switch 4A that can operate as the communication device 4 as in the example of FIG. Are configured on the server 33 by software such as VM.
  • the function of the control device 5 is constructed on the server 33 as the virtual controller 5A.
  • the server 33 includes, for example, a control unit (not shown in FIG. 13) that can activate at least one of the virtual switch 4A, the virtual gateway 3A, or the virtual controller 5A on the server 33.
  • the virtual gateway 3A includes a virtual C-Plane 30, a virtual U-Plane 31, a virtual switch 4A, and a virtual controller 5A.
  • the server 33 can operate as the control device 5 having at least one function of the virtual switch 4A or the virtual gateway 3A.
  • Control device management information (first example) As illustrated in FIG. 14, the management information stored in the path information DB 50 of the control device 5 is information managed by the control device 5 for the virtual gateway 3A functioning as the P-GW here.
  • the control device 5 manages, for example, communication path information and information on the virtual U-Plane 31 corresponding to the communication path identified by the communication path information (“virtual U-Plane” in FIG. 14).
  • the communication path information is, for example, an IP address (“GW IP addr” in FIG. 14) assigned to the virtual U-plane and a communication path identifier (TEID in FIG. 14).
  • GW IP addr is an IP address commonly assigned to each virtual U-Plane 31.
  • the control device 5 manages the above-mentioned GW IP addr and TEID as communication path information for uplink communication (communication directed from the terminal 1 to an external network such as the Internet).
  • the communication path information may include information related to the virtual U-Plane 31 corresponding to the communication path (for example, identification information of the virtual U-plane. Information indicated as “virtual U-Plane” in FIG. 14).
  • a communication path in which “GW IP addr” is GW-U and “TEID” is TEID # A corresponds to virtual U-Plane # 1.
  • the control device 5 includes, for example, information including the IP address of the terminal 1 (“UE IP addr” in FIG. 14) as communication path information for downlink communication (communication directed from the external network to the terminal 1). to manage. For example, the control device 5 acquires communication path information from the virtual C-plane 30.
  • an IP address is not assigned to each virtual U-plane 31, but a common IP address (“GW IP addr”) is assigned to each virtual U-plane.
  • GW IP addr a common IP address
  • “Not only such an allocation method but also a plurality of IP addresses (for example,“ GW-U # 1 ”and“ GW-U # 2 ”) may be allocated to the virtual U-plane. It is also possible to adopt an allocation method in which "GW-U # 1" is assigned to U-Plane # 1- # n and "GW-U # 2" is assigned to virtual U-Plane # m- # x. .
  • Communication device control information (first example) As illustrated in FIG. 15, the control device 5 can set control information in the communication device 4.
  • the control device 5 notifies, for example, an instruction for processing the received packet as control information to the communication device 4 that processes Uplink communication.
  • the communication device 4 processes the received packet according to the notified control information.
  • the control information notified by the control device 5, for example, identifies the bearer to which the received packet belongs based on the IP address ("GW IP addr") assigned to the virtual U-plane and the TEID, and corresponds to the identified bearer
  • the communication apparatus 4 is instructed to transfer the received packet to the virtual U-plane 31 to be transmitted.
  • the control information notified to the communication device 4 for Uplink communication includes, for example, “Matching Key” (identification condition) and “Instruction” (instruction).
  • “Matching Key” indicates a condition for identifying a packet based on the IP address for U-plane (“GW IP addr”) that is the destination address of the packet and the TEID.
  • “Instruction” indicates a method of processing a packet that matches the condition of “Matching Key”. For example, when a packet whose destination address (Dst Addr) is “GW-U” and whose TEID is “#A” is identified, the packet is instructed to be transferred to “virtual U-plane # 1”. .
  • the control device 5 notifies, for example, an instruction for processing the received packet as control information to the communication device 4 that processes Downlink communication.
  • the communication device 4 processes the received packet according to the notified control information.
  • the control information notified by the control device 5 identifies the bearer to which the received packet belongs based on the IP address of the terminal 1 that is the destination of the packet (“UE IP addr”), and the virtual U corresponding to the identified bearer. -Instruct the plane 31 to transfer the received packet.
  • the control information notified to the communication device 4 for Downlink communication includes, for example, “Matching Key” and “Instruction”.
  • “Matching Key” indicates a condition for identifying a packet based on the IP address (“UE IP addr”) of the terminal 1 that is the destination address of the packet.
  • “Instruction” indicates a method of processing a packet that matches the condition of “Matching Key”. For example, when a packet whose destination address (Dst Addr) is “UE # A ′” is identified, the packet is instructed to be transferred to “virtual U-plane # 1”.
  • the communication device 4 transfers the received packet to the virtual U-plane 31 according to the control information illustrated in FIG. 15. More specifically, the communication device 4 searches for a “Matching Key” corresponding to the received packet. When a matching “Matching Key” is found, the communication device 4 follows the “Instruction” corresponding to the “Matching Key”. Is transferred to the virtual U-plane 31.
  • a packet addressed to the virtual gateway 3 (a packet with Dst Addr being “GW-U”) is transferred to the virtual U-plane 31 according to the TEID.
  • a packet with TEID “#A” is in virtual U-plane # 1
  • a packet with TEID “#B” is in virtual U-plane # 2
  • a packet with TEID “#C” is virtual. Each is transferred to U-plane # 3.
  • the received packet is transferred to the virtual U-plane 31 according to the destination IP address.
  • a packet whose destination IP address is “UE # A ′” is to virtual U-plane # 1
  • a packet whose destination IP address is “UE # B ′” is to virtual U-plane # 2
  • Packets with the address “UE # C ′” are transferred to the virtual U-plane # 3, respectively.
  • Control device management information (second example) As illustrated in FIG. 17, the management information stored in the path information DB 50 of the control device 5 is information managed by the control device 5 for the virtual gateway 3A functioning as the S-GW.
  • the control device 5 manages, for example, communication path information and information regarding the virtual U-Plane 31 corresponding to the communication path identified by the communication path information.
  • the communication path information is, for example, an IP address (“GW IP addr” in FIG. 17) assigned to the virtual U-plane and a communication path identifier (TEID in FIG. 17).
  • the control device 5 manages, for example, the above-described GW IP addr and TEID as communication path information for Uplink communication.
  • the communication path information may include information on the virtual U-Plane 31 corresponding to the communication path (for example, identification information of the virtual U-Plane. Information indicated as “virtual U-Plane” in FIG. 17).
  • the control device 5 manages, for example, the above-described GW IP addr and TEID as communication path information for Downlink communication.
  • the communication path information may include information on the virtual U-Plane 31 corresponding to the communication path (for example, identification information of the virtual U-Plane. Information indicated as “virtual U-Plane” in FIG. 17). For example, the control device 5 acquires communication path information from the virtual C-plane 30.
  • an IP address is not assigned to each virtual U-plane 31, but a common IP address (“GW IP addr”) is assigned to the virtual U-plane.
  • GW IP addr a common IP address
  • an IP address “GW-U” for Uplink and an IP address “GW-U ′” for Downlink are assigned to the virtual U-plane, respectively.
  • a plurality of IP addresses for example, “GW-U # 1”, “GW-U # 2”, “GW-U ′ # 1”, “GW-U ′ # 2”) for the virtual U-plane May be assigned.
  • GW-U # 1 and “GW-U ′ # 1” are assigned to the virtual U-Plane # 1- # n
  • “GW-U # 2” is assigned to the virtual U-Plane # m- # x.
  • "And" GW-U '# 2 "are assigned.
  • Communication device control information (second example) As illustrated in FIG. 18, the control device 5 can set control information in the communication device 4.
  • the control device 5 notifies, for example, an instruction for processing the received packet as control information to the communication device 4 that processes Uplink communication.
  • the communication device 4 processes the received packet according to the notified control information.
  • the control information notified by the control device 5 is, for example, identifying the communication path to which the received packet belongs based on the IP address (“GW IP addr”) assigned to the virtual U-plane and the TEID, and the identified communication path
  • the communication device 4 is instructed to transfer the received packet to the virtual U-plane 31 corresponding to.
  • the control information notified to the communication device 4 for Uplink communication includes, for example, “Matching Key” and “Instruction”.
  • “Matching Key” indicates a condition for identifying a packet based on the IP address for U-plane (“GW IP addr”) that is the destination address of the packet and the TEID.
  • “Instruction” indicates a method of processing a packet that matches the condition of “Matching Key”. For example, when a packet whose destination address is “GW-U” and TEID is “#A” is identified, the packet is instructed to be transferred to “virtual U-plane # 1”.
  • the control device 5 notifies, for example, an instruction for processing the received packet as control information to the communication device 4 that processes Downlink communication.
  • the communication device 4 processes the received packet according to the notified control information.
  • the control information notified by the control device 5 is, for example, identifying the communication path to which the received packet belongs based on the IP address (“GW IP addr”) assigned to the U-plane and the TEID.
  • the communication device 4 is instructed to transfer the received packet to the corresponding virtual U-plane 31.
  • the control information notified to the communication device 4 for Downlink communication includes, for example, “Matching Key” and “Instruction”.
  • “Matching Key” indicates a condition for identifying a packet based on the IP address for U-plane (“GW IP addr”) that is the destination address of the packet and the TEID.
  • “Instruction” indicates a method of processing a packet that matches the condition of “Matching Key”. For example, when a packet whose destination address is “GW-U ′” and TEID is “#A ′” is identified, the packet is instructed to be transferred to “virtual U-plane # 1”.
  • the communication device 4 transfers the received packet to the virtual U-plane 31 according to the control information illustrated in FIG. 18. More specifically, the communication device 4 searches for a “Matching Key” corresponding to the received packet, and if a matching “Matching Key” is found, the communication device 4 transmits the received packet according to the “Instruction” corresponding to the “Matching Key”. Transfer to virtual U-planes 31.
  • a packet addressed to the gateway 3 (a packet whose Dst Addr is “GW-U”) is transferred to the virtual U-plane 31 according to the TEID.
  • a packet with TEID “#A” is a virtual U-plane # 1
  • a packet with TEID “#B” is a virtual U-plane # 2
  • a packet with TEID “#C” is a virtual Each is transferred to U-plane # 3.
  • a packet addressed to the gateway 3 (a packet whose Dst Addr is “GW-U ′”) is transferred to the virtual U-plane 31 according to the TEID.
  • a packet with TEID “#A” is in virtual U-plane # 1
  • a packet with TEID “#B” is in virtual U-plane # 2
  • a TEID is “#C”.
  • the packet is transferred to the virtual U-plane # 3.
  • control device 5 may also control a packet that has passed through the virtual U-plane.
  • Control of a packet that has passed through the virtual U-plane can be, for example, control based on a destination IP address.
  • the communication path is assigned to the virtual C-Plane and the virtual U-Plane.
  • the communication path may be assigned to the virtual gateway 3A.
  • an IP address “vGW” is assigned to the virtual gateway 3A, and a different IP address (eg, “IP # 1”) is assigned to each virtual U-Plane.
  • the communication device 4 When the communication device 4 receives the packet having the destination address “vGW”, the communication device 4 converts the destination address according to the TEID of the packet. For example, when the TEID is “#A”, the communication device 4 converts the destination address “vGW” into the IP address “IP # 1” of the virtual U-Plane # 1 corresponding to the TEID “#A”.
  • the communication device 4 When the communication device 4 receives a packet whose source address is the IP address of the virtual U-Plane, the communication device 4 converts the source address to the IP address “vGW” of the virtual gateway 3A.
  • the MAC address may be converted together with the IP address.
  • the MAC address “vGW_MAC” is assigned to the virtual gateway 3A, and a different MAC address (for example, “MAC # 1”) is assigned to each virtual U-Plane.
  • a common IP address is assigned to the virtual U-plane and the virtual C-plane. Even if the constituent virtual U-planes 31 are added, the switching of the gateway 3 corresponding to the communication path can be hidden from the terminal 1, and the occurrence of the reconstruction of the communication path can be avoided.
  • the packet transfer policy of the communication device 4 or the virtual switch 4A is updated.
  • the present embodiment can be applied to any technique disclosed in the first, second, or third embodiment.
  • various examples of updating the packet transfer policy of the communication device 4 or the virtual switch 4A will be described.
  • Transfer policy update (first example)
  • the transfer policy update sequence illustrated in FIG. 21 is a sequence for updating the packet transfer policy in the sequence (attach procedure “Attach Procedure”) disclosed in the LTE standard specification (3GPP TS23.401 V12.1.0). It is a procedure. “Attach Procedure” is disclosed in section 5.3.2 of the standard specification.
  • the attach procedure in FIG. 21 shows a part related to the present embodiment in the sequence described in the standard specification, and details of other sequences are omitted. Note that when the attach procedure is completed, a communication path for communication by the terminal 1 is set.
  • control device 5 operates as an MME of the LTE system. Or the function of the control apparatus 5 illustrated by the above-mentioned embodiment is added to MME of a LTE system.
  • MME5 the MME to which the function of the control device 5 is added.
  • the attach procedure is executed in the system. For example, in response to the start of the attach procedure, the MME 5 selects a virtual U-Plane to be assigned to the communication path set by the attach procedure (Operation S11).
  • the MME 5 transmits a “Create Session Request” message to the gateway 3 (S-GW) (Operation S12).
  • “Create Session Request” is a message for the MME 5 to request the S-GW to set a communication path.
  • the MME 5 selects the S-GW and the P-GW, assigns an ID (for example, EPS bearer ID) corresponding to the communication path of the terminal 1, and assigns the ID and communication path assigned to the gateway information and the communication path.
  • Information about QoS corresponding to (QCI, etc.) is notified to the S-GW by a “Create Session Request” message.
  • the S-GW notifies the gateway 3 (P-GW) of the communication path ID, the QoS information (QCI, etc.) corresponding to the communication path, etc. by the “Create Session Request” message (operation S13).
  • the P-GW that has received the “Create Session Request” message returns a “Create Session Response” message to the S-GW (operation S14).
  • the S-GW transmits a “Create Session Response” message to the MME 5 (operation S15).
  • the S-GW TEID for the S1-U interface and the S-GW TEID for the S5 / S8 interface are notified to the MME5 and the S-GW used in the communication path Is notified to the MME 5.
  • the S-GW address used in the communication path is, for example, an IP address common to each virtual U-Plane constituting the S-GW.
  • the MME 5 sets the packet transfer policy of the communication device 4 (“Routing Policy” in FIG. 21) based on the S-GW TEID and the S-GW address notified by the S-GW, and sends them to the communication device 4 Transmit (operation S16).
  • the packet transfer policy is, for example, the control information exemplified in the above-described third embodiment (that is, control information set by the control device 5 in the communication device 4).
  • the MME 5 sets the packet transfer policy illustrated in FIG. 18 in the communication device 4 based on the information notified from the S-GW.
  • a packet transfer policy based on the S1-U interface TEID is set for the communication device 4 on the uplink side
  • a packet transfer based on the TEID for the S5 / S8 interface is set for the communication device 4 on the downlink side.
  • a policy is set.
  • the gateway 3 and the communication device 4 are illustrated as different devices.
  • the present invention is not limited to this, and for example, as in the example of FIG. 5, the communication device 4 including the virtual switch 4A and the virtual gateway 3A.
  • the communication device 4 including the virtual switch 4A and the virtual gateway 3A.
  • the S-GW notifies the P-GW of the “Create Session Request” message and also notifies the MME 5 of the S-GW TEID for the S5 / S8 interface (operation S13a).
  • the P-GW may notify the MME 5 of the S-GW TEID for the S5 / S8 interface in response to the “Create Session Request” message received from the S-GW.
  • the gateway 3 and the communication device 4 are illustrated as different devices.
  • the present invention is not limited to this.
  • the communication device 4 including the virtual switch 4A and the virtual gateway 3A. It is also possible to operate according to the packet transfer policy notified from the control device 5.
  • Transfer policy update (third example)
  • the packet transfer policy of the communication device 4 is updated in accordance with the configuration change of the virtual U-Plane 31 of the virtual gateway 3A.
  • the configuration change of the virtual U-Plane 31 means, for example, installation of the virtual U-Plane 31 by newly starting a VM or uninstallation of the virtual U-Plane 31 by stopping the VM.
  • the MME 5 When the MME 5 detects the configuration change of the virtual U-Plane 31 (Operation S20), the MME 5 changes the correspondence between the communication path and the virtual U-Plane 31 (Operation S21). For example, the MME 5 determines a communication path to be assigned to the virtual U-Plane 31 newly installed in the virtual gateway 3A. For example, the MME 5 assigns the communication path assigned to the virtual U-Plane 31 that is uninstalled from the virtual gateway 3A to the other virtual U-Plane 31.
  • the load status of the virtual U-Plane 31 constituting the virtual gateway 3A is used instead of the configuration change of the virtual U-Plane 31 of the virtual gateway 3A. You can also. For example, there is control for switching a communication path from a virtual U-Plane 31 having a high load to a virtual U-Plane 31 having a low load.
  • the MME 5 updates the packet transfer policy of the communication device 4 based on the change in the correspondence relationship between the communication path and the virtual U-Plane 31 (Operation S22).
  • Transfer policy update (fourth example)
  • the MME 5 acquires information from the gateway 3 (S-GW) in order to update the packet transfer policy.
  • the MME 5 requests the TE-GW of the communication path established by the attach procedure of the standard specification (TS23.401) described above, for example, from the S-GW (operation S30).
  • the S-GW In response to the TEID request, the S-GW notifies the MME 5 of the TEID by a TEID response (operation S31). For example, the S-GW TEID for the S1-U interface and the S-GW TEID for the S5 / S8 interface are notified to the MME 5. At that time, for example, the S-GW notifies the TEID of the communication path established by the attach procedure of the standard specification (TS23.401) described above.
  • the MME 5 determines the virtual U-Plane 31 to be assigned to the TEID notified from the S-GW, and updates the packet transfer policy of the communication device 4 by notifying the communication device 4 (operation S32). That is, the MME 5 updates the packet transfer policy of the communication device 4 so that a packet corresponding to the TEID notified from the S-GW is transferred to the virtual U-Plane 31 assigned to the TEID.
  • the gateway 3 and the communication device 4 are illustrated as different devices.
  • the present invention is not limited to this.
  • the communication device 4 including the virtual switch 4A and the virtual gateway 3A.
  • Transfer policy update (fifth example)
  • the transfer policy update sequence illustrated in FIG. 25 is a packet transfer policy update procedure when the virtual gateway 3A has the functions of the communication device 4 and the control device 5 (for example, the configuration illustrated in FIG. 13). That is, the gateway 3 (S-GW) shown in FIG. 25 includes a virtual switch 4A and a virtual controller 5A.
  • the S-GW virtual controller 5A changes the correspondence between the communication path and the virtual U-Plane 31 (operation S40). For example, the path of the communication path #A is switched from the virtual U-Plane 31 (# 1) to the virtual U-Plane 31 (# 2).
  • the virtual controller 5A updates the packet transfer policy of the virtual switch 4A according to the change of the correspondence relationship between the communication path and the virtual U-Plane 31 (Operation S41). For example, the virtual controller 5A instructs the virtual switch 4A to switch the route of the communication path #A corresponding to the virtual U-Plane 31 (# 1) to a route via the virtual U-Plane 31 (# 2).
  • FIG. 26 shows a procedure for updating the packet transfer policy in the sequence (“Attach Procedure”) disclosed in the LTE standard specification (3GPP TS23.401 V12.1.0). “Attach Procedure” is disclosed in section 5.3.2 of the standard specification.
  • the control device 5 illustrated in FIG. 26 operates as a PCRF of the LTE system. That is, the function of the control device 5 exemplified in the above embodiment is added to the PCRF of the LTE system. That is, in the attach procedure of the terminal 1 (the procedure disclosed in TS23.401), the control device 5 (PCRF) sets a packet transfer policy for the communication device 4.
  • PCRF5 the PCRF to which the function of the control device 5 is added
  • IP-CAN IP Connectivity Session Establishment / Modification
  • IP-CAN IP Connectivity Session Establishment / Modification
  • IMS IP Multimedia Subsystem
  • the PCRF 5 selects, for example, the virtual U-Plane 31 to be assigned to the communication path established in the attach procedure in the “IP-CAN (IP Connectivity) Session Establishment / Modification” procedure (operation S52).
  • the PCRF 5 sets a packet transfer policy in the communication device 4 so that packets belonging to the communication path established by the attach procedure are transferred to the virtual U-Plane 31 assigned to the communication path (operation S53). It is assumed that the PCRF 5 has acquired a TEID related to the P-GW.
  • the gateway 3 and the communication device 4 are illustrated as different devices.
  • the present invention is not limited to this.
  • the communication device 4 including the virtual switch 4A and the virtual gateway 3A It is also possible to operate according to the packet transfer policy notified from the control device 5.
  • the gateway 3 in FIG. 27 is configured as a virtual gateway 3A on the server. Also in FIG. 27, as in the example of FIG. 26, since the function of the control device 5 exemplified in the above embodiment is added to the PCRF of the LTE system, such a PCRF is hereinafter referred to as “PCRF5”. .
  • the packet transfer policy of the communication device 4 or the virtual switch 4A is updated according to the configuration change of the virtual U-Plane 31 of the virtual gateway 3A.
  • the configuration change of the virtual U-Plane 31 means, for example, installation of the virtual U-Plane 31 by newly starting a VM or uninstallation of the virtual U-Plane 31 by stopping the VM.
  • the communication path is switched from the virtual U-Plane 31 having a high load to the virtual U-Plane 31 having a low load.
  • the PCRF 5 When the PCRF 5 detects a configuration change of the virtual U-Plane 31 (operation S60), the PCRF 5 changes the correspondence between the communication path and the virtual U-Plane 31 (operation S61). For example, when the virtual U-Plane 31 is newly installed in the virtual gateway 3A, the PCRF 5 determines a communication path to be assigned to the virtual U-Plane 31. Further, for example, when the virtual U-Plane 31 is uninstalled from the virtual gateway 3A, the PCRF assigns the communication path assigned to the virtual U-Plane 31 to the other virtual U-Plane 31. The PCRF 5 updates the packet transfer policy of the communication device 4 or the virtual switch 4A based on the change in the correspondence between the communication path and the virtual U-Plane 31 (Operation S62).
  • Transfer policy update (eighth example)
  • the PCRF 5 acquires information from the gateway 3 (P-GW) in order to update the packet transfer policy.
  • the PCRF 5 requests a TEID of the communication path from the P-GW (Operation S70).
  • the TEID of the communication path established by the attach procedure of the standard specification (TS23.401) described above is required.
  • the P-GW that has received the communication path TEID request notifies the PCRF 5 of the communication path TEID by a TEID response (operation S71).
  • the P-GW notifies the PCRF of the P-GW TEID of the communication path established by the above-described standard specification (TS23.401) attach procedure.
  • the PCRF 5 determines the virtual U-Plane 31 to be assigned to the TEID notified from the P-GW, and updates the packet transfer policy of the communication device 4 or the virtual switch 4A (Operation S72). This packet transfer policy is updated so that, for example, a packet corresponding to the TEID notified from the P-GW is transferred to the virtual U-Plane 31 assigned to the TEID.
  • the gateway 3 and the communication device 4 are exemplified as different devices.
  • the present invention is not limited to this.
  • the communication device 4 including the virtual switch 4A and the virtual gateway 3A.
  • FIG. 29 illustrates an example of a packet transfer policy update procedure when the gateway 3 has the functions of the communication device 4 or the virtual switch 4A and the control device 5 (for example, the configuration of the virtual gateway 3A illustrated in FIG. 13).
  • the gateway 3 (P-GW) includes a virtual switch 4A and a virtual controller 5A.
  • the P-GW virtual controller 5A changes, for example, the correspondence between the communication path and the virtual U-Plane 31 (operation S80). For example, the virtual controller 5A switches the path of the communication path #A from the virtual U-Plane 31 (# 1) to the virtual U-Plane 31 (# 2).
  • the virtual controller 5A updates the packet transfer policy of the virtual switch 4A according to the change in the correspondence between the communication path and the virtual U-Plane 31 (Operation S81). For example, the virtual controller 5A instructs the virtual switch 4A to switch the route of the communication path #A corresponding to the virtual U-Plane 31 (# 1) to a route via the virtual U-Plane 31 (# 2).
  • the fourth embodiment of the present invention it is possible to cope with a change in the configuration of the virtual U-plane by updating the route policy of the communication device or the virtual switch.
  • the switching of the gateway 3 corresponding to the communication path can be concealed from the terminal 1. It is possible to avoid the occurrence of communication path reconstruction.
  • the communication path may be assigned to the virtual gateway 3A.
  • control device controls the communication device according to a control protocol called OpenFlow.
  • OpenFlow a control protocol called OpenFlow.
  • the fifth embodiment can be applied to any technique disclosed in the first to fourth embodiments described above.
  • OpenFlow recognizes communication as an end-to-end flow and can perform path control and the like on a per-flow basis. Therefore, by using OpenFlow for the present invention, communication path control can be executed more flexibly.
  • the flow refers to a series of communication packets having a predetermined attribute that is identified based on information included in the packet (information such as a packet destination address and a source address).
  • FIG. 30 illustrates a system according to a fifth embodiment of the present invention using the OpenFlow technology.
  • the communication device 4B is a network switch that employs OpenFlow technology, and is centrally controlled by the control device 5A.
  • a control channel is set between the communication device 4B and the control device 5A, and the control device 5A controls the operation of the communication device 4B via the control channel.
  • This control channel is a communication path on which measures for preventing eavesdropping and tampering of communication have been made.
  • the control device 5A controls the operation of the communication device 4B by setting a processing rule (flow entry) in the flow table of the communication device 4B.
  • the flow entry is an instruction that specifies a matching rule for matching with information (for example, destination IP address, VLAN ID, etc.) included in the header of the packet received by the communication device 4B and a processing rule for a packet that matches the matching rule. (Instruction).
  • the control device 5 ⁇ / b> A includes a communication interface 52, a control unit 51, and a flow entry DB 53.
  • the communication interface 52 is an interface for communicating with the communication device 4B by the OpenFlow protocol.
  • the control unit 51 has a function of generating information stored in the flow entry DB 53 and a function of controlling the communication device 4B based on information stored in the flow entry DB 53.
  • the control device 5A can set a communication path identifier (for example, TEID or GRE Key) in the communication device 4B as a matching rule.
  • the communication path identifier is not defined as information that can be identified as a matching rule.
  • the control device 5A can set the communication path identifier as a matching rule.
  • the flow entry DB 53 illustrated in FIG. 32 includes a matching rule (Matching Rule) based on IP addresses and communication path identifiers commonly assigned to a plurality of virtual U-Planes 31. It shall consist of instructions.
  • the communication device 4B includes a control unit 43 and a flow entry DB 46 (that is, a flow table).
  • the control unit 43 includes a search unit 44 and a processing unit 45.
  • the flow entry DB 46 stores the flow entry notified from the control device 5A.
  • the search unit 44 searches the flow entry DB 46 for a flow entry corresponding to the received packet.
  • the search unit 44 of the communication device 4B can expand the OpenFlow protocol and search the flow table using the communication path identifier included in the received packet as a key. Accordingly, the search unit 44 searches for a flow entry corresponding to the communication path identifier of the received packet. That is, an entry in which an identifier corresponding to the communication path identifier of the received packet is defined as a matching rule is searched.
  • the search unit 44 can search the flow entry corresponding to the received packet from the flow entry DB 46 based on the information included in the outer header of the received packet. If the flow entry corresponding to the received packet is not set in the entry DB 46, the search unit 44 can inquire the flow entry corresponding to the received packet to the control device 5A.
  • the processing unit 45 processes the received packet according to the “Instruction” of the flow entry searched by the search unit 44. As shown in FIG. 32, here, according to “Instruction”, the packet is transferred to the virtual U-Plane corresponding to the communication path identifier. Note that the processing unit 45 can NAT the destination address according to the processing rule, for example, as in the example of FIG.
  • control device 5 groups communication paths and assigns a group including a plurality of communication paths to the virtual U-Plane 31.
  • the sixth embodiment can be applied to any technique disclosed in the first to fifth embodiments described above.
  • control device 5 assigns communication paths to different virtual U-planes in units of groups.
  • the communication path group (1) is assigned to the virtual U-plane (# 1).
  • control device 5 Since the control device 5 manages communication paths in units of groups, it is easy to manage the correspondence between the virtual U-Plane 31 and the communication paths. For example, in the route information DB 50, the control device 5 can manage the virtual U-Plane 31 corresponding to the communication path in units of communication path groups. Note that the control device 5 can also manage the virtual U-Plane 31 exemplified in the first and second embodiments in units of groups.
  • the control device 5 groups communication paths according to the attributes of the terminal 1 corresponding to each communication path. Examples of attributes of the terminal 1 are shown below. ⁇ Stay area of terminal 1 (E-UTRAN Cell ID, etc.) -Charging characteristics related to terminal 1 (regular charging, prepaid charging, flat rate, etc.) ⁇ Communication status of terminal 1 (whether or not a certain amount of communication has been performed during a certain period) -Operator ID (ID of the operator of the core network to which the terminal 1 is connected) ⁇ Packet Data Network (PDN) to which the terminal 1 is connected -Service types that need to be chained after leaving the communication path-QoS characteristics-Terminal 1 status (IDLE state, CONNECTED state): For example, the IDLE state is the session management and mobility between the terminal 1 and the core network.
  • PDN Packet Data Network
  • the CONNECTED state means, for example, a state in which the terminal 1 is continuously exchanging control signals for session management and mobility management with the core network, or a state in which the terminal 1 is wirelessly connected to the base station.
  • control device 5 can group communication paths according to other attributes.
  • the control device 5 groups communication paths based on information on UE (User Equipment) in “EPS Bearer Context” disclosed in Chapter 5.7 of the standard specification (3GPP TS23.401). It is possible.
  • control device 5 can group communication paths according to the contract contents between the user of the terminal 1 and the communication carrier.
  • the control device 5 may group communication paths related to a user (for example, “Premium Subscriber”) who has concluded a contract with a telecommunications carrier with a higher price than other users, and / or a user related to a normal contract. It is possible to group communication paths.
  • the control device 5 can also group communication paths based on information on the location of the terminal 1 (for example, GSP information, base station information to which the terminal 1 is attached). For example, it is possible to group communication paths of terminals that are close to each other based on information regarding the position.
  • control device 5 can also group communication paths according to QoS (Quality of Service) information of the communication paths.
  • QoS Quality of Service
  • the control device 5 can group communication paths according to QCI (Quality Class Indicator) corresponding to each communication path.
  • QCI Quality Class Indicator
  • the route switching causes a delay in communication related to the communication path and the user's QoE (Quality of Experience) is lowered.
  • a new virtual U- By assigning to the plane, it is possible to stop the communication path in which the QoE is lowered to the communication path with a low priority.
  • the TEID of each communication path may be assigned so that the TEIDs of the plurality of communication paths belonging to the group can be collectively identified.
  • the TEID is assigned to each of a plurality of communication paths belonging to the group so that the upper 24 bits of the TEID configured by 32-bit information are the same.
  • the control device 5 can collectively identify a plurality of communication paths belonging to the group based on the information of the upper 24 bits of the TEID.
  • the IP address of the terminal 1 is assigned to each of a plurality of terminals 1 belonging to the group so that the IP addresses of the respective terminals 1 can be collectively identified. May be.
  • the IP address of the terminal 1 is assigned to a plurality of terminals 1 belonging to the group so that the upper 24 bits of the IP address composed of 32-bit information are the same.
  • the control device 5 can collectively identify traffic related to a plurality of communication paths belonging to the group based on the information of the upper 24 bits of the IP address of the terminal 1.
  • the route information DB 50 of the control device 5 has the same configuration as that of the example of FIG.
  • the communication device 4 searches the route information DB 42 using the communication path identifier of the received packet as a key, and transfers the received packet to the virtual U-Plane 31 corresponding to the communication path identifier of the received packet.
  • the control device 5 can switch the corresponding gateway for each group of communication paths. For example, the control device 5 can switch the gateway corresponding to the group to which the communication paths with the communication path identifiers (A) to (C) belong from the gateway (a) to the gateway (e).
  • the control device 5 can significantly reduce the amount of control signal information for the communication device 4 by switching the corresponding gateway for each group of communication paths. As shown in FIG. 36, the control device 5 can transmit a corresponding gateway switching instruction to the communication device 4 using the group ID as a key.
  • the route information DB 42 of the communication device 4 has a configuration as shown in FIG.
  • the control device 5 switches the corresponding gateway of the group (1) from the gateway (a) to (e) as shown in FIG. 36
  • the control device 5 makes a communication path identifier (A) to the communication device 4. )-(C)
  • the control device 5 transmits a control signal using the group ID as a key as in the sixth embodiment, the control signal is reduced to one third in the example of FIG. That is, according to the sixth embodiment, the control device 5 has an advantage that the amount of control signal reduction increases as the number of communication paths to be grouped increases, and the switching speed of the communication path gateway is increased. It becomes possible to do.
  • FIG. 37 shows another configuration example of the route information DB 42. Note that the path information DB 50 of the control device 5 has the same configuration as the example of FIG.
  • the communication path identifier is set so that the identifiers of the communication paths belonging to the group can be collectively identified.
  • the communication path identifier is set so that a part of the identifiers of the communication paths belonging to the same group are common.
  • the identifiers of the communication paths belonging to the same group are set so that the values of the upper 24 bits are common, and the values common to the upper 24 bits of the communication path identifiers (A) to (B) (see FIG. In the example of 37, “X”) is set.
  • the number of entries in the route information DB 42 is reduced.
  • an entry in the route information DB 42 is set for each communication path identifier.
  • entries related to communication paths belonging to the same group can be consolidated into one entry, and the number of entries in the route information DB 42 is reduced.
  • the control signal transmitted from the control device 5 to the communication device 4 can be reduced. That is, the control device 5 can instruct switching of the corresponding gateway using the upper 24 bits of the communication path identifier as a key.
  • the control device 5 switches the gateway corresponding to the value “X” of the upper 24 bits of the communication path identifier. Instruct. That is, the control device 5 does not have to instruct the switching of the gateway to each of the communication path identifiers (A) to (C). Therefore, when the gateway is switched, the control signal transmitted from the control device 5 to the communication device 4 is reduced. Gateway switching is speeded up by reducing control signals.
  • FIG. 38 shows an example of the flow entry DB 46 of the communication device 4 when an OpenFlow flow table is used in the sixth embodiment. Note that the path information DB 50 of the control device 5 has the same configuration as the example of FIG.
  • OpenFlow has a function of regarding a plurality of packet processes as one group. Grouped packet processing is handled in the group table.
  • the communication device 4 includes a flow entry DB 46 that functions as a normal flow table, and a group table 46a of the flow entry DB 46.
  • the communication path identifiers (A) to (C) belong to the same communication path group.
  • the same processing group ID is set in “Instruction” corresponding to each flow entry whose matching rule is the communication path identifier (A)-(C).
  • “Instruction” that defines grouped packet processing is set for each processing group ID.
  • the control device 5 sets the flow entry DB 46 and the group table 46a in the example of FIG.
  • the communication device 4 searches the flow entry DB 46 using the communication path identifier of the received packet as a key.
  • the communication device 4 searches for an entry in which “processing group ID (1)” is set as “Instruction”. Subsequently, the group table 46a is searched using the processing group ID as a key.
  • the communication device 4 searches the group table 46a using “processing group ID (1)” as a key, and “processing group ID (1)”. The received packet is transferred to the gateway (a) in accordance with “Instruction” corresponding to.
  • the control device 5 When switching the virtual U-Plane 31 corresponding to the communication path group, the control device 5 transmits a control signal for changing the entry in the group table based on the processing group ID to the communication device 4. For example, in the example of FIG. 38, when the gateway corresponding to the communication path identifiers (A) to (C) is changed from (a) to (e), the control device 5 uses the identifier (A) ⁇ in the group table 46a. “Instruction” of the entry of “processing group ID (1)” corresponding to (C) is changed. That is, the control device 5 only needs to change the entry in the group table, and does not need to change the entry in the normal flow table. In the example of FIG.
  • the control device 5 does not need to change each entry corresponding to the identifiers (A) to (C), and does not change the entry corresponding to “processing group ID (1)” in the group table 46a. Change it. Therefore, when the gateway is switched, the control signal transmitted from the control device 5 to the communication device 4 is reduced. Gateway switching is speeded up by reducing control signals.
  • FIG. 39 shows another example of the flow entry DB 46 when an OpenFlow flow table is used in the sixth embodiment.
  • the route information DB 50 of the control device 5 has the same configuration as that in FIG.
  • OpenFlow switch can have multiple flow tables.
  • the communication device 4 has a plurality of flow entry DBs 46 (a flow table 46-1 and a flow table 46-2). For example, when receiving a packet, the communication device 4 searches a plurality of flow tables in a predetermined order. For example, in the example of FIG. 39, the communication device 4 searches the flow table 46-1 and then searches the flow table 46-2.
  • the communication path identifiers (A) to (C) belong to the same communication path group.
  • the flow table 46-1 in the “Instruction” corresponding to each flow entry whose matching rule is the communication path identifier (A)-(C), packet processing for adding “ID (1)” to the packet header is performed. Is set. The ID given to the packet is set for each group of communication paths.
  • the control device 5 sets the flow entry DB 46 in the example of FIG.
  • the communication device 4 searches the flow entry DB 46 (flow table 46-1) using the communication path identifier of the received packet as a key. Specifically, when the communication device 4 receives the packet with the communication path identifier (A), the communication device 4 searches for an entry in which “Instruction” indicating that “ID (1)” is added to the header of the packet. . Next, the communication device 4 searches the flow entry DB 46 (flow table 46-2) using “ID (1)” given to the packet as a key, and follows “Instruction” corresponding to “ID (1)”. The ID is deleted from the header, and the received packet is transferred to the gateway (a).
  • the control device 5 When the control device 5 switches the virtual U-Plane 31 corresponding to the communication path group, the control device 5 transmits to the communication device 4 a control signal for changing the entry based on the ID corresponding to the communication path group. For example, when the gateway corresponding to the communication path identifiers (A) to (C) is changed from (a) to (e), the control device 5 uses the identifier (A) in the flow entry DB 46 (flow table 46-2). -Change "Instruction" of the entry of "ID (1)" corresponding to (C). That is, the control device 5 may change the entry corresponding to the ID of the communication path group, and does not need to change the entry corresponding to each of the communication path identifiers. In the example of FIG.
  • the control device 5 does not need to change each entry corresponding to the identifiers (A) to (C), and “ID (1)” is stored in the flow entry DB 46 (flow table 46-2).
  • the entry corresponding to can be changed. Therefore, when the gateway is switched, the control signal transmitted from the control device 5 to the communication device 4 is reduced. Gateway switching is speeded up by reducing control signals.
  • the control device 5 can group communication paths based on other information (for example, an IP address or a PDN), and the communication device 4 can perform other information (for example, an IP address or an IP address). , PDN), it is possible to identify a group of communication paths.
  • the control device 5 selects the virtual U-Plane 31 to be assigned to the communication path according to the policy for selecting the virtual U-Plane 31 associated with the communication path. For example, according to the installation / uninstallation of the virtual U-Plane 31, it is possible to dynamically select the virtual U-Plane 31 associated with the communication path according to the policy. In addition, the control device 5 can dynamically change the virtual U-Plane 31 assigned to the communication path in accordance with a change in conditions regarding the policy.
  • an example of a policy for selecting the virtual U-Plane 31 is shown. However, this policy can also be used for selecting the gateway 3 exemplified in the first and second embodiments. Is possible.
  • the control device 5 includes a policy DB 54 in addition to the configuration example of the control device 5 illustrated in FIG.
  • the control unit 51 can select the virtual U-Plane 31 associated with the communication path with reference to the policy DB 54.
  • the policy stored in the policy DB 54 is configured such that, for example, the virtual U-Plane 31 corresponding to the communication quality requirement regarding the communication path is selected.
  • the policy stored in the policy DB 54 may be configured such that, for example, the virtual U-Plane 31 is selected for each group of communication paths in accordance with a communication quality request related to the communication path. For example, when the virtual U-Plane 31 is added, the control unit 51 refers to the policy DB 54 and selects the virtual U-Plane 31 associated with the communication path.
  • the control unit 51 selects the virtual U-Plane 31 associated with the communication path and adds an entry to the route information DB 50.
  • the control unit 51 notifies the communication device 4 of the correspondence between the communication path and the virtual U-Plane 31 based on the route information DB 50.
  • the control device 5 determines a virtual U-Plane 31 to be associated with the communication path based on the policy regarding the QCI corresponding to the communication path. For example, the control device 5 can acquire the QCI of the communication path from the MME.
  • the priority is set to the communication path corresponding to each QCI according to the value of QCI.
  • the control device 5 selects the virtual U-Plane 31 to be associated with the communication path according to the priority that is a condition for selecting the virtual U-Plane 31. For example, when the virtual U-Plane 31 is newly installed in the communication system, the control device 5 determines the newly installed virtual U-Plane 31 in order from the communication path corresponding to the QCI whose priority is set to “Low”. Associate with. That is, the control device 5 determines the correspondence between the newly installed virtual U-Plane 31 and the communication path in the order of priority of the QCI.
  • Switching the virtual U-Plane 31 corresponding to the communication path may cause a communication delay or the like due to the switching, but the virtual U-Plane 31 associated with the communication path in order from the communication path with the lowest QCI priority. By switching the, the deterioration of the communication quality of the communication path having a high QCI priority is suppressed. Thereby, the control apparatus 5 can select the virtual U-Plane 31 corresponding to the quality requirement corresponding to the QCI.
  • the priority for the QCI is “High”, “Mid”, and “Low”, but the method of assigning the priority is not limited to the example of FIG.
  • a value indicating the priority may be assigned to each QCI.
  • the control device 5 can determine the gateway associated with the communication path according to the priority of each QCI. For example, the control device 5 can associate a communication path corresponding to a QCI having a priority equal to or higher than a predetermined value with a virtual U-Plane 31 that can guarantee a communication band. Further, for example, the control device 5 can associate a communication path corresponding to a QCI having a priority level equal to or higher than a predetermined value with a virtual U-Plane 31 whose operation load is equal to or lower than a predetermined value.
  • the control device 5 can determine the gateway associated with the communication path for each QCI. For example, the control device 5 determines a communication path associated with a certain gateway according to the QCI. In this case, the QCIs of a plurality of communication paths assigned to a certain gateway are the same.
  • control device 5 can also determine the virtual U-Plane 31 associated with the communication path according to the communication amount and communication time of the communication path.
  • the control device 5 can monitor the virtual U-Plane 31 and acquire the communication amount and communication time through the communication path.
  • thresholds relating to the communication amount and communication time are set according to the communication path identifier.
  • a threshold value may be set for each group of communication paths as in the sixth embodiment.
  • the control device 5 selects the virtual U-Plane 31 to be associated with the communication path according to the threshold for communication volume and communication time, which are conditions for selecting the virtual U-Plane 31.
  • the virtual U-Plane 31 to be associated with the communication path is determined based on the policy regarding the communication amount and communication time by the communication path.
  • the control device 5 when the user of the terminal 1 concludes a prepaid billing contract with a communication carrier, the user can communicate up to the communication amount corresponding to the prepaid fee (that is, the communication amount threshold).
  • the control device 5 information related to a contract between the user of the terminal 1 and the communication carrier is set.
  • the control device 5 switches the communication path with a margin with respect to the threshold set in the policy DB 54.
  • the traffic (“X” Byte) is set as the threshold value of the communication path with the communication path identifier “A”.
  • control device 5 monitors the communication amount of the communication path with the identifier “A” from the virtual U-Plane 31 functioning as the P-GW, and the difference between the communication amount and the threshold (“X” Byte) is less than a predetermined value. If there is, the communication path is excluded from switching targets.
  • the user of the terminal 1 when the user of the terminal 1 concludes a two-stage charging contract with a communication carrier, the user pays a communication fee according to the communication amount until the communication amount exceeds a specific threshold value. Regardless of the amount, the communication fee is a flat rate (Flat). If the threshold value is exceeded, it is not necessary to accurately monitor the traffic volume. Therefore, when the control device 5 switches the communication path in accordance with installation or uninstallation of the virtual U-Plane 31, the traffic volume exceeds the threshold value. Switch the communication path with priority.
  • Flat flat rate
  • the control device 5 When switching the communication path according to the installation or uninstallation of the virtual U-Plane 31, the control device 5 preferentially switches the communication path whose communication amount exceeds the threshold set in the policy DB 54.
  • the traffic (“Y” Byte) is set as the threshold value of the communication path with the communication path identifier “D”.
  • the control device 5 monitors the communication amount of the communication path with the identifier “D” from the virtual U-Plane 31 functioning as the P-GW, and when the communication amount exceeds the threshold (“Y” Byte). Switches the communication path.
  • a virtual U-Plane 31 according to the request can be selected.
  • the control device 5 has a bearer that has a margin with respect to the deadline determined by the contract (for example, a bearer that has a margin of one hour or more with respect to the deadline). ) To switch. By switching bearers in this way, it is possible to suppress the possibility that a time limit will be exceeded during execution of bearer switching and communication that exceeds the contractual time limit will occur.
  • the control device 5 monitors the communication time of the identifier “B” communication path from the virtual U-Plane 31 functioning as the P-GW, and when the communication time exceeds the threshold (“23H”), The communication path is excluded from switching targets.
  • the control device 5 can select the virtual U-Plane 31 associated with the communication path according to the frequency of activating the virtual U-Plane 31.
  • the control device 5 selects the virtual U-Plane 31 to be associated with the communication path according to the frequency of installation or uninstallation of the virtual U-Plane 31 (or the frequency of activation or deactivation). Is possible.
  • the control device 5 selects the virtual U-Plane 31 to be associated with the communication path according to the install / uninstall frequency that is a condition for selecting the virtual U-Plane 31.
  • the control device 5 can monitor the virtual U-Plane 31 and acquire the install / uninstall frequency.
  • a priority for each communication path identifier is set.
  • a priority may be set for each group of communication paths as in the sixth embodiment.
  • the control device 5 selects the virtual U-Plane 31 to be associated with the communication path in accordance with a threshold related to priority, which is a condition for selecting the virtual U-Plane 31.
  • the control device 5 determines a virtual U-Plane 31 associated with a communication path based on a policy regarding the priority of the communication path identifier.
  • the control device 5 monitors the frequency of installation / uninstallation of the virtual U-plane 31, for example. For example, the control device 5 associates a communication path with a low priority (for example, a communication path with a priority of “Low” in the policy DB 54) with the virtual U-plane 31 that is frequently installed / uninstalled.
  • a communication path with a low priority for example, a communication path with a priority of “Low” in the policy DB 54
  • the control device 5 can suppress deterioration in communication quality of a communication path with a high priority.
  • the control device 5 can also determine the virtual U-Plane 31 to be associated with the communication path using a policy based on SLA (Service Level Agreement) required for the service regarding the communication path. For example, the control device 5 confirms the communication band required by the SLA based on the policy, and selects the virtual U-Plane 31 that can secure the communication band corresponding to the SLA. For example, the control device 5 can manage the communication band used in each virtual U-Plane 31 and the maximum communication band that can be secured in each virtual U-Plane 31, and the free band of each virtual U-Plane 31. Can select a gateway that meets the requirements of the SLA. Further, the control device 5 can associate a communication path with an SLA equal to or greater than a predetermined value with a virtual U-Plane 31 with an operation load equal to or less than a predetermined value.
  • SLA Service Level Agreement
  • the policy DB 54 can store a plurality of types of policies.
  • the policy DB 54 can store the policy illustrated in FIG. 42 and the policy illustrated in FIG. 44.
  • the control device 5 can select the virtual U-Plane 31 based on a plurality of types of policies stored in the policy DB 54.
  • the management device 6 is provided, and the control device generates control information used for selecting the virtual U-Plane 31 associated with the communication path.
  • the operator of the communication system manages the control device via the management device 6.
  • a plurality of control devices are assumed to be distributed in the communication system. In such a case, by managing the control device through the management device 6, the operator of the communication system can efficiently manage the communication system.
  • the control device 5 notifies the control device 5 of the control information, so that the control device 5 refers to the control information in accordance with the virtual U-Plane 31 dynamically added, and adds the virtual U -A communication path corresponding to Plane 31 can be determined.
  • the management device 6 for controlling the correspondence between the communication path and the virtual U-Plane 31 is shown.
  • the management device 6 is a gateway exemplified in the first and second embodiments. 3 can also be used to control the correspondence between the communication path 3 and the communication path.
  • Management device (first example) 47 the management device 6 includes a policy generation unit 60 and an interface 61, and communicates with the control device 5 (or the control device 5A) via the interface 61.
  • the policy generation unit 60 can generate control information for the control device 5 to select a virtual U-Plane 31 associated with a communication path.
  • the policy generation unit 60 generates control information so that, for example, the virtual U-Plane 31 corresponding to the communication quality request regarding the communication path is selected.
  • a policy stored in the policy DB 54 exemplified in the seventh embodiment is generated as the control information.
  • the policy generation unit 60 can generate information stored in the policy DB 54 (for example, information illustrated in FIGS. 42, 44, and 46) according to the operation of the operator of the communication system.
  • the policy generating unit 60 can generate a plurality of types of policies.
  • the policy generation unit 60 notifies the generated information to the control device 5 via the interface 61.
  • the control device 5 stores the policy notified from the management device 6 in the policy DB 54 and controls the communication device 4 based on the policy DB 54.
  • the policy generation unit 60 can also generate control information for the control device 5 to select a virtual U-Plane 31 associated with a communication path for each group of communication paths.
  • the policy generation unit 60 can generate the information exemplified in FIGS. 42, 44, and 46 for each group of communication paths.
  • the policy generation unit 60 can generate, for example, a policy (policy illustrated in FIG. 42) configured with a priority according to the QCI for each group of communication paths.
  • the policy generation unit 60 can generate the threshold illustrated in FIG. 44 for each communication path group, for example.
  • the policy generation unit 60 can generate the priority exemplified in FIG. 46 for each communication path group, for example.
  • the policy generation unit 60 may generate a policy for associating a communication path newly constructed by the attach procedure disclosed in the fourth embodiment with the virtual U-Plane 31.
  • An example of a policy for associating a communication path newly constructed by the attach procedure with the virtual U-Plane 31 is shown below.
  • the policy generation unit 60 generates a policy for determining, in round robin, the virtual U-Plane 31 associated with the communication path from the virtual U-Plane 31 activated in the communication system. For example, the policy generation unit 60 generates a policy for determining the virtual U-Plane 31 associated with the communication path in a round robin manner according to the load of each virtual U-Plane 31.
  • the policy generation unit 60 generates a policy based on information regarding the location where the terminal 1 stays, such as E-UTRAN Cell ID. For example, the policy generation unit 60 generates a policy for determining the virtual U-Plane 31 associated with the communication path based on at least one of the conditions exemplified below.
  • -Communication path corresponding to a predetermined Cell ID-Communication path corresponding to any of a plurality of Cell IDs (for example, communication path corresponding to any of a plurality of adjacent cells)
  • a communication path corresponding to a predetermined base station A communication path corresponding to any of a plurality of base stations (for example, a communication path corresponding to any of a plurality of adjacent base stations)
  • the policy generation unit 60 generates a policy indicating that the communication path corresponding to the Cell ID “a” is associated with the virtual gateway “A”. Further, for example, the policy generation unit 60 generates a policy indicating that the communication path corresponding to the cell ID “b” or “c” is associated with the virtual gateway “B”. Further, for example, the policy generation unit 60 creates a policy indicating that the communication path corresponding to the Cell ID “d” is associated with the gateway selected from the virtual gateways “C”, “D”, and “E” by the round robin. Generate.
  • the policy generation unit 60 generates a policy based on information on the QoS characteristic of the communication path. For example, the policy generation unit 60 generates a policy for determining the virtual U-Plane 31 associated with the communication path based on at least one of the conditions exemplified below. -Communication path corresponding to a predetermined QCI value-Communication path corresponding to one of a plurality of QCI values
  • the policy generation unit 60 generates a policy indicating that the communication path having the QCI value “5” is associated with the virtual gateway “A”. For example, the policy generation unit 60 generates a policy indicating that the communication path corresponding to the QCI value “1” or “3” is associated with the virtual gateway “B”. Further, for example, the policy generation unit 60 associates the communication path corresponding to the QCI value “4” with the gateway selected by the round robin from the virtual gateways “C”, “D”, and “E”. Is generated.
  • the policy generation unit 60 determines the communication path based on the conditions (for example, the conditions exemplified below) combining the above (2) and (3).
  • a policy for determining the virtual U-Plane 31 to be associated with the user may be generated.
  • the policy generation unit 60 may generate a policy for determining the virtual U-Plane 31 to be associated with the communication path group based on the attribute of the communication path group exemplified in the sixth embodiment. . Examples of communication path group attributes are shown below.
  • ⁇ Group by terminal 1's stay area E-UTRAN Cell ID, etc.
  • Communication status of terminal 1 by charging characteristics normal charging, prepaid billing, flat rate, etc.
  • charging characteristics normal charging, prepaid billing, flat rate, etc.
  • PDN Packet Data Network
  • Service types that need to be chained after leaving the communication path ⁇ QoS characteristics
  • Terminal 1 status IDLE status, CONNECTED status
  • the policy generation unit 60 when the communication path belongs to a group of prepaid billing characteristics, the policy generation unit 60 generates a policy indicating that the communication path is associated with the virtual gateway “A”.
  • the management device 6 can generate a policy, notify the control device 5 and operate the control device 5 according to the policy. Further, the management device 6 can also operate the route information DB 50 of the control device 5 as described below.
  • Management device (second example)
  • the management device 6 illustrated in FIG. 48 includes a UI (User Interface) display unit 62, a control unit 63, and a display 64 in addition to the configuration of FIG.
  • the UI display unit 62 displays a user interface as shown in the example of FIG.
  • the operator of the communication system can operate the user interface illustrated in FIG. 49 to operate the correspondence between the communication path and the virtual gateway.
  • the control unit 63 operates the route information DB 50 of the control device 5 based on the correspondence relationship between the communication path and the virtual gateway determined according to the operation of the operator. For example, it is assumed that the operator has changed the virtual gateway corresponding to the communication path with the communication path identifier “A” from the virtual gateway (a) to (e). In this case, the control unit 63 operates the route information DB 50 to change the virtual gateway corresponding to the communication path identifier “A” from the virtual gateway (a) to (e).
  • FIG. 49 shows an example of a GUI (Graphical User Interface) 700 displayed on the display 64 by the UI display unit 62.
  • the GUI 700 includes a network display window 701 and an operation window 702.
  • a network display window 701 displays an outline of the network configuration of the communication system.
  • the operation window 702 can display, for example, network objects including communication paths, virtual U-Planes 31 constituting gateways, and servers 33 corresponding to the virtual U-Planes 31.
  • the operation window 702 can display information on attributes (property) of the network object including the communication path and the virtual U-Plane 31. For example, the operator can select the virtual U-Plane 31 associated with the communication path with reference to information on the attribute of the network object.
  • the operation window 702 can display, for example, the IDs of the virtual U-Plane 31 and the server 33, the loads of the virtual U-Plane 31 and the server 33, and further, for example, the number of communication paths associated with the virtual U-Plane 31, the virtual U-Plane 31, The throughput of the U-Plane 31 and the free communication band of the virtual U-Plane 31 can be displayed as attributes of the network object.
  • the operation window 702 can display, for example, QCI related to a communication path, SLA of a service related to a communication path, and the like as attributes of a network object.
  • the operation window 702 can also display a plurality of attributes.
  • the operation window 702 can display the communication path set for each virtual U-Plane 31.
  • the operator can switch the communication path displayed in the window 702 to another virtual U-Plane 31 by Drag & Drop operation.
  • the operator can switch the communication path to the virtual U-Plane 31 with a low load by referring to the loads on the virtual U-Plane 31 and the server 33 displayed in the window 702.
  • the control unit 63 can change the correspondence relationship between the communication path and the virtual U-Plane 31 by operating the route information DB 50 of the control device 5.
  • the control unit 63 generates control information related to the correspondence between the communication path and the virtual U-Plane 31 by combining network objects, and notifies the control device 5 of the generated control information to change the route information DB 50.
  • the control device 5 notifies the communication device 4 of a change in the correspondence between the communication path and the virtual U-Plane 31 in response to the change of the route information DB 50.
  • Management device (third example)
  • the management apparatus 6 illustrated in FIG. 50 can directly control the path information DB 50 of the control apparatus 5 without generating information to be stored in the policy DB 54.
  • the management device 6 includes a route information generation unit 65 and an interface 61.
  • the route information generation unit 65 can generate control information for the control device 5 to select a virtual U-Plane 31 associated with a communication path.
  • the route information generation unit 65 generates control information so that, for example, the virtual U-Plane 31 corresponding to the communication quality request regarding the communication path is selected.
  • the path information generation unit 65 generates control information in response to the addition of the virtual U-Plane 31.
  • Information to be stored in the route information DB 50 of the control device 5 is generated as control information.
  • the route information generation unit 65 determines the correspondence between the communication path and the gateway.
  • the route information generation unit 65 sets a correspondence relationship between the communication path and the gateway in the route information DB 50 of the control device 5 via the interface 61.
  • the route information generation unit 65 can also generate control information (for example, a database having a structure exemplified in the sixth embodiment) for managing gateways corresponding to communication paths in units of communication path groups. .
  • the route information generation unit 65 can generate information set in the route information DB 50 based on, for example, the policy exemplified in the seventh embodiment.
  • the route information generation unit 65 can generate information to be set in the route information DB 50 based on the policies illustrated in FIGS. 42, 44, and 46.
  • the route information generation unit 65 sends information necessary for generating information to be set in the route information DB 50 (for example, communication amount and communication time of a communication path, frequency of adding a virtual gateway, etc.) via the control device 5. Can be collected.
  • the route information generation unit 65 can generate information to be set in the route information DB 50 based on, for example, the policies exemplified in the eighth embodiment (the above policies (1) to (5)).
  • the operator uses the management device 6 to group communication paths and manage them. By grouping the communication paths, the operator can efficiently manage the correspondence between the communication paths and the virtual U-Plane 31. Further, the management device 6 groups and visualizes the communication paths separately from the control grouping performed by the control device 5 in the sixth embodiment, so that the operator can view the communication paths and the virtual U-Plane 31. Can be managed efficiently.
  • the gateway 3 and the communication path exemplified in the first and second embodiments It is also possible to use it to control the correspondence between
  • the operator can group communication paths by using the GUI 700 displayed by the management apparatus 6.
  • An operation window 702 illustrated in FIG. 51 displays an aggregation policy 703 for aggregating (grouping) communication paths established in the virtual gateway 3.
  • the aggregation policy is set based on the attribute of the communication path, for example.
  • An example of the aggregation policy 703 is shown below.
  • ⁇ Stay area of terminal 1 E-UTRAN Cell ID, etc.
  • -Charging characteristics related to terminal 1 return to terminal 1
  • -Operator ID ID of the operator of the core network to which the terminal 1 is connected
  • -State of terminal 1 IDLE state, CONNECTED state
  • PDN Packet Data Network
  • the management device 6 can aggregate communication paths based on the example of the aggregation policy 703 described above.
  • the policy disclosed in the sixth embodiment as a condition for grouping communication paths can be used as the aggregation policy 703.
  • the control unit 63 of the management device 6 aggregates communication paths based on the clicked policy in response to, for example, the operator clicking one of the policies displayed in the aggregation policy 703. For example, the control unit 63 aggregates communication paths having the same aggregation policy attribute. For example, when “QoS characteristics” is selected as the aggregation policy, as illustrated in FIG. 51, the control unit 63 aggregates communication paths having the same QCI value.
  • the control unit 63 cancels the aggregation of communication paths and displays each communication path individually in response to, for example, clicking on “cancel aggregation” displayed in the aggregation policy 703.
  • the maximum number of communication paths managed by the GUI 700 is nine types for each virtual gateway 3 (defined by standard specifications such as 3GPP). Nine types of QCI are collected).
  • the number of communication paths managed by the operator can be reduced in a pseudo manner, and the management cost of the operator is greatly reduced.
  • the control unit 63 can change the route information DB 50 of the control device 5 in response to the operator collecting communication paths according to the aggregation policy.
  • FIG. 52 shows an example of the route information DB 50 when communication paths are aggregated based on the QCI.
  • the control unit 63 aggregates the communication paths based on the attribute of the aggregation policy (QCI in the example of FIG. 52), and associates each of the aggregated communication paths with the attribute of the aggregation policy (group ID in FIG. 52).
  • the control unit 63 changes the route information DB 50 so that the communication paths aggregated based on the QCI and the QCI value (group ID) are associated with each other.
  • the management device 6 changes the route information DB 50 as described above, the control device 5 can control the communication device 4 by the method exemplified in the sixth embodiment.
  • the control unit 63 of the management device 6 or the control unit 51 of the control device 5 can execute communication path reconstruction when the state of the communication path is changed from the attribute of the aggregate policy, for example.
  • Reconstructing a communication path means reconstructing a communication path after releasing the communication path.
  • the control unit 63 or the control unit 51 can reconfigure the corresponding communication path when the communication path state is changed from the attribute of the aggregate policy. For example, when the communication amount of the terminal 1 per unit period exceeds a certain value, the control unit 63 or the control unit 51 prompts the reconstruction of the corresponding communication path. Further, the route information DB 50 may be changed as necessary.
  • the communication path can belong to a group suitable for the current state.
  • control device 5 and the management device 6 reassign the communication path to the virtual U-plane 31 when the virtual U-plane 31 is increased or decreased by causing the communication path to belong to the group that matches the current state.
  • An excessive increase in the load can be suppressed. This is because if there is a communication path that does not belong to the group that matches the current state, it is necessary to control the communication path separately from the grouping and control.
  • FIG. 53 shows an example in which the operator manages the communication paths aggregated. For example, the operator selects an aggregated communication path, and drags and drops the selected communication path to another virtual gateway 3 to switch the correspondence relationship between the aggregated communication path and the virtual gateway 3.
  • the control unit 63 changes the route information DB 50 of the control device 5 in response to switching of the correspondence relationship between the aggregated communication path and the virtual gateway 3.
  • FIG. 54 shows an example in which the control unit 63 changes the route information DB 50.
  • the control unit 63 changes the gateway corresponding to the group using the group ID (ID corresponding to the QCI value in the example of FIG. 54) as a key.
  • the control unit 63 switches the virtual gateway 3 corresponding to the aggregated communication path having the QCI value “3” from the gateway having the ID “X” to the gateway having the ID “XX”.
  • the control device 5 changes the route information DB 42 of the communication device 4 by the method exemplified in the sixth embodiment, for example, in response to the change of the route information DB 50.
  • control unit 63 can collectively change the gateways corresponding to the aggregated communication paths using the group ID as a key. Therefore, the control unit 63 can significantly reduce the amount of control signal and the gateway switching time, compared with the case where the gateway corresponding to each entry of the route information DB 50 is changed.
  • FIG. 55 shows an example in which the management apparatus 6 aggregates communication paths using a plurality of aggregation policies.
  • the communication paths are aggregated based on the QCI of the communication path and the state of the terminal 1.
  • the operator selects a communication path aggregated by the QCI value (“1. Click”), and selects another aggregation policy (“2. Click”).
  • the management device 6 divides and displays the aggregated communication path having the QCI value “3” according to the state of the terminal 1 (IDLE state or CONNECTED state).
  • the control unit 63 changes the route information DB 50 of the control device 5 in response to the communication paths being aggregated based on a plurality of aggregation policies.
  • FIG. 56 shows an example of the route information DB 50 based on a plurality of aggregation policies. As shown in the example of FIG. 56, the control unit 63 responds to the addition of the aggregate policy regarding the state of the terminal 1 to the aggregated communication path having the QCI value “3” as in the example of FIG. The route information DB 50 is changed.
  • the present invention is applicable to general communication systems that communicate via a communication path.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Le problème décrit par la présente invention est de proposer une technique de communication et une technique de commande de voies de communication qui peuvent éviter les répercussions sur les services de communication lors de la commutation des trajets des voies de communication. La solution selon l'invention porte sur un appareil de communication (4B) servant à réaliser des communications par le biais de voies de communication établies dans un réseau, et comportant : un premier moyen (43, 46) qui peut recevoir des consignes de traitement incluant une règle d'identification, utilisée pour identifier un flux de communication sur la base d'informations comprenant un identificateur de voie de communication, et une règle de traitement indiquant de transférer un paquet, qui a été identifié selon la règle d'identification, à une passerelle correspondant à l'identificateur de voie de communication; et un second moyen (44, 45) qui peut transférer, sur la base des consignes de traitement, un paquet reçu à la passerelle correspondant à l'identificateur de voie de communication du paquet reçu.
PCT/JP2014/004364 2013-08-26 2014-08-25 Appareil et procédé de communication dans un système de communication, et appareil et procédé de commande de voies de communication WO2015029418A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2015533991A JP6500777B2 (ja) 2013-08-26 2014-08-25 通信システムにおける通信装置および方法、通信パスの制御装置および方法

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201361870119P 2013-08-26 2013-08-26
US61/870,119 2013-08-26
JP2013-250065 2013-12-03
JP2013250065 2013-12-03

Publications (1)

Publication Number Publication Date
WO2015029418A1 true WO2015029418A1 (fr) 2015-03-05

Family

ID=52586008

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2014/004364 WO2015029418A1 (fr) 2013-08-26 2014-08-25 Appareil et procédé de communication dans un système de communication, et appareil et procédé de commande de voies de communication

Country Status (2)

Country Link
JP (1) JP6500777B2 (fr)
WO (1) WO2015029418A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021192628A1 (fr) * 2020-03-25 2021-09-30 ソニーグループ株式会社 Dispositif de commande de réseau, procédé de commande de réseau et programme

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013121841A1 (fr) * 2012-02-16 2013-08-22 株式会社エヌ・ティ・ティ・ドコモ Système de communication mobile, système de communication, nœud de commande, nœud de traitement d'appel et procédé de commande de communication

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9615318B2 (en) * 2011-09-20 2017-04-04 Nokia Solutions And Networks Oy Multiplexing core networks in RAN sharing

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013121841A1 (fr) * 2012-02-16 2013-08-22 株式会社エヌ・ティ・ティ・ドコモ Système de communication mobile, système de communication, nœud de commande, nœud de traitement d'appel et procédé de commande de communication

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SHIGEAKI MAEDA: "OpenFlow ver1.1 Oyobi verl.2 no Tsuika Kino to Katsuyorei", THINK IT, 23 February 2012 (2012-02-23), Retrieved from the Internet <URL:http://thinkit.co.jp/story/2012/02/23/3388> *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021192628A1 (fr) * 2020-03-25 2021-09-30 ソニーグループ株式会社 Dispositif de commande de réseau, procédé de commande de réseau et programme

Also Published As

Publication number Publication date
JPWO2015029418A1 (ja) 2017-03-02
JP6500777B2 (ja) 2019-04-17

Similar Documents

Publication Publication Date Title
WO2015029420A1 (fr) Appareil de communication, procédé de communication, appareil de commande et appareil de gestion dans un système de communication
US9819578B2 (en) Communication device and method in a communication system, and device and method for communication path control
JP6436103B2 (ja) 情報処理装置、通信方法、ネットワーク制御装置、ネットワーク制御方法、通信システムおよびプログラム
US10638376B2 (en) RAN based gateway functions
EP3107249B1 (fr) Dispositif de traitement d&#39;informations, procédé de communication, dispositif de commande de réseau, procédé de commande de réseau et programme d&#39;ordinateur
WO2015029417A1 (fr) Appareil et procédé de communication dans un système de communication, et appareil et procédé de commande de voies de communication
WO2015133124A1 (fr) Serveur, dispositif de commande, dispositif de gestion, système de communication, procédé de communication, procédé de commande, procédé de gestion, et programme
WO2015133126A1 (fr) Serveur, dispositif de commande, dispositif de gestion, système de communication, procédé de communication, procédé de commande, procédé de gestion, et programme
WO2015133125A1 (fr) Serveur, dispositif de commande, dispositif de gestion, système de communication, procédé de communication, procédé de commande, procédé de gestion, et programme
US20170164253A1 (en) Communication system, communication apparatus, communication method, and program
JP6414065B2 (ja) 通信システムにおける通信装置および方法、通信パスの制御装置および方法
JP6515920B2 (ja) 通信装置、通信方法、通信システムおよびプログラム
US20170099221A1 (en) Service packet distribution method and apparatus
WO2015122178A1 (fr) Dispositif de traitement d&#39;informations, procédé de communication, dispositif de commande de réseau, procédé de commande de réseau, système de communication, et programme
WO2015141227A1 (fr) Dispositif de communication, procédé de communication, système de communication et programme
WO2015029418A1 (fr) Appareil et procédé de communication dans un système de communication, et appareil et procédé de commande de voies de communication
WO2015029419A1 (fr) Appareil et procédé de gestion dans un système de communication
US20170134505A1 (en) Communication apparatus, communication method, and program
WO2015141229A1 (fr) Dispositif de communication, procédé de communication, système de communication et programme

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14840157

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2015533991

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14840157

Country of ref document: EP

Kind code of ref document: A1