Determining network system problems

Abstract

Apparatuses, methods, and systems are disclosed for determining network system problems. A method (900) includes a first network device determining (902) a system problem corresponding to at least one second network device. The first network device is an analytics entity in a cellular network and the at least one second network device is a managed entity in the cellular network, and the system problem comprises a software problem, a hardware problem, a compatibility problem, an interaction problem between multiple second network devices including the at least one second network device, an interaction problem between the at least one second network device and another device, or some combination thereof. The analytics entity comprises an entity that analyzes one or more devices to determine a descriptive analytics, a predictive analytics, and / or a normative analytics. The method (900) includes providing (904) a notification indicative of the system problem.

Description

Technical Field

[0001] The subject matter disclosed in this article generally relates to wireless communication, and more specifically, to the problem of identifying network systems. Background Technology

[0002] The following abbreviations are defined herein, and at least some of them are mentioned in the following description: 3rd Generation Partnership Project (“3GPP”), 5th Generation (“5G”), 5G System (“5GS”), 5G QoS Identifier (“5QI”), Authentication, Authorization and Accounting (“AAA”), Positive Acknowledgment (“ACK”), Application Function (“AF”), Artificial Intelligence (“AI”), Authentication and Key Negotiation (“AKA”), Convergence Level (“AL”), Access and Mobility Management Function (“AMF”), Angle of Arrival (“AOA”), Angle of Departure (“AoD”), Access Point (“AP”), Application Programmable Interface (“API”), Access Layer (“AS”), Application Service Provider (“ASP”), Autonomous Uplink (“AUL”), Authentication Server Function (“AUSF”), Authentication Token (“AUTN”), Background Data Background Data Transmission (“BD”), Beam Fault Detection (“BFD”), Beam Fault Recovery (“BFR”), Binary Phase Shift Keying (“BPSK”), Base Station (“BS”), Buffer Status Report (“BSR”), Bandwidth (“BW”), Bandwidth Portion (“BWP”), Cell RNTI (“C-RNTI”), Carrier Aggregation (“CA”), Channel Access Priority Class (“CAPC”), Channel Busy Ratio (“CBR”), Contention-Based Random Access (“CBRA”), Idle Channel Assessment (“CCA”), Common Control Channel (“CCCH”), Control Channel Elements (“CCE”), Cyclic Delay Late Diversity (“CDD”), Code Division Multiple Access (“CDMA”), Control Element (“CE”), Contention-Free Random Access (“CFRA”), Configuration Grant (“CG”), Closed Loop (“CL”), Core Network (“CN”), Coordinated Multipoint (“CoMP”), Requirement Class (“CoR”), Channel Occupancy Time (“COT”), Cyclic Prefix (“CP”), Channel Quality Indicator (“CQI”), Cyclic Redundancy Check (“CRC”), Channel State Information (“CSI”), Channel State Information-Reference Signal (“CSI-RS”), Common Search Space (“CSS”), Control Resource Set (“CORESET”), Discrete Fourier Transform Extended (“DFTS”), Downlink Control Information (“DCI”), Downlink Feedback Information (“DFI”), Dynamic Grant (“DG”), Downlink (“DL”), Demodulation Reference Signal (“DMRS”), Data Network Name (“DNN”), Data Radio Bearer (“DRB”), Discontinuous Receive (“DRX”), Dedicated Short Range Communication (“DSRC”), Downlink Pilot Time Slot (“DwPTS”), End-to-End (“E2E”), Enhanced Idle Channel Assessment (“eCCA”), Enhanced Mobile Broadband (“eMBB”), Evolved Node B (“eNB”), Enhanced V2X (“eV2X”)Extensible Authentication Protocol (“EAP”), Enhanced ICIC (“eICIC”), Effective Isotropic Radiated Power (“EIRP”), Evolved Packet System (“EPS”), European Telecommunications Standards Institute (“ETSI”), Frame-Based Equipment (“FBE”), Frequency Division Duplex (“FDD”), Frequency Division Multiplexing (“FDM”), Frequency Division Multiple Access (“FDMA”), Frequency Division Orthogonal Coverage Code (“FD-OCC”), Frequency Range 1-Sub-6GHz Band and / or 410MHz to 7125MHz (“FR1”), Frequency Range 2-24.25GHz to 52.6GHz (“FR2”), Universal Geographic Area Description (“GAD”), Guaranteed Bit Rate (“GBR”) ), Guaranteed Flow Rate (“GFBR”), Group Leader (“GL”), 5G Node B or Next Generation Node B (“gNB”), Global Navigation Satellite System (“GNSS”), General Packet Radio Service (“GPRS”), Guard Period (“GP”), Global Positioning System (“GPS”), Universal Public Subscription Identifier (“GPSI”), Global System for Mobile Communications (“GSM”), Globally Unique Temporary UE Identifier (“GUTI”), Home AMF (“hAMF”), Hybrid Automatic Repeat Request (“HARQ”), Home Location Register (“HLR”), Handover (“HO”), Home PLMN (“HPLMN”), Home Subscriber Server (“HSS”), Hash Pre- Inter-cell interference coordination (“ICIC”), identification or identifier (“ID”), information element (“IE”), industrial Internet of Things (“IIOT”), International Mobile Equipment Identity (“IMEI”), International Mobile Subscriber Identity (“IMSI”), International Mobile Telecommunications (“IMT”), Internet of Things (“IoT”), Intelligent Transportation Systems (“ITS”), Key Performance Indicators (“KPI”), Layer 1 (“L1”), Layer 2 (“L2”), Layer 3 (“L3”), Licensed Auxiliary Access (“LAA”), Local Area Data Network (“LADN”), Local Area Network (“LAN”), Load-Based Equipment (“LBE”), Listen Before Talk (“LBT”), logical Logical Channel (“LCH”), Logical Channel Group (“LCG”), Logical Channel Priority (“LCP”), Log-Likelihood Ratio (“LLR”), Level of Automation (“LoA”), Line of Sight (“LOS”), Long Term Evolution (“LTE”), LTE Vehicles (“LTE-V”), Multiple Access (“MA”), Media Access Control (“MAC”), Multimedia Broadcast / Multicast Service (“MBMS”), Maximum Bit Rate (“MBR”), Minimum Communication Range (“MCR”), Modulation and Coding Scheme (“MCS”), Management Data Analysis Service (“MDAS”), Management and Orchestration Data Analysis Function (“MDAF”), Managed Entity (“ME”), Mobile Edge Computing (“MEC”)Master Information Block (“MIB”), Multiple Input Multiple Output (“MIMO”), Machine Learning (“ML”), Mobility Management (“MM”), Mobility Management Entity (“MME”), Master Node (“MN”), Management Function (“MnF” or “MF”), Mobile Network Operator (“MNO”), Management Service (“MnS”), Mobile Initiation (“MO”), Average Opinion Score (“MOS”), Massive MTC (“mMTC”), Maximum Power Reduction (“MPR”), Machine-Type Communication (“MTC”), Multiple Transmitter and Receiver Point (“M-TRP”), Multiple User Shared Access (“MUSA”), Non-Access Layer (“NAS”), Narrowband (“NB”), Negative Acknowledgment (“NACK”) or (“NAK”), New Data Indicator (“NDI”), Network Entity (“NE”), Network Open Function (“NEF”), Network Open Function / Service Capability Open Function (“NEF / SCEF”), Network Function (“NF”), Non-LOS (“NLOS”), Next Generation (“NG”), NG 5G S-TMSI (“NG-5G-S-TMSI”), Neural Network (“NN”), Non-Orthogonal Multiple Access (“NOMA”), New Radio (“NR”), NR Unlicensed (“NR-U”), Network Repository Function (“NRF”), Network Scheduling Modes (“NS Modes”) (e.g., Network Scheduling Mode for V2X Communication Resource Allocation - NR V2X Mode-1 and LTE) V2X Mode 3), Network Slicing Examples (“NSI”), Network Slice Selection Assistance Information (“NSSAI”), Network Slice Selection Function (“NSSF”), Network Slice Selection Policy (“NSSP”), Operation, Management and Maintenance System or Operation and Maintenance Center (“OAM”), Orthogonal Frequency Division Multiplexing (“OFDM”), Orthogonal Frequency Division Multiple Access (“OFDMA”), Open Loop (“OL”), Other System Information (“OSI”), Power Angle Spectrum (“PAS”), Physical Broadcast Channel (“PBCH”), Power Control (“PC”), UE-to-UE Interface (“PC5”), Principal Component Analysis (“PCA”), Policy and Charging Control (“PCC”) The physical layer includes the primary cell (“PCell”), policy and charging rules function (“PCRF”), policy control function (“PCF”), physical cell identifier (“PCI”), physical downlink control channel (“PDCCH”), packet data convergence protocol (“PDCP”), packet data network gateway (“PGW”), physical downlink shared channel (“PDSCH”), mode segmentation multiple access (“PDMA”), packet data unit (“PDU”), physical hybrid ARQ indicator channel (“PHICH”), power headroom (“PH”), power headroom report (“PHR”), physical layer (“PHY”), and public land mobile network (“PLMN”).Precoding Matrix Index (“PMI”), Physical Network Function (“PNF”), Per-Packet Neighborhood Service Priority (“PPPP”), Per-Packet Neighborhood Service Reliability (“PPPR”), PC5 5QI (“PQIs”), Predictive QoS (“P-QoS”), Physical Random Access Channel (“PRACH”), Physical Resource Block (“PRB”), Neighborhood Service (“ProSe”), Location Reference Signal (“PRS”), Physical Sidelink Control Channel (“PSCCH”), Primary and Secondary Cell (“PSCell”), Physical Sidelink Feedback Control Channel (“PSFCH”), Physical Uplink Control Channel (“PUCCH”), Physical Uplink Shared Channel (“PUSCH”), QoS Category Identifier (“QCI”), Quasi-Same Position (“QCL”), QoS Flow Indicator (“QFI”), Quality of Experience (“QoE”), Quality of Service (“QoS”), Quadrature Phase Shift Keying (“QPSK”), Registration Area (“RA”), RA RNTI (“RA-RNTI”), Radio Access Network (“RAN”), Random (“RAND”), Radio Access Technology (“RAT”), Serving RAT (“RAT-1”) (regarding Uu services), Other RAT (“RAT-2”) (regarding Uu non-services), Random Access Procedure (“RACH”), Random Access Preamble Identifier (“RAPID”), Random Access Response (“RAR”), Resource Block Assignment (“RBA”), Resource Element Group (“REG”), Ranking Indicator (“RI”), RAN Intelligent Controller (“RIC”), Radio Link Control (“RLC”), RLC Acknowledgment Mode (“RLC-AM”), RLC No-Acknowledgment Mode / Transparent Mode (“RLC-UM / TM”), Radio Link Failure (“RLF”), Radio Link Monitoring (“RLM”), Radio Network Information (“RNI”), RNI Service (“RNIS”) The following radio network temporary identifiers are used: (“RNTI”), (“RS”), (“RM”), (“RMSI”), (“RRC”), (“RRM”), (“RSMA”), (“RSRP”), (“RSSI”), (“RTT”), (“RX”), (“SCEF”), (“SCMA”), (“SR”), (“SRS”), (“SCH”), (“SCI”), (“SCS”), (“SC-FDMA”), (“SCell”), (“SCG”), (“SCH”), (“SCI”), (“SCS”), (“SDM”).Service Data Unit (“SDU”), Security Anchor Function (“SEAF”), Service Enabler Architecture Layer (“SEAL”), Sidelink Feedback Content Information (“SFCI”), Service Gateway (“SGW”), System Information Block (“SIB”), System Information Block Type 1 (“SIB1”), System Information Block Type 2 (“SIB2”), User Identifier / Identification Module (“SIM”), Signal-to-Interference-plus-Noise Ratio (“SINR”), Sidelink (“SL”), Service Level Agreement (“SLA”), Sidelink Synchronization Signal (“SLSS”), Session Management (“SM”), Session Management Function (“SMF”), Secondary Node (“SN”), Special Cell (“SpCell”), Semi-Persistent Scheduling (“SPS”), Single Network Slice Selection Auxiliary Information (“S-NSSAI”), Scheduling Request (“SR”), Signaling Radio Bearer (“SRB”), Shortened TMSI (“S-TMSI”), Time to Live (“ST”), Shortened TTI (“sTTI”), Synchronization Signal (“SS”), Sidelink CSI RS (“S-CSI RS”), Side Link PRS (“S-PRS”), Side Link SSB (“S-SSB”), Synchronization Signal Block (“SSB”), Subscription Hidden Identifier (“SUCI”), Scheduled User Equipment (“SUE”), Supplemental Uplink (“SUL”), User Permanent Identifier (“SUPI”), Support Vector Machine (“SVM”), Tracking Area (“TA”), TA Identifier (“TAI”), TA Update (“TAU”), Timing Alignment Timer (“TAT”), Transport Block (“TB”), Transport Block Size (“TBS”), Transport Configuration Indicator (“TCI”), Time Division Duplex (“TDD”), Time Division Multiplexing (TDD) Multiplexing (“TDM”), Time Division Orthogonal Cover Code (“TD-OCC”), Time Domain Resource Allocation (“TDRA”), Temporary Mobile Subscriber Identity (“TMSI”), Time of Flight (“ToF”), Transmit Power Control (“TPC”), Transmit Receive Point (“TRP”), Time Sensitive Communication (“TSC”), Time Sensitive Auxiliary Information (“TSCAI”), Transmission Time Interval (“TTI”), Transmission (“TX”), Uplink Control Information (“UCI”), Unified Data Management Function (“UDM”), Unified Data Repository (“UDR”), User Entity / Equipment (Mobile Terminal) (“UE”) (e.g., V2X) UE), UE autonomous mode (UE autonomous selection of V2X communication resources - e.g., mode-2 in NR V2X and mode-4 in LTE V2X. UE autonomous selection may or may not be based on resource sensing operation), uplink (“UL”), UL SCH (“UL-SCH”), Universal Mobile Telecommunications System (“UMTS”), user plane (“UP”), UP function (“UPF”), uplink pilot slots (“UpPTS”).Ultra-Reliable and Low-Latency Communication (“URLLC”), UE Routing Policy (“URSP”), Vehicle-to-Vehicle (“V2V”), Vehicle-to-Everything (“V2X”), V2X Control Functions (“V2XCF”), V2X UEs (e.g., UEs capable of vehicle communication using 3GPP protocols), V2X Application Enablers (“VAE”), Access AMF (“vAMF”), Virtualized Network Functions (“VNF”), Access NSSF (“vNSSF”), Access PLMN (“vPLMN”), Wide Area Networks (“WAN”), and Global Microwave Access Interoperability (“WiMAX”).

[0003] In some wireless communication networks, there may be system problems. Summary of the Invention

[0004] A method for determining network system problems is disclosed. Devices and systems also perform the functions of the method. One embodiment of the method includes: determining, at a first network device, a system problem corresponding to at least one second network device, wherein the first network device is an analysis entity in a cellular network, and the at least one second network device is a managed entity in the cellular network, and the system problem includes software problems, hardware problems, compatibility problems, interaction problems between a plurality of second network devices including the at least one second network device, interaction problems between the at least one second network device and another device, or some combination thereof, and wherein the analysis entity includes an entity that analyzes one or more devices to determine descriptive analysis, predictive analysis, prescriptive analysis, or some combination thereof. In some embodiments, the method includes providing a notification indicating the system problem.

[0005] An apparatus for determining network system problems includes: a processor that: determines a system problem corresponding to at least one second network device, wherein the first network device is an analysis entity in a cellular network, and the at least one second network device is a managed entity in the cellular network, and the system problem includes software problems, hardware problems, compatibility problems, interaction problems between a plurality of second network devices including the at least one second network device, interaction problems between the at least one second network device and another device, or some combination thereof, and wherein the analysis entity includes an entity that analyzes one or more devices to determine descriptive analysis, predictive analysis, prescriptive analysis, or some combination thereof; and provides a notification indicating the system problem. Attached Figure Description

[0006] A more specific description of the embodiments briefly described above will be presented with reference to specific embodiments illustrated in the accompanying drawings. It should be understood that these drawings depict only some embodiments and are therefore not intended to limit the scope; the embodiments will be described and explained more clearly and in detail using the accompanying drawings, in which:

[0007] Figure 1 This is a schematic block diagram illustrating one embodiment of a wireless communication system used to determine network system problems;

[0008] Figure 2 This is a schematic block diagram illustrating one embodiment of a device that can be used to determine problems in a network system;

[0009] Figure 3 This is a schematic block diagram illustrating one embodiment of a device that can be used to determine problems in a network system;

[0010] Figure 4 This is a hierarchical block diagram illustrating one embodiment of the logical representation of a management domain;

[0011] Figure 5 This is a layered diagram illustrating one embodiment of a deployment scenario for a management domain;

[0012] Figure 6 This is a communication diagram illustrating one embodiment of communication within the system;

[0013] Figure 7 This is a communication diagram illustrating one embodiment of communication based on management services;

[0014] Figure 8 This is a communication diagram illustrating another embodiment of communication based on management services; and

[0015] Figure 9 This is a flowchart illustrating one embodiment of a method for identifying problems in a network system. Detailed Implementation

[0016] As those skilled in the art will understand, aspects of the embodiments may be embodied as systems, devices, methods, or program products. Therefore, embodiments may take the form of entirely hardware embodiments, entirely software embodiments (including firmware, resident software, microcode, etc.), or embodiments combining software and hardware aspects generally referred to herein as "circuit," "module," or "system." Furthermore, embodiments may take the form of program products embodied in one or more computer-readable storage devices storing machine-readable code, computer-readable code, and / or program code (hereinafter referred to as "code"). Storage devices may be tangible, non-transitory, and / or non-transferable. Storage devices may not embody signals. In certain embodiments, storage devices use only signals to access code.

[0017] Certain functional units described in this specification may be labeled as modules to more specifically emphasize their implementation independence. For example, a module may be implemented as hardware circuitry comprising custom very large-scale integration (“VLSI”) circuitry or gate arrays, off-the-shelf semiconductors (e.g., logic chips), transistors, or other discrete components. Modules may also be implemented in programmable hardware devices (e.g., field-programmable gate arrays, programmable array logic, programmable logic devices, or the like).

[0018] Modules can also be implemented as code and / or software for execution by various types of processors. An identified code module may, for example, contain one or more physical or logical blocks of executable code, which may, for example, be organized as objects, programs, or functions. However, the executable file of the identified module does not need to be physically located together, but may contain different instructions stored in different locations that, when logically combined, encompass the module and achieve the stated purpose of the module.

[0019] In practice, a code module can be a single instruction or many instructions, and can even be distributed across several different code segments, different programs, and across several memory devices. Similarly, operational data can be identified and described within the module herein, and can be represented in any suitable form and organized within any suitable type of data structure. Operational data can be collected as a single dataset or distributed across different locations, including across different computer-readable storage devices. Where the module or part of a module is implemented in software, the software portion is stored on one or more computer-readable storage devices.

[0020] Any combination of one or more computer-readable media may be used. The computer-readable media may be a computer-readable storage medium. The computer-readable storage medium may be a storage device for storing code. The storage device may be (e.g., but not limited to) an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, device, or apparatus, or any suitable combination of the foregoing.

[0021] More specific examples of storage devices (a non-exhaustive list) will include: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (“RAM”), read-only memory (“ROM”), erasable programmable read-only memory (“EPROM” or flash memory), portable optical disc read-only memory (“CD-ROM”), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the context of this document, computer-readable storage media can be any tangible medium that may contain or store programs used by or in conjunction with an instruction execution system, device, or apparatus.

[0022] The code used to implement the operations of the embodiments can be any number of lines and can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, C++, or similar, and conventional procedural programming languages ​​such as the "C" programming language or similar, and / or machine languages ​​such as assembly language. The code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter case, the remote computer can be connected to the user's computer via any type of network, including local area networks ("LANs") or wide area networks ("WANs"), or can connect to external computers (e.g., through the Internet provided by an Internet service provider).

[0023] References to "an embodiment," "embodiment," or similar language throughout this specification mean that a particular feature, structure, or characteristic described in connection with an embodiment is included in at least one embodiment. Therefore, the phrases "in one embodiment," "in one embodiment," and similar language appearing throughout this specification may (but not necessarily) refer to the same embodiment, but rather to "one or more, but not all, embodiments," unless expressly specified otherwise. Unless expressly specified otherwise, the terms "comprising," "including," "having," and variations thereof mean "comprising (but not limited to)." Unless expressly specified otherwise, an enumerated list of items does not imply that any or all items are mutually exclusive. Unless expressly specified otherwise, the terms "a / an" and "described" also refer to "one or more."

[0024] Furthermore, the described features, structures, or characteristics of the embodiments can be combined in any suitable manner. Numerous specific details, such as examples of programming, software modules, user selection, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., are provided in the following description to provide a thorough understanding of the embodiments. However, those skilled in the art will recognize that the embodiments can be practiced without employing one or more of the specific details or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations have not been shown or described in detail to avoid obscuring aspects of the embodiments.

[0025] The following description of aspects of embodiments is based on schematic flowcharts and / or schematic block diagrams of methods, apparatus, systems, and program products according to embodiments. It will be understood that each block of the schematic flowcharts and / or schematic block diagrams, and combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. The code can be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to generate machinery, such that instructions executable via the processor of the computer or other programmable data processing apparatus create a manner for implementing the functions / actions specified in the blocks of the schematic flowcharts and / or one or more schematic block diagrams.

[0026] The code may also be stored in a storage device, which may instruct a computer, other programmable data processing device or other device to function in a particular manner, such that the instructions stored in the storage device produce an article of writing containing instructions that implement the functions / actions specified in the schematic flowchart and / or one or more schematic block diagram frames.

[0027] The code may also be loaded onto a computer, other programmable data processing device or other apparatus to cause a series of operational steps to be performed on the computer, other programmable device or other apparatus to produce a computer-implemented process, such that the code executing on the computer or other programmable device provides a process for implementing the functions / actions specified in the flowchart and / or one or more block diagram boxes.

[0028] The schematic flowcharts and / or block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of the device, system, method, and program products according to various embodiments. In this regard, each block in the schematic flowcharts and / or block diagrams may represent a code module, code segment, or code portion, which contains one or more executable instructions consisting of code for implementing a specified logical function.

[0029] It should also be noted that in some alternative implementations, the functions indicated in the boxes may not appear in the order shown in the figures. For example, depending on the functionality involved, two boxes shown consecutively may actually be performed substantially simultaneously, or sometimes the boxes may be performed in reverse order. Other steps and methods that are functionally, logically, or effectively equivalent to one or more boxes or portions thereof in the illustrated figures are conceivable.

[0030] While various arrow and line types may be used in flowcharts and / or block diagrams, they are not intended to limit the scope of the corresponding embodiments. In practice, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For example, an arrow may indicate a waiting or monitoring period of unspecified duration between the enumerated steps of the depicted embodiment. It will also be noted that each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, may be implemented by a system based on dedicated hardware or a combination of dedicated hardware and code that performs the specified function or action.

[0031] The description of the components in each figure can be referenced to the components in the previous figure. The same numbers refer to the same components in all figures, including alternative embodiments containing the same components.

[0032] Figure 1 An embodiment of a wireless communication system 100 for determining network system problems is described. In one embodiment, the wireless communication system 100 includes a remote unit 102, a network unit 104, and one or more V2X application units 105. Although in Figure 1 A specific number of remote units 102, network units 104, and V2X application units 105 are depicted in the description, but those skilled in the art will recognize that any number of remote units 102, network units 104, and V2X application units 105 may be included in the wireless communication system 100.

[0033] In one embodiment, remote unit 102 may include a computing device, such as a desktop computer, laptop computer, personal digital assistant (“PDA”), tablet computer, smartphone, smart TV (e.g., a TV connected to the Internet), set-top box, game console, security system (including security cameras), vehicle onboard computer, network device (e.g., router, switch, modem), aircraft, drone, or the like. In some embodiments, remote unit 102 includes a wearable device, such as a smartwatch, fitness tracker, optical head-mounted display, or the like. Furthermore, remote unit 102 may be referred to as a user unit, mobile device, mobile station, user, terminal, mobile terminal, fixed terminal, user station, UE, user terminal, device, or by other terms used in the art. Remote unit 102 may communicate directly with one or more of network units 104 via UL communication signals. In some embodiments, remote unit 102 may communicate directly with other remote units 102 via sidelink communication.

[0034] Network unit 104 may be distributed over a geographical area. In some embodiments, network unit 104 may also be referred to as an access point, access terminal, base station, base station, Node B, eNB, gNB, home Node B, relay node, device, core network, air server, radio access node, AP, NR, network entity, AMF, UDM, UDR, UDM / UDR, PCF, RAN, NSSF, or by any other term used in the art. Network unit 104 is typically a portion of a radio access network comprising one or more controllers communicatively coupled to one or more corresponding network units 104. The radio access network is typically communicatively coupled to one or more core networks, which may be coupled to other networks, such as the Internet and public switched telephone networks, and other networks. These and other elements of the radio access network and core network are not described but are generally well known to those skilled in the art.

[0035] In one implementation, the wireless communication system 100 conforms to the NR protocol standardized in 3GPP, wherein network unit 104 transmits using an OFDM modulation scheme on DL and remote unit 102 transmits using an SC-FDMA scheme or an OFDM scheme on UL. However, more generally, the wireless communication system 100 may implement other open or proprietary communication protocols, such as WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA2000, etc. ZigBee, Sigfoxx, and other protocols. This disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

[0036] Network unit 104 can serve several remote units 102 within a service area (e.g., a cell or cell sector) via a wireless communication link. Network unit 104 transmits DL communication signals in the time domain, frequency domain, and / or spatial domain to serve the remote units 102. In some embodiments, V2X application unit 105 can provide application requests to remote units 102 and / or network unit 104.

[0037] In various embodiments, network unit 104 may determine a system problem corresponding to at least one second network device at a first network device, wherein the first network device is an analysis entity in the cellular network, and at least one second network device is a managed entity in the cellular network. The system problem includes software problems, hardware problems, compatibility problems, interaction problems between multiple second network devices including at least one second network device, interaction problems between at least one second network device and another device, or some combination thereof. The analysis entity includes an entity that analyzes one or more devices to determine descriptive analysis (e.g., describing what has been analyzed), predictive analysis (e.g., making predictions based on analysis), prescriptive analysis (e.g., determining actions to be performed based on analysis), or some combination thereof. A managed entity may refer to managed resources and / or managed services (e.g., a managed entity may be infrastructure resources, such as virtual network functions, physical network functions, and / or services (e.g., cloud services, virtual network function network services, etc.)). The managed entity may also refer to any managed object, managed resource, and / or managed service (e.g., software and / or hardware entities, such as infrastructure resources, such as virtual network functions, physical network functions, and / or services (e.g., cloud services, virtual network function network services, etc.)). In some embodiments, network unit 104 may provide notifications indicating system problems. Therefore, network unit 104 can be used to determine network system problems.

[0038] Figure 2 One embodiment of a device 200 for determining network system problems is depicted. Device 200 includes one embodiment of a remote unit 102. Furthermore, the remote unit 102 may include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, the input device 206 and the display 208 are combined into a single device, such as a touchscreen. In some embodiments, the remote unit 102 may not include any input device 206 and / or display 208. In various embodiments, the remote unit 102 may include one or more of the processor 202, memory 204, transmitter 210, and receiver 212, and may not include an input device 206 and / or display 208.

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

[0040] In one embodiment, memory 204 is a computer-readable storage medium. In some embodiments, memory 204 includes volatile computer storage media. For example, memory 204 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 204 includes non-volatile computer storage media. For example, memory 204 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 204 includes both volatile and non-volatile computer storage media. In some embodiments, memory 204 also stores program code and related data, such as an operating system or other controller algorithms operating on remote unit 102.

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

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

[0043] In some embodiments, display 208 includes one or more speakers for generating sound. For example, display 208 may generate an audible alarm or notification (e.g., a beep or ring). In some embodiments, display 208 includes one or more haptic devices for generating vibration, motion, or other haptic feedback. In some embodiments, all or part of display 208 may be integrated with input device 206. For example, input device 206 and display 208 may form a touchscreen or similar touch-sensitive display. In other embodiments, display 208 may be positioned near input device 206.

[0044] Although only one transmitter 210 and one receiver 212 are described, the remote unit 102 may have any suitable number of transmitters 210 and receivers 212. The transmitters 210 and receivers 212 may be of any suitable type. In one embodiment, the transmitters 210 and receivers 212 may be part of a transceiver.

[0045] Figure 3 An embodiment of a device 300 for determining network system problems is depicted. Device 300 includes one embodiment of a network unit 104. Furthermore, network unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. As will be understood, the processor 302, memory 304, input device 306, display 308, transmitter 310, and receiver 312 may be substantially similar to the processor 202, memory 204, input device 206, display 208, transmitter 210, and receiver 212 of remote unit 102, respectively.

[0046] In some embodiments, processor 302 may: determine a system problem corresponding to at least one second network device, wherein the first network device is an analysis entity in the cellular network, and the at least one second network device is a managed entity in the cellular network, and the system problem includes software problems, hardware problems, compatibility problems, interaction problems between a plurality of second network devices including at least one second network device, interaction problems between at least one second network device and another device, or some combination thereof; and provide a notification indicating the system problem, wherein the analysis entity includes an entity that analyzes one or more devices to determine descriptive analysis, predictive analysis, prescriptive analysis, or some combination thereof. In some embodiments, transmitter 310 may be used to transmit the information described herein. Although only one transmitter 310 and one receiver 312 are described, network unit 104 may have any suitable number of transmitters 310 and receivers 312. Transmitters 310 and receivers 312 may be of any suitable type. In one embodiment, transmitters 310 and receivers 312 may be part of a transceiver.

[0047] In various embodiments, the system may include multiple managed entities, such as NSIs, NSSIs, and NFs (e.g., running on VNFs or PNFs), that may be susceptible to risks (e.g., inaccurate programming, unforeseen errors, vulnerabilities in the managed virtualization platform, protocol design flaws, security errors, etc.). In such embodiments, errors may be amplified due to complex interactions with other managed entities. In some embodiments, an anomalous managed entity may be a managed entity that exhibits significantly different behavior based on one or more observed KPIs compared to other similar managed entities.

[0048] In some embodiments, thresholds associated with abnormal or anomalous behavior may be configured by a human operator based on prior knowledge and / or experience. In such embodiments, if a threshold is exceeded during a performance measurement of the managed entity, a "notifyThresholdCrossing" notification may be issued by the management system. Upon notification, the operator can review available information related to the notification, the current state of the network, and identify corrective actions based on prior experience and knowledge.

[0049] In various embodiments, a management domain may be a collection of resources having its own management system. In some embodiments, a management system may be any collection of management services or implementations thereof in terms of management functions. In some embodiments, a management domain may include, for example, vendor devices, vendor solutions, technology domains (e.g., 3GPP core, 3GPP RAN, cloud domain, data center, transport network with its own controller, operator management domain, country domain, etc.) having their own management systems.

[0050] Figure 4This is a hierarchical block diagram 400 illustrating an embodiment of the logical representation of a management domain. Hierarchical domain 400 includes an E2E management domain 402. The E2E management domain 402 can manage a first management domain 404, a second management domain 406, and a third management domain 408.

[0051] Figure 5 This example demonstrates a possible deployment of a management domain for an operator providing services in the United States and Germany. As illustrated, only the German domain has been further expanded to demonstrate recursion within the management domain. Figure 5 yes Figure 4 This is one example of an embodiment, and other domains may exist, such as vendor-specific management domains and / or equipment.

[0052] To be clear, Figure 5 This is a layered diagram 500 illustrating one embodiment of a management domain deployment scenario. Layered domain 500 includes an E2E management domain 502. E2E management domain 502 can manage management domain 504 (e.g., external), management domain 506 (e.g., US carrier), management domain 508 (e.g., US-Germany transport network), and management domain 510 (e.g., Germany). Furthermore, management domain 510 can manage management domain 512 (e.g., North) and management domain 514 (e.g., South). Additionally, management domain 514 can manage management domain 516 (e.g., cloud) and management domain 518 (e.g., 3GPP).

[0053] In some embodiments, such as within the 3GPP management plane, MDAS can collect and / or analyze data collected within the management plane. In various embodiments, MDAS functionality may be referred to as a general analytics service. In some embodiments, statistical analysis and / or other machine learning techniques may be applied to enable analytics services (e.g., MDAS) to identify anomalous managed entities. In some embodiments, the behavior of a managed entity may be anomalous due to one or more of the following: compromised security; programming errors in the software system; use of incorrect or incompatible versions of equipment; and / or misconfiguration or design of equipment.

[0054] In various embodiments, based on the nature and / or cause of the anomalous ME, MDAS may recommend any or more of the following actions: 1) notifying the MDAS consumer; and / or 2) recommending any of the following possible corrective measures: a) advising the analytics consumer to continue operation by possible alternative means and / or methods (e.g., in the case of excluding the anomalous ME), such as isolating the anomalous managed entity or transferring responsibility for the anomalous ME to other equivalent MEs; b) the software management system providing and / or activating a replacement managed entity (e.g., with an updated software version or replacement software from a different vendor, proper configuration, etc.) to take over the operation of the anomalous ME; c) notifying the analytics consumer to enable the consumer to take further action; d) deploying services to deactivate and / or deassign the anomalous ME from the network, wherein alternatives are optionally deployed and / or activated; e) notifying the monitoring service to collect additional data or even different types of data at different times; and / or f) recording the actions of activating the anomalous ME. It is understood that the embodiments described herein are applicable to any management system with analytics, including cloud management, E2E, and / or domain management systems. As used in this article, anomalous MEs and / or MEs with abnormal behavior can refer to MEs whose behavior differs from other similar MEs as identified by the analytics service provider.

[0055] In various embodiments, in order to be enabled to provide the recommendations described herein, the analytics service may access data about the ME, such as: ME version (e.g., software version, hardware version); software and / or hardware vendor details; known compatibility issues related to the ME; other relevant performance data of the ME and / or related MEs; and / or ME fingerprints (e.g., used to identify anomalous MEs from their initial configuration version).

[0056] Figure 6 This is a communication diagram illustrating one embodiment of communication 600 in the system. Communication 600 includes communications transmitted between ME 602, monitoring service producer 604, analysis service producer 606, and analysis service consumer 608. As used herein, any of communication 600 may contain one or more messages.

[0057] In the first communication 610 transmitted between ME 602, monitoring service producer 604, and analysis service producer 606, analysis service producer 606 collects data from several managed entities (e.g., ME 602) via monitoring service producer 604. Analysis service producer 606 periodically analyzes 612 this data to identify anomalous and / or abnormal ME performance data. In some embodiments, MEs with anomalous and / or abnormal ME performance data may be identified 614. Specifically, anomalous and / or abnormal ME performance data can demonstrate abnormal behavior of the ME, which may indicate various problems such as errors in the network, potential misoperation, programming errors, incorrect installation, configuration, ME incompatibility, security vulnerabilities, and / or security issues related to the operation of the ME or a combination of MEs. If an abnormal ME is identified 616 by analysis service producer 606, then analysis service producer 606 notifies a set of appropriate analysis service consumers (e.g., analysis service consumer 608) of the cause of the anomaly, possible solutions, and associated information. In various embodiments, monitoring service producer 604 may be configured to collect appropriate data from the ME at appropriate times. In some embodiments, the analytics consumer may be configured to listen to the analytics service.

[0058] As part of the first communication 610, the monitoring service producer 604 periodically collects streaming or file-based data from the managed entities and periodically (e.g., action-driven or on-demand) reports it to the analysis service producer 606 for analysis. The periods for data collection, streaming, or analysis can all be different. As described herein, the analysis service producer 606 analyzes the collected data 612. This analysis can be performed periodically or activated by triggers (e.g., thresholds configured on the monitoring data exceeding a notification).

[0059] If analytics service producer 606 identifies an abnormal ME or a group of MEs (e.g., 616) in 616, then in a second communication 618, analytics service producer 606 notifies the appropriate analytics service consumer (e.g., analytics service consumer 608). The notification may include one or more of the following: an identifier of the abnormal ME or group of MEs (e.g., more than one); identifiers of other associated or affected MEs; the reason for the abnormal behavior identification; the severity of the anomaly; associated monitored data; recommended solutions (e.g., one or more solutions described herein); and / or references to other previously related occurrences. In some embodiments, the analytics service consumer 608 providing this notification may include a dashboard or management record system for a human operator.

[0060] In the third communication 620 (e.g., optional), the analytics service consumer 608 can respond to the notification using messages from the analytics service producer 606. The response may contain information indicating whether the analytics service's recommended solution (e.g., if provided) is approved or rejected.

[0061] Based on recommendations, the analytics service consumer 608 can be a management system, management service implementation, management domain, or human operator who accepts or rejects the recommendations. In some embodiments, recommendations may include (but are not limited to) one or more of the following: replacing the ME; isolating and / or isolating the ME; deactivating and / or deleting the ME; and / or observing and / or collecting relevant and / or detailed data from the ME (e.g., to help identify and / or classify the type of anomalous behavior, anomalous state, and / or anomalous cause).

[0062] Figure 7 This is a communication diagram illustrating one embodiment of communication 700 based on management services. Communication 700 includes communications transmitted between ME 702, performance measurement collection 704 (or performance measurement streaming service producer), analysis service producer 706 (e.g., anomaly detection service producer), orchestration service producer 708, and asset configuration producer 710. As used herein, any of communication 700 may contain one or more messages.

[0063] In the first communication 712 transmitted between ME 702, performance measurement collection 704, and analysis service producer 706, performance measurement collection 704 may collect streaming and / or file-based data from the managed entity and periodically report it to analysis service producer 706 for analysis. The periods for data collection, data streaming, or analysis may all be different.

[0064] Analysis service producers 706 (such as anomaly detection service producers) can use this data analysis 714 to analyze managed entities with behavioral anomalies, anomalies in ME settings, and / or anomalies in ME operations.

[0065] In some embodiments, MEs exhibiting anomalous behavior may optionally be identified 716 by the analytics service producer 706. Specifically, anomalous MEs (e.g., NFs) may be identified 718 by the analytics service producer 706. For example, the analytics service producer 706 may identify changes in traffic behavior in terms of the number of connections, throughput, and / or unexpected protocol requests (e.g., if all NFs are sending 15GB of data per hour and a similar NF example NF1 is sending 100GB of data per hour in the same period, then NF1 may be identified by the analytics service as an anomalous NF. This could be because NF1 is using a previously faulty version of software that has not been updated).

[0066] In a second communication 720 from analytics service producer 706 to orchestration service producer 708, analytics service producer 706 issues a notification that may include: an identifier of the erroneous behavior and / or compromised ME; and / or a recommended action, such as a software update to the latest version. In some embodiments, the consumer of this notification may include a dashboard or management log system of a human operator.

[0067] In the third communication 722 from orchestration service producer 708 to analysis service producer 706, orchestration service producer 708 responds to the notification, thereby accepting the recommendation from analysis service producer 706.

[0068] In the fourth communication 724 from orchestration service producer 708 to resource configuration service producer 710, orchestration service producer 708 may use resource configuration service producer 710 to: deploy a replacement ME for ME 702; deactivate and / or uninstall ME 702; update the ME 702 software installation in ME 702; redeploy the replacement ME 702, which may include state transfer (if applicable). In some embodiments, the fourth communication 724 may include the applicable state or session of ME 702 to be transferred to the new ME. As will be understood, no state transfer may imply that the new ME will be instantiated with the same responsibilities as ME 702 without any state or session being transferred.

[0069] In the fifth communication 726 transmitted from the resource configuration service producer 710 to the ME 702, the resource configuration service producer 710 may send a deactivation, termination, and / or unload request to the ME 702 (or the ME's component management system) while potentially saving its state and / or session for later analysis.

[0070] In various embodiments, the resource configuration service producer 710 may update the software version of ME 702. In the sixth communication 730 transmitted from the resource configuration service producer 710 to the ME-R 732, the ME-R 732 is replaced by the resource configuration service producer 710, and relevant knowledge from the ME 702 (e.g., status and session) may be applied. The sixth communication 730 may include information for deploying the ME-R 732 as a replacement for the ME 702.

[0071] In some embodiments, for example Figure 7 In the embodiments described herein, orchestration service producer 708 can be configured as a consumer of analytics services. Resource allocation service producer 710 or another service responsible for the software management of ME 702 can directly consume recommendations from analytics service producer 706 transmitted to orchestration service producer 708.

[0072] Figure 8This is a communication diagram illustrating another embodiment of a management service-based communication 800. Communication 800 includes communications transmitted between ME802 (e.g., SMF), Performance Assurance Service Producer 804, MDAS Producer 806 (e.g., MDAF), and Deployment Service Producer 808. As used herein, any of the communications 800 may contain one or more messages.

[0073] In the first communication 810 transmitted between ME 802, Performance Assurance Service Producer 804, and MDAS Producer 806, Performance Assurance Service Producer 804 periodically collects streaming and / or file-based data from the managed entity (e.g., ME 802) and periodically reports it to MDAS Producer 806 for analysis. The periods for data collection, streaming, or analysis can all be different.

[0074] MDAS producer 806 uses this data to analyze managed entities exhibiting abnormal behavior (812).

[0075] In some embodiments, MEs exhibiting anomalous behavior may optionally be identified by MDAS producer 806. Specifically, anomalous MEs (e.g., NSIs) are identified 816. For example, if all NSIs of a similar type experience a PDU session setup failure rate X per hour, and another similar NSI (i.e., NSI1) experiences 10 times the PDU session setup failure rate within the same period, then NSI1 may be identified as an anomalous ME by the analysis service of MDAS producer 806. In this instance, the cause may be determined to be that NSI1 (ME 802) uses SMF software from vendor A, while all other NSIs use software from vendor B.

[0076] In a second communication 818 transmitted from MDAS producer 806 to deployment service producer 808, MDAS producer 806 issues a notification that may include: an identifier of an erroneous behavior ME (e.g., ME 802); and / or a recommended action, such as replacing ME 802 with a software image from vendor B. In some embodiments, the consumer of the notification may include a dashboard or management record system of a human operator.

[0077] In the third communication 820 from the deployment service producer 808 to the MDAS producer 806, the deployment service producer 808 responds to the notification, thereby accepting the recommendation of the MDAS producer 806.

[0078] In some embodiments, during a fourth communication 822 from the deployment service producer 808 to the ME 802, the deployment service producer 808 deactivates, terminates, and / or deletes the ME 802. In various embodiments, information regarding the state of the ME 802 and other example-specific information may be stored.

[0079] In various embodiments, in the fifth communication 824 from the deployment service producer 808 to the ME-R 826 (e.g., SMF-R), the deployment service producer 808 creates a new NF instance from software, for example, from vendor B.

[0080] In some embodiments, in a sixth communication 828 from the deployment service producer 808 to the ME-R 826, the deployment service producer 808 may transmit status and session information from the deleted ME 802 to the ME-R 826 after the ME-R 826 is created.

[0081] In some embodiments, the management analytics entity may automatically identify managed entities exhibiting abnormal behavior (e.g., software management issues) based on collected data. In various embodiments, the management analytics entity may use a management domain, management service producer, or management system that provides the functionality to take action (e.g., update the software or firmware version of the managed entity). In some embodiments, to limit service interruptions to current interactions with other network functions, triggers may be initiated to initiate a recovery process for the managed entity, allowing for a smooth replacement of the managed entity to take further action.

[0082] In some embodiments, the identification and / or resolution of anomalous managed entities can free operators from routine tasks and prevent network problems and / or other issues that may not have been identified during testing due to improper use, malicious, incompatible, or error-prone versions of managed entities (e.g., software versions).

[0083] Figure 9 This is a flowchart illustrating one embodiment of a method 900 for determining network system problems. In some embodiments, method 900 is performed by a device such as network unit 104. In some embodiments, method 900 may be performed by a processor that executes programmed code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, or the like.

[0084] In various embodiments, method 900 includes determining 902 at a first network device that corresponds to a system problem corresponding to at least one second network device, wherein the first network device is an analysis entity in a cellular network, and the at least one second network device is a managed entity in a cellular network, and the system problem includes software problems, hardware problems, compatibility problems, interaction problems between a plurality of second network devices including at least one second network device, interaction problems between at least one second network device and another device, or some combination thereof, and wherein the analysis entity includes an entity that analyzes one or more devices to determine descriptive analysis, predictive analysis, prescriptive analysis, or some combination thereof. In various embodiments, method 900 includes providing 904 a notification indicating a system problem.

[0085] In some embodiments, determining the system problem includes determining the system problem based on the performance of the at least one second network device. In some embodiments, determining the system problem includes determining the system problem based on the current behavior of the at least one second network device, the expected behavior of the at least one second network device, the previous behavior of a device similar to the at least one second network device, or some combination thereof. In various embodiments, determining the system problem includes determining the system problem based on the current system state of the at least one second network device, the expected state of the at least one second network device, the previous system state of the at least one second network device, or some combination thereof.

[0086] In one embodiment, determining the system problem includes determining the system problem based on one or more thresholds. In some embodiments, providing a notification indicating the system problem includes transmitting: at least one identifier corresponding to the at least one second network device; at least one identifier corresponding to at least one third network device associated with the at least one second network device; an indication of the system problem; the severity of the system problem; monitored data corresponding to the system problem; a proposed solution to the system problem; information about previous occurrences of the system problem; or some combination thereof. In some embodiments, method 900 further includes implementing a solution to the system problem.

[0087] In various embodiments, the solution to the system problem includes: isolating the at least one second network device; deactivating the at least one second network device; removing the at least one second network device; replacing the at least one second network device; onboarding a replacement for the at least one second network device; configuring the replacement for the at least one second network device; deploying the replacement for the at least one second network device; activating the replacement for the at least one second network device; transmitting information corresponding to the at least one second network device to the replacement for the at least one second network device; updating the software version; changing the software version; updating the firmware version; changing the firmware version; changing the software to another implementation; or some combination thereof. In one embodiment, the information corresponding to the at least one second network device includes status information associated with the at least one second device, session information within the at least one second device, configuration information of the at least one second device, or some combination thereof. In some embodiments, a third network device is configured to perform the solution to the system problem. In some embodiments, the notification includes: a change in system status; an incorrect software version; a required correct or updated software version; an incorrect firmware version; a required correct or updated firmware version; hardware incompatibility; software incompatibility; an incorrect hardware version; a recommended solution; or some combination thereof.

[0088] In one embodiment, a method includes: determining at a first network device a system problem corresponding to at least one second network device, wherein the first network device is an analysis entity in a cellular network and the at least one second network device is a managed entity in the cellular network, and the system problem includes software problems, hardware problems, compatibility problems, interaction problems between a plurality of second network devices including the at least one second network device, interaction problems between the at least one second network device and another device, or some combination thereof, and wherein the analysis entity includes an entity that analyzes one or more devices to determine descriptive analysis, predictive analysis, prescriptive analysis, or some combination thereof; and providing a notification indicating the system problem.

[0089] In some embodiments, determining the system problem includes determining the system problem based on the performance of the at least one second network device.

[0090] In some embodiments, determining the system problem includes determining the system problem based on the current behavior of the at least one second network device, the expected behavior of the at least one second network device, the previous behavior of a device similar to the at least one second network device, or some combination thereof.

[0091] In various embodiments, determining the system problem includes determining the system problem based on the current system state of the at least one second network device, the expected state of the at least one second network device, the previous system state of the at least one second network device, or some combination thereof.

[0092] In one embodiment, determining the system problem includes determining the system problem based on one or more thresholds.

[0093] In some embodiments, the notification providing the indication of the system problem includes sending: at least one identifier corresponding to the at least one second network device; at least one identifier corresponding to at least one third network device associated with the at least one second network device; an indication of the system problem; the severity of the system problem; monitored data corresponding to the system problem; a proposed solution to the system problem; information about previous occurrences of the system problem; or some combination thereof.

[0094] In some embodiments, the method further includes implementing a solution to the system problem.

[0095] In various embodiments, the solution to the system problem includes: isolating the at least one second network device; deactivating the at least one second network device; removing the at least one second network device; replacing the at least one second network device; onboarding a replacement for the at least one second network device; configuring the replacement for the at least one second network device; deploying the replacement for the at least one second network device; activating the replacement for the at least one second network device; transmitting information corresponding to the at least one second network device to the replacement for the at least one second network device; updating the software version; changing the software version; updating the firmware version; changing the firmware version; changing the software to another implementation; or some combination thereof.

[0096] In one embodiment, the information corresponding to the at least one second network device includes status information associated with the at least one second device, session information within the at least one second device, configuration information of the at least one second device, or some combination thereof.

[0097] In some embodiments, a third network device is configured to implement the solution to the system problem.

[0098] In some embodiments, the notification includes: a change in system state; an incorrect software version; a required correct or updated software version; an incorrect firmware version; a required correct or updated firmware version; hardware incompatibility; software incompatibility; an incorrect hardware version; a recommended solution; or some combination thereof.

[0099] In one embodiment, a device includes a first network device comprising: a processor that: determines a system problem corresponding to at least one second network device, wherein the first network device is an analysis entity in a cellular network and the at least one second network device is a managed entity in the cellular network, and the system problem includes software problems, hardware problems, compatibility problems, interaction problems between a plurality of second network devices including the at least one second network device, interaction problems between the at least one second network device and another device, or some combination thereof, and wherein the analysis entity includes an entity that analyzes one or more devices to determine descriptive analysis, predictive analysis, prescriptive analysis, or some combination thereof; and provides a notification indicating the system problem.

[0100] In some embodiments, the processor determining the system problem includes the processor determining the system problem based on the performance of the at least one second network device.

[0101] In some embodiments, the processor determines the system problem by determining the system problem based on the current behavior of the at least one second network device, the expected behavior of the at least one second network device, the previous behavior of a device similar to the at least one second network device, or some combination thereof.

[0102] In various embodiments, the processor determines the system problem by determining the system problem based on the current system state of the at least one second network device, the expected state of the at least one second network device, the previous system state of the at least one second network device, or some combination thereof.

[0103] In one embodiment, the processor determines the system problem by determining the system problem based on one or more thresholds.

[0104] In some embodiments, the device further includes a transmitter, wherein the processor provides a notification indicating the system problem comprising the transmitter transmitting: at least one identifier corresponding to the at least one second network device; at least one identifier corresponding to at least one third network device associated with the at least one second network device; an indication of the system problem; the severity of the system problem; monitored data corresponding to the system problem; a proposed solution to the system problem; information about previous occurrences of the system problem; or some combination thereof.

[0105] In some embodiments, the processor implements a solution to the system problem.

[0106] In various embodiments, the solution to the system problem includes: isolating the at least one second network device; deactivating the at least one second network device; removing the at least one second network device; replacing the at least one second network device; onboarding a replacement for the at least one second network device; configuring the replacement for the at least one second network device; deploying the replacement for the at least one second network device; activating the replacement for the at least one second network device; transmitting information corresponding to the at least one second network device to the replacement for the at least one second network device; updating the software version; changing the software version; updating the firmware version; changing the firmware version; changing the software to another implementation; or some combination thereof.

[0107] In one embodiment, the information corresponding to the at least one second network device includes status information associated with the at least one second device, session information within the at least one second device, configuration information of the at least one second device, or some combination thereof.

[0108] In some embodiments, a third network device is configured to implement the solution to the system problem.

[0109] In some embodiments, the notification includes: a change in system state; an incorrect software version; a required correct or updated software version; an incorrect firmware version; a required correct or updated firmware version; hardware incompatibility; software incompatibility; an incorrect hardware version; a recommended solution; or some combination thereof.

[0110] The embodiments may be practiced in other specific forms. The described embodiments should be considered illustrative rather than restrictive in all respects. The scope of the invention is therefore indicated by the appended claims rather than by the foregoing description. All variations derived from the equivalent meaning and scope of the claims should be included within its scope.

Claims

1. A method for managing a cellular network, performed by a first network device, the first network device being a device in the cellular network, the method comprising: Receive Session Management Function (SMF) data from at least one second network device within the cellular network, wherein the at least one second network device is a managed entity in the cellular network, and wherein the SMF data includes one or more of the following: hardware version, software vendor, hardware vendor, managed entity ME compatibility information, or ME fingerprint. Analyze the SMF data; Based on the analyzed SMF data from the at least one second network device, a system problem corresponding to the at least one second network device is determined, wherein the system problem includes software problems, hardware problems, compatibility problems, interaction problems between multiple second network devices including the at least one second network device, or interaction problems between the at least one second network device and another device, or a combination thereof, and wherein the first network device includes a Management Data Analysis Function (MDAF); Predictive analytics performed on one or more cellular network devices are used to make predictions based on the analyzed SMF data; and The system problem is indicated to a third network device using a wireless communication network service, and a proposed solution to the system problem is provided. The third network device includes an MDAF consumer.

2. The method of claim 1, wherein determining the system problem includes determining the system problem based on the performance of the at least one second network device.

3. The method of claim 1, wherein determining the system problem comprises determining the system problem based on the current behavior of the at least one second network device, the expected behavior of the at least one second network device, the previous behavior of a device similar to the at least one second network device, or a combination thereof.

4. The method of claim 1, wherein determining the system problem comprises determining the system problem based on the current system state of the at least one second network device, the expected state of the at least one second network device, the previous system state of the at least one second network device, or a combination thereof.

5. The method of claim 1, wherein determining the system problem comprises determining the system problem based on one or more thresholds.

6. The method of claim 1, wherein providing the message indicating the system problem comprises transmitting: At least one identifier corresponding to the at least one second network device; At least one identifier corresponding to at least one third network device associated with the at least one second network device; Indication of the system problem; The severity of the system problem; Monitoring data corresponding to the system problem; Information regarding previous occurrences of the system problem; or Its combination.

7. The method of claim 1, further comprising implementing the proposed solution for the system problem.

8. The method of claim 7, wherein the proposed solution to the system problem comprises: The isolation of the at least one second network device; Deactivation of at least one second network device; The removal of at least one second network device; Replace the at least one second network device; Replacement of the at least one second network device on board; The replacement of the at least one second network device is configured; The replacement of the at least one second network device is deployed; Activate the replacement of the at least one second network device; The information corresponding to the at least one second network device is transmitted to the replacement of the at least one second network device; Update the software version; Change the software version; Update firmware version; Change the firmware version; Modify the software to another implementation scheme; or Its combination.

9. The method of claim 8, wherein the information corresponding to the at least one second network device includes status information associated with the at least one second network device, session information within the at least one second network device, configuration information of the at least one second network device, or a combination thereof.

10. The method of claim 9, wherein the third network device is configured to perform the proposed solution to the system problem.

11. The method of claim 1, wherein the message comprises: Changes in system state; Incorrect software version; The correct or updated software version required; Incorrect firmware version; The required correct or updated firmware version; Hardware incompatibility; Software incompatibility; Incorrect hardware version; Recommended solution; or Its combination.

12. A first network device for managing a cellular network, the first network device being a device in the cellular network, the first network device comprising: At least one memory; and At least one processor coupled to the at least one memory and configured such that the first network device: receives Session Management Function (SMF) data from at least one second network device within the cellular network, wherein the at least one second network device is a managed entity in the cellular network, and wherein the SMF data includes one or more of hardware version, software vendor, hardware vendor, managed entity ME compatibility information, or ME fingerprint. Analyze the SMF data; Based on the analyzed SMF data from the at least one second network device, a system problem corresponding to the at least one second network device is determined, wherein the system problem includes software problems, hardware problems, compatibility problems, interaction problems between multiple second network devices including the at least one second network device, interaction problems between the at least one second network device and another device, or a combination thereof, and wherein the first network device includes a Management Data Analysis Function (MDAF). Predictive analytics performed on one or more cellular network devices are used to make predictions based on the analyzed SMF data; and The system problem is indicated to a third network device using a wireless communication network service, and a proposed solution to the system problem is provided. The third network device includes an MDAF consumer.

13. The first network device of claim 12, wherein the at least one processor is configured such that the first network device determines the system problem based on the performance of the at least one second network device.

14. The first network device of claim 12, wherein the at least one processor is configured such that the first network device determines the system problem based on the current behavior of the at least one second network device, the expected behavior of the at least one second network device, the previous behavior of a device similar to the at least one second network device, or a combination thereof.

15. The first network device of claim 12, wherein the at least one processor is configured such that the first network device determines the system problem based on the current system state of the at least one second network device, the expected state of the at least one second network device, the previous system state of the at least one second network device, or a combination thereof.

16. The first network device of claim 12, wherein the at least one processor is configured such that the first network device determines the system problem based on one or more thresholds.

17. The first network device of claim 12, further comprising a transmitter, wherein the at least one processor is configured to cause the first network device to: At least one identifier corresponding to the at least one second network device; At least one identifier corresponding to at least one third network device associated with the at least one second network device; Indication of the system problem; The severity of the system problem; Monitoring data corresponding to the system problem; Information regarding previous occurrences of the system problem; or Its combination.

18. The first network device of claim 12, wherein the at least one processor is configured such that the first network device implements the proposed solution to the system problem.

19. The first network device of claim 18, wherein the proposed solution to the system problem comprises: The isolation of the at least one second network device; Deactivation of at least one second network device; The removal of at least one second network device; Replace the at least one second network device; Replacement of the at least one second network device on board; The replacement of the at least one second network device is configured; The replacement of the at least one second network device is deployed; Activate the replacement of the at least one second network device; The information corresponding to the at least one second network device is transmitted to the replacement of the at least one second network device; Update the software version; Change the software version; Update firmware version; Change the firmware version; Modify the software to another implementation scheme; or Its combination.

20. The first network device of claim 19, wherein the information corresponding to the at least one second network device includes status information associated with the at least one second network device, session information within the at least one second network device, configuration information of the at least one second network device, or a combination thereof.

Images