WO2018128894A1 - Systems, methods and devices for alarm notification in a network function virtualization infrastructure - Google Patents

Systems, methods and devices for alarm notification in a network function virtualization infrastructure Download PDF

Info

Publication number
WO2018128894A1
WO2018128894A1 PCT/US2017/068580 US2017068580W WO2018128894A1 WO 2018128894 A1 WO2018128894 A1 WO 2018128894A1 US 2017068580 W US2017068580 W US 2017068580W WO 2018128894 A1 WO2018128894 A1 WO 2018128894A1
Authority
WO
WIPO (PCT)
Prior art keywords
alarm
performance
notification
generate
alarm notification
Prior art date
Application number
PCT/US2017/068580
Other languages
English (en)
French (fr)
Inventor
Joey Chou
Yizhi Yao
Original Assignee
Intel IP 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 IP Corporation filed Critical Intel IP Corporation
Priority to DE112017005643.8T priority Critical patent/DE112017005643T5/de
Publication of WO2018128894A1 publication Critical patent/WO2018128894A1/en

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/06—Management of faults, events, alarms or notifications
    • H04L41/0681—Configuration of triggering conditions
    • 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/12—Discovery or management of network topologies
    • H04L41/122—Discovery or management of network topologies of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
    • 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/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/16—Threshold monitoring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/20—Arrangements for monitoring or testing data switching networks the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV
    • 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/04—Network management architectures or arrangements
    • H04L41/044—Network management architectures or arrangements comprising hierarchical management structures

Definitions

  • the present disclosure relates to cellular networks and more specifically to performance metrics based alarm notification in a network function virtualization (NFV) infrastructure.
  • NFV network function virtualization
  • Wireless mobile communication technology uses various standards and protocols to transmit data between a base station and a wireless mobile device.
  • Wireless communication system standards and protocols can include the 3rd Generation Partnership Project (3GPP) long term evolution (LTE); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, which is commonly known to industry groups as worldwide interoperability for microwave access (WiMAX); and the IEEE 802.11 standard for wireless local area networks (WLAN), which is commonly known to industry groups as Wi-Fi.
  • 3GPP 3rd Generation Partnership Project
  • LTE long term evolution
  • IEEE 802.16 which is commonly known to industry groups as worldwide interoperability for microwave access
  • Wi-Fi wireless local area networks
  • the base station can include a RAN Node such as a Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB) and/or Radio Network Controller (RNC) in an E-UTRAN, which communicate with a wireless communication device, known as user equipment (UE).
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • Nodes can include a 5G Node, new radio (NR) node or g Node B (gNB).
  • NR new radio
  • gNB g Node B
  • RANs use a radio access technology (RAT) to communicate between the RAN Node and UE.
  • RANs can include global system for mobile communications (GSM), enhanced data rates for GSM evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), and/or E-UTRAN, which provide access to communication services through a core network.
  • GSM global system for mobile communications
  • EDGE enhanced data rates for GSM evolution
  • GERAN enhanced data rates for GSM evolution
  • UTRAN Universal Terrestrial Radio Access Network
  • E-UTRAN which provide access to communication services through a core network.
  • Each of the RANs operates according to a specific 3GPP RAT.
  • the GERAN implements GSM and/or EDGE RAT
  • the UTRAN implements universal mobile telecommunication system (UMTS) RAT or other 3GPP RAT
  • E- UTRAN implements LTE RAT.
  • UMTS universal mobile telecommunication system
  • a core network can be connected to the UE through the RAN Node.
  • the core network can include a serving gateway (SGW), a packet data network (PDN) gateway (PGW), an access network detection and selection function (ANDSF) server, an enhanced packet data gateway (ePDG) and/or a mobility management entity (MME).
  • SGW serving gateway
  • PGW packet data network gateway
  • ANDSF access network detection and selection function
  • ePDG enhanced packet data gateway
  • MME mobility management entity
  • FIG. 1 is a block diagram illustrating components of a system to support network functions virtualization (NFV).
  • NFV network functions virtualization
  • FIG. 2 is a diagram illustrating a system for providing a performance alarm for VNF PM data consistent with embodiments disclosed herein.
  • FIG. 3 is a ladder diagram illustrating a performance alarm notification procedure for NF performance measurements related to VR consistent with embodiments disclosed herein.
  • FIG. 4 is a state diagram of a mapping of threshold crossing notifications to performance alarms consistent with embodiments disclosed herein.
  • FIG. 5 is a flow chart illustrating a method for performance alarm notification for network function performance measurement related to virtual resources consistent with embodiments disclosed herein.
  • FIG. 6 illustrates an architecture of a system of a network consistent with
  • FIG. 7 illustrates example components of a device consistent with embodiments disclosed herein.
  • FIG. 8 illustrates example interfaces of baseband circuitry consistent with
  • FIG. 9 is an illustration of a control plane protocol stack consistent with embodiments disclosed herein.
  • FIG. 10 is an illustration of a user plane protocol stack consistent with embodiments disclosed herein.
  • FIG. 11 illustrates components of a core network consistent with embodiments disclosed herein.
  • FIG. 12 is a block diagram illustrating components able to read instructions from a machine-readable or computer-readable medium and perform any one or more of the methodologies discussed herein.
  • VNFM network function virtualization
  • NM network manager
  • EM determines whether or which alarm notification (i.e., notifyNew Alarm, notifyChangedAlarm or notifyClearedAlarm) should be sent to NM based on parameters received in ThresholdCrossedNotification.
  • the virtualized resource performance measurements are required. These performance measurements need to reflect the way VNFs are impacted by the NFVI services, and the inherent nature of the services being offered by the NFVI, for example, CPU, Virtual Machines, memory, and Virtual Networks. Therefore, the NFV performance measurements need to be measured in VNF and NFVI.
  • the 3GPP management system has a mechanism of using the threshold to monitor certain performance counters. When a counter has crossed the threshold, a performance alarm will be generated.
  • this invention proposes a method for an Element Manager (EM) to generate a performance alarm when a threshold crossing notification is received from VNFM (VNF Manager).
  • EM Element Manager
  • FIG. 1 is a block diagram illustrating components, according to some example embodiments, of a system 100 to support NFV.
  • the system 100 is illustrated as including a virtualized infrastructure manager (VIM) 102, a network function virtualization infrastructure (NFVI) 104, a VNF manager (VNFM) 106, virtualized network functions (VNFs) 108, an element manager (EM) 110, an NFV Orchestrator (NFVO) 112, and a network manager (NM) 114.
  • VIP virtualized infrastructure manager
  • NFVI network function virtualization infrastructure
  • VNFM VNF manager
  • VNFs virtualized network functions
  • EM element manager
  • NFVO NFV Orchestrator
  • NM network manager
  • the VIM 102 manages the resources of the NFVI 104.
  • the NFVI 104 can include physical or virtual resources and applications (including hypervisors) used to execute the system 100.
  • the VIM 102 may manage the life cycle of virtual resources with the NFVI 104 (e.g., creation, maintenance, and tear down of virtual machines (VMs) associated with one or more physical resources), track VM instances, track performance, fault and security of VM instances and associated physical resources, and expose VM instances and associated physical resources to other management systems.
  • VMs virtual machines
  • the VNFM 106 may manage the VNFs 108.
  • the VNFs 108 may be used to execute EPC components/functions.
  • the VNFM 106 may manage the life cycle of the VNFs 108 and track performance, fault and security of the virtual aspects of VNFs 108.
  • the EM 110 may track the performance, fault and security of the functional aspects of VNFs 108.
  • the tracking data from the VNFM 106 and the EM 110 may comprise, for example, performance measurement (PM) data used by the VIM 102 or the NFVI 104. Both the VNFM 106 and the EM 110 can scale up/down the quantity of VNFs of the system 100.
  • PM performance measurement
  • the NFVO 112 may coordinate, authorize, release and engage resources of the NFVI 104 in order to provide the requested service (e.g., to execute an EPC function, component, or slice).
  • the NM 114 may provide a package of end-user functions with the responsibility for the management of a network, which may include network elements with VNFs, non- virtualized network functions, or both (management of the VNFs may occur via the EM 110).
  • FIG. 2 is a diagram illustrating a system for providing a performance alarm for VNF PM data.
  • the system in FIG. 2 depicts how a performance alarm for VNF PM data related to Virtualized Resource (VR) is generated.
  • NM 202 sends a PM job creation request to EM 204 that sends a PM job creation to VNFM 226 to create a PM job 218 to collect performance data related to virtualized resources.
  • NM 202 sends a threshold creation request to EM 204 that sends a threshold creation to VNFM 226 to create a threshold to monitor if performance data related to virtualized resources that have been collected has crossed the threshold.
  • TCRD Threshold Crossing/Reaching Detection
  • VNFM 226 When TCRD (Threshold Crossing/Reaching Detection) function 216 at VNFM 226 detects that a VNF PM data related to VR has crossed a pre-defined threshold, it sends a threshold crossing notification to EM 204.
  • EM 204 receives the threshold crossing notification from VNFM 226, the MTCPA 210 (mapping of threshold crossing notifications) determines whether a performance alarm should be sent to NM 202. If so, EM 204 determines which performance alarm should be sent. An operation of MTCPA 210 is described later in this specification.
  • FIG. 3 is a ladder diagram illustrating a performance alarm notification procedure for NF performance measurements related to VR.
  • the procedure describes how EM 304 can generate a performance alarm when threshold crossing notifications 308 are received from VNFM 306. It is assumed that EM 304 has subscribed to receive the threshold crossing notification from VNFM 306. In operation 308, VNFM 306 sends a
  • ThresholdCrossedNotification with the following parameters to EM 304 to indicate the threshold that has been crossed.
  • a thresholdld identifies the threshold which has been crossed.
  • a crossingDirection indicates whether the threshold was crossed in upward or downward direction.
  • An objectlnstanceld identifies the VNF or VNFC instance for which the threshold has been crossed.
  • a performanceMetric indicates the performance metric associated with the threshold.
  • a performance Value indicates the value of the metric that resulted in threshold crossing.
  • EM 304 determines whether or which alarm notification (i.e., notifyNewAlarm, notifyChangedAlarm or notifyClearedAlarm) should be sent to NM 302 based on parameters received in ThresholdCrossedNotification. In operation 312, if an alarm needs to be generated, then continue; otherwise skip the rest of the operations. In operation 314, the EM 304 saves the performance alarm to the AlarmList. In operation 316, if the performance alarm is a new alarm, then EM 304 sends a notifyNewAlarm notification to NM 302.
  • alarm notification i.e., notifyNewAlarm, notifyChangedAlarm or notifyClearedAlarm
  • FIG. 4 is a state diagram 400 of a mapping of threshold crossing notifications to performance alarms. In the embodiment shown and upon receiving a
  • ThresholdCrossedNotification from VNFM that indicates the performance measurements of VNF/VNFC identified by objectlnstanceld has crossed the threshold
  • EM generates a performance alarm, according to the ThresholdMonitor created by NM.
  • ThresholdMonitor definition allows a NM to assign up to four different severity levels (i.e., critical, major, minor, warning) for the performance alarm, based on four different threshold levels.
  • the state transition diagram shows whether a performance alarm should be sent, and if so, with which alarm severity, based on the threshold levels that have been crossed in the current and the previous ThresholdCrossedNotification.
  • the threshold diagram is based on 4 threshold levels - Threshold-1, Threshold-2, Threshold-3, and Threshold-4.
  • the threshold level that has been crossed for a given threshold level is based on 4 threshold levels - Threshold-1, Threshold-2, Threshold-3, and Threshold-4. The threshold level that has been crossed for a given threshold level.
  • ThresholdCrossedNotification notification can be derived from thresholdld
  • the crossingDirection notification indicates that the threshold crossing is in an increasing direction, and the value in performanceValue is 650. Then Threshold-3 has been crossed.
  • the following embodiment lists the states corresponding to each threshold level that was crossed in increasing direction of the threshold monitoring.
  • the performanceValue exceeding Threshold-4 generates an alarm with critical severity, while the performanceValue going under Threshold-1 declares an alarm has been cleared.
  • State-0 indicates that the performanceValue is below Threshold-1, and is the initial state.
  • State-1 indicates that the performanceValue is equal to or above Threshold-1, and below Threshold-2.
  • State-2 indicates that the performanceValue is equal to or above Threshold-2, and below Threshold- 3.
  • State-3 indicates that the performanceValue is equal to or above Threshold-3, and below Threshold-4.
  • State-4 indicates that the performanceValue is equal to or above Threshold-4.
  • the following embodiment lists the states corresponding to each threshold level that was crossed for decreasing direction of the threshold monitoring.
  • the performanceValue exceeding Threshold-4 declares an alarm has been cleared, while the performanceValue going under Threshold-1 generates an alarm with critical severity.
  • State-0 indicates that the performance Value is above Threshold-4, and is the initial state.
  • State-1 indicates that the performance Value is equal to or below Threshold-4, and above Threshold-3.
  • State-2 indicates that the performance Value is equal to or below Threshold-3, and above Threshold- 2.
  • State-3 indicates that the performanceValue is equal to or below Threshold-2, and above Threshold-1.
  • State-4 indicates that the performanceValue is equal to or below Threshold-1.
  • Act-1 no need to send alarm notification.
  • Act-2 send a notification notifyNew Alarm.
  • Act- 3 send a notification notifyChangedAlarm, if supported; otherwise, send a notification notifyClearedAlarm, and then notification notifyNewAlarm.
  • Act-4 send a notification notifyClearedAlarm.
  • FIG. 5 is a method of performance alarm notification for network function
  • an EM generates a request to a virtualized network function manager (VNFM) to subscribe to a crossing notification for a first performance metric threshold for a virtual network function (VNF) or virtual network function component (VNFC).
  • VNFM virtualized network function manager
  • VNFC virtual network function component
  • an EM processes the crossing notification from the VNFM indicating a performance metric value of the VNF or VNFC has crossed a performance metric threshold.
  • an EM maps a measured VNF or a measured VNFC to a network function.
  • an EM determines a performance measurement value for the mapped network function.
  • an EM determines that an alarm notification is to be sent to the network management (NM) based at least in part on the crossing notification and a threshold monitor created by the NM. In block 512, an EM saves a performance alarm to an alarm list. In block 514, an EM generates the alarm notification of the performance alarm to the NM.
  • NM network management
  • FIG. 6 illustrates an architecture of a system 600 of a network in accordance with some embodiments.
  • the system 600 is shown to include a user equipment (UE) 601 and a UE 602.
  • the UEs 601 and 602 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, or any computing device including a wireless communications interface.
  • PDAs Personal Data Assistants
  • any of the UEs 601 and 602 can comprise an Internet of Things (IoT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections.
  • 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 describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived
  • the IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.
  • background applications e.g., keep-alive messages, status updates, etc.
  • the UEs 601 and 602 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 610.
  • the RAN 610 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.
  • UMTS Evolved Universal Mobile Telecommunications System
  • E-UTRAN Evolved Universal Mobile Telecommunications System
  • NG RAN NextGen RAN
  • the UEs 601 and 602 utilize connections 603 and 604, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 603 and 604 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 3 GPP 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 601 and 602 may further directly exchange
  • the ProSe interface 605 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PS SCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink
  • PSCCH Physical Sidelink Control Channel
  • PS SCH Physical Sidelink Shared Channel
  • PSDCH Physical Sidelink Discovery Channel
  • PSBCH Broadcast Channel
  • the UE 602 is shown to be configured to access an access point (AP) 606 via connection 607.
  • the connection 607 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 606 would comprise a wireless fidelity (WiFi®) router.
  • WiFi® wireless fidelity
  • the AP 606 may be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).
  • the RAN 610 can include one or more access nodes that enable the connections 603 and 604. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next Generation NodeBs (gNB), RAN nodes, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
  • BSs base stations
  • eNBs evolved NodeBs
  • gNB next Generation NodeBs
  • RAN nodes and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
  • the RAN 610 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 611, 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 612.
  • macro RAN node 611 e.g., macro RAN node 611
  • 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 611 and 612 can terminate the air interface protocol and can be the first point of contact for the UEs 601 and 602.
  • any of the RAN nodes 611 and 612 can fulfill various logical functions for the RAN 610 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
  • the UEs 601 and 602 can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 611 and 612 over a multicarrier communication channel in accordance various communication techniques, such as, but not limited to, an Orthogonal Frequency-Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect.
  • OFDM signals can comprise a plurality of orthogonal subcarriers.
  • a downlink resource grid can be used for downlink
  • the grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot.
  • a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation.
  • Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively.
  • the duration of the resource grid in the time domain corresponds to one slot in a radio frame.
  • the smallest time-frequency unit in a resource grid is denoted as a resource element.
  • Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements.
  • Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks.
  • the physical downlink shared channel may carry user data and higher-layer signaling to the UEs 601 and 602.
  • the physical downlink control channel (PDCCH) may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs 601 and 602 about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel.
  • downlink scheduling (assigning control and shared channel resource blocks to the UE 602 within a cell) may be performed at any of the RAN nodes 611 and 612 based on channel quality information fed back from any of the UEs 601 and 602.
  • the downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 601 and 602.
  • the PDCCH may use control channel elements (CCEs) to convey the control information.
  • CCEs control channel elements
  • the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub- block interleaver for rate matching.
  • Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as resource element groups (REGs).
  • RAGs resource element groups
  • QPSK Quadrature Phase Shift Keying
  • the PDCCH can be transmitted using one or more CCEs, depending on the size of the downlink control information (DCI) and the channel condition.
  • DCI downlink control information
  • There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L l, 2, 4, or 8).
  • Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts.
  • some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission.
  • the EPDCCH may be transmitted using one or more enhanced the control channel elements (ECCEs). Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as enhanced resource element groups (EREGs). An ECCE may have other numbers of EREGs in some situations.
  • EPCCH enhanced physical downlink control channel
  • ECCEs enhanced the control channel elements
  • each ECCE may correspond to nine sets of four physical resource elements known as enhanced resource element groups (EREGs).
  • EREGs enhanced resource element groups
  • An ECCE may have other numbers of EREGs in some situations.
  • the RAN 610 is shown to be communicatively coupled to a core network (CN) 620 — via an SI interface 613.
  • the CN 620 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN.
  • EPC evolved packet core
  • NPC NextGen Packet Core
  • the SI interface 613 is split into two parts: the Sl-U interface 614, which carries traffic data between the RAN nodes 611 and 612 and a serving gateway (S-GW) 622, and an SI -mobility management entity (MME) interface 615, which is a signaling interface between the RAN nodes 611 and 612 and MMEs 621.
  • S-GW serving gateway
  • MME SI -mobility management entity
  • the CN 620 comprises the MMEs 621, the S-GW 622, a Packet Data Network (PDN) Gateway (P-GW) 623, and a home subscriber server (HSS) 624.
  • the MMEs 621 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
  • GPRS General Packet Radio Service
  • the MMEs 621 may manage mobility aspects in access such as gateway selection and tracking area list management.
  • the HSS 624 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions.
  • the CN 620 may comprise one or several HSSs 624, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc.
  • the HSS 624 can provide support for routing/roaming, authentication, authorization,
  • the S-GW 622 may terminate the SI interface 613 towards the RAN 610, and routes data packets between the RAN 610 and the CN 620.
  • the S-GW 622 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the P-GW 623 may terminate an SGi interface toward a PDN.
  • the P-GW 623 may route data packets between the CN 620 (e.g., an EPC network) and external networks such as a network including the application server 630 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 625.
  • an application server 630 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.).
  • the P-GW 623 is shown to be communicatively coupled to an application server 630 via an IP communications interface 625.
  • the application server 630 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 601 and 602 via the CN 620.
  • VoIP Voice-over-Internet Protocol
  • PTT sessions PTT sessions
  • group communication sessions social networking services, etc.
  • the P-GW 623 may further be a node for policy enforcement and charging data collection.
  • a Policy and Charging Enforcement Function (PCRF) 626 is the policy and charging control element of the CN 620.
  • PCRF Policy and Charging Enforcement Function
  • HPLMN Home Public Land Mobile Network
  • IP-CAN Internet Protocol Connectivity Access Network
  • HPLMN Home Public Land Mobile Network
  • V-PCRF Visited PCRF
  • VPLMN Visited Public Land Mobile Network
  • the PCRF 626 may be communicatively coupled to the application server 630 via the P-GW 623.
  • the application server 630 may signal the PCRF 626 to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters.
  • the PCRF 626 may provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which commences the QoS and charging as specified by the application server 630.
  • PCEF Policy and Charging Enforcement Function
  • TFT traffic flow template
  • QCI QoS class of identifier
  • FIG. 7 illustrates example components of a device 700 in accordance with some embodiments.
  • the device 700 may include application circuitry 702, baseband circuitry 704, Radio Frequency (RF) circuitry 706, front-end module (FEM) circuitry 708, one or more antennas 710, and power management circuitry (PMC) 712 coupled together at least as shown.
  • the components of the illustrated device 700 may be included in a UE or a RAN node.
  • the device 700 may include fewer elements (e.g., a RAN node may not utilize application circuitry 702, and instead include a processor/controller to process IP data received from an EPC).
  • the device 700 may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface.
  • the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN) implementations).
  • C-RAN Cloud-RAN
  • the application circuitry 702 may include one or more application processors.
  • the application circuitry 702 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the processor(s) may include any combination of general -purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.).
  • the processors may be coupled with or may include
  • processors of application circuitry 702 may process IP data packets received from an EPC.
  • the baseband circuitry 704 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 704 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 706 and to generate baseband signals for a transmit signal path of the RF circuitry 706.
  • Baseband processing circuity 704 may interface with the application circuitry 702 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 706.
  • the baseband circuitry 704 may include a third generation (3G) baseband processor 704 A, a fourth generation (4G) baseband processor 704B, a fifth generation (5G) baseband processor 704C, or other baseband processor(s) 704D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.).
  • the baseband circuitry 704 e.g., one or more of baseband processors 704A-D
  • baseband processors 704 A-D may be included in modules stored in the memory 704G and executed via a Central Processing Unit (CPU) 704E.
  • the radio control functions may include, but are not limited to, signal modulation/demodulation,
  • modulation/demodulation circuitry of the baseband circuitry 704 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality.
  • FFT Fast-Fourier Transform
  • encoding/decoding circuitry of the baseband circuitry 704 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.
  • the baseband circuitry 704 may include one or more audio digital signal processor(s) (DSP) 704F.
  • the audio DSP(s) 704F may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.
  • Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments.
  • some or all of the constituent components of the baseband circuitry 704 and the application circuitry 702 may be implemented together such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 704 may provide for
  • the baseband circuitry 704 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), or a wireless personal area network (WPAN).
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • Embodiments in which the baseband circuitry 704 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.
  • RF circuitry 706 may enable communication with wireless networks
  • the RF circuitry 706 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • the RF circuitry 706 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 708 and provide baseband signals to the baseband circuitry 704.
  • RF circuitry 706 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 704 and provide RF output signals to the FEM circuitry 708 for transmission.
  • the receive signal path of the RF circuitry 706 may include mixer circuitry 706A, amplifier circuitry 706B and filter circuitry 706C. In some embodiments,
  • the transmit signal path of the RF circuitry 706 may include filter circuitry 706C and mixer circuitry 706 A.
  • RF circuitry 706 may also include synthesizer circuitry 706D for synthesizing a frequency for use by the mixer circuitry 706A of the receive signal path and the transmit signal path.
  • the mixer circuitry 706A of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 708 based on the synthesized frequency provided by synthesizer circuitry 706D.
  • the amplifier circuitry 706B may be configured to amplify the down-converted signals and the filter circuitry 706C may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals.
  • Output baseband signals may be provided to the baseband circuitry 704 for further processing.
  • the output baseband signals may be zero-frequency baseband signals, although this is not a requirement.
  • the mixer circuitry 706A of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 706A of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 706D to generate RF output signals for the FEM circuitry 708.
  • the baseband signals may be provided by the baseband circuitry 704 and may be filtered by the filter circuitry 706C.
  • the mixer circuitry 706A of the receive signal path and the mixer circuitry 706A of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively.
  • the mixer circuitry 706A of the receive signal path and the mixer circuitry 706A of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 706A of the receive signal path and the mixer circuitry 706A may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry 706A of the receive signal path and the mixer circuitry 706A of the transmit signal path may be configured for super-heterodyne operation.
  • the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
  • the output baseband signals and the input baseband signals may be digital baseband signals.
  • the RF circuitry 706 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 704 may include a digital baseband interface to communicate with the RF circuitry 706.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
  • the synthesizer circuitry 706D may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 706D may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 706D may be configured to synthesize an output frequency for use by the mixer circuitry 706A of the RF circuitry 706 based on a frequency input and a divider control input.
  • the synthesizer circuitry 706D may be a fractional N/N+l synthesizer.
  • frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
  • VCO voltage controlled oscillator
  • Divider control input may be provided by either the baseband circuitry 704 or the application circuitry 702 (such as an applications processor) depending on the desired output frequency.
  • a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the application circuitry 702.
  • Synthesizer circuitry 706D of the RF circuitry 706 may include a divider, a delay- locked loop (DLL), a multiplexer and a phase accumulator.
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DP A).
  • the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio.
  • the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
  • the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
  • Nd is the number of delay elements in the delay line.
  • the synthesizer circuitry 706D may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
  • the output frequency may be a LO frequency (fLO).
  • the RF circuitry 706 may include an IQ/polar converter.
  • FEM circuitry 708 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 710, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 706 for further processing.
  • the FEM circuitry 708 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 706 for transmission by one or more of the one or more antennas 710.
  • the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 706, solely in the FEM circuitry 708, or in both the RF circuitry 706 and the FEM circuitry 708.
  • the FEM circuitry 708 may include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry 708 may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry 708 may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 706).
  • the transmit signal path of the FEM circuitry 708 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by the RF circuitry 706), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 710).
  • PA power amplifier
  • the PMC 712 may manage power provided to the baseband circuitry 704.
  • the PMC 712 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
  • the PMC 712 may often be included when the device 700 is capable of being powered by a battery, for example, when the device 700 is included in a UE.
  • the PMC 712 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.
  • FIG. 7 shows the PMC 712 coupled only with the baseband circuitry 704.
  • the PMC 712 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, the application circuitry 702, the RF circuitry 706, or the FEM circuitry 708.
  • the PMC 712 may control, or otherwise be part of, various power saving mechanisms of the device 700. For example, if the device 700 is in an
  • RRC Connected state where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 700 may power down for brief intervals of time and thus save power.
  • DRX Discontinuous Reception Mode
  • the device 700 may transition off to an RRC Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc.
  • the device 700 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again.
  • the device 700 may not receive data in this state, and in order to receive data, it transitions back to an RRC Connected state.
  • An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.
  • Processors of the application circuitry 702 and processors of the baseband circuitry 704 may be used to execute elements of one or more instances of a protocol stack.
  • processors of the baseband circuitry 704 alone or in combination, may be used to execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 702 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers).
  • Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below.
  • RRC radio resource control
  • Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below.
  • Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.
  • FIG. 8 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
  • the baseband circuitry 704 of FIG. 7 may comprise processors 704A-704E and a memory 704G utilized by said processors.
  • Each of the processors 704A-704E may include a memory interface, 804A-804E, respectively, to send/receive data to/from the memory 704G.
  • the baseband circuitry 704 may further include one or more interfaces to
  • a memory interface 812 e.g., an interface to send/receive data to/from memory external to the baseband circuitry 704
  • an application circuitry interface 814 e.g., an interface to send/receive data to/from the application circuitry 702 of FIG. 7
  • an RF circuitry interface 816 e.g., an interface to send/receive data to/from RF circuitry 706 of FIG.
  • a wireless hardware connectivity interface 818 e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components
  • a power management interface 820 e.g., an interface to send/receive power or control signals to/from the PMC 712.
  • FIG. 9 is an illustration of a control plane protocol stack in accordance with some embodiments.
  • a control plane 900 is shown as a communications protocol stack between the UE 601 (or alternatively, the UE 602), the RAN node 611 (or alternatively, the RAN node 612), and the MME 621.
  • a PHY layer 901 may transmit or receive information used by the MAC layer 902 over one or more air interfaces.
  • the PHY layer 901 may further perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers, such as an RRC layer 905.
  • the PHY layer 901 may still further perform error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, modulation/demodulation of physical channels, interleaving, rate matching, mapping onto physical channels, and Multiple Input Multiple Output (MIMO) antenna processing.
  • FEC forward error correction
  • MIMO Multiple Input Multiple Output
  • the MAC layer 902 may perform mapping between logical channels and transport channels, multiplexing of MAC service data units (SDUs) from one or more logical channels onto transport blocks (TB) to be delivered to PHY via transport channels, de-multiplexing MAC SDUs to one or more logical channels from transport blocks (TB) delivered from the PHY via transport channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), and logical channel prioritization.
  • SDUs MAC service data units
  • TB transport blocks
  • HARQ hybrid automatic repeat request
  • An RLC layer 903 may operate in a plurality of modes of operation, including:
  • the RLC layer 903 may execute transfer of upper layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transfers, and concatenation, segmentation and reassembly of RLC SDUs for UM and AM data transfers.
  • the RLC layer 903 may also execute re-segmentation of RLC data PDUs for AM data transfers, reorder RLC data PDUs for UM and AM data transfers, detect duplicate data for UM and AM data transfers, discard RLC SDUs for UM and AM data transfers, detect protocol errors for AM data transfers, and perform RLC re-establishment.
  • a PDCP layer 904 may execute header compression and decompression of IP data, maintain PDCP Sequence Numbers (SNs), perform in-sequence delivery of upper layer PDUs at re-establishment of lower layers, eliminate duplicates of lower layer SDUs at re- establishment of lower layers for radio bearers mapped on RLC AM, cipher and decipher control plane data, perform integrity protection and integrity verification of control plane data, control timer-based discard of data, and perform security operations (e.g., ciphering, deciphering, integrity protection, integrity verification, etc.).
  • SNs PDCP Sequence Numbers
  • the main services and functions of the RRC layer 905 may include broadcast of system information (e.g., included in Master Information Blocks (MIBs) or System
  • SIBs Information Blocks related to the non-access stratum (NAS)), broadcast of system information related to the access stratum (AS), paging, establishment, maintenance and release of an RRC connection between the UE and E-UTRAN (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance and release of point-to-point radio bearers, security functions including key management, inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting.
  • Said MIBs and SIBs may comprise one or more information elements (IEs), which may each comprise individual data fields or data structures.
  • IEs information elements
  • the UE 601 and the RAN node 611 may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange control plane data via a protocol stack comprising the PHY layer 901, the MAC layer 902, the RLC layer 903, the PDCP layer 904, and the RRC layer 905.
  • a Uu interface e.g., an LTE-Uu interface
  • the non-access stratum (NAS) protocols 906 form the highest stratum of the control plane between the UE 601 and the MME 621.
  • the NAS protocols 906 support the mobility of the UE 601 and the session management procedures to establish and maintain IP connectivity between the UE 601 and the P-GW 623.
  • the SI Application Protocol (Sl-AP) layer 915 may support the functions of the SI interface and comprise Elementary Procedures (EPs).
  • An EP is a unit of interaction between the RAN node 611 and the CN 620.
  • the Sl-AP layer services may comprise two groups: UE-associated services and non UE-associated services. These services perform functions including, but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transport, RAN Information Management (RIM), and configuration transfer.
  • E-RAB E-UTRAN Radio Access Bearer
  • RIM Radio Information Management
  • the Stream Control Transmission Protocol (SCTP) layer (alternatively referred to as the stream control transmission protocol/internet protocol (SCTP/IP) layer) 914 may ensure reliable delivery of signaling messages between the RAN node 611 and the MME 621 based, in part, on the IP protocol, supported by an IP layer 913.
  • An L2 layer 912 and an LI layer 911 may refer to communication links (e.g., wired or wireless) used by the RAN node and the MME to exchange information.
  • the RAN node 611 and the MME 621 may utilize an SI -MME interface to exchange control plane data via a protocol stack comprising the LI layer 911, the L2 layer 912, the IP layer 913, the SCTP layer 914, and the Sl-AP layer 915.
  • FIG. 10 is an illustration of a user plane protocol stack in accordance with some embodiments.
  • a user plane 1000 is shown as a communications protocol stack between the UE 601 (or alternatively, the UE 602), the RAN node 611 (or alternatively, the RAN node 612), the S-GW 622, and the P-GW 623.
  • the user plane 1000 may utilize at least some of the same protocol layers as the control plane 900.
  • the UE 601 and the RAN node 611 may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange user plane data via a protocol stack comprising the PHY layer 901, the MAC layer 902, the RLC layer 903, the PDCP layer 904.
  • a Uu interface e.g., an LTE-Uu interface
  • the General Packet Radio Service (GPRS) Tunneling Protocol for the user plane (GTP-U) layer 1004 may be used for carrying user data within the GPRS core network and between the radio access network and the core network.
  • the user data transported can be packets in any of IPv4, IPv6, or PPP formats, for example.
  • the UDP and IP security (UDP/IP) layer 1003 may provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication on the selected data flows.
  • the RAN node 611 and the S-GW 622 may utilize an Sl-U interface to exchange user plane data via a protocol stack comprising the LI layer 911, the L2 layer 912, the UDP/IP layer 1003, and the GTP-U layer 1004.
  • the S-GW 622 and the P-GW 623 may utilize an S5/S8a interface to exchange user plane data via a protocol stack comprising the LI layer 911, the L2 layer 912, the UDP/IP layer 1003, and the GTP-U layer 1004.
  • NAS protocols support the mobility of the UE 601 and the session management procedures to establish and maintain IP connectivity between the UE 601 and the P-GW 623.
  • FIG. 11 illustrates components of a core network in accordance with some embodiments.
  • the components of the CN 620 may be implemented in one physical node or separate physical nodes including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium).
  • Network Functions Virtualization NFV is utilized to virtualize any or all of the above described network node functions via executable instructions stored in one or more computer readable storage mediums (described in further detail below).
  • a logical instantiation of the CN 620 may be referred to as a network slice 1101.
  • a logical instantiation of a portion of the CN 620 may be referred to as a network sub- slice 1102 (e.g., the network sub-slice 1102 is shown to include the P-GW 623 and the PCRF 626).
  • NFV architectures and infrastructures may be used to virtualize one or more network functions, alternatively performed by proprietary hardware, onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches.
  • NFV systems can be used to execute virtual or reconfigurable implementations of one or more EPC components/functions.
  • FIG. 12 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • FIG. 12 shows a diagrammatic representation of hardware resources 1200 including one or more processors (or processor cores) 1210, one or more memory/storage devices 1220, and one or more communication resources 1230, each of which may be communicatively coupled via a bus 1240.
  • node virtualization e.g., NFV
  • a hypervisor 1202 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 1200.
  • the processors 1210 may include, for example, a processor 1212 and a processor 1214.
  • CPU central processing unit
  • RISC reduced instruction set computing
  • CISC complex instruction set computing
  • GPU graphics processing unit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • RFIC radio-frequency integrated circuit
  • the memory/storage devices 1220 may include main memory, disk storage, or any suitable combination thereof.
  • the memory/storage devices 1220 may include, but are not limited to any type of volatile or non-volatile memory such as dynamic random access memory (DRAM), static random-access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.
  • DRAM dynamic random access memory
  • SRAM static random-access memory
  • EPROM erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • Flash memory solid-state storage, etc.
  • the communication resources 1230 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 1204 or one or more databases 1206 via a network 1208.
  • the communication resources 1230 may include wired communication components (e.g., for coupling via a Universal Serial Bus (USB)), cellular communication components, NFC components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components.
  • wired communication components e.g., for coupling via a Universal Serial Bus (USB)
  • cellular communication components e.g., for coupling via a Universal Serial Bus (USB)
  • NFC components e.g., NFC components
  • Bluetooth® components e.g., Bluetooth® Low Energy
  • Wi-Fi® components e.g., Wi-Fi® components
  • Instructions 1250 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1210 to perform any one or more of the methodologies discussed herein.
  • the instructions 1250 may reside, completely or partially, within at least one of the processors 1210 (e.g., within the processor's cache memory), the memory/storage devices 1220, or any suitable combination thereof.
  • any portion of the instructions 1250 may be transferred to the hardware resources 1200 from any combination of the peripheral devices 1204 or the databases 1206. Accordingly, the memory of processors 1210, the memory/storage devices 1220, the peripheral devices 1204, and the databases 1206 are examples of computer-readable and machine-readable media.
  • Example 1 is an apparatus of an element manager (EM), the apparatus comprising a memory and a processor.
  • the memory interface is configured to send and retrieve a performance metric value.
  • the processor is configured to: process a notification from a virtualized network function manager (VNFM) indicating the performance metric value has crossed a first threshold; map a measured virtual network function (VNF) or a measured virtual network function component (VNFC) performance metric to a network function; determine a performance measurement value for the mapped network function; determine whether an alarm notification is to be sent to a network management (NM) based at least in part on a second threshold created by the NM and the performance measurement value; when the alarm notification is determined to be sent: save a performance alarm to an alarm list; and generate the alarm notification of the performance alarm to the NM.
  • VNFM virtualized network function manager
  • NM network management
  • Example 2 is the apparatus of the EM of Example 1, wherein to generate the alarm notification of the performance alarm to the NM further comprises to: determine the performance alarm is a new alarm; and generate a new alarm notification for the NM.
  • Example 3 is the apparatus of the EM of Example 1, wherein to generate the alarm notification of the performance alarm to the NM further comprises to: determine the performance alarm is a changed alarm; and generate a changed alarm notification for the NM.
  • Example 4 is the apparatus of the EM of Example 1, wherein to generate the alarm notification of the performance alarm to the NM further comprises to: determine the performance alarm is a changed alarm; generate a cleared alarm notification for the NM; and generate a new alarm notification for the NM.
  • Example 5 is the apparatus of the EM of Example 1, wherein to generate the alarm notification of the performance alarm to the NM further comprises to: determine the performance alarm is a changed alarm; determine whether the NM supports a changed alarm notification; when determined that the NM supports the changed alarm notification, generate the changed alarm notification for the NM; and when determined that the NM does not support the changed alarm notification: generate a cleared alarm notification for the NM, and generate a new alarm notification for the NM.
  • Example 6 is the apparatus of the EM of Example 1, wherein to generate the alarm notification of the performance alarm to the NM further comprises to: determine the performance alarm is a cleared alarm; and generate a cleared alarm notification for the NM.
  • Example 7 is the apparatus of the EM of any of Examples 1-6, wherein the notification indicates a threshold identifier for both the first threshold and the second threshold and a crossing direction.
  • Example 8 is the apparatus of the EM of Example 1, wherein the notification indicates a VNF instance or a VNFC instance for which the first threshold has been crossed.
  • Example 9 is the apparatus of the EM of any of Examples 1-6, wherein the processor is further configured to generate a request to the VNFM to subscribe to one or more crossing notifications for the first threshold.
  • Example 10 is the apparatus of the EM of any of Examples 1-6, wherein a performance metric or a performance measurement is related to a virtualized resource.
  • Example 11 is a method of performance alarm notification for network function performance measurement related to virtual resources, the method comprising: generating a request to a virtualized network function manager (VNFM) to subscribe to a crossing notification for a first performance metric threshold for a virtual network function (VNF) or virtual network function component (VNFC); processing the crossing notification from the VNFM indicating a performance metric value of the VNF or VNFC has crossed a
  • VNFM virtualized network function manager
  • NM network management
  • Example 12 is the method of Example 11, wherein to generate the alarm notification of the performance alarm to the NM further comprises to: determine whether to generate a new alarm notification, a cleared alarm notification or a changed alarm
  • Example 13 is the method of Example 11, further comprising: determine the performance alarm is a new alarm; and generate a new alarm notification for the NM.
  • Example 14 is the method of Example 11, further comprising: determine the performance alarm is a changed alarm; and generate a changed alarm notification for the NM.
  • Example 15 is the method of Example 11, further comprising: determine the performance alarm is a changed alarm; generate a cleared alarm notification for the NM, and generate a new alarm notification for the NM.
  • Example 16 is the method of Example 11, further comprising: determine the performance alarm is a changed alarm; determine whether the NM supports a changed alarm notification; when determined that the NM supports the changed alarm notification, generate the changed alarm notification for the NM; and when determined that the NM does not support the changed alarm notification: generate a cleared alarm notification for the NM, and generate a new alarm notification for the NM.
  • Example 17 is the method of Example 11, further comprising: determine the performance alarm is a cleared alarm; and generate a cleared alarm notification for the NM.
  • Example 18 is the method of any of Examples 11-17, wherein the crossing notification indicates a threshold identifier, crossing direction, a managed function distinguished name (DN), a virtual network function object instance identifier, a virtual network function component identifier, and a performance measurement or the performance measurement value.
  • DN managed function distinguished name
  • Example 19 is an apparatus comprising means to perform a method as exemplified in any of Examples 11-17.
  • Example 20 is a machine readable medium including code, when executed, to cause a machine to perform the method of any one of Examples 11-17.
  • Example 21 is a system for virtualized network functions, the system comprising: a virtualized network function manager (VNFM) configured to generate a crossing notification to an element manager (EM) indicating a performance metric value of a virtual network function (VNF) or virtual network function component (VNFC) has crossed a performance metric threshold; the EM configured to: process the crossing notification that the performance metric value of the VNF or VNFC has crossed the performance metric threshold; map the VNF or the VNFC to a network function; determine a performance measurement value for the mapped network function; determine whether an alarm
  • NM network management
  • Example 22 is the system of Example 21, wherein the EM further comprises storage for the alarm list.
  • Example 23 is the system of Example 21, wherein to generate the alarm notification to the NM of the performance alarm further comprises to: determine whether to generate a new alarm notification, a cleared alarm notification or a changed alarm
  • Example 24 is the system of any of Examples 21-23, wherein the NM is further configured to configure a threshold monitor for the EM.
  • Example 25 is the system of any of Examples 21-23, wherein a performance metric or a performance measurement is related to a virtualized resource.
  • Example 26 is a computer program product comprising a computer-readable storage medium that stores instructions for execution by a processor to perform operations of an element manager (EM), the operations, when executed by the processor, to perform a method, the method comprising: generating a request to a virtualized network function manager (VNFM) to subscribe to a crossing notification for a first performance metric threshold for a virtual network function (VNF) or virtual network function component (VNFC); processing the crossing notification from the VNFM indicating a performance metric value of the VNF or VNFC has crossed a performance metric threshold; mapping a measured VNF or a measured VNFC to a network function; determining a performance measurement value for the mapped network function; determining that an alarm notification is to be sent to the network management (NM) based at least in part on the crossing notification and a threshold monitor created by the NM; saving a performance alarm to an alarm list; and generating the alarm notification of the performance alarm to the NM.
  • VNFM virtualized network function manager
  • NM network
  • Example 27 is the computer program product of Example 26, wherein to generate the alarm notification of the performance alarm to the NM further comprises to: determine whether to generate a new alarm notification, a cleared alarm notification or a changed alarm notification.
  • Example 28 is an apparatus of an element manager (EM), the apparatus comprising: means for generating a request to a virtualized network function manager (VNFM) to subscribe to a crossing notification for a first performance metric threshold for a virtual network function (VNF) or virtual network function component (VNFC); means for processing the crossing notification from the VNFM indicating a performance metric value of the VNF or VNFC has crossed a performance metric threshold; means for mapping a measured VNF or a measured VNFC to a network function; means for determining a performance measurement value for the mapped network function; means for determining that an alarm notification is to be sent to the network management (NM) based at least in part on the crossing notification and a threshold monitor created by the NM; means for saving a performance alarm to an alarm list; and means for generating the alarm notification of the performance alarm to the NM.
  • VNFM virtualized network function manager
  • Example 29 is the apparatus of Example 28, wherein the means for generating the alarm notification of the performance alarm to the NM further comprises: means for determining whether to generate a new alarm notification, a cleared alarm notification or a changed alarm notification.
  • Additional Example 1 may include a non-transitory computer-readable storage medium that stores instructions for execution by one or more processors of an element manager (EM), the one or more processors to cause the EM to: receive a request from a network manager (NM) to create a performance management (PM) job to collect the performance data related to virtualized resources; send a request to virtual network functions manager (VNFM) to create a PM job to collect the performance data related to virtualized resources; receive a request from NM to create a threshold to monitor if the performance data related to virtualized resources have crossed the threshold; and send a request to VNFM to create a threshold to monitor if the performance data related to virtualized resources have crossed the threshold.
  • EM element manager
  • Additional Example 2 may include the apparatus of Additional Example 1 and/or some other Additional Example herein, wherein the one or more processors further cause the EM to: receive a threshold crossing notification from VNFM, indicating a performance counter has crossed the pre-defined threshold; and implement the MTCPA (mapping of threshold crossing notifications) to determine whether and which alarm notification should be sent to NM.
  • VNFM threshold crossing notification
  • MTCPA mapping of threshold crossing notifications
  • Additional Example 3 may include the medium of Additional Example 2 and/or some other Additional Example herein, wherein if MTCPA determines an alarm needs to be generated, then the one or more processors will cause the EM to: save the performance alarm to the AlarmList; and send the notifyNew Alarm alarm notification to NM, if the MTCPA determines a new alarm has been generated; send the notifyChangedAlarm alarm notification to NM, if the MTCPA determines the severity of an existing alarm has been changed; send the notifyClearedAlarm and notifyNew Alarm alarm notifications to NM, if the MTCPA determines the severity of an existing alarm has been changed, and if notifyChangedAlarm alarm notification is not supported; and send the notifyClearedAlarm alarm notification to M, if the MTCPA determines an existing alarm has been cleared.
  • Additional Example 4 may include the medium of Additional Example 1 and/or some other Additional Example herein, wherein NM may assign up to four different threshold levels that map to four different alarm severities (i.e., critical, major, minor, warning).
  • Additional Example 5 may include the medium of Additional Example 1 and/or some other Additional Example herein, wherein threshold crossing notification contains: thresholdld: identifies the threshold which has been crossed; crossingDirection: indicates whether the threshold was crossed in an upward or downward direction; objectlnstanceld: identifies the VNF or VNFC instance for which the threshold has been crossed;
  • performanceMetric indicates the performance metric associated with the threshold
  • performanceValue indicates the value of the metric that resulted in threshold crossing.
  • Additional Example 6 may include the medium of Additional Example 2 and/or some other Additional Example herein, wherein MTCPA has a state machine that has five states to determine whether and which alarm notification should be sent based on the threshold notification received from VNFM.
  • Additional Example 7 may include the medium of Additional Examples 6 and 5 and/or some other Additional Example herein, wherein if the crossingDirection attribute received in the threshold crossing notification is upward, then the state table that defines which state will be transitioned to, based on where the performanceValue among threshold levels is shown as the following: State-0: This state indicates that the performanceValue is below Threshold-1, and is the initial state; State-1 : This state indicates that the
  • performanceValue is equal to or above Threshold-4.
  • Additional Example 8 may include the medium of Additional Examples 6 and 5 and/or some other Additional Examples herein, wherein if the crossingDirection attribute received in the threshold crossing notification is downward, then the state table that defines which state will be transitioned to, based on where the performanceValue among threshold levels is shown as the following: State-0: This state indicates that the performanceValue is above Threshold-4, and is in the initial state; State-1 : This state indicates that the performance Value is equal to or below Threshold-4, and above Threshold-3; State-2: This state indicates that the performance Value is equal to or below Threshold-3, and above Threshold-2; State-3 : This state indicates that the performance Value is equal to or below Threshold-2, and above Threshold-1; and State-4: This state indicates that the
  • performance Value is equal to or below Threshold-1.
  • Additional Example 9 may include the medium of Additional Examples 7 and 8 and/or some other Additional Example herein, wherein there are two states - Current State that is initialized to State-0 and Next State.
  • Additional Example 10 may include the medium of Additional Examples 7, 8, 9 and/or some other Additional Example herein, wherein when a threshold notification is received, based on the performance Value: a next state is chosen based on the state table; a state transition from the current state to the next state (e.g., State-0 -> State-4, State-3 -> State-3, State-4 -> State-1); an action is associated with each state transition; and the current state is updated by the next state.
  • a threshold notification is received, based on the performance Value: a next state is chosen based on the state table; a state transition from the current state to the next state (e.g., State-0 -> State-4, State-3 -> State-3, State-4 -> State-1); an action is associated with each state transition; and the current state is updated by the next state.
  • Additional Example 11 may include the medium of Additional Examples 7, 8, 9, or 10 and/or some other Additional Example herein, wherein which state table will be used will be determined by crossingDirection (i.e., downward, upward).
  • Additional Example 12 may include the medium of Additional Example 10 and/or some other Additional Example herein, wherein there are 4 actions that are defined as the following: Act-1 : no need to send alarm notification; Act-2: send a notification
  • Act-3 send a notification notifyChangedAlarm, if supported; otherwise, send a notification notifyClearedAlarm, and then notification notifyNew Alarm; and Act-4: send a notification notifyClearedAlarm.
  • Additional Example 13 may include the medium of Additional Examples 10, 11, or 12 and/or some other Additional Example herein, wherein the state transition diagram is shown in FIG. 3.
  • Additional Example 14 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of Additional Examples 1- 13, or any other method or process described herein.
  • Additional Example 15 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 Additional Examples 1-13, or any other method or process described herein.
  • Additional Example 16 may include an apparatus comprising logic, modules, and/or circuitry to perform one or more elements of a method described in or related to any of
  • Additional Example 17 may include a method, technique, or process as described in or related to any of Additional Examples 1-13, or portions or parts thereof.
  • Additional Example 18 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 Additional Examples 1-13, or portions thereof.
  • Additional Example 19 may include a method of communicating in a wireless network as shown and described herein.
  • Additional Example 20 may include a system for providing wireless
  • Additional Example 21 may include a device for providing wireless
  • a performance alarm notification procedure for F performance measurements related to VR is used.
  • the procedure describes how EM can generate a performance alarm when threshold crossing notifications are received from VNFM. It is assumed that EM has subscribed to receive the threshold crossing notification from VNFM:
  • VNFM sends a ThresholdCrossedNotification with the following parameters to EM to indicate the threshold that has been crossed:
  • a thresholdld identifies the threshold which has been crossed.
  • a crossingDirection indicates whether the threshold was crossed in upward or downward direction.
  • An objectlnstanceld identifies the VNF or VNFC instance for which the threshold has been crossed.
  • a performanceMetric indicates the performance metric associated with the threshold.
  • a performance Value indicates the value of the metric that resulted in threshold crossing.
  • the EM maps the performance Value to the performance measurements for 3GPP NF related to VR, and determines whether or which alarm notification (i.e., notifyNew Alarm, notifyChangedAlarm or notifyClearedAlarm for the measurements that should be sent to NM, based on the ThresholdMonitor created by NM. Note that how the EM is to perform mapping depends on the definition/specification of "performance measurements for 3GPP NF related to VR" and of performanceMetric. If an alarm needs to be generated, the EM saves the performance alarm to the AlarmList. If the performance alarm is a new alarm, then EM sends a notifyNew Alarm notification to NM.
  • alarm notification i.e., notifyNew Alarm, notifyChangedAlarm or notifyClearedAlarm
  • EM sends to NM either a notifyChangedAlarm notification, or notifyClearedAlarm follow by a notifyNew Alarm notifications if notifyChangedAlarm is not supported. If the performance alarm is a cleared alarm, then EM sends a notifyClearedAlarm notification to NM.
  • Embodiments and implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instructions to be executed by a computer system.
  • a computer system may include one or more general- purpose or special-purpose computers (or other electronic devices).
  • the computer system may include hardware components that include specific logic for performing the operations or may include a combination of hardware, software, and/or firmware.
  • Suitable networks for configuration and/or use as described herein include one or more local area networks, wide area networks, metropolitan area networks, and/or Internet or IP networks, such as the World Wide Web, a private Internet, a secure Internet, a value-added network, a virtual private network, an extranet, an intranet, or even stand-alone machines which communicate with other machines by physical transport of media.
  • a suitable network may be formed from parts or entireties of two or more other networks, including networks using disparate hardware and network communication technologies.
  • One suitable network includes a server and one or more clients; other suitable networks may contain other combinations of servers, clients, and/or peer-to-peer nodes, and a given computer system may function both as a client and as a server.
  • Each network includes at least two computers or computer systems, such as the server and/or clients.
  • a computer system may include a workstation, laptop computer, disconnectable mobile computer, server, mainframe, cluster, so-called “network computer” or "thin client,” tablet, smart phone, personal digital assistant or other hand-held computing device, "smart” consumer electronics device or appliance, medical device, or a combination thereof.
  • Suitable networks may include communications or networking software, such as the software available from Novell®, Microsoft®, and other vendors, and may operate using TCP/IP, SPX, IPX, and other protocols over twisted pair, coaxial, or optical fiber cables, telephone lines, radio waves, satellites, microwave relays, modulated AC power lines, physical media transfer, and/or other data transmission "wires" known to those of skill in the art.
  • the network may encompass smaller networks and/or be connectable to other networks through a gateway or similar mechanism.
  • Various techniques, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, CD- ROMs, hard drives, magnetic or optical cards, solid-state memory devices, a nontransitory computer-readable storage medium, or any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the various techniques.
  • the computing device may include a processor, a storage medium readable by the processor (including volatile and nonvolatile memory and/or storage elements), at least one input device, and at least one output device.
  • the volatile and nonvolatile memory and/or storage elements may be a RAM, an EPROM, a flash drive, an optical drive, a magnetic hard drive, or other medium for storing electronic data.
  • the e B (or other base station) and UE (or other mobile station) may also include a transceiver component, a counter component, a processing component, and/or a clock component or timer component.
  • One or more programs that may implement or utilize the various techniques described herein may use an application programming interface (API), reusable controls, and the like. Such programs may be implemented in a high-level procedural or an object-oriented programming language to communicate with a computer system. However, the program(s) may be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language, and combined with hardware implementations.
  • Each computer system includes one or more processors and/or memory; computer systems may also include various input devices and/or output devices.
  • the processor may include a general purpose device, such as an Intel®, AMD®, or other "off-the-shelf microprocessor.
  • the processor may include a special purpose processing device, such as ASIC, SoC, SiP, FPGA, PAL, PLA, FPLA, PLD, or other customized or programmable device.
  • the memory may include static RAM, dynamic RAM, flash memory, one or more flip-flops, ROM, CD-ROM, DVD, disk, tape, or magnetic, optical, or other computer storage medium.
  • the input device(s) may include a keyboard, mouse, touch screen, light pen, tablet, microphone, sensor, or other hardware with accompanying firmware and/or software.
  • the output device(s) may include a monitor or other display, printer, speech or text synthesizer, switch, signal line, or other hardware with accompanying firmware and/or software.
  • a component may be implemented as a hardware circuit comprising custom very large scale integration (VLSI) circuits or gate arrays, or off-the-shelf semiconductors such as logic chips, transistors, or other discrete components.
  • VLSI very large scale integration
  • a component may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like.
  • Components may also be implemented in software for execution by various types of processors.
  • An identified component of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, a procedure, or a function. Nevertheless, the executables of an identified component need not be physically located together, but may comprise disparate instructions stored in different locations that, when joined logically together, comprise the component and achieve the stated purpose for the component.
  • a component of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices.
  • operational data may be identified and illustrated herein within components, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network.
  • the components may be passive or active, including agents operable to perform desired functions.
  • a software module or component may include any type of computer instruction or computer-executable code located within a memory device.
  • a software module may, for instance, include one or more physical or logical blocks of computer instructions, which may be organized as a routine, program, object, component, data structure, etc., that perform one or more tasks or implement particular data types. It is appreciated that a software module may be implemented in hardware and/or firmware instead of or in addition to software.
  • One or more of the functional modules described herein may be separated into sub-modules and/or combined into a single or smaller number of modules.
  • a particular software module may include disparate instructions stored in different locations of a memory device, different memory devices, or different computers, which together implement the described functionality of the module.
  • a module may include a single instruction or many instructions, and may be distributed over several different code segments, among different programs, and across several memory devices.
  • Some embodiments may be practiced in a distributed computing environment where tasks are performed by a remote processing device linked through a communications network.
  • software modules may be located in local and/or remote memory storage devices.
  • data being tied or rendered together in a database record may be resident in the same memory device, or across several memory devices, and may be linked together in fields of a record in a database across a network.
  • parameters/attributes/aspects/etc. of one embodiment can be used in another embodiment.
  • the parameters/attributes/aspects /etc. are merely described in one or more embodiments for clarity, and it is recognized that the parameters/attributes/aspects /etc. can be combined with or substituted for

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Mobile Radio Communication Systems (AREA)
PCT/US2017/068580 2017-01-06 2017-12-27 Systems, methods and devices for alarm notification in a network function virtualization infrastructure WO2018128894A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
DE112017005643.8T DE112017005643T5 (de) 2017-01-06 2017-12-27 Systeme, verfahren und einrichtungen zur alarmbenachrichtigung in einer netzfunktionsvirtualisierungsinfrastruktur

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201762443253P 2017-01-06 2017-01-06
US62/443,253 2017-01-06

Publications (1)

Publication Number Publication Date
WO2018128894A1 true WO2018128894A1 (en) 2018-07-12

Family

ID=61022441

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/068580 WO2018128894A1 (en) 2017-01-06 2017-12-27 Systems, methods and devices for alarm notification in a network function virtualization infrastructure

Country Status (2)

Country Link
DE (1) DE112017005643T5 (de)
WO (1) WO2018128894A1 (de)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020025009A1 (en) * 2018-08-03 2020-02-06 Huawei Technologies Co., Ltd. Methods and functions of network performance monitoring and service assurance
WO2020140041A1 (en) * 2018-12-27 2020-07-02 Apple Inc. Method and system for threshold monitoring
WO2020167664A1 (en) * 2019-02-12 2020-08-20 Apple Inc. Generation of a threshold monitoring service for a network function to monitor a performance measurement based on a threshold thus defined

Non-Patent Citations (7)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Performance Management (PM) for mobile networks that include virtualized network functions; Procedures (Release 14)", 3GPP STANDARD; 3GPP TS 28.521, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG5, no. V0.4.0, 30 January 2017 (2017-01-30), pages 1 - 13, XP051230663 *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Performance Management (PM) for mobile networks that include virtualized network functions; Procedures (Release 14)", 8 August 2016 (2016-08-08), XP051139674, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG5_TM/TSGS5_108/Docs/> [retrieved on 20160808] *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Performance Management (PM) for mobile networks that include virtualized network functions; Requirements (Release 14)", 30 November 2016 (2016-11-30), XP051200976, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG5_TM/TSGS5_110/Docs/> [retrieved on 20161130] *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Performance Management (PM) Integration Reference Point (IRP): Information Service (IS) (Release 14)", 3GPP STANDARD ; TECHNICAL SPECIFICATION ; 3GPP TS 32.412, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG5, no. V14.0.0, 20 December 2016 (2016-12-20), pages 1 - 68, XP051295518 *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Performance Management (PM); Concept and requirements (Release 13)", 3GPP STANDARD; 3GPP TS 32.401, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG5, no. V13.1.0, 24 June 2016 (2016-06-24), pages 1 - 29, XP051123885 *
"Network Functions Virtualisation (NFV); Management and Orchestration; Ve-Vnfm reference point - Interface and Information Model Specification", vol. NFV IFA, no. V2.1.1, 17 October 2016 (2016-10-17), pages 1 - 83, XP014279834, Retrieved from the Internet <URL:http://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/008/02.01.01_60/gs_NFV-IFA008v020101p.pdf> [retrieved on 20161017] *
INTEL: "pCR TS 28.521 add performance alarm notification procedure for NF perofmrance measurements related to VR", vol. SA WG5, no. Porto; 20170116 - 20170120, 6 January 2017 (2017-01-06), XP051205876, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG5_TM/TSGS5_111/Docs/> [retrieved on 20170106] *

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020025009A1 (en) * 2018-08-03 2020-02-06 Huawei Technologies Co., Ltd. Methods and functions of network performance monitoring and service assurance
US10892958B2 (en) 2018-08-03 2021-01-12 Huawei Technologies Co., Ltd. Methods and functions of network performance monitoring and service assurance
CN112514344A (zh) * 2018-08-03 2021-03-16 华为技术有限公司 网络性能监控和服务保障的方法和功能
CN112514344B (zh) * 2018-08-03 2022-05-10 华为技术有限公司 网络性能监控和服务保障的方法和功能
WO2020140041A1 (en) * 2018-12-27 2020-07-02 Apple Inc. Method and system for threshold monitoring
CN113228563A (zh) * 2018-12-27 2021-08-06 苹果公司 用于阈值监测的方法和系统
US20220086669A1 (en) * 2018-12-27 2022-03-17 Apple Inc. Method and system for threshold monitoring
CN113228563B (zh) * 2018-12-27 2024-04-05 苹果公司 用于阈值监测的方法和系统
WO2020167664A1 (en) * 2019-02-12 2020-08-20 Apple Inc. Generation of a threshold monitoring service for a network function to monitor a performance measurement based on a threshold thus defined

Also Published As

Publication number Publication date
DE112017005643T5 (de) 2019-08-22

Similar Documents

Publication Publication Date Title
US11019538B2 (en) Systems, methods and devices for legacy system fallback in a cellular communications system
EP3482602B1 (de) Systeme, verfahren und vorrichtungen zur trennung einer steuerungsbenutzerebene für 5g-funkzugangsnetzwerke
US11122453B2 (en) Systems, methods and devices for measurement configuration by a secondary node in EN-DC
US10833957B2 (en) Managing physical network function instances in a network service instance
US10749587B2 (en) Systems, methods and devices for using S-measure with new radio
US11792672B2 (en) Measurement job creation and performance data reporting for advanced networks including network slicing
US11018748B2 (en) Systems and methods for L1-RSRP measurement accuracy for beam detection
US11063844B2 (en) Systems, methods and devices for virtual resource metric management
EP3616431A1 (de) Zentralisierte einheit und verteilte einheitsverbindung in einem virtualisierten funkzugangsnetzwerk
US11265884B2 (en) Systems, methods and devices for uplink bearer and access category mapping
WO2018063998A1 (en) Systems, methods and devices for a mac-phy split interface
US11812414B2 (en) Interruption and delay for V2X sidelink carrier aggregation
WO2018125795A1 (en) Systems, methods and devices for congestion control for transport of user data via a control plane
WO2018118788A1 (en) Reporting supported cellular capability combinations of a mobile user device
WO2018128894A1 (en) Systems, methods and devices for alarm notification in a network function virtualization infrastructure
WO2018063997A1 (en) Systems, methods and devices for selecting a measurement bandwidth
WO2018106604A1 (en) Systems, methods and devices for virtual network function virtual processor usage reporting in cellular networks
WO2018102098A1 (en) Systems, methods and devices for managing harq buffer status
WO2018085029A1 (en) Srs switching to a target tdd-cc in a carrier aggegation based wireless communications system

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: 17833067

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17833067

Country of ref document: EP

Kind code of ref document: A1