A marine information push method supporting multiple platforms and multiple roles

Abstract

This invention discloses a method for pushing marine information across multiple platforms and roles, comprising the following steps: 1) receiving and classifying various types of business data; 2) converting the business data into a data structure that meets the business requirements of the push system; 3) constructing an information push platform and establishing corresponding push scenario templates according to different role characteristics and terminal types; 4) selecting scenario templates based on the target audience and content to be pushed, defining specific push content, and setting push rules including push time and push conditions, and sending the push content to the message server according to the relevant push rules; 5) when a user logs into the platform on various terminals, based on the role of the logged-in user's account, subscribing to corresponding topics based on different roles, receiving the corresponding information pushed by the server, and sending a receipt; the server ensures that the pushed user receives the information by receiving the receipt. This invention's method can quickly and accurately push various types of ship information to target users.

Description

Technical Field

[0001] This invention relates to ship communication technology, and more particularly to a shipboard information push method that supports multiple platforms and multiple roles. Background Technology

[0002] As the informatization and intelligence levels of ship equipment increase, more and more equipment is transitioning to intelligent and unmanned operation. Traditional shipboard communication methods are struggling to meet the needs of crew members for rapid and accurate information transmission. On the one hand, the emergence of shipboard wireless networks and mobile devices necessitates consideration of information transmission across different platforms. On the other hand, since shipboard operations are generally geared towards crew members, and each crew member's role corresponds to the information they should receive, information transmission for different roles needs to be considered. Therefore, a shipboard information push method that supports multiple platforms and roles is needed, capable of rapidly and accurately pushing various types of shipboard information to target users, enabling crew members to promptly grasp the necessary equipment and status information and carry out related work. Summary of the Invention

[0003] The technical problem to be solved by the present invention is to provide a method for pushing marine information that supports multiple platforms and multiple roles, in order to address the deficiencies in the prior art.

[0004] The technical solution adopted by this invention to solve its technical problem is: a method for pushing marine information that supports multiple platforms and multiple roles, comprising the following steps:

[0005] 1) Receive and classify various types of business data; the classification labels include business type and data format type, where business type includes ship navigation status, electromechanical inspection, equipment support and health management; data format type includes voice, video, image and text;

[0006] 2) Convert the business data into a data structure that meets the needs of the push system;

[0007] 3) Build an information push platform and establish corresponding push scenario templates according to different role characteristics and terminal types;

[0008] The push notification scenario template is created as follows:

[0009] The push scenario template includes the MessageTemplate table, the MessageTemplateDetail table, and the MessageTmpDetailMap table;

[0010] The MessageTemplate table is used to configure the basic content of the data template, including ID, template name, template type, and whether to configure a scenario details link.

[0011] The MessageTemplateDetail table is used to configure the content that a data template needs to present, including images, videos, text, and voice data that need to be presented in the scenario. It includes: ID, tmpId, systype attributes, and template association attributes. The content that the data template needs to present is bound according to the definition of the data business type. datatype and sub_datatype are based on the definition of the data format type corresponding to the business data and the definition of the data format type of the business sub-module. The paramBody attribute is used to configure the definition of the corresponding data format type when pushing data.

[0012] The MessageTmpDetailMap table is used to configure the association and binding relationship between scene templates and scene detail links;

[0013] 4) Select a scenario template based on the target audience and content to be pushed to, define the specific push content and set the corresponding push rules, including push time and push conditions, and send the push content to the message server in accordance with the relevant push rules;

[0014] The push rule structure is defined as follows:

[0015] The push rule structure includes the MessagPushRule table and the MessagePushRuleTarget table;

[0016] The `MessagPushRule` table is the entry point for configuring push rules. The `tmpId` attribute is the ID of the associated scenario template; the `ruleName` attribute is the name of the push rule displayed in the push console; `taregtType` indicates the target type to be pushed, categorized as role, user, or group; the `cron` attribute is the timed rule expression, which only takes effect when configured as a timed rule; and the `runStatus` attribute indicates the enabled status of the configured rule.

[0017] The MessagePushRuleTarget table is a push target association table used to configure the target users in push rules. Among them, messagePushruleid is the configured push rule ID, and messagepushtarget is the ID of the target user, including role ID, user ID or group ID. It is a push target association table.

[0018] 5) After a user logs into the platform using identity authentication technology on various terminals, the system subscribes to relevant topics based on the role permissions of the logged-in user's account, receives relevant information pushed by the server, and sends receipts.

[0019] The server ensures that the pushed information is received by the user by receiving a receipt; if the information is not successfully received, it will push it again.

[0020] According to the above scheme, in step 3), the constructed push scenario template needs to be adapted to different terminal platforms, including desktop, mobile applications and embedded pages.

[0021] According to the above scheme, in step 4), the message server is an EMQX message server based on the MQTT protocol.

[0022] The beneficial effects of this invention are:

[0023] 1. This invention establishes desktop, mobile, and embedded page templates to adapt to various push scenarios, enabling push notifications to multiple platform terminals that the same user can log in to with a single selection. Users can subscribe to messages on all types of platforms they log in to.

[0024] 2. This invention establishes push scenario templates and push rules, supporting push notifications in various ways such as custom groups and roles. It enables push notifications to multiple role users with a single selection. Based on the above multi-platform and multi-role push methods, various types of ship information can be quickly and accurately pushed to target users, making it easier for crew members to keep track of the necessary equipment and status information. Attached Figure Description

[0025] The present invention will be further described below with reference to the accompanying drawings and embodiments. In the accompanying drawings:

[0026] Figure 1 This is a flowchart of a method according to an embodiment of the present invention;

[0027] Figure 2 This is a schematic diagram of the scene template structure according to an embodiment of the present invention;

[0028] Figure 3 This is a schematic diagram of the push rule structure according to an embodiment of the present invention. Detailed Implementation

[0029] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the invention.

[0030] like Figure 1 As shown, a method for pushing marine information that supports multiple platforms and multiple roles includes the following steps:

[0031] 1) Receive and classify various types of business data; the classification labels include business type and data format type, where business type includes ship navigation status, electromechanical inspection, equipment support and health management; data format type includes voice, video, image and text;

[0032] 2) Convert the business data into a data structure that meets the needs of the push system;

[0033] 3) Build an information push platform and establish corresponding push scenario templates according to different role characteristics and terminal types. The push scenario templates must be compatible with different terminal platforms such as desktop, mobile applications and embedded pages.

[0034] The push notification scenario template is created as follows:

[0035] like Figure 2 The push scenario templates include the MessageTemplate table, the MessageTemplateDetail table, and the MessageTmpDetailMap table;

[0036] The MessageTemplate table is used to configure the basic content of the data template, including ID, template name, template type, and whether to configure a scenario details link.

[0037] The MessageTemplateDetail table is used to configure the content that a data template needs to present, including images, videos, text, and voice data that need to be presented in the scenario. It includes: ID, tmpId, systype attributes, and template association attributes. The content that the data template needs to present is bound according to the definition of the data business type. datatype and sub_datatype are based on the definition of the data format type corresponding to the business data and the definition of the data format type of the business sub-module. The paramBody attribute is used to configure the definition of the corresponding data format type when pushing data.

[0038] The MessageTmpDetailMap table is used to configure the association and binding relationship between scene templates and scene detail links;

[0039] 4) Select a scenario template based on the target audience and content to be pushed, define the specific push content and set the corresponding push rules, including push time and push conditions, and send the push content to the EMQX message server based on the MQTT protocol in accordance with the relevant push rules.

[0040] like Figure 3 The push rule structure is defined as follows:

[0041] The push rule structure includes the MessagPushRule table and the MessagePushRuleTarget table;

[0042] The `MessagPushRule` table is the entry point for configuring push rules. The `tmpId` attribute is the ID of the associated scenario template; the `ruleName` attribute is the name of the push rule displayed in the push console; `taregtType` indicates the target type to be pushed, categorized as role, user, or group; the `cron` attribute is the timed rule expression, which only takes effect when configured as a timed rule; and the `runStatus` attribute indicates the enabled status of the configured rule.

[0043] The MessagePushRuleTarget table is a push target association table used to configure the target users in push rules. Among them, messagePushruleid is the configured push rule ID, and messagepushtarget is the ID of the target user, including role ID, user ID or group ID. It is a push target association table.

[0044] 5) After a user logs into the platform using identity authentication technology on various terminals, the system subscribes to relevant topics based on the role permissions of the logged-in user's account, receives relevant information pushed by the server, and sends receipts.

[0045] The server ensures that the pushed information is received by the user by receiving a receipt; if the information is not successfully received, it will push it again.

[0046] It should be understood that those skilled in the art can make improvements or modifications based on the above description, and all such improvements and modifications should fall within the protection scope of the appended claims.

Claims

1. A method for pushing marine information that supports multiple platforms and multiple roles, characterized in that, Includes the following steps: 1) Receive and classify various types of business data; the classification labels include business type and data format type, where business type includes ship navigation status, electromechanical inspection, equipment support and health management; data format type includes voice, video, image and text; 2) Convert the business data into a data structure that meets the needs of the push system; 3) Build an information push platform and establish corresponding push scenario templates according to different role characteristics and terminal types; The push notification scenario template is created as follows: The push scenario template includes the MessageTemplate table, the MessageTemplateDetail table, and the MessageTmpDetailMap table; The MessageTemplate table is used to configure the basic content of the data template, including ID, template name, template type, and whether to configure a scenario details link. The MessageTemplateDetail table is used to configure the content that a data template needs to present, including images, videos, text, and voice data that need to be presented in the scenario. It includes: ID, tmpId, systype attributes, and template association attributes. The content that the data template needs to present is bound according to the definition of the data business type. datatype and sub_datatype are based on the definition of the data format type corresponding to the business data and the definition of the data format type of the business sub-module. The paramBody attribute is used to configure the definition of the corresponding data format type when pushing data. The MessageTmpDetailMap table is used to configure the association and binding relationship between scene templates and scene detail links; 4) Select a scenario template based on the target audience and content to be pushed to, define the specific push content and set the corresponding push rules, including push time and push conditions, and send the push content to the message server in accordance with the relevant push rules; 5) When a user logs into the platform on various terminals, based on the role permissions of the logged-in user's account, the user subscribes to the corresponding topics according to different roles, receives the corresponding information pushed by the server, and sends a receipt. The server ensures that the pushed information is received by the user by receiving a receipt; if the information is not successfully received, it will push it again.

2. The marine information push method supporting multiple platforms and multiple roles according to claim 1, characterized in that, In step 3), the constructed push scenario template needs to be adapted to different terminal platforms, including desktop, mobile applications and embedded pages.

3. The marine information push method supporting multiple platforms and multiple roles according to claim 1, characterized in that, In step 4), the message server is an EMQX message server based on the MQTT protocol.

4. The marine information push method supporting multiple platforms and multiple roles according to claim 1, characterized in that, In step 4), the push rule structure is defined as follows: The push rule structure includes the MessagPushRule table and the MessagePushRuleTarget table; The `MessagPushRule` table is the entry point for configuring push rules. The `tmpId` attribute is the ID of the associated scenario template; the `ruleName` attribute is the name of the push rule displayed in the push console; `taregtType` indicates the target type to be pushed, categorized as role, user, or group; the `cron` attribute is the timed rule expression, which only takes effect when configured as a timed rule; and the `runStatus` attribute indicates the enabled status of the configured rule. The MessagePushRuleTarget table is a push target association table used to configure the target users in push rules. Among them, messagePushruleid is the configured push rule ID, and messagepushtarget is the ID of the target user, including role ID, user ID, or group ID. It is a push target association table.

5. An electronic device, characterized in that, include: One or more processors; as well as Storage device for storing one or more programs. Wherein, when the one or more programs are executed by the one or more processors, the one or more processors perform the method according to any one of claims 1 to 4.

6. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method described in any one of claims 1 to 4.

Images