WO2024207406A1 - Logging and signaling of operations for machine learning life-cycle management - Google Patents
Logging and signaling of operations for machine learning life-cycle management Download PDFInfo
- Publication number
- WO2024207406A1 WO2024207406A1 PCT/CN2023/086829 CN2023086829W WO2024207406A1 WO 2024207406 A1 WO2024207406 A1 WO 2024207406A1 CN 2023086829 W CN2023086829 W CN 2023086829W WO 2024207406 A1 WO2024207406 A1 WO 2024207406A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- operations
- functionality
- receiving
- examples
- operation report
- Prior art date
Links
- 238000010801 machine learning Methods 0.000 title claims abstract description 224
- 230000011664 signaling Effects 0.000 title claims description 141
- 230000006854 communication Effects 0.000 claims abstract description 364
- 238000004891 communication Methods 0.000 claims abstract description 364
- 238000000034 method Methods 0.000 claims abstract description 143
- 230000003213 activating effect Effects 0.000 claims description 26
- 238000013473 artificial intelligence Methods 0.000 abstract description 61
- 230000009849 deactivation Effects 0.000 abstract description 16
- 230000004913 activation Effects 0.000 abstract description 11
- 230000006870 function Effects 0.000 description 53
- 230000005540 biological transmission Effects 0.000 description 37
- 238000007726 management method Methods 0.000 description 26
- 238000005516 engineering process Methods 0.000 description 19
- 238000010586 diagram Methods 0.000 description 17
- 238000012544 monitoring process Methods 0.000 description 16
- 238000012545 processing Methods 0.000 description 14
- 230000008093 supporting effect Effects 0.000 description 13
- 239000000969 carrier Substances 0.000 description 10
- 238000005259 measurement Methods 0.000 description 9
- 238000001228 spectrum Methods 0.000 description 9
- 238000001514 detection method Methods 0.000 description 8
- 230000002776 aggregation Effects 0.000 description 7
- 238000004220 aggregation Methods 0.000 description 7
- 230000008569 process Effects 0.000 description 7
- 238000003491 array Methods 0.000 description 6
- 230000003247 decreasing effect Effects 0.000 description 6
- 239000000835 fiber Substances 0.000 description 6
- 230000001976 improved effect Effects 0.000 description 5
- 230000001276 controlling effect Effects 0.000 description 4
- 125000004122 cyclic group Chemical group 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 230000002093 peripheral effect Effects 0.000 description 4
- 230000006399 behavior Effects 0.000 description 3
- 238000011084 recovery Methods 0.000 description 3
- 230000001360 synchronised effect Effects 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 238000012937 correction Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 239000002245 particle Substances 0.000 description 2
- 230000009467 reduction Effects 0.000 description 2
- 238000013468 resource allocation Methods 0.000 description 2
- 238000005070 sampling Methods 0.000 description 2
- 230000003595 spectral effect Effects 0.000 description 2
- 238000010408 sweeping Methods 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000007175 bidirectional communication Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000013480 data collection Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000001066 destructive effect Effects 0.000 description 1
- 230000007613 environmental effect Effects 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 239000011159 matrix material Substances 0.000 description 1
- 230000000116 mitigating effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000012913 prioritisation Methods 0.000 description 1
- 230000001902 propagating effect Effects 0.000 description 1
- 230000001105 regulatory effect Effects 0.000 description 1
- 238000013515 script Methods 0.000 description 1
- 230000011218 segmentation Effects 0.000 description 1
- 230000008054 signal transmission Effects 0.000 description 1
- 238000001774 stimulated Raman spectroscopy Methods 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
- 235000019527 sweetened beverage Nutrition 0.000 description 1
- 230000002123 temporal effect Effects 0.000 description 1
- 238000012549 training Methods 0.000 description 1
- 208000037918 transfusion-transmitted disease Diseases 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
-
- 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 following relates to wireless communications, including logging and signaling of operations for machine learning life-cycle management.
- Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power) .
- Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems.
- 4G systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems
- 5G systems which may be referred to as New Radio (NR) systems.
- a wireless multiple-access communications system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE) .
- UE user equipment
- a network entity may configure a user equipment (UE) to log artificial intelligence (AI) or ML life-cycle management (LCM) operations, together with associated conditions under which the UE performed the LCM operations, and then report the logged information to the network entity.
- the UE may log and report LCM operations for AI/ML models, functionalities, or both (e.g., for model-ID based LCM decisions and functionality-based LCM decisions) .
- LCM decisions may include model or functionality selection, activation, deactivation, switching, and fallback.
- the start and stop time for logging the information may be determined and configured by the network entity.
- the UE may also be configured to report statistics corresponding to the logged information.
- a method for wireless communications at a user equipment may include receiving control signaling indicating a scheme for reporting feedback information about using machine learning models to maintain a wireless communication link, performing one or more operations to activate or deactivate a functionality of at least one machine learning model for maintaining the wireless communication link based on receiving the control signaling, and transmitting, according to the scheme, an operation report including an indication of the one or more operations and one or more conditions corresponding to the one or more operations.
- the apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory.
- the instructions may be executable by the processor to cause the apparatus to receive control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link, perform one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link based on receiving the control signaling, and transmit, according to the scheme, an operation report including an indication of the one or more operations and one or more conditions corresponding to the one or more operations.
- the apparatus may include means for receiving control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link, means for performing one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link based on receiving the control signaling, and means for transmitting, according to the scheme, an operation report including an indication of the one or more operations and one or more conditions corresponding to the one or more operations.
- a non-transitory computer-readable medium storing code for wireless communications at a UE is described.
- the code may include instructions executable by a processor to receive control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link, perform one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link based on receiving the control signaling, and transmit, according to the scheme, an operation report including an indication of the one or more operations and one or more conditions corresponding to the one or more operations.
- Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, via the control signaling, a second indication to include the one or more conditions in the operation report, where transmitting the operation report including the one or more conditions may be based on receiving the second indication.
- Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for logging the one or more operations and the one or more conditions corresponding to the one or more operations at a local memory of the UE and retrieving the one or more operations and the one or more conditions corresponding to the one or more operations from the local memory, where transmitting the operation report may be based on the logging and the retrieving.
- Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, via the control signaling, a second indication of a starting time and an ending time for logging the one or more operations and the one or more conditions corresponding to the one or more operations, where the logging may be based on the starting time and the ending time.
- Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, via the control signaling, a request to provide statistical information associated with the one or more operations and generating the statistical information based on receiving the request, where the operation report includes the statistical information.
- the one or more conditions corresponding to the one or more operations include a UE location at a timing of performing the one or more operations, a zone identifier associated with a location of the UE when performing the one or more operations, a UE mobility state associated with the timing of performing the one or more operations, a reference signal receive power range associated with performing the one or more operations, a blockage event corresponding to the one or more operations, or any combination thereof.
- the operation report includes a radio resource control message or a media access control (MAC) control element (CE) .
- MAC media access control
- CE control element
- Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for activating or deactivating the functionality of the at least one ML model includes switching from a first functionality of the at least one ML model to a second functionality of a second ML model.
- Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for activating or deactivating the functionality includes activating or deactivating a first ML model corresponding to the functionality or switching from the first ML model corresponding to the functionality to a second ML model corresponding to the functionality.
- a method for wireless communications at a network entity may include transmitting control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link with a UE, receiving, according to the scheme, an operation report including an indication of one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link and one or more conditions corresponding to the one or more operations, and communicating with the UE via the wireless communication link based on receiving the operation report.
- the apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory.
- the instructions may be executable by the processor to cause the apparatus to transmit control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link with a UE, receive, according to the scheme, an operation report including an indication of one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link and one or more conditions corresponding to the one or more operations, and communicate with the UE via the wireless communication link based on receiving the operation report.
- the apparatus may include means for transmitting control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link with a UE, means for receiving, according to the scheme, an operation report including an indication of one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link and one or more conditions corresponding to the one or more operations, and means for communicating with the UE via the wireless communication link based on receiving the operation report.
- a non-transitory computer-readable medium storing code for wireless communications at a network entity is described.
- the code may include instructions executable by a processor to transmit control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link with a UE, receive, according to the scheme, an operation report including an indication of one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link and one or more conditions corresponding to the one or more operations, and communicate with the UE via the wireless communication link based on receiving the operation report.
- Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, via the control signaling, a second indication to include the one or more conditions in the operation report, where receiving the operation report including the one or more conditions may be based on transmitting the second indication.
- Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, via the control signaling, a second indication of a starting time and an ending time for logging the one or more operations and the one or more conditions corresponding to the one or more operations, where receiving the operation report including the one or more conditions may be based on transmitting the second indication of the starting time and the ending time.
- Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, via the control signaling, a request to provide statistical information associated with the one or more operations and receiving, via the operation report, the statistical information based on transmitting the request.
- the one or more conditions corresponding to the one or more operations include a UE location at a timing of performing the one or more operations, a zone identifier associated with a location of the UE when performing the one or more operations, a UE mobility state associated with the timing of performing the one or more operations, a reference signal receive power range associated with performing the one or more operations, a blockage event corresponding to the one or more operations, or any combination thereof.
- the operation report includes a radio resource control message or a MAC control element (CE) .
- CE MAC control element
- Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for activating or deactivating the functionality of the at least one ML model includes switching from a first functionality of the at least one ML model to a second functionality of a second ML model.
- Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for activating or deactivating the functionality includes activating or deactivating a first ML model corresponding to the functionality or switching from the first ML model corresponding to the functionality to a second ML model corresponding to the functionality.
- FIG. 1 shows an example of a wireless communications system that supports logging and signaling of operations for machine learning (ML) life-cycle management (LCM) in accordance with one or more aspects of the present disclosure.
- ML machine learning
- LCM life-cycle management
- FIG. 2 shows an example of a wireless communications system that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure.
- FIG. 3 shows an example of a process flow that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure.
- FIGs. 4 and 5 show block diagrams of devices that support logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure.
- FIG. 6 shows a block diagram of a communications manager that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure.
- FIG. 7 shows a diagram of a system including a device that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure.
- FIGs. 8 and 9 show block diagrams of devices that support logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure.
- FIG. 10 shows a block diagram of a communications manager that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure.
- FIG. 11 shows a diagram of a system including a device that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure.
- FIGs. 12 through 15 show flowcharts illustrating methods that support logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure.
- a user equipment may support artificial intelligence (AI) or machine learning (ML) , which the UE may use to perform wireless communications procedures (e.g., beam selection or beam prediction, among other examples) .
- the UE may perform life-cycle management (LCM) operations for a given AI/ML model or functionality (e.g., model or functionality selection, activation, deactivation, switching, and fallback, among other examples) .
- AI/ML functionality or models may change over time, or may be activated or deactivated autonomously by the UE.
- the network entity 105-a may make erroneous resource allocations, or may default to signaling related AI/ML functionalities that are not applicable if the UE 115-a has defaulted to fallback procedures that do not implement AI/ML functionalities or models.
- Such misaligned signaling and techniques may result in inefficient use of system resources, unreliable communications, increased system latency, and decreased user experience.
- a network entity may configure the UE to log LCM operations, together with associated conditions under which the UE performed the LCM operations, and then report the logged information to the network entity.
- the UE may log and report LCM operations for AI/ML models, functionalities, or both (e.g., for model-ID based LCM decisions and functionality-based LCM decisions) .
- LCM decisions may include model or functionality selection, activation, deactivation, switching, and fallback.
- the start and stop time for logging the information may be determined and configured by the network entity.
- the UE may also be configured to report statistics corresponding to the logged information (e.g., instead of or along with raw measurements and data) .
- aspects of the disclosure are initially described in the context of wireless communications systems and process flows. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to logging and signaling of operations for ML LCM.
- FIG. 1 shows an example of a wireless communications system 100 that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure.
- the wireless communications system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130.
- the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.
- LTE Long Term Evolution
- LTE-A LTE-Advanced
- LTE-A Pro LTE-A Pro
- NR New Radio
- the network entities 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may include devices in different forms or having different capabilities.
- a network entity 105 may be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature.
- network entities 105 and UEs 115 may wirelessly communicate via one or more communication links 125 (e.g., a radio frequency (RF) access link) .
- a network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entity 105 may establish one or more communication links 125.
- the coverage area 110 may be an example of a geographic area over which a network entity 105 and a UE 115 may support the communication of signals according to one or more radio access technologies (RATs) .
- RATs radio access technologies
- the UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times.
- the UEs 115 may be devices in different forms or having different capabilities. Some example UEs 115 are illustrated in FIG. 1.
- the UEs 115 described herein may be capable of supporting communications with various types of devices, such as other UEs 115 or network entities 105, as shown in FIG. 1.
- a node of the wireless communications system 100 which may be referred to as a network node, or a wireless node, may be a network entity 105 (e.g., any network entity described herein) , a UE 115 (e.g., any UE described herein) , a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein.
- a node may be a UE 115.
- a node may be a network entity 105.
- a first node may be configured to communicate with a second node or a third node.
- the first node may be a UE 115
- the second node may be a network entity 105
- the third node may be a UE 115.
- the first node may be a UE 115
- the second node may be a network entity 105
- the third node may be a network entity 105.
- the first, second, and third nodes may be different relative to these examples.
- reference to a UE 115, network entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity 105, apparatus, device, computing system, or the like being a node.
- disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.
- network entities 105 may communicate with the core network 130, or with one another, or both.
- network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., in accordance with an S1, N2, N3, or other interface protocol) .
- network entities 105 may communicate with one another via a backhaul communication link 120 (e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network entities 105) or indirectly (e.g., via a core network 130) .
- network entities 105 may communicate with one another via a midhaul communication link 162 (e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (e.g., in accordance with a fronthaul interface protocol) , or any combination thereof.
- the backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link) , one or more wireless links (e.g., a radio link, a wireless optical link) , among other examples or various combinations thereof.
- a UE 115 may communicate with the core network 130 via a communication link 155.
- One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or a giga-NodeB (either of which may be referred to as a gNB) , a 5G NB, a next-generation eNB (ng-eNB) , a Home NodeB, a Home eNodeB, or other suitable terminology) .
- a base station 140 e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or a giga-NodeB (either of which may be
- a network entity 105 may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140) .
- a network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) , which may be configured to utilize a protocol stack that is physically or logically distributed among two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (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 RAN
- vRAN virtualized RAN
- C-RAN cloud RAN
- a network entity 105 may include one or more of a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) 180 system, or any combination thereof.
- An RU 170 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 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (e.g., separate physical locations) .
- one or more network entities 105 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
- the split of functionality between a CU 160, a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170.
- functions e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combinations thereof
- a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack.
- the CU 160 may host upper protocol layer (e.g., layer 3 (L3) , layer 2 (L2) ) functionality and signaling (e.g., Radio Resource Control (RRC) , service data adaption protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) .
- the CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or 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 165 and an RU 170 such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack.
- the DU 165 may support one or multiple different cells (e.g., via one or more RUs 170) .
- a functional split between a CU 160 and a DU 165, or between a DU 165 and an RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170) .
- a CU 160 may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions.
- CU-CP CU control plane
- CU-UP CU user plane
- a CU 160 may be connected to one or more DUs 165 via a midhaul communication link 162 (e.g., F1, F1-c, F1-u) , and a DU 165 may be connected to one or more RUs 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface) .
- a midhaul communication link 162 or a fronthaul communication link 168 may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 105 that are in communication via such communication links.
- infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., to a core network 130) .
- IAB network one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other.
- One or more IAB nodes 104 may be referred to as a donor entity or an IAB donor.
- One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140) .
- the one or more donor network entities 105 may be in communication with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120) .
- IAB nodes 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by DUs 165 of a coupled IAB donor.
- IAB-MT IAB mobile termination
- An IAB-MT may include an independent set of antennas for relay of communications with UEs 115, or may share the same antennas (e.g., of an RU 170) of an IAB node 104 used for access via the DU 165 of the IAB node 104 (e.g., referred to as virtual IAB-MT (vIAB-MT) ) .
- the IAB nodes 104 may include DUs 165 that support communication links with additional entities (e.g., IAB nodes 104, UEs 115) within the relay chain or configuration of the access network (e.g., downstream) .
- one or more components of the disaggregated RAN architecture e.g., one or more IAB nodes 104 or components of IAB nodes 104) may be configured to operate according to the techniques described herein.
- an access network (AN) or RAN may include communications between access nodes (e.g., an IAB donor) , IAB nodes 104, and one or more UEs 115.
- the IAB donor may facilitate connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130) . That is, an IAB donor may refer to a RAN node with a wired or wireless connection to core network 130.
- the IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170) , in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link) .
- IAB donor and IAB nodes 104 may communicate via an F1 interface according to a protocol that defines signaling messages (e.g., an F1 AP protocol) .
- the CU 160 may communicate with the core network via an interface, which may be an example of a portion of backhaul link, and may communicate with other CUs 160 (e.g., a CU 160 associated with an alternative IAB donor) via an Xn-C interface, which may be an example of a portion of a backhaul link.
- An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UEs 115, wireless self-backhauling capabilities) .
- a DU 165 may act as a distributed scheduling node towards child nodes associated with the IAB node 104, and the IAB-MT may act as a scheduled node towards parent nodes associated with the IAB node 104. That is, an IAB donor may be referred to as a parent node in communication with one or more child nodes (e.g., an IAB donor may relay transmissions for UEs through one or more other IAB nodes 104) .
- an IAB node 104 may also be referred to as a parent node or a child node to other IAB nodes 104, depending on the relay chain or configuration of the AN. Therefore, the IAB-MT entity of IAB nodes 104 may provide a Uu interface for a child IAB node 104 to receive signaling from a parent IAB node 104, and the DU interface (e.g., DUs 165) may provide a Uu interface for a parent IAB node 104 to signal to a child IAB node 104 or UE 115.
- the DU interface e.g., DUs 165
- IAB node 104 may be referred to as a parent node that supports communications for a child IAB node, or referred to as a child IAB node associated with an IAB donor, or both.
- the IAB donor may include a CU 160 with a wired or wireless connection (e.g., a backhaul communication link 120) to the core network 130 and may act as parent node to IAB nodes 104.
- the DU 165 of IAB donor may relay transmissions to UEs 115 through IAB nodes 104, or may directly signal transmissions to a UE 115, or both.
- the CU 160 of IAB donor may signal communication link establishment via an F1 interface to IAB nodes 104, and the IAB nodes 104 may schedule transmissions (e.g., transmissions to the UEs 115 relayed from the IAB donor) through the DUs 165. That is, data may be relayed to and from IAB nodes 104 via signaling via an NR Uu interface to MT of the IAB node 104. Communications with IAB node 104 may be scheduled by a DU 165 of IAB donor and communications with IAB node 104 may be scheduled by DU 165 of IAB node 104.
- one or more components of the disaggregated RAN architecture may be configured to support logging and signaling of operations for ML LCM as described herein.
- some operations described as being performed by a UE 115 or a network entity 105 may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., IAB nodes 104, DUs 165, CUs 160, RUs 170, RIC 175, SMO 180) .
- a UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples.
- a UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA) , a tablet computer, a laptop computer, or a personal computer.
- PDA personal digital assistant
- a UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, or vehicles, meters, among other examples.
- WLL wireless local loop
- IoT Internet of Things
- IoE Internet of Everything
- MTC machine type communications
- the UEs 115 described herein may be able to communicate with various types of devices, such as other UEs 115 that may sometimes act as relays as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.
- devices such as other UEs 115 that may sometimes act as relays as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.
- the UEs 115 and the network entities 105 may wirelessly communicate with one another via one or more communication links 125 (e.g., an access link) using resources associated with one or more carriers.
- the term “carrier” may refer to a set of RF spectrum resources having a defined physical layer structure for supporting the communication links 125.
- a carrier used for a communication link 125 may include a portion of a RF spectrum band (e.g., a bandwidth part (BWP) ) that is operated according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR) .
- BWP bandwidth part
- Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information) , control signaling that coordinates operation for the carrier, user data, or other signaling.
- the wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation.
- a UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration.
- Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers.
- Communication between a network entity 105 and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity) of a network entity 105.
- the terms “transmitting, ” “receiving, ” or “communicating, ” when referring to a network entity 105 may refer to any portion of a network entity 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105) .
- a network entity 105 e.g., a base station 140, a CU 160, a DU 165, a RU 170
- a carrier may also have acquisition signaling or control signaling that coordinates operations for other carriers.
- a carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN) ) and may be identified according to a channel raster for discovery by the UEs 115.
- E-UTRA evolved universal mobile telecommunication system terrestrial radio access
- a carrier may be operated in a standalone mode, in which case initial acquisition and connection may be conducted by the UEs 115 via the carrier, or the carrier may be operated in a non-standalone mode, in which case a connection is anchored using a different carrier (e.g., of the same or a different radio access technology) .
- the communication links 125 shown in the wireless communications system 100 may include downlink transmissions (e.g., forward link transmissions) from a network entity 105 to a UE 115, uplink transmissions (e.g., return link transmissions) from a UE 115 to a network entity 105, or both, among other configurations of transmissions.
- Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode) .
- a carrier may be associated with a particular bandwidth of the RF spectrum and, in some examples, the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system 100.
- the carrier bandwidth may be one of a set of bandwidths for carriers of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz) ) .
- Devices of the wireless communications system 100 e.g., the network entities 105, the UEs 115, or both
- the wireless communications system 100 may include network entities 105 or UEs 115 that support concurrent communications using carriers associated with multiple carrier bandwidths.
- each served UE 115 may be configured for operating using portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.
- Signal waveforms transmitted via a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM) ) .
- MCM multi-carrier modulation
- OFDM orthogonal frequency division multiplexing
- DFT-S-OFDM discrete Fourier transform spread OFDM
- a resource element may refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related.
- the quantity of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both) , such that a relatively higher quantity of resource elements (e.g., in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication.
- a wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam) , and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.
- One or more numerologies for a carrier may be supported, and a numerology may include a subcarrier spacing ( ⁇ f) and a cyclic prefix.
- a carrier may be divided into one or more BWPs having the same or different numerologies.
- a UE 115 may be configured with multiple BWPs.
- a single BWP for a carrier may be active at a given time and communications for the UE 115 may be restricted to one or more active BWPs.
- Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms) ) .
- Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023) .
- SFN system frame number
- Each frame may include multiple consecutively-numbered subframes or slots, and each subframe or slot may have the same duration.
- a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a quantity of slots.
- each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing.
- Each slot may include a quantity of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period) .
- a slot may further be divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f ) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.
- a subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI) .
- TTI duration e.g., a quantity of symbol periods in a TTI
- the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs) ) .
- Physical channels may be multiplexed for communication using a carrier according to various techniques.
- a physical control channel and a physical data channel may be multiplexed for signaling via a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques.
- a control region e.g., a control resource set (CORESET)
- CORESET control resource set
- One or more control regions may be configured for a set of the UEs 115.
- one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner.
- An aggregation level for a control channel candidate may refer to an amount of control channel resources (e.g., control channel elements (CCEs) ) associated with encoded information for a control information format having a given payload size.
- Search space sets may include common search space sets configured for sending control information to multiple UEs 115 and UE-specific search space sets for sending control information to a specific UE 115.
- a network entity 105 may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or any combination thereof.
- the term “cell” may refer to a logical communication entity used for communication with a network entity 105 (e.g., using a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID) , a virtual cell identifier (VCID) , or others) .
- a cell also may refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) over which the logical communication entity operates.
- Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the network entity 105.
- a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with coverage areas 110, among other examples.
- a macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by the UEs 115 with service subscriptions with the network provider supporting the macro cell.
- a small cell may be associated with a lower-powered network entity 105 (e.g., a lower-powered base station 140) , as compared with a macro cell, and a small cell may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells.
- Small cells may provide unrestricted access to the UEs 115 with service subscriptions with the network provider or may provide restricted access to the UEs 115 having an association with the small cell (e.g., the UEs 115 in a closed subscriber group (CSG) , the UEs 115 associated with users in a home or office) .
- a network entity 105 may support one or multiple cells and may also support communications via the one or more cells using one or multiple component carriers.
- a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT) , enhanced mobile broadband (eMBB) ) that may provide access for different types of devices.
- protocol types e.g., MTC, narrowband IoT (NB-IoT) , enhanced mobile broadband (eMBB)
- NB-IoT narrowband IoT
- eMBB enhanced mobile broadband
- a network entity 105 may be movable and therefore provide communication coverage for a moving coverage area 110.
- different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105.
- the overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105.
- the wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.
- the wireless communications system 100 may support synchronous or asynchronous operation.
- network entities 105 e.g., base stations 140
- network entities 105 may have different frame timings, and transmissions from different network entities 105 may, in some examples, not be aligned in time.
- the techniques described herein may be used for either synchronous or asynchronous operations.
- Some UEs 115 may be low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication) .
- M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a network entity 105 (e.g., a base station 140) without human intervention.
- M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that uses the information or presents the information to humans interacting with the application program.
- Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.
- Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., a mode that supports one-way communication via transmission or reception, but not transmission and reception concurrently) .
- half-duplex communications may be performed at a reduced peak rate.
- Other power conservation techniques for the UEs 115 include entering a power saving deep sleep mode when not engaging in active communications, operating using a limited bandwidth (e.g., according to narrowband communications) , or a combination of these techniques.
- some UEs 115 may be configured for operation using a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs) ) within a carrier, within a guard-band of a carrier, or outside of a carrier.
- a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs) ) within a carrier, within a guard-band of a carrier, or outside of a carrier.
- the wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof.
- the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC) .
- the UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions.
- Ultra-reliable communications may include private communication or group communication and may be supported by one or more services such as push-to-talk, video, or data.
- Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications.
- the terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.
- a UE 115 may be configured to support communicating directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., in accordance with a peer-to-peer (P2P) , D2D, or sidelink protocol) .
- D2D device-to-device
- P2P peer-to-peer
- one or more UEs 115 of a group that are performing D2D communications may be within the coverage area 110 of a network entity 105 (e.g., a base station 140, an RU 170) , which may support aspects of such D2D communications being configured by (e.g., scheduled by) the network entity 105.
- one or more UEs 115 of such a group may be outside the coverage area 110 of a network entity 105 or may be otherwise unable to or not configured to receive transmissions from a network entity 105.
- groups of the UEs 115 communicating via D2D communications may support a one-to-many (1: M) system in which each UE 115 transmits to each of the other UEs 115 in the group.
- a network entity 105 may facilitate the scheduling of resources for D2D communications.
- D2D communications may be carried out between the UEs 115 without an involvement of a network entity 105.
- a D2D communication link 135 may be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UEs 115) .
- vehicles may communicate using vehicle-to-everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these.
- V2X vehicle-to-everything
- V2V vehicle-to-vehicle
- a vehicle may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information relevant to a V2X system.
- vehicles in a V2X system may communicate with roadside infrastructure, such as roadside units, or with the network via one or more network nodes (e.g., network entities 105, base stations 140, RUs 170) using vehicle-to-network (V2N) communications, or with both.
- roadside infrastructure such as roadside units
- network nodes e.g., network entities 105, base stations 140, RUs 170
- V2N vehicle-to-network
- the core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions.
- the core network 130 may be an evolved packet core (EPC) or 5G core (5GC) , which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management function (AMF) ) and at least one 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 function
- S-GW serving gateway
- PDN Packet Data Network gateway
- UPF user plane function
- the control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the network entities 105 (e.g., base stations 140) associated with the core network 130.
- NAS non-access stratum
- User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions.
- the user plane entity may be connected to IP services 150 for one or more network operators.
- the IP services 150 may include access to the Internet, Intranet (s) , an IP Multimedia Subsystem (IMS) , or a Packet-Switched Streaming Service.
- IMS IP Multimedia Subsystem
- the wireless communications system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz) .
- the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length.
- UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to communications using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.
- HF high frequency
- VHF very high frequency
- the wireless communications system 100 may also operate using a super high frequency (SHF) region, which may be in the range of 3 GHz to 30 GHz, also known as the centimeter band, or using an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) , also known as the millimeter band.
- SHF super high frequency
- EHF extremely high frequency
- the wireless communications system 100 may support millimeter wave (mmW) communications between the UEs 115 and the network entities 105 (e.g., base stations 140, RUs 170) , and EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas.
- mmW millimeter wave
- such techniques may facilitate using antenna arrays within a device.
- EHF transmissions may be subject to even greater attenuation and shorter range than SHF or UHF transmissions.
- the techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country or regulating body.
- the wireless communications system 100 may utilize both licensed and unlicensed RF spectrum bands.
- the wireless communications system 100 may employ License Assisted Access (LAA) , LTE-Unlicensed (LTE-U) radio access technology, or NR technology using an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band.
- LAA License Assisted Access
- LTE-U LTE-Unlicensed
- NR NR technology
- an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band.
- devices such as the network entities 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance.
- operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using a licensed band (e.g., LAA) .
- Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.
- a network entity 105 e.g., a base station 140, an RU 170
- a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming.
- the antennas of a network entity 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming.
- one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower.
- antennas or antenna arrays associated with a network entity 105 may be located at diverse geographic locations.
- a network entity 105 may include an antenna array with a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming of communications with a UE 115.
- a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations.
- an antenna panel may support RF beamforming for a signal transmitted via an antenna port.
- the network entities 105 or the UEs 115 may use MIMO communications to exploit multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers.
- Such techniques may be referred to as spatial multiplexing.
- the multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas. Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas.
- Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords) .
- Different spatial layers may be associated with different antenna ports used for channel measurement and reporting.
- MIMO techniques include single-user MIMO (SU-MIMO) , for which multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO) , for which multiple spatial layers are transmitted to multiple devices.
- SU-MIMO single-user MIMO
- Beamforming which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device.
- Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating along particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference.
- the adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device.
- the adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation) .
- a network entity 105 or a UE 115 may use beam sweeping techniques as part of beamforming operations.
- a network entity 105 e.g., a base station 140, an RU 170
- Some signals e.g., synchronization signals, reference signals, beam selection signals, or other control signals
- the network entity 105 may transmit a signal according to different beamforming weight sets associated with different directions of transmission.
- Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as a network entity 105, or by a receiving device, such as a UE 115) a beam direction for later transmission or reception by the network entity 105.
- a transmitting device such as a network entity 105
- a receiving device such as a UE 115
- Some signals may be transmitted by transmitting device (e.g., a transmitting network entity 105, a transmitting UE 115) along a single beam direction (e.g., a direction associated with the receiving device, such as a receiving network entity 105 or a receiving UE 115) .
- a single beam direction e.g., a direction associated with the receiving device, such as a receiving network entity 105 or a receiving UE 115
- the beam direction associated with transmissions along a single beam direction may be determined based on a signal that was transmitted along one or more beam directions.
- a UE 115 may receive one or more of the signals transmitted by the network entity 105 along different directions and may report to the network entity 105 an indication of the signal that the UE 115 received with a highest signal quality or an otherwise acceptable signal quality.
- transmissions by a device may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from a network entity 105 to a UE 115) .
- the UE 115 may report feedback that indicates precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more sub-bands.
- the network entity 105 may transmit a reference signal (e.g., a cell-specific reference signal (CRS) , a channel state information reference signal (CSI-RS) ) , which may be precoded or unprecoded.
- a reference signal e.g., a cell-specific reference signal (CRS) , a channel state information reference signal (CSI-RS)
- the UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook) .
- PMI precoding matrix indicator
- codebook-based feedback e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook
- these techniques are described with reference to signals transmitted along one or more directions by a network entity 105 (e.g., a base station 140, an RU 170)
- a UE 115 may employ similar techniques for transmitting signals multiple times along different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE 115) or for transmitting a signal along a single direction (e.g., for transmitting data to a receiving device) .
- a receiving device may perform reception operations in accordance with multiple receive configurations (e.g., directional listening) when receiving various signals from a receiving device (e.g., a network entity 105) , such as synchronization signals, reference signals, beam selection signals, or other control signals.
- a receiving device e.g., a network entity 105
- signals such as synchronization signals, reference signals, beam selection signals, or other control signals.
- a receiving device may perform reception in accordance with multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as “listening” according to different receive configurations or receive directions.
- a receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal) .
- the single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR) , or otherwise acceptable signal quality based on listening according to multiple beam directions) .
- receive configuration directions e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR) , or otherwise acceptable signal quality based on listening according to multiple beam directions
- the wireless communications system 100 may be a packet-based network that operates according to a layered protocol stack.
- communications at the bearer or PDCP layer may be IP-based.
- An RLC layer may perform packet segmentation and reassembly to communicate via logical channels.
- a MAC layer may perform priority handling and multiplexing of logical channels into transport channels.
- the MAC layer also may implement error detection techniques, error correction techniques, or both to support retransmissions to improve link efficiency.
- an RRC layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a network entity 105 or a core network 130 supporting radio bearers for user plane data.
- a PHY layer may map transport channels to physical channels.
- the UEs 115 and the network entities 105 may support retransmissions of data to increase the likelihood that data is received successfully.
- Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly via a communication link (e.g., a communication link 125, a D2D communication link 135) .
- HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC) ) , forward error correction (FEC) , and retransmission (e.g., automatic repeat request (ARQ) ) .
- FEC forward error correction
- ARQ automatic repeat request
- HARQ may improve throughput at the MAC layer in poor radio conditions (e.g., low signal-to-noise conditions) .
- a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific slot for data received via a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.
- a network entity 105 may configure the UE 115 to log LCM operations, together with associated conditions under which the UE performed the LCM operations, and then report the logged information to the network entity.
- the UE 115 may log and report LCM operations for AI/ML models, functionalities, or both (e.g., for model-ID based LCM decisions and functionality-based LCM decisions) .
- LCM decisions may include model or functionality selection, activation, deactivation, switching, and fallback.
- the start and stop time for logging the information may be determined and configured by the network entity.
- the UE 115 may also be configured to report statistics corresponding to the logged information (e.g., instead of or along with raw measurements and data) .
- FIG. 2 shows an example of a wireless communications system 200 that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure.
- the wireless communications system 200 may implement aspects of, or be implemented by aspects of, the wireless communications system 100.
- the wireless communications system 200 may include a network entity 105-a and a UE 115-a, which may be examples of corresponding devices described with reference to FIG. 1.
- the UE 115-a and the network entity 105-a may communicate with each other via a wireless communication link 205.
- the UE 115-a may enter a radio resource control (RRC) idle state or RRC inactive state.
- RRC radio resource control
- the UE 115-a may perform initial access (e.g., a synchronization signal block (SSB) beam (e.g., wide beam) sweeping) .
- SSB synchronization signal block
- the UE 115-a may successfully perform initial access, and ay perform beam management in an RRC connected state.
- Beam management may include beam prediction to identify and utilize beams without experience a beam failure or a link failure via the selected beams. If the UE experience a beam failure detection based on one or more measurements, the UE may perform beam failure recovery.
- Beam management in an RRC connected state may include receiving one or more reference signals for measurement and reporting (e.g., SSBs, CSI-RSs, SRSs, etc. ) , channel quality reporting (e.g., reference signal receive power (RSRP) reporting) , and TCI state configuration and indications (e.g., beam selection, configuration, and use) .
- Beam management may also include SINR reporting, overhead and latency reduction e.g., CC group beam updates, faster uplink beam updates, etc. ) .
- beam management may include efficiency enhancements, including unified TCI states, layer 1 or layer 2 centric mobility, dynamic TCI updates, uplink multi-panel use and selection, MPE mitigation, or the like. Beam management may also be applied to multi-transmission reception point (mTRP) scenarios.
- mTRP multi-transmission reception point
- the UE 115-a may perform beam failure detection, and beam failure recovery for various cells (e.g., primary cell (PCell, primary secondary cell (PSCell) , which may include beam failure detection via beam failure detection reference signals and physical downlink control channel (PDCCH) block error rate (BLER) as described in greater detail with reference to FIG. 3.
- PCell primary cell
- PSCell primary secondary cell
- PDCCH physical downlink control channel
- BLER block error rate
- SCell secondary cell
- the UE may perform beam failure detention similar to such procedure for an SCell.
- the UE 115-a may transmit a scheduling request (SR) , or a media access control (MAC) control element (CE) based on the beam failure request for the SCell.
- SR scheduling request
- MAC media access control
- CE media access control element
- the UE 115-a may support AI or ML procedures (AI/ML) for air-interface corresponding to various target use cases regarding aspects of communications such as performance, complexity, etc.
- use cases may include beam management (e.g., beam prediction in time and/or spatial domain for overhead and latency reduction, beam selection accuracy improvement) among other examples.
- AI/ML approaches to various use cases or sub use cases may be diverse enough to support various procedures and collaborations between the UE 115-a and the network entity 105-a.
- AI/ML models may support common and specific characteristics in various frameworks, including lifecycle management of AI/ML models (e.g., model training, model deployment, model interference, model monitoring, and model updating, among other examples) .
- the UE 115-a and the network entity 105-a may perform beam management or beam selection using AI/ML models or functionalities.
- the UE 115-a may support a first case (e.g., beam management (BM) case 1) and a second case (BM case 2) .
- BM case 1 the UE 115-a may perform spatial domain downlink beam prediction for a first set of beams (e.g., set A) based on measurement results of a second set of beams (e.g., set B) .
- the UE 115-a may perform temporal domain downlink beam prediction for a first set of beams (e.g., set A) based on measurement results of a second set of beams (e.g., set B) .
- Set A and Set B may be in the same frequency range, or different frequency range.
- the UE 115-a may perform actual measurement for one or more beams (e.g., set B) , and may use AI/ML models to predict a second set of beams (e.g., set A) for communications via the communication link 205.
- the UE 115-a may perform one or more LCM operations (e.g., decisions) for an AI/ML model or functionality.
- LCM operations may be based at least in part on the basis that an AIML model has a model identifier (ID) with associated information, or model functionality at least for some AI/ML operations/procedures.
- Model IDs may be associated with information and/or model functionality. Usage of model IDs with associated information or model functionality may be based on LCM procedures.
- indications of activation of LCM operations may be exchanged between the network entity 105-a and the UE 115-a.
- LCM operations e.g., activation, deactivation, switching, or fallback behaviors for a given AI/ML
- the UE 115-a and the network entity 105-a may indicate LCM operations such as model selection, activation, deactivation, switching, of fallback procedures, based on individual model IDs.
- LCM methodologies may include functionality-based LCM operations.
- the network entity 105-a may be aware of (e.g., may have access to information regarding) AI/ML functionality at the UE 115-a via UE capability reporting.
- the UE 115-a may report its capability to support one or more AI/ML functionalities (e.g., beam prediction, beam management, channel prediction, mobility operations, among other examples) .
- Each AI/ML functionality may correspond to a reference signal configuration from the network entity, and one or more AI/ML IDs (e.g., a single AI/ML model with a first AI/ML model ID may correspond to a low-doppler beam prediction AI/ML functionality, and a second AI/ML model with a second AI/ML model ID may correspond to a high-doppler beam prediction of the same AI/ML functionality) .
- the network entity 105-a may control AI/ML functionality at the UE 115-a.
- the network entity 105-a may instruct the UE 115-a to perform one or more LCM operations (e.g., activate, deactivate, switch, default, among other examples) for a reported AI/ML functionality.
- the controlling may refer to functionality selection, activation, deactivation, switching, falling back, or monitoring, among other examples.
- LCM methodologies may include model ID based LCM operations.
- AI/ML models are registered at the network entity 105 with mode IDs.
- the network entity 105-a may configure, or the UE 115-a may report, an indication of one or more model IDs supported by the UE 115-a.
- the model IDs may or may not correspond to AI/ML functionalities.
- the network entity 105-a may be aware of (e.g., have access to information regarding) the model IDs supported by the UE 115-a based on capability signaling from the UE 115-a (e.g., indicating which AI/ML model IDs the UE 115-a supports) .
- the UE may have one AI/ML model for a given AI/ML functionality, or may have multiple AI/ML models for the functionality.
- Functionalities may be indicated via identifiers, or by name or term, or may be defined via a table, bitmap, or other indication (e.g., and may be indicated via signaling or defined in one or more standards, or a combination thereof) .
- model ID based and functionality based LCM management methodologies may result in implications in terms of phases of ML workflow, and including data collection, interference, and model monitoring, as described herein.
- the network entity 105-a or the UE 115-a may initiate or determine the LCM operations
- the network entity 105-a may determine LCM operations (e.g., may determine whether the UE 115-a is to activate or deactivate a ML model or functionality) .
- the network entity 105-a may perform network-initiated LCM operations, or the UE 115-a may perform UE-initiated LCM decisions (e.g., may request the LCM operation, and the network entity 105-a may transmit an acknowledgment or approval indication of the requested LCM decision) .
- the decision may be performed by the UE 115-a.
- the UE 115-a may perform event-triggered LCM decisions (e.g., as configured by the network entity 105-a) , and the UE 115-a may report the LCM decision to the network entity 105-a.
- the UE 115-a may perform anonymous LCM decisions, reported to the network entity 105-a, or may perform anonymous LCM decisions, and may not report the decision to the network entity 105-a.
- the UE 115-a may perform LCM decisions (e.g., may activate, deactivate, switch between, etc., one or more AI/ML models, or functionalities) .
- LCM decisions e.g., may activate, deactivate, switch between, etc., one or more AI/ML models, or functionalities
- the network entity 105-a may make erroneous resource allocations, or may default to signaling related AI/ML functionalities that are not applicable if the UE 115-a has defaulted to fallback procedures that do not implement AI/ML functionalities or models.
- Such misaligned signaling and techniques may result in inefficient use of system resources, unreliable communications, increased system latency, and decreased user experience.
- the network entity 105-a may configure (e.g., via the configuration information 210) the UE 115-a to log LCM decisions together with associated conditions, and then report the logged data to the network entity 105-a (e.g., via the report 215) .
- the UE 115-a may log and report LCM decisions for AI/ML models, functionalities, or both (e.g., for model-ID based LCM decisions and functionality-based LCM decisions) .
- LCM decisions may include model or functionality selection, activation, deactivation, switching, and fallback.
- the network entity 105-a may be configured to use the LCM decisions reported by the UE 115-a to improve its configurations and signaling to the UE 115-a and other UEs.
- the start and stop time for logging the information may be determined and configured by the network entity 105-a.
- the network entity 105-a may configure the UE 115-a (e.g., via the configuration information 210) with a time window, time duration, or an initiation time and expiration time, during which the UE 115-a is to log any LCM decisions and the corresponding conditions under which the LCM decisions was taken.
- the UE 115-a may report (e.g., transmit the report 215) some or all of the logged LCM decisions and corresponding conditions for each LCM decision.
- the network entity 105-a may also configure the UE 115-a to perform one or more additional operations on the logged information before reporting.
- the UE 115-a may compute one or more statistics related to the logged information (e.g., which may reduce signaling overhead if the UE 115-a is configured to report statistics instead of raw data or raw measurements) .
- the conditions logged by the UE 115-a and reported in the report 215 may include a UE location (e.g. at the time of the LCM decision) .
- the UE 115-a may log the location associated with the LCM decision and then report the log to network entity 105-a.
- Such reporting configurations may support reporting of relevant information without exposing user privacy information (e.g., real-time UE locations may not be shared, only logged locations over a period of time may be shared in the report 215) .
- the conditions logged by the UE 115-a and reported in the report 215 may include a zone ID indicating location information corresponding to the LCM decision. For example, upon each monitoring decision, the UE 115-a may log the associated zone ID. Such information may be helpful at the network entity 105-a (e.g., the network entity 105-a may deduce that certain zone IDs are more susceptible to AI/ML model/functionality deactivation) . For instance, the network entity 105-a may determine that zone IDs closer to cell edge are more susceptible to AI/ML model/functionality deactivation and may use this information in the future.
- the conditions logged by the UE 115-a and reported in the report 215 may include a UE mobility state.
- Such information may include information about quantized UE speed and may provide the network entity 105-a useful information about which mobility conditions may lead to more AI/ML model/functionality deactivations.
- the conditions logged by the UE 115-a and reported in the report 215 may include an RSRP range.
- an AI/ML model or functionality may not be performing well and may be deactivated. Logging this information may give the network entity 105-a more visibility into the non-applicable conditions for AI/ML model/functionality.
- the conditions logged by the UE 115-a and reported in the report 215 may include a time of day at which the UE 115-a made the LCM decision. For example, logging information about time of day (e.g., in urban environments) may be useful. For instance, during daytime a given venue may be crowded and hence more susceptible to beam blockage and AI/ML model or functionality deactivation.
- the conditions logged by the UE 115-a and reported in the report 215 may include a blockage event.
- model deactivation at the UE 115-a is a result of beam failure detection, this may be logged and reported to the network entity 105-a.
- the UE 115-a may report that out of a total quantity (e.g., 100) of AI/ML model or functionality deactivations during the logging period, a quantity or percentage (e.g., 40%) were due to beam failure or detected blockages.
- the UE 115-a may include, in the report 215, statistical information related to the LCM decisions, accompanied by the associated conditions, as opposed to the real-time indications of LCM decisions, resulting in overhead savings.
- the report 215 may include the logged information.
- the report 215 may be a single MAC-CE message or a single RRC message, or may be multiple MAC-CE message or multiple RRC messages, or any combination thereof.
- FIG. 3 shows an example of a process flow 300 that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure.
- the process flow may implement aspects of, or be implemented by aspects of, the wireless communications system 100 and the wireless communications system 200.
- the process flow may include a UE 115-b and a network entity 105-a, which may be examples of corresponding devices described with reference to FIGs 1-2.
- the UE 115-b may receive (e.g., from the network entity 105-b) , control signaling indicating a scheme for reporting feedback information about using ML models or ML functionality to maintain a wireless communication link.
- the control signaling may be an example of the configuration information described with reference to FIG. 2.
- the UE 115-b may perform one or more operations (e.g., LCM decisions or operations, such as to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link) based at least in part on receiving the control signaling at 305.
- the control signaling may include an indication (e.g., an instruction) to include the one or more conditions in an operation report transmitted at 320.
- the conditions may include one or more current parameter values or scenarios in which the UE 115-b performs a given LCM operation.
- the one or more operations may include activating an AI/ML model or functionality, deactivating an AI/ML model or functionality, switching from a first AI/ML model or functionality to a second AI/ML model or functionality, switching to a default AI/ML model or functionality or to a default behavior that does not rely on AI/ML models or functionalities, or any combination thereof, among other examples.
- the conditions corresponding to a given LCM operation may include a UE location at a timing of performing the one or more operations, a zone ID associated with a location of the UE 115-b when performing the one or more operations, a UE mobility state associated with the timing of performing the one or more operations, an RSRP range associated with performing the one or more operations, a blockage event corresponding to the one or more operations, or any combination thereof.
- the UE 115-b may log the one or more operations and the one or more conditions corresponding to the one or more operations at a local memory of the UE 115-b. The UE 115-b may then retrieve the one or more operations and the one or more conditions corresponding to the one or more operations from the local memory, and include the retrieved operations and conditions in the operation report at 320.
- control signaling at 305 may include an indication of a starting time and an ending time for logging the one or more operations and the one or more conditions corresponding to the one or more operations, and the UE 115-b may log the operations and conditions at 315 between the starting time and ending time.
- control signaling at 305 may include a request (e.g., an instruction) to provide statistical information associated with the one or more operations in the operation report at 320.
- the UE 115-b may generate the statistical information based at least in part on receiving the request, and may include the generated statistical information in the operation report at 320.
- the UE 115-b may transmit the operation report.
- the operation report may include the logged operations, and the conditions correspond to each logged operation, the statistical information corresponding to logged information, or any combination thereof.
- the report may be a MAC-CE message, or an RRC message, among other examples.
- FIG. 4 shows a block diagram 400 of a device 405 that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure.
- the device 405 may be an example of aspects of a UE 115 as described herein.
- the device 405 may include a receiver 410, a transmitter 415, and a communications manager 420.
- the device 405 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
- the receiver 410 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to logging and signaling of operations for ML LCM) . Information may be passed on to other components of the device 405.
- the receiver 410 may utilize a single antenna or a set of multiple antennas.
- the transmitter 415 may provide a means for transmitting signals generated by other components of the device 405.
- the transmitter 415 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to logging and signaling of operations for ML LCM) .
- the transmitter 415 may be co-located with a receiver 410 in a transceiver module.
- the transmitter 415 may utilize a single antenna or a set of multiple antennas.
- the communications manager 420, the receiver 410, the transmitter 415, or various combinations thereof or various components thereof may be examples of means for performing various aspects of logging and signaling of operations for ML LCM as described herein.
- the communications manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may support a method for performing one or more of the functions described herein.
- the communications manager 420, the receiver 410, the transmitter 415, 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) , a central processing unit (CPU) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, 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.
- DSP digital signal processor
- CPU central processing unit
- ASIC application-specific integrated circuit
- FPGA field-programmable gate array
- a processor and memory coupled with the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory) .
- the communications manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure) .
- code e.g., as communications management software or firmware
- the functions of the communications manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a
- the communications manager 420 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 410, the transmitter 415, or both.
- the communications manager 420 may receive information from the receiver 410, send information to the transmitter 415, or be integrated in combination with the receiver 410, the transmitter 415, or both to obtain information, output information, or perform various other operations as described herein.
- the communications manager 420 may support wireless communications at a UE in accordance with examples as disclosed herein.
- the communications manager 420 is capable of, configured to, or operable to support a means for receiving control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link.
- the communications manager 420 is capable of, configured to, or operable to support a means for performing one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link based on receiving the control signaling.
- the communications manager 420 is capable of, configured to, or operable to support a means for transmitting, according to the scheme, an operation report including an indication of the one or more operations and one or more conditions corresponding to the one or more operations.
- the device 405 e.g., a processor controlling or otherwise coupled with the receiver 410, the transmitter 415, the communications manager 420, or a combination thereof
- the device 405 may support techniques for logging and reporting LCM operations and corresponding conditions, resulting in more efficient use of system resources, increased reliability of communications, decreased system latency, and improved user experience.
- FIG. 5 shows a block diagram 500 of a device 505 that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure.
- the device 505 may be an example of aspects of a device 405 or a UE 115 as described herein.
- the device 505 may include a receiver 510, a transmitter 515, and a communications manager 520.
- the device 505 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
- the receiver 510 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to logging and signaling of operations for ML LCM) . Information may be passed on to other components of the device 505.
- the receiver 510 may utilize a single antenna or a set of multiple antennas.
- the transmitter 515 may provide a means for transmitting signals generated by other components of the device 505.
- the transmitter 515 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to logging and signaling of operations for ML LCM) .
- the transmitter 515 may be co-located with a receiver 510 in a transceiver module.
- the transmitter 515 may utilize a single antenna or a set of multiple antennas.
- the device 505, or various components thereof may be an example of means for performing various aspects of logging and signaling of operations for ML LCM as described herein.
- the communications manager 520 may include an ML model reporting manager 525, an LCM operation manager 530, an operation report manager 535, or any combination thereof.
- the communications manager 520 may be an example of aspects of a communications manager 420 as described herein.
- the communications manager 520, or various components thereof may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 510, the transmitter 515, or both.
- the communications manager 520 may receive information from the receiver 510, send information to the transmitter 515, or be integrated in combination with the receiver 510, the transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.
- the communications manager 520 may support wireless communications at a UE in accordance with examples as disclosed herein.
- the ML model reporting manager 525 is capable of, configured to, or operable to support a means for receiving control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link.
- the LCM operation manager 530 is capable of, configured to, or operable to support a means for performing one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link based on receiving the control signaling.
- the operation report manager 535 is capable of, configured to, or operable to support a means for transmitting, according to the scheme, an operation report including an indication of the one or more operations and one or more conditions corresponding to the one or more operations.
- FIG. 6 shows a block diagram 600 of a communications manager 620 that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure.
- the communications manager 620 may be an example of aspects of a communications manager 420, a communications manager 520, or both, as described herein.
- the communications manager 620, or various components thereof, may be an example of means for performing various aspects of logging and signaling of operations for ML LCM as described herein.
- the communications manager 620 may include an ML model reporting manager 625, an LCM operation manager 630, an operation report manager 635, an operation condition manager 640, a logging manager 645, a statistical information manager 650, or any combination thereof.
- Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses) .
- the communications manager 620 may support wireless communications at a UE in accordance with examples as disclosed herein.
- the ML model reporting manager 625 is capable of, configured to, or operable to support a means for receiving control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link.
- the LCM operation manager 630 is capable of, configured to, or operable to support a means for performing one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link based on receiving the control signaling.
- the operation report manager 635 is capable of, configured to, or operable to support a means for transmitting, according to the scheme, an operation report including an indication of the one or more operations and one or more conditions corresponding to the one or more operations.
- the operation condition manager 640 is capable of, configured to, or operable to support a means for receiving, via the control signaling, a second indication to include the one or more conditions in the operation report, where transmitting the operation report including the one or more conditions is based on receiving the second indication.
- the logging manager 645 is capable of, configured to, or operable to support a means for logging the one or more operations and the one or more conditions corresponding to the one or more operations at a local memory of the UE. In some examples, the logging manager 645 is capable of, configured to, or operable to support a means for retrieving the one or more operations and the one or more conditions corresponding to the one or more operations from the local memory, where transmitting the operation report is based on the logging and the retrieving.
- the logging manager 645 is capable of, configured to, or operable to support a means for receiving, via the control signaling, a second indication of a starting time and an ending time for logging the one or more operations and the one or more conditions corresponding to the one or more operations, where the logging is based on the starting time and the ending time.
- the statistical information manager 650 is capable of, configured to, or operable to support a means for receiving, via the control signaling, a request to provide statistical information associated with the one or more operations. In some examples, the statistical information manager 650 is capable of, configured to, or operable to support a means for generating the statistical information based on receiving the request, where the operation report includes the statistical information.
- the one or more conditions corresponding to the one or more operations include a UE location at a timing of performing the one or more operations, a zone identifier associated with a location of the UE when performing the one or more operations, a UE mobility state associated with the timing of performing the one or more operations, a reference signal receive power range associated with performing the one or more operations, a blockage event corresponding to the one or more operations, or any combination thereof.
- the operation report includes a radio resource control message or a MAC control element (CE) .
- CE MAC control element
- activating or deactivating the functionality of the at least one ML model includes switching from a first functionality of the at least one ML model to a second functionality of a second ML model.
- activating or deactivating the functionality includes activating or deactivating a first ML model corresponding to the functionality or switching from the first ML model corresponding to the functionality to a second ML model corresponding to the functionality.
- FIG. 7 shows a diagram of a system 700 including a device 705 that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure.
- the device 705 may be an example of or include the components of a device 405, a device 505, or a UE 115 as described herein.
- the device 705 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof.
- the device 705 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 720, an input/output (I/O) controller 710, a transceiver 715, an antenna 725, a memory 730, code 735, and a processor 740. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 745) .
- a bus 745 e.g., a bus 745
- the I/O controller 710 may manage input and output signals for the device 705.
- the I/O controller 710 may also manage peripherals not integrated into the device 705.
- the I/O controller 710 may represent a physical connection or port to an external peripheral.
- the I/O controller 710 may utilize an operating system such as or another known operating system.
- the I/O controller 710 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device.
- the I/O controller 710 may be implemented as part of a processor, such as the processor 740.
- a user may interact with the device 705 via the I/O controller 710 or via hardware components controlled by the I/O controller 710.
- the device 705 may include a single antenna 725. However, in some other cases, the device 705 may have more than one antenna 725, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
- the transceiver 715 may communicate bi-directionally, via the one or more antennas 725, wired, or wireless links as described herein.
- the transceiver 715 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
- the transceiver 715 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 725 for transmission, and to demodulate packets received from the one or more antennas 725.
- the transceiver 715 may be an example of a transmitter 415, a transmitter 515, a receiver 410, a receiver 510, or any combination thereof or component thereof, as described herein.
- the memory 730 may include random access memory (RAM) and read-only memory (ROM) .
- the memory 730 may store computer-readable, computer-executable code 735 including instructions that, when executed by the processor 740, cause the device 705 to perform various functions described herein.
- the code 735 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory.
- the code 735 may not be directly executable by the processor 740 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
- the memory 730 may contain, 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 processor 740 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 740 may be configured to operate a memory array using a memory controller.
- a memory controller may be integrated into the processor 740.
- the processor 740 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 730) to cause the device 705 to perform various functions (e.g., functions or tasks supporting logging and signaling of operations for ML LCM) .
- the device 705 or a component of the device 705 may include a processor 740 and memory 730 coupled with or to the processor 740, the processor 740 and memory 730 configured to perform various functions described herein.
- the communications manager 720 may support wireless communications at a UE in accordance with examples as disclosed herein.
- the communications manager 720 is capable of, configured to, or operable to support a means for receiving control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link.
- the communications manager 720 is capable of, configured to, or operable to support a means for performing one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link based on receiving the control signaling.
- the communications manager 720 is capable of, configured to, or operable to support a means for transmitting, according to the scheme, an operation report including an indication of the one or more operations and one or more conditions corresponding to the one or more operations.
- the device 705 may support techniques for logging and reporting LCM operations and corresponding conditions, resulting in more efficient use of system resources, increased reliability of communications, decreased system latency, and improved user experience.
- the communications manager 720 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 715, the one or more antennas 725, or any combination thereof.
- the communications manager 720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 720 may be supported by or performed by the processor 740, the memory 730, the code 735, or any combination thereof.
- the code 735 may include instructions executable by the processor 740 to cause the device 705 to perform various aspects of logging and signaling of operations for ML LCM as described herein, or the processor 740 and the memory 730 may be otherwise configured to perform or support such operations.
- FIG. 8 shows a block diagram 800 of a device 805 that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure.
- the device 805 may be an example of aspects of a network entity 105 as described herein.
- the device 805 may include a receiver 810, a transmitter 815, and a communications manager 820.
- the device 805 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
- the receiver 810 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) .
- Information may be passed on to other components of the device 805.
- the receiver 810 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 810 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
- the transmitter 815 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 805.
- the transmitter 815 may output information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) .
- the transmitter 815 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 815 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
- the transmitter 815 and the receiver 810 may be co-located in a transceiver, which may include or be coupled with a modem.
- the communications manager 820, the receiver 810, the transmitter 815, or various combinations thereof or various components thereof may be examples of means for performing various aspects of logging and signaling of operations for ML LCM as described herein.
- the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may support a method for performing one or more of the functions described herein.
- the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
- the hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, 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.
- a processor and memory coupled with the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory) .
- the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure) .
- code e.g., as communications management software or firmware
- the functions of the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a
- the communications manager 820 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 810, the transmitter 815, or both.
- the communications manager 820 may receive information from the receiver 810, send information to the transmitter 815, or be integrated in combination with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.
- the communications manager 820 may support wireless communications at a network entity in accordance with examples as disclosed herein.
- the communications manager 820 is capable of, configured to, or operable to support a means for transmitting control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link with a UE.
- the communications manager 820 is capable of, configured to, or operable to support a means for receiving, according to the scheme, an operation report including an indication of one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link and one or more conditions corresponding to the one or more operations.
- the communications manager 820 is capable of, configured to, or operable to support a means for communicating with the UE via the wireless communication link based on receiving the operation report.
- the device 805 e.g., a processor controlling or otherwise coupled with the receiver 810, the transmitter 815, the communications manager 820, or a combination thereof
- the device 805 may support techniques for logging and reporting LCM operations and corresponding conditions, resulting in more efficient use of system resources, increased reliability of communications, decreased system latency, and improved user experience.
- FIG. 9 shows a block diagram 900 of a device 905 that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure.
- the device 905 may be an example of aspects of a device 805 or a network entity 105 as described herein.
- the device 905 may include a receiver 910, a transmitter 915, and a communications manager 920.
- the device 905 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
- the receiver 910 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) .
- Information may be passed on to other components of the device 905.
- the receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 910 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
- the transmitter 915 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 905.
- the transmitter 915 may output information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) .
- the transmitter 915 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 915 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
- the transmitter 915 and the receiver 910 may be co-located in a transceiver, which may include or be coupled with a modem.
- the device 905, or various components thereof may be an example of means for performing various aspects of logging and signaling of operations for ML LCM as described herein.
- the communications manager 920 may include an LCM operation manager 925, an operation report manager 930, a communication functionality manager 935, or any combination thereof.
- the communications manager 920 may be an example of aspects of a communications manager 820 as described herein.
- the communications manager 920, or various components thereof may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 910, the transmitter 915, or both.
- the communications manager 920 may receive information from the receiver 910, send information to the transmitter 915, or be integrated in combination with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.
- the communications manager 920 may support wireless communications at a network entity in accordance with examples as disclosed herein.
- the LCM operation manager 925 is capable of, configured to, or operable to support a means for transmitting control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link with a UE.
- the operation report manager 930 is capable of, configured to, or operable to support a means for receiving, according to the scheme, an operation report including an indication of one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link and one or more conditions corresponding to the one or more operations.
- the communication functionality manager 935 is capable of, configured to, or operable to support a means for communicating with the UE via the wireless communication link based on receiving the operation report.
- FIG. 10 shows a block diagram 1000 of a communications manager 1020 that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure.
- the communications manager 1020 may be an example of aspects of a communications manager 820, a communications manager 920, or both, as described herein.
- the communications manager 1020, or various components thereof, may be an example of means for performing various aspects of logging and signaling of operations for ML LCM as described herein.
- the communications manager 1020 may include an LCM operation manager 1025, an operation report manager 1030, a communication functionality manager 1035, an operation condition manager 1040, a logging information manager 1045, a statistical information manager 1050, or any combination thereof.
- Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses) which may include communications within a protocol layer of a protocol stack, communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105) , or any combination thereof.
- the communications manager 1020 may support wireless communications at a network entity in accordance with examples as disclosed herein.
- the LCM operation manager 1025 is capable of, configured to, or operable to support a means for transmitting control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link with a UE.
- the operation report manager 1030 is capable of, configured to, or operable to support a means for receiving, according to the scheme, an operation report including an indication of one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link and one or more conditions corresponding to the one or more operations.
- the communication functionality manager 1035 is capable of, configured to, or operable to support a means for communicating with the UE via the wireless communication link based on receiving the operation report.
- the operation condition manager 1040 is capable of, configured to, or operable to support a means for transmitting, via the control signaling, a second indication to include the one or more conditions in the operation report, where receiving the operation report including the one or more conditions is based on transmitting the second indication.
- the logging information manager 1045 is capable of, configured to, or operable to support a means for transmitting, via the control signaling, a second indication of a starting time and an ending time for logging the one or more operations and the one or more conditions corresponding to the one or more operations, where receiving the operation report including the one or more conditions is based on transmitting the second indication of the starting time and the ending time.
- the statistical information manager 1050 is capable of, configured to, or operable to support a means for transmitting, via the control signaling, a request to provide statistical information associated with the one or more operations. In some examples, the statistical information manager 1050 is capable of, configured to, or operable to support a means for receiving, via the operation report, the statistical information based on transmitting the request.
- the one or more conditions corresponding to the one or more operations include a UE location at a timing of performing the one or more operations, a zone identifier associated with a location of the UE when performing the one or more operations, a UE mobility state associated with the timing of performing the one or more operations, a reference signal receive power range associated with performing the one or more operations, a blockage event corresponding to the one or more operations, or any combination thereof.
- the operation report includes a radio resource control message or a MAC control element (CE) .
- CE MAC control element
- activating or deactivating the functionality of the at least one ML model includes switching from a first functionality of the at least one ML model to a second functionality of a second ML model.
- activating or deactivating the functionality includes activating or deactivating a first ML model corresponding to the functionality or switching from the first ML model corresponding to the functionality to a second ML model corresponding to the functionality.
- FIG. 11 shows a diagram of a system 1100 including a device 1105 that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure.
- the device 1105 may be an example of or include the components of a device 805, a device 905, or a network entity 105 as described herein.
- the device 1105 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communications over one or more wired interfaces, over one or more wireless interfaces, or any combination thereof.
- the device 1105 may include components that support outputting and obtaining communications, such as a communications manager 1120, a transceiver 1110, an antenna 1115, a memory 1125, code 1130, and a processor 1135. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1140) .
- a communications manager 1120 e.g., operatively, communicatively, functionally, electronically, electrically
- buses e.g., a bus 1140
- the transceiver 1110 may support bi-directional communications via wired links, wireless links, or both as described herein.
- the transceiver 1110 may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver 1110 may include a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
- the device 1105 may include one or more antennas 1115, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently) .
- the transceiver 1110 may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas 1115, by a wired transmitter) , to receive modulated signals (e.g., from one or more antennas 1115, from a wired receiver) , and to demodulate signals.
- the transceiver 1110 may include one or more interfaces, such as one or more interfaces coupled with the one or more antennas 1115 that are configured to support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas 1115 that are configured to support various transmitting or outputting operations, or a combination thereof.
- the transceiver 1110 may include or be configured for coupling with one or more processors or memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other outputting, or any combination thereof.
- the transceiver 1110, or the transceiver 1110 and the one or more antennas 1115, or the transceiver 1110 and the one or more antennas 1115 and one or more processors or memory components may be included in a chip or chip assembly that is installed in the device 1105.
- the transceiver may be operable to support communications via one or more communications links (e.g., a communication link 125, a backhaul communication link 120, a midhaul communication link 162, a fronthaul communication link 168) .
- one or more communications links e.g., a communication link 125, a backhaul communication link 120, a midhaul communication link 162, a fronthaul communication link 168 .
- the memory 1125 may include RAM and ROM.
- the memory 1125 may store computer-readable, computer-executable code 1130 including instructions that, when executed by the processor 1135, cause the device 1105 to perform various functions described herein.
- the code 1130 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1130 may not be directly executable by the processor 1135 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
- the memory 1125 may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.
- the processor 1135 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, discrete gate or transistor logic, a discrete hardware component, or any combination thereof) .
- the processor 1135 may be configured to operate a memory array using a memory controller.
- a memory controller may be integrated into the processor 1135.
- the processor 1135 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1125) to cause the device 1105 to perform various functions (e.g., functions or tasks supporting logging and signaling of operations for ML LCM) .
- the device 1105 or a component of the device 1105 may include a processor 1135 and memory 1125 coupled with the processor 1135, the processor 1135 and memory 1125 configured to perform various functions described herein.
- the processor 1135 may be an example of a cloud-computing platform (e.g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code 1130) to perform the functions of the device 1105.
- the processor 1135 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1105 (such as within the memory 1125) .
- the processor 1135 may be a component of a processing system.
- a processing system may generally refer to a system or series of machines or components that receives inputs and processes the inputs to produce a set of outputs (which may be passed to other systems or components of, for example, the device 1105) .
- a processing system of the device 1105 may refer to a system including the various other components or subcomponents of the device 1105, such as the processor 1135, or the transceiver 1110, or the communications manager 1120, or other components or combinations of components of the device 1105.
- the processing system of the device 1105 may interface with other components of the device 1105, and may process information received from other components (such as inputs or signals) or output information to other components.
- a chip or modem of the device 1105 may include a processing system and one or more interfaces to output information, or to obtain information, or both.
- the one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or a same interface configured to output information and to obtain information, among other implementations.
- the one or more interfaces may refer to an interface between the processing system of the chip or modem and a transmitter, such that the device 1105 may transmit information output from the chip or modem.
- the one or more interfaces may refer to an interface between the processing system of the chip or modem and a receiver, such that the device 1105 may obtain information or signal inputs, and the information may be passed to the processing system.
- a first interface also may obtain information or signal inputs
- a second interface also may output information or signal outputs.
- a bus 1140 may support communications of (e.g., within) a protocol layer of a protocol stack. In some examples, a bus 1140 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack) , which may include communications performed within a component of the device 1105, or between different components of the device 1105 that may be co-located or located in different locations (e.g., where the device 1105 may refer to a system in which one or more of the communications manager 1120, the transceiver 1110, the memory 1125, the code 1130, and the processor 1135 may be located in one of the different components or divided between different components) .
- a logical channel of a protocol stack e.g., between protocol layers of a protocol stack
- the device 1105 may refer to a system in which one or more of the communications manager 1120, the transceiver 1110, the memory 1125, the code 1130, and the processor 1135 may be located in one of the different
- the communications manager 1120 may manage aspects of communications with a core network 130 (e.g., via one or more wired or wireless backhaul links) .
- the communications manager 1120 may manage the transfer of data communications for client devices, such as one or more UEs 115.
- the communications manager 1120 may manage communications with other network entities 105, and may include a controller or scheduler for controlling communications with UEs 115 in cooperation with other network entities 105.
- the communications manager 1120 may support an X2 interface within an LTE/LTE-A wireless communications network technology to provide communication between network entities 105.
- the communications manager 1120 may support wireless communications at a network entity in accordance with examples as disclosed herein.
- the communications manager 1120 is capable of, configured to, or operable to support a means for transmitting control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link with a UE.
- the communications manager 1120 is capable of, configured to, or operable to support a means for receiving, according to the scheme, an operation report including an indication of one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link and one or more conditions corresponding to the one or more operations.
- the communications manager 1120 is capable of, configured to, or operable to support a means for communicating with the UE via the wireless communication link based on receiving the operation report.
- the device 1105 may support techniques for logging and reporting LCM operations and corresponding conditions, resulting in more efficient use of system resources, increased reliability of communications, decreased system latency, and improved user experience.
- the communications manager 1120 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver 1110, the one or more antennas 1115 (e.g., where applicable) , or any combination thereof.
- the communications manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1120 may be supported by or performed by the transceiver 1110, the processor 1135, the memory 1125, the code 1130, or any combination thereof.
- the code 1130 may include instructions executable by the processor 1135 to cause the device 1105 to perform various aspects of logging and signaling of operations for ML LCM as described herein, or the processor 1135 and the memory 1125 may be otherwise configured to perform or support such operations.
- FIG. 12 shows a flowchart illustrating a method 1200 that supports logging and signaling of operations for ML LCM in accordance with aspects of the present disclosure.
- the operations of the method 1200 may be implemented by a UE or its components as described herein.
- the operations of the method 1200 may be performed by a UE 115 as described with reference to FIGs. 1 through 7.
- a UE may execute a set of instructions to control the functional elements of the wireless UE to perform the described functions.
- the wireless UE may perform aspects of the described functions using special-purpose hardware.
- the method may include receiving control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link.
- the operations of 1205 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1205 may be performed by an ML model reporting manager 625 as described with reference to FIG. 6.
- the method may include performing one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link based on receiving the control signaling.
- the operations of 1210 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1210 may be performed by an LCM operation manager 630 as described with reference to FIG. 6.
- the method may include transmitting, according to the scheme, an operation report including an indication of the one or more operations and one or more conditions corresponding to the one or more operations.
- the operations of 1215 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1215 may be performed by an operation report manager 635 as described with reference to FIG. 6.
- FIG. 13 shows a flowchart illustrating a method 1300 that supports logging and signaling of operations for ML LCM in accordance with aspects of the present disclosure.
- the operations of the method 1300 may be implemented by a UE or its components as described herein.
- the operations of the method 1300 may be performed by a UE 115 as described with reference to FIGs. 1 through 7.
- a UE may execute a set of instructions to control the functional elements of the wireless UE to perform the described functions.
- the wireless UE may perform aspects of the described functions using special-purpose hardware.
- the method may include receiving control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link.
- the operations of 1305 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed by an ML model reporting manager 625 as described with reference to FIG. 6.
- the method may include receiving, via the control signaling, a second indication to include the one or more conditions in the operation report, where transmitting the operation report including the one or more conditions is based on receiving the second indication.
- the operations of 1310 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed by an operation condition manager 640 as described with reference to FIG. 6.
- the method may include performing one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link based on receiving the control signaling.
- the operations of 1315 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed by an LCM operation manager 630 as described with reference to FIG. 6.
- the method may include transmitting, according to the scheme, an operation report including an indication of the one or more operations and one or more conditions corresponding to the one or more operations.
- the operations of 1320 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1320 may be performed by an operation report manager 635 as described with reference to FIG. 6.
- FIG. 14 shows a flowchart illustrating a method 1400 that supports logging and signaling of operations for ML LCM in accordance with aspects of the present disclosure.
- the operations of the method 1400 may be implemented by a network entity or its components as described herein.
- the operations of the method 1400 may be performed by a network entity as described with reference to FIGs. 1 through 3 and 8 through 11.
- a network entity may execute a set of instructions to control the functional elements of the wireless network entity to perform the described functions.
- the wireless network entity may perform aspects of the described functions using special-purpose hardware.
- the method may include transmitting control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link with a UE.
- the operations of 1405 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed by an LCM operation manager 1025 as described with reference to FIG. 10.
- the method may include receiving, according to the scheme, an operation report including an indication of one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link and one or more conditions corresponding to the one or more operations.
- the operations of 1410 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed by an operation report manager 1030 as described with reference to FIG. 10.
- the method may include communicating with the UE via the wireless communication link based on receiving the operation report.
- the operations of 1415 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed by a communication functionality manager 1035 as described with reference to FIG. 10.
- FIG. 15 shows a flowchart illustrating a method 1500 that supports logging and signaling of operations for ML LCM in accordance with aspects of the present disclosure.
- the operations of the method 1500 may be implemented by a network entity or its components as described herein.
- the operations of the method 1500 may be performed by a network entity as described with reference to FIGs. 1 through 3 and 8 through 11.
- a network entity may execute a set of instructions to control the functional elements of the wireless network entity to perform the described functions.
- the wireless network entity may perform aspects of the described functions using special-purpose hardware.
- the method may include transmitting control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link with a UE.
- the operations of 1505 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed by an LCM operation manager 1025 as described with reference to FIG. 10.
- the method may include transmitting, via the control signaling, a second indication to include the one or more conditions in the operation report, where receiving the operation report including the one or more conditions is based on transmitting the second indication.
- the operations of 1510 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed by an operation condition manager 1040 as described with reference to FIG. 10.
- the method may include receiving, according to the scheme, an operation report including an indication of one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link and one or more conditions corresponding to the one or more operations.
- the operations of 1515 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed by an operation report manager 1030 as described with reference to FIG. 10.
- the method may include communicating with the UE via the wireless communication link based on receiving the operation report.
- the operations of 1520 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1520 may be performed by a communication functionality manager 1035 as described with reference to FIG. 10.
- a method for wireless communications at a UE comprising: receiving control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link; performing one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link based at least in part on receiving the control signaling; and transmitting, according to the scheme, an operation report comprising an indication of the one or more operations and one or more conditions corresponding to the one or more operations.
- Aspect 2 The method of aspect 1, further comprising: receiving, via the control signaling, a second indication to include the one or more conditions in the operation report, wherein transmitting the operation report comprising the one or more conditions is based at least in part on receiving the second indication.
- Aspect 3 The method of any of aspects 1 through 2, further comprising: logging the one or more operations and the one or more conditions corresponding to the one or more operations at a local memory of the UE; and retrieving the one or more operations and the one or more conditions corresponding to the one or more operations from the local memory, wherein transmitting the operation report is based at least in part on the logging and the retrieving.
- Aspect 4 The method of aspect 3, further comprising: receiving, via the control signaling, a second indication of a starting time and an ending time for logging the one or more operations and the one or more conditions corresponding to the one or more operations, wherein the logging is based at least in part on the starting time and the ending time.
- Aspect 5 The method of any of aspects 1 through 4, further comprising: receiving, via the control signaling, a request to provide statistical information associated with the one or more operations; and generating the statistical information based at least in part on receiving the request, wherein the operation report comprises the statistical information.
- Aspect 6 The method of any of aspects 1 through 5, wherein the one or more conditions corresponding to the one or more operations comprise a UE location at a timing of performing the one or more operations, a zone identifier associated with a location of the UE when performing the one or more operations, a UE mobility state associated with the timing of performing the one or more operations, a reference signal receive power range associated with performing the one or more operations, a blockage event corresponding to the one or more operations, or any combination thereof.
- Aspect 7 The method of any of aspects 1 through 6, wherein the operation report comprises a radio resource control message or a MAC control element (CE) .
- CE MAC control element
- Aspect 8 The method of any of aspects 1 through 7, wherein activating or deactivating the functionality of the at least one ML model comprises switching from a first functionality of the at least one ML model to a second functionality of a second ML model.
- Aspect 9 The method of any of aspects 1 through 8, wherein activating or deactivating the functionality comprises activating or deactivating a first ML model corresponding to the functionality or switching from the first ML model corresponding to the functionality to a second ML model corresponding to the functionality.
- a method for wireless communications at a network entity comprising: transmitting control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link with a UE; receiving, according to the scheme, an operation report comprising an indication of one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link and one or more conditions corresponding to the one or more operations; and communicating with the UE via the wireless communication link based at least in part on receiving the operation report.
- Aspect 11 The method of aspect 10, further comprising: transmitting, via the control signaling, a second indication to include the one or more conditions in the operation report, wherein receiving the operation report comprising the one or more conditions is based at least in part on transmitting the second indication.
- Aspect 12 The method of any of aspects 10 through 11, further comprising: transmitting, via the control signaling, a second indication of a starting time and an ending time for logging the one or more operations and the one or more conditions corresponding to the one or more operations, wherein receiving the operation report comprising the one or more conditions is based at least in part on transmitting the second indication of the starting time and the ending time.
- Aspect 13 The method of any of aspects 10 through 12, further comprising: transmitting, via the control signaling, a request to provide statistical information associated with the one or more operations; and receiving, via the operation report, the statistical information based at least in part on transmitting the request.
- Aspect 14 The method of any of aspects 10 through 13, wherein the one or more conditions corresponding to the one or more operations comprise a UE location at a timing of performing the one or more operations, a zone identifier associated with a location of the UE when performing the one or more operations, a UE mobility state associated with the timing of performing the one or more operations, a reference signal receive power range associated with performing the one or more operations, a blockage event corresponding to the one or more operations, or any combination thereof.
- Aspect 15 The method of any of aspects 10 through 14, wherein the operation report comprises a radio resource control message or a MAC control element (CE) .
- CE MAC control element
- Aspect 16 The method of any of aspects 10 through 15, wherein activating or deactivating the functionality of the at least one ML model comprises switching from a first functionality of the at least one ML model to a second functionality of a second ML model.
- Aspect 17 The method of any of aspects 10 through 16, wherein activating or deactivating the functionality comprises activating or deactivating a first ML model corresponding to the functionality or switching from the first ML model corresponding to the functionality to a second ML model corresponding to the functionality.
- Aspect 18 An apparatus for wireless communications at a UE, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 1 through 9.
- Aspect 19 An apparatus for wireless communications at a UE, comprising at least one means for performing a method of any of aspects 1 through 9.
- Aspect 20 A non-transitory computer-readable medium storing code for wireless communications at a UE, the code comprising instructions executable by a processor to perform a method of any of aspects 1 through 9.
- Aspect 21 An apparatus for wireless communications at a network entity, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 10 through 17.
- Aspect 22 An apparatus for wireless communications at a network entity, comprising at least one means for performing a method of any of aspects 10 through 17.
- Aspect 23 A non-transitory computer-readable medium storing code for wireless communications at a network entity, the code comprising instructions executable by a processor to perform a method of any of aspects 10 through 17.
- LTE, LTE-A, LTE-A Pro, or NR may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks.
- the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB) , Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.
- UMB Ultra Mobile Broadband
- IEEE Institute of Electrical and Electronics Engineers
- Wi-Fi Institute of Electrical and Electronics Engineers
- WiMAX IEEE 802.16
- IEEE 802.20 Flash-OFDM
- 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.
- 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 using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as or transmitted using one or more instructions or code of 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 location 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.
- any connection is properly termed a computer-readable medium.
- the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared, radio, and microwave
- the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium.
- Disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD) , floppy disk and Blu-ray disc. Disks may reproduce data magnetically, and discs may reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.
- determining encompasses a variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database or another data structure) , ascertaining and the like. Also, “determining” can include receiving (e.g., receiving information) , accessing (e.g., accessing data stored in memory) and the like. Also, “determining” can include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Methods, systems, and devices for wireless communications are described. In some examples, a network entity may configure a user equipment (UE) to log artificial intelligence (AI) machine learning (ML) life-cycle management (LCM) operations, together with associated conditions under which the UE performed the LCM operations, and then report the logged information to the network entity. The UE may log and report LCM operations for AI/ML models, functionalities, or both (e.g., for model-ID based LCM decisions and functionality-based LCM decisions). LCM decisions may include model or functionality selection, activation, deactivation, switching, and fallback. In some examples, the start and stop time for logging the information may be determined and configured by the network entity. In some examples, the UE may also be configured to report statistics corresponding to the logged information.
Description
FIELD OF TECHNOLOGY
The following relates to wireless communications, including logging and signaling of operations for machine learning life-cycle management.
Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power) . Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems. These systems may employ technologies such as code division multiple access (CDMA) , time division multiple access (TDMA) , frequency division multiple access (FDMA) , orthogonal FDMA (OFDMA) , or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM) . A wireless multiple-access communications system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE) .
SUMMARY
The described techniques relate to improved methods, systems, devices, and apparatuses that support logging and signaling of operations for machine learning (ML) life-cycle management. In some examples, a network entity may configure a user equipment (UE) to log artificial intelligence (AI) or ML life-cycle management (LCM) operations, together with associated conditions under which the UE performed the LCM operations, and then report the logged information to the network entity. The UE may log and report LCM operations for AI/ML models, functionalities, or both (e.g., for model-ID based LCM decisions and functionality-based LCM decisions) . LCM decisions may include model or functionality selection, activation, deactivation,
switching, and fallback. In some examples, the start and stop time for logging the information may be determined and configured by the network entity. In some examples, the UE may also be configured to report statistics corresponding to the logged information.
A method for wireless communications at a user equipment (UE) is described. The method may include receiving control signaling indicating a scheme for reporting feedback information about using machine learning models to maintain a wireless communication link, performing one or more operations to activate or deactivate a functionality of at least one machine learning model for maintaining the wireless communication link based on receiving the control signaling, and transmitting, according to the scheme, an operation report including an indication of the one or more operations and one or more conditions corresponding to the one or more operations.
An apparatus for wireless communications at a UE is described. The apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to receive control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link, perform one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link based on receiving the control signaling, and transmit, according to the scheme, an operation report including an indication of the one or more operations and one or more conditions corresponding to the one or more operations.
Another apparatus for wireless communications at a UE is described. The apparatus may include means for receiving control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link, means for performing one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link based on receiving the control signaling, and means for transmitting, according to the scheme, an operation report including an indication of the one or more operations and one or more conditions corresponding to the one or more operations.
A non-transitory computer-readable medium storing code for wireless communications at a UE is described. The code may include instructions executable by a processor to receive control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link, perform one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link based on receiving the control signaling, and transmit, according to the scheme, an operation report including an indication of the one or more operations and one or more conditions corresponding to the one or more operations.
Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, via the control signaling, a second indication to include the one or more conditions in the operation report, where transmitting the operation report including the one or more conditions may be based on receiving the second indication.
Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for logging the one or more operations and the one or more conditions corresponding to the one or more operations at a local memory of the UE and retrieving the one or more operations and the one or more conditions corresponding to the one or more operations from the local memory, where transmitting the operation report may be based on the logging and the retrieving.
Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, via the control signaling, a second indication of a starting time and an ending time for logging the one or more operations and the one or more conditions corresponding to the one or more operations, where the logging may be based on the starting time and the ending time.
Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, via the control signaling, a request to provide statistical information associated with the one or more operations and generating the statistical
information based on receiving the request, where the operation report includes the statistical information.
In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the one or more conditions corresponding to the one or more operations include a UE location at a timing of performing the one or more operations, a zone identifier associated with a location of the UE when performing the one or more operations, a UE mobility state associated with the timing of performing the one or more operations, a reference signal receive power range associated with performing the one or more operations, a blockage event corresponding to the one or more operations, or any combination thereof.
In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the operation report includes a radio resource control message or a media access control (MAC) control element (CE) .
Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for activating or deactivating the functionality of the at least one ML model includes switching from a first functionality of the at least one ML model to a second functionality of a second ML model.
Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for activating or deactivating the functionality includes activating or deactivating a first ML model corresponding to the functionality or switching from the first ML model corresponding to the functionality to a second ML model corresponding to the functionality.
A method for wireless communications at a network entity is described. The method may include transmitting control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link with a UE, receiving, according to the scheme, an operation report including an indication of one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link and one or more
conditions corresponding to the one or more operations, and communicating with the UE via the wireless communication link based on receiving the operation report.
An apparatus for wireless communications at a network entity is described. The apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to transmit control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link with a UE, receive, according to the scheme, an operation report including an indication of one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link and one or more conditions corresponding to the one or more operations, and communicate with the UE via the wireless communication link based on receiving the operation report.
Another apparatus for wireless communications at a network entity is described. The apparatus may include means for transmitting control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link with a UE, means for receiving, according to the scheme, an operation report including an indication of one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link and one or more conditions corresponding to the one or more operations, and means for communicating with the UE via the wireless communication link based on receiving the operation report.
A non-transitory computer-readable medium storing code for wireless communications at a network entity is described. The code may include instructions executable by a processor to transmit control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link with a UE, receive, according to the scheme, an operation report including an indication of one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link and one or more conditions corresponding to the one or more operations, and communicate with the UE via the wireless communication link based on receiving the operation report.
Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, via the control signaling, a second indication to include the one or more conditions in the operation report, where receiving the operation report including the one or more conditions may be based on transmitting the second indication.
Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, via the control signaling, a second indication of a starting time and an ending time for logging the one or more operations and the one or more conditions corresponding to the one or more operations, where receiving the operation report including the one or more conditions may be based on transmitting the second indication of the starting time and the ending time.
Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, via the control signaling, a request to provide statistical information associated with the one or more operations and receiving, via the operation report, the statistical information based on transmitting the request.
In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the one or more conditions corresponding to the one or more operations include a UE location at a timing of performing the one or more operations, a zone identifier associated with a location of the UE when performing the one or more operations, a UE mobility state associated with the timing of performing the one or more operations, a reference signal receive power range associated with performing the one or more operations, a blockage event corresponding to the one or more operations, or any combination thereof.
In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the operation report includes a radio resource control message or a MAC control element (CE) .
Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or
instructions for activating or deactivating the functionality of the at least one ML model includes switching from a first functionality of the at least one ML model to a second functionality of a second ML model.
Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for activating or deactivating the functionality includes activating or deactivating a first ML model corresponding to the functionality or switching from the first ML model corresponding to the functionality to a second ML model corresponding to the functionality.
FIG. 1 shows an example of a wireless communications system that supports logging and signaling of operations for machine learning (ML) life-cycle management (LCM) in accordance with one or more aspects of the present disclosure.
FIG. 2 shows an example of a wireless communications system that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure.
FIG. 3 shows an example of a process flow that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure.
FIGs. 4 and 5 show block diagrams of devices that support logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure.
FIG. 6 shows a block diagram of a communications manager that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure.
FIG. 7 shows a diagram of a system including a device that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure.
FIGs. 8 and 9 show block diagrams of devices that support logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure.
FIG. 10 shows a block diagram of a communications manager that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure.
FIG. 11 shows a diagram of a system including a device that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure.
FIGs. 12 through 15 show flowcharts illustrating methods that support logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure.
In some examples, a user equipment (UE) may support artificial intelligence (AI) or machine learning (ML) , which the UE may use to perform wireless communications procedures (e.g., beam selection or beam prediction, among other examples) . The UE may perform life-cycle management (LCM) operations for a given AI/ML model or functionality (e.g., model or functionality selection, activation, deactivation, switching, and fallback, among other examples) . However, AI/ML functionality or models may change over time, or may be activated or deactivated autonomously by the UE. However, without a mechanism to determine the switching, the network entity 105-a may make erroneous resource allocations, or may default to signaling related AI/ML functionalities that are not applicable if the UE 115-a has defaulted to fallback procedures that do not implement AI/ML functionalities or models. Such misaligned signaling and techniques may result in inefficient use of system resources, unreliable communications, increased system latency, and decreased user experience.
In some examples, as described herein, a network entity may configure the UE to log LCM operations, together with associated conditions under which the UE performed the LCM operations, and then report the logged information to the network
entity. The UE may log and report LCM operations for AI/ML models, functionalities, or both (e.g., for model-ID based LCM decisions and functionality-based LCM decisions) . LCM decisions may include model or functionality selection, activation, deactivation, switching, and fallback. In some examples, the start and stop time for logging the information may be determined and configured by the network entity. In some examples, the UE may also be configured to report statistics corresponding to the logged information (e.g., instead of or along with raw measurements and data) .
Aspects of the disclosure are initially described in the context of wireless communications systems and process flows. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to logging and signaling of operations for ML LCM.
FIG. 1 shows an example of a wireless communications system 100 that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure. The wireless communications system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.
The network entities 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may include devices in different forms or having different capabilities. In various examples, a network entity 105 may be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature. In some examples, network entities 105 and UEs 115 may wirelessly communicate via one or more communication links 125 (e.g., a radio frequency (RF) access link) . For example, a network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area over which a network entity 105 and a UE 115 may support the communication of signals according to one or more radio access technologies (RATs) .
The UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times. The UEs 115 may be devices in different forms or having different capabilities. Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communications with various types of devices, such as other UEs 115 or network entities 105, as shown in FIG. 1.
As described herein, a node of the wireless communications system 100, which may be referred to as a network node, or a wireless node, may be a network entity 105 (e.g., any network entity described herein) , a UE 115 (e.g., any UE described herein) , a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be a UE 115. As another example, a node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first, second, and third nodes may be different relative to these examples. Similarly, reference to a UE 115, network entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity 105, apparatus, device, computing system, or the like being a node. For example, disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.
In some examples, network entities 105 may communicate with the core network 130, or with one another, or both. For example, network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., in accordance with an S1, N2, N3, or other interface protocol) . In some examples, network entities 105 may communicate with one another via a backhaul communication link 120 (e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network entities 105) or indirectly (e.g., via a core network 130) . In some examples, network entities 105 may communicate
with one another via a midhaul communication link 162 (e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (e.g., in accordance with a fronthaul interface protocol) , or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link) , one or more wireless links (e.g., a radio link, a wireless optical link) , among other examples or various combinations thereof. A UE 115 may communicate with the core network 130 via a communication link 155.
One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or a giga-NodeB (either of which may be referred to as a gNB) , a 5G NB, a next-generation eNB (ng-eNB) , a Home NodeB, a Home eNodeB, or other suitable terminology) . In some examples, a network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140) .
In some examples, a network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) , which may be configured to utilize a protocol stack that is physically or logically distributed among two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (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) ) . For example, a network entity 105 may include one or more of a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) 180 system, or any combination thereof. An RU 170 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 105 in a disaggregated RAN architecture may be co-located, or one or more
components of the network entities 105 may be located in distributed locations (e.g., separate physical locations) . In some examples, one or more network entities 105 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) ) .
The split of functionality between a CU 160, a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170. For example, a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack. In some examples, the CU 160 may host upper protocol layer (e.g., layer 3 (L3) , layer 2 (L2) ) functionality and signaling (e.g., Radio Resource Control (RRC) , service data adaption protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) . The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or 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. Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU 165 and an RU 170 such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or multiple different cells (e.g., via one or more RUs 170) . In some cases, a functional split between a CU 160 and a DU 165, or between a DU 165 and an RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170) . A CU 160 may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU 160 may be connected to one or more DUs 165 via a midhaul communication link 162 (e.g., F1, F1-c, F1-u) , and a DU 165 may be connected to one or more RUs 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface) . In some examples, a midhaul communication link 162 or a fronthaul communication link 168 may be
implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 105 that are in communication via such communication links.
In wireless communications systems (e.g., wireless communications system 100) , infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., to a core network 130) . In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as a donor entity or an IAB donor. One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140) . The one or more donor network entities 105 (e.g., IAB donors) may be in communication with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120) . IAB nodes 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by DUs 165 of a coupled IAB donor. An IAB-MT may include an independent set of antennas for relay of communications with UEs 115, or may share the same antennas (e.g., of an RU 170) of an IAB node 104 used for access via the DU 165 of the IAB node 104 (e.g., referred to as virtual IAB-MT (vIAB-MT) ) . In some examples, the IAB nodes 104 may include DUs 165 that support communication links with additional entities (e.g., IAB nodes 104, UEs 115) within the relay chain or configuration of the access network (e.g., downstream) . In such cases, one or more components of the disaggregated RAN architecture (e.g., one or more IAB nodes 104 or components of IAB nodes 104) may be configured to operate according to the techniques described herein.
For instance, an access network (AN) or RAN may include communications between access nodes (e.g., an IAB donor) , IAB nodes 104, and one or more UEs 115. The IAB donor may facilitate connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130) . That is, an IAB donor may refer to a RAN node with a wired or wireless connection to core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170) , in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a
backhaul link) . IAB donor and IAB nodes 104 may communicate via an F1 interface according to a protocol that defines signaling messages (e.g., an F1 AP protocol) . Additionally, or alternatively, the CU 160 may communicate with the core network via an interface, which may be an example of a portion of backhaul link, and may communicate with other CUs 160 (e.g., a CU 160 associated with an alternative IAB donor) via an Xn-C interface, which may be an example of a portion of a backhaul link.
An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UEs 115, wireless self-backhauling capabilities) . A DU 165 may act as a distributed scheduling node towards child nodes associated with the IAB node 104, and the IAB-MT may act as a scheduled node towards parent nodes associated with the IAB node 104. That is, an IAB donor may be referred to as a parent node in communication with one or more child nodes (e.g., an IAB donor may relay transmissions for UEs through one or more other IAB nodes 104) . Additionally, or alternatively, an IAB node 104 may also be referred to as a parent node or a child node to other IAB nodes 104, depending on the relay chain or configuration of the AN. Therefore, the IAB-MT entity of IAB nodes 104 may provide a Uu interface for a child IAB node 104 to receive signaling from a parent IAB node 104, and the DU interface (e.g., DUs 165) may provide a Uu interface for a parent IAB node 104 to signal to a child IAB node 104 or UE 115.
For example, IAB node 104 may be referred to as a parent node that supports communications for a child IAB node, or referred to as a child IAB node associated with an IAB donor, or both. The IAB donor may include a CU 160 with a wired or wireless connection (e.g., a backhaul communication link 120) to the core network 130 and may act as parent node to IAB nodes 104. For example, the DU 165 of IAB donor may relay transmissions to UEs 115 through IAB nodes 104, or may directly signal transmissions to a UE 115, or both. The CU 160 of IAB donor may signal communication link establishment via an F1 interface to IAB nodes 104, and the IAB nodes 104 may schedule transmissions (e.g., transmissions to the UEs 115 relayed from the IAB donor) through the DUs 165. That is, data may be relayed to and from IAB nodes 104 via signaling via an NR Uu interface to MT of the IAB node 104. Communications with IAB node 104 may be scheduled by a DU 165 of IAB donor and communications with IAB node 104 may be scheduled by DU 165 of IAB node 104.
In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support logging and signaling of operations for ML LCM as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., IAB nodes 104, DUs 165, CUs 160, RUs 170, RIC 175, SMO 180) .
A UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA) , a tablet computer, a laptop computer, or a personal computer. In some examples, a UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, or vehicles, meters, among other examples.
The UEs 115 described herein may be able to communicate with various types of devices, such as other UEs 115 that may sometimes act as relays as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.
The UEs 115 and the network entities 105 may wirelessly communicate with one another via one or more communication links 125 (e.g., an access link) using resources associated with one or more carriers. The term “carrier” may refer to a set of RF spectrum resources having a defined physical layer structure for supporting the communication links 125. For example, a carrier used for a communication link 125 may include a portion of a RF spectrum band (e.g., a bandwidth part (BWP) ) that is operated according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR) . Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information) , control signaling that coordinates operation for the carrier, user data, or other signaling. The
wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation. A UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Communication between a network entity 105 and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity) of a network entity 105. For example, the terms “transmitting, ” “receiving, ” or “communicating, ” when referring to a network entity 105, may refer to any portion of a network entity 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105) .
In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates operations for other carriers. A carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN) ) and may be identified according to a channel raster for discovery by the UEs 115. A carrier may be operated in a standalone mode, in which case initial acquisition and connection may be conducted by the UEs 115 via the carrier, or the carrier may be operated in a non-standalone mode, in which case a connection is anchored using a different carrier (e.g., of the same or a different radio access technology) .
The communication links 125 shown in the wireless communications system 100 may include downlink transmissions (e.g., forward link transmissions) from a network entity 105 to a UE 115, uplink transmissions (e.g., return link transmissions) from a UE 115 to a network entity 105, or both, among other configurations of transmissions. Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode) .
A carrier may be associated with a particular bandwidth of the RF spectrum and, in some examples, the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system 100. For example, the
carrier bandwidth may be one of a set of bandwidths for carriers of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz) ) . Devices of the wireless communications system 100 (e.g., the network entities 105, the UEs 115, or both) may have hardware configurations that support communications using a particular carrier bandwidth or may be configurable to support communications using one of a set of carrier bandwidths. In some examples, the wireless communications system 100 may include network entities 105 or UEs 115 that support concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured for operating using portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.
Signal waveforms transmitted via a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM) ) . In a system employing MCM techniques, a resource element may refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The quantity of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both) , such that a relatively higher quantity of resource elements (e.g., in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication. A wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam) , and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.
One or more numerologies for a carrier may be supported, and a numerology may include a subcarrier spacing (Δf) and a cyclic prefix. A carrier may be divided into one or more BWPs having the same or different numerologies. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time and communications for the UE 115 may be restricted to one or more active BWPs.
The time intervals for the network entities 105 or the UEs 115 may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of Ts=1/ (Δfmax·Nf) seconds, for which Δfmax may represent a supported subcarrier spacing, and Nf may represent a supported discrete Fourier transform (DFT) size. Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms) ) . Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023) .
Each frame may include multiple consecutively-numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a quantity of slots. Alternatively, each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing. Each slot may include a quantity of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period) . In some wireless communications systems 100, a slot may further be divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., Nf) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.
A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI) . In some examples, the TTI duration (e.g., a quantity of symbol periods in a TTI) may be variable. Additionally, or alternatively, the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs) ) .
Physical channels may be multiplexed for communication using a carrier according to various techniques. A physical control channel and a physical data channel may be multiplexed for signaling via a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET) ) for a physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth or a subset of the system
bandwidth of the carrier. One or more control regions (e.g., CORESETs) may be configured for a set of the UEs 115. For example, one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to an amount of control channel resources (e.g., control channel elements (CCEs) ) associated with encoded information for a control information format having a given payload size. Search space sets may include common search space sets configured for sending control information to multiple UEs 115 and UE-specific search space sets for sending control information to a specific UE 115.
A network entity 105 may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or any combination thereof. The term “cell” may refer to a logical communication entity used for communication with a network entity 105 (e.g., using a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID) , a virtual cell identifier (VCID) , or others) . In some examples, a cell also may refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) over which the logical communication entity operates. Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the network entity 105. For example, a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with coverage areas 110, among other examples.
A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by the UEs 115 with service subscriptions with the network provider supporting the macro cell. A small cell may be associated with a lower-powered network entity 105 (e.g., a lower-powered base station 140) , as compared with a macro cell, and a small cell may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to the UEs 115 with service subscriptions with the network provider or may provide restricted access to the UEs 115 having an association with the small cell (e.g., the UEs 115 in a closed subscriber group (CSG) , the UEs 115
associated with users in a home or office) . A network entity 105 may support one or multiple cells and may also support communications via the one or more cells using one or multiple component carriers.
In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT) , enhanced mobile broadband (eMBB) ) that may provide access for different types of devices.
In some examples, a network entity 105 (e.g., a base station 140, an RU 170) may be movable and therefore provide communication coverage for a moving coverage area 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, the overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.
The wireless communications system 100 may support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base stations 140) may have similar frame timings, and transmissions from different network entities 105 may be approximately aligned in time. For asynchronous operation, network entities 105 may have different frame timings, and transmissions from different network entities 105 may, in some examples, not be aligned in time. The techniques described herein may be used for either synchronous or asynchronous operations.
Some UEs 115, such as MTC or IoT devices, may be low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication) . M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a network entity 105 (e.g., a base station 140) without human intervention. In some examples, M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture
information and relay such information to a central server or application program that uses the information or presents the information to humans interacting with the application program. Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.
Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., a mode that supports one-way communication via transmission or reception, but not transmission and reception concurrently) . In some examples, half-duplex communications may be performed at a reduced peak rate. Other power conservation techniques for the UEs 115 include entering a power saving deep sleep mode when not engaging in active communications, operating using a limited bandwidth (e.g., according to narrowband communications) , or a combination of these techniques. For example, some UEs 115 may be configured for operation using a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs) ) within a carrier, within a guard-band of a carrier, or outside of a carrier.
The wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC) . The UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communications may include private communication or group communication and may be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.
In some examples, a UE 115 may be configured to support communicating directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g.,
in accordance with a peer-to-peer (P2P) , D2D, or sidelink protocol) . In some examples, one or more UEs 115 of a group that are performing D2D communications may be within the coverage area 110 of a network entity 105 (e.g., a base station 140, an RU 170) , which may support aspects of such D2D communications being configured by (e.g., scheduled by) the network entity 105. In some examples, one or more UEs 115 of such a group may be outside the coverage area 110 of a network entity 105 or may be otherwise unable to or not configured to receive transmissions from a network entity 105. In some examples, groups of the UEs 115 communicating via D2D communications may support a one-to-many (1: M) system in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, a network entity 105 may facilitate the scheduling of resources for D2D communications. In some other examples, D2D communications may be carried out between the UEs 115 without an involvement of a network entity 105.
In some systems, a D2D communication link 135 may be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UEs 115) . In some examples, vehicles may communicate using vehicle-to-everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these. A vehicle may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information relevant to a V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure, such as roadside units, or with the network via one or more network nodes (e.g., network entities 105, base stations 140, RUs 170) using vehicle-to-network (V2N) communications, or with both.
The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or 5G core (5GC) , which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management function (AMF) ) and at least one 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) ) . The control plane entity may manage non-access stratum (NAS) functions such as mobility,
authentication, and bearer management for the UEs 115 served by the network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP services 150 for one or more network operators. The IP services 150 may include access to the Internet, Intranet (s) , an IP Multimedia Subsystem (IMS) , or a Packet-Switched Streaming Service.
The wireless communications system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz) . Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to communications using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.
The wireless communications system 100 may also operate using a super high frequency (SHF) region, which may be in the range of 3 GHz to 30 GHz, also known as the centimeter band, or using an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) , also known as the millimeter band. In some examples, the wireless communications system 100 may support millimeter wave (mmW) communications between the UEs 115 and the network entities 105 (e.g., base stations 140, RUs 170) , and EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas. In some examples, such techniques may facilitate using antenna arrays within a device. The propagation of EHF transmissions, however, may be subject to even greater attenuation and shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country or regulating body.
The wireless communications system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communications system 100 may employ License Assisted Access (LAA) , LTE-Unlicensed (LTE-U) radio access technology, or NR technology using an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. While operating using unlicensed RF spectrum bands, devices such as the network entities 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance. In some examples, operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using a licensed band (e.g., LAA) . Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.
A network entity 105 (e.g., a base station 140, an RU 170) or a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a network entity 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with a network entity 105 may be located at diverse geographic locations. A network entity 105 may include an antenna array with a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming of communications with a UE 115. Likewise, a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally, or alternatively, an antenna panel may support RF beamforming for a signal transmitted via an antenna port.
The network entities 105 or the UEs 115 may use MIMO communications to exploit multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques may be referred to as spatial multiplexing. The multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas. Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be
referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords) . Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO) , for which multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO) , for which multiple spatial layers are transmitted to multiple devices.
Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating along particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation) .
A network entity 105 or a UE 115 may use beam sweeping techniques as part of beamforming operations. For example, a network entity 105 (e.g., a base station 140, an RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to conduct beamforming operations for directional communications with a UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted by a network entity 105 multiple times along different directions. For example, the network entity 105 may transmit a signal according to different beamforming weight sets associated with different directions of transmission. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as a network entity 105, or by a receiving device,
such as a UE 115) a beam direction for later transmission or reception by the network entity 105.
Some signals, such as data signals associated with a particular receiving device, may be transmitted by transmitting device (e.g., a transmitting network entity 105, a transmitting UE 115) along a single beam direction (e.g., a direction associated with the receiving device, such as a receiving network entity 105 or a receiving UE 115) . In some examples, the beam direction associated with transmissions along a single beam direction may be determined based on a signal that was transmitted along one or more beam directions. For example, a UE 115 may receive one or more of the signals transmitted by the network entity 105 along different directions and may report to the network entity 105 an indication of the signal that the UE 115 received with a highest signal quality or an otherwise acceptable signal quality.
In some examples, transmissions by a device (e.g., by a network entity 105 or a UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from a network entity 105 to a UE 115) . The UE 115 may report feedback that indicates precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more sub-bands. The network entity 105 may transmit a reference signal (e.g., a cell-specific reference signal (CRS) , a channel state information reference signal (CSI-RS) ) , which may be precoded or unprecoded. The UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook) . Although these techniques are described with reference to signals transmitted along one or more directions by a network entity 105 (e.g., a base station 140, an RU 170) , a UE 115 may employ similar techniques for transmitting signals multiple times along different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE 115) or for transmitting a signal along a single direction (e.g., for transmitting data to a receiving device) .
A receiving device (e.g., a UE 115) may perform reception operations in accordance with multiple receive configurations (e.g., directional listening) when receiving various signals from a receiving device (e.g., a network entity 105) , such as
synchronization signals, reference signals, beam selection signals, or other control signals. For example, a receiving device may perform reception in accordance with multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as “listening” according to different receive configurations or receive directions. In some examples, a receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal) . The single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR) , or otherwise acceptable signal quality based on listening according to multiple beam directions) .
The wireless communications system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. An RLC layer may perform packet segmentation and reassembly to communicate via logical channels. A MAC layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer also may implement error detection techniques, error correction techniques, or both to support retransmissions to improve link efficiency. In the control plane, an RRC layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a network entity 105 or a core network 130 supporting radio bearers for user plane data. A PHY layer may map transport channels to physical channels.
The UEs 115 and the network entities 105 may support retransmissions of data to increase the likelihood that data is received successfully. Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly via a communication link (e.g., a communication link 125, a D2D communication link 135) . HARQ may include a combination of error detection (e.g.,
using a cyclic redundancy check (CRC) ) , forward error correction (FEC) , and retransmission (e.g., automatic repeat request (ARQ) ) . HARQ may improve throughput at the MAC layer in poor radio conditions (e.g., low signal-to-noise conditions) . In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific slot for data received via a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.
In some examples, as described herein, a network entity 105 may configure the UE 115 to log LCM operations, together with associated conditions under which the UE performed the LCM operations, and then report the logged information to the network entity. The UE 115 may log and report LCM operations for AI/ML models, functionalities, or both (e.g., for model-ID based LCM decisions and functionality-based LCM decisions) . LCM decisions may include model or functionality selection, activation, deactivation, switching, and fallback. In some examples, the start and stop time for logging the information may be determined and configured by the network entity. In some examples, the UE 115 may also be configured to report statistics corresponding to the logged information (e.g., instead of or along with raw measurements and data) .
FIG. 2 shows an example of a wireless communications system 200 that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure. The wireless communications system 200 may implement aspects of, or be implemented by aspects of, the wireless communications system 100. For example, the wireless communications system 200 may include a network entity 105-a and a UE 115-a, which may be examples of corresponding devices described with reference to FIG. 1.
The UE 115-a and the network entity 105-a may communicate with each other via a wireless communication link 205. In some examples, the UE 115-a may enter a radio resource control (RRC) idle state or RRC inactive state. Upon exiting the RRC idle state or inactive state, the UE 115-a may perform initial access (e.g., a synchronization signal block (SSB) beam (e.g., wide beam) sweeping) . The UE 115-a may successfully perform initial access, and ay perform beam management in an RRC connected state. Beam management may include beam prediction to identify and utilize
beams without experience a beam failure or a link failure via the selected beams. If the UE experience a beam failure detection based on one or more measurements, the UE may perform beam failure recovery.
Beam management in an RRC connected state may include receiving one or more reference signals for measurement and reporting (e.g., SSBs, CSI-RSs, SRSs, etc. ) , channel quality reporting (e.g., reference signal receive power (RSRP) reporting) , and TCI state configuration and indications (e.g., beam selection, configuration, and use) . Beam management may also include SINR reporting, overhead and latency reduction e.g., CC group beam updates, faster uplink beam updates, etc. ) . In some examples, beam management may include efficiency enhancements, including unified TCI states, layer 1 or layer 2 centric mobility, dynamic TCI updates, uplink multi-panel use and selection, MPE mitigation, or the like. Beam management may also be applied to multi-transmission reception point (mTRP) scenarios.
In the case of beam failure recovery, the UE 115-a may perform beam failure detection, and beam failure recovery for various cells (e.g., primary cell (PCell, primary secondary cell (PSCell) , which may include beam failure detection via beam failure detection reference signals and physical downlink control channel (PDCCH) block error rate (BLER) as described in greater detail with reference to FIG. 3. For a secondary cell (SCell) , the UE may perform beam failure detention similar to such procedure for an SCell. The UE 115-a may transmit a scheduling request (SR) , or a media access control (MAC) control element (CE) based on the beam failure request for the SCell.
In some examples, the UE 115-a may support AI or ML procedures (AI/ML) for air-interface corresponding to various target use cases regarding aspects of communications such as performance, complexity, etc. For example, use cases may include beam management (e.g., beam prediction in time and/or spatial domain for overhead and latency reduction, beam selection accuracy improvement) among other examples. AI/ML approaches to various use cases or sub use cases may be diverse enough to support various procedures and collaborations between the UE 115-a and the network entity 105-a. AI/ML models may support common and specific characteristics in various frameworks, including lifecycle management of AI/ML models (e.g., model training, model deployment, model interference, model monitoring, and model updating, among other examples) .
In some examples, the UE 115-a and the network entity 105-a may perform beam management or beam selection using AI/ML models or functionalities. For instance, for AI/ML based beam management, the UE 115-a may support a first case (e.g., beam management (BM) case 1) and a second case (BM case 2) . In BM case 1, the UE 115-a may perform spatial domain downlink beam prediction for a first set of beams (e.g., set A) based on measurement results of a second set of beams (e.g., set B) . In BM case 2, the UE 115-a may perform temporal domain downlink beam prediction for a first set of beams (e.g., set A) based on measurement results of a second set of beams (e.g., set B) . Set A and Set B may be in the same frequency range, or different frequency range. The UE 115-a may perform actual measurement for one or more beams (e.g., set B) , and may use AI/ML models to predict a second set of beams (e.g., set A) for communications via the communication link 205.
In some examples, the UE 115-a may perform one or more LCM operations (e.g., decisions) for an AI/ML model or functionality. LCM operations may be based at least in part on the basis that an AIML model has a model identifier (ID) with associated information, or model functionality at least for some AI/ML operations/procedures. Model IDs may be associated with information and/or model functionality. Usage of model IDs with associated information or model functionality may be based on LCM procedures. In some examples, for UE-side models, or for functionality-based LCM procedures, indications of activation of LCM operations (e.g., activation, deactivation, switching, or fallback behaviors for a given AI/ML) for an AI/ML functionality or AI/ML ID may be exchanged between the network entity 105-a and the UE 115-a. For Model-ID based LCM operations, the UE 115-a and the network entity 105-a may indicate LCM operations such as model selection, activation, deactivation, switching, of fallback procedures, based on individual model IDs.
LCM methodologies may include functionality-based LCM operations. In such examples, the network entity 105-a may be aware of (e.g., may have access to information regarding) AI/ML functionality at the UE 115-a via UE capability reporting. The UE 115-a may report its capability to support one or more AI/ML functionalities (e.g., beam prediction, beam management, channel prediction, mobility operations, among other examples) . Each AI/ML functionality may correspond to a reference signal configuration from the network entity, and one or more AI/ML IDs
(e.g., a single AI/ML model with a first AI/ML model ID may correspond to a low-doppler beam prediction AI/ML functionality, and a second AI/ML model with a second AI/ML model ID may correspond to a high-doppler beam prediction of the same AI/ML functionality) . During an inference phase of the AI/ML functionality, the network entity 105-a may control AI/ML functionality at the UE 115-a. For example, the network entity 105-a may instruct the UE 115-a to perform one or more LCM operations (e.g., activate, deactivate, switch, default, among other examples) for a reported AI/ML functionality. The controlling may refer to functionality selection, activation, deactivation, switching, falling back, or monitoring, among other examples.
LCM methodologies may include model ID based LCM operations. In such examples, AI/ML models are registered at the network entity 105 with mode IDs. For example, the network entity 105-a may configure, or the UE 115-a may report, an indication of one or more model IDs supported by the UE 115-a. The model IDs may or may not correspond to AI/ML functionalities. The network entity 105-a may be aware of (e.g., have access to information regarding) the model IDs supported by the UE 115-a based on capability signaling from the UE 115-a (e.g., indicating which AI/ML model IDs the UE 115-a supports) .
The UE may have one AI/ML model for a given AI/ML functionality, or may have multiple AI/ML models for the functionality. Functionalities may be indicated via identifiers, or by name or term, or may be defined via a table, bitmap, or other indication (e.g., and may be indicated via signaling or defined in one or more standards, or a combination thereof) .
Both model ID based and functionality based LCM management methodologies may result in implications in terms of phases of ML workflow, and including data collection, interference, and model monitoring, as described herein.
In some examples, for LCM operations (e.g., model selection, activation, deactivation, switching, and fallback) for a UE side AI/ML model or two-sided model, the network entity 105-a or the UE 115-a may initiate or determine the LCM operations For example, the network entity 105-a may determine LCM operations (e.g., may determine whether the UE 115-a is to activate or deactivate a ML model or functionality) . The network entity 105-a may perform network-initiated LCM
operations, or the UE 115-a may perform UE-initiated LCM decisions (e.g., may request the LCM operation, and the network entity 105-a may transmit an acknowledgment or approval indication of the requested LCM decision) . IN some examples, the decision may be performed by the UE 115-a. For example, the UE 115-a may perform event-triggered LCM decisions (e.g., as configured by the network entity 105-a) , and the UE 115-a may report the LCM decision to the network entity 105-a. In some examples, the UE 115-a may perform anonymous LCM decisions, reported to the network entity 105-a, or may perform anonymous LCM decisions, and may not report the decision to the network entity 105-a.
The UE 115-a may perform LCM decisions (e.g., may activate, deactivate, switch between, etc., one or more AI/ML models, or functionalities) . However, without a mechanism to determine the switching, the network entity 105-a may make erroneous resource allocations, or may default to signaling related AI/ML functionalities that are not applicable if the UE 115-a has defaulted to fallback procedures that do not implement AI/ML functionalities or models. Such misaligned signaling and techniques may result in inefficient use of system resources, unreliable communications, increased system latency, and decreased user experience.
In some examples, as described herein, the network entity 105-a may configure (e.g., via the configuration information 210) the UE 115-a to log LCM decisions together with associated conditions, and then report the logged data to the network entity 105-a (e.g., via the report 215) . The UE 115-a may log and report LCM decisions for AI/ML models, functionalities, or both (e.g., for model-ID based LCM decisions and functionality-based LCM decisions) . LCM decisions may include model or functionality selection, activation, deactivation, switching, and fallback. The network entity 105-a may be configured to use the LCM decisions reported by the UE 115-a to improve its configurations and signaling to the UE 115-a and other UEs.
In some examples, the start and stop time for logging the information may be determined and configured by the network entity 105-a. For example, the network entity 105-a may configure the UE 115-a (e.g., via the configuration information 210) with a time window, time duration, or an initiation time and expiration time, during which the UE 115-a is to log any LCM decisions and the corresponding conditions under which the LCM decisions was taken. Upon expiration of the time window (e.g., at the ending
time) , the UE 115-a may report (e.g., transmit the report 215) some or all of the logged LCM decisions and corresponding conditions for each LCM decision.
In some example, the network entity 105-a may also configure the UE 115-a to perform one or more additional operations on the logged information before reporting. For example, the UE 115-a may compute one or more statistics related to the logged information (e.g., which may reduce signaling overhead if the UE 115-a is configured to report statistics instead of raw data or raw measurements) .
In some examples, the conditions logged by the UE 115-a and reported in the report 215 may include a UE location (e.g. at the time of the LCM decision) . The UE 115-a may log the location associated with the LCM decision and then report the log to network entity 105-a. Such reporting configurations may support reporting of relevant information without exposing user privacy information (e.g., real-time UE locations may not be shared, only logged locations over a period of time may be shared in the report 215) .
In some examples, the conditions logged by the UE 115-a and reported in the report 215 may include a zone ID indicating location information corresponding to the LCM decision. For example, upon each monitoring decision, the UE 115-a may log the associated zone ID. Such information may be helpful at the network entity 105-a (e.g., the network entity 105-a may deduce that certain zone IDs are more susceptible to AI/ML model/functionality deactivation) . For instance, the network entity 105-a may determine that zone IDs closer to cell edge are more susceptible to AI/ML model/functionality deactivation and may use this information in the future.
In some examples, the conditions logged by the UE 115-a and reported in the report 215 may include a UE mobility state. Such information may include information about quantized UE speed and may provide the network entity 105-a useful information about which mobility conditions may lead to more AI/ML model/functionality deactivations.
In some examples, the conditions logged by the UE 115-a and reported in the report 215 may include an RSRP range. For certain ranges of RSRP, an AI/ML model or functionality may not be performing well and may be deactivated. Logging this
information may give the network entity 105-a more visibility into the non-applicable conditions for AI/ML model/functionality.
In some examples, the conditions logged by the UE 115-a and reported in the report 215 may include a time of day at which the UE 115-a made the LCM decision. For example, logging information about time of day (e.g., in urban environments) may be useful. For instance, during daytime a given venue may be crowded and hence more susceptible to beam blockage and AI/ML model or functionality deactivation.
In some examples, the conditions logged by the UE 115-a and reported in the report 215 may include a blockage event. For example, if model deactivation at the UE 115-a is a result of beam failure detection, this may be logged and reported to the network entity 105-a. For instance, the UE 115-a may report that out of a total quantity (e.g., 100) of AI/ML model or functionality deactivations during the logging period, a quantity or percentage (e.g., 40%) were due to beam failure or detected blockages.
In some examples, the UE 115-a may include, in the report 215, statistical information related to the LCM decisions, accompanied by the associated conditions, as opposed to the real-time indications of LCM decisions, resulting in overhead savings. The report 215 may include the logged information. In some examples, the report 215 may be a single MAC-CE message or a single RRC message, or may be multiple MAC-CE message or multiple RRC messages, or any combination thereof.
FIG. 3 shows an example of a process flow 300 that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure. The process flow may implement aspects of, or be implemented by aspects of, the wireless communications system 100 and the wireless communications system 200. For example, the process flow may include a UE 115-b and a network entity 105-a, which may be examples of corresponding devices described with reference to FIGs 1-2.
At 305, the UE 115-b may receive (e.g., from the network entity 105-b) , control signaling indicating a scheme for reporting feedback information about using ML models or ML functionality to maintain a wireless communication link. The control signaling may be an example of the configuration information described with reference to FIG. 2.
At 310, the UE 115-b may perform one or more operations (e.g., LCM decisions or operations, such as to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link) based at least in part on receiving the control signaling at 305. The control signaling may include an indication (e.g., an instruction) to include the one or more conditions in an operation report transmitted at 320. The conditions may include one or more current parameter values or scenarios in which the UE 115-b performs a given LCM operation. The one or more operations may include activating an AI/ML model or functionality, deactivating an AI/ML model or functionality, switching from a first AI/ML model or functionality to a second AI/ML model or functionality, switching to a default AI/ML model or functionality or to a default behavior that does not rely on AI/ML models or functionalities, or any combination thereof, among other examples.
The conditions corresponding to a given LCM operation may include a UE location at a timing of performing the one or more operations, a zone ID associated with a location of the UE 115-b when performing the one or more operations, a UE mobility state associated with the timing of performing the one or more operations, an RSRP range associated with performing the one or more operations, a blockage event corresponding to the one or more operations, or any combination thereof.
At 315, the UE 115-b may log the one or more operations and the one or more conditions corresponding to the one or more operations at a local memory of the UE 115-b. The UE 115-b may then retrieve the one or more operations and the one or more conditions corresponding to the one or more operations from the local memory, and include the retrieved operations and conditions in the operation report at 320.
In some examples, the control signaling at 305 may include an indication of a starting time and an ending time for logging the one or more operations and the one or more conditions corresponding to the one or more operations, and the UE 115-b may log the operations and conditions at 315 between the starting time and ending time.
In some examples, the control signaling at 305 may include a request (e.g., an instruction) to provide statistical information associated with the one or more operations in the operation report at 320. The UE 115-b may generate the statistical
information based at least in part on receiving the request, and may include the generated statistical information in the operation report at 320.
At 320, the UE 115-b may transmit the operation report. The operation report may include the logged operations, and the conditions correspond to each logged operation, the statistical information corresponding to logged information, or any combination thereof. The report may be a MAC-CE message, or an RRC message, among other examples.
FIG. 4 shows a block diagram 400 of a device 405 that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure. The device 405 may be an example of aspects of a UE 115 as described herein. The device 405 may include a receiver 410, a transmitter 415, and a communications manager 420. The device 405 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
The receiver 410 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to logging and signaling of operations for ML LCM) . Information may be passed on to other components of the device 405. The receiver 410 may utilize a single antenna or a set of multiple antennas.
The transmitter 415 may provide a means for transmitting signals generated by other components of the device 405. For example, the transmitter 415 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to logging and signaling of operations for ML LCM) . In some examples, the transmitter 415 may be co-located with a receiver 410 in a transceiver module. The transmitter 415 may utilize a single antenna or a set of multiple antennas.
The communications manager 420, the receiver 410, the transmitter 415, or various combinations thereof or various components thereof may be examples of means for performing various aspects of logging and signaling of operations for ML LCM as
described herein. For example, the communications manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may support a method for performing one or more of the functions described herein.
In some examples, the communications manager 420, the receiver 410, the transmitter 415, 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) , a central processing unit (CPU) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, 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. In some examples, a processor and memory coupled with the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory) .
Additionally, or alternatively, in some examples, the communications manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure) .
In some examples, the communications manager 420 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 410, the transmitter 415, or both. For example, the communications manager 420 may receive information from the receiver 410, send information to the transmitter 415, or be integrated in combination with the receiver 410, the transmitter 415, or both to obtain information, output information, or perform various other operations as described herein.
The communications manager 420 may support wireless communications at a UE in accordance with examples as disclosed herein. For example, the communications manager 420 is capable of, configured to, or operable to support a means for receiving control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link. The communications manager 420 is capable of, configured to, or operable to support a means for performing one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link based on receiving the control signaling. The communications manager 420 is capable of, configured to, or operable to support a means for transmitting, according to the scheme, an operation report including an indication of the one or more operations and one or more conditions corresponding to the one or more operations.
By including or configuring the communications manager 420 in accordance with examples as described herein, the device 405 (e.g., a processor controlling or otherwise coupled with the receiver 410, the transmitter 415, the communications manager 420, or a combination thereof) may support techniques for logging and reporting LCM operations and corresponding conditions, resulting in more efficient use of system resources, increased reliability of communications, decreased system latency, and improved user experience.
FIG. 5 shows a block diagram 500 of a device 505 that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure. The device 505 may be an example of aspects of a device 405 or a UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communications manager 520. The device 505 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
The receiver 510 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to logging and signaling of operations for ML LCM) . Information may be passed on to other components of the device 505. The receiver 510 may utilize a single antenna or a set of multiple antennas.
The transmitter 515 may provide a means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to logging and signaling of operations for ML LCM) . In some examples, the transmitter 515 may be co-located with a receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or a set of multiple antennas.
The device 505, or various components thereof, may be an example of means for performing various aspects of logging and signaling of operations for ML LCM as described herein. For example, the communications manager 520 may include an ML model reporting manager 525, an LCM operation manager 530, an operation report manager 535, or any combination thereof. The communications manager 520 may be an example of aspects of a communications manager 420 as described herein. In some examples, the communications manager 520, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 510, the transmitter 515, or both. For example, the communications manager 520 may receive information from the receiver 510, send information to the transmitter 515, or be integrated in combination with the receiver 510, the transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.
The communications manager 520 may support wireless communications at a UE in accordance with examples as disclosed herein. The ML model reporting manager 525 is capable of, configured to, or operable to support a means for receiving control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link. The LCM operation manager 530 is capable of, configured to, or operable to support a means for performing one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link based on receiving the control signaling. The operation report manager 535 is capable of, configured to, or operable to support a means for transmitting, according to the scheme, an operation report including an
indication of the one or more operations and one or more conditions corresponding to the one or more operations.
FIG. 6 shows a block diagram 600 of a communications manager 620 that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure. The communications manager 620 may be an example of aspects of a communications manager 420, a communications manager 520, or both, as described herein. The communications manager 620, or various components thereof, may be an example of means for performing various aspects of logging and signaling of operations for ML LCM as described herein. For example, the communications manager 620 may include an ML model reporting manager 625, an LCM operation manager 630, an operation report manager 635, an operation condition manager 640, a logging manager 645, a statistical information manager 650, or any combination thereof. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses) .
The communications manager 620 may support wireless communications at a UE in accordance with examples as disclosed herein. The ML model reporting manager 625 is capable of, configured to, or operable to support a means for receiving control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link. The LCM operation manager 630 is capable of, configured to, or operable to support a means for performing one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link based on receiving the control signaling. The operation report manager 635 is capable of, configured to, or operable to support a means for transmitting, according to the scheme, an operation report including an indication of the one or more operations and one or more conditions corresponding to the one or more operations.
In some examples, the operation condition manager 640 is capable of, configured to, or operable to support a means for receiving, via the control signaling, a second indication to include the one or more conditions in the operation report, where transmitting the operation report including the one or more conditions is based on receiving the second indication.
In some examples, the logging manager 645 is capable of, configured to, or operable to support a means for logging the one or more operations and the one or more conditions corresponding to the one or more operations at a local memory of the UE. In some examples, the logging manager 645 is capable of, configured to, or operable to support a means for retrieving the one or more operations and the one or more conditions corresponding to the one or more operations from the local memory, where transmitting the operation report is based on the logging and the retrieving.
In some examples, the logging manager 645 is capable of, configured to, or operable to support a means for receiving, via the control signaling, a second indication of a starting time and an ending time for logging the one or more operations and the one or more conditions corresponding to the one or more operations, where the logging is based on the starting time and the ending time.
In some examples, the statistical information manager 650 is capable of, configured to, or operable to support a means for receiving, via the control signaling, a request to provide statistical information associated with the one or more operations. In some examples, the statistical information manager 650 is capable of, configured to, or operable to support a means for generating the statistical information based on receiving the request, where the operation report includes the statistical information.
In some examples, the one or more conditions corresponding to the one or more operations include a UE location at a timing of performing the one or more operations, a zone identifier associated with a location of the UE when performing the one or more operations, a UE mobility state associated with the timing of performing the one or more operations, a reference signal receive power range associated with performing the one or more operations, a blockage event corresponding to the one or more operations, or any combination thereof.
In some examples, the operation report includes a radio resource control message or a MAC control element (CE) .
In some examples, activating or deactivating the functionality of the at least one ML model includes switching from a first functionality of the at least one ML model to a second functionality of a second ML model.
In some examples, activating or deactivating the functionality includes activating or deactivating a first ML model corresponding to the functionality or switching from the first ML model corresponding to the functionality to a second ML model corresponding to the functionality.
FIG. 7 shows a diagram of a system 700 including a device 705 that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure. The device 705 may be an example of or include the components of a device 405, a device 505, or a UE 115 as described herein. The device 705 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 705 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 720, an input/output (I/O) controller 710, a transceiver 715, an antenna 725, a memory 730, code 735, and a processor 740. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 745) .
The I/O controller 710 may manage input and output signals for the device 705. The I/O controller 710 may also manage peripherals not integrated into the device 705. In some cases, the I/O controller 710 may represent a physical connection or port to an external peripheral. In some cases, the I/O controller 710 may utilize an operating system such as
or another known operating system. Additionally or alternatively, the I/O controller 710 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I/O controller 710 may be implemented as part of a processor, such as the processor 740. In some cases, a user may interact with the device 705 via the I/O controller 710 or via hardware components controlled by the I/O controller 710.
In some cases, the device 705 may include a single antenna 725. However, in some other cases, the device 705 may have more than one antenna 725, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 715 may communicate bi-directionally, via the one or more antennas 725, wired, or wireless links as described herein. For example, the transceiver 715 may
represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 715 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 725 for transmission, and to demodulate packets received from the one or more antennas 725. The transceiver 715, or the transceiver 715 and one or more antennas 725, may be an example of a transmitter 415, a transmitter 515, a receiver 410, a receiver 510, or any combination thereof or component thereof, as described herein.
The memory 730 may include random access memory (RAM) and read-only memory (ROM) . The memory 730 may store computer-readable, computer-executable code 735 including instructions that, when executed by the processor 740, cause the device 705 to perform various functions described herein. The code 735 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 735 may not be directly executable by the processor 740 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the memory 730 may contain, 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.
The processor 740 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) . In some cases, the processor 740 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the processor 740. The processor 740 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 730) to cause the device 705 to perform various functions (e.g., functions or tasks supporting logging and signaling of operations for ML LCM) . For example, the device 705 or a component of the device 705 may include a processor 740 and memory 730 coupled with or to the processor 740, the processor 740 and memory 730 configured to perform various functions described herein.
The communications manager 720 may support wireless communications at a UE in accordance with examples as disclosed herein. For example, the communications manager 720 is capable of, configured to, or operable to support a
means for receiving control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link. The communications manager 720 is capable of, configured to, or operable to support a means for performing one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link based on receiving the control signaling. The communications manager 720 is capable of, configured to, or operable to support a means for transmitting, according to the scheme, an operation report including an indication of the one or more operations and one or more conditions corresponding to the one or more operations.
By including or configuring the communications manager 720 in accordance with examples as described herein, the device 705 may support techniques for logging and reporting LCM operations and corresponding conditions, resulting in more efficient use of system resources, increased reliability of communications, decreased system latency, and improved user experience.
In some examples, the communications manager 720 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 715, the one or more antennas 725, or any combination thereof. Although the communications manager 720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 720 may be supported by or performed by the processor 740, the memory 730, the code 735, or any combination thereof. For example, the code 735 may include instructions executable by the processor 740 to cause the device 705 to perform various aspects of logging and signaling of operations for ML LCM as described herein, or the processor 740 and the memory 730 may be otherwise configured to perform or support such operations.
FIG. 8 shows a block diagram 800 of a device 805 that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure. The device 805 may be an example of aspects of a network entity 105 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communications manager 820. The device 805 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
The receiver 810 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) . Information may be passed on to other components of the device 805. In some examples, the receiver 810 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 810 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
The transmitter 815 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 805. For example, the transmitter 815 may output information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) . In some examples, the transmitter 815 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 815 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 815 and the receiver 810 may be co-located in a transceiver, which may include or be coupled with a modem.
The communications manager 820, the receiver 810, the transmitter 815, or various combinations thereof or various components thereof may be examples of means for performing various aspects of logging and signaling of operations for ML LCM as described herein. For example, the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may support a method for performing one or more of the functions described herein.
In some examples, the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) . The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a
microcontroller, 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. In some examples, a processor and memory coupled with the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory) .
Additionally, or alternatively, in some examples, the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure) .
In some examples, the communications manager 820 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 810, the transmitter 815, or both. For example, the communications manager 820 may receive information from the receiver 810, send information to the transmitter 815, or be integrated in combination with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.
The communications manager 820 may support wireless communications at a network entity in accordance with examples as disclosed herein. For example, the communications manager 820 is capable of, configured to, or operable to support a means for transmitting control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link with a UE. The communications manager 820 is capable of, configured to, or operable to support a means for receiving, according to the scheme, an operation report including an indication of one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link and one or more
conditions corresponding to the one or more operations. The communications manager 820 is capable of, configured to, or operable to support a means for communicating with the UE via the wireless communication link based on receiving the operation report.
By including or configuring the communications manager 820 in accordance with examples as described herein, the device 805 (e.g., a processor controlling or otherwise coupled with the receiver 810, the transmitter 815, the communications manager 820, or a combination thereof) may support techniques for logging and reporting LCM operations and corresponding conditions, resulting in more efficient use of system resources, increased reliability of communications, decreased system latency, and improved user experience.
FIG. 9 shows a block diagram 900 of a device 905 that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure. The device 905 may be an example of aspects of a device 805 or a network entity 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communications manager 920. The device 905 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
The receiver 910 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) . Information may be passed on to other components of the device 905. In some examples, the receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 910 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
The transmitter 915 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 905. For example, the transmitter 915 may output information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets,
protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) . In some examples, the transmitter 915 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 915 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 915 and the receiver 910 may be co-located in a transceiver, which may include or be coupled with a modem.
The device 905, or various components thereof, may be an example of means for performing various aspects of logging and signaling of operations for ML LCM as described herein. For example, the communications manager 920 may include an LCM operation manager 925, an operation report manager 930, a communication functionality manager 935, or any combination thereof. The communications manager 920 may be an example of aspects of a communications manager 820 as described herein. In some examples, the communications manager 920, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 910, the transmitter 915, or both. For example, the communications manager 920 may receive information from the receiver 910, send information to the transmitter 915, or be integrated in combination with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.
The communications manager 920 may support wireless communications at a network entity in accordance with examples as disclosed herein. The LCM operation manager 925 is capable of, configured to, or operable to support a means for transmitting control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link with a UE. The operation report manager 930 is capable of, configured to, or operable to support a means for receiving, according to the scheme, an operation report including an indication of one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link and one or more conditions corresponding to the one or more operations. The communication
functionality manager 935 is capable of, configured to, or operable to support a means for communicating with the UE via the wireless communication link based on receiving the operation report.
FIG. 10 shows a block diagram 1000 of a communications manager 1020 that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure. The communications manager 1020 may be an example of aspects of a communications manager 820, a communications manager 920, or both, as described herein. The communications manager 1020, or various components thereof, may be an example of means for performing various aspects of logging and signaling of operations for ML LCM as described herein. For example, the communications manager 1020 may include an LCM operation manager 1025, an operation report manager 1030, a communication functionality manager 1035, an operation condition manager 1040, a logging information manager 1045, a statistical information manager 1050, or any combination thereof. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses) which may include communications within a protocol layer of a protocol stack, communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105) , or any combination thereof.
The communications manager 1020 may support wireless communications at a network entity in accordance with examples as disclosed herein. The LCM operation manager 1025 is capable of, configured to, or operable to support a means for transmitting control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link with a UE. The operation report manager 1030 is capable of, configured to, or operable to support a means for receiving, according to the scheme, an operation report including an indication of one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link and one or more conditions corresponding to the one or more operations. The communication functionality manager 1035 is capable of, configured to, or operable to support a means
for communicating with the UE via the wireless communication link based on receiving the operation report.
In some examples, the operation condition manager 1040 is capable of, configured to, or operable to support a means for transmitting, via the control signaling, a second indication to include the one or more conditions in the operation report, where receiving the operation report including the one or more conditions is based on transmitting the second indication.
In some examples, the logging information manager 1045 is capable of, configured to, or operable to support a means for transmitting, via the control signaling, a second indication of a starting time and an ending time for logging the one or more operations and the one or more conditions corresponding to the one or more operations, where receiving the operation report including the one or more conditions is based on transmitting the second indication of the starting time and the ending time.
In some examples, the statistical information manager 1050 is capable of, configured to, or operable to support a means for transmitting, via the control signaling, a request to provide statistical information associated with the one or more operations. In some examples, the statistical information manager 1050 is capable of, configured to, or operable to support a means for receiving, via the operation report, the statistical information based on transmitting the request.
In some examples, the one or more conditions corresponding to the one or more operations include a UE location at a timing of performing the one or more operations, a zone identifier associated with a location of the UE when performing the one or more operations, a UE mobility state associated with the timing of performing the one or more operations, a reference signal receive power range associated with performing the one or more operations, a blockage event corresponding to the one or more operations, or any combination thereof.
In some examples, the operation report includes a radio resource control message or a MAC control element (CE) .
In some examples, activating or deactivating the functionality of the at least one ML model includes switching from a first functionality of the at least one ML model to a second functionality of a second ML model.
In some examples, activating or deactivating the functionality includes activating or deactivating a first ML model corresponding to the functionality or switching from the first ML model corresponding to the functionality to a second ML model corresponding to the functionality.
FIG. 11 shows a diagram of a system 1100 including a device 1105 that supports logging and signaling of operations for ML LCM in accordance with one or more aspects of the present disclosure. The device 1105 may be an example of or include the components of a device 805, a device 905, or a network entity 105 as described herein. The device 1105 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communications over one or more wired interfaces, over one or more wireless interfaces, or any combination thereof. The device 1105 may include components that support outputting and obtaining communications, such as a communications manager 1120, a transceiver 1110, an antenna 1115, a memory 1125, code 1130, and a processor 1135. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1140) .
The transceiver 1110 may support bi-directional communications via wired links, wireless links, or both as described herein. In some examples, the transceiver 1110 may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver 1110 may include a wireless transceiver and may communicate bi-directionally with another wireless transceiver. In some examples, the device 1105 may include one or more antennas 1115, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently) . The transceiver 1110 may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas 1115, by a wired transmitter) , to receive modulated signals (e.g., from one or more antennas 1115, from a wired receiver) , and to demodulate signals. In some implementations, the transceiver 1110 may include one or more interfaces, such as
one or more interfaces coupled with the one or more antennas 1115 that are configured to support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas 1115 that are configured to support various transmitting or outputting operations, or a combination thereof. In some implementations, the transceiver 1110 may include or be configured for coupling with one or more processors or memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other outputting, or any combination thereof. In some implementations, the transceiver 1110, or the transceiver 1110 and the one or more antennas 1115, or the transceiver 1110 and the one or more antennas 1115 and one or more processors or memory components (for example, the processor 1135, or the memory 1125, or both) , may be included in a chip or chip assembly that is installed in the device 1105. In some examples, the transceiver may be operable to support communications via one or more communications links (e.g., a communication link 125, a backhaul communication link 120, a midhaul communication link 162, a fronthaul communication link 168) .
The memory 1125 may include RAM and ROM. The memory 1125 may store computer-readable, computer-executable code 1130 including instructions that, when executed by the processor 1135, cause the device 1105 to perform various functions described herein. The code 1130 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1130 may not be directly executable by the processor 1135 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the memory 1125 may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.
The processor 1135 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, discrete gate or transistor logic, a discrete hardware component, or any combination thereof) . In some cases, the processor 1135 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the processor 1135. The processor 1135 may
be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1125) to cause the device 1105 to perform various functions (e.g., functions or tasks supporting logging and signaling of operations for ML LCM) . For example, the device 1105 or a component of the device 1105 may include a processor 1135 and memory 1125 coupled with the processor 1135, the processor 1135 and memory 1125 configured to perform various functions described herein. The processor 1135 may be an example of a cloud-computing platform (e.g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code 1130) to perform the functions of the device 1105. The processor 1135 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1105 (such as within the memory 1125) . In some implementations, the processor 1135 may be a component of a processing system. A processing system may generally refer to a system or series of machines or components that receives inputs and processes the inputs to produce a set of outputs (which may be passed to other systems or components of, for example, the device 1105) . For example, a processing system of the device 1105 may refer to a system including the various other components or subcomponents of the device 1105, such as the processor 1135, or the transceiver 1110, or the communications manager 1120, or other components or combinations of components of the device 1105. The processing system of the device 1105 may interface with other components of the device 1105, and may process information received from other components (such as inputs or signals) or output information to other components. For example, a chip or modem of the device 1105 may include a processing system and one or more interfaces to output information, or to obtain information, or both. The one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or a same interface configured to output information and to obtain information, among other implementations. In some implementations, the one or more interfaces may refer to an interface between the processing system of the chip or modem and a transmitter, such that the device 1105 may transmit information output from the chip or modem. Additionally, or alternatively, in some implementations, the one or more interfaces may refer to an interface between the processing system of the chip or modem and a receiver, such that the device 1105 may
obtain information or signal inputs, and the information may be passed to the processing system. A person having ordinary skill in the art will readily recognize that a first interface also may obtain information or signal inputs, and a second interface also may output information or signal outputs.
In some examples, a bus 1140 may support communications of (e.g., within) a protocol layer of a protocol stack. In some examples, a bus 1140 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack) , which may include communications performed within a component of the device 1105, or between different components of the device 1105 that may be co-located or located in different locations (e.g., where the device 1105 may refer to a system in which one or more of the communications manager 1120, the transceiver 1110, the memory 1125, the code 1130, and the processor 1135 may be located in one of the different components or divided between different components) .
In some examples, the communications manager 1120 may manage aspects of communications with a core network 130 (e.g., via one or more wired or wireless backhaul links) . For example, the communications manager 1120 may manage the transfer of data communications for client devices, such as one or more UEs 115. In some examples, the communications manager 1120 may manage communications with other network entities 105, and may include a controller or scheduler for controlling communications with UEs 115 in cooperation with other network entities 105. In some examples, the communications manager 1120 may support an X2 interface within an LTE/LTE-A wireless communications network technology to provide communication between network entities 105.
The communications manager 1120 may support wireless communications at a network entity in accordance with examples as disclosed herein. For example, the communications manager 1120 is capable of, configured to, or operable to support a means for transmitting control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link with a UE. The communications manager 1120 is capable of, configured to, or operable to support a means for receiving, according to the scheme, an operation report including an indication of one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link and one or more
conditions corresponding to the one or more operations. The communications manager 1120 is capable of, configured to, or operable to support a means for communicating with the UE via the wireless communication link based on receiving the operation report.
By including or configuring the communications manager 1120 in accordance with examples as described herein, the device 1105 may support techniques for logging and reporting LCM operations and corresponding conditions, resulting in more efficient use of system resources, increased reliability of communications, decreased system latency, and improved user experience.
In some examples, the communications manager 1120 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver 1110, the one or more antennas 1115 (e.g., where applicable) , or any combination thereof. Although the communications manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1120 may be supported by or performed by the transceiver 1110, the processor 1135, the memory 1125, the code 1130, or any combination thereof. For example, the code 1130 may include instructions executable by the processor 1135 to cause the device 1105 to perform various aspects of logging and signaling of operations for ML LCM as described herein, or the processor 1135 and the memory 1125 may be otherwise configured to perform or support such operations.
FIG. 12 shows a flowchart illustrating a method 1200 that supports logging and signaling of operations for ML LCM in accordance with aspects of the present disclosure. The operations of the method 1200 may be implemented by a UE or its components as described herein. For example, the operations of the method 1200 may be performed by a UE 115 as described with reference to FIGs. 1 through 7. In some examples, a UE may execute a set of instructions to control the functional elements of the wireless UE to perform the described functions. Additionally, or alternatively, the wireless UE may perform aspects of the described functions using special-purpose hardware.
At 1205, the method may include receiving control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link. The operations of 1205 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1205 may be performed by an ML model reporting manager 625 as described with reference to FIG. 6.
At 1210, the method may include performing one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link based on receiving the control signaling. The operations of 1210 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1210 may be performed by an LCM operation manager 630 as described with reference to FIG. 6.
At 1215, the method may include transmitting, according to the scheme, an operation report including an indication of the one or more operations and one or more conditions corresponding to the one or more operations. The operations of 1215 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1215 may be performed by an operation report manager 635 as described with reference to FIG. 6.
FIG. 13 shows a flowchart illustrating a method 1300 that supports logging and signaling of operations for ML LCM in accordance with aspects of the present disclosure. The operations of the method 1300 may be implemented by a UE or its components as described herein. For example, the operations of the method 1300 may be performed by a UE 115 as described with reference to FIGs. 1 through 7. In some examples, a UE may execute a set of instructions to control the functional elements of the wireless UE to perform the described functions. Additionally, or alternatively, the wireless UE may perform aspects of the described functions using special-purpose hardware.
At 1305, the method may include receiving control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link. The operations of 1305 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1305
may be performed by an ML model reporting manager 625 as described with reference to FIG. 6.
At 1310, the method may include receiving, via the control signaling, a second indication to include the one or more conditions in the operation report, where transmitting the operation report including the one or more conditions is based on receiving the second indication. The operations of 1310 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed by an operation condition manager 640 as described with reference to FIG. 6.
At 1315, the method may include performing one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link based on receiving the control signaling. The operations of 1315 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed by an LCM operation manager 630 as described with reference to FIG. 6.
At 1320, the method may include transmitting, according to the scheme, an operation report including an indication of the one or more operations and one or more conditions corresponding to the one or more operations. The operations of 1320 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1320 may be performed by an operation report manager 635 as described with reference to FIG. 6.
FIG. 14 shows a flowchart illustrating a method 1400 that supports logging and signaling of operations for ML LCM in accordance with aspects of the present disclosure. The operations of the method 1400 may be implemented by a network entity or its components as described herein. For example, the operations of the method 1400 may be performed by a network entity as described with reference to FIGs. 1 through 3 and 8 through 11. In some examples, a network entity may execute a set of instructions to control the functional elements of the wireless network entity to perform the described functions. Additionally, or alternatively, the wireless network entity may perform aspects of the described functions using special-purpose hardware.
At 1405, the method may include transmitting control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link with a UE. The operations of 1405 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed by an LCM operation manager 1025 as described with reference to FIG. 10.
At 1410, the method may include receiving, according to the scheme, an operation report including an indication of one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link and one or more conditions corresponding to the one or more operations. The operations of 1410 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed by an operation report manager 1030 as described with reference to FIG. 10.
At 1415, the method may include communicating with the UE via the wireless communication link based on receiving the operation report. The operations of 1415 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed by a communication functionality manager 1035 as described with reference to FIG. 10.
FIG. 15 shows a flowchart illustrating a method 1500 that supports logging and signaling of operations for ML LCM in accordance with aspects of the present disclosure. The operations of the method 1500 may be implemented by a network entity or its components as described herein. For example, the operations of the method 1500 may be performed by a network entity as described with reference to FIGs. 1 through 3 and 8 through 11. In some examples, a network entity may execute a set of instructions to control the functional elements of the wireless network entity to perform the described functions. Additionally, or alternatively, the wireless network entity may perform aspects of the described functions using special-purpose hardware.
At 1505, the method may include transmitting control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link with a UE. The operations of 1505 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the
operations of 1505 may be performed by an LCM operation manager 1025 as described with reference to FIG. 10.
At 1510, the method may include transmitting, via the control signaling, a second indication to include the one or more conditions in the operation report, where receiving the operation report including the one or more conditions is based on transmitting the second indication. The operations of 1510 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed by an operation condition manager 1040 as described with reference to FIG. 10.
At 1515, the method may include receiving, according to the scheme, an operation report including an indication of one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link and one or more conditions corresponding to the one or more operations. The operations of 1515 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed by an operation report manager 1030 as described with reference to FIG. 10.
At 1520, the method may include communicating with the UE via the wireless communication link based on receiving the operation report. The operations of 1520 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1520 may be performed by a communication functionality manager 1035 as described with reference to FIG. 10.
The following provides an overview of aspects of the present disclosure:
Aspect 1: A method for wireless communications at a UE, comprising: receiving control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link; performing one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link based at least in part on receiving the control signaling; and transmitting, according to the scheme, an operation report comprising an indication of the one or more operations and one or more conditions corresponding to the one or more operations.
Aspect 2: The method of aspect 1, further comprising: receiving, via the control signaling, a second indication to include the one or more conditions in the operation report, wherein transmitting the operation report comprising the one or more conditions is based at least in part on receiving the second indication.
Aspect 3: The method of any of aspects 1 through 2, further comprising: logging the one or more operations and the one or more conditions corresponding to the one or more operations at a local memory of the UE; and retrieving the one or more operations and the one or more conditions corresponding to the one or more operations from the local memory, wherein transmitting the operation report is based at least in part on the logging and the retrieving.
Aspect 4: The method of aspect 3, further comprising: receiving, via the control signaling, a second indication of a starting time and an ending time for logging the one or more operations and the one or more conditions corresponding to the one or more operations, wherein the logging is based at least in part on the starting time and the ending time.
Aspect 5: The method of any of aspects 1 through 4, further comprising: receiving, via the control signaling, a request to provide statistical information associated with the one or more operations; and generating the statistical information based at least in part on receiving the request, wherein the operation report comprises the statistical information.
Aspect 6: The method of any of aspects 1 through 5, wherein the one or more conditions corresponding to the one or more operations comprise a UE location at a timing of performing the one or more operations, a zone identifier associated with a location of the UE when performing the one or more operations, a UE mobility state associated with the timing of performing the one or more operations, a reference signal receive power range associated with performing the one or more operations, a blockage event corresponding to the one or more operations, or any combination thereof.
Aspect 7: The method of any of aspects 1 through 6, wherein the operation report comprises a radio resource control message or a MAC control element (CE) .
Aspect 8: The method of any of aspects 1 through 7, wherein activating or deactivating the functionality of the at least one ML model comprises switching from a first functionality of the at least one ML model to a second functionality of a second ML model.
Aspect 9: The method of any of aspects 1 through 8, wherein activating or deactivating the functionality comprises activating or deactivating a first ML model corresponding to the functionality or switching from the first ML model corresponding to the functionality to a second ML model corresponding to the functionality.
Aspect 10: A method for wireless communications at a network entity, comprising: transmitting control signaling indicating a scheme for reporting feedback information about using ML models to maintain a wireless communication link with a UE; receiving, according to the scheme, an operation report comprising an indication of one or more operations to activate or deactivate a functionality of at least one ML model for maintaining the wireless communication link and one or more conditions corresponding to the one or more operations; and communicating with the UE via the wireless communication link based at least in part on receiving the operation report.
Aspect 11: The method of aspect 10, further comprising: transmitting, via the control signaling, a second indication to include the one or more conditions in the operation report, wherein receiving the operation report comprising the one or more conditions is based at least in part on transmitting the second indication.
Aspect 12: The method of any of aspects 10 through 11, further comprising: transmitting, via the control signaling, a second indication of a starting time and an ending time for logging the one or more operations and the one or more conditions corresponding to the one or more operations, wherein receiving the operation report comprising the one or more conditions is based at least in part on transmitting the second indication of the starting time and the ending time.
Aspect 13: The method of any of aspects 10 through 12, further comprising: transmitting, via the control signaling, a request to provide statistical information associated with the one or more operations; and receiving, via the operation report, the statistical information based at least in part on transmitting the request.
Aspect 14: The method of any of aspects 10 through 13, wherein the one or more conditions corresponding to the one or more operations comprise a UE location at a timing of performing the one or more operations, a zone identifier associated with a location of the UE when performing the one or more operations, a UE mobility state associated with the timing of performing the one or more operations, a reference signal receive power range associated with performing the one or more operations, a blockage event corresponding to the one or more operations, or any combination thereof.
Aspect 15: The method of any of aspects 10 through 14, wherein the operation report comprises a radio resource control message or a MAC control element (CE) .
Aspect 16: The method of any of aspects 10 through 15, wherein activating or deactivating the functionality of the at least one ML model comprises switching from a first functionality of the at least one ML model to a second functionality of a second ML model.
Aspect 17: The method of any of aspects 10 through 16, wherein activating or deactivating the functionality comprises activating or deactivating a first ML model corresponding to the functionality or switching from the first ML model corresponding to the functionality to a second ML model corresponding to the functionality.
Aspect 18: An apparatus for wireless communications at a UE, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 1 through 9.
Aspect 19: An apparatus for wireless communications at a UE, comprising at least one means for performing a method of any of aspects 1 through 9.
Aspect 20: A non-transitory computer-readable medium storing code for wireless communications at a UE, the code comprising instructions executable by a processor to perform a method of any of aspects 1 through 9.
Aspect 21: An apparatus for wireless communications at a network entity, comprising a processor; memory coupled with the processor; and instructions stored in
the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 10 through 17.
Aspect 22: An apparatus for wireless communications at a network entity, comprising at least one means for performing a method of any of aspects 10 through 17.
Aspect 23: A non-transitory computer-readable medium storing code for wireless communications at a network entity, the code comprising instructions executable by a processor to perform a method of any of aspects 10 through 17.
It should be noted that the methods described herein describe possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined.
Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB) , Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.
Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, 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 various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. 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 using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as or transmitted using one or more instructions or code of 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 location to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, 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. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc,
optical disc, digital versatile disc (DVD) , floppy disk and Blu-ray disc. Disks may reproduce data magnetically, and discs may reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.
As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” ) 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) . Also, as used herein, 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. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. ”
The term “determine” or “determining” encompasses a variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database or another data structure) , ascertaining and the like. Also, “determining” can include receiving (e.g., receiving information) , accessing (e.g., accessing data stored in memory) and the like. Also, “determining” can include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.
In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label, or other subsequent reference label.
The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration, ” and not “preferred” or
“advantageous over other examples. ” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.
The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.
Claims (30)
- An apparatus for wireless communications at a user equipment (UE) , comprising:a processor;memory coupled with the processor; andinstructions stored in the memory and executable by the processor to cause the apparatus to:receive control signaling indicating a scheme for reporting feedback information about using machine learning models to maintain a wireless communication link;perform one or more operations to activate or deactivate a functionality of at least one machine learning model for maintaining the wireless communication link based at least in part on receiving the control signaling; andtransmit, according to the scheme, an operation report comprising an indication of the one or more operations and one or more conditions corresponding to the one or more operations.
- The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to:receive, via the control signaling, a second indication to include the one or more conditions in the operation report, wherein transmitting the operation report comprising the one or more conditions is based at least in part on receiving the second indication.
- The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to:log the one or more operations and the one or more conditions corresponding to the one or more operations at a local memory of the UE; andretrieve the one or more operations and the one or more conditions corresponding to the one or more operations from the local memory, wherein transmitting the operation report is based at least in part on the logging and the retrieving.
- The apparatus of claim 3, wherein the instructions are further executable by the processor to cause the apparatus to:receive, via the control signaling, a second indication of a starting time and an ending time for logging the one or more operations and the one or more conditions corresponding to the one or more operations, wherein the logging is based at least in part on the starting time and the ending time.
- The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to:receive, via the control signaling, a request to provide statistical information associated with the one or more operations; andgenerate the statistical information based at least in part on receiving the request, wherein the operation report comprises the statistical information.
- The apparatus of claim 1, wherein the one or more conditions corresponding to the one or more operations comprise a UE location at a timing of performing the one or more operations, a zone identifier associated with a location of the UE when performing the one or more operations, a UE mobility state associated with the timing of performing the one or more operations, a reference signal receive power range associated with performing the one or more operations, a blockage event corresponding to the one or more operations, or any combination thereof.
- The apparatus of claim 1, wherein the operation report comprises a radio resource control message or a media access control (MAC) control element (CE) .
- The apparatus of claim 1, wherein activating or deactivating the functionality of the at least one machine learning model comprises switching from a first functionality of the at least one machine learning model to a second functionality of a second machine learning model.
- The apparatus of claim 1, wherein activating or deactivating the functionality comprises activating or deactivating a first machine learning model corresponding to the functionality or switching from the first machine learning model corresponding to the functionality to a second machine learning model corresponding to the functionality.
- An apparatus for wireless communications at a network entity, comprising:a processor;memory coupled with the processor; andinstructions stored in the memory and executable by the processor to cause the apparatus to:transmit control signaling indicating a scheme for reporting feedback information about using machine learning models to maintain a wireless communication link with a user equipment (UE) ;receive, according to the scheme, an operation report comprising an indication of one or more operations to activate or deactivate a functionality of at least one machine learning model for maintaining the wireless communication link and one or more conditions corresponding to the one or more operations; andcommunicate with the UE via the wireless communication link based at least in part on receiving the operation report.
- The apparatus of claim 10, wherein the instructions are further executable by the processor to cause the apparatus to:transmit, via the control signaling, a second indication to include the one or more conditions in the operation report, wherein receiving the operation report comprising the one or more conditions is based at least in part on transmitting the second indication.
- The apparatus of claim 10, wherein the instructions are further executable by the processor to cause the apparatus to:transmit, via the control signaling, a second indication of a starting time and an ending time for logging the one or more operations and the one or more conditions corresponding to the one or more operations, wherein receiving the operation report comprising the one or more conditions is based at least in part on transmitting the second indication of the starting time and the ending time.
- The apparatus of claim 10, wherein the instructions are further executable by the processor to cause the apparatus to:transmit, via the control signaling, a request to provide statistical information associated with the one or more operations; andreceive, via the operation report, the statistical information based at least in part on transmitting the request.
- The apparatus of claim 10, wherein the one or more conditions corresponding to the one or more operations comprise a UE location at a timing of performing the one or more operations, a zone identifier associated with a location of the UE when performing the one or more operations, a UE mobility state associated with the timing of performing the one or more operations, a reference signal receive power range associated with performing the one or more operations, a blockage event corresponding to the one or more operations, or any combination thereof.
- The apparatus of claim 10, wherein the operation report comprises a radio resource control message or a media access control (MAC) control element (CE) .
- The apparatus of claim 10, wherein activating or deactivating the functionality of the at least one machine learning model comprises switching from a first functionality of the at least one machine learning model to a second functionality of a second machine learning model.
- The apparatus of claim 10, wherein activating or deactivating the functionality comprises activating or deactivating a first machine learning model corresponding to the functionality or switching from the first machine learning model corresponding to the functionality to a second machine learning model corresponding to the functionality.
- A method for wireless communications at a user equipment (UE) , comprising:receiving control signaling indicating a scheme for reporting feedback information about using machine learning models to maintain a wireless communication link;performing one or more operations to activate or deactivate a functionality of at least one machine learning model for maintaining the wireless communication link based at least in part on receiving the control signaling; andtransmitting, according to the scheme, an operation report comprising an indication of the one or more operations and one or more conditions corresponding to the one or more operations.
- The method of claim 18, further comprising:receiving, via the control signaling, a second indication to include the one or more conditions in the operation report, wherein transmitting the operation report comprising the one or more conditions is based at least in part on receiving the second indication.
- The method of claim 18, further comprising:logging the one or more operations and the one or more conditions corresponding to the one or more operations at a local memory of the UE; andretrieving the one or more operations and the one or more conditions corresponding to the one or more operations from the local memory, wherein transmitting the operation report is based at least in part on the logging and the retrieving.
- The method of claim 20, further comprising:receiving, via the control signaling, a second indication of a starting time and an ending time for logging the one or more operations and the one or more conditions corresponding to the one or more operations, wherein the logging is based at least in part on the starting time and the ending time.
- The method of claim 18, further comprising:receiving, via the control signaling, a request to provide statistical information associated with the one or more operations; andgenerating the statistical information based at least in part on receiving the request, wherein the operation report comprises the statistical information.
- The method of claim 18, wherein the one or more conditions corresponding to the one or more operations comprise a UE location at a timing of performing the one or more operations, a zone identifier associated with a location of the UE when performing the one or more operations, a UE mobility state associated with the timing of performing the one or more operations, a reference signal receive power range associated with performing the one or more operations, a blockage event corresponding to the one or more operations, or any combination thereof.
- A method for wireless communications at a network entity, comprising:transmitting control signaling indicating a scheme for reporting feedback information about using machine learning models to maintain a wireless communication link with a user equipment (UE) ;receiving, according to the scheme, an operation report comprising an indication of one or more operations to activate or deactivate a functionality of at least one machine learning model for maintaining the wireless communication link and one or more conditions corresponding to the one or more operations; andcommunicating with the UE via the wireless communication link based at least in part on receiving the operation report.
- The method of claim 24, further comprising:transmitting, via the control signaling, a second indication to include the one or more conditions in the operation report, wherein receiving the operation report comprising the one or more conditions is based at least in part on transmitting the second indication.
- The method of claim 24, further comprising:transmitting, via the control signaling, a second indication of a starting time and an ending time for logging the one or more operations and the one or more conditions corresponding to the one or more operations, wherein receiving the operation report comprising the one or more conditions is based at least in part on transmitting the second indication of the starting time and the ending time.
- The method of claim 24, further comprising:transmitting, via the control signaling, a request to provide statistical information associated with the one or more operations; andreceiving, via the operation report, the statistical information based at least in part on transmitting the request.
- The method of claim 24, wherein the one or more conditions corresponding to the one or more operations comprise a UE location at a timing of performing the one or more operations, a zone identifier associated with a location of the UE when performing the one or more operations, a UE mobility state associated with the timing of performing the one or more operations, a reference signal receive power range associated with performing the one or more operations, a blockage event corresponding to the one or more operations, or any combination thereof.
- The method of claim 24, wherein the operation report comprises a radio resource control message or a media access control (MAC) control element (CE) .
- The method of claim 24, wherein activating or deactivating the functionality of the at least one machine learning model comprises switching from a first functionality of the at least one machine learning model to a second functionality of a second machine learning model.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2023/086829 WO2024207406A1 (en) | 2023-04-07 | 2023-04-07 | Logging and signaling of operations for machine learning life-cycle management |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2023/086829 WO2024207406A1 (en) | 2023-04-07 | 2023-04-07 | Logging and signaling of operations for machine learning life-cycle management |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2024207406A1 true WO2024207406A1 (en) | 2024-10-10 |
Family
ID=92970844
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2023/086829 WO2024207406A1 (en) | 2023-04-07 | 2023-04-07 | Logging and signaling of operations for machine learning life-cycle management |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2024207406A1 (en) |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104904260A (en) * | 2012-11-05 | 2015-09-09 | 瑞典爱立信有限公司 | Systems and methods for controlling logging and reporting under constraints |
WO2022222089A1 (en) * | 2021-04-22 | 2022-10-27 | Qualcomm Incorporated | Machine learning model reporting, fallback, and updating for wireless communications |
-
2023
- 2023-04-07 WO PCT/CN2023/086829 patent/WO2024207406A1/en unknown
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104904260A (en) * | 2012-11-05 | 2015-09-09 | 瑞典爱立信有限公司 | Systems and methods for controlling logging and reporting under constraints |
WO2022222089A1 (en) * | 2021-04-22 | 2022-10-27 | Qualcomm Incorporated | Machine learning model reporting, fallback, and updating for wireless communications |
Non-Patent Citations (2)
Title |
---|
JUN CHEN, HUAWEI, HISILICON: "Discussion on AIML methods", 3GPP DRAFT; R2-2212226; TYPE DISCUSSION; FS_NR_AIML_AIR, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Toulouse, FR; 20221114 - 20221118, 4 November 2022 (2022-11-04), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052216310 * |
JUN CHEN, HUAWEI, HISILICON: "Discussion on AIML methods", 3GPP DRAFT; R2-2301577; TYPE DISCUSSION; FS_NR_AIML_AIR, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Athens, GR; 20230227 - 20230303, 17 February 2023 (2023-02-17), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052246211 * |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20240089976A1 (en) | Sidelink-assisted node verification | |
US20230319931A1 (en) | Multi-path beam failure reporting techniques | |
WO2024207406A1 (en) | Logging and signaling of operations for machine learning life-cycle management | |
WO2024207418A1 (en) | Event-triggered activation and deactivation of machine learning functionality | |
WO2024197782A1 (en) | Transmission configuration indicator states for spatial beam prediction | |
WO2024192612A1 (en) | Beam correspondence conditions with joint beam pair prediction | |
WO2024092688A1 (en) | Techniques for uplink time alignment timer management for multiple transmission-reception points | |
US20240250737A1 (en) | Autonomous uplink beam selection and activation | |
WO2024036465A1 (en) | Beam pair prediction and indication | |
US20240022311A1 (en) | Slot aggregation triggered by beam prediction | |
WO2024031517A1 (en) | Unified transmission configuration indication determination for single frequency network | |
WO2023184062A1 (en) | Channel state information resource configurations for beam prediction | |
WO2024065372A1 (en) | Methods and apparatuses for reporting csi prediction for a set of beams | |
WO2024164106A1 (en) | Scheduling for frequency bands associated with a first band changing capability after a transmit chain switch | |
WO2024065373A1 (en) | Techniques for dynamically triggered csi reports carrying time-domain beam predictions | |
WO2024168657A1 (en) | Asymmetric confidence level for predictive beam management | |
WO2024000221A1 (en) | Transmission configuration indicator state selection for reference signals in multi transmission and reception point operation | |
WO2024059960A1 (en) | Uplink and downlink beam reporting | |
US20240098759A1 (en) | Common time resources for multicasting | |
US20240236873A1 (en) | Reduced power headroom reporting with configured grants | |
WO2024026603A1 (en) | Idle state quality of experience activation and reporting | |
WO2024026617A1 (en) | Default power parameters per transmission and reception point | |
US20240072980A1 (en) | Resource indicator values for guard band indications | |
WO2024178705A1 (en) | Beam application time for unified transmission configuration indicator states | |
US20240349280A1 (en) | Methods for symbol aggregation to enable adaptive beam weight communications |