Control device and control method

The control device and method address the challenge of configuring network slices across base stations with varying specifications by using a database to manage resource allocation, enabling automatic slice settings that meet diverse application requirements and ensure optimal network performance.

JP2026083946APending Publication Date: 2026-05-20NTT DOCOMO INC
View PDF 2 Cites 0 Cited by

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
NTT DOCOMO INC
Filing Date
2024-11-08
Publication Date
2026-05-20

AI Technical Summary

Technical Problem

Base stations in a mobile communication network with devices from multiple vendors face challenges in setting network slices due to varying specifications, making it difficult to automatically configure slices that meet diverse application requirements.

Method used

A control device and method that includes a receiving unit, access unit, setting unit, and writing unit to manage resource allocation and slice configuration across base stations with varying specifications, using a database to ensure compatibility and resource availability.

Benefits of technology

Enables automatic slice settings regardless of vendor-specific differences, ensuring optimal network performance and resource allocation for diverse applications.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2026083946000001_ABST
    Figure 2026083946000001_ABST
Patent Text Reader

Abstract

The slice settings are automatically configured regardless of differences in specifications between vendors. [Solution] A control device according to one embodiment includes: a receiving unit that receives a resource allocation request indicating the resource requirements for providing a slice that supports communication between a base station and a terminal; an access unit that accesses a database in which resource information indicating the allocation of resources in each of the multiple cells that each of the multiple base stations has is recorded; a setting unit that sets up a slice that supports communication between the base station and the terminal in a manner corresponding to the type of base station that is shown to satisfy the requirements according to the resource information among the multiple base stations; and a writing unit that writes the setting to the database.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to the control of slices in network slicing.

Background Art

[0002] The technology of network slicing in so-called 5G communication is known. For example, Patent Document 1 discloses an invention of a scheduler that considers the allocation without excess or deficiency and efficiency for wireless resources sliced for each service form between CU, DU, and RU. Patent Document 2 discloses an invention of selecting an allocated slice based on the analysis result of records recorded in a database when allocating a predefined slice network to a user terminal.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0004] Base stations in a mobile communication network may have a mixture of devices provided by multiple vendors. Although the general specifications of the base stations are common, the detailed specifications may vary depending on the vendor, and differences in the specifications for each vendor may become a problem when setting slices.

[0005] In contrast, the present invention provides a technology that can automatically set slices regardless of differences in specifications for each vendor.

Means for Solving the Problems

[0006] One aspect of the present disclosure provides a control device comprising: a receiving unit that receives a resource allocation request indicating the requirements for providing a slice that supports communication between a base station and a terminal; an access unit that accesses a database in which resource information indicating the allocation of resources in each of the multiple cells that each of the multiple base stations has is recorded; a setting unit that configures a slice that supports communication between a base station and a terminal in a manner corresponding to the type of base station that is shown by the resource information to satisfy the requirements among the multiple base stations; and a writing unit that writes the configuration to the database.

[0007] Another aspect of the present disclosure provides a control method comprising: receiving a reservation request indicating resource requirements for providing slices that support communication between a base station and a terminal; accessing a database in which resource information is recorded for each of a plurality of base stations indicating resource allocation in each of a plurality of cells that the base station has; configuring slices that support communication between the base station and a terminal in a manner corresponding to the type of base station among the plurality of base stations that the resource information indicates satisfies the requirements; and writing the configuration to the database. [Effects of the Invention]

[0008] According to the present invention, slice settings can be automatically configured regardless of differences in specifications among vendors. [Brief explanation of the drawing]

[0009] [Figure 1] A diagram showing an overview of a 5G network system 1 according to one embodiment. [Figure 2] A diagram illustrating the functions related to control system 3. [Figure 3] A diagram illustrating the functional configuration of NSSMF10. [Figure 4] A diagram illustrating the hardware configuration of the NSSMF10. [Figure 5] A sequence chart illustrating the operation according to one embodiment. [Figure 6] A diagram illustrating resource allocation. [Figure 7] A diagram illustrating the resource partition configuration in a base station gNB. [Figure 8] A diagram illustrating database 111. [Modes for carrying out the invention]

[0010] 1. Structure Figure 1 shows an overview of a 5G network system 1 according to one embodiment. The 5G network system 1 provides network slicing. Network slicing is a technology that divides a 5G network into virtual networks called "slices." Each slice is configured to meet its own requirements or specifications and can satisfy the demands of different applications or services. This allows different services to operate simultaneously on the same physical network without interfering with each other, providing optimal performance.

[0011] The 5G network system 1 comprises a core network 2, a base station gNB, and a user terminal UE. The 5G network system 1 provides a so-called on-demand slice allocation service, allocating slices according to requests from customer CLs. The operator OP is the person who inputs requests from customer CLs into the 5G network system 1. In one example, the customer CL is a service provider that provides services to user terminal UEs, i.e., end users, and the operator OP is a representative of a telecommunications carrier. The operator OP inputs requests into the 5G network system 1 via the operator terminal 50.

[0012] The increasing use of cloud services, AI, and IoT is diversifying the applications of mobile communications in customer communities. The characteristics required of a network differ depending on the application. For example, online gamers require low latency and high bandwidth, while IoT requires a large number of simultaneous connections. Generally, network slicing addresses these different requirements by setting up slices with different characteristics. For instance, in video transmission applications, stable communication is required that does not fall below a throughput limit even during congestion. Furthermore, there is a demand for such stable communication on demand.

[0013] Implementing on-demand provision of such slices presents the following challenges: In real-world systems, base station gNBs provided by multiple vendors coexist within the RAN (Radio Access Network). The specifications of the base station gNB equipment vary significantly from vendor to vendor. In related technologies, it has been difficult to automatically configure slices while absorbing these specification differences. 5G network system 1 addresses this problem.

[0014] Figure 2 shows the functions related to the control system 3. The control system 3 has various functions related to the core network 2, transport network TN, and base station gNB, but here only some functions related to slice resource allocation will be explained. Here, resource allocation in the RAN will be explained in particular. The RAN is a network that provides wireless communication between user terminal UEs (e.g., smartphones or IoT devices) and the core network 2. The RAN is responsible for enabling user terminal UEs to communicate using radio access technology. The RAN has a base station gNB. The base station gNB handles wireless communication with the user terminal UEs. The base station gNB is responsible for managing radio resources and monitoring the communication status of devices. The base station gNB has an antenna using beamforming or Massive MIMO (multiple input multiple output) technology. The transport network TN connects the base station gNB and the core network 2.

[0015] The 5G network system 1 has a control system 3. The control system 3 has an NSMF20 and an NSMMF10. The control system 3 monitors and controls various devices of the 5G network system 1. The devices monitored and controlled by the control system 3 include devices such as 5GC in the core network, devices such as network (NW) equipment in the transport network TN, and devices such as gNB in ​​the RAN. The NSMF20 (Network Slice Management Function) manages network slices. Specifically, the NSMF20 creates, orchestrates, and manages the lifecycle of slices. Slice creation includes translating service requirements, allocating resources, and deploying network functions. Regarding the translation of service requirements, the NSMF20 translates high-level service requirements into specific slice requirements. This includes defining the required network functions and resources. Regarding resource allocation, the NSMF20 allocates the required resources to the slice. Regarding the deployment of network functions, the NSMF20 deploys the required network functions and verifies that they are correctly configured to meet the slice requirements. The NSSMF (Network Slice Subnet Management Function) 10 manages specific subnets within a slice, such as the RAN or core network subnet. The NSSMF 10 works in conjunction with the NSMF 20 to achieve end-to-end slice management. In this example, the NSSMF 10 is a RAN-NSSMF, an example of a control device that performs resource allocation within the RAN.

[0016] FIG. 3 is a diagram illustrating the functional configuration of the NSSMF 10. The NSSMF 10 includes a storage unit 11, a reception unit 12, an access unit 13, a setting unit 14, a writing unit 15, a providing unit 16, and a control unit 19. The storage unit 11 stores various data. The data stored in the storage unit 11 includes a database 111. The database 111 is a database in which resource information about each of a plurality of base stations gNB is recorded. The resource information is information regarding resources for using a slice. The resource information is information indicating the resource allocation in each of a plurality of cells of the base station gNB. The reception unit 12 receives a reservation request. The reservation request is a request to reserve a slice that supports communication between the base station gNB and the user terminal UE, and indicates the requirements for resources for providing the slice. The access unit 13 accesses the database 111. The setting unit 14 sets a slice that supports communication between the base station gNB and the user terminal UE in accordance with the content corresponding to the type of the base station gNB shown to satisfy the requirements by the resource information among the plurality of base stations gNB. The writing unit 15 writes this setting into the database 111. The providing unit 16 provides information indicating whether resources that satisfy the requirements indicated by the reservation request can be reserved to the source of the reservation request. If resources that satisfy the requirements cannot be reserved, the providing unit 16 may provide a recommendation indicating that resources can be reserved if the requirements are changed.

[0017] FIG. 4 is a diagram illustrating the hardware configuration of the NSSMF10. In one example, the NSSMF10 is implemented in a virtual machine created on an information processing apparatus that is a physical server. Physically, this information processing apparatus is configured as a computer including a processor 101, a memory 102, a storage 103, a communication device 104, and a bus connecting these components. Each of these devices operates by power supplied from a power source not shown in the figure. In the following description, the term "device" can be read as a circuit, device, unit, etc. The hardware configuration of the information processing apparatus may be configured to include one or more of the devices shown in FIG. 4, or may be configured without including some of the devices. Also, a plurality of devices with different housings may be communicatively connected to constitute this information processing apparatus.

[0018] Each function in this information processing apparatus is realized by causing the processor 101 to perform operations by loading a predetermined software (program) onto hardware such as the processor 101 and the memory 102, controlling communication by the communication device 104, and controlling at least one of reading and writing data in the memory 102 and the storage 103.

[0019] The processor 101 controls the entire computer by operating an operating system, for example. The processor 101 may be constituted by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, registers, etc. Also, for example, a baseband signal processing unit, a call processing unit, etc. may be realized by the processor 101.

[0020] The processor 101 reads programs (program code), software modules, data, etc., from at least one of the storage 103 and the communication device 104 into the memory 102 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described later. The functional blocks of the terminal device 10 are stored in the memory 102 and may be implemented by control programs that run on the processor 101. Various processes may be executed by one processor 101, or they may be executed simultaneously or sequentially by two or more processors 101. The processor 101 may be implemented by one or more chips. The program may also be transmitted to the terminal device 10 via a telecommunications line.

[0021] Memory 102 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. Memory 102 may also be called a register, cache, main memory, etc. Memory 102 can store executable programs (program code), software modules, etc., for carrying out the method according to this embodiment.

[0022] The storage 103 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disc, a digital multipurpose disc, a Blu-ray® disc), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. The storage 103 may also be called an auxiliary storage device.

[0023] The communication device 104 is hardware (transceiver / receiver device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc.

[0024] Each device, such as the processor 101 and memory 102, is connected by a bus for communicating information. The bus may be configured using a single bus, or different buses may be used for each device.

[0025] This information processing device may include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or an FPGA (Field Programmable Gate Array), and some or all of each functional block may be implemented by such hardware. For example, processor 101 may be implemented using at least one of these hardware components.

[0026] Other functional elements of core network 2, such as NSMF20, are implemented in virtual machines created on a physical server, similar to NSSMF10. While a detailed explanation is omitted, the operator terminal 50 is a computer (e.g., a personal computer) having a processor, memory, storage, communication interface, and input / output devices. The operator terminal 50 has a program (hereinafter referred to as the "client application") installed for accessing core network 2 of the 5G network system 1. The physical server on which this virtual machine is built can be any configuration, such as a so-called cloud or on-premises. The cloud can be a so-called public cloud or a private cloud.

[0027] 2.Operation Figure 5 is a sequence chart illustrating the operation of one embodiment of the 5G network system 1. In one example, the flow in Figure 5 is initiated when the operator OP inputs a request from the customer CL at the operator terminal 50 running the client application.

[0028] In step S1, the operator terminal 50 sends a slice reservation request to the NSMF20. This reservation request includes information about the slice to which the reservation request applies (hereinafter referred to as the "target slice"). The information about the target slice includes information indicating the slice's attributes for several items, such as area, utilization rate, period, and slice ID. The item "area" is information that specifies the target base station gNB (i.e., the base station gNB that supports the target slice), and in this case, the base station gNB is specified by its geographical location. In the example in Figure 5, "all base station gNBs in Yokohama City" is exemplified as information for the item "area," specifying that all base station gNBs located in Yokohama City are the target. The NSMF20 / NSSMF10 has a database (hereinafter referred to as the "base station database"; not shown in the figure) in which the attributes of base station gNBs are recorded. The base station database records the attributes of each of multiple base station gNBs. The attributes of a base station gNB include the region in which the base station gNB is installed (for example, coordinates such as latitude and longitude or address). The attributes of a base station gNB further include information that identifies the vendor of that base station gNB. NSMF20 refers to this base station database to identify the target base station gNB.

[0029] The item "Utilization Rate" specifies the utilization rate (or occupancy rate or ratio) of a resource. Resource utilization rate indicates the ratio of the amount of resources allocated to the target slice to the total amount of resources. Resources refer to resources used for communication using a slice, and include, for example, at least one of the following: frequency band, time slot, antenna resources, transmission power, and computing resources. Resources in 5G network system 1 take these into consideration comprehensively, and the amount of resources is calculated by a predetermined formula. In addition, resource allocation in the RAN in 5G network system 1 is performed based on resource partitions. Resource partitions are a mechanism for allocating resources in the network (in this case, the RAN) to slices. Multiple resource partitions are defined in each base station gNB, and resources are allocated to each slice in units of resource partitions. In the example in Figure 5, the item "Utilization Rate" specifies that the uplink is 5% and the downlink is 3%. The item "Period" specifies the period for which the target slice is set (i.e., the requested period for securing resources). In the example in Figure 5, the "Period" field indicates that the target period is from November 1, 2024, 0:00 to November 9, 2024, 23:59. The "Slice ID" field is identification information used to identify a slice. In the example in Figure 5, "#005" is specified as the "Slice ID" field.

[0030] The term "reservation request" as used here encompasses both requests that specify a slice ID and requests that do not specify a slice ID. The 5G network system 1 may accept either a reservation request with a specified slice ID (i.e., a reservation request) or a search request without a specified slice ID. If the NSMF20 / NSSMF10 confirms availability for a request with a specified slice ID during the processing described later, the 5G network system 1 reserves that slice. If there is no availability for the specified slice ID, the NSMF20 / NSSMF10 responds to the operator terminal 50 with an alternative (recommendation information). The operator OP then inputs a slice request again at the operator terminal 50.

[0031] A request specifying a slice ID is equivalent to a request to search for an available slice. If NSMF20 / NSSMF10 can confirm that there is an available slice, NSMF20 / NSSMF10 responds to the operator terminal 50 with information on one or more slices that are candidates to be allocated to that request. The operator OP selects a slice from the presented candidates (i.e., specifies a slice) and requests the reservation of the slice.

[0032] In step S2, NSMF20 generates a confirmation request (hereinafter referred to as the "confirmation request") to determine whether resources can be secured to configure the target slice. This confirmation request can also be described as a request to generate an intent to secure resources for slice configuration if no slice ID is specified. This confirmation request includes information indicating the attributes of the target slice. In step S3, NSMF20 sends this confirmation request to NSMMF10.

[0033] Upon receiving a confirmation request from NSMF20, NSSMF10 verifies whether it can secure the resources necessary to configure the target slice (step S4). This process is known as a feasibility check. NSSMF10 stores a database (hereinafter referred to as the "resource database") that records the resource allocation status for each of the multiple base station gNBs. NSSMF10 refers to the resource database to verify whether it can secure the resources for the target slice.

[0034] Figure 6 illustrates the resource allocation status recorded in the resource database. For visual clarity, the resource allocation status for the target period is shown graphically. In this example, resource allocation is managed for each A (Active) cell. An A cell refers to the geographical range in which a base station gNB can transmit and receive radio waves. In the example in Figure 6, the target base station gNBs are 50 base station gNBs from base station gNB#1 to base station gNB#50. Each of these 50 base station gNBs has a maximum of 48 A cells. Figure 6 illustrates A cells#1 to A cells#48, which correspond to the maximum number. For each A cell, a certain percentage (40% in the example in Figure 6) is allocated for general communications (labeled "shared" in Figure 6), and the remainder (60% in the example in Figure 6) is pre-allocated. In this example, one physical base station gNB is shared by multiple customer CLs (three companies, X, Y, and Z in the example in Figure 6), and Figure 6 shows which of these customer CLs has the resources allocated to it. Note that resources allocated for only a portion of the target period are shown as resources allocated for the target period. In the example in Figure 6, for cell #1 of base station gNB#1, 20% of the resources are allocated to company X, 11% to company Y, and 22% to company Z, leaving 7% available. Also, while only the availability of a single cell is shown here, resource allocation is set independently for uplinks and downlinks.

[0035] For visual clarity, the resource allocation status is shown in a graph here. However, the data structure in the resource database can be in any format, as long as it allows for the identification of the resource allocation status of all A cells in a specified base station gNB during a specified period.

[0036] In summary, NSSMF10 determines that resource allocation is possible for the target slice if all A cells of the target base station gNB have available resources equal to or greater than the resource utilization rate specified in the "Utilization Rate" item. On the other hand, if even one A cell does not have available resources equal to or greater than the resource utilization rate specified in the "Utilization Rate" item, NSSMF10 determines that resource allocation is impossible for the target slice. More specifically, NSSMF10 performs a feasibility check considering the group to which each base station gNB belongs. In 5G network system 1, multiple base station gNBs are divided into multiple groups with different details regarding resource allocation methods. In this example, these groups are divided based on the vendor of the base station gNB. For example, in 5G network system 1, if there are three vendors of base station gNBs, companies A, B, and C, three groups are formed corresponding to each vendor. Details are as follows.

[0037] Figure 7 illustrates a resource partition configuration in a base station gNB. Each base station gNB has, for example, the following specifications. For each A cell, a predetermined number of resource partitions (RP in the diagram) are configured. • Resource partitions correspond to slice IDs. • Resource usage is set for each resource partition.

[0038] The details of resource partition configuration vary from vendor to vendor. Examples of vendor-specific specification differences include at least one of the following. Each vendor can configure these details arbitrarily; that is, at least one or more of these details may differ from vendor to vendor. (a) The maximum number of slices that can be set. (b) The number of resource partitions per A cell. (c) The correspondence between resource partitions and slice IDs (one-to-one, one-to-many, or many-to-one). (d) The sum of the maximum resource utilization (i.e., maximum utilization) (dl-max-slice-portion) in the downlink. (e) The minimum resource utilization in the downlink (i.e., minimum utilization) is a predetermined value. Regarding (a), in one example, there is an upper limit to the number of slices that can be set on the DU in 5G network system 1. NSSMF10 sets the slices so as not to exceed this upper limit. For example, if the DU corresponding to the target base station gNB has already set up to the upper limit, NSSMF10 will determine in the feasibility check that resource allocation is impossible.

[0039] Regarding (b), in one example, the NSSMF10 writes a predetermined value as the parameter value in the resource information for resource partitions in the target A cell that have not been assigned a slice. Here, so-called "F-padding" is used, and "F" (i.e., "0xF" in hexadecimal) is written as the predetermined value. In practice, all parameter values ​​in the resource information are initially written as F, and specific values ​​are written as the parameter values ​​corresponding to resource partitions to which slices have been assigned. In some base station gNBs, if a numerical value such as "0%" is recorded in the resource information instead of F-padding, it is associated with the slice ID and consumes the resource of the slice ID, but if F-padding is used, this resource is not consumed.

[0040] (c) is a reasonable limitation because if the total resource utilization exceeds 100%, a contradiction will occur when all slices are operating at maximum utilization. (d) In one example, resource partitions assigned to a slice are set to "0%", and resource partitions that are not assigned are set to "F" (i.e., F-filled).

[0041] NSSMF10 maintains these constraints, for example, in the form of a database (or checklist in another example). In this database, the constraints are associated with vendor identification information. NSSMF10 virtually allocates the available resource partitions in each A cell of the target base station gNB to the target slice. During the feasibility check, NSSMF10 refers to this database and determines whether the resource allocation to the target slice satisfies the constraints in each of the target base station gNBs. If even one A cell does not satisfy the constraints, NSSMF10 determines that resource allocation is impossible in the feasibility check. If all A cells satisfy the constraints, NSSMF10 determines that resource allocation is possible in the feasibility check.

[0042] Refer to Figure 5 again. In step S5, NSSMF10 sends a response containing the results of the feasibility check to NSMF20, the source of the resource intent. If the result is negative, the response includes the reason why resource allocation is not possible and recommendations for alternatives. The reason why resource allocation is not possible includes information identifying the A cells that do not have sufficient free space and the base station gNB that has those A cells. For example, the reason why resource allocation is not possible includes the string "No free space in A cells #1 to A cells #10 of base station gNB

[10] ".

[0043] NSSMF10 has an algorithm for determining alternatives. Specifically, NSSMF10 first extracts candidate alternatives. The candidate alternatives are defined, for example, (Candidate 1) using available resources of another base station gNB, and (Candidate 2) using general communication resources. A priority is defined for these two candidates, for example, Candidate 1 takes precedence over Candidate 2. NSSMF10 first determines whether Candidate 1 is available. Specifically, NSSMF10 determines whether there is an A cell of another base station gNB that covers the A cell of a base station gNB that is out of stock. The geographical range covered by each A cell is recorded in a base station database, for example, and NSSMF10 makes this determination by referring to the base station database. If it is determined that there is an A cell of another base station gNB that covers the A cell of a base station gNB that is out of stock, NSSMF10 decides to adopt Candidate 1 as the alternative for that A cell. If NSSMF10 determines that there are no other base station gNBs with A cells available to cover the A cell of a base station gNB that is currently empty, NSSMF10 decides to adopt candidate 2 as an alternative for that A cell.

[0044] The alternative recommendation includes a string indicating the alternative. In one example, the alternative recommendation includes information identifying an A cell that is unavailable and information identifying an alternative for that A cell, specifically the string "For A cells [1] to A cells

[10] of base station gNB

[10] , service can be provided by using general communication resources." If there are multiple A cells that are not sufficiently available and each has a different alternative, the alternative recommendation will include a string indicating the alternative for each A cell.

[0045] Upon receiving a response from NSSMF10, NSMF20 generates a response for operator terminal 50 (step S6). This response includes information about the response received from NSSMF10. This information includes, for example, the results of the feasibility check and a string indicating an alternative if resource allocation is not possible. NSMF20 sends the generated response to operator terminal 50, the source of the slice allocation request (step S7).

[0046] Upon receiving a response from NSSMF10, the operator terminal 50 displays information corresponding to this response (step S8). Along with, or after, the display of information corresponding to the response, the operator terminal 50 receives an instruction from operator OP regarding this response (step S9). This instruction includes an instruction to reserve a slice, i.e., to secure a resource, for the target slice. Upon receiving the instruction to reserve a slice, the operator terminal 50 sends a slice reservation request to NSMF20 (step S10). This reservation request includes information about the target slice. If NSSMF10 provides identification information for the feasibility check, the information about the target slice in the reservation request may include this identification information for the feasibility check. Note that for requests in which a slice ID is specified (i.e., slice reservation requests), the processing in steps S9 to S12 is not performed. In this case, if the resource can be secured in the feasibility check in step S4, the process proceeds to step S13 and the slice is set.

[0047] When NSMF20 receives a slice reservation request from the operator terminal 50, it generates a request to reserve the target slice (hereinafter referred to as the "reservation request") (step S11). This reservation request includes information indicating the attributes of the target slice. In step S3, NSMF20 sends this reservation request to NSMMF10 (step S12).

[0048] Upon receiving a reservation request from NSMF20, NSSMF10 configures the target slice (step S13). That is, NSSMF10 writes information regarding resource allocation for the target slice to the resource database. At this time, NSSMF10 considers the vendor of the target base station gNB and writes information to the resource database that has been adjusted according to the differences in equipment specifications for each vendor. The differences in equipment specifications for each vendor are as explained in the As and Feasibility Check sections.

[0049] Figure 8 illustrates database 111. Database 111 contains multiple records. Each record corresponds to one of multiple resource partitions. Figure 8 illustrates database 111 for a base station gNB. In database 111, the values ​​of each parameter are recorded for each unit period. In this example, the unit period is one week. Three parameters are exemplified: "S-NSSAI List ID", "dl-max-slice-portion", and "dl-min-slice-portion". For example, the top record in Figure 8 shows that for resource partition ID "#0", slices with "S-NSSAI List ID" (corresponding to slice ID) "#1" are assigned for the first and second weeks of December, and are available for the third and fourth weeks of December. For slices with "S-NSSAI List ID" "#1", the values ​​of the parameters "dl-max-slice-portion" and "dl-min-slice-portion" are set to "20%" and "0%", respectively.

[0050] As described above, according to this embodiment, on-demand slices can be automatically configured regardless of the detailed specification differences between base station gNB vendors.

[0051] 3. Variant The present invention is not limited to the embodiments described above, and various modifications are possible. Several modifications are described below. At least one of the items described below may be used in combination with other items or items described in the embodiments.

[0052] (1) Timing of slice settings The timing at which NSSMF10 sets the requested slice is not limited to the examples in this embodiment. In this embodiment, an example was described in which NSSMF10 returns the results to the operator after performing a feasibility check and then sets the slice after receiving instructions from the operator. For example, if NSSMF10 determines in the feasibility check that it is possible to secure resources for the requested slice, it may set the slice immediately without waiting for instructions from the operator.

[0053] (2) Resource Database The data recorded in database 111 and its data structure or data format are not limited to the examples of this embodiment. Database 111 may record any information that is used for resource allocation decisions (i.e., feasibility checks), and such information may be recorded in any data structure or data format. The specific parameters set in resource configuration are also not limited to the examples of this embodiment.

[0054] (3) Group of base station gNBs The grouping of base station gNBs is not limited to vendors. For example, if several vendors provide base station gNBs with common specifications, NSSMF10 may treat the base station gNBs provided by these vendors as belonging to the same group. Alternatively, if a single vendor provides base station gNBs with multiple different specifications, NSSMF10 may treat these as belonging to separate groups.

[0055] (4) System Configuration The device configuration in the 5G network system 1 is not limited to the examples of embodiments. The 5G network system 1 may be formed by devices with any hardware configuration as long as they can implement the required functions. Furthermore, the functional configuration of each device in the 5G network system 1 is not limited to the examples of embodiments. For example, with respect to the NSSMF 10, some of the functional elements described in Figure 3 may be omitted.

[0056] (5) Others The various programs executed by processor 101 may be provided by downloading them over a network such as the Internet, or they may be provided recorded on a computer-readable non-temporary recording medium such as a DVD-ROM. Each processor may be, for example, a CPU, an MPU (Micro Processing Unit), or a GPU (Graphics Processing Unit).

[0057] The block diagrams used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.

[0058] Functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. As mentioned above, the method of implementation is not particularly limited.

[0059] For example, an information processing device in one embodiment of the present disclosure may function as a computer that performs the processing described herein.

[0060] Each aspect or embodiment described in this disclosure may be applied to at least one of the following systems: LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER3f, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (new Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), and other appropriate systems, as well as next-generation systems extended based thereon. Furthermore, multiple systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A with 5G).

[0061] The processing procedures, sequences, flowcharts, etc., of each aspect or embodiment described in this disclosure may be reordered, provided they do not contradict each other. For example, the methods described in this disclosure present various step elements in an exemplary order and are not limited to the specific order presented.

[0062] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be sent to other devices.

[0063] The determination may be made by a value represented by 1 bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0064] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way.

[0065] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name. Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technologies (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technologies (such as infrared or microwave), at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0066] The information, signals, etc., described herein may be represented using any of the following different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc., which may be referred to throughout the above description, may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof. Terms used herein and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meaning.

[0067] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or corresponding other information.

[0068] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0069] Any reference to elements using designations such as “First,” “Second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the First and Second elements do not imply that only two elements may be employed, or that the First element must precede the Second element in any way.

[0070] In the above-described configuration of each device, the term "part" may be replaced with "means," "circuit," "device," etc.

[0071] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0072] In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0073] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different." [Explanation of Symbols]

[0074] 1...5G network system, 2...Core network, 10...Terminal device, 11...Storage unit, 12...Receiver unit, 13...Access unit, 14...Setting unit, 15...Writing unit, 16...Providing unit, 19...Control unit, 50...Operator terminal, 101...Processor, 102...Memory, 103...Storage, 104...Communication device, 111...Database, OP...Operator, TN...Transport network, UE...User terminal, gNB...Base station

Claims

1. A receiving unit that receives a resource allocation request indicating the resource requirements for providing a slice that supports communication between a base station and a terminal, For each of the multiple base stations, an access unit accesses a database that records resource information indicating the allocation of resources in each of the multiple cells that the base station possesses, A setting unit that configures slices to support communication between a base station and a terminal, according to the type of base station among the plurality of base stations that is shown to satisfy the requirements by the resource information, A writing unit that writes the above settings to the database. A control device having

2. The aforementioned multiple base stations are divided into multiple groups with different resource allocation methods, The setting unit searches for available resources that satisfy the requirements, taking into account the differences in resource allocation methods among the multiple groups. The control device according to claim 1.

3. In the aforementioned base station, each of the multiple cells corresponds to a multiple resource partition, The resource information includes, for each of the multiple unit periods and multiple resource partitions, the slice ID assigned to the unit period and resource partition. The aforementioned reservation request includes information that specifies the period for which the resource is to be reserved. The setting unit is, For each of the multiple unit periods belonging to the aforementioned request period, the slice ID is assigned to the resource partition. For each of the multiple unit periods belonging to the aforementioned request period, set the utilization rate of the resource partition. The control device according to claim 2.

4. The setting unit, for a base station belonging to one of the multiple groups, In the aforementioned base station, one or more slice IDs are assigned to one resource partition. For resource partitions that are not used, set information indicating that the resource partition is not being used. The control device according to claim 3.

5. The resource information includes, for each of the plurality of resource partitions, the minimum utilization rate during the unit period. The setting unit sets the minimum utilization rate of the resource partition to 0% for the resource partition being used. The control device according to claim 3.

6. The unit provides information to the source of the resource allocation request indicating whether the multiple base stations can secure resources that meet the requirements. The control device according to claim 1.

7. The resource information includes information indicating the use of the resource, If none of the aforementioned base stations meet the requirements, the providing unit provides the transmitting unit with a proposal to repurpose resources allocated for specific uses for some of the base stations. The control device according to claim 6.

8. The steps include receiving a reservation request that indicates the resource requirements for providing a slice that supports communication between a base station and a terminal, For each of the multiple base stations, the step of accessing a database that records resource information indicating the allocation of resources in each of the multiple cells that the base station possesses, The steps include: configuring slices to support communication between a base station and a terminal, with content corresponding to the type of base station among the plurality of base stations that is shown to satisfy the requirements by the resource information; The steps include writing the above settings to the database and A control method having