Method and apparatus for event reporting by telecommunications network

Abstract

According to an aspect there is provided a method (1500) of operation by a network node. The method comprises: sending (1502) a subscription request, requesting an event notification for a specified event in the telecommunications network, and requesting an instant report of a current event state; receiving (1504) a subscription response as a reply to the subscription request, the subscription response omitting the current event state; and interpreting (1506) a first event notification received after the subscription response as indicating a new event detection or indicating a current event state as requested in the subscription request, depending on whether the subscription response indicates an unavailability of the current event state.

Description

Technical Field

[0001] The disclosed methods and equipment relate to incident reporting via telecommunications networks. Background Technology

[0002] In the context of cellular networks, event exposure plays a crucial role in the interaction between applications and core network functions. For example, in the context of the fifth-generation (5G) specifications issued by the 3rd Generation Partnership Project (3GPP), the Network Exposure Function (NEF) exposes the capabilities of the 3GPP network to third-party applications and forwards such requests to the network.

[0003] Event reporting serves several purposes, such as real-time monitoring and analysis. In this context, event reporting allows service providers and third-party applications to monitor network status and performance in real time. This includes things like user location, service consumption, and Quality of Service (QoS).

[0004] Incident reporting also supports policy control and billing. In this context, incident reporting aids in real-time decision-making by providing information about network usage and other events. This can influence billing mechanisms and enable more dynamic and flexible service provisioning.

[0005] Furthermore, incident reporting can provide the data necessary for managing and orchestrating network slices, ensuring that resources are appropriately allocated to different virtual networks according to their needs. Moreover, incident reporting can be used to ensure that only authorized third-party applications can access network functions, and it can be part of tracking and managing these permissions, as well as auditing and logging for security purposes. Incident reporting also aids in diagnosing network problems, optimizing services to improve user experience, integrating with third-party services, and complying with regulatory requirements. Summary of the Invention

[0006] The disclosed methods and apparatus address one or more problems associated with event reporting, such as preventing ambiguous event reporting and avoiding corresponding misinterpretations of event reports. One problem addressed is the behavior of nodes involved in an event report within the context of instant reporting. Using instant reporting, a node subscribing to an event report requests the current event state in the subscription response. However, there are several reasons why the current event state can be omitted from the subscription response, and the disclosed techniques avoid ambiguity at the requesting node by adding information to the subscription response.

[0007] One embodiment includes a method operated by a network node. The method includes: sending a subscription request requesting event notification for a specified event in a telecommunications network and requesting an immediate report of the current event state; receiving a subscription response as a reply to the subscription request, the subscription response omitting the current event state; and interpreting a first event notification received after the subscription response as indicating either the detection of a new event or the current event state as requested in the subscription request, depending on whether the subscription response indicates the unavailability of the current event state.

[0008] In such an embodiment, a network node can be understood as a requesting node because it initiates a subscription request. An example requesting node includes a communication circuit and processing circuitry operatively associated with that communication circuitry, i.e., configured to use the communication circuitry to exchange messages or other signaling with other entities, such as other network nodes of the same or different types. In an example embodiment of the requesting node, its processing circuitry is configured to: send a subscription request requesting event notification for a specified event in the telecommunications network and requesting an immediate report of the current event status; receive a subscription response as a reply to the subscription request, the subscription response omitting the current event status; and, depending on whether the subscription response indicates the unavailability of the current event status, interpret a first event notification received after the subscription response as indicating a new event detection or indicating the current event status as requested in the subscription request.

[0009] Another embodiment includes a method operated by a network node of a telecommunications network, wherein the method includes: receiving a subscription request requesting event notification for a specified event in the telecommunications network and requesting an immediate report for the current event state; and sending a subscription response as a reply to the subscription request, the subscription response omitting the current event state. The method further includes the network node including an indication of the unavailability of the current event state in the subscription response in response to determining that the current event state is unavailable.

[0010] In such an embodiment, a network node can be understood as a response node because it responds to subscription requests. An example response node includes a communication circuit and processing circuitry operatively associated with that communication circuitry, i.e., configured to use the communication circuitry to exchange messages or other signaling with other entities, such as other network nodes of the same or different types. In an example embodiment of the response node, its processing circuitry is configured to: receive a subscription request, requesting event notification for a specified event in the telecommunications network, and requesting an immediate report of the current event status; and send a subscription response as a reply to the subscription request, the subscription response omitting the current event status. To send the subscription response, the processing circuitry is configured to include an indication of the unavailability of the current event status in the subscription response in response to determining that the current event status is unavailable.

[0011] In at least one embodiment, the technique is extended to subscription requests and corresponding subscription responses involving multiple specified events. In at least one such embodiment, the response node is configured to include an unavailability indication on a per-specify-event basis, such that unavailability can be indicated on an individual basis for each specified event included in the subscription request. This indication can be explicit, such as a set or clear flag or other informational elements (IEs) included in the subscription response. Alternatively, the indication can be implicit, such as the response node interpreting the absence of the current event state in the subscription response for a given event among two or more specified events as an implicit indication of the unavailability of the current event state of the given event, provided that the subscription response includes the current event state of one or more other specified events among the specified events.

[0012] In at least one embodiment, in contrast to a subscription response that omits the requested current event state due to a lack of support for immediate reporting of the current event state, the responding node is configured to include an indication of unsupported status in the subscription response. Correspondingly, the receiving node is configured to recognize the inclusion of such information and interpret a first event notification received after the subscription response as an indication of the requested current event state, rather than an indication of new event detection.

[0013] Of course, the present invention is not limited to the features and advantages described above. In fact, those skilled in the art will recognize additional features and advantages upon reading the following detailed description and viewing the accompanying drawings. Attached Figure Description

[0014] Some embodiments of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings, in which: Figure 1 This is a signaling diagram of a situation where the current state is available and supports Instant Event Reporting (IERSR) in the subscription creation response for subscription; Figure 2 This is a signaling diagram for a situation where the current state between Access and Mobility Management Function (AMF) and Unified Data Management (UDM) is available but IERSR is not supported; Figure 3(a) is the signaling diagram for “Problem A”, in which the current state is unavailable regardless of IERSR support; Figure 3(b) is the signaling diagram for “Problem A”, where the current state is unavailable and the event is detected by the UDM; Figure 3(c) is the signaling diagram for “Problem A”, where the current state is unavailable and events are detected by the AMF (directly from the NEF subscription). Figure 4(a) is a signaling diagram of a scenario where the current state is available and supports Event Reporting Inquiry (ERIR) (an event detected by the Mobility Management Entity (MME)) in the response; Figure 4(b) is a signaling diagram of a scenario where the current state is available and supports ERIR (an event detected by the Home Subscriber Server (HSS)); Figure 5(a) is the signaling diagram for “Problem B1”, where the current state is available but does not support ERIR; Figure 5(b) is the signaling diagram for “Problem B1”, where the current state is available but does not support ERIR (the event is detected by HSS). Figure 6(a) is the signaling diagram for “Problem B2”, in which the current state is unavailable regardless of ERIR support; Figure 6(b) is the signaling diagram for “Problem B2”, in which the current state is unavailable regardless of ERIR support; Figure 7(a) is a signaling diagram illustrating the solution to "Problem A" under the "Current Status Unavailable" indication; Figure 7(b) is a signaling diagram illustrating the solution to "Problem A" under the "Current State Unavailable" indication, where the event is detected by the UDM; Figure 7(c) is a signaling diagram illustrating the solution to "Problem A" under the "Current State Unavailable" indication, where the event is detected by AMF (direct subscription). Figure 8(a) is a signaling diagram illustrating the solution to "Problem B1", where HSS represents the MME sending the "current status"; Figure 8(b) is a signaling diagram illustrating an alternative solution to “Problem B1”, where the HSS represents the MME sending the “current status” (where the event is detected by the HSS). Figure 9(a) is a signaling diagram illustrating the solution to “Problem B2”, in which a “Current Status Unavailable” indication is sent; Figure 9(b) is a signaling diagram illustrating an alternative solution to “Problem B2”, in which the HSS sends “Current state unavailable” (where the event is detected by the HSS). Figure 10 This is a signaling diagram illustrating a general example of the techniques described herein; Figure 11 This is a block diagram of a telecommunications network according to an exemplary embodiment; Figure 12 This is a block diagram illustrating the components of a network node arranged according to an example; Figure 13 This is a block diagram illustrating an exemplary implementation of the processing circuitry components of a network node; Figure 14 This is a block diagram illustrating another embodiment of a network node arrangement according to an exemplary method; Figure 15 This is a flowchart illustrating an exemplary operation method of a network node; Figure 16 This is a flowchart illustrating another exemplary method of operation for a network node; Figure 17 The event notification process is shown; Figure 18 The procedure for configuring monitoring events in the MME is shown; Figure 19 This illustrates the process by which NF service consumers subscribe to notifications; and Figure 20 The event notification process is shown. Detailed Implementation

[0015] An AF (Application Function) can subscribe to a NEF (Network Exposure Function) to request notification of certain events. This subscription request may include a request for "immediate reporting" (including the "immediateRep" flag in the MonitoringEventSubscription data type), which is included as part of the Northbound Application Programming Interface (API) (NEF to AF) enhancement in Rel-18 (function enNB1), see 3GPP Technical Standard (TS) 29.122 version 18.1.0: "T8 Reference Point for the Northbound API".

[0016] Real-time reporting requires that when a subscription request is received by the notification sender, the value of any current state existing for the requested notification should be provided and embedded in the subscription response. For example, if a real-time report is requested for an AOI (Region of Interest) event, that value should be included in the subscription response if the Access and Mobility Management Function (AMF) already has a value for that AOI (e.g., inputs, outputs).

[0017] If immediate reporting is requested via an intermediate node, both the intermediate node and the "notification sender" must support the Instant Event Reporting (IERSR) function in the subscription creation response to provide immediate reporting (in the subscription response). See the following excerpt from Clause 6.2.8, "Access and Mobility Management Services," of 3GPP TS 29.518 Release 18.1.0: In addition, see the following excerpt from Clause 6.4.8 of 3GPP TS 29.503 version 18.1.0: “Unified Data Management Services”: While there are different use cases, they share some similarities: Unified Data Management (UDM) receives subscription requests applied to the Evolved Packet Core (EPC) with an instruction to request "instant reporting," see Clause 5.5.2.2.2 of 3GPP TS 29.503 Release 18.1.0: "Unified Data Management Service". If the NF service consumer has already included an immediateFlag with a value of "true" in the individual UE's event subscription, then an indication regarding whether the subscription also applies to the EPC is included in the request and set to "true," and the NF service consumer has already indicated support. "IERSR" As per the feature (see Clause 6.4.8), when subscribing to events on the HSS, the UDM should instruct support... "ERIR" Features (see Clause 6.4.8 of 3GPP TS 29.563

[62] ). If received from HSS in the subscription creation response, the UDM should include the current state of the event in the EPC.

[0018] In this scenario, the UDM sends a subscription request to the Mobility Management Entity (MME) via the Home Subscriber Server (HSS), and as mentioned above, the Event Reporting Indicator (ERIR) feature in the response is relevant. See “Home Subscriber Server (HSS) Service for Interoperability with Unified Data Management (UDM)” in 3GPP TS 29.563 Release 18.1.0: Within the context of the disclosed technology, at least two scenarios are of interest: a) Subscription via Intermediate Network Function (NF) (without 4G / 5G interoperability) b) Subscribing to the MME via UDM+HSS (4G / 5G interoperability) It should be noted that, in the context of this disclosure, the Session Management Function (SMF) can be used in place of the AMF in the diagram.

[0019] a) Subscription via intermediate NF (no 4G / 5G interoperability) For example, NEF subscribes to AMF via UDM, and then AMF notifies NEF directly.

[0020] Figure 1 This is a signaling diagram showing the current state as available and supporting IERSR. For events detected by the AMF, see [link to AMF documentation]. Figure 1 The following description. In Figure 1 middle: Step 0: Prerequisite: IERSR features are supported end-to-end.

[0021] Step 1: Send an EE (Event Exposure) subscription request with the “Report Instantly” flag.

[0022] Step 2: The EE subscription request is sent to the UDM.

[0023] Step 3: The EE subscription request is sent to the AMF.

[0024] Step 4: The current state of the event is available; in this example, it is equal to "X". Since IERSR is supported by both AMF and UDM, the "current state" should be included in the subscription response.

[0025] Steps 5, 6, and 7: Send an EE subscription response that includes the "current status".

[0026] Step 8: The received event information (“X”) is correctly interpreted by the application function (AF) as the “current state”.

[0027] See below for Figure 2 Further description, Figure 2 This is a signaling diagram showing the available state when IERSR is not supported between the UDM and AMF. Figure 2 middle: Step 0: Prerequisite: The IERSR function is not supported by either AMF or UDM.

[0028] Steps 1, 2, and 3: Similar to Figure 1 .

[0029] Step 4: Since IERSR is not supported by either AMF or UDM, the "Current State" is not included in the subscription response. However, a notification should be sent to provide this value (Step 9).

[0030] Steps 5, 6, and 7: Similar to Figure 1 However, it does not include event information.

[0031] Step 8: Since there is no event information in the received subscription response, AF expects to receive the "current status" in a subsequent notification because the request sent by AF requested "instant reporting".

[0032] Steps 9 and 10: The AMF sends the available "current status" in a subsequent notification.

[0033] Step 11: The received event information is correctly interpreted as the "current state".

[0034] However, some problems can be identified as shown in Figure 3(a). Figure 3(a) is a signaling diagram illustrating "Problem A," where the current state is unavailable regardless of IERSR support. In Figure 3(a): Step 0: There are no prerequisites; IERSR may or may not be supported.

[0035] Steps 1, 2, and 3: Similar to Figure 1 .

[0036] Step 4: Regardless of whether IERSR is supported, the key point of this step is that the "current state" is unavailable.

[0037] It should be noted that, for example, in the case of user equipment (UE) mobility, when there is no UE context transfer between serving nodes (e.g., UE context is not supported between public land mobile networks (PLMNs) by different vendors), the "current state" is unavailable in the AMF; or some events such as "PDN [Packet Data Network] Connectivity State" (MME) or "Connectivity Loss" (AMF) do not necessarily have a "current state". Steps 5, 6, and 7: Similar to Figure 1 .

[0038] Step 8: Problem A1: When AF does not receive event information in the subscription response, it assumes that the "current state" will be provided in a subsequent notification. However, in this case, the current state is not available, and AF may wait for a long time, in fact, until an event is detected for that subscription.

[0039] Steps 9 and 10: When an event is detected by the AMF (e.g., event = Y), a notification is sent.

[0040] Step 11: Problem A2: The AF assumes that the received value corresponds to the "current state" that is being waited for, rather than a newly detected event. For example, it might assume the UE is "IN" when it has actually just been moved "IN", which would lead to an error.

[0041] A similar problem arises when the event is detected by the UDM. In this case, IERSR support is irrelevant because there is no intermediate NF. See the description of Figure 3(b) below, which is another signaling diagram of "Problem A" where the current state is unavailable and the event is detected by the UDM. In Figure 3(b): Steps 1 and 2: Similar to Figure 3(a).

[0042] Step 3: Since the current state is unavailable, send a subscription response without event information.

[0043] Steps 4 and 5: Similar to steps 6 and 7 in Figure 3(a).

[0044] Steps 6 to 9: Similar to steps 8 to 11 in Figure 3(a).

[0045] Furthermore, a similar issue arises for events detected by the AMF when subscribing directly from the NEF to the AMF. See the description of Figure 3(c) below, another signaling diagram of "Problem A," where the current state is unavailable and the event is detected by the AMF (subscribed directly from the NEF). In Figure 3(c): Similar to Figure 3(b), where AMF replaces UDM.

[0046] B) Subscribing to MME via UDM+HSS (4G / 5G interoperability) Referring to the description of Figure 4(a), which is a signaling diagram in which the current state is available and supports the ERIR (Events Detected by the MME) problem for events detected by the MME, in Figure 4(a): Step 0: Prerequisites: End-to-end support for providing event notifications in subscription responses. This requires support for Service Capability Exposure Functionality (SCEF) + NEF and IERSR functionality in UDM, while UDM and HSS should support ERIR functionality.

[0047] Steps 1, 2, and 3: The EE subscription request is sent along with the instant report. SCEF+NEF sends a request to UDM, which includes an indication that the request applies to EPC. UDM should then indicate support for ERIR to HSS.

[0048] Step 4: The HSS sends an EE subscription to the MME using an Insert Subscription Data Request (IDR) Diameter request.

[0049] Step 5: The current state should be provided in the response whenever it is available.

[0050] Step 6: Because the “Current State” is available, the event information (“Current State”) is included in the Insert Subscription Data Response (IDA) Diameter request.

[0051] Step 7: Since ERIR is supported (which indicates that the network is capable of providing event information in its response to AF), the "current state" is included in the response.

[0052] Steps 8, 9, and 10: Send an EE subscription response that includes the event information "Current Status".

[0053] Step 11: AF correctly interprets the received event information as the "current state".

[0054] The following description of Figure 4(b) applies when the event is detected by the HSS. Figure 4(b) is a signaling diagram of the problem where the current state is available and supports ERIR (an event detected by the HSS). In Figure 4(b): Steps 0 to 3: Similar to Figure 4(a).

[0055] Steps 4 to 8: Similar to steps 7 to 11 in Figure 4(a).

[0056] The problem is identified in Figure 5(a), which is the signaling diagram for "Problem B1," where the current state is available but ERIR is not supported. In Figure 5(a): Step 0: Prerequisite: ERIR functionality is not supported by either UDM or HSS. Steps 1 to 6: Similar to Figure 4(a).

[0057] Step 7: Since ERIR is not supported by both UDM and HSS, the "current status" is not included in the subscription response.

[0058] Steps 8, 9, and 10: Similar to Figure 4(a), but without event information.

[0059] Step 11: When a subscription response is received without event information, AF assumes that subsequent notifications will provide the "current status".

[0060] Step 12: Problem B1: No "current status" received. The 3GPP does not clearly describe how "current status" can be provided in this situation.

[0061] For cases where the event is detected by the HSS, a similar problem is identified, as described below with reference to Figure 5(b), which is a signaling diagram illustrating "Problem B1," where the current state is available but ERIR is not supported (the event is detected by the HSS). In Figure 5(b): Steps 0 to 3: Similar to Figure 5(a).

[0062] Steps 4 to 9: Similar to steps 7 to 12 in Figure 5(a).

[0063] Another problem was identified, see the description below of Figure 6(a), which is the signaling diagram for "Problem B2," where the current state is unavailable for an event detected by the MME, regardless of ERIR support. In Figure 6(a): Step 0: No prerequisites. ERIR support is irrelevant to this use case.

[0064] Steps 1 to 4: Similar to Figure 5(a).

[0065] Step 5: "Current Status" is unavailable.

[0066] Step 6: Regardless of whether ERIR is supported, the "current state" cannot be included in the subscription response because it is not available.

[0067] Steps 8, 9, and 10: Similar to Figure 5(a).

[0068] Step 11: Question B2: When AF receives a subscription response without event information and is asked to "report immediately", it will assume that a subsequent notification will provide the "current status", but the "current status" is not available.

[0069] Steps 12 and 13: When an event is detected by the MME (e.g., event = Y), a notification is sent.

[0070] Step 14: Problem B2: The AF assumes that the received value corresponds to the "current state" that is being waited for, rather than a newly detected event. For example, it might assume the UE is "IN" when it has actually just been moved "IN", which would lead to an error.

[0071] For events detected by the HSS, similar issues are identified, as described below with reference to Figure 6(b), which is the signaling diagram for "Issue B2," where the current state is unavailable regardless of ERIR support. In Figure 6(a): Steps 0 to 3: Similar to Figure 6(a).

[0072] Step 4: The "current state" of the event detected in the HSS is not available.

[0073] Steps 5 to 9: Similar to steps 7 to 11 in Figure 6(a).

[0074] Steps 10 and 11: According to Clause 5.6.2 of 3GPP TS 23.632 version 18.1.0, "User Data Interoperability, Coexistence and Migration", see the excerpt below, the HSS sends a notification to the UDM, and the UDM sends a notification to the SCEF+NEF.

[0075] Clause 5.6.2 8. The monitoring event is reported to SCEF+NEF. If applicable, the MME notifies the event as defined in 3GPP TS 23.682

[16] using the SCEF notification address provided by the HSS in step 4. If the monitoring event is detected at the HSS or reported by the MME to the HSS, the HSS notifies the UDM of the monitoring event using the Nhss_EE_Notify service operation. The UDM then notifies the NEF using the Nudm_EE_Notify service operation.

[0076] Steps 12 and 13 are similar to steps 13 and 14 in Figure 6(a).

[0077] The two different scenarios are the areas of concern in this disclosure: Subscription via an intermediate NF (without 4G / 5G interoperability) – this includes cases where the event is detected by the UDM or AMF. Note that this also includes cases where subscription is made directly to the AMF, as the issue is similar.

[0078] Subscribing to the MME via UDM+HSS (4G / 5G interoperability) – this includes cases where events are detected by the MME and cases where events are detected by the HSS.

[0079] The techniques described herein, relative to the example embodiments, include the following: When a "Report Now" is requested but "Current Status" is unavailable, the AMF / SMF or HSS adds a new indication to the EE subscription response. It should be noted that "Current Status" is unavailable in the AMF, for example, in the case of UE mobility or when there is no UE context transfer between serving nodes (e.g., UE context not supported between PLMNs by different vendors); furthermore, some events such as "PDN Connectivity Status" (MME) or "Connectivity Loss" (AMF) do not necessarily have a "Current Status".

[0080] Furthermore, for scenario b): when a "current state" exists and is available from the MME, but the HSS cannot provide this information in the EE subscription response, the HSS will send a follow-up notification that includes the "current state". This also applies when the HSS detects an event.

[0081] The disclosed technology addresses one or more of the problems mentioned above. One proposed embodiment is a mechanism to notify the requesting node (e.g., the AF) when the "current state" is unavailable, which is crucial for application logic. Furthermore, for specific use cases, it allows the "current state" to be provided to the AF when it would otherwise be lost.

[0082] One or more of the following advantages can be generated by publicly available technologies. For example, based on the received new indication(s), the AF can know that the "current state" is unavailable. This allows the AF not to wait for subsequent notifications that will never be received. Moreover, this provides its application logic (e.g., for AOI events) with valid information that no information about the event is known, so if a new AOI event is received, such as an event with "IN", it will be interpreted as the UE just entering the AOI, and the application will then run accordingly (e.g., display some advertisements).

[0083] Furthermore, for scenario b): when a "current state" exists and is available from the MME, but the HSS cannot provide this information in the EE subscription response (or when an event is detected by the HSS), this solution prevents the "current state" from being lost (never being received by the AF). It also prevents the AF from waiting (until the timer expires, which can be a long time and wasteful of resources) for a subsequent notification that will not indicate the "current state" but rather "an event was detected." Without the proposed solution(s), the lack of "current state" will interfere with application logic. For example, a user (also known as a user equipment or UE) can be "IN" for a period of time in a specific tracking area or other defined area, but the AF will miss this information.

[0084] The Change Request (CR) document in the appendix to this detailed description provides additional information on one or more solutions described herein.

[0085] A) Example solution to problem A – subscription via intermediate NF Regarding the problem described in Figure 3 above, the signaling diagram in Figure 7(a) and the description below provide a solution. Specifically, Figure 7(a) is a signaling diagram illustrating the solution to "Problem A" with a new indication of "Current Status Unavailable". In Figure 7(a): Steps 0 to 4: Similar to Figure 3.

[0086] Steps 5, 6, and 7: Similar to Figure 3, except that when the AMF recognizes that the "Current Status" is unavailable and requests an "Immediate Report" (Step 3), an indication is included in the EE subscription response to notify of the situation, namely, "Current Status is unavailable".

[0087] Step 8: Based on the received new indication, the AF knows that the "current state" is unavailable. This allows the AF to avoid waiting for subsequent notifications that it will never receive. Furthermore, this provides its application logic (e.g., for AOI events) with valid information that no information about the event is known; therefore, if a new AOI event is received, such as an event with "IN", it will be interpreted as the UE just entering the AOI, and the application will then run accordingly (e.g., display some advertisements).

[0088] Steps 9 and 10: Similar to Figure 3.

[0089] Step 11: Since a new instruction was received in step 7, AF knows that subsequent notifications are for the detected event, not for the "current state".

[0090] For cases where the event is detected by the UDM, a similar solution is given in Figure 7(b). Figure 7(b) shows the solution for "Problem A" with the indication "Current state unavailable", where the event is detected by the UDM.

[0091] Figure 7(b) has a similar description to Figure 7(a).

[0092] As shown in Figure 7(c), a similar solution applies when the subscription is received directly from the NEF, where the AMF detects the event. Figure 7(c) is a signaling diagram illustrating the solution to "Problem A" with a "Current Status Unavailable" indication, where the event is detected by the AMF (Direct Subscription).

[0093] Figure 7(c) has a similar description to Figure 7(a).

[0094] B) Subscribing to MME via UDM+HSS For the problem described in Figure 5 (Problem B1), the signaling diagram in Figure 8(a) and the description below provide a solution. Figure 8(a) is a signaling diagram illustrating the solution to Problem B1, where HSS represents the MME sending the "current status". In Figure 8(a): Steps 0 to 11: Similar to Figure 5(a).

[0095] Step 12: The HSS has received the event information (in step 6), namely the "current status". The HSS cannot send this "current status" in the EE subscription response (in step 8) because ERIR is not supported, so it should be able to send the "current status" later using a self-organizing notification for that purpose. This behavior is not described in the current 3GPP specification.

[0096] Step 13: Describe three different solution proposals: Variant 1: HSS sends the "current status" directly to NEF in the notification (using the service-based interface (SBI)).

[0097] Variant 2: HSS sends the "current status" directly to SCEF in the notification (using Diameter).

[0098] Variant 3: The HSS sends the "current status" to the UDM in the notification (using SBI), and the UDM sends the notification to the NEF (using SBI).

[0099] Steps 14 and 15: The "current status" is provided to the AF that is waiting for this information.

[0100] A solution similar to that in Figure 8(a) applies to the case where the event is detected by the HSS, as described below and shown in Figure 8(b). Specifically, Figure 8(b) is a signaling diagram illustrating another solution to problem B1, where the HSS, on behalf of the MME, sends the "current status" (where the event is detected by the HSS). In Figure 8(b): Steps 0 to 3: Similar to Figure 8(a).

[0101] Steps 4 to 12: Similar to steps 7 to 15 in Figure 8(a).

[0102] For the problem described above relative to Figure 6(a), the signaling diagram in Figure 9(a) and the description below provide a solution similar to the solution for problem A described above relative to Figure 7(a). Figure 9(a) is a signaling diagram illustrating the solution to problem B2, in which a "current state unavailable" indication is sent. In Figure 9(a): Steps 0 to 7: Similar to Figure 6(a).

[0103] Steps 8, 9, and 10: Similar to Figure 6(a), except that when the HSS recognizes that the “Current Status” is unavailable and requests an “Immediate Report” (step 3), an indication is then included in the EE subscription response to notify of the situation, namely that the “Current Status is unavailable”.

[0104] Step 11: Based on the received "Current state unavailable" indication, the Application Advisor (AF) knows that the "current state" is unavailable. This allows the AF to avoid waiting for subsequent notifications that it will never receive. Furthermore, this provides valuable information for its application logic.

[0105] Steps 12 and 13: Similar to Figure 6(a).

[0106] Step 14: Since the “Current state unavailable” indication was received in step 10, AF knows that subsequent notifications are for the detected event, not for the “current state”.

[0107] A solution similar to that in Figure 9(a) applies to cases where the event is detected by the HSS, as described below and illustrated in Figure 9(b). Specifically, Figure 9(b) is a signaling diagram illustrating another solution to problem B2, where the HSS sends "Current state unavailable" (where the event is detected by the HSS). In Figure 9(b): Steps 0 to 3: Similar to Figure 9(a).

[0108] Step 4: The "current state" of the event detected in the HSS is not available.

[0109] Steps 5 to 9: Similar to steps 7 to 11 in Figure 9(a).

[0110] Steps 10 and 11: According to Clause 5.6.2 of 3GPP TS 23.632 version 18.1.0, "User Data Interoperability, Coexistence and Migration", see the excerpt below, the HSS sends a notification to the UDM, and the UDM sends a notification to the SCEF+NEF.

[0111] Clause 5.6.2: 8. The monitoring event is reported to SCEF+NEF. If applicable, the MME notifies the event as defined in 3GPP TS 23.682

[16] using the SCEF notification address provided by the HSS in step 4. If the monitoring event is detected at the HSS or reported to the HSS by the MME, the HSS notifies the UDM of the monitoring event using the Nhss_EE_Notify service operation. The UDM then notifies the NEF using the Nudm_EE_Notify service operation.

[0112] Steps 12 and 13: Similar to steps 13 and 14 in Figure 9(a).

[0113] Figure 10 Extensive examples according to one or more embodiments are shown, wherein the telecommunications network 10 includes a responding node 12 that receives a subscription request from a requesting node 14. As can be seen, the responding node 12 may or may not be communicatively coupled to the requesting node 14; for example, there may be one or more intermediate nodes between them. Furthermore, the responding node 12 is not necessarily a node that maintains event state and detects the occurrence of events specified in the subscription request. In at least one scenario, the responding node 12 is communicatively coupled to another node that acts as a detection node 18. This coupling may be direct or may be through one or more intermediate nodes 20.

[0114] In the example scenario, the requesting node 14 is an Application Function (AF) node, and the responding node is an Access and Mobility Management Function (AMF) node, and the two nodes are communicatively coupled via a Network Exposure Function (NEF) node, which is an intermediate node 16.

[0115] Regardless of these details, response node 12 generates a subscription response as a reply to requesting node 14. Here, Figure 10 Suppose a subscription request requests immediate reporting. For example, the subscription request might include an "immediate flag" indicating that the current event status should be included in the subscription response. Furthermore, it should be understood that... Figure 10The term "generation" in the response means either the original local generation of the response or a reformulation (modification or revision) of the response originally generated by another node. In either case, generation is intelligent regarding whether the current event state is available to be included in the response. If the current event state is unavailable, the response node 12 indicates the unavailability of the current event state in the subscribed response. As described, an indication of the unavailability of the current event state can be provided for each specified event identified in the subscribed response.

[0116] like Figure 10 As shown, requesting node 14 advantageously uses the included indications to correctly interpret the first event notification received after it receives the subscription response. That is, based on the knowledge that the subscription response omits the current event state due to its unavailability, requesting node 14 correctly interprets subsequent event notifications as indications of new event detection, rather than providing the current event state of an earlier request.

[0117] In at least one embodiment, the response node is configured to perform response generation based on whether it supports real-time event reporting. In this context, "support" refers to the relevant capabilities or configurations of the response node 12 and / or any other nodes involved in generating or forwarding the subscribed response to the requesting node 14.

[0118] Consider an example scenario where a subscription request requests instant reporting, but instant reporting is not supported. Therefore, the subscription response returned to request node 14 omits the current event state. However, in at least one embodiment, response node 12 is configured to include an indication that instant reporting is not supported in the subscription response that omits the current event state due to lack of support, rather than allowing request node 14 to make (potentially incorrect) assumptions about this omission and how the next event notification should be interpreted. Furthermore, regarding receiving such a response, in one or more embodiments, request node 14 is configured to interpret a first event notification of the specified event received after the subscription response as an indication of the current event state requested in the subscription request, rather than an indication of new event detection.

[0119] Figure 11 The example embodiments illustrate in more detail the source... Figure 10 Example telecommunications network 10.

[0120] As described Figure 11 The telecommunications networks in the examples include wireless communication networks, such as cellular networks. In a particular example, telecommunications network 10 includes a cellular network configured according to specifications issued by 3GPP, such as the fifth-generation (5G) specification.

[0121] Example network 10 includes a radio access network (RAN) 30 and a core network (CN) 32, the core network 32 including a response node 12. In this example, the requesting node 14 is outside the telecommunications network 10 and can be communicatively coupled to the CN 32 via one or more external networks (NWs) 34 (e.g., the Internet or other packet data networks (PDNs)). The requesting node 14 includes, for example, an AF node, or another host computer running one or more application services that respond to event statuses and notifications provided via the response node 12. In one or more other embodiments, the requesting node 14 resides within the telecommunications network 10.

[0122] Figure 11 Multiple terminals 36 associated with the telecommunications network 10 are also depicted, for example, they are connected to the telecommunications network 10 or otherwise use communication services provided through the telecommunications network 10. In one or more embodiments, a subscription request from the requesting node 14 to the responding node 12 specifies one or more events of interest and further specifies the terminals 36 of interest. In other words, the subscription request requests notification of the occurrence of one or more specific types of events involving one or more specific terminals 36. The subscription request may request reporting to a single terminal 36 or more terminals 36, for example by instructing a group or cluster of terminals 36.

[0123] Figure 12 An example arrangement of network nodes, such as response node 12 or request node 14, is shown. This example arrangement includes processing circuitry 40 and communication circuitry 42.

[0124] Processing circuitry 40 may include fixed circuitry, programmable circuitry, or a combination of both. Communication circuitry 42 includes physical layer wired or wireless signaling circuitry for transmitting (TX) and receiving (RX) signaling, such as messages or other information. Communication circuitry 42 may also include timing circuitry and protocol processing circuitry for implementing one or more protocol stacks, such as those used in one or more embodiments.

[0125] Figure 13 An example implementation of processing circuitry 40 is shown, wherein processing circuitry 40 includes one or more microprocessors 50 (or other types of digital processors, such as microcontrollers or DSPs), which are particularly adapted to perform the corresponding operations described herein in response to node 12 or request node 14 based on the execution of computer program instructions stored in storage device / memory 52.

[0126] Figure 13Such computer program instructions are illustrated as one or more computer programs 54 stored in storage device / memory 52. ​​Storage device / memory 52 includes one or more types of computer-readable media and may include volatile storage devices, non-volatile storage devices, or a mixture of volatile and non-volatile storage devices. Example storage devices / memory 52 include any one or more of SRAM, DRAM, NVRAM, FLASH, EEPROM, solid-state drive (SSD) storage devices, or hard disk drives. It will be understood that the computer program instructions and the corresponding microprocessor adaptations are different between response node 14 and request node 14.

[0127] Figure 14 Another embodiment of a network node is shown, wherein the network node includes a processing unit or module. Here, the processing unit or module can be understood as logic circuitry implemented via basic circuitry, and the example network node includes a communication module 60 and an associated processing module 62.

[0128] Although the same general modular approach can be used in both response node 12 and request node 14, it will be understood that the configuration of processing module 62 will be different between the two nodes.

[0129] For request node 14, processing module 62 is configured to: send a subscription request, requesting event notification of a specified event in the telecommunications network and requesting an immediate report of the current event status; receive a subscription response as a reply to the subscription request, which omits the current event status; and interpret a first event notification received after the subscription response as indicating a new event detection or indicating the current event status as requested in the subscription request, depending on whether the subscription response indicates the unavailability of the current event status.

[0130] For response node 12, processing module 62 is configured to: receive a subscription request, request event notification of a specified event in the telecommunications network, and request an immediate report of the current event status; and send a subscription response as a reply to the subscription request, wherein the subscription response omits the current event status. In response to processing module 62 determining that the current event status is unavailable, the subscription response includes an indication of the unavailability of the current event status.

[0131] Figure 15 An example method 1500 of the operation performed by a network node acting as the requesting node 14 is shown.

[0132] Method 1500 includes requesting node 14: sending (box 1502) a subscription request, requesting event notification of a specified event in the telecommunications network, and requesting an immediate report of the current event status; receiving (box 1504) a subscription response as a reply to the subscription request, the subscription response omitting the current event status; and interpreting a first event notification received after the subscription response as indicating a new event detection or indicating the current event status as requested in the subscription request, depending on whether the subscription response indicates the unavailability of the current event status (box 1506).

[0133] The telecommunications network can be a cellular network operating according to 3GPP specifications. The cellular network can be a 5G cellular network as defined by 3GPP specifications.

[0134] In some embodiments, in response to a subscription response indicating the unavailability of the current event state, the first event notification can be interpreted as indicating the detection of a new event.

[0135] In some embodiments, in response to a subscription response that does not indicate the unavailability of the current event state, the first event notification may be interpreted as indicating the current event state as requested in the subscription request.

[0136] In some embodiments, in response to a subscription response that indicates that instant event reporting is not supported, does not indicate the unavailability of the current event state, and is otherwise interpreted as indicating the detection of a new event, the first event notification may be interpreted as indicating the current event state as requested in the subscription response.

[0137] In some embodiments, the specified event is a first specified event among two or more specified events indicated in the subscription request, and the request for an immediate status report applies to each of the two or more specified events. In these embodiments, in response to the current event status being included in a subscription response for one or more other events among the two or more specified events, method 1500 may include determining that the subscription response implicitly indicates the unavailability of the current event status for the first specified event.

[0138] In some embodiments, the specified event is a first specified event among two or more specified events indicated in the subscription request, and the request for an immediate status report applies to each of the two or more specified events. In these embodiments, an event-specific indication of the unavailability of the current event state in response to the subscription response for the first specified event has been included in the subscription response for the first specified event, and method 1500 may include determining that the subscription response implicitly indicates the unavailability of the current event state of the first specified event.

[0139] Step 1502 may include the network node sending a subscription request to the NEF node of the telecommunications network. The NEF node is configured to expose specified standard events occurring within the telecommunications network. Step 1504 may include the network node receiving a subscription response from the NEF.

[0140] In the above embodiments, the event may relate to the activity or movement of a UE relative to a communication service provided by a telecommunications network or a network coverage area. In these embodiments, the subscription request may specify one or more UEs as the subject of the requested event report. In these embodiments, the network node may be an application function (AF) node configured to provide application services to one or more subscribers of the application service in response to an event notification.

[0141] Figure 16 An example method 1600 of the operation performed by a network node acting as a response node 12 is shown.

[0142] Method 1600 includes: receiving (box 1602) a subscription request that requests event notification of a specified event in a telecommunications network and requests an immediate report of the current event status; and sending (box 1604) a subscription response as a reply to the subscription request. In response to a responding node determining that the current event status is unavailable, the subscription response omits the current event status and includes an indication of the unavailability of the current event status.

[0143] A telecommunications network may be a cellular network that includes one of a User Data Management (UDM) node, an Access and Mobility Management Function (AMF) node, a Session Management Function (SMF) node, or a Home Subscriber Server (HSS) node.

[0144] The specified event may relate to the activities or movement of one or more UEs regarding communication services provided by a telecommunications network or network coverage area. In these embodiments, a subscription request may designate one or more UEs as the subject of the requested event report.

[0145] The telecommunications network can be a cellular network operating according to 3GPP specifications. The cellular network can be a 5G cellular network as defined by 3GPP specifications.

[0146] In method 1600, a network node can determine that the current event state is unavailable based on local information maintained by the network node.

[0147] In some embodiments, in response to determining that instant reporting is not supported for a subscription request, the method may further include the step of including an indication that instant reporting is not supported. In these embodiments, determining that instant reporting is not supported for a subscription request may be based on the capabilities of a network node. In some alternatives, determining that instant reporting is not supported for a subscription request may be based on the capabilities of another network node operating as an intermediary node between the network node and the requesting node that initiated the subscription request. In other alternatives, determining that instant reporting is not supported for a subscription request may be based on the capabilities of another network node operating as a detection node relative to a specified event.

[0148] The specified event may be a first specified event among two or more specified events indicated in the subscription request, and the request for an immediate status report applies to each of the two or more specified events. In some embodiments, including an indication of the unavailability of the current event status in the subscription response includes: implicitly indicating the unavailability of the current event status by omitting the current event status of the first specified event in combination with the current event status of any other specified event among two or more specified events whose current event status is available. In an alternative embodiment, method 1600 includes indicating the unavailability of the current event status of each specified event in the subscription response.

[0149] It is worth noting that those skilled in the art, benefiting from the teachings given in the foregoing description and the associated drawings, will conceive of modifications and other embodiments of the disclosed invention(s). Therefore, it is to be understood that the invention(s) is not limited to the specific embodiments disclosed, and modifications and other embodiments are intended to be included within the scope of this disclosure. Although specific terminology may be used herein, it is used only in a general and descriptive sense and not for limiting purposes.

[0150] Example Implementation 1. A method performed by a network node, the method comprising: Send a subscription request to request event notifications for specified events in the telecommunications network and to request an immediate report on the current event status; Receive a subscription response as a reply to the subscription request, wherein the subscription response omits the current event state; and Depending on whether the subscription response indicates the unavailability of the current event state, the first event notification received after the subscription response will be interpreted as indicating a new event detection or indicating the current event state as requested in the subscription request.

[0151] 2. The method according to embodiment 1, wherein, in response to the subscription response indicating the unavailability of the current event state, the first event notification is interpreted as indicating a new event detection.

[0152] 3. The method according to Embodiment 1, wherein, in response to the subscription response not indicating the unavailability of the current event state, the first event notification is interpreted as indicating the current event state as requested in the subscription request.

[0153] 4. The method according to Embodiment 1, wherein, in response to the subscription response having indicated a lack of support for instant event reporting and not indicating the unavailability of the current event state, the first event notification is interpreted as indicating the current event state as requested in the subscription response, and otherwise is interpreted as indicating a new event detection.

[0154] 5. The method according to Embodiment 1, wherein the designated event is a first designated event among two or more designated events indicated in the subscription request, wherein the request for an immediate status report is applied to each of the two or more designated events, and wherein the method includes determining, in response to a subscription response in which the current event status has been included in one or more other designated events among the two or more designated events, the unavailability of the current event status of the first designated event.

[0155] 6. The method according to Embodiment 1, wherein the designated event is a first designated event among two or more designated events indicated in the subscription request, wherein the request for an immediate status report is applied to each of the two or more designated events, and wherein the method includes determining, in response to an event-specific indication of the unavailability of the current event state being included in the subscription response of the first designated event, that the subscription response implicitly indicates the unavailability of the current event state of the first designated event.

[0156] 7. The method according to any one of Embodiments 1-6, wherein sending the subscription request includes the network node sending the subscription request to a Network Exposure Function (NEF) node of the telecommunications network, the NEF node being configured to expose to events of a specified standard occurring within the telecommunications network, and wherein receiving the subscription response includes the network node receiving the subscription response from the NEF.

[0157] 8. The method according to embodiment 7, wherein the event relates to the activity or movement of a user equipment (UE) relative to a communication service or network coverage area provided by the telecommunications network.

[0158] 9. The method according to embodiment 7 or 8, wherein the subscription request designates one or more UEs as the subject of the requested event report.

[0159] 10. The method according to any one of embodiments 7-9, wherein the network node is an application function (AF) node, the application function node being configured to provide the application service to one or more subscribers of the application service in response to the event notification.

[0160] 11. The method according to any one of Examples 1-10, wherein the telecommunications network is a cellular network operating in accordance with the 3rd Generation Partnership Project (3GPP) specifications.

[0161] 12. The method according to embodiment 11, wherein the cellular network is a fifth-generation (5G) cellular network as defined by the 3GPP specification.

[0162] 13. A network node, comprising: communications circuits; and The processing circuit is configured to perform the method as described in any one of Examples 1-12.

[0163] 14. A method operated by a network node of a telecommunications network, the method comprising: Receive subscription requests, requests for event notifications for specified events in the telecommunications network, and requests immediate reporting of the current event status; and Send a subscription response as a reply to the subscription request, wherein the current event state is omitted in the subscription response; The method further includes, in response to determining that the current event state is unavailable, including an indication of the unavailability of the current event state in the subscription response.

[0164] 15. The method according to embodiment 14 further includes determining that the current event state is unavailable based on local information maintained by the network node.

[0165] 16. The method according to embodiment 14, wherein the method further includes, in response to determining that instant reporting is not supported for the subscription request, an indication of non-support for instant reporting.

[0166] 17. The method according to embodiment 16 further includes determining, based on the capabilities of the network node, that instant reporting is not supported for the subscription request.

[0167] 18. The method according to embodiment 16 further includes determining, based on the capability of another network node operating as an intermediary node between the network node and the requesting node that initiated the subscription request, that immediate reporting is not supported for the subscription request.

[0168] 19. The method according to embodiment 16 further includes determining, based on the capability of another network node operating as a detection node relative to the specified event, that instant reporting is not supported for the subscription request.

[0169] 20. The method according to embodiment 14, wherein the designated event is a first designated event among two or more designated events indicated in the subscription request, wherein the request for an immediate status report is applied to each of the two or more designated events, and wherein... The indication of unavailability of the current event state in the subscription response includes: implicitly indicating the unavailability of the current event state by omitting the current event state of the first specified event and combining it with the current event state of any other specified event among the two or more specified events for which the current event state is available.

[0170] 21. The method according to embodiment 14, wherein the designated event is a first designated event among two or more designated events indicated in the subscription request, wherein the request for an immediate status report is applied to each of the two or more designated events, and wherein the method includes indicating in the subscription response the unavailability of the current event status of each designated event.

[0171] 22. The method according to any one of embodiments 14-21, wherein the telecommunications network is a cellular network, and wherein the network node includes one of a User Data Management (UDM) node, an Authorization and Mobility Management Function (AMF) node, a Session Management Function (SMF) node, a Policy Control Function (PCF) node, or a Home Subscriber Server (HSS) node.

[0172] 23. The method according to any one of embodiments 14-22, wherein the designated event relates to the activity or movement of one or more user equipments (UEs) relative to a communication service or network coverage area provided by the telecommunications network.

[0173] 24. The method according to embodiment 23, wherein the subscription request designates the one or more UEs as the subject of the requested event report.

[0174] 25. The method according to any one of Examples 14-24, wherein the telecommunications network is a cellular network operating in accordance with the 3rd Generation Partnership Project (3GPP) specifications.

[0175] 26. The method according to embodiment 25, wherein the cellular network is a fifth-generation (5G) cellular network as defined in the 3GPP specification.

[0176] 27. A network node, comprising: Communication circuits; and The processing circuit is configured to perform the method as described in any one of Examples 14-26.

[0177] appendix 3GPP TSG-CT WG4 Meeting #117 C4-233abc Gothenburg, Sweden, August 21-25, 2023 5.5.2.4.2 Event Notification Figure 5.5.2.4.2-1 illustrates a scenario where the UDM notifies the NF service consumer (which has subscribed to receive such notifications) about the occurrence of an event (see also 3GPP TS 23.502 [3] Figure 4.15.3.2.2-1 step 4a), or, if the event report cannot be included in the subscription response, notifies the current status of the subscription event that is being reported immediately (i.e., the IERSR / ERIR feature is not end-to-end supported by NEF / UDM / AMF / HSS). The request includes the reference ID as previously received in EESubscription (see Clause 6.4.6.2.2).

[0178] [ Figure 17 Figure 5.5.2.4.2-1 of 3GPP TS 29.503 v18.2.0 is shown. 1. UDM sends a POST request to the callbackReference URI provided by the NF service consumer during the subscription period. This request should include the reference ID of the associated monitoring configuration in each report.

[0179] 2. NF service consumers respond with "204 No Content".

[0180] On failure, the appropriate HTTP status code indicating the error should be returned, and appropriate additional error information should be returned in the body of the POST response.

[0181] 6.4.6.2.9 Type: CreatedEeSubscription Table 6.4.6.2.9-1: Definition of the CreatedEeSubscription type A.5 Nudm_EE API OpenAPI: 3.0.0 ************************Text skipped for clarity********************** ************************Text skipped for clarity********************** 3GPP TSG-CT WG4 Meeting #117 C4-233abc Gothenburg, Sweden, August 21-25, 2023 5.6.2 Configuring Monitoring Events in MME Figure 5.6.2-1 illustrates a scenario where the UDM receives a request from the combined SCEF+NEF to configure monitoring events (such as location changes) that need to be reported by the EPC.

[0182] [ Figure 18 Figure 5.6.2-1 shows the configuration of monitoring events in the MME in 3GPP TS 23.632 v18.3.0. 1. The UDM receives a request from the combined SCEF+NEF to configure monitoring events for the UE. This request indicates that the subscription also applies to the EPC, and that monitoring events will be reported by the MME (e.g., location changes). The request includes the notification addresses of both the NEF and SCEF.

[0183] 2. The UDM configures monitoring events for the UE in the 5GC. If the 5GS UDR is used, the UDM stores the configuration for monitoring events for the UE in the 5GS-UDR. The UDM contacts the corresponding NF (e.g., AMF, SMF) within the 5GC as required by the monitoring events.

[0184] 3. Unless the subscription information associated with the UE indicates that the UE has no EPC subscription data, the UDM requests the HSS to configure monitoring events for the UE in the EPC using the Nhss_EventExposure_Subscribe operation. In addition to the UDM notification address, the UDM also provides the SCEF notification address (i.e., the SCEF ID).

[0185] 4. HSS uses the procedure defined in 3GPP TS 23.682

[16] to configure monitoring events for UE in EPC.

[0186] 5. HSS replies to UDM with the result of the subscription request.

[0187] If immediate reporting is required, and the current event status is available at the HSS (or received from the MME in step 4), and if both the UDM and the HSS support including event reporting in the subscription response, then the HSS also includes the current event status in the subscription response to the UDM, and skips step 6a.

[0188] If immediate reporting is required, but the current event status is not available at the HSS (and not received from the MME in step 4), the HSS includes a flag in its subscription response indicating that immediate event reporting is unavailable.

[0189] 6. The UDM response combination SCEF+NEF, including subscription confirmation, is also successful in the EPC domain.

[0190] 6a. (Conditionally) If immediate reporting is required, and the current event status is available at the HSS (or received from the MME in step 4), but the UDM and / or HSS cannot support including event reporting in the subscription response, the HSS sends a notification to the UDM using the Nhss_EE_Notify service operation, including the current event status for immediate reporting. The UDM then notifies the NEF using the Nudm_EE_Notify service operation.

[0191] 7. In a later stage, a monitoring event is detected for the UE in the EPC domain. This event can be detected at the MME (e.g., location change) or at the HSS (e.g., UE reachability for SMS).

[0192] 8. The monitoring event is reported to SCEF+NEF. If applicable, the MME notifies the event as defined in 3GPP TS 23.682

[16] using the SCEF notification address provided by the HSS in step 4. If the monitoring event is detected at the HSS or reported to the HSS by the MME, the HSS notifies the UDM of the monitoring event using the Nhss_EE_Notify service operation. The UDM then notifies the NEF using the Nudm_EE_Notify service operation.

[0193] Note: Notifications of monitoring events from the HSS using the SBA interface (e.g., for SMS reachability) supersede the option for the HSS to use diameter S6t. Only events reported by the MME will keep the diameter T6a interface facing the SCEF.

[0194] 6.1.5.1 Nhss_EE_Subscribe Service Operations Service operation name: Nhss_EE_Subscribe.

[0195] Description: NF consumers request HSS subscriptions for notifications used to monitor events, as described in 3GPP TS 23.682

[16] (e.g., location changes).

[0196] Required inputs: IMSI, (one or more) monitoring event types, notification address.

[0197] Optional input: - Required output: result indication, subscription ID.

[0198] Optional output: Indicator that the current status is unavailable.

[0199] 3GPP TSG-CT WG4 Meeting #117 C4-233abc Gothenburg, Sweden, August 21-25, 2023 5.5.2.2.2 Subscribing to Event Notifications Figure 5.5.2.2.2-1 illustrates a scenario where an NF service consumer sends a request to the HSS to subscribe to event occurrence notifications. This request includes the callback URI, the type of event being monitored, and additional information such as the SCEF ID, event filters, and reporting options.

[0200] [ Figure 19 Figure 5.5.2.2-1: NF Service Consumer Subscription Notification is shown in 3GPP TS 29.563 v18.2.0. 1. The NF service consumer sends a POST request (... / {ueId} / ee-subscriptions) to the parent resource (subscription set) to create a subscription as presented in the message body. This request may include an expiration time suggested by the NF service consumer, indicating the desired duration for the subscription to remain active, and the time when events for (one or more) the subscription will cease generating notifications. Additionally, if public network exposure is used (i.e., if the combined SCEF+NEF request subscribes to / monitors (one or more) events in the EPC), the request may include the SCEF ID. If the HSS receives MTC provider information in the request, it will check whether the MTC provider is allowed to perform the operation for the UE; otherwise, the HSS will skip the MTC provider authorization check.

[0201] 2a. On success, the HSS responds with a "201 Created" message, with the message body containing an indication that the subscription has been created. The Location HTTP header should include the URI of the created subscription.

[0202] If immediate reporting is requested, and both the HSS and the NF consumer indicate support for the ERIR feature (see Clause 6.4.8), the HSS shall include available immediate event reports, i.e., reports already received from the MME, in the response body; otherwise, if the HSS and / or the NF consumer does not support the ERIR feature, the HSS shall send a notification to the NF consumer (see Clause 5.5.2.4.2) including the current status of the event for which immediate reporting is requested. If immediate reporting is requested, but the current status of one or more events is unavailable at the time of subscription, the HSS shall include an indication of the unavailability of the current status in the response.

[0203] If some requested monitoring configurations fail, the response may include failedMonitoringConfigs to indicate the reason for the failure of the monitoring configurations.

[0204] 2b. If the user does not exist, the HTTP status code "404 Not Found" should be returned, and additional error information should be included in the response body (in the "ProblemDetails" element).

[0205] 2c. If there is no valid subscription data for the UE, i.e., based on the UE's subscription information, monitoring of the requested event type is not allowed, or the requested event type is not supported, or the MTC provider is not allowed to perform the operation for the UE, then the HTTP status code "403 Forbidden" should be returned, including additional error information in the response body (in the "ProblemDetails" element).

[0206] 2d. In the case of redirection, the HSS should return a 3xx status code that includes a location header with a URI pointing to an endpoint of another HSS (service) instance.

[0207] 2e. If the requested monitoring event type or reporting option is not supported, the HTTP status code "501 Not Implemented" should be returned, and additional error information should be included in the response body (in the "ProblemDetails" element).

[0208] On failure, the appropriate HTTP status code indicating the error should be returned, and appropriate additional error information should be returned in the body of the POST response.

[0209] 5.5.2.4.2 Event Notification Figure 5.5.2.4.2-1 illustrates a scenario where, if the ERIR feature is not supported by the HSS and / or NF service consumer (see Clause 6.4.8), the HSS notifies the NF service consumer (who has subscribed to receive such notifications) of the occurrence of an event or the current status of an event for which immediate reporting is requested. This request includes the reference ID previously received in EeSubscription.

[0210] [ Figure 20 Figure 5.5.2.4.2-1 of 3GPP TS 29.563 v18.2.0 is shown. 1. HSS sends a POST request to the callbackReferenceURI provided by the NF service consumer during the subscription period.

[0211] 2a. NF service consumers respond with "204 No Content".

[0212] On failure, the appropriate HTTP status code indicating the error should be returned, and appropriate additional error information should be returned in the body of the POST response.

[0213] In the event of a redirect, the NF service consumer should return a 3xx status code, which should include a location header with a URI pointing to an alternative notification endpoint.

[0214] 6.4.6.2.3 Type: CreatedEeSubscription Table 6.4.6.2.3-1: Definition of the CreatedEeSubscription type A.5 Nhss_EE API OpenAPI: 3.0.0 ************************Text skipped for clarity********************** ************************Text skipped for clarity**********************

Claims

1. A method (1500) operated by a network node, the method comprising: Send (1502) subscription request, requesting event notification for a specified event in the telecommunications network, and requesting an immediate report of the current event status; Receive (1504) a subscription response as a reply to the subscription request, wherein the subscription response omits the current event state; as well as Depending on whether the subscription response indicates the unavailability of the current event state, the first event notification received after the subscription response will be interpreted (1506) as indicating a new event detection or indicating the current event state as requested in the subscription request.

2. The method (1500) according to claim 1, wherein, In response to the subscription response indicating the unavailability of the current event state, the first event notification is interpreted as indicating a new event detection.

3. The method (1500) according to claim 1, wherein, In response to the subscription response not indicating the unavailability of the current event state, the first event notification is interpreted as indicating the current event state as requested in the subscription request.

4. The method (1500) according to claim 1, wherein, In response to the subscription response indicating a lack of support for instant event reporting and not indicating the unavailability of the current event state, the first event notification is interpreted as indicating the current event state as requested in the subscription response, and otherwise is interpreted as indicating a new event detection.

5. The method (1500) according to claim 1, wherein, The specified event is a first specified event among two or more specified events indicated in the subscription request, wherein the request for an immediate status report is applied to each of the two or more specified events, and wherein the method includes determining, in response to a subscription response in which the current event status has been included in one or more other specified events among the two or more specified events, the unavailability of the current event status of the first specified event.

6. The method (1500) according to claim 1, wherein, The specified event is a first specified event among two or more specified events indicated in the subscription request, wherein the request for an immediate status report is applied to each of the two or more specified events, and wherein the method includes determining that the subscription response implicitly indicates the unavailability of the current event state of the first specified event in response to an event-specific indication of the unavailability of the current event state of the first specified event being included in the subscription response of the first specified event.

7. The method (1500) according to any one of claims 1-6, wherein, Sending the subscription request includes the network node sending the subscription request to a Network Exposure Function (NEF) node of the telecommunications network, the NEF node being configured to expose events of a specified standard occurring within the telecommunications network, and receiving the subscription response includes the network node receiving the subscription response from the NEF.

8. The method (1500) according to claim 7, wherein, The event refers to the activity or movement of a user equipment (UE) relative to a communication service or network coverage area provided by the telecommunications network.

9. The method according to claim 7 or 8, wherein, The subscription request designates one or more UEs as the subject of the requested event report.

10. The method (1500) according to any one of claims 7-9, wherein, The network node is an application function (AF) node, which is configured to provide the application service to one or more subscribers of the application service in response to the event notification.

11. The method (1500) according to any one of claims 1-10, wherein, The telecommunications network is a cellular network operating in accordance with the 3GPP (3rd Generation Partnership Project) specifications.

12. The method (1500) according to claim 11, wherein, The cellular network is a fifth-generation 5G cellular network as defined by the 3GPP specifications.

13. A network node, comprising: Communication circuit (42); and The processing circuit (40) is configured to perform the method as described in any one of claims 1-12.

14. A method (1600) operated by a network node of a telecommunications network, the method comprising: Receive (1602) subscription request, requesting event notification for a specified event in the telecommunications network, and requesting an immediate report of the current event status; as well as Send (1604) as a subscription response to the subscription request, the subscription response omitting the current event state; The method further includes, in response to determining that the current event state is unavailable, including an indication of the unavailability of the current event state in the subscription response.

15. The method (1600) of claim 14, further comprising determining that the current event state is unavailable based on local information maintained by the network node.

16. The method (1600) according to claim 14, wherein, The method further includes, in response to determining that instant reporting is not supported for the subscription request, an indication of non-support for instant reporting.

17. The method (1600) of claim 16, further comprising determining, based on the capabilities of the network node, that instant reporting is not supported for the subscription request.

18. The method (1600) of claim 16, further comprising determining, based on the capability of another network node operating as an intermediary node between the network node and the requesting node that initiated the subscription request, that immediate reporting is not supported for the subscription request.

19. The method (1600) of claim 16, further comprising determining, based on the capability of another network node operating as a detection node relative to the specified event, that instant reporting is not supported for the subscription request.

20. The method (1600) according to claim 14, wherein, The specified event is the first of two or more specified events indicated in the subscription request, wherein the request for an immediate status report applies to each of the two or more specified events, and wherein... The indication of unavailability of the current event state in the subscription response includes: implicitly indicating the unavailability of the current event state by omitting the current event state of the first specified event and combining it with the current event state of any other specified event among the two or more specified events for which the current event state is available.

21. The method (1600) according to claim 14, wherein, The specified event is the first of two or more specified events indicated in the subscription request, wherein the request for an immediate status report is applied to each of the two or more specified events, and wherein the method includes indicating in the subscription response the unavailability of the current event status of each specified event.

22. The method (1600) according to any one of claims 14-21, wherein, The telecommunications network is a cellular network, and the network nodes include one of the following: a User Data Management (UDM) node, an Access and Mobility Management (AMF) node, a Session Management (SMF) node, or a Home Subscriber Server (HSS) node.

23. The method according to any one of claims 14-22, wherein, The specified event refers to the activity or movement of one or more user equipment (UE) relative to the communication services or network coverage area provided by the telecommunications network.

24. The method according to claim 23, wherein, The subscription request designates one or more UEs as the subject of the requested event report.

25. The method according to any one of claims 14-24, wherein, The telecommunications network is a cellular network operating in accordance with the 3GPP (3rd Generation Partnership Project) specifications.

26. The method of claim 25, wherein, The cellular network is a fifth-generation 5G cellular network as defined in the 3GPP specifications.

27. A network node, comprising: Communication circuits; as well as The processing circuit is configured to perform the method as described in any one of claims 14-26.

28. A network node comprising a processor and a memory, the memory containing instructions executable by the processor, thereby operating the network node to perform the method as claimed in any one of claims 1-12 and 14-26.

Images