Network Node and Event Monitoring Method Therein

Abstract

The present disclosure provides a method (300) in a vertical application layer (VAL) server. The method (300) includes sending (310) a monitoring event subscription request to a network resource management (NRM) server. The monitoring event subscription request includes a list of one or more VAL user or VAL user equipment (UE) identifiers (IDs) for which event monitoring is requested, or a VAL group ID for one or more VAL users or groups of VAL UEs for which event monitoring is requested, and a monitoring profile ID corresponding to a list of one or more events to be monitored, or event details indicating the list of one or more events to be monitored. The method (300) further includes receiving (320) a monitoring event subscription response from the NRM server in response to the monitoring event subscription request.

Description

Technical Field

[0001] This Disclosure relates to communication technologies, and more particularly, to network nodes and methods therefor for event monitoring.

Background Art

[0002] Since the 3rd Generation Partnership Project (3GPP (registered trademark)) Release 16, a Service Enablement Architecture Layer (SEAL) for verticals has been introduced to support vertical applications (e.g., vehicle-to-everything (V2X) applications). 3GPP (registered trademark) Technical Specification (TS) 23.434, V17.2.0 (which is hereby incorporated by reference in its entirety) defines entities in the application plane and the signaling plane for application enablement services (e.g., group management, configuration management, location management, identification / key management, network resource management, etc.) that can also be reused for vertical applications. SEAL also defines northbound application programming interfaces (APIs) for its individual services to enable flexible integration with vertical applications.

[0003] Figure 1 shows a general on-network function model of SEAL. As shown in the figure, according to the Vertical Application Layer (VAL), VAL clients communicate with VAL servers via the VAL-UU reference point. The VAL-UU reference point supports both unicast and multicast delivery modes. The SEAL function entities on the user equipment (UE) and the server are grouped into SEAL clients and SEAL servers, respectively. SEAL consists of a common set of services (such as group management, location management, etc.) and reference points. SEAL provides its services to the VAL. SEAL clients communicate with SEAL servers via the SEAL-UU reference point. The SEAL-UU reference point supports both unicast and multicast delivery modes. SEAL clients provide service enabling layer support functions to VAL clients via the SEAL-C reference point. VAL servers communicate with SEAL servers via the SEAL-S reference point. One or more SEAL servers can communicate with the underlying 3GPP (registered trademark) network system using their respective 3GPP (registered trademark) interfaces defined by the 3GPP (registered trademark) network system.

[0004] One of the capabilities provided by SEAL is network resource management (NRM). NRM is a SEAL service that provides network resource management (e.g., unicast and multicast network resources) related functions for one or more vertical applications. Figure 2 shows the on-network functional model of SEAL for NRM. As shown, the NRM client communicates with the NRM server via the NRM-UU reference point. The NRM client supports NRM functions for the VAL client via the NRM-C reference point. The VAL server communicates with the NRM server via the NRM-S reference point. The NRM server communicates with the Broadcast Multicast Service Center (BM-SC) via the MB2-C and xMB-C reference points to obtain and control multicast resources from its underlying 3GPP network system. The NRM server communicates with the Policy and Charging Rules Function (PCRF) via the Receiving reference point and / or the Policy Control Function (PCF) via the N5 reference point to control unicast resources from its underlying 3GPP network system.

[0005] 3GPP networks provide event monitoring capabilities to application functions (AFs) in several network functions, including: ● Network Exposed Functions (NEF): The event exposed APIs specified in 3GPP® TS29.522, V17.2.0, and TS29.122, V17.2.0 provide functions such as UE reachability, packet data network (PDN) connectivity status, and loss of connectivity.

[0006] ●Network Data Analysis Function (NWDAF): The analysis public APIs specified in TS29.522, V17.2.0 and TS29.520, V17.3.0 provide capabilities related to UE mobility, network congestion, and quality of service (QoS) sustainability, among others.

[0007] In Figure 2, the NRM server communicates with the NEF via the T8 / N33 reference point to enable the event monitoring function in the SEAL's NRM service.

[0008] However, it is desirable to be able to provide enhanced functionality for event monitoring in SEAL instead of simply re-exposing 3GPP® Core Network services, or the VAL Server can directly invoke 3GPP® Core Network services without incurring the additional delay due to the additional message hop in the NRM service. Summary of the Invention

[0009] An object of the present disclosure is to provide a network node and method that can improve event monitoring in SEALs, particularly for NRMs.

[0010] According to a first aspect of the present disclosure, there is provided a method in a VAL server, the method including sending a monitoring event subscription request to an NRM server. subscription request The monitoring profile ID includes a list of one or more VAL user or VAL UE identifiers (IDs) for which event monitoring is requested, or a VAL group ID for one or more VAL user or VAL UE groups for which event monitoring is requested, a monitoring profile ID corresponding to a list of one or more events to be monitored, or event details indicating the list of one or more events to be monitored, a VAL service ID identifying a VAL service associated with at least one of the one or more events to be monitored, and one or more validity conditions for at least one of the one or more events to be monitored, wherein the one or more validity conditions include one or more temporal and / or spatial conditions for at least one event to be valid. subscription requestFurther including receiving a monitoring event subscription response (subscription response) as a response to

[0011] According to one embodiment, the monitoring event subscription request When including event details, the monitoring event subscription response May include a monitoring profile ID corresponding to a list of one or more events to be monitored.

[0012] According to one embodiment, each of the one or more events to be monitored may include a monitoring event or an analysis event.

[0013] According to one embodiment, the method may further include receiving from the NRM server a notification of at least one of the one or more events to be monitored.

[0014] According to a second aspect of the present disclosure, a method in an NRM server is provided. The method includes receiving a monitoring event subscription request From the VAL server. The monitoring event subscription request Is a list of IDs of one or more VAL users or VAL UEs for which event monitoring is requested, or a VAL group ID of one or more VAL users or VAL UE groups for which event monitoring is requested, and a monitoring profile ID corresponding to a list of one or more events to be monitored, or event details indicating a list of one or more events to be monitored, and a VAL service ID identifying a VAL service associated with at least one of the one or more events to be monitored, and one or more enabling conditions for at least one of the one or more events to be monitored, and the one or more enabling conditions include one or more temporal and / or spatial conditions for at least one event to be valid. The method further includes transmitting the monitoring event subscription request In response to the monitoring event subscription response To the VAL server.

[0015] According to one embodiment, the method comprises: subscription request may further include determining a monitoring profile ID corresponding to the list of one or more events to be monitored based on a correspondence or mapping between the monitoring profile ID and the event details when the monitoring profile ID includes event details. subscription response may include the determined monitoring profile ID.

[0016] According to one embodiment, the method comprises: subscription request may further include determining event details indicating a list of one or more events to be monitored based on a correspondence or mapping between the monitoring profile ID and the event details when the monitoring profile ID includes a monitoring profile ID.

[0017] According to one embodiment, the correspondence or mapping may be pre-configured by an operations and maintenance (O&M) entity or may be based on one or more previous monitored events with event details. subscription request It may be created based on the

[0018] According to one embodiment, each of the one or more events to be monitored may include a monitoring event or an analysis event.

[0019] According to one embodiment, the method may further include sending a request to a core network node to subscribe to at least one of the one or more events to be monitored for one or more VAL users or VAL UEs, receiving notification of the at least one event from the core network node, and notifying a VAL server about the at least one event.

[0020] According to one embodiment, the method may further include determining event-specific information for the VAL service based on the VAL service ID.

[0021] According to one embodiment, the event-specific information may be determined based on a correspondence or mapping between the VAL service ID and the event-specific information, and the correspondence or mapping is pre-configured by the O&M entity.

[0022] According to one embodiment, the determined event-specific information can complement the event-specific information in the event details.

[0023] According to one embodiment, the event-specific information may include service quality (QoS) requirements for at least one event.

[0024] According to one embodiment, the method further includes sending a subscription request for at least one event for one or more VAL users or VAL UEs, where the request includes event-specific information to a core network node, receiving a notification of at least one event from the core network node, and notifying a VAL server about at least one event.

[0025] According to one embodiment, the method further includes sending a subscription request for at least one event for one or more VAL users or VAL UEs to a core network node, where the request includes the one or more validity conditions, receiving a notification of at least one event from the core network node, and notifying a VAL server about at least one event.

[0026] According to one embodiment, the method further includes sending a subscription request for at least one event to a core network node, receiving a notification of at least one event from the core network node, and notifying a VAL server about at least one event only if at least one event is valid according to one or more validity conditions.

[0027] the present disclosure According to a third aspect, a network node is provided. The network node includes a communication interface, a processor, and a memory. The memory includes instructions executable by the processor, whereby the network node is operable to execute the method according to the first aspect when implementing a VAL server, or to execute the method according to the second aspect when implementing an NRM server.

[0028] According to a fourth aspect of the present disclosure, a computer-readable storage medium is provided. The computer-readable storage medium has computer-readable instructions stored thereon. The computer-readable instructions, when executed by a processor of a network node, configure the network node to execute the method according to the first aspect when implementing a VAL server, or to execute the method according to the second aspect when implementing an NRM server.

[0029] According to an embodiment of the present disclosure, the VAL server can send a monitoring event subscription request to the NRM server, and the monitoring event subscription request can include the VAL group ID of one or more VAL users or groups of UEs for which event monitoring is requested, such that event monitoring may be processed for the group rather than for individual users or UEs. Additionally or alternatively, the monitoring event subscription request may include a monitoring profile ID corresponding to a list of one or more events to be monitored such that the NRM server can derive event details indicating the one or more events from the monitoring profile ID. In this way, the event monitoring function can be improved by providing an API with added value to the VAL server.

Brief Description of the Drawings

[0030] The above and other objects, features and advantages will become more apparent from the following description of the embodiments with reference to the drawings.

[0031]

Figure 1

[0032]

Figure 2

[0033]

Figure 3

[0034]

Figure 4

[0035]

Figure 5

[0036]

Figure 6

[0037]

Figure 7

[0038]

Figure 8

[0039]

Figure 9

[0040] In the present disclosure, a network function, or NF, may be implemented as a network element on dedicated hardware, as a software instance running on dedicated hardware, or as a virtualized function instantiated on a suitable platform, such as a cloud infrastructure.

[0041] The term "terminal device" or "UE" refers to any end device that can access a wireless communication network and receive services therefrom. By way of example and not limitation, a terminal device refers to a mobile terminal, a user equipment (UE), or other suitable device. The UE may be, for example, a subscriber station (SS), a portable subscriber station, a mobile station (MS), or an access terminal (AT). A terminal device may be a portable computer, a desktop computer, an image capture terminal device such as a digital camera, a game terminal device, a music storage and playback device, movementIt may include, but is not limited to, a telephone, a mobile phone, a smartphone, a Voice over Internet Protocol (VoIP) phone, a wireless local loop phone, a tablet, a personal digital assistant (PDA), a wearable device, an in-vehicle wireless device, a wireless endpoint, a mobile station, a laptop embedded equipment (LEE), a laptop-mounted equipment (LME), a USB dongle, a smart device, a wireless customer premise equipment (CPE), etc. In the following description, the terms "terminal device", "terminal", "user device", and "UE" may be used interchangeably. As an example, the terminal device may represent a UE configured to communicate according to one or more communication standards published by the 3rd Generation Partnership Project (3GPP®), such as the Global System for Mobile Communications (GSM) for 3GPP® mobile communications, the Universal Mobile Telecommunications System (UMTS), the Long Term Evolution (LTE), and / or other suitable 1G (1st generation), 2G (2nd generation), 2.5G, 2.75G, 3G (3rd generation), 4G (4th generation), 4.5G, or 5G (5th generation). As used herein, the "user device" or "UE" does not necessarily have to have a "user" in the sense of a human user who owns and / or operates the associated device. According to some embodiments, the terminal device may be configured to transmit and / or receive information without direct human interaction. For example, the terminal device may be designed to transmit information to the network at a predetermined schedule, when triggered by an internal or external event, or in response to a request from a wireless communication network. Alternatively, the UE may represent a device that is intended for sale to or operation by a human user but is not initially associated with a specific human user.

[0042] The terminal device can support device-to-device (D2D) communication, for example, by implementing the 3GPP® standard for sidelink communication, in which case it can be called a D2D communication device.

[0043] As yet another example, in an Internet of Things (IoT) scenario, a terminal device can represent a machine or other device that performs monitoring and / or measurements and transmits the results of such monitoring and / or measurements to another terminal device and / or network equipment. In this case, the terminal device may be a machine-to-machine (M2M) device and may also be referred to as a machine type communication (MTC) device in the context of 3GPP (registered trademark). As one particular example, the terminal device may be a UE implementing the 3GPP (registered trademark) Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices such as power meters, industrial machines, or household or personal devices, such as personal wearables like refrigerators, TVs, and watches. In other scenarios, the terminal device can represent a vehicle or other device that can monitor and / or report its operating state or other functions related to its operation.

[0044] References herein to "one embodiment", "an embodiment", "exemplary embodiments", etc., indicate that the described embodiments may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Further, such phrases do not necessarily refer to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it will be understood by those of ordinary skill in the art that, whether or not explicitly described, such feature, structure, or characteristic can affect other embodiments in connection therewith. associated It will be understood that it is within the knowledge of those skilled in the art that such feature, structure, or characteristic can affect other embodiments in connection therewith, whether or not explicitly described, within the scope of knowledge of those skilled in the art.

[0045] Although terms such as "first" and "second" may be used herein to describe various elements, it should be understood that these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element can be referred to as a second element, and similarly, a second element can be referred to as a first element, without departing from the scope of the exemplary embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed terms.

[0046] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit example embodiments. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. The terms "comprises," "comprising," "has," "having," "includes," and / or "including," as used herein, specify the presence of stated features, elements, and / or components, etc., but may also include one or more other features, elements,

[0047] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein are defined by the principles of ordinary skill in the art to which this disclosure belongs. person having knowledge has the same meaning as commonly understood by

[0048] 3 is a flowchart illustrating a method 300 according to an embodiment of the present disclosure. The method 300 can be performed on a VAL server.

[0049] In block 310, a monitored event subscription request is sent to the NRM server. subscription requesthas: i) a list of the ID(s) of one or more VAL users or VAL UEs for which event monitoring is requested, or a VAL group ID of one or more VAL user or VAL UE groups for which event monitoring is requested, and ii) a monitoring profile ID corresponding to a list of one or more events to be monitored, or event details indicating a list of one or more events to be monitored.

[0050] Here, each of the one or more events to be monitored may be a monitoring event or an analysis event.

[0051] In block 320, a monitoring event subscription response is received from the NRM server as a response to the monitoring event subscription request

[0052] According to an example, if the monitoring event subscription request includes event details, the monitoring event subscription response may further include a monitoring profile ID corresponding to a list of one or more events to be monitored.

[0053] As an example, the monitoring event subscription request may further include a VAL service ID that identifies a VAL service such as V2X platooning or IoT mobility related to event monitoring.

[0054] As an example, the monitoring event subscription request may further include one or more enabling conditions for at least one of the one or more events to be monitored. Here, the one or more enabling conditions may be one or more temporal and / or spatial conditions for at least one event to be valid. For example, an example of an enabling condition may be that the event is valid only from 9:00 am to 10:00 am every Tuesday and / or only in tracking areas TA1 and TA2.

[0055] ​In particular, monitoring events subscription request is a monitoring event as defined in TS23.434 subscription request This can be changed as shown in Table 1 below:

[0056] Table 1 - Event Monitoring subscription request ┌──────────┬──────┬─────────────────────┐ │ Information element │ Status │ Description │ ├──────────┼──────┼───────────────────┤ │Indetities list │O(Note 1)│VAL users for whom event monitoring is required │ │Identifier list │ │or list of VALUE │ ├──────────┼──────┼───────────────────┤ │VAL Group ID │O(Note 1)│VAL UE Group │ │ │ │VAL Group ID │ ├──────────┼──────┼───────────────────┤ │VAL Service ID │O │VAL Service ID │ ├──────────┼──────┼───────────────────┤ │Monitoring Profile ID│O(Note 2)│Monitoring and / or Analytics Events│ │ │ │ Monitoring profile ID that identifies the list │ ├──────────┼──────┼───────────────────┤ │Validity Condition │O │For an event to be considered valid │ │ │ │applied temporal and / or spatial │ │ │ │Conditions │ ├──────────┼──────┼───────────────────┤ │ Event Details │ O (Note 2) │ Monitoring events that the VAL service is interested in │ │ │ │ Events and / or a list of analysis events │ │ │ │ of │ ├──────────┴──────┴───────────────────┤ │ Note 1: For the specified target UE, either a list of VAL users / UEs or │ │ a VAL UE group should be provided │ │ Note 2: Either event details or a monitoring profile ID should exist │ └─────────────────────────────────────┘

[0057] Moreover, the monitoring event subscription response may be a monitoring event as defined in TS23.434 subscription response and it may be modified as shown in Table 2 below:

[0058] Table 2 - Response of Monitoring Subscription of Events ┌──────────┬──────┬───────────────────┐ │ Information Element │ Status │ Description │ ├──────────┼──────┼───────────────────┤ │ Subscription Status │ M │ Indicates the subscription result │ ├──────────┼──────┼───────────────────┤ │ Monitoring Profile ID │ O │ Indicates the monitoring profile identifier. │ │ │ │ Exists when event details are provided in the monitoring event subscription request. │ │ │ │ └──────────┴──────┴───────────────────┘

[0059] As an example, the VAL server may receive notification of at least one of one or more events to be monitored from the NRM server. For example, the notification may be carried in a monitoring event notification message defined in TS 23.434, shown in Table 3 below:

[0060] Table 3 - Monitoring Event Notifications ┌──────────┬──────┬─────────────────────┐ │ Information element │ Status │ Description │ ├──────────┼──────┼───────────────────┤ │EventDetails │ │of the event associated with │VALUE │ │ │List │ ├──────────┼──────┼───────────────────┤ │>identity │M │VALUE to which the event can be associated │ │ Identifier │ │ │ ├──────────┼──────┼───────────────────┤ │>events │M │VALUE associated monitoring and │ │ Events │ │ List of analytics events │ ├──────────┼──────┼───────────────────┤ │Timestamp │O │Timestamp of monitoring and analysis events│ │Timestamp │ │ │ └──────────┴──────┴───────────────────┘

[0061] 4 is a flow chart illustrating a method 400 according to one embodiment of the present disclosure. The method 400 may be performed on an NRM server.

[0062] At block 410, the monitored event subscription requestis received from the VAL server. Monitoring event subscription request has: i) a list of one or more VAL user or VAL UE IDs for which event monitoring is requested, or a VAL group ID of one or more VAL users or VAL UE groups for which event monitoring is requested, and ii) a monitoring profile ID corresponding to a list of one or more events to be monitored, or event details indicating a list of one or more events to be monitored.

[0063] Here, each of the one or more events to be monitored may be a monitoring event or an analysis event.

[0064] Monitoring event subscription request may be a monitoring event as shown in Table 1 above subscription request above.

[0065] In block 420, the monitoring event subscription response is sent to the VAL server in response to the monitoring event subscription request above.

[0066] Monitoring event subscription response may be a monitoring event as shown in Table 2 above subscription response above.

[0067] As an example, the NRM server may then send, to a core network node (e.g., NEF within 5G Core (5GC)), for example, for UE monitoring events or UE analysis events according to 3GPP (registered trademark) TS23.502, V17.1.0 (which is hereby incorporated by reference in its entirety), or for one or more VAL users or VAL UEs according to V17.1.0 (which is hereby incorporated by reference in its entirety), at least one of the one or more events to be monitored subscription request above. Upon receiving a notification of at least one event from the core network node, the NRM server may, for the at least one event, for example, as abovetable It can be notified to the VAL server via the monitoring event notification message shown in 3.

[0068] As an example, for a monitoring event subscription request that includes event details, the NRM server can determine a monitoring profile ID corresponding to a list of one or more events to be monitored based on the correspondence or mapping between the monitoring profile ID and the event details. In this case, the monitoring event subscription response may include the determined monitoring profile ID.

[0069] According to one embodiment, when the monitoring event subscription request includes a monitoring profile ID, the NRM server can determine event details indicating a list of one or more events to be monitored based on the correspondence or mapping between the monitoring profile ID and the event details.

[0070] For example, the correspondence or mapping may be pre-configured by the O&M entity, or may be dynamically created and / or updated based on one or more previous monitoring events subscription request accompanied by event details.

[0071] As an example, the monitoring event subscription request may further include a VAL service ID that identifies a VAL service such as V2X platooning or IoT mobility related to event monitoring. The NRM server can determine event-specific information of the VAL service based on the VAL service ID, for example, based on the correspondence or mapping between the VAL service ID and the event-specific information. Here, the correspondence or mapping may be pre-configured by the O&M entity. For example, the event-specific information may be QoS requirements for at least one event (for example, QoS requirements for an analysis event). As an example, the determined event-specific information is event details (event details within the monitoring event subscription request or the monitoring eventsubscription request The event-specific information may be included in the subscription request sent to the core network node.

[0072] An example is monitoring events. subscription request may further include one or more validity conditions for at least one of the one or more events to be monitored. Here, the one or more validity conditions may be one or more temporal and / or spatial conditions for the at least one event to be valid. For example, an example of a validity condition may be that the event is valid only every Tuesday from 9:00 AM to 10:00 AM and / or only in tracking areas TA1 and TA2.

[0073] According to one embodiment, the core network node may include one or more validity conditions in a request for subscription sent to the core network node such that the core network node may send a notification to the NRM server only if the at least one event is valid according to the one or more validity conditions. Alternatively, upon receiving a notification of the at least one event from the core network node, the NRM server may determine whether the at least one event is valid according to the one or more validity conditions and notify the VAL server only if the at least one event is valid according to the one or more validity conditions.

[0074] The above methods 300 and 400 are further explained with reference to FIGS.

[0075] Figure 5 is a sequence diagram showing an exemplary monitoring event subscription procedure according to an embodiment of the present disclosure. Here, it is assumed that the NRM server is permitted to utilize core network services (monitoring events defined in 3GPP (registered trademark) TS23.502 and analysis services defined in 3GPP (registered trademark) TS23.288).

[0076] In 5.1, the VAL server sends a monitoring event subscription request to the NRM server and requests the NRM server to monitor events related to the VAL UE according to subscription request , and the VAL server shall include information related to events of interest. The VAL server shall include either event details or a monitoring profile ID to identify the monitoring and / or analysis event. The VAL server may also include a VAL service ID applied to the monitoring event, temporal and / or spatial validity conditions.

[0077] In 5.2, the NRM server checks whether the VAL server is permitted to start the monitoring event subscription request . If permitted, the NRM server responds with a monitoring event subscription response message, indicating a successful subscription status (subscription state) together with the subscription information to the VAL server. If the event details are not received, the NRM server derives the event details from the monitoring profile ID based on the local configuration (configuration), and then uses the derived information to utilize the relevant core network services. Otherwise, the NRM server uses the received event details to utilize the relevant core network services and generates a monitoring profile ID included in the monitoring event subscription response . The VAL service ID may be used by the NRM server to derive event-specific information in 3GPP (registered trademark) core network services (e.g., QoS requirements in analysis event subscription).

[0078] Here, the mapping between monitoring profile IDs and event details in the NRM server may be pre-configured by O&M and / or dynamically built based on a VAL server request with explicitly sent event details.

[0079] In 5.3, subscription request Based on the interest event information in the message, if applicable, the NRM server will: subscription request Subscribe to UE monitoring events (LOSS_OF_CONNECTIVITY, COMMUNICATION_FAILURE, etc.) for a set of UEs (VALUE) in

[0080] In 5.4, subscription request Based on the interest event information in the message, if applicable, the NRM server may: subscription request Subscribe to UE analytics events (such as ABNORMAL_BEHAVIOUR) for a set of UEs (VAL UE) in

[0081] 6 is a sequence diagram illustrating an exemplary monitoring event notification procedure according to another embodiment of the present disclosure, where it is assumed that the VAL server has subscribed to the NRM server using the monitoring event subscription procedure as shown in FIG.

[0082] In 6.1, the NRM Server receives VALUE related monitoring event notifications from the 3GPP® Core Network as specified in 3GPP® TS 23.502.

[0083] Alternatively, in 6.2, the NRM Server receives a VALUE related analysis event notification from the 3GPP® Core Network as specified in 3GPP® TS23.288.

[0084] In 6.3, the NRM server notifies the VAL server about events related to the UE in the notification monitoring event message. When multiple events are notified, the NRM server can aggregate the notifications and send them to the VAL server.

[0085] Corresponding to the above-described method 300, a VAL server is provided. FIG. 7 is a block diagram of a VAL server 700 according to an embodiment of the present disclosure.

[0086] The VAL server 700 operates to execute the method 300 as described above in relation to FIG. 3. The VAL server 700 includes a transmission unit 710 configured to send monitoring events subscription request to the NRM server. The monitoring events subscription request include a list of the IDs of one or more VAL users or VAL UEs for which event monitoring is requested, or a VAL group ID of a group of one or more VAL users or VAL UEs for which event monitoring is requested, and a monitoring profile ID corresponding to a list of one or more events to be monitored, or event details indicating a list of one or more events to be monitored. The VAL server 700 further includes a reception unit 720 configured to receive, as a response to the monitoring event subscription request from the NRM server, a monitoring event subscription response

[0087] According to one embodiment, when the monitoring event subscription request includes event details, the monitoring event subscription response may include a monitoring profile ID corresponding to a list of one or more events to be monitored.

[0088] According to one embodiment, the monitoring event subscription request may further include a VAL service ID that identifies a VAL service related to event monitoring.

[0089] According to one embodiment, the monitoring event subscription requestIt may further include one or more enabling conditions for at least one of one or more events to be monitored.

[0090] According to one embodiment, the one or more enabling conditions may include one or more temporal and / or spatial conditions for at least one event to be valid.

[0091] According to one embodiment, each of the one or more events to be monitored may include a monitoring event or an analysis event.

[0092] According to an embodiment, the receiving unit 720 may be further configured to receive from the NRM server a notification of at least one of the one or more events to be monitored.

[0093] The transmitting unit 710 and the receiving unit 720 may be implemented by one or more of a pure hardware solution, or a combination of software and hardware, such as a processor or a microprocessor, appropriate software and memory for storing the software, a programmable logic device (PLD), or other electronic components or processing circuits configured to perform the operations described above and shown, for example, in FIG. 3.

[0094] Corresponding to the method 400 described above, an NRM server is provided. FIG. 8 is a block diagram of an NRM server 800 according to an embodiment of the present disclosure.

[0095] The NRM server 800 operates to execute the method 400 as described above in connection with FIG. 4. The NRM server 800 includes a receiving unit 810 configured to receive monitoring events subscription request from the VAL server. The monitoring events subscription requestIt includes a list of IDs of one or more VAL users or VAL UEs for which event monitoring is requested, or a VAL group ID of one or more VAL users or VAL UEs groups for which event monitoring is requested, and a monitoring profile ID corresponding to a list of one or more events to be monitored, or event details indicating a list of one or more events to be monitored. The NRM server 800 monitors events subscription request In response to, it further includes a transmission unit 820 configured to send the monitoring event subscription response to the VAL server.

[0096] According to one embodiment, the NRM server 800 may further include a determination unit configured to determine a monitoring profile ID corresponding to a list of one or more events to be monitored based on the correspondence or mapping between the monitoring profile ID and the event details when the monitoring event subscription request includes event details. The monitoring event Subscription Response may include the determined monitoring profile ID.

[0097] According to one embodiment, the NRM server 800 may further include a determination unit configured to determine event details indicating a list of one or more events to be monitored based on the correspondence or mapping between the monitoring profile ID and the event details when the monitoring event Subscription Request includes a monitoring profile ID.

[0098] According to one embodiment, the correspondence or mapping may be pre-configured by the O&M entity, or may be created based on one or more previous monitoring events Subscription Request accompanied by event details.

[0099] According to one embodiment, each of the one or more events to be monitored may include a monitoring event or an analysis event.

[0100] According to one embodiment, the transmitting unit 820 may be further configured to send a request for subscription to at least one of one or more events to be monitored for one or more VAL users or VAL UEs to a core network node. The receiving unit 810 may be further configured to receive a notification of at least one event from the core network node. The transmitting unit 820 may be further configured to notify the VAL server of at least one event.

[0101] According to one embodiment, the monitoring event Subscription Request may further include a VAL service ID that identifies a VAL service associated with at least one of one or more events to be monitored.

[0102] According to one embodiment, the NRM server 800 may further include a determination unit configured to determine event-specific information regarding the VAL service based on the VAL service ID.

[0103] According to one embodiment, the event-specific information may be determined based on a correspondence or mapping between the VAL service ID and the event-specific information, and the correspondence or mapping is pre-configured by the O&M entity.

[0104] According to one embodiment, the determined event-specific information can complement the event-specific information in the event details.

[0105] According to one embodiment, the event-specific information may include QoS requirements for at least one event.

[0106] According to one embodiment, the transmitting unit 820 may be further configured to send a request for subscription to at least one event for one or more VAL users or VAL UEs to a core network node, where the request includes event-specific information. The receiving unit 810 may be further configured to receive a notification of at least one event from the core network node. The transmitting unit 820 may be further configured to notify the VAL server about at least one event.

[0107] According to one embodiment, a monitoring event Subscription Request may further include one or more valid conditions for at least one of one or more events to be monitored.

[0108] According to one embodiment, one or more valid conditions may include one or more temporal and / or spatial conditions for at least one event to be valid.

[0109] According to one embodiment, the transmitting unit 820 may be further configured to send a request for subscription to at least one event for one or more VAL users or VAL UEs to a core network node, where the request includes one or more valid conditions. The receiving unit 810 may be further configured to receive a notification of at least one event from the core network node. The transmitting unit 820 may be further configured to notify the VAL server about at least one event.

[0110] According to an embodiment, the sending unit 820 may be further configured to send a request for subscription to the at least one event to a core network node. The receiving unit 810 may be further configured to receive a notification of the at least one event from the core network node. The sending unit 820 may be further configured to notify the VAL server about the at least one event only when the at least one event is valid according to one or more validity conditions.

[0111] The transmitter 810 and receiver 820 may be implemented as a pure hardware solution or as a combination of software and hardware, for example by one or more of a processor or microprocessor, appropriate software and memory for storing the software, and a programmable logic device (PLD) or other electronic components or processing circuitry configured to perform the operations described above and shown, for example, in FIG. 4 .

[0112] FIG. 9 illustrates another embodiment of the present disclosure. Form of the network node 900 by Block Diagram It is.

[0113] The network node 900 includes a communication interface 910 , a processor 920 , and a memory 930 .

[0114] The memory 930 may include instructions executable by the processor 920 such that the network node 900, when implementing a VAL server, is operable to perform the procedural operations described above in relation to Figure 3. Specifically, the memory 930 may include instructions executable by the processor 920 such that the network node 900, when implementing a VAL server, is operable to send a monitoring event subscription request to the NRM server. Subscription Requestincludes a list of IDs of one or more VAL users or VAL UEs for which event monitoring is requested, or a VAL group ID of one or more VAL users or VAL UEs groups for which event monitoring is requested, a monitoring profile ID corresponding to a list of one or more events to be monitored, or event details indicating a list of one or more events to be monitored. The memory 930 can further include instructions executable by the processor 920, whereby the network node 900, when implementing the VAL server, receives from the NRM server, as a response to a monitoring event subscription request, a monitoring event Subscription Response and is operable to receive it.

[0115] According to one embodiment, when the monitoring event Subscription Request includes event details, the monitoring event Subscription Response may include a monitoring profile ID corresponding to a list of one or more events to be monitored.

[0116] According to one embodiment, the monitoring event Subscription Request may further include a VAL service ID identifying a VAL service related to event monitoring.

[0117] According to one embodiment, the monitoring event Subscription Request may further include one or more enabling conditions for at least one of the one or more events to be monitored.

[0118] According to one embodiment, the one or more enabling conditions may include one or more temporal and / or spatial conditions for at least one event to be valid.

[0119] According to one embodiment, each of the one or more events to be monitored may include a monitoring event or an analysis event.

[0120] According to one embodiment, the memory 930 can further include instructions executable by the processor 920, whereby the network node 900 is operable to receive, from the NRM server, a notification of at least one of one or more events to be monitored when implementing the VAL server.

[0121] Alternatively, the memory 930 can include instructions executable by the processor 920, whereby the network node 900 is operable to perform, when implementing the NRM server, for example, the operations of the procedure described above in connection with FIG. 4. In particular, the memory 930 can include instructions executable by the processor 920, whereby the network node 900 is operable to receive, from the VAL server, a monitoring event subscription request when implementing the NRM server. Monitoring events Subscription Request include a list of IDs of one or more VAL users or VAL UEs for which event monitoring is requested, or a VAL group ID of one or more VAL users or VAL UE groups for which event monitoring is requested, and a monitoring profile ID corresponding to a list of one or more events to be monitored, or event details indicating a list of one or more events to be monitored. The memory 930 can further include instructions executable by the processor 920, whereby the network node 900 is operable to send a monitoring event subscription response to the VAL server in response to a monitoring event subscription request when implementing the NRM server.

[0122] According to one embodiment, the memory 930 can further include instructions executable by the processor 920, whereby the network node 900, when implementing the NRM server, monitoring events SubscriptionWhen the request includes event details, it operates to determine a monitoring profile ID corresponding to a list of one or more events to be monitored, based on the correspondence or mapping between the monitoring profile ID and the event details. Monitoring event Subscription Response may include the determined monitoring profile ID.

[0123] According to one embodiment, the memory 930 can further include instructions executable by the processor 920, whereby the network node 900, when implementing an NRM server, monitoring event Subscription When the request includes a monitoring profile ID, it operates to determine event details indicating a list of one or more events to be monitored, based on the correspondence or mapping between the monitoring profile ID and the event details.

[0124] According to one embodiment, the correspondence or mapping may be preconfigured by an O&M entity, or may be created based on one or more previous monitoring events with event details Subscription Request thereof.

[0125] According to one embodiment, each of the one or more events to be monitored may include a monitoring event or an analysis event.

[0126] According to one embodiment, the memory 930 can further include instructions executable by the processor 920, whereby the network node 900, when implementing an NRM server, sends a request for subscription to at least one of the one or more events to be monitored for one or more VAL users or VAL UEs to a core network node, receives a notification of at least one event from the core network node, and notifies the VAL server of at least one event.

[0127] According to one embodiment, monitoring event Subscription Requestmay further include a VAL service ID that identifies a VAL service associated with at least one of the one or more events to be monitored.

[0128] According to one embodiment, the memory 930 may further include instructions executable by the processor 920, whereby the network node 900, when implementing an NRM server, is operable to determine event-specific information regarding the VAL service based on the VAL service ID.

[0129] According to one embodiment, the event-specific information may be determined based on a correspondence or mapping between the VAL service ID and the event-specific information, where the correspondence or mapping is pre-configured by an O&M entity.

[0130] According to one embodiment, the determined event-specific information may complement the event-specific information in the event details.

[0131] According to one embodiment, the event-specific information may include QoS requirements for at least one event.

[0132] According to one embodiment, the memory 930 may further include instructions executable by the processor 920, whereby the network node 900, when implementing an NRM server, is operable to send a request to a core network node for a subscription to at least one event for one or more VAL users or VAL UEs, the request including event-specific information, receive notification of the at least one event from the core network node, and notify the VAL server about the at least one event.

[0133] According to one embodiment, the monitored event Subscription Request may further include one or more enabling conditions for at least one of the one or more events to be monitored.

[0134] According to one embodiment, the one or more validity conditions may include one or more temporal and / or spatial conditions for the at least one event to be valid.

[0135] According to one embodiment, the memory 930 may further include instructions executable by the processor 920, whereby the network node 900, when implementing an NRM server, is operable to send a request to a core network node for a subscription to at least one event for one or more VAL users or VAL UEs, the request including one or more validity conditions, receive notification of the at least one event from the core network node, and notify the VAL server about the at least one event.

[0136] According to one embodiment, the memory 930 may further include instructions executable by the processor 920, whereby the network node 900, when implementing an NRM server, operates to send a request for subscription to at least one event to a core network node, receive notification of the at least one event from the core network node, and notify the VAL server about the at least one event only when the at least one event is valid according to one or more validity conditions.

[0137] The present disclosure also provides at least one computer program product in the form of a non-volatile or volatile memory, e.g., a non-transitory computer-readable storage medium, an Electrically Erasable Programmable Read-Only Memory (EEPROM), a flash memory, and a hard drive. The computer program product has a computer program. The computer program includes code / computer-readable instructions that, when executed by the processor 920, cause the network node 900 to perform the procedural operations described above in relation to Figure 3 when implementing a VAL server, or to perform the procedural operations described above in relation to Figure 4 when implementing an NRM server.

[0138] The computer program product may be configured as computer program code structured in computer program modules, which essentially perform the operations of the flows shown in FIG.

[0139] A processor may be a single CPU (Central Processing Unit), but may also be two or more p The processor may comprise a processing unit. For example, the processor may include a general-purpose microprocessor, an instruction set processor, and / or an associated chipset, and / or a special-purpose microprocessor such as an application-specific integrated circuit (ASIC). The processor may also comprise on-board memory for cache purposes. The computer program may be carried by a computer program product connected to the processor. The computer program product may include a non-transitory computer-readable storage medium on which the computer program is stored. For example, the computer program product may be a flash memory, a random access memory (RAM), a read-only memory (ROM), or an EEPROM, and the above computer program modules may be distributed in different computer program products in the form of memories according to different embodiments.

[0140] This disclosure has been described above with reference to its embodiments. It should be understood by those skilled in the art that various modifications, alternatives, and additions can be made without departing from the spirit and scope of this disclosure. Therefore, the scope of this disclosure is not limited to the specific embodiments described above, but is defined only by the appended claims.

Claims

1. A method (300) in a Virtual Application Layer (VAL) server, comprising: sending a monitoring event subscription request to a Network Resource Management (NRM) server (310), the monitoring event subscription request including: a list of identifiers (IDs) of one or more VAL users or VAL user equipment (UE) for which event monitoring is requested, or a VAL group ID of a group of one or more VAL users or VAL UEs for which event monitoring is requested; a monitoring profile ID corresponding to a list of one or more events to be monitored, or event details indicating a list of one or more events to be monitored; a VAL service ID identifying a VAL service associated with at least one of the one or more events to be monitored; one or more validity conditions for at least one of the one or more events to be monitored, wherein the one or more validity conditions include one or more temporal and / or spatial conditions for the at least one event to be valid; receiving, as a response to the monitoring event subscription request, a monitoring event subscription response from the NRM server (320); and wherein when the monitoring event subscription request includes the event details, the monitoring event subscription response includes a monitoring profile ID corresponding to the list of the one or more events to be monitored.

2. The method (300) according to claim 1, wherein each of the one or more events to be monitored includes a monitoring event or an analysis event.

3. The method (300) according to claim 1, further comprising: receiving, from the NRM server, a notification of at least one of the one or more events to be monitored. and

4. A method (400) in a Network Resource Management (NRM) server, comprising: receiving a monitoring event subscription request from a Virtual Application Layer (VAL) server (410), the monitoring event subscription request including: a list of identifiers (IDs) of one or more VAL users or VAL user equipment (UE) for which event monitoring is requested, or a VAL group ID of one or more groups of VAL users or VAL UEs for which event monitoring is requested; a monitoring profile ID corresponding to a list of one or more events to be monitored, or event details indicating a list of one or more events to be monitored; a VAL service ID identifying a VAL service associated with at least one of the one or more events to be monitored; one or more validity conditions for at least one of the one or more events to be monitored, wherein the one or more validity conditions include one or more temporal and / or spatial conditions for the at least one event to be valid; sending a monitoring event subscription response to the VAL server in response to the monitoring event subscription request (420); and The method further comprises, if the monitoring event subscription request includes the event details: determining a monitoring profile ID corresponding to the list of one or more events to be monitored based on a correspondence or mapping between monitoring profile IDs and event details; wherein the monitoring event subscription response includes the determined monitoring profile ID.

5. 5. The method (400) of claim 4, wherein the correspondence or mapping is pre-configured by an operations and maintenance (O&M) entity or is created based on one or more past monitoring event subscription requests with event details.

6. 5. The method (400) of claim 4, wherein each of the one or more events to be monitored comprises a monitoring event or an analysis event.

7. 5. The method (400) of claim 4, further comprising: sending a request to a core network node for a subscription to at least one of the one or more events to be monitored for the one or more VAL users or VAL UEs; Receiving a notification of the at least one event from the core network node; Notifying the VAL server about the at least one event; A method comprising the above.

8. The method (400) according to claim 4, further comprising: Determining event-specific information about the VAL service based on the VAL service ID; A method comprising the above.

9. The method (400) according to claim 8, wherein the event-specific information is determined based on a correspondence or mapping between the VAL service ID and the event-specific information, and the correspondence or mapping is pre-configured by an O&M entity.

10. The method (400) according to claim 8, wherein the determined event-specific information complements the event-specific information in the event details.

11. The method (400) according to claim 8, wherein the event-specific information includes service quality (QoS) requirements for the at least one event.

12. The method (400) according to claim 8, further comprising: Sending a request for subscription to the at least one event for the one or more VAL users or VAL UEs to the core network node, the request including the event-specific information; Receiving a notification of the at least one event from the core network node; Notifying the VAL server about the at least one event; A method comprising the above.

13. The method (400) according to claim 4, further comprising: Sending a request for subscription to the at least one event for the one or more VAL users or VAL UEs to the core network node, the request including the one or more valid conditions; Receiving a notification of the at least one event from the core network node; Notifying the VAL server about the at least one event; A method comprising the above.

14. The method (400) according to claim 4, further comprising: Sending a request for subscription to the at least one event to the core network node; Receiving a notification of the at least one event from the core network node; Notifying the VAL server about the at least one event only if the at least one event is valid according to the one or more validity conditions; A method having the above.

15. The method (400) according to claim 7, wherein the notifying further includes, when a plurality of events are to be notified, notifying the VAL server of an aggregated event. A method including this.

16. A method (400) in a Network Resource Management (NRM) server, Receiving (410) a monitoring event subscription request from a Virtual Application Layer (VAL) server, wherein the monitoring event subscription request includes: A list of identifiers (IDs) of one or more VAL users or VAL user devices (UEs) for which event monitoring is requested, or a VAL group ID of a group of one or more VAL users or VAL UEs for which event monitoring is requested; A monitoring profile ID corresponding to a list of one or more events to be monitored, or event details indicating a list of one or more events to be monitored; A VAL service ID identifying a VAL service associated with at least one of the one or more events to be monitored; One or more validity conditions for at least one of the one or more events to be monitored, wherein the one or more validity conditions include one or more temporal and / or spatial conditions for the at least one event to be valid; Sending (420) a monitoring event subscription response to the VAL server in response to the monitoring event subscription request; Having the above, The method further includes, when the monitoring event subscription request includes the monitoring profile ID, Determining event details indicating the list of the one or more events to be monitored based on a correspondence or mapping between the monitoring profile ID and the event details; A method having the above.

17. 1. A network node (900) comprising a communications interface (910), a processor (920) and a memory (930), said memory (930) comprising instructions executable by said processor (920), whereby said network node (900) operates to perform the method of any one of claims 1 to 3 when implementing a Vertical Application Layer (VAL) server.

18. 17. A network node (900) comprising a communications interface (910), a processor (920) and a memory (930), said memory (930) comprising instructions executable by said processor (920), whereby said network node (900) operates to perform the method of any one of claims 4 to 16 when implementing a network resource management (NRM) server.

19. 10. A computer-readable storage medium having stored thereon computer-readable instructions which, when executed by a processor of a network node, configure the network node to perform the method of any one of claims 1 to 3 when implementing a Vertical Application Layer (VAL) server.

20. 17. A computer readable storage medium having stored thereon computer readable instructions which, when executed by a processor of a network node, configure the network node to perform the method of any one of claims 4 to 16 when implementing a Network Resource Management (NRM) server.

Images