Model-based predictive interference management

Abstract

Apparatuses, methods, and systems are disclosed for model-based predictive interference management. One method includes receiving at least one monitoring report from a device. The method includes determining a monitoring event report based on a subscription and the at least one monitoring report. The method includes providing the monitoring event report to an application.

Description

TECHNICAL FIELD

[0001] The subject matter disclosed herein relates generally to wireless communications, and more particularly to model-based predictive interference management. BACKGROUND

[0002] The following acronyms are defined herein, at least some of which are referenced in the following description: Third Generation Partnership Project (“3GPP”), Fifth Generation (“5G”), 5G System (“5GS”), QoS for NR V2X communications (“5QI / PQI”), Authentication, Authorization, and Accounting (“AAA”), Acknowledgement (“ACK”), Artificial Intelligence (“AI”), Application Function (“AF”), Authentication and Key Agreement (“AKA”), Aggregation Level (“AL”), Access and Mobility Management Function (“AMF”), Angle of Arrival (“AoA”), Angle of Departure (“AoD”), Access Point (“AP”), Application Programming Interface (“API”), Application Server (“AS”), Application Service Provider (“ASP”), Autonomous Uplink (“AUL”), Authentication Server Function (“AUSF”), Authentication Token (“AUTN”), Background Data (“BD”), Background Data Transfer (“BDT”), Beam Failure Detection (“BFD”), Beam Failure Recovery (“BFR”), Backhaul (“BH”), Binary Phase Shift Keying (“BPSK”), Base Station (“BS”), Buffer Status Report (“BSR”), Bandwidth (“BW”), Bandwidth Part (“BWP”), Cloud - Resource Access Network (“C-RAN”), Cell RNTI (“C-RNTI”), Carrier Aggregation (“CA”), Channel Access Priority Class (“CAPC”), Coordinated Beamforming (“CB”), Contention-Based Random Access (“CBRA”), Clear Channel Assessment (“CCA”), Common Control Channel (“CCCH”), Control Channel Element (“CCE”), Cyclic Delay Diversity (“CDD”), Code Division Multiple Access (“CDMA”), Control Element (“CE”), Contention-Free Random Access (“CFRA”), Configured Grant (“CG”), Closed Loop (“CL”), Connected Mode Mobility Control (“CMC”), Coordinated Multipoint (“CoMP”), Channel Occupancy Time (“COT”), Cyclic Prefix (“CP”), Channel Quality Indicator (“CQI”), Cyclic Redundancy Check (“CRC”), Coordinated Scheduling (“CS”), Channel State Information (“CSI”), Channel State Information - Reference Signal (“CSI-RS”), Common Search Space (“CSS”), Control Resource Set (“CORESET”), Central Unit (“CU”), Device-to-Device (“D2D”), Discrete Fourier Transform Spread (“DFTS”), Downlink Control Information (“DCI”), Downlink Feedback Information (“DFI”), Downlink (“DL”), Demodulation Reference Signal (“DMRS”), Data Network Name (“DNN”), Dynamic Resource Allocation (“DRA”), Data Radio Bearer (“DRB”), Discontinuous Reception (“DRX”), Dedicated Short-Range Communications (“DSRC”), Distributed Unit (“DU”), Downlink Pilot Time Slot (“DwPTS”),Evolved Universal Terrestrial Access Network (“E-UTRAN”), E2 Terminal (“E2T”), Enhanced Clear Channel Assessment (“eCCA”), Enhanced Mobile Broadband (“eMBB”), Evolved Node B (“eNB”), Extensible Authentication Protocol (“EAP”), Enhanced Inter-Cell Interference Coordination (“eICIC”), Effective Isotropic Radiated Power (“EIRP”), European Telecommunications Standards Institute (“ETSI”), Frame Based Equipment (“FBE”), Frequency Division Duplex (“FDD”), Frequency Division Multiplex (“FDM”), Frequency Division Multiple Access (“FDMA”), Frequency Division Orthogonal Cover Code (“FD-OCC”), Fractional Frequency Reuse (“FFR”), Further Enhanced Inter-Cell Interference Coordination (“FeICIC”), Frequency Range 1 - Sub 6 GHz bands and / or 410 MHz to 7125 MHz (“FR1”), Frequency Range 2 - 24.25 GHz to 52.6 GHz (“FR2”), Generic Area Description (“GAD”), Guaranteed Bit Rate (“GBR”), Group Long (“GL”), 5G Node B or Next Generation Node B (“gNB”), Global Navigation Satellite System (“GNSS”), General Packet Radio Service (“GPRS”), Guard Period (“GP”), Global Positioning System (“GPS”), Generic Public Subscription Identifier (“GPSI”), Global System for Mobile communications (“GSM”), Globally Unique Temporary UE Identifier (“GUTI”), Home AMF (“hAMF”), Hybrid Automatic Repeat Request (“HARQ”), Heterogeneous Network (“HetNet”), High Interference Indicator (“HII”), Home Location Register (“HLR”), Handover (“HO”), Home PLMN (“HPLMN”), Home Subscriber Server (“HSS”), Hash Expected Response (“HXRES”), Inter-Cell Interference Coordination (“ICIC”), Identity or Identifier (“ID”), Information Element (“IE”), Industrial Internet of Things (“IIoT”), Interference Management (“IM”), International Mobile Equipment Identity (“IMEI”), International Mobile Subscriber Identity (“IMSI”), International Mobile Telecommunications (“IMT”), Internet of Things (“IoT”), Joint Reception (“JR”), Joint Transmission (“JT”), Key Management Function (“KMF”), Key Performance Indicators (“KPI”), Layer 1 (“L1”), Layer 2 (“L2”), Layer 3 (“L3”), License Assisted Access (“LAA”), Local Area Data Network (“LADN”), Local Area Network (“LAN”), Load Balancing (“LB”), Load Based Equipment (“LBE”), Listen-Before-Talk (“LBT”), Logical Channel (“LCH”), Logical Channel Group (“LCG”), Logical Channel Priority (“LCP”), Log Likelihood Ratio (“LLR”), Long Term Evolution (“LTE”), LTE Advanced (“LTE-A”), Multiple Access (“MA”),Media Access Control (“MAC”), Multimedia Broadcast Multicast Service (“MBMS”), Maximum Bit Rate (“MBR”), Minimum Communication Range (“MCR”), Modulation Coding Scheme (“MCS”), Master Information Block (“MIB”), Multimedia Internet Keying (“MIKEY”), Multiple Input Multiple Output (“MIMO”), Machine Learning (“ML”), Mobility Management (“MM”), Mobility Management Entity (“MME”), Mobile Network Operator (“MNO”), Mobile Originated (“MO”), Massive MTC (“mMTC”), Maximum Power Reduction (“MPR”), Machine Type Communication (“MTC”), Multi-User Shared Access (“MUSA”), Non-Access Stratum (“NAS”), Narrowband (“NB”), Negative Acknowledgement (“NACK”) or (“NAK”), New Data Indicator (“NDI”), Network Entity (“NE”), Network Exposure Function (“NEF”), Network Function (“NF”), Next Generation (“NG”), NG 5G S-TMSI (“NG-5G-S-TMSI”), Non-Orthogonal Multiple Access (“NOMA”), New Radio (“NR”), Unlicensed NR (“NR-U”), Network Repository Function (“NRF”), Network Scheduled Mode (“NS Mode”) (e.g., network scheduled mode for V2X communication resource allocation - Mode-1 in NR V2X and Mode-3 in LTE V2X), Network Slice Instance (“NSI”), Network Slice Selection Assistance Information (“NSSAI”), Network Slice Selection Function (“NSSF”), Network Slice Selection Policy (“NSSP”), Operations, Administration, and Maintenance system or Operation and Maintenance Center (“OAM”), O-RAN CU Control Plane (“O-CU-CP”), O-RAN CU User Plane (“O-CU-CP”), O-RAN DU (“O-DU”), Orthogonal Frequency Division Multiplexing (“OFDM”), Overload Indication (“OI”), Open Loop (“OL”), Open RAN (“O-RAN”), Other System Information (“OSI”), Power Angle Spectrum (“PAS”), Physical Broadcast Channel (“PBCH”), Power Control (“PC”), UE-to-UE interface (“PC5”), Policy and Charging Control (“PCC”), Primary Cell (“PCell”), Policy Control Function (“PCF”), Physical Cell Identity (“PCI”), Physical Downlink Control Channel (“PDCCH”), Packet Data Convergence Protocol (“PDCP”), Packet Data Network Gateway (“PGW”), Physical Downlink Shared Channel (“PDSCH”), Pattern Division Multiple Access (“PDMA”), Packet Data Unit (“PDU”), Physical Hybrid-ARQ Indicator Channel (“PHICH”), Power Headroom (“PH”), Power Headroom Report (“PHR”), Physical Layer (“PHY”),Public Land Mobile Network (“PLMN”), PC5 QoS Class Identifier (“PQI”), Physical Random Access Channel (“PRACH”), Physical Resource Block (“PRB”), Proximity Service (“ProSe”), Location Reference Signal (“PRS”), Physical Sidelink Control Channel (“PSCCH”), Primary and Secondary Cell (“PSCell”), Physical Sidelink Feedback Control Channel (“PSFCH”), Physical Uplink Control Channel (“PUCCH”), Physical Uplink Shared Channel (“PUSCH”), QoS Class Identifier (“QCI”), Quasi-Co-location (“QCL”), Quality of Experience (“QoE”), Quality of Service (“QoS”), Quadrature Phase Shift Keying (“QPSK”), Registration Area (“RA”), RA RNTI (“RA-RNTI”), Radio Access Network (“RAN”), Radio Access Network – Control Plane (“RANCP”), Random (“RAND”), Radio Access Network – User Plane (“RAN”) UP), Radio Access Technology (“RAT”), Service RAT (“RAT-1”) (regarding Uu service), Other RAT (“RAT-2”) (regarding Uu no service), Radio License Control (“RAC”), Random Access Procedure (“RACH”), Random Access Preamble Identifier (“RAPID”), Random Access Response (“RAR”), Resource Block (“RB”), Resource Block Assignment (“RBA”), Radio Bearer Control (“RBC”), Resource Element Group (“REG”), Radio Access Network Intelligent Controller (“RIC”), Radio Link Control (“RLC”), RLC Acknowledgment Mode (“RLC-AM”), RLC Unacknowledgment Mode / Transparent Mode (“RLC-UM / TM”), Radio Link Failure (“RLF”), Radio Link Monitoring (“RLM”), Radio Network Temporary Identifier (“RNTI”), Relative Narrowband TX Power (“RNTP”), Reference Signal (“RS”), Residual Minimum System Information (“RMSI”), Radio Resource Control (“RRC”), Radio Resource Management (“RRM”), Resource Extended Multiple Access (“RSMA”), Received Reference Signal Power (“RSRP”), Received Signal Strength Indicator (“RSSI”), Real-Time (“RT”), Round-Trip Time (“RTT”), Receive (“RX”), Sparse Code Multiple Access (“SCMA”), Scheduling Request (“SR”), Sound Reference Signal (“SRS”), Single Carrier Frequency Division Multiple Access (“SC-FDMA”), Secondary Cell (“SCell”), Secondary Cell Group (“SCG”), Shared Channel (“SCH”), Sidelink Control Information (“SCI”), Subcarrier Spacing (“SCS”), Software Defined Networking (“SDN”), Serving Data Unit (“SDU”), Security Anchor Function (“SEAF”).sidelink feedback content information (“SFCI”), soft frequency reuse (“SFR”), serving gateway (“SGW”), system information block (“SIB”), system information block type 1 (“SIB1”), system information block type 2 (“SIB2”), subscriber identity / identity module (“SIM”), signal-to-interference-plus-noise ratio (“SINR”), sidelink (“SL”), service level agreement (“SLA”), sidelink synchronization signal (“SLSS”), session management (“SM”), session management function (“SMF”), self-organizing network (“SON”), specific cell (“SpCell”), single-network slice selection assistance information (“S-NSSAI”), scheduling request (“SR”), signaling radio bearer (“SRB”), shortened-TMSI (“S-TMSI”), shortened TTI (“sTTI”), synchronization signal (“SS”), sidelink CSI RS (“S-CSI RS”), sidelink PRS (“S-PRS”), sidelink SSB (“S-SSB”), synchronization signal block (“SSB”), subscription concealed identifier (“SUCI”), scheduled user equipment (“SUE”), supplementary uplink (“SUL”), subscriber permanent identifier (“SUPI”), tracking area (“TA”), TA identifier (“TAI”), TA update (“TAU”), timing alignment timer (“TAT”), transport block (“TB”), transport block size (“TBS”), time division duplex (“TDD”), time division multiplex (“TDM”), time division orthogonal cover code (“TD-OCC”), temporary mobile subscriber identity (“TMSI”), time of flight (“ToF”), transmit power control (“TPC”), transmission reception point (“TRP”), transmission time interval (“TTI”), transmit (“TX”), uplink control information (“UCI”), unified data management function (“UDM”), ultra-dense network (“UDN”), unified data repository (“UDR”), user equipment / device (mobile terminal) (“UE”) (e.g., V2X UE), UE autonomous mode (UE autonomously selects V2X communication resources - e.g., mode 2 in NR V2X and mode 4 in LTE V2X. UE autonomous selection can or can not be based on resource sensing operations), uplink (“UL”), UL SCH (“UL-SCH”), universal mobile telecommunications system (“UMTS”), user plane (“UP”), UP function (“UPF”), uplink pilot time slot (“UpPTS”), ultra-reliability low-latency communications (“URLLC”), UE route selection policy (“URSP”), vehicle-to-vehicle (“V2V”), vehicle-to-everything (“V2X”), V2X UE (e.g., a UE capable of vehicular communication using 3GPP protocols), access AMF (“vAMF”),V2X encryption key (“VEK”), V2X group key (“VGK”), V2X MIKEY key (“VMK”), visiting NSSF (“vNSSF”), visiting PLMN (“VPLMN”), V2X traffic key (“VTK”), wide area network (“WAN”), and worldwide interoperability for microwave access (“WiMAX”).

[0003] In certain wireless communications networks, interference can occur. SUMMARY

[0004] A model-based predictive interference management method is disclosed. Apparatuses and systems also perform the functions of the method. One embodiment of a method includes receiving modeling information corresponding to a device, where the modeling information includes traffic parameters, radio parameters, mobility parameters, or some combination thereof, and the modeling information includes at least one machine learning model. In some embodiments, the method includes determining, for the device, a predicted inter-cell interference management policy based on the modeling information. In certain embodiments, the method includes providing the predicted inter-cell interference management policy to the device.

[0005] An apparatus for model-based predictive interference management includes a receiver that receives modeling information corresponding to a device, where the modeling information includes traffic parameters, radio parameters, mobility parameters, or some combination thereof, and the modeling information includes at least one machine learning model. In various embodiments, the apparatus includes a processor that: determines, for the device, a predicted inter-cell interference management policy based on the modeling information; and provides the predicted inter-cell interference management policy to the device.

[0006] Another embodiment of a method for model-based predictive interference management includes receiving at least one monitoring report from a device. In some embodiments, the method includes determining a monitoring event report based on a subscription and the at least one monitoring report. In certain embodiments, the method includes providing the monitoring event report to an application.

[0007] Another apparatus for model-based predictive interference management includes a receiver that receives at least one monitoring report from a device. In various embodiments, the apparatus includes a processor that: determines a monitoring event report based on a subscription and the at least one monitoring report; and provides the monitoring event report to an application.

[0008] Yet another embodiment of a method for model-based predictive interference management includes sending at least one monitoring report. In some embodiments, the method includes receiving information corresponding to a predicted inter-cell interference management policy in response to sending the at least one monitoring report.

[0009] Yet another apparatus for model-based predictive interference management includes a transmitter that transmits at least one monitoring report. In certain embodiments, the apparatus includes a receiver that receives information corresponding to a predictive inter-cell interference management strategy in response to transmitting the at least one monitoring report.

[0010] Another embodiment of a method for model-based predictive interference management includes transmitting an initial configuration. In various embodiments, the method includes receiving a request for modeling information in response to transmitting the initial configuration. In some embodiments, the method includes transmitting the modeling information in response to receiving the request, where the modeling information includes traffic parameters, radio parameters, mobility parameters, or some combination thereof, and the modeling information includes at least one machine learning model.

[0011] Another apparatus for model-based predictive interference management includes a transmitter that transmits an initial configuration. In certain embodiments, the apparatus includes a receiver that receives a request for modeling information in response to transmitting the initial configuration; where the transmitter transmits the modeling information in response to receiving the request, where the modeling information includes traffic parameters, radio parameters, mobility parameters, or some combination thereof, and the modeling information includes at least one machine learning model.

[0012] Further embodiments of a method for model-based predictive interference management include receiving a predictive resource management strategy from at least one application. In various embodiments, the method includes determining at least one radio parameter corresponding to the predictive resource management strategy. In some embodiments, the method includes transmitting the at least one radio parameter to a device based on the predictive resource management strategy.

[0013] A further apparatus for model-based predictive interference management includes a receiver that receives a predictive resource management strategy from at least one application. In certain embodiments, the apparatus includes a processor that determines at least one radio parameter corresponding to the predictive resource management strategy. In various embodiments, the apparatus includes a transmitter that transmits the at least one radio parameter to a device based on the predictive resource management strategy. BRIEF DESCRIPTION OF DRAWINGS

[0014] A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered to be limiting of the scope, embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

[0015] Figure 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for model-based predictive interference management;

[0016] Figure 2 is a schematic block diagram illustrating one embodiment of an apparatus that can be used for model-based predictive interference management;

[0017] Figure 3 is a schematic block diagram illustrating one embodiment of an apparatus that can be used for model-based predictive interference management;

[0018] Figure 4 is a diagram illustrating one embodiment of a system for interference management;

[0019] Figure 5 is a diagram illustrating another embodiment of a system for interference management;

[0020] Figure 6 is a diagram illustrating one embodiment of communications for interference management;

[0021] Figure 7 is a diagram illustrating another embodiment of communications for interference management;

[0022] Figure 8 is a flow diagram illustrating one embodiment of a method for model-based predictive interference management;

[0023] Figure 9 is a flow diagram illustrating another embodiment of a method for model-based predictive interference management;

[0024] Figure 10 is a flow diagram illustrating yet another embodiment of a method for model-based predictive interference management;

[0025] Figure 11 is a flow diagram illustrating a further embodiment of a method for model-based predictive interference management; and

[0026] Figure 12 is a flow diagram illustrating another embodiment of a method for model-based predictive interference management. DETAILED DESCRIPTION

[0027] As those skilled in the art will appreciate, the various aspects of the embodiments can be embodied as a system, apparatus, method, or program product. Accordingly, the embodiments can take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that can all generally be referred to herein as a "circuit," "module" or "system." Furthermore, the embodiments can take the form of a program product embodied in one or more computer-readable storage devices having stored thereon computer- readable code (i.e., program code) that, when executed by a computer, can implement the steps described herein. The program code can be stored in any type of computer-readable storage device or medium that is suitable for program code storage, including a non-transitory computer-readable storage device. The program code can be executed by one or more processors to implement the steps described herein.

[0028] Certain of the functional units described in this specification can be labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module can be implemented as a hardware circuit comprising custom very-large-scale integration ("VLSI") circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module can also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

[0029] Modules can also be implemented in code and / or software for execution by various types of processors. An identified module of code may, for instance, include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but can include disparate instructions stored in different locations which, when joined logically together, include the module and achieve the stated purpose for the module.

[0030] Indeed, a module of code can be a single instruction, or many instructions, and can even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data can be identified within the modules and illustrated as being stored in memory, but such data can be stored in any

[0031] Any combination of one or more computer-readable media can be utilized. The computer-readable media can be computer-readable storage media. The computer- readable storage media can be storage devices. Storage devices can be, for example, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor systems, apparatuses, or devices, or any suitable combination of the foregoing.

[0032] More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory ("RAM"), a read-only memory ("ROM"), an erasable programmable read-only memory ("EPROM" or Flash memory), a portable compact disc read-only memory ("CD-ROM"), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0033] Code for carrying out operations for embodiments can be any number of lines and can be written in any combination of one or more programming languages including an object- oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the "C" programming language, assembly language, or machine code. The code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network ("LAN") or a wide area network ("WAN"), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0034] Reference throughout this specification to "an embodiment", "embodiments", or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases "in one embodiment", "in embodiments", and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean "one or more but not all embodiments". Unless otherwise noted, the terms "including", "comprising", "having" and variations thereof herein are intended to be broad and encompass the terms "consisting of" and "consisting essentially of". Unless otherwise noted, lists of items should be construed as though each item in the list is individually and independently listed. Unless otherwise noted, multiple occurrences of the same term should not be construed as limitations of each occurrence to the same meaning.

[0035] Furthermore, features of the described embodiments can be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of the embodiments. One skilled in the relevant art will recognize, however, that the embodiments can be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail in order to avoid obscuring aspects of the embodiments.

[0036] Aspects of the embodiments are described below with reference to schematic flowcharts and / or schematic block diagrams of methods, apparatuses, systems, and program products according to the embodiments. It will be understood that each block of the schematic flowcharts and / or schematic block diagrams, and combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. The code can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the

[0037] The code can also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function / act specified in the schematic flowchart diagrams and / or schematic block diagrams block or blocks.

[0038] The code can also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions / acts specified in the flowchart diagrams and / or block diagrams block or blocks.

[0039] The schematic flowcharts and / or schematic block diagrams in the drawings show the architectural, functional, and operational views of possible implementations of apparatuses, systems, methods, and program products according to the different embodiments. In this regard, each block in the schematic flowcharts and / or schematic block diagrams can represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that the schematic flowcharts and / or schematic block diagrams can represent methods, apparatuses, systems, and program products according to the embodiments.

[0040] It should also be noted that in some alternative implementations, the functions noted in the blocks can occur out of the order noted in the figures. For example, two blocks shown in succession can in fact be executed substantially concurrently or the blocks can sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods can be conceived that are equivalent in function, logic, or effect to those illustrated, or portions thereof.

[0041] Although various arrow types and line types can be employed in the flow- chart and / or block diagrams, these are merely meant as graphical representations of

[0042] The description of elements in each figure can refer to elements of the preceding figures. Like reference numbers in all figures can indicate like elements, including like elements of alternative embodiments.

[0043] Figure 1 Embodiments of a wireless communication system 100 for model-based predictive interference management are depicted. In one embodiment, the wireless communication system 100 includes remote units 102 and network units 104. While Figure 1 A specific number of remote units 102 and network units 104 are depicted in the drawing figures, but one of skill in the art will recognize that any number of remote units 102 and network units 104 can be included in the wireless communication system 100.

[0044] In one embodiment, a remote unit 102 can include a computing device, such as a desktop computer, laptop computer, personal digital assistant (“PDA”), tablet computer, smart phone, smart television (e.g., a television connected to the Internet), set-top box, game console, security system (including security cameras), vehicle In some embodiments, the remote units 102 include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, etc. Moreover, the remote units 102 can be referred to as subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, UE, user terminals, devices, or by other terminology used in the art. The remote units 102 can communicate directly with one or more of the network units 104 via UL communication signals. In certain embodiments, the remote units 102 can communicate directly with other remote units 102 via sidelink communication.

[0045] The network units 104 can be distributed over a geographic region. In certain embodiments, a network unit 104 can also be referred to as an access point, an access terminal, a base, a base station, a Node-B, an eNB, a gNB, a Home Node-B, a relay node, a device, a core network, an aerial server, a radio access node, an AP, NR, a network entity, an AMF, a UDM, a UDR, a UDM / UDR, a PCF, a RAN, a NSSF, an AS, a NEF, a key management server, a KMF, a middleware device, a middleware entity, a middleware function, NR, subscription management, subscription management function, conflict mitigation, conflict mitigation function, an IM xAPP, a near RT RIC, a non-RT RIC, a service and / or management plane, a near RT RIC framework function, or by any other terminology used in the art and / or herein. The network units 104 are generally part of a radio access network, which is communicationally coupled to one or more core networks. The radio access network is typically communicationally coupled to one or more core networks, which can be coupled to other networks, like the Internet and public switched telephone networks, among other networks. These and other elements of radio access and core networks are not illustrated but are well known generally by those having ordinary skill in the art.

[0046] In one implementation, the wireless communication system 100 is compliant with the NR protocols standardized in 3GPP, where the network units 104 transmit using OFDM modulation scheme on the DL and the remote units 102 transmit on the UL using a SC-FDMA scheme or an OFDM scheme. More generally, however, the wireless communication system 100 can implement some other open or proprietary communication protocol, for example, WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA2000, ZigBee, Sigfoxx, among other protocols. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

[0047] The network units 104 can serve a number of remote units 102 within a serving area, for example, a cell or a cell sector via a wireless communication link. The network units 104 transmit DL communication signals to serve the remote units 102 in the time, frequency, and / or spatial domain.

[0048] In various embodiments, the network unit 104 can receive modeling information corresponding to a device, where the modeling information includes traffic parameters, radio parameters, mobility parameters, or some combination thereof, and the modeling information includes at least one machine learning model. In some embodiments, the network unit 104 can determine a predictive inter-cell interference management policy for the device based on the modeling information. In certain embodiments, the network unit 104 can provide the predictive inter-cell interference management policy to the device. Thus, the network unit 104 can be used for model-based predictive interference management.

[0049] In some examples, the network unit 104 can receive at least one monitoring report from a device. In various embodiments, the network unit 104 can determine a monitoring event report based on the subscription and the at least one monitoring report. In certain embodiments, the network unit 104 can provide the monitoring event report to an application. Thus, the network unit 104 can be used for model-based predictive interference management.

[0050] In certain embodiments, the network unit 104 can transmit at least one monitoring report. In various embodiments, the network unit 104 can receive information corresponding to a predictive inter-cell interference management policy in response to transmitting the at least one monitoring report. Thus, the network unit 104 can be used for model-based predictive interference management.

[0051] In various embodiments, the network unit 104 can transmit an initial configuration. In some embodiments, the network unit 104 can receive a request for modeling information in response to transmitting the initial configuration. In certain embodiments, the network unit 104 can transmit the modeling information in response to receiving the request, where the modeling information includes traffic parameters, radio parameters, mobility parameters, or some combination thereof, and the modeling information includes at least one machine learning model. Thus, the network unit 104 can be used for model-based predictive interference management.

[0052] In some examples, the network unit 104 can receive a predictive resource management policy from at least one application. In various embodiments, the network unit 104 can determine at least one radio parameter corresponding to the predictive resource management policy. In some embodiments, the network unit 104 can transmit the at least one radio parameter based on the predictive resource management policy to a device. Thus, the network unit 104 can be used for model-based predictive interference management.

[0053] Figure 2One embodiment of an apparatus 200 that can be used for model-based predictive interference management is depicted. The apparatus 200 includes one embodiment of the remote unit 102. Furthermore, the remote unit 102 can include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, the input device 206 and the display 208 are combined into a single device, such as a touch screen. In certain embodiments, the remote unit 102 can not include any input device 206 and / or display 208. In various embodiments, the remote unit 102 can include one or more of the processor 202, the memory 204, the transmitter 210, and the receiver 212, and can not include the input device 206 and / or the display 208.

[0054] In one embodiment, the processor 202 can include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, the processor 202 can be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, the processor 202 executes instructions stored in the memory 204 to perform methods and routines described herein. The processor 202 is communicatively coupled to the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212.

[0055] In one embodiment, the memory 204 is a computer readable storage medium. In some embodiments, the memory 204 includes both volatile and nonvolatile computer storage media. For example, the memory 204 can include both a volatile RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”), and non-volatile memory, including flash memory, hard drives, or any other suitable non-volatile computer storage devices. In some embodiments, the memory 204 includes a volatile and / or non-volatile memory that is managed by the processor 202. In some embodiments, the memory 204 also stores program code and related data, such as an operating system or other controller algorithms operating on the remote unit 102.

[0056] In one embodiment, input device 206 can include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. In some embodiments, input device 206 can be integrated with display 208, e.g., as a touchscreen or similar touch-sensitive display. In some embodiments, input device 206 includes a touchscreen such that text can be input using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, input device 206 includes two or more different devices, such as a keyboard and a touch panel.

[0057] In one embodiment, display 208 can include any known electronically controllable display or display device. Display 208 can be designed to output visual, audible, and / or tactile signals. In some embodiments, display 208 includes an electronic display capable of outputting visual data to a user. For example, display 208 can include, but is not limited to, an LCD display, a LED display, an OLED display, a projector, or similar display devices capable of outputting images, text, etc. to a user. As another non-limiting example, display 208 can include a wearable display such as a smart watch, smart glasses, a heads-up display, or the like. Further, display 208 can be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.

[0058] In certain embodiments, display 208 includes one or more speakers for producing sound. For example, display 208 can produce an audible alert or notification (e.g., a beep or chime). In some embodiments, display 208 includes one or more haptic devices for producing vibrations, motion, or other tactile feedback. In some embodiments, all or portions of display 208 can be integrated with input device 206. For example, input device 206 and display 208 can form a touchscreen or similar touch-sensitive display. In other embodiments, display 208 can be positioned near input device 206.

[0059] In certain embodiments, transmitter 210 can be used to transmit information described herein and / or receiver 212 can be used to receive information described herein.

[0060] Although only one transmitter 210 and one receiver 212 are illustrated, the remote unit 102 can have any suitable number of transmitters 210 and receivers 212. The transmitter 210 and the receiver 212 can be any suitable type of transmitters and receivers. In one embodiment, the transmitter 210 and the receiver 212 can be part of a transceiver. In some embodiments, the transmitter 210 can refer to the transmission or provision of data via software communication of data. In various embodiments, the receiver 212 can refer to the reception of data via software communication or software receiver.

[0061] Figure 3 One embodiment of an apparatus 300 that can be used for model-based predictive interference management is depicted. The apparatus 300 includes one embodiment of the network unit 104. Furthermore, the network unit 104 can include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. As can be appreciated, the processor 302, the memory 304, the input device 306, the display 308, the transmitter 310, and the receiver 312 can be substantially similar to the processor 202, the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212 of the remote unit 102, respectively.

[0062] In certain embodiments, the receiver 312 can receive modeling information corresponding to a device, where the modeling information includes traffic parameters, radio parameters, mobility parameters, or some combination thereof, and the modeling information includes at least one machine learning model. In various embodiments, the processor 302 can determine a predictive inter-cell interference management policy for the device based on the modeling information; and provide the predictive inter-cell interference management policy to the device.

[0063] In some embodiments, the receiver 312 can receive at least one monitoring report from the device. In various embodiments, the processor 302 can determine a monitoring event report based on the subscription and the at least one monitoring report; and provide the monitoring event report to an application.

[0064] In one embodiment, the transmitter 310 can transmit the at least one monitoring report. In certain embodiments, the receiver 312 can receive information corresponding to the predictive inter-cell interference management policy in response to transmitting the at least one monitoring report.

[0065] In various embodiments, transmitter 310 can transmit an initial configuration. In some embodiments, receiver 312 can receive a request for modeling information in response to transmitting the initial configuration. In certain embodiments, transmitter 310 can transmit the modeling information in response to receiving the request, where the modeling information includes traffic parameters, radio parameters, mobility parameters, or some combination thereof, and the modeling information includes at least one machine learning model.

[0066] In certain embodiments, receiver 312 can receive a predictive resource management policy from at least one application. In some embodiments, processor 302 can determine at least one radio parameter corresponding to the predictive resource management policy. In various embodiments, transmitter 310 can transmit the at least one radio parameter based on the predictive resource management policy to a device.

[0067] Certain embodiments described herein can be used to proactively minimize the impact of inter-cell interference in dense virtualized small cell co-deployment.

[0068] In some embodiments, such as in a 5G RAN, UDNs can cause interference challenges. In various embodiments, various factors can influence the way interference management is handled: extensive use of beamforming; UL and / or DL cross interference for TDD; novel communication modes (e.g., self-backhauling, cellular assisted D2D); and stringent application requirements (e.g., for delay-critical applications).

[0069] In certain embodiments, a separation of RAN CP (e.g., RRM) functions and UP for SDN can be used, such as in a 5G architecture. In such embodiments, interference management RRM functionality can be one key enabler for such separation to improve the flexibility and agility of the network. However, there can be challenges that complicate full separation (e.g., tight coupling of CP and UP in the RAN). For example, real-time scheduling (or fast RRM) functionality can be used with TTI scheduling, while interference management (which can be located at an edge cloud platform) applies in near real-time (e.g., 10-100 ms). In this example, real-time scheduling decisions can be provided to the IM function to adapt to policies. In some embodiments, such as in a virtualized cluster RAN system, it can be challenging to facilitate up-to-date IM decisions due to timing and / or backhaul requirements.

[0070] In various embodiments, data analytics (e.g., diagnostic and / or normative analytics) can be used to enhance the performance of interference mitigation techniques and allow decisions to be made at a semi-centralized entity without using real-time feedback from the involved RAN nodes. In such embodiments, the selection of UL power control parameters (e.g., fractional vs. full compensation power control) and / or time-domain interference coordination for an optimal number of blank subframes can be performed. Predictive analytics can support decisions for initial parameter setting configurations (e.g., taking into account possible load increases due to group mobility). Thus, using data analytics can improve resource utilization efficiency and / or reduce the need for frequent parameter adjustments.

[0071] Various embodiments described herein can be embodiments for minimizing inter-cell interference in a cluster virtualized RAN deployment while preserving low signaling load and / or complexity.

[0072] In some embodiments, RRM algorithms for cellular networks can be used to facilitate efficient use of available radio resources and provide mechanisms that enable E-UTRAN and / or 5GS to meet radio resource related requirements. In such embodiments, RRM can provide means to manage (e.g., assign, reassign, and / or release) radio resources for single and / or multi-cell systems.

[0073] In certain embodiments, inter-cell interference management can be RRM functionality that can reside at a BS or in a cloud platform of a cluster for access nodes (e.g., C-RAN). Interference management can take different forms, such as: 1) interference cancellation and / or randomization (e.g., related to physical layer enhancements to cancel interference); 2) interference avoidance and / or coordination (e.g., ICIC, eICIC, and / or FeICIC); and / or 3) interference cooperation (e.g., coordinated multi-point TX and / or RX).

[0074] As can be appreciated, if virtualization of radio resource management enables RRM functionality to be placed in different entities, such as centralized RRM, distributed RRM, and semi-centralized RRM, there can be different implementations of RRM algorithms.

[0075] In centralized RRM, RRM functions operate together in an entity for multiple access nodes in a group. This can provide fast and simple interaction between RRM functions, but on the other hand, in HetNets, ideal backhaul can be used for some fast RRM functions (e.g., CoMP, DRA). In addition, signaling overhead can be very high in ultra-dense environments. Further, for 5G systems, various embodiments can use a controller for clustering of HetNets using cloud-based resource pooling and management (e.g., cloud-RAN, C-RAN). As can be appreciated, resource pooling and centralized management of resources can provide high gain in terms of capacity. Nonetheless, this can use ideal backhaul and / or fronthaul, and can be challenging for DRA in certain environments where there can be interference from other C-RAN clusters.

[0076] In distributed RRM, such as used in 3GPP LTE and / or LTE-A, RRM functions reside at the eNB. The main RRM functions are with respect to DRA, ICIC, CMC, RAC, RBC, energy efficiency, and LB. In LTE RRM structure, there can be interaction between RRM functions. In one example, there can be cell on and / or off functions that can use inputs from resource restrictions for interference management, and can have outputs that use handovers that can impact CMC and LB. Because the main functions reside at the eNB, there can be no additional signaling specified in 3GPP for RRM interaction.

[0077] In semi-centralized RRM, there can be a focus on centralized interference management and load balancing and distributed fast RRM functionality. One challenge for semi-centralized RRM can be that interaction can use additional signaling and complexity in various RAN nodes.

[0078] O-RAN involves virtualization of access domain to RIC and virtualization of control functions (e.g., RRC and / or RRM), which can be collocated with gNB, or can be deployed for a cluster of gNBs. As can be appreciated, RRM and / or RRC functions can be flexibly located at the CU and / or DU or a dedicated RIC controller (e.g., near-RT RIC and non-RT RIC).

[0079] Figure 4 FIG. 4 is a diagram illustrating one embodiment of a system 400 for interference management. System 400 can operate with O-RAN and / or near-RT-RIC architecture.

[0080] As used herein, a non-RT RIC can refer to a logical function that is capable of non-real-time control and optimization of RAN elements and resources, AI and / or ML workflows including model training and updates, and policy-based steering of applications and / or features in the near-RT RIC.

[0081] Further, as used herein, a near-RT RIC and framework function can refer to a logical function that is capable of enabling near-real-time control and optimization of RAN elements and resources via fine-grained (e.g., UE basis, cell basis) data collection and actions over an E2 interface. The near-RT RIC can include a near-RT RIC base and / or framework function that can include subscription management, conflict mitigation, and E2T.

[0082] Further, as used herein, a conflict management and / or mitigation function can be a function that is part of the near-RT RIC and can be used to avoid conflicting control messages from different xApps. Based on the output of the conflict mitigation, the E2T can generate only one reasonable control message on one E2 interface.

[0083] Additionally, as used herein, a subscription management function can refer to a function in which xApps subscribe to control E2 nodes. The subscription management function can consolidate the same subscription from different xApps. Based on the output of the subscription management function, the E2T can generate only one message to send to an E2 node.

[0084] Additionally, as used herein, an xApp can refer to an application designed to run on the near-RT RIC. The application can include one or more microservices, and, where applicable, can identify which data it consumes and which data it provides. The application can be independent of the near-RT RIC and can be provided by a third party. The E2 can enable direct association between the xApp and RAN functions.

[0085] Further, as used herein, A1 (or O1) can refer to an interface between the non-RT RIC and the near-RT RIC to enable policy-driven steering of near-RT RIC applications and / or functions and can support AI and / or ML workflows.

[0086] Additionally, as used herein, E2 can refer to an interface connecting the near-RT RIC and the NR.

[0087] Further, as used herein, an E2 node can refer to a logical node that terminates the E2 interface (e.g., like an O-CU-CP, O-CU-UP, O-DU, or a virtualized eNB NR node).

[0088] Further, as used herein, an open API can refer to a definition within the near-RT RIC and / or can be an interface between the framework functions and the xAPPs.

[0089] Figure 4 The system 400 includes a service and / or management plane 402, a near-RT RIC 404, and a NR system 406. The service and / or management plane 402 communicates with the near-RT RIC 404 via an Al interface 408. Further, the near-RT RIC 404 communicates with the NR system 406 via an E2 interface 410. The service and / or management plane 402 includes a non-RT RIC 412 and a configuration 414. The configuration 414 can include policies, inventory, and / or design information.

[0090] The near-RT RIC 404 includes an AlT 416 (or OlT), which can be a logical node that terminates the Al interface 408. The near-RT RIC 404 also includes a plurality of xAPPs 418 that communicate with the AlT 416 via a first open API 420. The xAPPs 418 include a first xAPP 422, a second xAPP 424, a third xAPP 426, and a fourth xAPP 428. The near-RT RIC 404 further includes a near-RT RIC framework function 430. The near-RT RIC framework function 430 communicates with the xAPPs 418 via a second open API 432. Additionally, the near-RT RIC framework function 430 includes a subscription management function 434, a conflict resolution function 436, and a database 438. The near-RT RIC 404 still further includes an E2T 440, which can be a logical node that terminates the E2 interface 410 and can enable communication between components of the near-RT RIC 404 and the NR 406.

[0091] Described herein are various embodiments for configuring a representative resource allocation policy and / or an inter-cell interference aware resource allocation policy over a resource allocation policy for a set of RAN nodes with support of trained traffic and mobility Al and / or ML models. With respect to Figure 5 One embodiment is described.

[0092] Figure 5 is a diagram illustrating another embodiment of a system 500 for interference management. The system 500 includes a service and / or management plane 502, a near-RT RIC 504, and a NR system 506. The service and / or management plane 502 communicates with the near-RT RIC 504 via an Al interface. Further, the near-RT RIC 504 communicates with the NR system 506 via an E2 interface. The service and / or management plane 502 includes a non-RT RIC 508 and a configuration 510. The configuration 510 can include policies, inventory, and / or design information.

[0093] The near-RT RIC 504 includes an AlT 512 (or OlT), which can be a logical node that terminates the Al interface. The near-RT RIC 504 also includes a plurality of xAPPs 514 that communicate with the AlT 512 via open APIs. The xAPPs 514 include a first xAPP 516, a second xAPP 518 (e.g., an IM xAPP), a third xAPP 520, and a fourth xAPP 522. The near-RT RIC 504 also includes a near-RT RIC framework function 524. The near-RT RIC framework function 524 communicates with the xAPPs 514 via open APIs. In addition, the near-RT RIC framework function 524 includes a subscription management function 526, a conflict resolution function 528, and a database 530. The near-RT RIC 504 further includes an E2T 532, which can be a logical node that terminates the E2 interface and can enable communication between components of the near-RT RIC 504 and the NR 506. The system 500 can also include a middleware entity 534 to facilitate communication between the NR 506 and the near-RT RIC 504.

[0094] In a first communication 536 sent from the service and / or management plane 502 to the second xAPP 518, the second xAPP 518 initially receives an IM configuration policy (e.g., an initial configuration of a policy) from the service and / or management plane 502 including a list of available IM measurements (e.g., ICIC, eICIC, CoMP 1, CoMP 2), thresholds and / or criteria for access and BH metrics to support selection and / or updating of the IM policy, preferences, whether the policy can be enforced by the second xAPP 518, recommendations, time of override, and / or area of override. The IM configuration policy can be vertical specific (e.g., V2X, IIoT), or a generic configuration for all verticals using RAN resources. This IM configuration policy can provide the required interaction among xAPPs for intra- and cross-vertical cases if controlling the same RAN node.

[0095] In a second communication 538 sent between the subscription management function 526 and the second xAPP 518, in response to receiving the IM configuration policy, the second xAPP 518 subscribes to receive UE monitoring events, RAN monitoring events, and / or measurements for a set of cells indicated in the first communication 536.

[0096] In a third communication 540 sent from the NR 506 to the second xAPP 518, the second xAPP 518 receives a trigger time indicating that a UE performance metric and / or a RAN performance metric has changed (e.g., resource overload, QoS degradation) based on the subscription created in the second communication 538. The trigger event can be provided by the NR 506 or directly by the middleware entity 534 based on real-time radio measurements.

[0097] In a fourth communication 542 sent between the service and / or management plane 502 and the second xAPP 518, in response to receiving the trigger event, the second xAPP 518 requests and receives a trained AI model for traffic prediction and / or mobility prediction for each cell or for one or more UEs within a set of cells indicated at the trigger event. Such traffic prediction and / or mobility prediction can include an expected performance distribution of the RAN or selected UEs in a predefined time window (e.g., 10 ms to 1 s).

[0098] The second xAPP 518 determines an IM policy for the set of cells as indicated by the trigger event (e.g., to be enforced or to be used as a recommendation). The criteria for selecting a particular IM policy is the prediction output and can be determined whether the expected metrics are within thresholds as set in the first communication 536. The particular IM policy can be a policy that can be applied to a future given time window (e.g., for the next 1 s) based on the prediction output.

[0099] In a fifth communication 544 sent between the conflict mitigation function 528 and the second xAPP 518, the second xAPP 518 can verify and / or check whether the IM policy is feasible with the support of the common control function used to authorize the IM policy request.

[0100] In a sixth communication 546 sent from the second xAPP 518 to the NR 506, the second xAPP 518 sends the IM policy to the respective RAN nodes of the NR 506, either directly or via the middleware entity 534. The use of the middleware entity 534 can relax the constraints of dynamic IM policies (e.g., CoMP) by converting the IM policy to precise radio parameters (e.g., RB muting) if real-time radio parameters are needed. The middleware entity 534 can be part of the near-RT RIC 504 or can be deployed as a proxy co-located with the CU and / or gNB.

[0101] Figure 6is a diagram illustrating one embodiment of a communication 600 for interference management. In this embodiment, an implementation oriented to an O-RAN architecture is provided. In this architecture, the external application takes the form of an IM xAPP. The communication 600 includes communications between a non-RT RIC 602 (e.g., service and / or management plane, received by near-RT RIC at Al termination), an IM xAPP 604 (e.g., external application), conflict mitigation 606 (e.g., conflict mitigation function, can be at near-RT RIC), subscription management 608 (e.g., subscription management function, can be at near-RT RIC), and NR 610 (e.g., E2T, E2 node, CU, DU, RAN node). The communication 600 described herein can each include one or more messages.

[0102] In a first communication 612 sent from the non-RT RIC 602 to the IM xAPP 604, the IM xAPP 604 can receive an interference management policy message (e.g., from the non-RT RIC via AlT and via an open API between AlT and the IM xAPP 604). The interface management policy message can include: a cell ID; a network slice ID; a service type, application type, and / or application profile (e.g., these can be related to a vertical); a list of policy IDs (e.g., policy 1: ICIC scheme 1 (e.g., FFR); policy 2: ICIC scheme 2 (e.g., SFR); policy 3: eICIC scheme; policy 4: CoMP scheme 1 (e.g., CS, CB); policy 5: CoMP scheme 2 (e.g., coherent JT, coherent JR); policy 6: CoMP scheme 2 (e.g., non-coherent JT, non-coherent JR)); a per-policy threshold (e.g., O-RAN cell computation load; O-CU load; O-DU load; RAN allowed delay; per-policy backhaul requirement; UE density min and / or max; radio resource load); an indication of what the interference management preference contains (e.g., a list of cell IDs; a resource pool ID; a policy preference for a list of cells (e.g., should, prefer, avoid, prohibit); a priority of a policy for a list of cells (e.g., should, prefer, avoid, prohibit); a force enforcement flag (e.g., enforce the policy or not enforce the policy); a time validity; an area of coverage; per-vertical parameters (e.g., priority among xAPPs within the same vertical, spectrum considerations, spectrum restrictions, isolation level, per-vertical small cell dedicated cluster under near-RT RIC); and / or cross-vertical parameters (e.g., priority among xAPPs across verticals, spectrum considerations, spectrum restrictions, isolation level, common (for all verticals) small cell cluster under near-RT RIC.

[0103] In a second communication 614 sent between the IM xAPP 604 and the subscription management 608, the IM xAPP 604 subscribes to near-RT RIC to periodically receive RAN monitoring events, UE monitoring events, and / or measurements (e.g., RAN and / or UE) from the subscription management 608. The subscription management 608 provides requests to the RAN nodes (e.g., this can be a consolidated request from more than one similar xAPP) respectively. Such monitored events and / or measurements can include: radio resource utilization (e.g., DL and / or UL total PRB usage and / or distribution of usage, DL and / or UL PRBs used for data traffic); DRB related measurements (e.g., number of successfully setup DRBs, session active time of DRBs); CQI related measurements (e.g., wideband CQI distribution); MCS related measurements; QoS maintainability; KPI monitoring; KPI monitoring across RAN UEs; average and distribution of latency DL and / or UL air interface; NG-RAN handover success rate monitoring; number of requested handover resource allocations; and / or number of successful handover resource allocations.

[0104] The NR 610 detects a RAN or UE monitoring event 616.

[0105] In a third communication 618 sent from the NR 610 to the IM xAPP 604, the RAN or UE monitoring event is received by the IM xAPP 604 based on the monitoring subscription (e.g., radio resource load for cell 1 > X%) subscribed to in the second communication 614. This event can be provided directly from the E2 node or directly via other frameworks of the E2T and / or near-RT RIC function. Information indicating the RAN or UE monitoring event can include: cell ID; UE ID; network slice ID; resource ID; resource pool ID; UE QoE degradation indication; QoS degradation indication; high resource load indication; high RAN latency indication; low backhaul resource availability indication; QoS fluctuation indication; and / or radio link failure indication.

[0106] In a fourth communication 620 sent from the IM xAPP 604 to the non-RT RIC 602, the IM xAPP 604 sends a request (e.g., traffic prediction model message and / or mobility prediction model request message) for modeling information to the non-RT RIC 602 for all or selected UEs in a given area (e.g., cell edge, from point A to point B). This can apply to models for selected UEs if the monitoring event is a UE monitoring event.

[0107] In a fifth communication 622 sent from the non-RT RIC 602 to the IM xAPP 604, the IM xAPP 604 receives the modeling information (e.g., traffic prediction model reports and / or mobility prediction model reports including trained Al and / or ML models) from the non-RT RIC 602. In some embodiments, the fifth communication 622 can be sent from the non-RT RIC 602 to the IM xAPP 604, and in other embodiments, the modeling information can instead be stored in a near-RT RIC database and retrieved by the IM xAPP 604. The modeling information can include: expected RAN resource conditions (e.g., channel statistics distribution over the entire area with high and low points) over a time period (e.g., 10ms to 1 sec, pre-defined, configured, pre-configured) based on configured and / or predicted accuracy; expected wireless BH resource conditions (e.g., channel statistics distribution of the involved BH links) over a time period based on configured and / or predicted accuracy; expected UE mobility parameters, expected UE positioning information, and / or expected UE trajectories (e.g., anonymized) and / or predicted accuracy for UEs in a geographical area; expected performance metrics for UEs in a geographical area and / or predicted accuracy, expected distribution of any of the above over a time period; confidence level metrics for any of the above over a time period, and / or expected sequence of inter-cell handovers for UEs in a geographical area.

[0108] The IM xAPP 604 determines new IM policies for the affected RAN nodes 624. This can be a pre-defined policy based on the thresholds from the first communication 612 and / or the prediction information from the fifth communication 622. The determination can take into account the predicted performance metrics (e.g., also taking into account the prediction accuracy), and can also check whether these metrics meet the thresholds set from the first communication 612. The IM xAPP 604 can select an IM policy based on the IM policy preference from the first communication 612 that will result in a higher preference and / or priority for optimizing performance (e.g., CoMP is a higher priority than ICIC).

[0109] In a sixth communication 626 sent from the IM xAPP 604 to the conflict mitigation 606, the IM xAPP 604 sends an updated IM policy request message to the conflict mitigation 606. The updated IM policy request message can include: cell ID; network slice ID; CU ID; DU ID; current policy ID; new policy ID; enforcement flag; time validity; and / or area of coverage.

[0110] In a seventh communication 628 sent from the conflict mitigation 606 to the IM xAPP 604, the IM xAPP 604 receives a response (e.g., ACK, NACK) from the conflict mitigation 606.

[0111] In an eighth communication 630 sent from the IM xAPP 604 to the NR 610, the IM xAPP 604 provides the new IM policy to the impacted RAN node based on the successful receipt of the ACK with the updated IM policy message. The updated IM policy message includes: cell ID; network slice ID; CU ID; DU ID; current policy ID; new policy ID; enforcement flag; time validity; coverage area; and / or per-IM policy parameters (e.g., OI, HII, RNTP, ABS pattern information, CoMP coordination area, CoMP scheme, resource restrictions (e.g., in time, frequency, and / or spatial domain)).

[0112] Figure 7 FIG. 7 is a diagram illustrating another embodiment of a communication 700 for interference management. In this embodiment, an implementation towards an O-RAN architecture is provided. In this architecture, the external application takes the form of an IM xAPP and a middleware function is used. The use of a middleware function can reduce and / or relax the potentially high load on the IM xAPP (e.g., if the xAPP receives all radio related measurements and / or events and can be aware of low layer real-time configurations). As described herein, the middleware function can be deployed as a near-RT RIC function or as a proxy quasi co-located at the RAN side and can: receive UE and / or RAN monitoring reports and can translate them into behaviors and / or events (e.g., high load indication, RAN UE KPIs reaching low thresholds) that are perceivable by the IM xAPP - this can be used for embodiments where UE related measurements can not be exposed to the xAPP, but only abstract events can be provided as updated control messages to the xAPP; and receive the requested updated IM policy and translate it into precise radio parameters to be used based on real-time radio conditions - this can enable the IM xAPP to be only aware of high-level policies to be applied, rather than needing to be updated on radio parameters.

[0113] The communication 700 includes communications between a non-RT RIC 702 (e.g., service and / or management plane, received at Al termination by a near-RT RIC), an IM xAPP 704 (e.g., external application), conflict mitigation 706 (e.g., conflict mitigation function, can be at near-RT RIC), a subscription pipe 710 (e.g., middleware entity), and a NR 712 (e.g., E2T, E2 node, CU, DU, RAN node). The communication 700 described herein can each include one or more messages.

[0114] In a first communication 714 sent from the non-RT RIC 702 to the IM xAPP 704, the IM xAPP 704 can receive an interference management policy message (e.g., from the non-RT RIC via AlT and via an open API between AlT and the IM xAPP 604). The interface management policy message can include: a cell ID; a network slice ID; a service type, an application type, and / or an application profile (e.g., these can be related to a vertical); a list of policy IDs (e.g., Policy 1: ICIC scheme 1 (e.g., FFR); Policy 2: ICIC scheme 2 (e.g., SFR); Policy 3: eICIC scheme; Policy 4: CoMP scheme 1 (e.g., CS, CB); Policy 5: CoMP scheme 2 (e.g., coherent JT, coherent JR); Policy 6: CoMP scheme 2 (e.g., non-coherent JT, non-coherent JR)); a per-policy threshold (e.g., O-RAN cell computation load; O-CU load; O-DU load; RAN allowed delay; backhaul requirement per policy; UE density min and / or max; radio resource load); an indication of what the interference management preference contains (e.g., a list of cell IDs; a resource pool ID; a policy preference for a list of cells (e.g., should, prefer, avoid, prohibit); a priority of a policy for a list of cells (e.g., will, prefers, avoids, prohibits); an enforcement flag (e.g., enforce policy or do not enforce policy); a use of middleware flag (e.g., use or do not use); a middleware ID; a middleware address; a time validity; an area of coverage; per-vertical parameters (e.g., priority among xAPPs within the same vertical, spectrum considerations, spectrum limitations, isolation levels, per-vertical small cell dedicated clusters under near-RT RIC); and / or cross-vertical parameters (e.g., priority among xAPPs across verticals, spectrum considerations, spectrum limitations, isolation levels, common (for all verticals) small cell clusters under near-RT RIC.

[0115] In a second communication 716 sent between the IM xAPP 704 and the subscription management 708, the IM xAPP 704 subscribes to near-RT RIC to periodically receive RAN monitoring events, UE monitoring events, and / or measurements (e.g., RAN and / or UE) from the subscription management 708. The subscription management 708 provides requests to the RAN nodes (e.g., this can be a consolidated request from more than one similar xAPP) respectively. Such monitoring of events and / or measurements can include: radio resource utilization (e.g., DL and / or UL total PRB usage and / or distribution of usage, DL and / or UL PRBs used for data traffic); DRB related measurements (e.g., number of successfully setup DRBs, session active time of DRBs); CQI related measurements (e.g., wideband CQI distribution); MCS related measurements; QoS maintainability; KPI monitoring; RAN UE across KPI monitoring; average and distribution of latency DL and / or UL air interface; NG-RAN handover success rate monitoring; number of handover resource allocations requested; number of handover resource allocations successfully; and / or configuration of middleware ID and triggering events (e.g., this can be per vertical application or for all vertical applications).

[0116] In an optional third communication 718 sent between the subscription management 708 and the middleware 710, the subscription management 708 can provide requests to the middleware 710 for events and / or other information related to the subscription corresponding to the second communication 716.

[0117] In a fourth communication 720 sent from the NR 712 to the middleware 710, the middleware 710 receives a monitoring report from the NR 712. The monitoring report can include: cell ID; UE ID; network slice ID; resource ID; resource pool ID; UE QoE degradation indication; QoS degradation indication; high resource load indication; high RAN latency indication; low backhaul resource availability indication; QoS fluctuation indication; and / or radio link failure indication.

[0118] The middleware 710 can translate the monitoring report 722 into monitoring events based on the subscription information and real-time analytics.

[0119] In a fifth communication 722 sent from the middleware 710 to the IM xAPP 704, the middleware 710 sends a monitoring event report message to the IM xAPP 704 if the conditions are met (e.g., based on thresholds from the first communication 714 and / or the monitoring subscription). This report message can include: cell ID; UE ID; network slice ID; resource ID; resource pool ID; UE QoE degradation indication; QoS degradation indication; high resource load indication; high RAN latency indication; low backhaul resource availability indication; QoS fluctuation indication; bandwidth adaptation requirement, radio resource adaptation requirement, traffic steering requirement, and / or radio link failure indication.

[0120] In a sixth communication 726 sent from the IM xAPP 704 to the non-RT RIC 702, the IM xAPP 704 sends a request for modeling information (e.g., traffic prediction model message and / or mobility prediction model request message) to the non-RT RIC 702 for all or selected UEs in a given area (e.g., cell edge, from point A to point B). This can apply to models for selected UEs if the monitoring event is a UE monitoring event.

[0121] In a seventh communication 728 sent from the non-RT RIC 702 to the IM xAPP 704, the IM xAPP 704 receives modeling information (e.g., traffic prediction model report and / or mobility prediction model report including trained AI and / or ML models) from the non-RT RIC 702. In some embodiments, the seventh communication 728 can be sent from the non-RT RIC 702 to the IM xAPP 704, and in other embodiments, the modeling information can instead be stored in a near-RT RIC database and retrieved by the IM xAPP 704. The modeling information can include: expected RAN resource conditions (e.g., channel statistics distribution over the entire area with high and low points) over a time period (e.g., 10ms to 1 sec, pre-defined, configured, pre-configured) based on configured and / or predicted accuracy; expected wireless BH resource conditions (e.g., channel statistics distribution of the involved BH links) over a time period based on configured and / or predicted accuracy; expected UE mobility parameters, expected UE positioning information, and / or expected UE trajectory (e.g., anonymized) for UEs in a geographical area and / or predicted accuracy; expected performance metrics for UEs in a geographical area and / or predicted accuracy, expected distribution of any of the above over a time period; confidence level metrics for any of the above over a time period, and / or expected sequence of inter-cell handovers for UEs in a geographical area.

[0122] The IM xAPP 704 determines a new IM policy for the impacted RAN node 730. This can be a pre-defined policy based on the threshold from the first communication 714 and / or the prediction information from the seventh communication 728. The determination can take into account the predicted performance metrics (e.g., also taking into account the prediction accuracy), and can also check whether these metrics meet the threshold set from the first communication 714. The IM xAPP 704 can select an IM policy that will result in a higher preference and / or priority for optimizing performance based on the IM policy preference from the first communication 714 (e.g., CoMP is a higher priority than ICIC).

[0123] In an eighth communication 732 sent from the IM xAPP 704 to the conflict resolution 706, the IM xAPP 704 sends an updated IM policy request message to the conflict resolution 706. The updated IM policy request message can include: a cell ID; a network slice ID; a CU ID; a DU ID; a current policy ID; a new policy ID; an enforcement flag; a time validity; and / or an area of coverage.

[0124] In a ninth communication 734 sent from the conflict resolution 706 to the IM xAPP 704, the IM xAPP 704 receives a response (e.g., ACK, NACK) from the conflict resolution 706.

[0125] In a tenth communication 736 sent from the IM xAPP 704 to the middleware 710, the IM xAPP 704 provides a new IM policy to the middleware 710 with an updated IM policy message based on successfully receiving the ACK. The updated IM policy message includes: a cell ID; a network slice ID; a CU ID; a DU ID; a current policy ID; a new policy ID; an enforcement flag; a time validity; an area of coverage; and / or per-IM policy parameters (e.g., OI, HII, RNTP, ABS pattern information, CoMP coordination area, CoMP scheme, resource restrictions (e.g., in time, frequency, and / or spatial domain)).

[0126] The middleware 710 checks 738 real-time radio resource conditions for the involved RAN nodes and derives the policy parameters to be provided to the RAN nodes.

[0127] In an eleventh communication 740 sent from the middleware 710 to the NR 712, the middleware 710 sends an application message’s IM policy parameters to the NR 712. The application message’s IM policy parameters can include: a cell ID; a UE ID, a resource ID; a resource pool ID; and / or per-IM policy parameters (e.g., OI, HII, RNTP, ABS pattern information, CoMP coordination area, CoMP scheme, resource restrictions (e.g., in time, frequency, and / or spatial domain)).

[0128] Figure 8 FIG. 8 is a flow chart illustrating one embodiment of a method 800 for model-based predictive interference management. In some embodiments, the method 800 is performed by an apparatus, such as the network element 104. In certain embodiments, the method 800 can be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0129] In various embodiments, the method 800 includes receiving 802 modeling information corresponding to a device, where the modeling information includes traffic parameters, radio parameters, mobility parameters, or some combination thereof, and the modeling information includes at least one machine learning model. In some embodiments, the method 800 includes determining 804 a predictive inter-cell interference management policy for the device based on the modeling information. In certain embodiments, the method 800 includes providing 806 the predictive inter-cell interference management policy to the device.

[0130] In certain embodiments, the method 800 further includes receiving an initial configuration prior to determining the predictive inter-cell interference management policy. In some embodiments, the initial configuration is transmitted from a service entity, a management entity, or a combination thereof. In various embodiments, the initial configuration includes a cell identifier, a network slice identifier, a service type, an application type, a profile, a list of policy identifiers, per-policy metrics, per-policy thresholds, interference management preferences, an enforcement flag, a middleware flag, a middleware identifier, a time validity indicator, a geographic area, a vertical-specific parameter, a cross-vertical parameter, or some combination thereof.

[0131] In one embodiment, the initial configuration is configured per vertical customer. In certain embodiments, the method 800 further includes obtaining a monitoring event report related to the device. In some embodiments, the predictive inter-cell interference management policy is determined in response to obtaining the monitoring event report.

[0132] In various embodiments, the monitoring event report includes a cell identifier, a user equipment identifier, a network slice identifier, a resource identifier, a resource pool identifier, a user equipment quality of experience degradation indication, a user equipment quality of service degradation indication, a high resource load indication, a high radio access network latency indication, a low backhaul resource availability indication, a quality of service fluctuation indication, a radio link failure indication, or some combination thereof. In one embodiment, the method 800 further includes subscribing to a radio access network node, a subscription function, or a combination thereof, for receiving the monitoring event report. In certain embodiments, the device includes at least one network element, at least one user equipment, or a combination thereof.

[0133] In some embodiments, the modeling information includes: a first expectation of radio access network resource conditions over a predefined time period; a second expectation of wireless backhaul resource conditions over the predefined time period; a third expectation of user equipment mobility parameters, an expectation of user equipment positioning information, or a combination thereof, of user equipment in the geographic region; a fourth expectation of performance metrics of user equipment in the geographic region; an expected distribution of the first expectation, the second expectation, the third expectation, the fourth expectation, or some combination thereof, over the predefined time period; a confidence level metric of the first expectation, the second expectation, the third expectation, the fourth expectation, or some combination thereof, over the predefined time period; an expected probability density function over the radio access network resources, the backhaul resources, or a combination thereof; an expectation of inter-cell handover sequences of user equipment in the geographic region; or some combination thereof. In various embodiments, the predicted inter-cell interference management policy is provided to a middleware entity. In one embodiment, the predicted inter-cell interference management policy includes a cell identifier, an application identifier, a user equipment group identifier, a network slice identifier, a central unit identifier, a distributed unit identifier, a current policy identifier, a new policy identifier, a current traffic steering policy identifier (this identifier can map to one of the following policies for one or more user equipment: 1) intra-frequency gNB selection, 2) inter-frequency gNB selection, 3) central unit selection, 4) distributed unit selection, 5) dual connectivity operation selection), a new traffic steering policy identifier (this can be a traffic steering policy updated based on the predicted inter-cell interference management policy), a confidence level parameter, an enforcement flag, a time validity indicator, a zone indicator, an overload indication, a high interference indication, a relative narrowband transmit power, an almost blank subframe pattern information, a coordinated multipoint coordination zone, a coordinated multipoint scheme, a resource restriction, or some combination thereof.

[0134] In certain embodiments, the method 800 further includes requesting validation of the predicted inter-cell interference management policy from a conflict resolution function and receiving a validation response from the conflict resolution function. In some embodiments, the communication is transmitted and received using an open application program interface. In various embodiments, the Al interface is used for communication with a service entity, a management entity, or a combination thereof.

[0135] In one embodiment, the E2 interface is used for communication with a new radio device. In certain embodiments, the predicted inter-cell interference management policy is provided to the device via an application exposure function.

[0136] Figure 9 is a flow diagram illustrating another embodiment of a method 900 for model-based predicted interference management. In some embodiments, the method 900 is performed by an apparatus, such as the network unit 104. In certain embodiments, the method 900 can be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0137] In various embodiments, the method 900 includes receiving at least one monitoring report from the device 902. In some embodiments, the method 900 includes determining 904 a monitoring event report based on the subscription and the at least one monitoring report. In certain embodiments, the method 900 includes providing the monitoring event report to the application 906.

[0138] In certain embodiments, the method 900 further includes receiving a predicted inter-cell interference management policy from the application, determining at least one radio parameter corresponding to the predicted inter-cell interference management policy, and sending the at least one radio parameter to the device based on the predicted inter-cell interference management policy. In some embodiments, the predicted inter-cell interference management policy includes a cell identifier, an application identifier, a user equipment group identifier, a network slice identifier, a central unit identifier, a distributed unit identifier, a current policy identifier, a new policy identifier, a current traffic steering policy identifier (this identifier can map to one of the following policies for one or more user equipment: 1) intra-frequency gNB selection, 2) inter-frequency gNB selection, 3) central unit selection, 4) distributed unit selection, 5) dual connectivity operation selection), a new traffic steering policy identifier (this can be a traffic steering policy updated based on the predicted inter-cell interference management policy), a confidence level parameter, an enforcement flag, a time validity indicator, a zone indicator, or some combination thereof. In various embodiments, the at least one radio parameter includes an overload indication, a high interference indication, a relative narrowband transmit power, an almost blank subframe pattern information, a coordinated multipoint coordination zone, a coordinated multipoint scheme, a resource restriction, a parameter for traffic steering policy update (handover request indication, source cell identifier, target cell identifier, frequency selection indication, radio access technology selection indication, radio interface selection indication, distributed unit selection indication, central unit selection indication), or some combination thereof.

[0139] In one embodiment, the predicted inter-cell interference management policy is provided to the device via an application exposure function. In certain embodiments, the method 900 further includes receiving a subscription request for the subscription from the application. In some embodiments, the monitoring event report includes a cell identifier, a user equipment identifier, a network slice identifier, a resource identifier, a resource pool identifier, a user equipment quality of experience degradation indication, a user equipment quality of service degradation indication, a high resource load indication, a high radio access network latency indication, a low backhaul resource availability indication, a quality of service fluctuation indication, a radio link failure indication, a bandwidth adaptation requirement, a radio resource adaptation requirement, a traffic steering requirement, or some combination thereof.

[0140] Figure 10is a flow chart illustrating yet another embodiment of a method 1000 for model-based predictive interference management. In some embodiments, the method 1000 is performed by an apparatus, such as the network unit 104. In certain embodiments, the method 1000 can be performed by a processor executing program code, for example, a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, or the like.

[0141] In various embodiments, the method 1000 includes sending 1002 at least one monitoring report. In some embodiments, the method 1000 includes receiving information corresponding to a predictive inter-cell interference management policy in response to sending the at least one monitoring report 1004.

[0142] In certain embodiments, the at least one monitoring report includes a monitoring event report including a cell identifier, a user equipment identifier, a network slice identifier, a resource identifier, a resource pool identifier, a user equipment quality of experience degradation indication, a user equipment quality of service degradation indication, a high resource load indication, a high radio access network latency indication, a low backhaul resource availability indication, a quality of service fluctuation indication, a radio link failure indication, a bandwidth adaptation requirement, a radio resource adaptation requirement, a traffic steering requirement, or some combination thereof.

[0143] In some embodiments, the predictive inter-cell interference management policy includes a cell identifier, an application identifier, a user equipment group identifier, a network slice identifier, a central unit identifier, a distributed unit identifier, a current policy identifier, a new policy identifier, a current traffic steering policy identifier (this identifier can map to one of the following policies for one or more user equipment: 1) intra-frequency gNB selection, 2) inter-frequency gNB selection, 3) central unit selection, 4) distributed unit selection, 5) dual connectivity operation selection), a new traffic steering policy identifier (this can be a traffic steering policy after the predictive inter-cell interference management policy update), a confidence level parameter, an enforcement flag, a time validity indicator, a zone indicator, an overload indication, a high interference indication, a relative narrowband transmit power, an almost blank subframe pattern information, a coordinated multipoint coordination zone, a coordinated multipoint scheme, a resource restriction, or some combination thereof. In one embodiment, the information corresponding to the predictive inter-cell interference management policy is received from a middleware entity or an application.

[0144] Figure 11 is a flow chart illustrating yet another embodiment of a method 1000 for model-based predictive interference management. In some embodiments, the method 1000 is performed by an apparatus, such as the network unit 104. In certain embodiments, the method 1000 can be performed by a processor executing program code, for example, a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, or the like.

[0145] In various embodiments, the method 1100 includes sending 1102 an initial configuration. In some embodiments, the method 1100 includes receiving 1104 a request for modeling information in response to sending the initial configuration. In certain embodiments, the method 1100 includes sending modeling information 1106 in response to receiving the request, where the modeling information includes traffic parameters, radio parameters, mobility parameters, or some combination thereof, and the modeling information includes at least one machine learning model.

[0146] In certain embodiments, the initial configuration is sent to an application. In some embodiments, the initial configuration is sent from a service entity, a management entity, or some combination thereof. In various embodiments, the initial configuration includes a cell identifier, a network slice identifier, a service type, an application type, a profile, a list of policy identifiers, per-policy metrics, per-policy thresholds, interference management preferences, an enforcement flag, a middleware flag, a middleware identifier, a time validity indicator, a geographic area, a vertical-specific parameter, a cross-vertical parameter, or some combination thereof.

[0147] In one embodiment, the initial configuration is configured per vertical customer. In certain embodiments, the modeling information includes a first expectation of radio access network resource conditions over a predefined time period, a second expectation of wireless backhaul resource conditions over the predefined time period, a third expectation of user equipment mobility parameters, an expectation of user equipment positioning information, or a combination thereof, of user equipment in a geographic area, a fourth expectation of performance metrics of user equipment in the geographic area, an expected distribution of the first expectation, the second expectation, the third expectation, the fourth expectation, or some combination thereof, over the predefined time period, a confidence level metric of the first expectation, the second expectation, the third expectation, the fourth expectation, or some combination thereof, over the predefined time period, an expected probability density function over radio access network resources, backhaul resources, or a combination thereof, an expectation of inter-cell handover sequences of user equipment in the geographic area, or some combination thereof.

[0148] Figure 12 is a flow diagram illustrating another embodiment of a method 1200 for model-based predictive interference management. In some embodiments, the method 1200 is performed by an apparatus, such as the network element 104. In certain embodiments, the method 1200 can be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0149] In various embodiments, the method 1200 includes receiving 1202 a predictive resource management policy from at least one application. In various embodiments, the method 1200 includes determining 1204 at least one radio parameter corresponding to the predictive resource management policy. In some embodiments, the method 1200 includes sending 1206 the at least one radio parameter to a device based on the predictive resource management policy.

[0150] In certain embodiments, the predicted resource management policy includes an application identifier, a user equipment group identifier, a cell identifier, a network slice identifier, a central unit identifier, a distributed unit identifier, a current inter-cell interference management policy identifier, a new inter-cell interference policy identifier, a current traffic steering policy identifier (this identifier can map to one of the following policies for one or more user equipment: 1) intra-frequency gNB selection 2), inter-frequency gNB selection, 3) central unit selection, 4) distributed unit selection, 5) dual connectivity operation selection), a new traffic steering policy identifier (this can be a traffic steering policy updated based on the predicted inter-cell interference management policy), a confidence level parameter, a flag for enforcement, a time validity indicator, a zone indicator, or some combination thereof. In some embodiments, the at least one radio parameter includes an overload indication, a high interference indication, a relative narrowband transmit power, an almost blank subframe pattern information, a coordinated multipoint coordination zone, a coordinated multipoint scheme, a resource restriction, a parameter for traffic steering policy update (handover request indication, source cell identifier, target cell identifier, frequency selection indication, radio access technology selection indication, radio interface selection indication, distributed unit selection indication, central unit selection indication), or some combination thereof.

[0151] In various embodiments, the predicted resource management policy is provided to the device via an application exposure function. In one embodiment, the device includes at least one network unit, at least one user equipment, or a combination thereof. In certain embodiments, the at least one radio parameter is further determined based on at least one predefined rule corresponding to an application type, a service type, or a combination thereof.

[0152] In some embodiments, the predefined rule includes a key performance indicator, a service type identifier, an application type identifier, a radio access network identifier, a network slice profile, a service profile, a quality of service target (guaranteed traffic bit rate, maximum traffic bit rate, priority class, packet delay budget parameter, reliability parameter, packet error rate parameter), a quality of experience target (quality of experience score, initial buffering parameter, stall event, stall ratio, mean opinion score), a priority identifier, an application quality of service to network quality of service mapping information, or some combination thereof.

[0153] In various embodiments, the method 1200 further includes receiving at least one monitoring report from the device, determining a monitoring event report based on the subscription and the at least one monitoring report, and sending the monitoring event report to the application. In one embodiment, the method 1200 further includes receiving a subscription request for the subscription from the application.

[0154] In certain embodiments, the monitoring report includes a user equipment quality of service parameter, a user equipment quality of experience parameter, a radio resource quality parameter, a computed radio access network resource load parameter, a central unit load, a distributed unit load, channel state information, a radio resource management measurement, a radio link monitoring measurement, a received signal strength indicator, a reference signal received power parameter, a handover failure monitoring parameter, or some combination thereof.

[0155] In some embodiments, the monitoring report further includes a backhaul radio resource quality parameter, backhaul channel state information, a backhaul radio resource management measurement, a backhaul radio link monitoring measurement, a backhaul topology parameter, a backhaul type parameter, or some combination thereof. In various embodiments, the monitoring event report is determined based on offline user equipment analysis, online user equipment analysis, radio resource quality analysis, or some combination thereof.

[0156] In one embodiment, the monitoring event report includes a cell identifier, a user equipment identifier, a network slice identifier, a resource identifier, a resource pool identifier, a user equipment quality of experience degradation indication, a user equipment quality of service degradation indication, a high resource load indication, a high radio access network latency indication, a low backhaul resource availability indication, a quality of service fluctuation indication, a radio link failure indication, a bandwidth adaptation requirement, a radio resource adaptation requirement, a traffic steering requirement, or some combination thereof.

[0157] In one embodiment, a method includes receiving modeling information corresponding to a device, wherein the modeling information includes a traffic parameter, a radio parameter, a mobility parameter, or some combination thereof, and the modeling information includes at least one machine learning model; determining a predicted inter-cell interference management policy for the device based on the modeling information; and providing the predicted inter-cell interference management policy to the device.

[0158] In certain embodiments, the method further includes receiving an initial configuration prior to determining the predicted inter-cell interference management policy.

[0159] In some embodiments, the initial configuration is sent from a service entity, a management entity, or a combination thereof.

[0160] In various embodiments, the initial configuration includes a cell identifier, a network slice identifier, a service type, an application type, a profile, a list of policy identifiers, per-policy metrics, per-policy thresholds, an interference management preference, an enforcement flag, a middleware flag, a middleware identifier, a time validity indicator, a geographical area, a vertical-specific parameter, a cross-vertical parameter, or some combination thereof.

[0161] In one embodiment, the initial configuration is configured per vertical customer.

[0162] In certain embodiments, the method further comprises obtaining a monitoring event report related to the device.

[0163] In some embodiments, the predicting the inter-cell interference management strategy is determined in response to obtaining the monitoring event report.

[0164] In various embodiments, the monitoring event report comprises a cell identifier, a user equipment identifier, a network slice identifier, a resource identifier, a resource pool identifier, a user equipment quality of experience degradation indication, a user equipment quality of service degradation indication, a high resource load indication, a high radio access network latency indication, a low backhaul resource availability indication, a quality of service fluctuation indication, a radio link failure indication, or some combination thereof.

[0165] In one embodiment, the method further comprises subscribing to a radio access network node, a subscription function, or a combination thereof, for receiving the monitoring event report.

[0166] In certain embodiments, the device comprises at least one network element, at least one user equipment, or a combination thereof.

[0167] In some embodiments, the modeling information comprises: a first expectation of radio access network resource conditions over a predefined time period; a second expectation of wireless backhaul resource conditions over the predefined time period; a third expectation of a user equipment mobility parameter, an expectation of user equipment positioning information, or a combination thereof, of user equipment in a geographic region; a fourth expectation of a performance metric of user equipment in the geographic region; an expected distribution of the first expectation, the second expectation, the third expectation, the fourth expectation, or some combination thereof, over the predefined time period; a confidence level metric of the first expectation, the second expectation, the third expectation, the fourth expectation, or some combination thereof, over the predefined time period; an expected probability density function over radio access network resources, backhaul resources, or a combination thereof; an expectation of an inter-cell handover sequence of user equipment in the geographic region; or some combination thereof.

[0168] In various embodiments, the predicting the inter-cell interference management strategy is provided to a middleware entity.

[0169] In one embodiment, the predicted inter-cell interference management policy includes a cell identifier, an application identifier, a user equipment group identifier, a network slice identifier, a central unit identifier, a distributed unit identifier, a current policy identifier, a new policy identifier, a current traffic steering policy identifier (this identifier can map to one of the following policies for one or more user equipment: 1) intra-frequency gNB selection, 2) inter-frequency gNB selection, 3) central unit selection, 4) distributed unit selection, 5) dual connectivity operation selection), a new traffic steering policy identifier (this can be a traffic steering policy updated based on the predicted inter-cell interference management policy), a confidence level parameter, a flag for enforcement, a time validity indicator, a zone indicator, an overload indication, a high interference indication, a relative narrowband transmit power, an almost blank subframe pattern information, a coordinated multipoint coordination zone, a coordinated multipoint scheme, a resource restriction, or some combination thereof.

[0170] In certain embodiments, the method further includes requesting validation of the predicted inter-cell interference management policy from a conflict resolution function and receiving a validation response from the conflict resolution function.

[0171] In some embodiments, the communications are sent and received using an open application program interface.

[0172] In various embodiments, the Al interface is used for communications with a service entity, a management entity, or a combination thereof.

[0173] In one embodiment, the E2 interface is used for communications with a new radio device.

[0174] In certain embodiments, the predicted inter-cell interference management policy is provided to the device via an application exposure function.

[0175] In one embodiment, an apparatus includes a receiver that receives modeling information corresponding to a device, where the modeling information includes traffic parameters, radio parameters, mobility parameters, or some combination thereof, and the modeling information includes at least one machine learning model, and a processor that determines a predicted inter-cell interference management policy for the device based on the modeling information and provides the predicted inter-cell interference management policy to the device.

[0176] In certain embodiments, the receiver receives an initial configuration prior to determining the predicted inter-cell interference management policy.

[0177] In some embodiments, the initial configuration is sent from a service entity, a management entity, or a combination thereof.

[0178] In various embodiments, the initial configuration comprises a cell identifier, a network slice identifier, a service type, an application type, a profile, a list of policy identifiers, a per-policy metric, a per-policy threshold, an interference management preference, an enforcement flag, a middleware flag, a middleware identifier, a time validity indicator, a geographic area, a vertical-specific parameter, a cross-vertical parameter, or some combination thereof.

[0179] In one embodiment, the initial configuration is configured per vertical customer.

[0180] In certain embodiments, the receiver obtains a monitoring event report related to the device.

[0181] In some embodiments, the predicted inter-cell interference management policy is determined in response to obtaining the monitoring event report.

[0182] In various embodiments, the monitoring event report comprises a cell identifier, a user equipment identifier, a network slice identifier, a resource identifier, a resource pool identifier, a user equipment quality of experience degradation indication, a user equipment quality of service degradation indication, a high resource load indication, a high radio access network latency indication, a low backhaul resource availability indication, a quality of service fluctuation indication, a radio link failure indication, or some combination thereof.

[0183] In one embodiment, the processor subscribes to a radio access network node, a subscription function, or a combination thereof, for receiving the monitoring event report.

[0184] In certain embodiments, the device comprises at least one network element, at least one user equipment, or a combination thereof.

[0185] In some embodiments, the modeling information comprises a first expectation of radio access network resource conditions over a predefined time period, a second expectation of wireless backhaul resource conditions over the predefined time period, a third expectation of user equipment mobility parameters, an expectation of user equipment positioning information, or a combination thereof, of user equipment in a geographic area, a fourth expectation of performance metrics of user equipment in the geographic area, an expected distribution of the first expectation, the second expectation, the third expectation, the fourth expectation, or some combination thereof, over the predefined time period, a confidence level metric of the first expectation, the second expectation, the third expectation, the fourth expectation, or some combination thereof, over the predefined time period, an expected probability density function over radio access network resources, backhaul resources, or a combination thereof, an expectation of inter-cell handover sequences of user equipment in the geographic area, or some combination thereof.

[0186] In various embodiments, the predicted inter-cell interference management policy is provided to a middleware entity.

[0187] In one embodiment, the predicted inter-cell interference management policy includes a cell identifier, an application identifier, a user equipment group identifier, a network slice identifier, a central unit identifier, a distributed unit identifier, a current policy identifier, a new policy identifier, a current traffic steering policy identifier (this identifier can map to one of the following policies for one or more user equipment: 1) intra-frequency gNB selection, 2) inter-frequency gNB selection, 3) central unit selection, 4) distributed unit selection, 5) dual connectivity operation selection), a new traffic steering policy identifier (this can be a traffic steering policy updated based on the predicted inter-cell interference management policy), a confidence level parameter, a flag for enforcement, a time validity indicator, a zone indicator, an overload indication, a high interference indication, a relative narrowband transmit power, an almost blank subframe pattern information, a coordinated multipoint coordination area, a coordinated multipoint scheme, a resource restriction, or some combination thereof.

[0188] In certain embodiments, the receiver requests validation of the predicted inter-cell interference management policy from the conflict resolution function and receives a validation response from the conflict resolution function.

[0189] In some embodiments, the communication is sent and received using an open application program interface.

[0190] In various embodiments, the Al interface is used for communication with a service entity, a management entity, or a combination thereof.

[0191] In one embodiment, the E2 interface is used for communication with a new radio device.

[0192] In certain embodiments, the predicted inter-cell interference management policy is provided to the device via an application exposure function.

[0193] In one embodiment, a method includes receiving at least one monitoring report from a device, determining a monitoring event report based on a subscription and the at least one monitoring report, and providing the monitoring event report to an application.

[0194] In certain embodiments, the method further includes receiving a predicted inter-cell interference management policy from an application, determining at least one radio parameter corresponding to the predicted inter-cell interference management policy, and sending the at least one radio parameter to the device based on the predicted inter-cell interference management policy.

[0195] In some embodiments, the predicted inter-cell interference management policy includes a cell identifier, an application identifier, a user equipment group identifier, a network slice identifier, a central unit identifier, a distributed unit identifier, a current policy identifier, a new policy identifier, a current traffic steering policy identifier (this identifier can map to one of the following policies for one or more user equipment: 1) intra-frequency gNB selection, 2) inter-frequency gNB selection, 3) central unit selection, 4) distributed unit selection, 5) dual connectivity operation selection), a new traffic steering policy identifier (this can be a traffic steering policy updated based on the predicted inter-cell interference management policy), a confidence level parameter, a force enforcement flag, a time validity indicator, a zone indicator, or some combination thereof.

[0196] In various embodiments, the at least one radio parameter includes an overload indication, a high interference indication, a relative narrowband transmit power, an almost blank subframe pattern information, a coordinated multipoint coordination area, a coordinated multipoint scheme, a parameter for traffic steering policy update (handover request indication, source cell identifier, target cell identifier, frequency selection indication, radio access technology selection indication, radio interface selection indication, distributed unit selection indication, central unit selection indication), or some combination thereof.

[0197] In one embodiment, the predicted inter-cell interference management policy is provided to the device via an application exposure function.

[0198] In certain embodiments, the method further includes receiving a subscription request for the subscription from the application.

[0199] In some embodiments, the monitoring event report includes a cell identifier, a user equipment identifier, a network slice identifier, a resource identifier, a resource pool identifier, a user equipment quality of experience degradation indication, a user equipment quality of service degradation indication, a high resource load indication, a high radio access network latency indication, a low backhaul resource availability indication, a quality of service fluctuation indication, a radio link failure indication, or some combination thereof.

[0200] In one embodiment, an apparatus includes a receiver that receives at least one monitoring report from a device, and a processor that: determines a monitoring event report based on a subscription and the at least one monitoring report; and provides the monitoring event report to an application.

[0201] In certain embodiments, the apparatus further includes a transmitter, wherein: the receiver receives a predicted inter-cell interference management policy from the application; the processor determines at least one radio reference corresponding to the predicted inter-cell interference management policy; and the transmitter transmits at least one radio parameter to the device based on the predicted inter-cell interference management policy.

[0202] In some embodiments, the predicted inter-cell interference management policy includes a cell identifier, an application identifier, a user equipment group identifier, a network slice identifier, a central unit identifier, a distributed unit identifier, a current policy identifier, a new policy identifier, a current traffic steering policy identifier (this identifier can map to one of the following policies for one or more user equipment: 1) intra-frequency gNB selection, 2) inter-frequency gNB selection, 3) central unit selection, 4) distributed unit selection, 5) dual connectivity operation selection), a new traffic steering policy identifier (this can be a traffic steering policy updated based on the predicted inter-cell interference management policy), a confidence level parameter, a flag for enforcement, a time validity indicator, a zone indicator, or some combination thereof.

[0203] In various embodiments, the at least one radio parameter includes an overload indication, a high interference indication, a relative narrowband transmit power, an almost blank subframe pattern information, a coordinated multipoint coordination area, a coordinated multipoint scheme, a resource restriction, a parameter for traffic steering policy update (handover request indication, source cell identifier, target cell identifier, frequency selection indication, radio access technology selection indication, radio interface selection indication, distributed unit selection indication, central unit selection indication), or some combination thereof.

[0204] In one embodiment, the predicted inter-cell interference management policy is provided to the device via an application exposure function.

[0205] In certain embodiments, the receiver receives a subscription request for a subscription from the application.

[0206] In some embodiments, the monitoring event report includes a cell identifier, a user equipment identifier, a network slice identifier, a resource identifier, a resource pool identifier, a user equipment quality of experience degradation indication, a user equipment quality of service degradation indication, a high resource load indication, a high radio access network latency indication, a low backhaul resource availability indication, a quality of service fluctuation indication, a radio link failure indication, a bandwidth adaptation requirement, a radio resource adaptation requirement, a traffic steering requirement, or some combination thereof.

[0207] In one embodiment, a method includes: sending at least one monitoring report; and receiving information corresponding to a predicted inter-cell interference management policy in response to sending the at least one monitoring report.

[0208] In certain embodiments, the at least one monitoring report comprises a monitoring event report comprising a cell identifier, a user equipment identifier, a network slice identifier, a resource identifier, a resource pool identifier, a user equipment experience quality degradation indication, a user equipment service quality degradation indication, a high resource load indication, a high radio access network latency indication, a low backhaul resource availability indication, a quality of service fluctuation indication, a radio link failure indication, a bandwidth adaptation requirement, a radio resource adaptation requirement, a traffic steering requirement, or some combination thereof.

[0209] In some embodiments, the predicted inter-cell interference management policy comprises a cell identifier, an application identifier, a user equipment group identifier, a network slice identifier, a central unit identifier, a distributed unit identifier, a current policy identifier, a new policy identifier, a current traffic steering policy identifier (this identifier can map to one of the following policies for one or more user equipment: 1) intra-frequency gNB selection, 2) inter-frequency gNB selection, 3) central unit selection, 4) distributed unit selection, 5) dual connectivity operation selection), a new traffic steering policy identifier (this can be a traffic steering policy updated based on the predicted inter-cell interference management policy), a confidence level parameter, an enforcement flag, a time validity indicator, a zone indicator, an overload indication, a high interference indication, a relative narrowband transmit power, an almost blank subframe pattern information, a coordinated multipoint coordination zone, a coordinated multipoint scheme, a resource restriction, or some combination thereof.

[0210] In various embodiments, the at least one monitoring report is sent to a middleware entity or an application.

[0211] In one embodiment, information corresponding to a predicted inter-cell interference management policy is received from a middleware entity or an application.

[0212] In one embodiment, an apparatus comprises a transmitter that transmits at least one monitoring report and a receiver that receives information corresponding to a predicted inter-cell interference management policy in response to transmitting the at least one monitoring report.

[0213] In certain embodiments, the at least one monitoring report comprises a monitoring event report comprising a cell identifier, a user equipment identifier, a network slice identifier, a resource identifier, a resource pool identifier, a user equipment experience quality degradation indication, a user equipment service quality degradation indication, a high resource load indication, a high radio access network latency indication, a low backhaul resource availability indication, a quality of service fluctuation indication, a radio link failure indication, a bandwidth adaptation requirement, a radio resource adaptation requirement, a traffic steering requirement, or some combination thereof.

[0214] In some embodiments, the predicted inter-cell interference management policy includes a cell identifier, an application identifier, a user equipment group identifier, a network slice identifier, a central unit identifier, a distributed unit identifier, a current policy identifier, a new policy identifier, a current traffic steering policy identifier (this identifier can map to one of the following policies for one or more user equipment: 1) intra-frequency gNB selection, 2) inter-frequency gNB selection, 3) central unit selection, 4) distributed unit selection, 5) dual connectivity operation selection), a new traffic steering policy identifier (this can be a traffic steering policy updated based on the predicted inter-cell interference management policy), a confidence level parameter, an enforcement flag, a time validity indicator, a zone indicator, an overload indication, a high interference indication, a relative narrowband transmit power, an almost blank subframe pattern information, a coordinated multipoint coordination zone, a coordinated multipoint scheme, a resource restriction, or some combination thereof.

[0215] In various embodiments, the at least one monitoring report is sent to a middleware entity or an application.

[0216] In one embodiment, information corresponding to the predicted inter-cell interference management policy is received from a middleware entity or an application.

[0217] In one embodiment, a method includes sending an initial configuration, receiving a request for modeling information in response to sending the initial configuration, and sending the modeling information in response to receiving the request, wherein the modeling information includes traffic parameters, radio parameters, mobility parameters, or some combination thereof, and the modeling information includes at least one machine learning model.

[0218] In certain embodiments, the initial configuration is sent to an application.

[0219] In some embodiments, the initial configuration is sent from a service entity, a management entity, or a combination thereof.

[0220] In various embodiments, the initial configuration includes a cell identifier, a network slice identifier, a service type, an application type, a profile, a list of policy identifiers, per-policy metrics, per-policy thresholds, an interference management preference, an enforcement flag, a middleware flag, a middleware identifier, a time validity indicator, a geographical zone, a vertical-specific parameter, a cross-vertical parameter, or some combination thereof.

[0221] In one embodiment, the initial configuration is configured per vertical customer.

[0222] In certain embodiments, the modeling information includes: a first expectation of radio access network resource conditions over a predefined time period; a second expectation of wireless backhaul resource conditions over the predefined time period; a third expectation of user equipment mobility parameters, an expectation of user equipment positioning information, or a combination thereof, of user equipment in the geographic region; a fourth expectation of performance metrics of user equipment in the geographic region; an expected distribution of the first expectation, the second expectation, the third expectation, the fourth expectation, or some combination thereof, over the predefined time period; a confidence level metric of the first expectation, the second expectation, the third expectation, the fourth expectation, or some combination thereof, over the predefined time period; an expected probability density function over the radio access network resources, the backhaul resources, or a combination thereof; an expectation of inter-cell handover sequences of user equipment in the geographic region; or some combination thereof.

[0223] In one embodiment, an apparatus comprises: a transmitter that transmits an initial configuration; a receiver that receives a request for modeling information in response to transmitting the initial configuration; wherein the transmitter transmits the modeling information in response to receiving the request, wherein the modeling information includes traffic parameters, radio parameters, mobility parameters, or some combination thereof, and the modeling information includes at least one machine learning model.

[0224] In certain embodiments, the initial configuration is transmitted to an application.

[0225] In some embodiments, the initial configuration is transmitted from a service entity, a management entity, or a combination thereof.

[0226] In various embodiments, the initial configuration includes a cell identifier, a network slice identifier, a service type, an application type, a profile, a list of policy identifiers, per-policy metrics, per-policy thresholds, interference management preferences, enforcement flags, middleware flags, middleware identifiers, time validity indicators, geographic regions, vertical-specific parameters, cross-vertical parameters, or some combination thereof.

[0227] In one embodiment, the initial configuration is configured per vertical customer.

[0228] In certain embodiments, the modeling information comprises: a first expectation of radio access network resource conditions over a predefined time period; a second expectation of wireless backhaul resource conditions over a predefined time period; a third expectation of user equipment mobility parameters, an expectation of user equipment positioning information, or a combination thereof, of user equipment in a geographic region; a fourth expectation of performance metrics of user equipment in a geographic region; an expected distribution of the first expectation, the second expectation, the third expectation, the fourth expectation, or some combination thereof, over a predefined time period; a confidence level metric of the first expectation, the second expectation, the third expectation, the fourth expectation, or some combination thereof, over a predefined time period; an expected probability density function over radio access network resources, backhaul resources, or a combination thereof; an expectation of inter-cell handover sequences of user equipment in a geographic region; or some combination thereof.

[0229] In one embodiment, a method comprises: receiving a predictive resource management policy from at least one application; determining at least one radio parameter corresponding to the predictive resource management policy; and sending the at least one radio parameter to a device based on the predictive resource management policy.

[0230] In certain embodiments, the predictive resource management policy comprises an application identifier, a user equipment group identifier, a cell identifier, a network slice identifier, a central unit identifier, a distributed unit identifier, a current inter-cell interference management policy identifier, a new inter-cell interference policy identifier, a current traffic steering policy identifier (this identifier can map to one of the following policies for one or more user equipment: 1) intra-frequency gNB selection 2), inter-frequency gNB selection, 3) central unit selection, 4) distributed unit selection, 5) dual connectivity operation selection), a new traffic steering policy identifier (this can be a traffic steering policy updated based on the predicted inter-cell interference management policy), a confidence level parameter, an enforcement flag, a time validity indicator, a zone indicator, or some combination thereof.

[0231] In some embodiments, the at least one radio parameter comprises an overload indication, a high interference indication, a relative narrowband transmit power, an almost blank subframe pattern information, a coordinated multipoint coordination area, a coordinated multipoint scheme, a resource restriction, a parameter for traffic steering policy update (handover request indication, source cell identifier, target cell identifier, frequency selection indication, radio access technology selection indication, radio interface selection indication, distributed unit selection indication, central unit selection indication), or some combination thereof.

[0232] In various embodiments, the predictive resource management policy is provided to the device via an application exposure function.

[0233] In one embodiment, the device comprises at least one network element, at least one user equipment, or a combination thereof.

[0234] In certain embodiments, the at least one radio parameter is further determined based on at least one predefined rule corresponding to an application type, a service type, or a combination thereof.

[0235] In some embodiments, the predefined rule includes a key performance indicator, a service type identifier, an application type identifier, a radio access network identifier, a network slice profile, a service profile, a quality of service target (guaranteed traffic bit rate, maximum traffic bit rate, priority class, packet delay budget parameter, reliability parameter, packet error rate parameter), a quality of experience target (quality of experience score, initial buffering parameter, stall event, stall ratio, mean opinion score), a priority identifier, an application quality of service to network quality of service mapping information, or some combination thereof.

[0236] In various embodiments, the method further includes receiving at least one monitoring report from the device, determining a monitoring event report based on the subscription and the at least one monitoring report, and sending the monitoring event report to the application.

[0237] In one embodiment, the method further includes receiving a subscription request for the subscription from the application.

[0238] In certain embodiments, the monitoring report includes a user equipment quality of service parameter, a user equipment quality of experience parameter, a radio resource quality parameter, a computed radio access network resource load parameter, a central unit load, a distributed unit load, a channel state information, a radio resource management measurement, a radio link monitoring measurement, a received signal strength indicator, a reference signal received power parameter, a handover failure monitoring parameter, or some combination thereof.

[0239] In some embodiments, the monitoring report further includes a backhaul radio resource quality parameter, a backhaul channel state information, a backhaul radio resource management measurement, a backhaul radio link monitoring measurement, a backhaul topology parameter, a backhaul type parameter, or some combination thereof.

[0240] In various embodiments, the monitoring event report is determined based on an offline user equipment analysis, an online user equipment analysis, a radio resource quality analysis, or some combination thereof.

[0241] In one embodiment, the monitoring event report includes a cell identifier, a user equipment identifier, a network slice identifier, a resource identifier, a resource pool identifier, a user equipment quality of experience degradation indication, a user equipment quality of service degradation indication, a high resource load indication, a high radio access network latency indication, a low backhaul resource availability indication, a quality of service fluctuation indication, a radio link failure indication, a bandwidth adaptation requirement, a radio resource adaptation requirement, a traffic steering requirement, or some combination thereof.

[0242] In one embodiment, an apparatus includes: a receiver that receives a predictive resource management policy from at least one application; a processor that determines at least one radio parameter corresponding to the predictive resource management policy; and a transmitter that transmits at least one radio parameter to the apparatus based on the predictive resource management policy.

[0243] In some embodiments, the predictive resource management policy includes an application identifier, a user equipment group identifier, a cell identifier, a network slice identifier, a central unit identifier, a distributed unit identifier, a current inter-cell interference management policy identifier, a new inter-cell interference policy identifier, a current service redirection policy identifier (this identifier may be mapped to one of the following policies for one or more user equipments: 1) intra-frequency gNB selection, 2) inter-frequency gNB selection, 3) central unit selection, 4) distributed unit selection, 5) dual connectivity operation selection), a new service redirection policy identifier (this may be a service redirection policy updated based on the predictive inter-cell interference management policy), a confidence level parameter, an enforcement flag, a time validity indicator, a region indicator, or some combination thereof.

[0244] In some embodiments, at least one radio parameter includes overload indication, high interference indication, relatively narrowband transmit power, nearly blank subframe pattern information, coordinated multipoint coordination area, coordinated multipoint scheme, resource constraints, parameters for service transition policy updates (handover request indication, source cell identifier, target cell identifier, frequency selection indication, radio access technology selection indication, radio interface selection indication, distributed unit selection indication, central unit selection indication) or some combinations thereof.

[0245] In various embodiments, predictive resource management strategies are provided to the device via application exposure functionality.

[0246] In one embodiment, the device includes at least one network unit, at least one user equipment, or a combination thereof.

[0247] In some embodiments, at least one radio parameter is further determined based on at least one predefined rule corresponding to an application type, service type, or a combination thereof.

[0248] In some embodiments, predefined rules include key performance indicators, service type identifiers, application type identifiers, radio access network identifiers, network slice profiles, service profiles, quality of service objectives (guaranteed traffic bit rate, maximum traffic bit rate, priority level, packet delay budget parameter, reliability parameter, packet error rate parameter), quality of experience objectives (quality of experience score, initial buffer parameter, delay events, delay ratio, average opinion score), priority identifiers, application service quality to network service quality mapping information, or some combination thereof.

[0249] In various embodiments: the receiver receives at least one monitoring report from the device; the processor determines a monitoring event report based on the subscription and the at least one monitoring report; and the transmitter sends the monitoring event report to the application.

[0250] In one embodiment, the receiver receives a subscription request for a subscription from the application.

[0251] In certain embodiments, the monitoring report includes a user equipment quality of service parameter, a user equipment quality of experience parameter, a radio resource quality parameter, a computed radio access network resource load parameter, a central unit load, a distributed unit load, channel state information, a radio resource management measurement, a radio link monitoring measurement, a received signal strength indicator, a reference signal received power parameter, a handover failure monitoring parameter, or some combination thereof.

[0252] In some embodiments, the monitoring report further includes a backhaul radio resource quality parameter, backhaul channel state information, a backhaul radio resource management measurement, a backhaul radio link monitoring measurement, a backhaul topology parameter, a backhaul type parameter, or some combination thereof.

[0253] In various embodiments, the monitoring event report is determined based on offline user equipment analysis, online user equipment analysis, radio resource quality analysis, or some combination thereof.

[0254] In one embodiment, the monitoring event report includes a cell identifier, a user equipment identifier, a network slice identifier, a resource identifier, a resource pool identifier, a user equipment quality of experience degradation indication, a user equipment quality of service degradation indication, a high resource load indication, a high radio access network latency indication, a low backhaul resource availability indication, a quality of service fluctuation indication, a radio link failure indication, a bandwidth adaptation requirement, a radio resource adaptation requirement, a traffic steering requirement, or some combination thereof.

[0255] Embodiments can be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the application is, therefore, indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims

1. A method performed by a first network entity, the method comprising: Receive at least one Quality of Service (QoS) monitoring report from the second network entity; Based on application subscriptions and real-time analysis, the at least one QoS monitoring report is transformed into a monitoring event report; as well as The monitoring event report is provided to the application, wherein the application includes xAPP associated with a third network entity.

2. The method according to claim 1, further comprising: Receive the predicted inter-cell interference management strategy from the application; Determine at least one radio parameter corresponding to the predicted inter-cell interference management strategy; as well as The at least one radio parameter is sent to the second network entity based on the predicted inter-cell interference management strategy.

3. The method according to claim 2, wherein, The predicted inter-cell interference management strategy includes one or more of the following: cell identifier, application identifier, user equipment (UE) group identifier, network slice identifier, central unit (CU) identifier, distributed unit (DU) identifier, current policy identifier, new policy identifier, current service redirection policy identifier, new service redirection policy identifier, confidence level parameter, enforcement flag, time validity indicator, or area indicator.

4. The method according to claim 2, wherein, The at least one radio parameter includes one or more of the following: overload indication, high interference indication, relative narrowband transmit power, near-blank subframe pattern information, coordinated multipoint coordination area, coordinated multipoint scheme, resource limitation, handover request indication, source cell identifier, target cell identifier, frequency selection indication, radio access technology (RAT) selection indication, radio interface selection indication, distributed unit (DU) selection indication, or central unit (CU) selection indication.

5. The method according to claim 2, wherein, The predicted inter-cell interference management strategy is provided to the second network entity via the application exposure function.

6. The method of claim 1, further comprising receiving a subscription request for the subscription from the application.

7. The method according to claim 1, wherein, The monitoring event report includes one or more of the following: cell identifier, user equipment (UE) identifier, network slice identifier, resource identifier, resource pool identifier, UE quality of experience (QoE) degradation indication, UE QoS degradation indication, high resource load indication, high radio access network latency indication, low backhaul resource availability indication, QoS fluctuation indication, radio link failure (RLF) indication, bandwidth adaptation requirement, radio resource adaptation requirement, or service shifting requirement.

8. A first network entity, comprising: A receiver that receives at least one Quality of Service (QoS) monitoring report from a second network entity; as well as Processor, the processor: Based on application subscriptions and real-time analysis, the at least one QoS monitoring report is transformed into a monitoring event report; and The monitoring event report is provided to the application, wherein the application includes xAPP associated with a third network entity.

Images