WO2022123532A1 - Analyse cellulaire basée sur un protocole en temps réel - Google Patents

Analyse cellulaire basée sur un protocole en temps réel Download PDF

Info

Publication number
WO2022123532A1
WO2022123532A1 PCT/IB2021/061588 IB2021061588W WO2022123532A1 WO 2022123532 A1 WO2022123532 A1 WO 2022123532A1 IB 2021061588 W IB2021061588 W IB 2021061588W WO 2022123532 A1 WO2022123532 A1 WO 2022123532A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
type
traffic
data collection
user plane
Prior art date
Application number
PCT/IB2021/061588
Other languages
English (en)
Inventor
Attila BÁDER
László HÉVIZI
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2022123532A1 publication Critical patent/WO2022123532A1/fr

Links

Classifications

    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2416—Real-time traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2483—Traffic characterised by specific attributes, e.g. priority or QoS involving identification of individual flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0231—Traffic management, e.g. flow control or congestion control based on communication conditions

Definitions

  • Embodiments of the present disclosure are directed to wireless communications and, more particularly, to Real Time Protocol (RTP)-based cell analysis.
  • RTP Real Time Protocol
  • Network analytics is an integral part of the network management of mobile telecommunications systems. Data is collected from radio access network (RAN) and core network (CN) nodes as well as from user terminals. A large variety of key performance indicators (KPIs) describing all aspects of network operation are computed and evaluated in real time to maintain the specified service quality in the networks.
  • KPIs key performance indicators
  • the user plane quality metrics are usually obtained from the core network at the user plane function (UPF), either by the built-in network function or by using user plane traffic probes.
  • the UPF transports a wide variety of service types, which have different forwarding requirements and traffic characteristics.
  • the majority of traffic is related to mobile broadband (MBB) traffic, which includes many services provided by over the top (OTT) service providers, such as social media, video conferencing, etc. or any other internet services such as web browsing and file download.
  • MBB mobile broadband
  • OTT over the top
  • NM network management
  • EOA Ericsson Expert Analytics
  • Service quality metrics are either obtained from external sources (from service providers) or estimated from the QoS metrics computed by user plane probes. The quality metrics, however, are available for a limited set of traffic and service types. These types of solutions are suitable for session-based troubleshooting and analysis.
  • Event-based subscriber analytics or customer experience management are also used in service operation centers to monitor the quality of a wide variety of services at the network level, as well as to monitor the customer experience per individual, at subscriber level. These tools are widely used in customer care and other business scenarios.
  • Event-based analytics requires real-time collection and correlation of characteristic node and protocol events from different radio and core nodes. It requires probing the signaling interfaces (IFs) and sampling the user-plane traffic as well. In addition to the data collection and correlation functions, the system requires a platform with an advanced database, rule engine and big data analytics.
  • 5G fifth generation
  • UEs user equipment
  • MBB traffic at core network sites is in the order of several 100 Gbps.
  • User plane probes and probe functions require a large amount of hardware resources, legacy servers, and/or processing and memory capacities in virtual networks, such that it is basically impossible to parse and determine service quality for each and every user-plane data flow.
  • a further problem is that an increasing amount of the MBB traffic is encrypted, which makes it difficult to determine the service quality metrics at the user plane probes.
  • Service quality metrics could be obtained from the service provider, which could measure it at the end terminals. However, it would require more collaboration and standard interfaces between network and service providers, which is not viable in practice today. Drive tests to check service quality and radio quality in certain part of the network is an expensive and time-consuming method and can cover only limited part of the network.
  • an intelligent filtering module may control the event load at the network functions (NFs) based on statistical considerations to achieve target precision. It may determine the volume of traffic needed for the different use cases and it reduces the number of events to the minimum but still sufficient level. The idea is that it replaces a heavy traffic type with a much lighter traffic type to detect service quality degradations in the network.
  • NFs network functions
  • particular embodiments include a network analytics system that focuses and collects data primarily for the problematic flows and network nodes. For example, particular embodiments set the lifespan of collected data so that low-level, detailed data with minor information content is identified and discarded at an early stage of processing and lower aggregation levels.
  • Particular embodiments use voice over long term evolution (VoLTE)- and/or voice over 5G (Vo5G) related KPIs as real-time indicators on the general state of service quality because VoLTE and Vo5G is a commonly present, low-bitrate traffic type, which is especially sensitive to network troubles and overload, whereas it is strictly monitored in all circumstances.
  • VoIP voice over long term evolution
  • Vo5G voice over 5G
  • resource-demanding data processing and aggregation is focused to network segments, which are raised to an alert level according to the VoLTE and Vo5G KPIs.
  • the real-time protocol (RTP) and real-time transport control protocol (RTCP) packets of the VoLTE and Vo5G traffic are captured at a user plane function (UPF) for every flow.
  • the amount of user plane data is negligible compared to MBB traffic.
  • RTCP the delay, loss and jitter of both the uplink and downlink data flows are obtained.
  • the frequency of obtaining the information depends on the periodic time of the RTCP messages, which is on the order of 5-10 seconds.
  • additional RTP metrics such as out of sequence packets, the forward or backward jump or sequence restarts may also be obtained.
  • Radio measurement data in the problematic cells may be used for identifying the type of radio problem, e.g. coverage, interference, handover, etc.
  • particular embodiments control data sampling, collection and processing of network monitoring data, such that data with high-relevance to network performance are collected and processed. Meanwhile, data with minor significance to service performance are not collected or dropped at an early aggregation stage.
  • Particular embodiments operate on network-node and data-collection filters in the data collection and processing chains based on real-time computed VoLTE and Vo5G KPIs.
  • VoLTE or Vo5G KPIs Upon cumulative occurrences of deteriorating VoLTE or Vo5G KPIs in mobile network segments, the otherwise costly data collection, processing and aggregation are turned on for the involved network components, such that network monitoring is extended or intensified to the involved network nodes and to UE flows served via these nodes.
  • the enriched information is used to compute service-level KPIs to analyze the extent and to explore the root causes of potential service degradations.
  • a method performed by a network management system comprises: monitoring user plane metrics for a plurality of voice flows (e.g., RTP, RTCP) in a network; determining periodically a performance indicator for each of the plurality of voice flows; based on the performance indicator, classifying each of the plurality of voice flows as good or bad; determining one or more network nodes associated with each of the plurality of voice flows; and for each of the plurality of voice flows, transmitting a good or bad event to each of the one or more network nodes associated with the voice flow.
  • a plurality of voice flows e.g., RTP, RTCP
  • a method performed by a network management system comprises: receiving a user plane performance indication for a first type of network traffic (e.g., RTP, RTCP) from a network node; and based on the user plane performance indication for the first type of network traffic, adjusting a data collection level for a second type of network traffic (e.g., MBB).
  • a first type of network traffic e.g., RTP, RTCP
  • MBB second type of network traffic
  • adjusting the data collection level for the second type of network traffic comprises activating data collection for the second type of traffic.
  • Activating data collection for the second type of traffic may comprise activating one or more of control plane data collection and radio metric data collection for network nodes associated with the first type of network traffic.
  • adjusting the data collection level for the second type of network traffic comprises deactivating data collection for the second type of traffic.
  • Deactivating data collection for the second type of traffic may comprise deactivating one or more of control plane data collection and radio metric data collection for network nodes associated with the first type of network traffic.
  • adjusting the data collection level for the second type of network traffic comprises: determining one or more subscriber sessions associated with the user plane performance indication for the first type of network traffic from a network node; determining one or more network nodes associated with the one or more subscriber sessions; and forwarding the performance indication to the one or more network nodes.
  • the network management system receives the user plane performance indication from a UPF.
  • a network management system comprises processing circuitry operable to perform any of the network management system methods described above.
  • a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the network management system described above.
  • Certain embodiments may provide one or more of the following technical advantages. For example, particular embodiments reduce or eliminate the need to monitor and parse the user plane data of the heavy MBB traffic.
  • the volume of VoLTE and Vo5G traffic is relatively low compared to the rest of the traffic, namely the 20 kbps voice flows compared to 1-10 Mbps of MBB traffic flows.
  • Particular embodiments are able to parse and analyze all of the VoLTE and Vo5G traffic at the UPF with relatively low hardware resources.
  • the low rate VoLTE and Vo5G traffic load itself does not cause congestion or service quality degradation in advanced mobile networks.
  • VoLTE and Vo5G is transported over UDP/RTP, which is an unreliable data transport because there is no retransmission of packets if they are lost.
  • VoLTE and Vo5G packets are sent periodically with sequence numbers, so it is suitable to sensitively detect any packet level delivery issue.
  • particular embodiments detect any quality issues of MBB traffic sharing the same forwarding path and network cell.
  • MBB traffic is usually more tolerable to packet level issues because they generally include error correction, acknowledgement and retransmission functions.
  • Uplink metrics are especially useful for detecting and predicting possible quality issues because the UE data transmission in uplink direction is power limited in fourth generation (4G) and 5G networks, and the radio connections in uplink direction are more sensitive to troubles than in downlink direction. Therefore, radio issues appear with higher probability and earlier in uplink than in downlink direction.
  • FIGURE 1 is a network diagram illustrating a network architecture including an analytics system
  • FIGURE 2 is graph illustrating mobile broadband (MBB) key performance indicators (KPI) versus voice KPI;
  • FIGURE 3 is a flow diagram illustrating the data activation function (DAF) that enables the adaptive adjustment of data collection and filtering;
  • DAF data activation function
  • FIGURE 4 illustrates an example node sorter
  • FIGURE 5 is a block diagram illustrating an example wireless network
  • FIGURE 6 illustrates an example user equipment, according to certain embodiments.
  • FIGURE 7 is flowchart illustrating an example method in a network management system, according to certain embodiments.
  • FIGURE 8 is flowchart illustrating another example method in a network management system, according to certain embodiments.
  • FIGURE 9 illustrates a schematic block diagram of a wireless device and a network node in a wireless network, according to certain embodiments.
  • FIGURE 10 illustrates an example virtualization environment, according to certain embodiments.
  • FIGURE 11 illustrates an example telecommunication network connected via an intermediate network to a host computer, according to certain embodiments
  • FIGURE 12 illustrates an example host computer communicating via a base station with a user equipment over a partially wireless connection, according to certain embodiments
  • FIGURE 13 is a flowchart illustrating a method implemented, according to certain embodiments.
  • FIGURE 14 is a flowchart illustrating a method implemented in a communication system, according to certain embodiments
  • FIGURE 15 is a flowchart illustrating a method implemented in a communication system, according to certain embodiments.
  • FIGURE 16 is a flowchart illustrating a method implemented in a communication system, according to certain embodiments.
  • particular embodiments include a network analytics system that focuses and collects data primarily for the problematic flows and network nodes. For example, particular embodiments set the lifespan of collected data so that low-level, detailed data with minor information content is identified and discarded at an early stage of processing and lower aggregation levels. Particular embodiments use voice over long term evolution (VoLTE)- and/or voice over 5G (Vo5G) related KPIs as real-time indicators on the general state of service quality because VoLTE and Vo5G is a commonly present, low-bitrate traffic type, which is especially sensitive to network troubles and overload, whereas it is strictly monitored in all circumstances.
  • VoIP voice over long term evolution
  • Vo5G voice over 5G
  • VoLTE and Vo5G traffic are used as an active probe of the radio network.
  • VoLTE and Vo5G are frequently and widely used services, which provide a good test data coverage for the network.
  • the bandwidth of a call is relatively low, in the order of 20 kbps, therefore, the VoLTE and Vo5G traffic itself does not cause congestion in the radio cells and in other part of the network.
  • VoLTE and Vo5G are transported in an unreliable real time protocol User Datagram Protocol (UDP)/Real Time Protocol (RTP), which does not include any retransmission or error correction. Therefore, it is suitable for detecting any packet level delivery or transmission problem.
  • VoLTE and Vo5G RTP packets are sent frequently and periodically. The voice packets are sent every 20 ms and silence packets are sent every 160 ms with sequence number.
  • FIGURE 1 is a network diagram illustrating a network architecture including an analytics system.
  • the analytics system includes the data activation function (DAF) where the functionality of several embodiments may be implemented.
  • DAF data activation function
  • RTCP Real-time Transport Control Protocol
  • UPF user plane function
  • TCP Transport Control Protocol
  • UDP User Plane Function
  • RTP and RTCP data collection at UPF may be active for all flows and all the time.
  • Data collection for other traffic types at UPF and at other network functions (NFs) (core and radio) may be activated by the DAF.
  • NFs network functions
  • RTCP metrics may include packet delay, loss, and jitter.
  • the reporting frequency is typically 5-10s.
  • RTCP may not be used/sent by each device.
  • RTCP XR contains more detailed metrics, but this extension is not generally used in practice.
  • RTP metrics may be obtained at the UPF traffic probe or software probe every 5-10 seconds. Uplink RTP metrics are easily available for each RTP flow, because their capturing point is in the network side, so there is no need to collect information at the terminal.
  • the metrics may include loss, jitter, sequence jump forward, sequence jump backward, sequence restarts, and number of out of sequence packets.
  • MBB flow performance metrics may include throughput, video quality (MOS), and web page access and download time.
  • Packet level metrics may include TCP and QUIC packet loss and TCP and QUIC round trip time. KPIs may aggregated for the reporting time period (5-10 seconds).
  • Comparing MBB and RTP packet level metrics illustrates the correlation between MBB and voice service KPIs.
  • Collecting various cell-aggregated KPIs from an operational LTE network illustrates the correlation. While the computation of the MBB KPIs is resource demanding, it is easier for voice KPIs. Because voice KPIs are primarily important to judge network performance, these KPIs are continuously monitored.
  • Table 1 MBB and voice KPIs for cells with poor performance
  • Table 1 lists various MBB and voice KPIs.
  • the original user flow-level KPIs are aggregated for the shown cells over a time period of 1 hour.
  • the cells are ranked based on MBB service quality and the worst 5% of them are listed. There is a small fraction of cells where service quality is much worse than the average and so network optimization should focus on these, where the radio conditions suspected are not ideal.
  • VoLTE Vo5G packet metrics reveals the same underperforming cells. The typical, or average values for all cells are also given in the last row for reference.
  • Another example aggregates daily KPIs for a number of cells and scatter plots an MBB KPI versus a voice KPI. The relationship between the two KPIs can be seen in FIGURE 2.
  • FIGURE 2 is graph illustrating MBB KPI versus voice KPI.
  • the MBB KPI which is the downlink throughput in this case, depends on various circumstances, so the plot looks noisy, yet the inverse proportional trend among the two KPIs can be recognized.
  • Each point in FIGURE 2 belongs to a long term evolution (LTE) cell in a live network.
  • the data includes the cells of a region without any prefiltering.
  • the coordinate values of the points are service KPIs aggregated over a day.
  • the graph shows the relationship of a voice KPI on the horizontal and an MBB KPI in the vertical axis.
  • the increasing voice packet delay in downlink indicates deteriorating voice quality, which typically coincides with deteriorating MBB throughput.
  • FIGURE 3 is a flow diagram illustrating the DAF that enables the adaptive adjustment of data collection and filtering.
  • the illustrated DAF continuously monitors all voice flows in the network and periodically computes voice KPIs for each flow.
  • the KPI evaluator block classifies each voice flow either as “good” or “bad” by judging a single or a combination of voice flow KPIs.
  • the network node sorter function in the apparatus identifies all the network nodes (cells, links, gateways, etc.) that have anything to do with the voice flow.
  • the node sorter function sends a “good” or “bad” event trigger to the corresponding node KPI evaluator function, which is paired with the node.
  • the KPI evaluator function keeps a history of the latest triggers both the “good” and “bad” ones and sets the node data filter based on the evaluation of the recent event history.
  • the node data filter can turn on and off the collection of certain MBB KPI computation-related data and from that point on, the computation intensive KPI computation starts for each data flow running through the involved node(s).
  • FIGURE 4 illustrates an example node sorter.
  • the active voice connections are continuously monitored in the system.
  • the analytics system semi-periodically computes a set of KPIs for each voice flow, and when such a set of KPIs becomes available, it is classified as good or bad flow, then the network node sorter is notified.
  • the role of network node sorter is to look up the nodes involved in the transfer chain of the voice flow and trigger all those node KPI evaluators with the “good” or “bad” flow event.
  • Some embodiments add the affected subscribers to the white list.
  • White list filtering is usually supported by each network function. It results in consistent network-wide event generation because each node generates events for the same sessions (for subscribers on the white list).
  • Another option relies on node filtering at core NFs. In this case the full event generation may be turned on/off for the selected nodes. Some embodiments support filtering at UPF, because the UPF is the heaviest data source. If other NFs do not support the required filtering, they generate events for all sessions and the uncorrelated data are dropped at the correlator. Because the traffic and generated events at these NFs are much less than at UPF, this does not cause excessive load at the NF or at the analytics system.
  • MBB traffic volume at gateway sites today is on the order of several 100 Gbit/s.
  • Passive user plane network probes require about 100 servers per gateway site for capturing user plane traffic and to generate basic packet level metrics, traffic classification and service quality information, if it is possible at all due to encryption.
  • the VoLTE RTP user plane traffic is on the order of a few 100 Mbit/s per site and together with the traffic classification/filtering, obtaining the RTP metrics require less than 10 servers per sites.
  • Radio data is the other data source, which is quite demanding, not because of the volume but more from processing point of view. Especially when periodic radio measurements and reporting are active, generating radio report every few seconds for active UEs. Replacing radio data or at least reducing the amount of radio data, therefore can save significant processing capacity both at the radio network and OSS sides.
  • FIGURE 5 illustrates an example wireless network, according to certain embodiments.
  • the wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system.
  • the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures.
  • wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • WLAN wireless local area network
  • WiMax Worldwide Interoperability for Microwave Access
  • Bluetooth Z-Wave and/or ZigBee standards.
  • Network 106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • PSTNs public switched telephone networks
  • WANs wide-area networks
  • LANs local area networks
  • WLANs wireless local area networks
  • wired networks wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • Network node 160 and WD 110 comprise various components described in more detail below. These components work together to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network.
  • the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).
  • APs access points
  • BSs base stations
  • Node Bs evolved Node Bs
  • gNBs NR NodeBs
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs).
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
  • DAS distributed antenna system
  • network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), MDTs, and/or network management nodes, such as the network management system illustrated in FIGURE 1.
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • MCEs multi-cell/multicast coordination entities
  • core network nodes e.g., MSCs, MMEs
  • O&M nodes e.g., OSS nodes
  • SON nodes e.g., positioning nodes (e.g.
  • a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.
  • network node 160 includes processing circuitry 170, device readable medium 180, interface 190, auxiliary equipment 184, power source 186, power circuitry 187, and antenna 162.
  • network node 160 illustrated in the example wireless network of FIGURE 5 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components.
  • a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein.
  • components of network node 160 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 180 may comprise multiple separate hard drives as well as multiple RAM modules).
  • network node 160 may be composed of multiple physically separate components (e.g., aNodeB component and aRNC component, or aBTS component and aBSC component, etc.), which may each have their own respective components.
  • network node 160 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeB’s.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • network node 160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium 180 for the different RATs) and some components may be reused (e.g., the same antenna 162 may be shared by the RATs).
  • Network node 160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 160.
  • Processing circuitry 170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 170 may include processing information obtained by processing circuitry 170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing information obtained by processing circuitry 170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • Processing circuitry 170 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 160 components, such as device readable medium 180, network node 160 functionality.
  • processing circuitry 170 may execute instructions stored in device readable medium 180 or in memory within processing circuitry 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein.
  • processing circuitry 170 may include a system on a chip (SOC).
  • processing circuitry 170 may include one or more of radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174.
  • radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units.
  • part or all of RF transceiver circuitry 172 and baseband processing circuitry 174 may be on the same chip or set of chips, boards, or units
  • processing circuitry 170 executing instructions stored on device readable medium 180 or memory within processing circuitry 170.
  • some or all of the functionality may be provided by processing circuitry 170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner.
  • processing circuitry 170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 170 alone or to other components of network node 160 but are enjoyed by network node 160 as a whole, and/or by end users and the wireless network generally.
  • Device readable medium 180 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 170.
  • volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non
  • Device readable medium 180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 170 and, utilized by network node 160.
  • Device readable medium 180 may be used to store any calculations made by processing circuitry 170 and/or any data received via interface 190.
  • processing circuitry 170 and device readable medium 180 may be considered to be integrated.
  • Interface 190 is used in the wired or wireless communication of signaling and/or data between network node 160, network 106, and/or WDs 110. As illustrated, interface 190 comprises port(s)/terminal(s) 194 to send and receive data, for example to and from network 106 over a wired connection. Interface 190 also includes radio front end circuitry 192 that may be coupled to, or in certain embodiments a part of, antenna 162.
  • Radio front end circuitry 192 comprises filters 198 and amplifiers 196.
  • Radio front end circuitry 192 may be connected to antenna 162 and processing circuitry 170. Radio front end circuitry may be configured to condition signals communicated between antenna 162 and processing circuitry 170.
  • Radio front end circuitry 192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 198 and/or amplifiers 196. The radio signal may then be transmitted via antenna 162.
  • antenna 162 may collect radio signals which are then converted into digital data by radio front end circuitry 192.
  • the digital data may be passed to processing circuitry 170.
  • the interface may comprise different components and/or different combinations of components.
  • network node 160 may not include separate radio front end circuitry 192, instead, processing circuitry 170 may comprise radio front end circuitry and may be connected to antenna 162 without separate radio front end circuitry 192.
  • processing circuitry 170 may comprise radio front end circuitry and may be connected to antenna 162 without separate radio front end circuitry 192.
  • all or some of RF transceiver circuitry 172 may be considered a part of interface 190.
  • interface 190 may include one or more ports or terminals 194, radio front end circuitry 192, and RF transceiver circuitry 172, as part of a radio unit (not shown), and interface 190 may communicate with baseband processing circuitry 174, which is part of a digital unit (not shown).
  • Antenna 162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 162 may be coupled to radio front end circuitry 192 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 162 may be separate from network node 160 and may be connectable to network node 160 through an interface or port.
  • Antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.
  • Power circuitry 187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 160 with power for performing the functionality described herein. Power circuitry 187 may receive power from power source 186. Power source 186 and/or power circuitry 187 may be configured to provide power to the various components of network node 160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 186 may either be included in, or external to, power circuitry 187 and/or network node 160.
  • network node 160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 187.
  • power source 186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 187. The battery may provide backup power should the external power source fail.
  • Other types of power sources such as photovoltaic devices, may also be used.
  • network node 160 may include additional components beyond those shown in FIGURE 5 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • network node 160 may include user interface equipment to allow input of information into network node 160 and to allow output of information from network node 160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 160.
  • wireless device refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.
  • a WD may be configured to transmit and/or receive information without direct human interaction.
  • a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network.
  • Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE), a vehicle-mounted wireless terminal device, etc.
  • VoIP voice over IP
  • PDA personal digital assistant
  • LOE laptop-embedded equipment
  • LME laptop-mounted equipment
  • CPE wireless customer-premise equipment
  • a WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device.
  • D2D device-to-device
  • a WD may represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another WD and/or a network node.
  • the WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device.
  • M2M machine-to-machine
  • the WD may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard.
  • NB-IoT narrow band internet of things
  • machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.).
  • a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • a WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal.
  • a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.
  • wireless device 110 includes antenna 111, interface 114, processing circuitry 120, device readable medium 130, user interface equipment 132, auxiliary equipment 134, power source 136 and power circuitry 137.
  • WD 110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD 110.
  • Antenna 111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 114. In certain alternative embodiments, antenna 111 may be separate from WD 110 and be connectable to WD 110 through an interface or port. Antenna 111, interface 114, and/or processing circuitry 120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna 111 may be considered an interface.
  • interface 114 comprises radio front end circuitry 112 and antenna 111.
  • Radio front end circuitry 112 comprise one or more filters 118 and amplifiers 116.
  • Radio front end circuitry 112 is connected to antenna 111 and processing circuitry 120 and is configured to condition signals communicated between antenna 111 and processing circuitry 120.
  • Radio front end circuitry 112 may be coupled to or a part of antenna 111.
  • WD 110 may not include separate radio front end circuitry 112; rather, processing circuitry 120 may comprise radio front end circuitry and may be connected to antenna 111.
  • some or all of RF transceiver circuitry 122 may be considered a part of interface 114.
  • Radio front end circuitry 112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 118 and/or amplifiers 116. The radio signal may then be transmitted via antenna 111. Similarly, when receiving data, antenna 111 may collect radio signals which are then converted into digital data by radio front end circuitry 112. The digital data may be passed to processing circuitry 120. In other embodiments, the interface may comprise different components and/or different combinations of components.
  • Processing circuitry 120 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD 110 components, such as device readable medium 130, WD 110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 120 may execute instructions stored in device readable medium 130 or in memory within processing circuitry 120 to provide the functionality disclosed herein.
  • processing circuitry 120 includes one or more of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126.
  • the processing circuitry may comprise different components and/or different combinations of components.
  • processing circuitry 120 of WD 110 may comprise a SOC.
  • RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be on separate chips or sets of chips.
  • part or all of baseband processing circuitry 124 and application processing circuitry 126 may be combined into one chip or set of chips, and RF transceiver circuitry 122 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 122 and baseband processing circuitry 124 may be on the same chip or set of chips, and application processing circuitry 126 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be combined in the same chip or set of chips.
  • RF transceiver circuitry 122 may be a part of interface 114.
  • RF transceiver circuitry 122 may condition RF signals for processing circuitry 120.
  • processing circuitry 120 executing instructions stored on device readable medium 130, which in certain embodiments may be a computer-readable storage medium.
  • processing circuitry 120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner.
  • processing circuitry 120 can be configured to perform the described functionality.
  • the benefits provided by such functionality are not limited to processing circuitry 120 alone or to other components of WD 110, but are enjoyed by WD 110, and/or by end users and the wireless network generally.
  • Processing circuitry 120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 120, may include processing information obtained by processing circuitry 120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing information obtained by processing circuitry 120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • Device readable medium 130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 120.
  • Device readable medium 130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non- transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 120.
  • processing circuitry 120 and device readable medium 130 may be integrated.
  • User interface equipment 132 may provide components that allow for a human user to interact with WD 110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 132 may be operable to produce output to the user and to allow the user to provide input to WD 110. The type of interaction may vary depending on the type of user interface equipment 132 installed in WD 110. For example, if WD 110 is a smart phone, the interaction may be via a touch screen; if WD 110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected).
  • usage e.g., the number of gallons used
  • a speaker that provides an audible alert
  • User interface equipment 132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 132 is configured to allow input of information into WD 110 and is connected to processing circuitry 120 to allow processing circuitry 120 to process the input information. User interface equipment 132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 132 is also configured to allow output of information from WD 110, and to allow processing circuitry 120 to output information from WD 110. User interface equipment 132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 132, WD 110 may communicate with end users and/or the wireless network and allow them to benefit from the functionality described herein.
  • Auxiliary equipment 134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 134 may vary depending on the embodiment and/or scenario.
  • Power source 136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used.
  • WD 110 may further comprise power circuitry 137 for delivering power from power source 136 to the various parts of WD 110 which need power from power source 136 to carry out any functionality described or indicated herein.
  • Power circuitry 137 may in certain embodiments comprise power management circuitry.
  • Power circuitry 137 may additionally or alternatively be operable to receive power from an external power source; in which case WD 110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable.
  • Power circuitry 137 may also in certain embodiments be operable to deliver power from an external power source to power source 136. This may be, for example, for the charging of power source 136. Power circuitry 137 may perform any formatting, converting, or other modification to the power from power source 136 to make the power suitable for the respective components of WD 110 to which power is supplied.
  • a wireless network such as the example wireless network illustrated in FIGURE 5.
  • the wireless network of FIGURE 5 only depicts network 106, network nodes 160 and 160b, and WDs 110, 110b, and 110c.
  • a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device.
  • network node 160 and wireless device (WD) 110 are depicted with additional detail.
  • the wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.
  • FIGURE 6 illustrates an example user equipment, according to certain embodiments.
  • a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • UE 200 may be any UE identified by the 3 rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • UE 200 as illustrated in FIGURE 6, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3 rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards.
  • 3GPP 3 rd Generation Partnership Project
  • UE 200 includes processing circuitry 201 that is operatively coupled to input/output interface 205, radio frequency (RF) interface 209, network connection interface 211, memory 215 including random access memory (RAM) 217, read-only memory (ROM) 219, and storage medium 221 or the like, communication subsystem 231, power source 213, and/or any other component, or any combination thereof.
  • Storage medium 221 includes operating system 223, application program 225, and data 227. In other embodiments, storage medium 221 may include other similar types of information.
  • Certain UEs may use all the components shown in FIGURE 6, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • processing circuitry 201 may be configured to process computer instructions and data.
  • Processing circuitry 201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above.
  • the processing circuitry 201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.
  • input/output interface 205 may be configured to provide a communication interface to an input device, output device, or input and output device.
  • UE 200 may be configured to use an output device via input/output interface 205.
  • An output device may use the same type of interface port as an input device.
  • a USB port may be used to provide input to and output from UE 200.
  • the output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • UE 200 may be configured to use an input device via input/output interface 205 to allow a user to capture information into UE 200.
  • the input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof.
  • the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
  • RF interface 209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna.
  • Network connection interface 211 may be configured to provide a communication interface to network 243a.
  • Network 243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network 243a may comprise a Wi-Fi network.
  • Network connection interface 211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like.
  • Network connection interface 211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.
  • RAM 217 may be configured to interface via bus 202 to processing circuitry 201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers.
  • ROM 219 may be configured to provide computer instructions or data to processing circuitry 201.
  • ROM 219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory.
  • Storage medium 221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives.
  • storage medium 221 may be configured to include operating system 223, application program 225 such as a web browser application, a widget or gadget engine or another application, and data file 227.
  • Storage medium 221 may store, for use by UE 200, any of a variety of various operating systems or combinations of operating systems.
  • Storage medium 221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external microDIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM external mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • SIM/RUIM removable user identity
  • Storage medium 221 may allow UE 200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 221, which may comprise a device readable medium.
  • processing circuitry 201 may be configured to communicate with network 243b using communication subsystem 231.
  • Network 243a and network 243b may be the same network or networks or different network or networks.
  • Communication subsystem 231 may be configured to include one or more transceivers used to communicate with network 243b.
  • communication subsystem 231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like.
  • RAN radio access network
  • Each transceiver may include transmitter 233 and/or receiver 235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 233 and receiver 235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.
  • the communication functions of communication subsystem 231 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
  • communication subsystem 231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication.
  • Network 243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network 243b may be a cellular network, a Wi-Fi network, and/or a near-field network.
  • Power source 213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 200.
  • communication subsystem 231 may be configured to include any of the components described herein.
  • processing circuitry 201 may be configured to communicate with any of such components over bus 202.
  • any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 201 perform the corresponding functions described herein.
  • the functionality of any of such components may be partitioned between processing circuitry 201 and communication subsystem 231.
  • the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.
  • FIGURE 7 is a flowchart illustrating an example method in a network management system, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 7 may be performed by the network management system described with respect to FIGURES 1 and 3-5.
  • the method may begin at step 712, where the network management system monitors user plane metrics for a plurality of voice flows (e.g., RTP, RTCP) in a network.
  • a plurality of voice flows e.g., RTP, RTCP
  • monitoring the user plane metrics involves lightweight monitoring, the traffic is widely spread in the network, the traffic is sensitive to network problems, occurs in real-time, and has well established KPIs indicating errors.
  • the network management system determines periodically a performance indicator for each of the plurality of voice flows. For example, the network management system may determine that some of the voice flows are experiencing degradation.
  • the network management system classifies each of the plurality of voice flows as good or bad and, at step 718, determines one or more network nodes associated with each of the plurality of voice flows.
  • the network management system transmits a good or bad event to each of the one or more network nodes associated with the voice flow.
  • the network nodes associated with those voice flows may turn on additional data collection to troubleshoot the network.
  • the network nodes may monitor additional traffic (e.g., MBB) and may monitor control plane data and/or radio metrics.
  • the network nodes associated with those voice flows may deactivate additional data collection if the network node had previously activated additional data collection.
  • FIGURE 8 is a flowchart illustrating another example method in a network management system, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 8 may be performed by the network management system described with respect to FIGURES 1 and 3-5.
  • the method may begin at step 812, where the network management system receives a user plane performance indication for a first type of network traffic (e.g., RTP, RTCP) from a network node.
  • a first type of network traffic e.g., RTP, RTCP
  • the first type of traffic is traffic, such as user plane voice traffic, that is relatively lightweight to monitor, yet provides a good indication of network health.
  • the network management system Based on the user plane performance indication for the first type of network traffic, at step 814, the network management system adjusts a data collection level for a second type of network traffic (e.g., MBB). Accordingly, in a normal operating state the network management system is monitoring a minimal amount of traffic. When the minimal amount of traffic indicates a problem, the network management system may then adjust monitoring and collection in the nodes that may be affected by the problem.
  • a second type of network traffic e.g., MBB
  • adjusting the data collection level for the second type of network traffic comprises activating data collection for the second type of traffic.
  • Activating data collection for the second type of traffic may comprise activating one or more of control plane data collection and radio metric data collection for network nodes associated with the first type of network traffic.
  • adjusting the data collection level for the second type of network traffic comprises deactivating data collection for the second type of traffic.
  • Deactivating data collection for the second type of traffic may comprise deactivating one or more of control plane data collection and radio metric data collection for network nodes associated with the first type of network traffic.
  • adjusting the data collection level for the second type of network traffic comprises: determining one or more subscriber sessions associated with the user plane performance indication for the first type of network traffic from a network node; determining one or more network nodes associated with the one or more subscriber sessions; and forwarding the performance indication to the one or more network nodes.
  • the network management system receives the user plane performance indication from a UPF.
  • FIGURE 9 illustrates a schematic block diagram of two apparatuses in a wireless network (for example, the wireless network illustrated in FIGURE 5).
  • the apparatuses include a wireless device and a network node (e.g., wireless device 110 and network node 160 illustrated in FIGURE 5).
  • Apparatuses 1600 and 1700 are operable to carry out the example methods described herein. At least some operations of the methods can be performed by one or more other entities.
  • Virtual apparatuses 1600 and 1700 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the processing circuitry may be used to cause receiving module 1602, monitoring module 1604, transmitting module 1606, and any other suitable units of apparatus 1600 to perform corresponding functions according one or more embodiments of the present disclosure.
  • the processing circuitry described above may be used to cause monitoring module 1702, transmitting module 1704, and any other suitable units of apparatus 1700 to perform corresponding functions according one or more embodiments of the present disclosure.
  • apparatus 1600 includes receiving module 1602 configured to receive performance indications and/or data collection commands according to any of the embodiments and examples described herein.
  • Monitoring module 1604 is configured to monitor network parameters and conditions according to any of the embodiments and examples described herein.
  • Transmitting module 1606 is configured to transmit monitoring results, according to any of the embodiments and examples described herein.
  • apparatus 1700 includes monitoring module 1702 configured to monitor network traffic and radio conditions according to any of the embodiments and examples described herein.
  • Transmitting module 1704 is configured to transmit monitoring results according to any of the embodiments and examples described herein.
  • FIGURE 10 is a schematic block diagram illustrating a virtualization environment 300 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).
  • a node e.g., a virtualized base station or a virtualized radio access node
  • a device e.g., a UE, a wireless device or any other type of communication device
  • some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 300 hosted by one or more of hardware nodes 330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.
  • the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node)
  • the network node may be entirely virtualized.
  • the functions may be implemented by one or more applications 320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Applications 320 are run in virtualization environment 300 which provides hardware 330 comprising processing circuitry 360 and memory 390.
  • Memory 390 contains instructions 395 executable by processing circuitry 360 whereby application 320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
  • Virtualization environment 300 comprises general-purpose or special-purpose network hardware devices 330 comprising a set of one or more processors or processing circuitry 360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • processors or processing circuitry 360 which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • Each hardware device may comprise memory 390-1 which may be non-persistent memory for temporarily storing instructions 395 or software executed by processing circuitry 360.
  • Each hardware device may comprise one or more network interface controllers (NICs) 370, also known as network interface cards, which include physical network interface 380.
  • NICs network interface controllers
  • Each hardware device may also include non-transitory, persistent, machine-readable storage media 390-2 having stored therein software 395 and/or instructions executable by processing circuitry 360.
  • Software 395 may include any type of software including software for instantiating one or more virtualization layers 350 (also referred to as hypervisors), software to execute virtual machines 340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
  • Virtual machines 340 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 350 or hypervisor. Different embodiments of the instance of virtual appliance 320 may be implemented on one or more of virtual machines 340, and the implementations may be made in different ways.
  • processing circuitry 360 executes software 395 to instantiate the hypervisor or virtualization layer 350, which may sometimes be referred to as a virtual machine monitor (VMM).
  • VMM virtual machine monitor
  • Virtualization layer 350 may present a virtual operating platform that appears like networking hardware to virtual machine 340.
  • hardware 330 may be a standalone network node with generic or specific components. Hardware 330 may comprise antenna 3225 and may implement some functions via virtualization. Alternatively, hardware 330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 3100, which, among others, oversees lifecycle management of applications 320.
  • CPE customer premise equipment
  • MANO management and orchestration
  • NFV network function virtualization
  • NFV may be used to consolidate many network equipment types onto industry standard high-volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • virtual machine 340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of virtual machines 340, and that part of hardware 330 that executes that virtual machine be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 340, forms a separate virtual network elements (VNE).
  • VNE virtual network elements
  • VNF Virtual Network Function
  • one or more radio units 3200 that each include one or more transmitters 3220 and one or more receivers 3210 may be coupled to one or more antennas 3225.
  • Radio units 3200 may communicate directly with hardware nodes 330 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • control system 3230 which may alternatively be used for communication between the hardware nodes 330 and radio units 3200.
  • a communication system includes telecommunication network 410, such as a 3 GPP -type cellular network, which comprises access network 411, such as a radio access network, and core network 414.
  • Access network 411 comprises a plurality of base stations 412a, 412b, 412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 413a, 413b, 413c.
  • Each base station 412a, 412b, 412c is connectable to core network 414 over a wired or wireless connection 415.
  • a first UE 491 located in coverage area 413c is configured to wirelessly connect to, or be paged by, the corresponding base station 412c.
  • a second UE 492 in coverage area 413a is wirelessly connectable to the corresponding base station 412a. While a plurality of UEs 491, 492 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 412.
  • Telecommunication network 410 is itself connected to host computer 430, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • Host computer 430 may be under the ownership or control of a service provider or may be operated by the service provider or on behalf of the service provider.
  • Connections 421 and 422 between telecommunication network 410 and host computer 430 may extend directly from core network 414 to host computer 430 or may go via an optional intermediate network 420.
  • Intermediate network 420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 420, if any, may be a backbone network or the Internet; in particular, intermediate network 420 may comprise two or more sub-networks (not shown).
  • the communication system of FIGURE 11 as a whole enables connectivity between the connected UEs 491, 492 and host computer 430.
  • the connectivity may be described as an over-the-top (OTT) connection 450.
  • Host computer 430 and the connected UEs 491, 492 are configured to communicate data and/or signaling via OTT connection 450, using access network 411, core network 414, any intermediate network 420 and possible further infrastructure (not shown) as intermediaries.
  • OTT connection 450 may be transparent in the sense that the participating communication devices through which OTT connection 450 passes are unaware of routing of uplink and downlink communications.
  • base station 412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 430 to be forwarded (e.g., handed over) to a connected UE 491. Similarly, base station 412 need not be aware of the future routing of an outgoing uplink communication originating from the UE 491 towards the host computer 430.
  • FIGURE 12 illustrates an example host computer communicating via a base station with a user equipment over a partially wireless connection, according to certain embodiments.
  • Example implementations, in accordance with an embodiment of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to FIGURE 12.
  • host computer 510 comprises hardware 515 including communication interface 516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 500.
  • Host computer 510 further comprises processing circuitry 518, which may have storage and/or processing capabilities.
  • processing circuitry 518 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Host computer 510 further comprises software 511, which is stored in or accessible by host computer 510 and executable by processing circuitry 518.
  • Software 511 includes host application 512.
  • Host application 512 may be operable to provide a service to a remote user, such as UE 530 connecting via OTT connection 550 terminating at UE 530 and host computer 510. In providing the service to the remote user, host application 512 may provide user data which is transmitted using OTT connection 550.
  • Communication system 500 further includes base station 520 provided in a telecommunication system and comprising hardware 525 enabling it to communicate with host computer 510 and with UE 530.
  • Hardware 525 may include communication interface 526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 500, as well as radio interface 527 for setting up and maintaining at least wireless connection 570 with UE 530 located in a coverage area (not shown in FIGURE 12) served by base station 520.
  • Communication interface 526 may be configured to facilitate connection 560 to host computer 510. Connection 560 may be direct, or it may pass through a core network (not shown in FIGURE 12) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • hardware 525 of base station 520 further includes processing circuitry 528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Base station 520 further has software 521 stored internally or accessible via an external connection.
  • Communication system 500 further includes UE 530 already referred to. Its hardware 535 may include radio interface 537 configured to set up and maintain wireless connection 570 with a base station serving a coverage area in which UE 530 is currently located.
  • Hardware 535 of UE 530 further includes processing circuitry 538, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • UE 530 further comprises software 531, which is stored in or accessible by UE 530 and executable by processing circuitry 538.
  • Software 531 includes client application 532.
  • Client application 532 may be operable to provide a service to a human or non-human user via UE 530, with the support of host computer 510.
  • an executing host application 512 may communicate with the executing client application 532 via OTT connection 550 terminating at UE 530 and host computer 510.
  • client application 532 may receive request data from host application 512 and provide user data in response to the request data.
  • OTT connection 550 may transfer both the request data and the user data.
  • Client application 532 may interact with the user to generate the user data that it provides.
  • host computer 510, base station 520 and UE 530 illustrated in FIGURE 12 may be similar or identical to host computer 430, one of base stations 412a, 412b, 412c and one of UEs 491, 492 of FIGURE 10, respectively.
  • the inner workings of these entities may be as shown in FIGURE 12 and independently, the surrounding network topology may be that of FIGURE 10.
  • OTT connection 550 has been drawn abstractly to illustrate the communication between host computer 510 and UE 530 via base station 520, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from UE 530 or from the service provider operating host computer 510, or both. While OTT connection 550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., based on load balancing consideration or reconfiguration of the network).
  • Wireless connection 570 between UE 530 and base station 520 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to UE 530 using OTT connection 550, in which wireless connection 570 forms the last segment. More precisely, the teachings of these embodiments may improve the signaling overhead and reduce latency, which may provide faster internet access for users.
  • a measurement procedure may be provided for monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • There may further be an optional network functionality for reconfiguring OTT connection 550 between host computer 510 and UE 530, in response to variations in the measurement results.
  • the measurement procedure and/or the network functionality for reconfiguring OTT connection 550 may be implemented in software 511 and hardware 515 of host computer 510 or in software 531 and hardware 535 of UE 530, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 550 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above or supplying values of other physical quantities from which software 511, 531 may compute or estimate the monitored quantities.
  • the reconfiguring of OTT connection 550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 520, and it may be unknown or imperceptible to base station 520. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling facilitating host computer 510’s measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that software 511 and 531 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 550 while it monitors propagation times, errors etc.
  • FIGURE 13 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 11 and 12. For simplicity of the present disclosure, only drawing references to FIGURE 13 will be included in this section.
  • step 610 the host computer provides user data.
  • substep 611 (which may be optional) of step 610, the host computer provides the user data by executing a host application.
  • step 620 the host computer initiates a transmission carrying the user data to the UE.
  • step 630 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.
  • FIGURE 14 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 11 and 12. For simplicity of the present disclosure, only drawing references to FIGURE 14 will be included in this section.
  • step 710 of the method the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • step 720 the host computer initiates a transmission carrying the user data to the UE.
  • the transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 730 (which may be optional), the UE receives the user data carried in the transmission.
  • FIGURE 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 11 and 12. For simplicity of the present disclosure, only drawing references to FIGURE 15 will be included in this section.
  • step 810 the UE receives input data provided by the host computer. Additionally, or alternatively, in step 820, the UE provides user data. In substep 821 (which may be optional) of step 820, the UE provides the user data by executing a client application. In substep 811 (which may be optional) of step 810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 830 (which may be optional), transmission of the user data to the host computer. In step 840 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • FIGURE 16 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 11 and 12. For simplicity of the present disclosure, only drawing references to FIGURE 16 will be included in this section.
  • step 910 the base station receives user data from the UE.
  • step 920 the base station initiates transmission of the received user data to the host computer.
  • step 930 the host computer receives the user data carried in the transmission initiated by the base station.
  • the term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • references in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

Landscapes

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

Abstract

Selon certains modes de réalisation, un procédé mis en œuvre par un système de gestion de réseau consiste : à surveiller des mesures de plan utilisateur d'une pluralité de flux vocaux dans un réseau ; à déterminer périodiquement un indicateur de performances pour chaque flux de la pluralité de flux vocaux ; sur la base de l'indicateur de performances, à classer chaque flux de la pluralité de flux vocaux comme bon ou mauvais ; à déterminer un ou plusieurs nœuds de réseau associés à chaque flux de la pluralité de flux vocaux ; et pour chaque flux de la pluralité de flux vocaux, à transmettre un bon ou mauvais événement à chacun desdits nœuds de réseau associés au flux vocal.
PCT/IB2021/061588 2020-12-10 2021-12-10 Analyse cellulaire basée sur un protocole en temps réel WO2022123532A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202063123792P 2020-12-10 2020-12-10
US63/123,792 2020-12-10

Publications (1)

Publication Number Publication Date
WO2022123532A1 true WO2022123532A1 (fr) 2022-06-16

Family

ID=79270347

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2021/061588 WO2022123532A1 (fr) 2020-12-10 2021-12-10 Analyse cellulaire basée sur un protocole en temps réel

Country Status (1)

Country Link
WO (1) WO2022123532A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230016839A1 (en) * 2021-07-14 2023-01-19 At&T Intellectual Property I, L.P. Intelligent Customer Oriented Mobility Network Engineering at Edges
WO2024048871A1 (fr) * 2022-08-31 2024-03-07 Samsung Electronics Co., Ltd. Procédé et appareil de délestage de trafic dans une communication sans fil

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170208486A1 (en) * 2014-07-30 2017-07-20 Optulink Inc. Voice optimization enablement apparatus
CN108199916A (zh) * 2017-12-27 2018-06-22 中国移动通信集团山东有限公司 一种VoLTE语音质量监测方法及系统
US20190274186A1 (en) * 2017-09-07 2019-09-05 Intel IP Corporation Apparatuses for end-to-end coordination of voice over cellular data network communications
US20190342219A1 (en) * 2018-05-04 2019-11-07 T-Mobile Usa, Inc. Performance driven software defined networking

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170208486A1 (en) * 2014-07-30 2017-07-20 Optulink Inc. Voice optimization enablement apparatus
US20190274186A1 (en) * 2017-09-07 2019-09-05 Intel IP Corporation Apparatuses for end-to-end coordination of voice over cellular data network communications
CN108199916A (zh) * 2017-12-27 2018-06-22 中国移动通信集团山东有限公司 一种VoLTE语音质量监测方法及系统
US20190342219A1 (en) * 2018-05-04 2019-11-07 T-Mobile Usa, Inc. Performance driven software defined networking

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230016839A1 (en) * 2021-07-14 2023-01-19 At&T Intellectual Property I, L.P. Intelligent Customer Oriented Mobility Network Engineering at Edges
US11671861B2 (en) * 2021-07-14 2023-06-06 At&T Intellectual Property I, L.P. Intelligent customer oriented mobility network engineering at edges
WO2024048871A1 (fr) * 2022-08-31 2024-03-07 Samsung Electronics Co., Ltd. Procédé et appareil de délestage de trafic dans une communication sans fil

Similar Documents

Publication Publication Date Title
US12041490B2 (en) Notifying a management system of quality of experience measurement reporting status
EP4038940B1 (fr) Fourniture et exposition d'un modèle de communication d'équipement utilisateur (ue) associé à une application pour demander l'analyse du trafic de l'application dans le réseau central (cn)
US20200228260A1 (en) Buffer handling utilizing in-band control signaling
CN114600433B (zh) 用于使用机器学习和部分路径测量来估计网络性能的方法和系统
US20220394477A1 (en) False base station detection
US20230403606A1 (en) Managing resources in a radio access network
WO2020167223A1 (fr) Collecte de données initiée par ran
WO2022123532A1 (fr) Analyse cellulaire basée sur un protocole en temps réel
US20230111860A1 (en) Configuration of ue measurements
WO2023274149A1 (fr) Procédé, appareil d'assurance d'accord sur le niveau de service dans un réseau mobile
WO2019035092A1 (fr) Procédé permettant d'évaluer la qualité cellulaire de cellules à l'aide d'une formation de faisceau
US20230189022A1 (en) Predictive Decision-making in a Wireless Communication Network
US20240031868A1 (en) User Equipment, Radio Network Node and Methods for Handling Delay in Dual Connected Mode
EP4038932B1 (fr) Fonctionnement d'un compteur de débit de données dans un réseau de communication sans fil
US20230403548A1 (en) Method and apparatus for terminal device behavior classification
US20240196252A1 (en) Managing resources in a radio access network
US11910318B2 (en) Transfer of data between nodes
US20240080728A1 (en) Communication device measurement and report for pattern recognition of periodic resource availability for extended reality mobility
US20240089816A1 (en) Conditional Handover OAM Measurements
US20240155390A1 (en) Controlling Transmission on a Resource Subject to a Listen-Before-Talk Procedure
US20240314868A1 (en) Communication device pre-grant assistance
WO2024150087A1 (fr) Détection de trafic soumis à deux serveurs mandataires
WO2023223081A1 (fr) Établissement amélioré de rapports de mesures de qualité d'expérience (qoe)
WO2024218533A1 (fr) Surveillance de qualité de service de trafic webrtc dans des réseaux mobiles
CN117616865A (zh) 缓冲器状态报告开销估计

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21839260

Country of ref document: EP

Kind code of ref document: A1