Management system, management method, and management program

Abstract

A management system 1 that manages network resources comprises: a channel management device 21 that, for every network slice creation order, generates an information sharing channel that corresponds to an identifier for the network slice; and a plurality of resource information sharing devices 22A, 22B that share necessary resource information between network domains via the information sharing channel during execution of the creation order.

Description

Technical Field

[0001] The present invention relates to a management system, a management method, and a management program.

Background Art

[0002] Conventionally, there is a management system for managing NW resources between a terminal and a server.

[0003] The management system includes a controller that manages NW resources for each network slice obtained by logically or physically dividing NW resources. For example, there is a controller that manages the NW resources of domain A. There is a controller that manages the NW resources of domain B. There is a controller that manages the connection gateway of domain C that connects domain A and domain B.

[0004] In addition, the management system includes an end-to-end controller that manages each controller in order to manage end-to-end communication between the terminal and the server. For example, there is an end-to-end controller that manages the controller of domain A, the controller of domain B, and the controller of domain C.

[0005] When generating a network slice between end-to-end, it is necessary for the end-to-end controller and the controller for each domain to cooperate to distribute information (for example, area information, bandwidth information, delay information) necessary for network slice management to each domain. For example, the end-to-end controller transmits bandwidth information to the controller of domain A.

[0006] At that time, in order to utilize the resource information (e.g., SID (Slice ID), IP address) generated in a certain domain for resource generation in another domain, it is necessary to circulate the resource information between domains. For example, the controller of domain A sends the SID generated in domain A to the controller of domain C. The controller of domain B sends the IP address generated in domain B to the controller of domain C. Then, the controller of domain C sends the received SID and IP address to domain C.

[0007] Also, after the operation of the constructed network slice, in order to improve the efficiency of its maintenance operation, the concept of Closed Loop Automation is proposed in ETSI ZSM, etc., where the end-to-end controller acquires FM (Fault Management) information and PM (Performance Management) information flowing from each NW resource in each domain, determines the presence or absence of service impact based on the FM / PM information, and performs operations at the controller of each domain as necessary.

[0008] For example, when PM information (throughput) is issued from the NW resource of domain A and, accordingly, FM information (bandwidth excess) is issued from the controller of domain A, the end-to-end controller determines the presence or absence of impact on the service provided by the server to the terminal end-to-end based on the FM / PM information. If there is an impact on the service, a Closed Loop is executed at the controller of a predetermined domain. Specifically, in a predetermined controller, monitoring, analysis, processing decision, and processing execution are repeatedly executed in that order.

[0009] Here, the technology for sending and receiving information between domains will be described. When sending and receiving resource information, etc. between domains, REST API and Pub / Sub type protocols are used.

[0010] A REST API is an API composed of methods and URIs defined based on the design concept of a web system called Representational State Transfer. It enables one-to-one data transmission and reception in a client-server model.

[0011] For example, Client 1 in Domain A sends data to Server 1 in Domain B with the message "POST / user". Client 2 in Domain A retrieves data from Server 2 in Domain B with the message "GET / user".

[0012] A Pub / Sub type protocol is a lightweight messaging protocol that utilizes a data circulation unit called a topic. It supports not only one-to-one but also one-to-many communications, allowing data transmission and reception without being aware of the data format. Specifically, there are MQTT (Message Queue Telemetry Transport), AMQP (Advanced Message Queuing Protocol), etc.

[0013] For example, the Publisher in Domain A publishes "Topic:1" and publishes "Topic:2". The Subscriber in Domain B subscribes to "Topic:1" via the broker of "Topic:1". Three Subscribers 1 - 3 in Domain C each subscribe to "Topic:2" via the broker of "Topic:2".

Prior Art Documents

Non-Patent Documents

[0014]

Non-Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0015] In information circulation by REST API, when circulating information between domains, it is necessary for the opposing device to recognize the endpoint information and data format of the opposing device. Therefore, when the endpoint information and data format change due to construction in another domain, etc., the opposing domain device needs to detect and follow this change.

[0016] In information circulation by Pub / Sub type protocol, it is necessary for both the Publisher and Subscriber to share topic information in advance. Therefore, in cases where the information sharing target changes dynamically, such as in the generation / change / deletion process of network slices, it is necessary to dynamically convey the topic information to both of them.

[0017] The present invention has been made in view of the above circumstances, and an object of the present invention is to provide a technology that enables information circulating in a management system to be circulated simply.

Means for Solving the Problems

[0018] A management system according to an aspect of the present invention is a management system for managing network resources. For each construction order of a network slice, a management device that generates an information sharing channel according to an identifier related to the network slice, and a plurality of sharing devices that share resource information required at the time of execution of the construction order between domains of the network via the information sharing channel.

[0019] A management system according to an aspect of the present invention is a management system for managing network resources. For each network slice constructed in each domain of the network, a management device generates an information sharing channel according to an identifier related to the network slice, a plurality of registration devices respectively register maintenance operation information necessary for maintaining and operating network resources in each of the network slices for each of the plurality of information sharing channels, and an acquisition device acquires the maintenance operation information from a predetermined information sharing channel among the plurality of information sharing channels.

[0020] A management method according to an aspect of the present invention is a management method performed by a management system for managing network resources. A management device generates an information sharing channel according to an identifier related to a network slice for each construction order of the network slice, and a plurality of sharing devices share resource information necessary at the time of executing the construction order among domains of the network via the information sharing channel.

[0021] A management method according to an aspect of the present invention is a management method performed by a management system for managing network resources. A management device generates an information sharing channel according to an identifier related to the network slice for each network slice constructed in each domain of the network, a plurality of registration devices respectively register maintenance operation information necessary for maintaining and operating network resources in each of the network slices for each of the plurality of information sharing channels, and an acquisition device acquires the maintenance operation information from a predetermined information sharing channel among the plurality of information sharing channels.

[0022] A management program according to an aspect of the present invention causes a computer to function as the above management system.

Advantages of the Invention

[0023] According to the present invention, it is possible to provide a technology that enables information flowing in a management system to be circulated simply.

Brief Description of the Drawings

[0024]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Embodiments for Carrying Out the Invention

[0025] Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the description of the drawings, the same reference numerals are given to the same parts and the description thereof is omitted.

[0026] [Summary of the Invention] The present invention relates to a method for suitably circulating resource information between domains when dynamically managing network slices across domains, and a method for suitably circulating FM / PM information of each domain between the domain and the end-to-end controller after the construction of the network slice.

[0027] Specifically, the present invention generates a resource information sharing channel for sharing resource information that circulates between the controllers of each domain for each network slice construction order (for each NSID (Network Slice ID)), and realizes the circulation of resource information between domains when a service order (SO) is input using the resource information sharing channel.

[0028] Specifically, the present invention generates an FM / PM information sharing channel for sharing FM / PM information that circulates between a controller and an end-to-end controller for each slice (for each NSSID (Network Slice Subnet ID)) constructed in each domain, and realizes the circulation of FM / PM information necessary for the maintenance operation of the network slice using the FM / PM information sharing channel.

[0029] [Configuration example of management system] FIG. 1 is a diagram showing a configuration example of a management system 1 according to the present embodiment.

[0030] The management system 1 is a management system that manages network resources, and includes a controller 11A that manages NW resources of domain A between the terminal 100 and the server 200, a controller 11B that manages NW resources of domain B adjacent to domain A, and an end-to-end controller 12 that manages the controller 11A of domain A and the controller 11B of domain B.

[0031] Further, the management system 1 includes a channel management device 21, two resource information sharing devices 22A and 22B, two FM / PM information registration devices 23A and 23B, and an FM / PM information acquisition device 24.

[0032] The channel management device (management device) 21 includes a resource information sharing channel management functional unit 211 and an FM / PM information sharing channel management functional unit 212.

[0033] The resource information sharing channel management functional unit 211 has a function of generating a resource information sharing channel according to an identifier (NSID) related to the network slice for each network slice construction order. Specifically, the resource information sharing channel management functional unit 211 has a function of generating / modifying / deleting a resource information sharing channel CH1 for sharing resource information between the controllers 11A and 11B of domains A and B.

[0034] The FM / PM information sharing channel management functional unit 212 has a function of generating an FM / PM information sharing channel according to an identifier (NSSID) related to the network slice for each network slice constructed in each domain of the network. Specifically, the FM / PM information sharing channel management functional unit 212 has a function of generating / modifying / deleting an FM / PM information sharing channel CH2(A) for sharing FM / PM information between the controller 11A and the end-to-end controller 12, and an FM / PM information sharing channel CH2(B) for sharing FM / PM information between the controller 11B and the end-to-end controller 12.

[0035] The resource information sharing device (sharing device) 22A has a function of sharing resource information required at the time of executing a network slice construction order between domains of the network via a resource information sharing channel. Specifically, the resource information sharing device 22A has a function of sharing the resource information generated in domain A using the resource information sharing channel CH1 between the controller 11A and the controller 11B.

[0036] The resource information sharing device (sharing device) 22B has a function of sharing resource information required at the time of executing a network slice construction order between domains of the network via a resource information sharing channel. Specifically, the resource information sharing device 22B has a function of sharing the resource information generated in domain B using the resource information sharing channel CH1 between the controller 11A and the controller 11B.

[0037] The FM / PM information registration device (registration device) 23A has a function of registering, for an FM / PM information sharing channel, operation and maintenance information necessary for the operation and maintenance of network resources in a network slice. Specifically, the FM / PM information registration device 23A has a function of registering the FM / PM information issued from domain A to the FM / PM information sharing channel CH2(A).

[0038] The FM / PM information registration device (registration device) 23B has a function of registering, for an FM / PM information sharing channel, operation and maintenance information necessary for the operation and maintenance of network resources in a network slice. Specifically, the FM / PM information registration device 23A has a function of registering the FM / PM information issued from domain B to the FM / PM information sharing channel CH2(B).

[0039] The FM / PM information acquisition device (acquisition device) 24 has a function of acquiring operation and maintenance information from a predetermined FM / PM information sharing channel among a plurality of FM / PM information sharing channels. Specifically, the FM / PM information acquisition device 24 has a function of acquiring the FM / PM information issued from domain A from the FM / PM information sharing channel CH2(A), and acquiring the FM / PM information issued from domain B from the FM / PM information sharing channel CH2(B).

[0040] [Operation of the management system; Flow of resource information] A method for the flow of resource information will be described. The flow of resource information is executed when a network slice is constructed. The flow of resource information is executed by the channel management device 21 and two resource information sharing devices 22A and 22B.

[0041] Hereinafter, the case of receiving an order for constructing a network slice and the case of receiving an order for abolishing a network slice will be described. Note that a network slice includes logically or physically dividing one NW resource into a plurality of NW resources, and further dividing the divided NW resources.

[0042] Figure 2 is a diagram showing the flow of resource information during construction order reception.

[0043] Step S101; First, the end-to-end controller 12 transmits an NSID for identifying the resources of the network slice to the resource information sharing channel management function unit 211 of the channel management device 21, triggered by the order issuance to domain A which it calls first.

[0044] For example, the end-to-end controller 12 {"type": "create", "nsid": "1"} is transmitted.

[0045] Step S102; Next, the resource information sharing channel management function unit 211 generates a resource information sharing channel CH1 for the NSID based on the received NSID.

[0046] For example, the resource information sharing channel management function unit 211 uses mosquitto which is the OSS of the MQTT Broker broker (topic: / nsid / 1) to generate a resource information sharing channel CH1. The topic is also generated when mosquitto_pub is executed. A string containing the NSID for identifying the resources of the network slice is used for the topic which is the channel identifier of the resource information sharing channel CH1.

[0047] Steps S103, S104; Next, the controller 11A of domain A receives a construction order containing the above NSID from the end-to-end controller 12, and passes the NSID included in the received construction order and the resource information generated in its own domain A to the resource information sharing device 22A of domain A.

[0048] For example, the controller 11A {"type": "publish", "nsid": "1", "ipaddr": "192.168.1.1"} Pass it.

[0049] Step S105; Next, the resource information sharing device 22A accesses the resource information sharing channel CH1 of the NSID based on the passed NSID, and registers the information to be shared with another domain B (resource information generated in its own domain A) in the accessed resource information sharing channel CH1.

[0050] For example, the resource information sharing device 22A $mosquitto_pub -h <brokerip>-t / nsid / 1 -m "{"ipaddr":”192.168.1.1”}" Execute the mosquitto publish command as follows.

[0051] Steps S106, S107; The controller 11B in domain B also receives the construction order including the above NSID from the end - to - end controller 12, and passes the NSID included in the received construction order to the resource information sharing device 22B in domain B.

[0052] For example, the controller 11B passes {"type”: "subscribe”, "nsid”:”1”} .

[0053] Step S108; Next, the resource information sharing device 22B accesses the resource information sharing channel CH1 of the NSID based on the passed NSID, and acquires the information to be shared with the other domain A (the resource information registered by the other domain A) from the accessed resource information sharing channel CH1.

[0054] For example, the resource information sharing device 22B $ mosquitto_sub -h <brokerip>-t / nsid / 1 Execute the mosquitto subscribe command of "to".

[0055] Similarly, the resource information sharing device 22B can register information (resource information generated in its own domain B) to be shared with another domain A on the resource information sharing channel CH1. The resource information sharing device 22A can acquire information (resource information registered by another domain B) to be shared with another domain B from the resource information sharing channel CH1.

[0056] FIG. 3 is a diagram showing a processing flow at the time of receiving a cancellation order.

[0057] Step S201; First, the end-to-end controller 12 uses the reception of a response from the last-called domain B as a trigger to send the NSID to be cancelled to the resource information sharing channel management function unit 211 of the channel management device 21.

[0058] Step S202; Next, the resource information sharing channel management function unit 211 deletes the resource information sharing channel CH1 of the received NSID based on the received NSID.

[0059] [Operation of the management system; Flow of FM / PM information] The method of flowing FM / PM information will be described. The flow of FM / PM information is executed after the construction of the network slice in order to improve the maintenance operation efficiency of the network slice. The flow of FM / PM information is executed by the channel management device 21, two FM / PM information registration devices 23A and 23B, and the FM / PM information acquisition device 24.

[0060] FIG. 4 and FIG. 5 are diagrams showing the flow processing flow of FM / PM information. FIG. 4 is a processing flow until a FM / PM information sharing channel is generated. FIG. 5 is a processing flow when FM / PM information is circulated.

[0061] Steps S301, S302; First, every time the end-to-end controller 12 receives a response from domain A, it transmits the NSSID(A) that identifies the resource generated in domain A to the FM / PM information sharing channel management function unit 212 of the channel management device 21 together with the control command of "pm generation".

[0062] Step S303; Next, the FM / PM information sharing channel management function unit 212 generates the PM information sharing channel CH2(A)' of the NSSID(A) based on the received NSSID(A). At this time, if the FM / PM information sharing channel management function unit 212 has received the control command of "fm generation", it generates the FM information sharing channel, and if it has received the control command of "fm / pm generation", it generates the FM / PM information sharing channel.

[0063] For example, the FM / PM information sharing channel management function unit 212 uses mosquitto, which is the OSS of the MQTT Broker, broker (topic: / nsid / 1 / domA / pm / nssid / 1) to generate the PM information sharing channel CH2(A)'. The topic is also generated when mosquitto_pub is executed. For the topic, which is the channel identifier of the PM information sharing channel CH2(A)', a string obtained by concatenating the NSSID generated in domain A and the domain name is used to prevent naming duplication.

[0064] Step S304; Next, the FM / PM information sharing channel management function unit 212 associates the received NSSID(A) with the NSID held by the resource information sharing channel management function unit 211.

[0065] Steps S305, S306; Similarly, every time the end-to-end controller 12 receives a response from domain B, it transmits the NSSID(B) that identifies the resource generated in domain B to the FM / PM information sharing channel management function unit 212 of the channel management device 21 together with the control command of "fm generation".

[0066] Step S307; Next, the FM / PM information sharing channel management function unit 212 generates the FM information sharing channel CH2(B)' of the NSSID(B) based on the received NSSID(B). At this time, if the FM / PM information sharing channel management function unit 212 has received the control command of "pm generation", it generates the PM information sharing channel, and if it has received the control command of "fm / pm generation", it generates the FM / PM information sharing channel.

[0067] For example, the FM / PM information sharing channel management function unit 212 uses mosquitto, which is the OSS of the MQTT Broker, broker (topic: / nsid / 1 / domB / fm / nssid / 1) to generate the FM information sharing channel CH2(B)'. The topic is also generated when mosquitto_pub is executed. To prevent naming duplication, a character string obtained by concatenating the NSSID generated in domain B and the domain name is used for the topic, which is the channel identifier of the FM information sharing channel CH2(B)'.

[0068] Step S308; Next, the FM / PM information sharing channel management function unit 212 associates the received NSSID(B) with the NSID held by the resource information sharing channel management function unit 211.

[0069] It should be noted that the order of steps S301 to S304 and steps S305 to S308 may be interchanged with each other, or they may be executed simultaneously.

[0070] So far, the case of channel generation has been described. When the channel becomes unnecessary, the FM / PM information sharing channel management function unit 212 deletes the channel. That is, the FM / PM information sharing channel management function unit 212 generates / deletes the FM / PM information sharing channels CH2(A) and CH2(B) for each NW resource generated in domains A and B, respectively.

[0071] Subsequently, the FM / PM information distribution process will be described with reference to FIG. 5.

[0072] Step S401; After step S304, the controller 11A of domain A passes the domain name, NSSID(A), and the PM data issued from domain A to the FM / PM information registration device 23A of domain A in JSON format.

[0073] For example, the controller 11A of domain A {"domain”: "A”, "nssid”: "1”, "type”: "pm”,"throughput”:300} is passed.

[0074] Step S402; Next, the FM / PM information registration device 23A registers the PM data issued from domain A in the PM information sharing channel CH2(A)' corresponding to the passed domain name and NSSID(A).

[0075] For example, the FM / PM information registration device 23A $ mosquitto_pub -h <brokerip>-t / nsid / 1 / domA / pm / nssid1 -m "{"throughput”:300}" Execute the mosquitto publish command of "".

[0076] Step S403; Similarly, after step S308, the controller 11B of domain B passes the domain name, NSSID(B), and FM data issued from domain B to the FM / PM information registration device 23B of domain B in JSON format.

[0077] For example, the controller 11B {"domain”: "B”, "nssid”: "1”, "type” : "fm”, "alert”:”The delay is greater than the threshold”} and passes it.

[0078] Step S404; Next, the FM / PM information registration device 23B registers the FM data issued from domain B in the FM information sharing channel CH2(B)' corresponding to the passed domain name and NSSID(B).

[0079] For example, the FM / PM information registration device 23B $ mosquitto_pub -h <brokerip>-t / nsid / 1 / domB / fm / nssid / 1 -m {"alert”:”The delay is greater than the threshold”} Execute the mosquitto publish command as follows.

[0080] Step S405; After that, the end - to - end controller 12 passes the domain name and NSSID of the request target to the FM / PM information acquisition device 24. For example, when the end - to - end controller 12 requests the PM data of domain A, it passes domain A, NSSID(A), and the data type to the FM / PM information acquisition device 24.

[0081] For example, the end - to - end controller 12 {"domain”: "A”, "type”: "pm”, "nssid”: "1”} is passed.

[0082] Step S406; The FM / PM information acquisition device 24 acquires the FM / PM data issued from the domain corresponding to the passed domain name and NSSID from the FM / PM information sharing channel corresponding to the NSSID. For example, when the domain A, NSSID(A), and the PM data type are passed to the FM / PM information acquisition device 24, it acquires the PM data from the PM information sharing channel CH2(A) corresponding to NSSID(A).

[0083] For example, the FM / PM information acquisition device 24 $ mosquitto_sub -h <brokerip>-t / nsid / 1 / domA / pm / nssid / 1 Execute the mosquitto subscribe command of " ".

[0084] Step S407; After that, the FM / PM information acquisition device 24 returns the acquired FM / PM data to the end-to-end controller 12. The end-to-end controller 12 acquires the FM / PM data of the domain requested in step S405. For example, the end-to-end controller 12 acquires the FM / PM data issued from domain A.

[0085] For example, the end-to-end controller 12 {"domain”: "A”, "nssid”: "1”, "type”:”pm”, "throuput”:300} to acquire.

[0086] [Effect of Embodiment] According to the present embodiment, as shown in FIG. 6, identifiers related to slice resources such as NSID and NSSID are circulated between the end-to-end controller 12 and the per-domain controllers 11A to 11C, and an information sharing channel corresponding to those identifiers is dynamically generated. Therefore, resource information can be circulated between domains without the per-domain controllers 11A to 11C being aware of the endpoint information and format.

[0087] Further, according to the present embodiment, as shown in FIG. 7, since the end-to-end controller 12 receives the FM / PM information for each domain and each NW resource from the already constructed network slice, a Closed Loop can be realized by a predetermined controller by the end-to-end controller 12.

[0088] Further, according to this embodiment, as shown in FIG. 8, the channel management device 21 centrally manages the resource information sharing channels for each NSID and the FM / PM information sharing channels for each NSSID in association with each other. Therefore, when the resource information sharing device 22 or the FM / PM information acquisition device 24 acquires information, it is possible to specify a flexible information acquisition range such as an MQTT wild card (the '+' notation shown in FIG. 9).

[0089] [Others] The present invention is not limited to the above-described embodiment. The present invention can be variously modified within the scope of the gist of the present invention.

[0090] The channel management device 21 of the above-described embodiment can be realized, for example, by using a general-purpose computer system including a CPU 901, a memory 902, a storage 903, a communication device 904, an input device 905, and an output device 906, as shown in FIG. 10. The memory 902 and the storage 903 are storage devices. In the computer system, when the CPU 901 executes a predetermined program loaded on the memory 902, each function of the channel management device 21 is realized.

[0091] The channel management device 21 may be implemented by one computer. The channel management device 21 may be implemented by a plurality of computers. The channel management device 21 may be a virtual machine implemented on a computer. The program for the channel management device 21 can be stored in a computer-readable recording medium such as an HDD, an SSD, a USB memory, a CD, or a DVD. The program for the channel management device 21 can also be distributed via a communication network.

[0092] The resource information sharing devices 22A and 22B, the FM / PM information registration devices 23A and 23B, and the FM / PM information acquisition device 24 also have the same hardware configuration as the channel management device 21.

Explanation of Reference Numerals

[0093] 1: Management system 11A~11C: Controller 12: End-to-End Controller 21: Channel Management Device 211: Resource Information Sharing Channel Management Functional Unit 212: FM / PM Information Sharing Channel Management Functional Unit 22A~22C: Resource Information Sharing Device 23A~23C: FM / PM Information Registration Device 24: FM / PM Information Acquisition Device 100: Terminal 200: Server 901: CPU 902: Memory 903: Storage 904: Communication Device 905: Input Device 906: Output Device< / brokerip> < / brokerip> < / brokerip> < / brokerip> < / brokerip>

Claims

1. In a management system for managing network resources, a management device that generates an information sharing channel according to an identifier related to the network slice for each construction order of the network slice; a plurality of sharing devices that share resource information necessary for executing the construction order among domains of the network via the information sharing channel; A management system comprising:

2. In a management system for managing network resources, a management device that generates an information sharing channel according to an identifier related to the network slice for each network slice constructed in each domain of the network; a plurality of registration devices that respectively register maintenance operation information necessary for maintaining and operating network resources in each of the network slices for each of the plurality of information sharing channels; an acquisition device that acquires the maintenance operation information from a predetermined information sharing channel among the plurality of information sharing channels; A management system comprising:

3. The management device The management system according to claim 1 or 2, which associates an information sharing channel for sharing resource information necessary for executing the construction order of the network slice with an information sharing channel for sharing maintenance operation information necessary for maintaining and operating network resources in the network slice.

4. In a management method performed by a management system for managing network resources, a management device generates an information sharing channel according to an identifier related to the network slice for each construction order of the network slice; a plurality of sharing devices share resource information necessary for executing the construction order among domains of the network via the information sharing channel; A management method.

5. In a management method performed by a management system for managing network resources, a management device generates an information sharing channel according to an identifier related to the network slice for each network slice constructed in each domain of the network; a plurality of registration devices respectively register maintenance operation information necessary for maintaining and operating network resources in each of the network slices for each of the plurality of information sharing channels; The acquisition device acquires the maintenance operation information from a predetermined information sharing channel among the plurality of information sharing channels. Management method.

6. A management program that causes a computer to function as the management system according to claim 1 or 2.

Images