JP6754734B2 - Resource management device in RAN slice and resource management method in RAN slice - Google Patents

Description

The present invention relates to a resource management device in a RAN slice and a resource management method in a RAN slice. In addition, "RAN" in this specification means a radio access network (Radio Access Network), and "RAT" means a radio access technology (Radio Access Technology), for example, LTE, 5G (fifth generation mobile phone). It means a mobile communication line such as (telephone).

In addition, the term "service" or "network service" in the present specification refers to network resources such as communication services (dedicated line services, etc.) and application services (services using sensor devices such as video distribution and embedded devices). Means a service processed using. A "slice" is a virtual network that is logically generated on the network infrastructure, and the service is assigned to a slice and processed using the network resources of the allocated slice.

As a conventional resource allocation method in RAN, a method of determining a target resource allocation amount based on the experience quality for each user and the target service quality is known.

Japanese Unexamined Patent Publication No. 2012-049598

In recent years, it has been studied to apply a slicing technology that guarantees a resource allocation amount by separating a virtual network for each service to RAN. However, in the conventional resource allocation in RAN, prioritization for each service has not been considered so much, so it has been difficult to guarantee the resource allocation amount. If a method of simply allocating resources to each service in a fixed manner is adopted in order to guarantee the resource allocation amount, there is a risk that the resource division loss will increase and the resource utilization efficiency of the entire network will decrease. ..

The present invention has been made in view of the above, and in the resource management device and the RAN slice in the RAN slice, which can guarantee the resource allocation amount for each service while suppressing the decrease in the resource utilization efficiency in the entire network. The purpose is to provide a resource management method.

In order to achieve the above object, the resource management device in the RAN slice according to one embodiment of the present invention enjoys services and services using the virtual network for the RAN slice, which is a virtual network logically generated on the RAN. A resource management device in a RAN slice that allocates resources to a user terminal, the RAN slice is generated on a communication path between the user terminal and a service server that provides the service, and uses the virtual network. Information acquisition unit that acquires information necessary for slice generation, including service requirements that are requirements for functions or performance in the service provided by the network, and necessary resource allocation based on the information acquired by the information acquisition unit. The slice is related to the slice setting policy based on the slice setting policy determination unit that determines the slice setting policy including the amount and the priority of resource allocation for each slice, and at least the slice setting policy determined by the slice setting policy determination unit. A slice setting unit that determines the amount of resources to be allocated to one or more RATs, and at least a resource to be allocated to a user terminal that enjoys a service in the slice based on the amount of resources to be allocated determined by the slice setting unit. It includes a terminal allocation determination unit for determining.

In the resource management device in the above RAN slice, when the information acquisition unit acquires the information required for slice generation, including the service requirement which is the function or performance requirement in the service provided by using the virtual network, the slice setting is performed. Based on the acquired information, the policy determination unit determines a slice setting policy including the required resource allocation amount and resource allocation priority for each slice. Then, the slice setting unit determines the amount of resources to be allocated to one or more RATs related to the slice based on at least the determined slice setting policy, and the terminal allocation determination unit at least determines the amount of resources to be allocated. Based on, the resources to be allocated to the user terminals that enjoy the service in the slice are determined. In this way, slices are based on the slice setting policy (including the required resource allocation amount and resource allocation priority) determined based on the information including the service requirements that are the requirements of the function or performance in the service. The amount of resources to be allocated to one or more RATs related to the above is determined, and further, the resources to be allocated to the user terminals that enjoy the service in the slice are determined based on the amount of resources to be allocated. As a result, it is possible to suppress a decrease in resource utilization efficiency in the entire network, which is a problem when resources are fixedly allocated to each service as in the conventional case, and further, it is possible to guarantee the resource allocation amount for each service. ..

According to the present invention, it is possible to guarantee the resource allocation amount for each service while suppressing the decrease in resource utilization efficiency in the entire network.

It is a block diagram of the communication system which concerns on embodiment of this invention. It is a figure which shows the functional block composition of each apparatus which constitutes a communication system. It is a figure which shows an example of the information which a slice information holding part 43 holds. It is a figure which shows an example of the information which a slice information holding part 32 holds. It is a figure which shows an example of the information which a user information holding part 22 holds. It is a flow chart which shows the process which concerns on the resource management method in a RAN slice. (A) is a diagram for explaining a first example of a scheduling method, (b) is a diagram for explaining a second example of a scheduling method, and (c) is a diagram for explaining a third example of the scheduling method. It is a figure for demonstrating an example. It is a figure which shows the hardware configuration example of each apparatus.

Hereinafter, embodiments for carrying out the present invention will be described in detail with reference to the accompanying drawings. In the description of the drawings, the same elements are designated by the same reference numerals, and duplicate description will be omitted.

FIG. 1 shows the configuration of the communication system 1 according to the present embodiment. The communication system 1 according to the present embodiment is a system that provides a network service by using data communication to a UE (User Equipment) 10 which is a user terminal used by a user. The UE 10 here includes all portable terminals such as smartphones and tablet terminals.

Communication system 1 provides network services to UE 10 by allocating services to RAN slices, which are virtualized networks. The RAN slice here is a virtualized network or service network that virtually separates RAN resources, combines the separated RAN resources, and is logically generated on the combined RAN resources. Since the resources are separated from each other, they do not interfere with each other.

For the generation and management of slices for each service, resource division technology using MAC Scheduling (Media Access Control Scheduling) and ANDSF (Access Network Discovery and Selection Function) / LWA (LTE Wi-Fi Link Aggregation) / MPTCP ( It can be realized by using multiple RAT (Radio Access Technology) binding technology such as Multipath TCP) or resource binding technology.

In the communication system 1, a part of the nodes that realize the communication necessary for the UE 10 to use the service is provided on the RAN slice, which is a virtual network logically generated on the RAN. Therefore, the UE communicates via a route via a node such as a base station or AP (Access Point) provided on the RAN slice (hereinafter, referred to as “base station 20” for convenience). At that time, since it is conceivable to combine a plurality of RATs for communication, there may be a plurality of base stations 20 constituting one RAN slice.

Further, in the communication system 1, when the UE 10 communicates with a service server (service servers # 1, # 2, etc. in FIG. 1) that provides a service in order to use the service, it is selected according to the service. It is characterized by performing communication via other slices to be processed. Specifically, in the communication system 1 shown in FIG. 1, the UE 10 has a node set in the RAN slice and a node set in the core network slice (hereinafter referred to as “CN slice”). Communicates with the service server via. Therefore, the UE 10 provides a communication path between the service server and the service server via a total of two slices, a RAN slice and a CN slice. As described above, the communication system 1 of FIG. 1 shows a situation in which so-called E2E (End-to-End) slicing is realized.

The E2E slice and the RAN slice and CN slice that are the components of the E2E slice are set based on the requirements required for the service (for example, allowable delay time, frequency band, etc.). In the communication system 1, when the UE 10 uses the service # 1 (for example, a service using mMTC / massive Machine Type Communications), the UE 10 accesses the RAN # 1 slice and further accesses some CN slice. , Communicates with service server # 1 of service # 1. Similarly, when the UE 10 uses the service # 2 (for example, a service using URLLC / Ultra-Reliable and Low Latency Communications), the UE 10 accesses the RAN slice # 2 and further accesses some CN slice. Then, it communicates with the service server # 2 of service # 2. As described above, when the UE 10 uses a specific service, the UE 10 accesses and communicates with the RAN slice and the CN slice determined in advance according to the service.

Next, the device included in the communication system 1 will be described. As shown in FIG. 1, the communication system 1 includes a RAN resource management device 30, a slice management device 40, and a service operation device 50.

The RAN resource management device 30 has a function of setting a RAN slice corresponding to a service based on a slice setting request from the slice management device 40.

The slice management device 40 has a function of setting end-to-end slices based on the service requirements from the service operation device 50 and notifying the RAN resource management device 30 of the slice setting request. The function as the slice management device 40 can be mounted on, for example, an NFVO (NFV Orchestrator) defined as a MANO (Management and Orchestration) architecture. Further, the device having the slice selection function newly defined may be configured to include the function as the slice management device 40.

The service operation device 50 is a device managed by a service provider or the like, and has a function of notifying the slice management device 40 of service requirements.

The functions related to the RAN resource management device 30 and the slice management device 40 described above may be accommodated in the same device. Further, the functions related to the RAN resource management device 30 and the slice management device 40 may be realized by a plurality of devices, respectively.

Next, the functional block configuration of each device constituting the communication system 1 will be described with reference to FIG.

The slice management device 40 includes an information acquisition unit 41, a slice setting policy determination unit 42, and a slice information holding unit 43.

The information acquisition unit 41 includes service requirements (for example, required delay, throughput, etc.) which are requirements for functions or performance in a service provided by using a virtual network by communicating with the service operation device 50. However, it has a function to acquire the information required for slice generation. The acquired information required for slice generation is held by the slice information holding unit 43 and sent to the slice setting policy determining unit 42.

The slice setting policy determination unit 42 determines the slice setting policy including the required resource allocation amount (guaranteed allocated resource amount) and the resource allocation priority for each slice based on the information obtained from the information acquisition unit 41. Has a function. The determined slice setting policy information is held by the slice information holding unit 43 and sent to the RAN resource management device 30. As an example of the slice setting policy, the slice setting policy determination unit 42 may delete slices, generate new slices, and release and combine resources including a plurality of RATs according to the priority of resource allocation. At least one of the regenerations may be determined.

The slice information holding unit 43 has a function of holding information about a slice for a service. Information about slices for services includes information such as the name of slices currently in operation, the basic priority of slices, the amount of allocated resources to be guaranteed, the content of services that use slices, and their service requirements. As shown in FIG. 3, the slice information holding unit 43 holds information on the service requirement sent from the service operation device 50 and the slice setting policy determined by the slice setting policy determining unit 42, and for example, a plurality of slice information holding units 43. Information related to requirements (parameters A to B), slice priority, and guaranteed allocated resource amount are held for each slice. In this way, the slice information holding unit 43 holds information related to the characteristics of the slice for each slice.

Returning to FIG. 2, the RAN resource management device 30 includes a slice setting unit 31 and a slice information holding unit 32.

The slice setting unit 31 has a function of determining the amount of resources to be allocated to one or more RATs related to slices based on the slice setting policy sent from the slice management device 40. More specifically, the slice setting unit 31 selects and combines RATs capable of generating resources related to slices based on the slice setting policy, and determines the amount of allocated resources guaranteed by each RAT. Information on the amount of allocated resources guaranteed by each determined RAT is held by the slice information holding unit 32 and sent to the base station 20 of each RAT.

The slice information holding unit 32 has a function of holding information such as the amount of allocated resources guaranteed by each determined RAT. For example, as shown in FIG. 4, the slice information holding unit 32 has a slice priority, a slice name, location information of a user who enjoys the service, a guaranteed allocated resource amount, an allocated resource amount guaranteed by each RAT, and the like. Holds information about.

Returning to FIG. 2, the base station 20 includes a base station scheduler 21 (corresponding to the “terminal allocation determination unit” described in the claims) and a user information holding unit 22.

The base station scheduler 21 has at least a function of determining the amount of resources to be allocated to each user based on the information of the amount of allocated resources guaranteed by each RAT sent from the RAN resource management device 30. Further, the base station scheduler 21 can also determine the amount of resources to be allocated to each user based on the communication status sent from the UE 10. The specific scheduling method will be described later.

The user information holding unit 22 has a function of holding slice information for which the base station 20 guarantees resources, user information included in the slice, communication status information of the user, and the like. For example, as shown in FIG. 5, the user information holding unit 22 holds information such as a slice priority, a slice name, a user included in the slice, and a communication status of the user.

Returning to FIG. 2, next, a method of managing resources in the RAN slice at the base station 20 will be described. The base station 20 performs scheduling for the UE 10 based on the information regarding the allocated resource amount guaranteed for each slice sent from the RAN resource management device 30 and the communication status information sent from the UE 10. The "communication status information" means information such as the success / failure history of UL (Up Link) communication performed for each UE 10 by the resource allocation so far, the movement status of the UE 10. By using such communication status information, it is possible to obtain the expected communication success value when the resource is allocated to the UE 10 at the present time. By allocating a large number of resources to the UE 10 having a high expected communication success value, it is possible to expect an improvement in the overall throughput of the communication system 1, and it is possible to improve the resource utilization efficiency.

"Resource management in RAN slices" described in the claims by the information acquisition unit 41, the slice setting policy determination unit 42, the slice setting unit 31, and the base station scheduler 21 surrounded by the alternate long and short dash line in FIG. 2 described above. The device "60" is realized.

Next, a processing flow related to the resource management method in the RAN slice will be described with reference to FIG. First, the service operation device notifies the slice management device of the service requirement (step S1). Next, the slice management device determines the amount of resources to be guaranteed and the priority of the slice for the slice corresponding to the service (step S2), and notifies the RAN resource management device (step S3). The RAN resource management device determines the amount of allocated resources guaranteed in each RAT (step S4), and notifies the base station (step S5).

Then, when the service use request occurs, the UE notifies the base station (step S6). The base station notifies the RAN resource management device of the notification received from the UE (step S7). The RAN resource management device redetermines the resources to be allocated for each RAT based on the user's information (step S8), and re-notifies the base station (step S9). The base station that receives the service use request from the user performs scheduling based on the notification sent from the RAN resource management device (step S10), and notifies the UE of the schedule (step S11). Then, the UE performs UL communication based on the notified scheduling (step S12), and the base station updates the communication status information regarding the UE based on the result of the UL communication (step S13). After that, the base station and the UE repeatedly execute the processes of steps S10 to S13. As a result, resources are appropriately allocated to the UE.

The form of each device and each function described so far is not limited to the above-mentioned example. That is, the functional units provided in each device can be integrated and separated, and can be realized by one or a plurality of nodes different from the above.

Hereinafter, with reference to FIGS. 7A to 7C, three scheduling methods by the base station will be illustrated. In FIGS. 7A to 7C, a user terminal belonging to slice A (hereinafter referred to as “slice A user”), a user terminal belonging to slice B (hereinafter referred to as “slice B user”), and , It is assumed that resources are allocated to user terminals belonging to Slice C (hereinafter referred to as "Slice C users"). Here, it is assumed that the priority is higher in the order of slices A, B, and C. In FIGS. 7A to 7C, the allocated resources are indicated by a plurality of RBs (Resource Blocks), and each RB is hatched differently for each slice of the allocation destination.

FIG. 7A shows an example in which resources are allocated to user terminals with an emphasis on slice priority as the first method. First, allocate resources to the user with the highest priority slice A (step 1). At this time, the RB with the best communication status is selected and assigned to the user of slice A from the selectable RBs. At that time, the upper limit of the number of RBs allocated to the user of slice A is set so as not to exceed the slice setting policy (guaranteed allocated RB amount) determined by the slice management device. Next, resources are allocated to the user of slice B having the second highest priority (step 2). At this time, the RB having the best communication status is selected and assigned to the user of slice B from the RBs not selected in step 1 above. At that time, as in step 1, the upper limit of the number of RBs assigned to the user of slice B is set so as not to exceed the slice setting policy (guaranteed allocated RB amount) determined by the slice management device. Finally, the resource is allocated to the user of slice C having the third highest priority (step 3). At this time, the RB having the best communication status is selected and assigned to the user of slice C from the RBs not selected in steps 1 and 2 above. At that time, as in steps 1 and 2, the upper limit of the number of RBs assigned to the user of slice C is set so as not to exceed the slice setting policy (guaranteed allocated RB amount) determined by the slice management device. After that, if there are surplus RBs that can be allocated, the process returns to step 1, and additional resource allocation is performed in order from the user of slice A until there are no RBs that can be allocated or there are no allocation requests.

FIG. 7B shows an example in which one user is allocated to each slice while emphasizing the priority of slices as the second method. First, resources are allocated to one user of slice A having the highest priority (step 1). At this time, the RB having the best communication status is selected and assigned to one user of slice A from the selectable RBs. Next, resources are allocated to one user of slice B having the second highest priority (step 2). At this time, the RB having the best communication status is selected and assigned to one user of slice B from the RBs not selected in step 1 above. Finally, the resource is allocated to one user of slice C having the third highest priority (step 3). At this time, the RB having the best communication status is selected and assigned to one user of slice C from the RBs not selected in steps 1 and 2 above. After that, if there are surplus RBs that can be allocated, the process returns to step 1, and additional resource allocation is performed in order from other users related to slice A until there are no RBs that can be allocated or there are no allocation requests. Do. However, in the additional resource allocation, the upper limit of the number of RBs allocated to the user of each slice is set so as not to exceed the slice setting policy (allocated RB amount guaranteed for each slice) determined by the slice management device.

FIG. 7C shows an example in which resources are allocated to the user terminal with an emphasis on the communication status of the user terminal as the third method. That is, all user terminals are assigned in order from the one with the best communication status. However, for a plurality of user terminals having almost the same communication status, resources are allocated based on the slice priority. In the example of FIG. 7C, one or more RBs are assigned to the user terminals of slices A to C in step 1 (first step). In this method 2, the RB amount allocated to the user terminal belonging to each slice is accumulated, and the cumulative RB amount for any slice reaches the slice setting policy (guaranteed allocated RB amount) determined by the slice management device. At that point, the resource allocation to all user terminals belonging to the slice is stopped. In the example of FIG. 7C, resource allocation to all user terminals belonging to slice C is stopped at the end of step 2 (second step). After that, resource allocation to user terminals belonging to other slices is continued. Then, if there is a surplus of RBs that can be allocated when the resource allocation is stopped for all slices, the resource allocation for all slices is restarted, and thereafter, in the same procedure until there are no RBs that can be allocated. Alternatively, resource allocation is performed until there are no allocation requests.

With the various scheduling methods described above, while maintaining the slice setting policy (allocated RB amount guaranteed for each slice), resource utilization efficiency is lower than when resources are divided for each slice on the frequency axis as in the past. Can be expected to have the effect of suppressing.

According to the present embodiment described above, it is possible to guarantee the resource allocation amount for each service while suppressing the decrease in resource utilization efficiency in the entire network.

The block diagram used in the description of the above embodiment shows a block of functional units. These functional blocks (components) are realized by any combination of hardware and / or software. Further, the means for realizing 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 by two or more physically and / or logically separated devices. (For example, wired and / or wireless) may be connected and realized by these plurality of devices.

For example, each device of FIG. 2 (for example, the RAN resource management device 30) may function as a computer that performs the above-described processing. FIG. 8 is a diagram showing an example of the hardware configuration of the RAN resource management device 30. The RAN resource management device 30 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. The configuration example of the RAN resource management device 30 will be described below, but the same applies to the other devices of FIG.

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

For each function in the RAN resource management device 30, the processor 1001 performs an operation by loading predetermined software (program) on hardware such as the processor 1001 and the memory 1002, and the communication device 1004 communicates with the memory 1002 and the memory 1002. It is realized by controlling the reading and / or writing of data in the storage 1003.

Processor 1001 operates, for example, an operating system to control the entire computer. The processor 1001 may be composed of a central processing unit (CPU) including an interface with a peripheral device, a control device, an arithmetic unit, a register, and the like. For example, each functional unit of the RAN resource management device 30 may be realized by including the processor 1001.

Further, the processor 1001 reads a program (program code), a software module, and data from the storage 1003 and / or the communication device 1004 into the memory 1002, and executes various processes according to these. As the program, a program that causes a computer to execute at least a part of the operations described in the above-described embodiment is used. For example, each functional unit of the RAN resource management device 30 may be stored in the memory 1002 and realized by a control program operating in the processor 1001, and other functional blocks may be realized in the same manner. Although it has been described that the various processes described above are executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. Processor 1001 may be mounted on 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 is composed of at least one such as a ROM (Read Only Memory), an EPROM (Erasable Programmable ROM), an EPROM (Electrically Erasable Programmable ROM), and a RAM (Random Access Memory). May be done. The memory 1002 may be referred to as a register, a cache, a main memory (main storage device), or the like. The memory 1002 can store a program (program code), a software module, or the like that can be executed to carry out the method according to the embodiment of the present invention.

The storage 1003 is a computer-readable recording medium, and is, for example, an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (for example, a compact disk, a digital versatile disk, or a Blu-ray). It may consist of at least one (registered trademark) disk), smart card, flash memory (eg, card, stick, key drive), floppy (registered trademark) disk, magnetic strip, and the like. The storage 1003 may be referred to as an auxiliary storage device. The storage medium described above may be, for example, a database, server or other suitable medium containing memory 1002 and / or storage 1003.

The communication device 1004 is hardware (transmission / reception device) for performing communication between computers via a wired and / or wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, or the like. For example, each functional unit of the above-mentioned RAN resource management device 30 may be realized by 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, etc.) 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 outputs to the outside. The input device 1005 and the output device 1006 may have an integrated configuration (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 composed of a single bus or may be composed of different buses between the devices.

Further, the RAN resource management device 30 includes hardware such as a microprocessor, a digital signal processor (DSP: Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array). It may be configured to include, and a part or all of each functional block may be realized by the hardware. For example, processor 1001 may be implemented on at least one of these hardware.

Although the present embodiment has been described in detail above, it is clear to those skilled in the art that the present embodiment is not limited to the embodiment described in the present specification. This embodiment can be implemented as an amended or modified mode without departing from the gist and scope of the present invention determined by the description of the claims. Therefore, the description herein is for purposes of illustration only and does not have any limiting implications for this embodiment.

The order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in the present specification may be changed as long as there is no contradiction. For example, the methods described herein present elements of various steps in an exemplary order, and are not limited to the particular order presented.

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

The determination may be made by a value represented by 1 bit (0 or 1), by a boolean value (Boolean: true or false), or by comparing numerical values (for example, a predetermined value). It may be done by comparison with the value).

Each aspect / embodiment described in the present specification may be used alone, in combination, or switched with execution. Further, the notification of predetermined information (for example, the notification of "being X") is not limited to the explicit notification, but is performed implicitly (for example, the notification of the predetermined information is not performed). May be good.

Software is an instruction, instruction set, code, code segment, program code, program, subprogram, software module, whether called software, firmware, middleware, microcode, hardware description language, or another name. , Applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, features, etc. should be broadly interpreted to mean.

Further, software, instructions, and the like may be transmitted and received via a transmission medium. For example, the software uses wired technology such as coaxial cable, fiber optic cable, twisted pair and digital subscriber line (DSL) and / or wireless technology such as infrared, wireless and microwave to websites, servers, or other 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 referred to throughout the above description may be voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. It may be represented by a combination of.

Further, the information, parameters, etc. described in the present specification may be represented by an absolute value, a relative value from a predetermined value, or another corresponding 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, etc. It may also be referred to as a wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term.

As used herein, the terms "determining" and "determining" may include a wide variety of actions. "Judgment" and "decision" are, for example, judgment, calculation, computing, processing, deriving, investigating, looking up (for example, table). , Searching in a database or another data structure), ascertaining can be considered as a "judgment" or "decision". Also, "judgment" and "decision" are receiving (for example, receiving information), transmitting (for example, transmitting information), input (input), output (output), and access. (Accessing) (for example, accessing data in memory) may be regarded as "judgment" or "decision". In addition, "judgment" and "decision" mean that "resolving", "selecting", "choosing", "establishing", "comparing", etc. are regarded as "judgment" and "decision". Can include. That is, "judgment" and "decision" may include that some action is regarded as "judgment" and "decision".

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

As long as "include", "including", and variations thereof are used within the scope of the present specification or claims, these terms are similar to the term "comprising". Is intended to be inclusive. Furthermore, the term "or" as used herein or in the claims is intended not to be an exclusive OR.

In the present specification, a plurality of devices shall be included unless the device is apparently only one in the context or technically. In the whole of this disclosure, the plural shall be included unless the context clearly indicates the singular.

1 ... Communication system, 10 ... UE, 20 ... Base station, 21 ... Base station scheduler, 22 ... User information holding unit, 30 ... RAN resource management device, 31 ... Slice setting unit, 32 ... Slice information holding unit, 40 ... Slice Management device, 41 ... Information acquisition unit, 42 ... Slice setting policy determination unit, 43 ... Slice information holding unit, 50 ... Service operation device, 60 ... Resource management device in RAN slice, 1001 ... Processor, 1002 ... Memory, 1003 ... Storage , 1004 ... communication device, 1005 ... input device, 1006 ... output device, 1007 ... bus.

Claims (4)

A resource management device in a RAN slice that allocates resources to services that use the virtual network and user terminals that enjoy the services for the RAN slice, which is a virtual network logically generated on the RAN.
The RAN slice is generated on a communication path between the user terminal and a service server that provides the service.
An information acquisition unit that acquires information necessary for slice generation, including service requirements that are requirements for functions or performance in the service provided using the virtual network.
Based on the information acquired by the information acquisition unit, the slice setting policy determination unit that determines the slice setting policy including the required resource allocation amount and resource allocation priority for each slice, and the slice setting policy determination unit.
At least, a slice setting unit that determines the amount of resources to be allocated to one or more RATs related to the slice based on the slice setting policy determined by the slice setting policy determination unit.
At least, a terminal allocation determination unit that determines resources to be allocated to user terminals that enjoy services in the slice based on the amount of resources to be allocated determined by the slice setting unit.
With
The terminal allocation determination unit
A sub-step for allocating resources to the user terminals in descending order of communication status of the user terminals, and for a plurality of user terminals having the same communication status, a sub-step for allocating resources to the user terminals in descending order of priority. When,
The amount of resources allocated to the user terminal related to each slice is accumulated, and when the accumulated resource amount related to any slice reaches the required resource allocation amount for each slice included in the slice setting policy, the slice is assigned. A sub-step to stop the resource allocation to the user terminal and
A method in which the process including the above is repeated until the resource is exhausted or the allocation request is exhausted.
To determine the resources to be allocated to the user terminal based on
Resource management device for RAN slices. The slice setting unit further determines the amount of resources to be allocated to the RAT based on the information of the user terminal that has made the service use request.
The resource management device for the RAN slice according to claim 1. The slice setting policy determination unit performs at least one of erasing slices, newly generating slices, and releasing and merging resources containing a plurality of RATs to regenerate slices, depending on the priority of resource allocation. decide,
The resource management device for the RAN slice according to claim 1 or 2. Resources in the RAN slice executed by the resource management device in the RAN slice that allocates resources to the services that use the virtual network and the user terminals that enjoy the services for the RAN slice, which is a virtual network logically generated on the RAN. It ’s a management method,
The RAN slice is generated on a communication path between the user terminal and a service server that provides the service.
An information acquisition step for acquiring information necessary for slice generation, including service requirements that are requirements for functions or performance in the service provided using the virtual network, and
Based on the information acquired by the information acquisition step, the slice setting policy determination step for determining the slice setting policy including the required resource allocation amount and the priority of resource allocation for each slice, and the slice setting policy determination step.
At least, a slice setting step that determines the amount of resources to be allocated to one or more RATs related to the slice based on the slice setting policy determined by the slice setting policy determination step.
At least, a terminal allocation determination step that determines resources to be allocated to user terminals that enjoy services in the slice based on the amount of resources to be allocated determined by the slice setting step.
With
The resource management device is
A sub-step for allocating resources to the user terminals in descending order of communication status of the user terminals, and for a plurality of user terminals having the same communication status, a sub-step for allocating resources to the user terminals in descending order of priority. When,
The amount of resources allocated to the user terminal related to each slice is accumulated, and when the accumulated resource amount related to any slice reaches the required resource allocation amount for each slice included in the slice setting policy, the slice is assigned. A sub-step to stop the resource allocation to the user terminal and
A method in which the process including the above is repeated until the resource is exhausted or the allocation request is exhausted.
To determine the resources to be allocated to the user terminal based on
Resource management method for RAN slices.

Images