WO2015117417A1 - Procédé, serveur et système de personnalisation de notification d'événement - Google Patents

Procédé, serveur et système de personnalisation de notification d'événement Download PDF

Info

Publication number
WO2015117417A1
WO2015117417A1 PCT/CN2014/089509 CN2014089509W WO2015117417A1 WO 2015117417 A1 WO2015117417 A1 WO 2015117417A1 CN 2014089509 W CN2014089509 W CN 2014089509W WO 2015117417 A1 WO2015117417 A1 WO 2015117417A1
Authority
WO
WIPO (PCT)
Prior art keywords
time
event notification
client
server
session
Prior art date
Application number
PCT/CN2014/089509
Other languages
English (en)
Chinese (zh)
Inventor
戴娴娴
冯冲
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2015117417A1 publication Critical patent/WO2015117417A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications

Definitions

  • the present invention relates to network alarm technology, and more particularly to event notification.
  • the Network Configuration Protocol (NETCONF) is a configuration protocol that implements hierarchical management and provides mechanisms for configuring, querying, and event notification of network element devices. It uses the Extensible Markup Language (XML) to express all configuration query data and protocol messages.
  • XML Extensible Markup Language
  • the NETCONF hierarchy is depicted in Figure 1, with the alert notification location at the operational layer.
  • RFC 5277 defines the NETCONF event notification mechanism. Both the client and the server need to have the urn:ietf:params:netconf:capability:notification:1.0 capability, and this capability is reflected in the capability exchange.
  • the Hello packet when the server-side capability is exchanged is
  • the client needs to subscribe to the event notification to the server. If the subscription is successful, the server will record the subscription information of the session in the subscription list, and the session will no longer process the RPC request. When there is an event When born, the server sends an event notification to the client based on the recorded subscription message. When the session is terminated, the event is not in the subscription scope, event subscription changes, etc., the server will no longer send event notifications to the client.
  • a combination of optional parameters ⁇ stream>, ⁇ filter>, ⁇ startTime>, ⁇ stopTime> can be used to provide limited, single alarm filtering to meet the needs of simple scenarios.
  • NETCONF is connection-oriented, the number of terminals is limited, after the subscription event notification is successful, the subscription rule does not allow modification, the session will be occupied, only the event notification is processed, the RPC request is no longer processed, and the terminal resource is also a kind. waste.
  • the embodiment of the invention provides a method, a server and a system for customizing event notification, which solves the defects that the existing subscription technology cannot be applied to a large and complex network environment and a complex scenario, and solves the problem between the management server and the client.
  • the client is causing a waste of resources.
  • an embodiment of the present invention provides a method for customizing event notification, which is applied to a server.
  • the method includes: establishing a session with a client, and receiving, by the session, a custom filtering rule for a subscription event notification from a client, The client is specified in the custom filtering rule
  • the required event notification should meet the conditions; the historical event notification stored in the server and the event notification generated by the server are filtered according to the custom filtering rule, and an event notification that satisfies the condition is obtained; and the event notification that satisfies the condition is sent to the Said client.
  • the custom filter rule includes a specified event notification name, a time period, a date segment, an event level, and a custom note.
  • the historical event notification stored in the server and the event notification currently generated by the server are filtered according to the custom filtering rule, and the event notification that meets the condition is obtained: the time when the custom filtering rule is to be received.
  • the point is used as the subscription time; according to the specified start time and the subscription time in the custom filtering rule, a time range is determined, and the event notification in the time range is used as the event notification that satisfies the condition.
  • determining a time range includes: rule one, when there is no specified start time, the default of the time range The start time is the subscription time; rule 2, when the specified start time is not later than the subscription time, determining the time range according to the intersection of the time of the historical event notification buffered by the server and the specified start time Rule 3, when the specified start time is later than the subscription time, the time range starts from the specified start time; rule four, when the end time is not specified in the custom filter rule, the session The event notification will be processed until the session is terminated.
  • the method further includes: when the specified start time is later than the subscription time, from the subscription time to the specified start time, the session established with the client normally processes the general protocol request; When there is a specified end time in the custom filter rule, after the specified end time, the session begins to process the general protocol request normally.
  • the method further includes: sending an event notification start message to the client before sending the event notification to the client; and sending the event notification end message to the client after the event notification is sent to the client.
  • setting a time period and a date range in the custom filtering rule includes:
  • Extending the original start time parameter and the end time parameter specifying a future date and time period in the extended defined start time parameter and the end time parameter, and adding optional parameters for recording the piece of the date and time period The specified date or the specified time interval.
  • a server for custom event notification comprising: a session management unit, configured to establish a session with a client, and receive, through the session, a custom filtering rule for a subscription event notification from a client, where the custom filtering rule specifies a client The event notification that the required event notification should be satisfied; the notification management unit is configured to filter the historical event notification stored in the server and the event notification currently generated by the server according to the custom filtering rule, and obtain an event notification that satisfies the condition; An event notification that satisfies the condition is sent to the client.
  • the server further includes: an event center unit, configured to generate an event notification when an event occurs, and send the event notification to the notification management unit.
  • the notification management unit includes: a time range screening module, configured to set a time point of receiving the custom filtering rule as a subscription time; according to the specified start time in the custom filtering rule and the The subscription time determines a time range, and the event notification within the time range is used as the event notification that satisfies the condition.
  • a time range screening module configured to set a time point of receiving the custom filtering rule as a subscription time; according to the specified start time in the custom filtering rule and the The subscription time determines a time range, and the event notification within the time range is used as the event notification that satisfies the condition.
  • the time range screening module includes: a rule execution module, configured to execute rule one, when there is no specified start time, the default start time of the time range is the subscription time; rule two, When the specified start time is not later than the subscription time, determining the time range according to the intersection of the time of the historical event notification of the server cache and the specified start time; rule three, when the specified start time is later than the subscription In time, the time range is from the specified start time; rule four, when no end time is specified in the custom filter rule, the session will process the event notification until the session is terminated.
  • a rule execution module configured to execute rule one, when there is no specified start time, the default start time of the time range is the subscription time
  • rule two When the specified start time is not later than the subscription time, determining the time range according to the intersection of the time of the historical event notification of the server cache and the specified start time
  • rule three when the specified start time is later than the subscription In time, the time range is from the specified start time
  • rule four when no end time is specified in the custom filter
  • the server further includes: a protocol processing unit, configured to: when the specified start time is later than the subscription time, from the subscription time to the specified start time, the session is normally processed by the client. Request; when there is a specified end time in the custom filter rule, after the specified end time, the session begins to process the general protocol request normally.
  • a protocol processing unit configured to: when the specified start time is later than the subscription time, from the subscription time to the specified start time, the session is normally processed by the client. Request; when there is a specified end time in the custom filter rule, after the specified end time, the session begins to process the general protocol request normally.
  • a system for customizing event notifications comprising a server and a client; the client is configured to establish a session with the server, and send a custom filtering rule of the subscription event notification to the server through the session, where the custom filtering rule specifies the client
  • the server needs to notify the condition that the event notification should be satisfied;
  • the server includes: a session management unit, configured to establish a session with the client, and receive a custom filtering rule of the subscription event notification from the client through the session;
  • the notification management unit is set to According to the custom filtering rule, the historical event notification stored in the server and the current generated by the server The event notification is filtered to obtain an event notification that satisfies the condition; the session management unit is further configured to send an event notification that satisfies the condition to the client.
  • the embodiment of the invention further provides a computer program and a carrier thereof, the computer program comprising program instructions, when the program instruction is executed by the server, the server is enabled to perform the method for custom event notification.
  • the client determines the custom filtering rule and the specified starting time, and the event notification sent by the server to the client must comply with the custom filtering rule and the specified starting time, and provides the client with the A flexible subscription mechanism, and the session between the managed and the terminal ends in a timely manner, without wasting server and client resources to maintain unnecessary sessions.
  • Figure 1 is a schematic diagram showing the hierarchical structure of a network configuration protocol
  • FIG. 2 is a schematic flowchart of a method for customizing event notification according to an embodiment of the present invention
  • FIG. 3 is a message interaction diagram of a customized event notification in different scenarios based on a network configuration protocol according to an embodiment of the present invention
  • FIG. 4 is another message interaction diagram of a customized event notification in different scenarios based on a network configuration protocol according to an embodiment of the present invention
  • FIG. 5 is a schematic diagram of a process for a client to customize event notification to a server according to an embodiment of the present invention.
  • An embodiment of the present invention provides a method for customizing event notification, which is applied to a server. As shown in FIG. 2, the method includes:
  • Step 21 Establish a session with the client, and receive, by the session, a custom filtering rule for a subscription event notification from the client, where the custom filtering rule specifies a condition that the event notification required by the client should be met;
  • Step 22 Filter the historical event notification stored in the server and the event notification currently generated by the server according to the custom filtering rule, and obtain an event notification that meets the condition;
  • step 23 an event notification that satisfies the condition is sent to the client.
  • the client determines the custom filtering rule and the specified start time.
  • the event notification sent by the server to the client must conform to the custom filtering rule and the specified start time, providing a flexible subscription mechanism for the client.
  • the client records the client-defined filtering rule (called: custom filtering rule) in the option in the subscription event notification request, and the server receives the subscription event notification request from the client through the session, and records the subscription event notification request.
  • the option information is a filtering rule that sends an event notification to the client through a session with the client.
  • custom filter rules include a specified event notification name, time period, date segment, event level, and custom notes. Custom filter rules include, but are not limited to, these items or a combination of options for those items.
  • the historical event notification stored in the server and the event notification currently generated by the server are filtered according to the custom filtering rule, and the event notification that meets the condition is obtained:
  • the time point when the custom filtering rule is received is used as the subscription time
  • determining a time range according to the specified start time and the subscription time in the custom filtering rule includes:
  • Rule 2 when the specified start time is not later than the subscription time, determining the time range according to the intersection of the time of the historical event notification buffered by the server and the specified start time;
  • the event notification start message ⁇ notificationBegin> is sent to the client, and the historical event time and the specified start time are recorded according to the local cache. Set, send a historical event notification to the client that matches the session event notification filtering rule.
  • the historical event notification end message ⁇ replayComplete> is sent to the client.
  • the time range is determined according to the intersection of the time of the historical event notification buffered by the server and the specified start time.
  • the client and the server exchange capability through the Hello packet, and the client sends a subscription request to the server.
  • the server sends an event notification start message ⁇ notificationBegin> to the client, and sends the event corresponding to the session.
  • the event notification of the notification filtering rule; after the completion of the sending, the event notification end message ⁇ notification:replayComplete> is sent to the client; after that, the session can start to process the RPC request normally.
  • the server-managed session with the terminal ends in a timely manner without wasting server and client resources to maintain unnecessary sessions.
  • the method further includes:
  • the session established with the client normally processes a general protocol (RPC) request from the subscription time to the specified start time;
  • RPC general protocol
  • the session begins to process the general protocol request normally. If the end time is specified, after the specified end time is reached, the event notification end message ⁇ notificationComplete> is sent to the client through the session, after which the session begins to process the general protocol request normally.
  • the specified start time is later than the subscription time, the time range is from the specified start time, and the client and the server exchange capability through the Hello message, and the subscription time reaches the specified start time.
  • the session normally processes the RPC request.
  • the server processes the current operation, and the server sends an event notification start message ⁇ notificationBegin> to the client, and sends an event notification that conforms to the session event notification filtering rule; Finish After the transmission, the event notification end message ⁇ notificationComplete> is sent to the client; the session then begins to process the general protocol request normally.
  • the method further includes:
  • the event notification end message is sent to the client.
  • An embodiment of the present invention provides a server for custom event notification, including:
  • a session management unit configured to establish a session with the client, and receive, by the session, a custom filtering rule for a subscription event notification from the client, where the custom filtering rule specifies a condition that the event notification required by the client should be met;
  • the notification management unit is configured to filter the historical event notification stored in the server and the event notification currently generated by the server according to the custom filtering rule, and obtain an event notification that satisfies the condition;
  • the session management unit is further configured to send an event notification that satisfies the condition to the client.
  • the method further includes: an event center unit configured to generate an event notification of a type corresponding to the event as needed when an event occurs in the system, and send the event notification to the notification management unit.
  • the notification management unit comprises:
  • a time range screening module configured to use a time point of receiving the custom filtering rule as a subscription time
  • the time range screening module includes:
  • the method further includes:
  • a protocol processing unit configured to: when the specified start time is later than the subscription time, from the subscription time to the specified start time, the session established with the client normally processes the general protocol request;
  • the session begins to process the general protocol request normally.
  • the session between the client and the server is established by using the existing technology to establish a secure session.
  • the process of customizing the event notification to the server by using the custom filtering rule includes:
  • Steps 501-505 describe the flow of the server processing the subscription event notification request.
  • Step 501 The client sends a subscription event notification request (referred to as a subscription request) to the session management unit of the server, where the subscription request carries a custom filtering rule, where the custom filtering rule includes but is not limited to the event name, the specific time period/date Combinations of options such as segments, event levels, and customizations.
  • startTime must be earlier than currentTime
  • the event notification model based on the network configuration protocol NETCONF is supplementally defined.
  • the flexibility of the YANG language description can be customized to customize a variety of personalized rules to meet the needs of different scenarios.
  • the end time parameter ⁇ stopTime> is extended. Definition, specifying a future date and time period in the start time parameter and end time parameter after the extension definition, and adding an optional parameter ⁇ customization> to record a specified time interval (daily) or a specified day in a date, wherein The designated day is used to provide several methods, such as daily, working day, and day of the week.
  • scenario 1 the user pays attention to the event notification that occurs during the working day from Monday to Friday, and the event notification during the working day can be customized on the client.
  • the user pays attention to the event notification that occurs in the specified time interval every day, and can customize the event notification in the specified time interval on the client.
  • the user pays attention to the event notification that occurs in the specified date segment, and the event notification of the specified date segment can be customized on the client.
  • Step 502 The session management unit writes the received subscription request into the to-be-processed data queue of the notification management unit.
  • Step 503 the notification management unit processes the subscription request, and after the subscription is successful, adds the custom filtering rule to the preset subscription list.
  • Step 504 the notification management unit sends a response message to the session management unit.
  • Step 505 The session management unit sends a response message that meets the NETCONF message request to the client.
  • Step 506 - Step 507 describes the process of sending an internal event to notify the session start event after the subscription is successful.
  • the NETCONF-based event start message model is defined.
  • Step 506 the notification management unit records the subscription information of the session according to the subscription list, and starts the time polling as scheduled.
  • Step 507 the notification management unit sends an internal event start message to the session management unit.
  • step 508 the session management unit sends an event notification start message ⁇ notificationBegin> to the client.
  • a historical event notification conforming to the session event notification filtering rule is sent to the client according to the intersection of the historical event time recorded by the server local cache and the specified start time.
  • Steps 509 - 512 describe the flow of historical events for the normal service.
  • step 509 the information center unit transmits the historical event notification to the notification management unit.
  • step 510 the notification management unit performs filtering according to the filtering rule.
  • Step 511 the notification management unit sends an event notification to the session management unit.
  • Step 512 The session management unit sends an event notification that conforms to the NETCONF message rule to the client.
  • the notification management unit is notified to the session.
  • the unit sends a historical event end message.
  • Step 513 The notification management unit sends an internal historical event end message to the session management unit according to the filtering rule of the session.
  • step 514 the session management unit sends a historical event notification end message ⁇ replayComplete> to the client.
  • Steps 515 - 518 describe the flow of real-time events for normal services, similar to the process of processing historical event notifications.
  • step 515 the information center unit delivers the real-time event notification to the notification management unit.
  • step 516 the notification management unit performs filtering according to the filtering rule.
  • Step 517 the notification management unit sends the filtered event notification to the session management unit.
  • Step 518 The session management unit sends an event notification that conforms to the NETCONF message rule to the client.
  • the session management unit sends an event notification end message ⁇ notificationComplete> to the client when the specified end time is reached.
  • Steps 519 - 421 inform the management unit to send an internal event end message to the session management unit, the process of which is similar to the process of steps 506-508 describing the notification of the session start event.
  • Step 519 the notification management unit records the subscription information of the session according to the subscription list, such as specifying the end time polling.
  • Step 520 The notification management unit sends an internal event notification end message to the session management unit.
  • step 521 the session management unit sends an event notification end message ⁇ notificationComplete> to the client.
  • the system based on NETCONF custom event notification includes: a client supporting NETCONF, which can be called a NETCONF client, and a server supporting NETCONF, which can be called a NETCONF server.
  • Embodiments of the present invention provide a system for custom event notification, including a server and a client.
  • the client set to establish a session with the server, to send a subscription to the server through the session Custom filtering rules for notifications, which specify the conditions that the event notifications required by the client should be met;
  • the server includes:
  • a session management unit configured to establish a session with the client, and receive a custom filtering rule of the subscription event notification from the client through the session;
  • the notification management unit is configured to filter the historical event notification stored in the server and the event notification currently generated by the server according to the custom filtering rule, and obtain an event notification that satisfies the condition;
  • the session management unit is further configured to send an event notification that satisfies the condition to the client.
  • the client includes: a NETCONF client, configured to subscribe to an event notification to the NETCONF server, and receive an event notification sent by the NETCONF server;
  • the server includes: a NETCONF server, configured to cache historical events and generate event notifications when an event occurs in the system, and convert the event notification into a format recognizable by the NETCONF client, and send the format to the NETCONF client;
  • the NETCONF server includes: session management Unit, notification management unit, and event center unit.
  • the session management unit configured to process the message with the NETCONF client, includes: receiving a subscription request from the NETCONF client carrying the subscription notification type, sending the subscription request to the notification management unit, and receiving an event notification from the notification management unit, notifying the event Send to the NETCONF client;
  • a notification management unit configured to add a subscription request of the session management unit to the pre-saved subscription list, return a response message of the subscription success or failure; receive a historical or real-time event notification from the event center unit, and find a matching rule in the subscription list
  • the NETCONF client sends an event notification to the session management unit.
  • the event center unit is configured to generate an event notification of a type corresponding to the event as needed when an event occurs in the system, and send the event notification to the notification management unit.
  • the advantage of adopting this scheme is that the client determines the custom filtering rule and the specified starting time, and the event notification sent by the server to the client must comply with the custom filtering rule and the specified starting time, providing flexibility for the client. Subscription mechanism and its managed session with the terminal Ending at the right time, without wasting server and client resources to maintain unnecessary sessions.
  • all or part of the steps of the above embodiments may also be implemented by using an integrated circuit. These steps may be separately fabricated into individual integrated circuit modules, or multiple modules or steps may be fabricated into a single integrated circuit module. achieve. Thus, the invention is not limited to any specific combination of hardware and software.
  • the devices/function modules/functional units in the above embodiments may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.
  • each device/function module/functional unit in the above embodiment When each device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium.
  • the above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.
  • the client determines the custom filtering rule and the specified start time, and the event notification sent by the server to the client must meet the custom filtering rule and the specified start time, providing flexibility for the client.
  • the subscription mechanism saves resources on the server and client.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)

Abstract

L'invention concerne un procédé, un serveur et un système permettant de personnaliser une notification d'événement. Le procédé est appliqué au serveur, et consiste : à établir une session avec un client, et par l'intermédiaire de la session, recevoir en provenance du client une règle de filtrage personnalisée pour s'abonner à une notification d'événement, les conditions qui devraient être satisfaites par la notification d'événement demandée par le client étant spécifiées dans la règle de filtrage personnalisée ; conformément à la règle de filtrage personnalisée, filtrer des notifications d'événement historiques stockées dans un serveur et des notifications d'événement générées par le serveur actuellement, de manière à obtenir une notification d'événement qui satisfait les conditions ; et à envoyer la notification d'événement qui satisfait les conditions au client. Le client détermine la règle de filtrage définie par l'utilisateur et l'instant de début désigné, et la notification d'événement envoyée au client par le serveur doit se conformer à la règle de filtrage définie par l'utilisateur et à l'instant de début désigné, de manière à fournir un mécanisme d'abonnement flexible pour le client.
PCT/CN2014/089509 2014-08-19 2014-10-24 Procédé, serveur et système de personnalisation de notification d'événement WO2015117417A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410411417.7A CN105471604A (zh) 2014-08-19 2014-08-19 一种定制事件通知的方法、服务器和***
CN201410411417.7 2014-08-19

Publications (1)

Publication Number Publication Date
WO2015117417A1 true WO2015117417A1 (fr) 2015-08-13

Family

ID=53777234

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/089509 WO2015117417A1 (fr) 2014-08-19 2014-10-24 Procédé, serveur et système de personnalisation de notification d'événement

Country Status (2)

Country Link
CN (1) CN105471604A (fr)
WO (1) WO2015117417A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021052289A1 (fr) * 2019-09-16 2021-03-25 京东方科技集团股份有限公司 Procédé de notification d'événement, système, dispositif de serveur et support de stockage informatique
CN113079029A (zh) * 2020-01-03 2021-07-06 华为技术有限公司 配置信息订阅方法及装置
WO2022133871A1 (fr) 2020-12-24 2022-06-30 Huawei Technologies Co., Ltd. Appareil et procédés pour une signalisation de commande de liaison descendante dans des réseaux sans fil

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113159910A (zh) * 2016-07-29 2021-07-23 京东方科技集团股份有限公司 进行通知的方法、装置和***
US12028430B2 (en) 2018-11-28 2024-07-02 Beijing Boe Technology Development Co., Ltd. Event notification method, server device, apparatus and computer storage medium
CN111245875B (zh) * 2018-11-28 2022-03-04 京东方科技集团股份有限公司 事件通知方法、设备、装置和计算机存储介质
CN112787970B (zh) * 2019-11-01 2024-04-16 华为技术有限公司 用于订阅事件流的方法和装置
CN112199256A (zh) * 2020-10-16 2021-01-08 济南浪潮数据技术有限公司 一种部署事件监控方法、装置及设备
CN112541101B (zh) * 2020-12-11 2023-04-21 武汉旷视金智科技有限公司 订阅数据的推送方法、装置、电子设备及计算机存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101110822A (zh) * 2007-07-06 2008-01-23 华为技术有限公司 基于网络配置协议的事件通知发送方法、***及设备
CN101577865A (zh) * 2008-05-06 2009-11-11 双扬科技股份有限公司 通知因特网服务事件的方法
CN101604268A (zh) * 2009-07-13 2009-12-16 浪潮电子信息产业股份有限公司 一种监控目录变化事件过滤方法

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005151229A (ja) * 2003-11-17 2005-06-09 Nippon Telegr & Teleph Corp <Ntt> 映像流通ネットワークシステムの端末および映像流通方法
CN101860453A (zh) * 2010-06-10 2010-10-13 华为技术有限公司 事件通知的方法、装置和网络***

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101110822A (zh) * 2007-07-06 2008-01-23 华为技术有限公司 基于网络配置协议的事件通知发送方法、***及设备
CN101577865A (zh) * 2008-05-06 2009-11-11 双扬科技股份有限公司 通知因特网服务事件的方法
CN101604268A (zh) * 2009-07-13 2009-12-16 浪潮电子信息产业股份有限公司 一种监控目录变化事件过滤方法

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021052289A1 (fr) * 2019-09-16 2021-03-25 京东方科技集团股份有限公司 Procédé de notification d'événement, système, dispositif de serveur et support de stockage informatique
US11909839B2 (en) 2019-09-16 2024-02-20 Beijing Boe Technology Development Co., Ltd. Event notification method, system, server device, and computer storage medium
CN113079029A (zh) * 2020-01-03 2021-07-06 华为技术有限公司 配置信息订阅方法及装置
EP4064616A4 (fr) * 2020-01-03 2023-01-18 Huawei Technologies Co., Ltd. Procédé et dispositif de souscription d'informations de configuration
CN113079029B (zh) * 2020-01-03 2024-01-05 华为技术有限公司 配置信息订阅方法及装置
US11888688B2 (en) 2020-01-03 2024-01-30 Huawei Technologies Co., Ltd. Configuration information subscription method and apparatus
WO2022133871A1 (fr) 2020-12-24 2022-06-30 Huawei Technologies Co., Ltd. Appareil et procédés pour une signalisation de commande de liaison descendante dans des réseaux sans fil

Also Published As

Publication number Publication date
CN105471604A (zh) 2016-04-06

Similar Documents

Publication Publication Date Title
WO2015117417A1 (fr) Procédé, serveur et système de personnalisation de notification d&#39;événement
US10904739B2 (en) Network data collection method from network function device for network data analytic function
US11425583B2 (en) Network data collection method from application function device for network data analytic function
US9553831B2 (en) Adaptive publish/subscribe system
CN112789842B (zh) 用于在电信网络中支持事件监测的订阅和报告的服务的方法以及相关网络功能
JP5391276B2 (ja) インテリジェント移動体デバイス管理クライアント
CN101365118B (zh) 一种基于计算机网络的视频监控***
US10904303B2 (en) Control message from streaming source to facilitate scaling
CN101365119B (zh) 用于网络视频监控***所使用的录像负载均衡方法
US12015724B2 (en) Devices and methods for analytics exposure to application functions in 5G networks
US20060248182A1 (en) Formatted and/or tunable QoS data publication, subscription, and/or distribution including dynamic network formation
US20060248181A1 (en) Formatted and/or tunable QOS data publication, subscription, and/or distribution servers and clients
US9172765B2 (en) Polling-based secure network message notification system and method with performance enhancing features
WO2007048306A1 (fr) Méthode procurant des informations de présence et appareil correspondant
CN101360129B (zh) 网络视频监控***手机短信发送方法
JP2008519477A5 (fr)
EP2047380A1 (fr) Système et procédé de gestion de profil de préférences utilisateur
CN102255935A (zh) 云服务消费方法、云服务消息包、云服务中介及云***
US10609534B2 (en) Feed service engine
US20220070071A1 (en) Data handler
US8891524B2 (en) Method and apparatus of automatically providing registration information
CN115185705A (zh) 一种消息通知方法、装置、介质及设备
US20080208982A1 (en) Method and system for providing status information relating to a relation between a plurality of participants
EP3525400B1 (fr) Procédé et système de gestion de service de réseau
US8499035B2 (en) Methods, systems and computer readable media for providing session initiation protocol (SIP) event watcher entity information in a communications network

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14881503

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14881503

Country of ref document: EP

Kind code of ref document: A1