WO2016006491A1 - 制御ノード、ノード作成システム及びノード作成方法 - Google Patents
制御ノード、ノード作成システム及びノード作成方法 Download PDFInfo
- Publication number
- WO2016006491A1 WO2016006491A1 PCT/JP2015/068719 JP2015068719W WO2016006491A1 WO 2016006491 A1 WO2016006491 A1 WO 2016006491A1 JP 2015068719 W JP2015068719 W JP 2015068719W WO 2016006491 A1 WO2016006491 A1 WO 2016006491A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- node
- target node
- instruction
- identification information
- functional blocks
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5061—Partitioning or combining of resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/14—Backbone network devices
Definitions
- the present invention relates to a control node, a node creation system, and a node creation method for creating a node by combining functional blocks.
- Nodes that are components of a network such as a core network of a mobile communication network are connected to other nodes with applications / services such as network communication, voice communication, M2M (Machine to Machine) service (hereinafter collectively) Service).
- applications / services such as network communication, voice communication, M2M (Machine to Machine) service (hereinafter collectively) Service).
- P-GW Packet Data Network
- UE User Equipment
- nodes have a static configuration in which all services are processed by the same node and the same route (node permutation process). For this reason, there is a risk that costs will increase due to the implementation and operation of functions not used by many services. In addition, a variety of services are expected to develop in the future, and there is a concern that a static node configuration cannot flexibly add new functions.
- the present invention has been made in view of such a problem, and an object thereof is to provide a control node, a node creation system, and a node creation method capable of creating a node having a more flexible configuration.
- a control node arranges a plurality of functional blocks that provide a predetermined function, and processes each functional block or all functional blocks for each arranged functional block.
- each functional block executes a process according to the set scenario, and creates a target node that provides a specific function as a whole functional block.
- Creation instruction receiving means for receiving a creation instruction for creating the target node, including identification information, identification information of the target node, identification information of a plurality of functional blocks constituting the target node, and the plurality of functions Included in the creation instruction for the configuration table storage node that stores the target node configuration table that associates the scenario set for each block A plurality of functions associated with the target node identification information transmitted in the target node configuration table as a response based on the transmission by the target node identification information transmission unit.
- the configuration information receiving means for receiving the target node configuration information including the block identification information and the scenario, and the component element storage node for storing the functional block or the base node for arranging the target node, a plurality of items included in the target node configuration information Placement instruction transmission means for sending a placement instruction to place the plurality of functional blocks in combination, including functional block identification information, and target node configuration information for the plurality of functional blocks placed based on the placement instruction
- a setting instruction transmitting means for transmitting a setting instruction for setting a scenario included in Object node is created on the basis of the transmission constant instruction, and a setting instruction transmitting means.
- a creation instruction for creating a target node that provides a specific function is first received by the creation instruction receiving means.
- the configuration information receiving means receives information relating to a plurality of functional blocks constituting the target node and a scenario in which processing procedures for each of the plurality of functional blocks are defined.
- the placement instruction transmitting means transmits a placement instruction for placing a plurality of functional blocks constituting the target node in combination.
- a setting instruction for setting a scenario is transmitted to the plurality of functional blocks arranged based on the arrangement instruction by the setting instruction transmission means, and a target node is created based on the transmission of the setting instruction. .
- a plurality of functional blocks are arranged in combination, and a scenario is set for each arranged functional block, so that each functional block executes processing according to the set scenario, and the entire functional block
- a target node that provides a specific function can be created.
- the configuration contents and processing contents of the target node to be created can be specified in the target node configuration table by information regarding a plurality of functional blocks constituting the target node and a scenario set for each of the plurality of functional blocks. .
- a node having a more flexible configuration can be created.
- the creation instruction further includes identification information of the base node
- the arrangement instruction further includes identification information of the base node included in the creation instruction, and a plurality of functional blocks are combined. It is also possible to indicate an instruction to place the base node. By adopting such a configuration, it is possible to easily and reliably specify the location where the target node is created.
- a target node status table in which identification information of a created target node is associated with information on a plurality of functional blocks constituting the created target node is stored.
- Receives a change instruction to change the created target node to the changed target node including status table storage means, created target node identification information, and changed target node identification information
- a destination node changing means for sending a setting instruction for setting a post-change scenario to a plurality of function blocks corresponding to information about the acquired plurality of function blocks by controlling an indication transmission means, It may be further provided with a target node changing means for changing the created target node to the target node after the change
- a scenario for realizing the function of a desired target node (target node after change) is set for a plurality of functional blocks constituting the created target node. Thereby, the created target node can be easily and reliably changed to a desired target node.
- the target node changing means further includes: In the target node status table, the pre-change scenario, which is a scenario associated with the created target node identification information included in the change instruction, is obtained and compared with the pre-change scenario and the post-change scenario. Determine the difference between the multiple functional blocks that make up the target node and the multiple functional blocks that make up the changed target node, and change the multiple functional blocks that make up the created target node based on the determined difference It is good as well.
- the node creation system arranges a plurality of functional blocks that provide a predetermined function, and each functional block or all functions are arranged for each arranged functional block.
- each functional block executes processing according to the set scenario, and a target node that creates a target node that provides a specific function as the entire function block, and a target node A configuration table storage node that stores a target node configuration table that associates identification information of a plurality of functional blocks that constitute the target node with a scenario set in each of the plurality of functional blocks, and a functional block A component creation system including a component storage node to store, wherein the control node identifies the target node identification information.
- An arrangement instruction transmission means for transmitting an instruction; and a setting instruction transmission means for transmitting a setting instruction for setting a scenario included in the target node configuration information to a plurality of functional blocks arranged based on the arrangement instruction.
- a setting instruction transmitting means for creating a target node based on the transmission of the setting instruction
- the configuration table storage node includes the target node identification information.
- a configuration information transmitting unit that transmits target node configuration information including identification information and scenarios of the plurality of functional blocks, and the component storage node receives the configuration instruction transmitted by the configuration instruction transmitting unit Receiving means, and arranging means for arranging stored functional blocks corresponding to the identification information of the plurality of functional blocks included in the arrangement instruction.
- a target node can be created by linking a control node, a configuration table storage node, and a component storage node. That is, a plurality of functional blocks are arranged in combination, and a scenario is set for each arranged functional block, so that each functional block executes processing according to the set scenario, and a specific function as a whole functional block Can be created. Then, the configuration contents and processing contents of the target node to be created can be specified in the target node configuration table by information regarding a plurality of functional blocks constituting the target node and a scenario set for each of the plurality of functional blocks. . Thereby, a node having a more flexible configuration can be created.
- the node creation system arranges a plurality of functional blocks that provide a predetermined function, and each functional block or all functions are arranged for each arranged functional block.
- each functional block executes processing according to the set scenario, and a target node that creates a target node that provides a specific function as the entire function block, and a target node
- a configuration table storage node for storing a target node configuration table in which identification information of a plurality of functional blocks constituting the target node, identification information of a plurality of functional blocks constituting the target node, and a scenario set in each of the plurality of functional blocks are associated,
- a node creation system including a base node to be arranged, wherein the control node includes identification information of a target node;
- a creation instruction receiving means for receiving a creation instruction for creating the destination node; a destination node identification information sending means for sending identification information of the destination node included in the creation
- a configuration information transmitting unit configured to transmit target node configuration information including identification information and scenarios of a plurality of attached functional blocks, wherein the base node receives the configuration instruction received by the configuration instruction transmitting unit Means, and arrangement means for arranging functional blocks corresponding to the identification information of the plurality of functional blocks included in the arrangement instruction.
- a target node can be created by linking a control node, a configuration table storage node, and a base node. That is, a plurality of functional blocks are arranged in combination, and a scenario is set for each arranged functional block, so that each functional block executes processing according to the set scenario, and a specific function as a whole functional block Can be created. Then, the configuration contents and processing contents of the target node to be created can be specified in the target node configuration table by information regarding a plurality of functional blocks constituting the target node and a scenario set for each of the plurality of functional blocks. . Thereby, a node having a more flexible configuration can be created.
- one aspect of the present invention can be described as an invention of a node creation method as described below, in addition to being described as an invention of a control node and a node creation system as described above.
- This is substantially the same invention only in different categories, and has the same operations and effects.
- a plurality of functional blocks providing a predetermined function are arranged in combination, and the processing procedure of each functional block or all functional blocks is defined for each arranged functional block.
- a creation instruction receiving step for receiving a creation instruction for creating the target node, including identification information of the target node; identification information of the target node; identification information of a plurality of functional blocks constituting the target node; Configuration table storage that stores the target node configuration table that associates the scenario set for each of the plurality of functional blocks
- Target node identification information transmission step for transmitting target node identification information included in the creation instruction, and identification of the target node transmitted in the target node configuration table as a response based on transmission in the target node identification information transmission step
- a configuration information receiving step for receiving target node configuration information including identification information and scenarios of a plurality of functional blocks associated with the information, and a component element storage node for storing the functional block or a base node for arranging the target node
- a placement instruction transmitting step for sending a placement instruction for placing the plurality of functional blocks in combination, including identification information of the plurality of functional blocks included in the target node configuration information, and a plurality of placements based on the placement instruction Setting to set
- the node creation method arranges a plurality of functional blocks that provide a predetermined function, and the processing procedure of each functional block or all functional blocks is defined for each arranged functional block.
- each functional block executes processing according to the set scenario and creates a target node that provides a specific function as the entire function block, identification information of the target node, and the target
- a configuration table storage node for storing a target node configuration table in which identification information of a plurality of functional blocks constituting a node and a scenario set in each of the plurality of functional blocks are associated, and a component storage node for storing the functional blocks
- a node creation method executed by a node creation system including: A creation instruction receiving step for receiving a creation instruction for creating the target node including other information, and a control node for sending the identification information of the target node included in the creation instruction to the configuration table storage node An identification information transmission step; a destination node identification information reception step in which the configuration table storage node receive
- the placement step and the control node transmit a setting instruction for setting a scenario included in the target node configuration information to a plurality of functional blocks arranged based on the placement instruction, and based on the transmission of the setting instruction A setting instruction transmission step in which a target node is created.
- the node creation method arranges a plurality of functional blocks that provide a predetermined function, and the processing procedure of each functional block or all functional blocks is defined for each arranged functional block.
- each functional block executes processing according to the set scenario and creates a target node that provides a specific function as the entire function block, identification information of the target node, and the target
- a configuration table storage node for storing a target node configuration table in which identification information of a plurality of functional blocks constituting a node and a scenario set in each of the plurality of functional blocks are associated, and a base node on which the target node is arranged
- a creation instruction receiving step for receiving a creation instruction for creating the target node, and transmission of target node identification information for the control node to transmit identification information of the target node included in the creation instruction to the configuration table storage node
- a target node identification information receiving step in which the configuration table storage node receives the identification information of the target node transmitted in the target node identification information transmission step; and the configuration table storage node sends the target node configuration table to the control node.
- a configuration information transmitting step for transmitting target node configuration information including identification information and scenarios of a plurality of functional blocks associated with the target node identification information received in the target node identification information receiving step, and a control node
- the configuration information receiving step for receiving the node configuration information and the control node
- the placement instruction sending step for sending the placement instruction for placing the plurality of functional blocks in combination, including the identification information of the plurality of functional blocks included in the target node configuration information
- the placement instruction sending step A placement instruction receiving step for receiving the sent placement instruction, a placement step for placing the functional block corresponding to the identification information of the plurality of functional blocks included in the placement instruction, and a control node based on the placement instruction
- a setting instruction transmission step for transmitting a setting instruction for setting a scenario included in the target node configuration information to a plurality of functional blocks arranged in a manner, and generating a target node based on the transmission of the setting instruction; ,including.
- FIG. 1 is a system configuration diagram of a node creation system including a control node according to an embodiment of the present invention. It is a figure which shows the hardware constitutions of the management node which concerns on embodiment of this invention, a control node, a structure table storage node, a component storage node, and a base node. It is the figure which showed the structural example of the functional block which comprises a P-GW node. It is a figure which shows the example of a scenario set to the functional block which comprises a P-GW node. It is a figure which shows the example of a packet header transmitted / received in the process in a P-GW node. It is a sequence diagram which shows the example of a process performed between the functional blocks in a P-GW node.
- FIG. 1 is a system configuration diagram of a node creation system 1 including a Controller 3 (control node) according to an embodiment of the present invention.
- the node creation system 1 includes Admin / Orchestrator 2 (management node), Controller 3, CookBook 4 (configuration table storage node), Repository 5 (component storage node), and Platform 6 (base node). Consists of. Admin / Orchestrator 2 and Controller 3, Controller 3 and CookBook 4, Controller 3 and Repository 5, Controller 3 and Platform 6 are configured to be able to communicate with each other via a network or the like.
- the Repository 5 and the Platform 6 may also be configured to communicate with each other via a network or the like.
- FIG. 2 is a diagram illustrating an example of the hardware configuration of each of Admin / Orchestrator 2, Controller 3, CookBook 4, and Repository 5.
- each of Admin / Orchestrator 2, Controller 3, CookBook 4, and Repository 5 shown in FIG. 1 is physically CPU 10, RAM 11 and ROM 12, which are main storage devices, input / output device 13 such as a display, and communication.
- the computer system includes a module 14 and an auxiliary storage device 15.
- each functional block which will be described later, of Admin / Orchestrator 2, Controller 3, CookBook 4 and Repository 5 shown in FIG. 1 are read out by loading predetermined computer software on the hardware such as CPU 10 and RAM 11 shown in FIG. This is realized by operating the input / output device 13, the communication module 14, and the auxiliary storage device 15 under the control of the above, and reading and writing data in the RAM 11.
- the node creation system 1 creates a target node that provides a specific function by linking Admin / Orchestrator 2, Controller 3, CookBook 4, and Repository 5. Specifically, a plurality of function blocks (FB, Function Block) providing a predetermined function are arranged in combination, and a scenario in which the processing procedure of each FB or all FBs is defined is set for each arranged FB. Thus, each FB executes processing according to the set scenario, and creates a target node that provides a specific function as the entire FB.
- FB Function Block
- FIG. 3 is a diagram showing a configuration example of the FB constituting the P-GW node 100 which is a specific example of the target node.
- the P-GW node 100 includes a transmission / reception management FB 101, a bearer management FB 102, a DPI (Deep Packet Inspection) packet management (FB 103) management, and a billing management FB 104. Is done.
- the transmission / reception management FB 101 and bearer management FB 102, the transmission / reception management FB 101 and DPI management FB 103, the transmission / reception management FB 101 and the charge management FB 104 are configured in a star shape so that they can communicate with each other via a network or the like.
- the network configuration is not limited to the star type, and may be configured with other network configurations such as a ring type.
- the P-GW node 100 is an example of a target node in which the transmission / reception management FB 101, bearer management FB 102, DPI management FB 103, and billing management FB 104 are combined by the node creation system 1.
- the FB is a minimum unit constituting the target node (that is, the target node is a set of a plurality of FBs), provides a predetermined function, and has a common interface (input In, output Out, management Mng).
- the transmission / reception management FB 101 provides a transmission / reception management function in the P-GW
- the bearer management FB 102 provides a bearer management function in the P-GW
- the DPI management FB 103 provides a DPI management function in the P-GW
- the charge management FB 104 provides a charge management function in the P-GW.
- one FB is configured by one VM (Virtual Machine), and the FBs in the target node are L2 coupled.
- the nodes are L3 coupled. As shown in FIG. 3, each node has one GW (Gateway).
- FIG. 4 is a diagram showing a scenario example (C-Plane processing) set in the FB constituting the P-GW node 100.
- a uniform scenario is set for all the FBs in the P-GW node 100 (stored inside).
- the scenario is defined in a flowchart format in which processing units (reference numerals 110 to 123) in which processing in each FB is defined are connected.
- the processing unit 110 illustrated in FIG. 4 indicates that the transmission / reception management FB 101 performs the header analysis processing, and the processing moves to the processing unit 111.
- the node creation system 1 sets the scenario shown in FIG. 4 in each of the arranged transmission / reception management FB 101, bearer management FB 102, DPI management FB 103, and billing management FB 104, so that each FB performs processing according to the set scenario.
- the P-GW node 100 is executed to provide the P-GW function as the entire FB.
- FIG. 5 is a diagram showing an example of a packet header transmitted / received in processing within the P-GW node 100.
- the packet header is composed of a scenario number (number), a transmission source, and SF (Scenario Field).
- the scenario number is a unique number that is incremented each time the processing unit is moved.
- the transmission source is identification information of the transmission source FB.
- the SF stores values output by some processing units.
- the packet header shown in FIG. 5 shows the final packet header when the scenario shown in FIG. 4 is executed in the P-GW node 100. When the scenario is executed, each processing unit first checks the transmission source, then writes the processing result in the output part of the SF, and then transmits to the next destination according to the scenario.
- FIG. 6 is a sequence diagram showing an example of processing executed between FBs in the P-GW node 100.
- C-Plane processing will be described.
- the C-Plane packet is received by the transmission / reception management FB 101 (S100).
- header analysis GTP (GPRS Tunneling Protocol) -c, PMIP (Proxy MobileIP)
- S101 header analysis
- PMIP Proxy MobileIP
- header transmission is performed by the transmission / reception management FB 101 to the bearer management FB 102 (S102).
- header analysis QCI (QoS Class Identifier) determination
- the QCI setting is transmitted from the bearer management FB 102 to the transmission / reception management FB 101 (S104).
- the transmission / reception management FB 101 performs header transfer to the DPI management FB 103 (S105).
- the DPI management FB 103 performs header analysis (DPI existence determination) (S106).
- the DPI management FB 103 transmits the DPI presence / absence setting to the transmission / reception management FB 101 (S107).
- header transmission is performed to the accounting management FB 104 by the transmission / reception management FB 101 (S108).
- header analysis determination of charge / non-charge
- the billing management FB 104 transmits a billing presence / absence setting to the transmission / reception management FB 101 (S110).
- the transmission / reception management FB 101 transmits a U-Plane transmission permission to the communication source node.
- the transmission / reception management FB 101 receives a U-Plane packet (S120).
- header analysis GTP
- the transmission / reception management FB 101 transfers the packet to the DPI management FB 103 (S122).
- the packet is recorded in the buffer by the DPI management FB 103 (S123).
- the DPI management FB 103 transmits a recording completion notification to the transmission / reception management FB 101 (S124).
- the transmission / reception management FB 101 transfers the packet to the charge management FB 104 (S125).
- billing processing is performed by the billing management FB 104 (S126).
- the charging management FB 104 transmits a charging completion notification to the transmission / reception management FB 101 (S127).
- the transmission / reception management FB 101 transfers the packet to the Internet (S128).
- Fig. 7 is a functional block diagram of Admin / Orchestrator 2. As shown in FIG. 7, Admin / Orchestrator 2 includes a creation instruction unit 20, a change instruction unit 21, and a configuration information registration instruction unit 22.
- the creation instruction unit 20 issues a node creation instruction to the Controller 3. Specifically, the creation instructing unit 20 instructs the controller 3 to identify target node identification information (target node ID, node name, etc.) and a creation location (physical position or logical) for creating the target node. A creation instruction (creation instruction information) for creating the target node is transmitted, including the location and Platform 6 identification information).
- target node identification information target node ID, node name, etc.
- a creation location physical position or logical
- the change instruction unit 21 issues a node change instruction to the Controller 3.
- the change instruction unit 21 includes, for Controller 3, the identification information of the created target node, the creation location where the created target node is created, and the identification information of the target node after the change. Then, a change instruction (change instruction information) for changing the created target node to the target node after the change is transmitted.
- the change instructing unit 21 adds and deletes FBs constituting the target node by instructing node change.
- the configuration information registration instruction unit 22 instructs the controller 3 to register a target node configuration table described later. Specifically, the configuration information registration instruction unit 22 instructs the controller 3 to register (add / delete) the target node configuration table including the target node configuration table or partial data of the target node configuration table. (Registration instruction information) is transmitted.
- the configuration information registration instruction unit 22 may instruct Controller 3 to register an FB. Specifically, the configuration information registration instruction unit 22 transmits to the Controller 3 a registration instruction for registering (adding / deleting) an FB including identification information of the FB to be newly registered or the FB to be deleted.
- the Admin / Orchestrator 2 may autonomously transmit the above-described creation instruction, change instruction, or registration instruction to the Controller 3 based on an action (processing content) set in advance by the user.
- Fig. 8 is a functional block diagram of Controller 3.
- the Controller 3 includes a creation instruction receiving unit 300 (creation instruction receiving unit), a creation possibility determination unit 301, a configuration information acquisition unit 302 (target node identification information transmission unit, configuration information reception unit), Usage area securing availability determination unit 303, arrangement instruction unit 304 (arrangement instruction transmission unit), scenario acquisition unit 305, setting instruction unit 306 (setting instruction transmission unit), and situation table storage unit 307 (situation table storage unit)
- a change instruction receiving unit 308 change instruction receiving unit
- a change instruction unit 309 target node changing unit
- a configuration information registration instruction receiving unit 310
- a configuration information registration instruction unit 311 a configuration information registration instruction receiving unit 311
- the creation instruction receiving unit 300 receives a creation instruction from Admin / Orchestrator 2.
- the creation possibility determination unit 301 determines that the destination node identified by the identification information of the destination node included in the creation instruction is the CookBook 4 purpose described later. It is inquired whether or not it is stored in the node configuration table, that is, whether or not the target node can be created. Then, the creation possibility determination unit 301 receives a creation possibility result from CookBook 4 as a response based on the inquiry, and determines whether creation is possible. When it is determined that the creation is possible by the creation possibility determination unit 301, the process proceeds to a configuration information acquisition unit 302 described later. On the other hand, when it is determined that the creation is impossible by the creation possibility determination unit 301, the Admin / Orchestrator 2 is notified via the creation instruction receiving unit 300 that the creation is impossible.
- the identification information of the target node included in the creation instruction received by the creation instruction receiving unit 300 is transmitted to CookBook4, and the response based on the transmission corresponds to the identification information of the target node transmitted in the target node configuration table of CookBook4.
- a plurality of attached FB identification information, Repository 5 identification information, a scenario (or a pointer to a scenario stored in Repository 5), a memory capacity, and target node configuration information including a creation time are received. Details of the target node configuration table will be described later.
- the use area securing availability determination unit 303 confirms the creation location included in the creation instruction received by the creation instruction reception unit 300. In the present embodiment, it is assumed that Platform 6 is designated as the creation location. Next, the use area reservation availability determination unit 303 makes a use area reservation permission inquiry about whether or not the use area for creating the target node can be reserved for the designated Platform 6. When making the inquiry, the use area reservation availability determination unit 303 instructs the platform 6 to store the memory capacity included in the target node configuration information received by the configuration information acquisition unit 302 or the use area when the use area can be reserved. Send instructions to reserve or secure.
- the use area reservation availability determination unit 303 receives the use area reservation permission from Platform 6 as a response based on the inquiry, and determines whether or not the use area reservation is possible. When it is determined that the use area can be secured, the use area reservation availability determination unit 303 transmits an instruction to secure the use area to the Platform 6, and proceeds to the processing of the arrangement instruction unit 304 described later. If the use area securing availability determination unit 303 determines that the use area can be secured, the use area securing availability determination unit 303 may notify the Admin / Orchestrator 2 that the use area can be secured via the creation instruction receiving unit 300. .
- the administration instruction receiving unit 300 notifies the Admin / Orchestrator 2 that the use area cannot be secured.
- the use area reservation determination unit 303 transmits an instruction to secure the area, and when the use area can be secured on the Platform 6, the Platform 6 secures the area. Then, the use area securing availability determination unit 303 receives a creation possible notification indicating that the area has been secured instead of the use area securing availability, determines that the use area can be secured and has actually been secured, and an arrangement instruction described later Proceed to the processing of unit 304.
- the placement instruction unit 304 identifies the identification information of the Repository 5 included in the target node configuration information received by the configuration information acquisition unit 302 when the use region reservation availability determination unit 303 determines that the use region can be secured or secured.
- the identification information of a plurality of FBs included in the target node configuration information received by the configuration information acquisition unit 302 and the creation location (Platform 6) included in the creation instruction received by the creation instruction reception unit 300 are stored in the Repository 5
- an arrangement instruction for arranging the plurality of FBs in combination is transmitted.
- the arrangement instruction unit 304 displays the Platform 6 that is the creation location included in the creation instruction received by the creation instruction reception unit 300.
- an arrangement instruction for arranging the plurality of FBs in combination including the identification information of the plurality of FBs included in the target node configuration information received by the configuration information acquisition unit 302 may be transmitted.
- the placement instruction unit 304 may receive a placement completion notification indicating that the placement based on the placement instruction is completed from the placed target node.
- the placement completion notification includes position information of a plurality of FBs that constitute the placed target node, and the Controller 3 identifies a plurality of FBs that constitute the placed target node based on the position information. can do.
- the scenario acquisition unit 305 transmits an arrangement instruction by the arrangement instruction unit 304.
- an arrangement completion notification is received by the arrangement instruction unit 304
- a scenario acquisition request indicated by the pointer is transmitted to the Repository 5.
- the scenario acquisition unit 305 receives a scenario from the Repository 5 as a response based on the transmission.
- the setting instruction unit 306 is a setting instruction for setting a scenario included in the target node configuration information or a scenario received by the scenario acquisition unit 305 for a plurality of FBs arranged based on the arrangement instruction by the arrangement instruction unit 304 Send.
- a destination node is created on Platform 6 based on the transmission of the setting instruction.
- the setting instruction unit 306 receives a placement instruction from the placement instruction unit 304, receives a placement completion notification from the placement instruction unit 304, or receives a scenario from the scenario acquisition unit 305.
- a setting instruction for setting the scenario included in the target node configuration information or the scenario received by the scenario acquisition unit 305 is transmitted to the plurality of FBs arranged based on the arrangement instruction by the arrangement instruction unit 304.
- the setting instruction unit 306 receives a scenario update completion notification that the scenario setting is completed from the target node, and sends the destination node of the target node to the Admin / Orchestrator 2 via the creation instruction receiving unit 300. Send a creation completion notification to the effect that creation has been completed.
- the status table storage unit 307 includes identification information of a created target node (currently operating), a creation location of the target node, a node name of the target node, and a plurality of FBs ( Information)) and a target node situation table in which scenarios set in the plurality of FBs are associated with each other.
- the information regarding the plurality of FBs constituting the target node may include position information of the plurality of FBs.
- FIG. 9 is a diagram illustrating a table example of the target node situation table stored by the situation table storage unit 307.
- the change instruction receiving unit 308 receives the change instruction from Admin / Orchestrator 2.
- the change instruction unit 309 includes a plurality of destination nodes in the target node situation table stored by the situation table storage unit 307 and associated with the identification information of the created target nodes included in the change instruction received by the change instruction receiver 308.
- the scenario is associated with the changed target node identification information included in the change instruction.
- target node configuration information including a certain post-change scenario and controlling the setting instruction unit 306, based on the processing of the setting instruction unit 306, a plurality of FBs corresponding to the acquired information about the plurality of FBs Then, a setting instruction for setting the post-change scenario is transmitted. Based on the transmission of the setting instruction, the created target node is changed to the target node after the change.
- the change instruction unit 309 acquires a pre-change scenario that is a scenario associated with the identification information of the created target node included in the change instruction in the target node status table, and determines the pre-change scenario and the post-change scenario. By comparing, a difference between a plurality of FBs configuring the created target node and a plurality of FBs configuring the target node after the change is determined, and a plurality of configuring the created target node based on the determined difference The FB may be changed.
- the change instruction unit 309 logically deletes the FB by updating the scenario for all the FBs in the target node, and then physically (See the sequence diagram of FIG. 15).
- the FB is created, and then the scenario is updated for all the FBs in the target node (see the sequence diagram of FIG. 16).
- the configuration information registration instruction receiving unit 310 receives the target node configuration table or the FB registration instruction.
- the configuration information registration instruction unit 311 transmits the registration instruction received by the configuration information registration instruction reception unit 310 to the CookBook 4 or Repository 5 to be registered.
- FIG. 10 is a functional block diagram of CookBook4. As shown in FIG. 10, the CookBook 4 includes a target node configuration table storage unit 40, a creation availability response unit 41, a configuration information response unit 42 (target node identification information reception unit, configuration information transmission unit), and a configuration information registration unit. 43.
- the target node configuration table storage unit 40 stores the target node configuration table.
- FIG. 11 is a diagram illustrating a table example of the target node configuration table stored by the target node configuration table storage unit 40.
- the target node configuration table includes the target node identification information, the identification information of a plurality of FBs constituting the target node, the identification information of the Repository 5 in which the FB is stored, and the plurality of FBs.
- the target node configuration information including the scenario set in (or a pointer to the scenario stored in the Repository 5), the memory capacity, and the availability of creation is received.
- the target node configuration table may further associate the creation time of the target node and the like.
- the target node configuration table storage unit 40 periodically communicates with the Repository 5 to determine whether the target node can be created (whether the corresponding FB is held in the Repository 5). Store in table.
- the creation possibility response unit 41 receives the inquiry about creation possibility including the identification information of the target node transmitted from the Controller 3, and the target node in which the identification information of the target node is stored by the target node configuration table storage unit 40 It is determined whether or not it is included in the configuration table, and a determination result is returned to the Controller 3 as a result of whether or not it can be created.
- the configuration information response unit 42 receives the identification information of the target node from the Controller 3, and in the target node configuration table stored by the target node configuration table storage unit 40, a plurality of pieces of information associated with the received identification information of the target node
- the target node configuration information including the FB identification information, the Repository 5 identification information, the scenario (or a pointer to the scenario stored in the Repository 5), the memory capacity, and the creation time is returned to the Controller 3.
- the configuration information registration unit 43 receives the target node configuration table transmitted from the Controller 3, and registers the target node configuration table stored by the target node configuration table storage unit 40 based on the received target node configuration table.
- FIG. 12 is a functional block diagram of Repository 5.
- the Repository 5 includes an FB storage unit 50, a scenario storage unit 51, an arrangement instruction receiving unit 52 (arrangement instruction receiving unit, arrangement unit), a configuration information registration unit 53, and a scenario acquisition unit 54. Consists of including.
- the FB storage unit 50 stores the FB.
- the scenario storage unit 51 stores a scenario.
- the placement instruction reception unit 52 receives the placement instruction transmitted from the Controller 3, acquires the FB (or a copy of the FB) corresponding to the identification information of the plurality of FBs included in the placement instruction from the FB storage unit 50, and places the placement instruction Create the target node by placing it in the creation location included in.
- the placement instruction receiving unit 52 may send a placement instruction to the Platform 6 including the FB in order to direct the actual placement to the Platform 6.
- the placement instruction receiving unit 52 receives the FB copy instruction transmitted from the Platform 6 and requesting the FB copy including the FB identification information
- the FB copy corresponding to the FB identification information is stored in the FB. It may be acquired from the unit 50 and a copy of the acquired FB may be returned to the Platform 6.
- the configuration information registration unit 53 receives the FB or scenario transmitted from the Controller 3 and registers it by storing it in the FB storage unit 50 or the scenario storage unit 51.
- the scenario acquisition unit 54 receives the scenario acquisition request transmitted from the Controller 3, acquires the scenario indicated by the scenario pointer included in the request from the scenario storage unit 51, and returns it to the Controller 3.
- FIG. 13 is a functional block diagram of Platform 6. As illustrated in FIG. 13, the Platform 6 includes a use area securing availability response unit 60, an arrangement unit 61 (arrangement instruction receiving unit, arrangement unit), a scenario setting unit 62, and a scenario change unit 63.
- the Platform 6 includes a use area securing availability response unit 60, an arrangement unit 61 (arrangement instruction receiving unit, arrangement unit), a scenario setting unit 62, and a scenario change unit 63.
- the use area reservation availability response unit 60 receives the use area reservation availability inquiry transmitted from the Controller 3, and determines whether the use area can be reserved on the Platform 6 based on the memory capacity included in the use area reservation availability inquiry. Judgment is made, and the judgment result is returned to Controller 3 as availability of use area availability. Note that if the use area reservation possibility inquiry includes an instruction to reserve or secure the use area when the use area can be secured, the use area is reserved according to the instruction.
- the placement unit 61 receives the placement instruction transmitted from the Repository 5 and places the FB included in the placement instruction on the Platform 6 based on the placement instruction. In addition, the placement unit 61 receives the placement instruction transmitted from the Controller 3, and transmits the FB corresponding to the identification information of the plurality of FBs included in the placement instruction to the Repository 5 as described above. It may be acquired from Repository 5 and arranged.
- the scenario setting unit 62 receives the placement instruction transmitted from the Controller 3, and sets the scenario included in the setting instruction to the corresponding FB.
- the scenario changing unit 63 receives the setting instruction for setting the post-change scenario transmitted from the Controller 3, and sets the post-change scenario included in the setting instruction to the corresponding FB.
- a node creation instruction is transmitted from the Admin / Orchestrator 2 to the Controller 3 (S1).
- the controller 3 makes an inquiry about whether or not a node can be created to the CookBook 4 (S2).
- the cook book 4 notifies the controller 3 whether or not it can be created (S3).
- the controller 3 sends a node configuration information request to the CookBook 4 (S4).
- the node configuration information is notified to Controller 3 by CookBook 4 (S5).
- the node creation location is confirmed by the Controller 3 (S6).
- the controller 3 makes an inquiry about whether or not to secure the use area to the Platform 6 (S7).
- the platform 6 notifies the controller 3 whether or not to secure the use area (S8).
- the Controller 3 confirms the Repository 5 in which the FB is stored (S9).
- the controller 3 transmits an FB copy instruction to the Repository 5 (S10).
- the FB copy is transmitted to the Platform 6 by the Repository 5 (S11).
- the platform 6 transmits an FB copy completion notification to the controller 3 (S12).
- a scenario acquisition instruction is transmitted from the Controller 3 to the Repository 5 (S13).
- the scenario is notified to the Controller 3 by the Repository 5 (S14).
- the controller 3 edits and confirms the scenario (S15).
- the controller 3 instructs the scenario 6 to update the scenario (S16).
- the platform 6 transmits a scenario update completion notification to the controller 3 (S17).
- the controller 3 transmits a node creation completion notification to the Admin / Orchestrator 2 (S18).
- S10 and S11 may be replaced with the following processing. That is, following S9, the controller 3 transmits an FB copy instruction to the Platform 6. Next, an FB copy instruction is transmitted to the Repository 5 by the Platform 6. Next, the FB copy is transmitted to the Platform 6 by the Repository 5.
- a node change instruction is transmitted from the Admin / Orchestrator 2 to the Controller 3 (S30).
- the controller 3 makes an inquiry about whether or not a node can be created to the CookBook 4 (S31).
- the cook book 4 notifies the controller 3 whether or not it can be created (S32).
- the controller 3 sends a node configuration information request to the CookBook 4 (S33).
- the node configuration information is notified to Controller 3 by CookBook 4 (S34).
- the scenario is edited and confirmed by Controller 3 (S35).
- the controller 3 instructs the platform 6 to update the scenario (S36).
- the platform 6 sends a scenario update completion notification to the Controller 3 (S37).
- the controller 3 transmits an FB deletion instruction to the platform 6 (S38).
- the platform 6 sends a deletion completion notification to the controller 3 (S39).
- the controller 3 sends a node change completion notification to the Admin / Orchestrator 2 (S40).
- the Admin / Orchestrator 2 sends a node creation instruction to the Controller 3 (S50).
- the controller 3 makes an inquiry about whether or not a node can be created to the CookBook 4 (S51).
- the cook book 4 notifies the controller 3 whether or not it can be created (S52).
- the controller 3 makes a node configuration information request to the CookBook 4 (S53).
- the node configuration information is notified to the Controller 3 by the CookBook 4 (S54).
- the controller 3 makes an inquiry about whether or not the use area can be secured to the platform 6 (S55).
- the platform 6 notifies the controller 3 whether or not a use area can be secured (S56).
- the Controller 3 confirms the Repository 5 in which the FB is stored (S57).
- the FB copy instruction is transmitted from the Controller 3 to the Repository 5 (S57).
- the FB copy is transmitted to the Platform 6 by the Repository 5 (S59).
- the platform 6 transmits an FB copy completion notification to the controller 3 (S60).
- the scenario is edited and confirmed by the Controller 3 (S61).
- the controller 3 instructs the scenario 6 to update the scenario (S62).
- the platform 6 sends a scenario update completion notification to the controller 3 (S63).
- the controller 3 transmits a node change completion notification to the Admin / Orchestrator 2 (S64).
- S58 and S59 may be replaced with the following processing. That is, following S57, the controller 3 transmits an FB copy instruction to the Platform 6. Next, an FB copy instruction is transmitted to the Repository 5 by the Platform 6. Next, the FB copy is transmitted to the Platform 6 by the Repository 5.
- the creation instruction receiving unit 300 receives a creation instruction for creating a target node that provides a specific function.
- the configuration information acquisition unit 302 receives information on a plurality of FBs constituting the target node and a scenario in which processing procedures for each of the plurality of FBs are defined.
- the placement instruction unit 304 transmits a placement instruction for placing a plurality of FBs constituting the target node in combination.
- the setting instruction unit 306 transmits a setting instruction for setting a scenario to a plurality of FBs arranged based on the arrangement instruction, and creates a target node based on the transmission of the setting instruction.
- a plurality of FBs are arranged in combination, and a scenario is set for each arranged FB, so that each FB executes a process according to the set scenario, and the FB as a whole has a specific function.
- the configuration contents and processing contents of the target node desired to be created can be specified in the target node configuration table by information regarding a plurality of FBs constituting the target node and a scenario set for each of the plurality of FBs.
- a node having a more flexible configuration can be created.
- the creation instruction further includes the identification information of Platform 6
- the placement instruction further includes the identification information of Platform 6 included in the creation instruction, and a plurality of FBs are combined and placed on the Platform 6 May be indicated.
- a situation table storage unit that stores a destination node situation table in which identification information of a created destination node and information on a plurality of FBs constituting the created destination node are associated with each other 307, a change instruction for receiving a change instruction to change the created target node to the changed target node, including the created target node identification information and the changed target node identification information
- the change instruction Receiving the target node configuration information including the post-change scenario that is a scenario associated with the target node identification information after the change included in 6 is a change instruction unit 309 that transmits a setting instruction for setting a post-change scenario to a plurality of FBs corresponding to the acquired information on the plurality of FBs.
- a change instructing unit 309 may be further provided, in which the created target node is changed to the target node after the change.
- the target node status table further associates the scenario set for each of the plurality of FBs constituting the created target node
- the change instruction unit 309 further includes the target node status table.
- the scenario before the change that is the scenario associated with the identification information of the created target node included in the change instruction is acquired, and the created target node is configured by comparing the pre-change scenario with the post-change scenario. It is also possible to determine a difference between a plurality of FBs to be created and a plurality of FBs constituting the target node after the change, and to change a plurality of FBs constituting the created target node based on the determined difference.
- the created target node in order to change the created target node to a desired target node, for example, it is reliably determined which FB should be changed among a plurality of FBs constituting the created target node. be able to. As a result, the created target node can be easily and more reliably changed according to the desired target node.
- the target node can be created by linking the Controller 3, CookBook 4, and Repository 5. That is, a plurality of FBs are arranged in combination, and a scenario is set for each arranged FB, so that each FB executes a process according to the set scenario and provides a specific function as the entire FB Nodes can be created. Then, the configuration contents and processing contents of the target node desired to be created can be specified in the target node configuration table by information regarding a plurality of FBs constituting the target node and a scenario set for each of the plurality of FBs. Thereby, a node having a more flexible configuration can be created.
- the target node can be created by linking the Controller 3, CookBook 4, and Platform 6. That is, a plurality of FBs are arranged in combination, and a scenario is set for each arranged FB, so that each FB executes a process according to the set scenario and provides a specific function as the entire FB Nodes can be created. Then, the configuration contents and processing contents of the target node desired to be created can be specified in the target node configuration table by information regarding a plurality of FBs constituting the target node and a scenario set for each of the plurality of FBs. Thereby, a node having a more flexible configuration can be created.
- the node creation system 1 of the present embodiment it is possible to construct a system that enables a core node configuration specialized for services (voice, M2M, etc.). Further, it is possible to construct a system in which new node functions can be easily added and deleted using FBs and scenarios held by each FB. In addition, the FBs and scenarios in the target node created by a plurality of FBs can be dynamically rearranged using the components Controller 3, CookBook 4, and Repository 5.
- Creation instruction reception unit 301 ... Creation possibility determination , 302 ... Configuration information acquisition unit, 303 ... Usage area securing availability determination unit, 304 ... Placement instruction unit, 305 ... Scenario acquisition unit, 306 ... Setting instruction unit, 307 ... Situation table storage unit, 308 ... Change instruction reception unit, 09 ... change instruction unit, 310 ... configuration information registration instruction reception unit, 311 ... configuration information registration instruction unit.
Abstract
Description
Claims (9)
- 所定の機能を提供する機能ブロックを複数組み合わせて配置し、配置された各機能ブロックに対し、各機能ブロック又は全機能ブロックの処理手順が規定されたシナリオを設定することで、設定されたシナリオに従って各機能ブロックが処理を実行し、機能ブロック全体として特定の機能を提供する目的ノードを作成する制御ノードであって、
目的ノードの識別情報を含む、当該目的ノードを作成する旨の作成指示を受信する作成指示受信手段と、
目的ノードの識別情報と、当該目的ノードを構成する複数の機能ブロックの識別情報と、当該複数の機能ブロックそれぞれに設定されるシナリオとを対応付けた目的ノード構成表を格納する構成表格納ノードに対し、作成指示に含まれる目的ノードの識別情報を送信する目的ノード識別情報送信手段と、
前記目的ノード識別情報送信手段による送信に基づく応答として、目的ノード構成表において送信した目的ノードの識別情報に対応付けられた複数の機能ブロックの識別情報及びシナリオを含む目的ノード構成情報を受信する構成情報受信手段と、
機能ブロックを格納する構成要素格納ノード又は目的ノードを配置する基盤ノードに対し、目的ノード構成情報に含まれる複数の機能ブロックの識別情報を含む、当該複数の機能ブロックを組み合わせて配置する旨の配置指示を送信する配置指示送信手段と、
配置指示に基づいて配置された複数の機能ブロックに対し、目的ノード構成情報に含まれるシナリオを設定する旨の設定指示を送信する設定指示送信手段であって、当該設定指示の送信に基づいて目的ノードが作成される、設定指示送信手段と、
を備える制御ノード。 - 作成指示は、基盤ノードの識別情報をさらに含み、
配置指示は、作成指示に含まれる基盤ノードの識別情報をさらに含み、複数の機能ブロックを組み合わせて当該基盤ノードに配置する旨の指示を示す、
請求項1に記載の制御ノード。 - 作成済みの目的ノードの識別情報と、当該作成済みの目的ノードを構成する複数の機能ブロックに関する情報とが対応付けられた目的ノード状況表を格納する状況表格納手段と、
作成済みの目的ノードの識別情報と、変更後の目的ノードの識別情報とを含む、当該作成済みの目的ノードを当該変更後の目的ノードに変更する旨の変更指示を受信する変更指示受信手段と、
目的ノード状況表において変更指示に含まれる作成済みの目的ノードの識別情報に対応付けられた複数の機能ブロックに関する情報を取得し、前記構成情報受信手段を制御することで、変更指示に含まれる変更後の目的ノードの識別情報に対応付けられたシナリオである変更後シナリオを含む目的ノード構成情報を受信し、前記設定指示送信手段を制御することで、取得した複数の機能ブロックに関する情報に対応する複数の機能ブロックに対し、変更後シナリオを設定する旨の設定指示を送信する目的ノード変更手段であって、当該設定指示の送信に基づいて作成済みの目的ノードが変更後の目的ノードに変更される、目的ノード変更手段と、
をさらに備える請求項1又は2に記載の制御ノード。 - 目的ノード状況表では、作成済みの目的ノードを構成する複数の機能ブロックそれぞれに設定されたシナリオがさらに対応付けられ、
前記目的ノード変更手段は、さらに、目的ノード状況表において変更指示に含まれる作成済みの目的ノードの識別情報に対応付けられたシナリオである変更前シナリオを取得し、変更前シナリオと変更後シナリオとを比較することで、作成済みの目的ノードを構成する複数の機能ブロックと変更後の目的ノードを構成する複数の機能ブロックとの差分を判定し、判定した差分に基づいて作成済みの目的ノードを構成する複数の機能ブロックを変更する、
請求項3に記載の制御ノード。 - 所定の機能を提供する機能ブロックを複数組み合わせて配置し、配置された各機能ブロックに対し、各機能ブロック又は全機能ブロックの処理手順が規定されたシナリオを設定することで、設定されたシナリオに従って各機能ブロックが処理を実行し、機能ブロック全体として特定の機能を提供する目的ノードを作成する制御ノードと、目的ノードの識別情報と当該目的ノードを構成する複数の機能ブロックの識別情報と当該複数の機能ブロックそれぞれに設定されるシナリオとを対応付けた目的ノード構成表を格納する構成表格納ノードと、機能ブロックを格納する構成要素格納ノードとを含むノード作成システムであって、
制御ノードは、
目的ノードの識別情報を含む、当該目的ノードを作成する旨の作成指示を受信する作成指示受信手段と、
構成表格納ノードに対し、作成指示に含まれる目的ノードの識別情報を送信する目的ノード識別情報送信手段と、
目的ノード構成情報を受信する構成情報受信手段と、
構成要素格納ノードに対し、目的ノード構成情報に含まれる複数の機能ブロックの識別情報を含む、当該複数の機能ブロックを組み合わせて配置する旨の配置指示を送信する配置指示送信手段と、
配置指示に基づいて配置された複数の機能ブロックに対し、目的ノード構成情報に含まれるシナリオを設定する旨の設定指示を送信する設定指示送信手段であって、当該設定指示の送信に基づいて目的ノードが作成される、設定指示送信手段と、
を備え、
構成表格納ノードは、
前記目的ノード識別情報送信手段によって送信された目的ノードの識別情報を受信する目的ノード識別情報受信手段と、
制御ノードに対し、目的ノード構成表において前記目的ノード識別情報受信手段によって受信された目的ノードの識別情報に対応付けられた複数の機能ブロックの識別情報及びシナリオを含む目的ノード構成情報を送信する構成情報送信手段と、
を備え、
構成要素格納ノードは、
前記配置指示送信手段によって送信された配置指示を受信する配置指示受信手段と、
配置指示に含まれる複数の機能ブロックの識別情報に対応する格納された機能ブロックを配置する配置手段と、
を備える、
ノード作成システム。 - 所定の機能を提供する機能ブロックを複数組み合わせて配置し、配置された各機能ブロックに対し、各機能ブロック又は全機能ブロックの処理手順が規定されたシナリオを設定することで、設定されたシナリオに従って各機能ブロックが処理を実行し、機能ブロック全体として特定の機能を提供する目的ノードを作成する制御ノードと、目的ノードの識別情報と当該目的ノードを構成する複数の機能ブロックの識別情報と当該複数の機能ブロックそれぞれに設定されるシナリオとを対応付けた目的ノード構成表を格納する構成表格納ノードと、目的ノードを配置する基盤ノードとを含むノード作成システムであって、
制御ノードは、
目的ノードの識別情報を含む、当該目的ノードを作成する旨の作成指示を受信する作成指示受信手段と、
構成表格納ノードに対し、作成指示に含まれる目的ノードの識別情報を送信する目的ノード識別情報送信手段と、
目的ノード構成情報を受信する構成情報受信手段と、
目的ノードを配置する基盤ノードに対し、目的ノード構成情報に含まれる複数の機能ブロックの識別情報を含む、当該複数の機能ブロックを組み合わせて配置する旨の配置指示を送信する配置指示送信手段と、
配置指示に基づいて配置された複数の機能ブロックに対し、目的ノード構成情報に含まれるシナリオを設定する旨の設定指示を送信する設定指示送信手段であって、当該設定指示の送信に基づいて目的ノードが作成される、設定指示送信手段と、
を備え、
構成表格納ノードは、
前記目的ノード識別情報送信手段によって送信された目的ノードの識別情報を受信する目的ノード識別情報受信手段と、
制御ノードに対し、目的ノード構成表において前記目的ノード識別情報受信手段によって受信された目的ノードの識別情報に対応付けられた複数の機能ブロックの識別情報及びシナリオを含む目的ノード構成情報を送信する構成情報送信手段と、
を備え、
基盤ノードは、
前記配置指示送信手段によって送信された配置指示を受信する配置指示受信手段と、
配置指示に含まれる複数の機能ブロックの識別情報に対応する機能ブロックを配置する配置手段と、
を備える、
ノード作成システム。 - 所定の機能を提供する機能ブロックを複数組み合わせて配置し、配置された各機能ブロックに対し、各機能ブロック又は全機能ブロックの処理手順が規定されたシナリオを設定することで、設定されたシナリオに従って各機能ブロックが処理を実行し、機能ブロック全体として特定の機能を提供する目的ノードを作成する制御ノードにより実行されるノード作成方法であって、
目的ノードの識別情報を含む、当該目的ノードを作成する旨の作成指示を受信する作成指示受信ステップと、
目的ノードの識別情報と、当該目的ノードを構成する複数の機能ブロックの識別情報と、当該複数の機能ブロックそれぞれに設定されるシナリオとを対応付けた目的ノード構成表を格納する構成表格納ノードに対し、作成指示に含まれる目的ノードの識別情報を送信する目的ノード識別情報送信ステップと、
前記目的ノード識別情報送信ステップにおける送信に基づく応答として、目的ノード構成表において送信した目的ノードの識別情報に対応付けられた複数の機能ブロックの識別情報及びシナリオを含む目的ノード構成情報を受信する構成情報受信ステップと、
機能ブロックを格納する構成要素格納ノード又は目的ノードを配置する基盤ノードに対し、目的ノード構成情報に含まれる複数の機能ブロックの識別情報を含む、当該複数の機能ブロックを組み合わせて配置する旨の配置指示を送信する配置指示送信ステップと、
配置指示に基づいて配置された複数の機能ブロックに対し、目的ノード構成情報に含まれるシナリオを設定する旨の設定指示を送信する設定指示送信ステップであって、当該設定指示の送信に基づいて目的ノードが作成される、設定指示送信ステップと、
を含むノード作成方法。 - 所定の機能を提供する機能ブロックを複数組み合わせて配置し、配置された各機能ブロックに対し、各機能ブロック又は全機能ブロックの処理手順が規定されたシナリオを設定することで、設定されたシナリオに従って各機能ブロックが処理を実行し、機能ブロック全体として特定の機能を提供する目的ノードを作成する制御ノードと、目的ノードの識別情報と当該目的ノードを構成する複数の機能ブロックの識別情報と当該複数の機能ブロックそれぞれに設定されるシナリオとを対応付けた目的ノード構成表を格納する構成表格納ノードと、機能ブロックを格納する構成要素格納ノードとを含むノード作成システムにより実行されるノード作成方法であって、
制御ノードが、目的ノードの識別情報を含む、当該目的ノードを作成する旨の作成指示を受信する作成指示受信ステップと、
制御ノードが、構成表格納ノードに対し、作成指示に含まれる目的ノードの識別情報を送信する目的ノード識別情報送信ステップと、
構成表格納ノードが、前記目的ノード識別情報送信ステップにおいて送信された目的ノードの識別情報を受信する目的ノード識別情報受信ステップと、
構成表格納ノードが、制御ノードに対し、目的ノード構成表において前記目的ノード識別情報受信ステップにおいて受信された目的ノードの識別情報に対応付けられた複数の機能ブロックの識別情報及びシナリオを含む目的ノード構成情報を送信する構成情報送信ステップと、
制御ノードが、目的ノード構成情報を受信する構成情報受信ステップと、
制御ノードが、構成要素格納ノードに対し、目的ノード構成情報に含まれる複数の機能ブロックの識別情報を含む、当該複数の機能ブロックを組み合わせて配置する旨の配置指示を送信する配置指示送信ステップと、
構成要素格納ノードが、前記配置指示送信ステップにおいて送信された配置指示を受信する配置指示受信ステップと、
構成要素格納ノードが、配置指示に含まれる複数の機能ブロックの識別情報に対応する格納された機能ブロックを配置する配置ステップと、
制御ノードが、配置指示に基づいて配置された複数の機能ブロックに対し、目的ノード構成情報に含まれるシナリオを設定する旨の設定指示を送信し、当該設定指示の送信に基づいて目的ノードが作成される、設定指示送信ステップと、
を含むノード作成方法。 - 所定の機能を提供する機能ブロックを複数組み合わせて配置し、配置された各機能ブロックに対し、各機能ブロック又は全機能ブロックの処理手順が規定されたシナリオを設定することで、設定されたシナリオに従って各機能ブロックが処理を実行し、機能ブロック全体として特定の機能を提供する目的ノードを作成する制御ノードと、目的ノードの識別情報と当該目的ノードを構成する複数の機能ブロックの識別情報と当該複数の機能ブロックそれぞれに設定されるシナリオとを対応付けた目的ノード構成表を格納する構成表格納ノードと、目的ノードを配置する基盤ノードとを含むノード作成システムにより実行されるノード作成方法であって、
制御ノードが、目的ノードの識別情報を含む、当該目的ノードを作成する旨の作成指示を受信する作成指示受信ステップと、
制御ノードが、構成表格納ノードに対し、作成指示に含まれる目的ノードの識別情報を送信する目的ノード識別情報送信ステップと、
構成表格納ノードが、前記目的ノード識別情報送信ステップにおいて送信された目的ノードの識別情報を受信する目的ノード識別情報受信ステップと、
構成表格納ノードが、制御ノードに対し、目的ノード構成表において前記目的ノード識別情報受信ステップにおいて受信された目的ノードの識別情報に対応付けられた複数の機能ブロックの識別情報及びシナリオを含む目的ノード構成情報を送信する構成情報送信ステップと、
制御ノードが、目的ノード構成情報を受信する構成情報受信ステップと、
制御ノードが、基盤ノードに対し、目的ノード構成情報に含まれる複数の機能ブロックの識別情報を含む、当該複数の機能ブロックを組み合わせて配置する旨の配置指示を送信する配置指示送信ステップと、
基盤ノードが、前記配置指示送信ステップにおいて送信された配置指示を受信する配置指示受信ステップと、
基盤ノードが、配置指示に含まれる複数の機能ブロックの識別情報に対応する機能ブロックを配置する配置ステップと、
制御ノードが、配置指示に基づいて配置された複数の機能ブロックに対し、目的ノード構成情報に含まれるシナリオを設定する旨の設定指示を送信し、当該設定指示の送信に基づいて目的ノードが作成される、設定指示送信ステップと、
を含むノード作成方法。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP15819521.4A EP3169025A4 (en) | 2014-07-08 | 2015-06-29 | Control node, node creation system and node creation method |
JP2016532885A JP6232137B2 (ja) | 2014-07-08 | 2015-06-29 | 制御ノード、ノード作成システム及びノード作成方法 |
US15/318,400 US20170123847A1 (en) | 2014-07-08 | 2015-06-29 | Control node, node creation system and node creation method |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2014140937 | 2014-07-08 | ||
JP2014-140937 | 2014-07-08 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2016006491A1 true WO2016006491A1 (ja) | 2016-01-14 |
Family
ID=55064128
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2015/068719 WO2016006491A1 (ja) | 2014-07-08 | 2015-06-29 | 制御ノード、ノード作成システム及びノード作成方法 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20170123847A1 (ja) |
EP (1) | EP3169025A4 (ja) |
JP (1) | JP6232137B2 (ja) |
WO (1) | WO2016006491A1 (ja) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111866856B (zh) * | 2020-07-22 | 2023-08-25 | 青岛易来智能科技股份有限公司 | Mesh设备的控制方法和系统、存储介质及电子装置 |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH1097417A (ja) * | 1996-07-30 | 1998-04-14 | Toray Ind Inc | プログラム組立装置及び記憶媒体 |
JP2009049641A (ja) * | 2007-08-17 | 2009-03-05 | Nippon Telegr & Teleph Corp <Ntt> | メディアストリーム加工システム、メディアストリーム加工方法、コンポーネント実現装置 |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7426393B2 (en) * | 2001-11-19 | 2008-09-16 | Nokia Corporation | Method and system of identifying network services |
US20050289244A1 (en) * | 2004-06-28 | 2005-12-29 | Himansu Sahu | Method for service chaining in a communication network |
US8141090B1 (en) * | 2007-04-24 | 2012-03-20 | Hewlett-Packard Development Company, L.P. | Automated model-based provisioning of resources |
US8161479B2 (en) * | 2008-06-13 | 2012-04-17 | Microsoft Corporation | Synchronizing virtual machine and application life cycles |
US8601474B2 (en) * | 2011-10-14 | 2013-12-03 | International Business Machines Corporation | Resuming execution of an execution plan in a virtual machine |
CN103346980B (zh) * | 2013-07-02 | 2016-08-10 | 华为技术有限公司 | 一种业务调度方法、装置及网络设备 |
-
2015
- 2015-06-29 WO PCT/JP2015/068719 patent/WO2016006491A1/ja active Application Filing
- 2015-06-29 US US15/318,400 patent/US20170123847A1/en not_active Abandoned
- 2015-06-29 EP EP15819521.4A patent/EP3169025A4/en not_active Withdrawn
- 2015-06-29 JP JP2016532885A patent/JP6232137B2/ja active Active
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH1097417A (ja) * | 1996-07-30 | 1998-04-14 | Toray Ind Inc | プログラム組立装置及び記憶媒体 |
JP2009049641A (ja) * | 2007-08-17 | 2009-03-05 | Nippon Telegr & Teleph Corp <Ntt> | メディアストリーム加工システム、メディアストリーム加工方法、コンポーネント実現装置 |
Non-Patent Citations (2)
Title |
---|
KUNIHIKO TOMURA ET AL.: "Study of modular IP node architecture", IEICE TECHNICAL REPORT, vol. 103, no. 442, 13 November 2003 (2003-11-13), pages 59 - 62, XP008183306 * |
See also references of EP3169025A4 * |
Also Published As
Publication number | Publication date |
---|---|
EP3169025A1 (en) | 2017-05-17 |
JPWO2016006491A1 (ja) | 2017-04-27 |
EP3169025A4 (en) | 2017-12-06 |
US20170123847A1 (en) | 2017-05-04 |
JP6232137B2 (ja) | 2017-11-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP6855575B2 (ja) | ネットワーク間変更方法および装置、ならびに関連デバイス | |
RU2695990C1 (ru) | Система связи, базовая станция, способ связи и энергонезависимый компьютерно-читаемый носитель, хранящий программу | |
EP3836515B1 (en) | Communication method and communication device for reducing complexity in processing of service instances. | |
US11259344B2 (en) | Network architecture and information exchange method and apparatus | |
WO2016056321A1 (ja) | 基地局装置、端末装置、位置管理装置および制御方法 | |
CN105580328A (zh) | 无线通信网络的网关排布 | |
CN103813302A (zh) | 签约转移方法、装置及系统 | |
CN106664551B (zh) | 一种ip地址分配的方法和装置 | |
JP6982100B2 (ja) | Ipバージョンの選択 | |
US9491791B2 (en) | Communication apparatus, method of controlling the same, and non-transitory computer-readable storage medium | |
CN110365727A (zh) | 通信方法和相关装置 | |
CN102045691A (zh) | 获取物联网设备组别标识的方法及装置 | |
JP4009293B2 (ja) | 小規模ネットワーク間の接続確立方法及びシステム | |
JPWO2017169281A1 (ja) | 位置登録エリアリスト更新方法 | |
JPWO2017141810A1 (ja) | 伝送装置選択方法、ゲートウェイ選択方法及び通信システム | |
WO2012023214A1 (en) | Mediation server, communication device, and connecting method | |
JP6232137B2 (ja) | 制御ノード、ノード作成システム及びノード作成方法 | |
CN102316543A (zh) | 服务网关的重选方法、系统和设备 | |
JP5695514B2 (ja) | 通信制御装置および通信制御方法 | |
CN102781055A (zh) | 数据传输的方法、无线接入网设备和通信系统 | |
CN114915966A (zh) | 配置演进分组系统非接入层安全算法的方法及相关装置 | |
JP6496648B2 (ja) | 通信制御方法および通信システム | |
CN114902609B (zh) | 一种通信方法、设备、系统及存储介质 | |
CN103069917A (zh) | 用于建立数据路径、设备和通信系统的方法 | |
EP4290388A1 (en) | Network service management system and network service management method |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 15819521 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2016532885 Country of ref document: JP Kind code of ref document: A |
|
REEP | Request for entry into the european phase |
Ref document number: 2015819521 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2015819521 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15318400 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |