Radio resource management configuration device and method

Abstract

The present invention provides a radio resource management (radio-resource management, RRM) configuration device (100) and a corresponding method for a network (200) including multiple access nodes. The device (100) is configured to divide a plurality of access nodes of the network (200) into clusters (201), and select at least one access node in each cluster (201) as an RRM controller (202). Furthermore, the device (100) is configured to determine non-selected access nodes in each cluster (201) as slave nodes (203), and select for each cluster (201) each slave node of the corresponding cluster (201) RRM partitioning between a node (203) and at least one RRM controller (202). The device (100) is further configured to send to each access node information about its cluster (201), at least one RRM controller (202) of the cluster (201) and the selected RRM partition.

Description

technical field [0001] The present invention relates to a radio resource management (radio resource management, RRM) configuration device and an RRM configuration method. In particular, the RRM configuration device and the method are used to select and activate at least one access node to act as an RRM controller for a plurality of other access nodes. Furthermore, the RRM configuration device and the method are used to determine at which access node to place and execute the RRM, ie specific RRM functions, especially when operating in a slice-aware network. The RRM configuration apparatus and the method are particularly suitable for heterogeneous networks (HetNets) where multiple 5G services and verticals share the same physical radio access network (RAN) deployment. Background technique [0002] As foreseen in some 5G scenarios, the explosive growth of capacity and coverage requirements has led to the evolution of traditional RANs to highly dense and heterogeneous deploymen...

AI Technical Summary

Problems solved by technology

[0021] However, selecting an RRM controller is challenging because the physical layout and size of the RRM controller play a large role in the efficiency of the RRM

A large number of RRM controllers will further provide more granular RRM, but in cases where these RRM controllers exist in different entities, this may cause high latency to communication between RRM controllers due to functional dependencies

On the other hand, a flat RRM controller for RAN will not allow RRM tailored for efficient slices since the impact of centralization will vary from slice to slice

Additionally, the backhaul function provides constraints on the placement of the RRM controller

Therefore, the RRM controller needs to be close to the access node, because factors such as control plane (C-Plane) delay are very important for dynamic resource allocation, otherwise the efficiency of RRM will be very low

Images