WO2016148049A1 - Communication device, system, and method, and allocation device and program - Google Patents

Abstract

The purpose of the present invention is to optimize the allocation of traffic-processing resources and to increase the efficiency of resource use. In the present invention, traffic is allocated to a prescribed virtual network function in accordance with a service level that is set so as to correspond to information related to the traffic, and, depending on the allocation results, the traffic is forwarded to the prescribed virtual network function.

Description

COMMUNICATION DEVICE, SYSTEM, METHOD, ALLOCATION DEVICE, AND PROGRAM

[Description of related applications]
The present invention is based on a Japanese patent application: Japanese Patent Application No. 2015-051224 (filed on March 13, 2015), and the entire description of the application is incorporated herein by reference.
The present invention relates to a communication device, a system, a method, an allocation device, and a program, and more particularly, to a device, a system, a method, and a program suitable for application to a mobile network.

MVNO (Mobile Virtual Network Operator), which is one of the business forms that provide mobile communication services, does not have its own wireless communication infrastructure, but MNO (Mobile Network Operator: Mobile operator) ) Borrow necessary infrastructure such as wireless communication infrastructure from) and conduct mobile communication business under own brand.

<L3 connection>
In MVNO with layer 3 (L3: network layer) connection, as schematically shown in FIG. 19A, layer 2 (Layer2: L2) for IP (Internet Protocol) packet transfer from an end user (End User) The GTP (GPRS (General Packet Radio Service) Tunneling Protocol) session is terminated in the MNO network (core network). An MVNO connected to L3 only needs to prepare a router (Router) or the like that provides an L3 communication service in the MVNO network 3.

FIG. 19 (B) is a diagram schematically showing an example of a form of MVNO with L3 connection. 19B shows an EPC (Evolved Packet Packet Core) that accommodates the existing 2G / 3G network and LTE (Long Term Evolution Evolution) access network defined by 3GPP (3rd Generation Partnership Project), and MNO network 2 In addition, a configuration example in which the MVNO network 3 includes a router such as an edge router, a server (not shown), and the like and is connected to the Internet 4 is schematically shown. Here, each node of EPC will be outlined (for details, refer to 3GPP TS 23.401 V9.5.0 (2010-06), etc.).

MME (Mobility Management Entity) performs various processes such as mobility management and authentication of terminal (mobile terminal) 1 (User Equipment: UE), setting of user data transfer path, and the like. MME also performs user authentication in cooperation with HSS (Home Subscriber Server) (holding subscriber profiles). Further, the MME connects to a control station / base station (RNC (Radio Network Controller / NodeB)) of SGSN (Serving GPRS Support Node) (3rd Generation: 3G) to register the location of the 3G terminal. The MME sets and releases the user data transfer path in the section (S1-U) from the SGW (Serving Gateway) to the base station eNB (eNodeB).

The SGW transmits and receives user data to and from the eNB, and sets and releases the communication route with the PGW (PDN (Packet Data Network) Gateway). The PGW is connected to a packet data network (PDN) such as an IMS (IP Multimedia Subsystem) or the Internet, and assigns an IP (Internet Protocol) address (private IP address) to the terminal. PCRF (Policy and Charging Rules) is a policy control device that determines policy control and charging control rules such as QoS (Quality of Service). The PGW and SGW perform policy control, for example, on a packet basis, based on notification information (policy) from the PCRF. In FIG. 19B, reference numerals S11 and the like of the lines between the nodes represent interfaces, broken lines indicate signals (data) of the control plane (C-Plane), and solid lines indicate user planes (U-Plane). Represents.

In the case of L3 connection, MVNO does not directly operate PGW (or GGSN (Gateway GPRS Support Node) (not shown)) that is a packet relay device on the network 2 of MVO. The IP address for the terminal (mobile terminal) 1 is issued by the MNO PGW or the like. In L3 connection, communication control in MVNO is performed in L3 (network layer). In addition, the packet transfer amount, which is information necessary for charging or the like, is generally the transfer amount in units of days or months provided from the MNO side.

<L2 connection>
In the MVNO by the layer 2 (L2: data link layer) connection, as schematically shown in FIG. 20A, the end user's GTP session is extended to the MVNO. The MVNO needs to install a packet relay device on the MVO network. The L2 GTP tunnel is terminated at the PGW (or GGSN) of the MVNO network, for example.

FIG. 20 (B) is a diagram schematically showing an example of an L2 connection MVNO configuration. FIG. 20B schematically shows a configuration example in which the EPC is the MNO network 2, the MVNO network 3 is provided with the PGW, and is connected to the Internet 4.

The L2 connection is a connection form in which the end user terminal 1 and the MVNO PGW are connected by an L2 tunnel (GTP). Since the PGW is on the MVNO side, the MVNO can perform various controls. Further, various control servers are arranged adjacent to the PGW on the MVNO network 3. For example, a RADIUS server (not shown) responsible for user management and authentication, OCS (Online Charging System) (not shown) that manages user data capacity and billing information, PCRF that manages communication rules for each user (Policy and Charging Rules Function), PCEF (Policy and Enforcement Function) (not shown) that applies a rule to the PGW to control packet transfer. Packet relay devices and servers such as PGW are technically advanced and expensive compared to IP routers, etc. In L2 connection MVNO, the cost of operation and maintenance of PGW etc. requires L3 connection only Although it is expensive compared to the form, the MVNO with L2 connection can perform band control or the like by PGW or the like on the network 3 of the MVNO.

ETSI GS NFV-MAN 001 V1.1.1 (2014-12) Network Functions Virtualization (NFV); Management and Orchestration January 25, 2015 Search Internet <http://www.etsi.org/deliver/etsi_gs/NFV-MAN /001_099/001/01.01.01_60/gs_NFV-MAN001v010101p.pdf>

Below, the analysis performed by the present inventors is given.

As described above, the MVNO borrows from the lending source MNO without providing wireless communication facilities and the like, and provides services to the user at low cost. For this reason, when MVNO and MNO services are compared, MVNOs are often limited. For example,
・ Slow communication speed
・ Maximum usage capacity per month is low,
・ There are no additional functions such as voice calls.
Etc.

When an MVNO tries to impose restrictions on user traffic, for example, at present, restrictions are imposed by traffic shaping (bandwidth control) in a specific node such as a gateway in the MVNO network. For example, traffic shaping is performed on an S1-U interface between an eNB and an SGW in an EPC that is an MVNO network.

MVNO pays MNO for the amount of resources and services (for example, bandwidth) provided by MNO in principle. For example, in an L3 connection MVNO, charging is generally performed by a connection band between the MVNO and the MNO (for example, a band at the reference point SGi in FIG. 19B). In MVNO, a service (for example, bandwidth) corresponding to the amount (customer payment amount, etc.) is provided.

Therefore, it is desirable to be able to flexibly control services (for example, bandwidth) provided to customers.

However, bandwidth control is generally performed based on the predicted traffic volume. For this reason, flexible and accurate bandwidth control is difficult. For example, depending on the traffic volume, a considerable amount of error may occur between the predicted value and the actual value.

In particular, real-time control of bandwidth control is not possible with an L3-connected MVNO that does not have a packet transfer device such as PGW. For this reason, user traffic that does not require a high-performance and high-performance device may be assigned to the high-performance and high-performance device. Conversely, user traffic that requires a high-performance, high-performance device may be assigned to a low-function, low-performance device. In either case, it is far from effective use of resources and services.

Accordingly, the present invention has been made in view of the above problems, and its purpose is to provide an apparatus, a system, a method, and a program for achieving appropriate allocation of resources for processing traffic and efficient use of resources. Is to provide.

According to one aspect of the present invention, the first means (control) operable to assign the traffic to a predetermined virtual network function according to a service level set corresponding to information related to the traffic. Unit: a first unit) and second means (processing unit: second unit) operable to transfer the traffic to the predetermined virtual network function according to the allocation result An apparatus is provided.

According to another aspect of the present invention, the traffic is allocated to a predetermined virtual network function according to a service level set corresponding to information related to the traffic, and the predetermined traffic is determined according to the allocation result. A method is provided for forwarding the traffic to a virtual network function.

According to still another aspect of the present invention, according to a service level set corresponding to information related to traffic, the traffic is assigned to a predetermined virtual network function, according to the assignment result, There is provided a program for causing a computer to execute a process of transferring the traffic to a virtual machine that realizes the above. Furthermore, according to the present invention, a recording medium (non-transitorytranscomputer readable recording medium) such as a computer-readable storage device that records the program is provided.

According to still another aspect of the present invention, a plurality of virtual network functions having different processing performances are provided on a plurality of virtual machines, and a plurality of virtual network functions are provided according to a service level associated with received traffic. A server device is provided in which one of them is selected and the traffic is allocated.

According to the present invention, it is possible to optimize allocation of resources for processing traffic and increase the efficiency of resource utilization.

(A), (B) is a figure explaining an example of the basic concept of this invention. (A), (B) is a figure explaining an example of the allocation apparatus of FIG. It is a figure explaining Embodiment 1 of this invention. It is a figure explaining an example of Embodiment 1 of the present invention. (A), (B) is a figure explaining Embodiment 1-1 of this invention. It is a figure explaining the modification of Embodiment 1-1 of this invention. (A), (B) is a figure explaining Embodiment 1-2 of this invention. (A), (B) is a figure explaining Embodiment 1-3 of this invention. (A), (B) is a figure explaining Embodiment 1-4 of this invention. It is a figure explaining Embodiment 2 of this invention. It is a figure explaining an example of Embodiment 2 of the present invention. (A) and (B) are diagrams for explaining the embodiment 2-1 of the present invention. (A), (B) is a figure explaining Embodiment 2-2 of this invention. (A), (B) is a figure explaining Embodiment 2-3 of this invention. (A), (B) is a figure explaining Embodiment 2-4 of this invention. It is a figure explaining Embodiment 3 of this invention. (A) thru | or (D) is a figure explaining Embodiment 4 of this invention. (A) thru | or (D) is a figure explaining Embodiment 5 of this invention. (A), (B) is a figure explaining MVNO of L3 connection. (A), (B) is a figure explaining MVNO of L2 connection.

Embodiments of the present invention will be described below.

According to one aspect of the present invention, a user of an MNO or MVNO carrier using a virtual network function (Virtual Network Function: Virtual VNF) in which part or all of the functions of a network device, a node, etc. are virtualized on a server device. To provide services.

First, the network function virtualization technology that is the premise of the present invention will be outlined. In NFV (Network Functions Virtualization), a technology that virtualizes network functions, virtual machines on the virtualization layer (Virtualization Layer) such as the hypervisor (HyperVisor) and virtual machine monitor (Virtual Machine Monitor (VMM)) A network function is realized in software by an application (VNF) running on (Virtual Machine: VM). For example, the functions of dedicated devices (EPC nodes such as MME, PGW, SGW, etc.) can be implemented as VNFs that run on VMs on the virtualization layer. The hardware resources such as computing, storage, and network of the server device and the virtualization layer constitute an NFVI (Network Function Virtualization Service) infrastructure that is a VNF execution platform. As a management unit for controlling each of NFVI and VNF, VIM (Virtualized Infrastructure Manager) and VNFM (Virtual Network Function Manager) are provided, and NFVO is provided for managing the entire network service (see Non-Patent Document 1, for example).

According to one aspect of the present invention, the allocating device (111 in FIG. 1A) determines whether the traffic to be transferred to the VNF depends on which carrier or user the traffic is transferred to. Controls the assignment to the VNF. In other words, the assignment of the VNF (VM) as the traffic transfer destination is controlled according to the service level set for at least one of the carrier (for example, MNO or MVNO carrier), the user, the content of the traffic, etc. To do. Alternatively, assignment of a VNF that is a traffic transfer destination may be determined according to the type of the user terminal (mobile terminal) that is the transmission source or destination of the traffic.

Control of traffic allocation to the VNF by the allocation device (111 in FIG. 1A) may be performed on a virtual machine (VM) basis on which the VNF operates. At that time, a group consisting of one or a plurality of virtual machines (VMs) is provided according to, for example, functions, etc. (In this case, VNFs operating on virtual machines (VMs) in the same group provide the same functions. ), Select one group from a plurality of groups, and then select one group from the group according to a predetermined scheduling algorithm (for example, a randomly assigned random method or a sequentially assigned round robin method). A virtual machine may be selected, and the selected virtual machine may be a traffic assignment destination.

The allocation device (111 in FIG. 1A) stores the correspondence between the VNF and the virtual machine (VM) that realizes the VNF in a table or the like, and executes the virtual machine (VM that executes the traffic allocation destination VNF) The traffic may be forwarded to the address. In addition, one VNF consists of a combination of multiple Virtual Network Functions (Components), and multiple VNFCs support multiple virtual machines (VMs). (VM) may be executed. Also in this case, the assigning device (111 in FIG. 1A) stores in advance the correspondence between the VNF and the virtual machine (VM) that is the traffic transfer destination among the plurality of virtual machines (VM) that execute the VNF. It is good also as composition to do.

Alternatively, the allocating device (111 in FIG. 1A) uses the VNF identification information (or VDU (Virtual Deployment) Unit) identification information) to which traffic is allocated as an unused area in the header of the packet to be transferred ( For example, the TOS (Type ヘ ッ ダ of Service) of the IP header and the unused field such as the bit field of the flag are set and transferred to the server device (100 in FIG. 1A), and the server device (100 in FIG. 1A) is transferred. ) Side control unit (hypervisor, etc.) analyzes the header of the packet, etc., determines the VNF of the packet transfer destination, and sends the packet to the VNF via the virtual switch (vSwitch) etc. that realizes the VNF You may make it forward.

Alternatively, the traffic allocation destination may be controlled in units of server devices (physical servers) in which VNFs are arranged. Also in this case, the allocation device (111 in FIG. 1A) may be configured to store and hold in advance the correspondence between the VNF and the server device (traffic transfer destination server device) on which the VNF is arranged.

In addition, when controlling traffic allocation in units of server devices (physical servers), a group of one or more server devices is provided with a plurality of groups according to functions, for example (in this case, a plurality of servers in the same group). The device provides the same function), and selects one group from a plurality of groups, and then, from the selected group, according to a predetermined scheduling algorithm (for example, a random method or a round robin method) One server device may be selected.

Referring to FIG. 1A, the server device (physical server) 100 includes a control unit 101, a plurality of virtual machines (VM) 102A to 102C, and a plurality of VNFs 103A to 103C. The plurality of VNFs 103A to 103C (VNF1A, VNF1B, VNF1C,...) Are, for example, the same virtual network function and may have different performance. In this specification, in notations such as “VNF1A”, “VNF1B”, and “VNF1C”, “1” represents a function, and “A”, “B”, and “C” represent a performance class. Although not particularly limited, each VNF 103 may be a virtualized network device or part thereof. For example, the VNF 103 may be implemented as application software that virtualizes part or all of the functions such as the PGW of the MVNO network 3 in FIG. 20B and operates on a virtual machine (VM). Alternatively, some or all of the functions of the router of the MVNO network 3 in FIG. 19B or a server (not shown) may be virtualized and implemented as application software that operates on a virtual machine (VM). Good. There is no limitation on the number of the plurality of VNFs 103.

The control unit 101 includes, for example, a memory such as a CPU (Central Processing Unit), a RAM (Random Access Memory), a storage such as an HDD (Hard Disk Drive), and a hardware resource (HW) such as a network interface controller (Network Interface Controller: NIC). ) A virtualization layer such as a hypervisor that virtualizes 104 and assigns it to a virtual machine (VM) is provided.

In FIG. 1A, an example in which the control unit 101 includes a virtual switch (vSwitch) as virtual hardware is shown for ease of explanation. For example, when conforming to the NFV standard specification, the control unit 101 and the hardware resource (HW) 104 constitute an NFVI that provides a virtualization infrastructure for executing a virtual machine (VM) for VNF. The NFVI is controlled by an NFV-MANO (Management and Orchestration) VIM (Virtualization Infrastructure Manager) (not shown) for setting a virtual machine (VM), VNF generation, stop scaling, and updating, for example.

Although not particularly limited, for example, VNF1A103A is a high function (performance) type, VNF1B103B is a medium (standard) function (performance) type, and VNF1C103C is a low function (performance) type. A VNF package from a maintenance terminal (not shown) or OSS (Operations Support Systems) to an NFV management device (for example, NFV-MANO (including NFV Orchestrator (NFVO), VNF Manager (VNFM), VIM))) By registering (on-boarding VNF Package) or updating (update), setting or updating of the VM image (image file of the virtual machine VM) corresponding to the VNF is performed. The processing performance of the VNF is controlled by, for example, the number of virtual CPUs (vCPUs) allocated to the virtual machine (VM) on which the VNF operates, the capacity of virtual memory, the number and bandwidth of virtual NICs, the capacity of virtual storage, and the like. These are set by definition information of a VNF descriptor that is referred to when instance information such as VNF is generated by NFV Orchestrator (NFVO) (see Non-Patent Document 1 for details).

In the example shown in FIG. 1B, carrier A is the first service level (high speed, high quality), but is a high-priced contract. Carrier A may be an MNO carrier or an MVNO carrier. On the other hand, the carrier C (MVNO carrier) is the third service level (low speed, low quality), but the service level (second service level) of the carrier B (MVNO carrier) is the first and third service levels. It is assumed that it is in the middle.

In this case, the allocation device 111 allocates the traffic of carriers A, B, and C to VNF1A, VNF1B, and VNF1C, respectively.

In other words, user traffic of carriers A, B, and C (traffic of terminals contracted with carriers A, B, and C) is transferred to virtual machines (VMs) that implement VNF1A, VNF1B, and VNF1C, respectively, and VNF1A, Processed by VNF1B and VNF1C. For example, a packet (for example, information specifying VNF or identification information of a virtual machine that realizes VNF is set in the header) received by the NIC or the like of the server apparatus 100 is transmitted to the hypervisor, virtual switch (vSwitch), or the like. The packet (frame) data from the VNF is transmitted to the virtual machine (VM) that realizes the VNF via the virtual switch, NIC, etc. of the server device 100, the router of the MVNO network, etc. It is transferred to a destination (destination node) via a packet data network such as IMS.

According to an aspect of the present invention, the allocation of the VNF that processes traffic is controlled for each carrier corresponding to the service level. That is, the allocation device 111 in FIG. 1A changes the allocation of user traffic to one of the high function VNF 1A to the low function VNF 1C, for example, depending on the carrier. When carrier A is an MNO that lends communication equipment to an MVNO carrier, the user traffic of MNO carrier A is assigned to a high-performance (or highest-performance) VNF among a plurality of VNFs having the same function.

It should be noted that the service level illustrated in FIG. 1B is merely illustrative and is not limited to three stages. Further, the service level granularity may be further classified based on the relationship between the combination of communication speed (bandwidth) (for example, downlink communication speed) and QoS (Quality of Service) and the contract amount. For example, for each carrier,
・ High speed and high quality: high price,
・ High speed and medium quality: Slightly expensive
・ Medium speed and medium quality: Intermediate
・ Medium speed and low quality: Intermediate
・ Low speed and medium quality: Slightly low
-Low speed and low quality: low price.

In this case, the allocating device 111 may allocate traffic to a high performance among a plurality of VNFs having the same function to an MVNO carrier with a large contract among MVNO carriers. On the other hand, in the case of an MVNO carrier with a low-price contract, traffic may be assigned to a low-performance one among a plurality of VNFs having the same function.

When traffic is assigned on a carrier basis, the traffic assignment destinations of the terminals of multiple subscribers on the same carrier are the same. Alternatively, as will be described in an embodiment described later, the traffic allocation to the VNF may be performed in units of users instead of in units of carriers. When assigning VNFs for each user, for example, even for subscribers of the same carrier, the service level is set for each subscriber (user) according to the contract contents of the subscriber. As a result, the traffic of multiple subscribers (for example, users of MVNO carriers) on the same carrier may be assigned to different VNFs.

In FIG. 1A, a plurality of virtual machines (VMs) that operate a plurality of VNFs are mounted on different server devices, and traffic is assigned to VNFs on a server device basis for each carrier or each user. You may make it control to.

According to one aspect of the present invention, by controlling the allocation of VNFs in units of carriers or in units of users, more flexible control is possible, and effective use of resources can be achieved.

FIG. 2 (A) is a diagram schematically illustrating an example of the configuration of the assignment device 111 in FIG. 1 (A). The allocation device 111 includes a control unit 112, a processing unit 113, and a storage unit 114. FIG. 2B is a diagram schematically illustrating information stored in the storage unit 114.

The control unit 112 of the allocation device 111 identifies the terminal that transmitted the packet from the terminal identification information (address information) included in the header of the received packet and the like, and transmits the packet to the virtual machine that realizes the VNF corresponding to the terminal. The processing unit 113 is controlled so as to transfer.

Under the control of the control unit 112, the processing unit 113 of the allocation device 111 identifies virtual machine (VM) identification information (for example, a virtual machine (VM) that realizes the corresponding VNF as transmission destination information in the header of a packet transmitted from the terminal side. The host name of the virtual machine, the IP address of the virtual NIC (vNIC) / MAC (Media Access Control) address, etc.) may be set, or may be transmitted to the transmission port addressed to the virtual machine.

As shown in FIG. 2B, for example, the storage unit 114 of the assignment device 111 stores the correspondence between the terminal identification information (for example, an address) and the assignment destination VNF as a table structure. The correspondence between the terminal identification information (address) stored and held in the storage unit 114 and the assigned VNF is stored in the HSS or the like as needed in the attach process or the like that the terminal registers in the network via the base station. Based on the user's contract information and the like, the control unit 112 associates the carrier contracted with the terminal (MNO / MVNO) with the terminal identification information (address) of the terminal, and stores the terminal identification information (address ) And the assignment destination VNF corresponding to the carrier may be stored. In the assignment device 111, the terminal identification information (address) and assignment destination storage processing in the storage unit 114 may be performed at the time of establishment of an EPS (Evolved Packet System) session after authentication by the MME in the attach process. A session creation request (Create Session Request) is transmitted from the MME to the SGW, a session creation request (Create Session Request) is transmitted from the SGW to the PGW, and a tunnel is established between the SWG and the PGW. The attach request message transmitted from the terminal to the MME includes IMSI (International Mobile Subscriber Identity) which is subscriber identification information. IMSI is included in the session creation request (Create Session Request) message transmitted from the MME to the SGW and from the SGW to the PGW. For example, the allocating device 111 captures the session generation request message, acquires the IMSI, and refers to the contract information of the subscriber from the HSS, and determines the carrier (MNO / MVNO carrier, etc.) with which the subscriber contracts In the case of an MVNO with a high-priced contract, the allocation destination is VNFA, and in the case of a low-priced contract or intermediate MVNO, the allocation destination is the allocation destination of terminal traffic (data traffic, etc.) on a carrier basis, based on the allocation rules VNFC and VNFB. The VNF may be determined. Alternatively, the allocating device 111 may refer to service contract information of SPR (Service Profile Repository) by IMSI and determine a traffic allocation destination for each user based on the contents of the service contract of the subscriber (user). . Alternatively, the MME or the like may determine the allocation destination VNF of the terminal traffic (data traffic or the like) from the contract information of the subscriber from the HSS based on the IMSI, and notify the allocation device 111 of this. The allocation device 111 associates the IP address of the terminal and the allocation destination VNF and stores them in the storage unit 114, thereby determining the VNF of the transfer destination of the packet using the IP address of the packet header or the like as the terminal identification information. be able to. Further, the allocation device 111 is configured to correspond to the terminal identification information (address) and the allocation destination VNF (packet transfer destination VNF) corresponding to the carrier, the VNF and the server device in which the VNF is arranged, or the VNF The correspondence with the identification information (for example, host name, IP / MAC (Media Access Control) address of the virtual NIC (vNIC)) of the virtual machine (VM) realized by may be stored and held.

With this configuration, a packet transferred from the terminal after the connection of the terminal is established, the source address information extracted from the packet header (source （IP address: the IP address of the terminal) and the address of the terminal in the storage unit 114 are allocated. The VNF is determined from the correspondence of the destination VNF, and the processing unit 113 transfers the packet to a server device or a virtual machine (VM) on which the corresponding VNF operates. The processing unit 113 may include an input port and a switch having a plurality of output ports.

<Embodiment 1>
FIG. 3 is a diagram illustrating the configuration of the first embodiment. In FIG. 3, the terminal 1 and the base station (eNB) 20 are the same as those described with reference to FIG. 3, the SGW 30 has the same basic configuration as that described with reference to FIG. 20A and the like, but has the function of the allocation device 111 described with reference to FIGS. 1 and 2. .

In FIG. 3, the terminal 1 (mobile terminal) establishes a network connection by wireless connection with the base station (eNB) 20, and connects to a destination node (for example, a node (not shown) of the Internet 40 in FIG. 20A). .

In the first embodiment, VNFs 1A to VNF1C having the same function but different performance are mounted on different server devices 100A to 100C, respectively, and the allocation of traffic to the VNF is controlled in units of server devices (physical servers). To do. Although not particularly limited, VNF 1A to VNF 1C mounted on server apparatuses 100A to 100C realize part or all of the functions of PGW (see, for example, FIG. 19B or FIG. 20B). There may be a firewall, a load balancer, or another server function.

The server apparatus 100A has a relatively high performance, the server apparatus 100C has a relatively low performance (performance is lower than that of the server apparatus 100A), and a server is provided between the server apparatus 100A and the server apparatus 100C. The configuration may include one or a plurality of server devices 100B having intermediate performance between the device 100A and the server device 100C. There is no particular limitation on the number of server devices.

In FIG. 3, the SGW 30 selects a server device (a virtual machine (VM) on which the VNF operates is arranged) on which a VNF corresponding to a carrier unit (for example, MVNO or MNO and MVNO) is arranged. The SGW 30 transfers the traffic to the server device (any one of 100A to 100C) where the assigned VNF is arranged. In the server device, the received traffic is transferred to a virtual machine (VM) in which the VNF operates via a hypervisor or the like on the server device.

For example, the SGW 30 has the function of the allocation device 111 described with reference to FIG. 2, and allocates the traffic of the MNO or the expensive MVNO carrier to the VNF 1A installed in the high-performance server device 100A. Note that, as in the example described later, the traffic of a high-priced MVNO carrier may be assigned to a dedicated device (not using NFV). You may make it allocate the traffic of the user of the carrier provided with the dedicated apparatus to a dedicated apparatus.

The SGW 30 allocates the traffic of the low-priced MVNO carrier to the VNF 1C installed in the general-purpose server (general-purpose server including a plurality of VNFs: VNF processing performance is reduced) or the low-performance server apparatus 100C. May be.

Alternatively, in FIG. 3, VNFs may be assigned to each user. The traffic of the user with the higher service class is assigned to the VNF 1A installed in the high-performance server apparatus 100A. In addition, you may make it allocate to a dedicated apparatus (NFV is not used) per user. The traffic of the user whose service class is lower is assigned to the VNF 1C on the low-performance server apparatus 100C.

Alternatively, for example, for a plurality of users contracting with the same carrier, the traffic of a user with a high-priced contract is allocated to the VNF 1A installed in the high-performance server apparatus 100A, and the traffic of a user with a low-priced contract is installed in the low-performance server apparatus 100C You may make it allocate to VNF1C.

In the first embodiment, the configuration is such that VNF allocation is controlled on a server device basis. And it is set as the structure which determines to which VNF traffic is allocated to a carrier unit or a user unit. Therefore, it is only necessary to select a server device in which VNFs determined in units of carriers or in units of users are arranged, so that allocation control and the like are simplified.

As a modification of the first embodiment, a server device group in which a plurality of server devices are grouped may be provided. In this case, the server device group may have a configuration in which a plurality of server devices are grouped into a plurality of groups according to functions or the like (for example, a plurality of server devices having the same function are grouped so as to belong to the same group). Also good).

In the case of this modified example, when selecting a server device to which traffic is allocated, primary allocation is performed to one server device group from among a plurality of server device groups according to the service level. One server device may be selected from one server device group, and traffic may be allocated to the one server device. Server device assignment within a group is random, continuation from the previous assignment (the server device assigned last time (last) is selected again, and as a result, assignment is continued), or a round robin method, etc. You may make it carry out. One server device group may include at least one server device. For example, when server devices in the same group provide the same function, the VNFs of one or more server devices in the same group are the same function (Network （Function). The performance of multiple server devices in the same group may be high or low (groups include server devices with the same function but different performance), or the same performance (all server devices in the group (Same function, same performance)

For example, a plurality of server device groups (groups A, B, and C) having different performance classes corresponding to each of a plurality of carriers (carriers A, B, and C), and a carrier (for example, carrier A, for example) that the subscriber contracts with. ), One server device group (for example, group A) is selected from a plurality of server device groups, and the subscriber's contract contents, etc. from the selected one server device group (for example, group A) A configuration may be adopted in which one server device corresponding to the performance corresponding to is selected.

<Another example of how to sort>
For example, an M2M (Machine to Machine) terminal
・ The amount of communication is small, and
・ Communication frequency is low,
It is assumed that

For this reason, it can be said that there is no particular problem with the traffic of the M2M terminal even through a route that does not have throughput. Therefore, in FIG. 3, when the terminal 1 is an M2M terminal, the traffic of the M2M terminal is distributed to the VNF1C of the low-performance server apparatus 100C. In this case, for example, when the connection of the M2M terminal is established (at the time of attachment), based on the terminal information (terminal identification information, terminal type, etc.) acquired by the eNB 20 or the like, the type of the M2M terminal and the address information of the packet transmission source Therefore, when the traffic is from an M2M terminal, the traffic may be allocated to the VNF 1C of the low-performance server apparatus 100C in units of packets.

Traffic such as mobile terminals of types other than M2M is allocated to the VNF 1A 103A on the high-performance server device 100A. This is because mobile terminals such as smartphones have more communication volume and higher communication frequency than M2M terminals (video download to terminal 1, Twitter や (trademark or registered trademark of Twitter, Inc.), Facebook ( This is because the communication volume and communication frequency of Facebook, Inc., etc.) are large, and the route through which the throughput is higher is taken. Traffic (downstream packets) addressed to the terminal 1 from the communication partner of the terminal 1 (node connected to the packet data network such as the Internet or IMS) is a router (switch) or the like (for example, a router on the MVNO network in FIG. 20B). To the VNF on the server device assigned corresponding to the carrier to which the terminal 1 subscribes (for example, the PGW function is virtually realized), and transmitted from the VNF to the terminal 1 via the SGW 30 and the eNB 20 Is done. In this case, the router (switch) or the like retains the correspondence between the terminal identification information shown in FIG. 2B and the assignment destination VNF, and includes a packet (downstream packet) addressed to the terminal 1 with the assignment destination VNF. You may make it transfer to a server apparatus. In FIG. 3, the VNFs 103A to 103C on the server devices 100A to 100C only handle the upstream traffic from the terminal 1, such as a firewall function (packet filter) that controls the passage permission of the upstream packet from the terminal 1, for example. Of course, it may be processed in one direction (in this case, a packet (downstream packet) addressed to the terminal 1 is not transferred to the VNF).

<Example of Embodiment 1>
FIG. 4 is a diagram illustrating an example of the first embodiment of FIG. In FIG. 4, the terminal 1 and the base station (eNB) 20 of FIG. 3 are omitted. In the example of FIG. 4, the server apparatuses 100A to 100C are selected by the switch (physical switch) 110. In this case, the SGW 30 and the switch 110 correspond to the assignment device 111 in FIG.

In FIG. 4, the SGW 30 selects a server device in which a traffic allocation destination VNF is arranged for each carrier or each user from among the server devices 100A to 100C. The SGW 30 transfers the traffic to the selected server device via the switch 110. The SGW 30 may transfer a frame in which identification information (for example, a MAC address) of the selected server device is set in a header or the like to the switch 110. The switch 110 manages the correspondence between the port number and the MAC address of the server device to which the port is connected in a table, and the frame is transmitted from the destination MAC address of the frame header to the port connected to the server device to which the frame is transferred. Forward.

<Embodiment 1-1>
FIG. 5A and FIG. 5B are diagrams for explaining Embodiment 1-1. Embodiment 1-1 describes Embodiment 1 more specifically. In Embodiment 1-1, VNF allocation is controlled in units of server devices (physical servers) as in Embodiment 1. As shown in FIG. 5A, in the embodiment 1-1, the SGW 30 controls the allocation of traffic to the VNF for each carrier based on the policy set by the control device (or operator) 50. In FIG. 5A, for example, the control device 50 and the SGW 30 realize the function of the assignment device 111 described with reference to FIGS.

The SGW 30 transfers traffic to the server device in which the assigned VNF is placed. In the server device, the received traffic is transferred to a virtual machine (VM) in which the VNF operates via a hypervisor or the like on the server device.

FIG. 5B is a diagram illustrating an example of a policy set by the control device (or operator) 50. As shown in FIG. 5B, VNF allocation is determined according to the service level set for each carrier. Note that the assignment method is the same as that in FIG. In each of the following embodiments, carrier A may be MNO or MVNO. Similarly, carrier B and the like are not limited to MVNO.

As described above, in the embodiment 1-1, the VNF is allocated according to the service level set for each carrier by setting the policy from the control device (or operator) 50 to the SGW 30. For this reason, it is possible to variably set the correspondence between the carrier, the service level, and the assigned VNF by variably setting (updating setting) the policy in the SGW 30 from the control device (or operator) 50, for example. For this reason, the resources of the server device can be used effectively and appropriately.

<Modification of Embodiment 1-1>
FIG. 6 is a diagram for explaining a modification of the embodiment 1-1 described above. In this modification, a control device is configured by the PCRF 51 and a PCEF (Policy and Enforcement Function) 52 and traffic is allocated by the PGW 40. In FIG. 6, the PCEF 52 applies a policy to communication (traffic) passing through the PGW 40 in cooperation with an OCS (Online Charging System) or PCRF 51 (not shown). In FIG. 6, for example, the PCRF 51 and the PGW 40 realize the function of the assignment device 111 described with reference to FIGS. 1 and 2.

The PCEF 52 controls the traffic of carriers passing through the PGW 40 based on, for example, a high speed policy, a low speed policy, and the like. The PCEF 52 may be mounted in the PGW 40.

In the configuration example of FIG. 6, the PGW 40 may allocate traffic for each carrier, for example. Furthermore, in the PGW 40, based on policy control information transmitted from the PCRF 51 via the Gxc interface, for example, VNFs are assigned to the same carrier in units of server devices according to service levels. Select the deployed server device. In this case, in the PGW 40, for example, by the control of the PCEF 52 or the like, VNF allocation may be performed in units of servers according to different service levels in units of users in the same carrier. For example, for a prepaid billing plan (contract) for a user, the PCRF 51 that has acquired a communicable amount from an OCS (not shown) that manages the communication amount and converts it into a prepaid balance determines a communication policy (communication speed), and the PCEF 52 A policy for user traffic is applied in the PGW 40. For example, when there is a remaining communication amount in a prepaid rate plan (for example, 2 GB (Gigabytes)), the PCEF 52 applies a policy of high-speed communication, and user traffic is assigned to VNF1A on the server device 100A. For example, switching to a low-speed communication policy such as a maximum of 128 kbps (kilo bits per second) may be performed, and user traffic may be assigned to VNF1C on the server device 100C. The PCRF 51 and the PCEF 52 in FIG. 6 can be said to be modifications of the control device 50 in FIG. 5. However, the policy setting and the traffic allocation control method based on the policy are not limited to the configuration in FIG. Of course.

<Embodiment 1-2>
FIG. 7A and FIG. 7B are diagrams for explaining the embodiment 1-2. The embodiment 1-2 describes the embodiment 1 more specifically. Like the embodiment 1, the VNF allocation is controlled in units of server devices (physical servers).

As shown in FIGS. 7A and 7B, in the embodiment 1-2, based on the policy set by the control device (or operator) 50, the user unit (terminal identification information (terminal ID of terminal 1) ), Or address unit), the allocation of traffic to the VNF is controlled. Note that the identification information of the terminal 1 is stored in the SIM (Subscriber Identity Module) card of the terminal 1 and is included in the Attachment request message transmitted from the terminal 1 to the MME. Identification information such as a mobile communication subscriber identifier) may be used.

As shown in FIG. 7A, in the embodiment 1-2, the SGW 30 controls the allocation of traffic to the VNF for each user based on the policy set by the control device (or operator) 50. The SGW 30 forwards the traffic to the assigned VNF to the server device in which the VNF is arranged. In the server device, the received traffic is transferred to a virtual machine (VM) in which the VNF operates via a hypervisor or the like on the server device.

FIG. 7B is a diagram for explaining an example of a policy set by the control device (or operator) 50. As shown in FIG. 7B, VNF allocation is controlled according to the service level set for each user (the ID or address of the terminal 1).

In the example of FIG.
-The traffic of the terminal of user 1 who subscribes to carrier A, which is an MNO or MVNO carrier, is a high-speed server device 100A on which VNF1A operates,
-The traffic of the terminal of the user 2 who subscribes to the carrier A is a medium-speed server device 100B in which VNF1B operates,
-The traffic of the terminal of the user 3 who subscribes to the MVNO carrier B is the low-speed server device 100C where the VNF1C operates,
Assigned to each.

As described above, in the embodiment 1-2, the VNF is allocated according to the service level set for each user by the policy setting from the control device (or operator) 50 to the SGW 30. By setting the policy from the control device (or operator) 50 variably, it is possible to variably set the correspondence between the user, the service level, and the VNF to which the user traffic is allocated. For this reason, the resources of the server device can be used effectively and appropriately.

Of course, the control device 50 of FIG. 7A may be configured by the PCRF 51 and the PCEF 52 as described with reference to FIG. In this case, the PCRF 51 may set the policy with reference to the charging rules of the user.

If the terminal 1 is an M2M terminal, the policy for setting the third service level in FIG. 7B may be used, and traffic from the M2M terminal may be allocated to the low-speed server apparatus 100C in which VNF1C is set. . Traffic (downstream packets) addressed to the terminal 1 from the communication partner (node connected to the packet data network such as the Internet or IMS) of the terminal 1 is a router (switch) or the like (for example, a router on the MVNO network in FIG. 20B). To the VNF on the server device assigned for each user (for example, the PGW function is virtually realized), and is transmitted from the VNF to the terminal 1 via the SGW 30 and the eNB 20. In this case, the router (switch) or the like retains the correspondence between the terminal address (user terminal ID) shown in FIG. 7B and the assigned VNF, and the packet addressed to the terminal 1 of the corresponding user (downlink packet) ) May be transferred to the server device provided with the allocation destination VNF. In FIG. 7A, the VNFs 103A to 103C on the server apparatuses 100A to 100C are connected upstream of the terminal 1 such as a firewall function (packet filter) that controls the passage permission of the upstream packet from the terminal 1, for example. Of course, only the traffic may be processed in one direction (in this case, a packet (downstream packet) addressed to the terminal 1 is not transferred to the VNF).

<Embodiment 1-3>
FIG. 8A and FIG. 8B are diagrams for explaining Embodiment 1-3. Embodiment 1-3 describes Embodiment 1 more specifically, and controls VNF allocation in units of server devices (physical servers) as in Embodiment 1.

As shown in FIG. 8A, in the embodiment 1-3, the subscriber information of the HSS 70 or the service contract information of the SPR (Subscriber Profile Repository) (contract contents change: for example, charge plan change, prepaid charge addition, etc.) Based on this, the allocation of traffic to VNF is controlled for each user. In the SGW 30, the traffic is transferred to the server device in which the assigned VNF is arranged. In the server device, the received traffic is transferred to a virtual machine (VM) in which the VNF is operated via a hypervisor or the like on the server device.

8A, the MME 60 authenticates the terminal 1 in cooperation with the HSS 70 during the terminal 1 attach process. In the authentication procedure (Authentication Procedure), the attach request message transmitted from the terminal 1 to the MME 60 includes the IMSI, the MME 60 transmits an authentication information request including the IMSI and the serving network ID to the HSS 70, and the HSS 70 authenticates. A vector is generated and transmitted to the MME 60. The MME 60 transmits an authentication request to the terminal 1, the terminal 1 authenticates the network, and transmits an authentication response of the terminal 1 to the MME 60. In the MME 60, the authentication response value (RES) from the terminal 1 and the authentication vector from the HSS 70 The user is authenticated by comparing the value (XRES) contained in. Following this authentication, the MME 60 acquires the subscriber profile information (service contract information, billing information, etc.) of the SPR (Subscriber Profile Repository) of the HSS 70 using the IMSI of the terminal 1, and assigns traffic to each user. The VNF may be determined for each server device. Alternatively, the SGW 30 uses the IMSI included in the session generation request (Create Session Request) message transmitted from the MME 60 to the SGW 30 following the above authentication, and the subscriber profile information (service contract information, billing information) of the HSS 70 Etc.) and the VNF to which traffic is allocated for each user may be determined for each server device. Alternatively, based on a service policy (service policy for a user) determined by PCRF (not shown), the SGW 30 may determine a VNF to which traffic is allocated for each user on a server device basis. Alternatively, the base station (eNB) 20 may determine the VNF to which traffic is assigned for each user on a server device basis. In this case, base station (eNB) 20 is good also as a structure provided with the allocation apparatus 111 demonstrated with reference to FIG.

FIG. 8B is a diagram showing an example of VNF allocation in user units (terminal identification information (terminal ID) of terminal 1, address unit). The assignment in FIG. 8B is the same as the policy in FIG. 7B (assignment of VNFs for each user), and thus description thereof is omitted.

In the embodiment 1-3, for example, based on the service contract information (billing information) of the user of the HSS 70, the user traffic is allocated to the VNF according to the change of the contract of the user (eg, change of charge plan or addition of prepaid charge) The setting may be changed.

In Embodiment 1-3, for example, the setting of allocation of user traffic to VNF is changed according to increase in communication capacity per month by adding a prepaid fee (for example, changing from low-performance VNF to high-performance VNF) You may make it do.

Alternatively, in Embodiment 1-3, allocation of user traffic to a VNF is performed so that a VNF further added with a function is allocated to the currently selected VNF due to a change (for example, upgrade) of a user service contract. The setting may be changed (scale up / scale out, etc.). Also, by changing the user service contract details (eg downgrade, etc.), the setting of allocation of user traffic to VNF is changed from the currently selected VNF to the VNF with reduced functions (scale down / scale in, etc.) You may make it do.

Furthermore, in Embodiment 1-3, the voice call and SMS (Short Message Service) function may be released by upgrading the change in the service contract contents of the user. The service chain (deployment of physical and virtual components supporting VNF and VNF) may be reconfigured so that the traffic of the corresponding user can be used for voice calls and SMS. Conversely, when the contract content change is downgraded, the VNF service chain may be reconfigured so that the functions set up to that point cannot be used.

According to the embodiment 1-3, it is possible to allocate user traffic to the VNF according to the contents of the service contract of the user, and it is possible to allocate the optimum VNF following the change of the contents of the service contract.

In Embodiment 1-3, as in Embodiment 1-2, when the terminal 1 is an M2M terminal, the low-speed server in which VNF1C is set for traffic from the M2M terminal according to the contract information of the M2M terminal You may make it allocate to the apparatus 100C.

<Embodiment 1-4>
FIG. 9A and FIG. 9B are diagrams for explaining Embodiments 1-4. The embodiment 1-4 describes the embodiment 1 more specifically. As in the embodiment 1, the VNF allocation is controlled in units of server devices (physical servers). As shown in FIG. 9A and FIG. 9B, in the embodiment 1-4, based on the policy from the control device 50, the SGW 30 sends traffic from the server devices 100A to 100C on which the VNF operates. Depending on the content and application, the server device on which the allocation VNF is installed is selected. The SGW 30 forwards the traffic to the assigned VNF to the server device in which the VNF is arranged. In the server device, the received traffic is transferred to a virtual machine (VM) in which the VNF operates via a hypervisor or the like on the server device.

In the policy shown in FIG.
・ Content: YouTube (registered trademark) (HD (High Definition television)) is high-speed, the first service level, the allocation destination is VNF1A,
-Content: YouTube (registered trademark) (SD (Standard Definition television)) is low speed, 3rd service level, assigned to VNF1C,
・ Other video services are at the second service level, and the allocation destination is VNF1B
It is said.

For example, header (HTTP header) information of an HTTP (Hypertext Transport Protocol) request may be analyzed to acquire content information and the like. For example, the URI (Uniform Resource Identifier) indicating the unique location of the content may be acquired from the URL (Uniform Resource Locator) of the content distribution source or the Content-Location of the entity header from the host field (HTTP 1.1) Good. Furthermore, content or application information is extracted using deep packet inspection (Deep Packet Inspection) that analyzes the payload part of a packet or stateful deep packet inspection (Stateful Deep Packet Inspection) that checks the packet header part. May be. The acquired content information is checked against the policy, and the server device on which the virtual machine (VM) that realizes the traffic assignment destination VNF is installed is selected.

According to Embodiment 1-4, it is possible to assign a VNF corresponding to the content to be transferred or an application that provides the content.

<Embodiment 2>
FIG. 10 is a diagram illustrating the configuration of the second embodiment. In the second embodiment, VNF allocation is controlled in units of virtual machines (VMs). For example, a plurality of VNFs (VNF1A to VNF1C) having the same function are mounted on different virtual machines (VMs) on the same server device. There is no particular limitation on the number of virtual machines. In the example of FIG. 10, virtual machines (VM) 102A to 102C mounted on a virtualization layer (control unit 101) such as a hypervisor of the server apparatus 100 are provided, and VNFs 1A to 102C are respectively provided on the virtual machines (VM) 102A to 102C. VNF1C operates. In FIG. 10, the SGW 30 has the function of the allocation device 111 described with reference to FIGS. 1 (A) and 2 (A).

The processing performance of the virtual machines 102A to 102C is relatively high for the virtual machine 102A, relatively low for the virtual machine 102C, and intermediate for the virtual machine 102B (not shown). The performance value of the virtual machine 102B is, for example, an intermediate value between the performances of the virtual machine 102A and the virtual machine 102C.

When allocating VNFs in units of MVNO carriers, for example, traffic of MVNO carriers with high-priced contracts is allocated to VNF 1A operating on high-performance VM 102A. On the other hand, the traffic of the low-value contract MVNO carrier is allocated to the VNF 1C operating on the low-performance VM 102C.

Or, when performing VNF allocation for each user, based on the user service contract information, the traffic of the user whose service class is higher is allocated to the VNF 1A operating on the high-performance VM 102A. On the other hand, the traffic of the user whose service class is lower is allocated to the VNF 1C operating on the low-performance VM 102C.

The SGW 30 transmits traffic to the server device 100. At this time, the SGW 30 sets information (identification information etc.) specifying the assigned VNF in the header of the traffic packet (for example, an unused bit field of the IP header) and transfers it to the server apparatus 100. Also good. Alternatively, the SGW 30 uses the MAC address of the virtual machine (VM) on which the assigned VNF is running (virtual MAC address automatically assigned by software by the hypervisor when the VM is powered on, etc.) in the traffic frame header. It may be set and transferred to the server apparatus 100.

The server device 100 transfers the traffic received from the SGW 30 to a virtual machine (VM) on which the VNF assigned by the SGW 30 operates among the plurality of VNFs 1A to VNF1C on the server device.

According to the second embodiment, VNF allocation is controlled in units of virtual machines (VMs). For this reason, it is possible to reduce the resources (for example, the number of server devices) of the server device as compared with the first embodiment in which the allocation is controlled on a server device basis, and the operation cost can be reduced.

<Example of Embodiment 2>
FIG. 11 is a diagram schematically illustrating an example of the configuration of the second embodiment. In the example of FIG. 11, the traffic received from the SGW 30 by the virtual switch (vSwitch) 106 in the server apparatus 100 is transferred to the virtual machine (VM).

The frame (packet) from the physical NIC 105 is input to the input port (U) of the virtual switch 106. In the virtual switch 106, for example, the header of the frame is analyzed, and the MAC address of the virtual machine (VM) set in the header of the frame in the SGW 30, or the identification information set in the header in the SGW 30 (an unused bit field of the header, etc.) The output port to which the destination virtual machine (VM) is connected is determined based on the VNF identification information set in the virtual machine (VM), etc., and the input frame is assigned to the virtual NIC of the virtual machine (VM) and the guest OS (Operating System) ) To the assigned VNF (application) running on the guest OS via (device driver). Data (packet data) processed by the VNF and output from the VNF is converted into, for example, a frame by the virtual NIC, and is transferred to the MVNO network transfer destination (the MVNO network of FIG. 20B) via the virtual switch 106 and the physical NIC 105. Router, etc.) and further transmitted to the communication partner of the terminal 1 via a packet data network such as the Internet or IMS. In FIG. 11, the virtual switch (vSwitch) 106, together with the SGW 30 in FIG. 11, constitutes the allocation device 111 in FIG. Although not particularly limited, when one VNF is realized by a plurality of virtual machines (VM), a virtual NIC (virtual network: external) among a plurality of VNFCs (VNF Component) constituting the VNF Traffic is transferred to a virtual machine (VM) that realizes VNFC connected to (link).

<Embodiment 2-1>
FIG. 12A and FIG. 12B are diagrams for explaining Embodiment 2-1. The embodiment 2-1 describes the embodiment 2 more specifically, and controls the allocation of VNFs in units of virtual machines (VMs) as in the case of the embodiment 2.

As shown in FIG. 12A, in the embodiment 2-1, based on the policy set by the control device (or operator) 50, the SGW 30 assigns traffic to the VNF for each carrier, on the virtual machine ( Control by VM). The SGW 30 uses virtual machine (VM) identification information (for example, virtual MAC address) in the header information of the frame or packet so that traffic is transferred to the virtual machine (VM) on which the assigned VNF operates. Is transferred to the server apparatus 100. In the server apparatus 100, as described with reference to FIG. 11, the traffic is transferred to the destination VNF.

FIG. 12B is a diagram for explaining an example of a policy set by the control device (or operator) 50. As shown in FIG. 12B, VNF allocation is controlled according to the service level set for each carrier. Note that the assignment method is the same as that in FIG.

In the embodiment 2-1, according to the policy setting from the control device (or operator) 50 to the SGW 30, the VNF is allocated according to the service level set for each carrier. By variably setting the policy from the control device (or operator) 50, the correspondence between the MVNO carrier, the service level, and the VNF can be variably set. For this reason, the resources of the server can be used effectively and appropriately.

In the embodiment 2-1, as in the modification of the embodiment 1-1 (see FIG. 6), the SGW 30 assigns traffic to virtual machines (groups) for each carrier. Further, in the PGW 40, Based on policy control information transmitted from the PCRF 51 via the Gxc interface, VNFs may be assigned to the same carrier in units of virtual machines according to the service level.

<Embodiment 2-2>
FIG. 13A and FIG. 13B are diagrams for explaining the embodiment 2-2. The embodiment 2-2 describes the embodiment 2 more specifically. Similar to the embodiment 2, the allocation of the VNF is controlled in units of virtual machines (VMs).

As shown in FIGS. 13A and 13B, in the embodiment 2-2, based on the policy set by the control device (or operator) 50, the SGW 30 is configured so that the user unit (terminal identification information of the terminal 1). (Assignment of terminal ID) or address) to control allocation of traffic to VNF. As the identification information of the terminal 1, IMSI (International Mobile Subscriber Identity) stored in a SIM (Subscriber Identity Module) card of the terminal may be used. The SGW 30 sets virtual machine identification information (for example, virtual MAC address) in the header information of the frame or packet so that traffic is transferred to the virtual machine (VM) on which the assigned VNF operates. , Transfer to the server device 100. In the server apparatus 100, as described with reference to FIG. 11, the traffic is transferred to the destination VNF.

As shown in FIG. 13A, in the embodiment 2-2, the allocation of traffic to the VNF is controlled for each user based on the policy set by the control device (or operator) 50. FIG. 13B is a diagram for explaining an example of a policy set by the control device (or operator) 50. As shown in FIG. 13B, VNF allocation is controlled according to the service level set for each user (the ID or address of the terminal 1). In the example of FIG.
-The traffic of the terminal of user 1 who subscribes to carrier A (MNO or MVNO) is a high-speed VM 102A on which VNF1A operates,
-The traffic of the terminal of the user 2 who subscribes to the carrier A (MNO or MVNO) is a medium speed VM 102B on which VNF1B is operating,
-The traffic of the terminal of the user 3 who subscribes to the carrier B (MVNO carrier) is a low-speed VM 102C on which VNF1C operates,
Assigned to each.

13A, the control device (or operator) 50 and the SGW 30 realize the function of the assignment device 111 described with reference to FIGS. 1A and 2A.

In the embodiment 2-2, a VNF is assigned according to a service level set for each user by setting a policy from the control device (or operator) 50 to the SGW 30. According to the embodiment 2-2, the correspondence between the user, the service level, and the VNF can be variably set by setting the policy from the control device (or operator) 50 variably. For this reason, the resources of the server, particularly the VM, can be used effectively and appropriately.

In the embodiment 2-2, as in the embodiment 1-2, when the terminal 1 is an M2M terminal, the policy is set to the third service level in FIG. 13B, and traffic from the M2M terminal is slow. You may make it allocate to VNF1C of.

<Embodiment 2-3>
FIG. 14A and FIG. 14B are diagrams for explaining Embodiment 2-3. The embodiment 2-3 describes the embodiment 2 more specifically, and controls the allocation of VNFs on a virtual machine (VM) basis as in the second embodiment.

As shown in FIG. 14 (A), in the embodiment 2-3, based on the subscriber information of the HSS 70 (for example, change of service contract contents (eg change of charge plan, addition of prepaid charge, etc.)) Control assignment to VNF.

14A, the MME 60 performs authentication and the like in cooperation with the HSS 70 during the attach process of the terminal 1. The MME 60 may refer to subscriber profile information (contract information, billing information, etc.) of the HSS 70 and determine a VNF to which traffic is allocated based on the subscriber profile information. The SGW 30 receives a notification (assignment destination VNF) from the MME 60 or the base station 20, and in the header information of the frame or packet so that traffic is transferred to the virtual machine (VM) on which the assigned VNF operates. Virtual machine identification information (for example, a virtual MAC address) is set and transferred to the server apparatus 100. In the server apparatus 100, as described with reference to FIG. 11, the traffic is transferred to the destination VNF.

In the present embodiment, the base station 20 may determine the VNF to which traffic is allocated for each user on a virtual machine (VM) basis.

FIG. 14B is a diagram showing an example of VNF allocation in user units (terminal identification information (terminal ID) of terminal 1, address unit). The assignment in FIG. 14A is the same as the policy in FIG. 8B (assignment of VNFs for each user), and thus the description is omitted.

In Embodiment 2-3, the setting of allocation of user traffic to the VNF may be changed in accordance with a change in the contract contents of the user (eg, change of charge plan, addition of prepaid charge).

In the embodiment 2-3, for example, the setting of the allocation of user traffic to the VNF is changed according to the increase in communication capacity per month by adding a prepaid charge (for example, changing from a low-performance VNF to a high-performance VNF) You may make it do.

Alternatively, in the embodiment 2-3, the setting for assigning user traffic to the VNF is changed so as to assign a VNF with additional functions to the currently selected VNF by changing the contract contents (for example, upgrading). May be. Further, by changing the contract contents (for example, downgrade or the like), the setting of allocation of user traffic to the VNF may be changed from the currently selected VNF to the VNF with reduced functions.

Furthermore, in Embodiment 2-3, the voice call and SMS (Short Message Service) functions may be released by upgrading the contract content change or the like. The service chain (deployment of physical and virtual components supporting VNF and VNF) may be reconfigured so that the traffic of the corresponding user can be used for voice calls and SMS. Conversely, when the contract content change is downgraded, the VNF service chain may be reconfigured so that the functions set up to that point cannot be used.

According to Embodiment 2-3, it is possible to allocate user traffic to a VNF according to the contents of a user's contract, and to make an optimal VNF allocation following changes in the contract contents.

In Embodiment 2-3, similarly to Embodiment 2-2, when the terminal 1 is an M2M terminal, traffic from the M2M terminal may be allocated to the low-speed VNF 1C according to the contract information of the M2M terminal. Good.

<Embodiment 2-4>
FIG. 15A and FIG. 15B are diagrams for explaining the embodiment 2-4. The embodiment 2-4 describes the embodiment 2 more specifically. Similar to the embodiment 2, the VNF allocation is controlled in units of VMs.

As shown in FIGS. 15A and 15B, in the embodiment 2-4, based on the policy from the control device 50, the SGW 30 selects from a plurality of VNFs 1A to VNF1C arranged in the server device 100. In accordance with the traffic content, application, etc., the VNF to which the traffic is assigned is selected. In the policy shown in FIG.
・ Content: YouTube (registered trademark) (HD (High Definition television)) is high-speed, the first service level, the allocation destination is VNF1A,
-Content: YouTube (registered trademark) (SD (Standard Definition television)) is low speed, 3rd service level, assigned to VNF1C,
・ Other video services are at the second service level, and the allocation destination is VNF1B
It is said.

The SGW 30 receives a notification (assignment destination VNF) from the MME 60 or the base station 20, and in the header information of the frame or packet so that traffic is transferred to the virtual machine (VM) on which the assigned VNF operates. Virtual machine identification information (for example, a virtual MAC address) is set and transferred to the server apparatus 100. In the server apparatus 100, as described with reference to FIG. 11, the traffic is transferred to the destination VNF.

In Embodiment 2-4, as in Embodiment 1-4, for example, header (HTTP header) information of an HTTP (Hypertext Transport Protocol) request may be analyzed to acquire content information and the like. For example, the URI (Uniform Resource Identifier) indicating the unique location of the content may be acquired from the URL (Uniform Resource Locator) of the content distribution source or the Content-Location of the entity header from the host field (HTTP 1.1) Good. Furthermore, content or application information is extracted using deep packet inspection (Deep Packet Inspection) that analyzes the payload part of a packet or stateful deep packet inspection (Stateful Deep Packet Inspection) that checks the packet header part. May be. The acquired content information may be checked against the policy, and a virtual machine (VM) that realizes the VNF to which traffic is allocated may be selected.

According to Embodiment 2-4, it is possible to assign a VNF corresponding to the content to be transferred or the application that provides the content.

<Embodiment 3>
FIG. 16 is a diagram illustrating the configuration of the third embodiment. Also in the third embodiment, allocation of VNFs is controlled on a virtual machine (VM) basis.

In the example shown in FIG. 16, the services provided by the VNFs (VNF1A, VNF1B) on the first server device 100D and the VNFs (VNF2A, VNF2B) on the second server device 100E are different from each other. That is, VNF1A and VNF1B have the same function (first function), but have different performance classes. VNF2A and VNF2B have the same function (second function: different from the first function), but have different performance classes.

In the first server device 100D in which VNF1A and VNF1B providing the first service are installed, the virtual machine VM1A is a high performance VM and the virtual machine VM1B is a low performance VM. The VNF 1A on the virtual machine VM1A has high performance, and the VNF 1B on the virtual machine VM1B has low performance. In the second server apparatus 100E in which VNF2A and VNF2B providing the second service are installed, the virtual machine VM2A is a high performance VM and the virtual machine VM2B is a low performance VM. VNF2A on the virtual machine VM2A has high performance, and VNF2B on the virtual machine VM2B has low performance.

As described above, in the third embodiment, a plurality of VNFs classified by quality for each service have a chaining configuration. The granularity of classification such as quality for each VNF may be different between the server apparatuses 100D and 100E. For example, the first server device 100D divides the service level into 8 levels, and the second server device 100E divides the service level into 4 levels, depending on QoS (Quality of Service), communication speed, contract, etc. Service level granularity may be different.

In Embodiment 3, the classification hierarchy (rank) may be different depending on the VNF. For example, a high-performance and low-performance VNF may be arranged in the server device 100D, and a high-performance, medium-performance, and low-performance VNF may be arranged in the server device 100E.

In Embodiment 3, some VNFs may be shared without dividing the server device for each service provided by the VNF.

In the third embodiment, a configuration may be adopted in which VNFs classified for each service and VNFs for selecting whether to add the function itself (for example, SMS option) are mixed.

Further, in the third embodiment, as described in the first to fourth embodiments, the second embodiment, and the like, the VNF to which traffic is allocated is selected based on the subscriber information of the user (selection of the server device and in the server device). (You may select VNF at Alternatively, as in Embodiments 1-2, 1-3, 2-2, 2-3, etc., a VNF assigned by the SGW 30 is selected based on the set policy (selection of the server device and within the server device). VNF selection).

According to the third embodiment, it is possible to finely allocate resources according to the combination of the provided service (function) and quality, and the granularity of classification.

<Embodiment 4>
FIG. 17A illustrates the configuration of the fourth embodiment. Referring to FIG. 17A, in the fourth embodiment, the carrier grade dedicated device 120 and the server device of the first embodiment described with reference to FIG. 3 (the server among the server devices 100A to 100C of FIG. 3). Device 100B). The VNF 1B on the server device 100B is a function (network function) of the dedicated device 120 virtualized on the server device 100B, and the processing and functions performed by the dedicated device 120 are realized in software on the virtual machine. . The dedicated device 120 may be owned by the MNO, or may be owned by a specific MVNO carrier. In FIG. 17A, only one server device is shown for simplicity, but it is needless to say that there may be a plurality of server devices.

As shown in FIG. 17 (B), for example, when carrier A is a carrier (MNO or MVNO) that owns infrastructure such as dedicated device 120, or carrier A is an MVNO carrier with a large contract, The dedicated device 120 is allocated to the traffic of the carrier A. The traffic of MVNO carriers B and C with a low-price contract is assigned to VNF 1B on server device 100B or VNF 1C on server device 100C (not shown).

When assigning user traffic to the dedicated device 120, the SGW 30 may set the MAC address of the dedicated device 120 in the frame header of the traffic and transfer it. When the traffic is allocated to the VNF 1B, the SGW 30 selects the server device 100 in which the VNF 1B is arranged (selection for each server). The SGW 30 sets the identification information (or VNF identification information) of the virtual machine (VM) that realizes the VNF 1B in the frame header (packet header) of the traffic, and forwards the traffic to the server apparatus 100B. Also good. In the server apparatus 100B, as described with reference to FIG. 11, the traffic is transferred to the destination VNF.

As a modification of the fourth embodiment, the traffic allocation destination may be controlled for each user. For example, in the example shown in FIG. 17C, the user 1 of the carrier A corresponds to the first service level, the traffic is assigned to the dedicated device 120, and the user 2 of the carrier A is the second service level. And the traffic is assigned to VNF1B.

Alternatively, as a further modification of the fourth embodiment, for example, for the traffic of users of the same carrier, the traffic is allocated according to the service level corresponding to the content carried by the traffic (traffic addressed to the terminal 1). 120, VNF1B, or VNF1C may be set. As shown in FIG. 17D, traffic carrying content of the first service level may be assigned to the dedicated device 120.

The dedicated device 120 is an arbitrary network facility or a server device. For example, the PGW or server group in FIG. 20B or the router in FIG. 19B may be used.

According to the fourth embodiment, an existing dedicated device 120 that does not comply with NFV (for example, an existing PGW) can be used in combination with NFV, and as a transitional measure (system configuration) until the network equipment is completely converted to NFV It is extremely effective.

<Embodiment 5>
FIG. 18A illustrates the configuration of the fifth embodiment. Referring to FIG. 18A, the fifth embodiment includes a dedicated device 120 and a server device 100. The server apparatus 100 corresponds to the server apparatus 100 of the second embodiment described with reference to FIG. 10 (however, VNF has VNF1B and VNF1C). In FIG. 18A, VNF1B and VNF1C on the server device 100 are virtualized functions of the dedicated device 120, and the processing and functions performed by the dedicated device 120 are realized in software on the virtual machine. ing. The dedicated device 120 may be owned by the MNO, or may be owned by a specific MVNO carrier. FIG. 18A shows only one server device for simplicity, but it goes without saying that there may be a plurality of server devices.

As shown in FIG. 18 (B), for example, when carrier A is a carrier (MNO or MVNO) that owns infrastructure such as dedicated device 120, or carrier A is an MVNO carrier with a large contract, The dedicated device 120 is allocated to the traffic of the carrier A. The traffic of MVNO carriers B and C with low-price contracts is assigned to VNF 1B and VNF 1C on server device 100B.

When assigning traffic to the dedicated device 120, the SGW 30 may set the MAC address of the dedicated device 120 in the frame header of the traffic and transfer the traffic, for example. When the traffic is allocated to the VNF 1B, the SGW 30 selects the server device 100 in which the VNF 1B is arranged (selection for each server). The SGW 30 sets the identification information (or VNF identification information) of the virtual machine (VM) that realizes the VNF 1B in the frame header (packet header) of the traffic, and forwards the traffic to the server apparatus 100B. Also good. In the server apparatus 100B, as described with reference to FIG. 11, the traffic is transferred to the destination VNF.

As a modification of the fifth embodiment, as shown in FIG. 18C, the traffic of the user 1 of the carrier A at the first service level may be assigned to the dedicated device 120. That is, a traffic assignment destination is set for each user.

Alternatively, as a further modification of the fifth embodiment, as illustrated in FIG. 18D, traffic carrying content of the first service level may be assigned to the dedicated device 120. That is, the traffic allocation destination is set according to the service level corresponding to the content carried by the traffic (traffic destined for terminal 1).

The dedicated device 120 is an arbitrary network facility or a server device. For example, the PGW or server group in FIG. 20B or the router in FIG. 19B may be used.

According to the fifth embodiment, the existing dedicated device 120 that does not comply with NFV can be used in combination with NFV, and is extremely effective as a transitional measure (system configuration) until the network equipment is completely converted to NFV.

It should be noted that the disclosure of Non-Patent Document 1 is incorporated herein by reference. Within the scope of the entire disclosure (including claims) of the present invention, the embodiments and examples can be changed and adjusted based on the basic technical concept. Various combinations or selections of various disclosed elements (including each element of each claim, each element of each embodiment, each element of each drawing, etc.) are possible within the scope of the claims of the present invention. . That is, the present invention of course includes various variations and modifications that could be made by those skilled in the art according to the entire disclosure including the claims and the technical idea.

Although the above-described embodiment is not particularly limited, for example, it is added as follows.

(Appendix 1)
First means (control unit: first unit) for allocating the traffic to a predetermined virtual network function according to a service level set corresponding to information related to traffic, and according to the allocation result And a second means (processing unit: second unit) for transferring the traffic to the predetermined virtual network function.

(Appendix 2)
The first means (control unit: first unit) includes the traffic in a first virtual network among virtual machines that realize the predetermined virtual network function according to the attribute of the traffic. The communication apparatus according to appendix 1, wherein the communication apparatus is assigned to a first virtual machine or a second virtual machine included in a second virtual network.

(Appendix 3)
The communication apparatus according to appendix 1 or 2, wherein the information related to the traffic includes a communication carrier to which a user of the traffic subscribes is extracted corresponding to the traffic.

(Appendix 4)
The communication apparatus according to appendix 1 or 2, wherein the information related to the traffic includes information unique to the user extracted corresponding to the traffic.

(Appendix 5)
The communication apparatus according to appendix 1 or 2, wherein the information related to the traffic includes content carried by the traffic extracted corresponding to the traffic.

(Appendix 6)
The communication apparatus according to appendix 1 or 2, wherein the information related to the traffic includes an application of the content transmission source extracted corresponding to the traffic.

(Appendix 7)
The first means (first unit) selects a server device having the virtual network function when allocating traffic to the virtual network function according to the service level. 6. The communication device according to any one of 6.

(Appendix 8)
The first means (first unit) allocates traffic to the virtual network function according to the service level in a server device, and the virtual network function operates on a virtual machine unit on which the virtual network function operates. The communication device according to any one of appendices 1 to 6, wherein the communication device is performed.

(Appendix 9)
The first means (first unit) selects the server device having the processing performance corresponding to the service level and having the virtual network function from the plurality of server devices having different processing performance. The communication apparatus according to appendix 7, wherein the traffic is allocated to a virtual machine that realizes the virtual network function in the selected server apparatus.

(Appendix 10)
The server device includes a plurality of virtual network functions having different processing performance on the plurality of virtual machines,
The first means (first unit) selects one of the virtual network functions according to the service level, and sends the traffic to a virtual machine that realizes the selected virtual network function. The communication device according to appendix 7, wherein the communication device is assigned.

(Appendix 11)
A plurality of the server devices having the virtual network function having different functions,
A plurality of the virtual network functions having the same function and different processing performances are provided on the same server device,
The first means (first unit) selects the virtual network function according to the service level from the plurality of virtual network functions on the selected server device, and selects the selected virtual network The communication device according to appendix 7, wherein the traffic is assigned to a function.

(Appendix 12)
One or more server devices that implement one or more virtual machines that implement one or more virtual network functions;
The communication device according to any one of appendices 1 to 11, and
A communication system comprising:

(Appendix 13)
First means (first unit) for allocating the traffic to a predetermined virtual network function according to a service level set corresponding to information related to the traffic;
A second means (second unit) for transferring the traffic to the predetermined virtual network function according to the allocation result;
An allocating device characterized by comprising:

(Appendix 14)
The first means (first unit) includes a first virtual network included in a first virtual network among virtual machines that realize the predetermined virtual network function according to the attribute of the traffic. 14. The assigning device according to appendix 13, wherein the assigning device is assigned to a virtual machine or a second virtual machine included in the second virtual network.

(Appendix 15)
15. The allocation apparatus according to appendix 13 or 14, wherein the information related to the traffic includes a telecommunications carrier to which a user of the traffic subscribes is extracted corresponding to the traffic.

(Appendix 16)
15. The allocation apparatus according to appendix 13 or 14, wherein the information related to the traffic includes information specific to the user extracted corresponding to the traffic.

(Appendix 17)
15. The allocation device according to appendix 13 or 14, wherein the information related to the traffic includes content carried by the traffic extracted corresponding to the traffic.

(Appendix 18)
15. The allocation apparatus according to appendix 13 or 14, wherein the information related to the traffic includes the application of the content transmission source extracted corresponding to the traffic.

(Appendix 19)
The first means (first unit) selects a server device having the virtual network function when allocating the traffic to the virtual network function according to the service level. The assigning device according to any one of 13 to 18.

(Appendix 20)
The first means (first unit) is implemented on a server device for allocating traffic to the virtual network function according to the service level, and the virtual network unit on which the virtual network function operates The assigning device according to any one of appendices 13 to 18, characterized in that:

(Appendix 21)
The first means (first unit) selects the server device having the processing performance corresponding to the service level and having the virtual network function from the plurality of server devices having different processing performance. The allocation device according to appendix 19, wherein the traffic is allocated to a virtual machine that realizes the virtual network function in the selected server device.

(Appendix 22)
The server device includes a plurality of virtual network functions having different processing performance on the plurality of virtual machines,
The first means (first unit) selects one of a plurality of the virtual network functions and allocates the traffic according to the service level, and the traffic is allocated to the first means (first unit). Allocation device.

(Appendix 23)
A plurality of the server devices having the virtual network function having different functions,
A plurality of the virtual network functions having the same function and different processing performances are provided on the same server device,
The first means (first unit) selects and selects the virtual network function having processing performance according to the service level from the plurality of virtual network functions on the selected server device. The assigning device according to appendix 19, wherein the traffic is assigned to the virtual network function.

(Appendix 24)
Depending on the service level set in response to information related to traffic, the traffic is assigned to a predetermined virtual network function,
In accordance with the allocation result, the traffic is transferred to the predetermined virtual network function.

(Appendix 25)
According to the attribute of the traffic, the traffic is included in the first virtual machine included in the first virtual network or the second virtual network among the virtual machines that realize the predetermined virtual network function. The communication method according to appendix 24, wherein the communication method is assigned to a second virtual machine.

(Appendix 26)
26. The communication method according to appendix 24 or 25, wherein the information related to the traffic includes a telecommunications carrier to which a user of the traffic subscribed is extracted corresponding to the traffic.

(Appendix 27)
26. The communication method according to appendix 24 or 25, wherein the information related to the traffic includes unique information of the user extracted corresponding to the traffic.

(Appendix 28)
26. The communication method according to appendix 24 or 25, wherein the information related to the traffic includes content carried by the traffic extracted corresponding to the traffic.

(Appendix 29)
26. The communication method according to appendix 24 or 25, wherein the information related to the traffic includes an application of the content transmission source extracted corresponding to the traffic.

(Appendix 30)
30. The communication method according to any one of appendices 24 to 29, wherein when allocating the traffic to the virtual network function according to the service level, a server device having the virtual network function is selected.

(Appendix 31)
Any one of appendices 24 to 29, wherein the allocation of traffic to the virtual network function according to the service level is performed in units of virtual machines mounted on a server device and operating on the virtual network function. The communication method as described in one.

(Appendix 32)
The traffic to a virtual machine that realizes the virtual network function by selecting the server apparatus having the processing performance corresponding to the service level and having the virtual network function from among the plurality of server apparatuses having different processing performance 32. The communication method according to supplementary note 30, wherein the communication method is assigned.

(Appendix 33)
The server device includes a plurality of virtual network functions having different processing performance on the plurality of virtual machines,
31. The communication method according to appendix 30, wherein one of a plurality of virtual network functions is selected and the traffic is allocated according to the service level.

(Appendix 34)
For a plurality of the server devices having the virtual network functions having different functions, on the same server device, the plurality of virtual network functions having the same functions and different processing performances are provided.
The traffic is allocated to the virtual network function selected according to the service level from among the plurality of virtual network functions on the server apparatus selected from the plurality of server apparatuses. The communication method according to appendix 30.

(Appendix 35)
A process of allocating the traffic to a predetermined virtual network function according to a service level set corresponding to information related to the traffic;
A process of forwarding the traffic to the predetermined virtual network function according to the allocation result;
A program that causes a computer to execute.

(Appendix 36)
According to the attribute of the traffic, the traffic is included in the first virtual machine included in the first virtual network or the second virtual network among the virtual machines that realize the predetermined virtual network function. The program according to appendix 35, which causes the computer to execute processing to be assigned to the second virtual machine.

(Appendix 37)
A base station comprising the assigning device according to any one of appendices 13 to 23.

(Appendix 38)
A core network node comprising the assignment device according to any one of appendices 13 to 23.

1 terminal (mobile terminal)
2 MNO network (MNO NW)
3 MVNO network (MVNO NW)
4 Internet 20 eNB (base station)
30 SGW
40 PGW
50 Controller 51 PCRF
52 PCEF
60 MME
70 HSS
100, 100A to 100E Server device (physical server)
101, 101A to 101C Control unit (hypervisor)
102, 102A to 102C Virtual machine (VM)
103, 103A-103C VNF
104 Hardware resources 105 Physical NIC
106 Virtual switch (vSwitch)
107A, 107B Virtual NIC
108A, 108B Guest OS
110 switch (physical switch)
111 Allocation device 112 Control unit 113 Processing unit 114 Storage unit 120 Dedicated device

Claims (36)

A first means for allocating the traffic to a predetermined virtual network function according to a service level set corresponding to information related to the traffic;
A second means for forwarding the traffic to the predetermined virtual network function according to the assignment result;
A communication apparatus comprising: The communication device, according to the attribute of the traffic, the first virtual machine included in the first virtual network among the virtual machines that realize the predetermined virtual network function, or the second The communication apparatus according to claim 1, wherein the communication apparatus is assigned to a second virtual machine included in the virtual network. 3. The communication apparatus according to claim 1, wherein the information related to the traffic includes a communication carrier to which a user of the traffic subscribed is extracted corresponding to the traffic. 3. The communication apparatus according to claim 1, wherein the information related to the traffic includes information unique to the user extracted corresponding to the traffic. 3. The communication apparatus according to claim 1, wherein the information related to the traffic includes content carried by the traffic extracted corresponding to the traffic. 3. The communication apparatus according to claim 1, wherein the information related to the traffic includes an application of the content transmission source extracted corresponding to the traffic. 7. The server according to claim 1, wherein the first means selects a server device having the virtual network function when allocating traffic to the virtual network function according to the service level. The communication device according to item. The first means assigns traffic to the virtual network function in accordance with the service level for each virtual machine that is mounted on a server device and on which the virtual network function operates. The communication device according to any one of claims 1 to 6. The first means selects the server device having a processing performance corresponding to the service level and having the virtual network function from the plurality of server devices having different processing performances, and the selected server device. The communication device according to claim 7, wherein the traffic is allocated to a virtual machine that realizes the virtual network function. The server device includes a plurality of virtual network functions having different processing performance on the plurality of virtual machines,
The first means selects one of a plurality of the virtual network functions according to the service level, and assigns the traffic to a virtual machine that realizes the selected virtual network function. The communication apparatus according to claim 7. A plurality of the server devices having the virtual network function having different functions,
A plurality of the virtual network functions having the same function and different processing performances are provided on the same server device,
The first means selects the virtual network function according to the service level from the plurality of virtual network functions on the selected server device, and assigns the traffic to the selected virtual network function. The communication apparatus according to claim 7, wherein: One or more server devices that implement one or more virtual machines that implement one or more virtual network functions;
The communication device according to any one of claims 1 to 11,
A communication system comprising: A first means for allocating the traffic to a predetermined virtual network function according to a service level set corresponding to information related to the traffic;
A second means for forwarding the traffic to the predetermined virtual network function according to the assignment result;
An allocating device characterized by comprising: The allocating device assigns the traffic to a first virtual machine included in a first virtual network or a second virtual machine among virtual machines that realize the predetermined virtual network function according to the attribute of the traffic. 14. The allocation apparatus according to claim 13, wherein the allocation apparatus is allocated to a second virtual machine included in the virtual network. The allocation apparatus according to claim 13 or 14, wherein the information related to the traffic includes a communication carrier to which a user of the traffic subscribes extracted in correspondence with the traffic. 15. The allocation apparatus according to claim 13 or 14, wherein the information related to the traffic includes information unique to the user extracted corresponding to the traffic. 15. The allocation device according to claim 13, wherein the information related to the traffic includes content carried by the traffic extracted corresponding to the traffic. 15. The allocation apparatus according to claim 13, wherein the information related to the traffic includes the application of the content transmission source extracted in correspondence with the traffic. 19. The server according to claim 13, wherein the first means selects a server device having the virtual network function when allocating the traffic to the virtual network function according to the service level. 2. The assigning device according to claim 1. The first means assigns traffic to the virtual network function in accordance with the service level for each virtual machine mounted on a server device and operating on the virtual network function. The assigning device according to any one of claims 13 to 18. The first means selects the server device having a processing performance corresponding to the service level and having the virtual network function from the plurality of server devices having different processing performances, and the selected server device. The allocation apparatus according to claim 19, wherein the traffic is allocated to a virtual machine that realizes the virtual network function. The server device includes a plurality of virtual network functions having different processing performance on the plurality of virtual machines,
The assigning device according to claim 19, wherein the first means assigns the traffic by selecting one of the plurality of virtual network functions according to the service level. A plurality of the server devices having the virtual network function having different functions,
A plurality of the virtual network functions having the same function and different processing performances are provided on the same server device,
The first means selects the virtual network function according to the service level from among the plurality of virtual network functions on the selected server device, and assigns the traffic to the selected virtual network function. The assigning device according to claim 19. Depending on the service level set in response to information related to traffic, the traffic is assigned to a predetermined virtual network function,
In accordance with the allocation result, the traffic is transferred to the predetermined virtual network function. According to the attribute of the traffic, the traffic is included in the first virtual machine included in the first virtual network or the second virtual network among the virtual machines that realize the predetermined virtual network function. 25. The communication method according to claim 24, wherein the communication method is assigned to a second virtual machine. 26. The communication method according to claim 24 or 25, wherein the information related to the traffic includes a telecommunications carrier to which a user of the traffic subscribed is extracted corresponding to the traffic. 26. The communication method according to claim 24 or 25, wherein the information related to the traffic includes information unique to the user extracted corresponding to the traffic. 26. The communication method according to claim 24 or 25, wherein the information related to the traffic includes content carried by the traffic extracted corresponding to the traffic. 26. The communication method according to claim 24 or 25, wherein the information related to the traffic includes an application of the content transmission source extracted corresponding to the traffic. 30. The communication according to claim 24, wherein a server device having the virtual network function is selected when allocating the traffic to the virtual network function according to the service level. Method. 30. The allocation of traffic to the virtual network function according to the service level is implemented in a server device, and the virtual network function is performed in units of virtual machines on which the virtual network function operates. The communication method according to any one of the above. The server device having a processing performance corresponding to the service level and having the virtual network function is selected from the plurality of server devices having different processing performances, and the virtual network function of the selected server device is selected. The communication method according to claim 30, wherein the traffic is allocated to a virtual machine to be realized. The server device includes a plurality of virtual network functions having different processing performance on the plurality of virtual machines,
The communication method according to claim 30, wherein one of a plurality of the virtual network functions is selected and the traffic is allocated according to the service level. For a plurality of the server devices having the virtual network functions having different functions, on the same server device, the plurality of virtual network functions having the same functions and different processing performances are provided.
The virtual network function is selected according to the service level from the plurality of virtual network functions on the server apparatus selected from the plurality of server apparatuses, and the traffic is sent to the selected virtual network function. The communication method according to claim 30, wherein the communication method is assigned. A process of allocating the traffic to a predetermined virtual network function according to a service level set corresponding to information related to the traffic;
A process of forwarding the traffic to the predetermined virtual network function according to the allocation result;
A program that causes a computer to execute. According to the attribute of the traffic, the traffic is included in the first virtual machine included in the first virtual network or the second virtual network among the virtual machines that realize the predetermined virtual network function. 36. The program according to claim 35, which causes the computer to execute a process assigned to a second virtual machine.

Images