JP2019021953A - Resource management apparatus in RAN slice and resource management method in RAN slice - Google Patents

Abstract

To secure a resource allocation amount in each service while suppressing deterioration of a resource utilization efficiency in a whole network.SOLUTION: A resource management apparatus 60 in a RAN slice comprises: an information acquisition part 41 that acquires information which is required for generating a slice including a service requirement which is a requirement on a function or a performance in a service provided by using a virtual network; a slice setting principle determination part 42 that determines a slice setting principle including a resource allocation amount required and a priority of a resource allocation for each slice on the basis of the information acquired; a slice setting part 31 that determines a resource amount to be allocated to one or more RAT regarding the slice on the basis of at least the above slice setting principle; and a base station scheduler 21 (terminal allocation determination part) that determines the resource to be allocated to a user terminal receiving the service in the slice on the basis of at least the resource amount to be allocated.SELECTED DRAWING: Figure 2

Description

  The present invention relates to a resource management apparatus in a RAN slice and a resource management method in a RAN slice. In this specification, “RAN” means a radio access network, and “RAT” means a radio access technology such as LTE, 5G (fifth generation mobile phone). Mobile communication line such as telephone).

  In addition, “service” or “network service” in this specification refers to network resources such as a communication service (private line service, etc.) and an application service (service using a sensor device such as moving image distribution or an embedded device). Means a service processed using. A “slice” is a virtual network that is logically generated on the network infrastructure. The service is assigned to a slice and processed using the network resources of the assigned slice.

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

JP 2012-049598 A

  In recent years, it has been studied to apply a slicing technique that guarantees resource allocation by separating a virtual network for each service to a RAN. However, in the conventional resource allocation in the RAN, since prioritization for each service has not been studied much, it has been difficult to guarantee the resource allocation amount. If a method of simply allocating resources fixedly for each service is used to guarantee the resource allocation amount, there is a risk that resource partitioning loss will increase and resource utilization efficiency in the entire network may be reduced. .

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

  To achieve the above object, a resource management apparatus in a RAN slice according to an aspect of the present invention receives services and services using the virtual network for the RAN slice that is a virtual network logically generated on the RAN. A resource management apparatus in a RAN slice that allocates resources to a user terminal that uses the virtual network generated on a communication path between the user terminal and a service server that provides the service. Information acquisition unit for acquiring information necessary for slice generation, including service requirements that are functional or performance requirements in the service to be provided, and necessary resource allocation based on the information acquired by the information acquisition unit Slice setting policy including amount and resource allocation priority is determined for each slice. A slice setting policy determining unit that determines at least a resource amount to be allocated to one or more RATs related to the slice based on the slice setting policy determined by the slice setting policy determining unit; And a terminal allocation determination unit that determines a resource to be allocated to a user terminal that enjoys a service in the slice based on the allocated resource amount determined by the slice setting unit.

  In the resource management apparatus in the RAN slice described above, when the information acquisition unit acquires information necessary for slice generation, including service requirements that are functional or performance requirements in the service provided using the virtual network, slice setting is performed. Based on the acquired information, the policy determination unit determines a slice setting policy including a necessary resource allocation amount and resource allocation priority for each slice. Then, the slice setting unit determines a resource amount 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 determining unit at least determines the determined resource amount to be allocated Based on the above, the resource to be allocated to the user terminal that enjoys the service in the slice is determined. As described above, the slice is based on the slice setting policy (including necessary resource allocation amount and resource allocation priority) determined for each slice based on the information including the service requirement that is a function or performance requirement in the service. A resource amount to be allocated to one or more RATs according to the above is determined, and further, a resource to be allocated to a user terminal that enjoys a service in the slice is determined based on the resource amount 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 for each service as in the past, and further, it is possible to guarantee a resource allocation amount for each service. .

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

1 is a configuration diagram of a communication system according to an embodiment of the present invention. It is a figure which shows the functional block structure of each apparatus which comprises a communication system. It is a figure which shows an example of the information which the slice information holding part 43 hold | maintains. It is a figure which shows an example of the information which the slice information holding part 32 hold | maintains. It is a figure which shows an example of the information which the user information holding part 22 hold | maintains. It is a flowchart which shows the process which concerns on the resource management method in a RAN slice. (A) is a figure for demonstrating the 1st example of a scheduling system, (b) is a figure for demonstrating the 2nd example of a scheduling system, (c) is the 3rd of a scheduling system. It is a figure for demonstrating an example. It is a figure which shows the hardware structural example of each apparatus.

  DESCRIPTION OF EMBODIMENTS 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 denoted by the same reference numerals, and redundant description is omitted.

  FIG. 1 shows a configuration of a 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 to a UE (User Equipment) 10 that is a user terminal used by a user using data communication. Here, the UE 10 includes, for example, all portable terminals such as smartphones and tablet terminals.

  In the communication system 1, a network service is provided to the UE 10 by allocating a service to the RAN slice that is a virtual network. The RAN slice here is a virtualized network or service network that virtually divides 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 slice generation and management for each service, resource scheduling technology using MAC Scheduling (Media Access Control Scheduling), ANDSF (Access Network Discovery and Selection Function) / LWA (LTE Wi-Fi Link Aggregation) / MPTCP ( This can be realized by using a plurality of RAT (Radio Access Technology) coupling technologies or resource coupling technologies such as Multipath TCP).

  In the communication system 1, a part of a node that realizes communication necessary for the UE 10 to use a service is provided on a RAN slice that is a virtual network logically generated on the RAN. Therefore, the UE performs communication through a route passing through a node (hereinafter referred to as “base station 20” for convenience) such as a base station and an AP (Access Point) provided on the RAN slice. At that time, it is conceivable to perform communication by combining a plurality of RATs, and therefore there may be a plurality of base stations 20 constituting one RAN slice.

  Further, in the communication system 1, when communication is performed with a service server (service server # 1, # 2, etc. in FIG. 1) that provides a service for the UE 10 to use the service, a selection is made according to the service. The communication is performed via another slice. Specifically, in the communication system 1 illustrated in FIG. 1, the UE 10 includes a node set in a RAN slice and a node set in a core network (Core Network) slice (hereinafter referred to as “CN slice”). Via the service server. Therefore, the UE 10 provides a communication path with the service server via a total of two slices, the RAN slice and the CN slice. As described above, the communication system 1 in FIG. 1 shows a situation where slicing by so-called E2E (End-to-End) is realized.

  The E2E slice and the RAN slice and CN slice, which are constituent elements of the E2E slice, are set based on requirements (for example, allowable delay time, frequency band, etc.) required for the service. 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. Communicate 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, communication is performed with service server # 2 of service # 2. As described above, when using a specific service, the UE 10 performs communication by accessing the RAN slice and the CN slice determined in advance according to the service.

  Next, devices 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 an end-to-end slice based on the service requirements from the service operation device 50 and notifying the RAN resource management device 30 of a 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, a device having a newly defined slice selection function may be configured to have 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.

  Note that 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.

  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, requested delay, throughput, etc.) that are functional or performance requirements in a service provided using a virtual network by communicating with the service operation device 50. However, it has a function of acquiring information necessary for slice generation. The acquired information necessary for generating the slice is held by the slice information holding unit 43 and sent to the slice setting policy determining unit 42.

  Based on the information obtained from the information acquisition unit 41, the slice setting policy determination unit 42 determines, for each slice, a slice setting policy that includes a necessary resource allocation amount (allocated resource amount to be guaranteed) and resource allocation priority. It has a function. Information on the determined slice setting policy is held by the slice information holding unit 43 and also sent to the RAN resource management device 30. As an example of the slice setting policy, the slice setting policy determination unit 42 deletes a slice, generates a new slice, and releases and combines resources including a plurality of RATs according to the priority of resource allocation. At least one of regeneration may be determined.

  The slice information holding unit 43 has a function of holding information related to slices for services. The information related to the slice for the service includes information such as the name of the slice that is currently operated, the basic priority of the slice, the allocated resource amount to be guaranteed, the service content that uses the slice, and its service requirements. As shown in FIG. 3, the slice information holding unit 43 holds the service requirement sent from the service operation device 50 and information on the slice setting policy determined by the slice setting policy determining unit 42. Information relating to requirements (parameters A to B), slice priority, and guaranteed allocated resource amount are held for each slice. Thus, 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 resource amount to be allocated to one or more RATs related to the slice based on the slice setting policy sent from the slice management device 40. More specifically, the slice setting unit 31 selects and combines RATs that can generate resources related to the slices based on the slice setting policy, and determines an allocation resource amount guaranteed by each RAT. Information on the allocated resource amount guaranteed by each determined RAT is held by the slice information holding unit 32 and is sent to the base station 20 of each RAT.

  The slice information holding unit 32 has a function of holding information on the allocated resource amount guaranteed by each determined RAT. For example, as illustrated in FIG. 4, the slice information holding unit 32 includes a slice priority, a slice name, location information of a user who enjoys the service, an allocated resource amount guaranteed, an allocated resource amount guaranteed by each RAT, and the like. The information of is retained.

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

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

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

  Returning to FIG. 2, a method for managing resources in the RAN slice in the base station 20 will be described next. The base station 20 performs scheduling for the UE 10 based on the information on the allocated resource amount guaranteed for each slice sent from the RAN resource management device 30 and the information on the communication status 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, and the like. By using such communication status information, it is possible to obtain the expected communication success value when resources are allocated to the UE 10 at this time. By allocating many resources to the UE 10 having a high expected communication success value, an improvement in the overall throughput of the communication system 1 can be expected, and the resource utilization efficiency can be improved.

  2 described above, the information acquisition unit 41, the slice setting policy determination unit 42, the slice setting unit 31, and the base station scheduler 21 enclosed by the alternate long and short dash line in FIG. 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 apparatus notifies service requirements to the slice management apparatus (step S1). Next, the slice management device determines the resource amount 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 allocated resource amount guaranteed in each RAT (step S4) and notifies the base station (step S5).

  Then, when a service use request is generated, the UE notifies the base station (step S6). The base station notifies the RAN resource management apparatus of the notification received from the UE (step S7). The RAN resource management device re-determines resources to be allocated for each RAT based on the user information (step S8), and re-notifies the base station (step S9). The base station that has received 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 information on the communication status related to the UE based on the UL communication result (step S13). Thereafter, the base station and the UE repeatedly execute the processes in steps S10 to S13. Thereby, resource allocation to UE is performed appropriately.

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

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

  FIG. 7A shows an example in which resource allocation to user terminals is performed with emphasis on slice priority as a first method. First, resources are allocated to the user of slice A with the highest priority (step 1). At this time, the RB having 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 in the slice management device. Next, resources are allocated to the user of slice B having the second highest priority (step 2). At this time, for the user of slice B, the RB with the best communication status is selected and assigned from the RBs not selected in step 1 above. At this time, similarly to step 1, the upper limit of the number of RBs allocated to the user of slice B is set so as not to exceed the slice setting policy (guaranteed allocated RB amount) determined in the slice management apparatus. Finally, a resource is allocated to the user of slice C with the third highest priority (step 3). At this time, for the user of slice C, the RB having the best communication status is selected and assigned from the RBs not selected in steps 1 and 2 above. At this time, similarly to steps 1 and 2, the upper limit of the number of RBs allocated to the user of slice C is set so as not to exceed the slice setting policy (guaranteed allocated RB amount) determined in the slice management apparatus. After that, if there are remaining allocatable RBs, the process returns to step 1 and additional resources are allocated in order from the user of slice A until there is no allocatable RB or there is no allocation request in the same procedure.

  FIG. 7B shows an example in which resource allocation is performed by one user for each slice with priority given to 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, a resource is allocated to one user of slice B having the second highest priority (step 2). At this time, an 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, a resource is allocated to one user of slice C having the third highest priority (step 3). At this time, an 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 remaining RBs that can be allocated, the process returns to Step 1 and additional resources are allocated in order from other users related to slice A until there is no RB that can be allocated or there is no allocation request in the same procedure. 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 (the allocated RB amount guaranteed for each slice) determined in the slice management apparatus.

  FIG. 7C shows an example in which resource allocation to user terminals is performed with emphasis on the communication status of user terminals as a third method. That is, it assigns to all user terminals in order from the one with the best communication status. However, for a plurality of user terminals having substantially the same communication status, resource allocation is performed based on the priority of slices. In the example of FIG. 7C, one or more RBs are allocated to the user terminals of the slices A to C in Step 1 (first stage). In Method 2, the RB amount allocated to the user terminal belonging to each slice is accumulated, and the accumulated RB amount for any slice has reached the slice setting policy (guaranteed allocated RB amount) determined in the slice management device. At this point, 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 the slice C is stopped at the end of step 2 (second stage). Thereafter, resource allocation to user terminals belonging to other slices is continued. Then, if there are remaining RBs that can be allocated when resource allocation is stopped for all slices, resource allocation for all slices is resumed, and thereafter, until there are no allocable RBs in the same procedure Alternatively, resource allocation is performed until there is no allocation request.

  Using various scheduling methods as 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. The effect that it can suppress can be expected.

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

  The block diagram used in the description of the above embodiment shows 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 device physically and / or logically coupled, and two or more devices physically and / or logically separated may be directly and / or indirectly. (For example, wired and / or wireless) and may be realized by these plural devices.

  For example, each device in 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 illustrating an example of a 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. Hereinafter, a configuration example of the RAN resource management device 30 will be described, but the same applies to other devices in FIG.

  In the following description, the term “apparatus” 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 a plurality of the devices illustrated in the figure, or may be configured not to include some devices.

  Each function in the RAN resource management device 30 is read by a predetermined software (program) loaded on hardware such as the processor 1001 and the memory 1002, so that the processor 1001 performs an operation to perform communication by the communication device 1004, This is realized by controlling reading and / or writing of data in the storage 1003.

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

  Further, the processor 1001 reads a program (program code), software module, and data from the storage 1003 and / or the communication device 1004 to 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 embodiments is used. For example, each functional unit of the RAN resource management device 30 may be realized by a control program stored in the memory 1002 and operated by the processor 1001, or may be realized similarly for other functional blocks. Although the above-described various processes have been described as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. Note that the program may be transmitted from a network via a telecommunication line.

  The memory 1002 is a computer-readable recording medium and includes, for example, at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), and the like. May be. The memory 1002 may be called 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, and the like that can be executed to perform the method according to the embodiment of the present invention.

  The storage 1003 is a computer-readable recording medium, such as an optical disc such as a CD-ROM (Compact Disc ROM), a hard disc drive, a flexible disc, a magneto-optical disc (eg, a compact disc, a digital versatile disc, a Blu-ray). (Registered trademark) disk, smart card, flash memory (for example, 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 including the memory 1002 and / or the 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 a network device, a network controller, a network card, a communication module, or the like. For example, each functional unit of the RAN resource management device 30 described above may be realized including the communication device 1004.

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

  Each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured with a single bus or may be configured with different buses between apparatuses.

  The RAN resource management device 30 includes hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), and a field programmable gate array (FPGA). A part or all of each functional block may be realized by the hardware. For example, the processor 1001 may be implemented by at least one of these hardware.

  Although the present embodiment has been described in detail above, it will be apparent to those skilled in the art that the present embodiment is not limited to the embodiment described in this specification. The present embodiment can be implemented as a modification and change without departing from the spirit and scope of the present invention defined by the description of the scope of claims. Therefore, the description of the present specification is for illustrative purposes and does not have any limiting meaning to the present embodiment.

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

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

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

  Each aspect / embodiment described in this specification may be used independently, may be used in combination, or may be switched according to execution. In addition, notification of predetermined information (for example, notification of being “X”) is not limited to explicitly performed, but is performed implicitly (for example, notification of the predetermined information is not performed). Also good.

  Software, whether it is called software, firmware, middleware, microcode, hardware description language, or other names, instructions, instruction sets, codes, code segments, program codes, programs, subprograms, software modules , Applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc. should be interpreted broadly.

  Also, software, instructions, etc. may be transmitted / received via a transmission medium. For example, software may use websites, servers, or other devices using 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. When transmitted from a remote source, these wired and / or wireless technologies are included within the definition of transmission media.

  Information, signals, etc. described herein may be represented using any of a variety of different technologies. For example, data, commands, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description are voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these May be represented by a combination of

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

  A mobile communication terminal is defined by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, It may also be referred to as a wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate terminology.

  As used herein, the terms “determining” and “determining” may encompass a wide variety of actions. “Judgment” and “determination” are, for example, judgment, calculation, calculation, processing, derivation, investigating, looking up (eg, table , Searching in a database or another data structure), considering ascertaining as “determining”, “deciding”, and the like. In addition, “determination” and “determination” include receiving (for example, receiving information), transmitting (for example, transmitting information), input (input), output (output), and access. (accessing) (e.g., accessing data in a memory) may be considered as "determined" or "determined". In addition, “determination” and “decision” means that “resolving”, “selecting”, “choosing”, “establishing”, and “comparing” are regarded as “determining” and “deciding”. May be included. In other words, “determination” and “determination” may include considering some operation as “determination” and “determination”.

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

  These terms are similar to the term “comprising” as long as “include”, “including”, and variations thereof are used herein or in the claims. It is intended to be comprehensive. Furthermore, the term “or” as used herein or in the claims is not intended to be an exclusive OR.

  In this specification, a plurality of devices are also included unless there is only one device that is clearly present in context or technically. Throughout this disclosure, the plural is included unless the context clearly indicates one.

  DESCRIPTION OF SYMBOLS 1 ... Communication system, 10 ... UE, 20 ... Base station, 21 ... Base station scheduler, 22 ... User information holding part, 30 ... RAN resource management apparatus, 31 ... Slice setting part, 32 ... Slice information holding part, 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 (8)

A resource management device in a RAN slice that allocates resources to a user terminal that enjoys a service and service using the virtual network for a RAN slice that 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 functional or performance requirements in the service provided using the virtual network;
Based on the information acquired by the information acquisition unit, a slice setting policy determination unit that determines a slice setting policy including a necessary resource allocation amount and resource allocation priority for each slice;
A slice setting unit that determines an amount of resources to be allocated to one or more RATs related to the slice based on at least the slice setting policy determined by the slice setting policy determination unit;
A terminal allocation determination unit that determines a resource to be allocated to a user terminal that enjoys a service in the slice, based on at least the allocated resource amount determined by the slice setting unit;
A resource management device in a RAN slice. The terminal allocation determining unit determines a resource to be allocated to the user terminal based on at least one of a priority of resource allocation regarding a slice related to the user terminal and a communication status of the user terminal;
The resource management apparatus in the RAN slice according to claim 1. The terminal allocation determination unit
A sub-step of allocating resources to user terminals related to the highest priority slice;
A sub-step of allocating resources from the remaining resources to a user terminal related to the slice having the next highest priority;
From the remaining resources, a sub-step of allocating resources to the user terminals related to the slices in descending order of priority,
A first method that repeats the process including: until the resource is exhausted or the allocation request is exhausted,
Determining resources to be allocated to the user terminal based on
The resource management apparatus in the RAN slice according to claim 2. The terminal allocation determination unit
A sub-step of allocating resources to one user terminal related to the slice having the highest priority;
A sub-step of allocating resources to one user terminal related to a slice having the next highest priority from the remaining resources;
A sub-step of allocating resources to one user terminal related to a slice from the remaining resources in order of higher priority thereafter;
A second method that repeats the process including: until the resource is exhausted or the allocation request is exhausted,
Determining resources to be allocated to the user terminal based on
The resource management apparatus in the RAN slice according to claim 2. The terminal allocation determination unit
A sub-step of allocating resources to the user terminals in order of good communication status, and a sub-step of allocating resources to the user terminals in descending order of priority for a plurality of user terminals having the same communication status;
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, A sub-step for stopping resource allocation to the user terminal;
A third method that repeats the process including: until the resource is exhausted or the allocation request is exhausted,
Determining resources to be allocated to the user terminal based on
The resource management apparatus in the RAN slice according to claim 2. The slice setting unit further determines the resource amount to be allocated to the RAT based on information on a user terminal that has made a service use request.
The resource management apparatus in the RAN slice according to any one of claims 1 to 5. The slice setting policy determining unit performs at least one of slice deletion, new slice generation, and slice regeneration by releasing and combining resources including a plurality of RATs according to the resource allocation priority. decide,
The resource management apparatus in the RAN slice according to any one of claims 1 to 6. A resource in a RAN slice, which is executed by a resource management device in a RAN slice that allocates resources to a user terminal that uses the virtual network and a user terminal that enjoys the service for a RAN slice that is a virtual network logically generated on the RAN 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 of acquiring information necessary for slice generation, including service requirements that are functional or performance requirements in the service provided using the virtual network;
A slice setting policy determination step for determining, for each slice, a slice setting policy including a necessary resource allocation amount and a priority of resource allocation based on the information acquired by the information acquisition step;
A slice setting step for determining a resource amount to be allocated to one or more RATs related to the slice based on at least the slice setting policy determined by the slice setting policy determination step;
At least a terminal allocation determination step for determining resources to be allocated to user terminals that enjoy services in the slice, based on the allocated resource amount determined by the slice setting step;
A resource management method in a RAN slice.

Images