Common Event Exposer in a Network Domain

Abstract

To provide a method performed by an exposure node having first identification information in a first network domain in a communication network.SOLUTION: A method includes initiating a request for a subscription to an event of a communication device toward a first network node. The request includes subscription information for a common network exposure in at least two network domains. The method also includes receiving a response from the first network node. The response includes at least one of first confirmation in which the event is to be reported to an exposure node for a second network domain for the common network exposure, and second conformation in which the event is to be reported to an exposure node for a first network domain.SELECTED DRAWING: Figure 7

Description

Technical Field

[0001] The present disclosure generally relates to wireless communication systems, and more particularly, to the exposure (publication) of common events in at least two network domains (e.g., 4G and 5G).

Background Art

[0002] Cellular Internet of Things (CIoT) is a technology that enables machine type communication devices (MTC devices) to participate so that communication operators can provide other parties / enterprises' networks for various applications.

[0003] Examples of such applications are the use of smart metering readers where MTC devices are placed in various locations and can periodically start sending and receiving data (e.g., power consumption reports, water levels, etc.). Another example is where a taxi company can place an MTC device in each vehicle to track consumers / customers and send local advertisements whenever they pass through a specific location.

Summary of the Invention

[0004] According to various embodiments of the concepts of the present disclosure, a method is provided that is executed by an exposer node having first identification information in a first network domain in a communication network. The method includes initiating a request to a first network node for subscribing to events of a communication device. The request includes subscription information for reporting on the event, and the subscription information includes an indication of a common network exposer in at least two network domains. The at least two network domains include the first network domain to which the first network node belongs and at least one other network domain. The subscription information further includes second identification information of the exposer node for reporting on events in at least one other second network domain. The method further includes receiving a response from the first network node in response to the request. The response includes at least one of a first confirmation indicating that the event is reported to an exposer node for a second network domain for the common network exposer and a second confirmation indicating that the event will be reported to an exposer node for the first network domain. The second confirmation omits the indication of the common network exposer.

[0005] In some embodiments, further operations executed by the exposer node include, after receiving the first confirmation, receiving event notifications from each of a second network node and a third network node for each of the at least two network domains.

[0006] In some embodiments, further operations performed by the exposure node include starting a subscription to a fourth network node for reporting an event by a second network node for a second network domain after receiving only the second configuration.

[0007] Corresponding embodiments of the concepts of the present disclosure for the exposure node, computer product, and computer program are also provided.

[0008] According to other embodiments of the concepts of the present disclosure, a method performed by a first network node in a communication network is provided. The method includes receiving a request from an exposure node for subscribing to an event of a communication device. The request includes an indication of a common network exposer in at least a second network domain for reporting about the event and identification information of the exposure node for reporting about an event related to the second network domain. The method further includes checking a fourth network node in the communication network that provides a common event exposure service.

[0009] In some embodiments, further operations performed by the first network node include storing subscription information.

[0010] In some embodiments, further operations performed by the first network node include identifying a fourth network node in the communication network that provides a common event exposure service. The method is for the fourth network node via a common event exposure service generated by the second network node. SubFurther including starting at least one request for scripting and for a fourth network node for monitoring events of a communication device. The method further includes receiving, from the fourth network node, a response including an indication that the combined network node has successfully accepted the subscription and is monitoring the event, in response to the at least one request.

[0011] In some embodiments, further operations performed by the first network node include starting a response to the exposer node in response to the request. The response includes at least one of a first indication indicating that an event is being monitored in one of at least two network domains and a second indication indicating that the event is accepted in a second network domain.

[0012] Corresponding embodiments, computer products, and computer programs of the concepts of the present disclosure for the first network node are also provided.

[0013] When a home subscriber server (HSS) and an integrated data management (UDM: Unified Data Management) node in a communication network are not co-located, events can be detected and reported without depending on where the communication device is camped (e.g., 4G / Evolved Packet System (EPS) or 5GC). One approach for a serving node of a communication device to report an event to an exposer node for two network domains (e.g., 4G and 5G) can be to send an event subscription to both the HSS and the UDM.

[0014] Such an approach is not efficient from a network perspective and can slow down the evolution and modernization of the operator's network.

[0015] Various embodiments of the present disclosure can provide solutions to these and other potential problems. In various embodiments of the present disclosure, an exposure node and another network node operate to provide a method for a common network exposure in a deployment where the HSS and UDM will not be combined. As a result, duplicate subscriptions from the exposure node are avoided, and the network can develop more efficiently.

Brief Description of the Drawings

[0016] Included to provide a further understanding of the present disclosure, the accompanying drawings, which are incorporated in and constitute a part of this application, illustrate specific and non-limiting embodiments of the inventive concept. In the drawings:

[0017]

Figure 1

[0018]

Figure 2a

Figure 2b

Figure 2c

Figure 2d

[0019]

Figure 3

[0020]

Figure 4

[0021]

Figure 5

[0022]

Figure 6

[0023]

Figure 7

[0024]

Figure 8

[0025]

Figure 9

DETAILED DESCRIPTION OF THE INVENTION

[0026] Hereinafter, the concept of the present disclosure will be more fully described with reference to the accompanying drawings showing examples of embodiments of the concept of the present disclosure. However, the concept of the present disclosure can be embodied in many different forms and should not be construed as limited to the embodiments described herein. Rather, these embodiments are provided so that the present disclosure will be thorough and complete, and will fully convey the scope of the concept of the present disclosure to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components of one embodiment may be implicitly assumed to exist / used in another embodiment.

[0027] The following description presents various embodiments of the disclosed subject matter. These embodiments are presented as illustrative examples and should not be construed as limiting the scope of the disclosed subject matter. For example, specific details of the described embodiments may be modified, omitted, or extended without departing from the scope of the described subject matter.

[0028] The term "exposure function (EF)" (also referred to as an exposure node in this specification) is used in a non-limiting manner and, as described below, can refer to any functional entity (network function / node) that can receive the configuration (configuration information) of various monitoring events (e.g., when an MTC device becomes reachable) initiated by an application function (AF) (also referred to as an application node in this specification). The term "exposure function" in this specification is compatible with and can be replaced by "EF", "exposure node", "EF node", "service capability exposure function (SCEF)", "network exposure function (NEF)", and / or SCEF+NEF combined node. Monitoring can be performed via the diameter protocol (e.g., 3GPP TS 29.336, Release 16.1.0, http: / / www.3gpp.org / ftp / / Specs / archive / 29_series / 29.336 / As described in 29336-g10.zip (March 3, 2020), via the s6t interface) to the mobility management entity (MME) (also referred to as the MME node in this specification) in the 4G core, via the HSS, or, for example, 3GPP TS 29.503, Release 16.2.0, http: - www.3gpp.org / / www.3gpp.org / ftp / / Specs / archive / 29_series / 29.503 / As described in 29503-g20.zip (March 3, 2020), it can be sent by the EF node via the UDM (Unified Data Management) (also referred to as the UDM node in this specification) towards the Access Management Function (AMF) (also referred to as the AMF node in this specification) in the 5G core.

[0029] As mentioned in this specification, the exposure node refers to the SCEF and / or NEF in relation to the access type (e.g., 4G or 5G). Depending on the vendor, the SCEF and NEF can be combined shi into a single node or made into separate nodes. Further, the HSS and UDM can be combined shi into a single node or separate nodes. In other words, each of the SCEF and NEF, as well as each of the HSS and UDM, can be co-located or deployed within a separate functional entity node. Also, refer to 3GPP TS 23.501, Release 16.3.0, http: / / www.3gpp.org / ftp / / Specs / archive / 23_series / 23.501 / See also 5.17.5 section of 23501-g30.zip (March 3, 2020).

[0030] The following description of potential problems shows the current implementation as part of this disclosure and should not be construed as being previously known to others. In some approaches, even when the SCEF and NEF are combined shita into an EF, if the HSS and UDM are not co-located, certain events reported by the serving node (e.g., MME / AMF / SMF) are combined shitaIf it needs to be reported to the EF, regardless of where the UE / MTC device is camped (e.g., on 4G / EPS or 5GC), to ensure that the event is detected and reported, the event subscription is sent to both the HSS and the UDM. This is because two parallel subscriptions need to be maintained at the combined shi SCEF and NEF (also referred to as SCEF+NEF in this specification), which may not be efficient from the network perspective, one is sent to the HSS via Diameter and the other is sent to the UDM via HTTP.

[0031] In addition, such an approach may slow down the development and modernization of the operator's network because the Diameter protocol is still used for these scenarios for these deployments and it may not be beneficial for the operator to maintain such legacy protocols and procedures. Instead, the operator may wish to evolve to cloud-native network functions (HTTP-based) to enable future expansion and enhancement of the procedures.

[0032] Various embodiments of the present disclosure can provide solutions to these and other potential problems. In various embodiments of the present disclosure, by including an indication from the EF in the subscription request, the indication can show that the event subscription is for not only the domain to which the targeted network function belongs (e.g., 5GC in the case of the UDM), but also for a second domain (e.g., the EPS domain). To receive potential notifications from the second domain (e.g., from the MME within the EPS domain), the EF formed by combining SCEF+NEF can further include its SCEF Diameter identification information. As a result, the second domain (e.g., the EPS domain) can handle the event and report the event for the indicated Diameter identification information.

[0033] In some embodiments of the present disclosure, the service is provided by an HSS that is an NF service producer. This service (e.g., common network exposure) enables interworking with the UDM for the network exposure, such that the UDM (which is an NF service consumer) can use the service (i.e., subscribe to the HSS instead of the EF) and provide a single subscription procedure to the combined SCEF+NEF.

[0034] In some embodiments of the present disclosure, an indication is included in the subscription response from the UDM to cause the combined EF to recognize events monitored in both domains (e.g., EPS and 5GC). As a result, the EF skips subscribing to the HSS.

[0035] FIG. 1 is a block diagram of a communication network according to various embodiments of the present disclosure.

[0036] The subject matter described herein may be implemented in any suitable type of system using any suitable components, but the embodiments disclosed herein are described with respect to a combined SCEF+NEF node for two network domains (4G / EPS and 5G), such as the exemplary communication network shown in FIG. 1. For simplicity, the communication network of FIG. 1 depicts only the combined SCEF+NEF node. In reality, SCEF and NEF may each be separate nodes. Further, for simplicity, the communication network of FIG. 1 shows only the HSS 107 and the integrated data management node (UDM113) as separate nodes. In reality, HSS107 and UDM113 are combined shiIt can be a node. Further, although various embodiments are described with reference to 4G / EPS and 5G as two network domains, the present disclosure is not limited thereto and includes any two or more network domains involved in the monitoring and notification of common event exposure (common event disclosure). Further, the communication network of FIG. 1 includes an MME 103, an integrated data repository - EPS (UDR - EPS) node 105, an access management function (AMF) node 109, a UDR - 5G node 111, and a service capability server (SCS) / application server (AS) / application function (AF) 117. However, the identification information of these nodes is used without limiting the method and refers to any type of network node that performs the operations described in detail below.

[0037] FIG. 1 shows an example of a communication network represented as 4G / EPS and a 5G network architecture composed of core network functions. The cooperative operation between network functions is represented by point - to - point reference points / interfaces.

[0038] Viewed from the access side, the network architecture of FIG. 1 includes a user equipment (UE) 101 connected to two radio access networks (RANs) (5G RAN 119 and 4G / EPC RAN 121) by radio interfaces. Usually, the RAN includes base stations such as evolved Node B (eNB) or 5G base station (gNB) or similar nodes. The 5G core network functions shown in FIG. 1, viewed from the 5G core network, include an AMF 109, a UDR - 5G 111, a UDM 113, and an SCEF + NEF combined node 115. Viewed from the 4G / EPC core network, the 4G / EPC network functions shown in FIG. 1 are an MME 103, a UDR - EPS 105, and an HSS - FE 107. The SCS / AS / AF 117 is also shown in FIG. 1 and is communicatively connected to both the 5G core network and the 4G core network.

[0039] Figures 2a to 2d are exemplary signaling sequences for common event exposure according to some embodiments of the present disclosure. The embodiments of Figures 2a to 2d are presented as illustrative examples and should not be construed as limiting the scope of the disclosed subject matter. For example, specific details of the described embodiments may be modified, omitted, or extended without departing from the scope of the described subject matter.

[0040] Here, the signaling flow of Figures 2a to 2d will be generally described.

[0041] In operations 201 to 203, the SCS / AS / AF 117 subscribes (subscribes) to events (e.g., location change) to be monitored and reported.

[0042] In operations 205 to 209, the SCEF+NEF combined node 115 issues (initiates) a subscription to the UDM 113 including two information elements according to various embodiments of the inventive concept: - The first information element includes an indication of the common network exposer 。 That is, the EF is the combined SCEF+NEF (e.g., the SCEF+NEF combined node 115), and as a result, if possible, the second network domain (e.g., the EPS domain) should also report the event without the need for an individual subscription to the HSS (e.g., the HSS-FE 107) when the event is detected. - The second information element includes the identification information of the combined SCEF+NEF (e.g., the combined SCEF diameter identification information (SCEF Id)) for reporting events in the second network domain. This is because assuming that the SCEF Id is the destination address for reporting in the second network domain (e.g., the EPS domain via the T6a diameter interface), this may be required by the MME (e.g., the MME 103) when reporting the event.

[0043] Note that the SCEF Id is a Diameter Uniform Resource Identifier (URI), and the NEF address is an HTTP URI. If necessary, both URIs may be the same when identifying the domain part (e.g., combined-scef-nef-1.ericsson.com).

[0044] In operations 211 to 215, in addition to configuring the events within AMF 109 to be detectable within 5GC, UDM 113 checks (either via local configuration (configuration) or via NRF discovery) whether there is an HSS instance that provides a common exposure service.

[0045] In operations 215 to 225, if there is an HSS that provides a common exposure service, UDM 113 subscribes to the HSS via the common exposure service. The subscription includes the type of event, the UDM notification address if the event is terminated at the HSS, the SCEF-id, etc.

[0046] In operations 227 - 231a, 231b, if the procedure to the HSS is successful, UDM 113 notifies the EPS domain that it should also monitor (and report) the event by putting an indication in the response to the EF and sending it. Therefore, no parallel subscription to the HSS is made.

[0047] In operations 233 to 239, event changes (e.g., location change) are reported to the correct address within the combined node (e.g., MME 103 reports to the SCEF within SCEF + NEF combined node 115, and AMF 109 reports to the NEF within SCEF + NEF combined node 115).

[0048] In operations 241 to 251, when UDM 113 fails when configuring an event within the EPS domain (e.g., when common exposure is not supported and / or when there is no combined HSS / UDM), UDM 113 does not include an indication of common exposure in the response to the EF. As a result, the EF performs a parallel subscription to the HSS so that the event is monitored in 4G.

[0049] Here, the operations of FIGS. 2a to 2d will be described in more detail.

[0050] Referring to FIG. 2a, at 201, an application of network node 117 (e.g., a service capability server (SCS), an application server (AS), and / or an application function node (AF), collectively referred to herein as SCS / AS / AF 117) starts a subscription to an event for a given UE (e.g., UE 101), such that the event will be reported when the event occurs (e.g., a location change). At 203, SCS / AS / AF 117 initiates a subscription request (e.g., MonitoringEventSubscribe) to the SCEF+NEF combined node 115 to monitor and receive a notification when the event occurs. The request includes an identifier of the UE (e.g., External-id=user1@ericsson.com) and an identifier of the event (e.g., event=location-change).

[0051] While the SCEF+NEF combined node 115 integrates SCEF and NEF, the combined node 115 is configured (via local policy) to use a single endpoint (e.g., UDM) as the target of the subscription. Thus, in 205, the SCEF+NEF combined node 115 includes, via an event subscription, an indication indicating that notifications to the combined SCEF / NEF node 115 are also required to cover location changes in the evolved packet core (EPC) / 4G. That is, it is not necessary to subscribe to the same event to the HSS (e.g., HSS front end (HSS-FE) 107) via the s6t diameter interface.

[0052] In operation 207, the diameter identification information of the SCEF+NEF combined node 115 is also included for the EPC / MME (e.g., MME103) to report directly via T6a in case of a location change detected in the EPC. As a result, an AMF (e.g., AMF109) that reports location changes to the SCEF+NEF combined node 115 (using 5GC HTTP-based notifications) and an MME103 that reports location changes to the SCEF+NEF combined node 115 (using, e.g., a legacy type of diameter protocol) are obtained.

[0053] In 209, the SCEF+NEF combined node 115 initiates a request (e.g., MonitoringEventSubscribe) to the UDM113. The request includes the UE's identification information (e.g., External-id=user1@ericsson.com), the identifier of the event (e.g., event=location-change), the identifier of another requested domain (e.g., additional-requested-domain=EPC), and the identifier of the SCEF+NEF combined node 115 for the another requested domain (e.g., combined-SCEF-id).

[0054] In 211, the UDM 113 stores the subscription data (e.g., event type = location change, NEF notification address, and combined - SCEF - id) sent by the SCEF+NEF combined node 115. In some embodiments, the UDM 113 stores the configuration (configuration information) in the 5GS - UDR. In 212, the UDM 113 configures (sets) the monitoring events for the UE in the 5GC. In some embodiments, the UDM 113 contacts (communicates with) the corresponding NF (e.g., AMF, SMF) within the 5GC required by the event to be monitored.

[0055] In 214, the UDM 113 sends a response, including a confirmation (acknowledgment) indicating that the configuration of the monitoring event has been successful in both the 5GC domain and the EPC domain, to the combined SCEF+NEF. Some embodiments provide that the UDM 113, which supports interworking with the EPC, depends on the HSS to synchronize the UDM 113 to the status of these monitoring events within the EPC domain. For example, the UDM 113 may not need to configure the monitoring event in the HSS.

[0056] In some embodiments, the SCEF+NEF does not need to execute the same procedure for configuring the event to be monitored twice for the HSS+UDM. For example, when the HSS+UDM is deployed as a combined node, the monitoring event needs to be configured only once by the SCEF+NEF.

[0057] Some embodiments provide that the SCEF+NEF can configure monitoring events applicable to both the EPC and 5GC using only 5GC procedures for the UDM. In this case, the SCEF+NEF indicates that the monitoring event is also applicable to the EPC (i.e., the event must be reported by both the 5GC and the EPC), and may include SCEF identification information (i.e., if the event needs to be configured at the serving node within the EPC, the corresponding notification needs to be sent directly to the SCEF). When the HSS and UDM are deployed as separate network entities, the UDM uses the HSS service to configure monitoring events in the EPC as defined in 3GPP TS 23.632

[0102] . The UDM returns an indication to the SCEF+NEF indicating whether the configuration of the monitoring event in the EPC was successful. If the UDM reports that it is not possible to configure the monitoring event in the EPC, the SCEF+NEF can configure the monitoring event using EPC procedures via the HSS as defined in 3GPP TS 23.682

[36] . In some embodiments, the SCEF+NEF configures monitoring events in the EPC and 5GC using only 5GC procedures.

[0058] Referring to FIG. 2b, at 213 and 215, the UDM113 checks (via the Network Repository Function (NRF)) whether there is an HSS-FE in the network that provides a common event exposure service (e.g., nhss-common-ee).

[0059] Referring to FIGS. 2b to 2c, when an HSS-FE that supports the common event exposure service exists in the network according to operations 213 and 215, operations 217 to 239 can be performed. Alternatively, if the HSS-FE that supports the common event exposure service is not identified (recognized), or if a specific event is not supported, or if it is rejected by the HSS-FE, operations 241 to 251 in FIGS. 2c to 2d can be performed.

[0060] First, referring to FIGS. 2b to 2c and operations 217 to 239, in operation 217, an HSS-FE that supports the common event exposure service in the network is identified (e.g., HSS-FE107). In 219, the UDM113 starts a subscription to HSS-FE107 via a new service (e.g., nhss-ee) generated by the HSS-FE107. In 221, the UDM113 starts a request (e.g., MonitoringEventSubscribe) to the HSS-FE107. The request includes the identification information of the UE (e.g., External-id=user1@ericsson.com), the identifier of the event (e.g., event=location-change), the identifier of the UDM (e.g., UDM notification address), and the identifier of the SCEF+NEF combined node 115 (e.g., combined-SCEF-id ).

[0061] In 223, the HSS-FE107 stores the subscription information in another network node (e.g., integrated data repository (UDR)-evolved packet system (EPS) UDR-EPS node 105). The subscription information includes, for example, the event type, the identification of the UE, the identifier of the UDM, and the identifier of the SCEF+NEF combined node 115. The HSS-FE107 configures the events in the mobility management entity node (e.g., MME103) to be reported to the SCEF+NEF combined node 115.

[0062] At 225, HSS-FE 107 starts a response to UDM 113 indicating that HSS-FE 107 has successfully accepted a subscription from UDM 113, including an indication that an event (e.g., location change) is being monitored in the EPC domain. As a result, MME 103 also reports events detected in the EPC via the same subscription (e.g., common exposure) indicated by SCEF+NEF combined node 115.

[0063] At 229, UDM 113 starts a response (e.g., MonitoiringEventSubscribeResponse) to SCEF+NEF combined node 115, indicating that a single subscription has been applied to at least two network domains (e.g., EPC and 5G). The response also includes an indication (e.g., EPC-monitoring-common-exposure) notifying SCEF+NEF combined node 115 that the event is being monitored in each of at least two network domains.

[0064] Referring to Figure 2c, at 231a, UDM 113 starts a management notification (e.g., manually terminated event), which is reported from UDM 113 to SCEF+NEF combined node 115 without going through HSS-FE 107. At 231b, since a subscription for common exposure has been accepted, SCEF+NEF combined node 115 does not start a subscription to HSS-FE 107 via the diameter (e.g., s6t interface). Notifications regarding events (e.g., location change) related to both at least two network domains (e.g., EPC and 5G) are sent from MME 103 and AMF node 109 to SCEF+NEF combined node 115.

[0065] At 233, AMF 109 detects an event (e.g., location change).

[0066] At 235, AMF109 starts a notification (e.g., EventNotify) to the SCEF+NEF combined node 115. The notification includes a notification address (e.g., SCEF+NEF HTTP notification address) for the SCEF+NEF combined node 115.

[0067] At 237, MME103 also detects an event (e.g., location change) in the second network domain.

[0068] At 237, MME103 starts a notification (e.g., EventNotify) to the SCEF+NEF combined node 115. The notification includes a notification address (e.g., SCEF+NEF diameter address) for the SCEF+NEF combined node 115.

[0069] Referring to FIGS. 2c-2d, as referred to above, alternatively, when the HSS-FE that supports the common event exposure service is not identified, or when a specific event is not supported or is rejected by the HSS-FE, the operations 241-251 in FIGS. 2c-2d may be performed.

[0070] At 241, in response to operations 213 and 215, UDM113 starts a response to the SCEF+NEF combined node 115 without an explicit indication that the event (e.g., location change) is being monitored in the second network domain (e.g., EPC). As a result, only AMF109 notifies the SCEF+NEF combined node 115 about the detected event (e.g., location change) (in other words, there is no common network exposure).

[0071] In 243, the UDM 113 initiates a response (e.g., MonitoringEventSubscribeResponse) to the SCEF+NEF combined node 115. The response includes an indication that notifies the SCEF+NEF combined node 115 that the event is being monitored in at least one of two network domains (e.g., in 5G).

[0072] In 245, since there is no indication indicating that an event is configured in the second network domain (e.g., EPC) using a single subscription to the UDM 113, the SCEF+NEF combined node 115 initiates a subscription to the HSS-FE 107 for the MME 103 to monitor and report events in the second network domain (e.g., EPC).

[0073] In 247, the SCFE+NEF combined node 115 initiates a request (e.g., s6t-Configuration-Information-Request) to the HSS-FE 107 for a subscription to monitor and report events in the second network domain (e.g., EPC). The request includes the identification information of the UE and the identification information of the event (e.g., event=location-change).

[0074] In 249, the HSS-FE 107 stores the subscription information (e.g., event type, identification information of the UE, and identification information of the SCEF+NEF combined node 115) in the UDR-EPS 105 and configures an event in the MME 103 to report the detected event to the SCEF+NEF combined node 115.

[0075] At 251, HSS-FE107 starts a response (e.g., s6t-Configuration-Information-Answer) to the SCEF+NEF combined node 115. The response includes an indication that the event is properly configured for the MME103 to monitor and report events in the second network domain (e.g., EPC).

[0076] In various embodiments of the present disclosure, the HSS and UDM are combined sa A method for common network exposure in a deployment / network where they cannot be combined (e.g., in the case of some vendors) is provided. Thus, the method can provide advantages by avoiding the need for duplicate subscriptions from the combined EF.

[0077] In addition, since the method provides a single entry point (e.g., HTTP-based) for network exposure, the method can provide further advantages by enabling the evolution of the network in a more cloud-native manner. As a result, it will bring in the future that the method can be enhanced without the need to infinitely support legacy diameter protocols.

[0078] Next, the operation of the exposure node (e.g., the SCEF+NEF combined node 115 implemented using the block diagram configuration of FIG. 5) will be described in relation to the flowchart of FIG. 7 according to various embodiments of the concepts of the present disclosure. For example, the modules may be stored in the memory 505 of FIG. 5, and these modules may provide instructions such that when the instructions of the modules are executed by at least one processor 503, at least one processor 503 executes each operation of the flowchart.

[0079] Referring now to FIG. 9, an exemplary signaling sequence for common event exposure according to various embodiments of the present disclosure is shown. As illustrated, in a scenario where interworking between 5GS and EPC is possible, an information flow is provided for configuring a monitoring event applicable to both EPC and 5GC using 5GC procedures towards the UDM. At 902, the AF configures a monitoring event via the SCEF+NEF using the Nnef_EventExposure_Subscribe service operation. At 904, the SCEF+NEF configures a monitoring event within the UDM+HSS using the Nudm_EventExposure_Subscribe service operation. In some embodiments, the combined SCEF+NEF indicates that the monitoring event is also applicable to the EPC (i.e., the event must be reported by both 5GC and EPC). Depending on the type of event, the SCEF+NEF may include SCEF identification information (i.e., if the event needs to be configured at a serving node within the EPC, the corresponding notification needs to be sent directly to the SCEF).

[0080] In 906a and 906b, the HSS+UDM configures the monitoring events. For events that need to be reported to the serving node (e.g., location change), the HSS+UDM requests the corresponding serving nodes in the 5GC and EPC to configure the monitoring events. The HSS+UDM uses the corresponding Nnf_EventExposure_Subscribe service operation to configure the monitoring events in the 5GC serving NF. The HSS+UDM uses the procedures defined in 3GPP TS 23.682

[23] to configure the monitoring events in the EPC serving node (i.e., in the MME). The HSS+UDM provides the SCEF Id to the MME during the configuration of the monitoring events in the EPC. When the HSS and UDM are deployed as separate network entities, the UDM uses the HSS service to configure the monitoring events in the EPC as defined in 3GPP TS 23.632

[68] .

[0081] In 908, the HSS+UDM responds to the SCEF+NEF with an indication indicating that the monitoring events have been successfully configured in the 5GC and EPC by sending the Nudm_EventExposure_Subscribe response.

[0082] In 910, the SCEF+NEF responds to the AF by sending the Nnef_EventExposure_Subscribe response.

[0083] In 912a, 912b, and 912c, the HSS+UDM or 5GC or EPC serves nguWhen a node detects the corresponding event, SCEF+NEF is notified. HSS+UDM notifies SCEF+NEF using the Nudm_EventExposure_Notify service operation. The serving NF within 5GC notifies SCEF+NEF using the corresponding Nnf_EventExposure_Notify service operation. In operation 906, MME notifies SCEF+NEF using the procedure defined in 3GPP TS 23.682

[23] and using the SCEF identification information provided by HSS+UDM.

[0084] In 914, SCEF+NEF notifies AF using the Nnef_EventExposure_Notify service operation.

[0085] Referring to FIG. 7, at 701, an exposure node (e.g., 115, 500) initiates a request to a first network node for subscription to events of a communication device. The request includes subscription information for a report regarding the event, including an indication of a common network exposure in at least two network domains, including the first network domain to which the first network node belongs and at least one other network domain, and second identification information of the exposure node for a report regarding the event for at least one other second network domain.

[0086] At 703, in response to a request, the exposure node receives a response from the first network node. The response includes at least one of: a first confirmation indicating that an event will be reported to the exposure node for a second network domain for the common network exposer; and a second confirmation indicating that an event will be reported to the exposure node for the first network domain. The second confirmation omits the indication of the common network exposer.

[0087] In some embodiments, the operation of the exposure node can further include, after receiving the first confirmation, receiving event notifications from each of a second network node and a third network node for each of at least two network domains (705).

[0088] In some embodiments, the subscription includes a single subscription to events within at least two network domains.

[0089] In some embodiments, the identification information of the exposure node includes the diameter identification information of the combined service capability exposure function (SCEF) for the second network domain.

[0090] In some embodiments, receiving event notifications from each of a second network node and a third network node for each of at least two network domains respectively includes: receiving an event notification from the second network node via the diameter protocol; and receiving an event notification from the third network node via an http-based notification.

[0091] In some embodiments, the operation of the exposure node may further include starting a subscription (707) towards a fourth network node regarding the reporting of events by a second network node for a second network domain after receiving only the second confirmation.

[0092] In some embodiments, the first network node is an integrated data management (UDM) node in a 5GC network.

[0093] In some embodiments, the second network node is a mobility management entity (MME) node in an evolved packet core (EPC) network.

[0094] In some embodiments, the third network node is at least one of an access management function no - node (AMF) and a session management function node (SMF) in a 5GC network.

[0095] In some embodiments, the fourth network node is a home subscriber server (HSS) in an evolved packet core (EPC) network.

[0096] In some embodiments, the first identification information of the exposure node in the first network domain is the identification information of a network exposure function node (NEF).

[0097] The various operations from the flowchart of FIG. 7 may be optional with respect to some embodiments of the exposure node and related methods. For example, the operations of blocks 705-707 may be optional.

[0098] Corresponding embodiments of the concepts of the present disclosure for an exposure node, a computer product, and a computer program are also provided.

[0099] Next, the operation of the first network node (e.g., UDM 113 implemented using the block diagram configuration of FIG. 6) will be described in relation to the flowchart of FIG. 8 according to some embodiments of the inventive concept. For example, the modules may be stored in the memory 605 of FIG. 6, and these modules may provide instructions such that when the instructions of the modules are executed by at least one processor 603, at least one processor 603 executes each operation of the flowchart.

[0100] Referring to FIG. 8, a first network node (e.g., UDM 113, 500) receives a request (801) from an exposure node for a subscription (registration) for an event of a communication device. The request includes an indication of a common network exposure in at least a second network domain for a report on the event and identification information of the exposure node for a report on the event related to the second network domain. The first network node further checks (803) a fourth network node in the communication network that provides a common event exposure service.

[0101] In some embodiments, the operation of the first network node may further include storing subscription information (805).

[0102] In some embodiments, the operation of the first network node can further include identifying (specifying) a fourth network node in the communication network that provides a common event exposure service (807). This operation further includes initiating at least one request (809) directed to the fourth network node for monitoring events of the communication device for joining the fourth network node via the common event exposure service generated by the fourth network node. This operation further includes receiving (811), in response to the at least one request, a response from the fourth network node that includes an indication that the combined network node has successfully accepted the subscription and is monitoring events.

[0103] In some embodiments, the operation of the first network node can further include initiating a response to the exposure node (813) in response to the request. The response includes at least one of a first indication indicating that events are being monitored in one of at least two network domains and a second indication indicating that the events have been accepted in the second network domain.

[0104] In some embodiments, the first network node includes an integrated data management (UDM) node within the 5G core network.

[0105] In some embodiments, the second network node includes a home subscriber server (HSS) within the evolved packet core (EPC) network.

[0106] The various operations from the flowchart of FIG. 8 can be optional with respect to some embodiments of the first network node and related methods. For example, the operations of blocks 805-813 can be optional.

[0107] Corresponding embodiments of the inventive concept for the first network node, computer product, and computer program are also provided Exemplary communication devices and network nodes:

[0108] FIG. 3 is a block diagram showing a communication device 300 (e.g., UE 101 of FIG. 1) configured according to some embodiments. In the context of the present disclosure, the term communication device includes a device that can communicate with a network node such as a base station or another wireless device by transmitting and / or receiving wireless signals. Thus, the term communication device includes, but is not limited to, mobile phones, fixed or mobile wireless MTC devices for machine-to-machine communication, integrated or embedded wireless cards, externally pluggable wireless cards, and the like. The communication device 300 includes a transceiver 301 having one or more power amplifiers for transmitting and receiving via a plurality of antennas of an antenna array to provide uplink and downlink wireless communication with a wireless network node (e.g., base station, eNB, gNB, etc.) of a communication network. The transceiver 3 Instead of, or in addition to, the transceiver 01, the communication device 300 may include an optical reception front end configured to receive such optical signaling from an optical WiFI AP. The communication device 300 transceiver further includes a processor circuit 303 (also referred to as a processor) coupled to the 301 and a memory circuit 305 (also referred to as a memory). The memory 305 stores computer-readable program code that, when executed by the processor circuit 303, causes the processor circuit 303 to perform operations according to the embodiments disclosed herein. According to other embodiments, the processing circuit 303 may be defined to incorporate memory so that a separate memory circuit is not required.

[0109] FIG. 4 is a configuration diagram showing a radio access network node 400 of a communication network (e.g., the base station of FIG. 1, eNB, gNB, 5G RAN node 199, EPC RAN node 121 of FIG. 1, etc.). The network node 400 includes a processor circuit 403 (also referred to as a processor), a memory circuit 405 (also referred to as a memory), and a network interface 407 configured to communicate with other network nodes (e.g., a wired network interface and / or a wireless network interface). The network node 400 may be configured as a radio network node including a transceiver 401 and / or an optical signal front end, and has one or more power amplifiers for transmitting and receiving via a plurality of antennas of an antenna array. The memory 405 stores computer-readable program code that, when executed by the processor 403, causes the processor 403 to perform operations according to the embodiments disclosed herein. According to other embodiments, the processing circuit 403 may be defined to include a memory so that a separate memory circuit is not required.

[0110] FIG. 5 is a configuration diagram showing an exposure node 500 of a communication network (e.g., the SCEF+NEF combined node 115 of FIG. 1). The exposure node 500 includes a network interface circuit 507 (also referred to as a network interface) configured to provide communication with other nodes of the core network and / or the radio access network RAN. The exposure node may also include a processing circuit 503 (also referred to as a processor) coupled to the network interface circuit, and a memory circuit 505 (also referred to as a memory) coupled to the processing circuit. The memory circuit 505 may include computer-readable program code that, when executed by the processing circuit 503, causes the processing circuit to perform operations according to the embodiments disclosed herein. According to other embodiments, the processing circuit 503 may be defined to include a memory so that a separate memory circuit is not required.

[0111] As described herein, the operation of the exposure node 500 may be performed by the processing circuit 503 and / or the network interface circuit 507. For example, the processing circuit 503 may control the network interface circuit 507 to transmit communications to one or more other network nodes through the network interface circuit 507 and / or receive communications from one or more other network nodes through the network interface circuit. Further, the modules may be stored in the memory 505, and these modules may provide instructions such that when the instructions of the modules are executed by the processing circuit 503, the processing circuit 503 performs respective operations (e.g., the operations discussed herein with respect to the exemplary embodiments regarding the public network node).

[0112] FIG. 6 is a block diagram showing a first network node 600 (e.g., UDM 113 in FIG. 1) of a communication network. The first network node 600 includes a network interface circuit 607 (also referred to as a network interface) configured to provide communication with other nodes of a core network and / or a radio access network RAN. The first network node may also include a processing circuit 603 (also referred to as a processor) coupled to the network interface circuit and a memory circuit 605 (also referred to as a memory) coupled to the processing circuit. The memory circuit 605 may include computer-readable program code that, when executed by the processing circuit 603, causes the processing circuit to perform operations according to the embodiments disclosed herein. According to other embodiments, the processing circuit 603 may be defined to include a memory such that a separate memory circuit is not required.

[0113] As described herein, the operation of the first network node 600 may be performed by the processing circuit 603 and / or the network interface circuit 607. For example, the processing circuit 603 may control the network interface circuit 607 to transmit communications to one or more other network nodes through the network interface circuit 607 and / or receive communications from one or more other network nodes through the network interface circuit. Further, the modules may be stored in the memory 605, and these modules may provide instructions such that when the instructions of the modules are executed by the processing circuit 603, the processing circuit 603 performs respective operations (e.g., the operations discussed herein with respect to exemplary embodiments related to an exposure network node). Further definitions and embodiments are discussed below:

[0114] In the foregoing description of various embodiments of the concepts of the present disclosure, it should be understood that the terms used herein are for the purpose of describing particular embodiments only and are not intended to limit the concepts of the present disclosure. Unless otherwise defined, all terms (including technical and scientific terms) used herein shall have the same meaning as commonly understood by one of ordinary skill in the art to which the concepts of the present disclosure pertain. Further, terms defined as in a commonly used dictionary shall be interpreted to have a meaning that coincides with the meaning in the context of the present specification and the relevant art, and shall not be interpreted in an idealized or overly formal sense unless explicitly defined herein.

[0115] When an element is referred to as being "connected to", "coupled to", "responsive to", or variations thereof, another element, it can be directly connected to, coupled to, or responsive to the other element, or intervening elements may be present. In contrast, when an element is referred to as being "directly connected", "directly coupled", "directly responsive", or variations thereof, there are no intervening elements. The same reference numerals refer to the same elements throughout. Further, as used herein, "coupled", "connected", "responsive", or variations thereof can include being wirelessly coupled, connected, or responsive. As used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. Well-known functions or configurations may not be described in detail for brevity and / or clarity. The term "and / or" includes any and all combinations of one or more of the associated listed items.

[0116] The terms first, second, third, etc. may be used herein to describe various elements / acts, but it will be understood that these elements / acts are not to be limited by these terms. These terms are only used to distinguish one element / act from another. Thus, a first element / act in some embodiments may be referred to as a second element / act in other embodiments without departing from the teachings of the concepts of the present disclosure. The same reference numerals or the same reference signs indicate the same or similar elements throughout the specification.

[0117] As used herein, the terms "comprise", "comprising", "comprises", "have", "having", "has", or variations thereof are open-ended and include one or more recited features, integers, elements, steps, parts, or functions or groups of functions, but do not preclude the presence or addition of one or more other features, integers, elements, steps, parts, functions, or groups of functions. Further, as used herein, the general abbreviation "e.g." (for example), derived from the Latin phrase "exempli gratia", may be used to introduce or specify a general example or examples of the previously mentioned items and is not intended to limit such items. The general abbreviation "i.e.", derived from the Latin phrase "id est", may be used to specify a particular item from a more general listing.

[0118] Exemplary embodiments are described herein with reference to block diagrams and / or flowcharts of a computer-implemented method, apparatus (system and / or device), and / or computer program product. wo The block diagrams and / or flowcharts no blocks, as well as the block diagrams and / or flowcharts noIt should be understood that the combination of blocks can be implemented by computer program instructions executed by one or more computer circuits. These computer program instructions are provided to the processor circuits of general-purpose computer circuits, dedicated computer circuits, and / or other programmable data processing circuits, and the instructions, conversions, and control transistors executed via the processor of a computer and / or other programmable data processing device, the values stored in memory locations, and other hardware components within such circuits implement the functions / operations specified in the block diagrams and / or flowchart blocks or blocks, thereby generating a machine to create the means (function) and / or structure for implementing the functions / operations specified in the block diagrams and / or flowchart blocks.

[0119] These computer program instructions can also be stored in a tangible computer-readable medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable medium produce a manufactured article that includes instructions for implementing the functions / operations specified in one or more blocks of the block diagram and / or flowchart. Accordingly, embodiments of the concepts of the present disclosure can be implemented in hardware and / or software (including firmware, resident software, microcode, etc.) executed on a processor such as a digital signal processor, and these may collectively be referred to as "circuits," "modules," or variations thereof.

[0120] Also, note that in some alternative embodiments, the functions / operations described within a block may be performed in an order different from that described in the flowchart. For example, two blocks shown in succession may actually be performed substantially simultaneously, or the blocks may sometimes be performed in the reverse order depending on the functions / operations involved. Further, the function of a given block in a flowchart and / or block diagram may be split into multiple blocks, and / or the functions of two or more blocks in a flowchart and / or block diagram may be at least partially integrated. Finally, other blocks may be added / inserted between the illustrated blocks and / or blocks / operations may be omitted without departing from the scope of the concepts of the present disclosure. Additionally, although some of the figures include arrows on communication paths to indicate the primary direction of communication, it should be understood that communication may occur in the direction opposite to that of the drawn arrows.

[0121] Without substantially departing from the principles of the concepts of the present disclosure, many variations and modifications can be made to the embodiments. All such variations and modifications are intended to be included within the scope of the concepts of the present disclosure. Therefore, the subject matter disclosed above should be considered illustrative and not limiting, and the examples of embodiments are intended to encompass all such modifications, enhancements, and other embodiments within the spirit and scope of the concepts of the present disclosure. Accordingly, the scope of the concepts of the present disclosure should be determined by the broadest permissible interpretation of the present disclosure, including the examples of embodiments and their equivalents, to the maximum extent permitted by law, and should not be limited or restricted by the foregoing detailed description.

[0122] The claims are set forth below. Reference numerals / letters are provided in parentheses as examples / illustrations without limiting the claims to the specific elements indicated by the reference numerals / letters.

Claims

1. A method performed by a first network node (113, 600) in a communication network, the method comprising: Receiving, from an exposer node, a request for subscription to an event of a communication device, the request including an indication of a common network exposer in at least a second network domain for reporting on the event and identification information of the exposer node for the second network domain for the reporting on the event (801); Identifying a fourth network node (107) in the communication network that provides a common event exposer service (807); Initiating, for monitoring the event of the communication device, at least one request directed to the fourth network node (107), the at least one request being for subscription to the fourth network node (107) via the common event exposer service generated by the fourth network node (107) (809); Receiving, from the fourth network node (107), a response to the at least one request, the response including an indication that the combined network node has successfully accepted the subscription and is monitoring the event (811); A method having the above.

2. The method according to claim 1, further comprising: Storing subscription information (805).

3. The method according to claim 1 or 2, further comprising: In response to the request, initiating a response to the exposer node (813), the response including at least one of a first indication that the event is being monitored in one of at least two network domains including a first network domain to which the first network node belongs and the second network domain and a second indication that the event has been accepted in the second network domain.

4. The method according to any one of claims 1 to 3, wherein the first network node includes an integrated data management (UDM) node in a 5G C network.

5. The method according to any one of claims 1 to 4, wherein the fourth network node includes a home subscriber server (HSS) in an evolved packet core (EPC) network.

6. A first network node (113, 600) in a communication network, Receiving, from an exposure node, a request for subscription to an event of a communication device, the request including an indication of a common network exposure in at least a second network domain for reporting on the event and identification information of the exposure node for the second network domain for reporting on the event (801); Identifying a fourth network node (107) in the communication network that provides a common event exposure service (807); Initiating, for monitoring the event of the communication device, at least one request directed to the fourth network node (107), the at least one request being for subscription to the fourth network node (107) via the common event exposure service generated by the fourth network node (107) (809); Receiving, from the fourth network node (107), a response to the at least one request, the response including an indication that the combined network node has successfully accepted the subscription and is monitoring the event (811); A first network node adapted to perform operations including.

7. The first network node (113, 600) according to claim 6, adapted to perform the method according to any one of claims 2 to 5.

8. A computer program comprising program code to be executed by at least one processor (603) of a first network node (113, 600), which, when executed, causes the first network node to execute the method according to any one of claims 1 to 5.

9. A method to be executed by a fourth network node (107) in a communication network, the fourth network node providing a common event exposure service, the method comprising: Receiving (809) from a first network node at least one request for a subscription for monitoring events of a communication device via the common event exposure service generated by the fourth network node (107); In response to the at least one request, providing (811) to the first network node a response including an indication that a combined network node has successfully accepted the subscription and is monitoring the events; A method having the above steps.

10. The method according to claim 9, wherein the fourth network node includes a home subscriber server (HSS) in an evolved packet core (EPC) network.

11. The method according to claim 9 or 10, wherein the first network node includes an integrated data management (UDM) node in a 5G C network.

12. A fourth network node in a communication network, the fourth network node providing a common event exposure service and Receiving (809) from a first network node at least one request for a subscription for monitoring events of a communication device via the common event exposure service generated by the fourth network node (107); In response to the at least one request, providing, to the first network node, a response that includes an indication that the combined network node has successfully accepted the subscription and is monitoring the event (811); A fourth network node adapted to perform operations including this. **Claim 13**: The fourth network node according to claim 12, the fourth network node including a home subscriber server (HSS) in an evolved packet core (EPC) network. **Claim 14**: A communication network having the first network node according to claim 6 or 7 and the fourth network node according to claim 12 or 13.

Images