JP6460743B2 - Setting information generation system and setting information generation method - Google Patents

Setting information generation system and setting information generation method Download PDF

Info

Publication number
JP6460743B2
JP6460743B2 JP2014236534A JP2014236534A JP6460743B2 JP 6460743 B2 JP6460743 B2 JP 6460743B2 JP 2014236534 A JP2014236534 A JP 2014236534A JP 2014236534 A JP2014236534 A JP 2014236534A JP 6460743 B2 JP6460743 B2 JP 6460743B2
Authority
JP
Japan
Prior art keywords
setting information
virtual node
additional
network
management
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
JP2014236534A
Other languages
Japanese (ja)
Other versions
JP2016100750A (en
Inventor
正昭 小杉
正昭 小杉
アシック カーン
アシック カーン
基 田村
基 田村
Original Assignee
株式会社Nttドコモ
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社Nttドコモ filed Critical 株式会社Nttドコモ
Priority to JP2014236534A priority Critical patent/JP6460743B2/en
Publication of JP2016100750A publication Critical patent/JP2016100750A/en
Application granted granted Critical
Publication of JP6460743B2 publication Critical patent/JP6460743B2/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Description

  The present invention relates to a setting information generation system and a setting information generation method for generating setting information to be set in a node of a communication system.
  Conventionally, for various purposes, a computer has been made a virtual machine (VM) by server virtualization technology. In addition, using this technique, it is considered that a node (core node) in a core network of a mobile communication network (mobile communication network) is a virtual machine (see, for example, Non-Patent Document 1).
ETSI Group Specification (ETSI GS NFV 002 v1.1.1 (2013.10)) Network Functions Virtualisation (NFV); Architectural Framework
  In the initial stage of commercial introduction of a communication system realized by NFV (Network Functions Virtualisation) disclosed in Non-Patent Document 1, the components NS (Network Service), VNF (Virtual Network Function), and VNFC (Virtual When creating a Network Function Component), it is assumed that each setting information needs to be designed and created in advance.
  However, it is desirable that the setting information be automatically generated in consideration of cost reduction related to the design and creation of the setting information and improvement in follow-up performance of the communication system with respect to changes in traffic.
  The present invention has been made in view of the above, and an object of the present invention is to provide a setting information generation system and a setting information generation method capable of automatically generating setting information of a communication system.
  In order to solve the above-described problem, the setting information generation system of the present invention is a setting related to an additional node that is added to a communication system including nodes connected to each other via a network in addition to an existing node. When an information generation request is acquired, means for acquiring existing setting information, which is setting information of an existing node constituting the communication system, and network information relating to a network to which the additional node is connected, and adding to the communication system Whether or not an additional condition for adding a node is satisfied, is determined based on at least one of existing setting information and network information, or both, and when the additional condition is satisfied, based on the existing setting information, Means for generating setting information of the additional node.
  According to such a setting information generation system, when the generation request is acquired, the existing setting information is acquired, and the setting information related to the additional node is generated based on the acquired existing setting information. With this configuration, the setting information can be automatically generated based on the setting information generation request regarding the additional node. Further, according to such a setting information generation system, when the generation request is acquired, the existing setting information and the network information are acquired, and whether or not the additional condition is satisfied, at least one of the existing setting information and the network information, Alternatively, determination is made based on both, and setting information is generated when the additional condition is satisfied. With such a configuration, when the additional condition for adding the additional node to the communication system is satisfied, the setting information regarding the additional node is generated, so that the setting information can be generated more reliably without waste. .
  Further, in the setting information generation system of the present invention, the nodes constituting the communication system have a hierarchical structure, and a node in a certain hierarchy is managed by a management node that is a predetermined node in the hierarchy one level above. The network to which the management node is connected is managed by the management node of the node, and the acquisition means may acquire the existing setting information of the management node of the additional node and network information related to the network managed by the management node. If such a configuration is adopted, it is determined whether or not the additional condition is satisfied and the setting information is generated based on the existing setting information and network information of the management node that manages the additional node, so that the additional condition is more reliably satisfied. It can be determined whether or not setting information is generated.
  In the setting information generation system of the present invention, the existing setting information of the management node includes the maximum number of nodes that can be managed by the management node, and the means for generating includes an additional condition for adding an additional node to the communication system. Is determined based on a comparison between the maximum number of nodes included in the existing setting information of the management node and the number of nodes managed by the management node. Based on the setting information, additional node setting information may be generated. With this configuration, for example, when the number of nodes currently managed by the management node is equal to the maximum number of nodes, it is determined that the additional condition is not satisfied because no more nodes can be added to the communication system. It is possible to determine whether or not the additional condition is satisfied.
  In the setting information generation system according to the present invention, the network information of the management node includes a connection condition for connecting to the network managed by the management node, and the means for generating adds an additional node to the communication system. Is determined based on the connection conditions included in the network information of the management node, and if the additional conditions are satisfied, configuration information for the additional nodes is generated based on the existing configuration information May be. If such a configuration is adopted, it is determined whether or not the additional condition is satisfied based on the connection condition included in the network information of the management node that manages the additional node. Can be determined.
  The setting information generation system of the present invention further includes means for transmitting a processing request based on a determination result that the additional condition is not satisfied to the management node of the additional node when the additional condition is not satisfied. May be. By adopting such a configuration, for example, when the additional condition is not satisfied, a processing request for satisfying the additional condition can be escalated to the management node, so even if the additional condition is not satisfied, When the management node performs processing that satisfies the additional condition based on the processing request, the additional condition is satisfied, and setting information can be generated.
  By the way, the present invention can be described as the invention of the setting information generation system as described above, and can also be described as the invention of the setting information generation method as follows. This is substantially the same invention only in different categories, and has the same operations and effects.
  That is, the setting information generation method according to the present invention is a setting information generation method executed by the setting information generation system, and is an existing communication system configured to include nodes connected to each other via a network. When a setting information generation request related to an additional node is acquired in addition to the node, the existing setting information that is the setting information of the existing node constituting the communication system and the network related to the network to which the additional node is connected It is determined based on at least one of existing setting information and / or network information, and whether or not an additional condition for adding an additional node to the communication system is satisfied, and whether the additional condition is satisfied. Generating configuration information for additional nodes based on existing configuration information, and Including the.
  According to the present invention, setting information of a communication system can be automatically generated.
It is a figure which shows the structure of the management system which concerns on embodiment of this invention, and the mobile communication system containing the said management system. It is the figure which showed the hierarchy of the component. It is a figure which shows the structure of the setting information automatic generation part which concerns on embodiment of this invention, and a relationship information record. It is an example table of the setting information hold | maintained at a relationship information record. It is an example of the table of the relationship information hold | maintained at a relationship information record. It is a figure which shows the hardware constitutions of the apparatus which has the setting information automatic generation part which concerns on embodiment of this invention. It is a sequence diagram (the 1) which shows the process (setting information generation method) performed by the setting information automatic generation part which concerns on embodiment of this invention. It is a sequence diagram (the 2) which shows the process (setting information generation method) performed by the setting information automatic generation part which concerns on embodiment of this invention. It is a sequence diagram (the 3) which shows the process (setting information generation method) performed by the setting information automatic generation part which concerns on embodiment of this invention. It is a sequence diagram (the 4) which shows the process (setting information generation method) performed by the setting information automatic generation part which concerns on embodiment of this invention. It is a sequence diagram (the 5) which shows the process (setting information generation method) performed by the setting information automatic generation part which concerns on embodiment of this invention. It is a sequence diagram (the 6) which shows the process (setting information generation method) performed by the setting information automatic generation part which concerns on embodiment of this invention.
  Hereinafter, the mobile communication system 1 according to the present embodiment will be described in detail with reference to the drawings. In the description of the drawings, the same elements are denoted by the same reference numerals, and redundant description is omitted.
  FIG. 1 shows a configuration of a mobile communication system 1 including a management system 2 (communication system) according to the present embodiment. The mobile communication system 1 is a system that provides the mobile communication terminal 11 with a mobile communication function. The mobile communication terminal 11 is a device used by a user to connect to a mobile communication system (mobile communication network) by wireless communication and perform mobile communication. Specifically, the mobile communication terminal 11 corresponds to a mobile phone or the like. For example, the mobile communication terminal 11 establishes a call connection with the opposite node 12 via the mobile communication system 1 to perform communication. The opposite node 12 is, for example, another mobile communication terminal, a server device that provides various services to the mobile communication terminal, or a device for connecting to another communication network (for example, MME (Mobility Management Entity), S-GW (Serving Gateway), P-GW (PDN Gateway)) and the like. The mobile communication terminal 11 can perform mobile communication by, for example, a user of the mobile communication terminal making a contract with a communication carrier of the mobile communication system 1. The mobile communication terminal may be the same as a conventional mobile communication terminal.
  As shown in FIG. 1, the management system 2 includes an orchestrator 4, a VNFM (VNF Manager) 6, and a VIM (Virtual Infrastructure Manager) 8. The mobile communication system 1 includes an OSS / BSS (Operations Support System / Business Support System) 3, an NFVI (NFV Infrastructure) 7, and a VNF (Virtual Network Function) 5. These components constitute the core network of the mobile communication system 1. Note that components that need to transmit and receive information to each other are connected by wire or wirelessly so that information can be transmitted and received.
  In the mobile communication system 1 according to the present embodiment, a communication function is provided to the mobile communication terminal 11 by a virtual server operating in a virtual machine realized on a physical server. That is, the mobile communication system 1 is a virtualized mobile communication network. The communication function is provided to the mobile communication terminal 11 by executing communication processing corresponding to the communication function by the virtual machine.
  The NFVI 7 is a physical resource, a virtualization layer, and a virtualization resource that constitute a virtualization environment. Physical resources include computing resources, storage resources, and transmission resources. The virtualization layer virtualizes physical resources and provides them to the VNF 5 (APL). The virtualized resource is a virtualized infrastructure resource provided to the VNF 5. That is, the NFVI 7 is a virtualized resource configured to include a physical server that is a physical server device that performs communication processing in the mobile communication system 1. The physical server includes a storage unit such as a CPU (core, processor), a memory, and a hard disk. Usually, a plurality of physical servers constituting the NFVI 7 are arranged together at a base such as a data center (DC). In the data center, the arranged physical servers are connected by a network inside the data center, and can exchange information with each other. The mobile communication system 1 is provided with a plurality of data centers. Data centers are connected by a network, and physical servers provided in different data centers can transmit / receive information to / from each other via the network.
  The VNF 5 is a virtual server (function for executing communication processing) that is a virtual communication processing node that executes communication processing. VNF5 is realized in NFVI7. In VNF5, for example, a virtual machine (VM) technology is used, a CPU provided in NFVI7 is allocated for VNF5, a virtual machine is realized on the allocated CPU, and a program is executed on the virtual machine. It is realized by. The VNF 5 is normally generated (implemented) according to the communication process to be executed. Further, the VNF 5 may be configured to include a plurality of VNFCs (Virtual Network Function Components) that are its constituent elements.
  The mobile communication system 1 includes one or more (or multiple) VNFs 5. The VNF 5 corresponds to a node such as CSCF (Call Session Control Function) or AS (Application Server) in the IMS. Alternatively, the VNF 5 is a GPRS (General Packet Radio Service) system, which is one of mobile communication systems, for example, an SGSN (Serving GPRS Support Node), an LTE / EPC (Long Term Evolution / Evolved Packet Core) system, an MME ( It corresponds to a node such as Mobility Management Entity) or S-GW.
  The OSS / BSS 3 is a node that performs service management in the mobile communication system 1 and instructs the management system 2 regarding a communication function in the mobile communication system 1. For example, the OSS / BSS 3 instructs the management system 2 to activate a new communication function (communication service). The OSS / BSS 3 can be operated by a telecommunications carrier related to the mobile communication system 1.
  The orchestrator 4 that is a component of the management system 2 is an overall management node (functional entity) that manages the entire NFVI 7 that is a virtualized resource. The orchestrator 4 receives an instruction from the OSS / BSS 3 and performs a process according to the instruction. The orchestrator 4 manages the entire mobile communication network of infrastructure and communication services. The orchestrator 4 realizes a communication service composed of a plurality of VNFs 5 at an appropriate place via the VNFM 6 and the VIM 8. For example, service life cycle management (specifically, for example, generation, update, scale control, event collection), resource distribution / reservation / allocation management, service / instance management, and policy management (in the mobile communication network) Specifically, for example, resource reservation / allocation, optimal placement based on geography / laws, etc.) is performed.
  The VNFM 6 that is a component of the management system 2 is a virtual communication function management node (functional entity) that manages the VNF 5. A plurality of VNFMs 6 may be provided in the mobile communication system 1. In that case, VNFM6 managed for every VNF5 may be predetermined. The VNFM 6 performs life cycle management of the VNF 5 (APL, application). The VNFM 6 performs overall control related to the virtualization of the VNF 5. For example, VNF5 instance generation, update, scale control, termination, and auto healing (automatic healing) are performed.
  The VIM 8 that is a component of the management system 2 is a virtual resource management node (functional entity) that manages each virtual resource (infrastructure resource) in a unit in which the VNF 5 in the NFVI 7 is realized. Specifically, resource allocation / update / recovery management, association between virtual resources and physics, and management of hardware resources and SW resources (hypervisor) list are performed. Usually, the VIM 8 performs management for each data center (station building). The management of virtual resources can be performed by a method according to the data center. There are various types of data center management methods (management resource mounting methods) such as OpenStack and vCenter. Normally, the VIM 8 is provided for each data center management method. In other words, the management system 2 includes a plurality of VIMs 8 that manage the respective virtual resources in units in which the VNFs 5 in the NFVI 7 are realized in different ways. Note that the units of virtual resources managed by different management methods do not necessarily have to be data center units.
  The orchestrator 4, the VNFM 6, and the VIM 8 are realized by executing a program on a physical server device. The orchestrator 4, the VNFM 6, and the VIM 8 may be realized by separate physical server devices or may be realized by the same server device. The orchestrator 4, VNFM6, and VIM8 (programs for realizing) may be provided from different vendors.
  An SDN (Software Defined Networking) 10 is a network that can dynamically set and change configuration, induction, performance, and the like by software.
  The architecture is based on that described in Non-Patent Document 1. Further, the mobile communication system 1 may include components other than those described above in order to realize a mobile communication function.
  Here, the relationship between the hierarchy of components (nodes) that are components of the management system 2 and the network will be described. The management system 2 includes components that are connected to each other via a network. The components have a hierarchical structure, and a component in a certain hierarchy is a management component (management node) that is a predetermined component in the hierarchy one level above. The network to which a component of a certain hierarchy is connected is managed by the management component of the component. It should be noted that the highest layer component does not have a management node or is managed by a node of another system connected by a network. In addition, the network to which the highest layer component is connected is managed by a node of another system.
  As a specific example, FIG. 2 is a diagram showing a hierarchy of components. As shown in FIG. 2, there are three layers of components: an NS (Network Service) layer, a VNF (Virtual Network Functions) layer, and a VNFC (Virtual Network Function Components) layer. The NS layer is composed of one or more NS, and includes a VNF layer in the lower layer. The VNF layer is composed of one or more VNFs, and includes the VNFC layer in the lower layer. The VNF of the VNF layer is managed by a predetermined NS that is a management component of the NS layer that is one level above, and a network to be connected (a network that connects between VNF and VNF) is the management component (predetermined NS) Managed by. The VNFC layer is composed of one or more VNFCs, and the VNFC is a minimum unit of components. The VNFC of the VNFC layer is managed by a predetermined VNF that is a management component of the VNF layer that is one level above, and a network to be connected (a network that connects between VNFC and VNFC) is the management component (predetermined VNF) Managed by.
  As shown in FIG. 1, the management system 2 according to this embodiment further includes a setting information automatic generation unit 9 (setting information generation system). The setting information automatic generation unit 9 generates setting information regarding an additional component (additional node) that is added to the management system 2 in addition to the existing component. The generated setting information is set to a target additional node by a component of the management system 2 such as the setting information automatic generation unit 9. Note that the setting information automatic generation unit 9 may be configured as a single computer device or as a system that includes a plurality of computer devices and performs processing in cooperation with each other, rather than as a function or means. . Moreover, although the setting information automatic generation unit 9 is shown as a higher function of the orchestrator 4 in FIG. 1, it exists as a higher function of OSS / BSS3, VNFM6, or VIM8 depending on the range of setting information generated by the function. Or may be included as part of the function.
  FIG. 3 is a functional block diagram of the setting information automatic generation unit 9. As shown in FIG. 3, the setting information automatic generation unit 9 includes a generation processing request reception unit 90 (request acquisition unit), an automatic generation unit 91 (addition determination unit, setting information generation unit, escalation unit), and an information acquisition unit 92. (Information acquisition means).
  The setting information automatic generation unit 9 refers to a relationship information record 900 (storage means) held by a component (for example, the orchestrator 4) of the management system 2. Examples of tables of setting information and relationship information (network information) held in the relationship information record 900 are shown in FIGS. 4 and 5, respectively.
  The setting information is information set for each component (including additional components) in the management system 2. Note that the setting information of the existing components constituting the management system 2 is appropriately referred to as “existing setting information”. In the setting information table example shown in FIG. 4, the setting information includes an identifier “Identifier”, a type “Type”, a “Cardinality” indicating the number that can have a value of “Type”, and an explanation content “Description”. ”. Among the values of “Type”, “Leaf” is a single information element that identifies the value, “Reference” is an information element that holds a reference to another information element, and “Element” It is the information element itself that identifies the other levels in the tree structure data. Of the “Cardinality” values, “1” indicates that a single value can be obtained, “0 ... N” indicates that 0 or more values can be included, and “1 ...” N ″ indicates that it can have one or more values. The above-described terms described in FIG. 4 (and the terms in FIG. 5 described later) conform to the description of the standardized draft document “GS NFV-MAN 001 v0.6.3 (2014-09)” of NFV.
  The contents of the table example of the setting information shown in FIG. 4 will be specifically described. In the setting information, “id” indicating the component ID, “component_layer” indicating the component hierarchy (NS / VNF / VNFC), and connection are connected. “Network” indicating a reference to the network, “network_id” indicating the network ID (eg, IP address) of the component, “atribute” indicating the attribute of the component (eg, service type such as IMS or EPC), “Application_data” indicating the setting information as an application (for example, the range of subscribers providing services, billing information, connection destination information at the application level, etc.), component information of the lower layer components (attribute, maximum number of arrangements (maximum Number of nodes, the maximum component that the managed component can manage Number))), etc. "Vnf_reference" or "vnfc_reference" indicating the reference to the component in the hierarchy ("vnf_reference" if the component for which the setting information is set is NS, and "vnfc_reference" if the component is VNF) Used and not used in the case of VNFC because it is the lowest layer). Since “application_data” depends on the implementation of the application, the setting value items and ranges differ for each application.
  The relationship information is information related to the network to which the additional component is connected in the management system 2. Relationship information exists for each network in the management system 2. In the relationship information table example shown in FIG. 5, the relationship information is defined by “Identifier”, “Type”, “Cardinality”, and “Description”, as in the setting information table example shown in FIG. 4. . The contents of the table example of the relationship information shown in FIG. 5 will be specifically described. The relationship information includes “id” indicating an ID of a network (for example, Virtual Link), a network management component (for example, NS, “Parent_component” indicating a reference to VNF, VNFC, etc.) “connect_requirements” indicating conditions for connecting to the network (managed by the management component) (for example, the maximum number of connections, component attributes, etc.), currently connected “Connected_components” indicating a reference to a component that is allocated, “allocate_network_id_range” indicating a network ID that can be allocated, conditions for scaling by the network (scaling policy, for example, connection components necessary for scaling, required bandwidth) scale_policy ”is included.
  As described above, the setting information automatic generation unit 9 may be configured by hardware such as a CPU. FIG. 6 is a diagram illustrating an example of a hardware configuration when the setting information automatic generation unit 9 is configured by hardware. As shown in FIG. 6, the setting information automatic generation unit 9 shown in FIG. 3 physically includes a CPU 100, a RAM 101 and a ROM 102 as main storage devices, an input / output device 103 such as a display, a communication module 104, and an auxiliary device. The computer system includes a storage device 105 and the like.
  The function of each functional block of the setting information automatic generation unit 9 shown in FIG. 3 is input / output under the control of the CPU 100 by loading predetermined computer software on the hardware such as the CPU 100 and the RAM 101 shown in FIG. It is realized by operating the device 103, the communication module 104, and the auxiliary storage device 105, and reading and writing data in the RAM 101.
  Hereinafter, each functional block of the setting information automatic generation unit 9 illustrated in FIG. 3 will be described.
  The generation process request receiving unit 90 acquires a generation process request (generation request) for setting information to be set in the additional component. Specifically, the generation process request receiving unit 90 has a function of receiving a setting information generation process request from the orchestrator 4 and notifying the received generation process request to the automatic generation unit 91. Further, the generation process request accepting unit 90 has a function of controlling so that no contradiction occurs in the state of the management system 2 when a plurality of generation process requests are transmitted in parallel and continuously (generation process request scheduling function). ).
  The automatic generation unit 91 has a function of automatically generating setting information based on information acquired from the information acquisition unit in response to the generation processing request received from the generation processing request receiving unit 90. In addition, the automatic generation unit 91 confirms the existing setting information and the relationship information acquired from the information acquisition unit 92, and if the condition necessary for generating the setting information is not satisfied, an operation for satisfying the condition is performed. Alternatively, it has a function of notifying the orchestrator 4 through the generation processing request receiving unit 90 that generation is impossible.
  Specifically, the automatic generation unit 91 sets an additional condition for adding an additional component to the management system 2 based on at least one of the existing setting information and the relationship information acquired by the information acquisition unit 92, or both. It is determined whether it is satisfied. The automatic generation unit 91 satisfies the additional condition based on the comparison between the maximum number of components included in the existing setting information of the management component acquired by the information acquisition unit 92 and the number of components managed by the management component. It is determined whether or not. Further, the automatic generation unit 91 determines whether or not the additional condition is satisfied based on the connection condition included in the relationship information of the management component acquired by the information acquisition unit 92. Further, when the automatic generation unit 91 determines that the additional condition is satisfied, the automatic generation unit 91 generates setting information to be set in the additional component based on the existing setting information acquired by the information acquisition unit 92. Further, when the automatic generation unit 91 determines that the additional condition is not satisfied, the automatic generation unit 91 transmits a processing request based on the determination result to the management component of the additional component.
  The information acquisition unit 92 has a function of acquiring setting information and relationship information of existing components from the relationship information record 900 and notifying the automatic generation unit 91 of the setting information and relationship information. Specifically, the information acquisition unit 92 is the setting information of the existing components constituting the management system 2 stored in the relationship information record 900 based on the generation processing request acquired by the generation processing request receiving unit 90. The existing setting information and the relationship information regarding the network to which the additional component is connected in the management system 2 are acquired. Further, the information acquisition unit 92 acquires the existing setting information of the management component of the additional component and the relationship information regarding the network managed by the management component.
  The above is the configuration of the management system 2 according to the present embodiment. Hereinafter, an example of setting information automatic generation control (setting information generation method) according to the present embodiment will be described with reference to the sequence diagrams of FIGS.
  In the sequence diagram shown in FIG. 7, first, in S1 (request acquisition step), a setting information generation processing request to be set as an additional component is sent from the setting information generation request source (for example, orchestrator 4) to the generation processing request receiving unit 90. Sent. Note that the setting information generation request source may be the OSS / BSS 3, the VNFM 6, the VIM 8, or the setting information automatic generation unit 9. Examples of data included in the generation processing request include a component ID one level above the additional component, an attribute of the additional component, and hierarchical information of the additional component. Next, a setting information generation instruction (including data included in the generation process request) is transmitted from the generation process request receiving unit 90 to the automatic generation unit 91 in S2 (request acquisition step). Next, a layer (NS, VNF, or VNFC) check of the additional component is performed in S3. For example, the automatic generation unit 91 performs a layer check of the additional component based on the layer information of the additional component included in the generation processing request.
  Next, in S4 (information acquisition step), from the automatic generation unit 91 to the information acquisition unit 92, an acquisition request for existing setting information and relationship information (the ID of the component in the hierarchy one level higher than the additional component acquired in S2) Is sent). For example, when VNFC setting information is generated, a relationship information acquisition request in which VNF setting information as an upper layer and information on a network to which VNF connects (manages) is described is transmitted. Next, an acquisition request for existing setting information and relationship information is transmitted from the information acquisition unit 92 to the relationship information record 900 in S5 (information acquisition step). The relationship information record 900 acquires the existing setting information of the component by using the ID of the component one level above the additional component included in the received acquisition request. Next, the relationship information record 900 acquires the relationship information of the network by referring to the value of “network” indicating the reference to the connected network included in the acquired existing setting information. Next, the existing setting information and the relationship information are transmitted from the relationship information record 900 to the information acquisition unit 92 in S6 (information acquisition step). Next, the existing setting information and the relationship information are transmitted from the information acquisition unit 92 to the automatic generation unit 91 in S7 (information acquisition step).
  Note that the process of S3 may be performed after the process of S7. In that case, the automatic generation unit 91 specifies the hierarchy of the additional component from the setting information of the management component of the additional component that sets the existing setting information acquired in S7 after the process of S7. Specifically, the automatic generation unit 91 specifies the layer of the additional component by using the value of “component_layer” and the value of “vnf_reference / vnfc_reference” in the management component setting information.
  Subsequent to S7, in S8 (addition determination step), the maximum arrangement number of components for generating the existing setting information is checked. For example, when generating the VNFC setting information, the maximum number of VNFC arrangements described in the VNF setting information that is the upper layer is checked. Specifically, the automatic generation unit 91 checks the maximum number of arrangements using the value of “constituent_vnf / constituent_vnfc” in the management component setting information. Based on the check result of the maximum number of arrangements in S8, the processing continues to the sequence diagram shown in FIG. 8 or the sequence diagram shown in FIG.
  The sequence diagram shown in FIG. 8 shows a sequence of processing that continues when the maximum number of arrangements is not exceeded in S8 of FIG. The sequence from S9 to S12 shown as L1 in FIG. 8 is used for confirming the conditions necessary for arrangement in S13 (Purpose 1), and is used to generate setting information in S14 of FIG. 9 described later. Therefore, when the purpose 1 and the purpose 2 can be satisfied only by the existing setting information and the relationship information acquired from the relationship information record 900, the L1 may not be performed. . Hereinafter, L1 will be described.
  In S9, the information generation request for confirming the conditions necessary for the arrangement is transmitted from the automatic generation unit 91 to the information acquisition unit 92. For example, when generating VNFC setting information, the status of resources (for example, CPU, memory, HDD) necessary for creating the VNFC and the status to the connection destination network (to determine whether the VNFC can be connected) Information) is transmitted. Next, in S10, an information provision request for confirming conditions necessary for arrangement is transmitted from the information acquisition unit 92 to the information provider. Note that the information provider may be any component of the mobile communication system 1. Next, information for confirming the conditions necessary for arrangement is transmitted from the information provider to the information acquisition unit 92. Next, information for confirming the conditions necessary for arrangement is transmitted from the information acquisition unit 92 to the automatic generation unit 91. The above is an explanation of L1.
  Next, in S13 (addition determination step), it is checked whether or not a condition necessary for the arrangement is satisfied. Two specific examples will be described below. First, as an example of the conditions necessary for the arrangement, the availability of storage means such as a CPU, a memory, and a hard disk included in the NFVI 7 can be mentioned. The automatic generation unit 91 obtains from the NFVI 7 (there may be another component, for example, via the orchestrator 4), and checks whether there is a resource sufficient to generate a component. Second, the automatic generation unit 91 is a condition for connecting to a network (network managed by a higher-level component) to which an additional component can be connected (“connect_requirements” in the relationship information table example illustrated in FIG. 5). To check if For example, when checking the maximum number of connections, the automatic generation unit 91 performs the check by comparing with the number of “connected_components” in the relationship information table example illustrated in FIG. 5. Based on the check result of whether or not the conditions necessary for the arrangement of S13 are satisfied, the processing continues to the sequence diagram shown in FIG. 9, the sequence diagram shown in FIG. 11, or the sequence diagram shown in FIG.
  The sequence diagram shown in FIG. 9 shows the sequence of processing that follows when the conditions necessary for the arrangement are satisfied in S13 of FIG. In FIG. 9, the setting information of the additional component is automatically generated in S14 (setting information generation step). For example, when generating VNFC setting information, “id” in the setting information table shown in FIG. 4 is assigned in accordance with a predetermined numbering standard. Next, “network” refers to the information of “network” to which the existing VNFC is connected. Next, “network_id” is assigned according to a predetermined assignment criterion from “allocate_network_id_range” described in the relationship information of the network to which the existing VNFC is connected. Next, “attribute” is set to a value included in the setting information generation request. Next, “application_data” is assigned in accordance with a predetermined provision criterion, although the items and ranges of setting values differ for each application as described above.
  Subsequent to S14, the setting information of the additional component is transmitted from the automatic generation unit 91 to the generation processing request reception unit 90 in S15. Next, in S16, the setting information of the additional component is transmitted from the generation process request receiving unit 90 to the setting information generation request source.
  The sequence diagram shown in FIG. 10 shows a sequence of processing that continues when the maximum number of arrangements is exceeded in S8 of FIG. If the maximum number of arrangements is exceeded in S8, the automatic generation unit 91 also confirms whether there is a higher hierarchy in order to execute the escalation process. In FIG. 10, an escalation request is transmitted from the automatic generation unit 91 to the generation processing request reception unit 90 in S17. If it is determined in S8 in FIG. 7 that escalation is not possible, an escalation impossible notification is transmitted. Next, in S18, an escalation request is transmitted from the generation process request receiving unit 90 to the setting information generation request source. If it is determined in S8 in FIG. 7 that escalation is not possible, an escalation impossible notification is transmitted. If the setting information automatic generation unit 9 has the authority to determine whether or not to execute the escalation process, S18 is not transmitted, and the escalation process (upper layer setting information generation process) is started from S2 in FIG.
  The sequence diagram shown in FIG. 11 is a case where the conditions necessary for the arrangement are not satisfied in S13 of FIG. 8 (one or more conditions necessary for the arrangement are not satisfied) and the conditions necessary for the arrangement are satisfied. 4 shows a sequence of processing that follows when the authority to execute the processing for this is in the setting information automatic generation unit 9. In FIG. 11, in S <b> 19, the automatic generation unit 91 transmits a notification that the conditions necessary for the arrangement are not satisfied to the generation processing request reception unit 90 and the details including the conditions to be satisfied. Next, a process for satisfying a necessary condition is executed in S20.
  Hereinafter, a specific example of the process for satisfying the necessary condition executed in S20 will be described. For example, when the condition for connecting to the network is not satisfied, it is necessary to create a new network. In this case, the setting information automatic generation unit 9 first checks “scale_policy” in the relationship information of the network to which the additional component can be connected. As an example, whether there is a bandwidth necessary for creating a network is confirmed by information obtained from an information provider. Further, the setting information automatic generation unit 9 checks whether or not there is a connection component other than the additional component necessary for the network scale, and if there is, a new generation processing request reception request for the setting information of the component is received. To the unit 90.
  The sequence diagram shown in FIG. 12 is a case where the conditions necessary for the arrangement are not satisfied in S13 of FIG. 8 (one or more conditions necessary for the arrangement are not satisfied) and the conditions necessary for the arrangement are satisfied. The sequence of the processing that follows when the setting information automatic generation unit 9 does not have the authority to execute the processing for this is shown. In FIG. 12, in S <b> 21, the automatic generation unit 91 transmits to the generation processing request reception unit 90 a notification that the conditions necessary for the arrangement are not satisfied and the details of the conditions to be satisfied. Next, in S22, the generation process request receiving unit 90 transmits a notification that the conditions necessary for the arrangement are not satisfied to the setting information generation request source and the details including the conditions to be satisfied. At this time, the setting information generation request source determines whether or not to perform the process that satisfies the conditions necessary for the arrangement, and if it determines that the setting information generation request is performed, the setting information generation request is again issued after executing the process. 9 to send.
  Next, the effect of the setting information automatic generation unit 9 configured as in the present embodiment will be described.
  According to the setting information automatic generation unit 9 of the present embodiment, when a generation request is acquired, the existing setting information is acquired, and setting information related to the additional component is generated based on the acquired existing setting information. With this configuration, the setting information can be automatically generated based on a setting information generation request regarding the additional component. In addition, according to such a setting information automatic generation unit 9, when a generation request is acquired, the existing setting information and the relationship information are acquired, and whether or not the additional condition is satisfied, whether the existing setting information and the network information are satisfied. Determination is made based on at least one or both, and setting information is generated when the additional condition is satisfied. With such a configuration, when the additional condition for adding the additional component to the management system 2 is satisfied, the setting information regarding the additional component is generated, so the setting information can be generated more reliably without waste. it can.
  In addition, according to the setting information automatic generation unit 9 of the present embodiment, it is possible to determine whether or not the additional condition is satisfied based on the existing setting information and relationship information of the management component that manages the additional component, and to generate setting information. Therefore, it is possible to more reliably determine whether or not the additional condition is satisfied and to generate setting information.
  Further, according to the setting information automatic generation unit 9 of the present embodiment, for example, when the number of components currently managed by the management component is equal to the maximum number of components, no more components can be added to the management system 2. Therefore, it can be determined that the additional condition is not satisfied, and it can be more reliably determined whether or not the additional condition is satisfied.
  Moreover, according to the setting information automatic generation unit 9 of the present embodiment, since it is determined whether or not the additional condition is satisfied based on the connection condition included in the relationship information of the management component that manages the additional component, It is possible to more reliably determine whether or not the additional condition is satisfied.
  Further, according to the setting information automatic generation unit 9 of the present embodiment, for example, when it is determined that the additional condition is not satisfied, the processing request for satisfying the additional condition is escalated to the management component. Therefore, even if it is determined that the additional condition is not satisfied, the management component performs the process that satisfies the additional condition based on the processing request, so that the additional condition is satisfied and the setting information is generated. It can be performed.
  Conventionally, in the initial stage of NFV, a virtual machine template in which communication system setting information has already been input is used, or setting information created in advance is input after creation of a virtual machine. It was assumed that the setting information of the communication system used was used. However, it is desirable that the setting information is automatically generated and input in consideration of cost reduction related to the design / creation of the setting information and improvement in performance followability to traffic.
  According to the setting information automatic generation unit 9 of the present embodiment relating to the method for automatically generating setting information of the communication system, the components that make up the communication system and the networks that connect the components are associated with each other, and the connection conditions, scale policies, etc. By holding and dynamically updating, setting information can be automatically generated when there is a request for adding a new component. Thus, automating the design and creation of the setting information has the effect of reducing the costs associated with them. In addition, since the design / creation time can be shortened, the time required for reflection in the communication system can be shortened, and there is an effect of improving the follow-up performance of the communication system with respect to changes in traffic.
  DESCRIPTION OF SYMBOLS 1 ... Mobile communication system, 2 ... Management system, 3 ... OSS / BSS, 4 ... Orchestrator, 5 ... VNF, 6 ... VNFM, 7 ... NFVI, 8 ... VIM, 9 ... Setting information automatic generation part, 10 ... SDN , 11 ... mobile communication terminal, 12 ... opposite node, 90 ... generation process request reception unit, 91 ... automatic generation unit, 92 ... information acquisition unit, 900 ... relationship information record.

Claims (5)

  1. Addition that is a virtual node that is added to an existing virtual node to a communication system that includes virtual nodes that are virtualized based on virtualization technology and that are connected to each other via a network When a generation request for requesting generation of setting information related to a virtual node is acquired, existing setting information that is setting information of an existing virtual node that constitutes the communication system and network information related to a network to which the additional virtual node is connected Means to obtain,
    When the additional condition for adding an additional virtual node to the communication system is satisfied, determined based on at least one of the existing setting information and the network information, or both, and when the additional condition is satisfied A means for automatically generating setting information of the additional virtual node based on the existing setting information;
    Means for setting the automatically generated setting information in an additional virtual node;
    Equipped with a,
    The virtual nodes constituting the communication system have a hierarchical structure, a virtual node in a certain hierarchy is managed by a management virtual node that is a predetermined virtual node in the hierarchy one level above, and a network to which a virtual node in a certain hierarchy is connected Virtual node management Managed by virtual nodes,
    The acquisition means acquires the existing setting information of a management virtual node of an additional virtual node and the network information related to a network managed by the management virtual node.
    Configuration information generation system.
  2. The existing setting information of the management virtual node includes the maximum number of nodes that can be managed by the management virtual node,
    The generating means manages whether or not an additional condition for adding an additional virtual node to the communication system is satisfied, the maximum number of nodes included in the existing setting information of the management virtual node and the management virtual node. Automatically determining the setting information of the additional virtual node based on the existing setting information when the additional condition is satisfied based on the comparison with the number of nodes that are present,
    The setting information generation system according to claim 1 .
  3. The network information of the management virtual node includes a connection condition for connecting to a network managed by the management virtual node,
    The generating means determines whether or not an additional condition for adding an additional virtual node to the communication system is satisfied based on a connection condition included in the network information of the management virtual node, and satisfies the additional condition Automatically generating the setting information of the additional virtual node based on the existing setting information,
    The setting information generation system according to claim 1 or 2 .
  4. A means for transmitting a processing request based on a determination result that the additional condition is not satisfied when the additional condition is not satisfied to the management virtual node of the additional virtual node;
    The setting information generation system according to any one of claims 1 to 3 .
  5. A setting information generation method executed by a setting information generation system,
    Addition that is a virtual node that is added to an existing virtual node to a communication system that includes virtual nodes that are virtualized based on virtualization technology and that are connected to each other via a network When a generation request for requesting generation of setting information related to a virtual node is acquired, existing setting information that is setting information of an existing virtual node that constitutes the communication system and network information related to a network to which the additional virtual node is connected A step to obtain,
    When the additional condition for adding an additional virtual node to the communication system is satisfied, determined based on at least one of the existing setting information and the network information, or both, and when the additional condition is satisfied Automatically generating setting information of the additional virtual node based on the existing setting information;
    Setting the automatically generated setting information in an additional virtual node;
    Only including,
    The virtual nodes constituting the communication system have a hierarchical structure, a virtual node in a certain hierarchy is managed by a management virtual node that is a predetermined virtual node in the hierarchy one level above, and a network to which a virtual node in a certain hierarchy is connected Virtual node management Managed by virtual nodes,
    The obtaining step obtains the existing setting information of the management virtual node of the additional virtual node and the network information related to a network managed by the management virtual node.
    Setting information generation method.
JP2014236534A 2014-11-21 2014-11-21 Setting information generation system and setting information generation method Active JP6460743B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2014236534A JP6460743B2 (en) 2014-11-21 2014-11-21 Setting information generation system and setting information generation method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP2014236534A JP6460743B2 (en) 2014-11-21 2014-11-21 Setting information generation system and setting information generation method

Publications (2)

Publication Number Publication Date
JP2016100750A JP2016100750A (en) 2016-05-30
JP6460743B2 true JP6460743B2 (en) 2019-01-30

Family

ID=56077587

Family Applications (1)

Application Number Title Priority Date Filing Date
JP2014236534A Active JP6460743B2 (en) 2014-11-21 2014-11-21 Setting information generation system and setting information generation method

Country Status (1)

Country Link
JP (1) JP6460743B2 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102075760B1 (en) * 2016-10-05 2020-03-02 에스케이텔레콤 주식회사 Apparatus and method for managing and orchestrating network function virtualization

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2007243372A (en) * 2006-03-07 2007-09-20 Nec Corp Central control system and method for network communication device
JP4894590B2 (en) * 2007-03-30 2012-03-14 ブラザー工業株式会社 Network system, information processing apparatus, and information processing program
US8155028B2 (en) * 2008-03-17 2012-04-10 Alcatel Lucent Method and apparatus for providing full logical connectivity in MPLS networks
WO2014110453A1 (en) * 2013-01-11 2014-07-17 Huawei Technologies Co., Ltd. Network function virtualization for a network device
JP2016519487A (en) * 2013-03-20 2016-06-30 ヴォルティング ホールディング ベー.フェー. Compilers and methods for software defined networks
US9973375B2 (en) * 2013-04-22 2018-05-15 Cisco Technology, Inc. App store portal providing point-and-click deployment of third-party virtualized network functions
JP2015191246A (en) * 2014-03-27 2015-11-02 株式会社Nttドコモ Communication system and management method

Also Published As

Publication number Publication date
JP2016100750A (en) 2016-05-30

Similar Documents

Publication Publication Date Title
CN108293004B (en) System and method for network slice management
US10481953B2 (en) Management system, virtual communication-function management node, and management method for managing virtualization resources in a mobile communication network
CN109952796B (en) Shareable slice instance creation and modification
US10298439B2 (en) Network functions virtualization network system and data processing method, and apparatus
RU2643451C2 (en) System and method for virtualisation of mobile network function
US10481935B2 (en) Management system, overall management node, and management method for managing virtualization resources in a mobile communication network
CN111480366A (en) Shared PDU session establishment and binding
US20190014504A1 (en) Service allocation determining method
EP3512233A1 (en) Method for managing network slice and management unit
US20200195511A1 (en) Network management method and related device
JP6263424B2 (en) Management system and management method
US20200187182A1 (en) Slice allocating method
KR20200062272A (en) Mobile network interaction proxy
EP3609161B1 (en) Network slice creating method and apparatus, and communication system
US20180004563A1 (en) Orchestrator apparatus, system, virtual machine creation method, and computer-readable recording medium
US10924966B2 (en) Management method, management unit, and system
WO2019007345A1 (en) Method, apparatus, and system for selecting network slice, and storage medium
US20200403970A1 (en) Providing Network Address Translation in a Software Defined Networking Environment
JP2015191246A (en) Communication system and management method
JP6460743B2 (en) Setting information generation system and setting information generation method
JP6305812B2 (en) Flow control apparatus and flow control method
CN109358967B (en) ME platform APP instantiation migration method and server
JP6243294B2 (en) COMMUNICATION SYSTEM, CONTROL DEVICE, AND DATABASE ACCESS METHOD
CN111245634B (en) Virtualization management method and device
US10855757B2 (en) High availability and high utilization cloud data center architecture for supporting telecommunications services

Legal Events

Date Code Title Description
A621 Written request for application examination

Free format text: JAPANESE INTERMEDIATE CODE: A621

Effective date: 20170817

A977 Report on retrieval

Free format text: JAPANESE INTERMEDIATE CODE: A971007

Effective date: 20180607

A131 Notification of reasons for refusal

Free format text: JAPANESE INTERMEDIATE CODE: A131

Effective date: 20180626

A521 Written amendment

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20180813

A131 Notification of reasons for refusal

Free format text: JAPANESE INTERMEDIATE CODE: A131

Effective date: 20181023

A521 Written amendment

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20181204

TRDD Decision of grant or rejection written
A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

Effective date: 20181218

A61 First payment of annual fees (during grant procedure)

Free format text: JAPANESE INTERMEDIATE CODE: A61

Effective date: 20181225

R150 Certificate of patent or registration of utility model

Ref document number: 6460743

Country of ref document: JP

Free format text: JAPANESE INTERMEDIATE CODE: R150