WO2021082832A1 - 用于订阅事件流的方法和装置 - Google Patents

用于订阅事件流的方法和装置 Download PDF

Info

Publication number
WO2021082832A1
WO2021082832A1 PCT/CN2020/117813 CN2020117813W WO2021082832A1 WO 2021082832 A1 WO2021082832 A1 WO 2021082832A1 CN 2020117813 W CN2020117813 W CN 2020117813W WO 2021082832 A1 WO2021082832 A1 WO 2021082832A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
event streams
identifier
stream
event
Prior art date
Application number
PCT/CN2020/117813
Other languages
English (en)
French (fr)
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 WO2021082832A1 publication Critical patent/WO2021082832A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1859—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast adapted to provide push services, e.g. data channels
    • 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/02—Standardisation; Integration
    • H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
    • 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
    • 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/14—Network analysis or design
    • H04L41/145—Network analysis or design involving simulating, designing, planning or modelling of a network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/06—Generation of reports
    • H04L43/065—Generation of reports related to network devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/06—Message adaptation to terminal or network requirements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/214—Monitoring or handling of messages using selective forwarding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/303—Terminal profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/562—Brokering proxy services

Definitions

  • This application relates to the field of communications, and in particular to a method and device for subscribing to event streams.
  • a device running a network management protocol server obtains the state parameters of an event stream corresponding to a certain service requirement according to a preset period.
  • the device sends an event message to the controller running the network management protocol client, and the event message includes the state parameter of the event stream.
  • This business requirement can correspond to multiple event streams, such as CPU utilization, port status, etc. After the status of multiple event streams corresponding to the business requirement changes, the device sends multiple event messages to the controller. This will cause excessive communication overhead between the device and the controller, and the controller may not respond to event messages in a timely manner.
  • the embodiment of the present application provides a method and device for subscribing to an event stream, which can save network resources and improve response speed.
  • a method for subscribing to an event stream includes: a first device generates a first message for subscribing to an event stream, the first message includes a group identifier, and the group identifier is associated with multiple Corresponding to each event stream; the first device sends the first message to the second device to obtain data of the multiple event streams corresponding to the group identifier.
  • the first device may send a group identifier to the second device so that the second device can report data of multiple event streams corresponding to the group identifier according to the group identifier, saving network resources and improving response speed.
  • the method further includes: the first device receives the second message sent by the second device, and the The second message includes a subscription identifier, and the subscription identifier is used to identify a subscription generated based on the multiple event streams.
  • the first device can learn, according to the subscription identifier, that the subsequently received data is for multiple event streams under which subscription.
  • the method further includes: the first device receives a third message sent by the second device, and the The third message includes the subscription identifier and data of at least one event stream among the plurality of event streams.
  • the third message further includes the group identification.
  • the first device can directly learn the multiple event streams corresponding to the data in the third message according to the group identifier in the third message.
  • the method further includes: the first device obtains a policy according to the data of the at least one event stream, The policy is used to instruct the second device to perform an action corresponding to the at least one event stream; the first device sends the policy to the second device.
  • the second device can execute actions according to the strategy, improving processing efficiency.
  • the method before the first device sends the first message to the second device, the method further includes: the first device receives the capability identifier sent by the second device, and the capability The identifier is used to identify that the second device supports subscribing to multiple event streams.
  • the network configuration protocol NETCONF is used to communicate between the first device and the second device, and the capability identifier may be expressed as:
  • the first device and the second device communicate with the presentation layer state transition configuration protocol RESTCONF, and the capability identifier may be expressed as:
  • the method before the first device sends the first message to the second device, the method further includes: the first device sends a corresponding relationship to the second device, and the corresponding relationship Including the group identifier and the plurality of event streams. In this way, the subsequent first device can directly issue the group identifier to realize the subscription to multiple event streams on the second device, simplifying operations.
  • a method for subscribing to an event stream includes: a second device receives a first message for subscribing to an event stream sent by a first device, the first message includes a group identifier, and The group identifier corresponds to multiple event streams; the second device generates subscriptions corresponding to the multiple event streams according to the first message.
  • the second device can generate subscriptions corresponding to multiple event streams according to the group identifier, which can save network resources.
  • the method further includes: the second device obtains a subscription identifier, and the subscription identifier is used to identify a subscription based on the multiple event streams. Subscription generated by the event stream; the second device sends a second message to the first device, and the second message includes the subscription identifier.
  • the method further includes: the second device obtains data of at least one event stream among the multiple event streams The second device generates a third message according to the data of the at least one event stream, and the third message includes the subscription identifier and the data of the at least one event stream; the second device sends the data to the first A device sends the third message.
  • the acquiring, by the second device, the data of at least one event stream among the multiple event streams includes: the second device determines the corresponding group identifier according to the group identifier. Multiple event streams; the second device periodically obtains data of one or more event streams in the multiple event streams, or the second device obtains data from one or more event streams in the multiple event streams Obtain the data of the one or more event streams after the state changes.
  • the third message further includes the group identification.
  • the method before the second device receives the first message sent by the first device for subscribing to the event stream, the method further includes: the second device sends a capability identifier to the first device The capability identifier is used to identify that the second device supports subscribing to multiple event streams.
  • the network configuration protocol NETCONF is used to communicate between the second device and the first device, and the capability identifier may be expressed as:
  • the second device and the first device communicate using the presentation layer state transition configuration protocol RESTCONF, and the capability identifier may be expressed as:
  • the method further includes: the second device receives a policy sent by the first device, and the policy is used to indicate The second device executes an action corresponding to the at least one event stream; the second device executes the action according to the policy.
  • the method before the second device receives the first message sent by the first device for subscribing to the event stream, the method further includes: the second device receives the corresponding message sent by the first device A relationship, and the corresponding relationship includes the group identifier and the multiple event streams.
  • an apparatus for subscribing to an event stream is provided, the apparatus is set in a first device, and the apparatus includes a function that can implement the above-mentioned first aspect or any one of the possible designs of the first aspect. Module.
  • a device for subscribing to event streams is provided, the device is set in a second device, and the device includes a function that can implement the second aspect or any one of the possible designs of the second aspect.
  • a computer-readable storage medium includes instructions that, when run on a computer, cause the computer to execute the first aspect or any one of the first aspects described above. Design the described method for subscribing to the event stream.
  • a computer-readable storage medium includes instructions that, when run on a computer, cause the computer to execute the second aspect or any one of the possibilities of the second aspect. Design the described method for subscribing to the event stream.
  • a computer program product containing instructions which when running on a computer, causes the computer to execute the above-mentioned first aspect or any one of the possible designs of the first aspect for subscribing to the event stream Methods.
  • a computer program product containing instructions which when running on a computer, causes the computer to execute the second aspect or any one of the possible designs of the second aspect for subscribing to the event stream Methods.
  • a device for subscribing to an event stream includes: a processor, a memory, a bus, and a communication interface;
  • the bus is connected, and when the device is running, the processor executes the computer-executable instructions stored in the memory, so that the device executes the first aspect or any one of the possible designs of the first aspect.
  • the method used to subscribe to the event stream may be the first device mentioned in the first aspect or any possible design of the first aspect.
  • a device for subscribing to an event stream includes: a processor, a memory, a bus, and a communication interface;
  • the bus connection when the device is running, the processor executes the computer-executable instructions stored in the memory, so that the device executes the second aspect or any one of the possible designs of the second aspect The method used to subscribe to the event stream.
  • the device may be the second device mentioned in the above second aspect or any possible design of the second aspect.
  • An eleventh aspect provides a system for subscribing to an event stream.
  • the system includes the device provided in the third aspect or the ninth aspect, and the device provided in the fourth or tenth aspect.
  • Figure 1 is a schematic diagram of a network scenario provided by an embodiment of the application.
  • FIG. 2 is a schematic flowchart of a method for subscribing to an event stream provided in Embodiment 1 of this application.
  • FIG. 3 is a schematic flowchart of a method for subscribing to an event stream provided in the second embodiment of the application.
  • Fig. 4 is a schematic structural diagram of an apparatus for subscribing to an event stream provided by an embodiment of the application.
  • Fig. 5 is a schematic structural diagram of an apparatus for subscribing to an event stream provided by an embodiment of the application.
  • Fig. 6 is a schematic structural diagram of an apparatus for subscribing to an event stream provided by an embodiment of the application.
  • Fig. 7 is a schematic structural diagram of an apparatus for subscribing to an event stream provided by an embodiment of the application.
  • the embodiment of the present application provides a method for subscribing to event streams.
  • the first device can subscribe to multiple event streams of the second device once.
  • the second device may report data of one or more event streams required by the second device to the first device according to this subscription.
  • the first device generates a first message for subscribing to an event stream, the first message includes a group identifier, and the group identifier corresponds to a plurality of event streams; the first device sends a message to the second device The first message is sent to obtain data of multiple event streams corresponding to the group identifier.
  • the second device After receiving the first message, the second device generates subscriptions corresponding to the multiple event streams according to the group identifier included in the first message.
  • FIG. 1 is a schematic diagram of a network scenario provided by an embodiment of the application.
  • the control device 101 can perform subscription settings for the device 102 and the device 103.
  • the control device 101 is a client running a network management protocol.
  • Both the device 102 and the device 103 are servers running a network management protocol.
  • the communication protocol adopted between the control device 101 and the device 102 is a network management protocol, which may specifically be a network configuration protocol (Network Configuration Protocol, NETCONF) or a presentation layer state transfer configuration protocol (Representational State Transfer Configuration Protocol RESTCONF).
  • the communication protocol adopted between the control device 101 and the device 103 is the same as the communication protocol adopted between the control device 101 and the device 102.
  • the device 102 and the device 103 may be any network devices that support the foregoing network management protocol, such as routers, switches, servers, and so on.
  • FIG. 2 is a schematic flowchart of a method for subscribing to an event stream provided in Embodiment 1 of this application. 1 and 2, taking the interaction between the control device 101 and the device 102 as an example, the method for subscription provided in the embodiment of the present application will be described.
  • the control device 101 and the device 102 establish a session based on the network management protocol.
  • the device 102 sends a capability identifier to the control device 101, where the capability identifier is used to identify that the second device supports subscribing to multiple event streams.
  • the device 102 sends a hello message to the control device 101, where the hello message includes the capability identifier.
  • the network management protocol is NETCONF
  • the capability identifier included in the hello message may take the following forms:
  • the capability identifier included in the hello message may take the following form:
  • Netconf bulk-stream-sn capability represents the capability of a batch event stream (event stream) under NETCONF.
  • Restconf bulk-stream-sn capability represents the capability of batch event streaming under RESTCONF.
  • bulk-stream-sn: 1.0 indicates support for subscribing to bulk event streams.
  • Batch event streams can also be referred to as multiple event streams.
  • the event stream is a group of continuous events sorted by time that converge under certain circumstances, such as: system restart-related parameters, node configuration information, node status information, alarm events, time delay, etc.
  • the hello message adopts the following format:
  • the control device 101 may learn that the device 102 supports subscribing to multiple event streams.
  • the control device 101 may determine multiple event streams according to configuration or requirements.
  • the control device 101 packs multiple event streams into a group, and configures a corresponding group identifier.
  • the control device 101 obtains a corresponding relationship, and the corresponding relationship includes a group identifier and multiple event streams corresponding to the group identifier.
  • the group identifier is the index of the batch subscription model.
  • the corresponding relationship can be represented by a batch subscription model.
  • the batch subscription model is a model that uses the YANG model to subscribe to multiple event streams.
  • the control device 101 may send the corresponding relationship to the device 102.
  • the model related to the corresponding relationship in the batch subscription model can be expressed as follows:
  • module:ietf-bulk-subscription indicates that the data model is a batch subscription model.
  • group-id represents the group ID.
  • stream* represents multiple event streams.
  • the requirements on which the control device 101 packages multiple event streams may be business requirements.
  • Business requirements can correspond to multiple event streams.
  • the business requirement is business guarantee, and the event stream can be an alarm event.
  • the specific alarm events can be equipment alarms, communication alarms, processing error alarms, etc.
  • the business requirement is the business guarantee, and the event flow can also be the threshold of the business parameter, delay, QoS, etc.
  • the business requirement is fault diagnosis, and the event stream can be response time, network attack, CPU usage, etc.
  • S202 The control device 101 generates a first message, where the first message includes a group identifier.
  • control device 101 realizes the subscription to multiple event streams on the device 102 by sending the first message, so as to obtain the data of the multiple event streams corresponding to the group identifier.
  • the first message may use the following format to send the group identifier, so as to subscribe to multiple event streams corresponding to the group identifier.
  • augment/sn:subscriptions/sn:subscription/sn:target means configuration subscription.
  • augment/sn:establish-subscription/sn:input/sn:target means dynamic subscription.
  • Dynamic subscription can be implemented through remote procedure call (RPC).
  • the first message also includes a batch reporting model.
  • the batch reporting model is a model used by the device 102 to report data corresponding to multiple event streams to the control device 101.
  • the batch reporting model can take the following forms:
  • ietf-bulk-notification indicates that the data model is a batch reporting model.
  • group-id represents the group ID.
  • the first message further includes a message identifier, so that when the second message including the subscription identifier sent by the device 102 is received, the subscription identifier and the subscription identifier are determined according to the message identifier carried in the second message.
  • the group ID corresponds.
  • S203 The control device 101 sends a first message to the device 102.
  • control device 101 may use a network management protocol to send the first message to the device 102.
  • S204 The device 102 generates a second message, and the second message includes a subscription identifier.
  • the device 102 For example, the device 102 generates a subscription according to the group identifier in the first message and obtains the subscription identifier.
  • the subscription identifier may be a randomly generated identifier.
  • Subscription generation is to enable the device to report data according to the data model by issuing a configuration or invoking a configuration command.
  • the subscription identifier included in the second message generated by the device 102 may take the following form.
  • output means reply.
  • the second message further includes the message identifier.
  • the device 102 sends the message identification and the subscription identification to the control device 101, so that the control device 101 determines that the subscription identification corresponds to the group identification according to the message identification.
  • S205 The device 102 sends a second message to the control device 101.
  • the device 102 may use a network management protocol to send the second message to the control device 101.
  • S206 The device 102 generates a third message, where the third message includes the subscription identifier and data of N event streams.
  • the device 102 determines the multiple event streams subscribed to by the control device 101 according to the received correspondence in the batch subscription model and the group identifier in the first message.
  • the device 102 periodically obtains the data corresponding to the N event streams, or obtains the data when the state corresponding to the N event streams changes.
  • N is an integer greater than or equal to 1.
  • the multiple event streams corresponding to the group identifier include the N event streams.
  • the N event streams may be multiple event streams corresponding to the group identifier.
  • the device 102 generates a third message according to the subscription identifier and the data of the N event streams.
  • the third message may use the following format to report the subscription identifier and the data of the N event streams.
  • structure message represents the format of the message.
  • subscription-id represents the subscription ID.
  • the data of N event streams can be carried in notification-contents.
  • the device 102 can report data of N event streams through batch report notifications.
  • the third message further includes the group identifier, so that the controller 101 determines data related to those requirements or configurations according to the group identifier.
  • the third message may adopt the following format to carry the group identifier.
  • group-id represents the group ID.
  • message-header represents the message header.
  • ietf-bulk-notification means bulk notification.
  • augment-structure/nm:message/nm:message-header indicates that the group identifier is carried in the message header of the structure message.
  • the device 102 sends a third message to the control device 101.
  • the device 102 may use a network management protocol to send a third message to the control device 101.
  • the device 102 can obtain data of N event streams corresponding to the group ID according to the group ID sent by the control device 101.
  • the N event streams are event streams subscribed by the control device 101. Through one subscription, the data acquisition of multiple event streams is realized, which saves network resources.
  • FIG. 3 is a schematic flowchart of a method for subscribing to an event stream provided in the second embodiment of the application.
  • the device in the network scenario shown in FIG. 1 may also use the method provided in the embodiment corresponding to FIG. 3.
  • the difference between the method provided in the second embodiment and the method provided in the first embodiment lies in the content of S301 to S303.
  • S301 The control device 101 generates a strategy.
  • the control device 101 generates the strategy according to the data of the N event streams reported by the device 102, and the strategy is used to instruct 102 to perform actions corresponding to the N event streams.
  • a failure of module 1 on the device 102 leads to an alarm event 1
  • a module 2 on the device 102 calls the failed module 1 to cause an alarm event 2
  • the device Module 3 on 102 causes alarm event 3 due to calling module 2.
  • the module on the device 102 may be hardware or software, which is not limited in the embodiment of the present application.
  • the device 102 can perform statistics on the above-mentioned alarm events, and determine whether to notify the user according to the number of statistics and a preset threshold.
  • the device 102 reports the alarm event 1, the alarm event 2 and the alarm event 3 to the control device 101.
  • the control device 101 learns that the alarm event 2 and the alarm event 3 are caused by the alarm event 1 according to the alarm event 1, the alarm event 2 and the alarm event 3. .
  • the control device 101 determines that the alarm event 1 is a valid alarm, and the alarm event 2 and the alarm event 3 are invalid alarms.
  • the strategy is to confirm alarm event 1 and clear alarm event 2 and alarm event 3.
  • S302 The control device 101 sends a policy to the device 102.
  • control device 101 sends the policy to the device 102 through a network management protocol.
  • the device 102 executes corresponding actions according to the policy. Taking the aforementioned alarm event as an example, the device 102 clears the alarm event 2 and the alarm event 1, and confirms the alarm event 1. Optionally, the device 102 may further notify the user of the alarm event 1 after confirming the alarm event 1, so as to efficiently eliminate the fault.
  • control device 101 can determine a strategy according to the data of the N event streams reported by the device 102, so that the device 102 can adjust the action on the event stream, which can improve the response speed and failure processing efficiency.
  • the control device in the embodiment of the present application may include a cloud controller and an analyzer, or the control device is a cloud analyzer, or the control device is a device that integrates the functions of the cloud controller and the analyzer.
  • the messages, identifiers, data, etc. in the method provided in the embodiments of the present application can all be expressed using the data model in the YANG model.
  • Figure 4 is a schematic structural diagram of an apparatus for subscribing to event streams provided by an embodiment of the application.
  • the device 400 provided in the embodiment corresponding to FIG. 4 is described from the perspective of a logical structure.
  • the apparatus 400 provided in the embodiment corresponding to FIG. 4 may be the control device 101 in the first embodiment or the second embodiment.
  • the second device in the embodiment corresponding to FIG. 4 may be the device 102 in the first embodiment or the second embodiment.
  • the device 400 includes a generating module 401 and a first sending module 402.
  • the generating module 401 is used to generate a first message for subscribing to the event stream.
  • the first message includes a group identifier, and the group identifier corresponds to multiple event streams.
  • the first sending module 402 is configured to send the first message to a second device to obtain data of the multiple event streams corresponding to the group identifier.
  • the generating module 401 is used to support the apparatus 400 to execute step S202 in the first embodiment or the second embodiment.
  • the first sending module 402 is used to support the apparatus 400 to perform step S203 in the first embodiment or the second embodiment.
  • the device further includes a first receiving module 403.
  • the first receiving module 403 is configured to receive a second message sent by the second device, the second message includes a subscription identifier, and the subscription identifier is used to identify a subscription generated based on the multiple event streams.
  • the first receiving module 403 is used to support the apparatus 400 to execute S205 in the first embodiment or the second embodiment.
  • the device further includes: a second receiving module 404.
  • the second receiving module 404 is configured to receive a third message sent by the second device, where the third message includes the subscription identifier and data of at least one event stream among the multiple event streams.
  • the second receiving module 404 is used to support the apparatus 400 to execute S207 in the first embodiment or the second embodiment.
  • the third message further includes the group identifier.
  • the device further includes an obtaining module 405 and a second sending module 406.
  • the obtaining module 405 is configured to obtain a strategy according to the data of the at least one event stream, and the strategy is used to instruct the second device to perform an action corresponding to the at least one event stream.
  • the second sending module 406 is configured to send the policy to the second device.
  • the obtaining module 405 is used to support the apparatus 400 to execute S301 in the second embodiment.
  • the second sending module 406 is used to support the apparatus 400 to execute S302 in the second embodiment.
  • the device further includes a third receiving module 407.
  • the third receiving module 407 is configured to receive a capability identifier sent by the second device, where the capability identifier is used to identify that the second device supports subscribing to multiple event streams.
  • the third receiving module 407 is used to support the apparatus 400 to execute S201 in the first embodiment or the second embodiment.
  • the device further includes a third sending module 408.
  • the third sending module 408 is configured to send a corresponding relationship to the second device, where the corresponding relationship includes the group identifier and the multiple event streams.
  • the third sending module 408 is used to support the apparatus 400 to execute S201 in the first embodiment or the second embodiment.
  • the first receiving module 403 and the second receiving module 404 in the embodiment of the present application may be one receiving unit.
  • the first sending module 402, the second sending module 406, and the third sending module 408 may be one sending unit.
  • the first message for subscribing to the event stream generated by the generating module 401 can be that the second device that receives the first message reports the data of multiple event streams according to the subscription, which helps Save network resources.
  • Fig. 5 is a schematic structural diagram of an apparatus for subscribing to an event stream provided by an embodiment of the application.
  • the device 500 provided in the embodiment corresponding to FIG. 5 is described from the perspective of a logical structure.
  • the apparatus 500 provided in the embodiment corresponding to FIG. 5 may be the device 102 in the first embodiment or the second embodiment.
  • the first device in the embodiment corresponding to FIG. 5 may be the control device 101 in the first embodiment or the second embodiment.
  • the device 500 includes a first receiving module 501 and a first generating module 502.
  • the first receiving module 501 is configured to receive a first message for subscribing to an event stream sent by a first device, where the first message includes a group identifier, and the group identifier corresponds to multiple event streams.
  • the first generating module 502 is configured to generate subscriptions corresponding to the multiple event streams according to the first message.
  • the first receiving module 501 is used to support the device 500 to execute S203 in the first embodiment or the second embodiment.
  • the first generating module 502 is used to support the apparatus 500 to execute S204 in the first embodiment or the second embodiment.
  • the device further includes a first obtaining module 503 and a first sending module 504.
  • the first obtaining module 503 is configured to obtain a subscription identifier, and the subscription identifier is used to identify a subscription generated based on the multiple event streams.
  • the first sending module 504 is configured to send a second message to the first device, and the second message includes the subscription identifier.
  • the first obtaining module 503 is used to support the apparatus 500 to execute S204 in the first embodiment or the second embodiment.
  • the first sending module 504 is used to support the apparatus 500 to execute S205 in the first embodiment or the second embodiment.
  • the device further includes a second obtaining module 505, a second generating module 506, and a second sending module 507.
  • the second obtaining module 505 is configured to obtain data of at least one event stream among the multiple event streams.
  • the second generating module 506 is configured to generate a third message according to the data of the at least one event stream, and the third message includes the subscription identifier and the data of the at least one event stream.
  • the second sending module 507 is configured to send the third message to the first device.
  • the second obtaining module 505 and the second generating module 506 are used to support the apparatus 500 to execute S206 in the first embodiment or the second embodiment.
  • the second sending module 507 is used to support the apparatus 500 to execute S207 in the first embodiment or the second embodiment.
  • the third message further includes the group identifier.
  • the second obtaining module 505 is specifically configured to: determine the multiple event streams corresponding to the group identifier according to the group identifier; periodically obtain one or more events in the multiple event streams Or obtain the data of one or more event streams after the state of one or more event streams in the multiple event streams changes.
  • the device further includes a third sending module 508.
  • the third sending module 508 is configured to send a capability identifier to the first device, where the capability identifier is used to identify that the second device supports subscribing to multiple event streams.
  • the third sending module 508 is used to support the apparatus 500 to execute S201 in the first embodiment or the second embodiment.
  • the device further includes a second receiving module 509 and a processing module 510.
  • the second receiving module 509 is configured to receive a policy sent by the first device, and the policy is used to instruct the second device to perform an action corresponding to the at least one event stream.
  • the processing module 510 is configured to execute the action according to the strategy.
  • the second receiving module 509 is used to support the apparatus 500 to execute S302 in the second embodiment.
  • the processing module 510 is used to support the apparatus 500 to execute S303 in the second embodiment.
  • the device further includes a third receiving module 511.
  • the third receiving module 511 is configured to receive the corresponding relationship sent by the first device, where the corresponding relationship includes the group identifier and the multiple event streams.
  • the third receiving module 511 is used to support the apparatus 500 to execute S201 in the first embodiment or the second embodiment.
  • the first receiving module 501, the second receiving module 509, and the third receiving module 511 in the embodiment of the present application may be one receiving unit.
  • the first sending module 504, the second sending module 507, and the third sending module 508 may be one sending unit.
  • the first obtaining module 503 and the second obtaining module 505 may be one obtaining unit.
  • the first generation module 502 generates subscriptions corresponding to multiple event streams according to the group identifier in the first message, so that the data of multiple event streams can be subsequently reported at once, which helps to save network resources. .
  • Fig. 6 is a schematic structural diagram of an apparatus for subscribing to an event stream provided by an embodiment of the application.
  • the apparatus 600 provided in the embodiment corresponding to FIG. 6 may be the apparatus 400 provided in the embodiment corresponding to FIG. 4.
  • the apparatus 600 provided in the embodiment corresponding to FIG. 6 is described from the perspective of the hardware structure.
  • the apparatus 600 provided in the embodiment corresponding to FIG. 6 can implement the function of the control device 101 in the first embodiment or the second embodiment.
  • the apparatus 600 provided in the embodiment corresponding to FIG. 6 includes a processor 601, a memory 602, a communication bus 604, and a communication interface 603.
  • the processor 601, the memory 602, and the communication interface 603 are connected through a communication bus 604.
  • the memory 602 is used to store programs.
  • the processor 601 executes the method executed by the control device 101 in the first embodiment or the second embodiment according to the executable instructions included in the program read from the memory 602.
  • the processor 601 can negotiate and communicate with the second device, that is, the device 102 in the first embodiment or the second embodiment, through the communication interface 603.
  • the communication interface 603 is used to support the device 600 to execute S201, S203, S205, and S207 in the first embodiment or the second embodiment.
  • the communication interface 603 is also used to support the device 600 to execute S302 in the second embodiment.
  • the processor 601 is configured to support the apparatus 600 to execute S202 in the first embodiment or the second embodiment.
  • the processor 601 is further configured to support the apparatus 600 to execute S301 in the second embodiment.
  • the memory 602 is also used to cache the group identification, subscription identification, and data of N event streams in the first embodiment or the second embodiment.
  • Fig. 7 is a schematic structural diagram of an apparatus for subscribing to an event stream provided by an embodiment of the application.
  • the apparatus 700 provided in the embodiment corresponding to FIG. 7 may be the apparatus 500 provided in the embodiment corresponding to FIG. 5.
  • the apparatus 700 provided in the embodiment corresponding to FIG. 7 is described from the perspective of the hardware structure.
  • the apparatus 700 provided in the embodiment corresponding to FIG. 7 can implement the function of the device 102 in the first embodiment or the second embodiment.
  • the apparatus 700 provided in the embodiment corresponding to FIG. 7 includes a processor 701, a memory 702, a communication bus 704, and a communication interface 703.
  • the processor 701, the memory 702, and the communication interface 703 are connected through a communication bus 704.
  • the memory 702 is used to store programs.
  • the processor 701 executes the method executed by the device 102 in the first embodiment or the second embodiment according to the executable instructions included in the program read from the memory 702.
  • the processor 701 can negotiate and communicate with the first device, that is, the control device 101 in the first embodiment or the second embodiment, through the communication interface 703.
  • the communication interface 703 is used to support the apparatus 700 to execute S201, S203, S205, and S207 in the first embodiment or the second embodiment.
  • the communication interface 703 is also used to support the apparatus 700 to execute S302 in the second embodiment.
  • the processor 601 is configured to support the apparatus 700 to execute S204 and S206 in the first embodiment or the second embodiment.
  • the processor 601 is further configured to support the apparatus 700 to execute S303 in the second embodiment.
  • the memory 602 is also used to cache the group identification, subscription identification, data and policies of the N event streams in the first or second embodiment.
  • An embodiment of the present application provides a system for subscribing to an event stream.
  • the system includes a first device and a second device.
  • the device 400 for subscribing to an event stream or the device 600 for subscribing to an event stream may be provided in the first device.
  • the device 500 for subscribing to an event stream or the device 700 for subscribing to an event stream may be provided in the second device.
  • the first device can perform the actions performed by the control device 101 in the first embodiment or the second embodiment.
  • the second device can perform the actions performed by the device 102 in the first embodiment or the second embodiment.
  • the general-purpose processor mentioned in the embodiments of the present application may be a microprocessor or the processor may also be any conventional processor.
  • the steps of the method disclosed in the embodiments of the present invention can be directly embodied as a combination of hardware and software modules in the processor.
  • the code for realizing the above functions can be stored in a computer-readable medium.
  • Computer readable media include computer storage media.
  • the storage medium may be any available medium that can be accessed by a computer.
  • the computer-readable medium can be random access memory (full name in English, random-access memory, abbreviated as RAM), read-only memory (full name in English, read-only memory, abbreviated as ROM in English) , Electrically erasable programmable read-only memory (English full name is electrically erasable programmable read-only memory, English abbreviation is EEPROM), CD-ROM (English full name is compact disc read-only memory, English abbreviation is CD-ROM) or other Optical disk storage, magnetic disk storage media or other magnetic storage devices, or any other media that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer.
  • RAM random access memory
  • read-only memory full name in English, read-only memory, abbreviated as ROM in English
  • EEPROM Electrically erasable programmable read-only memory
  • CD-ROM English full name is compact disc read-only memory, English abbreviation is CD-ROM
  • the computer-readable medium can be a compact disc (the full English name is compact disc, the English abbreviation is CD), a laser disc, a digital video disc (the full English name is digital video disc, and the English abbreviation is DVD), a floppy disk or a Blu-ray disc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例公开了一种用于订阅事件流的方法，所述方法包括：第一设备生成用于订阅事件流的第一消息，所述第一消息包括组标识，所述组标识与多个事件流对应；所述第一设备向第二设备发送所述第一消息，以获得与所述组标识对应的所述多个事件流的数据。

Description

用于订阅事件流的方法和装置
本申请要求于2019年11月1日提交中国国家知识产权局、申请号为CN201911060982.2、发明名称为“用于订阅事件流的方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种用于订阅事件流的方法和装置。
背景技术
目前，运行有网络管理协议服务端的设备根据预设周期，获取某一业务需求对应的事件流(event stream)的状态参数。该设备向运行有网络管理协议客户端的控制器发送事件消息，该事件消息包括该事件流的状态参数。该业务需求可对应多个事件流，比如CPU利用率、端口状态等。该业务需求对应的多个事件流的状态发生改变后，该设备会向该控制器发送多个事件消息。这会造成设备与控制器之间的通信开销过大，控制器可能会出现无法及时响应事件消息的问题。
发明内容
本申请实施例提供了一种用于订阅事件流的方法和装置，能够节省网络资源和提高响应速度。
第一方面，提供了一种用于订阅事件流的方法，所述方法包括：第一设备生成用于订阅事件流的第一消息，所述第一消息包括组标识，所述组标识与多个事件流对应；所述第一设备向第二设备发送所述第一消息，以获得与所述组标识对应的所述多个事件流的数据。
上述方法中，第一设备可通过发送组标识给第二设备，以便第二设备可根据组标识上报与所述组标识对应的多个事件流的数据，节省网络资源，提高响应速度。
在一种可能的设计中，所述第一设备向第二设备发送所述第一消息之后，所述方法还包括：所述第一设备接收所述第二设备发送的第二消息，所述第二消息包括订阅标识，所述订阅标识用于标识基于所述多个事件流生成的订阅。这样，第一设备可根据订阅标识，获知后续接收到的数据是针对哪个订阅下的多个事件流。
在一种可能的设计中，所述第一设备向第二设备发送所述第一消息之后，所述方法还包括：所述第一设备接收所述第二设备发送的第三消息，所述第三消息包括所述订阅标识和所述多个事件流中至少一个事件流的数据。
在一种可能的设计中，所述第三消息还包括所述组标识。这样，第一设备可直接根据第三消息中的组标识，获知第三消息中的数据所对应的多个事件流。
在一种可能的设计中，所述第一设备接收所述第二设备发送的第三消息之后，所述方法还包括：所述第一设备根据所述至少一个事件流的数据，获得策略，所述策略用于指示所述第二设备执行对应所述至少一个事件流的动作；所述第一设备向所述第二设备发送所述策略。这样，第二设备可根据策略执行动作，提高处理效率。
在一种可能的设计中，所述第一设备向第二设备发送所述第一消息之前，所述方法还 包括：所述第一设备接收所述第二设备发送的能力标识，所述能力标识用于标识所述第二设备支持订阅多个事件流。
在一种可能的设计中，所述第一设备与所述第二设备间采用网络配置协议NETCONF通信，所述能力标识可表示为：
Netconf bulk-stream-sn capability：
    urn:ietf:params:netconf:capability:bulk-stream-sn:1.0
或者所述第一设备与所述第二设备间采用表现层状态转换配置协议RESTCONF通信，所述能力标识可表示为：
Restconf bulk-stream-sn capability：
     urn:ietf:params:restconf:capability:bulk-stream-sn:1.0。
在一种可能的设计中，所述第一设备向第二设备发送所述第一消息之前，所述方法还包括：所述第一设备向所述第二设备发送对应关系，所述对应关系包括所述组标识和所述多个事件流。这样，后续第一设备可直接下发组标识来实现对第二设备上多个事件流的订阅，简化操作。
第二方面，提供了一种用于订阅事件流的方法，所述方法包括：第二设备接收第一设备发送的用于订阅事件流的第一消息，所述第一消息包括组标识，所述组标识与多个事件流对应；所述第二设备根据所述第一消息，生成与所述多个事件流对应的订阅。
上述方法中，第二设备可根据组标识，生成与多个事件流对应的订阅，能够节省网络资源。
在一种可能的设计中，所述生成与所述多个事件流对应的订阅之后，所述方法还包括：所述第二设备获得订阅标识，所述订阅标识用于标识基于所述多个事件流生成的订阅；所述第二设备向所述第一设备发送第二消息，所述第二消息包括所述订阅标识。
在一种可能的设计中，所述第二设备向所述第一设备发送第二消息之后，所述方法还包括：所述第二设备获取所述多个事件流中至少一个事件流的数据；所述第二设备根据所述至少一个事件流的数据，生成第三消息，所述第三消息包括所述订阅标识和所述至少一个事件流的数据；所述第二设备向所述第一设备发送所述第三消息。
在一种可能的设计中，所述第二设备获取所述多个事件流中至少一个事件流的数据包括：所述第二设备根据所述组标识，确定与所述组标识对应的所述多个事件流；所述第二设备周期性获取所述多个事件流中一个或多个事件流的数据，或者所述第二设备在所述多个事件流中一个或多个事件流的状态改变后获取所述一个或多个事件流的数据。
在一种可能的设计中，所述第三消息还包括所述组标识。
在一种可能的设计中，所述第二设备接收第一设备发送的用于订阅事件流的第一消息之前，所述方法还包括：所述第二设备向所述第一设备发送能力标识，所述能力标识用于标识所述第二设备支持订阅多个事件流。
在一种可能的设计中，所述第二设备与所述第一设备间采用网络配置协议NETCONF通信，所述能力标识可表示为：
Netconf bulk-stream-sn capability：
      urn:ietf:params:netconf:capability:bulk-stream-sn:1.0
或者所述第二设备与所述第一设备间采用表现层状态转换配置协议RESTCONF通信，所述能力标识可表示为：
Restconf bulk-stream-sn capability：
     urn:ietf:params:restconf:capability:bulk-stream-sn:1.0。
在一种可能的设计中，所述生成与所述多个事件流对应的订阅之后，所述方法还包括：所述第二设备接收所述第一设备发送的策略，所述策略用于指示所述第二设备执行对应所述至少一个事件流的动作；所述第二设备根据所述策略执行所述动作。
在一种可能的设计中，所述第二设备接收第一设备发送的用于订阅事件流的第一消息之前，所述方法还包括：所述第二设备接收所述第一设备发送的对应关系，所述对应关系包括所述组标识和所述多个事件流。
第三方面，提供一种用于订阅事件流的装置，所述装置设置于第一设备，所述装置包括能够实现上述第一方面或第一方面的任一种可能的设计所对应的功能的模块。
第四方面，提供一种用于订阅事件流的装置，所述装置设置于第二设备，所述装置包括能够实现上述第二方面或第二方面的任一种可能的设计所对应的功能的模块
第五方面，提供一种计算机可读存储介质，所述计算机可读存储介质包括指令，当其在计算机上运行时，使得所述计算机执行上述第一方面或第一方面的任一种可能的设计所述的用于订阅事件流的方法。
第六方面，提供一种计算机可读存储介质，所述计算机可读存储介质包括指令，当其在计算机上运行时，使得所述计算机执行上述第二方面或第二方面的任一种可能的设计所述的用于订阅事件流的方法。
第七方面，提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得所述计算机执行上述第一方面或第一方面的任一种可能的设计所述的用于订阅事件流的方法。
第八方面，提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得所述计算机执行上述第二方面或第二方面的任一种可能的设计所述的用于订阅事件流的方法。
第九方面，提供一种用于订阅事件流的装置，所述装置包括：处理器、存储器、总线和通信接口；所述存储器用于存储计算机执行指令，所述处理器与所述存储器通过所述总线连接，当所述装置运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述装置执行上述第一方面或第一方面的任一种可能的设计所述的用于订阅事件流的方法。其中，所述装置可以是上述第一方面或第一方面的任一种可能的设计中提及的第一设备。
第十方面，提供一种用于订阅事件流的装置，所述装置包括：处理器、存储器、总线和通信接口；所述存储器用于存储计算机执行指令，所述处理器与所述存储器通过所述总线连接，当所述装置运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述装置执行上述第二方面或第二方面的任一种可能的设计所述的用于订阅事件流的方法。其中，所述装置可以是上述第二方面或第二方面的任一种可能的设计中提及的第二设备。
第十一方面，提供一种用于订阅事件流的系统，所述系统包括上述第三方面或第九方面提供的装置，以及上述第四方面或第十方面提供的装置。
附图说明
图1为本申请实施例提供的网络场景示意图。
图2为本申请实施例一提供的用于订阅事件流的方法流程示意图。
图3为本申请实施例二提供的用于订阅事件流的方法流程示意图。
图4为本申请实施例提供的用于订阅事件流的装置结构示意图。
图5为本申请实施例提供的用于订阅事件流的装置结构示意图。
图6为本申请实施例提供的用于订阅事件流的装置结构示意图。
图7为本申请实施例提供的用于订阅事件流的装置结构示意图。
具体实施方式
下面结合附图，对本发明的实施例进行描述。
本申请实施例提供了一种用于订阅事件流的方法，该方法中，第一设备能够对第二设备的多个事件流进行一次订阅。所述第二设备可根据该次订阅，向所述第一设备上报其所需的一个或多个事件流的数据。具体地，所述第一设备生成用于订阅事件流的第一消息，所述第一消息包括组标识，所述组标识与多个事件流对应；所述第一设备向所述第二设备发送所述第一消息，以获得与所述组标识对应的多个事件流的数据。第二设备接收到第一消息后，根据所述第一消息包括的所述组标识生成与所述多个事件流对应的订阅。
图1为本申请实施例提供的网络场景示意图。在图1所示的网络场景中，控制设备101能够对设备102和设备103进行订阅设置。比如：控制设备101为运行有网络管理协议的客户端。设备102和设备103均为运行有网络管理协议的服务端。控制设备101与设备102之间采用的通信协议为网络管理协议，具体可以是网络配置协议(Network Configuration Protocol，NETCONF)或表现层状态转换配置协议(Representational State Transfer Configuration Protocol RESTCONF)。控制设备101与设备103间采用的通信协议与控制设备101与设备102间采用的通信协议相同。设备102和设备103可以是任何支持上述网络管理协议的网络设备，比如路由器、交换机、服务器等。
图2为本申请实施例一提供的用于订阅事件流的方法流程示意图。现结合图1和图2，以控制设备101与设备102间的交互为例，对本申请实施例提供的用于订阅的方法进行说明。
S201，控制设备101与设备102之间进行能力协商。
举例说明，控制设备101和设备102建立基于网络管理协议的会话。设备102向控制设备101发送能力标识，所述能力标识用于标识所述第二设备支持订阅多个事件流。例如：设备102向控制设备101发送问候(hello)消息，所述hello消息包括所述能力标识。所述网络管理协议为NETCONF时，所述hello消息中包括的能力标识可采用以下形式：
Netconf bulk-stream-sn capability：
    urn:ietf:params:netconf:capability:bulk-stream-sn:1.0
所述网络管理协议为RESCONF时，所述hello消息中包括的能力标识可采用以下形式：
Restconf bulk-stream-sn capability：
       urn:ietf:params:restconf:capability:bulk-stream-sn:1.0
其中，Netconf bulk-stream-sn capability表示NETCONF下的批量事件流(event stream)的能力。Restconf bulk-stream-sn capability表示RESTCONF下的批量事件流的能力。bulk-stream-sn:1.0表示支持订阅批量事件流。批量事件流也可称为多个事件流。事件流为在某些情况下汇聚的一组连续的按时间排序的事件，例如：系统重启相关的参数、节点配 置信息、节点状态信息、告警事件、时延等。
以所述网络管理协议为NETCONF为例，hello消息采用下述格式：
<hello xmlns＝"urn:ietf:params:xml:ns:netconf:base:1.0">
<capabilities>
<capability>
urn:ietf:params:netconf:base:1.1
</capability>
<capability>
urn:ietf:params:netconf:capability:startup:1.0
</capability>
<capability>
urn:ietf:params:netconf:capability:bulk-stream-sn:1.0
</capability>
</capabilities>
<session-id>4</session-id>
</hello>
举例说明，控制设备101可在接收到设备102的能力标识之后，获知设备102支持订阅多个事件流。控制设备101可根据配置或需求，确定多个事件流。控制设备101将多个事件流打包至一个组，配置相应的组标识。控制设备101获取对应关系，所述对应关系包括组标识和与所述组标识对应的多个事件流。所述组标识为批量订阅模型的索引。所述对应关系可通过批量订阅模型来表示。批量订阅模型为采用YANG模型对多个事件流进行订阅的模型。控制设备101可向设备102发送所述对应关系。
批量订阅模型中与所述对应关系相关的模型可表示如下：
Figure PCTCN2020117813-appb-000001
其中，module:ietf-bulk-subscription表示该数据模型为批量订阅模型。group-id表示组标识。stream*表示多个事件流。
举例说明，控制设备101打包多个事件流所依据的需求可以是业务需求。业务需求可对应多个事件流。比如：业务需求是业务保证，事件流可以是告警事件。告警事件具体可以是设备告警，通讯告警，处理错误告警等。业务需求是业务保证，事件流还可以是业务参数的门限值，时延，QoS等。业务需求是故障诊断，事件流可以是响应时间，网络攻击，CPU占用率等。
S202，控制设备101生成第一消息，所述第一消息包括组标识。
举例说明，控制设备101通过发送第一消息，实现对设备102上多个事件流的订阅，以获取所述组标识对应的多个事件流的数据。
所述第一消息可采用下述格式来发送组标识，实现订阅所述组标识对应的多个事件流。
Figure PCTCN2020117813-appb-000002
Figure PCTCN2020117813-appb-000003
其中，augment/sn:subscriptions/sn:subscription/sn:target表示配置订阅。augment/sn:establish-subscription/sn:input/sn:target表示动态订阅。动态订阅可通过远程过程调用(remote procedure call，RPC)来实现。
可选地，第一消息还包括批量上报模型。所述批量上报模型为设备102向控制设备101上报与多个事件流对应的数据所采用的模型。所述批量上报模型可采用以下形式：
Figure PCTCN2020117813-appb-000004
其中，ietf-bulk-notification表示该数据模型为批量上报模型。group-id表示组标识。
可选地，所述第一消息还包括消息标识(message identifier)，以便接收设备102发送的包括订阅标识的第二消息时，根据第二消息携带的所述消息标识，确定所述订阅标识与所述组标识对应。
S203，控制设备101向设备102发送第一消息。
举例说明，控制设备101可采用网络管理协议，向设备102发送第一消息。
S204，设备102生成第二消息，第二消息包括订阅标识。
举例说明，设备102根据第一消息中的组标识，生成订阅并获得订阅标识。所述订阅标识可以是随机生成的标识。订阅生成为通过下发配置或者调用配置的命令使得设备按照数据模型上报数据。设备102所生成的第二消息中包括的订阅标识可采用下述形式。
Figure PCTCN2020117813-appb-000005
其中，output表示回复。id表示的订阅标识(subscription-id)。
可选地，所述第二消息还包括所述消息标识。设备102将所述消息标识和所述订阅标识发送给控制设备101，以便控制设备101根据所述消息标识，确定所述订阅标识与所述组标识对应。
S205，设备102向控制设备101发送第二消息。
举例说明，设备102可采用网络管理协议，向控制设备101发送第二消息。
S206，设备102生成第三消息，所述第三消息包括所述订阅标识和N个事件流的数据。
举例说明，设备102根据接收到的批量订阅模型中的对应关系和第一消息中的组标识，确定控制设备101所订阅的多个事件流。设备102周期性获得N个事件流对应的数据，或者在N个事件流对应的状态发生改变时获取其数据。N为大于或等于1的整数。所述组标识对应的多个事件流包括所述N个事件流。为了节省网络资源和提高响应速度，所述N个事件流可以为所述组标识对应的多个事件流。设备102根据所述订阅标识和所述N个事件流的数据，生成第三消息。
所述第三消息可采用下述格式上报所述订阅标识和所述N个事件流的数据。
Figure PCTCN2020117813-appb-000006
Figure PCTCN2020117813-appb-000007
其中，structure message表示消息的格式。subscription-id表示订阅标识。N个事件流的数据可携带在notification-contents中。设备102可通过批量上报通知实现上报N个事件流的数据。
可选地，所述第三消息还包括所述组标识，以便控制器101根据组标识确定是与那些需求或配置相关的数据。所述第三消息可采用下述格式来携带所述组标识。
Figure PCTCN2020117813-appb-000008
其中，group-id表示组标识。message-header表示消息头。ietf-bulk-notification表示批量上报。augment-structure/nm:message/nm:message-header表示组标识携带在structure message的消息头中。
S207，设备102向控制设备101发送第三消息。
举例说明，设备102可采用网络管理协议，向控制设备101发送第三消息。
本申请实施例一提供的方法中，设备102能够根据控制设备101发送的组标识，获取与所述组标识对应的N个事件流的数据。所述N个事件流为控制设备101订阅的事件流。通过一次订阅实现了对多个事件流的数据的获取，节省了网络资源。
实施例二
图3为本申请实施例二提供的用于订阅事件流的方法流程示意图。图1所示网络场景 中的设备也可采用图3对应的实施例提供的方法。实施例二提供的方法与实施例一提供的方法的不同之处在于S301至S303的内容。
实施例二的S201至S207的内容可参见实施例一的S201至S207的相应内容，在此不再赘述。下面结合图1和图3，对S301至S303的内容进行说明。
S301，控制设备101生成策略。
举例说明，控制设备101根据设备102上报的N个事件流的数据，生成所述策略，所述策略用于指示102执行对应所述N个事件流的动作。以控制设备101所订阅的多个事件流为故障导致的告警事件为例，设备102上的模块1故障导致告警事件1，设备102上的模块2因调用故障的模块1导致告警事件2，设备102上的模块3因调用模块2导致告警事件3。设备102上的模块可以是硬件或软件，本申请实施例对此不进行限定。设备102可对上述告警事件进行统计，并根据统计的数量和预设的阈值，确定是否通知用户。设备102上报告警事件1、告警事件2和告警事件3给控制设备101。控制设备101根据告警事件1、告警事件2和告警事件3，获知告警事件2和告警事件3是因告警事件1导致的，比如根据生成告警的时间和/或模块之间的调用关系获知上述内容。控制设备101确定告警事件1为有效告警，告警事件2和告警事件3为无效告警。所述策略为确认告警事件1，且清除告警事件2和告警事件3。
S302，控制设备101向设备102发送策略。
举例说明，控制设备101通过网络管理协议，向设备102发送所述策略。
S303，设备102根据策略执行动作。
举例说明，设备102根据策略执行相应的动作。以上述的告警事件为例，设备102清除告警事件2和告警事件1，确认告警事件1。可选地，设备102可在确认告警事件1之后，进一步通知用户告警事件1，以便高效地排除故障。
本申请实施例二提供的方法中，控制设备101可根据设备102上报的N个事件流的数据确定策略，以便设备102调整对于事件流的动作，能够提高响应速度和故障处理效率。
本申请实施例中的控制设备可以包括云控制器和分析器，或者控制设备为云分析器，或者控制设备为集成了云控制器的功能和分析器的功能的设备。
本申请实施例提供的方法中的消息、标识、数据等均可采用YANG模型中的数据模型来进行表达。
图4为本申请实施例提供的用于订阅事件流的装置结构示意图。图4对应的实施例提供的装置400是从逻辑结构的角度进行的描述。图4对应的实施例提供的装置400可以是实施例一或实施例二中的控制设备101。图4对应的实施例中的第二设备可以是第一实施例或第二实施例中的设备102。下面结合图4，对本申请实施例提供的装置结构进行说明。
所述装置400包括生成模块401和第一发送模块402。所述生成模块401用于生成用于订阅事件流的第一消息。所述第一消息包括组标识，所述组标识与多个事件流对应。所述第一发送模块402用于向第二设备发送所述第一消息，以获得与所述组标识对应的所述多个事件流的数据。所述生成模块401用于支持装置400执行实施例一或实施例二中的步骤S202。所述第一发送模块402用于支持装置400执行实施例一或实施例二中的步骤S203。
可选地，所述装置还包括第一接收模块403。所述第一接收模块403用于接收所述第二设备发送的第二消息，所述第二消息包括订阅标识，所述订阅标识用于标识基于所述多个事件流生成的订阅。所述第一接收模块403用于支持装置400执行实施例一或实施例二 中的S205。
可选地，所述装置还包括：第二接收模块404。所述第二接收模块404用于接收所述第二设备发送的第三消息，所述第三消息包括所述订阅标识和所述多个事件流中至少一个事件流的数据。所述第二接收模块404用于支持装置400执行实施例一或实施例二中的S207。可选地，所述第三消息还包括所述组标识。
可选地，所述装置还包括获得模块405和第二发送模块406。所述获得模块405用于根据所述至少一个事件流的数据，获得策略，所述策略用于指示所述第二设备执行对应所述至少一个事件流的动作。所述第二发送模块406用于向所述第二设备发送所述策略。所述获得模块405用于支持装置400执行实施例二中的S301。所述第二发送模块406用于支持装置400执行实施例二中的S302。
可选地，所述装置还包括第三接收模块407。所述第三接收模块407用于接收所述第二设备发送的能力标识，所述能力标识用于标识所述第二设备支持订阅多个事件流。所述第三接收模块407用于支持装置400执行实施例一或实施例二中的S201。
可选地，所述装置还包括第三发送模块408。所述第三发送模块408用于向所述第二设备发送对应关系，所述对应关系包括所述组标识和所述多个事件流。所述第三发送模块408用于支持装置400执行实施例一或实施例二中的S201。
本申请实施例中的第一接收模块403和第二接收模块404可以为一个接收单元。所述第一发送模块402、所述第二发送模块406和所述第三发送模块408可以为一个发送单元。
本申请实施例提供的装置中，生成模块401所生成的用于订阅事件流的第一消息，能够是的接收到第一消息的第二设备根据订阅上报多个事件流的数据，有助于节省网络资源。
图5为本申请实施例提供的用于订阅事件流的装置结构示意图。图5对应的实施例提供的装置500是从逻辑结构的角度进行的描述。图5对应的实施例提供的装置500可以是实施例一或实施例二中的设备102。图5对应的实施例中的第一设备可以是实施例一或实施例二中的控制设备101。下面结合图5，对本申请实施例提供的装置结构进行说明。
所述装置500包括第一接收模块501和第一生成模块502。所述第一接收模块501用于接收第一设备发送的用于订阅事件流的第一消息，所述第一消息包括组标识，所述组标识与多个事件流对应。所述第一生成模块502用于根据所述第一消息，生成与所述多个事件流对应的订阅。所述第一接收模块501用于支持装置500执行实施例一或实施例二中的S203。所述第一生成模块502用于支持装置500执行实施例一或实施例二中的S204。
可选地，所述装置还包括第一获得模块503和第一发送模块504。所述第一获得模块503用于获得订阅标识，所述订阅标识用于标识基于所述多个事件流生成的订阅。所述第一发送模块504用于向所述第一设备发送第二消息，所述第二消息包括所述订阅标识。所述第一获得模块503用于支持装置500执行实施例一或实施例二中的S204。所述第一发送模块504用于支持装置500执行实施例一或实施例二中的S205。
可选地，所述装置还包括第二获得模块505、第二生成模块506和第二发送模块507。所述第二获得模块505用于获取所述多个事件流中至少一个事件流的数据。所述第二生成模块506用于根据所述至少一个事件流的数据，生成第三消息，所述第三消息包括所述订阅标识和所述至少一个事件流的数据。所述第二发送模块507用于向所述第一设备发送所述第三消息。所述第二获得模块505和所述第二生成模块506用于支持装置500执行实施 例一或实施例二中的S206。所述第二发送模块507用于支持装置500执行实施例一或实施例二中的S207。可选地，所述第三消息还包括所述组标识。
举例说明，所述第二获得模块505具体用于：根据所述组标识，确定与所述组标识对应的所述多个事件流；周期性获取所述多个事件流中一个或多个事件流的数据，或者在所述多个事件流中一个或多个事件流的状态改变后获取所述一个或多个事件流的数据。
可选地，所述装置还包括第三发送模块508。所述第三发送模块508用于向所述第一设备发送能力标识，所述能力标识用于标识所述第二设备支持订阅多个事件流。所述第三发送模块508用于支持装置500执行实施例一或实施例二中的S201。
可选地，所述装置还包括第二接收模块509和处理模块510。所述第二接收模块509用于接收所述第一设备发送的策略，所述策略用于指示所述第二设备执行对应所述至少一个事件流的动作。所述处理模块510用于根据所述策略执行所述动作。所述第二接收模块509用于支持装置500执行实施例二中的S302。所述处理模块510用于支持装置500执行实施例二中的S303。
可选地，所述装置还包括第三接收模块511。所述第三接收模块511用于接收所述第一设备发送的对应关系，所述对应关系包括所述组标识和所述多个事件流。所述第三接收模块511用于支持装置500执行实施例一或实施例二中的S201。
本申请实施例中的第一接收模块501、第二接收模块509和第三接收模块511可以为一个接收单元。所述第一发送模块504、所述第二发送模块507和所述第三发送模块508可以为一个发送单元。所述第一获得模块503和所述第二获得模块505可以为一个获得单元。
本申请实施例提供的装置中，第一生成模块502根据第一消息中的组标识生成与多个事件流对应的订阅，以便后续一次性上报多个事件流的数据，有助于节省网络资源。
图6为本申请实施例提供的用于订阅事件流的装置结构示意图。图6对应的实施例提供的装置600可以是图4对应的实施例提供的装置400。图6对应的实施例提供的装置600是从硬件结构的角度进行的描述。图6对应的实施例提供的装置600可实现实施例一或实施例二中控制设备101的功能。图6对应的实施例提供的装置600包括处理器601、存储器602、通信总线604和通信接口603。所述处理器601、所述存储器602和所述通信接口603通过通信总线604连接。所述存储器602用于存储程序。所述处理器601根据从所述存储器602中读取的程序所包括的可执行指令，执行上述实施例一或实施例二中的控制设备101执行的方法。所述处理器601可通过通信接口603与第二设备，即实施例一或实施例二中的设备102，进行协商和通信。
其中，通信接口603用于支持装置600执行实施例一或实施例二中的S201、S203、S205和S207。通信接口603还用于支持装置600执行实施例二中的S302。所述处理器601用于支持装置600执行实施例一或实施例二中的S202。所述处理器601还用于支持装置600执行实施例二中的S301。所述存储器602除了用于存储程序代码和数据之外，还用于缓存实施例一或实施例二中的组标识、订阅标识和N个事件流的数据。
图7为本申请实施例提供的用于订阅事件流的装置结构示意图。图7对应的实施例提供的装置700可以是图5对应的实施例提供的装置500。图7对应的实施例提供的装置700是从硬件结构的角度进行的描述。图7对应的实施例提供的装置700可实现实施例一或实施例二中设备102的功能。图7对应的实施例提供的装置700包括处理器701、存储器702、 通信总线704和通信接口703。所述处理器701、所述存储器702和所述通信接口703通过通信总线704连接。所述存储器702用于存储程序。所述处理器701根据从所述存储器702中读取的程序所包括的可执行指令，执行上述实施例一或实施例二中的设备102执行的方法。所述处理器701可通过通信接口703与第一设备，即实施例一或实施例二中的控制设备101，进行协商和通信。
其中，通信接口703用于支持装置700执行实施例一或实施例二中的S201、S203、S205和S207。通信接口703还用于支持装置700执行实施例二中的S302。所述处理器601用于支持装置700执行实施例一或实施例二中的S204和S206。所述处理器601还用于支持装置700执行实施例二中的S303。所述存储器602除了用于存储程序代码和数据之外，还用于缓存实施例一或实施例二中的组标识、订阅标识、N个事件流的数据和策略。
本申请实施例提供了一种用于订阅事件流的系统，所述系统包括第一设备和第二设备。用于订阅事件流的装置400或用于订阅事件流的装置600可设于所述第一设备。用于订阅事件流的装置500或用于订阅事件流的装置700可设于所述第二设备。所述第一设备可执行实施例一或实施例二中控制设备101所执行的动作。所述第二设备可执行实施例一或实施例二中设备102所执行的动作。
本申请实施例中所提及的通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器。结合本发明实施例所公开的方法的步骤，可以直接体现为处理器中的硬件及软件模块组合执行完成。当使用软件实现时，可以将实现上述功能的代码存储在计算机可读介质中。计算机可读介质包括计算机存储介质。存储介质可以是计算机能够存取的任何可用介质。以此为例但不限于：计算机可读介质可以是随机存取存储器(英文全称为random-access memory，英文缩写为RAM)、只读存储器(英文全称为read-only memory，英文缩写为ROM)、电可擦可编程只读存储器(英文全称为electrically erasable programmable read-only memory，英文缩写为EEPROM)、只读光盘(英文全称为compact disc read-only memory，英文缩写为CD-ROM)或其他光盘存储、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质。计算机可读介质可以是压缩碟(英文全称为compact disc，英文缩写为CD)、激光碟、数字视频光碟(英文全称为digital video disc，英文缩写为DVD)、软盘或者蓝光碟。
本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于系统实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。

Claims (33)

  1. 一种用于订阅事件流的方法，其特征在于，所述方法包括：
    第一设备生成用于订阅事件流的第一消息，所述第一消息包括组标识，所述组标识与多个事件流对应；
    所述第一设备向第二设备发送所述第一消息，以获得与所述组标识对应的所述多个事件流的数据。
  2. 根据权利要求1所述的方法，其特征在于，所述第一设备向第二设备发送所述第一消息之后，所述方法还包括：
    所述第一设备接收所述第二设备发送的第二消息，所述第二消息包括订阅标识，所述订阅标识用于标识基于所述多个事件流生成的订阅。
  3. 根据权利要求2所述的方法，其特征在于，所述第一设备向第二设备发送所述第一消息之后，所述方法还包括：
    所述第一设备接收所述第二设备发送的第三消息，所述第三消息包括所述订阅标识和所述多个事件流中至少一个事件流的数据。
  4. 根据权利要求3所述的方法，其特征在于，所述第三消息还包括所述组标识。
  5. 根据权利要求3或4所述的方法，其特征在于，所述第一设备接收所述第二设备发送的第三消息之后，所述方法还包括：
    所述第一设备根据所述至少一个事件流的数据，获得策略，所述策略用于指示所述第二设备执行对应所述至少一个事件流的动作；
    所述第一设备向所述第二设备发送所述策略。
  6. 根据权利要求1至5任一所述的方法，其特征在于，所述第一设备向第二设备发送所述第一消息之前，所述方法还包括：
    所述第一设备接收所述第二设备发送的能力标识，所述能力标识用于标识所述第二设备支持订阅多个事件流。
  7. 根据权利要求6所述的方法，其特征在于，所述第一设备与所述第二设备间采用网络配置协议NETCONF通信，所述能力标识可表示为：
    Netconf bulk-stream-sn capability：
    urn:ietf:params:netconf:capability:bulk-stream-sn:1.0
    或者所述第一设备与所述第二设备间采用表现层状态转换配置协议RESTCONF通信，所述能力标识可表示为：
    Restconf bulk-stream-sn capability：
    urn:ietf:params:restconf:capability:bulk-stream-sn:1.0。
  8. 根据权利要求1至7任一所述的方法，其特征在于，所述第一设备向第二设备发送所述第一消息之前，所述方法还包括：
    所述第一设备向所述第二设备发送对应关系，所述对应关系包括所述组标识和所述多个事件流。
  9. 一种用于订阅事件流的方法，其特征在于，所述方法包括：
    第二设备接收第一设备发送的用于订阅事件流的第一消息，所述第一消息包括组标识，所述组标识与多个事件流对应；
    所述第二设备根据所述第一消息，生成与所述多个事件流对应的订阅。
  10. 根据权利要求9所述的方法，其特征在于，所述生成与所述多个事件流对应的订阅之后，所述方法还包括：
    所述第二设备获得订阅标识，所述订阅标识用于标识基于所述多个事件流生成的订阅；
    所述第二设备向所述第一设备发送第二消息，所述第二消息包括所述订阅标识。
  11. 根据权利要求10所述的方法，其特征在于，所述第二设备向所述第一设备发送第二消息之后，所述方法还包括：
    所述第二设备获取所述多个事件流中至少一个事件流的数据；
    所述第二设备根据所述至少一个事件流的数据，生成第三消息，所述第三消息包括所述订阅标识和所述至少一个事件流的数据；
    所述第二设备向所述第一设备发送所述第三消息。
  12. 根据权利要求11所述的方法，其特征在于，所述第二设备获取所述多个事件流中至少一个事件流的数据包括：
    所述第二设备根据所述组标识，确定与所述组标识对应的所述多个事件流；
    所述第二设备周期性获取所述多个事件流中一个或多个事件流的数据，或者所述第二设备在所述多个事件流中一个或多个事件流的状态改变后获取所述一个或多个事件流的数据。
  13. 根据权利要求11或12所述的方法，其特征在于，所述第三消息还包括所述组标识。
  14. 根据权利要求9至13任一所述的方法，其特征在于，所述第二设备接收第一设备发送的用于订阅事件流的第一消息之前，所述方法还包括：
    所述第二设备向所述第一设备发送能力标识，所述能力标识用于标识所述第二设备支持订阅多个事件流。
  15. 根据权利要求14所述的方法，其特征在于，所述第二设备与所述第一设备间采用网络配置协议NETCONF通信，所述能力标识可表示为：
    Netconf bulk-stream-sn capability：
    urn:ietf:params:netconf:capability:bulk-stream-sn:1.0
    或者所述第二设备与所述第一设备间采用表现层状态转换配置协议RESTCONF通信，所述能力标识可表示为：
    Restconf bulk-stream-sn capability：
    urn:ietf:params:restconf:capability:bulk-stream-sn:1.0。
  16. 根据权利要求11至13任一所述的方法，其特征在于，所述生成与所述多个事件流对应的订阅之后，所述方法还包括：
    所述第二设备接收所述第一设备发送的策略，所述策略用于指示所述第二设备执行对应所述至少一个事件流的动作；
    所述第二设备根据所述策略执行所述动作。
  17. 根据权利要求9至16任一所述的方法，其特征在于，所述第二设备接收第一设备发送的用于订阅事件流的第一消息之前，所述方法还包括：
    所述第二设备接收所述第一设备发送的对应关系，所述对应关系包括所述组标识和所述多个事件流。
  18. 一种用于订阅事件流的装置，其特征在于，所述装置设置于第一设备，所述装置包括：
    生成模块，用于生成用于订阅事件流的第一消息，所述第一消息包括组标识，所述组标识与多个事件流对应；
    第一发送模块，用于向第二设备发送所述第一消息，以获得与所述组标识对应的所述多个事件流的数据。
  19. 根据权利要求18所述的装置，其特征在于，所述装置还包括：
    第一接收模块，用于接收所述第二设备发送的第二消息，所述第二消息包括订阅标识，所述订阅标识用于标识基于所述多个事件流生成的订阅。
  20. 根据权利要求19所述的装置，其特征在于，所述装置还包括：
    第二接收模块，用于接收所述第二设备发送的第三消息，所述第三消息包括所述订阅标识和所述多个事件流中至少一个事件流的数据。
  21. 根据权利要求20所述的装置，其特征在于，所述第三消息还包括所述组标识。
  22. 根据权利要求20或21所述的装置，其特征在于，所述装置还包括：
    获得模块，用于根据所述至少一个事件流的数据，获得策略，所述策略用于指示所述第二设备执行对应所述至少一个事件流的动作；
    第二发送模块，用于向所述第二设备发送所述策略。
  23. 根据权利要求18至22任一所述的装置，其特征在于，所述装置还包括：
    第三接收模块，用于接收所述第二设备发送的能力标识，所述能力标识用于标识所述第二设备支持订阅多个事件流。
  24. 根据权利要求18至23任一所述的装置，其特征在于，所述装置还包括：
    第三发送模块，用于向所述第二设备发送对应关系，所述对应关系包括所述组标识和所述多个事件流。
  25. 一种用于订阅事件流的装置，其特征在于，所述装置设置于第二设备，所述装置包括：
    第一接收模块，用于接收第一设备发送的用于订阅事件流的第一消息，所述第一消息包括组标识，所述组标识与多个事件流对应；
    第一生成模块，用于根据所述第一消息，生成与所述多个事件流对应的订阅。
  26. 根据权利要求25所述的装置，其特征在于，所述装置还包括：
    第一获得模块，用于获得订阅标识，所述订阅标识用于标识基于所述多个事件流生成的订阅；
    第一发送模块，用于向所述第一设备发送第二消息，所述第二消息包括所述订阅标识。
  27. 根据权利要求26所述的装置，其特征在于，所述装置还包括：
    第二获得模块，用于获取所述多个事件流中至少一个事件流的数据；
    第二生成模块，用于根据所述至少一个事件流的数据，生成第三消息，所述第三消息包括所述订阅标识和所述至少一个事件流的数据；
    第二发送模块，用于向所述第一设备发送所述第三消息。
  28. 根据权利要求27所述的装置，其特征在于，所述第二获得模块具体用于：
    根据所述组标识，确定与所述组标识对应的所述多个事件流；
    周期性获取所述多个事件流中一个或多个事件流的数据，或者在所述多个事件流中一 个或多个事件流的状态改变后获取所述一个或多个事件流的数据。
  29. 根据权利要求27或28所述的装置，其特征在于，所述第三消息还包括所述组标识。
  30. 根据权利要求25至29任一所述的装置，其特征在于，所述装置还包括：
    第三发送模块，用于向所述第一设备发送能力标识，所述能力标识用于标识所述第二设备支持订阅多个事件流。
  31. 根据权利要求27至29任一所述的装置，其特征在于，所述装置还包括：
    第二接收模块，用于接收所述第一设备发送的策略，所述策略用于指示所述第二设备执行对应所述至少一个事件流的动作；
    处理模块，用于根据所述策略执行所述动作。
  32. 根据权利要求25至31任一所述的装置，其特征在于，所述装置还包括：
    第三接收模块，用于接收所述第一设备发送的对应关系，所述对应关系包括所述组标识和所述多个事件流。
  33. 一种计算机可读介质，包括指令，当其在计算机上执行时，使得所述计算机执行如权利要求1至17任一权利要求所述的方法。
PCT/CN2020/117813 2019-11-01 2020-09-25 用于订阅事件流的方法和装置 WO2021082832A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911060982.2 2019-11-01
CN201911060982.2A CN112787970B (zh) 2019-11-01 2019-11-01 用于订阅事件流的方法和装置

Publications (1)

Publication Number Publication Date
WO2021082832A1 true WO2021082832A1 (zh) 2021-05-06

Family

ID=75715758

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/CN2020/117813 WO2021082832A1 (zh) 2019-11-01 2020-09-25 用于订阅事件流的方法和装置
PCT/CN2020/123655 WO2021083075A1 (zh) 2019-11-01 2020-10-26 用于订阅事件流的方法和装置

Family Applications After (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/123655 WO2021083075A1 (zh) 2019-11-01 2020-10-26 用于订阅事件流的方法和装置

Country Status (4)

Country Link
US (1) US11863368B2 (zh)
EP (1) EP4044545B1 (zh)
CN (1) CN112787970B (zh)
WO (2) WO2021082832A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114301817A (zh) * 2021-12-17 2022-04-08 中电信数智科技有限公司 基于Netconf协议的设备监测阈值设置方法和系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101453355A (zh) * 2007-11-30 2009-06-10 华为技术有限公司 一种轮询方法、系统、网管站及被管设备
CN102317915A (zh) * 2009-02-16 2012-01-11 英科伦有限责任公司 分析系统的实时能力的方法
CN102402420A (zh) * 2010-10-14 2012-04-04 微软公司 解析可观察集合
US20170116089A1 (en) * 2015-10-22 2017-04-27 Oracle International Corporation Event batching, output sequencing, and log based state storage in continuous query processing
CN109997139A (zh) * 2016-09-30 2019-07-09 爱维士软件有限责任公司 利用基于散列的指纹检测恶意软件

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7254616B1 (en) * 2001-07-27 2007-08-07 Ciena Corporation Reliable communication mechanism with “at most once” delivery guarantee
CN104009865B (zh) * 2014-05-08 2017-07-25 北京百度网讯科技有限公司 网络管理方法和装置
CN105263163B (zh) * 2014-07-18 2019-01-15 中兴通讯股份有限公司 一种通知消息的发送方法、装置和系统
CN105471604A (zh) * 2014-08-19 2016-04-06 中兴通讯股份有限公司 一种定制事件通知的方法、服务器和系统
US10313455B2 (en) * 2015-08-31 2019-06-04 Ayla Networks, Inc. Data streaming service for an internet-of-things platform
US11276006B2 (en) * 2015-10-02 2022-03-15 Outlier AI, Inc. System, apparatus, and method to identify intelligence using a data processing platform
CN109981538A (zh) * 2017-12-28 2019-07-05 深圳市优必选科技有限公司 订阅事件的注册方法及系统、订阅事件的处理方法及系统
CN109996216B (zh) * 2018-01-02 2022-06-03 中国移动通信有限公司研究院 订阅请求处理方法、网络实体及能力开放平台
CN110113381B (zh) * 2019-04-09 2023-04-07 深圳前海微众银行股份有限公司 一种区块链中订阅主题的方法及装置
US11429669B2 (en) * 2019-08-06 2022-08-30 Twitter, Inc. Managing query subscription renewals in a messaging platform

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101453355A (zh) * 2007-11-30 2009-06-10 华为技术有限公司 一种轮询方法、系统、网管站及被管设备
CN102317915A (zh) * 2009-02-16 2012-01-11 英科伦有限责任公司 分析系统的实时能力的方法
CN102402420A (zh) * 2010-10-14 2012-04-04 微软公司 解析可观察集合
US20170116089A1 (en) * 2015-10-22 2017-04-27 Oracle International Corporation Event batching, output sequencing, and log based state storage in continuous query processing
CN109997139A (zh) * 2016-09-30 2019-07-09 爱维士软件有限责任公司 利用基于散列的指纹检测恶意软件

Also Published As

Publication number Publication date
WO2021083075A1 (zh) 2021-05-06
EP4044545B1 (en) 2024-02-14
EP4044545A4 (en) 2022-10-12
US20220255789A1 (en) 2022-08-11
CN112787970B (zh) 2024-04-16
CN112787970A (zh) 2021-05-11
US11863368B2 (en) 2024-01-02
EP4044545A1 (en) 2022-08-17

Similar Documents

Publication Publication Date Title
TWI397277B (zh) 統一訊息服務之系統及方法
US9356998B2 (en) Method for load balancing of requests&#39; processing of diameter servers
KR101457241B1 (ko) 네트워크에서의 완전 메시 레이트 트랜잭션
US8081610B2 (en) Modifying remote service discovery based on presence
WO2020207091A1 (zh) 一种管理客户端、设备监控系统及方法
RU2517382C2 (ru) Способ и система для синхронизации данных в сети доставки контента
EP3709664B1 (en) Stream pushing method, system and server
CN104811459A (zh) 用于消息服务的处理方法、装置及系统、消息服务系统
WO2010072081A1 (zh) 一种实现流媒体服务器大量终端接入的方法及系统
US11102319B2 (en) Method, system and server for stream-pushing
US11431781B1 (en) User-defined quality of experience (QoE) prioritizations
WO2012088954A1 (zh) 基于网络配置协议的网络配置管理方法、设备和系统
WO2022148363A1 (zh) 数据传输方法及数据传输服务器
WO2016197861A1 (zh) 远程管理方法、被管理设备、管理设备和智能电视系统
WO2011044786A1 (zh) 一种统一消息调度系统、业务消息通知方法及系统
CN102916906B (zh) 一种实现应用性能自适应的方法、装置及系统
WO2021083075A1 (zh) 用于订阅事件流的方法和装置
CN110661848B (zh) 一种基于视联网的消息推送方法、装置、设备和介质
CN111224889A (zh) 一种数据传输的方法和装置
WO2013159492A1 (zh) 信息上报与下载的方法及系统
CN111596940B (zh) 一种版本升级方法、装置、电子设备及存储介质
US8924486B2 (en) Method and system for aggregating communications
US20170142215A1 (en) Relaying mobile communications
CN111193904B (zh) 巡检控制方法、装置及可读存储介质
CN113630366A (zh) 一种物联网设备接入方法及系统

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: 20881028

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: 20881028

Country of ref document: EP

Kind code of ref document: A1