Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W24/00—Supervisory, monitoring or testing arrangements
  • H04W24/08—Testing, supervising or monitoring using real traffic
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W24/00—Supervisory, monitoring or testing arrangements
  • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports

Definitions

• Embodiments pertain to wireless communications in 5 th generation (5G), or new radio (NR), systems. Some embodiments relate to radio access network (RAN)-user equipment (UE) throughput in 5G networks. Some embodiments relate to performance measurements and KPIs for RAN-UE throughput in 5G networks.
• 5G 5 th generation
• NR new radio
• FIG. 1A illustrates an architecture of a network, in accordance with some aspects.
• FIG. 1B illustrates a non-roaming 5G system architecture in accordance with some aspects.
• FIG. 1C illustrates a non-roaming 5G system architecture in accordance with some aspects.
• FIG. 2 illustrates a block diagram of a communication device in accordance with some embodiments.
• FIG. 3 illustrates network slice relations with network functions in accordance with some embodiments.
• FIG. 4 illustrates network slice performance measurement generation in accordance with some embodiments.
• FIG. 5A illustrates network slice performance measurement generation in accordance with some embodiments.
• FIG. 5B illustrates network slice performance measurement generation in accordance with some embodiments.
• FIG. 6 illustrates network slice performance measurement generation in accordance with some embodiments.
• FIG. 7 illustrates a method of providing RAN-UE throughput key performance indicators in accordance with some embodiments.
• FIG. 1 A illustrates an architecture of a network in accordance with some aspects.
• the network 140A includes 3GPP LTE/4G and NG network functions.
• a network function can be implemented as a discrete network element on a dedicated hardware, as a software instance running on dedicated hardware, and/or as a virtualized function instantiated on an appropriate platform, e.g., dedicated hardware or a cloud infrastructure.
• the network 140A is shown to include user equipment (UE) 101 and UE 102.
• the UEs 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also include any mobile or non-mobile computing device, such as portable (laptop) or desktop computers, wireless handsets, drones, or any other computing device including a wired and/or wireless communications interface.
• the UEs 101 and 102 can be collectively referred to herein as UE 101 , and UE 101 can be used to perform one or more of the techniques disclosed herein.
• Any of the radio links described herein may operate according to any exemplary radio communication technology and/or standard.
• Any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and other frequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and other frequencies).
• LSA Licensed Shared Access
• SAS Spectrum Access System
• OFDM Orthogonal Frequency Domain Multiplexing
• SC-FDMA SC-FDMA
• SC-OFDM filter bank-based multicarrier
• OFDMA OFDMA
• 3GPP NR 3GPP NR
• any of the UEs 101 and 102 can comprise an Internet-of-Things (loT) UE or a Cellular loT (CloT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing shortlived UE connections.
• any of the UEs 101 and 102 can include a narrowband (NB) IoT UE (e.g., such as an enhanced NB-IoT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE).
• NB narrowband
• eNB-IoT enhanced NB-IoT
• FeNB-IoT Further Enhanced
• An IoT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity -Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or IoT networks.
• M2M or MTC exchange of data may be a machine-initiated exchange of data.
• An IoT network includes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections.
• the IoT UEs may execute background applications (e.g., keepalive messages, status updates, etc.) to facilitate the connections of the IoT network.
• any of the UEs 101 and 102 can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.
• the UEs 101 and 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 110.
• the RAN 110 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a Next Gen RAN (NG RAN), or some other type of RAN.
• UMTS Evolved Universal Mobile Telecommunications System
• E-UTRAN Evolved Universal Mobile Telecommunications System
• NG RAN Next Gen RAN
• the UEs 101 and 102 utilize connections 103 and 104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 103 and 104 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth- generation (5G) protocol, a New Radio (NR) protocol, and the like.
• GSM Global System for Mobile Communications
• CDMA code-division multiple access
• PTT Push-to-Talk
• POC PTT over Cellular
• UMTS Universal Mobile Telecommunications System
• LTE Long Term Evolution
• 5G fifth- generation
• NR New Radio
• the UEs 101 and 102 may further directly exchange communication data via a ProSe interface 105.
• the ProSe interface 105 may alternatively be referred to as a sidelink (SL) interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control
• PSCCH Physical Sidelink Shared Channel
• PSSCH Physical Sidelink Shared Channel
• PSDCH Physical Sidelink Discovery Channel
• PSBCH Physical Sidelink Broadcast Channel
• PSFCH Physical Sidelink Feedback Channel
• the UE 102 is shown to be configured to access an access point (AP) 106 via connection 107.
• the connection 107 can comprise a local wireless connection, such as, for example, a connection consistent with any IEEE 802.11 protocol, according to which the AP 106 can comprise a wireless fidelity (WiFi®) router.
• WiFi® wireless fidelity
• the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).
• the RAN 110 can include one or more access nodes that enable the connections 103 and 104.
• These access nodes can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN nodes, and the like, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
• the communication nodes 111 and 112 can be transmission/reception points (TRPs). In instances when the communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs can function within the communication cell of the NodeBs.
• TRPs transmission/reception points
• RAN 110 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 111, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 112.
• macro RAN node 111 e.g., macro RAN node 111
• femtocells or picocells e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells
• LP low power
• any of the RAN nodes 111 and 112 can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 102.
• any of the RAN nodes 111 and 112 can fulfill various logical functions for the RAN 110 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
• RNC radio network controller
• any of the nodes 111 and/or 112 can be a gNB, an eNB, or another type of RAN node.
• the RAN 110 is shown to be communicatively coupled to a core network (CN) 120 via an SI interface 113.
• the CN 120 may be an evolved packet core (EPC) network, aNextGen Packet Core (NPC) network, or some other type of CN (e.g., as illustrated in reference to FIGS. 1B-1C).
• EPC evolved packet core
• NPC NextGen Packet Core
• the SI interface 113 is split into two parts: the Sl-U interface 114, which carries traffic data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122, and the Sl-mobility management entity (MME) interface 115, which is a signaling interface between the RAN nodes 111 and 112 and MMEs
• the CN 120 comprises the MMEs 121, the S-GW 122, the Packet Data Network (PDN) Gateway (P-GW) 123, and a home subscriber server (HSS) 124.
• the MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
• the MMEs 121 may manage mobility aspects in access such as gateway selection and tracking area list management.
• the HSS 124 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions.
• the CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc.
• the HSS 124 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
• the S-GW 122 may terminate the SI interface 113 towards the
• the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW 122 may include a lawful intercept, charging, and some policy enforcement.
• the P-GW 123 may terminate an SGi interface toward a PDN.
• the P-GW 123 may route data packets between the EPC network 120 and external networks such as a network including the application server 184
• the P-GW 123 can also communicate data to other external networks 131 A, which can include the Internet, IP multimedia subsystem (IPS) network, and other networks.
• the application server 184 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.).
• PS Packet Services
• the P-GW 123 is shown to be communicatively coupled to an application server 184 via an IP interface 125.
• the application server 184 can also be configured to support one or more communication services (e.g., Voice-over- Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 101 and 102 via the CN 120.
• VoIP Voice-over- Internet Protocol
• PTT sessions PTT sessions
• group communication sessions social networking services, etc.
• the P-GW 123 may further be a node for policy enforcement and charging data collection.
• Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120.
• PCRF Policy and Charging Rules Function
• HPLMN Home Public Land Mobile Network
• IP-CAN Internet Protocol Connectivity Access Network
• H-PCRF Home PCRF
• V-PCRF Visited PCRF
• the PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123.
• the communication network 140A can be an IoT network or a 5G network, including 5G new radio network using communications in the licensed (5G NR) and the unlicensed (5G NR-U) spectrum.
• One of the current enablers of IoT is the narrowband-loT (NB-IoT). Operation in the unlicensed spectrum may include dual connectivity (DC) operation and the standalone LTE system in the unlicensed spectrum, according to which LTE-based technology solely operates in unlicensed spectrum without the use of an “anchor” in the licensed spectrum, called MulteFire.
• DC dual connectivity
• An NG system architecture can include the RAN 110 and a 5G network core (5GC) 120.
• the NG-RAN 110 can include a plurality of nodes, such as gNBs and NG-eNBs.
• the core network 120 e.g., a 5G core network or 5GC
• the AMF and the UPF can be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces.
• the gNBs and the NG-eNBs can be connected to the AMF by NG-C interfaces, and to the UPF by NG-U interfaces.
• the gNBs and the NG-eNBs can be coupled to each other via Xn interfaces.
• the NG system architecture can use reference points between various nodes as provided by 3GPP Technical Specification (TS) 23.501 (e.g., V15.4.0, 2018-12).
• TS 3GPP Technical Specification
• each of the gNBs and the NG- eNBs can be implemented as a base station, a mobile edge server, a small cell, a home eNB, and so forth.
• a gNB can be a master node (MN) and NG-eNB can be a secondary node (SN) in a 5G architecture.
• FIG. 1B illustrates a non-roaming 5G system architecture in accordance with some aspects. In particular, FIG.
• the 5G system architecture 140B includes a plurality of network functions (NFs), such as an AMF 132, session management function (SMF) 136, policy control function (PCF) 148, application function (AF) 150, UPF 134, network slice selection function (NSSF) 142, authentication server function (AUSF) 144, and unified data management (UDM)/home subscriber server (HSS) 146.
• NFs network functions
• AMF session management function
• PCF policy control function
• AF application function
• UPF network slice selection function
• AUSF authentication server function
• UDM unified data management
• HSS home subscriber server
• the UPF 134 can provide a connection to a data network (DN)
• the AMF 132 can be used to manage access control and mobility and can also include network slice selection functionality.
• the AMF 132 may provide UE-based authentication, authorization, mobility management, etc., and may be independent of the access technologies.
• the SMF 136 can be configured to set up and manage various sessions according to network policy. The SMF 136 may thus be responsible for session management and allocation of IP addresses to UEs.
• the SMF 136 may also select and control the UPF 134 for data transfer.
• the SMF 136 may be associated with a single session of a UE 101 or multiple sessions of the UE 101. This is to say that the UE 101 may have multiple 5G sessions. Different SMFs may be allocated to each session. The use of different SMFs may permit each session to be individually managed. As a consequence, the functionalities of each session may be independent of each other.
• the UPF 134 can be deployed in one or more configurations according to the desired service type and may be connected with a data network.
• the PCF 148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to PCRF in a 4G communication system).
• the UDM can be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).
• the AF 150 may provide information on the packet flow to the
• the PCF 148 responsible for policy control to support a desired QoS.
• the PCF 148 may set mobility and session management policies for the UE 101. To this end, the PCF 148 may use the packet flow information to determine the appropriate policies for proper operation of the AMF 132 and SMF 136.
• the AUSF 144 may store data for UE authentication.
• the 5G system architecture 140B includes an IP multimedia subsystem (IMS) 168B as well as a plurality of IP multimedia core network subsystem entities, such as call session control functions (CSCFs).
• IMS IP multimedia subsystem
• CSCFs call session control functions
• the IMS 168B includes a CSCF, which can act as a proxy CSCF (P-CSCF) 162BE, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) (not illustrated in FIG. 1B), or interrogating CSCF (I-CSCF) 166B.
• the P-CSCF 162B can be configured to be the first contact point for the UE 102 within the IM subsystem (IMS) 168B.
• the S-CSCF 164B can be configured to handle the session states in the network, and the E-CSCF can be configured to handle certain aspects of emergency sessions such as routing an emergency request to the correct emergency center or PSAP.
• the I-CSCF 166B can be configured to function as the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's service area.
• the I-CSCF 166B can be connected to another IP multimedia network 170E, e.g. an IMS operated by a different network operator.
• the UDM/HSS 146 can be coupled to an application server 160E, which can include a telephony application server (TAS) or another application server (AS).
• TAS telephony application server
• AS application server
• the AS 160B can be coupled to the IMS 168B via the S-CSCF 164B or the I-CSCF 166B.
• FIG. 1B illustrates the following reference points: N1 (between the UE 102 and the AMF 132), N2 (between the RAN 110 and the AMF 132), N3 (between the RAN 110 and the UPF 134), N4 (between the SMF 136 and the UPF 134), N5 (between the PCF 148 and the AF 150, not shown), N6 (between the UPF 134 and the DN 152), N7 (between the SMF 136 and the PCF 148, not shown), N8 (between the UDM 146 and the AMF 132, not shown), N9 (between two UPFs 134, not shown), N10 (between the UDM 146 and the SMF 136, not shown), N11 (between the AMF 132 and the SMF 136, not shown), N12 (between the AUSF 144 and the AMF 132, not shown), N13 (between the AUSF 144 and the UDM 132 and the UDM
• FIG. 1C illustrates a 5G system architecture 140C and a service- based representation.
• system architecture 140C can also include a network exposure function (NEF) 154 and a network repository function (NRF) 156.
• NEF network exposure function
• NRF network repository function
• 5G system architectures can be service-based and interaction between network functions can be represented by corresponding point-to-point reference points Ni or as service-based interfaces.
• service-based representations can be used to represent network functions within the control plane that enable other authorized network functions to access their services.
• 5G system architecture 140C can include the following service- based interfaces: Namf 158H (a service-based interface exhibited by the AMF 132), Nsmf 1581 (a service-based interface exhibited by the SMF 136), Nnef 158B (a service-based interface exhibited by the NEF 154), Npcf 158D (a service-based interface exhibited by the PCF 148), aNudm 158E (a service- based interface exhibited by the UDM 146), Naf 158F (a service-based interface exhibited by the AF 150), Nnrf 158C (a service-based interface exhibited by the NRF 156), Nnssf 158A (a service-based interface exhibited by the NSSF 142), Nausf 158G (a service-based interface exhibited by the
• NR-V2X architectures may support high-reliability low latency sidelink communications with a variety of traffic patterns, including periodic and aperiodic communications with random packet arrival time and size.
• FIG. 2 illustrates a block diagram of a communication device in accordance with some embodiments.
• the communication device 200 may be a UE such as a specialized computer, a personal or laptop computer (PC), a tablet PC, or a smart phone, dedicated network equipment such as an eNB, a server running software to configure the server to operate as a network device, a virtual device, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine.
• the communication device 200 may be implemented as one or more of the devices shown in FIG. 1. Note that communications described herein may be encoded before transmission by the transmitting entity (e.g., UE, gNB) for reception by the receiving entity (e.g., gNB, UE) and decoded after reception by the receiving entity.
• the transmitting entity e.g., UE, gNB
• the receiving entity e.g., gNB, UE
• Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms.
• Modules and components are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner.
• circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module.
• the whole or part of one or more computer systems e.g., a standalone, client or server computer system
• one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations.
• the software may reside on a machine readable medium.
• the software when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.
• module (and “component”) is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein.
• each of the modules need not be instantiated at any one moment in time.
• the modules comprise a general-purpose hardware processor configured using software
• the general-puipose hardware processor may be configured as respective different modules at different times.
• Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.
• the communication device 200 may include a hardware processor (or equivalently processing circuitry) 202 (e.g., a central processing unit (CPU), a GPU, a hardware processor core, or any combination thereof), a main memory 204 and a static memory 206, some or all of which may communicate with each other via an interlink (e.g., bus) 208.
• the main memory 204 may contain any or all of removable storage and non-removable storage, volatile memory or non-volatile memory.
• the communication device 200 may further include a display unit 210 such as a video display, an alphanumeric input device 212 (e.g., a keyboard), and a user interface (UI) navigation device 214 (e.g., a mouse).
• UI user interface
• the display unit 210, input device 212 and UI navigation device 214 may be a touch screen display.
• the communication device 200 may additionally include a storage device (e.g., drive unit) 216, a signal generation device 218 (e.g., a speaker), a network interface device 220, and one or more sensors, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor.
• GPS global positioning system
• the communication device 200 may further include an output controller, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
• a serial e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
• USB universal serial bus
• IR infrared
• NFC near field communication
• the storage device 216 may include a non-transitory machine readable medium 222 (hereinafter simply referred to as machine readable medium) on which is stored one or more sets of data structures or instructions 224 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein.
• the instructions 224 may also reside, completely or at least partially, within the main memory 204, within static memory 206, and/or within the hardware processor 202 during execution thereof by the communication device 200.
• the machine readable medium 222 is illustrated as a single medium, the term "machine readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 224.
• machine readable medium may include any medium that is capable of storing, encoding, or carrying instructions for execution by the communication device 200 and that cause the communication device 200 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions.
• Non-limiting machine readable medium examples may include solid-state memories, and optical and magnetic media.
• machine readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Radio access Memory
• non-volatile memory such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices
• EPROM Electrically Programmable Read-Only Memory
• EEPROM Electrically Erasable Programmable Read-Only Memory
• flash memory devices e.g., electrically Erasable Programmable Read-Only Memory (EEPROM)
• EPROM Electrically Programmable Read-Only Memory
• EEPROM Electrically Erasable Programmable Read-Only Memory
• the instructions 224 may further be transmitted or received over a communications network using a transmission medium 226 via the network interface device 220 utilizing any one of a number of wireless local area network (WLAN) transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.).
• WLAN wireless local area network
• Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks. Communications over the networks may include one or more different protocols, such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi, I ⁇ 802.16 family of standards known as WiMax, IEEE
• the network interface device 220 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the transmission medium 226.
• LTE Long Term Evolution
• UMTS Universal Mobile Telecommunications System
• P2P peer-to-peer
• NG next generation
• 5G 5th generation
• the network interface device 220 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the transmission medium 226.
• 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 cany 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 or “processor” as used herein thus 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.
• processor circuitry or “processor” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single- or multi-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.
• KPI has been defined in 3GPP TS 28.554, v. 16.5.0. However, the manner in which the DL/UL RAN UE throughput KPI is calculated for subnetwork level is unclear, and the KPI for network slice subnet level does not exist.
• the NR cell is modelled as NRCellDU information object class (IOC) andNRCellCU IOC (see TS 28.541, v. 16.5.0), and both IOCs derivatives of ManagedFunction IOC.
• IOC NRCellDU information object class
• NRCellCU IOC see TS 28.541, v. 16.5.0
• NRCellDU MOIs The KPI mentioned above for current systems is not defined clearly regarding how to aggregate from the NRCellDU level.
• FIG. 3 illustrates network slice relations with network functions in accordance with some embodiments.
• the network slice selection service enables the network to select the network slice to serve the UE, and enables the NSSF to provide the AMF with the Allowed NSSAI and the Configured NSSAI for the Serving PLMN.
• the network slice selection service may be consumed during the registration procedure, during the inter-PLMN mobility procedure, during PDU session establishment and UE configuration update, etc.
• the network slice selection is the primary step enabling the 5G networks to support network slicing, therefore the performance of network slice selection should be monitored.
• the S-NSSAI(s) supported by the AMF on a per TS basis may be changed. This change is to be updated to the NSSF.
• the AMF may subscribe to the notification of any changes to the NSSA1 availability information updated by another AMF on a per tracking area (TA) basis.
• the up-to-date and effective S- NSSAI availability information may be used to support network slicing, therefore the performance of S-NSSAI availability service is to be monitored.
• some embodiments are directed to generating KPIs on the DL/UL RAN UE throughput KPI for the NR cell level, subnetwork level and for network slice subnet level, and measurements related to network slice selection.
• the KPIs on delay on the DL/UL RAN UE throughput KPI and measurements related to network slice selection can reflect the performance of the 5GS.
• FIG. 4 illustrates user plane packet delay in accordance with some embodiments.
• a service producer collects the raw performance measurements from NFs, and then generates the performance measurements for
• FIG. 5A illustrates network slice performance measurement generation in accordance with some embodiments.
• FIG. 5B illustrates network slice performance measurement generation in accordance with some embodiments.
• FIG. 6 illustrates network slice performance measurement generation in accordance with some embodiments. [0059] 2. KPIs [0060] 6.3.6.x DL RAN UE throughput
• This KPI describes the average DL RAN UE throughput for a NRCellDU.
• the KPI type is MEAN in kbit per second.
• This KPI can optionally be split into KPIs per QoS level (mapped 5QI or QCI in NR option 3) and per S-NSSAI.
• DlUeThroughput _Cell DRB.UEThpDl
• QOS identifies the target quality of service class
• DlUeThroughput _Cell.SNSSAI DRB.UEThpDl.SNSSAI
• This KPI describes the average DL RAN UE throughput for a sub-network.
• the KPI type is MEAN in kbit per second.
• This KPI can optionally be split into KPIs per QoS level (mapped 5QI or QCI in NR option 3) and per S-NSSAI.
• the #NRCellDU is the number of NRCellDU’ s in the
• This KPI describes the average DL RAN UE throughput for a network slice subnet.
• the KPI type is MEAN in kbit per second.
• the #NRCellDU is the number of NRCellDU’s associated with the NetworkSliceSubnet.
• QOS DRB.UEThpUl.QOS, [0096] where QOS identifies the target quality of service class;
• This KPI describes the average UL RAN UE throughput for a sub-network.
• the KPI type is MEAN in kbit per second.
• This KPI can optionally be split into KPIs per QoS level (mapped 5QI or QCI in NR option 3) and per S-NSSAI.
• W is the measurement for the weighted average, it is one of the following:
• the #NRCellDU is the number of NRCellDU’ s in the
• W is the measurement for the weighted average, it is one of the following:
• the #NRCellDU is the number of NRCellDU’s associated with the NetworkSliceSubnet.
• the SNSSAI identifies the S-NSSA1 that the NetworkSliceSubnet supports.
• Each measurement is an integer value.
• Nnssf_NSSAIAvailability_Update request message from AMF (see 3GPP TS 23.502).
• NSSAI availability updates made by the NSSF are updated.
• Nnssf_NSSAIAvailability_Update response message indicating a successful S- NSSAI availability update to AMF (see 3 GPP TS 29.531).
• Nnssf_NSSAIAvailabilily_Subscribe request message from AMF (see 3GPP TS 23.502).
• Nnssf_NSSAIAvailability_Subscribe response message indicating a successful S-NSSAI availability notification subscription to AMF (see 3GPP TS 29.531).
• d) A single integer value.
• Nnssf_NSSAIAvailability_Subscribe response message indicating a S-NSSAI availability notification subscription to AMF (see 3GPP TS 29.531), each message increments the relevant subcounter per failure cause by 1. [00204] d) A single integer value.
• Nnssf_NSSAIAvailability_Notify message to AMF (see 3GPP TS 23.502).
• FIG. 7 illustrates a method of providing RAN-UE throughput key performance indicators in accordance with some embodiments.
• the method 700 shown in FIG. 7 may be performed by a management system apparatus.
• the method 700 may include, for example, receiving raw performance measurements from one or more NFs at operation 702.
• the method 700 may generate a performance measurement based on the raw performance measurements.
• the generated performance measurement includes a KPI, such as that described above.
• the UE throughput in the NG-RAN is a performance parameter for operating 5G network that, if not met, cause actions to be performed to the network, e.g. reconfiguration or capacity increase. That is, one or more NFs of the 5G network may be adjusted in response to at least one of the KPIs not meeting a trigger threshold.
• network slicing is supported by the NG- RAN, multiple network slices may be supported. The UL and DL UE throughput for each network slice may then allow pinpointing of a specific performance problem and take the appropriate actions above.

Landscapes

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

Priority Applications (1)

Applications Claiming Priority (2)

Publications (1)

Family

ID=80118386

Family Applications (1)

Country Status (2)

Citations (2)

• 2021
  • 2021-06-03 WO PCT/US2021/035758 patent/WO2022031356A1/en active Application Filing
  • 2021-06-03 CN CN202180047394.4A patent/CN115868195A/zh active Pending

Patent Citations (2)

Non-Patent Citations (4)

Also Published As

Similar Documents

Legal Events