CN112328407A - Message transmission system suitable for coordination of development and management tasks of spacecraft - Google Patents

Message transmission system suitable for coordination of development and management tasks of spacecraft Download PDF

Info

Publication number
CN112328407A
CN112328407A CN202011127693.2A CN202011127693A CN112328407A CN 112328407 A CN112328407 A CN 112328407A CN 202011127693 A CN202011127693 A CN 202011127693A CN 112328407 A CN112328407 A CN 112328407A
Authority
CN
China
Prior art keywords
message
module
receiving
sending
registered
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.)
Pending
Application number
CN202011127693.2A
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.)
Beijing Institute of Spacecraft System Engineering
Original Assignee
Beijing Institute of Spacecraft System Engineering
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 Beijing Institute of Spacecraft System Engineering filed Critical Beijing Institute of Spacecraft System Engineering
Priority to CN202011127693.2A priority Critical patent/CN112328407A/en
Publication of CN112328407A publication Critical patent/CN112328407A/en
Pending 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
    • 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)
  • Information Transfer Between Computers (AREA)

Abstract

The application discloses a message transmission system suitable for coordination of spacecraft development management tasks, which comprises: the system comprises a message receiving module, a message registering module, a message scheduling module and a message sending module; the message receiving module is used for receiving unregistered message data sent by at least one message source according to a preset interface; the message registration module is connected with the message receiving module and used for adding registration information in the message data to obtain a registered message set; the message scheduling module is connected with the message registration module and is used for intensively adding the registered messages into a message queue for storing messages to be sent; and the message sending module is connected with the message scheduling module and used for reading the message set to be sent from the message queue and sending the message set to be sent to at least one message receiving end. The method and the device solve the technical problem that the prior art cannot effectively meet the actual message transmission requirements required by a collaborative scene of a spacecraft development management task.

Description

Message transmission system suitable for coordination of development and management tasks of spacecraft
Technical Field
The application relates to the technical field of spacecraft development management, in particular to a message transmission system suitable for coordination of spacecraft development management tasks.
Background
The development of the spacecraft is a complex system engineering, and needs to perform efficient task cooperation by taking development tasks as a core, adopting scientific development and management means and organizing and utilizing the advantage resources of various disciplines of each specialty. At present, the development and management work of the spacecraft is carried out by a comprehensive application informatization means, and various information facing development and management personnel, such as important item notification, to-be-done work reminding, service flow notification, early warning and alarming information and the like, can be generated by each software system along with the application process so as to meet the task collaborative management requirements of item extension, task issuing, progress tracking, closed-loop feedback, monitoring and management and the like in the development and management process of the spacecraft. Therefore, whether the message can be transmitted timely, reliably and safely becomes a key factor for restricting the task cooperative effect.
Based on the above background, a message passing system for cooperation of spacecraft development management tasks needs to satisfy the following five specificity requirements at the same time: firstly, the message transmission system needs to have universality, is not influenced by the difference of the existing system, and has universal application capability; secondly, the message transmission system needs to have low cost, the cost of system transformation is low, and the cost of message transmission process management is low; thirdly, the message transmission system needs to have strong controllability, and the message body, the message source, the message destination, the transmission link and the transmission time are required to be controllable; fourthly, the message transmission system needs to have high safety, and the transmitted sensitive information can be desensitized automatically and is not easy to steal and cannot be stolen; fifthly, the message transmission system needs to have traceability, and the message body and the message transmission process can be audited and traced.
At present, the existing message transmission system mainly includes the following steps that a data interface technology is adopted to realize point-to-point information transmission between systems, and a data bus technology is adopted to realize message transmission based on a bus between systems, wherein the data bus technology is adopted to realize message transmission based on the bus between the systems, and the main process of the system for message transmission is as follows: the unified receiving, route identification and unified sending of the messages to be sent are realized through the message bus. The message source side sends the message by calling the bus service and appoints the destination, the bus judges the routing relation according to the destination of the message, and calls the receiving service of the corresponding message receiver to finish the message distribution. The system can meet the requirements of universality and low cost, but cannot completely meet the requirements of strong controllability, high safety and traceability. Firstly, a message source side cannot be limited, a message transmission direction is pre-designated by a message sending side, message sending time is real-time sending, dynamic adjustment cannot be carried out in the transmission process, and strong controllability requirements cannot be met; secondly, the bus cannot perform desensitization processing on message contents and cannot completely meet the requirement of high safety; finally, the bus only forwards messages, the message body is not reserved, the process records of message receiving, routing and sending are insufficient, sufficient basis cannot be provided for message audit and tracing, and the requirement of traceability cannot be met. Therefore, the existing message transmission system cannot effectively meet the message transmission requirement required by a collaborative scene of a spacecraft development management task.
Disclosure of Invention
The technical problem that this application was solved is: aiming at the problem that the prior art can not effectively meet the actual message transmission requirements needed by a collaborative scene of a spacecraft development management task, the application provides a message transmission system suitable for coordination of the spacecraft development management task, in the scheme provided by the embodiment of the application, the message data of a message source received by a message receiving module is unregistered message data, then the unregistered message data is registered by a message registration module, namely, the message name, the message source, the message destination and the sending opportunity are added into the message data, namely, the message source does not set the message source, the message destination and the sending opportunity, but uniformly registers the received message data according to a preset message registration strategy by the message registration module, thereby realizing the controlled management of the message name, the message source, the message destination and the like, and greatly improving the controllability of message transmission, and further effectively meeting the actual message transmission requirements needed by the collaborative scene of the spacecraft development management task.
In a first aspect, an embodiment of the present application provides a message delivery system suitable for coordination of a spacecraft development management task, where the system includes: the system comprises a message receiving module, a message registering module, a message scheduling module and a message sending module; wherein,
the message receiving module is used for receiving unregistered message data sent by at least one message source according to a preset interface;
the message registration module is connected with the message receiving module and used for adding registration information in the message data according to a preset message registration strategy to obtain a registered message set, wherein the registration information comprises a message name, a message source, a message destination and a message sending opportunity;
the message scheduling module is connected with the message registration module and is used for adding the messages in the registered message set into a message queue for storing messages to be sent;
the message sending module is connected with the message scheduling module and used for reading a message set to be sent from the message queue and sending the message set to be sent to at least one message receiving end.
Optionally, the preset interface includes: RESTFUL interface, WebService interface, URL interface, SMTP interface.
Optionally, the message registration module is specifically configured to:
determining interface information for receiving each message data, and determining registration information corresponding to each message data according to a mapping relation between the interface information and the registration information;
and determining a message identifier according to the registration information, and adding the message identifier and the registration information to each message data to obtain the registered message set.
Optionally, the message scheduling module is specifically configured to: traversing and analyzing the unsent messages in the registered message set to obtain the message identification and the message destination;
judging whether any unsent message meets the sending opportunity or not according to the message identification and preset message registration information;
and if so, inserting any unsent message into the tail of the message queue.
Optionally, the message scheduling module is specifically configured to:
determining a message source of any unsent message, and determining a message queue corresponding to any unsent message according to a mapping relation between the message source and the message queue;
inserting the any unsent message to the end of the message queue.
Optionally, the message queue includes: MSMQ message queues, RabbitMQ message queues, and rockmq message queues.
Optionally, the method further comprises: a message processing module; the message processing module is arranged between the message registration module and the message scheduling module and is used for carrying out content inspection and desensitization processing on the registered messages in the message set to obtain inspected messages.
Optionally, the message processing module is specifically configured to:
performing content verification on the registered messages in the message set to obtain verified messages, wherein the content verification comprises verifying whether the messages are registered, whether a message receiving end exists, whether the message content exceeds a preset length or not or whether the message content contains preset characters;
desensitizing the verified message to obtain a desensitized message, wherein the desensitizing comprises performing fuzzy comparison on the verified message and a preset sensitive word bank to determine a sensitive word in the verified message, determining a public word corresponding to the sensitive word according to a preset mapping relation between the sensitive word and the public word, and replacing the sensitive word with the public word.
Optionally: a message monitoring and auditing module; the message monitoring and auditing module is used for receiving the data sent by the message receiving module, the message registering module, the message processing module and the message sending module, and performing message monitoring, message auditing and message tracing according to the data.
Compared with the prior art, the scheme provided by the embodiment of the application has the following beneficial effects:
1. in the scheme provided by the embodiment of the application, the message data of the message source received by the message receiving module is unregistered message data, and then the unregistered message data is registered by the message registering module, namely, the message name, the message source, the message destination and the sending time are added in the message data, namely, the message source does not set the message source, the message destination and the sending time, but uniformly registers the received message data through a preset message registering strategy according to the message registering module, so that the controlled management of the message name, the message source, the message destination and other contents is realized, the message transmission controllability is greatly improved, and the actual message transmission requirement required by a spacecraft development and management task collaborative scene is effectively met;
2. in the scheme provided by the embodiment of the application, the content inspection and desensitization processing is carried out on the registered message in the message set through the message processing module, namely the message content is verified and sensitive words in the message content are replaced through public words, so that the safety of message transmission is improved;
3. in the scheme provided by the embodiment of the application, the received message data, the process records of message receiving, routing and sending are reserved through the message monitoring and auditing module, and message monitoring, message auditing and message tracing are realized according to the reserved message data, the process records of message receiving, routing and sending, so that the requirement of message traceability is met.
Drawings
Fig. 1 is a schematic structural diagram of a message delivery system suitable for coordination of a spacecraft development management task according to an embodiment of the present application.
Detailed Description
In the solutions provided in the embodiments of the present application, the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In order to better understand the technical solutions, the technical solutions of the present application are described in detail below with reference to the drawings and specific embodiments, and it should be understood that the specific features in the embodiments and examples of the present application are detailed descriptions of the technical solutions of the present application, and are not limitations of the technical solutions of the present application, and the technical features in the embodiments and examples of the present application may be combined with each other without conflict.
Referring to fig. 1, a message delivery system suitable for spacecraft development management task coordination provided in an embodiment of the present application includes a message receiving module 11, a message registering module 12, a message scheduling module 13, and a message sending module 14; wherein,
the message receiving module 11 is configured to receive unregistered message data sent by at least one message source according to a preset interface;
the message registration module 12 is connected to the message receiving module 11, and configured to add registration information to the message data according to a preset message registration policy to obtain a registered message set, where the registration information includes a message name, a message source, a message destination, and a message sending time;
the message scheduling module 13 is connected to the message registering module 12, and configured to add the messages in the registered message set to a message queue storing messages to be sent;
the message sending module 14 is connected to the message scheduling module 13, and configured to read a message set to be sent from the message queue, and send the message set to be sent to at least one message receiving end.
In the solution provided in the embodiment of the present application, the message receiving module 11 may set a plurality of interfaces for receiving messages according to actual requirements. Specifically, there are various types of interfaces for receiving messages, and some examples are described below.
In a possible implementation manner, the preset interface includes: RESTFUL interface, WebService interface, URL interface, SMTP interface.
Further, in a possible implementation manner, the message registration module 12 is specifically configured to:
determining interface information for receiving each message data, and determining registration information corresponding to each message data according to a mapping relation between the interface information and the registration information;
and determining a message identifier according to the registration information, and adding the message identifier and the registration information to each message data to obtain the registered message set.
Specifically, in the scheme provided in the embodiment of the present application, the sending opportunity includes a time rule and a quantity rule, where the time rule includes three modes, namely real-time mode, timing mode and delay mode. The preset message registration strategy can be adjusted according to actual requirements.
Further, in a possible implementation manner, the message scheduling module 13 is specifically configured to:
traversing and analyzing the unsent messages in the registered message set to obtain the message identification and the message destination; judging whether any unsent message meets the sending opportunity or not according to the message identification and preset message registration information; and if so, inserting any unsent message into the tail of the message queue.
Further, in a possible implementation manner, the message scheduling module 13 is specifically configured to:
determining a message source of any unsent message, and determining a message queue corresponding to any unsent message according to a mapping relation between the message source and the message queue; inserting the any unsent message to the end of the message queue.
Further, in a possible implementation manner, the message queue includes: MSMQ message queues, RabbitMQ message queues, and rockmq message queues.
Further, in the solution provided in the embodiment of the present application, after receiving the message queue sent by the message scheduling module 13, the message sending module 14 sends the message in the message queue to at least one message receiving end. Specifically, the process of the message scheduling module 13 for sending the message includes: the method comprises the steps that a message sending agent and an adaptive sending service are used, wherein the message sending agent reads a message set to be sent from a message queue, traverses and analyzes the destination of a message, acquires the adaptive sending service, the adaptive sending service is related to a message receiving interface provided by a destination software system, and for different destination software systems, the adaptive sending service can be adapted for life only by customizing and expanding once; the adaptation sending service calls a message receiving interface corresponding to the software system to complete the message sending process.
Further, in order to improve the security of message delivery, in a possible implementation manner, the method further includes: a message processing module 15; the message processing module 15 is disposed between the message registering module 12 and the message scheduling module 13, and configured to perform content inspection and desensitization processing on the messages in the registered message set to obtain inspected messages.
In a possible implementation manner, the message processing module 15 is specifically configured to:
performing content verification on the registered messages in the message set to obtain verified messages, wherein the content verification comprises verifying whether the messages are registered, whether a message receiving end exists, whether the message content exceeds a preset length or not or whether the message content contains preset characters;
desensitizing the verified message to obtain a desensitized message, wherein the desensitizing comprises performing fuzzy comparison on the verified message and a preset sensitive word bank to determine a sensitive word in the verified message, determining a public word corresponding to the sensitive word according to a preset mapping relation between the sensitive word and the public word, and replacing the sensitive word with the public word.
In the scheme provided by the embodiment of the application, the message processing module 15 is used for performing content inspection and desensitization processing on the registered messages in the message set, namely, the message content is verified and sensitive words in the message content are replaced by public words, so that the message transmission safety is improved.
Further, in order to meet the traceability requirement, in a possible implementation manner, the system further includes: a message monitoring audit module 16; the message monitoring and auditing module 16 is configured to receive data sent by the message receiving module 11, the message registering module 12, the message processing module 15, and the message sending module 14, and perform message monitoring, message auditing, and message tracing according to the data.
Specifically, in the scheme provided in this embodiment of the present application, in a message transmission process, the message receiving module 11 sends message data of at least one message source received by the message receiving module to the message monitoring and auditing module 16, the message registering module 12 sends a registered message set to the message monitoring and auditing module 16, the message processing module 15 sends a message after verification processing to the message monitoring and auditing module 16, and the message sending module 14 sends message information in a message queue to the message monitoring and auditing module 16.
Further, after the message monitoring and auditing module 16 receives the message data of at least one message source, the registered message set, the checked and processed message and the message information in the message alignment column, the message monitoring and auditing module 16 performs message monitoring and auditing. Specifically, the message monitoring and auditing process includes: the method comprises the steps of message monitoring, message auditing and message tracing, wherein the message monitoring refers to a real-time monitoring service for providing on-the-road message sending progress, can be used for accurately positioning according to message identification, and can also be used for classified positioning according to rules such as message types, message sources and message destinations; the message audit refers to providing a list of messages which are waiting to be sent, sent and failed to be sent within a certain time range and a statistical result; the message tracing refers to inquiring the log information of the whole process from receiving to sending according to the message identification.
In the scheme provided by the embodiment of the application, the received message data, the process records of message receiving, routing and sending are reserved through the message monitoring and auditing module 16, and message monitoring, message auditing and message tracing are realized according to the reserved message data, the process records of message receiving, routing and sending, so that the requirement of message traceability is met.
To facilitate an understanding of the operation of the messaging system described above, the following briefly describes the processes of message registration, message processing, message scheduling, and message transmission by way of example.
Step 1, setting the interface type { I |0 is more than or equal to I and less than or equal to 1, wherein I belongs to Z }, and respectively representing WebService and SMTP from small to large.
And 2, setting an updating mode of the message { M |0 is more than or equal to M and less than or equal to 1, wherein M belongs to Z }, and respectively representing an increment mode and a coverage mode from small to large.
And 3, setting a state value { S |0 is less than or equal to S is less than or equal to 1, wherein S belongs to Z }, 0 represents a new addition, and 1 represents an end.
And step 4, after receiving the message data sent by at least one message source, if at least one message is a backlog with M ═ 0 in the message data, the message receiving module performs structural processing on the at least one message, wherein the structural processing includes setting a message Id, a message type, a message title, a message content, a generation time, and a state S (the value is 0).
Step 5, if at least one message is a message with the value of M ═ 0, the message receiving module performs structural processing on the at least one message, wherein the structural processing comprises setting of a message Id, a message type and a state S (the value is 1); since the state S of the at least one message is 1, that is, it indicates that the at least one message is completed, the message receiving module sends the at least one message to the message registration module, and performs step 8 in the message registration module.
And 6, after the message receiving module carries out structuring processing on the received messages, for any message with the state S of 0, which represents a newly added message, the message receiving module sends the message to the message registering module, and the step 8 is executed in the message registering module.
And 7, if at least one message is M-1, the message receiving module reports all current messages according to a certain period, and the reported message attributes comprise contents such as message Id, message type, message title, message content and generation time.
Step 8, after the message registration module receives the message data sent by the message receiving module through a preset interface, judging the type of the interface for receiving any message data according to the message type in the message data; if I is 0, the message is transmitted to the message MSMQ through the SOAP protocol interface, and if I is 1, the message is transmitted to the MSMQ message queue through the SMTP protocol interface.
And 9, reading the message in the MSMQ queue by the message sending component in the message scheduling module.
And step 10, the message sending module forwards the message in the MSMQ message queue to at least one message receiving end by using an XMPP protocol. Specifically, the IP address information corresponding to the user account of the message receiving end is pushed to each message receiving end.
In the scheme provided in the embodiment of the application, the message data of the message source received by the message receiving module 11 is unregistered message data, and then the unregistered message data is registered by the message registering module 12, that is, the message name, the message source, the message destination and the sending time are added to the message data, that is, the message source does not set the message source, the message destination and the sending time, but the received message data is uniformly registered by the message registering module 12 through a preset message registering policy, so that the controlled management of the contents of the message name, the message source, the message destination and the like is realized, the controllability of message transmission is greatly improved, and the actual requirement of message development required by a spacecraft management task collaborative scene is effectively met.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims (9)

1. A messaging system adapted for coordination of spacecraft development management tasks, comprising: the system comprises a message receiving module, a message registering module, a message scheduling module and a message sending module; wherein,
the message receiving module is used for receiving unregistered message data sent by at least one message source according to a preset interface;
the message registration module is connected with the message receiving module and used for adding registration information in the message data according to a preset message registration strategy to obtain a registered message set, wherein the registration information comprises a message name, a message source, a message destination and a message sending opportunity;
the message scheduling module is connected with the message registration module and is used for intensively adding the registered messages into a message queue for storing messages to be sent;
the message sending module is connected with the message scheduling module and used for reading a message set to be sent from the message queue and sending the message set to be sent to at least one message receiving end.
2. The system of claim 1, wherein the predetermined interface comprises: RESTFUL interface, WebService interface, URL interface, SMTP interface.
3. The system of claim 2, wherein the message registration module is specifically configured to:
determining interface information for receiving each message data, and determining registration information corresponding to each message data according to a mapping relation between the interface information and the registration information;
and determining a message identifier according to the registration information, and adding the message identifier and the registration information to each message data to obtain the registered message set.
4. The system of claim 3, wherein the message scheduling module is specifically configured to:
traversing and analyzing the unsent message set in the registered message set to obtain the message identification and the message destination;
judging whether any unsent message meets the sending opportunity or not according to the message identification and preset message registration information;
and if so, inserting any unsent message into the tail of the message queue.
5. The system of claim 4, wherein the message scheduling module is specifically configured to:
determining a message source of any unsent message, and determining a message queue corresponding to any unsent message according to a mapping relation between the message source and the message queue;
inserting the any unsent message to the end of the message queue.
6. The system of claim 5, wherein the message queue comprises: MSMQ message queues, RabbitMQ message queues, and rockmq message queues.
7. The system of any one of claims 1 to 6, further comprising: a message processing module; the message processing module is arranged between the message registration module and the message scheduling module and is used for carrying out content inspection and desensitization processing on the registered messages in the message set to obtain inspected messages.
8. The system of claim 7, wherein the message processing module is specifically configured to:
performing content verification on the registered messages in the message set to obtain verified messages, wherein the content verification comprises verifying whether the messages are registered, whether a message receiving end exists, whether the message content exceeds a preset length or not or whether the message content contains preset characters;
desensitizing the verified message to obtain a desensitized message, wherein the desensitizing comprises performing fuzzy comparison on the verified message and a preset sensitive word bank to determine a sensitive word in the verified message, determining a public word corresponding to the sensitive word according to a preset mapping relation between the sensitive word and the public word, and replacing the sensitive word with the public word.
9. The system of claim 8, further comprising: a message monitoring and auditing module; the message monitoring and auditing module is used for receiving the data sent by the message receiving module, the message registering module, the message processing module and the message sending module, and performing message monitoring, message auditing and message tracing according to the data.
CN202011127693.2A 2020-10-20 2020-10-20 Message transmission system suitable for coordination of development and management tasks of spacecraft Pending CN112328407A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011127693.2A CN112328407A (en) 2020-10-20 2020-10-20 Message transmission system suitable for coordination of development and management tasks of spacecraft

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011127693.2A CN112328407A (en) 2020-10-20 2020-10-20 Message transmission system suitable for coordination of development and management tasks of spacecraft

Publications (1)

Publication Number Publication Date
CN112328407A true CN112328407A (en) 2021-02-05

Family

ID=74310535

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011127693.2A Pending CN112328407A (en) 2020-10-20 2020-10-20 Message transmission system suitable for coordination of development and management tasks of spacecraft

Country Status (1)

Country Link
CN (1) CN112328407A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114896232A (en) * 2022-04-24 2022-08-12 重庆旅游云信息科技有限公司 Method for supporting data acquisition and cleaning of multi-type positioning hardware

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1635781A (en) * 2003-12-29 2005-07-06 北京中视联数字系统有限公司 A method for uniform processing of digital television receiver middleware messages
US20070266393A1 (en) * 2006-05-10 2007-11-15 Oracle International Corporation Method of optimizing propagation of non-persistent messages from a source database management system to a destination database management system
US20100122084A1 (en) * 2007-07-24 2010-05-13 Huawei Technologies Co., Ltd. Method, apparatus and system for registering new member in group key management
US20110059727A1 (en) * 2009-09-10 2011-03-10 Michael-Anthony Lisboa Simple Mobile Registration: A mechanism enabling people to use electronic mobile devices and their messaging capabilities-instead of the traditionally used personal computer-to sign-up or register in real time for access to services and applications delivered via mobile devices
CN105721623A (en) * 2016-01-22 2016-06-29 中国互联网络信息中心 Domain name shared registering method and system oriented to unified scheduling and management
CN106899412A (en) * 2017-03-30 2017-06-27 北京链银博科技有限责任公司 A kind of block chain method for secret protection, apparatus and system
US20180109648A1 (en) * 2016-10-14 2018-04-19 Canon Kabushiki Kaisha Message execution server and control method

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1635781A (en) * 2003-12-29 2005-07-06 北京中视联数字系统有限公司 A method for uniform processing of digital television receiver middleware messages
US20070266393A1 (en) * 2006-05-10 2007-11-15 Oracle International Corporation Method of optimizing propagation of non-persistent messages from a source database management system to a destination database management system
US20100122084A1 (en) * 2007-07-24 2010-05-13 Huawei Technologies Co., Ltd. Method, apparatus and system for registering new member in group key management
US20110059727A1 (en) * 2009-09-10 2011-03-10 Michael-Anthony Lisboa Simple Mobile Registration: A mechanism enabling people to use electronic mobile devices and their messaging capabilities-instead of the traditionally used personal computer-to sign-up or register in real time for access to services and applications delivered via mobile devices
CN105721623A (en) * 2016-01-22 2016-06-29 中国互联网络信息中心 Domain name shared registering method and system oriented to unified scheduling and management
US20180109648A1 (en) * 2016-10-14 2018-04-19 Canon Kabushiki Kaisha Message execution server and control method
CN106899412A (en) * 2017-03-30 2017-06-27 北京链银博科技有限责任公司 A kind of block chain method for secret protection, apparatus and system

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114896232A (en) * 2022-04-24 2022-08-12 重庆旅游云信息科技有限公司 Method for supporting data acquisition and cleaning of multi-type positioning hardware
CN114896232B (en) * 2022-04-24 2023-05-23 重庆旅游云信息科技有限公司 Method for supporting multi-type positioning hardware data acquisition and cleaning

Similar Documents

Publication Publication Date Title
CN110113381B (en) Method and device for subscribing theme in block chain
US10492039B1 (en) State-based electronic message management systems and controllers
CN106210099B (en) Data processing system and method
CN111371892A (en) High-concurrency distributed message pushing system and method
WO2021190087A1 (en) Task execution method, device and system, and server
CN106059892A (en) Message engine integrated with communication system
CN111240862A (en) Universal interface platform and data conversion method
CN113723840B (en) Internet of vehicles scene calculation method, device and system
CN111901308B (en) Information interaction method
CN104636211A (en) Information interaction method among software systems, and middleware system
CN112328407A (en) Message transmission system suitable for coordination of development and management tasks of spacecraft
US20080103862A1 (en) Instant messaged forms based business process decision point facilitation
EP1574980A1 (en) Context objects for accessing message content
CN109873720A (en) A kind of cloud center intelligence O&M method and system based on enterprise's public platform
CN111698310B (en) Multi-test environment scheduling method and device based on SWIFT network
CN108063803B (en) Message management method and system based on distributed subscription and publication message system
US8224771B2 (en) Resource sharing for document production
CN110943921B (en) Intelligent route configuration method
US20050155035A1 (en) Information kit objects for publish/subscribe integration architecture
EP1560137A1 (en) Technique for reliable message confirmation
CN113285855B (en) Server monitoring method and system
CN113298331B (en) Work order processing method, device and system and electronic equipment
CN115589394B (en) Mailbox-based data processing method, device, equipment and storage medium
CN111478945B (en) Pumped storage operation and inspection data processing system and method
KR20010047202A (en) Server system having function for changing personal information using internet and method thereof

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