CN116266923A

CN116266923A - Device for fault monitoring and management of service consumers and producers

Info

Publication number: CN116266923A
Application number: CN202211389109.XA
Authority: CN
Inventors: 乔伊·周; 姚羿志
Original assignee: Intel Corp
Current assignee: Intel Corp
Priority date: 2021-12-16
Filing date: 2022-11-08
Publication date: 2023-06-20

Abstract

The present application relates to an apparatus for use in fault monitoring and management service (MnS) consumers and producers. An apparatus for use at a fault-monitoring MnS consumer includes a processor circuit configured to cause the fault-monitoring MnS consumer to: sending a subscription request message to a fault-monitoring MnS producer, wherein the subscription request message is used for requesting subscription to a fault alarm notification associated with a Network Function (NF) in a mobile network; and receiving a subscription response message from the fault-monitoring MnS producer, wherein the subscription response message contains information indicating whether the fault-monitoring MnS producer successfully created a new subscription for the fault alert notification.

Description

Device for fault monitoring and management of service consumers and producers

Cross Reference to Related Applications

The present application is based on and claims priority from U.S. patent application Ser. No.63/290,266 filed on 12/16 of 2021, the entire contents of which are incorporated herein by reference.

Technical Field

Embodiments of the present disclosure relate generally to the field of wireless communications, and more particularly, to an apparatus for use at fault monitoring management service (MnS) consumers and producers.

Background

Mobile communications have evolved from early voice systems to today's highly complex integrated communication platforms. A 5G or New Radio (NR) wireless communication system will provide various users and applications with access to information and sharing of data anytime and anywhere.

Drawings

Embodiments of the present disclosure will be illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings in which like reference numerals refer to similar elements.

Fig. 1 illustrates a block diagram of an example edge computing network, according to some embodiments of the disclosure.

Fig. 2A illustrates a flowchart of an example method for fault monitoring MnS consumers in accordance with some embodiments of the present disclosure.

Fig. 2B illustrates a flowchart of an example method for fault monitoring MnS producers according to some embodiments of the present disclosure.

Fig. 2C illustrates a schematic diagram of an example deployment of fault-monitoring MnS, according to some embodiments of the present disclosure.

Fig. 2D illustrates a timing diagram of an example process for an ECSP management system to receive a fault alert notification associated with NF in a mobile network from a PLMN management system using fault monitoring MnS, according to some embodiments of the present disclosure.

Fig. 3A illustrates a flowchart of another example method for fault monitoring MnS consumers according to some embodiments of the present disclosure.

Fig. 3B illustrates a flowchart of another example method for fault monitoring MnS producers according to some embodiments of the present disclosure.

Fig. 3C illustrates a schematic diagram of another example deployment of fault-monitoring MnS, according to some embodiments of the present disclosure.

Fig. 3D illustrates a timing diagram of an example process for a PLMN management system to receive fault alert notifications associated with NF and/or ECS in an EDN from an ECSP management system using fault monitoring MnS, according to some embodiments of the present disclosure.

Fig. 4 illustrates a schematic diagram of a network in accordance with various embodiments of the present disclosure.

Fig. 5 illustrates a schematic diagram of a wireless network in accordance with various embodiments of the present disclosure.

Fig. 6 illustrates a block diagram of components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein, in accordance with various embodiments of the disclosure.

Detailed Description

Various aspects of the illustrative embodiments will be described using terms commonly employed by those skilled in the art to convey the substance of the disclosure to others skilled in the art. However, it will be apparent to those skilled in the art that many alternative embodiments may be implemented using portions of the described aspects. For purposes of explanation, specific numbers, materials, and configurations are set forth in order to provide a thorough understanding of the illustrative embodiments. It will be apparent, however, to one skilled in the art that alternative embodiments may be practiced without these specific details. In other instances, well-known features may be omitted or simplified in order not to obscure the illustrative embodiments.

Furthermore, various operations will be described as multiple discrete operations in turn, in a manner that is most helpful in understanding the illustrative embodiments; however, the order of description should not be construed as to imply that these operations are necessarily order dependent. In particular, these operations need not be performed in the order of presentation.

The phrases "in an embodiment," "in one embodiment," and "in some embodiments" are repeated herein. These phrases generally do not refer to the same embodiment; however, they may also refer to the same embodiments. The terms "comprising," "having," and "including" are synonymous, unless the context dictates otherwise. The phrases "A or B" and "A/B" mean "(A), (B), or (A and B)".

Fig. 1 illustrates a block diagram of an example edge computing network, according to some embodiments of the disclosure. As shown in fig. 1, the edge computing network 100 includes a mobile network 102, edge Data Networks (EDNs) 104 and 106, and an Edge Computing Server (ECS) 108, wherein the mobile network 102 is owned by a Public Land Mobile Network (PLMN) operator, and the EDNs 104 and 106 are owned by one or more Edge Computing Service Providers (ECSPs).

In the edge computing network 100, the EDNs 104 are trusted by PLMN operators, and Edge Application Servers (EAS) 104-2 and Edge Enable Servers (EES) 104-4 in the EDNs 104 act as trusted Application Functions (AFs) to interface with Policy Control Functions (PCFs) 102-2 in the mobile network 102 through an N5 reference point. However, in existing edge application enabled architectures, the EAS 104-2 and EES 104-4 will interface with the PCF 102-2 via the edge-7 and edge-2 interfaces to request, via the PCF 102-2, session Management Function (SMF) 102-4 in the mobile network 102 to route Edge Computing (EC) application data from User Equipment (UE) to the EAS 104-2 via User Plane Functions (UPF) 102-6 and N6 reference points in the mobile network 102.

In the edge computing network 100, the EDNs 106 are not trusted by the PLMN operator, and the EAS 106-2 and EES 106-4 in the EDNs 106 not only act as untrusted AFs interfacing with the network open function (NEF)/service capability open function (SCEF) 102-8 in the mobile network 102 through the N33 reference point, but also interface with the NEF/SCEF 102-8 through the edge-7 and edge-2 interfaces to request the SMF 102-4 through the PCF 102-2 to route EC application data from the UE to the EAS 106-2 through the UPF 102-10 and N6 reference points in the mobile network 102.

In the edge computing network 100, the ECS 108 is connected to the NEF/SCEF 102-8 via an N33 or edge-8 interface and to the EES 104-4 and EES 106-4 via an edge-6 interface.

As shown in fig. 1, end-to-end edge computation requires cooperation between the mobile network and Network Functions (NF) in the EDN, such as UPF, PCF, NEF/SCEF, EAS, and EES. Any failure of some NFs in the mobile network can affect NFs in the EDN. Accordingly, it is necessary for a Public Land Mobile Network (PLMN) management system to report to an Edge Computing Service Provider (ECSP) management system a failure alarm detected from NFs in the mobile network that are associated with NFs in the EDN. However, no solution currently exists for ECSP management systems and PLMN management systems to exchange information about failure alarms detected from NFs required to support edge computing applications.

In view of the above, the present disclosure proposes a fault monitoring management service (MnS) to exchange information about fault alarms detected from NFs required to support edge computing applications between an ECSP management system and a PLMN management system.

FIG. 2A illustrates a flowchart of an example method for fault monitoring MnS consumers (MnS-C) according to some embodiments of the present disclosure. As shown in fig. 2A, a method 200A for fault monitoring MnS consumers includes: S202A, sending a first subscription request message to a fault monitoring MnS producer (MnS-P), wherein the first subscription request message is used for requesting subscription to a first fault alarm notification associated with NF in a mobile network; and S204A, receiving a first subscription response message from the fault-monitoring MnS producer, wherein the first subscription response message contains information indicating whether the fault-monitoring MnS producer successfully creates a new subscription for the first fault alert notification.

In some embodiments, the method 200A may further comprise: when the fault-monitoring MnS producer successfully creates a new subscription for the first fault-alert notification, the first fault-alert notification is received from the fault-monitoring MnS producer, wherein the first fault-alert notification is to indicate a new fault alert detected by the fault-monitoring MnS producer from the NF in the mobile network.

Fig. 2B illustrates a flowchart of an example method for fault monitoring MnS producers according to some embodiments of the present disclosure. As shown in fig. 2A, a method 200B for fault monitoring MnS producers includes: S202B, receiving a first subscription request message from a fault monitoring MnS consumer, wherein the first subscription request message is used for requesting subscription to a first fault alert notification associated with NF in the mobile network; S204B, creating a new subscription for the first fault alarm notification; and S206B, sending a first subscription response message to the fault-monitoring MnS consumer, wherein the first subscription response message contains information indicating whether the fault-monitoring MnS producer successfully creates a new subscription for the first fault alert notification.

In some embodiments, the method 200B may further comprise: detecting a new failure alarm from NF in the mobile network after successfully creating a new subscription for the first failure alarm notification; and sending a first fault alert notification to the fault-monitoring MnS consumer, wherein the first fault alert notification is to indicate a new fault alert detected from the NF in the mobile network.

Fig. 2C illustrates a schematic diagram of an example deployment of fault-monitoring MnS, according to some embodiments of the present disclosure. As shown in fig. 2C, the fault-monitoring MnS consumer is implemented in the ECSP management system, the fault-monitoring MnS producer is implemented in the PLMN management system, and the fault-monitoring MnS may implement the transmission of a first fault alert notification associated with NF in the mobile network from the PLMN management system to the ECSP management system after implementing the

methods

200A and 200B shown in fig. 1 and 2.

In some embodiments, the first subscription request message may include a first filtering parameter specifying a first filtering constraint that the fault monitoring MnS producer will use to filter fault alert notifications associated with NFs in the mobile network.

In some embodiments, NF and EDN in the mobile network (which together with the mobile network form at least part of the edge computing network) are related. For example, the NF may be any of PCF, UPF, NEF, and SCEF associated with EDN in a mobile network.

In some embodiments, when the NF and the EDN in the mobile network (which together with the mobile network forms at least a part of the edge computing network) are not related, the first subscription request message contains a base object class parameter specifying a NF class to which the NF in the mobile network belongs or a base object instance parameter specifying the NF in the mobile network, wherein the base object instance parameter may be a Domain Name (DN) for identifying the NF in the mobile network.

Fig. 3A illustrates a flowchart of another example method for fault monitoring MnS consumers according to some embodiments of the present disclosure. As shown in fig. 3A, a method 300A for fault monitoring MnS consumers includes: S302A, sending a second subscription request message to a fault monitoring MnS producer, wherein the second subscription request message is used for requesting subscription to a second fault alarm notification associated with NF or ECS in the EDN; and S304A, receiving a second subscription response message from the fault-monitoring MnS producer, wherein the second subscription response message contains information indicating whether the fault-monitoring MnS producer successfully creates a new subscription for the second fault alert notification.

In some embodiments, the method 300A may further comprise: a second fault alert notification is received from the fault-monitoring MnS producer, wherein the second fault alert notification is to indicate a new fault alert detected by the fault-monitoring MnS producer from the NF or ECS in the EDN.

Fig. 3B illustrates a flowchart of another example method for fault monitoring MnS producers according to some embodiments of the present disclosure. As shown in fig. 3B, a method 300B for fault monitoring MnS producers includes: S302B, receiving a second subscription request message from the fault monitoring MnS consumer, wherein the second subscription request message is used for requesting subscription to a second fault alert notification associated with NF or ECS in the EDN; S304B, creating a new subscription for the second fault alarm notification; and S306B, sending a second subscription response message to the fault-monitoring MnS consumer, wherein the second subscription response message contains information indicating whether a new subscription for the second fault alert notification was successfully created.

In some embodiments, the method 300B may further comprise: detecting a new fault alert from the NF or ECS in the EDN; and sending a second fault alert notification to the fault-monitoring MnS consumer, wherein the second fault alert notification is to indicate a new fault alert detected from the NF or ESC in the EDN.

Fig. 3C illustrates a schematic diagram of another example deployment of fault-monitoring MnS, according to some embodiments of the present disclosure. As shown in fig. 3B, the fault-monitoring MnS consumer is implemented in the PLMN management system and the fault-monitoring MnS producer is implemented in the ECSP management system, the fault-monitoring MnS may enable transmission of a second fault alert notification associated with NF or ECS in the EDN from the ECSP management system to the PLMN management system after implementing the

methods

300A and 300B shown in fig. 3A-3B.

In some embodiments, the second subscription request message may include a second filtering parameter specifying a second filtering constraint that the fault monitoring MnS producer will use to filter fault alert notifications associated with NF or ECS in the EDN.

It should be appreciated that the fault-monitoring MnS may implement subscription-related steps in methods 200A-200B and/or methods 300A-300B to enable a fault-monitoring MnS producer to receive first and/or second fault alert notifications from a fault-monitoring MnS consumer, and that subscription-related steps in methods 200A-200B and methods 300A-300B may be collectively referred to as subscription operations. The fault-monitoring MnS consumer may invoke a subscription operation to receive the first fault alert notification and/or the second fault alert notification from the fault-monitoring MnS producer.

Fig. 2D illustrates a timing diagram of an example process for an ECSP management system to receive a fault alert notification associated with NF in a mobile network from a PLMN management system using fault monitoring MnS, according to some embodiments of the present disclosure. As shown in fig. 2D, the fault-monitoring MnS consumer is implemented in an ECSP management system, the fault-monitoring MnS producer is implemented in a PLMN management system, and the process 200D of the ECSP management system using the fault-monitoring MnS to receive fault alert notifications associated with NFs in a mobile network from the PLMN management system includes:

S202D: the ECSP management system performs a subscription operation as a fault monitoring MnS consumer to subscribe to fault alert notifications associated with NFs in the mobile network.

S204D: the PLMN management system detects fault alarms from NFs in the mobile network as a fault monitoring MnS producer.

S206D: the PLMN management system transmits a fault alert notification associated with NF in the mobile network (i.e., a notification associated with a fault alert detected from NF in the mobile network) to the ECSP management system as a fault monitoring MnS producer through a notification new alert (notify alarm) notification to indicate the detected fault alert.

As can be seen from fig. 2A-2D, fault monitoring MnS may be implemented such that the ECSP management system is able to receive fault alert notifications from the PLMN management system that are associated with NFs in the mobile network that may affect the performance of NFs and/or ECSs in the EDNs, such that the ECSP management system may correlate the fault alert notifications associated with those NFs in the mobile network to determine root causes of poor performance of one or more NFs and/or ECSs in the EDNs. In particular, the ECSP management system may receive a fault alert notification associated with an NF in the mobile network from the PLMN management system by using the fault monitoring MnS consumer subscription, and the PLMN management system may send the fault alert notification associated with the NF in the mobile network to the ECSP management system by using the fault monitoring MnS producer upon detecting a fault alert from the NF in the mobile network.

Fig. 3D illustrates a timing diagram of an example process for a PLMN management system to receive fault alert notifications associated with NF and/or ECS in an EDN from an ECSP management system using fault monitoring MnS, according to some embodiments of the present disclosure. As shown in fig. 3D, the fault-monitoring MnS consumer is implemented in a PLMN management system, the fault-monitoring MnS producer is implemented in an ECSP management system, and the process 300D for the PLMN control system to receive fault alert notifications associated with NF and/or ECS in the EDN from the ECSP control system using the fault-monitoring MnS includes:

S302D: the PLMN management system performs a subscription operation as a fault monitoring MnS consumer to subscribe to fault alert notifications associated with NF and/or ECS in the EDN.

S304D: the ECSP management system detects fault alarms as fault monitoring MnS producers from NF and/or ECS in the EDN.

S306D: the ECSP management system sends fault alert notifications associated with NF and/or ECS in the EDN (i.e., notifications associated with fault alerts detected from NF and/or ECS in the EDN) as fault monitoring MnS producers through NotifyNewAlarm notifications to the PLMN management system to indicate detected fault alerts.

As can be seen from fig. 3A-3D, fault monitoring MnS may be implemented such that the PLMN management system is able to receive fault alert notifications associated with NF and/or ECS in the EDN from the ECSP management system such that the PLMN management system may correlate fault alert notifications associated with NF and/or ECS in the EDN to determine root causes of problems with one or more NF in the mobile network. Specifically, the PLMN management system may receive fault alert notifications associated with NF and/or ECS in the EDN from the ECSP management system by using fault monitoring MnS consumer subscriptions, and the ECSP management system may send fault alert notifications associated with NF and/or ECS in the EDN to the PLMN management system by using fault monitoring MnS producers when fault alerts are detected from NF and/or ECS in the EDN.

Table 1 shows an example list of parameters to be included in the subscription request message.

TABLE 1

In some embodiments, the subscription request message may be implemented as an HTTP POST request and the subscription response message may be implemented as an HTTP POST response. An example procedure for subscribing to a fault alert notification is as follows:

-the fault monitoring MnS consumer sends an HTTP POST request to the fault monitoring MnS producer. In an HTTP POST request, a Uniform Resource Identifier (URI) identifies a "…/subscription" aggregate resource, the query component does not exist or contains the DN of the NF for which the fault alert notification can be generated, and the request message body carries a data structure containing the filter criteria and the consumer side URI, wherein the fault monitoring MnS producer will then send a fault alert notification to the consumer side URI regarding events that match the filter criteria.

-the fault-monitoring MnS producer creates a new subscription for fault-management-related notifications and creates a resource representing the subscription.

-the fault-monitoring MnS production sends an HTTP POST response to the fault-monitoring MnS consumer, wherein:

if successful, it should return "201 created". In an HTTP POST response, the response message body carries a representation of the created resource and the location header carries the URI of the created resource.

If it fails, the appropriate error code should be returned. The response message body may carry additional error information.

Fig. 4-5 illustrate various systems, devices, and components that may implement aspects of the disclosed embodiments.

Fig. 4 illustrates a schematic diagram of a network 400, according to various embodiments of the present disclosure. The network 400 may operate in accordance with the 3GPP technical specifications of a Long Term Evolution (LTE) or 5G/NR system. However, the example embodiments are not limited in this respect and the described embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems, and the like.

The network 400 may include a UE 402, which may include any mobile or non-mobile computing device designed to communicate with a Radio Access Network (RAN) 404 via an over-the-air connection. The UE 402 may be, but is not limited to, a smart phone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment device, in-vehicle entertainment device, dashboard, heads-up display device, on-board diagnostic device, dashboard mobile device, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, network device, machine-to-machine (M2M) or device-to-device (D2D) device, internet of things (IoT) device, etc.

In some embodiments, the network 400 may include multiple UEs directly coupled to each other through a side link interface. The UE may be an M2M/D2D device that communicates using a physical sidelink channel (e.g., without limitation, a Physical Sidelink Broadcast Channel (PSBCH), a Physical Sidelink Discovery Channel (PSDCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Control Channel (PSCCH), a physical sidelink substrate channel (PSFCH), etc.).

In some embodiments, the UE 402 may also communicate with an Access Point (AP) 406 over an over-the-air connection. The AP 406 may manage Wireless Local Area Network (WLAN) connections, which may be used to offload some/all network traffic from the RAN 404. The connection between the UE 402 and the AP 406 may be consistent with any IEEE 802.11 protocol, where the AP 406 may be wireless fidelity

And a router. In some embodiments, the UE 402, RAN 404, and AP 406 may utilize cellular WLAN aggregation (e.g., LTE-WLAN aggregation (LWA)/lightweight IP (L)WIP). Cellular WLAN aggregation may involve configuring the UE 402 by the RAN 404 to utilize both cellular radio resources and WLAN resources.

RAN 404 may include one or more access nodes, such as AN Access Node (AN) 408. The AN 408 may terminate the air interface protocol of the UE 402 by providing access layer protocols including Radio Resource Control (RRC) protocol, packet Data Convergence Protocol (PDCP), radio Link Control (RLC) protocol, medium Access Control (MAC) protocol, and L1 protocol. In this way, the AN 408 may enable a data/voice connection between the Core Network (CN) 420 and the UE 402. In some embodiments, AN 408 may be implemented in a discrete device or as one or more software entities running on a server computer (as part of a virtual network, which may be referred to as a distributed RAN (CRAN) or virtual baseband unit pool, for example). The AN 408 may be referred to as a Base Station (BS), a next generation base station (gNB), a RAN node, AN evolved node B (eNB), a next generation eNB (ng-eNB), a node B (NodeB), a roadside unit (RSU), a transmission reception point (TRxP), a transmission point (TRP), and the like. The AN 408 may be a macrocell base station or a low power base station for providing a microcell, picocell, or other similar cell having a smaller coverage area, smaller user capacity, or higher bandwidth than the macrocell.

In embodiments where the RAN 404 includes multiple ANs, the ANs may be coupled to each other through AN X2 interface (if the RAN 404 is AN LTE RAN) or AN Xn interface (if the RAN 404 is a 5G RAN). In some embodiments, the X2/Xn interface, which may be separated into control/user plane interfaces, may allow the AN to communicate information related to handoff, data/context transfer, mobility, load management, interference coordination, etc.

The AN of the RAN 404 may respectively manage one or more cells, groups of cells, component carriers, etc. to provide the UE 402 with AN air interface for network access. The UE 402 may be connected simultaneously with multiple cells provided by the same or different ANs of the RAN 404. For example, the UE 402 and the RAN 404 may use carrier aggregation to allow the UE 402 to connect with multiple component carriers, each component carrier corresponding to a primary cell (PCell) or a secondary cell (SCell). In a dual connectivity scenario, a first AN may be a primary node providing a primary cell group (MCG) and a second AN may be a secondary node providing a Secondary Cell Group (SCG). The first/second AN may be any combination of eNB, gNB, ng-enbs, etc.

RAN 404 may provide an air interface on licensed spectrum or unlicensed spectrum. To operate in unlicensed spectrum, a node may use License Assisted Access (LAA), enhanced LAA (eLAA), and/or further enhanced LAA (feLAA) mechanisms based on Carrier Aggregation (CA) techniques of PCell/Scell. Prior to accessing the unlicensed spectrum, the node may perform a medium/carrier sensing operation based on, for example, a Listen Before Talk (LBT) protocol.

In a vehicle-to-everything (V2X) scenario, the UE 402 or AN 408 may be or act as a roadside unit (RSU), which may refer to any transport infrastructure entity for V2X communications. The RSU may be implemented in or by a suitable AN or stationary (or relatively stationary) UE. An RSU implemented in or by a UE may be referred to as a "UE-type RSU"; an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU"; RSUs implemented in or by next generation nodebs (gnbs) may be referred to as "gNB-type RSUs" or the like. In one example, the RSU is a computing device coupled with a radio frequency circuit located at the roadside that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications/software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may provide very low latency communications required for high speed events (e.g., collision avoidance, traffic alerts, etc.). Additionally or alternatively, the RSU may provide other cellular/WLAN communication services. The components of the RSU may be enclosed in a weather-proof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., ethernet) to a traffic signal controller or backhaul network.

In some embodiments, the RAN 404 may be an LTE RAN 410, including an evolved node B (eNB), such as eNB 412. The LTE RAN 410 may provide an LTE air interface with the following characteristics: subcarrier spacing (SCS) of 15 kHz; a single carrier frequency division multiple access (SC-FDMA) waveform for the Uplink (UL) and a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform for the Downlink (DL); turbo codes for data, tail Biting Convolutional Codes (TBCCs) for control, and the like. The LTE air interface may rely on channel state information reference signals (CSI-RS) for CSI acquisition and beam management; PDSCH/PDCCH demodulation is performed in dependence on Physical Downlink Shared Channel (PDSCH)/Physical Downlink Control Channel (PDCCH) demodulation reference signals (DMRS); and relying on Cell Reference Signals (CRS) for cell search and initial acquisition, channel quality measurements, and channel estimation, and on channel estimation for coherent demodulation/detection at the UE. The LTE air interface may operate on the 6GHz sub-band.

In some embodiments, RAN 404 may be a Next Generation (NG) -RAN 414 with a gNB (e.g., gNB 416) or gn-eNB (e.g., NG-eNB 418). The gNB416 may connect with 5G enabled UEs using a 5G NR interface. The gNB416 may connect with the 5G core through a NG interface, which may include an N2 interface or an N3 interface. The NG-eNB 418 may also connect with the 5G core over the NG interface, but may connect with the UE over the LTE air interface. The gNB416 and the ng-eNB 418 may be connected to each other via an Xn interface.

In some embodiments, the NG interface may be divided into two parts, an NG user plane (NG-U) interface that carries traffic data between the nodes of the UPF 448 and NG-RAN 414 (e.g., an N3 interface) and an NG control plane (NG-C) interface that is a signaling interface between the access and mobility management function (AMF) 444 and the nodes of the NG-RAN 414 (e.g., an N2 interface).

NG-RAN 414 may provide a 5G-NR air interface having the following characteristics: a variable SCS; cyclic prefix-orthogonal frequency division multiplexing (CP-OFDM) for DL, CP-OFDM for UL, and DFT-s-OFDM; polarity, repetition, simplex, and reed-muller codes for control; and a low density parity check code (LDPC) for data. The 5G-NR air interface may rely on channel state reference signals (CSI-RS), PDSCH/PDCCH demodulation reference signals (DMRS) like the LTE air interface. The 5G-NR air interface may not use Cell Reference Signals (CRSs), but may use Physical Broadcast Channel (PBCH) demodulation reference signals (DMRS) for PBCH demodulation; phase tracking of PDSCH using Phase Tracking Reference Signals (PTRS); and performing time tracking using the tracking reference signal. The 5G-NR air interface may operate on an FR1 band including a 6GHz sub-band or an FR2 band including 24.25GHz to 52.6GHz bands. The 5G-NR air interface may include a synchronization signal and a PBCH block (SSB), which is a region of a downlink resource grid including a Primary Synchronization Signal (PSS)/Secondary Synchronization Signal (SSS)/PBCH.

In some embodiments, the 5G-NR air interface may use bandwidth part (BWP) for various purposes. For example, BWP may be used for dynamic adaptation of SCS. For example, the UE 402 may be configured with multiple BWP, where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 402, the SCS of the transmission is also changed. Another use case of BWP relates to power saving. In particular, the UE 402 may be configured with multiple BWPs having different numbers of frequency resources (e.g., PRBs) to support data transmission in different traffic load scenarios. BWP containing a smaller number of PRBs may be used for data transmission with smaller traffic load while allowing power saving at UE 402 and in some cases the gNB 416. BWP comprising a large number of PRBs may be used for scenarios with higher traffic load.

The RAN 404 is communicatively coupled to a CN 420 that includes network elements to provide various functions to support data and telecommunications services to clients/subscribers (e.g., users of the UE 402). The components of CN 420 may be implemented in one physical node or in a different physical node. In some embodiments, network Function Virtualization (NFV) may be used to virtualize any or all of the functions provided by the network elements of CN 420 onto physical computing/storage resources in servers, switches, and the like. The logical instance of CN 420 may be referred to as a network slice, and the logical instance of a portion of CN 420 may be referred to as a network sub-slice.

In some embodiments, CN 420 may be LTE CN 422, which may also be referred to as an Evolved Packet Core (EPC). LTE CN 422 may include a Mobility Management Entity (MME) 424, a Serving Gateway (SGW) 426, a serving General Packet Radio Service (GPRS) support node (SGSN) 428, a Home Subscriber Server (HSS) 430, a Proxy Gateway (PGW) 432, and a policy control and charging rules function (PCRF) 434, which are coupled to each other through an interface (or "reference point") as shown. The function of the elements of LTE CN 422 may be briefly described as follows.

MME 424 may implement mobility management functions to track the current location of UE 402 to facilitate paging, bearer activation/deactivation, handover, gateway selection, authentication, etc.

The SGW 426 may terminate the S1 interface towards the RAN and route data packets between the RAN and the LTE CN 422. The SGW 426 may be a local mobility anchor for inter-RAN node handover and may also provide an anchor for inter-3 GPP mobility. Other responsibilities may include lawful interception, billing, and some policy enforcement.

The SGSN 428 may track the location of the UE 402 and perform security functions and access control. In addition, SGSN 428 may perform EPC inter-node signaling for mobility between different Radio Access Technology (RAT) networks; MME 424 specified PDN and S-GW selection; MME selection for handover, etc. The S3 reference point between MME 424 and SGSN 428 may enable user and bearer information exchange for inter-3 GPP access network mobility in the idle/active state.

HSS 430 may include a database for network users that includes subscription-related information that supports network entity handling communication sessions. HSS 430 may provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, and the like. The S6a reference point between HSS 430 and MME 424 may enable the transmission of subscription and authentication data for authenticating/authorizing user access to LTE CN 420.

PGW 432 may terminate an SGi interface towards a Data Network (DN) 436 that may include an application/content server 438. PGW 432 may route data packets between LTE CN 422 and data network 436. PGW 432 may be coupled to SGW 426 via an S5 reference point to facilitate user plane tunneling and tunnel management. PGW 432 may also include nodes (e.g., PCEFs) for policy enforcement and charging data collection. In addition, the SGi reference point between PGW 432 and data network 436 may be, for example, an operator external public, private PDN, or an operator internal packet data network for providing IP Multimedia Subsystem (IMS) services. PGW 432 may be coupled with PCRF 434 via a Gx reference point.

PCRF 434 is a policy and charging control element of LTE CN 422. PCRF 434 may be communicatively coupled to application/content server 438 to determine the appropriate quality of service (QoS) and charging parameters for the service flow. PCRF 432 may provide the relevant rules to the PCEF (via Gx reference point) with the appropriate Traffic Flow Templates (TFTs) and QoS Class Identifiers (QCIs).

In some embodiments, CN 420 may be a 5G core network (5 GC) 440. The 5gc 440 may include an authentication server function (AUSF) 442, an access and mobility management function (AMF) 444, a Session Management Function (SMF) 446, a User Plane Function (UPF) 448, a Network Slice Selection Function (NSSF) 450, a network open function (NEF) 452, an NF storage function (NRF) 454, a Policy Control Function (PCF) 456, a Unified Data Management (UDM) 458, and an Application Function (AF) 460, which are coupled to each other through an interface (or "reference point") as shown. The function of the elements of the 5gc 440 may be briefly described as follows.

AUSF 442 may store data for authentication of UE 402 and process authentication related functions. AUSF 442 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5gc 440 through a reference point as shown, the AUSF 442 may also present an interface based on the Nausf service.

AMF 444 may allow other functions of 5gc 440 to communicate with UE 402 and RAN 404 and subscribe to notifications about mobility events of UE 402. The AMF 444 may be responsible for registration management (e.g., registering the UE 402), connection management, reachability management, mobility management, lawful intercept AMF related events, and access authentication and authorization. The AMF 444 may provide for the transmission of Session Management (SM) messages between the UE 402 and the SMF446 and act as a transparent proxy for routing SM messages. AMF 444 may also provide for transmission of SMS messages between UE 402 and SMSF. The AMF 444 may interact with the AUSF 442 and the UE 402 to perform various security anchoring and context management functions. Furthermore, the AMF 444 may be an end point of the RAN CP interface, which may include or be an N2 reference point between the RAN 404 and the AMF 444; the AMF 444 may act as an endpoint for NAS (N1) signaling and perform NAS ciphering and integrity protection. The AMF 444 may also support NAS signaling communications with the UE 402 over the N3 IWF interface.

The SMF 446 may be responsible for SM (e.g., tunnel management, session establishment between UPF448 and AN 408); UE IP address allocation and management (including optional authorization); selection and control of the UP function; configuring flow control at the UPF448 to route traffic to the appropriate destination; termination of the interface to the policy control function; control policy enforcement, charging, and a portion of QoS; legal interception (for SM events and interfaces to LI systems); terminating the SM portion of the NAS message; downlink data notification; initiating AN-specific SM information (sent to AN 408 over N2 by AMF 444); and determining the SSC mode of the session. SM may refer to the management of PDU sessions, and PDU session or "session" may refer to a PDU connection service that provides or enables PDU exchanges between UE 402 and data network 436.

The UPF448 may serve as an anchor for intra-RAT and inter-RAT mobility, an external PDU session point interconnected with the data network 436, and a branching point to support multi-homing PDU sessions. The UPF448 may also perform packet routing and forwarding, perform packet inspection, perform policy rules user plane parts, lawful interception packets (UP collection), perform traffic usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF to QoS flow mapping), transport layer packet tagging in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. The UPF448 may include an uplink classifier to support routing traffic flows to a data network.

NSSF 450 may select a set of network slice instances to serve UE 402. The NSSF 450 can also determine the allowed Network Slice Selection Assistance Information (NSSAI) and the mapping to subscribed individual NSSAIs (S-NSSAIs), if desired. NSSF 450 may also determine the set of AMFs to use for serving UE 402, or a list of candidate AMFs, based on a suitable configuration and possibly by querying NRF 454. The selection of a set of network slice instances for UE 402 may be triggered by AMF 444 (UE 402 registers with the AMF by interacting with NSSF 450), which may result in a change of AMF. NSSF 450 may interact with AMF 444 via an N22 reference point; and may communicate with another NSSF in the visited network via an N31 reference point (not shown). In addition, NSSF 450 may expose an interface based on the Nnssf service.

NEF452 may securely disclose services and capabilities provided by 3GPP network functions for third parties, internal exposure/re-exposure, AF (e.g., AF 460), edge computing or fog computing systems, and the like. In these embodiments, NEF452 may authenticate, authorize, or restrict AF. NEF452 may also convert information exchanged with AF 460 and information exchanged with internal network functions. For example, NEF452 may translate between AF service identifiers and internal 5GC information. The NEF452 may also receive information from other NFs based on their public capabilities. This information may be stored as structured data at NEF452 or at data storage NF using a standardized interface. The NEF452 may then re-expose the stored information to other NFs and AFs, or for other purposes such as analysis. In addition, NEF452 may expose an interface based on Nnef services.

NRF 454 may support a service discovery function, receive NF discovery requests from NF instances, and provide information of the discovered NF instances to the NF instances. NRF 454 also maintains information of available NF instances and services supported by them. As used herein, the terms "instantiate," "instance," and the like may refer to creating an instance, "instance" may refer to a specific occurrence of an object, which may occur, for example, during execution of program code. Further, NRF 454 may expose an interface based on Nnrf services.

PCF 456 may provide policy rules to control plane functions to enforce these policy rules and may also support a unified policy framework to manage network behavior. PCF 456 may also implement a front end to access subscription information related to policy decisions in the UDR of UDM 458. In addition to communicating with functions through reference points as shown, PCF 456 also presents an interface based on an Npcf service.

The UDM 458 may process subscription-related information to support network entity handling communication sessions and may store subscription data for the UE 402. For example, subscription data may be communicated via an N8 reference point between the UDM 458 and the AMF 444. UDM 458 may include two parts: application front-end and User Data Record (UDR). The UDR may store policy data and subscription data for UDM 458 and PCF 456, and/or structured data and application data for NEF 452 for exposure (including PFD for application detection, application request information for multiple UEs 402). The UDR may expose an interface based on the Nudr service to allow the UDM 458, PCF 456, and NEF 452 to access specific sets of stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notifications of related data changes in the UDR. The UDM may include a UDM-FE (UDM front end) that is responsible for handling credentials, location management, subscription management, etc. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification processing, access authorization, registration/mobility management, and subscription management. In addition to communicating with other NFs through reference points as shown, the UDM 458 may also expose Nudm service based interfaces.

AF 460 may provide application impact on traffic routing, provide access to the NEF, and interact with the policy framework for policy control.

In some embodiments, the 5gc 440 may enable edge computation by selecting an operator/third party service that is geographically close to the point where the UE 402 connects to the network. This may reduce delay and load on the network. To provide edge computing implementations, the 5gc 440 may select the UPF448 in close proximity to the UE 402 and perform traffic steering from the UPF448 to the data network 436 over the N6 interface. This may be based on UE subscription data, UE location, and information provided by AF 460. Thus, AF 460 may affect UPF (re) selection and traffic routing. Based on the operator deployment, the network operator may allow the AF 460 to interact directly with the associated NF when the AF 460 is considered a trusted entity. In addition, AF 460 may expose an interface based on Naf services.

The data network 436 may represent various network operator services, internet access, or third party services that may be provided by one or more servers including, for example, an application/content server 438.

Fig. 5 illustrates a wireless network 500 in accordance with various embodiments. The wireless network 500 may include a UE 502 in wireless communication with AN 504. The UE 502 and the AN 504 may be similar to and substantially interchangeable with the synonym components described elsewhere herein.

The UE 502 may be communicatively coupled with the AN 504 via a connection 506. Connection 506 is shown as an air interface to enable communicative coupling and may operate at millimeter wave or below 6GHz frequencies in accordance with a cellular communication protocol, such as the LTE protocol or the 5G NR protocol.

The UE 502 may include a host platform 508 coupled with a modem platform 510. Host platform 508 may include application processing circuitry 512, which may be coupled with protocol processing circuitry 514 of modem platform 510. Application processing circuitry 512 may run various applications for UE 502 to acquire/receive its application data. The application processing circuitry 512 may also implement one or more layer operations to transmit/receive application data to/from the data network. These layer operations may include transport (e.g., UDP) and internet (e.g., IP) operations.

Protocol processing circuitry 514 may implement one or more layers of operations to facilitate the transmission or reception of data over connection 506. Layer operations implemented by the protocol processing circuit 514 may include, for example, medium Access Control (MAC), radio Link Control (RLC), packet Data Convergence Protocol (PDCP), radio Resource Control (RRC), and non-access stratum (NAS) operations.

Modem platform 510 may further include digital baseband circuitry 516, which digital baseband circuitry 516 may implement one or more layer operations "below" the layer operations performed by protocol processing circuitry 514 in the network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/demapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, where these functions may include one or more of space-time, space-frequency, or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.

Modem platform 510 may further include transmit circuitry 518, receive circuitry 520, RF circuitry 522, and RF front end (RFFE) circuitry 524, which may include or be connected to one or more antenna panels 526. Briefly, the transmit circuit 518 may include digital-to-analog converters, mixers, intermediate Frequency (IF) components, and the like; the receive circuitry 520 may include analog-to-digital converters, mixers, IF components, etc.; RF circuitry 522 may include low noise amplifiers, power tracking components, and the like; RFFE circuit 524 may include filters (e.g., surface/bulk acoustic wave filters), switches, antenna tuners, beam forming components (e.g., phased array antenna components), and so forth. The selection and arrangement of the components of the transmit circuit 518, receive circuit 520, RF circuit 522, RFFE circuit 524, and antenna panel 526 (collectively "transmit/receive components") may be specific to the specifics of the particular implementation, e.g., whether the communication is Time Division Multiplexed (TDM) or Frequency Division Multiplexed (FDM), at mmWave or below 6GHz frequencies, etc. In some embodiments, the transmit/receive components may be arranged in a plurality of parallel transmit/receive chains, and may be arranged in the same or different chips/modules, etc.

In some embodiments, protocol processing circuit 514 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.

UE reception may be established through and via antenna panel 526, RFFE circuitry 524, RF circuitry 522, receive circuitry 520, digital baseband circuitry 516, and protocol processing circuitry 514. In some embodiments, the antenna panel 526 may receive transmissions from the AN 504 by receiving beamformed signals received by multiple antennas/antenna elements of one or more antenna panels 526.

UE transmissions may be established via and through protocol processing circuitry 514, digital baseband circuitry 516, transmit circuitry 518, RF circuitry 522, RFFE circuitry 524, and antenna panel 526. In some embodiments, the transmit component of the UE 502 may apply spatial filtering to the data to be transmitted to form a transmit beam that is transmitted by the antenna elements of the antenna panel 526.

Similar to the UE 502, the AN 504 may include a host platform 528 coupled with a modem platform 530. Host platform 528 may include application processing circuitry 532 coupled with protocol processing circuitry 534 of modem platform 530. The modem platform may also include digital baseband circuitry 536, transmit circuitry 538, receive circuitry 540, RF circuitry 542, RFFE circuitry 544, and antenna panel 546. The components of the AN 504 may be similar to the like-named components of the UE 502 and may be substantially interchangeable with the like-named components of the UE 502. In addition to performing data transmission/reception as described above, the components of the AN 504 may perform various logic functions including, for example, radio Network Controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

Fig. 6 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein, according to some example embodiments. In particular, fig. 6 shows a schematic diagram of a hardware resource 600, the hardware resource 600 comprising one or more processors (or processor cores) 610, one or more memory/storage devices 620, and one or more communication resources 630, wherein each of these processors, memory/storage devices, and communication resources may be communicatively coupled via a bus 640 or other interface circuit. For embodiments that utilize node virtualization (e.g., network Function Virtualization (NFV)), the hypervisor 602 can be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 600.

The processor 610 may include, for example, a processor 612 and a processor 614. The processor 610 may be, for example, a Central Processing Unit (CPU), a Reduced Instruction Set Computing (RISC) processor, a Complex Instruction Set Computing (CISC) processor, a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP) such as a baseband processor, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a Radio Frequency Integrated Circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

Memory/storage 620 may include main memory, disk storage, or any suitable combination thereof. Memory/storage 620 may include, but is not limited to, any type of volatile, nonvolatile, or semi-volatile memory such as Dynamic Random Access Memory (DRAM), static Random Access Memory (SRAM), erasable Programmable Read Only Memory (EPROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory, solid state memory, and the like.

Communication resources 630 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 604 or one or more databases 606 or other network elements via network 608. For example, the communication resources 630 may include wired communication components (e.g., for coupling via USB, ethernet, etc.), cellular communication components, near Field Communication (NFC) components, and so forth,

(or->

Low energy) component, < >>

Components, and other communication components.

The instructions 650 may include software, programs, applications, applets, applications, or other executable code for causing at least any one of the processors 610 to perform any one or more of the methods discussed herein. The instructions 650 may reside, completely or partially, within at least one of the processor 610 (e.g., in a cache of the processor), the memory/storage 620, or any suitable combination thereof. Further, any portion of instructions 650 may be transferred from any combination of peripherals 604 or databases 606 to hardware resource 600. Thus, the memory of the processor 610, the memory/storage 620, the peripherals 604, and the database 606 are examples of computer readable and machine readable media.

The following paragraphs describe examples of various embodiments.

Example 1 includes an apparatus for use at a fault monitoring management service (MnS) consumer, wherein the apparatus includes a processor circuit configured to cause the fault monitoring MnS consumer to: sending a subscription request message to a fault-monitoring MnS producer, wherein the subscription request message is used for requesting subscription to a fault alarm notification associated with a Network Function (NF) in a mobile network; and receiving a subscription response message from the fault-monitoring MnS producer, wherein the subscription response message contains information indicating whether the fault-monitoring MnS producer successfully created a new subscription for the fault alert notification.

Example 2 includes the apparatus of example 1, wherein the subscription request message includes a filter parameter specifying a filter constraint that the fault-monitoring MnS producer is to use to filter fault alert notifications associated with the NF.

Example 3 includes the apparatus of example 1, wherein the NF is associated with an Edge Data Network (EDN), the EDN together with the mobile network forming at least a portion of an edge computing network.

Example 4 includes the apparatus of example 1, wherein the subscription request message contains a base object class parameter specifying a NF class to which the NF belongs or a base object instance parameter specifying the NF when the NF and an Edge Data Network (EDN) are not related, wherein the EDN together with the mobile network forms at least a portion of an edge computing network.

Example 5 includes the apparatus of example 4, wherein the base object instance parameter is a Domain Name (DN) to identify the NF.

Example 6 includes the apparatus of example 1, wherein the processor circuit is further configured to cause the fault-monitoring MnS consumer to, upon successful creation of the new subscription for the fault alert notification by the fault-monitoring MnS producer: the fault alert notification is received from the fault-monitoring MnS producer, wherein the fault alert notification is to indicate a new fault alert detected by the fault-monitoring MnS producer from the NF.

Example 7 includes the apparatus of example 1, wherein the fault-monitoring MnS consumer is implemented in an Edge Computing Service Provider (ECSP) management system and the fault-monitoring MnS producer is implemented in a Public Land Mobile Network (PLMN) management system.

Example 8 includes an apparatus for use in a fault-monitoring management service (MnS) producer, wherein the apparatus includes a processor circuit configured to cause the fault-monitoring MnS producer to: receiving a subscription request message from a fault-monitoring MnS consumer, wherein the subscription request message is for requesting subscription to a fault alert notification associated with a Network Function (NF) in a mobile network; creating a new subscription for the fault alert notification; and sending a subscription response message to the fault-monitoring MnS consumer, wherein the subscription response message contains information indicating whether the new subscription for the fault alert notification was successfully created.

Example 9 includes the apparatus of example 8, wherein the subscription request message includes a filter parameter specifying a filter constraint that the fault-monitoring MnS producer is to use to filter fault alert notifications associated with the NF.

Example 10 includes the apparatus of example 8, wherein the NF is associated with an Edge Data Network (EDN), the EDN together with the mobile network forming at least a portion of an edge computing network.

Example 11 includes the apparatus of example 8, wherein the subscription request message contains a base object class parameter specifying a NF class to which the NF belongs or a base object instance parameter specifying the NF when the NF and an Edge Data Network (EDN) are not related, the EDN together with the mobile network forming at least a portion of an edge computing network.

Example 12 includes the apparatus of example 11, wherein the base object instance parameter is a Domain Name (DN) to identify the NF.

Example 13 includes the apparatus of example 8, wherein the processor circuit is further configured to cause the fault-monitoring MnS producer to, after successfully creating the new subscription for the fault alert notification: detecting a new fault alert from the NF; and sending the fault alert notification to the fault-monitoring MnS consumer, wherein the fault alert notification is to indicate the new fault alert detected from the NF.

Example 14 includes the apparatus of example 8, wherein the fault-monitoring MnS consumer is implemented in an Edge Computing Service Provider (ECSP) management system and the fault-monitoring MnS producer is implemented in a Public Land Mobile Network (PLMN) management system.

Example 15 includes an apparatus for use at a fault monitoring management service (MnS) consumer, wherein the apparatus comprises a processor circuit configured to cause the fault monitoring MnS consumer to: sending a subscription request message to a fault-monitoring MnS producer, wherein the subscription request message is for requesting subscription to a fault alert notification associated with a Network Function (NF) or an Edge Computing Server (ECS) in an Edge Data Network (EDN); and receiving a subscription response message from the fault-monitoring MnS producer, wherein the subscription response message contains information indicating whether the fault-monitoring MnS producer successfully created a new subscription for the fault alert notification.

Example 16 includes the apparatus of example 15, wherein the subscription request message includes a filter parameter specifying a filter constraint that the fault-monitoring MnS producer is to use to filter fault alert notifications associated with the NF or the ECS.

Example 17 includes the apparatus of example 15, wherein the processor circuit is further configured to cause the fault-monitoring MnS consumer to, upon successful creation of the new subscription for the fault alert notification by the fault-monitoring MnS producer: the fault alert notification is received from the fault-monitoring MnS producer, wherein the fault alert notification is to indicate a new fault alert detected by the fault-monitoring MnS producer from the NF or the ECS.

Example 18 includes the apparatus of example 15, wherein the fault-monitoring MnS consumer is implemented in a Public Land Mobile Network (PLMN) management system and the fault-monitoring MnS producer is implemented in an Edge Computing Service Provider (ECSP) management system.

Example 19 includes an apparatus for use with a fault-monitoring management service (MnS) producer, wherein the apparatus includes a processor circuit configured to cause the fault-monitoring MnS producer to: receiving a subscription request message from a fault-monitoring MnS consumer, wherein the subscription request message is for requesting subscription to a fault alert notification associated with a Network Function (NF) or an Edge Computing Server (ECS) in an Edge Data Network (EDN); creating a new subscription for the fault alert notification; and sending a subscription response message to the fault-monitoring MnS consumer, wherein the subscription response message contains information indicating whether the new subscription for the fault alert notification was successfully created.

Example 20 includes the apparatus of example 19, wherein the subscription request message includes a filter parameter specifying a filter constraint that the fault-monitoring MnS producer is to use to filter fault alert notifications associated with the NF.

Example 21 includes the apparatus of example 19, wherein the processor circuit is further configured to cause the fault-monitoring MnS producer to, after successfully creating the new subscription for the fault alert notification: detecting a new fault alert from the NF or the ECS; and sending the fault alert notification to the fault-monitoring MnS consumer, wherein the fault alert notification is to indicate the new fault alert detected from the NF or the ESC.

Example 22 includes a method for use in a fault monitoring management service (MnS) consumer, wherein the method comprises: sending a subscription request message to a fault-monitoring MnS producer, wherein the subscription request message is used for requesting subscription to a fault alarm notification associated with a Network Function (NF) in a mobile network; and receiving a subscription response message from the fault-monitoring MnS producer, wherein the subscription response message contains information indicating whether the fault-monitoring MnS producer successfully created a new subscription for the fault alert notification.

Example 23 includes the method of example 22, wherein the subscription request message includes a filter parameter specifying a filter constraint that the fault-monitoring MnS producer is to use to filter fault alert notifications associated with the NF.

Example 24 includes the method of example 22, wherein the NF is associated with an Edge Data Network (EDN), the EDN together with the mobile network forming at least a portion of an edge computing network.

Example 25 includes the method of example 22, wherein the subscription request message contains a base object class parameter specifying a NF class to which the NF belongs or a base object instance parameter specifying the NF when the NF and an Edge Data Network (EDN) are not related, wherein the EDN together with the mobile network forms at least a portion of an edge computing network.

Example 26 includes the method of example 25, wherein the base object instance parameter is a Domain Name (DN) to identify the NF.

Example 27 includes the method of example 22, wherein the method further comprises, upon successful creation of the new subscription for the fault alert notification by the fault-monitoring MnS producer: the fault alert notification is received from the fault-monitoring MnS producer, wherein the fault alert notification is to indicate a new fault alert detected by the fault-monitoring MnS producer from the NF.

Example 28 includes the method of example 22, wherein the fault-monitoring MnS consumer is implemented in an Edge Computing Service Provider (ECSP) management system and the fault-monitoring MnS producer is implemented in a Public Land Mobile Network (PLMN) management system.

Example 29 includes a method for use in a fault monitoring management service (MnS) producer, wherein the method comprises: receiving a subscription request message from a fault-monitoring MnS consumer, wherein the subscription request message is for requesting subscription to a fault alert notification associated with a Network Function (NF) in a mobile network; creating a new subscription for the fault alert notification; and sending a subscription response message to the fault-monitoring MnS consumer, wherein the subscription response message contains information indicating whether the new subscription for the fault alert notification was successfully created.

Example 30 includes the method of example 29, wherein the subscription request message includes a filter parameter specifying a filter constraint that the fault-monitoring MnS producer is to use to filter fault alert notifications associated with the NF.

Example 31 includes the method of example 29, wherein the NF is associated with an Edge Data Network (EDN), the EDN together with the mobile network forming at least a portion of an edge computing network.

Example 32 includes the method of example 29, wherein the subscription request message contains a base object class parameter specifying a NF class to which the NF belongs or a base object instance parameter specifying the NF when the NF and an Edge Data Network (EDN) are not related, the EDN together with the mobile network forming at least a portion of an edge computing network.

Example 33 includes the method of example 32, wherein the base object instance parameter is a Domain Name (DN) to identify the NF.

Example 34 includes the method of example 29, wherein the method further comprises, after successfully creating the new subscription for the failure alert notification: detecting a new fault alert from the NF; and sending the fault alert notification to the fault-monitoring MnS consumer, wherein the fault alert notification is to indicate the new fault alert detected from the NF.

Example 35 includes the method of example 29, wherein the fault-monitoring MnS consumer is implemented in an Edge Computing Service Provider (ECSP) management system and the fault-monitoring MnS producer is implemented in a Public Land Mobile Network (PLMN) management system.

Example 36 includes a method for use in a fault monitoring management service (MnS) consumer, wherein the method comprises: sending a subscription request message to a fault-monitoring MnS producer, wherein the subscription request message is for requesting subscription to a fault alert notification associated with a Network Function (NF) or an Edge Computing Server (ECS) in an Edge Data Network (EDN); and receiving a subscription response message from the fault-monitoring MnS producer, wherein the subscription response message contains information indicating whether the fault-monitoring MnS producer successfully created a new subscription for the fault alert notification.

Example 37 includes the method of example 36, wherein the subscription request message includes a filter parameter specifying a filter constraint that the fault-monitoring MnS producer is to use to filter fault alert notifications associated with the NF or the ECS.

Example 38 includes the method of example 36, wherein the method further comprises, upon successful creation of the new subscription for the fault alert notification by the fault-monitoring MnS producer: the fault alert notification is received from the fault-monitoring MnS producer, wherein the fault alert notification is to indicate a new fault alert detected by the fault-monitoring MnS producer from the NF or the ECS.

Example 39 includes the method of example 36, wherein the fault-monitoring MnS consumer is implemented in a Public Land Mobile Network (PLMN) management system and the fault-monitoring MnS producer is implemented in an Edge Computing Service Provider (ECSP) management system.

Example 40 includes a method for use in a fault monitoring management service (MnS) producer, wherein the method comprises: receiving a subscription request message from a fault-monitoring MnS consumer, wherein the subscription request message is for requesting subscription to a fault alert notification associated with a Network Function (NF) or an Edge Computing Server (ECS) in an Edge Data Network (EDN); creating a new subscription for the fault alert notification; and sending a subscription response message to the fault-monitoring MnS consumer, wherein the subscription response message contains information indicating whether the new subscription for the fault alert notification was successfully created.

Example 41 includes the method of example 40, wherein the subscription request message includes a filter parameter specifying a filter constraint that the fault-monitoring MnS producer is to use to filter fault alert notifications associated with the NF.

Example 42 includes the method of example 40, wherein the method further comprises, after successfully creating the new subscription for the failure alert notification: detecting a new fault alert from the NF or the ECS; and sending the fault alert notification to the fault-monitoring MnS consumer, wherein the fault alert notification is to indicate the new fault alert detected from the NF or the ESC.

Example 43 includes a computer-readable storage medium having stored thereon computer-executable instructions, wherein the computer-executable instructions, when executed by processor circuitry of an apparatus for a fault monitoring management service (MnS) consumer, cause the fault monitoring MnS consumer to perform the method of any one of examples 22-28 and 36-39.

Example 44 includes a computer-readable storage medium having stored thereon computer-executable instructions, wherein the computer-executable instructions, when executed by processor circuitry of an apparatus for a fault-monitoring management service (MnS) producer, cause the fault-monitoring MnS producer to perform the method of any of examples 29-35 and 40-42.

Example 45 includes an apparatus for use at a fault monitoring management service (MnS) consumer, wherein the apparatus comprises means for performing the method of any one of examples 22-28 and 36-39.

Example 46 includes an apparatus for use in a fault monitoring management service (MnS) producer, wherein the apparatus comprises means for performing the method of any of examples 29-35 and 40-42.

Although certain embodiments have been illustrated and described herein for purposes of description, a wide variety of alternate and/or equivalent embodiments or implementations calculated to achieve the same purposes may be substituted for the embodiments shown and described without departing from the scope of the present disclosure. This application is intended to cover any adaptations or variations of the embodiments discussed herein. Accordingly, the embodiments described herein are obviously limited only by the following claims and equivalents thereof.

Claims

1. An apparatus for use at a fault monitoring management service (MnS) consumer, wherein the apparatus comprises a processor circuit configured to cause the fault monitoring MnS consumer to:

sending a subscription request message to a fault-monitoring MnS producer, wherein the subscription request message is used for requesting subscription to a fault alarm notification associated with a Network Function (NF) in a mobile network; and

A subscription response message is received from the fault-monitoring MnS producer, wherein the subscription response message contains information indicating whether the fault-monitoring MnS producer successfully created a new subscription for the fault alert notification.

2. The apparatus of claim 1, wherein the subscription request message includes a filter parameter specifying a filter constraint that the fault-monitoring MnS producer is to use to filter fault alert notifications associated with the NF.

3. The apparatus of claim 1, wherein the NF is associated with an Edge Data Network (EDN), the EDN together with the mobile network forming at least a portion of an edge computing network.

4. The apparatus of claim 1, wherein the subscription request message contains a base object class parameter specifying a NF class to which the NF belongs or a base object instance parameter specifying the NF when the NF and an Edge Data Network (EDN) are not related, wherein the EDN together with the mobile network forms at least a portion of an edge computing network.

5. The apparatus of claim 4, wherein the base object instance parameter is a Domain Name (DN) identifying the NF.

6. The apparatus of claim 1, wherein the processor circuit is further configured to cause the fault-monitoring MnS consumer to, upon successful creation of the new subscription for the fault-alert notification by the fault-monitoring MnS producer:

the fault alert notification is received from the fault-monitoring MnS producer, wherein the fault alert notification is to indicate a new fault alert detected by the fault-monitoring MnS producer from the NF.

7. The apparatus of claim 1, wherein the fault-monitoring MnS consumer is implemented in an Edge Computing Service Provider (ECSP) management system and the fault-monitoring MnS producer is implemented in a Public Land Mobile Network (PLMN) management system.

8. An apparatus for use in a fault-monitoring management service (MnS) producer, wherein the apparatus comprises a processor circuit configured to cause the fault-monitoring MnS producer to:

receiving a subscription request message from a fault-monitoring MnS consumer, wherein the subscription request message is for requesting subscription to a fault alert notification associated with a Network Function (NF) in a mobile network;

creating a new subscription for the fault alert notification; and

And sending a subscription response message to the fault-monitoring MnS consumer, wherein the subscription response message contains information indicating whether the new subscription for the fault alert notification was successfully created.

9. The apparatus of claim 8, wherein the subscription request message includes a filter parameter specifying a filter constraint that the fault-monitoring MnS producer is to use to filter fault alert notifications associated with the NF.

10. The apparatus of claim 8, wherein the NF is associated with an Edge Data Network (EDN), the EDN together with the mobile network forming at least a portion of an edge computing network.

11. The apparatus of claim 8, wherein the subscription request message contains a base object class parameter specifying a NF class to which the NF belongs or a base object instance parameter specifying the NF when the NF and an Edge Data Network (EDN) are not related, the EDN together with the mobile network forming at least a portion of an edge computing network.

12. The apparatus of claim 11, wherein the base object instance parameter is a Domain Name (DN) identifying the NF.

13. The apparatus of claim 8, wherein the processor circuit is further configured to cause the fault-monitoring MnS producer to, upon successful creation of the new subscription for the fault alert notification:

Detecting a new fault alert from the NF; and

and sending the fault alarm notification to the fault-monitoring MnS consumer, wherein the fault alarm notification is used for indicating the new fault alarm detected from the NF.

14. The apparatus of claim 8, wherein the fault-monitoring MnS consumer is implemented in an Edge Computing Service Provider (ECSP) management system and the fault-monitoring MnS producer is implemented in a Public Land Mobile Network (PLMN) management system.

15. An apparatus for use at a fault monitoring management service (MnS) consumer, wherein the apparatus comprises a processor circuit configured to cause the fault monitoring MnS consumer to:

sending a subscription request message to a fault-monitoring MnS producer, wherein the subscription request message is for requesting subscription to a fault alert notification associated with a Network Function (NF) or an Edge Computing Server (ECS) in an Edge Data Network (EDN); and

16. The apparatus of claim 15, wherein the subscription request message includes a filter parameter specifying a filter constraint that the fault-monitoring MnS producer is to use to filter fault alert notifications associated with the NF or the ECS.

17. The apparatus of claim 15, wherein the processor circuit is further configured to cause the fault-monitoring MnS consumer to, upon successful creation of the new subscription for the fault-alert notification by the fault-monitoring MnS producer:

the fault alert notification is received from the fault-monitoring MnS producer, wherein the fault alert notification is to indicate a new fault alert detected by the fault-monitoring MnS producer from the NF or the ECS.

18. The apparatus of claim 15, wherein the fault-monitoring MnS consumer is implemented in a Public Land Mobile Network (PLMN) management system and the fault-monitoring MnS producer is implemented in an Edge Computing Service Provider (ECSP) management system.

19. An apparatus for use in a fault-monitoring management service (MnS) producer, wherein the apparatus comprises a processor circuit configured to cause the fault-monitoring MnS producer to:

Receiving a subscription request message from a fault-monitoring MnS consumer, wherein the subscription request message is for requesting subscription to a fault alert notification associated with a Network Function (NF) or an Edge Computing Server (ECS) in an Edge Data Network (EDN);

creating a new subscription for the fault alert notification; and

20. The apparatus of claim 19, wherein the subscription request message includes a filter parameter specifying a filter constraint that the fault-monitoring MnS producer is to use to filter fault alert notifications associated with the NF.

21. The apparatus of claim 19, wherein the processor circuit is further configured to cause the fault-monitoring MnS producer to, upon successful creation of the new subscription for the fault alert notification:

detecting a new fault alert from the NF or the ECS; and

and sending the fault alert notification to the fault-monitoring MnS consumer, wherein the fault alert notification is to indicate the new fault alert detected from the NF or the ESC.

22. A computer-readable storage medium having stored thereon computer-executable instructions, wherein the computer-executable instructions, when executed by processor circuitry of an apparatus for use in a fault monitoring management service (MnS) consumer, cause the fault monitoring MnS consumer to:

23. The computer-readable storage medium of claim 22, wherein the subscription request message contains a base object class parameter specifying a NF class to which the NF belongs or a base object instance parameter specifying the NF when the NF and an Edge Data Network (EDN) are not related, the EDN together with the mobile network forming at least a portion of an edge computing network.

24. A computer-readable storage medium having stored thereon computer-executable instructions, wherein the computer-executable instructions, when executed by processor circuitry of an apparatus for use in a fault monitoring management service (MnS) consumer, cause the fault monitoring MnS consumer to:

25. The computer-readable storage medium of claim 24, wherein the computer-executable instructions, when executed by a processor circuit of an apparatus for the fault-monitoring MnS consumer, further cause the fault-monitoring MnS consumer to: