WO2019064678A1

WO2019064678A1 - Management device and network architecture control method

Info

Publication number: WO2019064678A1
Application number: PCT/JP2018/018547
Authority: WO
Inventors: 宏司坪内; 榑林　亮介; アシックカーン; マルケースジョアントリエイ
Original assignee: 株式会社Ｎｔｔドコモ
Priority date: 2017-09-26
Filing date: 2018-05-14
Publication date: 2019-04-04
Also published as: JP2021010042A

Abstract

A management device (60) deploys a network function unit (NF) on the basis of a deployment request for an NF constituting a slice, said deployment request including the NF type corresponding to the deployment request and NF requirements which include an isolation requirement related to non-sharing and associated with the NF. The management device (60) comprises a network architecture control unit (62S) that, on the basis of at least the NF type, the requirements including the isolation requirement, and pre-stored usable computer information, as well as deployment information relating to pre-stored deployed NF and/or infrastructure, deploys to a usable computer an NF corresponding to the deployment request, such that the isolation requirement is satisfied.

Description

Management device and network configuration control method

The present invention relates to a management device and a network configuration control method.

In 3GPP TS23.501 (5G system), it is considered to divide the system into logical networks (slices) and to assign slices for each service (see Non-Patent Document 1). Also, when configuring one slice, one or more network function units (hereinafter referred to as “NF”) suitable for the requirements for providing a service corresponding to the slice (slice requirements) It is considered to configure the slice. At this time, one or more NFs may be shared by multiple slices.

As a requirement of a certain slice, it is assumed that the NFs constituting the one slice are not desired to be shared between the different slices in order to exclude the influence from the different slices. Also, if you do not want to share, there are several levels to consider. For example, as a requirement for non-sharing associated with NF (hereinafter referred to as "isolation requirement"), "do not share both NF and the computing device that operates this NF with different slices", "do not share NF with different slices However, there may be a requirement that “the computing device that operates the NF can be shared between different slices” and “the NF can be shared between different slices”.

However, under the present circumstances, techniques for appropriately controlling the network configuration in accordance with the isolation requirements as described above have not been widely studied.

The present invention has been made to solve the above-mentioned problems, and it is an object of the present invention to appropriately control a network configuration in accordance with isolation requirements.

A management apparatus according to an embodiment of the present invention is an NF type indicating a type of an NF corresponding to a deployment request, which is a deployment request of a network function unit (NF) configuring a slice that is a virtual network on a network infrastructure, A request receiving unit for receiving the deployment request including at least a requirement of the NF including an isolation requirement that is a requirement related to non-sharing accompanying the NF, and at least the deployment request accepted by the request accepting unit Based on said NF type contained in and said requirements including said isolation requirements, pre-stored available computing device information, and deployment information regarding pre-stored deployed NF and / or infrastructure. Use NF according to the deployment request to meet the isolation requirement Comprising a network configuration control unit for deployment in Noh computing device. Note that “deployment” in this case includes the creation of new products and the diversion of existing products.

In the above management apparatus, the request receiving unit is a deployment request of the network function unit (NF) configuring a slice that is a virtual network on the network infrastructure, and an NF type indicating the type of the NF corresponding to the deployment request, Receiving the deployment request including the requirement of the NF including the isolation requirement that is a requirement regarding non-sharing associated with the NF, and the network configuration control unit receiving at least the request accepted by the request accepting unit. Based on the NF type included in the deployment request and the requirements including the isolation requirement, pre-stored available computing device information, and deployment information regarding pre-stored deployed NF and / or infrastructure. To meet the above isolation requirements, and The F, deploying the available computing devices. In this way, when deploying an NF based on the deployment request of the NF configuring the slice, it is possible to use the NF according to the deployment request so as to satisfy the isolation requirement which is the requirement for non-sharing associated with the NF By installing in a computing device, the network configuration can be appropriately controlled according to the isolation requirements.

According to the present invention, the network configuration can be appropriately controlled according to the isolation requirements.

It is a figure showing the logical composition of the communication system concerning the embodiment of the invention. It is a figure showing physical composition of a communication system concerning an embodiment of the invention. It is a functional block block diagram of a management apparatus. It is a figure which shows an example of the information memorize | stored in an availability requirement table. It is a figure which shows an example of the information memorize | stored in an available NF grade table. It is a figure which shows an example of the information memorize | stored in an isolation requirement table. It is a figure which shows an example of the information memorize | stored in a computing device table. It is a figure which shows an example of the information memorize | stored in the NF / infrastructure information table of 1st Embodiment. It is a figure which shows an example of the information memorize | stored in NF connection information table. It is a flowchart which shows the process performed by a management apparatus. It is a figure which shows an example of the information memorize | stored in the NF / infrastructure information table of 2nd Embodiment. It is a figure which shows another structural example of a management apparatus. It is a figure which shows an example of the hardware constitutions of a management apparatus.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.

First Embodiment
First, the logical configuration and physical configuration of the communication system 1 including the management apparatus according to the present invention will be described with reference to FIG. 1 and FIG.

As shown in FIG. 1, in the communication system 1 as a logical configuration, slices (here, slices # 1 and # 2) are formed for each service provided to the UE 30, and each slice provides a service corresponding to the slice. Configured by one or more NFs (network function units) 10 suitable for the requirements (slice requirements) to In the example of FIG. 1, slice # 1 is configured to include NF1 to NF4, slice # 2 is configured to include NF1, NF2, NF5, and NF6, and NF1 and NF2 shown by thick lines in FIG. , Shared by # 2. Also, the communication system 1 is provided with an NRF (Network Repository Function) 20 that centrally manages connection information of each NF, and each NF inquires of the NRF 20 when communicating with other NFs and communicates with the NF of the communication destination NF. Get connection information.

As shown in FIG. 2, as a physical configuration, the communication system 1 includes a management device 60, the above-described NRF 20, UE 30, an access device 70 (for example, a base station, e-NodeB, etc.), the above-described NF 10, and a computing device 50. And they can be communicated with each other via the network 80. The UE 30 is connected to the network 80 via the access device 70. The NF 10 and the computing device 50 are housed in data centers 40 provided at various locations. Further, the NF 10 is configured in one or both of virtual NF 10 A virtually generated in a plurality of in the computing device 50 and physical NF 10 B provided in a form of occupying a device equivalent to the computing device 50. Be done.

Next, the functional block configuration of the management device 60 will be described using FIG. As shown in FIG. 3, the management apparatus 60 includes a request receiving unit 61, a use NF determination unit 62, a shareability determination unit 63, an NF deployment unit 64, an NRF registration unit 65, an availability requirement table 66, and an available NF grade table 67. , An isolation requirement table 69A, a computing device table 69B, and a deployed NF / infrastructure information table 68. The outline of each functional unit will be described below.

The request receiving unit 61 is a functional unit for receiving a deployment request including an NF type indicating the type of the NF desired to be deployed, and a requirement required for the NF.

The use NF determination unit 62 uses the NF grade based on the NF type and requirements included in the deployment request accepted by the request acceptance unit 61 and the information of the availability requirement table 66 and the available NF grade table 67 described later. It is a functional unit that determines a candidate. Further, the use NF determination unit 62 may determine one NF grade as an NF grade candidate to be used, or may determine a plurality of NF grade candidates. Below, it illustrates about the case where use NF deciding part 62 decides one NF grade.

Although details will be described later, the sharing availability determination unit 63 derives the sharing type of the NF from the isolation requirement, and determines whether the NF related to the NF grade candidate determined above can be shared according to the obtained sharing type. Is a functional unit that executes processing such as determination of

The NF deployment unit 64 is a functional unit that deploys an NF that satisfies the above requirements by newly generating an NF or using an existing NF according to the determination result by the shareability determination unit 63. Also, the NF deployment unit 64 adds / updates the deployed NF instance information to the NF / infrastructure information table 68.

The use NF determination unit 62, the sharing availability determination unit 63, and the NF deployment unit 64 described above correspond to the “network configuration control unit” described in the claims, and at least a requirement including the NF type and the isolation requirement. To meet the isolation requirements based on pre-stored available computing device information and information regarding pre-stored deployed NF and / or infrastructure (hereinafter referred to as “deployed NF / infrastructure information”) , Corresponds to a functional unit that deploys an NF corresponding to a deployment request to an available computing device.

The NRF registration unit 65 registers the NF type, the slice identification auxiliary information, and the connection information in an NF connection information table 21 described later of the NRF 20 so that the newly generated NF and the diverted NF can be used.

For example, as shown in FIG. 4, the availability requirement table 66 is a table storing information in which the availability requirement and the redundant configuration are associated.

The available NF grade table 67 is a table that is provided for each NF type and stores information in which requirements required for the NF for the NF type are associated with available NF grades. For example, FIG. 5 shows an example where the NF type is mobility management function (AMF), and as a requirement required for the NF, an availability requirement (specifically, a redundant configuration corresponding to the availability requirement) And functional requirements (standards A to C, unique A, B) are illustrated, and available NF grades (grades 1 to 9) corresponding to these requirements are shown.

The isolation requirement table 69A, for example, as shown in FIG. 6, is a table that defines the correspondence between the isolation requirement and the share type, and the description related to each share type is also described. Here, the isolation requirement "low" is associated with a sharing type "A" that allows the NF to be shared between different slices, and the isolation requirement "medium" does not allow the NF to share with different slices, but the NF A computing device to be operated is associated with a sharing type “B” that enables sharing between different slices, and an isolation requirement “high” is a sharing type that does not share both the NF and the computing device that operates the NF with different slices It is mapped to "C".

The computing device table 69B is a table storing information on available computing devices. For example, as shown in FIG. 7, the region name, area name, data center name, computing device as information on available computing devices Information such as ID, inter-slice sharing type, and dedicated slice identification auxiliary information is stored in association with each other.

The NF / infrastructure information table 68 is a table storing the already deployed NF / infrastructure information (corresponding to “deployment information” in the claims), for example, as shown in FIG. As information on infrastructure, information such as region name, area name, data center name, computing device ID, NF instance ID, NF specification ID, used network (used band / available band), shared type is stored in association with each other. There is.

Returning to FIG. 3, the NRF 20 includes the NF connection information table 21 illustrated in FIG. 9 in order to centrally manage the connection information of each NF, and the NF connection information table 21 includes NF types and slice identification auxiliary information. And NF connection information are stored in association with each other.

Next, processing (processing according to the network configuration control method of the present invention) executed by the management device 60 will be described along the flowchart of FIG.

The process of FIG. 10 is triggered by, for example, the deployment request of the NF from the administrator or the upper apparatus to the management apparatus 60 as a trigger. The above deployment request is given, as input information, an NF type to be deployed, slice identification auxiliary information, connection information to the NF, and requirements required for the NF (including isolation requirements).

As the above-mentioned NF type, a mobility management function (AMF), an authentication function (AUSF), a session management function (SMF), a data transfer function (UPF) and the like are exemplified. The above-mentioned slice identification auxiliary information is information used by the user at the time of slice access, corresponds to NSSAI described in 3GPP TS 23.501 (Table 5.15.2.2-1), and eMBB, URLLC, MIoT, etc. are exemplified. An IP address, FQDN, etc. are illustrated as connection information to said NF. The requirements for the above NF include: functional requirements (eg, standard, no standard / no mobility, standard and predetermined customization functions etc.), availability requirements (eg, low, medium, high), isolation requirements (eg, Low, medium, high), connected network requirements (eg, 100M, 1G, 10G etc.), location requirements (eg, specified data center specified, specified area specified, specified region specified, not specified etc) It can be mentioned. Among the above, the slice identification auxiliary information and the connection information to the NF may be generated as output information by the management device 60 instead of being input to the management device 60.

In step S1 of FIG. 10, the request receiving unit 61 receives a deployment request including the above-described NF type and requirements.

In the next step S2, the use NF determination unit 62 determines the NF grade to be used, for example, as follows. That is, the use NF determination unit 62 first determines a redundant configuration from the input availability requirement with reference to the availability requirement table 66 of FIG. 4. Next, the use NF determination unit 62 determines the available NF grade table 67 (FIG. 5) to be referred to from the input NF type, and refers to the available NF grade table 67 to enter the input function. Extract an NF grade that meets the requirements and the redundant configuration determined in step S21. Furthermore, the use NF determination unit 62 determines the lowest NF grade among the extracted NF grades as the NF grade to be used.

In the next step S3, the sharing determination unit 63 derives the sharing type of the NF from the input isolation requirement with reference to the isolation requirement table 69A of FIG. 6, and in the next step S4, the sharing type To determine the

If it is determined in step S4 that the sharing type = C (non-sharing), the process proceeds to step S5, and the sharing permission determination unit 63 refers to the computing device table 69B of FIG. Yes, and “the dedicated slice identification auxiliary information corresponds to the requested one or described as being not used”, and the computing device satisfying the location requirement is extracted, and the NF deploying unit 64 extracts The NF is newly deployed to the calculated computing device (calculating device for specific slice occupancy). Note that although available NW information is omitted in the computing device table 69B, available NW information is added to the computing device table 69B, and the available NW information satisfies the connection destination NW requirements of the NF. The following condition may be added to extract the computing device. In addition, when a plurality of computing devices are extracted, one computing device that newly generates an NF may be selected according to, for example, any of the following selection criteria.
・ Select one randomly.
• Select the computing device with the lowest usage rate.

If it is determined in step S4 that the sharing type = B (multiple slices can share only the computing device), the process proceeds to step S6, and the sharing permission determination unit 63 refers to the computing device table 69B in FIG. A computing device which is “type of sharing between slices = sharing” and satisfies the location requirement is extracted, and the NF deploying unit 64 newly deploys the NF to the extracted computing device (the computing device for slice sharing). As in step S5 described above, the available NW information is added to the computing device table 69B, and a condition that the available NW information satisfies the connection destination NW requirements of the NF is added, and the computing device is extracted May be When a plurality of computing devices are extracted, a computing device that newly generates an NF may be selected according to any of the selection criteria exemplified in step S5.

Furthermore, if it is determined in step S4 that the sharing type = A (multiple slices can share the NF), the process proceeds to step S7, and the sharing availability determination unit 63 refers to the deployed NF / infrastructure information table 68 of FIG. Then, it is determined whether or not the NF grade NF to be used is already deployed, and if deployed, it is determined whether the NF can be shared with other slices. In addition, in this step S7, when it is determined that sharing is possible, for example, the shared NF is selected by the following procedure.

The deployed NF (NF instance ID in FIG. 8) satisfying these requirements is searched from the deployed NF / infrastructure information table 68 of FIG. Show an example of determining whether sharing is possible.

NF specification ID “AMF 8”, location requirement “region name = Asia, area name = jp-east”, connection destination network requirement “for management communication = 10 M, for data communication = N / A (not used), for control communication = Assuming that “100 M” is input as a requirement, the following two (ie, region name, area) surrounded by a bold frame in FIG. 8 are provided from the deployed NF / infrastructure information table 68 of FIG. The name, data center name, computing device ID, and NF instance ID are as follows:
・ Asia, jp-east, tokyo1, CN1, ins1
・ Asia, jp-east, tokyo1, CN2, ins2
When a plurality of shareable candidates are extracted in this way, the shared NF is selected, for example, according to any of the following selection criteria.
・ Select one randomly.
• In the network used, select the place with the least bandwidth.
Select the place where the usage rate of the computing device is the lowest.

If it is determined in step S7 that the NF is not shareable or not deployed with other slices, the process proceeds to step S6 described above, and the NF deployment unit 64 uses the NF grade NF to be used in the computing device satisfying the location requirements. Newly deploy.

On the other hand, when the NF can be shared with another slice in step S7, the process proceeds to step S8, and the NF deploying unit 64 sets the deployed NF setting information stored in the deployed NF / infrastructure information table 68. Make corrections as necessary. For example, it is set to generate predetermined management information (such as traffic flow rate information) for the requested slice identification auxiliary information.

In the next step S9, the NF deploying unit 64 adds and updates deployed NF instance information to the deployed NF / infrastructure information table 68.

Then, in step S10, the NRF registration unit 65 uses the NF connection information table 21 of FIG. 9 stored by the NRF 20 to enable the newly generated NF and the diverted NF, and the NF type, slice identification auxiliary information, and Register connection information.

In the first embodiment described above, when deploying an NF based on a deployment request of an NF configuring a slice, a computing device that can be used to satisfy the isolation requirement that is a requirement for non-sharing associated with the NF. In addition, by deploying the NF according to the deployment request, it is possible to control the network configuration appropriately according to the isolation requirement.

Second Embodiment
In the second embodiment, an example in which another information is used as an isolation requirement will be described. For example, as isolation requirements, it is desirable to share NF among slices owned by the same mobile network operator (hereinafter referred to as "MNO") as much as possible, but slices owned by MNO and virtual mobile communications It is conceivable that the user does not want to share the NF from the viewpoint of security, service quality assurance, etc. with a slice owned by a mobile virtual network operator (hereinafter referred to as "MVNO").

The above-mentioned case “I want to share NF as much as possible” corresponds to the case of isolation requirement = low described in the first embodiment, so in the second embodiment, in order to realize the isolation requirement as described above As a parameter of the deployment request input to the management device 60, "affinity group ID" is newly introduced. Specifically, when it is desired to share NF among slices as much as possible, the same affinity group ID as the slice to be shared is specified as a parameter of the deployment request at the time of deployment request of the NF related to the relevant slice. When it is desired not to share the NF as much as possible, at the time of the deployment request of the NF related to the slice, an affinity group ID different from the slice not to be shared is specified as a parameter of the deployment request.

As shown in FIG. 11, in the deployed NF / infrastructure information table 68S in the second embodiment, in addition to the information in the deployed NF / infrastructure information table 68 (FIG. 8) of the first embodiment, “affinity group ID "" Information is stored in association with each other.

In the second embodiment, the process in FIG. 10 is processed as follows in step S7, which is performed when it is determined in step S4 that sharing type = A (multiple slices can share NF). That is, in step S7, when the NF grade NF to be used is already deployed and it is determined that the NF can be shared with other slices, the “NF specification ID” used in the first embodiment, In addition to the “location requirements” and the “destination network requirements”, the “affinity group ID” is used as input information, and the deployed NFs satisfying these requirements (for example, the affinity group IDs match) (NF instance ID in FIG. 11) ) Is retrieved from the deployed NF / infrastructure information table 68S of FIG.

As described above, in the second embodiment, when it is desired to share NF among slices as much as possible, the same affinity group ID as the slice to be shared is specified as a deployment request parameter, while sharing NF among slices as possible. If you do not want to make this happen, specify a different affinity group ID from the slice you do not want to share as a deployment request parameter, and then search for the deployed NF with the requirement that "affinity group ID matches". This makes it appropriate to satisfy the isolation requirements such as “I would like to share NF between slices owned by MNO, but not want to share NF between slices owned by MNO and slices owned by MVNO”. Can be deployed.

Further, in the management device 60 of FIG. 3, the NF deployment unit 64 and the NRF registration unit 65 may be cut out as separate devices. For example, as shown in FIG. 12, the NF deployment unit 64 and the NRF registration unit 65 are disposed in another apparatus 60B, and accordingly, the management apparatus 60 of FIG. 3 is configured with an NF descriptor (design information of NF) and an NF setting. It may be configured as a management data generation device 60A that generates data and NRF setting data and passes it to another device 60B. More specifically, an NF descriptor / setting data generation / correction unit 64A and an NRF setting data generation unit 65A are provided in the management data generation apparatus 60A, and the NF descriptor / setting data generation / correction unit 64A is an NF descriptor (NF design information And NF setting data are generated and passed to the NF deployment unit 64 in another device 60B, and the NRF setting data generation unit 65A generates NRF setting data, and passes it to the NRF registration unit 65 in another device 60B. It should be configured as follows. In the case of the configuration as shown in FIG. 12, the management apparatus according to the present invention can be grasped as being configured by the management data generation apparatus 60A and another apparatus 60B, and a part of the management apparatus 60 of FIG. Even when the functional units of the above are cut out to be configured, substantially the same processing can be performed, and similar effects can be obtained.

Furthermore, input information input from the administrator / upper level device to the management device 60 of FIG. 3 is stored in advance as a template in the management device 60, and the information actually input is the template ID and the necessary minimum information. (For example, slice identification auxiliary information and the like) may be selected, and in this case, it is possible to reduce the data amount of input information and to make the processing more efficient. Examples of templates include OpenStack Heat Orchestration Template (HOT), OASIS TOSCA, ETSI NFV VNFD / NSD, and the like.

The block diagrams used in the description of the above embodiments show blocks in functional units. These functional blocks (components) are realized by any combination of hardware and / or software. Moreover, the implementation means of each functional block is not particularly limited. That is, each functional block may be realized by one physically and / or logically coupled device, or directly and / or indirectly two or more physically and / or logically separated devices. It may be connected by (for example, wired and / or wireless) and realized by the plurality of devices.

For example, the management device 60 in the above embodiment may function as a computer that performs the processing of the management device 60 described above. FIG. 13 is a diagram illustrating an example of a hardware configuration of the management device 60. The management device 60 described above may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007 and the like.

In the following description, the term "device" can be read as a circuit, a device, a unit, or the like. The hardware configuration of the management device 60 may be configured to include one or more of the devices shown in the figure, or may be configured without some devices.

Each function in the management device 60 causes the processor 1001 to perform an operation by reading predetermined software (program) on hardware such as the processor 1001, the memory 1002, and the communication by the communication device 1004, the memory 1002 and the storage 1003. It is realized by controlling reading and / or writing of data.

The processor 1001 operates, for example, an operating system to control the entire computer. The processor 1001 may be configured by a central processing unit (CPU: Central Processing Unit) including an interface with a peripheral device, a control device, an arithmetic device, a register, and the like. For example, each functional unit of the management device 60 may be realized including the processor 1001.

The processor 1001 also reads a program (program code), a software module, data, and the like from the storage 1003 and / or the communication device 1004 to the memory 1002, and executes various processing according to these. As a program, a program that causes a computer to execute at least a part of the operations described in the above embodiments is used. For example, each functional unit of the management device 60 may be realized by a control program stored in the memory 1002 and operated by the processor 1001, or may be realized similarly for other functional blocks. The various processes described above have been described to be executed by one processor 1001, but may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may be transmitted from the network via a telecommunication line.

The memory 1002 is a computer readable recording medium, and includes, for example, at least one of a ROM (Read Only Memory), an EPROM (Erasable Programmable ROM), an EEPROM (Electrically Erasable Programmable ROM), and a RAM (Random Access Memory). It may be done. The memory 1002 may be called a register, a cache, a main memory (main storage device) or the like. The memory 1002 may store a program (program code), a software module, etc. that can be executed to implement the method according to an embodiment of the present invention.

The storage 1003 is a computer readable recording medium, and for example, an optical disc such as a CD-ROM (Compact Disc ROM), a hard disc drive, a flexible disc, a magneto-optical disc (eg, a compact disc, a digital versatile disc, a Blu-ray A (registered trademark) disk, a smart card, a flash memory (for example, a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, and the like may be used. The storage 1003 may be called an auxiliary storage device. The above-mentioned storage medium may be, for example, a database including the memory 1002 and / or the storage 1003, a server or any other suitable medium.

The communication device 1004 is hardware (transmission / reception device) for performing communication between computers via a wired and / or wireless network, and is also called, for example, a network device, a network controller, a network card, a communication module, or the like. For example, each functional unit of the management device 60 described above may be realized including the communication device 1004.

The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, and the like) that receives an input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that performs output to the outside. The input device 1005 and the output device 1006 may be integrated (for example, a touch panel).

Further, each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured by a single bus or may be configured by different buses among the devices.

Further, the management device 60 includes hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), and a field programmable gate array (FPGA). It may be configured, and part or all of each functional block may be realized by the hardware. For example, processor 1001 may be implemented in at least one of these hardware. The configuration other than the management device 60 illustrated in FIG. 1 may have the same configuration as that of the communication terminal.

As mentioned above, although this embodiment was described in detail, it is clear for persons skilled in the art that this embodiment is not limited to the embodiment described in this specification. This embodiment can be implemented as a modification and a change mode, without deviating from the meaning and range of the present invention which become settled by statement of a claim. Therefore, the description of the present specification is for the purpose of illustration and does not have any limitation on the present embodiment.

As long as there is no contradiction, the processing procedure, sequence, flow chart, etc. of each aspect / embodiment described in this specification may be reversed. For example, for the methods described herein, elements of the various steps are presented in an exemplary order and are not limited to the particular order presented.

The input / output information may be stored in a specific place (for example, a memory), or may be managed by a management table. Information to be input or output may be overwritten, updated or added. The output information may be deleted. The input information or the like may be transmitted to another device.

The determination may be performed by a value (0 or 1) represented by one bit, may be performed by a boolean value (Boolean: true or false), or may be compared with a numerical value (for example, a predetermined value). Comparison with the value).

Each aspect / embodiment described in this specification may be used alone, may be used in combination, and may be switched and used along with execution. In addition, notification of predetermined information (for example, notification of "it is X") is not limited to what is explicitly performed, but is performed by implicit (for example, not notifying of the predetermined information) It is also good.

Software may be called software, firmware, middleware, microcode, hardware description language, or any other name, and may be instructions, instruction sets, codes, code segments, program codes, programs, subprograms, software modules. Should be interpreted broadly to mean applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc.

Also, software, instructions, etc. may be sent and received via a transmission medium. For example, software may use a wireline technology such as coaxial cable, fiber optic cable, twisted pair and digital subscriber line (DSL) and / or a website, server or other using wireless technology such as infrared, radio and microwave When transmitted from a remote source, these wired and / or wireless technologies are included within the definition of transmission medium.

The information, signals, etc. described herein may be represented using any of a variety of different techniques. For example, data, instructions, commands, information, signals, bits, symbols, chips etc that may be mentioned throughout the above description may be voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or photons, or any of these May be represented by a combination of

In addition, the information, parameters, and the like described in the present specification may be represented by absolute values, may be represented by relative values from predetermined values, or may be represented by corresponding other information. .

Mobile communication terminals may be subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, by those skilled in the art. It may also be called a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable term.

The terms "determining", "determining" as used herein may encompass a wide variety of operations. "Judgment", "decision" are, for example, judging, calculating, calculating, processing, processing, deriving, investigating, looking up (for example, a table) (Searching in a database or another data structure), ascertaining may be regarded as “decision”, “decision”, etc. Also, "determination" and "determination" are receiving (e.g. receiving information), transmitting (e.g. transmitting information), input (input), output (output), access (accessing) (for example, accessing data in a memory) may be regarded as “judged” or “decided”. Also, "judgement" and "decision" are to be considered as "judgement" and "decision" that they have resolved (resolving), selecting (selecting), choosing (choosing), establishing (establishing), etc. May be included. That is, "judgment" "decision" may include considering that some action is "judged" "decision".

As used herein, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

As long as "includes", "including", and variations thereof are used in the present specification or claims, these terms as well as the term "comprising" Is intended to be comprehensive. Further, it is intended that the term "or" as used in the present specification or in the claims is not an exclusive OR.

In the present specification, a plurality of devices are also included unless it is a device clearly having only one context or technically. Throughout this disclosure, unless the context clearly indicates otherwise, it is intended to include the plural.

DESCRIPTION OF SYMBOLS 1 communication system, 10 ... NF, 20 ... NRF, 21 ... NF connection information table, 30 ... UE, 40 ... data center, 50 ... calculation apparatus, 60 ... management apparatus, 60A ... management data generation apparatus, 60B ... another Devices 61, request acceptance unit 62, use NF determination unit 62S, network configuration control unit 63, sharing availability determination unit 64, NF deployment unit 64A, NF descriptor, setting data generation / modification unit 65,. NRF registration unit, 65A: NRF setting data generation unit, 66: availability requirement table, 67: available NF grade table, 68, 68S: deployed NF / infrastructure information table, 69A: isolation requirement table, 69B: computing device table , 70: access device, 80: network, 1001: processor, 1002: memory, 1003: stress Di-, 1004 ... communication equipment, 1005 ... input device, 1006 ... output device, 1007 ... bus.

Claims

It is a deployment request of a network function unit (NF) constituting a slice that is a virtual network on a network infrastructure, and an NF type indicating the type of the NF corresponding to the deployment request, and a requirement regarding non-sharing associated with the NF A request receiving unit that receives the deployment request including the requirements of the NF including a certain isolation requirement;
The requirement including at least the NF type and the isolation requirement included in the deployment request received by the request receiving unit, the pre-stored available computing device information, and the pre-stored deployment information A network configuration control unit for deploying an NF according to the deployment request to an available computing device so as to satisfy the isolation requirement based on deployment information regarding at least one of the NF and the infrastructure;
Management device provided with
The NF requirements include a location requirement that indicates the location of the computing device on which the NF is deployed,
The network configuration control unit
If the isolation requirement corresponds to the requirement not to share both the NF and the computing device that operates the NF with different slices, newly deploy the NF on the computing device for satisfying the location requirement and occupying a specific slice. ,
In order to satisfy the location requirements and to be shared by multiple slices, if the isolation requirement does not allow the NF to be shared with different slices, but the computing device that operates the NF corresponds to the requirement to be able to be shared between different slices. Deploy a new NF on a computing device,
The management device according to claim 1.
The network configuration control unit
If the isolation requirement corresponds to a requirement that allows NFs to be shared between different slices, the existing requirement based on at least the requirement including the location requirement, the available computing device information, and the deployment information It is judged whether the NF can be shared or not, and depending on the judgment result, the NF is newly deployed in a computing device for diverting the existing NF or meeting the location requirements and sharing in multiple slices. Deploy the NF according to the deployment request,
The management device according to claim 2.
The network configuration control unit
An affinity group for identifying an affinity group consisting of a plurality of NF-shareable slices, which is further included in the deployment request, when the isolation requirement corresponds to a requirement for enabling the NF to be shared between different slices. Based on the identification information, determine whether it is possible to share the existing NF,
The management apparatus according to claim 3.
A network configuration control method executed by a management device in a network, comprising:
It is a deployment request of a network function unit (NF) constituting a slice that is a virtual network on a network infrastructure, and an NF type indicating the type of the NF corresponding to the deployment request, and a requirement regarding non-sharing associated with the NF Accepting the deployment request, including the requirements of the NF including certain isolation requirements;
At least the requirements included the NF type and the isolation requirements included in the received deployment request, the pre-stored available computing device information, and at least the pre-stored deployed NF and infrastructure. Deploying an NF corresponding to the deployment request to an available computing device to meet the isolation requirement based on deployment information on one side;
A network configuration control method comprising: