OA20853A - Report application programming interface (API) capability change based on API filter. - Google Patents

Abstract

Systems and methods for reporting API capability change according to an API filter are provided. According to one aspect, a method for reporting API capability change according to an API filter comprises receiving a request to be notified of an API capability change related to an identified wireless device, the request identifying a set of one or more APIs to be monitored; receiving a notification that the identified wireless device has changed from a first type of core network to a second type of core network; determining an API capability change from the first type of core network to the second type of core network for the identified set of one or more APIs to be monitored; and reporting the API capability change for the identified set of one or more APIs to be monitored and not reporting the API capability change for APIs not in the identified set.

Description

REPORT APPLICATION PROGRAMMING INTERFACE (API) CAPABILITY CHANGE BASED ON API FILTER

Technical Field

[0001] The present disclosure relates to wireless communication System and, more specifically, to Application Programming Interface (API) capability change notification based on an API filter such that a API capability change notification contains information about API capability changes for only the subset of APIs specified in an API list that was provided as part of the subscription request.

Background

[0002] Third Génération Partnership Project (3GPP) networks provide different kinds of capabilities, such as monitoring capability, provisioning capability, policy/charging capability, and analytics reporting capability, initially for Internet of Things (loT) devices. Such capability may also be used in other type of devices, such as enhanced Mobile Broadband (eMBB) User Equipment (UE). Communications networks are generally comprised of a Radio Access Network (RAN) and a Core Network (CN). The core network for Fourth Génération (4G) networks, such as Long Term Evolution (LTE) networks, is known as the Evolved Packet Core (EPC). The core network for Fifth Génération (5G) networks is known as the 5G Core (5GC). Generally speaking, télécommunication core networks are “closed,” meaning that access to the core network is tightly controlled and not avaiiable to the public. However, there can be benefits to allowing an Application Function (AF) external to the core network to hâve limited access to some of the core network fonctions and vice versa.

[0003] For this reason, both 4G networks and 5G networks include a Network Function (NF) that allows AFs or other entities outside of the core network to find out what nodes, capabilities, or features are supported by the core network. Such a network function is referred to as an “exposure function, since it exposes the otherwise hidden capabilities of the network to entities outside of the network. In EPC, this function is the Service Capability Exposure Function (SCEF), and in 5GC, this function is the Network Exposure Function (NEF). That is, a SCEF is the entry point for providing such exposure capability in EPC and a NEF is the entry point providing such exposure capability in 5GC. An AF interacts with an exposure function via a set of one or more Application Programming Interfaces (APIs).

[0004] In orderto make AF beagnosticto SCEF and NEF, starting from 3GPP Release 16, a combined exposure node is required (Le., SCEF+NEF). However, the EPC and 5GC hâve different capabilities and thus hâve different sets of APIs.

[0005] Because the combined SCEF+NEF provides exposure capability for both EPC and 5GC, an AF that uses the SCEF+NEF needstoknow whether the SCEF+NEF is an entry point into an EPC or whether it is an entry point into a 5GC. This is important, for example, in the scénario in which a UE changes from an EPC to a 5GC or vice versa, or in any other scénario where the new core network has different capabilities than the old core network had.

[0006] This issue was partially addressed in 3GPP Technical Spécification (TS) 23,501, version 5.17.6.1 (hereinafter, “TS 23.501). TS 23.501 notes the following:

• A service related with a common north-bound API may become unavailable due to the UE being served by a CN node not supporting the service. If the availability or expected level of support of a service API associated with a UE changes, for example due to mobilîty between a 5GC and an EPC, the AF shall be made aware of the change. If the Common API Framework (CAPIF) is supported, and if the service APIs become (un)available for the 5GC or EPC network, the AF obtains such information from the CAPIF core function, • If the SCEF+NEF receives the subscription requestfrom the AF for the availability or expected level of support of a service API, the SCEF+NEF subscribes a CN Type Change event for the UE or Group of UEs to the Home Subscriber Server (HSS) + Unified Data Management (UDM) node (HSS+UDM). If the HSS+UDM receives a subscription for a CN Type Change event, the HSS+UDM includes the latest CN type for the UE or group of UEs in the response for the subscription.

• If the HSS+UDM detects that the UE switches between being served by an MME (in EPC) and being served by an AMF (in 5GC), the CN Type Change event is triggered, and the HSS+UDM notifies the latest CN type for the UE or group of UEs to the SCEF+NEF. Based on the CN type information, the SCEF+NEF can détermine the availability or expected level of support of a given service. The AF will be informed of such information via a subscription/notification service operation. The AF can subscribe for the availability or expected level of support of a service API with report type indicating either One-time report or Continuous report.

• If there is no CN type information for the UE in the SCEF+NEF, the SCEF+NEF subscribes event monitoring for a new CN Type Change event for the UE or group of UEs to the HSS+UDM; otherwise, the SCEF+NEF détermines the CN type locally in the following conditions:

o If the AF subscribes with report type indicating One-time report, the SCEF+NEF may consider the Freshness Timer ofthe latest CN type information for the UE or Group of UEs. The Freshness Timer is a parameter that is configured based on local SCEF+NEF policy. When a subscription request with One-time report type is received the SCEF+NEF checks if there is the latest CN type information received from the HSS+UDM for the indicated UE ID or Extemal Group ID. If the elapsed time for the CN type information since the last réception is less than the Freshness Timer, then the SCEF+NEF may respond to the AF with the latest CN type information in order to avoid repeated query to HSS+UDM.

o The SCEF+NEF has established a direct connection with MME or AMF or SMF.

• When the UE or ail members of a group of UEs are being served by a MME, the CN type is determîned to be “EPC.” When the UE or ail members of a group of UEs are being served by an AMF, the CN type is determined to be “5GC, When the UE is registered both in EPC and 5GC, or some members of a group of UEs are registered in EPC while some members are registered in 5GC, the CN type is determined to be “5GC+EPC.” If 5GC+EPC is determined asthe CN type serving the UE orthe group of UEs, the SCEF+NEF détermines that service APIs for both 5GC and EPC are available to the UE or the group of UEs.

[0007] In order to support monitoring of the availability or expected level of support of a service API, TS 29.122 re-uses the MonitoringEvent API to support the event API support capability change.'' An AF is thus able to subscribe to SCEF+NEF for such an event and then be notifiée! about the 3GPP system level support for the exposure APIs and the supported feature for each API.

Summary

[0008] In a real deployment, not ail APIs are supported by an AF. In conventional Systems, when a AF subscribes to the API support capability change event, the AF is notified about ail ofthe APIs supported by that system, whether or not the AF is interested in ail ofthose APIs. This créâtes a signalling impact for the network due to unnecessary information in the event notification. Currently, there are approximately 20 APIs in the network capability exposure, with more predicted to be added in the future. This means that more and more unnecessary information will be conveyed to the AF.

[0009] The présent disclosure provides a new event filter for the API support capability change event. This event filter opérâtes to limit the amount of information sent over the network te an Application Function (AF) that has subscribed to the API support capability change event. In some embodiments, the event filter identifies the API(s) in which the AF is interested, e.g., by API name.

[0010] According to one aspect of the présent disclosure, a method for reporting Application Programming Interface (API) capability change according to an API filter comprises: at a first node within a télécommunication core network: receiving, from a requesting entîty, a request to be notified of an API capability change related to an identified wireless device, the request identifying a set of one or more APIs to be monitored; subscribing to receive notifications of a core network type change for the identified wireless device; receiving a notification that the identified wireless device has changed from a first type of core network to a second type of core network; determining an API capability change from the first type of core network to the second type of core network for the identified set of one or more APIs to be monitored; and reporting, to the requesting entity, the API capability change for the identified set of one or more APIs to be monitored and not reporting the API capability change for APis not in the identified set.

[0011] In some embodiments, the first node comprises a node forexposing services and capabilities of a télécommunication core network to entities outside of the télécommunication core network.

[0012] In some embodiments, the first node comprises a Service Capability Exposure Function (SCEF), a Network Exposure Function (NEF), or a combined SCEF+NEF.

[0013] In some embodiments, the requesting entity comprises an Application Function (AF), a Service Capability Server (SCS), and/or an Application Server (AS).

[0014] In some embodiments, receiving the request to be notified of an API capability change related to an identified wireless device comprises receiving a monitoring request.

[0015] In some embodiments, subscribing to receive notifications of a core network type change for the identified wireless device comprises sending a subscribe request to a node comprising a Home Subscriber Server (HSS), a Unified Data Management function (UDM), or a combined HSS+UDM.

[0016] In some embodiments, subscribing to receive notifications of a cote network type change for the identified wireless device comprises sending a Nudm_EventExposure_Subscribe Request.

[0017] In some embodiments, receiving a notification that the identified wireless device has changed from a first type of cote network to a second type of core network comprises receiving a Nudm_EventExposure_Notify Response.

[0018] In some embodiments, reporting the API capability change comprises sending a monitoring indication request.

[0019] According to another aspect of the présent disclosure, a method for reporting API capability change according to an API fîlter comprises: at a requesting entity: sending, to a first node within a télécommunication core network, a request to be notified of an API capability change related to an identified wireless device, the request identifying a set of one or more APIs to be monitored; and receiving, from the first node, a notification of an API capability change related to the identified wireless device, the notification including the API capability change for the identified set of one or more APIs to be monitored and not including an API capability change for APIs not in the identified set.

[0020] In some embodiments, sending the request to the first node comprises sending the request to a node for exposing services and capabilities of a télécommunication core network to entities outside of the télécommunication core network.

[0021] In some embodiments, the first node comprises a SCEF, a NEF, or a combined SCEF+NEF.

[0022] In some embodiments, the requesting entity comprises an AF, a SCS, and/or an AS.

[0023] In some embodiments, sending the request to be notified of an API capability change related to an identified wireless device comprises sending a monitoring request.

[0024] In some embodiments, receiving the notification of an API capability change related to the identified wireless device comprises receiving a monitoring indication request,

[0025] According to another aspect of the présent disclosure, a network node for reporting API capability change according to an API fîlter comprises: one or more processors; and memory storing instructions exécutable by the one or more processors, whereby the network node is opérable to: receive, from a requesting entity, a request to be notified of an API capability change related to an identified wireless device, the request identifying a set of one or more APIs to be monitored; subscribe to receive notifications of a core network type change for the identified wireless device; receive a notification that the identified wireless device has changed from a first type of core network to a second type of core network; détermine an API capabilily change from the first type of core network to the second type of core network for the identified set of one or more APIs to be monitored; and report, to the requesting entity, the API capability change for the identified set of one or more APIs to be monitored and not reporting the API capability change for APIs not in the identified set.

[0026] In some embodiments, the network node is enabled to perform any of the exposure function methods described herein.

[0027] According to another aspect of the présent disclosure, a network node confîgured for reporting API capability change according to an API filter comprises processing circuity adapted to: receive, from a requesting entity, a request to be notified of an API capability change related to an identified wireless device, the request identifying a set of one or more APIs to be monitored; subscribe to receive notifications of a core network type change for the identified wireless device; receive a notification that the identified wireless device has changed from a first type of core network to a second type of core network; détermine an API capability change from the first type of core network to the second type of core network for the identified set of one or more APIs to be monitored; and report, to the requesting entity, the API capability change for the identified set of one or more APIs to be monitored and not reporting the API capability change for APIs not in the identified set.

[0028] In some embodiments, the network node is enabled to perform any of the exposure function methods described herein.

[0029] According to another aspect of the présent disclosure, a network node for reporting API capability change according to an API filter comprises modules adapted to: receive, from a requesting entity, a request to be notified of an API capability change related to an identified wireless device, the request identifying a set of one or more APIs to be monitored; subscribe to receive notifications of a core network type change for the identified wireless device; receive a notification that the identified wireless device has changed from a first type of core network to a second type of core network; détermine an API capability change from the first type of core network to the second type of core network for the identified set of one or more APIs to be monitored; and report, to the requesting entity, the API capability change for the identified set of one or more APIs to be monitored and not reporting the API capability change for APIs not in the identified set.

[0030] In some embodiments, the network node is enabled to perform any of the exposure function methods described herein.

[0031] According to another aspect ofthe présent disclosure, a network node for reporting API capability change according to an API filter comprises: one or more processors; and memory storing instructions exécutable by the one or more processors, whereby the network node is opérable to: send, to a first node within a télécommunication core network, a request to be notified of an API capability change related to an identified wireless device, the request identifying a set of one or more APIs to be monitored; and receive, from the first node, a notification of an API capability change related to the identified wireless device, the notification încluding the API capability change for the identified set of one or moreAPIsto be monitored and not încluding an API capability change for APls not in the identified set.

[0032] In some embodiments, the network node is enabled to perform any of the application function methods described herein.

[0033] According to another aspect of the present disclosure, a network node configured for reporting API capability change according to an API filter comprises processing circuity adapted to: send, to a first node within a télécommunication core network, a request to be notified of an API capability change related to an identified wireless device, the request identifying a set of one or more APls to be monitored; and receive, from the first node, a notification of an API capability change related to the identified wireless device, the notification încluding the API capability change for the identified set of one or more APlsto be monitored and not încluding an API capability change for APls not in the identified set.

[0034] In some embodiments, the network node is enabled to perform any of the application function methods described herein.

[0035] According to another aspect of the present disclosure, a network node for reporting API capability change according to an API filter comprises modules adapted to: send, to a first node within a télécommunication core network, a request to be notified of an API capability change related to an identified wireless device, the request identifying a set of one or more APls to be monitored; and receive, from the fïrst node, a notification of an API capability change related to the identified wireless device, the notification încluding the API capability change for the identified set of one or more APls to be monitored and not încluding an API capability change for APls not in the identified set.

[0036] In some embodiments, the network node is enabled to perform any of the application function methods described herein.

[0037] The advantages provided by the present disclosure include, but are not limited to, improved signaling transmission to avold încluding unneeded or unused information in the event notification message(s) and flexible event subscription from the AF’s perspective, e.g., the AF can get information for ail APls or only some of the APls.

Brief Description of the Drawings

[0038] The accompanying drawing figures incorporated in and forming a part of this spécification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

Figure 1 illustrâtes one example of a cellular communications network according to some embodiments of the present disclosure;

Figure 2 illustrâtes a wireless communication system represented as a 5G network architecture composer! of core Network Functions (NFs), where interaction between any two NFs is represented by a point-to-point reference point/interface;

Figure 3 illustrâtes a 5G network architecture using service-based interfaces between the N Fs in the control plane, instead of the point-to-point reference points/interfaces used in the 5G network architecture of Figure 2;

Figure 4 is a signaling graph showing messages exchanged during an exemplary process for Application Programming Interface (API) capability change notification based on an API filter according to some embodiments of the présent disclosure;

Figure 5 is a schematic block diagram of a network node according to some embodiments of the présent disclosure;

Figure 6 is a schematic block diagram that illustrâtes a virtualized embodiment of the radio access node of Figure 5 according to some embodiments of the présent disclosure;

Figure 7 is a schematic block diagram of the radio access node of Figure 5 according to some other embodiments of the présent disclosure;

Figure 8 is a schematic block diagram of a User Equipment device (UE) according to some embodiments of the présent disclosure;

Figure 9 is a schematic block diagram of the UE of Figure 8 according to some other embodiments of the présent disclosure;

Detailed Description

[0039] The embodiments set forth below represent information to enabie those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts ofthe disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0040] Radio Node; As used herein, a “radio node” is either a radio access node or a wireless communication device,

[0041] Radio Access Node: As used herein, a radio access node” or radio network node or “radio access network node is any node in a radio access network of a cellular communications network that opérâtes to wirelessîy transmit and/or receive signais. Some examples of a radio access node include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Génération Partnership Project (3GPP) Fifth Génération (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, orthe like), a relay node, a network node that implements part ofthe functionality of a base station or a network node that implements a gNB Distributed Unit (gNB-DU)) or a network node that implements part of the functionality of some other type of radio access node.

[0042] Core Network Node: As used herein, a core network node” is any type of node in a core network or any node that implements a core network function. Some examples of a core network node include, e.g., a

Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), or the like. Some other examples of a core network node include a node implementing a Core Access and Mobility Management Function (AMF), a UPF, a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Sélection Function (NSSF), a Network Exposure Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), or the like.

[0043] Communication Device: As used herein, a “communication device¹’ is any type of device that has access to an access network. Some examples of a communication device include, but are not limited to: mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, caméra, or any type of consumer electronic, for instance, but not limited to, a télévision, radio, lighting arrangement, tablet computer, laptop, or Personal Computer (PC). The communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and/or data via a wireless or wireline connection.

[0044] Wireless Communication Device: One type of communication device is a wireless communication device, which may be any type of wireless device that has access to (i.e., is served by) a wireless network (e.g., a cellular network). Some examples of a wireless communication device include, but are not limited to: a User Equipment device (UE) in a 3GPP network, a Machine Type Communication (MTC) device, and an Internet of Things (loT) device. Such wireless communication devices may be, or may be integrated into, a mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, caméra, or any type of consumer electronic, for instance, but not limited to, a télévision, radio, lighting arrangement, tablet computer, laptop, or PC. The wireless communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and/or data via a wireless connection.

[0045] Network Node: As used herein, a “network node is any node that is either part of the radio access network or the core network of a cellular communications network/system.

[0046] Note that the description given herein focuses on a 3GPP cellular communications System and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP System.

[0047] Note that, in the description herein, reference may be made to the term “cell”; however, particularly with respect to 5G NR concepts, beams may be used instead of cells and, as such, it is important to note that the concepts described herein are equally applicable to both cells and beams.

Figure 1

[0048] Figure 1 illustrâtes one example of a cellular communications System 100 in which embodiments of the présent disclosure may be implemented. The subject matter disclosed herein addresses a spécifie problem that may occur when a UE changes from a 5G network to an LTE network of vice versa, and thus the cellular communications System 100 may be a 5G System (5GS) including a NR RAN or LTE RAN (i.e„ E

UTRA RAN), an Evolved Racket System (EPS) including a LTE RAN, or both. In this example, the RAN includes base stations 102-1 and 102-2, which in LTE are referred to as eNBs (when connected to EPC) and in 5G NR are referred to as gNBs (LTE RAN nodes connected to 5GC are referred to as gn-eNBs), controlling correspondîng (macro) cells 104-1 and 104-2. The base stations 102-1 and 102-2 are generally referred to herein collectively as base stations 102 and individually as base station 102. Likewise, the (macro) cells 1041 and 104-2 are generally referred to herein collectively as (macro) cells 104 and individually as (macro) cell 104. The RAN may also include a number oflow power nodes 106-1 through 106-4 controlling correspondîng small cells 108-1 through 1084. The low power nodes 106-1 through 1064 can be small base stations (such as pico or femto base stations) or Remote Radio Heads (RRHs), or the like. Notably, while not il lustrated, one or more ofthe small cells 108-1 through 1084 may altematively be provided by the base stations 102. The low power nodes 106-1 through 1064 are generally referred to herein collectively as low power nodes 106 and individually as low power node 106. Likewise, the small cells 108-1 through 1084 are generally referred to herein collectively as small cells 108 and individually as small cell 108. The cellular communications System 100 also includes a core network 110, which in the 5GS is referred to as the 5G core (5GC). The base stations 102 (and optionally the low power nodes 106) are connected to the core network 110.

[0049] The base stations 102 and the low power nodes 106 provide service to wireless communication devices 112-1 through 112-5 in the correspondîng cells 104 and 108. The wireless communication devices 112-1 through 112-5 are generally referred to herein collectively as wireless communication devices 112 and individually as wireless communication device 112. In the following description, the wireless communication devices 112 are oftentimes UEs, but the présent disclosure is not limited thereto.

Figure 2

[0050] Figure 2 illustrâtes a wireless communication System represented as a 5G network architecture composed of core Network Functions (NFs), where interaction between any two NFs is represented by a pointto-point reference point/interface. Figure 2 can be viewed as one particular implémentation ofthe System 100 of Figure 1.

[0051] Seen from the access side the 5G network architecture shown in Figure 2 comprises a plurality of User Equipment (UEs) connected to either a Radio Access Network (RAN) or an Access Network (AN) as well as an Access and Mobility Management Function (AMF). Typically, the (R)AN comprises base stations, e.g., such as evolved Node Bs (eNBs) or NR base stations (gNBs) or similar. Seen from the core network side, the 5G core NFs shown in Figure 2 include a Network Slice Sélection Fonction (NSSF), an Authentication Server Function (AUSF), a Unified Data Management (UDM), an AMF, a Session Management Function (SMF), a Policy Control Function (PCF), and an Application Function (AF).

[0052] Reference point représentations of the 5G network architecture are used to develop detailed call flows in the normative standardization. The N1 reference point is defined to carry signaling between the UE and AMF. The reference points for connecting between the AN and AMF and between the AN and U PF are defined as N2 and N3, respectively. There is a reference point, N11, between the AMF and SMF, which implies that the SMF is at least partly controlled by the AMF. N4 is used by the SMF and UPF so that the UPF can be set using the control signal generated by the SMF, and the UPF can report its state to the SMF. N9 is the _ref_erence point for the connection between different UPFs, and N14 is the reference point connecting between different AM Fs, respectively. N15 and N7 are defined since the PCF applîes policy to the AMF and SMP, respectively. N12 is required forthe AMF to perform authentication ofthe UE. N8 and N10 are defined because the subscription data of the UE is required for the AMF and SMF.

[0053] The 5G core network aims at separating user plane and control plane. The user plane carries user traffic while the control plane carries signaling in the network. In Figure 2, the UPF is in the user plane and ail other NFs, i.e., the AMF, SMF, PCF, AF, AUSF, and UDM, are in the control plane. Separating the user and control planes guarantees each plane resource to be scaled independently. It also aliows UPFs to be deployed separately from control plane functions in a distributed fashion. In this architecture, UPFs may be deployed very close to U Es to shorten the Round Trip Time (RTT) between U Es and data network for some applications requiring low latency.

[0054] The core 5G network architecture is composed of modularized functions. For example, the AMF and SMF are independent functions in the control plane. Separated AMF and SMF allow independent évolution and sealing. Other control plane functions like the PCF and AUSF can be separated as shown in Figure 2. Modularized fonction design enables the 5G core network to support various services flexibly.

[0055] Each NF interacts with another N F directly. It is possible to use intermediate functions to route messages from one NF to another NF. In the control plane, a set of interactions between two NFs is defined as service so that its reuse is possible. This service enables support for modularity. The user plane supports interactions such as forwarding operations between different UPFs.

Figure 3

[0056] Figure 3 illustrâtes a 5G network architecture using service-based interfaces between the NFs in the control plane, instead ofthe point-to-point reference points/interfaces used in the 5G network architecture of Figure 2. However, the NFs described above with reference to Figure 2 correspond to the NFs shown in Figure 3. The service(s) etc. that a NF provides to other aulhorized NFs can be exposed tothe authorized NFs through the service-based interface. In Figure 3 the service based interfaces are indicated by the letter N” followed by the name of the N F, e.g., Namf for the service based interface of the AMF and Nsmf for the service based interface of the SMF etc. The Network Exposure Fonction (NEF) and the Network Function (NF) Repository Function (NRF) in Figure 3 are not shown in Figure 2 discussed above. However, it should be ciarified that ail NFs depicted in Figure 2 can interact with the NEF and the NRF of Figure 3 as necessary, though not explicitly indicated in Figure 2.

[0057] Some properties ofthe NFs shown in Figures 2 and 3 may be described in the following manner. The AMF provides UE-based authentication, authorization, mobility management, etc. A UE even using multiple access technologies is basically connected to a single AMF because the AMF is independent ofthe access technologies. The SMF is responsible for session management and allocates Internet Protocol (IP) addressesto U Es. It also selects and contrais the UPF for data transfer. If a UE has multiple sessions, different SM Fs may be allocated to each session to manage them individually and possibly provide different functionaiities per session. The AF provides information on the packet flow to the PCF responsible for policy control in order to support Quality of Service (QoS), Based on the information, the PCF détermines policies about mobility and session management to make the AMF and SMF operate properly. The AUSF supports authentication fonction for UEs or similar and thus stores data for authentication of UEs or similar while the UDM stores subscription data of the UE. The Data Network (DN), not part of the 5G core network, provides Internet access oroperator services and similar.

[0058] An N F may be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized fonction instantiated on an appropriate platform, e.g., a cloud infrastructure.

Figure 4

[0059] Figure 4 is a signaling graph showing messages exchanged during an exemplary process for Application Programming Interface (API) capability change notification based on an API filter according to some embodiments of the présent disclosure. In the embodiment illustrated in Figure 4, the process includes the following steps:

[0060] Step 400. A requesting entity, such as an Application Function (AF), Service Capability Server (SCS), or Application Server (AS), sends a monitoring request to a combined Service Capability Exposure Function (SCEF) and Network Exposure Function (NEF), referred to as a SCEF+NEF. In the embodiment illustrated in Figure 4, the monitoring request spécifiés that the requesting entity wants to monitor the API Capability Change events for a specified UE (identified by UE ID), and further includes a list of API names or other means by which to specify the API or APIs in which the requesting entity is interested.

[0061] Step 402, The SCEF+NEF sends a subscribe request to a Home Subscriber Server (HSS) and Unified Data Management (UDM) function, referred to as a HSS+UDM. In the embodiment illustrated in Figure 4, the subscribe request spécifiés that the SCEF+NEF wants to be notified when a CN Type Change event occurs for the specified UE. In some embodiments, the subscribe request comprises a Nudm_EventExposure_Subscribe request, and may include parameters such as an event ID, a UE ID, a maximum number of reports, etc.

[0062] Step 404. The HSS+UDM responds to the subscribe request by sending a subscribe response back to the SCEF+NEF. In the embodiment illustrated in Figure 4, the subscribe response comprises a Nudm_EventExposure_Subscribe response.

[0063] Step 406. The SCEF+NEF sends a monitoring response to the entity that issued the monitoring request. Exampie responses include notification that the monitor request was received, that the monitor request was granted ordenied, etc. In the embodiment illustrated in Figure 4, the monitor request was granted. [0064] Step 408. The UE moves between different Systems, and the HSS+UDM receives notification of this fact. For example, if the UE moves from an EPC to a 5GC, the HSS+UDM may receive a

Nudm_UECM_Registration message (step 410) from a 5GC Cote Access and Mobility Management Function (AMF). If the UE moves from a 5GC to an EPC, the HSS+UDM may receive a Location Update message (step 412) from a Serving General Packet Radio Service (GPRS) Support Node (SGSN) or a Mobility Management Entity (MME).

[0065] Step 414. In response to determining that the UE has changed from one CN type to another (e.g., from EPC to 5GC or from 5GC to EPC), the HSS+UDM notifies the SCEF+NEF of this fact. In the embodiment illustrated in Figure 4, the HSS+UDM sends a Nudm_EventExposure_Notify Request to the SCEF+NEF, and may include parameters such as eventiD, CN type, UE ID, etc.

[0066] Step 416. The SCEF+NEF responds to the notification from the HSS+UDM. In the embodiment illustrated in Figure 4, the SCEF+NEF sends a Nudm_ExposureEvent_Notify Response to the HSS+UDM.

[0067] Step 418. The SCEF+NEF détermines that the requesting entity (Le., the AF) is monitoring the UE that changed and has requested to be notified when there is an API capability change. Further, the SCEF+NEF détermines that the AF wants to be notified of an API capability change to a particular subset of APIs, e.g., the APls identified in the monitoring request sent at step 400. That is, the SCEF+NEF applies the event filters to filter out all but the APIs in which the AF has indicated an interest.

[0068] Step 420. The SCEF+NEF notifies the requesting entity of the API capability change for those APIs in which the AF has indicated an interest. In the embodiment illustrated in Figure 4, the SCEF+NEF issues a Monitoring Indication Request to the AF, which may include parameters such as event ID (indicating an API capability change) and a list of API names and their respective supported features.

[0069] Step 422, The requesting entity sends a Monitoring Indication Response to the SCEF+NEF. Example Implémentations

[0070] The following changes to 3GPP TS 29.122 are proposed.

*** Ist Change to 3GPP TS 29.122 ***

4.4.2.2.2.1 General

The following monitoring events are applicable for the monitoring event configuration via HS S foian individual UE or a group of UEs:

- Loss of connectivity;

- UE reachability;

- Location Reporting;

- Change of IMSI-IMEI(SV) Association;

- Roaming Status;

- Communication Failure;

- Availabilitv after PNN Failure; and

- API support capability.

Only one-time reporting is supported if the reachabilityType” attribute sets to SMS for the event UE reachability, if the locationType attribute sets to LAST_KNOWN_LOC ATION for the event Location Reporting in the monitoring event request.

*** Next Change to 3GPP TS 29.122 ***

5.3.2.1.2 Type: MonitoringEventSubscription

This type represents a subscription to inonitoring an event. The same structure is used in the subscription request and subscription response.

Table 5.3.2.1.2-1: Définition of type MonitoringEventSubscription

Attribute name	Data type	Cardinaiity	Description	AppHcability (NOTE 3)
self	Link	0..1	Link to the resource Individual Monitoring Event Subscription. This parameter shall be supplied by the SCEF in HTTP res penses.
supportedFeatures	SupportedFeatur es	0..1	Used to negotiate the supported optional features of the API as described in subclause 5.2.7. This attribute shall be provided in the POST request and in the response of successful resource création.
mtcProviderld	string	0..1	Identifies the MTC Service Provider and/or MTC Application. (NOTE 7)
externalld	Externalld	0..1	Identifies a user as defined in Clause 4.6.2 of 3GPP TS 23.682 [2]. (NOTE 1)	(NOTE 5)
msisdn	Msisdn	0..1	Identifies the MS internai PSTN/ISDN number allocated for a UE. (NOTE 1)	(NOTE 5)
externalGroupld	ExternalGroupld	0..1	Identifies a user group as defined in Clause 4.6.2 of 3GPP TS 23.682 [2], (NOTE 1) (NOTE 6)
addExtGroupids	array(ExternalGr oupld)	0..N	identifies user groups as defined in Clause 4.6.2 of 3GPP TS 23.682 [2], (NOTE 1) (NOTE 6)	Number_ofJJE s_in_an_area_ notification, NumberofUE s_in_an_area_ notification_5G
ipv4Addr	lpv4Addr	0..1	Identifies the Ipv4 address. (NOTE 1)	Location_notific ation. Communication _failure_notific ation
ipv6Addr	lpv6Addr	0..1	Identifies the Ipv6 address. (NOTE 1)	Location_notific ation. Communication _failure_notific ation
n otifi cati on Desti natio n	Link	1	An URI of a notification destination that T8 message shall be delivered to.
req uestTes t N oti f icati on	boolean	0..1	Set to true by the SCS/AS to request the SCEF to send a test notification as defined in subclause 5.2.5.3. Set to false or omitted otherwise.	Notification_tes t_event
we bsockN oti fCo nf ig	WebsockNotifCo nfig	0..1	Configuration parameters to set up notification delivery over Websocket protocol as defined in subclause 5.2.5.4.	Notification_we b socket

monitoringType	MonitoringType	1	Enumération of monitoring type. Refer to clause 5.3.2.4.3.
m a xi m u m N u m berOf Re ports	integer	0..1	Identifies the maximum number of event reports to be generated by the HSS, MME/SGSN as specified in subclause 5.6.0 of 3GPP TS 23.682 [2], (NOTE 2)
monitorExpireTime	DateTime	0„1	Identifies the absolute time at which the related monitoring event request is considered to expire, as specified in subclause 5.6.0 of 3GPP TS 23.682 [2]. (NOTE 2)
groupReportGuardTim e	Du ration Sec	0..1	Identifies the time for which the SC EF can aggregate the monitoring event reports detected by the UEs in a group and report them together to the SCS/AS, as specified in subclause 5.6.0 of 3GPP TS 23.682 [21.
maximumDetectionTim e	□urationSec	0..1	If monitoringType is ”LOSS_OF_CONNECTlViTY, this parameter may be included to identify the maximum period of time after which the UE is considered to be unreachable.	Loss_of_conne ctlvity_notificati on
reachabilîtyType	ReachabilityTyp e	0..1	If monitoringType is UE_REACHABILITY, this parameter s hall be included to identify whether the request is for Reachabilîty for SMS or Reachability for Data.	Uereachability_no tifi cation
m a xi m u m Late ncy	DurationSec	0..1	If monitoringType is UE_REACHABILITY, this parameter may be included to identify the maximum delay acceptable for downlink data transfers.	Uereachability_no tification
maximumResponseTi me	Du ration Sec	0..1	If monitoringType is UE_REACHAB1LITY”, this parameter may be included to identify the length of time for which the UE stays reachable to allow the SCS/AS to reliably deliver the required downlink data.	Uereachability_no tification
s ug ge sted N u m b e rOf DI Rackets	integer	0..1	If monitoringType is UEREACHABILITY, this parameter may be included to identify the number of packets that the serving gateway shall buffer in case that the UE is not reachable.	Uereachabilitynotifi cation
idleStat us Indication	boolean	0..1	If monitoringType is setto UE_REACHABILITY or AV Al LAB ILITY_AFTER_DDN_FAI LURE, this parameter may be included to indicate the notification of when a UE, for which PSM is enabled, transitions into idle mode. truei indicate enabling of notification false: indicate no need to notify Default: false.	Uereachability_no tification, Availability_afte r_DDN_failure_ notification, Availability_afte r_DDN_failure_ notification_en hancement
locationType	LocationType	0..1	If monitoringType is LOCATION REPORTING or NUMBER_OF_UES_IN_AN_AREA, this parameter shall be included to identify whether the request is for Current Location or Last known Location. (NOTE 4)	Location_notific ation, Number_of_UE s_in_an_area_ notification, Number_of_UE sjn_an_area_ notification 5 G

accuracy	Accuracy	0..1	If monitoringType is LOCATIONREPORTING, this parameter may be included to identify the desired level of accuracy of the requested location information, as described in subclause 4.9.2 of 3GPP TS 23.682 [2],	Locationnotific ation
minimumReportlnterval	DurationSec	0..1	If monitoringType is LOCATION_REPORTING”, this parameter may be included to identify a minimum time interval between Location Reporting notifications.	Location_notific ation
associationType	AssociationType	0..1	If monitoringType” is CHANGE_OF_IMSI_IMEI_ASSOCIATIO N, this parameter shall be included to identify whether the change of IMSI-IMEl or IMSI-IMEISV association shall be detected.	Change_of_IM SI_IMEI_associ ation_notificatio n
pim n Indication	boolean	0..1	If monitoringType is ROAMING^STATUS, this parameter may be included to indicate the notification of UE's Serving PLMN ID. true”: The value shall be used to indicate enabling of notification; - false: The value shall be used to indicate disabling of notification. Default: false.	Roaming_statu sanctification
location Area	LocationArea	0..1	If monitoringType is NUMBER_OF_UES_IN_AN_AREA, this parameter may be included to indicate the area within which the SCS/AS requests the number of UEs.	Number_of_UE s_in_an_area_ notification
location Area 5 G	Location Area 5 G	0..1	If monitoringType is NUMBER_OF_UES_IN_AN_AREA, this parameter may be included to indicate the area within which the AF requests the number of UEs.	Number_of_UE s_in_an_area_ notification_5G
dddTraDes	DddT raffic Descri ptor	0..1	The traffic descriptor of the downlink data source. May be included for event DOWNLINK_DATA_DELIVERY_STATU S or AVAILABILITYAFTERD DNFAILURE.	Downlink_data _delivery_statu s_5G, Availability_afte r_DDN_failure_ notification_en hancement
dddStati	array(DddStatus )	0..N	May be included for event DOWNLINK_DATA_DELIVERY_STATU S. The subscribed stati (delivered, transmîtted, buffered) for the event. If omitted ail stati are subscribed.	Downlink_data _delivery_statu s_5G

apiNames	arrav(strina)	0..N	Each eiement identifies the name of an	APi support
			API. It shall set as faoiName} part of the UR!	caoabîiitv not ification
structure for each T8 or N33 API as defined in the present spécification or
3GPP TS 29.522 FTS295221, respectively. This aliows the SCS/AS to reouest the
capability change for the listed APIs (which are aiso supoorted bv the SCEF+NEF). If it is omitted. the SCS/AS reauests to be notified for capabiiitv change for ah APIs the SCEF+NEF supports.
monitoringEventReport	MonitoringEvent Report	0..1	Identifies a monitoring event report which is sent from the SCEF to the SCS/AS.

NOTE 1 : One of the properties external Id, msisdn, ipv4Addr. ipv6Addr or external Groupld” shall be included for features Location_notifi cation and Communication_failure_notification;. ipv4Addr or “ipv6Addr is required for monitoring via the PCRF for an individual UE. One ofthe properties externalld, msisdn or extern alGroupld shall be included for features ''Pdn_connectivity_status, Loss_of_connectivit y_n ot i f icati o n, U e-rea c ha b il i ty _notifi catio n , ”C h a nge_of_l M S J_ IΜ E l_associatio n_n ot if icatio n, Roa m i n g_sta t us_notifi cati o n , A va i la b ί I ity_afte r_D D N_fa i I u re_n otificationand

A va i I a bi I i ty _afte r_D D N_fa i I u re_n otifï cat io ne nhancement;;

NOTE 2: Inclusion of either maximumNumberOfReports (with a value higher than 1) or monitorExpireTime makes the Monitoring Request a Continuous Monitoring Request, where the SCEF sends Notifications until either the maximum number of reports or the monitoring duration indicated by the property monitorExpireTime is exceeded. The maximumNumberOfReports with a value 1 makes the Monitoring Request a One-time Monitoring Request At least one of maximumNumberOfReports' or monitorExpireTime shall be provided.

NOTE 3: Properties marked with a feature as defined in subclause 5.3.4 are applicable as described in subclause 5.2.7. If no features are indicated, the related property applies for ail the features.

NOTE 4: In this release, for features Number_of_UEs_in_an_area_notification and Number_of_UEs_in_an_area_notification_5G, locationType shall be set to LAST_KNOWN_LOCATION.

NOTE 5: The property does not apply for the features Number_of_UEs_in_an_area_notification and N u m ber_of_U E sJ n_a n_a re an ot i fi catio n_5G .

NOTE 6: For the features Number_of_UEs_in_an_area_notification and Number_of_UEs_in_an_area_notification_5G, the property externalGroupld may be included for single group and addExtGroupIds may be included for multiple groups but not both.

NOTE 7: The SCEF should check received MTC provider identifier and then the SCEF may: override it with local configured value and send it to HSS;

send it directly to the HSS; or

-reject the monitoring configuration request.

*** Next Change to 3GPP TS 29.122 ***

A.3 MonitoringEvent API openapi: 3.0.0 infO:

title: 3gpp-monitoring-event version: 1.1.0.alpha-3 description: |

API for Monitoring Event.

® 2013, 3GPP Organizational Partners (ARIB, ATIS. CCSA, ETSI, TSDSI, TTA, TTC).

Ail rights reserved.

externalDocs:

description: 3GPP TS 29.122 V16.3.0 T8 reference point for Northbound APIs url : 'http:/ /www. 3gpp.org/f tp/Specs/archive/2 9_3eri.es/29.122 / ¹ security:

- f) - oA.uth2ClientCredentials: [] servers :

- url: ¹{apiRoot}/3gpp-monitoring-event/vl' variables:

apiRoot:

default : https ://exemple . com description: apiRoot as defined in subclause 5,2.4 of 3GPP TS 29,122* paths:

/{scsAsId}/subscript ions :

get :

summary: read ail of the active subscriptions for the SCS/AS tags :

- MonitoringEvent API SCS/AS level GET Operation parameters:

- name: scsAsId in: path description: Identifier of the SCS/AS required: true schéma.: type: string responses:

'200 ^r:

description: OK [Successful get ail of the active subscriptions for the SCS/AS) content :

application/j son : schéma:

type : array items:

$ref: ^r#/comportents/schémas/MonitoringEventSubscription’ minltems: 0 description: Monitoring event subscriptions ^r400^r:

$ref: 'TS29122_CommohData.yaml#/components/responses/400¹ '401^h:

$ref ; ¹ TS29122_CommohData. yaml#/components/responses/401 ' ' 403¹ :

$ref : ¹ TS29122_ComTnonData .yaml#/components/responses/403 ’ '404':

$ref: ¹TS29122_CommonData*yaml#/comportents/responses/404¹ '406':

$ref: ^rTS29122_CommonData.yaml#/components/responses/406^r ’429^]:

$ re f: ·TS2 912 2_CommonData.yaml#/comportent s/re spons e s/4 2 9^{1 1}500¹ :

$ re f: ¹TS2 912 2_CommonData.yaml#/comportent s/re sponse s/5 0 0 ^{r 1}503 ¹ :

$ref : ' TS2 9122_ComrnonData . yaml#/components/responses/503 ¹ default :

$ref : ' TS29122_CommonData.yaml#/components/responses/default¹ post :

summary: Créâtes a new subscription resource for monitoring event notification tags :

- MonitoringEvent API Subscription level POST Operation parameters:

- name: scsAsId in: path description: Identifier of the SCS/AS required: true schéma : type: string reçue stBody:

description: Subscription for notification about monitoring event required: true content :

application/j son : schéma :

$ref: ¹#/comportents/schémas/MonitoringEventSubscription’ callbacks:

notificationDestination:

’{request.body^/notificationDestination)^f: post :

requestBody: # contents of the callback message required: true content :

application/j son : schéma :

$ref : ' fi /comportent s/schémas/Moni ter ingNot if icat ion¹ responses:

¹204 ^Γ :

description: No Content (successful notification) >400'î $ref : ¹ TS29122_CommonData. yaml#/components/responses/400 ' ¹ 401’ :

$ref : ^rTS29122_CommonData .yaml#/components/responses/401¹ '403':

$ re f : ¹TS2 912 2_ComimonData.yaml# / comportent s / re sponses/4 0 3¹ '404¹:

$ ref: 'TS2912 2_CommonData.yaml#/components/responses/404 ^{f 1}411 ¹ :

$ref; ¹TS29122_CommonData,yaml#/components/responses/411^{1 r}413 ^r î $ref: ¹ΤΞ29122_CommonData_tyaml#/components/responses/413^{1 r} 415' :

$ref ; ^rTS29122_CommoiiData_Tyaml#/components/responses/415 ' ^h 429’ :

$ref: 'TS29122_CommonData.yaml#/components/responses/429¹ '500' :

$ ref ; ' TS2 912 2_CommonData . yaml# / comportent s / respons e s / 5 0 0 ^{1 1}Ξ03¹:

$ re f: 'TS2 912 2_CommonData,yaml#/components/re sponses/5 0 3 ^r defaulti $ref: ¹TS29122_CommonData.yaml#/components/responses/default' responses: '201' :

description: Created (Successful création of subscription) content :

application/j son: schéma :

$ref : ¹ #/comportents/schemas/MonitoringEventSubscript ion ¹ headers: Location;

description: 'Contains the URI of the newly created resource¹ required: true schéma:

type: string ^f20Û ^f :

description: The operation is successful and immédiate report is included. content :

application/json : schéma:

$ref: '#/components/schémas/MonitoringEventReport¹ ' 400':

$ref: ^rTS29122_CommonData►yaml#/components/responses/400* '401' :

5ref: ^h TS2 9122_CommonData.yaml#/components/responses/401' '403 ¹ :

$ref: 'TS29122_CommonData.yarnl#/components/responses/403' '4 04 ¹ :

$ref: ^r TS2 9122_CommonData.yaml#/components/responses/404¹ ’ 411¹ :

$ re f; * TS2 912 2_CommonData.yaml#/components/re sponses/411¹ '413¹ ;

$ref: ¹TS29122_ComrnonData.yaml#/components/responses/413' ' 415' :

$ref: ’TS2 9122_CommonData.yaml#/components/responses/415¹ '429¹ :

$ref: 'TS29122_ComrnonData.yaml#/components/responses/429^{1 1} 500 ¹ :

Sref: ¹TS29122_CommonData.yaml#/components/responses/500^{1 1}503¹ :

$ref: 'TS29122_CommonData.yaml#/components/responses/503¹ default:

$ref: ^,TS29122_CommonData.yaml#/components/responses/default' /{scsAsïd}/subscriptions/{subscriptionld}:

get :

summary: read an active subscriptions for the SCS/AS and the subscription Id tags :

- MonitoringEvent API Subscription level GET Operation parameters:

- name: scsAsïd in: path description: Identifier of the SCS/AS required: true schéma :

type: string

- name : subscriptionld in: path description: Identifier of the subscription resource required: true schéma:

type: string responses:

¹200':

description: OK (Successful get the active subscription) content :

application/json: schéma :

$ref: ¹tt/components/schernas/MonitoringEventSubscription' ‘400'î $ r ef: ¹ TS 2 912 2_CommonDa ta -yami#/component s / re sponses/4 00' '401'î $ref: ¹TS29122_CommonData.yaml#/components/responses/401^{1 1}403 ' :

$ref: ¹TS29122_CommonData₊yaml#/components/responses/403’ ¹404' :

$ref: ^fTS29122_CommonData.yaml^/components/responses/404^{1 τ}406¹:

$ref: ¹TS29122_CommonData.yaml#/components/responses/406^{1 r}429¹:

$ref: 'TS29122_CommonData.yaml#/components/responses/429’ ^T 500¹ :

$ref: 'TS29122_CommonData.yaml#/components/responses/500¹ ‘503¹ :

$ref : ’ TS29122_CommonData .yaml#/componen.ts/responsea/503 ¹ default :

$ref: 'TS29122_CommonData♦yaml#/components/responses/default' put:

summary: Updates/replaces an existing subscript ion resource tags :

- MonitoringEvent API subscription level PUT Operation parameters:

- name: scsAsId in: path description: Identifier of the SCS/AS required: true schéma :

type : string

- name: subscriptionld in: path description: Identifier of the siibscription resource required: true schéma :

type: string requestBody:

description: Parameters to update/replace the existing subscription required: true content :

application/json: schéma:

$ref: '#/components/schémas/MonitoringEventSubscription¹ responses: ¹20ü¹ :

description: OK (Successful update of the subscription) content :

application/j son : schéma :

$ref: ¹#/components/schemas/MonitoringEventSubscription' ¹ 400¹ :

$ref: 'TS29122_OommonData.yaml#/components/responses/400^{1 1}401^r:

$ref: ¹TS29122_CommonData.yaml#/components/responses/401^{1 1}403¹ :

$ref: 'TS2 9122_CommonData.yaml#/components/responses/4 0 3^{1 1}404¹ :

$ref: 'TS2 9122_CommonData.yaml#/components/responses/404^{1 1}411¹ :

$ref : ^rTS29122_CommonData,yaml#/components/responses/411^{1 1} 413 ' :

Sref: ^rTS29122_CommonData.yaml#/components/responses/413^{1 1}415¹ :

$ref: 'TS29122_CommonData.yaml#/components/responses/415^{1 r}429 ¹ :

$ref: ¹TS29122_CommonData.yaml#/components/responses/429^f ‘500 ^r:

$ref : ' TS29122_CommonData.yaml#/cornponents/responses/500 ^r '503 ^h :

$ref : ¹ TS29122_CommonData.yaml#/components/responses/503 ¹ default;

$ref: ¹TS29122_CommonData.yaml#/components/responses/default^f delete;

summary: Deletes an already existing monitoring event subscription tags ;

- MonitoringEvent API Subscription levai DELETE Operation parameters:

- name : SCSAsId in: path description: Identifier of the SCS/AS required: true schéma : type: string

- name: subscriptionld in: path description: Identifier of the subscription resource requiredt crue schéma : type: string responses: '204':

description: No Content {Successful délétion of the existing subscription) ’ 200' :

description: OK (Successful délétion of the existing subscription} content :

application/j son : schéma : type: array items ;

$ref: '#/components/schémas/MonitoringEventReport' minltems: 1 description: The subscription was terminated successfully, the monitoring event report(s) shall be included if received.

'400':

$ref: ^r TS29122_CommonData.yaml#/components/responses/400¹ ’ 401¹:

$ref: ^rTS29122_CommonData.yaml#/components/responses/401¹ ’403¹ :

$ref: ^rTS29122_CommonData.yamltf/components/responses/403¹ '404':

Sref : ^r TS2 9122_CommonData . yamlit/components/responses/4 04 ^{1 3} 429 ³ :

$ref : *TS29122_CommonData . yaml#/components/responses/42 9 ¹ '500' :

$ref: ^rTS29122_CommonData.yaml#/components/responses/500^{1 1}503 ¹ :

$ref: *TS29122_CommonData.yaml#/components/responses/503 ^r default:

$ref: *TS29122_CommonData.yaml#/components/responses/defsuit’ components:

securitySchemes:

oAuthZClientCredentials: type : oauth2 flOWS;

clientCredentials: tokenUrl: ^r{tokenUrl)' scopes : {} schémas :

MonitoringEventSubscription: type: object properties:

self ;

$ref: ^rTS29122_CommonData.yamlfl/components/schémas/Link¹ supportedFeatures:

$ref : ' ΤΞ2 9571_CommonData. yaml#/components/schemas/SupportedFeatures ' mtcProviderld: type: string description: Identifies the MTC Service Provider and/or MTC Application, externalld:

$ref : ' TS29122_CommonData.yaml#/components/schemas/ExternalId¹ ms i sdn:

$ref: ’ ΤΞ 2 912 2_CommonData.yami#/components/schémas/Ms i sdn¹ externalGroupld:

$ref : ¹ TS29122_CoramonData.yaml#/components/schemas/ExternalGroupId’ addExtGroupId: type: array items :

$ref : ' TS29122_CommonData .yaml#/components/schémas/ExternalGroupId' minltems: 2 ipv4Addr:

Sref : ' TS29122_CommonData .yaml#/components/schémas/Ipv4Addr ' ipvSAddr :

$ref: 'ΤΞ29122_CommohData.yaml#/components/schémas/IpvSAddr' not i f i ca t ionDes t inat ion :

$ref: ¹TS29122_CommonData.yaml#/components/schemas/Link¹ requestTestMotification:

type : boolean description: Set to true by the SCS/AS to request the SCEF to send a test notification as defined in subclause 5.2.5.3. Set to false or omitted otherwise.

websockNotifConfig:

$ref: 'TS29122_CommonData.yaml#/components/schemas/WebsockNOtifConfig' monitoringType:

$ ref: '#/components/schémas/Moni tori ngType' maximumNumberOfReports :

type: integer minimum : 1 description; Identifies the maximum number of event reports to be generated by the HSS, MME/SGSN as specified in subclause 5.6.0 of 3GPP TS 2 3.6 92 [2] . monitorExpireTime:

$ref: ’TS2 9122_CommonData.yaml#/composents/schémas/DateTime' groupReportGuardTime:

$ref: 'TSE 9122_CommonData.yaml#/components/schémas/DurationSec' maximumDetectionTime:

$ref: 'TS29122_CommonData.yami#/components/schémas/Durationsec' reachabilityType:

$ref : ' #/components/schetnas/ReachabilityType ' maximumLa t e ncy:

Sref: 'TS29122_CommonData.yaml#/components/schemas/DurationSec' max imumResponseTime:

$ref: 'ΤΞ2 9122_CommonData.yaml#/components/schémas/DurationSec' suggestedNumberOfDIRackets :

type : integer minimum : 0 description: If monitoringType is UE_REACHABILITY, this parameter may be included to identify the number of packets that the serving gateway shall buffer in case that the UE is not reachable.

idleStatusIndication :

type : boolean description: If monitoringType is set to UE_REACHABILITY or ⁿAVAllABll.lTY_AFTER_DDN_FAlLURE, this parameter may be included to indicate the notification of when a UE, for which PSM is enabled, transitions into idle mode. true indicate enabling of notification - false indicate no need to notify Default false”.

locationType:

Sref: '#/components/schémas/LocationType' accuracy:

Sref: ’#/components/schémas/Accuracy' minimumReportInterval :

$ref: 'TS29122_CommonData.yaml#/components/schémas/DurationSec' associationType:

Jref: '#/components/schémas/AssociationType' plmnlndication: type: boolean description: If monitoringType is ROAMIUG_STATUS”. this parameter may be included to indicate the notification of UE¹ s Serving PLMN ID. -true The value shall be used to indicate enabling of notification; - false The value shall be used to indicate disabling of notification. Default false.

locationArea:

$ref: ^rTS29122_CommonData.yaml#/components/schémas/LocationArea’ locationAreaSG:

$ref : ’TS2 9122_CoïnmonData . yaml·if/components/schemas/LocationAreaSG ' dddTraDes:

$ref :

* TS2 9508_Nsmf_EventExposure-yaml#/components/schémas/DddTraf £ icDescriptor^f dddStati:

type : array items:

?ref? ^JTS2^5gS Nsmf Æven tExpc^ure » yam l#/camponen ts/schamas/DddSta tus ^r api JTantes :

__________array __________items:

_____________type ; g tring minltems: 1 monitoringEventReport :

$ref: ¹S/components/sohemas/MonitoringEventReport¹ required:

- notificationDestination

- monitoringType anyOf:

- required: [maximumKumberOfReports]

- required: [monitorExpireTimel

MonitoringNotification:

type: object properties:

subscript ion :

Sref: 'TS2 9122_CommonData.yaml#/components/schemas/Link' configResultS: type: array items :

$ref : ' TS29122_CommonData.yaml#/components/schemas/ConfigResult ' minltems: 1 description: Each element identifies a notification of grouping configuration resuit.

monitoringEventReports: type : array items:

$ r e f : ¹ # / c ompone nt s/schemas/Monitor ingEve ntReport¹ minltems: 1 description: Monitoring event reports.

cancellnd:

type : boolean description: Indicates whether to request to cancel the corresponding monitoring subscription. Set to false or omitted otherwise.

appliedParam:

$ref: '#/components/schémas/AppliedParameterConfiguration' required:

- subscription

MonitoringEventReport :

type: object properties:

ImeiChange:

Sref: '#/components/schémas/AssociationType' externalld:

Sref: 'TS29122_CommonData.yaml#/components/schémas/ExternalId¹ idleStatusInfo:

Sref: 'ü/components/schémas/IdleStatusInfo¹ locationlnfo:

$ref: '#/components/schémas/Locationlnfo' lossOfConnectReason: type : integer description: If monitoringType is LOSS_OF_CONNECTIVITY’', this parameter shall be included if available to identify the reason wby loss of connectivity is reported. Refer to 3GPP TS 29.33S [11] Subclause 8.4,58.

maxURAvailabilityTime :

§ref: 'TS2 9122_CommonData.yaml#/components/schémas/DateTime' msisdn:

Sref: 'TS2 9122_CommonData.yaml#/components/schémas/Msisdn’ monitoringType :

Sref: '#/components/schémas/MonitoringType¹ uePerLocationReport:

Sref: '#/components/schémas/UePerLoca t ionReport¹ plmnld:

Sref: 'TS29122_CommonData.yaml#/components/schemas/PlmnId' reachabilityTyp©:

$ref : ' tt/components/sehemas/ReachabilityType¹ roamingStatus: type : boolean description: If monitoringType is ROAMING-STATUS_t this parameter shall be set to true if the UE is on roaming status. Set to false or omitted otherwise.

failureCause:

$ref: ¹#/components/schémas/FailureCause¹ eventTime:

$ref: ^rTS29122_CommonData.yaml#/components/schémas/DateTime^f pdnConnlnfO :

$ref: ^r #/components/schémas/PdnConnectionlnformation¹ dddStatus :

$ref: ’TS29508_Nsmf_EventExposure.yaml#/comportents/schémas/Dddstatus¹ maxWaitTime:

$ref: ·TS29122_CommonData.yaml#/components/schemas/DateTime' requirëd: - monitoringType

IdleStatusInfo t type: object properties: activeTime : $ref: ’TS29122_ComrnoilData.yaml#/components/schemas/DurationSec¹ edrxCycleLength: format: float type : number minimum: 0 suggestedNumberOfDlPackets: type: integer minimum: 0 description: Identifies the number of packets shall be buffered in the serving gateway. It shall be présent if the idle status indication is requested by the SCS/AS with idleStatusIndication in the ^ri mon.it or ingEvent Subscript ion sets to true”. idleStatusTimestamp:

$ref: ^hTS29122_CommonData.yaml#/components/schémas/DateTime' periodicAUTimer:

$ref: ^h TS2 9122_CommonData.yaml#/components/schemas/DurationSec^h UePerLocationReport: type: object properties: ueCount: type: integer minimum: 0 description: Identifies the number of UEs.

extemal Ids : type : array items :

$ref: ¹TS29122_CommonData.yaml#/components/schemas/Externalld' minltems: 1 description: Each element uniquely identifies a user, msisdns:

type : array i t ems:

$ref: ¹TS29122_CommonData.yaml#/components/schemas/Msisdn' minltems: 1 description.: Each element identifies the MS internai PSTN/ISDN number allocated for a UE. required: - ueCount Locat ionlnfor type: object properties:

ageOfLocationlnfo:

$ref: 'TS29122_CommonData.yaml#/components/schémas/DurâtionMin¹ cellld:

type: string description: Indicates the Cell Global Identification of the user which identifies the cell the UE is registered.

enodeBId: type: string description: Indicates the eNodeB in which the UE is currently located.

rout ingAreaId: type : string description: Identifies the Routing Area Identity of the user where the UE is located.

trackingAreald:

type: string

description;	Identifies	the	Tracking Area Identity of the user 1	where the UE
is located. plmnld: type: string description:	Identifies	the	PLMN Identity of the user where the	UE is
located. twanld: type: string description:	Identifies	the	TWAN Identity of the user where the	UE is

located.

géographieArea:

$ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/GeographicArea¹ FailureCause: type: object properties:

bssgpCause:

type : integer

	description: Identifies a non-transparent copy	of	the BSSGP cause code	. Refer
to 3GPP 3 GP P TS	TS 29.128 [12], causeType: type: integer description: Identify the type of the SIAP-Cause. 29.128 [12]. gmmCau.se : type : integer	Refer to
to 3GPP	description: Identifies a non-transparent copy TS 29.128 [12]. ranapCause: type: integer	of	the GMM cause code.	Refer
	description: Identifies a non-transparent copy	of	the RANAP cause code	. Refer

to 3GPP TS 29.128 [12].

ranNasCause: type: string description: Indicates RAN and/or NAS release cause code information, TWAN release cause code information or untrusted WLAN relea.se cause code information. Refer to 3GPP TS 29.214 [10].

siApCause: type: integer

description: Identifies a non-transparent copy of	the S1AP cause code. Refer
to 3GPP TS 29.123 [12]. smCause: type: integer description: Identifies a non-transparent copy of	the SM cause code. Refer to
3GPP TS 29.128 [12]. PdnConne c t i onInformatiοn: type: object properties: status : $ref : 1#/components/schémas/PdnConnectionStatus' apn : type: string description: Identify the APN, it is depending on	the SCEF local

configuration whether or not this attributs is sent to the SCS/AS, pdnType:

$ref: ¹^/components/schémas/PdnType¹ interfaceïnd:

$ref: ¹#/components/schémas/InterfaceIndication’ ipv4Addr:

$ref: ¹TS29122_CommohData.yaml#/components/schémas/Ipv4Addr¹ ipvôAddr:

$ref: ’TS29122_CommonData.yaml#/components/schémas/Ipv$Addr¹ required: - status - pdnType anyOf:

- required: [ipv4Addr]

- required: [ipv6Addr]

AppliedParameterConfiguration:

type: object properties: externallds: type : array items :

$ref; ¹TS29122_CommonData.yaml#/components/schémas/Externalld¹ minltems: 1 description: Each element uniquely identifies a user, msisdns: type; array items :

$ref : ^h TS2 9122_CommonData - yamlfi/components/schemas/Msisdn ¹ minltems: 1 description: Each element identifies the MS internai PSTN/ISDN number allocated for a UE, max i mumLa t en cy:

$ref ; ¹ TS29122_CommonData - yaml#/components/schémas/DurationSec ¹ maximumResponseTime:

$ref; ¹TS29122_CommonData.yaml#/cornponents/schemas/DurationSec¹ maximumDetectionTime:

$ref: ¹TS29122_CommonData.yaral#/components/schemas/DurationSec * MonitcringType:

anyOf:

- type: string enum:

- LOSS_OF_CONNECTIVITY

- UE_REACHABILITY

- LOCATION_REPORTING

- CHANGE_OF_IMSI_IMEI_ASSOCIATION

- ROAMING-STATUS

- COMMUN I CAT ION_FAI DURE

- AVAILABILÏTY_AFTER_DDN_FAILURE

- NUMBER_OF_UES_IN_AN_AREA

- PDN_CONNECTIVITY_STATUS

- DOWNLINK_DATA_DELIVERY_STATUS

- type: string descriptions > This string provides forward-compatibility with future extensions to the énumération but is not used to encode content defined in the présent version of this API. description: > Possible values are

- LOSS-OF_CONNECTIVITY: The SCS/AS requests to be notified when the 3GPF network detects that the UE is no longer reachable for signalling or user plane commun i c a t i on

- UE—REACHABILITY: The SCS/AS requests to be notified when the UE becomes reachable for sending either SMS or downlink data to the UE

- LOCATION—REPQRTING: The SCS/AS requests to be notified of the Current location or the last known location of the UE

- CHANGE-OF-IMSI-IMEI_ASSOCIATION: The SCS/AS requests to be notified when the association of an ME (IMEI(SV)) that uses a spécifia subsaription (IMSI) is changed

- ROAMING—STATUS ; The SCS/AS queries the UE ^h s current roaming status and requests to get notified when the status changes

- COMMUNICATION—FAILURE: The SCS/AS requests to be notified of communication failure events

- AVAILABILITY—AFTER—DDN—FAILURE: The SCS/AS requests to be notified when the UE has become available after a DDN failure

- NUMBER—OF—UES—IN—AN—AREA: The SCS/AS requests to be notified the number of UEs in a given géographie area

- PDN—CONNECTIVITY—STATUS : The SCS/AS requests to be notified when the 3GPP network detects that the UE's PDN connection is set up or torn down

- DOWNLINK—DATA—DELIVERY—STATUS : The AF requests to be notified when the 3GPP network detects that the downlink data delivery status is changed.

ReachabilityType:

anyOf:

- type: string enum:

- SMS

- DATA

- type: string description: > This string provides forward-compatibility with future extensions to the énumération but is not used to encode content defined in the présent version of this API.

description: >

Possible values are

- SMS : The SCS/AS requests to be notified when the UE becomes reachable for sending SMS to the UE

- DATA: The SCS/AS requests to be notified when the UE becomes reachable for sending downlink data to the UE

LocationType:

anyOf:

- type : string enum:

- CURRENT_LOCATION

- LAST_KNOWN_LOCATIOU - type : string description: >

This string provides forward-compatibility with future extensions to the énumération but is not used to encode content defined in the présent version of this API. description: > Possible values are

- CURRENT_LOCATION: The SCS/AS requests to be notified for current location

- LAST_KNOWN_LOCATION: The SCS/AS requests to be notified for last known location

AssociationType: anyOf: - type: string enum : - ΙΜΞΙ - IMEISV - type: string description: >

This string pxovid.es forward-compatibility with future extensions to the énumération but is not used to encode content defined in the présent version of this API. description: > Possible values are

- IMEI: The value shall be used when the change of IMSI-IMEI association shall be detected

- IMEISV: The value shall be used when the change of IMSI-IMEÏSV association shall be detected

Accuracy: anyOf: - type: string enum : - CGI_ECGI - ENODEB - TA_RA - PLMN - TWAN-ID - GEO_AREA - type: string description: >

This string provides forward-compatibility with future extensions to the énumération but is not used to encode content defined in the présent version of this API. description: Possible values are

- CGI_ECGI: The SCS/AS requests to be notified. at cell level location accuracy. - ENODEB: The SCS/AS requests to be notified at eNodeB level location accuracy. - TA_RA: The SCS/AS requests to be notified at TA/RA level location accuracy.

- PLMN: The SCS/AS requests to be notified at PLMN level location accuracy.

- TWAN_ID: The SCS/AS requests to be notified at TWAN identifier level location accuracy.

- GEO_AREA: The SCS/AS requests to be notified of the geographical area accuracy.

PdnConnectionStatus:

anyOf:

- type: atring enum :

- CREATED

- RELEASED * type: string description: >

This string provides forward-compatibility with future extensions to the énumération but is not used to encode content defined in the présent version of this API. description: > Possible values are - CREATED : The PDN connection is created. - RELEASED: The PDN connection is released.

PdnType:

anyOf:

- type: string enum:

- IP

- NON-IP

- type; string description: > This string provides forward-compatibility with future extensions to the énumération but is not used to encode content defined in the présent version of this API.

description: > Possible values are - IP: FDM connection of IP type. - NON_IP: PDN connection of non-IP type. InterfaceIndication;

anyQf:

- type; string enum:

- EXPOSURE_FUNCTION

- PDN-GATEWAY

- type: string description; > This string provides forward-compatibility with future extensions to the énumération but is not used to encode content defined in the présent version of this API.

description: > Possible values are - EXPOSURE-FONCTION : SCEF is used for the PDN connection towards the SCS/AS. - PDN_GATEWAY: PDN gateway is used for the PDN connection towards the SCS/AS* *** End of Changes to 3GPP TS 29.122 ***

Figure 5

[0071] Figure 5 is a schematic block diagram of a network node 500 according to some embodiments of the présent disclosure. Optional features are represented by dashed boxes. The network node 500 may be, for example, a rare network node or a radio access network node. The network node 500 may be, for example, a base station 102 or 106 or a network node that implements ail or part of the functionality of the base station 102 or gNB described herein. As illustrated, the network node 500 includes a control System 502 that includes one or more processors 504 (e.g., Central Processing Units (CPUs), Application Spécifie Integrated Circuits (ASICs), Field Programmable GateArrays (FPGAs), and/or the like), memory 506, and a network interface 508, The one or more processors 504 are also referred to herein as processing circuitry. In addition, the network node 500 may include one or more radio units 510 that each includes one or more transmitters 512 and one or more recel vers 514 coupled to one or more antennas 516. The radio units 510 may be referred to or be part of radio interface circuitry. In some embodiments, the radio unit(s) 510 is external to the control System 502 and connected to the control System 502 via, e.g., a wired connection (e.g., an optical cable). However, in some other embodiments, the radio unit(s) 510 and potentially the antenna(s) 516 are integrated together with the control System 502. The one or more processors 504 operate to provide one or more fonctions of a network node 500 as described herein. In some embodiments, the function(s) are implemented in software that is stored, e.g., in the memory 506 and executed by the one or more processors 504.

Figure 6

[0072] Figure 6 is a schematic biock diagram that illustrâtes a virtualized embodiment of the network node 500 according to some embodiments of the présent disclosure. This discussion is equally applicable to othertypes of network nodes. Further, othertypes ofnetwork nodes may hâve similar virtualized architectures. 5 Again, optional features are represented by dashed boxes.

[0073] As used herein, a “virtualized radio access node is an implémentation of the network node 500 in which at least a portion of the functionality of the network node 500 is implemented as a Virtual component(s) (e.g., via a Virtual machine(s) executing on a physical processing node(s) in a network(s)). As illustrated, in this example, the network node 500 may include the control system 502 and/or the one or more radio units 10 510, as described above. The control system 502 may be connected to the radio unit(s) 510 via, for example, an optical cable or the like. The network node 500 includes one or more processing nodes 600 coupled to or inciuded as part of a network(s) 602. If présent, the control system 502 or the radio unit(s) are connected to the processing node(s) 600 via the network 602. Each processing node 600 includes one or more processors 604 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 606, and a network interface 608.

[0074] In this example, functions 610 of the network node 500 described herein are implemented at the one or more processing nodes 600 or distributed across the one or more processing nodes 600 and the control system 502 and/or the radio unit(s) 510 in any desired manner. In some particular embodiments, some or ali ofthe functions 610 ofthe network node 500 described herein are implemented as Virtual components executed by one or more Virtual machines implemented in a Virtual environment(s) hosted by the processing node(s) 20 600. As will be appreciated by one of ordinary skili in the art, additional signaling or communication between the processing node(s) 600 and the control system 502 is used in order to carry out at least some of the desired functions 610, Notably, in some embodiments, the control system 502 may not be inciuded, in which case the radio unit(s) 510 communicate directly with the processing node(s) 600 via an appropriate network interface(s). [0075] In some embodiments, a computer program including instructions which, when executed by at 25 least one processor, causes the at least one processor to carry out the functionality of network node 500 or a node (e.g., a processing node 600) implementing one or more of the functions 610 ofthe network node 500 in a Virtual environment according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a 30 non-transitory computer readable medium such as memory).

Figure 7

[0076] Figure 7 is a schematic biock diagram of the network node 500 according to some other embodiments of the présent disclosure. The network node 500 includes one or more modules 700, each of which is implemented in software. The module(s) 700 provide the functionality of the network node 500 35 described herein. This discussion is equally applicable to the processing node 600 of Figure 6 where the modules 700 may be implemented at one ofthe processing codes 600 ordistributed across multiple processing nodes 600 and/or distributed across the processing node(s) 600 and the control system 502.

Figure 8

[0077] Figure 8 is a schematic block diagram of a wireless communication device 800 according to some embodiments of the présent disclosure. As illustrated, the wireless communication device 800 includes one or more processors 802 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 804, and one or more transceivers 806 each including one or more transmitters 808 and one or more receivers 810 coupled to one or more antennas 812. The transceiver(s) 806 includes radio-front end circuitry connected to the antenna(s) 812 that is configured to condition signais communicated between the antenna(s) 812 and the processor(s) 802, as will be appreciated by on of ordinary skill in the art, The processors 802 are also referred to herein as processing circuitry, The transceivers 806 are also referred to herein as radio circuitry. In some embodiments, the functionality of the wireless communication device 800 described above may be fully or partially implemented in software that is, e.g., stored in the memory 804 and executed by the processor(s) 802. Note that the wireless communication device 800 may include additional components not illustrated in Figure 8 such as, e.g., one or more user interface components (e.g., an input/output interface including a display, buttons, a touch screen, a microphone, a speaker(s), and/or the like and/or any other components for allowing input of information into the wireless communication device 800 and/or allowing output of information from the wireless communication device 800), a power supply (e.g., a battery and associated power circuitry), etc.

[0078] In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the wireless communication device 800 according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

Figure 9

[0079] Figure 9 is a schematic block diagram of the wireless communication device 800 according to some other embodiments of the présent disclosure. The wireless communication device 800 includes one or more modules 900, each of which is implemented in software, The module(s) 900 provide the functionality of the wireless communication device 800 described herein.

Some Embodiments

[0080] Some embodiments described above may be summarized in the following manner:

1. A method for reporting Application Programming Interface, API, capability change according to an API filter, the method comprising:

at a first node within a télécommunication core network:

receiving (400), from a requesting entity, a request to be notified of an API capability change related to an identified wireless device, the request identifying a set of one or more APIs to be monitored;

subscribing (402,404) to receîve notifications of a core network type change for the identified wireless device;

receiving (414) a notification that the identified wireless device has changed from a first type of core network to a second type of core network;

determining (418) an API capability change from the first type of core network to the second type of core network for the identified set of one or more APIs to be monitored; and reporting (420), to the requesting entity, the API capability change for the identified set of one or more APIs to be monitored and not reporting the API capability change for APIs not in the identified set.

2. The method of embodiment 1 wherein the first node comprises a node for exposing services and capabilities of a télécommunication core network to entities outside of the télécommunication core network.

3. The method of embodiment 2 wherein the first node comprises a Service Capability Exposure Function, SCEF, a Network Exposure Function, NEF, or a combined SCEF+NEF.

4, The method of any one of embodiment 1 - 3 wherein the requesting entity comprises an Application Function, AF, a Service Capability Server, SCS, and/or an Application Server, AS.

5. The method of any one of embodiment 1 - 4 wherein receiving (400) the request to be notified of an API capability change related to an identified wireless device comprises receiving a monitoring request.

6. The method of any one of embodiment 1 - 5 wherein subscribing (402,404) to receîve notifications of a core network type change for the identified wireless device comprises sending a subscribe request to a node comprising a Home Subscriber Server, HSS, a Unified Data Management fonction, UDM, or a combined HSS+UDM.

7. The method of any one of embodiment 1 - 6 wherein subscribing (402,404) to receîve notifications of a core network type change for the identified wireless device comprises sending a Nudm_EventExposure_Subscribe Request.

8. The method of any one of embodiment 1 - 7 wherein receiving (414) a notification that the identified wireless device has changed from a first type of core network to a second type of core network comprises receiving a Nudm_EventExposure_Notify Response.

9. The method of any one of embodiment 1 - 8 wherein reporting (420) the API capability change comprises sending a monitoring indication request,

10. A method for reporting Application Programming Interface, API, capability change according to an API filter, the method comprising:

at a requesting entity:

sending (400), to a first node within a télécommunication core network, a request to be notified of an API capability change related to an identified wireless device, the request identifying a set of one or more APIs to be monitored; and receiving (420), from the first node, a notification of an API capability change related to the identified wireless device, the notification including the API capability change for the identified set of one or more APIs to be monitored and not including an API capability change for APIs not in the identified set.

11, The method of embodiment 10 wherein sending (400) the request to the first node comprises sending the request to a node for exposing services and capabilities of a télécommunication core network to entities outside of the télécommunication core network.

12. The method of embodiment 11 wherein the first node comprises a Service Capability Exposure Function, SCEF, a Network Exposure Function, NEF, or a combined SCEF+NEF.

13. The method of any one of embodiment 10 -12 wherein the requesting entity comprises an Application Function, AF, a Service Capability Server, SCS, and/or an Application Server, AS.

14. The method of any one of embodiment 10 -13 wherein sending (400) the request to be notified of an API capability change related to an identified wireless device comprises sending a monitoring request.

15. The method of any one of embodiment 10-14 wherein receiving (420) the notification of an API capability change related to the identified wireless device comprises receiving a monitoring indication request.

16. A network node (500) for reporting Application Programming Interface, API, capability change according to an API filter, the network node comprising:

one or more processors (504); and memory (506) storing instructions exécutable by the one or more processors, whereby the network node is opérable to:

receive (400), from a requesting entity, a request to be notified of an API capability change related to an identified wireless device, the request identifying a set of one or more APIs to be monitored;

subscribe (402,404) to receive notifications of a core network type change for the identified wireless device;

receive (414) a notification that the identified wireless device has changed from a first type of core network to a second type of core network;

détermine (418) an API capability change from the first type of core network to the second type of core network for the identified set of one or more APIs to be monitored; and report (420), to the requesting entity, the API capability change for the identified set of one or more APIs to be monitored and not reporting the API capability change for APIs not in the identified set.

17. The network node of embodiment 16 comprising a node for exposing services and capabilities of a télécommunication core network to entities outside of the télécommunication core network.

18. The network node of embodiment 17 comprising a Service Capability Exposure Function, SCEF, a Network Exposure Function, NEF, or a combined SCEF+NEF.

19. The network node of any one of embodiment 16-18 wherein receiving (400) the request to be notified of an API capability change related to an identified wireless device comprises receiving a monitoring request.

20. The network node of any one of embodiment 16-19 wherein subscribing (402,404) to receive notifications of a core network type change for the identified wireless device comprises sending a subscribe request to a node comprising a Home Subscriber Server, HSS, a Unified Data Management function, UDM, or a combined HSS+UDM.

21. The network node of any one of embodiment 16 - 20 wherein subscribing (402,404) to receive notifications of a core network type change for the identified wireless device comprises sending a Nudm_EventExposure_Subscribe Request.

22. The network node of any one of embodiment 16-21 wherein receiving (414) a notification that the identified wireless device has changed from a first type of core network to a second type of core network comprises receiving a Nudm_EventExposureJtotify Response.

23. The network node of any one of embodiment 16 - 22 wherein reporting (420) the API capability change comprises sending a monitoring indication request.

24. A network node (500) configured for reporting Appiication Programming Interface, API, capability change according to an API filter, the network node comprising processing cîrcuity (504) adapted to:

_receive (400), from a requesting entity, a request to be notified of an API capability change related to an identified wireless device, the request identifying a set of one or more APIs to be monitored;

subscribe (402,404) to receive notifications of a core network type change for the identified wireless device;

receive (414) a notification that the identified wireless device has changed from a first type of core network to a second type of core network;

déterminé (418) an API capability change from the first type of core network to the second type of core network for the identified set of one or more APIs to be monitored; and report (420), to the requesting entity, the API capability change for the identified set of one or more APIs to be monitored and not reporting the API capability change for APIs not in the identified set.

25. The network node of embodiment 24 comprising a node for exposing services and capabilities of a télécommunication core network to entities outside of the télécommunication core network.

26. The network node of embodiment 25 comprising a Service Capability Exposure Function, SCEF, a Network Exposure Function, NEF, or a combined SCEF+NEF.

27. The network node of any one of embodiment 24 - 26 wherein receiving (400) the request to be notified of an API capability change related to an identified wireless device comprises receiving a monitoring request

28. The network node of any one of embodiment 24 - 27 wherein subscribing (402,404) to receive notifications of a core network type change for the identified wireless device comprises sending a subscribe request to a node comprising a Home Subscriber Server, HSS, a Unified Data Management function, UDM, or a combined HSS+UDM.

29. The network node of any one of embodiment 24 - 28 wherein subscribing (402,404) to receive notifications of a core network type change for the identified wireless device comprises sending a Nudm_EventExposure_Subscribe Request.

30, The network node of any one of embodiment 24 - 29 wherein receiving (414) a notification that the identified wireless device has changed from a first type of core network to a second type of core network comprises receiving a Nudm_EventExposure_Notify Response,

31. The network node of any one of embodiment 24 - 30 wherein reporting (420) the API capability change comprises sending a monitoring indication request.

32, A network node (500) for reporting Application Programming Interface, API, capability change according to an API filter, the network node comprising modules (700) adapted to:

receive (400), from a requesting entity, a request to be notified of an API capability change related to an identified wireless device, the request identifying a set of one or more APIs to be monitored;

subscribe (402,404) to receive notifications of a core network type change for the identified wireless device;

_receive (414) a notification that the identified wireless device has changed from a first type of core network to a second type of core network;

déterminé (418) an API capability change from the first type of core network to the second type of core network for the identified set of one or more APIs to be monitored; and report (420), to the requesting entity, the API capability change for the identified set of one or more APIs to be monitored and not reporting the API capability change for APIs not in the identified set.

33. The network node of embodiment 32 comprising a node for exposing services and capabilities of a télécommunication core network to entities outside of the télécommunication core network.

34. The network node of embodiment 33 comprising a Service Capability Exposure Function, SCEF, a Network Exposure Function, NEF, or a combined SCEF+NEF.

35. The network node of any one of embodiment 32 - 34 wherein receiving (400) the request to be notified of an API capability change related to an identified wireless device comprises receiving a monitoring request.

36. The network node of any one of embodiment 32 - 35 wherein subscribing (402,404) to receive notifications of a core network type change for the identified wireless device comprises sending a subscribe request to a node comprising a Home Subscriber Server, HSS, a Unified Data Management function, UDM, or a combined HSS+UDM.

37. The network node of any one of embodiment 32 - 36 wherein subscribing (402,404) to receive notifications of a core network type change for the identified wireless device comprises sending a Nudm_EventExposure_Subscribe Request.

38. The network node of any one of embodiment 32 - 37 wherein receiving (414) a notification that the identified wireless device has changed from a first type of core network to a second type of cote network comprises receiving a Nudm_EventExposure_Notify Response.

39. The network node of any one of embodiment 32 -38 wherein reporting (420) the API capability change comprises sending a monitoring indication request,

40. A network node (500) for reporting Application Programming Interface, API, capability change according to an API filter, the network node comprising:

one or more processors (504); and memory (506) storing instructions exécutable by the one or more processors, whereby the network node is opérable to:

send (400), to a first node within a télécommunication core network, a request to be notified of an API capability change related to an identified wireless device, the request identifying a set of one or more APIs to be monitored; and receive (420), from the first node, a notification of an API capability change related to the identified wireless device, the notification including the API capability change for the identified set of one or more APIs to be monitored and not including an API capability change for APIs not in the identified set.

41. The network node of embodiment 40 wherein sending (400) the request to the first node comprises sending the request to a node for exposing services and capabilities of a télécommunication core network to entities outside of the télécommunication core network.

42. The network node of embodiment 41 wherein the first node comprises a Service Capability Exposure Function, SCEF, a Network Exposure Function, NEF, or a combined SCEF+NEF,

43. The network node of any one of embodiment 40 - 42 wherein the requesting entity comprises an Application Function, AF, a Service Capability Server, SCS, and/or an Application Server, AS.

44. The network node of any one of embodiment 40 - 43 wherein sending (400) the request to be notified of an API capability change related to an identified wireless device comprises sending a monitoring request.

45, The network node of any one of embodiment 40 - 44 wherein receiving (420) the notification of an API capability change related to the identified wireless device comprises receiving a monitoring indication request.

46. A network node (500) configured for reporting Application Programming Interface, API, capability change according to an API filter, the network node comprising processing circuity (504) adapted to:

send (400), to a first node within a télécommunication core network, a request to be notified of an API capability change related to an identified wireless device, the request identifying a set of one or more APIs to be monitored; and receîve (420), from the first node, a notification of an API capability change related to the identified wireless device, the notification including the API capability change for the identified set of one or more APIs to be monitored and not including an API capability change for APIs not in the identified set.

47. The network node of embodiment 46 wherein sending (400) the request to the first node comprises sending the request to a node for exposing services and capabilities of a télécommunication core network to entities outside of the télécommunication core network.

48. The network node of embodiment 47 wherein the first node comprises a Service Capability Exposure Function, SCEF, a Network Exposure Function, NEF, or a combined SCEF+NEF.

49. The network node of any one of embodiment 46 - 48 wherein the requesting entity comprises an Application Function, AF, a Service Capability Server, SCS, and/or an Application Server, AS.

50. The network node of any one of embodiment 46 - 49 wherein sending (400) the request to be notified of an API capability change related to an identified wireless device comprises sending a monitoring request.

51. The network node of any one of embodiment 46 - 50 wherein receiving (420) the notification of an API capability change related to the identified wireless device comprises receiving a monitoring indication request.

52. A network node (500) for reporting Application Programming Interface, API, capability change according to an API filter, the network node comprising modules (700) adapted to:

send (400), to a first node within a télécommunication core network, a request to be notified of an API capability change related to an identified wireless devise, the request identifying a set of one or more APIs to be monitored; and receive (420), from the first node, a notification of an API capability change related to the identified wireless device, the notification including the API capability change for the identified set of one or more APIs to be monitored and not including an API capability change for APIs not in the identified set

53. The network node of embodiment 52 wherein sending (400) the request to the first node comprises sending the request to a node for exposing services and capabilities of a télécommunication core network to entities outside of the télécommunication core network.

54. The network node of embodiment 53 wherein the first node comprises a Service Capability Exposera Function, SCEF, a Network Exposure Fonction, NEF, or a combined SCEF+NEF.

55. The network node of any one of embodiment 52 - 54 wherein the requesting entity comprises an Application Function, AF, a Service Capability Server, SCS, and/or an Application Server, AS,

56, The network node of any one of embodiment 52 - 55 wherein sending (400) the request to be notified of an API capability change related to an identified wireless device comprises sending a monitoring request.

57. The network node of any one of embodiment 52 -56 wherein receiving (420) the notification of an API capability change related to the identified wireless device comprises receiving a monitoring indication request.

[0081] Any appropriate steps, methods, features, fonctions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more Virtual apparatuses. Each Virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include DSPs, special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as ROM, RAM, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more télécommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implémentations, the processing circuitry may be used to cause the respective functional unit to perform corresponding fonctions according one or more embodiments of the présent disclosure.

[00 82] While processes in the figures may show a particular order of operations performed by certain embodiments of the présent disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform the operations in a different order, combine certain operations, overlap certain operations, etc.).

[0083] At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subséquent listing(s).

- 3GPP	Third Génération Partnership Project
5 · 4G	Fourth Génération
• 5G	Fifth Génération
• 5GC	Fifth Génération Core network
• 5GS	Fifth Génération System
• AF	Application Function
10 · AMF	Core Access and Mobility Management Function
• AN	Access Network
• AP	Access Point
• API	Application Programming Interface
• AS	Application Server
15 · AUSF	Authentication Server Function
- CN	Core Network
• DN	Data Network
• DSP	Digital Signal Processor
• eNB	Enhanced or Evolved Node B
20 · EPC	Evolved Packet Core
• EPS	Evolved Packet System
• gNB	New Radio Base Station
. GPRS	General Packet Radio Service
. HSS	Home Subscriber Server
25 · loT	internet of Things
• IP	Internet Protocol
• LTE	Long Term Evolution
• MME	Mobility Management Entity
. MITC	Machine Type Communication
30 · NEF	Network Exposure Function
• NF	Network Function
• NR	New Radio
• NRF	Network Function Repository Function
• NSSF	Network Slice Sélection Function
35 · OTT	Over-the-Top

*	PCF	Policy Control Function
•	P-GW	Packet Data Network Gateway
•	QoS	Quality of Service
•	RAN	Radio Access Network
5 ·	SCEF	Service Capability Exposure Function
•	SCS	Service Capability Server
•	SGSN	Serving General Packet Radio Service Support Node
•	SMF	Session Management Function
•	TS	Technicai Spécification
10	UDM	Unified Data Management
•	UE	User Equipment
[0084]	Those skilied in the adwill recognize improvements and modificationsto theembodimentsofthe
présent disclosure. AH such improvements and modifications are considered within the scope ofthe concepts

disclosed herein.

Claims (10)

1. A method for reporting Application Programming Interface, API, capability change according to an API filter, the method comprising:

ai a first node within a télécommunication core network, which first node comprises a combined Service Capability Exposure Function, SCEF, and Network Exposure Function, NEF,:

receiving (400), from a requesting entity that comprises an Application Function, AF, a monitoring request to be notified of an API capability change related to an identified wireless device associated with a service API, the monitoring request identifying a subset of one or more APIs in which the AF is interested to hâve monitored;

subscribing (402,404) to receîve notifications of a core network type change for the identified wireless device;

receiving (414) a notification that the identified wireless device has changed from a first type of core network to a second type of core network;

determining (418) an API capability change from the first type of core network to the second type of core network for the identified subset of one or more APIs in which the AF is interested and filtering out ail but the APIs in which the AF is interested; and reporting (420), to the requesting entity, the API capability change for the identified subset of one or more APIs in which the AF is interested and not reporting the API capability change for other APIs not in the identified subset.

2. The method of any one of claim 1 wherein subscribing (402,404) to receîve notifications of a core network type change for the identified wireless device comprises sending a subscribe request to a node comprising a Home Subscriber Server, HSS, a Unified Data Management function, UDM, or a combined HSS+UDM.

3. The method of any one of claims 1 - 2 wherein subscribing (402,404) to receîve notifications of a core network type change for the identified wireless device comprises sending a Nudm_EventExposure_Subscribe Request.

4, The method of any one of claims 1 - 3 wherein receiving (414) a notification that the identified wireless device has changed from a first type of core network to a second type of core network comprises receiving a Nudm_EventExposure_Notify Response,

5. The method of any one of claims 1 - 4 wherein reporting (420) the API capability change comprises sending a monitoring indication request.

6. A network node comprising a combined Service Capability Exposure Function, SCEF, and Network Exposure Function, NEF, (500) for reporting Application Programming Interface, API, capability change according to an API filter, the network node comprising:

one or more processors (504); and memory (506) storing instructions exécutable by the one or more processors, whereby the network node is operabie to:

receive (400), from a requesting entity comprising an Application Function, AF, a monitoring request to be notified of an API capability change related to an identified wireless device associated with a service API, the monitoring request identifying a subset of one or more APIs in which the AF is interested to hâve monitored;

subscribe (402,404) to receive notifications of a core network type change for the identified wireless device;

receive (414) a notification that the identified wireless device has changed from a first type of core network to a second type of core network;

déterminé (418) an API capability change from the first type of core network to the second type of core network for the identified subset of one or more APIs in which the AF is interested and fiitering out ail but the APIs in which the AF is interested; and report (420), to the requesting entity, the API capability change for the identified subset of one or more APIs in which the AF is interested and not reporting the API capability change for other APIs not in the identified subset.

7. The network node of claim 6 wherein subscribing (402,404) te receive notifications of a core network type change for the identified wireless device comprises sending a subscribe request to a node comprising a Home Subscriber Server, HSS, a Unified Data Management function, UDM, or a combined HSS+UDM.

8. The network node of any one of claims 6-7wherein subscribing (402,404) to receive notifications of a core network type change for the identified wireless device comprises sending a Nudm_EventExposure_Subscribe Request.

9. The network node of any one of daims 6-8 wherein receiving (414) a notification that the identified wireless device has changed from a first type of core network to a second type of core network comprises receiving a Nudm_EventExposure_Notify Response.

10. The network node of any one of daims 6-9 wherein reporting (420) the API capability change comprises sending a monitoring indication request.