Priority bit rate based slice control

CN121128227APending Publication Date: 2025-12-12ALCATEL LUCENT SHANGHAI BELL CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380098292.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-03-16
Publication Date
2025-12-12

Smart Images

  • Figure CN121128227A_ABST
    Figure CN121128227A_ABST
Patent Text Reader

Abstract

Disclosed is a method comprising determining an expected priority bit rate for each of one or more logical channels based at least on a spectral efficiency of at least one user equipment and a target share of a slice, the at least one user equipment being configured to communicate with the slice via the logical channels, wherein the target share indicates an expected proportion of radio resources allocated for a slice in a cell divided into a plurality of slices; and sending a message to the at least one user equipment, the message indicating at least an expected priority bit rate for each of the one or more logical channels.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The following example embodiments relate to wireless communication and network slicing. Background Technology

[0002] Network slicing is a technique that can be used in communication networks to create multiple logical networks (or "slices") on top of a single physical network infrastructure. Summary of the Invention

[0003] The scope of protection sought by the various example embodiments is defined by the independent claims. Example embodiments and features (if any) described in this specification that do not fall within the scope of the independent claims should be interpreted as examples helpful in understanding the various embodiments.

[0004] According to one aspect, an apparatus is provided, comprising at least one processor and at least one memory, the memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: determine an expected priority bit rate for each of one or more logical channels, based at least on the spectral efficiency of at least one user equipment and a target share of a slice, wherein the at least one user equipment is configured to communicate with the slice via the logical channels, wherein the target share indicates an expected proportion of radio resources allocated to the slice in a cell divided into multiple slices; and send a message to the at least one user equipment, the message indicating at least the expected priority bit rate for each of the one or more logical channels.

[0005] According to another aspect, an apparatus is provided, comprising: components for determining an expected priority bit rate for each of one or more logical channels based at least on the spectral efficiency of at least one user equipment and a target share of a slice, the at least one user equipment being configured to communicate with the slice via the logical channels, wherein the target share indicates an expected proportion of radio resources allocated to the slice in a cell divided into multiple slices; and components for sending a message to the at least one user equipment, the message indicating at least the expected priority bit rate for each of the one or more logical channels.

[0006] According to another aspect, a method is provided, comprising: determining an expected priority bit rate for each of one or more logical channels based at least on the spectral efficiency of at least one user equipment and a target share of a slice, wherein the at least one user equipment is configured to communicate with the slice via the logical channels, wherein the target share indicates an expected proportion of radio resources allocated to the slice in a cell divided into multiple slices; and sending a message to the at least one user equipment, the message indicating at least the expected priority bit rate for each of the one or more logical channels.

[0007] According to another aspect, a computer program is provided, the computer program including instructions that, when executed by a device, cause the device to perform at least the following: determining an expected priority bit rate for each of one or more logical channels based at least on the spectral efficiency of at least one user equipment and a target share of a slice, the at least one user equipment being configured to communicate with the slice via the logical channels, wherein the target share indicates an expected proportion of radio resources allocated to the slice in a cell divided into multiple slices; and sending a message to the at least one user equipment, the message indicating at least the expected priority bit rate for each of the one or more logical channels.

[0008] According to another aspect, a computer-readable medium is provided, including program instructions that, when executed by an apparatus, cause the apparatus to perform at least the following: determining an expected priority bit rate for each of one or more logical channels based at least on the spectral efficiency of at least one user equipment and a target share of a slice, wherein the at least one user equipment is configured to communicate with the slice via the logical channels, wherein the target share indicates an expected proportion of radio resources allocated to the slice in a cell divided into multiple slices; and sending a message to the at least one user equipment that at least indicates the expected priority bit rate for each of the one or more logical channels.

[0009] According to another aspect, a non-transitory computer-readable medium is provided, comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least the following: determining an expected priority bit rate for each of one or more logical channels based at least on the spectral efficiency of at least one user equipment and a target share of a slice, wherein the at least one user equipment is configured to communicate with the slice via the logical channels, wherein the target share indicates an expected proportion of radio resources allocated to the slice in a cell divided into multiple slices; and sending a message to the at least one user equipment that at least indicates the expected priority bit rate for each of the one or more logical channels.

[0010] According to another aspect, an apparatus is provided, comprising at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: receive a message indicating at least an expected priority bit rate for each of one or more logical channels; and configure one or more logical channels by at least applying the expected priority bit rate for each of the one or more logical channels, wherein the expected priority bit rate is based at least on the spectral efficiency of the apparatus and a target share of a slice, the apparatus being configured to communicate with the slice via the logical channel, wherein the target share indicates an expected proportion of radio resources allocated to the slice in a cell divided into multiple slices.

[0011] According to one aspect, an apparatus is provided, comprising: a component for receiving a message indicating at least an expected priority bit rate for each of one or more logical channels; and a component for configuring one or more logical channels by applying at least the expected priority bit rate for each of the one or more logical channels, wherein the expected priority bit rate is based at least on the spectral efficiency of the apparatus and a target share of a slice, the apparatus being configured to communicate with the slice via the logical channel, wherein the target share indicates an expected proportion of radio resources allocated to the slice in a cell divided into multiple slices.

[0012] According to another aspect, a method is provided, comprising: receiving a message indicating at least an expected priority bit rate for each of one or more logical channels; and configuring one or more logical channels by applying at least the expected priority bit rate for each of the one or more logical channels, wherein the expected priority bit rate is based at least on the spectral efficiency of the device and a target share of a slice, the device being configured to communicate with the slice via the logical channel, wherein the target share indicates an expected proportion of radio resources allocated to the slice in a cell divided into multiple slices.

[0013] According to another aspect, a computer program is provided, the computer program including instructions that, when executed by a device, cause the device to perform at least the following: receiving a message indicating at least an expected priority bit rate for each of one or more logical channels; and configuring one or more logical channels by applying at least the expected priority bit rate for each of the one or more logical channels, wherein the expected priority bit rate is based at least on the spectral efficiency of the device and a target share of a slice, the device being configured to communicate with the slice via the logical channel, wherein the target share indicates an expected proportion of radio resources allocated to the slice in a cell divided into multiple slices.

[0014] According to another aspect, a computer-readable medium is provided, including program instructions that, when executed by a device, cause the device to perform at least the following: receiving a message indicating at least an expected priority bit rate for each of one or more logical channels; and configuring one or more logical channels by applying at least the expected priority bit rate for each of the one or more logical channels, wherein the expected priority bit rate is based at least on the spectral efficiency of the device and a target share of a slice, the device being configured to communicate with the slice via the logical channel, wherein the target share indicates an expected proportion of radio resources allocated to the slice in a cell divided into multiple slices.

[0015] According to another aspect, a non-transitory computer-readable medium is provided, including program instructions that, when executed by a device, cause the device to perform at least the following: receiving a message indicating at least an expected priority bit rate for each of one or more logical channels; and configuring one or more logical channels by applying at least the expected priority bit rate for each of the one or more logical channels, wherein the expected priority bit rate is based at least on the spectral efficiency of the device and a target share of a slice, the device being configured to communicate with the slice via the logical channel, wherein the target share indicates an expected proportion of radio resources allocated to the slice in a cell divided into multiple slices.

[0016] According to another aspect, a system is provided, comprising at least one user equipment (UE) and a network node of a radio access network. The network node is configured to: determine an expected priority bit rate for each of one or more logical channels based at least on the spectral efficiency of the at least one UE and a target share of a slice, the at least one UE being configured to communicate with the slice via the logical channel, wherein the target share indicates an expected proportion of radio resources allocated to the slice in a cell divided into multiple slices; and send a message to the at least one UE, the message indicating at least the expected priority bit rate for each of the one or more logical channels. The at least one UE is configured to: receive a message indicating at least the expected priority bit rate for each of the one or more logical channels; and configure the one or more logical channels by applying at least the expected priority bit rate for each of the one or more logical channels.

[0017] According to another aspect, a system is provided, comprising at least one user equipment and a network node of a radio access network. The network node includes: components for determining an expected priority bit rate for each of one or more logical channels based at least on the spectral efficiency of the at least one user equipment and a target share of a slice, the at least one user equipment being configured to communicate with the slice via the logical channel, wherein the target share indicates an expected proportion of radio resources allocated to the slice in a cell divided into multiple slices; and components for sending a message to the at least one user equipment, the message indicating at least the expected priority bit rate for each of the one or more logical channels. The at least one user equipment includes: components for receiving a message indicating at least the expected priority bit rate for each of the one or more logical channels; and components for configuring the one or more logical channels by applying at least the expected priority bit rate for each of the one or more logical channels. Attached Figure Description

[0018] In the following description, various exemplary embodiments will be described in more detail with reference to the accompanying drawings, in which:

[0019] Figure 1 An example of a wireless communication network is shown;

[0020] Figure 2 An example of the system is shown;

[0021] Figure 3 An example of a logical channel is shown;

[0022] Figure 4 The signal flow graph is shown;

[0023] Figure 5 A flowchart is shown;

[0024] Figure 6 A flowchart is shown;

[0025] Figure 7 A flowchart is shown;

[0026] Figure 8 An example of the device is shown; and

[0027] Figure 9 An example of the device is shown. Detailed Implementation

[0028] The following embodiments are merely exemplary. Although this specification may refer to "a," "an," or "some" embodiments in multiple places throughout the text, this does not necessarily mean that each reference refers to the same embodiment(s), or that a particular feature applies only to a single embodiment. Individual features of different embodiments may also be combined to provide other embodiments.

[0029] Some of the example embodiments described herein can be implemented in a wireless communication network, including a radio access network based on one or more of the following radio access technologies: Global System for Mobile Communications (GSM) or any other second-generation radio access technology, Universal Mobile Telecommunications System (UMTS, 3G) based on Basic Wideband Code Division Multiple Access (W-CDMA), High-Speed ​​Packet Access (HSPA), Long Term Evolution (LTE), LTE Advanced, Fourth Generation (4G), Fifth Generation (5G), 5G New Radio (NR), 5G Advanced (i.e., 3GPP NR Rel-18 and later), or Sixth Generation (6G). Some examples of radio access networks include Universal Mobile Telecommunications System (UMTS) Radio Access Network (UTRAN), Evolved Universal Terrestrial Radio Access Network (E-UTRA), or Next Generation Radio Access Network (NG-RAN). The wireless communication network may also include a core network, and some example embodiments may also be applied to the network functions of the core network.

[0030] It should be noted that these embodiments are not limited to the wireless communication networks given as examples, but those skilled in the art can also apply this solution to other wireless communication networks or systems that are provided with the necessary properties. For example, some example embodiments can also be applied to communication systems based on the IEEE 802.11 standard or communication systems based on the IEEE 802.15 standard.

[0031] Figure 1 An example of a simplified wireless communication network is depicted, showing some physical and logical entities. Figure 1 The connection shown can be a physical connection or a logical connection. It will be apparent to those skilled in the art that the wireless communication network may also include, in addition to... Figure 1 Other physical and logical entities besides those shown.

[0032] However, the exemplary embodiments described herein are not limited to the wireless communication networks given as examples, but those skilled in the art can apply the embodiments described herein to other wireless communication networks that are provided with the necessary properties.

[0033] Figure 1 The example wireless communication network shown includes an access network (such as a radio access network (RAN)) and a core network 110.

[0034] Figure 1 User equipment (UE) 100 and 102 are illustrated, configured to wirelessly connect to an access node (AN) 104 of an access network on one or more communication channels in a radio cell. AN 104 may be an evolved Node B (eNB or eNodeB) or a next-generation Node B (gNB or gNodeB) providing the radio cell. A wireless connection from the UE to the access node 104 (e.g., a radio link) may be referred to as an uplink (UL) or a reverse link, while a wireless connection from the access node to the UE (e.g., a radio link) may be referred to as a downlink (DL) or a forward link. UE 100 may also communicate directly with UE 102 via a wireless connection commonly referred to as a sidelink (SL), and vice versa. It should be understood that the access node 104 or its functionality can be implemented using any entity suitable for providing these functions, such as a node, host, server, or access point.

[0035] An access network may include more than one access node, in which case the access nodes may be configured to communicate with each other via wired or wireless links. These links between access nodes may be used to send and receive control plane signaling, or to route data from one access node to another.

[0036] An access node may include a computing device configured to control the access node's radio resources. The access node may also be referred to as a base station, base transceiver station (BTS), access point, radio access node, or any other type of node capable of wirelessly connecting to a UE (e.g., UE 100, 102). The access node may include or be coupled to a transceiver. From the transceiver of the access node, a connection may be provided to an antenna element that establishes a bidirectional radio link to UE 100, 102. The antenna element may include one antenna or antenna element, or multiple antennas or antenna elements.

[0037] Access node 104 can also be connected to core network (CN) 110. Core network 110 may include an evolved packet core (EPC) network and / or a fifth-generation core network (5GC). EPC may include network entities such as serving gateways (S-GW for routing and forwarding packets), packet data network gateways (P-GW) for providing connectivity between the UE and external packet data networks, and mobility management entities (MME). 5GC may include network functions such as user plane functions (UPF), access and mobility management functions (AMF), and location management functions (LMF).

[0038] The core network 110 may also be able to communicate with one or more external networks 113, such as the public switched telephone network or the Internet, or utilize services provided by them. For example, in a 5G wireless communication network, the UPF of the core network 110 may be configured to communicate with an external data network via the N6 interface. In an LTE wireless communication network, the P-GW of the core network 110 may be configured to communicate with an external data network.

[0039] The UEs 100 and 102 shown are devices of a type to which resources on the air interface can be allocated and assigned. UEs 100 and 102 may also be referred to as wireless communication devices, subscriber units, mobile stations, remote terminals, access terminals, user terminals, terminal equipment, or user equipment, to name just a few. A UE may be a computing device with or without a Subscriber Identity Module (SIM), including but not limited to the following types of computing devices: mobile phones, smartphones, personal digital assistants (PDAs), handheld devices, computing devices including wireless modems (e.g., alarm or measuring devices), laptops, desktop computers, tablets, game consoles, laptops, multimedia devices, redcap devices, wearable devices with radio components (e.g., watches, headphones, or glasses), sensors including wireless modems, or any computing device including wireless modems integrated into a vehicle.

[0040] Any UE-specific features described herein can also be implemented using corresponding devices, such as relay nodes. An example of such a relay node could be a Layer 3 relay (self-backhaul relay) toward an access node. A self-backhaul relay node can also be referred to as an Integrated Access and Backhaul (IAB) node. An IAB node can comprise two logical parts: a Mobile Termination (MT) part, which is responsible for (multiple) backhaul links (i.e., (multiple) links between the IAB node and the donor node, also referred to as the parent node) and a Distributed Unit (DU) part, which is responsible for (multiple) access links, i.e., (multiple) sub-links between the IAB node and (multiple) UEs, and / or (multiple) sub-links between the IAB node and other IAB nodes (in multi-hop scenarios).

[0041] Another example of such a relay node might be a Layer 1 relay known as a repeater. A repeater can amplify signals received from an access node and forward them to the UE, and / or amplify signals received from a UE and forward them to the access node.

[0042] It should be understood that a UE can also be a nearly exclusive uplink-only device; one example might be a camera or camcorder that loads images or video clips onto the network. A UE can also be a device capable of operating in an Internet of Things (IoT) network, a scenario where objects can be provided with the ability to transmit data over the network without requiring human-to-human or human-to-computer interaction. A UE can also leverage the cloud. In some applications, computation can be performed in the cloud or within another UE.

[0043] Wireless communication networks can also support the use of cloud services; for example, at least a portion of core network operations can be performed as a cloud service (this is in...). Figure 1 (Described by “Cloud” 114). The communication system may also include a central control entity, etc., providing facilities for wireless communication networks of different operators to cooperate, for example, in spectrum sharing.

[0044] The various techniques described in this article can also be applied to cyber-physical systems (CPS) (systems that control collaborative computing elements of physical entities). CPS enables and utilizes a large number of interconnected ICT devices (sensors, actuators, processors, microcontrollers, etc.) embedded in physical objects in different locations. Mobile cyber-physical systems, where the physical systems under discussion may have inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robotics and electronics transported by humans or animals.

[0045] 5G enables the use of multiple-input multiple-output (MIMO) antennas in access nodes 104 and / or UEs 100, 102, far more base stations or access nodes than LTE networks (the so-called small cell concept), including macro sites operating in cooperation with smaller sites, and employing a variety of radio technologies depending on service requirements, use cases, and / or available spectrum. 5G wireless communication networks can support a wide range of use cases and related applications, including video streaming, augmented reality, different data sharing methods, and various forms of machine-type applications such as (large) machine-type communications (MMTC), including vehicle safety, various sensors, and real-time control.

[0046] In 5G wireless communication networks, access nodes and / or UEs may have multiple radio interfaces, namely sub-6GHz, cmWave, and mmWave, and can also be integrated with existing legacy radio access technologies such as LTE. Integration with LTE can be achieved, for example, as a system where macro coverage can be provided by LTE, while 5G radio interface access comes from small cells via aggregation to LTE. In other words, 5G wireless communication networks can support both RAT inter-operability (such as LTE-5G) and RI inter-operability (radio interface inter-operability, such as sub-6GHz-cmWave-mmWave). One concept that will be used in 5G wireless communication networks is network slicing, where multiple independent and dedicated virtual subnetworks (network instances) can be created on essentially the same infrastructure to run services with different requirements for latency, reliability, throughput, and mobility.

[0047] 5G enables analytics and knowledge generation to occur at the data source. This approach may involve leveraging resources that may not be continuously connected to the network, such as laptops, smartphones, tablets, and sensors. Multi-access edge computing (MEC) can provide a distributed computing environment for application and service hosting. It can also have the ability to store and process content in the vicinity of cellular subscribers to accelerate response times. Edge computing can encompass a variety of technologies, such as wireless sensor networks, mobile data acquisition, mobile signature analytics, collaborative distributed peer-to-peer self-organizing networks and processing (which can also be categorized as local cloud / fog computing and grid / mesh computing), dew computing, mobile edge computing, cloud, distributed data storage and retrieval, autonomous self-healing networks, remote cloud services, augmented reality and virtual reality, data caching, the Internet of Things (IoT) (massive connectivity and / or latency critical), and critical communications (autonomous vehicles, traffic safety, real-time analytics, time-critical control, healthcare applications).

[0048] In some exemplary embodiments, an access node (e.g., access node 104) may include: a radio unit (RU) including radio transceivers (TRXs), i.e., transmitters (Tx) and receivers (Rx); one or more distributed units (DUs) 105, which may be used for so-called Layer 1 (L1) processing and real-time Layer 2 (L2) processing; and a central unit (CU) 108 (also referred to as a centralized unit), which may be used for non-real-time Layer 2 and Layer 3 (L3) processing. The CU 108 may be connected to one or more DUs 105 via, for example, an F1 interface. Such embodiments of the access node allow for the centralization of the CU relative to the cell site and the DU, while the DU can be more distributed, or even retained at the cell site. The CU and DU may also be collectively referred to as baseband or baseband unit (BBU). The CU and DU may also be included in a radio access point (RAP).

[0049] CU 108 may be a logical node carrying Radio Resource Control (RRC), Serving Data Adaptive Protocol (SDAP), and / or Packet Data Convergence Protocol (PDCP) for the NR protocol stack of the access node. DU 105 may be a logical node carrying Radio Link Control (RLC), Media Access Control (MAC), and / or Physical Layer (PHY) for the NR protocol stack of the access node. The operation of the DU may be at least partially controlled by the CU. It should also be understood that the functional allocation between DU 105 and CU 108 may vary depending on the implementation. CU may include a control plane (CU-CP), which may be a logical node carrying the control plane portions of the RRC and PDCP protocols for the NR protocol stack of the access node. CU may also include a user plane (CU-UP), which may be a logical node carrying the user plane portions of the PDCP and SDAP protocols for the CU of the access node.

[0050] Cloud computing systems can also be used to provide CU 108 and / or DU 105. CUs provided by cloud computing systems can be referred to as virtualized CUs (vCUs). In addition to vCUs, virtualized DUs (vDUs) provided by cloud computing systems can also exist. Furthermore, combinations can exist where DUs can be implemented with respect to so-called bare-metal solutions, such as application-specific integrated circuits (ASICs) or customer-specific standard products (CSSPs) system-on-chips (SoCs).

[0051] Edge cloud can be introduced into the access network (e.g., RAN) by leveraging Network Functions Virtualization (NFV) and Software-Defined Networking (SDN). Using edge cloud may mean that access node operations are performed, at least partially, in a computing system coupled to the access node's Remote Radio Head (RRH) or Radio Unit (RU). Access node operations may also be performed on a distributed computing system or cloud computing system located at the access node. The application of cloud RAN architecture enables real-time RAN functions to be performed in the access network (e.g., in DU 105), while non-real-time functions can be performed centrally (e.g., in CU 108).

[0052] It should also be understood that in future wireless communication networks, the functional allocation between core network operations and access node operations will differ from, and may even not exist, compared to LTE or 5G. Some other technological advancements that can be utilized include big data and all-IP, which may transform how wireless communication networks are built and managed. 5G (or New Radio, NR) wireless communication networks can support multi-tiered architectures, where multi-access edge computing (MEC) servers can be placed between the core network 110 and access nodes 104. It should be understood that MEC can also be applied to LTE wireless communication networks.

[0053] 5G wireless communication networks (“5G networks”) can also include non-terrestrial communication networks (such as satellite communication networks) to enhance or supplement the coverage of 5G radio access networks. For example, satellite communications can support the transmission of data between the 5G radio access network and the core network, thereby enabling wider network coverage. Possible use cases could be providing service continuity for machine-to-machine (M2M) or Internet of Things (IoT) devices or vehicular passengers, or ensuring service availability for critical communications and future rail / maritime / aviation communications. Satellite communications can utilize geostationary orbit (GEO) satellite systems or low Earth orbit (LEO) satellite systems, particularly mega-constellations (systems in which hundreds of (nano) satellites are deployed). A given satellite 106 in a mega-constellation can cover several network entities supporting the satellites, which can create terrestrial cells. Terrestrial cells can be created by ground relay access nodes or by access nodes 104 located on the ground or in satellites.

[0054] It is obvious to those skilled in the art that Figure 1The access node 104 shown is merely an example of a portion of an access network (e.g., a wireless access network). In reality, an access network may include multiple access nodes, UEs 100 and 102 may have access to multiple wireless cells, and the access network may also include other devices, such as physical layer relay access nodes or other entities. At least one of the access nodes may be a home eNodeB or a home gNodeB. A home gNodeB or home eNodeB is a type of access node that can be used to provide indoor coverage in homes, offices, or other indoor environments.

[0055] Additionally, multiple different types of wireless cells and multiple wireless cells can be provided within the geographical area of ​​the access network (e.g., a wireless access network). Wireless cells can be macrocells (or umbrella cells), which can be large cells with diameters of up to tens of kilometers, or smaller cells such as micro, femtocells, or picocells. Figure 1 Multiple access nodes can provide any type of cell. A cellular wireless network can be implemented as a multi-layered access network that includes several types of wireless cells. In a multi-layered access network, one access node can provide one or more types of wireless cells, therefore multiple access nodes may be required to provide such a multi-layered access network.

[0056] To meet the need for improved access network performance, the concept of "plug-and-play" access nodes can be introduced. Access networks that may be able to use "plug-and-play" access nodes, besides the home eNodeB or home gNodeB, may also include the home Node B gateway or HNB-GW (Host Node B Gateway). Figure 1 (Not shown in the image). An HNB-GW, which can be installed in the operator's access network, can aggregate services from a large number of home eNodeBs or home gNodeBs back to the operator's core network.

[0057] 6G wireless communication networks are expected to leverage local spectrum licensing, spectrum sharing, infrastructure sharing, and intelligent automated management based on mobile edge computing, artificial intelligence, short packet communication, and blockchain technology to adopt flexible decentralized and / or distributed computing systems and architectures and ubiquitous computing. Key features of 6G may include intelligent interconnected management and control capabilities, programmability, integrated sensing and communication, reduced energy footprint, reliable infrastructure, scalability, and affordability. In addition, 6G targets new use cases encompassing the integration of location and sensing capabilities into the system definition to unify the user experience in the physical and digital worlds.

[0058] Some services, such as enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC), may have high requirements for high bandwidth, low latency, and ultra-reliability. Network slicing is a technology enabler that can simultaneously support these services with service differentiation and guaranteed performance.

[0059] Network slicing is a technology that can be used in communication networks to create multiple logical networks (or "slices") on top of a single physical network infrastructure. A given slice is a self-contained network with its own characteristics, such as bandwidth, latency, security, and Quality of Service (QoS), tailored to meet the needs of a specific set of users or applications. Network slicing allows network operators to optimize their resources and deliver customized services to different types of customers. Therefore, network slicing can operate on a shared physical infrastructure while accommodating several independent logical networks for different business needs and Service Level Agreement (SLA) requirements. Network slicing may refer to RAN, transport, and core network slices.

[0060] Some example implementations relate to RAN slicing. RAN slicing is a technology in network slicing that allows multiple logical networks (or "slices") to share a common physical RAN infrastructure. Using RAN slicing, network operators can support multiple slices (e.g., Public Land Mobile Networks (PLMNs)) with agreed-upon RAN resource shares as indicated by SLAs, and network operators can customize resources for given service characteristics, services, and SLAs.

[0061] Figure 2 An example of a network management system (tenant slicing portal system) 200 is shown, which has a wireless intelligent controller (RIC) 210, a gNB 220, and a UE 230. The gNB 220 can correspond to... Figure 1 Access node 104, and UE 230 can correspond to Figure 1 UE 100 or 102.

[0062] The Network Management System (NMS) 200 is a centralized platform that enables operators to manage and monitor various network components, including the RAN, core network, and transport network. The NMS provides a single interface through which operators can perform various tasks, such as provisioning new network services, configuring network components, monitoring network performance, and detecting and resolving network faults.

[0063] In this example, the NMS 200 can provide a tenant slice portal. The tenant slice portal is a web-based interface used to manage network slices. Tenants (such as enterprise customers or third-party service providers) can use it to request and configure network slices to meet their specific needs. The tenant slice portal provides tenants with a way to specify their slice requirements based on QoS, bandwidth, latency, and other parameters, and to monitor and manage their slices at any time. Therefore, the tenant slice portal enables the dynamic creation, modification, and management of slices to meet the needs of various applications and services.

[0064] The RIC 210 is a network component that separates the RAN's control plane and data plane to allow for more flexible and efficient network operation. The RIC 210 is responsible for implementing network policies and controlling radio resources, enabling the network to dynamically optimize its operation to support different use cases, services, and devices. The RIC 210 can interact with other network elements, such as core network and edge computing resources, to coordinate network services and functions.

[0065] Alternatively, the system may include Operations, Administration and Maintenance (OAM) functions to replace or supplement RIC 210. OAM refers to the set of processes, procedures and tools used to manage and maintain the network. OAM allows network operators to monitor network performance, diagnose and resolve problems, and perform maintenance tasks. OAM functions may include fault management, performance management, security management, and configuration management.

[0066] The Layer 2 Packet Scheduler (L2-PS) 221 in the gNB 220 is responsible for allocating radio resources in the UL and DL, and it can enforce capacity control of RAN slice resources. Currently, when requesting resources from the gNB 220, the UE 230 may not report the logical channel (LCH) identifier for the requested resources. Instead, the request can be made at the logical channel group (LCG) level. Currently, when the UE 230 requests resources from the same logical channel group (LCG) (e.g., ...), ... Figure 2 When multiple channels in LCG-1 send resource requests, L2-PS 221 may be unable to send uplink grants from the corresponding slice. Therefore, UE230 may not consider any slice quotas when assigning uplink grants.

[0067] The one or more logical channels mentioned in this document represent Data Radio Bearers (DRBs). A DRB is a logical connection that enables the transmission of data between the UE 230 and gNB 220 in a cellular network. For example, a DRB can carry user data, such as voice, video, and internet services, between the UE 230 and gNB 220.

[0068] Figure 3Examples of logical channels 311, 312, 313 and logical channel group 321 between UE 230 and gNB 220 are shown. Logical channel group 321 (e.g., LCG-1) includes multiple different logical channels 311, 312, 313 (e.g., LCH-1, LCH-2, and LCH-3).

[0069] While enforcing slice capacity or quota control in the downlink may be relatively simple, there are two inherent challenges in slice-aware scheduling in the uplink.

[0070] The first challenge is that UE 230 may send a scheduling request (SR) to gNB 220 to request uplink shared channel (UL-SCH) resources (uplink grant) for new transmissions. The buffer status report (BSR) sent by UE 230 to the serving gNB 220 provides details about the amount of data awaiting transmission in the UL buffer at UE 230. However, currently, slice-specific information, such as Single Network Slice Selection Assistance Information (S-NSSAI) or (multiple) logical channel identifiers, is absent from the SR or BSR sent by UE 230 to gNB 220 when requesting uplink grant. In other words, UE 230 does not send any slice-specific details (i.e., resources must be allocated from a specific slice quota) when requesting uplink grant. Different LCHs 311, 312, and 313 may have their corresponding quotas in different slices 331, 332, and 333, but this indication is not sent to gNB 220 when requesting uplink grant. Additionally, the cached state (the amount of data awaiting authorization at UE 230) is at the LCG level, rather than at each LCH level.

[0071] The second challenge is that currently, uplink grant allocation by the gNB 220 is performed at the per-UE level to reduce Physical Downlink Control Channel (PDCCH) overhead. Upon receiving an uplink grant, the UE 230 selects one or more bearers for data transmission based on priorities and other parameters configured on the UE 230 by the gNB 220. In other words, the UE 230 uses a standardized logical channel prioritization process when assigning uplink grants to transmit data in the uplink, which does not consider any network slicing aspects. Furthermore, currently, detailed information about which slice the resources are allocated from by the gNB 220 is not transmitted to the UE 230. Due to this behavior, there is currently no method available to enforce slice quota control in the uplink direction.

[0072] Logical channel prioritization can be used to prioritize the transmission of data on different logical channels. In this process, a given logical channel is assigned a priority value that determines the order in which data from these channels is transmitted via the air interface. Priority values ​​can be assigned based on the QoS requirements of the applications using the logical channels. For example, real-time applications such as video streaming can be assigned a higher priority than non-real-time applications such as email to ensure that video data is transmitted with minimal latency and jitter.

[0073] In summary, under the current procedure, when UE 230 requests uplink grant from gNB 220, UE 230 does not specify which specific logical channel it is requesting uplink grant for (because the request is made at the LCG level), therefore there is currently no direct method to map resource requests to slices to provide UL grant. To exacerbate this problem, UE 230 may use its own discretion when using received uplink grants (according to the logical channel prioritization process), and UE 230 may not consider any slice-specific aspects. In other words, uplink multiplexing is performed according to a set of explicitly defined rules at UE 230 (according to the logical channel prioritization process). Furthermore, when gNB 220 grants resources, it does so at the UE level and does not enforce that allocated resources must be used for a specific logical channel belonging to a slice, which is granted from the slice quota. These challenges make it difficult to manage and enforce slice-specific quotas to their corresponding logical channels in the uplink.

[0074] Some example embodiments address the aforementioned challenges and provide a method for effectively controlling RAN slice resource quotas in the uplink direction within the scope of the LCP procedure based on logical channel priority bit rate (PBR) reconfiguration. For example, some example embodiments may provide a mechanism for uplink slice control via reconfiguration based on logical channel priority, PBR, and / or bucket size duration (BSD) of the media access control (MAC) control unit (CE).

[0075] Priority Bit Rate (PBR) is a logical channel configuration parameter that the UE uses according to a standardized logical channel prioritization process when allocating received uplink grants to its logical channels. PBR indicates the guaranteed minimum bit rate for a specific logical channel (i.e., DRB). PBR can be used in packet networks to ensure certain types of traffic receive a specific level of service and can be combined with other QoS parameters such as latency, jitter, and packet loss. PBR can be defined based on a minimum bit rate, and the network (e.g., gNB) and UE can attempt to allocate sufficient bandwidth to meet this requirement, but are subject to other constraints such as available network capacity and the priority of other services.

[0076] Bucket duration refers to the length of time data is collected and analyzed for network service management purposes. Data can be collected into "buckets" of fixed duration, ranging from milliseconds to one second, and used in conjunction with PBR (Programmable Bit Rate) to measure bit rate. By analyzing these metrics, network operators can identify bottlenecks and congestion points in the network and take steps to optimize network performance and improve the quality of service for end users.

[0077] For example, the PBR can be reconfigured using the RRC reconfiguration procedure. However, in the context of RAN slice control, the RRC reconfiguration procedure can be inefficient (causing longer delays), where the PBR may need to be reconfigured more frequently based on slice resource usage. Therefore, a more efficient LCH reconfiguration can be provided based on MAC CE. Thus, some example embodiments can provide efficient mechanisms to dynamically adjust resource usage according to SLA-compliant slice quotas.

[0078] To illustrate the use of PBR for uplink slice control, we assume the following system model. Multiple slices are configured in a cell, meaning the cell's resources are sliced ​​into different logical partitions that can be managed independently. A given slice is configured with a parameter called the "target share," which indicates the expected proportion of resources allocated to that slice within the cell. For example, the target share can be expressed as a percentage value in the range of 0 to 1 (0% to 100%). In other words, the target share of a given slice can represent the expected percentage of cell resources, i.e., a certain number of Physical Resource Blocks (PRBs) that need to be allocated to the UEs or logical channels that have their resource quotas in the corresponding slice. The total target share for all slices in the cell is equivalent to 1.0 (100%). UL RAN slice control can be implemented by shaping non-guaranteed bit rate (non-GBR) traffic, i.e., controlling the bit rate of non-GBR DRBs. It should ensure that a given slice receives resources according to its target share (SLA). If necessary, PBR can be reconfigured to affect the allocation of UL grants during the LCP process for the UE.

[0079] Guaranteed Bit Rate (GBR) refers to the minimum bandwidth or data rate guaranteed to be available to a user or service. In other words, GBR is a Service Level Agreement (SLA) between a network operator and a user, whereby the network operator guarantees that the user will always have a certain level of bandwidth or data rate available to them, regardless of network congestion or other factors. This contrasts with non-GBR services, such as best-effort services, where available bandwidth or data rate may vary depending on network conditions.

[0080] Some example implementations are based on a technique known as PRB efficiency measurement and PBR update.

[0081] PRB efficiency measurements periodically update the system model relating the PRB used to throughput for a given user equipment. In other words, this function determines the spectral efficiency of a given UE that will be used for PBR updates. Spectral efficiency is a measure of the rate at which information can be transmitted over a given communication channel bandwidth. For example, spectral efficiency can be expressed in bits per second per hertz (bps / Hz).

[0082] The function of PBR updates is to periodically determine the expected PBR for a given logical channel, ensuring that each slice consistently reaches its target share. When the expected PBR of a logical channel needs to be changed to a higher or lower level, efficient PBR reconfiguration via MAC CE can be applied to notify the corresponding UE. The expected PBR of a logical channel may depend on at least one of the following: the weight of the logical channel, the resource (PRB) usage by GBR and non-GBR services in a given slice, the target share of the given slice, and the spectral efficiency of the UE.

[0083] Some example embodiments will use the principles and terminology of 5G wireless access technology as described below, but these example embodiments are not limited to 5G wireless access technology.

[0084] Figure 4 A signal flow diagram is shown according to an example embodiment for PBR-based uplink slice control.

[0085] At position 401, the gNB sends an RRC reconfiguration message to the UE, which includes initial LCH settings with default priority, PBR, and BSD. In other words, the UE can be configured to communicate with at least one slice via one or more logical channels. The gNB can correspond to... Figure 1 Access node 104, or Figure 2 The gNB 220. The UE can correspond to Figure 1 UE100 or 102, or Figure 2 UE 230.

[0086] According to current 3GPP standards, a given UE can be configured with up to eight LCGs. For example, LCHs with similar priority service categories can be grouped into one LCG. As shown in the example in Table 1 below, LCGs can correspond to signaling, GBR (voice, video, etc.), and non-GBR service categories. The service requirements of signaling and GBR LCHs can be unconditionally satisfied. Subsequently, if there are still available cell resources, non-GBR LCHs will be scheduled and sliced. Table 1. Examples of logical channel groups

[0087] In Table 1, 5QI is an abbreviation for "5G QoS Identifier". 5QI is a parameter used to indicate the priority and characteristics of a specific flow or service. 5QI values ​​can range from 1 to 255 and can be used to map a flow or service to a specific QoS profile defined by the network operator. A given 5QI value may be associated with a specific set of QoS parameters, such as guaranteed bit rate, maximum bit rate, and packet delay budget, which determine the quality of service that the flow or service will receive.

[0088] During LCH establishment, signaling LCHs or GBR LCHs can be configured with a higher priority than any non-GBR LCHs (a smaller priority value according to TS 38.331). Additionally, the PBR of the signaling LCH can be set to 15 (infinity), meaning that if the signaling LCH has a chance to be scheduled, its buffer should be cleared if sufficient cell resources are available. The PBR of the GBR LCH should be set according to its guaranteed bit rate. On the other hand, during LCH establishment, the priority of non-GBR LCHs can be set to a lower value than any signaling LCH or GBR LCH (a larger priority value). One method to differentiate priorities among non-GBR LCHs is to set the same priority for non-GBR LCHs of the same LCG (e.g., LCHs in LCG IDs 1 and 2 in Table 1 are configured with the same priority and are therefore treated equally), and to set the non-GBR LCHs of LCGs with higher QoS requirements to a higher priority (e.g., the LCH in LCG ID 3 in Table 1 is configured with a higher priority than the LCHs in LCG IDs 1 and 2 due to the stricter QoS requirements of low-latency applications). Initially, the PBR for non-GBR LCHs can be set to the expected throughput of the LCH, or according to the PBR update algorithm, which will be specified at 404 below. Figure 5 It is described in the text.

[0089] At position 402, the UE sends an RRC reconfiguration complete message to the gNB to indicate that the UE has successfully applied the configuration parameters included in the RRC reconfiguration message.

[0090] At 403, the gNB performs PRB efficiency measurements for UEs targeting one or more LCHs. PRB efficiency indicates the relationship between PRB usage and data rate (throughput). The gNB can continuously perform PRB efficiency measurements. PRB efficiency may also be referred to as spectral efficiency in this document.

[0091] The goal of PRB efficiency measurement is to maintain an up-to-date model of the relationship between PRB and throughput for a given UE. This model can be used for PBR updates at 404. More specifically, for the UE... u This model can be derived from It means that, among them Q Throughput is measured in bytes, and R This is the number of PRBs expected to supply such a throughput. For simplicity, we can assume... It is a linear function, that is ,in Indicates UE u In UL time slot t PRB efficiency. Larger. This corresponds to better channel quality.

[0092] Due to UE mobility and variations in the radio environment, the UE's PRB efficiency will change over time. PRB efficiency can be updated as frequently as possible; for example, if computational overhead is acceptable, the PRB efficiency can be updated whenever the UE is scheduled in a UL time slot. Specifically, in the current time slot... t UE u The PRB efficiency can be estimated as follows. Let... t’ For UE u The most recent UL time slot that was scheduled is then: in For UE u In the time slot t’ The number of bytes of UL data sent in the middle, and For UE u In the time slot t’ The number of PRBs used.

[0093] For lower computational overhead, another option is to collect... A set of points, which correspond to the UE u The number of previous UL time slots scheduled within it is determined, and the current time slot is estimated using linear regression. t PRB efficiency This option has the added advantage of providing a more stable PRB efficiency measurement over longer estimation intervals (e.g., 10, 20, or 50 ms), which may be beneficial for infrequent PBR updates. Assume the existence of a set of points. ,in and PRB efficiency It can be found by minimizing the sum of squared errors (SSE): By setting We have:

[0094] At position 404, gNB updates the expected PBR for one or more LCHs based on PBR efficiency measurements, i.e., selecting an appropriate PBR level for one or more LCHs. gNB can continuously perform PBR updates.

[0095] For example, a cell may contain a radio access control unit that ensures that the average GBR traffic per slice does not use more of the cell's resource target share than the slice's total resource target. The target share indicates the percentage of resources allocated to a slice within a cell divided into multiple slices. i The expected proportion of wireless resources allocated. For slicing. i Let the target share be And in UL time slots t The average (e.g., exponential moving average) share of resources allocated to GBR services is Then, the expected average share of resources to be allocated to non-GBR businesses can be estimated as follows:

[0096] Let the average number of PRBs corresponding to cell resources used for data communication be... M And make the slices i Non-GBRLCH j The weight is ,in With slices i Non-GBR LCH assigned to LCH j The amount of resources allocated to LCH is proportional to the expected amount. j The expected number of PRBs can be determined as follows: in It is a slice i The non-GBR LCH set. Let LCH j Belongs to UE u And assuming an average of every time TThere is one UL time slot (in seconds).

[0097] Application measured PRB efficiency LCH j The expected PBR can be determined as follows:

[0098] According to LogicalChannelConfig in TS 38.331, PBR can be a value between 0 and 15, corresponding to 0 kBps, 8 kBps, 16 kBps, ..., 65536 kBps and infinity. We obtained PBR levels between 0 and 14. It corresponds to less than or equal to The highest PBR.

[0099] Finally, if targeting LCH j of Compared to the previously configured LCH j If the PBR level has changed, the relevant PBR reconfiguration command can be sent, for example, on a first-come, first-served basis. LCH reconfiguration may occur when at least one of the following conditions has changed: slice GBR load, LCH or slice configuration, and / or UE PRB efficiency. Typically, one LCH reconfiguration MAC CE may be sufficient for PBR reconfiguration of all LCHs for a given UE, as they may share the same PBR timeout interval (described below). After a PBR timeout, the PBR value of the associated LCH is restored to its default value (set by the RRC reconfiguration at step 401). The timeout mechanism can be used to temporarily increase or decrease the PBR, thereby reducing LCH throughput for a predefined duration.

[0100] At 405, if the PBR level of at least one LCH has changed due to a PBR update, the gNB sends an LCH reconfiguration MAC CE to the UE, indicating that the PBR will be updated for one or more relevant LCHs.

[0101] Sending PBR reconfiguration via MAC CE reduces overhead compared to sending PBR reconfiguration via RRC reconfiguration, as RRC reconfiguration can introduce longer latency. To support this feature, the current MAC CE can be extended to include a new MAC CE LCH reconfiguration. This MAC CE LCH reconfiguration is generic and supports reconfiguration of at least three LCH parameters associated with the LCP procedure: priority, prioritizedBitRate, and bucketSizeDuration. For example, the LCH reconfiguration MAC CE can use a reserved Logical Channel Identifier (LCID) = 33, along with the payload listed in Table 2 below. In this paper, the LCH reconfiguration MAC CE is designed in a more general way because UL slicing can take many forms. For example, UL slicing can be performed by dynamically adjusting the priority of LCHs so that higher-priority LCHs are served first. Table 2. Examples of LCH reconfiguration of MAC CE

[0102] If the PRIO bit is set, the PRIO block is included in the MAC CE. The PRIO block indicates the priority to be configured for the associated logical channels(s).

[0103] If the PBR BIT is set, the PBR block is included in the MAC CE. The PBR block indicates the PBR (prioritised Bit Rate) to be configured for (multiple) related logical channels.

[0104] If the BSD bit is set, the BSD block is included in the MAC CE. The BSD block indicates the BSD (bucketSizeDuration) to be configured for (multiple) related logical channels.

[0105] The LCID number indicates the number of logical channels for which a PBR reconfiguration should be performed. For example, the LCID number can range from 0 to 31, representing 1 to 32 logical channels.

[0106] LCID# i Indicates the first i A 6-bit identifier for each logical channel.

[0107] PRIO# i It indicates that it is necessary to target the first iThe priority value for each logical channel update (configuration). It can be defined according to the priority in LogicalChannelConfig. For example, the value can be in the range of 0 to 15, representing priority values ​​1 to 16. If the PRIO bit is set, the PRIO block can include 4 (LCID Number) bits.

[0108] PBR# i Indicates to the first i The PBR value is updated (configured) for each logical channel. It can be defined in the same way as the prioritizedBitRate in LogicalChannelConfig. For example, the PBR value range can be from 0 to 15, representing 0, 8, 16, ..., 32768, 65536 kilobytes per second and infinity. If the PBR bit is set, the PBR block can include 4... (LCID Number) bits.

[0109] BSD# i Indicates to the first i The BSD value for each logical channel update (configuration). It can be defined according to bucketSizeDuration in LogicalChannelConfig. For example, the BSD value range can be from 0 to 8, representing 5, 10, 20, 50, 100, 150, 300, 500, and 1000 milliseconds. If BSD BIT is set, the BSD block can include 4 (LCID Number) bits.

[0110] Table 2 shows the TIMEOUT timeout interval (e.g., measured in milliseconds). If TIMEOUT = 0, the timeout interval can be set to infinity. Otherwise, the timeout interval can be equal to 2^(TIMEOUT-1) milliseconds, for example, ranging from 1 millisecond to 298.26 hours. During LCH establishment, three timers can be created for a given LCH, for the priority, PBR, and BSD parameters respectively. Initially, all three timers can be deactivated. When the LCH reconfiguration MAC CE is received by the UE, if TIMEOUT ≠ 0, all LCH-related timers indicated in the MAC CE (depending on the PRIO, PBR, and BSD bits) can be activated with the indicated timeout interval. If TIMEOUT = 0, all LCH-related timers indicated in the MAC CE (depending on the PRIO, PBR, and BSD bits) can be deactivated. After the timeout of a given timer, the associated parameter (priority, PBR, or BSD) is set to its default value (i.e., the value set by RRC reconfiguration at 401). For example, aggressive LCH reconfiguration can provide fast convergence to the target share and use a smaller timeout interval.

[0111] At 406, based on the received LCH reconfiguration MAC CE, the UE configures one or more logical channels indicated in the LCH reconfiguration MAC CE.

[0112] If the PRIO BIT is set in the LCH reconfiguration MAC CE, one or more logical channels are configured using the associated PRIO value.

[0113] If the PBR BIT is set in the LCH reconfiguration MAC CE, one or more logical channels are configured using the associated PBR value.

[0114] If the BSD bit is set in the LCH reconfiguration MAC CE, one or more logical channels are configured using the associated BSD value.

[0115] If the timeout interval is non-zero, the reconfigured values ​​can have a valid duration. Otherwise, they may remain valid indefinitely until modified by another LCH reconfiguration MAC CE in the future.

[0116] At point 407, the UE can send a Buffer Status Report (BSR) to the gNB to notify the gNB of the amount of data the UE has buffered for transmission. The gNB can use the BSR information to determine whether to authorize additional uplink resources to the UE to support the transmission of the buffered data.

[0117] At 408, the gNB determines and sends one or more uplink grants to the UE based on the buffer status report. One or more uplink grants can be sent on the PDCCH per uplink slot. For a UE to be scheduled in an uplink slot, one or more uplink grants can be determined such that they provide sufficient frequency domain resources to satisfy the following two requirements: 1) a given GBR LCH is assigned a PRB such that its guaranteed bit rate requirement is met on average; 2) multiple non-GBR LCHs are assigned PRBs such that in the slot... t If multiple slices are competing for cell resources, then a given slice i according to Approaching its resource share for non-GBR services (see the PBR update at 404 above). In this document, "approaching" refers to the slice. i The actual resource share of non-GBR business should be as close as possible to the expected average resource share. .

[0118] In other words, one or more uplink grants can be determined by assigning radio resources to slices. i One or more guaranteed bit rate logical channels, such that the guaranteed bit rate requirement is met and based on the channels to be allocated for slicing. i The expected average resource share of non-guaranteed bit rate services assigns radio resources to one or more non-guaranteed bit rate logical channels in the slice.

[0119] At 409, based on the expected priority bit rate of each of the one or more logical channels indicated in the LCH reconfiguration MAC CE at 405, the UE uses the LCP procedure to assign one or more received uplink grants to one or more logical channels.

[0120] At 410, in the event of a timeout, the UE restores the default priority, PBR, and / or BSD for one or more relevant LCHs. In other words, after the timer times out, the associated parameters (priority, PBR, and / or BSD) are set to their default values ​​(i.e., the values ​​set by RRC reconfiguration at 401).

[0121] The aforementioned UL slice control method offers several advantages. First, the UE is slice-independent, thus the slice configuration and algorithm can be updated simply by changing the gNB behavior. Second, modifications to the 3GPP standard are minimal, with little impact on the UE. Third, the additional communication overhead resulting from UL slice control is low.

[0122] Figure 5A flowchart illustrating an example embodiment of a method performed by a device is shown. For example, the device may be a network node of a wireless access network, or a network node comprising a wireless access network, or a network node included in a wireless access network. A network node may correspond to... Figure 1 Access node 104, or Figure 2 gNB 220, or Figure 4 gNB.

[0123] Figure 5 The algorithm shown can run once every N time slots. The goal of this algorithm is to allow a given slice to satisfy its target resource usage. This algorithm can... Figure 4 It is executed in block 404.

[0124] refer to Figure 5 In block 501, input information is obtained, which indicates the average PRB usage (resource usage) for each slice (e.g., a percentage). Average PRB usage refers to the value defined above. and .

[0125] As described above at 404, the expected average resource share will be allocated for non-guaranteed bit rate traffic in this slice in at least one time slot. It can be obtained from the target share of the slice Subtract the average resource share allocated for the guaranteed bit rate service of the slice in at least one time slot. To estimate.

[0126] In block 502, the expected number of PRBs (i.e., radio resource quantity) allocated per logical channel per time slot is determined based on the target share and the average PRB usage per slice. The expected number of PRBs refers to the number defined above. .

[0127] As described above at 404, the expected number of physical resource blocks allocated to each logical channel in one or more logical channels of a slice in at least one time slot. This can be based at least on the expected share of physical resources that will be allocated for non-guaranteed bit rate traffic in at least one time slot of the slice. To determine.

[0128] Expected number of physical resource blocks It can also be based on the weight value of the logical channel. It is determined that the weight value is proportional to the expected amount of radio resources for one or more logical channels among those allocated to the slice.

[0129] In block 503, at least based on the expected number of physical resource blocks allocated per logical channel. and the spectral efficiency of at least one UE (exist Figure 4 (As determined at point 403), the expected PBR for each logical channel can be determined. The expected PBR refers to the PBR defined at point 404 above. .

[0130] In block 504, it is determined whether the PBR level of at least one logical channel for at least one UE has changed compared to the previously configured PBR level of the at least one logical channel. The PBR level refers to the level defined at 404 above. .

[0131] In block 505, based on the determination that the PBR level has changed (block 504: yes), the expected PBR for one or more relevant logical channels of at least one UE is updated to the nearest PBR level that is lower than or equal to the expected PBR.

[0132] In block 506, a message indicating an updated PBR (e.g., MAC CE) is sent to at least one UE.

[0133] Figure 6 A flowchart illustrating an example embodiment of a method performed by a device is shown. For example, the device may be a network node of a wireless access network, a network node comprising a wireless access network, or a network node included in a wireless access network. The network node may correspond to... Figure 1 Access node 104 or DU 105 or CU 108, or Figure 2 gNB 220, or Figure 4 gNB 220.

[0134] refer to Figure 6 In block 601, the apparatus determines, at least based on the spectral efficiency of at least one user equipment 230 and the target share of slice 331, the expected priority bit rate of each of one or more logical channels 311, 312, 313, wherein the at least one user equipment 230 is configured to communicate with slice 331 via logical channel 311, wherein the target share indicates the proportion of expected radio resources allocated to slice 331 in a cell divided into multiple slices 331, 332, 333. The expected priority bit rate may refer to the expected priority bit rate level. .

[0135] The fact that the cell is divided into multiple slices means that the cell's wireless point resources are divided into multiple slices.

[0136] For example, the expected priority bit rate of each logical channel can be determined by: estimating the expected average resource share of non-guaranteed bit rate services to be allocated to the slice in at least one time slot by subtracting the average resource share of guaranteed bit rate services allocated to the slice in at least one time slot from the target share of the slice; determining the expected number of expected physical resource blocks allocated per logical channel in one or more logical channels of the slice in at least one time slot, based at least on the expected average resource share of non-guaranteed bit rate services allocated to the slice in at least one time slot; and determining the expected priority bit rate of each of the one or more logical channels based at least on the expected number of expected physical resource blocks allocated per logical channel and the spectral efficiency of at least one user equipment.

[0137] The expected number of physical resource blocks allocated per logical channel can also be determined based on a weight value for the logical channel, which is proportional to the expected amount of radio resources for the logical channels among one or more logical channels allocated to the slice.

[0138] In block 602, the device sends a message to at least one user equipment that indicates at least the expected priority bit rate for each of one or more logical channels. For example, the message may include a value indicating the expected priority bit rate for each logical channel (e.g., a PBR value for each logical channel). For example, the message may be a MAC CE message.

[0139] The message may also indicate at least one of the following: the priority of each of the one or more logical channels, or the bucket-size duration of each of the one or more logical channels. For example, the message may include a value indicating the priority of each logical channel (e.g., one priority value per logical channel) and / or a value indicating the bucket-size duration of each logical channel (e.g., one BSD value per logical channel).

[0140] The message may also indicate a timeout interval, wherein the timeout interval indicates that at least one of the following will be restored after the timeout interval expires: the default expected priority bit rate of each of the one or more logical channels, the default priority of each of the one or more logical channels, or the default bucket size duration of each of the one or more logical channels.

[0141] The message can be sent based on the detected change in the expected priority bit rate level of each logical channel compared to the previously configured expected priority bit rate level of the logical channel.

[0142] The apparatus can also determine one or more uplink grants for at least one user equipment by: assigning radio resources to one or more guaranteed bit rate logical channels of the slice such that the guaranteed bit rate requirement is met; and assigning radio resources to one or more non-guaranteed bit rate logical channels of the slice based on the expected average resource share of non-guaranteed bit rate traffic to be allocated for the slice. The apparatus can send one or more uplink grants to at least one user equipment.

[0143] This message enables at least one user equipment to allocate one or more uplink grants to one or more logical channels based on the expected priority bit rate of each of the one or more logical channels.

[0144] Figure 7 A flowchart illustrating an example embodiment of a method performed by a device is shown. For example, the device may be a user equipment, or include a user equipment, or be included in a user equipment. The user equipment may also be referred to as a wireless communication device, subscriber unit, mobile station, remote terminal, access terminal, user terminal, terminal equipment, or user equipment (UE). The user equipment may correspond to... Figure 1 UE 100 or 102, or Figure 2 UE 230, or Figure 4 UE.

[0145] refer to Figure 7 In block 701, the device receives a message that indicates at least the expected priority bit rate for each of one or more logical channels 311, 312, 313. For example, the message may include values ​​indicating the expected priority bit rate (e.g., a PBR value for each logical channel). For example, the message may be a MAC CE message. This message can be received from a network node of the radio access network, such as... Figure 1 Access node 104 or DU 105, or Figure 2 gNB 220, or Figure 4 gNB.

[0146] In block 702, the device configures one or more logical channels 311, 312, 313 by applying at least the expected priority bit rate of each logical channel 311 of one or more logical channels 311, 312, 313. For example, the device may apply the expected priority bit rate value of each logical channel 311 of one or more logical channels 311, 312, 313.

[0147] The expected priority bit rate is based at least on the spectral efficiency of the device and the target share of slice 331, which is configured to communicate with slice 331 via logical channel 311. The target share indicates the expected proportion of radio resources allocated to slice 331 in the cells divided into multiple slices 331, 332, and 333.

[0148] The device can allocate one or more received uplink grants to one or more logical channels based on the expected priority bit rate of each of the one or more logical channels.

[0149] The message may also indicate at least one of the following: the priority of each logical channel in one or more logical channels, or the bucket-size duration of each logical channel in one or more logical channels. For example, the message may include: a value indicating the priority of each logical channel (e.g., one priority value per logical channel), and / or a value indicating the bucket-size duration of each logical channel (e.g., one BSD value per logical channel). The device can configure one or more logical channels by applying at least one of the following: the priority of each logical channel in one or more logical channels, or the bucket-size duration of each logical channel in one or more logical channels.

[0150] The message can also indicate a timeout interval. The device can restore at least one of the following after the timeout interval expires: the default expected priority bit rate for each of the one or more logical channels, the default priority for each of the one or more logical channels, or the default bucket size duration for each of the one or more logical channels. In other words, the device can restore the configured PBR value, priority value, and / or BSD value of a given logical channel to their respective default values ​​after the timeout interval expires.

[0151] The above has been approved. Figures 4 to 7 The described blocks, related functions, and information exchanges (messages) are not in an absolute chronological order; some may be executed simultaneously or in a different order than described. Other functions may also be executed between or within them, and other information may be sent and / or other rules may be applied. Certain blocks, partial blocks, or one or more messages may also be omitted or replaced by corresponding blocks, partial blocks, or one or more messages.

[0152] As used herein, “at least one of the following: ” and “at least one of ” and similar wording (where the list of two or more elements is connected by “and” or “or”) means at least any one element, or at least any two or more elements, or at least all elements.

[0153] Figure 8An example of apparatus 800 is shown, which includes components for performing one or more of the example embodiments described above. For example, apparatus 800 may be an apparatus such as a user equipment, or include a user equipment, or be included in a user equipment. User equipment may also be referred to as a wireless communication device, subscriber unit, mobile station, remote terminal, access terminal, user terminal, terminal equipment, or user equipment (UE). User equipment may correspond to... Figure 1 UE 100, 102, or Figure 2 UE 230 or Figure 4 One of the UEs.

[0154] The device 800 may include a circuit system or chipset suitable for implementing one or more of the example embodiments described above. For example, the device 800 may include at least one processor 810. The at least one processor 810 interprets instructions (e.g., computer program instructions) and processes data. The at least one processor 810 may include one or more programmable processors. The at least one processor 810 may include programmable hardware with embedded firmware and may alternatively or additionally include one or more application-specific integrated circuits (ASICs).

[0155] The at least one processor 810 is coupled to at least one memory 820. The at least one processor is configured to read data from and write data to the at least one memory 820. The at least one memory 820 may include one or more memory cells. These memory cells may be volatile or non-volatile. It should be noted that one or more non-volatile memory cells and one or more volatile memory cells may be present, or alternatively, one or more non-volatile memory cells may be present, or alternatively, one or more volatile memory cells may be present. Volatile memory may be, for example, random access memory (RAM), dynamic random access memory (DRAM), or synchronous dynamic random access memory (SDRAM). Non-volatile memory may be, for example, read-only memory (ROM), programmable read-only memory (PROM), electrically erasable programmable read-only memory (EEPROM), flash memory, optical storage, or magnetic storage. In general, memory may be referred to as a non-transitory computer-readable medium. As used herein, the term "non-transitory" refers to the limitation of the medium itself (i.e., tangible, not tactile), rather than a limitation on the persistence of data storage (e.g., RAM and ROM). At least one memory 820 stores computer-readable instructions that are executed by at least one processor 810 to perform one or more of the example embodiments described above. For example, non-volatile memory stores the computer-readable instructions, and at least one processor 810 uses volatile memory to temporarily store data and / or instructions to execute these instructions. The computer-readable instructions may refer to computer program code.

[0156] Computer-readable instructions may have been pre-stored in at least one memory 820, or alternatively or additionally, they may be received by the device via an electromagnetic carrier signal, and / or may be copied from a physical entity (such as a computer program product). Execution of the computer-readable instructions by at least one processor 810 causes the device 800 to perform one or more of the example embodiments described above. That is, at least one processor and at least one memory storing the instructions can provide components for providing or causing execution of any of the methods and / or blocks described above.

[0157] In the context of this document, "memory" or "computer-readable medium" can be any nontransitory medium or component capable of containing, storing, communicating, propagating, or transmitting instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer. As used herein, the term "nontransitory" refers to limitations inherent in the medium itself (i.e., tangible rather than tactile), rather than limitations on the persistence of data storage (e.g., RAM and ROM).

[0158] The device 800 may also include an input unit 830 or be connected to an input unit 830. The input unit 830 may include one or more interfaces for receiving input. These interfaces may include, for example, one or more temperature, motion, and / or orientation sensors, one or more cameras, one or more accelerometers, one or more microphones, one or more buttons, and / or one or more touch detection units. Furthermore, the input unit 830 may also include an interface for connecting to external devices.

[0159] The device 800 may also include an output unit 840. This output unit may include or be connected to one or more displays capable of displaying visual content, such as a light-emitting diode (LED) display, a liquid crystal display (LCD), and / or a liquid crystal on silicon (LCoS) display. The output unit 840 may also include one or more audio outputs. These one or more audio outputs may be, for example, speakers.

[0160] Device 800 also includes a connectivity unit 850. Connectivity unit 850 supports wireless connectivity with one or more external devices. Connectivity unit 850 includes at least one transmitter and at least one receiver, which may be integrated into device 800 or connected to it. The at least one transmitter includes at least one transmitting antenna, and the at least one receiver includes at least one receiving antenna. Connectivity unit 850 may include an integrated circuit or a set of integrated circuits that provides wireless communication capabilities to device 800. Alternatively, wireless connectivity may be a hardwired application-specific integrated circuit (ASIC). Connectivity unit 850 may also provide components for performing at least some of the blocks in one or more of the example embodiments described above. Connectivity unit 850 may include one or more components such as: power amplifiers, digital front-ends (DFEs), analog-to-digital converters (ADCs), digital-to-analog converters (DACs), frequency converters, (de)modulators, and / or encoder / decoder circuitry, which are controlled by corresponding control units.

[0161] It should be noted that device 800 may also include Figure 8 Various components are not shown. These various components can be hardware components and / or software components.

[0162] Figure 9 An example of apparatus 900 is shown, which includes components for performing one or more of the example embodiments described above. For example, apparatus 900 may be, or include, a network node such as a wireless access network, or be included in or incorporated into the network node. The network node may correspond to... Figure 1 Access nodes 104, DU 105, or CU 108, or Figure 2 gNB 220, or Figure 4 gNB.

[0163] Network nodes can also be referred to as, for example, network elements, radio access network (RAN) nodes, next-generation radio access network (NG-RAN) nodes, NodeB, eNB, gNB, base transceiver station (BTS), base station, NR base station, 5G base station, access node, access point (AP), relay node, repeater, aggregated access and backhaul (IAB) node, IAB donor node, distributed unit (DU), central unit (CU), baseband unit (BBU), radio unit (RU), radio head, remote radio head (RRH), or transmit and receive point (TRP).

[0164] Apparatus 900 may include, for example, a circuit system or chipset suitable for implementing one or more of the example embodiments described above. Apparatus 900 may be an electronic device including one or more electronic circuit systems. Apparatus 900 may include a communication control circuit system 910 (such as at least one processor) and at least one memory 920, the at least one memory 920 storing instructions 922, which, when executed by the at least one processor, cause apparatus 900 to perform one or more of the example embodiments described above. These instructions 922 may, for example, include computer program code (software). The at least one processor and the at least one memory storing the instructions may provide components for providing or causing execution of any of the methods and / or blocks described above.

[0165] A processor is coupled to memory 920. The processor is configured to read and write data from memory 920. Memory 920 may include one or more memory cells. These memory cells may be volatile or non-volatile. It should be noted that one or more non-volatile memory cells and one or more volatile memory cells may be present, or alternatively, one or more non-volatile memory cells and one or more volatile memory cells may be present. Volatile memory may be, for example, random access memory (RAM), dynamic random access memory (DRAM), or synchronous dynamic random access memory (SDRAM). Non-volatile memory may be, for example, read-only memory (ROM), programmable read-only memory (PROM), electrically erasable programmable read-only memory (EEPROM), flash memory, optical storage, or magnetic storage. In general, memory may be referred to as a non-transitory computer-readable medium. As used herein, the term "non-transitory" refers to the limitations of the medium itself (i.e., tangible, not tactile), rather than limitations on the persistence of data storage (e.g., RAM and ROM). Memory 920 stores computer-readable instructions that are executed by the processor. For example, non-volatile memory stores computer-readable instructions, and the processor uses volatile memory to temporarily store data and / or instructions to execute those instructions.

[0166] The computer-readable instructions may have been pre-stored in memory 920, or alternatively or additionally, they may be received by the device via an electromagnetic carrier signal, and / or copied from a physical entity (such as a computer program product). Execution of the computer-readable instructions causes the device 900 to perform one or more of the functions described above.

[0167] The memory 920 can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. The memory may include a configuration database for storing configuration data, such as a current list of neighboring cells, and, in some example embodiments, the structure of frames used in detected neighboring cells.

[0168] The device 900 may also include or be connected to a communication interface 930 (such as a radio unit), which includes hardware and / or software for implementing communication connectivity with one or more wireless communication devices according to one or more communication protocols. The communication interface 930 includes at least one transmitter (Tx) and at least one receiver (Rx), which may be integrated into the device 900 or to which the device 900 may be connected. The communication interface 930 may provide components for performing some blocks for one or more of the above-described example embodiments. The communication interface 930 may include one or more components such as: power amplifiers, digital front-ends (DFE), analog-to-digital converters (ADCs), digital-to-analog converters (DACs), frequency converters, (de)modulators, and / or encoder / decoder circuitry systems, which are controlled by corresponding control units.

[0169] Communication interface 930 provides the device with radio communication capabilities for communication within a wireless communication network. For example, the communication interface may provide a radio interface with one or more wireless communication devices. The device 900 may also include or be connected to another interface toward a core network (such as a network coordinator device or AMF) and / or an access node for a cellular communication system.

[0170] The device 900 may also include a scheduler 940 configured to allocate radio resources. The scheduler 940 may be configured together with the communication control circuitry system 910, or it may be configured separately.

[0171] It should be noted that device 900 may also include Figure 9 Various components not shown. These components may be hardware components and / or software components.

[0172] As used in this application, the term "circuit system" may refer to one or more or all of the following: a) a hardware circuit implementation only (such as an implementation in an analog and / or digital circuit system only); and b) a combination of hardware circuits and software, such as (if applicable): i) a combination of (multiple) analog and / or digital hardware circuits with software / firmware; and ii) any part of a hardware processor having software (including (multiple) digital signal processors, software, and (multiple) memories, which work together to enable a device (such as a mobile phone) to perform various functions); and c) (multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, that require software (e.g., firmware) to operate, but may be absent when operation does not require software.

[0173] This definition of "circuit system" applies to all uses of the term in this application, including in any claim. As another example, as used in this application, the term "circuit system" also covers an implementation consisting solely of a single hardware circuit or processor (or multiple processors) or a portion thereof and its accompanying software and / or firmware. The term "circuit system" also covers (e.g., if applicable to a particular claim element) baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or networking devices.

[0174] The techniques and methods described herein can be implemented in various ways. For example, these techniques can be implemented in hardware (one or more devices), firmware (one or more devices), software (one or more modules), or a combination thereof. For hardware implementation, the apparatus(s) of the example embodiments can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), graphics processing units (GPUs), processors, controllers, microcontrollers, microprocessors, other electronic units designed to perform the functions described herein, or combinations thereof. For firmware or software, the implementation can be executed by a module (e.g., a program, function, etc.) of at least one chipset that performs the functions described herein. Software code can be stored in a memory cell and executed by a processor. The memory cell can be implemented inside the processor or outside the processor. In the latter case, it can be communicatively coupled to the processor via various means known in the art. In addition, the components of the systems described herein can be rearranged and / or supplemented by additional components to facilitate the implementation of the various aspects described herein, and as will be understood by those skilled in the art, these aspects are not limited to the precise configuration shown in the given figures.

[0175] It will be apparent to those skilled in the art that the inventive concept can be implemented in various ways as technology advances. The embodiments are not limited to the exemplary embodiments described above, but can be varied within the scope of the claims. Therefore, all words and expressions should be interpreted broadly, and they are intended to illustrate the embodiments, not limit them.

Claims

1. An apparatus comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: determine an expected prioritized bit rate for each of one or more logical channels based at least on a spectral efficiency of at least one user equipment configured to communicate with a slice via the logical channels and a target share of the slice, wherein the target share indicates an expected proportion of wireless resources allocated for the slice in a cell partitioned into a plurality of slices; and send a message to the at least one user equipment indicating at least the expected prioritized bit rate for each of the one or more logical channels.

2. The apparatus of claim 1, wherein the message is a medium access control, MAC, control element, CE, message.

3. The apparatus of any preceding claim, wherein the message further indicates at least one of a priority of each of the one or more logical channels or a bucket size duration of each of the one or more logical channels.

4. The apparatus of any preceding claim, wherein the message further indicates an override interval, wherein the override interval indicates a resumption, upon expiration of the override interval, of at least one of a default expected prioritized bit rate of each of the one or more logical channels, a default priority of each of the one or more logical channels, or a default bucket size duration of each of the one or more logical channels.

5. The apparatus of any preceding claim, wherein the message is sent based on detecting a change in a level of the expected prioritized bit rate of each of the logical channels compared to a previously configured expected prioritized bit rate of the logical channel.

6. The apparatus of any preceding claim, further caused to: estimate an expected average resource share of non-guaranteed bit rate traffic to be allocated for the slice in at least one time slot by subtracting an average resource share of guaranteed bit rate traffic allocated for the slice in the at least one time slot from the target share of the slice; and determine an expected number of physical resource blocks allocated per logical channel of the one or more logical channels of the slice in the at least one time slot based at least on the expected average resource share of the non-guaranteed bit rate traffic to be allocated for the slice in the at least one time slot, wherein the expected prioritized bit rate of each of the one or more logical channels is determined based at least on the expected number of physical resource blocks allocated per logical channel and the spectral efficiency of the at least one user equipment.

7. The apparatus of claim 6, wherein the expected number of physical resource blocks allocated per said logical channel is further determined based on a weight value of the logical channel, the weight value being proportional to an expected amount of radio resources allocated to the logical channel among the one or more logical channels assigned to the slice.

8. The apparatus of any one of claims 6-7, further caused to: determine one or more uplink grants for the at least one user equipment by: assigning radio resources to one or more guaranteed bit rate logical channels of the slice such that the guaranteed bit rate requirements are fulfilled; and assign radio resources to one or more non-guaranteed bit rate logical channels of the slice based on the expected average resource share to be allocated for the non-guaranteed bit rate traffic of the slice; and transmit the one or more uplink grants to the at least one user equipment.

9. The apparatus of claim 8, wherein the message causes the at least one user equipment to allocate the one or more uplink grants to the one or more logical channels based on the expected priority bit rate of each of the one or more logical channels.

10. The apparatus of any preceding claim, wherein the apparatus comprises or is comprised in a network node of a radio access network.

11. An apparatus comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive a message indicating at least an expected priority bit rate of each of one or more logical channels; and configure the one or more logical channels by applying at least the expected priority bit rate of each of the one or more logical channels, wherein the expected priority bit rate is based at least on a spectral efficiency of the apparatus and a target share of a slice, the apparatus being configured to communicate with the slice via the logical channels, wherein the target share indicates an expected proportion of radio resources allocated for the slice in a cell divided into a plurality of slices.

12. The apparatus of claim 11, further caused to: allocate one or more received uplink grants to the one or more logical channels based on the expected priority bit rate of each of the one or more logical channels.

13. The apparatus of any one of claims 11-12, wherein the message is a medium access control, MAC, control element, CE, message.

14. The apparatus of any one of claims 11-13, wherein the message further indicates at least one of: a priority of each of the one or more logical channels, or a bucket size duration of each of the one or more logical channels; the apparatus being further caused to: configure the one or more logical channels by applying at least one of: the priority of each of the one or more logical channels, or the bucket size duration of each of the one or more logical channels. ​ 15. The apparatus of any one of claims 11 to 14, wherein the message further indicates a time-out interval; the apparatus is further caused to: resume, after the time-out interval expires, at least one of a default expected priority bit rate for each of the one or more logical channels, a default priority for each of the one or more logical channels, or a default bucket size duration for each of the one or more logical channels.

16. The apparatus of any one of claims 11 to 15, wherein the apparatus comprises or is comprised in a user equipment.

17. An apparatus comprising: means for determining an expected priority bit rate for each of one or more logical channels based at least on a spectral efficiency of at least one user equipment and a target share of a slice, the at least one user equipment being configured to communicate with the slice via the logical channels, wherein the target share indicates an expected proportion of wireless resources allocated for the slice in a cell divided into a plurality of slices; and means for sending a message to the at least one user equipment, the message indicating at least the expected priority bit rate for each of the one or more logical channels.

18. An apparatus comprising: means for receiving a message, the message indicating at least an expected priority bit rate for each of one or more logical channels; and means for configuring the one or more logical channels by applying at least the expected priority bit rate for each of the one or more logical channels, wherein the expected priority bit rate is based at least on a spectral efficiency of the apparatus and a target share of a slice, the apparatus being configured to communicate with the slice via the logical channels, wherein the target share indicates an expected proportion of wireless resources allocated for the slice in a cell divided into a plurality of slices.

19. A method comprising: determining an expected priority bit rate for each of one or more logical channels based at least on a spectral efficiency of at least one user equipment and a target share of a slice, the at least one user equipment being configured to communicate with the slice via the logical channels, wherein the target share indicates an expected proportion of wireless resources allocated for the slice in a cell divided into a plurality of slices; and sending a message to the at least one user equipment, the message indicating at least the expected priority bit rate for each of the one or more logical channels.

20. A method comprising: receiving, by an apparatus, a message, the message indicating at least an expected priority bit rate for each of one or more logical channels; and configuring, by the apparatus, the one or more logical channels by applying at least the expected priority bit rate for each of the one or more logical channels, wherein the expected priority bit rate is based at least on a spectral efficiency of the apparatus and a target share of a slice, the apparatus being configured to communicate with the slice via the logical channels, ​ ​ ​ ​ wherein the target share indicates an intended proportion of wireless resources allocated for the slice in a cell divided into a plurality of slices.

21. A non-transitory computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least the following: determining an intended priority bit rate for each of one or more logical channels based at least on a spectral efficiency of at least one user equipment and a target share of a slice, the at least one user equipment being configured to communicate with the slice via the logical channels, wherein the target share indicates an intended proportion of wireless resources allocated for the slice in a cell divided into a plurality of slices; and sending a message to the at least one user equipment, the message indicating at least the intended priority bit rate for each of the one or more logical channels.

22. A non-transitory computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least the following: receiving a message, the message indicating at least an intended priority bit rate for each of one or more logical channels; and configuring the one or more logical channels by applying at least the intended priority bit rate for each of the one or more logical channels, wherein the intended priority bit rate is based at least on a spectral efficiency of the apparatus and a target share of a slice, the apparatus being configured to communicate with the slice via the logical channels, wherein the target share indicates an intended proportion of wireless resources allocated for the slice in a cell divided into a plurality of slices.

23. A system comprising at least one user equipment and a network node of a radio access network, wherein the network node is configured to: determine an intended priority bit rate for each of one or more logical channels based at least on a spectral efficiency of the at least one user equipment and a target share of a slice, the at least one user equipment being configured to communicate with the slice via the logical channels, wherein the target share indicates an expected proportion of radio resources allocated for the slice in a cell divided into multiple slices; and send a message to the at least one user equipment, the message indicating at least the intended priority bit rate for each of the one or more logical channels; wherein the at least one user equipment is configured to: receive the message, the message indicating at least the intended priority bit rate for each of the one or more logical channels; and configure the one or more logical channels by applying at least the intended priority bit rate for each of the one or more logical channels.