WO2022217083A1 - Procédés et appareil pour prendre en charge une optimisation de gestion de ressources radio (rrm) pour des instances de tranches de réseau dans des systèmes 5g - Google Patents

Procédés et appareil pour prendre en charge une optimisation de gestion de ressources radio (rrm) pour des instances de tranches de réseau dans des systèmes 5g Download PDF

Info

Publication number
WO2022217083A1
WO2022217083A1 PCT/US2022/024066 US2022024066W WO2022217083A1 WO 2022217083 A1 WO2022217083 A1 WO 2022217083A1 US 2022024066 W US2022024066 W US 2022024066W WO 2022217083 A1 WO2022217083 A1 WO 2022217083A1
Authority
WO
WIPO (PCT)
Prior art keywords
rrm
measurements
network
mns
network slice
Prior art date
Application number
PCT/US2022/024066
Other languages
English (en)
Inventor
Joey Chou
Yizhi Yao
Shu-Ping Yeh
Original Assignee
Intel Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corporation filed Critical Intel Corporation
Priority to CN202280020295.1A priority Critical patent/CN117099390A/zh
Publication of WO2022217083A1 publication Critical patent/WO2022217083A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/50—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP for cross-charging network operators
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices

Definitions

  • This disclosure generally relates to field of wireless communications, and more particularly relates to methods and apparatus related to radio resource management in network slice instances that dynamically manage logical discrete end-to-end networks.
  • the next generation mobile networks in particular, Third Generation Partnership Project (3GPP) systems such as Fifth Generation (5G) and Long-Term Evolution (LTE) and the evolutions thereof, are among the latest cellular wireless technologies developed to deliver ten times faster data rates than LTE and are being deployed with multiple carriers in the same area and across multiple spectrum bands.
  • Network slices are end-to-end virtual networks that share the resources of a physical network including core network (CN) and radio access network (RAN) resources.
  • Slicing RAN resources includes maintaining isolation of network slices while handling distribution of radio resources. What is needed is methods and apparatus to optimize and support radio resource management (RMM) for network slice instances.
  • RRMM radio resource management
  • FIG. 1 illustrates a wireless network in accordance with an embodiment of the disclosure.
  • FIG. 2 illustrates an operation flow diagram in accordance with an embodiment of the disclosure.
  • FIG. 3 illustrates a flow diagram of a method in accordance with an embodiment of the disclosure.
  • FIG. 4 illustrates an exemplary network in accordance with various embodiments of the disclosure.
  • FIG. 5 illustrates an exemplary wireless network in accordance with various embodiments of the disclosure.
  • this disclosure is generally directed to systems and methods for supporting radio resource management (RRM) optimization for network slice instances in 5G systems.
  • RRM radio resource management
  • 5G networks are becoming increasingly complex with the densification of millimeter- wave small cells, and various new services, such as eMBB (enhanced Mobile Broadband), URLLC (Ultra Reliable Low Latency Communications), and mMTC (massive Machine Type Communications) that are characterized by high speed high data volume, low speed ultra-low latency, and infrequent transmitting low data volume from a large number of emerging smart devices, respectively.
  • eMBB enhanced Mobile Broadband
  • URLLC Ultra Reliable Low Latency Communications
  • mMTC massive Machine Type Communications
  • the network traffic tends to be sporadic, where there may be different usage patterns in terms of time, location, UE distribution, and types of applications. For example, most IoT sensor applications may run during off-peak hours or weekends. Special events, such as sports games, and concerts, can cause traffic demand to shoot up at certain times and locations. Therefore, the radio resource monitoring (RRM) resources allocated among network slice instance(s) need to be optimized to ensure the RRM resources are efficiently used while providing quality end-user experience and performance.
  • RRM resource optimization function trains the artificial intelligence/machine learning ( AI/ML) model, based on the huge volume of performance data collected over days, weeks, and months from RAN nodes. The RRM resource optimization function then uses the AI/ML model to predict the traffic demand patterns of 5G networks at different times and locations for a network slice instance and automatically re-allocates the RRM resources ahead of surfaced network issues.
  • AI/ML artificial intelligence/machine learning
  • one or more embodiments are directed to RRM resource optimization for network slice instances in 5G networks targeting 3GPP technical standard for 5G section TS 28.313 which covers self-organizing networks (SONs).
  • One or more embodiments are directed to Mobility Robustness Optimization (MRO).
  • MRO Mobility Robustness Optimization
  • some embodiments may include one or more RRM resource optimization requirements, RRM resource optimization use cases, management services, and information definitions to support RRM resource optimization and RRM resource optimization procedures.
  • One or more embodiments are further directed to a centralized SON (C-SON), and RRM resource optimations for network slice instances.
  • C-SON centralized SON
  • embodiments herein enable the optimization of the RRM resources allocated among network slice instances to ensure the RRM resources are efficiently used, while providing quality end-user experience and performance.
  • One or more embodiments are directed to centralized self-organized networks (C-SON) functions to support RRM resource optimization for network slices instances.
  • C-SON functions affect gNBs such a 5G nodes that produce provisioning management services (MnS).
  • MnS provisioning management services
  • 5G new radio cells are in operation and an AI/ML model is created based on the RRM related performance measurements previously received.
  • a method for a C-SON function includes collecting RRM related measurements on a per network slice instance basis.
  • measurements can include mean DL/UL PRB used for data traffic, mean number of DRBs successfully setup, and mean number of PDU sessions successfully set up and the like.
  • the C- SON function collects the RRM related measurements on a per network slice instance based by consuming the management services (MnS) of performance assurance.
  • MnS management services
  • the C-SON function analyzes the measurements to train the AI/ML model and determines the actions required to optimize the RRM resources for network slice instance(s) that include consuming the MnS of provisioning to update the appropriate RRM policies.
  • the method is reflected in a traceable function “REQ- RRM-FUN-1” as a producer of provisioning MnS that have the capability of allowing authorized consumers to update RRM policies, and REQ-RRM.
  • Management Services (MnS) under 3 GPP are service oriented such an MnS consumer and an MnS producer interact such that MnS consumers may request operations from an MnS producer, and request performance assurances, notifications, services and the like.
  • MnS Management Services
  • 3GPP defines three types of management that can interact and flexibly accommodate network operations.
  • the MnS For the MnS that includes a group of management operations and notifications agnostic of managed entities, the MnS is referred to as type A.
  • the MnS For the MnS with management information represented by an information model of managed entities, the MnS is referred to as Type B.
  • the MnS For the MnS with the performance information of a managed entity and fault information of the managed entity, the MnS is referred to as Type C.
  • MnS components A, B and C allow MnS service components to conform to the needs of the network technology to be managed and the automation requirements of a network and/or the service operations.
  • an MnS may include a combination of component type A and type B, or a combination of A, B and C types of service components.
  • RRM resource optimization type A may be shown as illustrated in Table 1, below, associated with 3GPP Technical Specification (TS) 28.531, 532 and 28.550 related to provisioning for network functions (NF).
  • TS Technical Specification
  • NF network functions
  • embodiments relate to component types for Managed Object Instance (MOI) operations and attributes.
  • Table 1 RRM resources optimization type A.
  • One or more embodiments are directed to technical specifications for 3 GPP specifications for management services for C-SON management including MnS component type B definitions with parameters updated for shown as illustrated in Table 2, below, associated with 3GPP Technical Specification (TS) 28.541 related to RRM related parameters.
  • TS Technical Specification
  • One or more embodiments are directed to technical specifications for 3 GPP specifications for management services for C-SON management including MnS component type C definitions with parameters updated for shown as illustrated in Table 3, below, associated with 3GPP Technical Specification (TS) 28.552, clause 5.1.1.2.5 and 5.1.1.2.7, 5.1.1.3.1-4 related to RRM performance measurements.
  • Table 3 RRM related performance measurements.
  • One or more embodiments are directed to technical specifications for 3 GPP specifications for management services for C-SON, specifically related to RRM resources optimization for network slice instances. Specifically, referring now to FIG. 1, an example of network slice instances are shown in an example network 100.
  • a base station in 5G networks also referred to as G NodeB (gNB) can be physically separated into a central unit and a distributed unit (CU and DU).
  • the central unit is further separated to illustrate a central unit with a user plane (CUUP) and a central unit with a control plane (CUCP).
  • CUUP user plane
  • CUCP control plane
  • a DU 110 is coupled to a CUUP 120 and a CUCP 130, which are both coupled to a 5G core network, shown as 5GC 150.
  • Distributed unit 110 is shown with network slices formed, including slice 140, 142 and 144, which may represent slice instances created to support various services, such as URLLC, eMBB, or mMTC with different RRM resources requirements, wherein network slice instances 142 and 144 represent sNSSAi #2-1 and sNSSAi #2-2 and support RRM requirements and network slice instances nSSAi #1 140 supports different RRM requirements.
  • slice 140, 142 and 144 may represent slice instances created to support various services, such as URLLC, eMBB, or mMTC with different RRM resources requirements, wherein network slice instances 142 and 144 represent sNSSAi #2-1 and sNSSAi #2-2 and support RRM requirements and network slice instances nSSAi #1 140 supports different RRM requirements.
  • DU 100, CUUP 120 and CUCP 130 are characterized by RRMPolicy Ratio for Information Obect Class (IOC) with RRMPolicyMaxRatio, RRMPolicyMinRatio, and RRMPolicyDedicatedRatio attributes to define the shared resources, prioritized resources, and dedicated resources for network slice instances as provided in 3GPP specification 28.541.
  • IOC Information Obect Class
  • the RRMPolicy Ratio IOC has a base class RRMPolicy IOC that contains resourceType (e.g. PRB for DU, DRB for CUUP, and RRC connected user for CUCP) and RRMPolicyMemberList that contains the network slice instance(s) subject to this policy (see 3GPP specification clause 4.3.43 in TS 28.541.
  • a network function may have one or more RRMPolicy Ratio MOI(s) wherein each RRMPolicyRatio MOI is associated with network slice instance(s) that share the same RRM resource requirements.
  • the attribute RRMPolicyMaxRatio defines the maximum resource usage quota for the associated RRMPolicyMemberList, including at least one of shared resources, prioritized resources and dedicated resources.
  • the sum of the ‘ RRMPolicyMaxRatio ’ values assigned to all RRMPolicyRatio(s) name-contained by the same MangedEntity can be greater than 100.
  • the attribute RRMPolicyMinRatio defines the minimum resource usage quota for the associated RRMPolicyMemberList, including at least one of prioritized resources and dedicated resources, which provides the resources quota that need to be guaranteed for use by the associated RRMPolicyMemberList.
  • the sum of the ‘ RRMPolicyMinRatio ’ values assigned to all RRMPolicyRatio(s) name-contained by same Manged Entity is less or equal to 100.
  • the attribute RRMPolicyDedicatedRatio defines the dedicated resource usage quota for the RRMPolicyMemberList, including dedicated resources.
  • the sum of the RRM Policy DedicaiedRalio' values assigned to all RRMPolicyRatio(s) name-contained by same Manged Entity is less than or equal to 100.
  • shared resources means the resources that are shared with other RRMPolicyMemberList(s). Specifically, the RRMPolicyMemberList(s) defined in RRMPolicyRatio(s) name-contained by the same Managed Entity. The shared resources are not guaranteed for use by the associated RRMPolicyMemberList.
  • the shared resources quota is represented by [ RRMPolicyMaxRatio-RRMPolicyMinRatio ].
  • prioritized resources means the resources are preferentially used by the associated RRMPolicyMemberList. Prioritized resources are guaranteed for use by the associated RRMPolicyMemberList when it needs to use them. When not used, prioritized resources may be used by other RRM Policy Membe rList(s) in particular, the RRMPolicyMemberList(s) defined in RRMPolicyRatio(s) name-contained by the same Managed Entity.
  • the prioritized resources quota is represented by RRMPolicyMinRatio- RRMPolicyDedicatedRatio.
  • dedicated resources means the resources are dedicated for use by the associated RRMPolicyMemberList. These resources can not be shared even if the associated RRMPolicyMember does not use them.
  • the Dedicated resources quota is represented by [RRMPolicyDedicatedRatio] .
  • one or more embodiments are directed to RRM policies for multiple network slice instances illustrated by how a C-SON function consumes MnS of performance assurances and creates performance management (PM) jobs to collect RRM- related measurements.
  • FIG. 2 shows an artificial intelligence/machine learning (AI/ML) model based on user plane and control plane loads and traffic patterns collected from received RRM related performance measurements.
  • AI/ML artificial intelligence/machine learning
  • FIG. 2 illustrates network 200 with C-SON function 210, producer of performance assurances MnS 220, producer of provisioning MnS 230, network function (NF) DU 240, NF CUUP 250 and NF CUCP 260.
  • C-SON function 210 producer of performance assurances MnS 220
  • MnS 230 producer of provisioning MnS 230
  • network function (NF) DU 240 network function (NF) 240
  • NF CUUP 250 NF CUCP 260.
  • RRM resources optimization includes a loop 270, that C-SON function receives RRM related measurements from network function CUCP 271, network function CUUP 272, network function DU 273.
  • step 274 analyzing the measurements to train the A I/M L model and determine the actions to optimize the RRM resources.
  • Optional step 275 provides that if the RRM resources for the network slice instances at the distributed unit need updating, then at step 276 there is a MODIFYMOIAttributes to update the RRMPolicyRatio and at step 277 an update to the RRMPolicy Ratio followed by a notification at step 278 NotifyMOIAttributesValueChange to indicate a successful update.
  • Optional step 280 provides that if the RRM resources for the network slices at the CUUP need an update, then at step 282 an update to the RRMPolicyRatio 283 is followed by a notification at step 284 NotifyMOIAttributesValueChange to indicate a successful update.
  • Optional step 288 provides that if the RRM resources for the network slices at the CUCP need an update, then at step 290 an update to the RRMPolicyRatio 291 is followed by a notification at step 292 NotifyMOIAttributesValueChange to indicate a successful update.
  • Block 310 provides for a C-SON function to receive RRM related measurements from a producer of performance assurance MnS (220) which received measurements from a distributed unit, and monitor the performance of network slice instances.
  • MnS performance assurance MnS
  • FIG. 1 slices are identified by sNSSAI #1, sNSSAI #2-1 and SNSSAI #2-2.
  • Producer of performance assurance MnS 220 is shown in FIG. 2 as coupled to NF DU 240.
  • Measurements can mean, for example, mean and peak numbers of PRB usage on downlink and uplink user equipment (UE), throughput with respect to a gNode base station (gNB), and the distribution of a downlink/uplink UE throughput of gNB from network function distributed unit (NF DU).
  • UE downlink and uplink user equipment
  • gNB gNode base station
  • NF DU network function distributed unit
  • Block 320 provides for the C-SON function to receive RRM related measurements from a producer of performance assurance MnS (220) which received measurements from NF CUUP to monitor the performance of network slice instances, such as those identified in FIG. 1 including sNSSAI #1, sNSSAI #2-1 and SNSSAI #2-2.
  • the measurements may include mean and peak numbers of measurements related to data radio bearers (DRBs) that are successfully set up.
  • NF CUUP is shown in FIG. 2 as NF CUUP 250.
  • Block 330 provides for the C-SON function to receive RRM related measurements from a producer of performance assurance MnS (220) which received measurements from NF CUCP to monitor the performance of network slice instances.
  • MnS performance assurance
  • the measurements may include mean numbers of protocol data unit (PDU) sessions requested to setup, mean numbers of PDU sessions successfully setup.
  • NF CUCP is shown in FIG. 2 as NF CUCP 260.
  • Block 340 provides for the C-SON function to analyze the measurements received and to train an artificial intelligence/machine learning model and determine actions needed to optimize RRM resources for network slice instances for MnS consumers and for provisioning to update RRMPolicy Ratio corresponding to network slice instances.
  • Block 350 provides that if RRM resources for a network slice instance at a distributed unit requires an update, then the C-SON function receives the MnS NF provisioning with modify MOl Attributes and reconfigures the RRMPolicy Ratio for the NF DU and the MnS updates RRMPolicy Ratio at the NF DU.
  • Block 3502 within block 350 provides that C-SON function receive from a producer of provisioning MnS, such as producer 230, shown in FIG. 2, a notification notifyMOIAttributeValueChange to C-SON to indicate a successful RRMPolicy Ratio update.
  • a producer of provisioning MnS such as producer 230, shown in FIG. 2
  • notifyMOIAttributeValueChange to C-SON to indicate a successful RRMPolicy Ratio update.
  • Block 360 provides that if RRM resources for a network slice instance at CUUP need an update that the C-SON function receives from the producer of provisioning MnS, such as 230, operation modify MOl Attributes to reconfigure the RRMPolicy Ratio for the NF CUUP 250.
  • Block 3602 within block 360 provides for producer of provisioning MnS then to update RRMPolicy Ratio at the NF CUUP 260.
  • Block 3604 provides for the C-SON function to receive from producer of provisioning MnS a notification notifyMOIAttributeValueChange to indicate the successful RRMPolicy Ratio update.
  • Block 370 provides that if RRM resources for a network slice instance at CUCP need an update that the C-SON function receives from the producer of provisioning MnS a modify MOl Attributes operation to reconfigure the RRMPolicy Ratio for the NF CUCP, such as NF CUCP 260.
  • block 3702 which provides for the producer of provisioning MnS to update the RRMPolicy Ratio at the NF CUCP 260.
  • block 3704 which provides that C-SON function receive from the producer of provisioning MnS a notification notifyMOIAttributeValueChange to indicate a successful RRMPolicy Ratio update.
  • FIG. 3 represents a method for a operating a New Radio (NR) network that includes a C-SON function configured to support a RRM resources optimization function, wherein the C-SON function is to consume the performance assurance MnS to create performance management PM jobs to collect RRM related measurements from RAN nodes, such as DU, CUUP, and CUCP as shown in FIG.s 1 and 2.
  • the C-SON function creates the AI/ML model based on the user plane and control plane information based on traffic loads and patterns that are collected from the RRM related performance measurements.
  • the C-SON function consumes the performance assurance MnS to receive RRM related measurements from RAN nodes, such as DU, CUUP, and CUCP to monitor the performance of network slice instance(s) identified by one or more single network slice selection assistance information (sNSSAI).
  • RAN nodes such as DU, CUUP, and CUCP to monitor the performance of network slice instance(s) identified by one or more single network slice selection assistance information (sNSSAI).
  • sNSSAI single network slice selection assistance information
  • the C-SON function then analyzes the measurements to train the AI/ML model and determines the actions if needed to optimize the RRM resources for network slice instances.
  • the network slice instances identified by sNSSAI support various services, such as URLLC, eMBB, or mMTC with different RRM resources requirements.
  • a RRMPolicy Ratio IOC has been created for a network function (e.g. DU, CUUP, and CUCP) where the RRMPolicy Ratio IOC contains rRMPolicyMaxRatio, rRMPolicyMinRatio, and rRMPolicyDedicatedRatio attributes to define the shared resources, prioritized resources, and dedicated resources for one more network slice instance(s) that share the same RRM resource requirements.
  • a network function e.g. DU, CUUP, and CUCP
  • a network function may have one or more RRMPolicy Ratio MOI(s), where each RRMPolicy Ratio MOI defines the RRM resource requirements for network slice instance(s).
  • the RRMPolicy Ratio IOC has a base class RRMPolicy IOC that includes resourceType that define the resource to which the RRM policy applies and eRMPolicyMemberList that contains the network slice instance(s) subject to the RRM policy.
  • the resourceType in the RRMPolicy IOC defines resources for network functions, for example, PRB for DU, DRB for CUUP, and RRC connected user for CUCP.
  • the measurements received from DU that are used to determine if the RRM resources in DU needed to be updated include those described in Table
  • the measurements received from CUUP that are used to determine if the RRM resources in CUUP needed to be updated include those shown in Table
  • the measurements received from CUCP that are used to determine if the RRM resources needed to be updated include those in Table 5, below:
  • the C-SON function optimizes the RRM resources for network slice instance(s), by consuming the MnS of NF provisioning with modify MOI Attributes operation to re-configure the RRMPolicy Ratio for the NF DU, and receive a notification notifyMOIAttributeValueChange indicating the successful
  • RRMPolicy Ratio update then consumes the MnS of NF provisioning with modifyMOIAttributes operation to re-configure the RRMPolicy Ratio for the NF CUUP, and receive a notification notifyMOIAttributeValueChange indicating the successful RRMPolicy Ratio update, and consumes the MnS of NF provisioning with modifyMOIAttributes operation to re-configure the RRMPolicy Ratio for the NF CUCP, and receive a notification notifyMOIAttributeValueChange indicating the successful
  • Figures 4-5 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.
  • FIG. 4 illustrates a network 400 in accordance with various embodiments.
  • the network 400 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems.
  • 3GPP technical specifications for LTE or 5G/NR systems 3GPP technical specifications for LTE or 5G/NR systems.
  • the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems, or the like.
  • the network 400 may include a UE 402, which may include any mobile or non-mobile computing device designed to communicate with a RAN 404 via an over-the-air connection.
  • the UE 402 may be communicatively coupled with the RAN 404 by a Uu interface.
  • the UE 402 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, IoT device, etc.
  • the network 400 may include a plurality of UEs coupled directly with one another via a sidelink interface.
  • the UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.
  • the UE 402 may additionally communicate with an AP 406 via an over-the-air connection.
  • the AP 406 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 404.
  • the connection between the UE 402 and the AP 406 may be consistent with any IEEE 802.11 protocol, wherein the AP 406 could be a wireless fidelity (Wi-Fi®) router.
  • the UE 402, RAN 404, and AP 406 may utilize cellular- WLAN aggregation (for example, LWA/LWIP).
  • Cellular- WLAN aggregation may involve the UE 402 being configured by the RAN 404 to utilize both cellular radio resources and WLAN resources.
  • the RAN 404 may include one or more access nodes, for example, AN 408.
  • AN 408 may terminate air-interface protocols for the UE 402 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 408 may enable data/voice connectivity between CN 420 and the UE 402.
  • the AN 408 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool.
  • the AN 408 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc.
  • the AN 408 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.
  • the RAN 404 may be coupled with one another via an X2 interface (if the RAN 404 is an LTE RAN) or an Xn interface (if the RAN 404 is a 5G RAN).
  • the X2/Xn interfaces which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.
  • the ANs of the RAN 404 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 402 with an air interface for network access.
  • the UE 402 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 404.
  • the UE 402 and RAN 404 may use carrier aggregation to allow the UE 402 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell.
  • a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG.
  • the first/second ANs may be any combination of eNB, gNB, ng-eNB, etc.
  • the RAN 404 may provide the air interface over a licensed spectrum or an unlicensed spectrum.
  • the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells.
  • the nodes Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.
  • LBT listen-before-talk
  • the UE 402 or AN 408 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications.
  • An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE.
  • An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like.
  • an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs.
  • the RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic.
  • the RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services.
  • the components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.
  • the RAN 404 may be an LTE RAN 410 with eNBs, for example, eNB 412.
  • the LTE RAN 410 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc.
  • the LTE air interface may rely on CSI- RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE.
  • the LTE air interface may operating on sub-6 GHz bands.
  • the RAN 404 may be an NG-RAN 414 with gNBs, for example, gNB 416, or ng-eNBs, for example, ng-eNB 418.
  • the gNB 416 may connect with 5G-enabled UEs using a 5G NR interface.
  • the gNB 416 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface.
  • the ng-eNB 418 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface.
  • the gNB 416 and the ng-eNB 418 may connect with each other over an Xn interface.
  • the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 414 and a UPF 448 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN414 and an AMF 444 (e.g., N2 interface).
  • NG-U NG user plane
  • N3 interface e.g., N3 interface
  • N-C NG control plane
  • the NG-RAN 414 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data.
  • the 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface.
  • the 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking.
  • the 5G- NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz.
  • the 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH.
  • the 5G-NR air interface may utilize BWPs for various purposes.
  • BWP can be used for dynamic adaptation of the SCS.
  • the UE 402 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 402, the SCS of the transmission is changed as well.
  • Another use case example of BWP is related to power saving.
  • multiple BWPs can be configured for the UE 402 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios.
  • a BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 402 and in some cases at the gNB 416.
  • a BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.
  • the RAN 404 is communicatively coupled to CN 420 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 402).
  • the components of the CN 420 may be implemented in one physical node or separate physical nodes.
  • NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 420 onto physical compute/storage resources in servers, switches, etc.
  • a logical instantiation of the CN 420 may be referred to as a network slice, and a logical instantiation of a portion of the CN 420 may be referred to as a network sub-slice.
  • the CN 420 may be an LTE CN 422, which may also be referred to as an EPC.
  • the LTE CN 422 may include MME 424, SGW 426, SGSN 428, HSS 430, PGW 432, and PCRF 434 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 422 may be briefly introduced as follows.
  • the MME 424 may implement mobility management functions to track a current location of the UE 402 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.
  • the SGW 426 may terminate an SI interface toward the RAN and route data packets between the RAN and the LTE CN 422.
  • the SGW 426 may be a local mobility anchor point for inter- RAN node handovers and also may provide an anchor for inter-3 GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the SGSN 428 may track a location of the UE 402 and perform security functions and access control. In addition, the SGSN 428 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 424; MME selection for handovers; etc.
  • the S3 reference point between the MME 424 and the SGSN 428 may enable user and bearer information exchange for inter-3GPP access network mobility in idle/active states.
  • the HSS 430 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions. The HSS 430 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • An S6a reference point between the HSS 430 and the MME 424 may enable transfer of subscription and authentication data for authenticating/authorizing user access to the LTE CN 420.
  • the PGW 432 may terminate an SGi interface toward a data network (DN) 436 that may include an application/content server 438.
  • the PGW 432 may route data packets between the LTE CN 422 and the data network 436.
  • the PGW 432 may be coupled with the SGW 426 by an S 5 reference point to facilitate user plane tunneling and tunnel management.
  • the PGW 432 may further include a node for policy enforcement and charging data collection (for example, PCEF).
  • the SGi reference point between the PGW 432 and the data network 4 36 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services.
  • the PGW 432 may be coupled with a PCRF 434 via a Gx reference point.
  • the PCRF 434 is the policy and charging control element of the LTE CN 422.
  • the PCRF 434 may be communicatively coupled to the app/content server 438 to determine appropriate QoS and charging parameters for service flows.
  • the PCRF 432 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.
  • the CN 420 may be a 5GC 440.
  • the 5GC 440 may include an AUSF 442, AMF 444, SMF 446, UPF 448, NSSF 450, NEF 452, NRF 454, PCF 456, UDM 458, and AF 460 coupled with one another over interfaces (or “reference points”) as shown.
  • Functions of the elements of the 5GC 440 may be briefly introduced as follows.
  • the AUSF 442 may store data for authentication of UE 402 and handle authentication- related functionality.
  • the AUSF 442 may facilitate a common authentication framework for various access types.
  • the AUSF 442 may exhibit an Nausf service-based interface.
  • the AMF 444 may allow other functions of the 5GC 440 to communicate with the UE 402 and the RAN 404 and to subscribe to notifications about mobility events with respect to the UE 402.
  • the AMF 444 may be responsible for registration management (for example, for registering UE 402), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization.
  • the AMF 444 may provide transport for SM messages between the UE 402 and the SMF 446, and act as a transparent proxy for routing SM messages.
  • AMF 444 may also provide transport for SMS messages between UE 402 and an SMSF.
  • AMF 444 may interact with the AUSF 442 and the UE 402 to perform various security anchor and context management functions.
  • AMF 444 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 404 and the AMF 444; and the AMF 444 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection.
  • AMF 444 may also support NAS signaling with the UE 402 over an N3 IWF interface.
  • the SMF 446 may be responsible for SM (for example, session establishment, tunnel management between UPF 448 and AN 408); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 448 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to FI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 444 over N2 to AN 408; and determining SSC mode of a session.
  • SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 402 and the data network 436.
  • the UPF 448 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 436, and a branching point to support multi-homed PDU session.
  • the UPF 448 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UF/DF rate enforcement), perform uplink traffic verification (e.g., SDF-to-QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering.
  • UPF 448 may include an uplink classifier to support routing traffic flows to a data network.
  • the NSSF 450 may select a set of network slice instances serving the UE 402.
  • the NSSF 450 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed.
  • the NSSF 450 may also determine the AMF set to be used to serve the UE 402, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 454.
  • the selection of a set of network slice instances for the UE 402 may be triggered by the AMF 444 with which the UE 402 is registered by interacting with the NSSF 450, which may lead to a change of AMF.
  • the NSSF 450 may interact with the AMF 444 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 450 may exhibit an Nnssf service-based interface.
  • the NEF 452 may securely expose services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 460), edge computing or fog computing systems, etc.
  • the NEF 452 may authenticate, authorize, or throttle the AFs.
  • NEF 452 may also translate information exchanged with the AF 460 and information exchanged with internal network functions. For example, the NEF 452 may translate between an AF-Service-Identifier and an internal 5GC information.
  • NEF 452 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 452 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 452 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 452 may exhibit an Nnef service-based interface.
  • the NRF 454 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 454 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 454 may exhibit the Nnrf service-based interface.
  • the PCF 456 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior.
  • the PCF 456 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 458.
  • the PCF 456 exhibit an Npcf service-based interface.
  • the UDM 458 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 402. For example, subscription data may be communicated via an N8 reference point between the UDM 458 and the AMF 444.
  • the UDM 458 may include two parts, an application front end and a UDR.
  • the UDR may store subscription data and policy data for the UDM 458 and the PCF 456, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 402) for the NEF 452.
  • the Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 458, PCF 456, and NEF 452 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR.
  • the UDM may include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions.
  • the UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management.
  • the UDM 458 may exhibit the Nudm service-based interface.
  • the AF 460 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.
  • the 5GC 440 may enable edge computing by selecting operator/3 rd party services to be geographically close to a point that the UE 402 is attached to the network. This may reduce latency and load on the network.
  • the 5GC 440 may select a UPF 448 close to the UE 402 and execute traffic steering from the UPF 448 to data network 436 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 460. In this way, the AF 460 may influence UPF (re)selection and traffic routing.
  • the network operator may permit AF 460 to interact directly with relevant NFs. Additionally, the AF 460 may exhibit an Naf service-based interface.
  • the data network 436 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application/content server 438.
  • the wireless network 500 may include a UE 502 in wireless communication with an AN 504.
  • the UE 502 and AN 504 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.
  • the UE 502 may be communicatively coupled with the AN 504 via connection 506.
  • the connection 506 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mm Wave or sub-6GHz frequencies.
  • the UE 502 may include a host platform 508 coupled with a modem platform 510.
  • the host platform 508 may include application processing circuitry 512, which may be coupled with protocol processing circuitry 514 of the modem platform 510.
  • the application processing circuitry 512 may ran various applications for the UE 502 that source/sink application data.
  • the application processing circuitry 512 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations
  • the protocol processing circuitry 514 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 506.
  • the layer operations implemented by the protocol processing circuitry 514 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.
  • the modem platform 510 may further include digital baseband circuitry 516 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 514 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.
  • PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may
  • the modem platform 510 may further include transmit circuitry 518, receive circuitry 520, RF circuitry 522, and RF front end (RFFE) 524, which may include or connect to one or more antenna panels 526.
  • the transmit circuitry 518 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.
  • the receive circuitry 520 may include an analog-to-digital converter, mixer, IF components, etc.
  • the RF circuitry 522 may include a low-noise amplifier, a power amplifier, power tracking components, etc.
  • RFFE 524 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc.
  • transmit/receive components may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mm Wave or sub-6 gHz frequencies, etc.
  • the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.
  • the protocol processing circuitry 514 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.
  • a UE reception may be established by and via the antenna panels 526, RFFE 524, RF circuitry 522, receive circuitry 520, digital baseband circuitry 516, and protocol processing circuitry 514.
  • the antenna panels 526 may receive a transmission from the AN 504 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 526.
  • a UE transmission may be established by and via the protocol processing circuitry 514, digital baseband circuitry 516, transmit circuitry 518, RF circuitry 522, RFFE 524, and antenna panels 526.
  • the transmit components of the UE 504 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 526.
  • the AN 504 may include a host platform 528 coupled with a modem platform 530.
  • the host platform 528 may include application processing circuitry 532 coupled with protocol processing circuitry 534 of the modem platform 530.
  • the modem platform may further include digital baseband circuitry 536, transmit circuitry 538, receive circuitry 540, RF circuitry 542, RFFE circuitry 544, and antenna panels 546.
  • the components of the AN 504 may be similar to and substantially interchangeable with like-named components of the UE 502.
  • the components of the AN 508 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.
  • At least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below.
  • the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.
  • circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.
  • Example 1 may include an apparatus comprising a memory; processing circuitry coupled to the memory, the processing circuitry configured to: operate as a centralized self- organizing network (C-SON) function, the processing circuitry to: receive from a provisioning management service (MnS-P) radio resource management (RRM) measurements from a distributed unit (DU); receive from the MnS-P RRM measurements from a centralized unit user plane (CUUP); receive from the MnS-P RRM measurements from a centralized unit control plane (CUCP); train an artificial intelligence/machine learning model based on the RRM measurements, the RRM measurements providing performance measurements related to a plurality of network slice instances; and determine, based on the A I/M L model with the RRM measurements, the actions if needed, to optimize the RRM resources for network slice instance(s); in response to a determination that the RRM resources need to be optimized, update an RRM policy ratio corresponding to the plurality of network slice instances based on the RRM measurements.
  • MnS-P provisioning management service
  • Example 2 may include the apparatus of example 1 and/or some other example herein, wherein the RRM measurements received from DU include: mean and peak numbers of physical resource blocks (PRBs) that user equipment (UE) use on downlink and uplink traffic; average downlink and uplink UE throughput with respect to a base station; and distribution of downlink and uplink UE throughput in gNB.
  • PRBs physical resource blocks
  • UE user equipment
  • Example 3 may include the apparatus of example 1 and/or some other example herein, wherein the RRM measurements received from CUUP include: mean and peak numbers of measurements related to data radio bearers (DRBs).
  • DRBs data radio bearers
  • Example 4 may include the apparatus of example 1 and/or some other example herein, wherein the RRM measurements received from CUCP include: mean number of PDU Sessions requested to setup; mean number of PDU Sessions successfully setup.
  • Example 5 may include the apparatus of example 1 and/or some other example herein, wherein the processing circuitry configured to operate as the C-SON function, has further processing circuitry to: modify managed object instance (MOI) attributes, modify MOI Attributes ; and reconfigure RRM policy ratio RRMPolicy Ratio for the DU, CUUP, and CUCP.
  • MOI managed object instance
  • RRMPolicy Ratio reconfigure RRM policy ratio RRMPolicy Ratio for the DU, CUUP, and CUCP.
  • Example 6 may include the apparatus of example 1 and/or some other example herein, wherein the C-SON function invokes the provisioning MnS with a modify MOI Attributes operation when RRM resources for a network slice instance require updating.
  • Example 7 may include the apparatus of example 1 and/or some other example herein, wherein the C-SON function receives a notification notifyMOIAttributeValueChange to indicate the successful RRMPolicy Ratio update for a network slice instance.
  • Example 8 may include the apparatus of example 1 and/or some other example herein, wherein the C-SON function receives a notifyMOIAttributeValueChange to indicate a RRMPolicy Ratio update.
  • Example 9 may include the apparatus of example 8 and/or some other example herein, wherein the RRMPolicy Ratio may include updating a maximum RRM policy ratio, minimum RRM policy ratio, or a dedicated RRM policy ratio.
  • Example 10 may include a method comprising: receiving at a C-SON function from a provisioning management service (MnS-P) radio resource management (RRM) measurements from a distributed unit (DU); receiving from the MnS-P RRM measurements from a centralized unit user plane (CUUP); receiving from the MnS-P RRM measurements from a centralized unit control plane (CUCP); training an artificial intelligence/machine learning model based on the RRM measurements, the RRM measurements providing performance measurements related to a plurality of network slice instances; and determine, based on the A I/M L model with the RRM measurements, the actions if needed, to optimize the RRM resources for network slice instance(s); in response to a determination that the RRM resources need to be optimized, updating an RRM policy ratio corresponding to the plurality of network slice instances based on the RRM measurements.
  • MnS-P provisioning management service
  • RRM radio resource management
  • Example 11 may include the method of example 10 and/or some other example herein, wherein the RRM measurements received from DU include: mean and peak numbers of physical resource blocks (PRBs) that user equipment (UE) use on downlink and uplink traffic; average downlink and uplink UE throughput with respect to a base station; and distribution of downlink and uplink UE throughput in gNB.
  • PRBs physical resource blocks
  • UE user equipment
  • Example 12 may include the method of example 10 and/or some other example herein, wherein the RRM measurements received from CUUP include: mean and peak numbers of measurements related to data radio bearers (DRBs).
  • RRBs data radio bearers
  • Example 13 may include the method of example 10 and/or some other example herein, wherein the RRM measurements received from CUCP include: mean number of PDU Sessions requested to setup; mean number of PDU Sessions successfully setup.
  • Example 14 may include the method of example 10 and/or some other example herein, further comprising: modifying managed object instance (MOI) attributes, modify MOI Attributes ; and reconfiguring RRM policy ratio RRMPolicy Ratio for the DU.
  • MOI managed object instance
  • Example 15 may include the method of example 10 and/or some other example herein, further comprising: invoking the provisioning MnS with a modifyMOI Attributes operation when RRM resources for a network slice instance require updating.
  • Example 16 may include the method of example 10 and/or some other example herein, further comprising: receiving a notification notifyMOIAttributeValueChange to indicate an RRMPolicy Ratio update for a network slice instance.
  • Example 17 may include the method of example 10 and/or some other example herein, further comprising: receiving notifyMOIAttributeValueChange to indicate a RRMPolicy Ratio update.
  • Example 18 may include a computer-readable storage medium comprising instmctions to cause processing circuitry, upon execution of the instructions by the processing circuitry, to: receive from a provisioning management service (MnS-P) radio resource management (RRM) measurements from a distributed unit (DU); receive from the MnS-P RRM measurements from a centralized unit user plane (CUUP); receive from the MnS-P RRM measurements from a centralized unit control plane (CUCP); and processing circuitry coupled to the memory and the transceiver, the processing circuitry configured to operate as a centralized self-organizing network (C-SON) function, the processing circuitry to: train an artificial intelligence/machine learning model based on the RRM measurements, the RRM measurements providing performance measurements related to a plurality of network slice instances; and determine, based on the A I/M L model with the RRM measurements, the actions if needed, to optimize the RRM resources for network slice instance(s); and in response to a determination that the RRM resources need to be optimized, update an RRM
  • Example 19 may include the computer-readable storage medium of example 18 and/or some other example herein, wherein the RRM measurements received from DU include: mean and peak numbers of physical resource blocks (PRBs) that user equipment (UE) use on downlink and uplink traffic; average downlink and uplink UE throughput with respect to a base station; and distribution of downlink and uplink UE throughput in gNB.
  • PRBs physical resource blocks
  • UE user equipment
  • Example 20 may include the computer-readable storage medium of example 18 and/or some other example herein, wherein the RRM measurements received from CUUP include: mean and peak numbers of measurements related to data radio bearers (DRBs).
  • DRBs data radio bearers
  • Example 21 may include the computer-readable storage medium of example 18 and/or some other example herein, wherein the RRM measurements received from CUCP include: mean number of PDU Sessions requested to setup; mean number of PDU Sessions successfully setup.
  • Example 22 may include the computer-readable storage medium of example 18 and/or some other example herein, wherein the processing circuitry configured to operate as the C- SON function, has further processing circuitry to: modify managed object instance (MOI) attributes, modify MOI Attributes ; and reconfigure RRM policy ratio RRMPolicy Ratio for the DU, CUUP, and CUCP.
  • MOI managed object instance
  • RRMPolicy Ratio reconfigure RRM policy ratio
  • Example 23 may include the computer-readable storage medium of example 18 and/or some other example herein, wherein the C-SON function invokes the provisioning MnS with a modifyMOIAttributes operation when RRM resources for a network slice instance require updating.
  • Example 24 may include the computer-readable storage medium of example 18 and/or some other example herein, wherein the C-SON function receives a notification notifyMOIAttributeValueChange to indicate the successful RRMPolicyRatio update for a network slice instance, the RRMPolicyRatio updating a maximum RRM policy ratio, minimum RRM policy ratio, or a dedicated RRM policy ratio.
  • the C-SON function receives a notification notifyMOIAttributeValueChange to indicate the successful RRMPolicyRatio update for a network slice instance, the RRMPolicyRatio updating a maximum RRM policy ratio, minimum RRM policy ratio, or a dedicated RRM policy ratio.
  • Example 25 may include an apparatus comprising means for performing any of the methods of examples 1-24.
  • Example 26 may include a network node comprising a communication interface and processing circuitry connected thereto and configured to perform the methods of examples 1- 24.
  • Example 27 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-24, or any other method or process described herein.
  • Example 28 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-24, or any other method or process described herein.
  • Example 29 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-24, or any other method or process described herein.
  • Example 30 may include a method, technique, or process as described in or related to any of examples 1-24, or portions or parts thereof.
  • Example 31 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-24, or portions thereof.
  • Example 32 may include a signal as described in or related to any of examples 1-24, or portions or parts thereof.
  • Example 33 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-24, or portions or parts thereof, or otherwise described in the present disclosure.
  • PDU protocol data unit
  • Example 34 may include a signal encoded with data as described in or related to any of examples 1-24, or portions or parts thereof, or otherwise described in the present disclosure.
  • Example 35 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-24, or portions or parts thereof, or otherwise described in the present disclosure.
  • PDU protocol data unit
  • Example 36 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-24, or portions thereof.
  • Example 37 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-24, or portions thereof.
  • Example 38 may include a signal in a wireless network as shown and described herein.
  • Example 39 may include a method of communicating in a wireless network as shown and described herein.
  • Example 40 may include a system for providing wireless communication as shown and described herein.
  • Example 41 may include a device for providing wireless communication as shown and described herein.
  • references in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” “an example embodiment,” “example implementation,” etc., indicate that the embodiment or implementation described may include a particular feature, structure, or characteristic, but every embodiment or implementation may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment or implementation. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment or implementation, one skilled in the art will recognize such feature, structure, or characteristic in connection with other embodiments or implementations whether or not explicitly described. For example, various features, aspects, and actions described above with respect to an autonomous parking maneuver are applicable to various other autonomous maneuvers and must be interpreted accordingly.
  • Implementations of the systems, apparatuses, devices, and methods disclosed herein may comprise or utilize one or more devices that include hardware, such as, for example, one or more processors and system memory, as discussed herein.
  • An implementation of the devices, systems, and methods disclosed herein may communicate over a computer network.
  • a “network” is defined as one or more data links that enable the transport of electronic data between computer systems and/or modules and/or other electronic devices. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or any combination of hardwired or wireless) to a computer, the computer properly views the connection as a transmission medium.
  • Transmission media can include a network and/or data links, which can be used to carry desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer. Combinations of the above should also be included within the scope of non-transitory computer-readable media.
  • Computer-executable instructions comprise, for example, instructions and data which, when executed at a processor, cause the processor to perform a certain function or group of functions.
  • the computer-executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, or even source code.
  • a memory device can include any one memory element or a combination of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, etc.)) and non-volatile memory elements (e.g., ROM, hard drive, tape, CDROM, etc.).
  • volatile memory elements e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, etc.)
  • non-volatile memory elements e.g., ROM, hard drive, tape, CDROM, etc.
  • the memory device may incorporate electronic, magnetic, optical, and/or other types of storage media.
  • a “non-transitory computer-readable medium” can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device.
  • the computer-readable medium would include the following: a portable computer diskette (magnetic), a random-access memory (RAM) (electronic), a read-only memory (ROM) (electronic), an erasable programmable read-only memory (EPROM, EEPROM, or Flash memory) (electronic), and a portable compact disc read-only memory (CD ROM) (optical).
  • a portable computer diskette magnetic
  • RAM random-access memory
  • ROM read-only memory
  • EPROM erasable programmable read-only memory
  • EPROM erasable programmable read-only memory
  • CD ROM portable compact disc read-only memory
  • the computer-readable medium could even be paper or another suitable medium upon which the program is printed, since the program can be electronically captured, for instance, via optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
  • the present disclosure may be practiced in network computing environments with many types of computer system configurations, including in-dash vehicle computers, personal computers, desktop computers, laptop computers, message processors, nomadic devices, multi-processor systems, microprocessor- based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, mobile telephones, PDAs, tablets, pagers, routers, switches, various storage devices, and the like.
  • the disclosure may also be practiced in distributed system environments where local and remote computer systems, which are linked (either by hardwired data links, wireless data links, or by any combination of hardwired and wireless data links) through a network, both perform tasks.
  • program modules may be located in both the local and remote memory storage devices.
  • ASICs application specific integrated circuits
  • At least some embodiments of the present disclosure have been directed to computer program products comprising such logic (e.g., in the form of software) stored on any computer- usable medium.
  • Such software when executed in one or more data processing devices, causes a device to operate as described herein.
  • any or all of the aforementioned alternate implementations may be used in any combination desired to form additional hybrid implementations of the present disclosure.
  • any of the functionality described with respect to a particular device or component may be performed by another device or component.
  • embodiments of the disclosure may relate to numerous other device characteristics.
  • embodiments have been described in language specific to structural features and/or methodological acts, it is to be understood that the disclosure is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as illustrative forms of implementing the embodiments.
  • circuitry refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality.
  • FPD field-programmable device
  • FPGA field-programmable gate array
  • PLD programmable logic device
  • CPLD complex PLD
  • HPLD high-capacity PLD
  • DSPs digital signal processors
  • the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality.
  • the term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.
  • processor circuitry refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data.
  • Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information.
  • processor circuitry may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes.
  • Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like.
  • the one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators.
  • CV computer vision
  • DL deep learning
  • application circuitry and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.”
  • interface circuitry refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices.
  • interface circuitry may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like.
  • user equipment refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network.
  • the term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc.
  • the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.
  • network element refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services.
  • network element may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and/or the like.
  • computer system refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources.
  • appliance refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource.
  • program code e.g., software or firmware
  • a “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource.
  • resource refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, and/or the like.
  • a “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s).
  • a “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc.
  • network resource or “communication resource” may refer to resources that are accessible by computer devices/systems via a communications network.
  • system resources may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.
  • channel refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream.
  • channel may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated.
  • link refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.
  • instantiate refers to the creation of an instance.
  • An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.
  • Coupled may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other.
  • directly coupled may mean that two or more elements are in direct contact with one another.
  • communicatively coupled may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or link, and/or the like.
  • information element refers to a structural element containing one or more fields.
  • field refers to individual contents of an information element, or a data element that contains content.
  • SMTC refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.
  • SSB refers to an SS/PBCH block.
  • a “Primary Cell” refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure.
  • Primary SCG Cell refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation.
  • Secondary Cell refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA.
  • Secondary Cell Group refers to the subset of serving cells comprising the PSCell and zero or more secondary cells for a UE configured with DC.
  • Server Cell refers to the primary cell for a UE in RRC_CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell.
  • serving cell refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC_CONNECTED configured with CA/.
  • Special Cell refers to the PCell of the MCG or the PSCell of the SCG for

Landscapes

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

Abstract

La divulgation est relative à des systèmes et à des procédés de configuration de ressources pour un réseau sans fil pour un réseau d'auto-organisation centralisé (C-SON), les circuits de traitement étant destinés à recevoir des mesures de gestion de ressources radio (RRM) d'un service de gestion d'approvisionnement (MnS-P) à partir d'une unité distribuée (DU), pour recevoir à partir du MnS-P, des mesures RRM, à partir d'un plan utilisateur unitaire centralisé (CUUP), pour recevoir, à partir du MnS-P, des mesures RRM à partir d'un plan de commande unitaire centralisé (CUCP), pour former un modèle d'apprentissage d'intelligence artificielle/machine sur la base des mesures RRM, les mesures RRM fournissant des mesures de performance associées à une pluralité d'instances de tranche de réseau, et pour mettre à jour un rapport de politique RRM correspondant à la pluralité d'instances de tranche de réseau sur la base des mesures RRM.
PCT/US2022/024066 2021-04-09 2022-04-08 Procédés et appareil pour prendre en charge une optimisation de gestion de ressources radio (rrm) pour des instances de tranches de réseau dans des systèmes 5g WO2022217083A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202280020295.1A CN117099390A (zh) 2021-04-09 2022-04-08 针对5g系统中的网络切片实例支持无线电资源管理（rrm）优化的方法和装置

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202163173264P 2021-04-09 2021-04-09
US63/173,264 2021-04-09

Publications (1)

Publication Number Publication Date
WO2022217083A1 true WO2022217083A1 (fr) 2022-10-13

Family

ID=83545777

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/US2022/024078 WO2022217093A1 (fr) 2021-04-09 2022-04-08 Procédés et appareil pour prendre en charge l'enregistrement d'applications de serveur d'application périphérique (eas) et d'applications d'informatique périphérique à accès multiple (mec) à des serveurs catalyseurs périphériques (ees) et à des platesformes mec
PCT/US2022/024066 WO2022217083A1 (fr) 2021-04-09 2022-04-08 Procédés et appareil pour prendre en charge une optimisation de gestion de ressources radio (rrm) pour des instances de tranches de réseau dans des systèmes 5g

Family Applications Before (1)

Application Number Title Priority Date Filing Date
PCT/US2022/024078 WO2022217093A1 (fr) 2021-04-09 2022-04-08 Procédés et appareil pour prendre en charge l'enregistrement d'applications de serveur d'application périphérique (eas) et d'applications d'informatique périphérique à accès multiple (mec) à des serveurs catalyseurs périphériques (ees) et à des platesformes mec

Country Status (2)

Country Link
EP (1) EP4320834A1 (fr)
WO (2) WO2022217093A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020080913A1 (fr) * 2018-10-19 2020-04-23 엘지전자 주식회사 Procédé prenant en charge une transmission de données séparée pour des tranches de réseau indépendantes dans un système de communication sans fil
WO2021049783A1 (fr) * 2019-09-09 2021-03-18 주식회사맥데이타 Procédé, dispositif et système de diagnostic de performance de réseau de communication mobile 5g

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3967067A4 (fr) * 2019-05-09 2022-06-22 Samsung Electronics Co., Ltd. Appareil et procédé pour fournir des services informatiques mobile edge dans un système de communication sans fil
CN114557117A (zh) * 2019-09-25 2022-05-27 Idac控股公司 5g设备与mec主机之间的mec应用程序实例的透明重定位

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020080913A1 (fr) * 2018-10-19 2020-04-23 엘지전자 주식회사 Procédé prenant en charge une transmission de données séparée pour des tranches de réseau indépendantes dans un système de communication sans fil
WO2021049783A1 (fr) * 2019-09-09 2021-03-18 주식회사맥데이타 Procédé, dispositif et système de diagnostic de performance de réseau de communication mobile 5g

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
DEUTSCHE TELEKOM: "Use cases for AI/ML in RAN and potential benefits", 3GPP DRAFT; R3-206198, vol. RAN WG3, 22 October 2020 (2020-10-22), pages 1 - 4, XP051941655 *
ERICSSON: "AI/ML based Use Cases", 3GPP DRAFT; R3-206437, vol. RAN WG3, 22 October 2020 (2020-10-22), pages 1 - 15, XP051941757 *
HUAWEI : "SOD on Use Cases for SI on Data Collection", 3GPP TSG RAN WG3 #110-E, no. R3-206874, 17 November 2020 (2020-11-17), pages 1 - 17, XP009540198 *

Also Published As

Publication number Publication date
WO2022217093A1 (fr) 2022-10-13
EP4320834A1 (fr) 2024-02-14

Similar Documents

Publication Publication Date Title
US11871436B2 (en) Apparatus for UE measurement delay and granularity for new radio positioning measurement
US11968559B2 (en) Apparatus and method for 5G quality of service indicator management
US20230141237A1 (en) Techniques for management data analytics (mda) process and service
US11871460B2 (en) Domain name system (DNS)-based discovery of regulatory requirements for non-3GPP inter-working function (N3IWF) selection
US11792814B2 (en) Techniques for cancelation of one or more uplink transmissions from a user equipment
WO2022159400A1 (fr) Surveillance de qualité de service dans un réseau ponté sensible au temps cellulaire intégré
WO2022155108A1 (fr) Saut de fréquence inter-intervalles amélioré permettant une couverture de liaison montante dans des systèmes 5g
WO2022011527A1 (fr) Configuration et transmission de srs en multi-dci multi-trp et agrégation de porteuses
US11979894B2 (en) Soft resource availability indication for integrated access and backhaul (IAB) operation in paired spectrum
WO2022154961A1 (fr) Support pour serveur activateur de périphérie et gestion de cycle de vie de serveur de configuration de périphérie
EP4278530A1 (fr) Atténuation de chevauchements de domaine temporel impliquant un bloc de transport sur des transmissions à fentes multiples
EP4239479A1 (fr) Orchestration de services informatiques et de ressources pour des systèmes de prochaine génération
WO2022217083A1 (fr) Procédés et appareil pour prendre en charge une optimisation de gestion de ressources radio (rrm) pour des instances de tranches de réseau dans des systèmes 5g
US20240214147A1 (en) Group-based channel state information reference signal (csi-rs) transmission
US20240214868A1 (en) Apparatus and method for 5g quality of service indicator management
US11751228B2 (en) Methods and apparatuses for uplink spatial relation info switch
EP4207666A1 (fr) Configuration d'occasions de surveillance de pdcch pour capacité de surveillance de pdcch à intervalles multiples
EP4385184A1 (fr) Procédés et appareil de gestion de cycle de vie améliorée dans des serveurs informatiques périphériques 5g
WO2023033813A1 (fr) Transmission de csi-rs (signal de référence d'informations d'état de canal) basée sur un groupe
WO2023212049A1 (fr) Mécanismes de commutation d'émission à porteuses multiples pour des systèmes de nouvelle radio dans un ran1 5g
WO2022155505A1 (fr) Techniques de déclenchement d'un signal de référence de sondage (srs) apériodique et flexible
EP4278628A1 (fr) Mesures de performance pour fonction d'exposition de réseau sur la fourniture de paramètres de service, la négociation de politique et l'établissement de connexion
WO2022216859A1 (fr) Configuration d'avance temporelle pour mobilité inter-cellules
CN117099390A (zh) 针对5g系统中的网络切片实例支持无线电资源管理（rrm）优化的方法和装置
WO2022235690A1 (fr) Chaînage de fonctions de service amélioré dans des réseaux cellulaires de prochaine génération

Legal Events

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

Ref document number: 22785550

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202280020295.1

Country of ref document: CN

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22785550

Country of ref document: EP

Kind code of ref document: A1