CN117834723A - Message pushing method, system and device - Google Patents
Message pushing method, system and device Download PDFInfo
- Publication number
- CN117834723A CN117834723A CN202410008846.3A CN202410008846A CN117834723A CN 117834723 A CN117834723 A CN 117834723A CN 202410008846 A CN202410008846 A CN 202410008846A CN 117834723 A CN117834723 A CN 117834723A
- Authority
- CN
- China
- Prior art keywords
- application system
- message
- target
- pushing
- public api
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 78
- 230000009191 jumping Effects 0.000 claims abstract description 7
- 238000004590 computer program Methods 0.000 claims description 18
- 238000003860 storage Methods 0.000 claims description 17
- 238000012795 verification Methods 0.000 claims description 12
- 238000012545 processing Methods 0.000 abstract description 25
- 230000000694 effects Effects 0.000 abstract description 3
- 238000004891 communication Methods 0.000 description 14
- 238000010586 diagram Methods 0.000 description 11
- 230000006870 function Effects 0.000 description 11
- 230000008569 process Effects 0.000 description 11
- 230000005540 biological transmission Effects 0.000 description 7
- 230000003993 interaction Effects 0.000 description 5
- 230000007246 mechanism Effects 0.000 description 5
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000010365 information processing Effects 0.000 description 3
- 230000002452 interceptive effect Effects 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 230000008901 benefit Effects 0.000 description 2
- 239000007795 chemical reaction product Substances 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 230000010354 integration Effects 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 239000000047 product Substances 0.000 description 2
- 230000000750 progressive effect Effects 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 108010001267 Protein Subunits Proteins 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000001364 causal effect Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000002354 daily effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 230000003203 everyday effect Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The application provides a message pushing method, a system and a device, and relates to the technical field of mobile interconnection, wherein the method comprises the following steps: the public API platform receives a target message sent by an accessed first application system; the public API platform stores the target message in a message center module; determining whether a pushing opportunity of the target message is reached; under the condition that the pushing time for reaching the target message is determined, pushing the target message to a target application system in the target terminal by the public API platform in a message window card mode for displaying, wherein the target application system is a second application system accessed to the public API platform, and jumping to the first application system through triggering the message window card displayed in the second application system. The technical problems that the existing multi-application system operates independently, frequent switching is needed, and the message processing efficiency is low are solved, and the technical effect of effectively improving the message processing efficiency of the multi-application system is achieved.
Description
Technical Field
The application belongs to the technical field of mobile interconnection, and particularly relates to a message pushing method, a system and a device.
Background
Currently, there are many management systems and business systems within an enterprise, and these systems are typically developed independently with user system portals, for example: the user enters a background system to process daily information to be handled, enters an OA system to process approval flow, enters a travel system to process reimbursement, enters a human resource system to process attendance tasks and the like. Independent development tends to lead to frequent switching among multiple systems, difficulty in timely processing information of each system, and low information processing efficiency due to the need of switching among the multiple systems. And each system has a user authentication system and a message notification mechanism, which results in lower circulation efficiency of internal information and lower information processing efficiency.
In view of the above problems, no effective solution has been proposed at present.
Disclosure of Invention
The application aims to provide a message pushing method, a system and a device, which can effectively improve the processing efficiency of messages in a multi-application system.
The application provides a message pushing method, a system and a device, which are realized in the following way:
a message pushing method, comprising:
The public API platform receives a target message sent by an accessed first application system;
the public API platform stores the target message in a message center module;
determining whether a pushing opportunity of the target message is reached;
under the condition that the pushing time for the target message is determined, the public API platform pushes the target message to a target application system in a target terminal in a message window card mode for displaying, wherein the target application system is a second application system accessed to the public API platform, and the target application system jumps to the first application system through triggering the message window card displayed in the second application system.
In one embodiment, jumping to the first application system by triggering the message window card displayed in the second application system includes:
receiving triggering operation of a user on the message window card displayed in the second application system;
responding to the triggering operation, and sending user information required by authentication to an authentication center by the second application system;
the authentication center performs user authentication according to the user information, and returns a token to the second application system after the authentication is passed;
The second application system sends authentication information carrying a token to the authentication center;
the authentication center verifies the token in the authentication information, and after the verification is passed, an authentication bill is returned to the second application system;
the second application system transmits the authentication ticket to the first application system;
the first application system sends a secret key and an authentication bill to the authentication center;
and the authentication center verifies the secret key and the authentication bill, and returns a token to the first application system after the verification is passed so as to jump to the first application system.
In one embodiment, before the public API platform receives the target message sent by the accessed first application system, the method further includes:
the public API platform receives an access application sent by the first application system;
responding to the access application, the public API platform distributes an access identifier and an access password for the first application system;
after the allocation is completed, the first application system is recorded in an application system list as an application system to which access is allowed.
In one embodiment, in the case of determining a pushing opportunity reaching the target message, the public API platform pushes the target message to a target application system in a target terminal in a message window card manner for display, where the method includes:
Under the condition that the pushing time reaching the target message is determined, acquiring the user identification of the target message;
taking the user identified by the user identification as a target user;
determining a set of application systems associated with the target user that are permitted to access the public API platform;
determining an application system in which a target user in each application system in an application set is in a login state currently;
taking an application system of which the target user is in a login state currently as a target application;
and pushing the target message to a target application system in the target terminal by the public API platform in a message window card mode for display.
In one embodiment, determining whether a push opportunity for the target message is reached includes:
extracting an emergency identifier from the target message;
determining a pushing opportunity reaching the target message under the condition that the emergency identifier indicates that the target message is an emergency message;
determining whether the current time point is a preset push time point or not under the condition that the emergency identifier indicates the target message to be a non-emergency message;
and under the condition that the current time point is determined to be a preset pushing time point, determining the pushing time for reaching the target message.
A message push system, comprising: public API platform, first application system and second application system, wherein:
the first application system and the second application system access the public API platform;
the public API platform receives a target message sent by the first application system and stores the target message in a message center module; and under the condition that the pushing time of the target message is reached, pushing the target message to a second application system in a target terminal by the public API platform in a message window card mode for display, and jumping to the first application system by triggering the message window card displayed in the second application system.
A message pushing device, located in a public API platform, comprising:
the receiving module is used for receiving a target message sent by a first application system accessed to the public API platform;
a storage module for storing the target message in a message center module;
the determining module is used for determining whether the pushing time of the target message is reached;
the pushing module is used for pushing the target message to a target application system in a target terminal in a message window card mode for displaying under the condition that the pushing time of the target message is determined, wherein the target application system is a second application system accessed to the public API platform, and the target application system jumps to the first application system through triggering the message window card displayed in the second application system.
An electronic device comprising a processor and a memory for storing processor-executable instructions, which when executed by the processor implement the steps of the above-described method.
A computer readable storage medium having stored thereon a computer program/instruction which when executed by a processor performs the steps of the above method.
A computer program product comprising computer programs/instructions which when executed by a processor implement the steps of the above method.
According to the message pushing method, system and device, the public API platform receives the target message sent by the accessed first application system, and pushes the target message to the target application system in the target terminal in the mode of a message window card for display under the condition that the pushing time of the target message is confirmed, wherein the target application system is a second application system accessed to the public API platform, and the first application system is skipped through triggering the message window card displayed in the second application system. The method and the device have the advantages that through the arrangement of the public API platform, rapid jump among the multiple application systems can be realized, the technical problems that the existing multiple application systems independently operate and are required to be frequently switched and the message processing efficiency is too low are solved, and the technical effect of effectively improving the message processing efficiency of the multiple application systems is achieved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments described in the present application, and that other drawings may be obtained according to these drawings without inventive effort to a person skilled in the art.
FIG. 1 is a method flow diagram of one embodiment of a message pushing method provided herein;
FIG. 2 is a flowchart providing steps for interactive control of multiple application systems;
FIG. 3 is an interactive schematic diagram provided herein for verifying applications;
fig. 4 is a hardware block diagram of an electronic device according to a message pushing method provided in the present application;
fig. 5 is a schematic block diagram of an embodiment of a message pushing device provided in the present application.
Detailed Description
In order to better understand the technical solutions in the present application, the following description will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, shall fall within the scope of the present application.
If multiple business systems are stored in an enterprise, for example: attendance systems, office systems, etc., then the user needs to repeatedly switch between multiple systems when he wants to know the messages of each system. Based on this, in this example, considering that a common API (Application Programming Interface ) platform may be set, after the user passes through the unified user system authentication, the user may receive the message card pushed by other application systems through the current application system, and jump to these other application systems by clicking the message card to be processed, so as to implement the processing of the message and the flow.
Based on this, in this example, a message pushing system is provided, which may include: the system comprises a public API platform, a first application system and a second application system, wherein the first application system and the second application system are connected to the public API platform, and the public API platform receives a target message sent by the first application system and stores the target message in a message center module; and under the condition that the pushing time of the target message is reached, pushing the target message to a second application system in a target terminal by the public API platform in a message window card mode for display, and jumping to the first application system by triggering the message window card displayed in the second application system.
Fig. 1 is a method flowchart of an embodiment of a message pushing method provided in the present application. Although the present application provides a method operation step or apparatus structure as shown in the following examples or figures, more or fewer operation steps or module units may be included in the method or apparatus based on routine or non-inventive labor. In the steps or structures where there is no necessary causal relationship logically, the execution order of the steps or the module structure of the apparatus is not limited to the execution order or the module structure shown in the drawings and described in the embodiments of the present application. The described methods or module structures may be implemented sequentially or in parallel (e.g., in a parallel processor or multithreaded environment, or even in a distributed processing environment) in accordance with the embodiments or the method or module structure connection illustrated in the figures when implemented in a practical device or end product application.
Specifically, as shown in fig. 1, the message pushing method may include the following steps:
step 101: the public API platform receives a target message sent by an accessed first application system;
that is, for the public API platform, a plurality of application systems may be accessed, for example, if the public API platform is internal to an enterprise, an OA system of the enterprise, an attendance system of the enterprise, a financial system of the enterprise, an office system of the enterprise, etc., all of which may access the public API platform.
Step 102: the public API platform stores the target message in a message center module;
the public API platform is used as the transfer of the messages, the accessed application system can transmit the messages which need to be touched to the user to the API platform, and the API platform can be provided with a message center module for storing the messages and distributing the messages at a proper time point.
Step 103: determining whether a pushing opportunity of the target message is reached;
step 104: under the condition that the pushing time for the target message is determined, the public API platform pushes the target message to a target application system in a target terminal in a message window card mode for displaying, wherein the target application system is a second application system accessed to the public API platform, and the target application system jumps to the first application system through triggering the message window card displayed in the second application system.
Specifically, when determining the target application system, the application in the login state of the user can be considered as the target application system, so that the user can see the information more quickly. Specifically, the user identifier of the target message may be obtained under the condition that the pushing opportunity reaching the target message is determined; taking the user identified by the user identification as a target user; determining a set of application systems associated with the target user that are permitted to access the public API platform; determining an application system in which a target user in each application system in an application set is in a login state currently; taking an application system of which the target user is in a login state currently as a target application; and pushing the target message to a target application system in the target terminal by the public API platform in a message window card mode for display. When the method is implemented, if a plurality of application systems in a login state are determined, message window cards can be pushed to all the application systems, if only one application system in the login state exists, message window cards are pushed to the application system, if no application system in the login state exists currently, one or more application systems which are most likely to be logged in preferentially in future time of a user can be determined as target application systems under the condition that the user history logs in the application systems.
When the message window card is triggered to jump to the first application system, because the second application system is in a login state, identity verification needs to be performed on the second application system, and for this purpose, the triggering of the message window card displayed in the second application system to jump to the first application system may include:
s1: receiving triggering operation of a user on the message window card displayed in the second application system;
s2: responding to the triggering operation, and sending user information required by authentication to an authentication center by the second application system;
s3: the authentication center performs user authentication according to the user information, and returns a token to the second application system after the authentication is passed;
s4: the second application system sends authentication information carrying a token to the authentication center;
s5: the authentication center verifies the token in the authentication information, and after the verification is passed, an authentication bill is returned to the second application system;
s6: the second application system transmits the authentication ticket to the first application system;
s7: the first application system sends a secret key and an authentication bill to the authentication center;
S8: and the authentication center verifies the secret key and the authentication bill, and returns a token to the first application system after the verification is passed so as to jump to the first application system.
Further, for each application system, the public API platform may be accessed, for example, before the public API platform receives the target message sent by the accessed first application system, the public API platform receives the access application sent by the first application system (or may be the second application system, or other application systems); responding to the access application, the public API platform distributes an access identifier and an access password for the first application system; after the allocation is completed, the first application system is recorded in an application system list as an application system to which access is allowed. For multiple application systems accessing the public API, access control is also required, and when access control is performed, client_id (access identifier) and client_seclet (access password) allocated by the public API platform may be used to ensure that only authorized application systems can access the public API, and further, access control may also be performed on the application systems by means of an IP whitelist, an API key, token, and the like.
When determining whether the pushing time of the target message is reached, extracting an emergency identifier from the target message; determining a pushing opportunity reaching the target message under the condition that the emergency identifier indicates that the target message is an emergency message; determining whether the current time point is a preset push time point or not under the condition that the emergency identifier indicates the target message to be a non-emergency message; and under the condition that the current time point is determined to be a preset pushing time point, determining the pushing time for reaching the target message. The above-mentioned method is an active push method, when implementing, the second application system may also actively pull the user message to the message center module (i.e. receive the pull message request of the second application system, determine the push time reaching the target message), and then display the message to be processed of each first application system in card form. When the method is implemented, the message center module can also be used for actively pushing the message to the user, namely, when the service application system has an urgent message (whether the urgent mark is set in the message to judge whether the message is an urgent message) to be processed, the message center module can be used for actively pushing the message to the user, so that the urgent message can reach the user at the first time, and the message is displayed on the user side in the form of a message card.
The above method is described below in connection with a specific embodiment, however, it should be noted that this specific embodiment is only for better illustrating the present application and is not meant to be a undue limitation on the present application.
Along with the continuous improvement of the informatization degree of enterprises, various management systems and application systems inside the enterprises are more and more, data interaction and information sharing are often required to be carried out among the systems, development and maintenance of the systems are generally carried out by different departments and institutions, each system is provided with a user authentication system and a message notification mechanism, and therefore the information circulation efficiency inside the enterprises is low and the information processing efficiency is low. Meanwhile, the user needs to switch between different systems, so that inconvenience is brought to the user in use. Switching between multiple business systems necessarily results in a reduction in work efficiency if the user is an enterprise employee.
Considering the problems, the lack of unified data exchange standard and information sharing standard among the systems results in unsmooth data interaction and information sharing; because of different authentication mechanisms among different systems, the user needs to perform repeated login operation among different application systems, and the user experience is reduced; because the message notification mechanisms between the application systems are not uniformly managed, the internal message notification systems lack integration and push technology, which results in low information circulation efficiency and low processing efficiency.
Based on the above, in this example, a plurality of application systems are accessed to a common API platform, so as to realize data interaction and information sharing between the systems, and further, by setting a message center on the side of the common API platform as a central node for information transmission and pushing, when the associated application system has important notification or reminding information to reach a user, the associated application system can call an API to send. And a unified message pushing mechanism can be provided, after the notification message or the reminding message reaches the message center, the message can be uniformly pushed to the APP currently in a login state by the staff or the APP preset by the staff (for example, the enterprise application system that the staff is continuously online every day), and the message can be displayed in the form of a chat window card during pushing.
Specifically, in this example, a public API platform accessible to each application system is provided, where the public API platform accessed by the message may include: URI, HTTP actions, and status codes of the resource, etc. For example, the interface design of the public API for message access may be as shown in table 1 below, including: interface information, header parameter description, parameter description.
TABLE 1
For the public API platform, a plurality of possible authentication manners may be set, for example, including: the authentication method of the user name and the password, the authentication method based on Token, and the like, specifically, can be selected according to actual requirements, and the application is not limited to this. Furthermore, access control is also required for a plurality of application systems accessing the public API, and when access control is performed, client_id and client_seclet allocated by the public API platform can be used to ensure that only authorized application systems can access the public API, and further access control can be performed on the application systems by means of an IP whitelist, an API key, a Token and the like.
Given that upgrades and updates exist for multiple applications being accessed, there is also a need to periodically version control the public API to determine efficient and stable access for multiple applications. Further, detailed documents and test tools can be set to ensure that the accuracy and stability of the API are ensured in the process of developing and testing the public API by a developer. And the public API can be managed and monitored, for example, statistics of usage and error log monitoring can be performed.
In the case of performing interactive control on a plurality of application systems, as shown in fig. 2, the method may include the following steps:
(1) each business application system submits an access application to a public API platform, and the platform distributes client_ID and client_SECRET for each application system in response to the access application, and after distribution is completed, the application systems are allowed to access the public API platform.
(2) The service application system adds information such as encryption, authentication and the like into the message header according to a preset interface access standard so as to send service messages, for example: leave messages, travel messages, etc.
(3) The public API platform authenticates the interface for sending the service message, and after the parameter verification is passed, the received service message is stored in the message center module.
(4) After a user logs in to an enterprise communication APP end or a WEB end (may be a central communication application, for example, an enterprise communication APP, or may be an APP in which the identified user is currently in a login state), the user message may be actively pulled to the message center module, and then, the message to be processed of each service application system is displayed in a card form, which may be considered as an active pulling mode. When the method is implemented, a mode of actively pushing by the message center module can also be adopted, namely, when the service application system has an urgent message (whether the urgent message is an urgent message or not can be judged by setting an urgent mark in the message) to be processed, the message center module can actively push the message to a user so that the urgent message can reach the user at the first time, and the message is displayed on a user side in a message card form.
That is, after the application system needing to be accessed calls the public API, the message can reach the message center module, the message center module distributes the message to reach the user side, and after the user side receives the message through the mobile phone and other devices, the message is displayed in a unified message window in the form of a card. Thus, for a user, a unified enterprise application portal may be used, and clicking on a card may process messages from different external application systems.
(5) The user clicks the message card, the APP end can automatically jump to the service application system corresponding to the message, and the security authentication is carried out on the user for the service application system.
The application system receiving the push message is used as a first application system, the application system generating the push message is used as a second application system, the second application system pushes the message to a message center module through a public API, the message center module pushes the message to the first application system through the public API, the first application system displays the message in a message card mode, and a user can jump to the second application system after clicking the card by the first application system.
Upon jumping to the second application system, security authentication may be performed as shown in fig. 3:
the method comprises the steps that a first application system sends user information required for authentication to a unified user authentication center on a public API side, the unified user authentication center carries out user authentication and returns a token to the first application system, the first application system sends authentication information carrying the token to the unified user authentication center to replace the token, the unified user authentication center verifies the token and verifies resource authority, after the authentication is passed, the token is returned, the first application system jumps to a second application system carrying the token, the second application system sends an assigned key to the unified user authentication center and an instruction of replacing the token by the token, the unified user authentication center verifies the key and the token, and after the authentication is passed, the unified user authentication center returns the token information to the second application system to realize the jump.
The unified user authentication center is arranged on the public API side and is used as an identity authentication system shared by all accessed application systems, the unified user authentication communication compares information adopted by user login with information in a user information base to realize login authentication of the user, if the authentication is passed, a unified authentication mark ticket is generated and returned to the user, and the unified user authentication center can identify and extract ticket information to realize verification.
(6) And after the authentication is successful, returning token and related user information to the service application system for sending the message so as to successfully jump to a message processing page of the service application system for sending the message.
By the mode of the embodiment, unified message access of each service system can be realized, so that the message is finally contacted with a user, the efficiency of a plurality of application systems in collaborative office is improved, various management systems and application systems in enterprises are accessed and integrated through a common API platform, and data interaction and information sharing among the systems are uniformly managed, so that message notification integration and pushing in the enterprises are realized. And the common APP is taken as an entrance, after the user passes the authentication of the unified user system, the user receives the message card pushed by other systems, and the user can jump to the application system for sending the message for processing by clicking the message card to be processed. Furthermore, a multi-factor authentication mode can be adopted, for example, joint authentication can be performed by means of enterprise user names, mobile phone numbers, passwords, verification codes and the like.
The method embodiments provided in the above embodiments of the present application may be performed in a mobile terminal, a computer terminal or similar computing device. Taking the example of running on an electronic device, fig. 4 is a block diagram of a hardware structure of the electronic device of a message pushing method provided in the present application. As shown in fig. 4, the electronic device 10 may include one or more (only one is shown in the figure) processors 02 (the processors 02 may include, but are not limited to, a microprocessor MCU or a processing device such as a programmable logic device FPGA), a memory 04 for storing data, and a transmission module 06 for communication functions. It will be appreciated by those of ordinary skill in the art that the configuration shown in fig. 4 is merely illustrative and is not intended to limit the configuration of the electronic device described above. For example, the electronic device 10 may also include more or fewer components than shown in FIG. 4, or have a different configuration than shown in FIG. 4.
The memory 04 may be used to store software programs and modules of application software, such as program instructions/modules corresponding to the message pushing method in the embodiment of the present application, and the processor 02 executes the software programs and modules stored in the memory 04, thereby executing various functional applications and data processing, that is, implementing the message pushing method of the application program. Memory 04 may include high-speed random access memory, but may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, memory 04 may further include memory located remotely from processor 02, which may be connected to electronic device 10 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The transmission module 06 is used for receiving or transmitting data via a network. Specific examples of the network described above may include a wireless network provided by a communications provider of the electronic device 10. In one example, the transmission module 06 includes a network adapter (Network Interface Controller, NIC) that can connect to other network devices through a base station to communicate with the internet. In one example, the transmission module 06 may be a Radio Frequency (RF) module, which is used to communicate with the internet in a wireless manner.
At the software level, as shown in fig. 5, the message pushing device may be located in a public API platform, and includes:
a receiving module 501, configured to receive a target message sent by a first application system accessing the public API platform;
a storage module 502, configured to store the target message in a message center module;
a determining module 503, configured to determine whether a pushing opportunity of the target message is reached;
and the pushing module 504 is configured to push the target message to a target application system in a target terminal for display in a message window card manner when determining that the pushing time of the target message arrives, where the target application system is a second application system accessing the public API platform, and skip to the first application system by triggering the message window card displayed in the second application system.
In one embodiment, the triggering of the message window card displayed in the second application system to jump to the first application system may include: receiving triggering operation of a user on the message window card displayed in the second application system; responding to the triggering operation, and sending user information required by authentication to an authentication center by the second application system; the authentication center performs user authentication according to the user information, and returns a token to the second application system after the authentication is passed; the second application system sends authentication information carrying a token to the authentication center; the authentication center verifies the token in the authentication information, and after the verification is passed, an authentication bill is returned to the second application system; the second application system transmits the authentication ticket to the first application system; the first application system sends a secret key and an authentication bill to the authentication center; and the authentication center verifies the secret key and the authentication bill, and returns a token to the first application system after the verification is passed so as to jump to the first application system.
In one embodiment, before the public API platform receives the target message sent by the accessed first application system, the method further includes: the public API platform receives an access application sent by the first application system; responding to the access application, the public API platform distributes an access identifier and an access password for the first application system; after the allocation is completed, the first application system is recorded in an application system list as an application system to which access is allowed.
In one embodiment, in the case of determining the pushing time for reaching the target message, the public API platform pushes the target message to a target application system in a target terminal in a message window card manner for display, and may include: under the condition that the pushing time reaching the target message is determined, acquiring the user identification of the target message; taking the user identified by the user identification as a target user; determining a set of application systems associated with the target user that are permitted to access the public API platform; determining an application system in which a target user in each application system in an application set is in a login state currently; taking an application system of which the target user is in a login state currently as a target application; and pushing the target message to a target application system in the target terminal by the public API platform in a message window card mode for display.
In one embodiment, the determining module 503 may specifically extract the emergency identifier from the target message; determining a pushing opportunity reaching the target message under the condition that the emergency identifier indicates that the target message is an emergency message; determining whether the current time point is a preset push time point or not under the condition that the emergency identifier indicates the target message to be a non-emergency message; and under the condition that the current time point is determined to be a preset pushing time point, determining the pushing time for reaching the target message.
The target terminal can be terminal equipment or software operated and used by a user. Specifically, the target terminal may be a terminal device such as a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart watch, or other wearable devices. Of course, the target terminal may be software that can be executed in the terminal device. For example: application software such as an enterprise communication application, an enterprise office application, or a browser.
The embodiment of the application also provides a specific implementation manner of the electronic device, which can realize all the steps in the message pushing method in the embodiment, and the electronic device specifically comprises the following contents: a processor (processor), a memory (memory), a communication interface (Communications Interface), and a bus; the processor, the memory and the communication interface complete communication with each other through the bus; the processor is configured to invoke the computer program in the memory, where the processor executes the computer program to implement all the steps in the message pushing method in the foregoing embodiment, for example, the processor executes the computer program to implement the following steps:
Step 1: the public API platform receives a target message sent by an accessed first application system;
step 2: the public API platform stores the target message in a message center module;
step 3: determining whether a pushing opportunity of the target message is reached;
step 4: under the condition that the pushing time for the target message is determined, the public API platform pushes the target message to a target application system in a target terminal in a message window card mode for displaying, wherein the target application system is a second application system accessed to the public API platform, and the target application system jumps to the first application system through triggering the message window card displayed in the second application system.
The embodiments of the present application also provide a computer-readable storage medium capable of implementing all the steps of the message pushing method in the above embodiments, the computer-readable storage medium storing thereon a computer program that, when executed by a processor, implements all the steps of the message pushing method in the above embodiments, for example, the processor implements the following steps when executing the computer program:
step 1: the public API platform receives a target message sent by an accessed first application system;
Step 2: the public API platform stores the target message in a message center module;
step 3: determining whether a pushing opportunity of the target message is reached;
step 4: under the condition that the pushing time for the target message is determined, the public API platform pushes the target message to a target application system in a target terminal in a message window card mode for displaying, wherein the target application system is a second application system accessed to the public API platform, and the target application system jumps to the first application system through triggering the message window card displayed in the second application system.
As can be seen from the foregoing description, in the embodiment of the present application, a target message sent by an accessed first application system is received through a public API platform, and when determining that a pushing time of the target message is reached, the public API platform pushes the target message to a target application system in a target terminal in a message window card manner for displaying, where the target application system is a second application system accessing the public API platform, and the trigger of the message window card displayed in the second application system is skipped to the first application system. The method and the device have the advantages that through the arrangement of the public API platform, rapid jump among the multiple application systems can be realized, the technical problems that the existing multiple application systems independently operate and are required to be frequently switched and the message processing efficiency is too low are solved, and the technical effect of effectively improving the message processing efficiency of the multiple application systems is achieved.
User information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, presented data, etc.) referred to herein are both information and data that is authorized by the user or is fully authorized by the parties, and the collection, use, and processing of relevant data requires compliance with relevant laws and regulations and standards, and is provided with corresponding operational portals for the user to choose authorization or denial.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for a hardware+program class embodiment, the description is relatively simple, as it is substantially similar to the method embodiment, as relevant see the partial description of the method embodiment.
The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
Although the present application provides method operational steps as described in the examples or flowcharts, more or fewer operational steps may be included based on conventional or non-inventive labor. The order of steps recited in the embodiments is merely one way of performing the order of steps and does not represent a unique order of execution. When implemented by an actual device or client product, the instructions may be executed sequentially or in parallel (e.g., in a parallel processor or multi-threaded processing environment) as shown in the embodiments or figures.
The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. One typical implementation is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a car-mounted human-computer interaction device, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
Although the present description provides method operational steps as described in the examples or flowcharts, more or fewer operational steps may be included based on conventional or non-inventive means. The order of steps recited in the embodiments is merely one way of performing the order of steps and does not represent a unique order of execution. When implemented in an actual device or end product, the instructions may be executed sequentially or in parallel (e.g., in a parallel processor or multi-threaded processing environment, or even in a distributed data processing environment) as illustrated by the embodiments or by the figures. The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, it is not excluded that additional identical or equivalent elements may be present in a process, method, article, or apparatus that comprises a described element.
For convenience of description, the above devices are described as being functionally divided into various modules, respectively. Of course, when implementing the embodiments of the present disclosure, the functions of each module may be implemented in the same or multiple pieces of software and/or hardware, or a module that implements the same function may be implemented by multiple sub-modules or a combination of sub-units, or the like. The above-described apparatus embodiments are merely illustrative, for example, the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
Those skilled in the art will also appreciate that, in addition to implementing the controller in a pure computer readable program code, it is well possible to implement the same functionality by logically programming the method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers, etc. Such a controller can be regarded as a hardware component, and means for implementing various functions included therein can also be regarded as a structure within the hardware component. Or even means for achieving the various functions may be regarded as either software modules implementing the methods or structures within hardware components.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Disks (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
It will be appreciated by those skilled in the art that embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, the present specification embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present description embodiments may take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
The present embodiments may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The embodiments of the specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, as relevant to see a section of the description of method embodiments. In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the embodiments of the present specification. In this specification, schematic representations of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.
The foregoing is merely an example of an embodiment of the present disclosure and is not intended to limit the embodiment of the present disclosure. Various modifications and variations of the illustrative embodiments will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, or the like, which is within the spirit and principles of the embodiments of the present specification, should be included in the scope of the claims of the embodiments of the present specification.
Claims (10)
1. A message pushing method, comprising:
the public API platform receives a target message sent by an accessed first application system;
the public API platform stores the target message in a message center module;
determining whether a pushing opportunity of the target message is reached;
under the condition that the pushing time for the target message is determined, the public API platform pushes the target message to a target application system in a target terminal in a message window card mode for displaying, wherein the target application system is a second application system accessed to the public API platform, and the target application system jumps to the first application system through triggering the message window card displayed in the second application system.
2. The method of claim 1, wherein jumping to the first application system by triggering the message window card displayed in the second application system comprises:
Receiving triggering operation of a user on the message window card displayed in the second application system;
responding to the triggering operation, and sending user information required by authentication to an authentication center by the second application system;
the authentication center performs user authentication according to the user information, and returns a token to the second application system after the authentication is passed;
the second application system sends authentication information carrying a token to the authentication center;
the authentication center verifies the token in the authentication information, and after the verification is passed, an authentication bill is returned to the second application system;
the second application system transmits the authentication ticket to the first application system;
the first application system sends a secret key and an authentication bill to the authentication center;
and the authentication center verifies the secret key and the authentication bill, and returns a token to the first application system after the verification is passed so as to jump to the first application system.
3. The method of claim 1, further comprising, before the public API platform receives the target message sent by the accessed first application system:
the public API platform receives an access application sent by the first application system;
Responding to the access application, the public API platform distributes an access identifier and an access password for the first application system;
after the allocation is completed, the first application system is recorded in an application system list as an application system to which access is allowed.
4. The method according to claim 1, wherein in case of determining a pushing opportunity to reach the target message, the public API platform pushes the target message to a target application system in a target terminal in a message window card manner for display, including:
under the condition that the pushing time reaching the target message is determined, acquiring the user identification of the target message;
taking the user identified by the user identification as a target user;
determining a set of application systems associated with the target user that are permitted to access the public API platform;
determining an application system in which a target user in each application system in an application set is in a login state currently;
taking an application system of which the target user is in a login state currently as a target application;
and pushing the target message to a target application system in the target terminal by the public API platform in a message window card mode for display.
5. The method of claim 1, wherein determining whether a push occasion for the target message is reached comprises:
extracting an emergency identifier from the target message;
determining a pushing opportunity reaching the target message under the condition that the emergency identifier indicates that the target message is an emergency message;
determining whether the current time point is a preset push time point or not under the condition that the emergency identifier indicates the target message to be a non-emergency message;
and under the condition that the current time point is determined to be a preset pushing time point, determining the pushing time for reaching the target message.
6. A message pushing system, comprising: public API platform, first application system and second application system, wherein:
the first application system and the second application system access the public API platform;
the public API platform receives a target message sent by the first application system and stores the target message in a message center module; and under the condition that the pushing time of the target message is reached, pushing the target message to a second application system in a target terminal by the public API platform in a message window card mode for display, and jumping to the first application system by triggering the message window card displayed in the second application system.
7. A message pushing device, located in a public API platform, comprising:
the receiving module is used for receiving a target message sent by a first application system accessed to the public API platform;
a storage module for storing the target message in a message center module;
the determining module is used for determining whether the pushing time of the target message is reached;
the pushing module is used for pushing the target message to a target application system in a target terminal in a message window card mode for displaying under the condition that the pushing time of the target message is determined, wherein the target application system is a second application system accessed to the public API platform, and the target application system jumps to the first application system through triggering the message window card displayed in the second application system.
8. An electronic device comprising a processor and a memory for storing processor-executable instructions, wherein the processor, when executing the instructions, performs the steps of the method of any one of claims 1 to 5.
9. A computer readable storage medium having stored thereon a computer program/instruction, which when executed by a processor, implements the steps of the method according to any of claims 1 to 5.
10. A computer program product comprising computer programs/instructions which, when executed by a processor, implement the steps of the method of any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410008846.3A CN117834723A (en) | 2024-01-02 | 2024-01-02 | Message pushing method, system and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410008846.3A CN117834723A (en) | 2024-01-02 | 2024-01-02 | Message pushing method, system and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117834723A true CN117834723A (en) | 2024-04-05 |
Family
ID=90507702
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410008846.3A Pending CN117834723A (en) | 2024-01-02 | 2024-01-02 | Message pushing method, system and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117834723A (en) |
-
2024
- 2024-01-02 CN CN202410008846.3A patent/CN117834723A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10158670B1 (en) | Automatic privilege determination | |
| US20230082879A1 (en) | Systems and methods for providing a two-way, intelligent text messaging platform | |
| CN105391803A (en) | Message pushing method and device | |
| US9667808B2 (en) | Techniques for contextual mobile data access | |
| CN110264190A (en) | Triggering method, device, equipment and the storage medium of intelligent contract | |
| CN104572263A (en) | Page data interaction method, related device and system | |
| CN109165157B (en) | Method for testing application program and test platform | |
| WO2014204832A1 (en) | Systems, methods, and computer program products for processing a request relating to a mobile communication device | |
| US11868492B2 (en) | Systems and methods for mediating permissions | |
| CN102859505B (en) | The management method of management system and computer system | |
| CN110278192A (en) | Method, apparatus, computer equipment and the readable storage medium storing program for executing of extranet access Intranet | |
| US20220366066A1 (en) | Display method, display device, and electronic device | |
| CN111833507A (en) | Visitor authentication method, device, equipment and computer readable storage medium | |
| CN111444090B (en) | Contract testing method and device in blockchain, electronic equipment and storage medium | |
| JP6494990B2 (en) | User authentication method and user authentication system for service account, and storage medium | |
| US11503456B1 (en) | Maintaining electronic subscriber identity module (eSIM) profiles across multiple mobile network operators (MNOs) | |
| CN113296744A (en) | Application development system and method | |
| CN117834723A (en) | Message pushing method, system and device | |
| CN113079085B (en) | Business service interaction method, business service interaction device, business service interaction equipment and storage medium | |
| Hill | Scalable iot platforms | |
| CN115687826A (en) | Page refreshing method and device, computer equipment and storage medium | |
| CN107562501A (en) | A kind of smart machine management-control method and system | |
| US20230067756A1 (en) | Using machine learning for security anomaly detection and user experience inference | |
| Damianou | Digital Forensic Readiness in Smart, Circular Cities. | |
| CN107528819A (en) | Account binding method and device |
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 |