Data processing device, method and program
The data processing device automates the extraction and validation of candidate resources and parameters for intent-based control, addressing high human costs and inflexibility in conventional methods, thereby enhancing resource management efficiency and adaptability.
Patent Information
- Application Number
- JP2024505842
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2022-03-11
- Publication Date
- 2025-12-23
- Estimated Expiration
- 2042-03-11
AI Technical Summary
Conventional manual resource control methods based on user intent incur high human costs and risk overlooking important resources or parameters, and are inflexible to changes in the service provision environment or specifications.
A data processing device and method that automatically extracts and validates candidate resources and parameters using intent-based control, reducing manual intervention by utilizing a file describing the service content, extraction units, and designation units to manage and adapt to changes in the service environment.
This approach reduces personnel costs, enhances flexibility in responding to environmental changes, and ensures comprehensive control of resources and parameters, minimizing unexpected control issues.
Smart Images

Figure 0007790550000001 
Figure 0007790550000002 
Figure 0007790550000003
Abstract
Description
[Technical Field]
[0001] FIELD Embodiments of the present invention relate to a data processing device, a method, and a program. [Background technology]
[0002] Conventionally, resource control methods based on intent (the intention or purpose of a user (sometimes referred to as a customer)) such as service quality requirements for a network service or an application service have adopted a so-called inquiry-based method in which inquiries are made to developers or administrators of application programs (hereinafter sometimes referred to as applications or apps), networks, or servers (hereinafter sometimes referred to as applications, etc.), i.e., manual intervention is used to determine adjustable resources or parameters in the applications, or the range of adjustable values of parameters. [Prior art documents] [Non-patent literature]
[0003] [Non-Patent Document 1] Wu et al., “Intent-driven cloud resource design framework to meet cloud performance requirements and its application to a cloud-sensor system, Journal of Cloud Computing: Advances, Systems and Applications(2021) Summary of the Invention [Problem to be solved by the invention]
[0004] However, the above-mentioned manual approach incurs a large amount of human costs, and there is a risk that resources or parameters that users, administrators, and developers are not aware of may be overlooked, and there is also the issue of responding to changes in controllable resources or parameters due to changes in the service provision environment or specifications.
[0005] The present invention has been made in light of the above-mentioned circumstances, and its object is to provide a data processing device, method, and program that are capable of appropriately controlling resources based on intent. [Means for solving the problem]
[0006] A data processing device according to one aspect of the present invention includes a file in which the content of the service to be provided is described. a file relating to the control of resources used to provide the service; used to provide the said services Configurable as a resource an extracting unit that extracts resource candidates and parameter candidates used to control the resources; and a parameter extracting unit that extracts resources and parameters used to provide the service from the resources and parameters extracted by the extracting unit. Be and a designation unit that accepts designation of resources and parameters to be used.
[0007] A data processing method according to one aspect of the present invention is performed by a data processing device. circle a file in which the content of the service to be provided is described by an extraction unit of the data processing device, a file relating to the control of resources used to provide the service; used to provide the said services Configurable as a resource extracting resource candidates and parameter candidates used to control the resources; and selecting, by a designation unit of the data processing device, candidates to be used to provide the service from among the extracted resources and parameters. Be and accepting a specification of resources and parameters to be used. [Effects of the Invention]
[0008] According to the present invention, resources can be appropriately controlled based on intent. [Brief explanation of the drawings]
[0009] [Figure 1] FIG. 1 is a diagram showing an application example of a data processing device according to an embodiment of the present invention. [Figure 2] FIG. 2 is a diagram illustrating an example of a management target managed by the intent-based resource manager. [Figure 3] FIG. 3 is a diagram showing an application example of a data processing device according to an embodiment of the present invention. [Figure 4] FIG. 4 is a diagram illustrating an example of the operation of the parameter extraction unit. [Figure 5] FIG. 5 is a diagram illustrating an example of the operation of the parameter variation detection unit. [Figure 6] FIG. 6 is a flow chart illustrating an example of a processing procedure performed by a data processing device according to one embodiment of the present invention. [Figure 7] FIG. 7 is a diagram showing a specific example of parameter extraction. [Figure 8] FIG. 8 is a diagram showing a specific example of parameter variation detection. [Figure 9] FIG. 9 is a block diagram showing an example of the hardware configuration of a data processing device according to one embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION
[0010] An embodiment of the present invention will be described below with reference to the drawings. In this embodiment, in the first stage (initial stage), candidate resources that can be configured for intent-based resource control to be used in providing the service or candidate parameters to be used in controlling the resources are extracted using rules, natural language techniques, etc. from a file that describes the content of the service to be provided and is an administrative file related to the control of an application, network, or server, such as a contract, specification, or config file (hereinafter sometimes referred to as a config, etc.).
[0011] In this embodiment, in the second stage (operational stage), changes in the configurations of the applications, networks, or servers are periodically checked, and new resource or parameter variations arising from changes in the service provision environment, specifications, or contracts are extracted as candidates for newly configurable resources or parameters. Also, the processing in the first stage may be performed again as necessary.
[0012] The candidates are presented to a user, developer, or administrator, who can add to, modify, or enable the candidates.
[0013] In this embodiment, candidates for newly configurable resources or parameters are automatically extracted, and the extracted results are validated by an administrator. This allows for a more comprehensive extraction of configurable parameters, etc., compared to conventional manual inquiry-based methods. This reduces personnel costs and significantly reduces the time required for extraction, making it possible to appropriately and easily introduce intent-based control. It also prevents control related to unexpected parameters.
[0014] Furthermore, in this embodiment, as described above, newly configurable resources or parameters are extracted based on changes in configuration, etc., so that after the above-described intent-based control is introduced, it is possible to respond quickly and flexibly to changes in the service provision environment or specifications, etc., or changes in the user's usage environment. For simplicity, the following description will be given assuming that only parameters are extracted.
[0015] FIG. 1 is a diagram showing an application example of a data processing device according to an embodiment of the present invention. As shown in FIG. 1, a resource management device 100, which is a data processing device according to one embodiment of the present invention, has a parameter extraction unit 11, an application parameter collection unit (application parameter collection unit) 12, and a parameter change detection unit 13 as components related to an application.
[0016] The resource management device 100 has a parameter extraction unit 21, an access network parameter collection unit 22, and a parameter variation detection unit 23 as components related to an access network. The resource management device 100 has a parameter extraction unit 31, a core network parameter collection unit 32, and a parameter variation detection unit 33 as components related to the core network.
[0017] The resource management device 100 has a parameter extraction unit 41, a cloud parameter collection unit 42, and a parameter variation detection unit 43 as components related to the server.
[0018] Hereinafter, the above parameter extraction units 11, 21, 31, and 41 may be referred to as the respective parameter extraction units. Hereinafter, the above application parameter collection unit 12, access network parameter collection unit 22, core network parameter collection unit 32, and cloud parameter collection unit 42 may be referred to as the respective parameter collection units. Hereinafter, the above parameter variation detection units 13, 23, 33, and 43 may be referred to as the respective parameter variation detection units.
[0019] The resource management device 100 includes an intent-based resource management unit 51 at the subsequent stage of each of the parameter collection units, and a designation unit 52 that accepts an input operation related to parameter designation and designates the parameter in accordance with this input operation. Here, the configuration used in the first stage will be described, excluding the parameter variation detection units. Furthermore, while Figure 1 shows a configuration for extracting and collecting parameters related to four types of resources, it is also possible to have only a configuration for extracting and collecting parameters related to one to three types of controlled resources, or a configuration for extracting and collecting parameters related to five or more types of controlled resources. Furthermore, when a configuration for extracting and collecting parameters relating to a plurality of types of resources is provided, these configurations may operate serially or in parallel.
[0020] The parameter extraction unit 11 extracts candidates for parameters that can be newly set for an application from a management file D1 that may include an application specification, a system configuration, a client configuration, etc. The extracted candidates are passed to the intent-based resource management unit 51 via the application parameter collection unit 12. Note that an application developer or the like (reference symbol p1 in FIG. 1 ) may directly set parameters by inputting data into the resource management device 100.
[0021] The parameter extraction unit 21 extracts candidates for parameters that can be newly set for the access network from a management file D2 that includes an access network specification, a contract, a system configuration, etc. The extracted candidates are passed to the intent-based resource management unit 51 via the access network parameter collection unit 22. Note that an access network administrator or the like (reference symbol p2 in FIG. 1) may directly set the parameters by inputting them into the resource management device 100.
[0022] The parameter extraction unit 31 extracts candidates for parameters that can be newly set for the core network from a management file D3 that includes a core network specification, a contract, a system configuration, etc. The extracted candidates are passed to the intent-based resource management unit 51 via the core network parameter collection unit 32. Note that the core network administrator or the like (reference number p3 in FIG. 1) may directly set the parameters by inputting the parameters.
[0023] The parameter extraction unit 41 extracts candidates for parameters that can be newly set for the cloud server from a management file D4 that includes a cloud server specification, a contract, a system configuration, or the like. The extracted candidates are passed to the intent-based resource management unit 51 via the cloud parameter collection unit 42. Note that a cloud administrator or the like (reference number p4 in FIG. 1) may directly set parameters by inputting them into the resource management device 100. Hereinafter, the above management files D1 to D4 may be referred to as individual management files.
[0024] In the first stage of this embodiment, when intent-based resource management is first introduced, various parameter extraction units comprehensively extract newly configurable parameters from the management files.
[0025] FIG. 2 is a diagram illustrating an example of a management target managed by the intent-based resource manager. Next, types of resources and parameters for controlling resources according to intents will be described.
[0026] The intent-based resource management unit 51 recognizes the resources or parameters shown in (1) to (4) below and appropriately controls the resources so that intents such as service quality requirements are satisfied.
[0027] (1) Parameters (labeled pa1 in Figure 2) that can be controlled within an app installed on a personal computer (labeled a1 in Figure 2) or a mobile device (labeled a2 in Figure 2) (2) Parameters that can be controlled by access network resources (labeled b1 and b2 in Figure 2) (labeled pa2 in Figure 2) (3) Parameters that can be controlled by core network resources (item c in Figure 2) (item pa3 in Figure 2) (4) Resources and controllable parameters (labeled pa4 in Figure 2) of the stationary server (labeled d1 in Figure 2) or cloud server (labeled d2 in Figure 2) that handles the load.
[0028] FIG. 3 is a diagram showing an application example of a data processing device according to an embodiment of the present invention. Here, various parameter variation detection units, that is, parameter variation detection units 13, 23, 33, and 43, will be described as components used in the second stage. In this embodiment, extraction by the various parameter extraction unit is repeated at regular timing, and the results collected at each timing are collected by the various parameter variation detection unit and stored in the internal memory of the various parameter variation detection unit. During operation, there is a possibility that new parameters that did not exist in the initial stage will appear due to changes in the service provision environment, specifications, or contracts. However, as in the first stage above, the method of re-reading management files such as specifications or contracts using various parameter extraction units and re-extracting the types of configurable parameters will result in duplication of extraction results, resulting in wasted effort and cost.
[0029] Therefore, in this embodiment, as a second step, various parameter change detection units periodically check the time series changes in the contents of management files such as configurations, and detect newly occurring parameters in the configurations in these management files, thereby making it possible to narrow down and extract only the parameters after the changes.
[0030] In detail, parameter variation detection unit 13 periodically checks for variations over time in the contents of management file D1, which includes application specifications, contracts, and system configuration client configurations, and when a variation occurs in this management file, such as the addition of a new parameter, a change in a parameter value (e.g., a numerical value or ID (IDentifier)), or the deletion of a parameter, it extracts the details of the variation and passes them to application parameter collection unit 12. This application parameter collection unit 12 changes the results of collection in the first stage according to the passed details.
[0031] The parameter variation detection unit 23 periodically checks for variations over time in the contents of the management file D2, such as the access network specifications, and when a variation occurs in this management file, it extracts the details of the variation and passes them to the access network parameter collection unit 22. This access network parameter collection unit 22 changes the results of collection in the first stage according to the contents passed to it.
[0032] The parameter variation detection unit 33 periodically checks for variations over time in the contents of the management file D3, such as the core network specifications, and when a variation occurs in this management file, it extracts the details of the variation and passes them to the core network parameter collection unit 32. This core network parameter collection unit 32 changes the results of collection in the first stage according to the passed details.
[0033] The parameter change detection unit 43 periodically checks for changes over time in the contents of the management file D4, such as the server service specifications, and when a change occurs in this management file, it extracts the details of the change and passes them to the cloud parameter collection unit 42. This cloud parameter collection unit 42 changes the results of collection in the first stage according to the passed details.
[0034] Next, the operation of the parameter extraction unit in the first stage will be described. Fig. 4 is a diagram showing an example of the operation by the parameter extraction unit. Here, the parameter extraction unit 11 will be described as an example. The parameter extraction unit 11 uses natural language processing, rule-based techniques, or the like to automatically extract candidate types of parameters that can be newly set ("Parameter 1" and "Parameter 2" in FIG. 4) and candidate ranges of values that the parameters can take (sometimes referred to as parameter types and value ranges) from the management file D1 that includes the application specifications, contracts, system configurations, and client configurations, as candidate parameters to be controlled by the intent-based resource management unit 51. The parameter extraction unit 11 associates the candidate with information in the management file D1 from which the candidate was extracted ("Specification" in FIG. 4) and sets the initial value of the Active flag ("Active" in FIG. 4), which is a flag indicating whether the candidate is enabled, i.e., whether the type and value range of the parameter to be controlled by the intent-based resource management unit 51, to "No." The parameter extraction unit 11 passes the result of this setting to the application parameter collection unit 12 as information on the parameter candidate. The Active flag is sometimes called an enable flag.
[0035] The application parameter collection unit 12 stores the information received from the parameter extraction unit 11 in an internal memory and presents it to an application administrator / developer (sometimes referred to as an operator) or a user (denoted by P in FIG. 4) by displaying it on a screen, etc. Information on parameter candidates may be presented to the user, for example.
[0036] The application administrator, developer, or the like who receives this presentation determines the parameter to be controlled by the intent-based resource management unit 51 from the presented parameter candidate information, for example, the parameter type "Parameter 1" in Fig. 4, and performs an input operation to the resource management device 100 to specify this type of parameter as the parameter to be controlled. The specification unit 52 accepts this input operation and sets to "Yes" the Active flag associated with the same record as the record (each row in Fig. 4) of the parameter specified by the input operation.
[0037] In addition to the type and value range of the automatically extracted parameter, the application administrator / developer can also register a desired parameter ("Parameter 3" in FIG. 4) and value range to be controlled by the intent-based resource manager 51 by inputting the parameter into the resource management device 100. In this case, the designator 52 sets the initial value of the Active flag for the same record to "Yes."
[0038] The items surrounded by the symbol a in FIG. 4 are items that are set through automatic extraction by the parameter extraction unit 11, and the items surrounded by the symbol b in FIG. 4 are items that are set by the designation unit 52 in accordance with input operations by the application administrator, developer, etc.
[0039] Next, the operation of the parameter variation detection unit in the second stage will be described. Fig. 5 is a diagram showing an example of the operation of the parameter variation detection unit. Here, the parameter variation detection unit 13 will be described as an example.
[0040] The parameter variation detection unit 13 periodically reads out a management file D1 containing application specifications, a contract, a system configuration, and a client configuration, and detects the difference between the contents of the read out management file D1 and the contents of the management file D1 read out at a timing (e.g., time t in Figure 5) a predetermined time before the current time (e.g., time t+1 in Figure 5).
[0041] When the parameter change detection unit 13 detects a change in the contents of the configuration in the management file D1, for example, a new type of parameter, between time t+1 and time t+2, the parameter change detection unit 13 passes the new parameter type (for example, “Parameter 4” in FIG. 5) and value range detected as this difference to the application parameter collection unit 12 as candidates for the new parameter type and value range (candidate parameters) to be controlled by the intent-based resource management unit 51.
[0042] The application parameter collection unit 12 sets the initial value of the Active flag ("No" in the "Parameter 4" row in FIG. 5) to the information passed from the parameter extraction unit 11, and presents the information as a new candidate parameter to the application administrator, developer, etc. (reference symbol P in FIG. 5) by displaying it on a screen, etc. The information on the new candidate parameter may be presented to the user, for example.
[0043] When the application administrator, developer, or the like who has received this presentation determines that the presented candidate is appropriate as a parameter to be controlled by the intent-based resource management unit 51, the application administrator, developer, or the like performs an input operation to the resource management device 100 to designate this type of parameter as the parameter to be controlled. The designation unit 52 accepts this input operation and sets the Active flag associated with the same record as the record of the designated parameter to "Yes."
[0044] The items surrounded by the symbol a1 in FIG. 5 are items that are set through automatic extraction by the parameter extraction unit 11, the items surrounded by the symbol a2 in FIG. 5 are items that are set through automatic detection by the parameter variation detection unit 13, and the items surrounded by the symbol b in FIG. 5 are items that are set by the designation unit 52 in accordance with input operations by the application administrator, developer, etc.
[0045] FIG. 6 is a flowchart illustrating an example of a processing procedure performed by a data processing device according to an embodiment of the present invention. First, in the first stage (symbol a in Figure 6), each parameter extraction unit extracts candidates for the type and value range of the parameter to be controlled from each management file D1 to D4, i.e., specifications, contracts, and configurations of the application, access network, core network, and server, and passes them to each parameter collection unit along with information on the extraction source (S11).
[0046] Each parameter collection unit sets the initial value of the Active flag associated with the parameter candidate extracted in S11 to "No" (S12).
[0047] A user, administrator, developer, or the like selects a parameter to be controlled by the intent-based resource manager 51 from the candidates extracted in S11 and performs an input operation on the resource management device 100 to designate it as a candidate parameter to be controlled. The designation unit 52 accepts this input operation and sets the Active flag for the parameter designated by the input operation to "Yes." Each parameter collection unit associates the type of this parameter, the value range, the extraction source, and the Active flag, and passes them to the intent-based resource manager 51 (S13).
[0048] Next, in the second stage (reference symbol b in FIG. 6), the intent-based resource manager 51 controls the parameters associated with the Active flag set to "Yes" according to the intent (S21).
[0049] In addition, each parameter change detection unit reads each management file D1 to D4, i.e., the application, access network, core network, server configuration, etc. (S22), and detects the difference between the current content and the content at the previous point in time, a predetermined time before the current point in time (S23).
[0050] If the difference detected in S23 is a new parameter or its variation that did not exist at the previous time point, each parameter variation detection unit registers this parameter as a new parameter to be controlled and sets the initial value of the Active flag related to this parameter to "No." Each parameter variation detection unit presents information related to this parameter to the user, administrator, developer, etc. (S24).
[0051] A user, an administrator, a developer, or the like performs an input operation on the resource management device 100 to select (specify) a parameter to be controlled by the intent-based resource manager 51 from the presented candidates. The specification unit 52 accepts this input operation and sets the Active flag associated with the selected parameter to “Yes” in response to the input operation (S25).
[0052] FIG. 7 is a diagram showing a specific example of parameter extraction. Here, an example will be described in which, in the first stage, parameter candidates are extracted by the parameter extraction unit 41 from the cloud service contract and specifications in the management file D4.
[0053] In the example shown in Figure 7, the first parameter is the "instance type" described in the cloud service contract / specification, which is extracted as a candidate type of parameter to be controlled, "Small" and "Large" described in the cloud service contract / specification, which are extracted as the value range of the parameter to be controlled, and the cloud service contract / specification is extracted as the source of candidate parameters to be controlled, and an example is shown in which the Active flag is set to "Yes" by a cloud administrator / developer, etc. (reference number P4 in Figure 7).
[0054] Furthermore, in the example shown in Figure 7, as the second parameter, the "external connection option" described in the cloud service contract and specifications is extracted as a candidate type of parameter to be controlled, "512kbps" and "1024kbps" described in the cloud service contract and specifications are extracted as the value range of the parameter to be controlled, and the cloud service contract and specifications are extracted as the candidate source of the parameter to be controlled, and an example is shown in which the Active flag is set to "Yes" by a cloud administrator, developer, etc. (reference number P4 in Figure 7).
[0055] The items surrounded by the symbol a in Figure 7 are items that are set through automatic extraction by the parameter extraction unit 41, and the items surrounded by the symbol b in Figure 7 are items that are set by the designation unit 52 in accordance with input operations by a cloud administrator or the like.
[0056] FIG. 8 is a diagram showing a specific example of parameter variation detection. Here, we will explain an example in which, in the second stage, the parameter variation detection unit 23 detects a parameter variation from the access network configuration in the management file D2, and new candidates for the parameter type or parameter value range are extracted in accordance with this variation.
[0057] In the example shown in Figure 8, the parameter variation detection unit 23 detects variations in the type of parameters and variations in the value of parameters described in the management file at different times by comparing the contents described in the device's access network configuration (c(t1) to c(t4) in Figure 8) between times before time t1 and the time period from times t1 to t4 after this time.
[0058] The parameter variation detection unit 23 can detect that the above configuration at time t1 differs in that it contains a new parameter “Wi-Fi” and its value (ID) “Wi-Fi-1” that were not described in the above configuration at times prior to time t1.
[0059] The parameter variation detection unit 23 can detect that the above config at time t2, which is after time t1, differs in that it contains a new parameter “Wi-Fi” and its value “Wi-Fi-2”, which were not described in the above config at the time before time t1.
[0060] The parameter variation detection unit 23 can detect that the above configuration at time t3, which is after time t2, differs in that it contains a new parameter ``5G'' (5th Generation) and its value ``Mobile-A'', which were not described in the above configuration before time t1.
[0061] The parameter variation detection unit 23 can detect that the above config at time t4, which is after time t3, differs in that it contains a new parameter “Ether Network” and its value “Local_Connection_a,” which were not described in the above config before time t1.
[0062] As a result of the above detection, it is detected that the new parameters before time t1 and in the time period from time t1 to time t4 after time t1 are "Wi-Fi", "5G", and "Ether Network". The range of possible values for the parameter "Wi-Fi" is "Wi-Fi-1" or "Wi-Fi-2". The value that the new parameter "5G" can take is "Mobile-A", and the value that the new parameter "Ether Network" can take is "Local_Connection_a". These new parameters and their values become candidates for new parameters to be controlled by the intent-based resource manager 51.
[0063] In addition, when a user or an administrator / developer (reference symbol P2 in FIG. 8) performs an input operation on the resource management device 100 to select (specify) a parameter from among the new parameter candidates that the intent-based resource management unit 51 will actually control, the specification unit 52 sets the Active flag associated with the parameter selected by this input operation to “Yes.”
[0064] The items surrounded by the symbol a in Figure 8 are items that are set after detection by the parameter variation detection unit 23, and the items surrounded by the symbol b in Figure 8 are items that are set by the designation unit 52 in accordance with input operations by an access network administrator or the like.
[0065] FIG. 9 is a block diagram showing an example of the hardware configuration of a resource management device according to an embodiment of the present invention. 9, the resource management device 100 according to the above embodiment is configured, for example, by a server computer or a personal computer, and has a hardware processor 111A such as a CPU (Central Processing Unit). A program memory 111B, a data memory 112, an input / output interface 113, and a communication interface 114 are connected to this hardware processor 111A via a bus 115.
[0066] The communication interface 114 includes, for example, one or more wireless communication interface units, and enables transmission and reception of information to and from the communication network NW. As the wireless interface, for example, an interface that adopts a low-power wireless data communication standard such as a wireless LAN (Local Area Network) is used.
[0067] The input / output interface 113 is an input device attached to the resource management device 100 and used by a user or the like. 2 00 and output device 3 00 is connected. The input / output interface 113 is an input device such as a keyboard, a touch panel, a touchpad, a mouse, etc. 2 The device receives operation data input by a user through the device 00 and outputs the output data to an output device including a display device using a liquid crystal or organic EL (Electro Luminescence) display. 3 00 and display it. 2 00 and output device 300 may be a device built into the resource management device 100, or may be an input device and an output device of another information terminal that can communicate with the resource management device 100 via the network NW.
[0068] The program memory 111B is a non-transitory tangible storage medium that is a combination of a non-volatile memory that can be written to and read from at any time, such as a hard disk drive (HDD) or a solid state drive (SSD), and a non-volatile memory such as a read only memory (ROM), and stores programs necessary to execute various control processes, etc., according to one embodiment.
[0069] The data memory 112 is a tangible storage medium that is, for example, a combination of the above-mentioned nonvolatile memory and a volatile memory such as RAM (Random Access Memory), and is used to store various data acquired and created during various processing steps.
[0070] A resource management device 100 according to one embodiment of the present invention can be configured as a data processing device having the parameter extraction units, parameter collection units, and parameter variation detection units shown in FIG. 1 as software-based processing function units.
[0071] Each information storage unit used as a working memory or the like by each unit of the resource management device 100 can be configured by using the data memory 112 shown in Fig. 9. However, these configured storage areas are not essential components within the resource management device 100, and may be areas provided in, for example, an external storage medium such as a USB (Universal Serial Bus) memory, or a storage device such as a database server located in the cloud.
[0072] The processing function units in each of the parameter extraction units, parameter collection units, and parameter variation detection units can all be realized by reading and executing a program stored in the program memory 111B by the hardware processor 111A. Note that some or all of these processing function units may be realized in various other forms, including integrated circuits such as an application specific integrated circuit (ASIC) or a field-programmable gate array (FPGA).
[0073] The methods described in each embodiment may be stored as a program (software means) that can be executed by a computer on a recording medium such as a magnetic disk (e.g., a floppy disk, a hard disk, etc.), an optical disk (e.g., a CD-ROM, a DVD, an MO, etc.), or a semiconductor memory (e.g., a ROM, a RAM, a flash memory, etc.), or may be transmitted and distributed via a communication medium. The program stored on the medium also includes a configuration program that configures the software means (including not only execution programs but also tables and data structures) that the computer executes. The computer that realizes this device reads the program stored on the recording medium and, in some cases, configures the software means using the configuration program, and executes the above-described processing by having the operation controlled by this software means. The term "recording medium" as used herein is not limited to a storage medium for distribution, but also includes a storage medium such as a magnetic disk or semiconductor memory installed inside the computer or in a device connected via a network.
[0074] The present invention is not limited to the above-described embodiments, and various modifications can be made in the implementation stage without departing from the spirit of the invention. Furthermore, the embodiments may be implemented in appropriate combinations, in which case the combined effects can be obtained. Furthermore, the above-described embodiments include various inventions, and various inventions can be extracted by combining selected elements from the disclosed elements. For example, if the problem can be solved and the desired effect can be obtained even if some elements are deleted from all elements shown in the embodiments, the configuration from which these elements are deleted can be extracted as an invention. [Explanation of symbols]
[0075] 100...Resource management device 11, 21, 31, 41...Parameter extraction section 12...Application parameter collection section 13, 23, 33, 43...Parameter fluctuation detection section 22...Access network parameter collection unit 32...Core network parameter collection unit 42...Cloud parameter collection unit 51...Intent-based resource management unit 52...Specified part
Claims
1. an extracting unit that extracts, from a file describing the content of a service to be provided, resources that can be set as resources to be used in providing the service and parameter candidates to be used in controlling the resources, the file being related to control of resources to be used in providing the service; a designation unit that accepts designation of resources and parameters to be used in providing the service from among the resources and parameters extracted by the extraction unit; A data processing device comprising:
2. The extraction unit When there is a difference between the content written in the file at a first timing and the content written in the file at a second timing after the first timing, further extracting candidates for new resources to be used in providing the service and candidates for new parameters to be used in controlling the resources that were not extracted from the file at the first timing.
2. The data processing device according to claim 1.
3. The extraction unit extracting from the file candidate types of the parameters used in providing the service and candidate values that the parameters of the candidate types can take; 2. The data processing device according to claim 1.
4. The extraction unit further extracting candidates for the type of the new parameter and candidates for the value that the parameter of the type can take; 3. The data processing device according to claim 2.
5. 1. A method performed by a data processing device, comprising: extracting, by an extraction unit of the data processing device, from a file in which the content of the service to be provided is described and which relates to control of resources to be used in providing the service, candidate resources that can be set as resources to be used in providing the service and candidate parameters to be used in controlling the resources; receiving, by a designation unit of the data processing device, designation of resources and parameters to be used in providing the service from among the extracted resources and parameters; A data processing method comprising:
6. A data processing program that causes a processor to function as each unit of the data processing device according to any one of claims 1 to 4.
Citation Information
Patent Citations
Setting control device, setting control method, and setting control program
JP2013080275A
Resource determination device, resource determination method and resource determination processing program
JP2019087105A
System and method for distributed resource management
US20170317945A1