CN111078430A - Message notification processing method, device and storage medium - Google Patents

Message notification processing method, device and storage medium Download PDF

Info

Publication number
CN111078430A
CN111078430A CN201911251211.1A CN201911251211A CN111078430A CN 111078430 A CN111078430 A CN 111078430A CN 201911251211 A CN201911251211 A CN 201911251211A CN 111078430 A CN111078430 A CN 111078430A
Authority
CN
China
Prior art keywords
message
queue
sending
subscription information
event
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.)
Withdrawn
Application number
CN201911251211.1A
Other languages
Chinese (zh)
Inventor
段萌
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Suzhou Inspur Intelligent Technology Co Ltd
Original Assignee
Suzhou Inspur Intelligent Technology Co Ltd
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 Suzhou Inspur Intelligent Technology Co Ltd filed Critical Suzhou Inspur Intelligent Technology Co Ltd
Priority to CN201911251211.1A priority Critical patent/CN111078430A/en
Publication of CN111078430A publication Critical patent/CN111078430A/en
Withdrawn legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/54Interprogram communication
    • G06F9/546Message passing systems or structures, e.g. queues
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/54Interprogram communication
    • G06F9/542Event management; Broadcasting; Multicasting; Notifications
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00Indexing scheme relating to G06F9/00
    • G06F2209/54Indexing scheme relating to G06F9/54
    • G06F2209/548Queue

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The invention discloses a message notification processing method, which comprises the following steps: receiving message subscription information and message notification content; generating a message event by using the message notification content and the attribute parameter corresponding to the message notification content; encapsulating the message event and the sending parameters corresponding to the message event into a message object; adding the message object into a first queue; and sending the message event in the message object in the first queue to a receiving end corresponding to the message subscription information, and updating the sending parameter in the message object. The invention also discloses a computer device and a readable storage medium. The proposal provided by the invention services and configures the message notification in the storage cluster, can configure different message processing modes according to different sub-module service characteristics, enriches and perfects the unified management of cluster message notification processing.

Description

Message notification processing method, device and storage medium
Technical Field
The present invention relates to the field of message processing, and in particular, to a message notification processing method, device, and storage medium.
Background
In the era of mass data, storage clusters are widely used, and message notification processing in the storage clusters also becomes a vital technology. For different application scenarios and data processing complexity, there are numerous service modules in a cluster, and the message notification modes of each module are various, and one message notification method cannot realize the message notification modes and message sending modes of all modules, because a client may require that the cluster message notification can be smoothly merged into its own system, and a new message notification mode and message sending mode may be proposed.
Disclosure of Invention
In view of the above, in order to overcome at least one aspect of the above problems, an embodiment of the present invention provides a message notification processing method, including:
receiving message subscription information and message notification content;
generating a message event by using the message notification content and the attribute parameter corresponding to the message notification content;
encapsulating the message event and the sending parameters corresponding to the message event into a message object;
adding the message object into a first queue;
and sending the message event in the message object in the first queue to a receiving end corresponding to the message subscription information, and updating the sending parameter in the message object.
In some embodiments, receiving the message subscription information further comprises:
judging the type of the message subscription information;
in response to the type being a subscription, adding the subscription information to a second queue;
in response to the type being unsubscribe, judging whether subscription information identical to the identifier in the subscription information exists in the second queue;
in response to there being a subscription message that is the same as the identifier in the subscription message, deleting the corresponding subscription message in the second queue.
In some embodiments, adding the message object to the first queue further comprises:
assigning values to the sending parameters in the message objects;
judging whether the same message object exists in the first queue according to the identifier corresponding to the message event in the message object;
in response to the presence of the identical message object, replacing the identical message object in the first queue with the message object.
In some embodiments, sending the message event in the message object in the first queue to a receiving end corresponding to the message subscription information, and updating a sending parameter in the message object, further includes:
determining a receiving end corresponding to the message subscription information according to a preset mapping relation between an identifier in the subscription information and an identifier corresponding to a message event in the message object;
sending the message event to the receiving end according to a message notification mode in the message subscription information;
and updating the sending times and sending time in the message object.
In some embodiments, further comprising:
judging whether the sending times of the message objects in the first queue reach preset sending times or not and the difference value between the first sending time and the last sending time reaches a preset difference value;
and in response to the sending times reaching a preset sending time and the difference reaching a preset difference, deleting the message object from the first queue.
Based on the same inventive concept, according to another aspect of the present invention, an embodiment of the present invention further provides a computer apparatus, including:
at least one processor; and
a memory storing a computer program operable on the processor, wherein the processor executes the program to perform the steps of:
receiving message subscription information and message notification content;
generating a message event by using the message notification content and the attribute parameter corresponding to the message notification content;
encapsulating the message event and the sending parameters corresponding to the message event into a message object;
adding the message object into a first queue;
and sending the message event in the message object in the first queue to a receiving end corresponding to the message subscription information, and updating the sending parameter in the message object.
In some embodiments, receiving the message subscription information further comprises:
judging the type of the message subscription information;
in response to the type being a subscription, adding the subscription information to a second queue;
in response to the type being unsubscribe, judging whether subscription information identical to the identifier in the subscription information exists in the second queue;
in response to there being a subscription message that is the same as the identifier in the subscription message, deleting the corresponding subscription message in the second queue.
In some embodiments, adding the message object to the first queue further comprises:
assigning values to the sending parameters in the message objects;
judging whether the same message object exists in the first queue according to the identifier corresponding to the message event in the message object;
in response to the presence of the identical message object, replacing the identical message object in the first queue with the message object.
In some embodiments, sending the message event in the message object in the first queue to a receiving end corresponding to the message subscription information, and updating a sending parameter in the message object, further includes:
determining a receiving end corresponding to the message subscription information according to a preset mapping relation between an identifier in the subscription information and an identifier corresponding to a message event in the message object;
sending the message event to the receiving end according to a message notification mode in the message subscription information;
and updating the sending times and sending time in the message object.
Based on the same inventive concept, according to another aspect of the present invention, an embodiment of the present invention further provides a computer-readable storage medium storing a computer program which, when executed by a processor, performs the steps of any of the message notification processing methods described above.
The invention has one of the following beneficial technical effects: the proposal provided by the invention services and configures the message notification in the storage cluster, can configure different message processing modes according to different sub-module service characteristics, enriches and perfects the unified management of cluster message notification processing.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other embodiments can be obtained by using the drawings without creative efforts.
Fig. 1 is a schematic flowchart of a message notification processing method according to an embodiment of the present invention;
fig. 2 is a block diagram of a system for implementing a message notification processing method according to an embodiment of the present invention;
fig. 3 is a flowchart illustrating a process of a message notification subscription module according to an embodiment of the present invention;
fig. 4 is a schematic processing flow diagram of a message notification processing module according to an embodiment of the present invention;
FIG. 5 is a schematic structural diagram of a computer device provided in an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a computer-readable storage medium according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the following embodiments of the present invention are described in further detail with reference to the accompanying drawings.
It should be noted that all expressions using "first" and "second" in the embodiments of the present invention are used for distinguishing two entities with the same name but different names or different parameters, and it should be noted that "first" and "second" are merely for convenience of description and should not be construed as limitations of the embodiments of the present invention, and they are not described in any more detail in the following embodiments.
According to an aspect of the present invention, an embodiment of the present invention provides a message notification processing method, as shown in fig. 1, which may include the steps of: s1, receiving message subscription information and message notification content; s2, generating message event by using the message notification content and the attribute parameter corresponding to the message notification content; s3, encapsulating the message event and the sending parameter corresponding to the message event into a message object; s4, adding the message object into the first queue; s5, sending the message event in the message object in the first queue to a receiving end corresponding to the message subscription information, and updating the sending parameter in the message object.
The proposal provided by the invention services and configures the message notification in the storage cluster, can configure different message processing modes according to different sub-module service characteristics, enriches and perfects the unified management of cluster message notification processing. The data are synchronized among the modules through the message channel, the message notification sending module is separated, a comprehensive message mode is set, a set of brand-new message notification event updating mechanism is adopted, the development task amount required by adding a new message notification mode is reduced, and various message butt joint sending modes are provided so as to meet the user requirements to the greatest extent.
As shown in fig. 2, the message notification processing method provided by the present invention can be completed by four modules, such as a message notification subscription module, a message notification collection module, a message notification processing module, and a message notification sending module, which are deployed in a cluster. The message notification collection module is responsible for collecting message notification information in each module of the cluster, forming a message notification event SubMsgEvent and sending the message notification event SubMsgEvent to the message processing module. The message notification processing module receives the message notification event SubMsgEvent sent by the message notification collection module, encapsulates the SubMsgEvent into a SubMsgObj object, and the message notification sending module sends the event in the SubMsgObj object to a corresponding receiving end.
In some embodiments, in the receiving the message subscription information at step S1, the method may further include:
judging the type of the message subscription information;
in response to the type being a subscription, adding the subscription information to a second queue;
in response to the type being unsubscribe, judging whether subscription information identical to the identifier in the subscription information exists in the second queue;
in response to there being a subscription message that is the same as the identifier in the subscription message, deleting the corresponding subscription message in the second queue.
Specifically, each module in the cluster may send subscription information (including a message notification mode MsgType, a message mode MsgModel, and a message receiving end DestModel) to the message notification subscription module, and the subscription module stores the subscription information in a queue SubMsgQueue.
It should be noted that, one module is allowed to send multiple pieces of subscription information at a time, the subscription information may also be deleted, and a "message notification mode, a message mode, and a receiver DestModel" may be used as a joint unique identifier for distinguishing different pieces of subscription information.
The message notification method MsgType indicates what type of message notification event is sent to the subscriber. The message mode comprises a frequency mode and a duration mode, wherein the COUNTER _ mode refers to that a message notification is sent at a fixed time interval each time, and repeated judgment is carried out until the preset times are reached; if the configuration is 1, the message is mainly used for foreground message notification, and if the configuration is more than 1, the message is mainly used for the failure repetition judgment module. The DURATION mode refers to that a message notification is sent every time at a fixed interval, and is timed from the first sending until the preset DURATION is reached, so that the DURATION mode is mostly used for background message tasks.
In some embodiments, as shown in fig. 3, a processing flow of the message subscription module is shown, and the specific flow is as follows:
step1, monitoring the subscription and deletion request of each submodule, judging whether the subscription information (including but not limited to the MsgType, the MsgModel and the Destmodel) and the operation type of the submodule are received, if so, going to the next Step, otherwise, continuing monitoring.
Step 2: a child thread is created and started.
Step 3: and judging whether the operation type is 'subscribe' or 'unsubscribe', if so, turning to Step4, and otherwise, turning to Step 5.
Step 4: and locking the queue SubMsgQueue, adding subscription information to the queue SubMsgQueue, and unlocking the queue SubMsgQueue.
Step 5: and locking the queue SubMsgQueue, judging whether subscription information with the same identifier exists in the queue SubMsgQueue or not by taking a message notification mode, a message mode and a message receiving end DestModel as the identifier, deleting the subscription information from the queue SubMsgQueue if the subscription information exists, and unlocking the queue SubMsgQueue.
Step 6: the child thread ends.
In some embodiments, in step S2, the attribute parameter corresponding to the message notification content may be a message notification level msghevel, a message notification source identifier MsgSourceID (for identifying the message notification source, the MsgSourceID must be unique within the cluster), or other message notification event information (e.g., event ID, etc., which is not specifically required by the present invention). As such, each message event SubMsgEvent may contain a message notification level MsgLevel, a message notification source identification MsgSource ID, and other message notification event information.
In some embodiments, in step S3, the sending parameter corresponding to the message event may be a message notification sending time interval MsgInterval (default no interval, sending only once, reserved for the existence of modules requiring multiple sending intervals), a sent time MsgSendCounts (default once, reserved for the existence of modules requiring multiple sending), a permitted sending time MsgCount (maximum 3 times, reserved for failed resending times), a first sending time msgffstime (first Send time), a permitted sending time MsgDuration (reserved for modules such as alarms), and a latest sending time mssttime (recent Send time) of submsevet. In this way, each message object may have a message event SubMsgEvent and a send parameter corresponding to the message event.
In some embodiments, adding the message object to the first queue at step S4, further comprises:
assigning values to the sending parameters in the message objects;
judging whether the same message object exists in the first queue according to the identifier corresponding to the message event in the message object;
in response to the presence of the identical message object, replacing the identical message object in the first queue with the message object.
Specifically, a message object submsgiobj to be added to the first queue may be recorded as msgiobj _ Copy, and assigned to each member variable of msgiobj _ Copy: MsgObj _ copy.msginterval is a cluster configuration value; MsgObj _ copy. msgsendcounts ═ 0; msgiobj _ copy.msgcount ═ cluster configuration values (configurable, different values may be configured for message notification events of different levels msgiobj _ copy.submsgevent.msglevel, e.g., configured by priority, etc.); MsgObj _ copy. msgffstime ═ 0; msgduration ═ cluster configuration values (configurable, different values can be configured for message notification events of different classes msgad _ copy.
Then, locking the first queue EventQueue, and judging whether the first queue EventQueue has the following objects:
msgnsourceid, wherein "═ means" equal "if present, replaces this object in the first queue with msgnbj _ Copy; otherwise, MsgObj _ Copy is added to the queue EventQueue, and the queue EventQueue is unlocked.
In some embodiments, sending the message event in the message object in the first queue to a receiving end corresponding to the message subscription information, and updating a sending parameter in the message object, further includes:
determining a receiving end corresponding to the message subscription information according to a preset mapping relation between an identifier in the subscription information and an identifier corresponding to a message event in the message object;
sending the message event to the receiving end according to a message notification mode in the message subscription information;
and updating the sending times and sending time in the message object.
In some embodiments, the method further comprises:
judging whether the sending times of the message objects in the first queue reach preset sending times or not and the difference value between the first sending time and the last sending time reaches a preset difference value;
and in response to the sending times reaching a preset sending time and the difference reaching a preset difference, deleting the message object from the first queue.
When the cluster is initialized, the message notification processing module starts a processing thread MsgProcThread, and processes the object in EventQueue in a timed loop, wherein the flow of the loop processing each time is as shown in fig. 4:
step1: locking the queue EventQueue, keeping the first element as MsgObj _1, updating the value of MsgObj _1.MsgFSTime to the current time, and if MsgObj _1.MsgFSTime is 0, then MsgObj _1.MsgFSTime is MsgObj _1. MsgRSTime.
Step 2: if msgabj _1.MsgSendCounts > -msgabj _1.MsgCount and (msgabj _1. MsgRSTime-msgabj _1. msgffstime) > -msgabj _1.MsgDuration, msgabj _1 is deleted from the queue EventQueue, go to Step 5; otherwise go to the next step.
Step 3: msgabj _ Copy ═ msgabj _1 (i.e., equivalent to msgabj _ Copy already in the first queue being the same as the message object msgabj _1 to be added to the first queue), assigns msgabj _1 to msgabj _ Copy, and passes msgabj _ Copy to the event sending module for sending.
Step 4: update attribute value of msgObj _ 1: MsgObj _1.MsgSendCounts + +, and the unlock queue EventQueue.
Step 5: other member objects in the queue EventQueue are processed according to the steps.
When sending message events, the message notification sending module polls and subscribes to the information queue SubMsgQueue, and sends the events in the submsgObj object to all receiving ends in the queue SubMsgQueue.
Recording a certain element in the subscription information queue SubMsgQueue as: the specific operation flow for sending the submisgobj object to the receiving end in the submisgobj _1 is as follows:
step1: marking SubMsgObj _1 as a certain element in a subscription information queue SubMsgQueue, and then determining MsgObj _1 in SubMsgQueue by an identifier (a unique identifier determined by a message notification mode, a message mode and a receiver DestModel) in SubMsgObj _1, wherein the message notification source identifier MsgSource ID of MsgObj _1 has a preset mapping relation with the identifier in SubMsgObj _1.
Step 2: if "submsgiobj _1.MsgSendCount (message mode) ═ COUNTER _ mode (frequency mode) and MsgObj _1.MsgSendCount (message sent number) < msgabj _1.MsgCount (allowed number of times of sending)", or "submsgabj _1. msgdmodel (message mode) ═ DURATION _ mode) and (msgabj _1. msgstime (first sending time)) < msgabj _1. MsgDuration)" the receiving end transmits msgaevev _1. msgevt to subbj _1.MsgDuration using a mode specified by submsgabj _1.MsgType (message notification mode).
The proposal provided by the invention services and configures the message notification in the storage cluster, can configure different message processing modes according to different sub-module service characteristics, enriches and perfects the unified management of cluster message notification processing. The modules synchronize data through message channels, and the message notification processing method and the message notification processing device in the storage cluster are formed by organic combination and interaction.
Based on the same inventive concept, according to another aspect of the present invention, as shown in fig. 5, an embodiment of the present invention further provides a computer apparatus 501, comprising:
at least one processor 520; and
the memory 510, the memory 510 stores a computer program 511 that is executable on the processor, and the processor 520 executes the program to perform the steps of any of the message notification processing methods as described above.
Based on the same inventive concept, according to another aspect of the present invention, as shown in fig. 6, an embodiment of the present invention further provides a computer-readable storage medium 601, where the computer-readable storage medium 601 stores computer program instructions 610, and the computer program instructions 610, when executed by a processor, perform the steps of any of the above message notification processing methods.
Finally, it should be noted that, as will be understood by those skilled in the art, all or part of the processes of the methods of the above embodiments may be implemented by a computer program to instruct related hardware to implement the methods. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), a Random Access Memory (RAM), or the like. The embodiments of the computer program may achieve the same or similar effects as any of the above-described method embodiments.
In addition, the apparatuses, devices, and the like disclosed in the embodiments of the present invention may be various electronic terminal devices, such as a mobile phone, a Personal Digital Assistant (PDA), a tablet computer (PAD), a smart television, and the like, or may be a large terminal device, such as a server, and the like, and therefore the scope of protection disclosed in the embodiments of the present invention should not be limited to a specific type of apparatus, device. The client disclosed by the embodiment of the invention can be applied to any one of the electronic terminal devices in the form of electronic hardware, computer software or a combination of the electronic hardware and the computer software.
Furthermore, the method disclosed according to an embodiment of the present invention may also be implemented as a computer program executed by a CPU, and the computer program may be stored in a computer-readable storage medium. The computer program, when executed by the CPU, performs the above-described functions defined in the method disclosed in the embodiments of the present invention.
Further, the above method steps and system elements may also be implemented using a controller and a computer readable storage medium for storing a computer program for causing the controller to implement the functions of the above steps or elements.
Further, it should be appreciated that the computer-readable storage media (e.g., memory) herein can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. By way of example, and not limitation, nonvolatile memory can include Read Only Memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM), which can act as external cache memory. By way of example and not limitation, RAM is available in a variety of forms such as synchronous RAM (DRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The storage devices of the disclosed aspects are intended to comprise, without being limited to, these and other suitable types of memory.
Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as software or hardware depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosed embodiments of the present invention.
The various illustrative logical blocks, modules, and circuits described in connection with the disclosure herein may be implemented or performed with the following components designed to perform the functions herein: a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination of these components. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP, and/or any other such configuration.
The steps of a method or algorithm described in connection with the disclosure herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.
In one or more exemplary designs, the functions may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes Compact Disc (CD), laser disc, optical disc, Digital Versatile Disc (DVD), floppy disk, blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
The foregoing is an exemplary embodiment of the present disclosure, but it should be noted that various changes and modifications could be made herein without departing from the scope of the present disclosure as defined by the appended claims. The functions, steps and/or actions of the method claims in accordance with the disclosed embodiments described herein need not be performed in any particular order. Furthermore, although elements of the disclosed embodiments of the invention may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.
It should be understood that, as used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly supports the exception. It should also be understood that "and/or" as used herein is meant to include any and all possible combinations of one or more of the associated listed items.
The numbers of the embodiments disclosed in the embodiments of the present invention are merely for description, and do not represent the merits of the embodiments.
It will be understood by those skilled in the art that all or part of the steps of implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
Those of ordinary skill in the art will understand that: the discussion of any embodiment above is meant to be exemplary only, and is not intended to intimate that the scope of the disclosure, including the claims, of embodiments of the invention is limited to these examples; within the idea of an embodiment of the invention, also technical features in the above embodiment or in different embodiments may be combined and there are many other variations of the different aspects of the embodiments of the invention as described above, which are not provided in detail for the sake of brevity. Therefore, any omissions, modifications, substitutions, improvements, and the like that may be made without departing from the spirit and principles of the embodiments of the present invention are intended to be included within the scope of the embodiments of the present invention.

Claims (10)

1. A message notification processing method, comprising the steps of:
receiving message subscription information and message notification content;
generating a message event by using the message notification content and the attribute parameter corresponding to the message notification content;
encapsulating the message event and the sending parameters corresponding to the message event into a message object;
adding the message object into a first queue;
and sending the message event in the message object in the first queue to a receiving end corresponding to the message subscription information, and updating the sending parameter in the message object.
2. The method of claim 1, wherein receiving message subscription information, further comprises:
judging the type of the message subscription information;
in response to the type being a subscription, adding the subscription information to a second queue;
in response to the type being unsubscribe, judging whether subscription information identical to the identifier in the subscription information exists in the second queue;
in response to there being a subscription message that is the same as the identifier in the subscription message, deleting the corresponding subscription message in the second queue.
3. The method of claim 2, wherein adding the message object to the first queue, further comprising:
assigning values to the sending parameters in the message objects;
judging whether the same message object exists in the first queue according to the identifier corresponding to the message event in the message object;
in response to the presence of the identical message object, replacing the identical message object in the first queue with the message object.
4. The method of claim 3, wherein sending the message event in the message object in the first queue to a receiver corresponding to the message subscription information, and updating a sending parameter in the message object, further comprises:
determining a receiving end corresponding to the message subscription information according to a preset mapping relation between an identifier in the subscription information and an identifier corresponding to a message event in the message object;
sending the message event to the receiving end according to a message notification mode in the message subscription information;
and updating the sending times and sending time in the message object.
5. The method of claim 4, further comprising:
judging whether the sending times of the message objects in the first queue reach preset sending times or not and the difference value between the first sending time and the last sending time reaches a preset difference value;
and in response to the sending times reaching a preset sending time and the difference reaching a preset difference, deleting the message object from the first queue.
6. A computer device, comprising:
at least one processor; and
a memory storing a computer program operable on the processor, wherein the processor executes the program to perform the steps of:
receiving message subscription information and message notification content;
generating a message event by using the message notification content and the attribute parameter corresponding to the message notification content;
encapsulating the message event and the sending parameters corresponding to the message event into a message object;
adding the message object into a first queue;
and sending the message event in the message object in the first queue to a receiving end corresponding to the message subscription information, and updating the sending parameter in the message object.
7. The computer device of claim 6, wherein receiving message subscription information further comprises:
judging the type of the message subscription information;
in response to the type being a subscription, adding the subscription information to a second queue;
in response to the type being unsubscribe, judging whether subscription information identical to the identifier in the subscription information exists in the second queue;
in response to there being a subscription message that is the same as the identifier in the subscription message, deleting the corresponding subscription message in the second queue.
8. The computer device of claim 7, wherein the message object is added to a first queue, further comprising:
assigning values to the sending parameters in the message objects;
judging whether the same message object exists in the first queue according to the identifier corresponding to the message event in the message object;
in response to the presence of the identical message object, replacing the identical message object in the first queue with the message object.
9. The computer device of claim 8, wherein sending the message event in the message object in the first queue to a recipient corresponding to the message subscription information and updating a sending parameter in the message object, further comprises:
determining a receiving end corresponding to the message subscription information according to a preset mapping relation between an identifier in the subscription information and an identifier corresponding to a message event in the message object;
sending the message event to the receiving end according to a message notification mode in the message subscription information;
and updating the sending times and sending time in the message object.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, is adapted to carry out the steps of the method of any one of claims 1 to 5.
CN201911251211.1A 2019-12-09 2019-12-09 Message notification processing method, device and storage medium Withdrawn CN111078430A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911251211.1A CN111078430A (en) 2019-12-09 2019-12-09 Message notification processing method, device and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911251211.1A CN111078430A (en) 2019-12-09 2019-12-09 Message notification processing method, device and storage medium

Publications (1)

Publication Number Publication Date
CN111078430A true CN111078430A (en) 2020-04-28

Family

ID=70313289

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911251211.1A Withdrawn CN111078430A (en) 2019-12-09 2019-12-09 Message notification processing method, device and storage medium

Country Status (1)

Country Link
CN (1) CN111078430A (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116095036A (en) * 2021-11-05 2023-05-09 中国石油天然气股份有限公司 Message notification method and device
WO2023143030A1 (en) * 2022-01-25 2023-08-03 武汉微智创大科技有限公司 Simple no-response communication method and apparatus

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116095036A (en) * 2021-11-05 2023-05-09 中国石油天然气股份有限公司 Message notification method and device
WO2023143030A1 (en) * 2022-01-25 2023-08-03 武汉微智创大科技有限公司 Simple no-response communication method and apparatus

Similar Documents

Publication Publication Date Title
US9401842B2 (en) Method and device for configuring terminal devices
KR101871383B1 (en) Method and system for using a recursive event listener on a node in hierarchical data structure
EP3656108B1 (en) Unstructured data storage function (udsf) services
US20160219125A1 (en) Method and apparatus for implementing subscription notification
US20190181901A1 (en) Local profile assistant and application programming interface
JP7130767B2 (en) Event monitoring method and apparatus
RU2494554C2 (en) Targeted queries using oma dm protocol
US20080201475A1 (en) Device Management Method Using Nodes Having Additional Attribute and Device Management Client Thereof
CN111078430A (en) Message notification processing method, device and storage medium
CN111708834A (en) Method, system, equipment and medium for synchronizing service configuration data
CN109167819B (en) Data synchronization system, method, device and storage medium
US9654547B2 (en) Method for enabling hierarchical architecture of device management gateways
CN107612753B (en) Wireless information processing method and device and wireless access equipment
US11533597B2 (en) Method for processing message in M2M system and device therefor
US10085175B2 (en) Load control method and apparatus for notification messages
CN111240933B (en) Method, system, device and medium for monitoring performance data of multiple data centers
CN115567388A (en) Method, system, device and storage medium for automatically updating network slice configuration
US10171285B2 (en) Proactive M2M framework using device-level vCard for inventory, identity, and network management
US20230083529A1 (en) Selection of service-providing network functions in a 3gpp communication network
CN111400327B (en) Data synchronization method and device, electronic equipment and storage medium
WO2021115464A1 (en) Network slice selection method and related device
CN104936199A (en) Resource notification management method and public service entity
CN103503358A (en) A method and an apparatus for message interaction of group resources
CN107113597B (en) System and method for providing service allowance aggregation on multiple device SIM cards
CN113824577B (en) Information processing method, related network equipment and storage 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
WW01 Invention patent application withdrawn after publication

Application publication date: 20200428

WW01 Invention patent application withdrawn after publication