CN111310043B - Method and device for pushing information - Google Patents
Method and device for pushing information Download PDFInfo
- Publication number
- CN111310043B CN111310043B CN202010093060.8A CN202010093060A CN111310043B CN 111310043 B CN111310043 B CN 111310043B CN 202010093060 A CN202010093060 A CN 202010093060A CN 111310043 B CN111310043 B CN 111310043B
- Authority
- CN
- China
- Prior art keywords
- information
- client
- event information
- event
- dimension
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/953—Querying, e.g. by the use of web search engines
- G06F16/9535—Search customisation based on user profiles and personalisation
Abstract
The embodiment of the disclosure discloses a method and a device for pushing information. One embodiment of the method comprises the following steps: generating initial event information in response to detecting a failure or resource adjustment; generating event information of system dimension based on the initial event information supplementary time information and resource information; acquiring a corresponding relation between a client and a resource thereof, and matching the corresponding relation with event information of a system dimension; determining the successfully matched clients as target clients influenced by the event, and generating event information aiming at the client dimension of the target clients; event information for the client dimension is pushed to the target client. According to the cloud service management method and device, the problems of untimely caused by manual notification, unnecessary disturbing caused by inaccurate notification range, information invalidation caused by incomplete event information and the like can be effectively solved, and then the treatment efficiency and accuracy of a customer when the cloud service is abnormal can be effectively improved.
Description
Technical Field
The embodiment of the disclosure relates to the technical field of computers, in particular to a method and a device for pushing information.
Background
With the rapid development and landing of cloud computing, more and more enterprises build own services on public clouds, and various cloud services and components are used, and for the enterprises, the stability of the business is more and more dependent on the system stability of the cloud services; when cloud service fails or is subjected to planned adjustment, the service of an enterprise client can be influenced, the information needs to be timely and accurately pushed to the enterprise client side, the client can be helped to quickly perceive accurate abnormal information, the corresponding adjustment and processing are further accelerated, and the influence of the cloud service failure or adjustment on the client is reduced; if such a message fails to reach the client side, it may affect the fault handling decision of the client, which may further lead to an expansion of the fault impact, and may also affect the brand public praise of the cloud computing manufacturer itself.
The conventional common methods for notifying clients of public cloud service fault event information generally comprise the following two methods:
1. customer manager channel: before faults occur or adjustment is carried out in a plan, related contents are synchronized to a client manager by operation and maintenance or research personnel of cloud service, and then the client manager notifies all clients through communication tools such as telephone, weChat and the like; the clients are synchronized with the progress of the event at irregular intervals and for indefinite times; i.e. the event information is provided to the client in a "person-to-person" manner. Because the clients are manually contacted by the client manager, the condition that the notification is not timely or not coming can occur, and the fault information synchronization is delayed, so that the fault handling judgment of the clients can be influenced.
2. Intra-station communication channel: before a fault event occurs or adjustment is carried out in a plan, the related content is synchronized to after-sales support or related administrators by operation and maintenance or research personnel of cloud service, and then event information is pushed to all clients through station internal information; typically a one-time notification, without too many status updates and subsequent notifications. Because the cloud service is sent by the station communication full staff, the clients which are not affected by the fault or adjustment of the cloud service at the time can be also reminded and notified in the same way, and extra interference can be caused to the clients
In the two methods, with the development of faults, the intermediate state and the final state are not timely and clear, so that when a customer compares with the fault, the customer is puzzled due to the fact that the customer is not aligned due to no clear time and context, the information becomes invalid information, and the trust of the customer to a cloud service manufacturer is reduced.
Disclosure of Invention
The embodiment of the disclosure provides a method and a device for pushing information.
In a first aspect, embodiments of the present disclosure provide a method for pushing information, including: generating initial event information in response to detecting a failure or resource adjustment; generating event information of system dimension based on the initial event information supplementary time information and resource information; acquiring a corresponding relation between a client and a resource thereof, and matching the corresponding relation with event information of a system dimension; determining the successfully matched clients as target clients influenced by the event, and generating event information aiming at the client dimension of the target clients; event information for the client dimension is pushed to the target client.
In some embodiments, the method further comprises: and receiving feedback information of the target client to assist the cloud service side in carrying out relevant adjustment and response.
In some embodiments, after generating the event information for the client dimension of the target client, the method further comprises: and if the target client is determined to have no pushing authority, event information of the client dimension is filtered, and the event information is not pushed to the target client.
In some embodiments, the method further comprises: and (5) performing regular offline data mining and processing to generate the corresponding relation of the clients and the resources thereof.
In some embodiments, the method further comprises: event related information is displayed at the front end.
In some embodiments, generating event information for a client dimension of a target client includes: generating state information according to the monitored data state; event information of the system dimension is adjusted to a form understood by a customer and state information is added.
In a second aspect, embodiments of the present disclosure provide an apparatus for pushing information, including: a generation unit configured to generate initial event information in response to detection of a failure or resource adjustment; a complementing unit configured to complement the time information and the resource information based on the initial event information, and generate event information of a system dimension; the matching unit is configured to acquire the corresponding relation between the clients and the resources thereof and match the corresponding relation with the event information of the system dimension; a conversion unit configured to determine a successfully matched client as a target client affected by the event and generate event information for a client dimension of the target client; and the pushing unit is configured to push the event information of the client dimension to the target client.
In some embodiments, the apparatus further comprises a feedback unit configured to: and receiving feedback information of the target client to assist the cloud service side in carrying out relevant adjustment and response.
In some embodiments, the apparatus further comprises a filtering unit configured to: after generating the event information of the client dimension for the target client, if it is determined that the target client does not have the pushing authority, filtering the event information of the client dimension and not pushing the event information to the target client.
In some embodiments, the apparatus further comprises an excavating unit configured to: and (5) performing regular offline data mining and processing to generate the corresponding relation of the clients and the resources thereof.
In some embodiments, the apparatus further comprises a display unit configured to: event related information is displayed at the front end.
In some embodiments, the conversion unit is further configured to: generating state information according to the monitored data state; event information of the system dimension is adjusted to a form understood by a customer and state information is added.
In a third aspect, embodiments of the present disclosure provide an electronic device for pushing information, including: one or more processors; a storage device having one or more programs stored thereon, which when executed by one or more processors, cause the one or more processors to implement the method as in any of the first aspects.
In a fourth aspect, embodiments of the present disclosure provide a computer readable medium having a computer program stored thereon, wherein the program when executed by a processor implements a method as in any of the first aspects.
The method and the device for pushing information provided by the embodiment of the disclosure are mainly aimed at enterprise clients with services deployed in public cloud environments, and when public cloud services are in fault or are adjusted in a plan, the scene of how to quickly and accurately acquire related information can be effectively solved, so that the problems in multiple aspects such as untimely caused by manual notification, unnecessary disturbance caused by inaccurate notification range, information invalidation caused by incomplete event information and the like can be effectively solved, and further the disposal efficiency and the accuracy of the clients when the cloud services are abnormal can be effectively improved.
Drawings
Other features, objects and advantages of the present disclosure will become more apparent upon reading of the detailed description of non-limiting embodiments, made with reference to the following drawings:
FIG. 1 is an exemplary system architecture diagram in which an embodiment of the present disclosure may be applied;
FIG. 2 is a flow chart of one embodiment of a method for pushing information according to the present disclosure;
FIG. 3 is a schematic illustration of one application scenario of a method for pushing information according to the present disclosure;
FIG. 4 is a flow chart of yet another embodiment of a method for pushing information according to the present disclosure;
FIG. 5 is a schematic structural view of one embodiment of an apparatus for pushing information according to the present disclosure;
fig. 6 is a schematic diagram of a computer system suitable for use in implementing embodiments of the present disclosure.
Detailed Description
The present disclosure is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be noted that, for convenience of description, only the portions related to the present invention are shown in the drawings.
It should be noted that, without conflict, the embodiments of the present disclosure and features of the embodiments may be combined with each other. The present disclosure will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
Fig. 1 illustrates an exemplary system architecture 100 to which embodiments of the methods for pushing information or apparatuses for pushing information of the present disclosure may be applied.
As shown in fig. 1, the system architecture 100 may include client terminal devices 101, 102, 103 and a server 104. The terminal devices 101, 102, 103 and the server 104 are connected via a network. The network may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
The client can interact with the server 104 via the network 104 using the terminal devices 101, 102, 103 to receive or send messages or the like. Various communication client applications, such as a web browser application, a shopping class application, a search class application, an instant messaging tool, a mailbox client, social platform software, etc., may be installed on the terminal devices 101, 102, 103.
The terminal devices 101, 102, 103 may be hardware or software. When the terminal devices 101, 102, 103 are hardware, they may be various electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablet computers, electronic book readers, MP3 players (Moving Picture Experts Group Audio Layer III, dynamic video expert compression standard audio plane 3), MP4 (Moving Picture Experts Group Audio Layer IV, dynamic video expert compression standard audio plane 4) players, laptop and desktop computers, and the like. When the terminal devices 101, 102, 103 are software, they can be installed in the above-listed electronic devices. Which may be implemented as multiple software or software modules (e.g., to provide distributed services), or as a single software or software module. The present invention is not particularly limited herein.
The server 104 provides a whole set of solutions for event management in public cloud scenes, the specific content and state update of event information are managed through a fault management system at the back end, the events and clients are correspondingly managed through basic data of a client asset management system, the events are pushed to the clients through the event management system, the clients can check and pay attention to the events through a dashboard at the front end, and peripheral management and automation flow tools are constructed, so that an integral solution is formed.
The main working mechanism and functions of each link and module are described as follows:
1. fault management system: the system has the main functions of managing event information at the cloud service side, and storing the event information into a fault management system in the form of an event (the event form at least comprises the content of the event, the time of the event and a resource (asset) list influenced by the event when the monitoring system alarms abnormally) when the cloud service malfunctions or is adjusted in a planning way, and the system supports automatic information recording (such as capturing related abnormality from the monitoring system) and manual recording and modification (such as adjustment in a planning way). The master control module is used for managing fault events and providing an API, and can automatically store the fault events into a database through the module or manually record the events through the module; the information of interactions with the database is event data.
2. Customer asset management system: the system has the main functions that a user stores the corresponding relation between a client and resources thereof, and when an event occurs, the mapping relation between the corresponding affected resources and the client is required to be acquired from the module to acquire an accurate user for the subsequent event information pushing; because of the large data volume, the content is mainly generated by periodic offline mining, a cache system is used for subsequent flow, and when an event with high real-time requirement is encountered, the event can be met through the real-time interface. The offline computation is mainly to perform offline convergence computation on clients and corresponding resource (asset) information in each system to form a unified data structure for subsequent query.
3. Event management system: the system is a core module in the whole event management scheme, and has the main functions of carrying out real-time calculation and mapping by combining information of client assets after acquiring an event, finding out a specific client influenced by the event and influenced resources thereof, generating corresponding event information, pushing the event information to the client, and providing the client with reference and understanding; when the event has a status update in the following, the system can also update and push quickly.
Event matching is mainly to match an event with a client, and the general method is to match resources in data of the event (such as a machine list, an IP, etc.) with the resources (assets) of the client in the client asset management, so as to find an association match of the event with the client.
Event filtering mainly considers that not all events can be pushed to a client side, such as some sensitive business information or internal information, cannot be directly pushed, so that certain filtering is needed.
The trigger is to push the event to the message pushing module after the event filtering is completed, so as to trigger the pushing of the event information.
The front end is a web interface which can be seen by a client and is used for viewing pushed event information
It should be noted that, the method for pushing information provided by the embodiments of the present disclosure is generally performed by the server 104, and accordingly, the device for pushing information is generally disposed in the server 104.
It should be understood that the number of terminal devices, networks and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
With continued reference to fig. 2, a flow 200 of one embodiment of a method for pushing information according to the present disclosure is shown.
In response to detecting a failure or resource adjustment, initial event information is generated, step 201.
In this embodiment, the execution entity (e.g., the server shown in fig. 1) of the method for pushing information may perform regular offline data mining and processing by the client asset management system before the event occurs, so as to generate the correspondence between the existing client and its asset. Because the information of { client: resource } exists in various systems, such as virtual machines, storage, networks and the like of the cloud are different systems, the data can be in different places, and therefore offline calculation is needed, namely, the client in each system and the corresponding resource and asset information are subjected to offline convergence calculation to form a unified data structure.
When a fault event occurs, the fault is found to be alarmed by the monitoring system, and the fault management system can automatically capture the fault.
When an adjustment event (such as "program for upgrading xx cluster is expected at point 0 of the next wednesday, and xx machines of the cluster are out of service during upgrading") occurs, the operation and maintenance of cloud service or research personnel enter main information through an interface or interface of a fault management system.
Step 202, event information of system dimension is generated based on the initial event information supplementary time information and resource information.
In this embodiment, the initial event information is incomplete and needs to be completed. When a fault event occurs, the monitoring system includes part of time information and resource information, and the time information may not need to be supplemented, but in some situations, the resource information needs to be supplemented (for example, in a virtual machine system, the monitoring finds out the resources of a host machine, but the resource information of the virtual machine needs to be supplemented, so that the data in the asset management system can be conveniently docked). The fault management system supplements information enrichment, such as adding time information, resource information and the like, and structurally stores the information in the storage of the fault management system.
When the adjustment event occurs, the operation and maintenance of the cloud service or the research and development personnel enter main information through an interface or an interface of the fault management system, and the fault management system can automatically supplement other information such as time information, resource information and the like, and the information is stored in the storage of the fault management system in the same structure.
Step 203, obtaining the corresponding relation between the clients and the resources thereof, and matching the corresponding relation with the event information of the system dimension.
In this embodiment, the event management system matches the event information with the client asset information to generate a correspondence of the event, the client, and the asset. Event matching is mainly to match an event with a client, and the general method is to match resources in data of the event (such as a machine list, an IP, etc.) with the resources (assets) of the client in the client asset management, so as to find an association match of the event with the client.
In step 204, the successfully matched clients are determined to be the target clients affected by the event, and event information for the client dimensions of the target clients is generated.
In this embodiment, event information of the system dimension is converted into a form understood by the customer. And pertinently supplementing the related information of the target client to generate event information of the client dimension.
Optionally, the status is updated for the newly added event and the data is stored. The state is according to the data state in the monitoring system, then the state of the event that the fault management system generates mainly has newly added, operates, terminates, ends; the non-new additions herein are mainly to say events that have been terminated and ended. The state information is added to the event information for the client dimension.
Step 205, pushing event information of a client dimension to a target client.
In this embodiment, the event pushing may send important information, such as occurrence of a fault, end of the fault, etc., to the client in real time through a short message or mail, etc.; all information related to the event is synchronized to the front end for display.
Event aggregation (such as a fault of xx service occurring in xx time in the last week and adjustment of xx service occurring in xx time) can be performed at the front end of event management, so that a customer can conveniently master cloud service operation quality in the last period, and the customer can be helped to optimize self service stability.
Through the above parts, the complete scheme of event information management can be realized, by utilizing the scheme, the faults of the cloud service side and the adjustment in the plan can be accurately and timely synchronized to the client, the client can more comprehensively, timely and accurately master the service quality of the cloud used by the client, and the decision of the client on fault treatment can be accelerated.
With continued reference to fig. 3, fig. 3 is a schematic diagram of an application scenario of the method for pushing information according to the present embodiment. In the application scenario of fig. 3, operation and maintenance of the cloud service or research personnel enter upgrade information through an interface or an interface of the fault management system to obtain initial event information "upgrade program of xx cluster". The fault management system automatically supplements other event information such as time information, resource information and the like for generating system dimension' 2020, 2 months, 19 days and 24:00 upgrades the program of xx clusters, during which xx machines of the clusters will break service. The event management system will periodically read the content from the fault management system at high frequency (minute granularity, e.g., 1 minute for a fault with high timeliness requirements and 5 minutes for a fault with relatively low requirements) and make up or adjust the data to some extent. And the event management system matches the information with the client asset information to generate the corresponding relation of the event, the client and the asset, determines the target client to be pushed, and generates the event information of the client dimension aiming at the target client, for example, different clients have different affected resources. And then pushing information according to a pushing mode preset by a client.
The method and the system mainly aim at enterprise clients with services deployed in public cloud environments, when public cloud services are in fault or adjusted in a plan, the scene of how to quickly and accurately acquire related information can be effectively solved, the problems of untimely problems caused by manual notification, unnecessary disturbance problems caused by inaccurate notification range, information invalidation caused by incomplete event information and the like can be effectively solved, and further the disposal efficiency and the accuracy of the clients when the cloud services are abnormal can be effectively improved.
With further reference to fig. 4, a flow 400 of yet another embodiment of a method for pushing information is shown. The flow 400 of the method for pushing information comprises the steps of:
in response to detecting the failure or resource adjustment, initial event information is generated, step 401.
Step 402, event information of system dimension is generated based on the initial event information supplemental time information and resource information.
Step 403, obtaining the corresponding relation between the client and the resource thereof, and matching the corresponding relation with the event information of the system dimension.
Step 404, determining the successfully matched clients as the target clients affected by the event, and generating event information for the client dimensions of the target clients.
Steps 401-404 are substantially identical to steps 201-204 and are therefore not described in detail.
Step 405 determines if the target client has push rights.
In this embodiment, some sensitive information or internal information cannot be pushed to the client at will, and it is necessary to confirm whether the client has the corresponding authority. The client authority can be confirmed manually or according to the set client authority. For example, setting a that the client cannot receive the resource transformation information is not pushed to it. Event filtering mainly considers that not all events can be pushed to a client side, such as some sensitive business information or internal information, cannot be directly pushed, so that certain filtering is needed.
Step 406, pushing event information of the client dimension to the target client.
Step 406 is substantially the same as step 205 and will not be described in detail.
Step 407, receiving feedback information of the target client to assist the cloud service side in performing relevant adjustment and response.
In this embodiment, after receiving the relevant information, the client may operate and manage the event through the front end of the event management, for example, marking has no effect, feedback advice, etc., and these information may also be fed back to the operation and maintenance or research personnel of the cloud service, so as to assist the cloud service side in performing relevant adjustment and response. The primary purpose of the tag is to be known to the cloud-side operators who may be treated differently or may be prioritized if certain customers think that the fault or adjustment has no effect on him. Feedback suggestions are also mainly used for helping cloud-side operators to make different corresponding schemes.
As can be seen from fig. 4, compared to the corresponding embodiment of fig. 2, the flow 400 of the method for pushing information in this embodiment embodies the step of filtering the event. Therefore, the scheme described in the embodiment can ensure that the internal information is not leaked while targeted pushing is performed.
With further reference to fig. 5, as an implementation of the method shown in the foregoing figures, the present disclosure provides an embodiment of an apparatus for pushing information, where the embodiment of the apparatus corresponds to the embodiment of the method shown in fig. 2, and the apparatus may be specifically applied in various electronic devices.
As shown in fig. 5, the apparatus 500 for pushing information of the present embodiment includes: a generating unit 501, a complementing unit 502, a matching unit 503, a converting unit 504, and a pushing unit 505. Wherein the generating unit 501 is configured to generate initial event information in response to detecting a failure or resource adjustment; a complementing unit 502 configured to complement the time information and the resource information based on the initial event information, and generate event information of a system dimension; a matching unit 503 configured to obtain a correspondence between a client and its resource, and match the correspondence with event information of a system dimension; a conversion unit 504 configured to determine a successfully matched client as a target client affected by the event and generate event information for a client dimension of the target client; a pushing unit 505 configured to push event information of a client dimension to a target client.
In this embodiment, specific processes of the generating unit 501, the complementing unit 502, the matching unit 503, the converting unit 504, and the pushing unit 505 of the apparatus 500 for pushing information may refer to steps 201, 202, 203, 204, and 205 in the corresponding embodiment of fig. 2.
In some optional implementations of the present embodiment, the apparatus 500 further includes a feedback unit (not shown in the drawings) configured to: and receiving feedback information of the target client to assist the cloud service side in carrying out relevant adjustment and response.
In some optional implementations of the present embodiment, the apparatus 500 further includes a filtering unit (not shown in the drawings) configured to: after generating the event information of the client dimension for the target client, if it is determined that the target client does not have the pushing authority, filtering the event information of the client dimension and not pushing the event information to the target client.
In some optional implementations of the present embodiment, the apparatus 500 further includes an excavating unit (not shown in the drawings) configured to: and (5) performing regular offline data mining and processing to generate the corresponding relation of the clients and the resources thereof.
In some optional implementations of the present embodiment, the apparatus 500 further includes a display unit (not shown in the drawings) configured to: event related information is displayed at the front end.
In some optional implementations of the present embodiment, the conversion unit is further configured to: generating state information according to the monitored data state; event information of the system dimension is adjusted to a form understood by a customer and state information is added.
Referring now to fig. 6, a schematic diagram of an electronic device (e.g., server or terminal device of fig. 1) 600 suitable for use in implementing embodiments of the present disclosure is shown. The terminal devices in the embodiments of the present disclosure may include, but are not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), car terminals (e.g., car navigation terminals), and the like, and stationary terminals such as digital TVs, desktop computers, and the like. The terminal device/server illustrated in fig. 6 is merely an example, and should not impose any limitation on the functionality and scope of use of embodiments of the present disclosure.
As shown in fig. 6, the electronic device 600 may include a processing means (e.g., a central processing unit, a graphics processor, etc.) 601, which may perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 602 or a program loaded from a storage means 608 into a Random Access Memory (RAM) 603. In the RAM603, various programs and data required for the operation of the electronic apparatus 600 are also stored. The processing device 601, the ROM 602, and the RAM603 are connected to each other through a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
In general, the following devices may be connected to the I/O interface 605: input devices 606 including, for example, a touch screen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, and the like; an output device 607 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 608 including, for example, magnetic tape, hard disk, etc.; and a communication device 609. The communication means 609 may allow the electronic device 600 to communicate with other devices wirelessly or by wire to exchange data. While fig. 6 shows an electronic device 600 having various means, it is to be understood that not all of the illustrated means are required to be implemented or provided. More or fewer devices may be implemented or provided instead. Each block shown in fig. 6 may represent one device or a plurality of devices as needed.
In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network via communication means 609, or from storage means 608, or from ROM 602. The above-described functions defined in the methods of the embodiments of the present disclosure are performed when the computer program is executed by the processing means 601. It should be noted that, the computer readable medium according to the embodiments of the present disclosure may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In an embodiment of the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. Whereas in embodiments of the present disclosure, the computer-readable signal medium may comprise a data signal propagated in baseband or as part of a carrier wave, with computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, fiber optic cables, RF (radio frequency), and the like, or any suitable combination of the foregoing.
The computer readable medium may be contained in the electronic device; or may exist alone without being incorporated into the electronic device. The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: generating initial event information in response to detecting a failure or resource adjustment; generating event information of system dimension based on the initial event information supplementary time information and resource information; acquiring a corresponding relation between a client and a resource thereof, and matching the corresponding relation with event information of a system dimension; determining the successfully matched clients as target clients influenced by the event, and generating event information aiming at the client dimension of the target clients; event information for the client dimension is pushed to the target client.
Computer program code for carrying out operations of embodiments of the present disclosure may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units involved in the embodiments described in the present disclosure may be implemented by means of software, or may be implemented by means of hardware. The described units may also be provided in a processor, for example, described as: a processor comprises a generating unit, a complementing unit, a matching unit, a converting unit and a pushing unit. Where the names of the units do not constitute a limitation of the unit itself in some cases, for example, the generating unit may also be described as "a unit that generates initial event information in response to detection of a failure or resource adjustment".
The foregoing description is only of the preferred embodiments of the present disclosure and description of the principles of the technology being employed. It will be appreciated by those skilled in the art that the scope of the invention referred to in this disclosure is not limited to the specific combination of features described above, but encompasses other embodiments in which any combination of features described above or their equivalents is contemplated without departing from the inventive concepts described. Such as those described above, are mutually substituted with the technical features having similar functions disclosed in the present disclosure (but not limited thereto).
Claims (14)
1. A method for pushing information, comprising:
generating initial event information in response to detecting a fault or resource adjustment, wherein prior to the occurrence of the event, periodic offline data mining and processing is performed by a customer asset management system to generate a correspondence for an existing customer and its assets;
generating event information of system dimension based on the initial event information supplementary time information and resource information;
acquiring a corresponding relation between a client and a resource thereof, and matching the corresponding relation with event information of the system dimension;
determining a successfully matched client as a target client influenced by an event, converting event information of a system dimension into a client understanding form, and pertinently supplementing related information of the target client to generate event information of a client dimension of the target client;
and pushing the event information of the client dimension to the target client.
2. The method of claim 1, wherein the method further comprises:
and receiving feedback information of the target client to assist the cloud service side in carrying out relevant adjustment and coping.
3. The method of claim 1, wherein after generating event information for the client dimension of the target client, the method further comprises:
and if the target client is determined to have no pushing authority, filtering event information of the client dimension, and not pushing the event information to the target client.
4. The method of claim 1, wherein the method further comprises:
and (5) performing regular offline data mining and processing to generate the corresponding relation of the clients and the resources thereof.
5. The method of claim 1, wherein the method further comprises:
event related information is displayed at the front end.
6. The method of one of claims 1-5, wherein the generating event information for a client dimension of the target client comprises:
generating state information according to the monitored data state;
and adjusting the event information of the system dimension into a form understood by a client and adding the state information.
7. An apparatus for pushing information, comprising:
a generation unit configured to generate initial event information in response to detection of a failure or resource adjustment, wherein prior to occurrence of an event, periodic offline data mining and processing is performed by the customer asset management system, generating correspondence of existing customers and their assets;
a complementing unit configured to complement time information and resource information based on the initial event information, and generate event information of a system dimension;
the matching unit is configured to acquire the corresponding relation between the clients and the resources thereof and match the corresponding relation with the event information of the system dimension;
the conversion unit is configured to determine a successfully matched client as a target client influenced by an event, convert event information of a system dimension into a form understood by the client, and pertinently supplement related information of the target client to generate event information of the client dimension of the target client;
and the pushing unit is configured to push the event information of the client dimension to the target client.
8. The apparatus of claim 7, wherein the apparatus further comprises a feedback unit configured to:
and receiving feedback information of the target client to assist the cloud service side in carrying out relevant adjustment and coping.
9. The apparatus of claim 7, wherein the apparatus further comprises a filtering unit configured to:
after generating the event information of the client dimension aiming at the target client, if the target client is determined to have no pushing authority, filtering the event information of the client dimension, and not pushing the event information to the target client.
10. The apparatus of claim 7, wherein the apparatus further comprises an excavating unit configured to:
and (5) performing regular offline data mining and processing to generate the corresponding relation of the clients and the resources thereof.
11. The apparatus of claim 7, wherein the apparatus further comprises a display unit configured to:
event related information is displayed at the front end.
12. The apparatus according to one of claims 7-11, wherein the conversion unit is further configured to:
generating state information according to the monitored data state;
and adjusting the event information of the system dimension into a form understood by a client and adding the state information.
13. An electronic device for pushing information, comprising:
one or more processors;
a storage device having one or more programs stored thereon,
when executed by the one or more processors, causes the one or more processors to implement the method of any of claims 1-6.
14. A computer readable medium having stored thereon a computer program, wherein the program when executed by a processor implements the method of any of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010093060.8A CN111310043B (en) | 2020-02-14 | 2020-02-14 | Method and device for pushing information |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010093060.8A CN111310043B (en) | 2020-02-14 | 2020-02-14 | Method and device for pushing information |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111310043A CN111310043A (en) | 2020-06-19 |
| CN111310043B true CN111310043B (en) | 2023-07-28 |
Family
ID=71145001
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010093060.8A Active CN111310043B (en) | 2020-02-14 | 2020-02-14 | Method and device for pushing information |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111310043B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105323309A (en) * | 2015-09-29 | 2016-02-10 | 北京金山安全软件有限公司 | Method and device for pushing bubble resources |
| US9947202B1 (en) * | 2016-01-06 | 2018-04-17 | State Farm Mutual Automobile Insurance Company | Sensor data to identify catastrophe areas |
| CN110097341A (en) * | 2019-04-29 | 2019-08-06 | 重庆天蓬网络有限公司 | A kind of automation O&M management-control method, device, medium and electronic equipment |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2009151560A (en) * | 2007-12-20 | 2009-07-09 | Hitachi Ltd | Resource management method, information processing system, information processor and program |
| US8924489B2 (en) * | 2011-01-05 | 2014-12-30 | Apple Inc. | Message push notification client improvements for multi-user devices |
| US9246894B2 (en) * | 2012-10-30 | 2016-01-26 | Microsoft Technology Licensing, Llc. | Communicating state information to legacy clients using legacy protocols |
| CN104795896B (en) * | 2015-04-17 | 2017-11-17 | 国家电网公司 | A kind of automatic point-to-point note Notification Method of client's outage information |
| CN106933630B (en) * | 2017-03-09 | 2020-07-31 | 百度在线网络技术（北京）有限公司 | Client upgrading method, device, equipment and storage medium |
-
2020
- 2020-02-14 CN CN202010093060.8A patent/CN111310043B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105323309A (en) * | 2015-09-29 | 2016-02-10 | 北京金山安全软件有限公司 | Method and device for pushing bubble resources |
| US9947202B1 (en) * | 2016-01-06 | 2018-04-17 | State Farm Mutual Automobile Insurance Company | Sensor data to identify catastrophe areas |
| CN110097341A (en) * | 2019-04-29 | 2019-08-06 | 重庆天蓬网络有限公司 | A kind of automation O&M management-control method, device, medium and electronic equipment |
Non-Patent Citations (3)
| Title |
|---|
| The Design and Implementation of News Media Comprehensive Information Push System Based on Cloud Push;Zhuohang Li et al.;《2014 Fourth International Conference on Instrumentation and Measurement, Computer, Communication and Control》;全文 * |
| 基于Netty面向Android端消息推送系统的实现;孙丽琼;《中国优秀硕士学位论文全文数据库（电子期刊）》;全文 * |
| 能源企业运营监测数据集成平台的设计与实现;陈聪翔;《中国优秀硕士学位论文全文数据库（电子期刊）》;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111310043A (en) | 2020-06-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109582310B (en) | Data processing method and device, electronic equipment and computer readable storage medium | |
| CN111338834B (en) | Data storage method and device | |
| CN112860343A (en) | Configuration changing method, system, device, electronic equipment and storage medium | |
| CN113220342A (en) | Centralized configuration method and device, electronic equipment and storage medium | |
| CN111639086A (en) | Data reconciliation method, device, equipment and storage medium | |
| CN111310043B (en) | Method and device for pushing information | |
| CN111198853B (en) | Data processing method, device, electronic equipment and computer readable storage medium | |
| CN111367720A (en) | Data protection method and device, electronic equipment and computer readable storage medium | |
| CN110727558A (en) | Information prompting method and device, storage medium and electronic equipment | |
| US11277300B2 (en) | Method and apparatus for outputting information | |
| CN111290873B (en) | Fault processing method and device | |
| CN110750424B (en) | Resource inspection method and device | |
| CN112241332B (en) | Interface compensation method and device | |
| CN110221854B (en) | Multi-process data updating method, device, medium and electronic equipment | |
| CN113568695A (en) | Corner mark processing method and device for boarder application | |
| CN112463616A (en) | Chaos testing method and device for Kubernetes container platform | |
| CN110262756B (en) | Method and device for caching data | |
| CN114253520B (en) | Interface code generation method and device | |
| US11513817B2 (en) | Preventing disruption within information technology environments | |
| CN112783733B (en) | Interface fusing control method, device, medium and electronic equipment | |
| US20240103992A1 (en) | Alert rule manipulation in sync of temporary configuration change | |
| CN110633324B (en) | Method, apparatus, electronic device and computer readable medium for synchronizing data | |
| CN110750242B (en) | File deployment method, system, medium and electronic equipment | |
| CN112749042B (en) | Application running method and device | |
| CN117931588A (en) | Data source monitoring method and device, electronic equipment and computer readable medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |