WO2024093341A1 - Prise en charge d'assurance de sla pour tranche de ran - Google Patents

Prise en charge d'assurance de sla pour tranche de ran Download PDF

Info

Publication number
WO2024093341A1
WO2024093341A1 PCT/CN2023/106179 CN2023106179W WO2024093341A1 WO 2024093341 A1 WO2024093341 A1 WO 2024093341A1 CN 2023106179 W CN2023106179 W CN 2023106179W WO 2024093341 A1 WO2024093341 A1 WO 2024093341A1
Authority
WO
WIPO (PCT)
Prior art keywords
ran slice
network entity
sla
information related
slice
Prior art date
Application number
PCT/CN2023/106179
Other languages
English (en)
Inventor
Shuigen Yang
Congchi ZHANG
Mingzeng Dai
Le Yan
Original Assignee
Lenovo (Beijing) Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo (Beijing) Limited filed Critical Lenovo (Beijing) Limited
Priority to PCT/CN2023/106179 priority Critical patent/WO2024093341A1/fr
Publication of WO2024093341A1 publication Critical patent/WO2024093341A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition

Definitions

  • the present disclosure relates to wireless communications, and more specifically to an apparatus and a method for supporting assurance of service layer agreement (SLA) for a radio access network (RAN) slice.
  • SLA service layer agreement
  • RAN radio access network
  • a wireless communications system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology.
  • Each network communication devices such as a base station may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE) , or other suitable terminology.
  • the wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) .
  • the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G) ) .
  • 3G third generation
  • 4G fourth generation
  • 5G fifth generation
  • 6G sixth generation
  • a network slice is a logical network that provides specific network capabilities and network characteristics.
  • An operator can deploy multiple network slices delivering different features for the same group of UEs, or the same features but for different groups of UEs, for example, as they deliver a different committed service and/or because they are dedicated to a customer.
  • the network should support the needs of the business through the several service needs such as data rate, traffic capacity, user density, latency, reliability, and availability. These service needs are always provided based on an SLA for a network slice between a mobile operator and a business customer.
  • network slicing is conceived to be an end-to-end feature that includes a core network a transport network and a radio access network
  • the SLA should be fulfilled at any slice subnet during the lifetime of a network slice, especially at RAN side.
  • the slice subnet of the network slice at RAN side is also referred to as RAN slice.
  • the present disclosure relates to network entities and methods that support assurance of SLA for a RAN slice at a network entity.
  • the network entities and methods may assure the SLA by dynamically controlling a load of the RAN slice based on information related to the SLA for the RAN slice and prevent possible violations of the SLA.
  • Some implementations of a first network entity described herein may include: receiving, at the first network entity from a second network entity, second performance information related to a RAN slice; determining, based at least on the second performance information, information related to SLA for the RAN slice.
  • the first network entity is further configured to: transmit, via the transceiver to the second network entity, the information related to the SLA for the RAN slice.
  • the information related to the SLA for the RAN slice comprises a measurement or prediction of at least one of the following: an indication indicating whether the SLA for the RAN slice is non-fulfilled or fulfilled, a percentage of radio resources used by the RAN slice, a ratio of the number of fulfilled parameter values associated with the SLA to a total number of parameter values associated with the SLA, or at least one action to be taken at the second network entity to fulfill the SLA.
  • the first network entity is a distributed unit (DU) in a base station and the second network entity is a central unit (CU) in the base station.
  • DU distributed unit
  • CU central unit
  • the first network entity is further configured to determine first performance information related to the RAN slice; and the first network entity is configured to determine the information related to the SLA for the RAN slice by determining the information related to the SLA for the RAN slice based on the first performance information and the second performance information.
  • the first performance information comprises a measurement or prediction of at least one of the following: a downlink (DL) user equipment (UE) throughput of the RAN slice, an uplink (UL) UE throughput of the RAN slice, a first average over-the-air interface packet delay in a DL of the RAN slice, a first number of physical resource blocks (PRBs) used in the DL for data traffic, a second number of PRBs used in a UL of the RAN slice for the data traffic, a second average over-the-air interface packet delay in the UL of the RAN slice, an average radio link control (RLC) packet delay in the UL of the RAN slice, a first mean number of active UEs in the DL of the RAN slice, a second mean number of active UEs in the UL of the RAN slice, a first maximum number of active UEs in the DL of the RAN slice, a second maximum number of active UEs in the UL of the RAN slice
  • the second performance information comprises a measurement or prediction of at least one of the following: a UL packet data convergence protocol (PDCP) service data unit (SDU) loss rate of the RAN slice, a DL PDCP SDU data volume of the RAN slice, a UL PDCP SDU data volume of the RAN slice, an average PDCP re-ordering delay in the UL of the RAN slice, or an indication indicating whether the SLA for the RAN slice is non-fulfilled or fulfilled in the second network entity.
  • PDCP packet data convergence protocol
  • SDU service data unit
  • the first network entity is configured to receive the second performance information related to the RAN slice by: transmitting a first request for the second performance information via the transceiver to the second network entity, the first request comprising an identifier of the RAN slice and a first measurement object associated with the second performance information; and receiving a first response via the transceiver from the second network entity, the first response comprising the second performance information.
  • the first measurement object comprises at least one of the following: a UL packet data convergence protocol (PDCP) service data unit (SDU) loss rate, a PDCP SDU data volume, or an average PDCP re-ordering delay in a UL.
  • PDCP packet data convergence protocol
  • SDU service data unit
  • the first request comprises a bitmap, each of bits in the bitmap indicating the first measurement object.
  • the information related to the SLA for the RAN slice comprises at least one action to be taken at the second network entity to fulfill the SLA, the at least one action comprising at least one of the following: radio admission control based on the RAN slice, or radio bearer control based on the RAN slice.
  • the first network entity is a CU in a base station and the second network entity is a DU in the base station.
  • the first network entity is further configured to determine first performance information related to the RAN slice; and the first network entity is configured to determine the information related to the SLA for the RAN slice by determining the information related to the SLA for the RAN slice based on the first performance information and the second performance information.
  • the first performance information comprises a measurement or prediction of at least one of the following: a UL packet data convergence protocol (PDCP) service data unit (SDU) loss rate of the RAN slice, a DL PDCP SDU data volume of the RAN slice, a UL PDCP SDU data volume of the RAN slice, or an average PDCP re-ordering delay in the UL of the RAN slice.
  • PDCP packet data convergence protocol
  • SDU service data unit
  • the second performance information comprises a measurement or prediction of at least one of the following: a DL UE throughput of the RAN slice, a UL UE throughput of the RAN slice, a first average over-the-air interface packet delay in a DL of the RAN slice, a first number of physical resource blocks (PRBs) used in the DL for data traffic, a second number of PRBs used in a UL of the RAN slice for the data traffic, a second average over-the-air interface packet delay in the UL of the RAN slice, an average radio link control (RLC) packet delay in the UL of the RAN slice, a first mean number of active UEs in the DL of the RAN slice, a second mean number of active UEs in the UL of the RAN slice, a first maximum number of active UEs in the DL of the RAN slice, a second maximum number of active UEs in the UL of the RAN slice, a packet Uu loss rate
  • the first network entity is configured to receive the second performance information related to the RAN slice by: transmitting a second request for the second performance information via the transceiver to the second network entity, the second request comprising an identifier of the RAN slice and a second measurement object associated with the second performance information; and receiving a second response via the transceiver from the second network entity, the second response comprising the second performance information.
  • the second measurement object comprises at least one of the following: a UE throughput, an average over-the-air interface packet delay, the number of PRBs used for data traffic, an average RLC packet delay in a UL, the number of active UEs, or a packet Uu loss rate in a DL.
  • the second request comprises a bitmap, each of bits in the bitmap indicating the second measurement object.
  • the information related to the SLA for the RAN slice comprises at least one action to be taken at the second network entity to fulfill the SLA, the at least one action comprising at least one of the following: a resource sharing indication indicating that the RAN slice is allowed to use unused dedicated resources of at least one network slice different from the RAN slice, priority values to achieve scheduling prioritization among network slices with different priorities, each of the priority values being associated with one of the network slices, or dedicated resource allocation percentages for DL or UL.
  • the first network entity is a target base station and the second network entity is a source base station.
  • the second performance information comprises a third request for the information related to the SLA for the RAN slice, the third request comprising an identifier of the RAN slice and a third measurement object associated with the information related to the SLA.
  • the third measurement object comprises at least one of the following: a state of the SLA for the RAN slice in a cell of the target base station, a percentage of radio resources used by the RAN slice in the cell, a ratio of the number of fulfilled parameters associated with the SLA to a total number of parameters associated with the SLA in the cell, or load information related to the RAN slice in the cell.
  • the third request comprises a bitmap, each of bits in the bitmap indicating the third measurement object.
  • the information related to the SLA for the RAN slice comprises a measurement or prediction of at least one of the following: an indication indicating whether the SLA for the RAN slice is non-fulfilled or fulfilled in a cell of the target base station, a percentage of radio resources used by the RAN slice in the cell, a ratio of the number of fulfilled parameters associated with the SLA to a total number of parameters associated with the SLA in the cell, or load information related to the RAN slice in the cell.
  • the load information related to the RAN slice in the cell comprises at least one of the following: usage of resources for the RAN slice for traffics in downlink, usage of resources for the RAN slice for traffics in uplink, or a ratio of the number of resources in the cell available for the RAN slice to a total number of resources available for the cell.
  • Some implementations of a second network entity described herein may include: determining second performance information related to a RAN slice; and transmitting, to a first network entity, the second performance information related to the RAN slice, wherein information related to SLA for the RAN slice is determined based at least on the second performance information.
  • the second network entity is further configured to receive, via the transceiver from the first network entity, the information related to the SLA for the RAN slice.
  • the information related to the SLA for the RAN slice comprises at least one of the following: an indication indicating whether the SLA for the RAN slice is non-fulfilled or fulfilled, a percentage of radio resources used by the RAN slice, a ratio of the number of fulfilled parameter values associated with the SLA to a total number of parameter values associated with the SLA, or at least one action to be taken at the second network entity to fulfill the SLA.
  • the first network entity is a DU in a base station and the second network entity is a CU in the base station.
  • the second performance information comprises a measurement or prediction of at least one of the following: a UL packet data convergence protocol (PDCP) service data unit (SDU) loss rate of the RAN slice, a DL PDCP SDU data volume of the RAN slice, a UL PDCP SDU data volume of the RAN slice, an average PDCP re-ordering delay in the UL of the RAN slice, or an indication indicating whether the SLA for the RAN slice is non-fulfilled or fulfilled in the second network entity.
  • PDCP packet data convergence protocol
  • SDU service data unit
  • the second network entity is configured to transmit the second performance information related to the RAN slice by: receiving a first request for the second performance information via the transceiver from the first network entity, the first request comprising an identifier of the RAN slice and a first measurement object associated with the second performance information; and transmitting a first response via the transceiver to the first network entity, the first response comprising the second performance information.
  • the first measurement object comprises at least one of the following: a UL PDCP SDU loss rate, a PDCP SDU data volume, or an average PDCP re-ordering delay in a UL.
  • the first request comprises a bitmap, each of bits in the bitmap indicating the first measurement object.
  • the information related to the SLA for the RAN slice comprises at least one action to be taken at the second network entity to fulfill the SLA, the at least one action comprising at least one of the following: radio admission control based on the RAN slice, or radio bearer control based on the RAN slice.
  • the first network entity is a CU in a base station and the second network entity is a DU in the base station.
  • the second performance information comprises a measurement or prediction of at least one of the following: a DL UE throughput of the RAN slice, a UL UE throughput of the RAN slice, a first average over-the-air interface packet delay in a DL of the RAN slice, a first number of PRBs used in the DL for data traffic, a second number of PRBs used in a UL of the RAN slice for the data traffic, a second average over-the-air interface packet delay in the UL of the RAN slice, an average RLC packet delay in the UL of the RAN slice, a first mean number of active UEs in the DL of the RAN slice, a second mean number of active UEs in the UL of the RAN slice, a first maximum number of active UEs in the DL of the RAN slice, a second maximum number of active UEs in the UL of the RAN slice, a packet Uu loss rate in the DL of the RAN slice,
  • the second network entity is configured to transmit the second performance information related to the RAN slice by: receiving a second request for the second performance information via the transceiver from the first network entity, the second request comprising an identifier of the RAN slice and a second measurement object associated with the second performance information; and transmitting a second response via the transceiver to the first network entity, the second response comprising the second performance information.
  • the second measurement object comprises at least one of the following: a UE throughput, an average over-the-air interface packet delay, the number of PRBs used for data traffic, an average RLC packet delay in a UL, the number of active UEs, or a packet Uu loss rate in a DL.
  • the second request comprises a bitmap, each of bits in the bitmap indicating the second measurement object.
  • the information related to the SLA for the RAN slice comprises at least one action to be taken at the second network entity to fulfill the SLA, the at least one action comprising at least one of the following: a resource sharing indication indicating that the RAN slice is allowed to use unused dedicated resources of at least one network slice different from the RAN slice, priority values to achieve scheduling prioritization among network slices with different priorities, each of the priority values being associated with one of the network slices, or dedicated resource allocation percentages for DL or UL.
  • the first network entity is a target base station and the second network entity is a source base station.
  • the information related to the SLA for the RAN slice comprises information related to the SLA for the RAN slice in a cell of the target base station; and the second network entity is further configured to: receive, via the transceiver from the first network entity, the information related to the SLA for the RAN slice; and determine the cell as a target cell based on the information related to the SLA for the RAN slice in the cell.
  • the second performance information comprises a third request for the information related to the SLA for the RAN slice, the third request comprising an identifier of the RAN slice and a third measurement object associated with the information related to the SLA.
  • the third measurement object comprises at least one of the following: a state of the SLA for the RAN slice in the cell, a percentage of radio resources used by the RAN slice in the cell, a ratio of the number of fulfilled parameters associated with the SLA to a total number of parameters associated with the SLA in the cell, or load information related to the RAN slice in the cell.
  • the third request comprises a bitmap, each of bits in the bitmap indicating the third measurement object.
  • the information related to the SLA for the RAN slice comprises a measurement or prediction of at least one of the following: an indication indicating whether the SLA for the RAN slice is non-fulfilled or fulfilled in the cell, a percentage of radio resources used by the RAN slice in the cell, a ratio of the number of fulfilled parameters associated with the SLA to a total number of parameters associated with the SLA in the cell, or load information related to the RAN slice in the cell.
  • the load information related to the RAN slice in the cell comprises at least one of the following: usage of resources for the RAN slice for traffics in downlink, usage of resources for the RAN slice for traffics in uplink, or a ratio of the number of resources in the cell available for the RAN slice to a total number of resources available for the cell.
  • Some implementations of a method described herein may include: receiving, at the first network entity from a second network entity, second performance information related to a RAN slice; determining, based at least on the second performance information, information related to SLA for the RAN slice.
  • Some implementations of a method described herein may include: determining second performance information related to a RAN slice; and transmitting, to a first network entity, the second performance information related to the RAN slice, wherein information related to SLA for the RAN slice is determined based at least on the second performance information.
  • Fig. 1 illustrates an example of a wireless communications system that supports assurance of SLA for a RAN slice in accordance with aspects of the present disclosure
  • Fig. 2 illustrates a signaling chart illustrating an example process that supports assurance of SLA for a RAN slice in accordance with aspects of the present disclosure, respectively;
  • Figs. 3, 4 and 5 illustrate a signaling chart illustrating an example implementation of the example process in Fig. 2, respectively;
  • Fig. 6 illustrates an example of a device that supports assurance of SLA for a RAN slice in accordance with some aspects of the present disclosure
  • Fig. 7 illustrates an example of a device that supports assurance of SLA for a RAN slice in accordance with other aspects of the present disclosure
  • Fig. 8 illustrates a flowchart of a method that supports assurance of SLA for a RAN slice in accordance with some aspects of the present disclosure
  • Fig. 9 illustrates a flowchart of a method that supports assurance of SLA for a RAN slice in accordance with other aspects of the present disclosure.
  • references in the present disclosure to “one embodiment, ” “an example embodiment, ” “an embodiment, ” “some embodiments, ” and the like indicate that the embodiment (s) described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment (s) . Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • first and second or the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element could also be termed as a second element, and similarly, a second element could also be termed as a first element, without departing from the scope of embodiments. As used herein, the term “and/or” includes any and all combinations of one or more of the listed terms.
  • OAM operation and maintenance
  • RRM radio resource management
  • a first network entity determines first performance information related to a RAN slice and receives second performance information related to the RAN slice from a second network entity.
  • the first network entity determines, based on the first performance information and the second performance information, information related to SLA for the RAN slice.
  • the first network entity transmit, via the transceiver to the second network entity, the information related to the SLA for the RAN slice.
  • the SLA for the RAN slice may be assured by dynamically controlling a load of the RAN slice based on the information related to the SLA for the RAN slice and possible violations of the SLA may be prevented.
  • Fig. 1 illustrates an example of a wireless communications system 100 that supports assurance of SLA for a RAN slice in accordance with aspects of the present disclosure.
  • the wireless communications system 100 may include one at least one of network entities 102-1 and 102-2 (also referred to as network equipment (NE) ) , one or more terminal devices or UEs 104, a core network 106, and a packet data network 108.
  • the wireless communications system 100 may support various radio access technologies.
  • the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-advanced (LTE-A) network.
  • LTE-A LTE-advanced
  • the wireless communications system 100 may be a 5G network, such as an NR network.
  • the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20.
  • IEEE institute of electrical and electronics engineers
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • IEEE 802.20 The wireless communications system 100 may support radio access technologies beyond 5G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA) , frequency division multiple access (FDMA) , or code division multiple access (CDMA) , etc.
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • CDMA code division multiple access
  • the network entities 102-1 and 102-2 may be collectively referred to as network entities 102 or individually referred to as a network entity 102. Alternatively, the network entities 102-1 and 102-2 may be referred to as a first network entity 102-1 and a second network entity 102-2, respectively.
  • the network entities 102 may be dispersed throughout a geographic region to form the wireless communications system 100.
  • One or more of the network entities 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a radio access network (RAN) node, a base transceiver station, an access point, a NodeB, an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology.
  • a network entity 102 and a UE 104 may communicate via a communication link 110, which may be a wireless or wired connection.
  • a network entity 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.
  • a network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc. ) for one or more UEs 104 within the geographic coverage area 112.
  • a network entity 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc. ) according to one or multiple radio access technologies.
  • a network entity 102 may be moveable, for example, a satellite associated with a non-terrestrial network.
  • different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas 112 may be associated with different network entities 102.
  • Information and signals described herein may be represented using any of a variety of different technologies and techniques.
  • data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
  • the one or more UEs 104 may be dispersed throughout a geographic region of the wireless communications system 100.
  • a UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device, or some other suitable terminology.
  • the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples.
  • the UE 104 may be referred to as an internet-of-things (IoT) device, an internet-of-everything (IoE) device, or machine-type communication (MTC) device, among other examples.
  • IoT internet-of-things
  • IoE internet-of-everything
  • MTC machine-type communication
  • a UE 104 may be stationary in the wireless communications system 100.
  • a UE 104 may be mobile in the wireless communications system 100.
  • the one or more UEs 104 may be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in Fig. 1.
  • a UE 104 may be capable of communicating with various types of devices, such as the network entities 102, other UEs 104, or network equipment (e.g., the core network 106, the packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network equipment) , as shown in Fig. 1.
  • a UE 104 may support communication with other network entities 102 or UEs 104, which may act as relays in the wireless communications system 100.
  • a UE 104 may also be able to support wireless communication directly with other UEs 104 over a communication link 114.
  • a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link.
  • D2D device-to-device
  • the communication link 114 may be referred to as a sidelink.
  • a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.
  • a network entity 102 may support communications with the core network 106, or with another network entity 102, or both.
  • a network entity 102 may interface with the core network 106 through one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) .
  • the network entities 102 may communicate with each other over the backhaul links 116 (e.g., via an X2, Xn, or another network interface) .
  • the network entities 102 may communicate with each other directly (e.g., between the network entities 102) .
  • the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106) .
  • one or more network entities 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC) .
  • An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs) .
  • TRPs transmission-reception points
  • a network entity 102 may be configured in a disaggregated architecture, which may be configured to utilize a protocol stack physically or logically distributed among two or more network entities 102, such as an integrated access backhaul (IAB) network, an open radio access network (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance) , or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN) ) .
  • IAB integrated access backhaul
  • O-RAN open radio access network
  • vRAN virtualized RAN
  • C-RAN cloud RAN
  • a network entity 102 may include one or more of a central unit (CU) , a distributed unit (DU) , a radio unit (RU) , a RAN intelligent controller (RIC) (e.g., a near-real time RIC (Near-RT RIC) , a non-real time RIC (Non-RT RIC) ) , a service management and orchestration (SMO) system, or any combination thereof.
  • CU central unit
  • DU distributed unit
  • RU radio unit
  • RIC RAN intelligent controller
  • SMO service management and orchestration
  • An RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) .
  • One or more components of the network entities 102 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 102 may be located in distributed locations (e.g., separate physical locations) .
  • one or more network entities 102 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .
  • VCU virtual CU
  • VDU virtual DU
  • VRU virtual RU
  • Split of functionality between a CU, a DU, and an RU may be flexible and may support different functionalities depending upon which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof) are performed at a CU, a DU, or an RU.
  • functions e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof
  • a functional split of a protocol stack may be employed between a CU and a DU such that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack.
  • the CU may host upper protocol layer (e.g., a layer 3 (L3) , a layer 2 (L2) ) functionality and signaling (e.g., radio resource control (RRC) , service data adaption protocol (SDAP) , packet data convergence protocol (PDCP) ) .
  • the CU may be connected to one or more DUs or RUs, and the one or more DUs or RUs may host lower protocol layers, such as a layer 1 (L1) (e.g., physical (PHY) layer) or an L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160.
  • L1 e.g., physical (PHY) layer
  • L2 e.g., radio link control (RLC) layer, medium access control (MAC) layer
  • a functional split of the protocol stack may be employed between a DU and an RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack.
  • the DU may support one or multiple different cells (e.g., via one or more RUs) .
  • a functional split between a CU and a DU, or between a DU and an RU may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU, a DU, or an RU, while other functions of the protocol layer are performed by a different one of the CU, the DU, or the RU) .
  • a CU may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions.
  • a CU may be connected to one or more DUs via a midhaul communication link (e.g., F1, F1-c, F1-u)
  • a DU may be connected to one or more RUs via a fronthaul communication link (e.g., open fronthaul (FH) interface)
  • FH open fronthaul
  • a midhaul communication link or a fronthaul communication link may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 102 that are in communication via such communication links.
  • the core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions.
  • the core network 106 may be an evolved packet core (EPC) , or a 5G core (5GC) , which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management functions (AMF) ) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a packet data network (PDN) gateway (P-GW) , or a user plane function (UPF) ) .
  • EPC evolved packet core
  • 5GC 5G core
  • MME mobility management entity
  • AMF access and mobility management functions
  • S-GW serving gateway
  • PDN gateway packet data network gateway
  • UPF user plane function
  • control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc. ) for the one or more UEs 104 served by the one or more network entities 102 associated with the core network 106.
  • NAS non-access stratum
  • the core network 106 may communicate with the packet data network 108 over one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) .
  • the packet data network 108 may include an application server 118.
  • one or more UEs 104 may communicate with the application server 118.
  • a UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the core network 106 via a network entity 102.
  • the core network 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server 118 using the established session (e.g., the established PDU session) .
  • the PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106) .
  • the network entities 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) ) to perform various operations (e.g., wireless communications) .
  • the network entities 102 and the UEs 104 may support different resource structures.
  • the network entities 102 and the UEs 104 may support different frame structures.
  • the network entities 102 and the UEs 104 may support a single frame structure.
  • the network entities 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures) .
  • the network entities 102 and the UEs 104 may support various frame structures based on one or more numerologies.
  • One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix.
  • a first subcarrier spacing e.g., 15 kHz
  • a normal cyclic prefix e.g. 15 kHz
  • the first numerology associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe.
  • a time interval of a resource may be organized according to frames (also referred to as radio frames) .
  • Each frame may have a duration, for example, a 10 millisecond (ms) duration.
  • each frame may include multiple subframes.
  • each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration.
  • each frame may have the same duration.
  • each subframe of a frame may have the same duration.
  • a time interval of a resource may be organized according to slots.
  • a subframe may include a number (e.g., quantity) of slots.
  • the number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100.
  • Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols) .
  • the number (e.g., quantity) of slots for a subframe may depend on a numerology.
  • a slot For a normal cyclic prefix, a slot may include 14 symbols.
  • a slot For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing) , a slot may include 12 symbols.
  • an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc.
  • the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz –7.125 GHz) , FR2 (24.25 GHz –52.6 GHz) , FR3 (7.125 GHz –24.25 GHz) , FR4 (52.6 GHz –114.25 GHz) , FR4a or FR4-1 (52.6 GHz –71 GHz) , and FR5 (114.25 GHz –300 GHz) .
  • FR1 410 MHz –7.125 GHz
  • FR2 24.25 GHz –52.6 GHz
  • FR3 7.125 GHz –24.25 GHz
  • FR4 (52.6 GHz –114.25 GHz)
  • FR4a or FR4-1 52.6 GHz –71 GHz
  • FR5 114.25 GHz
  • the network entities 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands.
  • FR1 may be used by the network entities 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data) .
  • FR2 may be used by the network entities 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.
  • FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies) .
  • FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies) .
  • Fig. 2 illustrates a signaling chart illustrating an example process 200 that supports assurance of SLA for a RAN slice in accordance with aspects of the present disclosure.
  • the process 200 will be described with reference to Fig. 1.
  • the process 200 may involve the first network entity 102-1 and the second network entity 102-2 in Fig. 1.
  • the first network entity 102-1 receives 210, from the second network entity 102-2, second performance information related to a RAN slice.
  • the first network entity 102-1 determines 220 information related to SLA for the RAN slice based at least on the second performance information.
  • the first network entity 102-1 may optionally determine the information related to SLA for the RAN slice using an artificial intelligence (AI) /machine learning (ML) model for assurance of the SLA for the RAN slice.
  • AI artificial intelligence
  • ML machine learning
  • the inputs of the AI/ML model may be the second performance information related to the RAN slice.
  • the outputs of the AI/ML model may be the information related to the SLA for the RAN slice.
  • the information related to the SLA for the RAN slice may comprise a measurement or prediction of an indication indicating whether the SLA for the RAN slice is non-fulfilled or fulfilled.
  • the indication indicating whether the SLA for the RAN slice is non-fulfilled or fulfilled is also referred to as “a state of the SLA for the RAN slice” .
  • the state of the SLA for the RAN slice may be “non-fulfilled” or “fulfilled” .
  • the information related to the SLA for the RAN slice may comprise a measurement or prediction of a percentage of radio resources used by the RAN slice.
  • the percentage of radio resources used by the RAN slice may comprise a percentage of dedicated resources related to the total resources for the RAN slice, or a percentage of prioritized resources related to the total resources for the RAN slice.
  • the information related to the SLA for the RAN slice may comprise a measurement or prediction of a RAN slice SLA class value.
  • the RAN slice SLA class value may indicate a ratio of the number of fulfilled parameter values associated with the SLA to a total number of parameter values associated with the SLA. For example, if the total number of parameter values associated with the SLA is equal to 20 and the number of fulfilled parameter values associated with the SLA is equal to 18, the RAN slice SLA class value is equal to 90 indicating that 90%of the parameter values associated with the SLA are fulfilled.
  • the information related to the SLA for the RAN slice may comprise at least one action to be taken at the second network entity to fulfill the SLA.
  • the first network entity 102-1 may optionally transmit, to the second network entity 102-2, the information related to the SLA for the RAN slice.
  • the first network entity 102-1 may transmit, to the second network entity 102-2, the information related to the SLA for the RAN slice.
  • the first network entity 102-1 may transmit, to the second network entity 102-2, the information related to the SLA for the RAN slice.
  • the first network entity 102-1 may transmit, to the second network entity 102-2, the information related to the SLA for the RAN slice.
  • the first network entity 102-1 may transmit, to the second network entity 102-2, the information related to the SLA for the RAN slice.
  • the second network entity 102-2 may optionally take at least one action to fulfill the SLA based on the information related to the SLA for the RAN slice.
  • the SLA for the RAN slice may be assured by dynamically controlling a load of the RAN slice based on the information related to the SLA for the RAN slice and possible violations of the SLA may be prevented.
  • the first network entity 102-1 may optionally determine first performance information related to the RAN slice. In turn, the first network entity 102-1 may determine the information related to the SLA for the RAN slice based on the first performance information and the second performance information.
  • the first performance information may comprise at least one of the following: a UE throughput, a packet delay, the number of resources used by the RAN slice, the number of active UEs, a packet Uu loss rate, or a status of the SLA for the RAN slice.
  • the second performance information may comprise at least one of the following: PDCP SDU loss rate, a data volume, an average PDCP re-ordering delay, or a status of the SLA for the RAN slice.
  • the first performance information may comprise at least one of the following: PDCP SDU loss rate, a data volume, an average PDCP re-ordering delay, or a status of the SLA for the RAN slice.
  • the second performance information may comprise at least one of the following: a UE throughput, a packet delay, the number of resources used by the RAN slice, the number of active UEs, a packet Uu loss rate, or a status of the SLA for the RAN slice.
  • the first network entity 102-1 may be a DU in a base station and the second network entity 102-2 may be a CU in the base station.
  • the first network entity 102-1 i.e., the DU
  • the second network entity 102-2 may determine the information related to SLA for the RAN slice and trigger at least one action to be taken at the second network entity 102-2 (i.e., the CU) to fulfill the SLA. This will be described with reference to Fig. 3.
  • Fig. 3 illustrates a signaling chart illustrating an example process 300 that supports assurance of SLA for a RAN slice in accordance with aspects of the present disclosure.
  • the example process 300 may be considered as an example implementation of the process 200.
  • the process 300 will be described with reference to Fig. 1.
  • the process 300 may involve the first network entity 102-1 and the second network entity 102-2 in Fig. 1.
  • the first network entity 102-1 is a DU in a base station and the second network entity 102-2 is a CU in the base station.
  • the first network entity 102-1 is also referred to as a DU 102-1 and the second network entity 102-2 is also referred to as a CU 102-2.
  • the DU 102-1 determines 310 first performance information related to the RAN slice. It shall be noted that the action 310 is optional.
  • the first performance information may comprise a measurement or prediction of at least one of the following: a downlink (DL) UE throughput of the RAN slice, or an uplink (UL) UE throughput of the RAN slice.
  • DL/UL UE throughput of the RAN slice may be determined according to the where ThpVol represents the radio link control (RLC) level volume of a data burst in DL/UL in the RAN slice, excluding the data transmitted in the slot when the buffer is emptied; ThpTime represents the time to transmit a data burst excluding the data transmitted in the slot when the buffer is emptied.
  • RLC radio link control
  • the first performance information may comprise a measurement or prediction of a first average over-the-air interface packet delay in a DL of the RAN slice.
  • the first average over-the-air interface packet delay provides the average time it takes for packet transmission over-the-air interface in the DL direction in the RAN slice.
  • the first average over-the-air interface packet delay may be determined according to the where T1 represents the point in time when the last part of an RLC service data unit (SDU) packet was sent to the UE which was consequently confirmed by reception of hybrid automatic repeat request (HARQ) acknowledge (ACK) from UE for unacknowledged mode (UM) mode or point in time when the last part of an RLC SDU packet was sent to the UE which was consequently confirmed by reception of RLC ACK for acknowledged mode (AM) mode; T2 represents the time when corresponding RLC SDU part arrives at medium access control (MAC) layer; I (T) represents the total number of RLC SDUs transmitted to the UE successfully.
  • HARQ hybrid automatic repeat request
  • ACK hybrid automatic repeat request
  • UM unacknowledged mode
  • AM acknowledged mode
  • T2 represents the time when corresponding RLC SDU part arrives at medium access control (MAC) layer
  • I (T) represents the total number of RLC SDUs transmitted to the UE successfully.
  • the first performance information may comprise a measurement or prediction of at least one of the following: a first number of physical resource blocks (PRBs) used in the DL for data traffic, or a second number of PRBs used in a UL of the RAN slice for the data traffic.
  • PRBs physical resource blocks
  • the first performance information may comprise a measurement or prediction of a second average over-the-air interface packet delay in the UL of the RAN slice.
  • the second average over-the-air interface packet delay provides the average time it takes for packet transmission over-the-air interface in the UL direction in the RAN slice.
  • the second average over-the-air interface packet delay may be determined according to the where T1 represents the point in time when the UL MAC SDU is successfully sent to RLC; T2 represents the point in time when the UL MAC SDU is scheduled in MAC layer as per the scheduling grant provided; I (T) represents the total number of UL MAC SDU.
  • the first performance information may comprise a measurement or prediction of an average RLC packet delay in the UL of the RAN slice.
  • the average RLC packet delay in the UL of the RAN slice provides the average RLC packet delay in UL, i.e., the delay within the DU 102-1 (i.e., DU) .
  • the average RLC packet delay in the UL of the RAN slice may be determined according to the where T1 represents the point in time when the UL RLC SDU is sent to PDCP or CU; T2 represents the point in time when the UL RLC PDU including the first part of the UL RLC SDU is received; I (T) represents the total number of UL RLC SDU.
  • the first performance information may comprise a measurement or prediction of at least one of the following: a first mean number of active UEs in the DL of the RAN slice, or a second mean number of active UEs in the UL of the RAN slice, where “active UEs” means UEs whose applications are transmitting and receiving data.
  • the first mean number of active UEs in the DL of the RAN slice or the second mean number of active UEs in the UL of the RAN slice may be determined according to the where i represents the sampling occasion during time period T; T represents the time period during which the measurement is performed; P represents the sampling period length; I (T, P) represents the total number of sampling occasions during time period T; Ni represents the number of active UEs for which there is data available for transmission for the DL/UL in MAC or RLC layers for a data radio bearer (DRB) of traffic class at sampling occasion i.
  • DRB data radio bearer
  • the first performance information may comprise a measurement or prediction of at least one of the following: a first maximum number of active UEs in the DL of the RAN slice, or a second maximum number of active UEs in the UL of the RAN slice.
  • the first maximum number of active UEs in the DL of the RAN slice or the second maximum number of active UEs in the UL of the RAN slice may be determined according to the following: ⁇ drbs max T N i , where i represents the sampling occasion during time period T; T represents the time period during which the measurement is performed; Ni represents the number of active UEs for which there is data available for transmission for the DL/UL in MAC or RLC layers for a DRB of traffic class at sampling occasion i.
  • the first performance information may comprise a measurement or prediction of a packet Uu loss rate in the DL of the RAN slice.
  • the packet Uu loss rate in the DL of the RAN slice provides the fraction of RLC SDU packets that are lost at Uu transmission.
  • the packet Uu loss rate in the DL of the RAN slice may be determined according to the where Dloss represents the number of DL packets for which at least a part has been transmitted over the air but not positively acknowledged; Nsuccess represents the number of DL packets for which has been transmitted over the air and positively acknowledged.
  • the first performance information may comprise a measurement or prediction of an indication indicating whether the SLA for the RAN slice is non-fulfilled or fulfilled in the DU 102-1.
  • the first performance information may comprise a state of the SLA for the RAN slice determined at the DU 102-1.
  • the state of the SLA for the RAN slice may be “non-fulfilled” or “fulfilled” .
  • the DU 102-1 may determine the state of the SLA for the RAN slice based on the measurement or prediction of at least one of the parameters as described above.
  • the DU 102-1 transmits 320 a first request for the second performance information to the CU 102-2.
  • the first request comprises an identifier of the RAN slice and a first measurement object associated with the second performance information.
  • the identifier of the RAN slice may include but is not limited to single network slice selection assistance information (S-NSSAI) of the RAN slice.
  • S-NSSAI single network slice selection assistance information
  • the S-NSSAI of the RAN slice may comprise at least one of the following a slice/service type, which refers to the expected network slice behavior in terms of features and services; or a slice differentiator, which is optional information that complements the slice/service type (s) to differentiate amongst multiple network slices of the same slice/service type.
  • the first measurement object may comprise at least one of the following: a UL packet data convergence protocol (PDCP) SDU loss rate, a PDCP SDU data volume, or an average PDCP re-ordering delay in a UL.
  • PDCP packet data convergence protocol
  • the first request may comprise a bitmap.
  • Each of bits in the bitmap indicates the first measurement object. For example, a first bit in the bitmap indicates the UL PDCP SDU loss rate of the RAN slice, a second bit in the bitmap indicates the PDCP SDU data volume of the RAN slice, a third bit in the bitmap indicates the average PDCP re-ordering delay in the UL of the RAN slice, other bits are reserved for further use.
  • the first request may comprise the identifier of the RAN slice only, e.g., S-NSSAI, without the first measurement object or the bitmap.
  • the CU 102-2 may provide the second performance information related to all the first measurement object as described above.
  • the CU 102-2 determines 330 the second performance information related to the RAN slice.
  • the second performance information may comprise a measurement or prediction of a UL PDCP SDU loss rate of the RAN slice.
  • the UL PDCP SDU loss rate of the RAN slice provides the fraction of PDCP SDU packets that are not successfully received at the CU 102-2.
  • the UL PDCP SDU loss rate of the RAN slice may be determined according to the following: 1000000*Number of missing UL PDCP sequence numbers, representing packets that are not delivered to higher layers, divided by Total number of UL PDCP sequence numbers (also including missing sequence numbers) , starting from the sequence number of the first packet delivered by UE PDCP to the CU 102-2 until the sequence number of the last packet.
  • the second performance information may comprise a measurement or prediction of a DL PDCP SDU data volume of the RAN slice.
  • the DL PDCP SDU data volume of the RAN slice provides the data volume in the DL delivered to the PDCP layer.
  • the measurement of the DL PDCP SDU data volume of the RAN slice may be obtained by the CU 102-2 by counting the number of bits entering the PDCP layers belonging to the RAN slice.
  • the second performance information may comprise a measurement or prediction of a UL PDCP SDU data volume of the RAN slice.
  • the UL PDCP SDU data volume of the RAN slice provides the data volume in the UL delivered from the PDCP layer to the upper layer or core network.
  • the measurement of the UL PDCP SDU data volume may be obtained by the CU 102-2 by counting the number of bits leaving the PDCP layers belonging to the RAN slice.
  • the second performance information may comprise a measurement or prediction of an average PDCP re-ordering delay in the UL of the RAN slice.
  • the average PDCP re-ordering delay in the UL of the RAN slice provides the average PDCP re-ordering delay on the UL, i.e., the delay within the CU 102-2.
  • the average PDCP re-ordering delay in the UL of the RAN slice may be determined according to the where T1 represents the point in time when the UL PDCP SDU is sent to upper service access point (SAP) ; T2 represents the point in time when the UL PDCP PDU is received; I (T) represents the total number of UL PDCP SDU during time period T.
  • the second performance information may comprise a measurement or prediction of an indication indicating whether the SLA for the RAN slice is non-fulfilled or fulfilled in the CU 102-2.
  • the second performance information may comprise a measurement or prediction of a state of the SLA for the RAN slice determined at the CU 102-2.
  • the state of the SLA for the RAN slice may be “non-fulfilled” or “fulfilled” .
  • the CU 102-2 may determine the state of the SLA for the RAN slice based on the measurement or prediction of at least one of the following: the UL PDCP SDU loss rate of the RAN slice, the DL PDCP SDU data volume of the RAN slice, the UL PDCP SDU data volume of the RAN slice, or the average PDCP re-ordering delay in the UL of the RAN slice.
  • the CU 102-2 Upon determining the second performance information related to the RAN slice, the CU 102-2 transmits 340 a first response to the DU 102-1.
  • the first response comprises the second performance information.
  • the first request may comprise S-NSSAIs of multiple RAN slices, which indicates that performance information related to the multiple RAN slices are requested to report.
  • the CU 102-2 may transmit multiple responses to the DU 102-1. Each of the multiple responses comprises performance information related to one of the multiple RAN slices.
  • the DU 102-1 Upon receiving the second performance information related to the RAN slice, the DU 102-1 determines 350 the information related to the SLA for the RAN slice based on the second performance information related to the RAN slice.
  • the DU 102-1 determines 350 the information related to the SLA for the RAN slice based on the first performance information related to the RAN slice and the second performance information related to the RAN slice.
  • the DU 102-1 may determine the information related to SLA for the RAN slice using an AI/ML model for assurance of the SLA for the RAN slice.
  • the inputs of the AI/ML model may be the second performance information related to the RAN slice, or the first performance information related to the RAN slice and the second performance information related to the RAN slice.
  • the outputs of the AI/ML model may be the information related to the SLA for the RAN slice.
  • the information related to the SLA for the RAN slice may comprise a measurement or prediction of at least one of the following: an indication indicating whether the SLA for the RAN slice is non-fulfilled or fulfilled, a percentage of radio resources used by the RAN slice, a ratio of the number of fulfilled parameter values associated with the SLA to a total number of parameter values associated with the SLA, or at least one action to be taken at the CU 102-2 to fulfill the SLA.
  • the at least one action to be taken at the CU 102-2 to fulfill the SLA may comprise at least one of the following: radio admission control based on the RAN slice (e.g., RRC connection release) or radio bearer control based on the RAN slice (e.g., dual connectivity (DC) addition, DRB addition) .
  • radio admission control based on the RAN slice e.g., RRC connection release
  • radio bearer control based on the RAN slice e.g., dual connectivity (DC) addition, DRB addition
  • the DU 102-1 Upon determining the information related to the SLA for the RAN slice, the DU 102-1 transmits 360 the information related to the SLA for the RAN slice to the CU 102-2. It shall be noted that the action 360 is optional.
  • the CU 102-2 Upon receiving the information related to the SLA for the RAN slice, the CU 102-2 takes 370 at least one action to fulfill the SLA based on the information related to the SLA for the RAN slice. For example, if the information related to SLA for the RAN slice comprises at least one action to be taken at the CU 102-2 to fulfill the SLA, the CU 102-2 may take the at least one action as indicated in the information related to SLA. For another example, the CU 102-2 may take at least one action which is not indicated in the information related to SLA. It shall be noted that the action 370 is optional.
  • action 310 is shown prior to the actions 320, 330 and 340 by way of example. In other implementations, the action 310 may be performed in parallel to or subsequent to any of the actions 320, 330 and 340.
  • the first network entity 102-1 may be a CU in a base station and the second network entity 102-2 may be a DU in the base station.
  • the first network entity 102-1 i.e., the CU
  • the second network entity 102-2 may determine the information related to SLA for the RAN slice and trigger at least one action to be taken at the second network entity 102-2 (i.e., the DU) to fulfill the SLA. This will be described with reference to Fig. 4.
  • Fig. 4 illustrates a signaling chart illustrating an example process 400 that supports assurance of SLA for a RAN slice in accordance with aspects of the present disclosure.
  • the example process 400 may be considered as another example implementation of the process 200.
  • the process 400 will be described with reference to Fig. 1.
  • the process 400 may involve the first network entity 102-1 and the second network entity 102-2 in Fig. 1.
  • the first network entity 102-1 is a CU in a base station and the second network entity 102-2 is a DU in the base station.
  • the first network entity 102-1 is also referred to as a CU 102-1 and the second network entity 102-2 is also referred to as a DU 102-2.
  • the CU 102-1 determines 410 first performance information related to the RAN slice. It shall be noted that the action 410 is optional.
  • the first performance information may comprise a measurement or prediction of at least one of the following: a UL PDCP SDU loss rate of the RAN slice, a DL PDCP SDU data volume of the RAN slice, a UL PDCP SDU data volume of the RAN slice, or an average PDCP re-ordering delay in the UL of the RAN slice.
  • Details of the first performance information in the process 400 are the same as details of the second performance information as described above regarding the action 330 in the process 300. Thus, the details of the first performance information in the process 400 are omitted for brevity.
  • the CU 102-1 transmits 420 a second request for the second performance information to the DU 102-2.
  • the second request comprises an identifier of the RAN slice and a second measurement object associated with the second performance information.
  • the identifier of the RAN slice may include but is not limited to S-NSSAI of the RAN slice.
  • the second measurement object may comprise at least one of the following: a UE throughput, an average over-the-air interface packet delay, the number of PRBs used for data traffic, an average RLC packet delay in a UL, the number of active UEs, or a packet Uu loss rate in a DL.
  • the second request may comprise a bitmap.
  • Each of bits in the bitmap indicating the second measurement object For example, a first bit in the bitmap indicates the UE throughput of the RAN slice, a second bit in the bitmap indicates the average over-the-air interface packet delay of the RAN slice, a third bit in the bitmap indicates the PRB used for data traffic of the RAN slice, a fourth bit in the bitmap indicates the average RLC packet delay in the UL of the RAN slice, a fifth bit in the bitmap indicates the number of active UEs of the RAN slice, a sixth bit in the bitmap indicates the packet Uu loss rate in the DL of the RAN slice, other bits are reserved for further use.
  • the second request may comprise the identifier of the RAN slice only, e.g., S-NSSAI, without the second measurement object or the bitmap.
  • the DU 102-2 may provide the second performance information related to all the second measurement object as described above.
  • the DU 102-2 determines 430 the second performance information related to the RAN slice.
  • the second performance information may comprise a measurement or prediction of at least one of the following:
  • the percentage of radio resources used by the RAN slice may comprise at least one of the following: a percentage of dedicated resources related to the total resources for the RAN slice, or a percentage of prioritized resources related to the total resources for the RAN slice.
  • Details of the second performance information in the process 400 are the same as details of the first performance information as described above regarding the action 310 in the process 300. Thus, the details of the second performance information in the process 400 are omitted for brevity.
  • the DU 102-2 Upon determining the second performance information related to the RAN slice, the DU 102-2 transmits 440 a second response to the CU 102-1.
  • the second response comprises the second performance information.
  • the second request may comprise S-NSSAIs of multiple RAN slices, which indicates that performance information related to the multiple RAN slices are requested to report.
  • the DU 102-2 may transmit multiple responses to the CU 102-1. Each of the multiple responses comprises performance information related to one of the multiple RAN slices.
  • the CU 102-1 Upon receiving the second performance information related to the RAN slice, the CU 102-1 determines 450 the information related to the SLA for the RAN slice based on the second performance information related to the RAN slice.
  • the CU 102-1 determines 450 the information related to the SLA for the RAN slice based on the first performance information related to the RAN slice and the second performance information related to the RAN slice.
  • the CU 102-1 may determine the information related to SLA for the RAN slice using an AI/ML model for assurance of the SLA for the RAN slice.
  • the inputs of the AI/ML model may be second performance information related to the RAN slice, or the first performance information related to the RAN slice and the second performance information related to the RAN slice.
  • the outputs of the AI/ML model may be the information related to the SLA for the RAN slice.
  • the information related to the SLA for the RAN slice may comprise a measurement or prediction of at least one of the following: an indication indicating whether the SLA for the RAN slice is non-fulfilled or fulfilled, a percentage of radio resources used by the RAN slice, a ratio of the number of fulfilled parameter values associated with the SLA to a total number of parameter values associated with the SLA, or at least one action to be taken at the DU 102-2 to fulfill the SLA.
  • the at least one action to be taken at the DU 102-2 to fulfill the SLA may comprise at least one of the following: a resource sharing indication indicating that the RAN slice is allowed to use unused dedicated resources of at least one network slice different from the RAN slice, priority values to achieve scheduling prioritization among network slices with different priorities, each of the priority values being associated with one of the network slices, or dedicated resource allocation percentages for DL or UL.
  • the CU 102-1 Upon determining the information related to the SLA for the RAN slice, the CU 102-1 transmits 460 the information related to the SLA for the RAN slice to the DU 102-2. It shall be noted that the action 460 is optional.
  • the DU 102-2 Upon receiving the information related to the SLA for the RAN slice, the DU 102-2 takes 470 at least one action to fulfill the SLA based on the information related to the SLA for the RAN slice. For example, if the information related to SLA for the RAN slice comprises at least one action to be taken at the DU 102-2 to fulfill the SLA, the DU 102-2 may take the at least one action as indicated in the information related to SLA. For another example, the DU 102-2 may take at least one action which is not indicated in the information related to SLA. It shall be noted that the action 470 is optional.
  • action 410 is shown prior to the actions 420, 430 and 440 by way of example. In other implementations, the action 410 may be performed in parallel to or subsequent to any of the actions 420, 430 and 440.
  • the first network entity 102-1 is a target base station and the second network entity 102-2 is a source base station.
  • the source base station may obtain information related to the SLA for the RAN slice in a cell of the target base station.
  • the source base station may determine the cell of the target base station as a target cell based on the information related to the SLA for the RAN slice in the cell. This will be described with reference to Fig. 5.
  • Fig. 5 illustrates a signaling chart illustrating an example process 500 that supports assurance of SLA for a RAN slice in accordance with aspects of the present disclosure.
  • the example process 500 may be considered as a further example implementation of the process 200.
  • the process 500 will be described with reference to Fig. 1.
  • the process 500 may involve the first network entity 102-1 and the second network entity 102-2 in Fig. 1.
  • the first network entity 102-1 is a target base station and the second network entity 102-2 is a source base station.
  • the first network entity 102-1 is also referred to as a target base station 102-1 and the second network entity 102-2 is also referred to as a source base station 102-2.
  • the target base station 102-1 receives 510, from the source base station 102-2, second performance information related to a RAN slice.
  • the second performance information related to the RAN slice comprises a third request for the information related to the SLA for the RAN slice.
  • the third request comprises an identifier of the RAN slice and a third measurement object associated with the information related to the SLA.
  • the identifier of the RAN slice may include but is not limited to S-NSSAI of the RAN slice.
  • the third measurement object may comprise at least one of the following: a state of the SLA for the RAN slice in a cell of the target base station 102-1, a percentage of radio resources used by the RAN slice in the cell, a ratio of the number of fulfilled parameters associated with the SLA to a total number of parameters associated with the SLA in the cell, or load information related to the RAN slice in the cell.
  • the third request may comprise a bitmap.
  • Each of bits in the bitmap indicates the third measurement object. For example, a first bit in the bitmap indicates the state of the SLA for the RAN slice in the cell, a second bit in the bitmap indicates the percentage of radio resources used by the RAN slice in the cell, a third bit in the bitmap indicates the ratio of the number of fulfilled parameters associated with the SLA to the total number of parameters associated with the SLA in the cell, a fourth bit in the bitmap indicates the load information related to the RAN slice in the cell, other bits are reserved for further use.
  • the third request may comprise the identifier of the RAN slice only, e.g., S-NSSAI, without the third measurement object or the bitmap.
  • the target base station 102-1 may provide the information related to SLA for the RAN slice in the cell related to all the third measurement object as described above.
  • the target base station 102-1 determines 520 information related to SLA for the RAN slice in the cell based at least on the second performance information.
  • the target base station 102-1 may determine the information related to SLA for the RAN slice in the cell using an AI/ML model for assurance of the SLA for the RAN slice, as described above regarding the action 220 in Fig. 2, the action 350 in Fig. 3 or the action 450 in Fig. 4. Details of the determination of the information related to SLA for the RAN slice in the cell are omitted for brevity.
  • the information related to the SLA for the RAN slice in the cell may comprise a measurement or prediction of an indication indicating whether the SLA for the RAN slice is non-fulfilled or fulfilled in the cell of the target base station 102-1.
  • the information related to the SLA for the RAN slice in the cell may comprise a measurement or prediction of a percentage of radio resources used by the RAN slice in the cell.
  • the percentage of radio resources used by the RAN slice in the cell may comprise a percentage of dedicated resources related to the total resources for the RAN slice in the cell, or a percentage of prioritized resources related to the total resources for the RAN slice in the cell.
  • the information related to the SLA for the RAN slice in the cell may comprise a measurement or prediction of a RAN slice SLA class value.
  • the RAN slice SLA class value indicates a ratio of the number of fulfilled parameter values associated with the SLA to a total number of parameter values associated with the SLA in the cell. For example, if the total number of parameter values associated with the SLA is equal to 20 and the number of fulfilled parameter values associated with the SLA is equal to 18, the RAN slice SLA class value is equal to 90 indicating that 90%of the parameter values associated with the SLA are fulfilled.
  • the information related to the SLA for the RAN slice in the cell may comprise a measurement or prediction of load information related to the RAN slice in the cell.
  • the load information related to the RAN slice is also referred to as a slice level load.
  • the load information related to the RAN slice in the cell may comprise at least one of the following: a slice radio resource status, or a slice available capacity.
  • the slice radio resource status may indicate usage of resources for the RAN slice for traffics in DL and/or UL.
  • the slice available capacity may indicate a ratio of the number of resources in the cell available for the RAN slice to a total number of resources available for the cell.
  • the target base station 102-1 transmits 530 the information related to the SLA for the RAN slice in the cell to the source base station 102-2.
  • the source base station 102-2 Upon receiving the information related to the SLA for the RAN slice in the cell, the source base station 102-2 determines 540 whether to select the cell as a target cell based on the information related to the SLA for the RAN slice in the cell.
  • the source base station 102-2 determines to select the cell as the target cell if the state of the SLA for the RAN slice in the cell is fulfilled.
  • the source base station 102-2 determines to select the cell as the target cell if the cell has the highest RAN slice SLA class value.
  • the source base station 102-2 determines to select the cell as the target cell if the cell has the highest percentage of radio resources used by the RAN slice.
  • the source base station 102-2 determines to select the cell as the target cell if the cell has the lowest slice level load.
  • the source base station 102-2 initiates a handover procedure towards the selected target cell in the target base station 102-1.
  • Fig. 6 illustrates an example of a device 600 that supports assurance of SLA for a RAN slice at a network entity in accordance with aspects of the present disclosure.
  • the device 600 may be an example of the network entity 102-1 as described herein.
  • the device 600 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof.
  • the device 600 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 602, a memory 604, a transceiver 606, and, optionally, an I/O controller 608. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .
  • the processor 602, the memory 604, the transceiver 606, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein.
  • the processor 602, the memory 604, the transceiver 606, or various combinations or components thereof may support a method for performing one or more of the operations described herein.
  • the processor 602, the memory 604, the transceiver 606, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field- programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • the processor 602 and the memory 604 coupled with the processor 602 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 602, instructions stored in the memory 604) .
  • the processor 602 may support wireless communication at the device 600 in accordance with examples as disclosed herein.
  • the processor 602 may be configured to operable to support a means for the following: receiving, from a second network entity, second performance information related to a RAN slice; determining, based at least on the second performance information, information related to SLA for the RAN slice.
  • the processor 602 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) .
  • the processor 602 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 602.
  • the processor 602 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 604) to cause the device 600 to perform various functions of the present disclosure.
  • the memory 604 may include random access memory (RAM) and read-only memory (ROM) .
  • the memory 604 may store computer-readable, computer-executable code including instructions that, when executed by the processor 602 cause the device 600 to perform various functions described herein.
  • the code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory.
  • the code may not be directly executable by the processor 602 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 604 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • BIOS basic I/O system
  • the I/O controller 608 may manage input and output signals for the device 600.
  • the I/O controller 608 may also manage peripherals not integrated into the device M02.
  • the I/O controller 608 may represent a physical connection or port to an external peripheral.
  • the I/O controller 608 may utilize an operating system such as or another known operating system.
  • the I/O controller 608 may be implemented as part of a processor, such as the processor 606.
  • a user may interact with the device 600 via the I/O controller 608 or via hardware components controlled by the I/O controller 608.
  • the device 600 may include a single antenna 610. However, in some other implementations, the device 600 may have more than one antenna 610 (i.e., multiple antennas) , including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the transceiver 606 may communicate bi-directionally, via the one or more antennas 610, wired, or wireless links as described herein.
  • the transceiver 606 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 606 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 610 for transmission, and to demodulate packets received from the one or more antennas 610.
  • the transceiver 606 may include one or more transmit chains, one or more receive chains, or a combination thereof.
  • a transmit chain may be configured to generate and transmit signals (e.g., control information, data, packets) .
  • the transmit chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium.
  • the at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM) , frequency modulation (FM) , or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM) .
  • the transmit chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium.
  • the transmit chain may also include one or more antennas 610 for transmitting the amplified signal into the air or wireless medium.
  • a receive chain may be configured to receive signals (e.g., control information, data, packets) over a wireless medium.
  • the receive chain may include one or more antennas 610 for receive the signal over the air or wireless medium.
  • the receive chain may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal.
  • the receive chain may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal.
  • the receive chain may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
  • Fig. 7 illustrates an example of a device 700 that supports assurance of SLA for a RAN slice at a network entity in accordance with aspects of the present disclosure.
  • the device 700 may be an example of the network entity 102-2 as described herein.
  • the device 700 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof.
  • the device 700 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 702, a memory 704, a transceiver 706, and, optionally, an I/O controller 708. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .
  • the processor 702, the memory 704, the transceiver 706, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein.
  • the processor 702, the memory 704, the transceiver 706, or various combinations or components thereof may support a method for performing one or more of the operations described herein.
  • the processor 702, the memory 704, the transceiver 706, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • the processor 702 and the memory 704 coupled with the processor 702 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 702, instructions stored in the memory 704) .
  • the processor 702 may support wireless communication at the device 700 in accordance with examples as disclosed herein.
  • the processor 702 may be configured to operable to support a means for the following: determining second performance information related to a RAN slice; and transmitting, to a first network entity, the second performance information related to the RAN slice.
  • the processor 702 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) .
  • the processor 702 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 702.
  • the processor 702 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 704) to cause the device 700 to perform various functions of the present disclosure.
  • the memory 704 may include random access memory (RAM) and read-only memory (ROM) .
  • the memory 704 may store computer-readable, computer-executable code including instructions that, when executed by the processor 702 cause the device 700 to perform various functions described herein.
  • the code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory.
  • the code may not be directly executable by the processor 702 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 704 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • BIOS basic I/O system
  • the I/O controller 708 may manage input and output signals for the device 700.
  • the I/O controller 708 may also manage peripherals not integrated into the device M02.
  • the I/O controller 708 may represent a physical connection or port to an external peripheral.
  • the I/O controller 708 may utilize an operating system such as or another known operating system.
  • the I/O controller 708 may be implemented as part of a processor, such as the processor 706.
  • a user may interact with the device 700 via the I/O controller 708 or via hardware components controlled by the I/O controller 708.
  • the device 700 may include a single antenna 710. However, in some other implementations, the device 700 may have more than one antenna 710 (i.e., multiple antennas) , including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the transceiver 706 may communicate bi-directionally, via the one or more antennas 710, wired, or wireless links as described herein.
  • the transceiver 706 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 706 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 710 for transmission, and to demodulate packets received from the one or more antennas 710.
  • the transceiver 706 may include one or more transmit chains, one or more receive chains, or a combination thereof.
  • a transmit chain may be configured to generate and transmit signals (e.g., control information, data, packets) .
  • the transmit chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium.
  • the at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM) , frequency modulation (FM) , or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM) .
  • the transmit chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium.
  • the transmit chain may also include one or more antennas 710 for transmitting the amplified signal into the air or wireless medium.
  • a receive chain may be configured to receive signals (e.g., control information, data, packets) over a wireless medium.
  • the receive chain may include one or more antennas 710 for receive the signal over the air or wireless medium.
  • the receive chain may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal.
  • the receive chain may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal.
  • the receive chain may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
  • Fig. 8 illustrates a flowchart of a method 800 that supports assurance of SLA for a RAN slice at a network entity in accordance with aspects of the present disclosure.
  • the operations of the method 800 may be implemented by a device or its components as described herein.
  • the operations of the method 800 may be performed by the network entity 102-1 as described herein.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving, from a second network entity, second performance information related to a RAN slice.
  • the operation of 810 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation of 810 may be performed by a device as described with reference to Fig. 1.
  • the method may include determining, based at least on the second performance information, information related to SLA for the RAN slice.
  • the operation of 820 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation of 820 may be performed by a device as described with reference to Fig. 1.
  • Fig. 9 illustrates a flowchart of a method 900 that supports assurance of SLA for a RAN slice at a network entity in accordance with aspects of the present disclosure.
  • the operations of the method 900 may be implemented by a device or its components as described herein.
  • the operations of the method 900 may be performed by the network entity 102-2 as described herein.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include determining second performance information related to a RAN slice.
  • the operation of 910 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation of 910 may be performed by a device as described with reference to Fig. 1.
  • the method may include transmitting, to a first network entity, the second performance information related to the RAN slice.
  • the operation of 920 may be performed in accordance with examples as described herein. In some implementations, aspects of the operation of 920 may be performed by a device as described with reference to Fig. 1.
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • the functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations
  • Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.
  • non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • an article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements.
  • the terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable.
  • a list of items indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) .
  • the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure.
  • the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.
  • a “set” may include one or more elements.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Divers aspects de la présente divulgation concernent des entités de réseau et des procédés de prise en charge de l'assurance de SLA pour une tranche de RAN au niveau d'une entité de réseau. Selon un aspect, une première entité de réseau reçoit, en provenance d'une seconde entité de réseau, des secondes informations de performance relatives à une tranche de RAN. La première entité de réseau détermine, au moins sur la base des secondes informations de performance, des informations relatives au SLA pour la tranche de RAN.
PCT/CN2023/106179 2023-07-06 2023-07-06 Prise en charge d'assurance de sla pour tranche de ran WO2024093341A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/106179 WO2024093341A1 (fr) 2023-07-06 2023-07-06 Prise en charge d'assurance de sla pour tranche de ran

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/106179 WO2024093341A1 (fr) 2023-07-06 2023-07-06 Prise en charge d'assurance de sla pour tranche de ran

Publications (1)

Publication Number Publication Date
WO2024093341A1 true WO2024093341A1 (fr) 2024-05-10

Family

ID=90929583

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/106179 WO2024093341A1 (fr) 2023-07-06 2023-07-06 Prise en charge d'assurance de sla pour tranche de ran

Country Status (1)

Country Link
WO (1) WO2024093341A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190327153A1 (en) * 2016-10-18 2019-10-24 Telefonaktiebolaget Lm Ericsson (Publ) SLA Handling In Network Slices
US20210368379A1 (en) * 2020-05-19 2021-11-25 T-Mobile Usa, Inc. Bandwidth part configuration for network slicing
US20220022090A1 (en) * 2018-11-20 2022-01-20 Telefonaktiebolaget Lm Ericsson (Publ) Network Slice Service Level Agreement, SLA, Fulfilment
WO2023009046A1 (fr) * 2021-07-27 2023-02-02 Telefonaktiebolaget Lm Ericsson (Publ) Procédés de commande de transfert intercellulaire de session de service entre des tranches de réseau, nœuds de réseau et dispositif de communications mettant en œuvre les procédés dans un réseau de communications

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190327153A1 (en) * 2016-10-18 2019-10-24 Telefonaktiebolaget Lm Ericsson (Publ) SLA Handling In Network Slices
US20220022090A1 (en) * 2018-11-20 2022-01-20 Telefonaktiebolaget Lm Ericsson (Publ) Network Slice Service Level Agreement, SLA, Fulfilment
US20210368379A1 (en) * 2020-05-19 2021-11-25 T-Mobile Usa, Inc. Bandwidth part configuration for network slicing
WO2023009046A1 (fr) * 2021-07-27 2023-02-02 Telefonaktiebolaget Lm Ericsson (Publ) Procédés de commande de transfert intercellulaire de session de service entre des tranches de réseau, nœuds de réseau et dispositif de communications mettant en œuvre les procédés dans un réseau de communications

Similar Documents

Publication Publication Date Title
KR102488415B1 (ko) 채널 리소스 이용에 따라 우선순위화된 트래픽을 위한 lte-v2v 에서의 혼잡 제어
CN107667559B (zh) 在无线通信系统中使用不同的无线连接技术提供多连接的装置和方法
US10784994B2 (en) Method for transmitting information for LTE-WLAN aggregation system and a device therefor
WO2021183920A1 (fr) Prise en charge de qualité de service pour service de relais de liaison latérale
CN115486188A (zh) 非地面网络中的缓冲区状态报告传输
JP2022550802A (ja) フィードバック制御をサポートするためのサイドリンクグループキャスト構成
US20200092045A1 (en) Radio Node and Methods in a Wireless Communications Network
CN114270909B (zh) 用于无线回程系统中的协调通知的方法和装置
WO2023199171A1 (fr) Sélection d'agrégation de porteuses de liaison latérale
WO2024093341A1 (fr) Prise en charge d'assurance de sla pour tranche de ran
CN116762445A (zh) 用于侧链路全双工通信的资源分配
WO2024093370A1 (fr) Obtention de rapport d'accès aléatoire pour noeud secondaire
US20240237061A9 (en) Techniques for sidelink channel sensing with mini-slots
US20240137975A1 (en) Techniques for sidelink channel sensing with mini-slots
US20240098619A1 (en) Sidelink unlicensed channel relay selection
US20230388094A1 (en) Enhancing reference signal transmission in carrier aggregation
WO2024077590A1 (fr) Récupération améliorée après défaillance de liaison radio dans un relais ue à ue
US20230397192A1 (en) Transmission control protocol acknowledgement shaping
US20230388970A1 (en) Retransmission and selection of harq and mcs based on partial sensing
WO2024113300A1 (fr) Techniques de planification de transmissions de liaison latérale non causales
WO2024088019A1 (fr) Signalisation de rapport d'état de retard
US20240089947A1 (en) Broadcast traffic scheduling across multiple radio access technologies
US20240214923A1 (en) Dynamic adaptation of a sleep cycle for a cell
US20240236959A9 (en) Bandwidth part switching techniques for network power savings
US20240137918A1 (en) Bandwidth part switching techniques for network power savings

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23884280

Country of ref document: EP

Kind code of ref document: A1