CN115065656A - Message processing method and device, electronic equipment and computer readable medium - Google Patents

The application discloses a message processing method, a message processing device, electronic equipment and a computer readable medium, which relate to the technical field of medical health, and the method comprises the following steps: receiving a message processing request, and acquiring a corresponding message source identifier and a corresponding user identifier; calling message middleware to acquire corresponding messages based on the message source identifiers, and further aggregating the messages to generate aggregated messages; determining a corresponding device identifier according to the user identifier, acquiring login log data of the device corresponding to the device identifier, and acquiring login time corresponding to the user identifier from the login log data; and determining target equipment in each piece of equipment corresponding to the equipment identifier according to the login time, and further pushing the aggregation message to the target equipment. The method comprises the steps of aggregating messages from multiple sources to generate aggregate messages, determining target equipment according to login time corresponding to login log information of the multi-terminal equipment, and sending the aggregate messages to the target equipment so as to avoid repeated and undifferentiated multi-terminal sending and avoid disturbing users.

Message processing method and device, electronic equipment and computer readable medium

Technical Field

The present application relates to the field of medical health technologies, and in particular, to a message processing method, an apparatus, an electronic device, and a computer-readable medium.

Background

Currently, with the development of services, a message center system has been developed to a multi-end message system including apps, H5, intelligent hardware devices, and the like, through a single client, wherein each client processes its own message event source independently and has its own message sending logic, and there is no association between them, when a user logs in multiple devices, each client is independent of each other, and in some cases, multi-end sending may be caused, which may disturb the user.

In the process of implementing the present application, the inventor finds that at least the following problems exist in the prior art:

when a user logs in with multiple devices, a subscribed message may be sent from multiple terminals, which may disturb the user.

Disclosure of Invention

In view of this, embodiments of the present application provide a message processing method and apparatus, an electronic device, and a computer readable medium, which can solve the problem that when a user logs in to multiple devices, a subscribed message may be sent from multiple terminals, which may disturb the user.

In order to achieve the above object, according to an aspect of an embodiment of the present application, there is provided a message processing method including:

receiving a message processing request, and acquiring a corresponding message source identifier and a corresponding user identifier;

calling message middleware to acquire corresponding messages based on the message source identifiers, and further aggregating the messages to generate aggregated messages;

determining a corresponding device identifier according to the user identifier, acquiring login log data of the device corresponding to the device identifier, and acquiring login time corresponding to the user identifier from the login log data;

and determining target equipment in each equipment corresponding to the equipment identifier according to the login time, and further pushing the aggregation message to the target equipment.

Optionally, before aggregating the messages to generate an aggregated message, the method further comprises:

acquiring a scene identifier carried in a message processing request;

filtering the message according to the scene identifier to obtain a message corresponding to the scene identifier; and

aggregating messages to generate an aggregated message, comprising:

and aggregating the messages corresponding to the scene identifications to generate an aggregated message.

Optionally, pushing the aggregated message to the target device includes:

acquiring message distribution configuration information, and determining customized content corresponding to the target equipment according to the message distribution configuration information;

and adjusting the aggregation message based on the customized content, and pushing the adjusted aggregation message to the target device.

Optionally, pushing the aggregated message to the target device includes:

and asynchronously sending the aggregated message to a message distribution service, so that the asynchronous distribution service calls an event communication framework to send a message event to a sending end corresponding to the target equipment, and the sending end pushes the aggregated message to the target equipment based on the message event.

Optionally, before obtaining the corresponding message based on the message source identifier, the method further includes:

in response to detecting that a user signing event is triggered, acquiring a corresponding user identifier and a signing object identifier, and further establishing a session based on the user identifier and the signing object identifier;

and acquiring the session content corresponding to the created session, and further generating and outputting a session document based on the session content.

Optionally, before generating the session document based on the session content, the method further includes:

and calling a session change message monitoring program, acquiring the unread message in the session content, generating an unread identifier based on the unread message, and displaying the unread identifier at a display position corresponding to the unread message.

Optionally, after the unread message is displayed at the display position corresponding to the unread message, the method further includes:

and acquiring the existence time of the unread message, and clearing the unread message and the unread mark in response to the existence time exceeding a preset time threshold.

Optionally, determining a target device in each device corresponding to the device identifier according to the login time includes:

calculating the time interval between the current time and each login time;

and determining the equipment corresponding to the login time corresponding to the time interval smaller than the preset threshold value as the target equipment.

In addition, the present application also provides a message processing apparatus, including:

the receiving unit is configured to receive the message processing request and acquire a corresponding message source identifier and a corresponding user identifier;

the message aggregation unit is configured to call message middleware to acquire corresponding messages based on the message source identifiers, and further aggregate the messages to generate aggregated messages;

the login time acquisition unit is configured to determine a corresponding device identifier according to the user identifier, acquire login log data of the device corresponding to the device identifier, and acquire login time corresponding to the user identifier from the login log data;

and the message pushing unit is configured to determine a target device in each device corresponding to the device identifier according to the login time, and further push the aggregated message to the target device.

Optionally, the message processing apparatus further comprises a message filtering unit configured to:

acquiring a scene identifier carried in a message processing request;

filtering the message according to the scene identifier to obtain a message corresponding to the scene identifier; and

the message aggregation unit is further configured to:

and aggregating the messages corresponding to the scene identifications to generate an aggregated message.

Optionally, the message pushing unit is further configured to:

acquiring message distribution configuration information, and determining customized content corresponding to the target equipment according to the message distribution configuration information;

and adjusting the aggregation message based on the customized content, and pushing the adjusted aggregation message to the target device.

Optionally, the message pushing unit is further configured to:

and asynchronously sending the aggregated message to a message distribution service, so that the asynchronous distribution service calls an event communication framework to send a message event to a sending end corresponding to the target equipment, and the sending end pushes the aggregated message to the target equipment based on the message event.

Optionally, the message processing apparatus further comprises a session creating unit configured to:

in response to detecting that a user signing event is triggered, acquiring a corresponding user identifier and a signing object identifier, and further establishing a session based on the user identifier and the signing object identifier;

and acquiring the session content corresponding to the created session, and further generating and outputting a session document based on the session content.

Optionally, the message processing apparatus further comprises a listening unit configured to:

and calling a session change message monitoring program, acquiring the unread message in the session content, generating an unread identifier based on the unread message, and displaying the unread identifier at a display position corresponding to the unread message.

Optionally, the listening unit is further configured to:

and acquiring the existence time of the unread message, and clearing the unread message and the unread mark in response to the existence time exceeding a preset time threshold.

Optionally, the message pushing unit is further configured to:

calculating the time interval between the current time and each login time;

and determining the equipment corresponding to the login time corresponding to the time interval smaller than the preset threshold value as the target equipment.

In addition, the present application also provides an electronic device for message processing, including: one or more processors; a storage device for storing one or more programs which, when executed by one or more processors, cause the one or more processors to implement the message processing method as described above.

In addition, the present application also provides a computer readable medium, on which a computer program is stored, which when executed by a processor implements the message processing method as described above.

One embodiment of the above invention has the following advantages or benefits: the method comprises the steps of obtaining a corresponding message source identifier and a corresponding user identifier by receiving a message processing request; calling message middleware to acquire corresponding messages based on the message source identifiers, and further aggregating the messages to generate aggregated messages; determining a corresponding device identifier according to the user identifier, acquiring login log data of the device corresponding to the device identifier, and acquiring login time corresponding to the user identifier from the login log data; and determining target equipment in each equipment corresponding to the equipment identifier according to the login time, and further pushing the aggregation message to the target equipment. The method comprises the steps of aggregating messages from multiple sources to generate aggregate messages, determining target equipment according to login time corresponding to login log information of the multi-terminal equipment, and sending the aggregate messages to the target equipment so as to avoid repeated and undifferentiated multi-terminal sending and avoid disturbing users.

Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.

Drawings

The drawings are included to provide a further understanding of the application and are not to be construed as limiting the application. Wherein:

FIG. 1 is a schematic diagram of a main flow of a message processing method according to one embodiment of the present application;

FIG. 2 is a schematic diagram of a main flow of a message processing method according to one embodiment of the present application;

FIG. 3 is a system schematic illustration of a message processing method according to one embodiment of the present application;

fig. 4 is a schematic application scenario diagram of a message processing method according to a fourth embodiment of the present application;

fig. 5 is a message aggregation diagram of a message processing method according to a fifth embodiment of the present application;

fig. 6 is a schematic diagram of target device determination logic of a message processing method according to a sixth embodiment of the present application;

fig. 7 is a schematic diagram of main units of a message processing apparatus according to an embodiment of the present application;

FIG. 8 is an exemplary system architecture diagram to which embodiments of the present application may be applied;

FIG. 9 is a schematic block diagram of a computer system suitable for use in implementing a terminal device or server according to embodiments of the present application;

fig. 10 is a schematic view of an application scenario of a message processing method according to an embodiment of the present application.

Detailed Description

The following description of the exemplary embodiments of the present application, taken in conjunction with the accompanying drawings, includes various details of the embodiments of the application for the understanding of the same, which are to be considered exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present application. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

The present disclosure contemplates that entities responsible for collecting, analyzing, disclosing, transmitting, storing, or otherwise using such personal information data will comply with established privacy policies and/or privacy practices. In particular, such entities should enforce and adhere to the use of privacy policies and practices that are recognized to meet or exceed industry or government requirements for maintaining privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as data is collected and/or used. Personal information from the user should be collected for legitimate and legitimate uses by the entity and not shared or sold outside of these legitimate uses. Furthermore, such acquisition/sharing should be performed after receiving user informed consent. Furthermore, such entities should consider taking any necessary steps to defend and secure access to such personal information data, and to ensure that others who have access to the personal information data comply with their privacy policies and procedures. In addition, such entities may subject themselves to third party evaluations to prove compliance with widely accepted privacy policies and practices. In addition, policies and practices should be adjusted to the particular type of personal information data collected and/or accessed, and to applicable laws and standards including specific considerations of jurisdiction. For example, in the united states, the collection or acquisition of certain health data may be governed by federal and/or state laws, such as the health insurance flow and accountability act (HIPAA); while other countries may have health data subject to other regulations and policies and should be treated accordingly. Therefore, different privacy practices should be maintained for different personal data types in each country.

Regardless of the foregoing, the present disclosure also contemplates embodiments in which a user selectively prevents use or access to personal information data. That is, the present disclosure contemplates that hardware elements and/or software elements may be provided to prevent or block access to such personal information data. For example, in terms of accessing or storing health information, the techniques of the present invention may be configured to allow a user to opt-in or opt-out of participating in the collection of personal information data during registration services or at any time thereafter. In another example, the user may choose not to provide certain types of health-related information. In yet another example, the user may choose to limit the length of time the health-related information is maintained or to prohibit the storage of the health-related information altogether. In addition to providing "opt-in" and "opt-out" options, the present disclosure contemplates providing notifications related to accessing or using personal information. For example, the user may be notified that their personal information data is to be accessed when the application is downloaded, and then be reminded again just before the personal information data is accessed by the application.

Further, it is an object of the present disclosure that personal information data should be managed and processed to minimize the risk of inadvertent or unauthorized access or use. Once the data is no longer needed, the risk can be minimized by limiting data collection and deleting data. In addition, and when applicable, including in certain health-related applications, data de-identification may be used to protect the privacy of the user. De-identification may be facilitated by removing particular identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at a city level rather than at an address level), controlling how data is stored (e.g., aggregating data among users), and/or other methods, as appropriate.

Fig. 1 is a schematic diagram of a main flow of a message processing method according to an embodiment of the present application, and as shown in fig. 1, the message processing method includes:

step S101, receiving a message processing request, and acquiring a corresponding message source identifier and a corresponding user identifier.

In this embodiment, an execution subject (for example, a server) of the message processing method may receive the message processing request through a wired connection or a wireless connection. The message processing request may specifically be a request for distributing (or forwarding) a message. After receiving the message processing request, the execution body may obtain a message source identifier and a user identifier carried in the request. Wherein the message source identifier is used for characterizing the source of the message, and the source of the message can be a health consultation APP or an inquiry consultation APP, for example. The message corresponding to the message processing request may be, for example, a health consultation message, an inquiry referral message, or a combined message of the health consultation message and the inquiry referral message, and the content of the message corresponding to the message processing request is not specifically limited in the embodiments of the present application. The user identifier is used for representing the user name or the user mobile phone number of the message corresponding to the message processing request, and the specific content of the user identifier is not limited in the embodiment of the application.

Step S102, calling message middleware to obtain corresponding messages based on the message source identification, and further aggregating the messages to generate aggregated messages.

For example, the execution body may invoke the message middleware to locate the corresponding message source APP according to the message source identifier, and further obtain various generated messages from the located message source APP. Messages from multiple sources are targeted to a certain topic or content, and cross-system search, refinement and integration of messages are key among the messages based on aggregation of multi-source messages. The execution main body can carry out message aggregation facing to the user, carry out cross-system search of the message according to the message requirement of the user, realize message aggregation facing to the user through filtering, and generate the aggregated message. Therefore, messages with the same meaning or format in the disordered messages can be aggregated together, and the message format is unified so as to be conveniently distributed to each terminal.

Specifically, before acquiring a corresponding message based on a message source identifier, the message processing method includes: in response to detecting that a user signing event is triggered, acquiring a corresponding user identifier and a signing object identifier, and further establishing a session based on the user identifier and the signing object identifier; and acquiring the session content corresponding to the created session, and further generating and outputting a session document based on the session content.

When the execution main body detects that the user signing event is triggered, the user identification and the signing object identification corresponding to the user signing event are obtained. The user identifier may be, for example, a user name or a mobile phone tail number of the user consulting the medical condition. The sign of the contract object may be, for example, the number of the doctor who receives the medical consultation or the health consultation, the name of the doctor, or the like. The embodiment of the application does not limit the specific content of the user identifier and the signed object identifier.

After the execution main body obtains the user identifier and the signed object identifier, a consultation session window can be created based on the obtained user identifier and the signed object identifier so that a user corresponding to the user identifier can communicate with a doctor corresponding to the signed object identifier. When the execution main body detects a session ending identifier (such as end) or does not detect an interactive session for a long time, acquiring session content corresponding to the consultation session window, and generating and outputting a session document based on the session content. The session document may be a prescription document in the session content or a list of recommended meals, and the content of the session document is not specifically limited in the embodiment of the present application.

Specifically, before generating the session document based on the session content, the message processing method further includes:

calling a conversation change message monitoring program, acquiring the unread message in the conversation content, generating an unread identifier based on the unread message, and displaying the unread identifier at a display position corresponding to the unread message.

pin (personal identification number). The pin is a serial number composed of numbers and used to authenticate the user's identity and authorize the user to enter the system. As shown in fig. 5, the executing agent may call a session change message listener to listen, in compliance, whether a pin of a user (e.g., a patient) is online, whether the session type is chatty (a session type corresponding to a session generated by an instant chat APP), or an internet hospital (mutual medical for short). Doctors can communicate with patients and make on-line inquiry through internet hospital (mutual medical service for short) software, and can check patient files and health data under the condition of compliance. If the session type is chatting (namely the session without limiting the content), judging whether a principal responsible doctor participates in the session, and if the session type is an internet hospital (for short, mutual medical service), judging whether the session is managed single chatting according to a scene value in the session. The "housekeeper" may represent doctors who are on duty at a preset time point or a preset place, or may represent personnel who transfer for each doctor on duty. An example "housekeeping single chat" may be a single-line conversation chat with a user (e.g., a patient) by a doctor on duty that other doctors cannot participate in. If the doctor is the master responsibility doctor (the master responsibility doctor can be one doctor or a plurality of doctors, and particularly can be doctors designated by the user) participating in the session or chatting in the housekeeping list, the unread messages in the session are inquired, wherein the unread messages can comprise the unread messages of the master responsibility doctor in chatting, and can also comprise the chatting unread messages in the housekeeping list in an internet hospital (short for mutual medical service). A long connection means that a plurality of packets can be continuously transmitted over one connection, and if no packet is transmitted during the connection holding period, both sides connected to the long connection need to transmit a link check packet to detect and maintain the long connection. For example, the long link may be that the data transmission is completed, the link is kept not disconnected (i.e. a rst (reset the connection) packet for forcibly disconnecting the TCP link is not sent), and the data transmission in the channel is waited to continue under the same domain name. The executive agent may invoke the long link service to monitor whether the user's (e.g., patient) pin is online and continuously detect in real-time, through the long link interface, unread messages and display them in the created conversation window.

After detecting the unread message, the execution main body may determine a display position corresponding to the unread message, where the display position may be a right side, a left side, an upper side, a lower side, and the like of the unread message, and the display position of the unread message is not specifically limited in the embodiment of the present application. The execution main body can generate the unread identification based on the unread message, and after the display position of the unread message is determined, the unread identification is displayed at the display position corresponding to the unread message so as to remind a user to check the dimension message in time, so that the real-time performance of conversation communication is improved, and the user experience is improved.

Specifically, after the unread message is displayed at the display position corresponding to the unread message, the method further includes: and acquiring the existence time of the unread message, and clearing the unread message and the unread mark in response to the existence time exceeding a preset time threshold.

When the execution main body detects that the existence duration of the unread message from the generation time to the current time exceeds the preset duration threshold, that is, the existence duration of the unread message is too long and is not read, the execution main body can start an elimination program to eliminate the unread message of which the existence duration exceeds the preset duration threshold, so as to ensure the real-time performance of the conversation and avoid the wrong answer of the user (here, the patient).

As another implementation manner, the execution main body may further generate a citation reminding message according to the unread message with an excessively long existence time and without being read, that is, cite the message with an excessively long existence time and without being read and send a reminding message to the user (here, the patient) to remind the user to respond to the reminding message in time, so that the integrity of the session can be ensured, any question is not missed, and the integrity of the question in the session and the integrity of the answer of the user (here, the patient) to the question in the session are ensured.

Step S103, determining a corresponding device identifier according to the user identifier, acquiring login log data of the device corresponding to the device identifier, and acquiring login time corresponding to the user identifier from the login log data.

After obtaining the user identifier, the execution main body may query what devices the user corresponding to the user identifier logs in, and determine, based on log data of each device, which device or devices are the most recently logged in (which may include logging in within several hours from the current time, logging in on the same day, logging in yesterday, and the like, and the embodiment of the present application does not specifically limit the time of the most recently logged in). Specifically, the login time may be obtained from login log data of several devices that the user logs in by the user corresponding to the user identifier. And determining the target equipment according to the sequence of the login time.

And step S104, determining target equipment in each equipment corresponding to the equipment identifier according to the login time, and further pushing the aggregation message to the target equipment.

Specifically, determining a target device in each device corresponding to the device identifier according to the login time includes: calculating the time interval between the current time and each login time; and determining the equipment corresponding to the login time corresponding to the time interval smaller than the preset threshold value as the target equipment.

For example, the execution subject may calculate a difference between the current time and the login time of the device that the user has logged in most recently and corresponds to the user identifier, to obtain each time interval. The execution subject may determine, as the target device, a device that has logged in most recently and corresponds to a smaller time interval (that is, a time interval smaller than a preset threshold, for example, 3 hours, which is not specifically limited by the embodiment of the present application).

Specifically, pushing the aggregated message to the target device includes: acquiring message distribution configuration information, and determining customized content corresponding to the target equipment according to the message distribution configuration information; and adjusting the aggregation message based on the customized content, and pushing the adjusted aggregation message to the target device.

In this embodiment of the present application, the message distribution configuration information stores information about push modes/methods of each client, applet, and intelligent hardware device, and the execution main body may obtain customized content corresponding to the target device according to the information about push modes/methods of each client, applet, and intelligent hardware device in the message distribution configuration information, where the customized content may include customized content information such as formats, prefixes, and suffixes of distribution messages that can be received by each client, applet, and intelligent hardware device. After obtaining the customized content of the target device, the execution main body may adjust the corresponding content of the aggregated message according to the definition of the format, prefix, suffix, and the like of the message in the customized content, and push the adjusted aggregated message to the target device.

Specifically, pushing the aggregated message to the target device includes: and asynchronously sending the aggregated message to a message distribution service, so that the asynchronous distribution service calls an event communication framework to send a message event to a sending end corresponding to the target equipment, and the sending end pushes the aggregated message to the target equipment based on the message event.

The execution main body can generate an asynchronous task according to the adjusted aggregation message, send the generated asynchronous task to an asynchronous task pool, wait for the execution time of the asynchronous task to arrive, execute the asynchronous task and send the corresponding adjusted aggregation message to the message distribution service. The asynchronous distribution service calls an event communication framework (for example, eventbus) to send a message event, each sending terminal which is responsible for sending messages to a specific client receives the message event, and then sends the message event to different clients (namely target devices, the number of the target devices can be one or more), so that the purpose of one message and multi-terminal touch is achieved.

In the embodiment, a message source identifier and a user identifier corresponding to a message are acquired by receiving a message processing request; calling message middleware to acquire corresponding messages based on the message source identifiers, and further aggregating the messages to generate aggregated messages; determining a corresponding device identifier according to the user identifier, acquiring login log data of the device corresponding to the device identifier, and acquiring login time corresponding to the user identifier from the login log data; and determining target equipment in each equipment corresponding to the equipment identifier according to the login time, and further pushing the aggregation message to the target equipment. The method comprises the steps of aggregating messages from multiple sources to generate aggregate messages, determining target equipment according to login time corresponding to login log information of the multi-terminal equipment, and sending the aggregate messages to the target equipment so as to avoid repeated and undifferentiated multi-terminal sending and avoid disturbing users.

Fig. 2 is a schematic main flow diagram of a message processing method according to an embodiment of the present application, and as shown in fig. 2, the message processing method includes:

step S201, receiving a message processing request, and acquiring a corresponding message source identifier and a corresponding user identifier.

Step S202, calling message middleware to acquire corresponding messages based on the message source identification.

Step S203, a scene identifier carried in the message processing request is acquired.

The message processing request may carry a scene identifier. The scene identification, i.e. the scene value, is used to characterize the type of the chat scene. The types of the chat scenes can include a smooth chat scene, an internet hospital scene, and the like. Wherein, the chatting scene can be a scene that the user chats with a family doctor (the chatting content can include chatting of diet health, postpartum recovery and the like). The internet hospital (for short, mutual medical service) scene may be a scene in which a user and a family doctor make an inquiry based on a specific disease.

And step S204, filtering the message according to the scene identifier to obtain the message corresponding to the scene identifier.

After the execution main body obtains the scene identification carried in the message processing request, the information can be filtered based on the scene identification, the filtered information is inquiry information generated corresponding to a smooth chat scene or a corresponding doctor inquiry scene, namely the information corresponding to the scene identification is obtained, and noise points are removed, so that the information processing efficiency and the accuracy are improved.

Step S205, aggregating the messages corresponding to the scene identifiers to generate an aggregated message.

And the execution body aggregates the messages filtered based on the scene identification to generate an aggregated message. The aggregated message may be an inquiry message in a single scene, or an aggregated message obtained by aggregating inquiry messages in different scenes based on a preset aggregation rule.

Step S206, determining the corresponding equipment identification according to the user identification, obtaining the log data of the equipment corresponding to the equipment identification, and obtaining the log time corresponding to the user identification from the log data.

Step S207, determining a target device of the devices corresponding to the device identifier according to the login time, and pushing the aggregation message to the target device.

The execution main body can push the aggregation message to the equipment which is logged by the user recently so as to avoid indiscriminate multi-end sending and improve user experience.

Fig. 3 is a schematic view of an application scenario of a message processing method according to an embodiment of the present application. The message processing method of the embodiment of the application is applied to a scene of pushing the message subscribed by the user to the terminal logged in by the user. For example, as shown in fig. 3, the executing entity monitors a health consultation message and an inquiry referral message by using a message queue, and then aggregates and enhances the two messages, and then uniformly outputs the messages as a family doctor (home doctor for short) side message. And after the processing is finished, sending the message to a message distribution system, and performing the distribution processing of the message by using an event communication framework eventBus technology. Different sending ends monitor event of event bus message arrival, then according to message distribution configuration, determine whether to send and each end customization content sent, and then touch the processed message to user. After the execution body enhances the unified processing of the messages from different sources, the execution body sends an event through eventBus to complete the message aggregation processing and the sending of multiple clients (such as APP1, applet 2 and IOT 3). Wherein, IOT: intelligent hardware devices such as XX boxes. IOT3 is an intelligent hardware device numbered 3, and the number of IOT is not specifically limited in this embodiment of the present application.

Fig. 4 is a schematic diagram of an application scenario of a message processing method according to a fourth embodiment of the present application. As shown in fig. 4, after the execution subject acquires the mutual medical IM message and the chat IM message, the IM message is synchronized to a preprocessing service in a form of a message queue JMQ for enhanced processing to obtain data in a uniform format. The preprocessing service PRE _ PROCESS is maintained with an enhanced home service package ID and a user service package ID. Then, the executive body can call the home medicine underlying service, obtain the corresponding service package information according to the session ID generating the IM message, and further call the corresponding atomic service (atomic service: the atom is the basic service unit which can not be decomposed any more and is also the minimum unit which can be managed and assigned by the operation system, and can be shared by a plurality of applications) to execute mutual medical service and home medical service in the atomic service (the home medical service obeys the home doctor basic service specification DB). After obtaining the data with the uniform format, the execution main body asynchronously delivers the data with the uniform format to a distribution service for data delivery, specifically, a rule engine is called to call a DISPATCH distribution service by using an event communication framework EventBus technology according to a configured distribution rule, and the distribution service is distributed through a message center, specifically, a uniform interface of the message center is used for carrying out specific message distribution processing aiming at each end (such as a health APP, a home doctor H5, intelligent hardware equipment and an applet). According to the method and the device, the EventBus technology is utilized to carry out distribution processing on the user message push, so that the purpose that the terminals are triggered respectively is achieved.

Fig. 5 is a message aggregation diagram of a message processing method according to a fifth embodiment of the present application.

As shown in FIG. 5, first when a user logs into the X enterprise health service home page, the last message of a card on the home page is clicked. Before the user does not trigger a message on the home page, a body timing (e.g., 2s) polling the trigger status of the message on the home page is performed or the trigger status of the connected message is determined by whether a long link connected to the message on the home page is triggered. And the execution main body inquires the message sent by the user through the X enterprise health service home page through the gateway interface and initializes the message. In turn, the executive principal may invoke the medical atomic service to invoke the IM underlying service to obtain and update the smooth chat message MQ and clear the unread MQ. The executive may also obtain a mutual medical inquiry MQ generated by the doctor/PC. And the executive main body can send the mutual medical inquiry MQ and the chatting new message MQ to the family medical portal for aggregation to obtain the aggregated message. The method specifically comprises the following steps: screening out user IDs of the home doctors; performing reverse checking on the enhanced Usp & Config _ ID according to the Sid (the Sid is a unique identity number, specifically, a service pack ID or a user service pack ID); creating an JMQ3 message, the JMQ3 message created is the aggregate message. The executive body can send the aggregated message to the message center, push the aggregated message by other ends, and send the aggregated message to the family doctor Tab. And sent to the health APP, public number, or applet via the message center. Or the other end can push the data to the gateway interface again for further aggregation and reinforcement. After the family medical portal generates the polymerization information, the family medical portal can be monitored by the smooth chatting new message MQ, the smooth chatting clearing unread MQ and the mutual medical message change MQ. Wherein, the mutual medical information change MQ monitoring can monitor the mutual medical information, the patient entering the conversation, etc. The execution subject can get chat IM from all monitored information through a filter (filtering out non-medical IM messages), and then perform corresponding message enhancement based on the cached Sid enhancement service package information. The execution subject can obtain mutual medical IM from all monitored information through a filter (filtering out non-home medical IM messages), and further perform corresponding message enhancement based on the cached DiagId enhanced service package information. The enhancement content includes: service package information: such as service package ID, service package type; sender information: such as From factor; the session type is as follows: e.g., chatting/inter-medical; the type of change: e.g., new message/clear unread; the reason for the change is as follows: for example: doctor/patient new message, patient enter session; original session information: title, content, time, etc. After the message enhancement processing is completed, the executive main body responds to the monitored medical session change message MQ and judges whether the pin of the user (such as a patient) is online or not, whether the session type is smooth chat (the session type corresponding to the session generated by the instant chat APP) or internet hospital (mutual medical service for short) or not, and a doctor can communicate with the patient and perform online inquiry through internet hospital (mutual medical service for short) software, and can check patient files, health data and manage the patient at any time. If the session type is chatting, whether a principal responsible doctor is participating in the session is judged (the judgment can be omitted), and if the session type is an internet hospital (for short, mutual medical service), whether housekeeping chatting is judged according to scene values in the session (the judgment can be omitted). And if the master responsibility doctor participates in the conversation or the housekeeping single chats, inquiring unread messages in the conversation, wherein the unread messages can comprise the unread messages of the master responsibility doctor in chatting, and can also comprise the housekeeping single chatting in an internet hospital (for short mutual medical service). A long connection means that a plurality of packets can be continuously transmitted over one connection, and if no packet is transmitted during the connection holding period, both sides connected to the long connection need to transmit a link check packet to detect and maintain the long connection. For example, the long link can be a link which is not disconnected after the data transmission is completed (no RST packet is sent and no four-way handshake is performed), and the data transmission with the channel is waited to continue under the same domain name. The executive agent may invoke the long link service to monitor whether the user's (e.g., patient) pin is online and continuously detect in real-time, through the long link interface, unread messages and display them in the created conversation window.

In the family doctor service scene in the embodiment of the application, a service obtaining mode of a user is mainly realized through a session, the user describes own health condition in the session and obtains health suggestions of a doctor or a housekeeper, and two realization modes are provided on finer-grained interaction, namely a health management scene based on health consultation and an inquiry scene based on internet medical referral. The former is active medical treatment, and the latter is serious medical treatment. Serious medical treatment is a core objective of treating diseases and saving people, and is the most credible relation between doctors and patients.

Whether the consultation is health consultation or consultation referral, the technical scheme of session realization is based on the underlying technology of XX instant messaging software, the XX instant messaging software provides an IM session management and message management mechanism, and a session scene of a health scene is built on the basis of the capability of the XX instant messaging software.

Based on the capability of the bottom IM (instant messaging), two implementation modes of the upper layer encapsulation are respectively an inquiry IM of an internet hospital and a chatting IM of a family doctor scene.

The inquiry IM and the inquiry phase are mutually bound, a user needs to designate a doctor, the system generates an inquiry list for the doctor, then a session is asynchronously generated, IM chatting is established, and the doctor and a patient carry out inquiry consultation in the IM; the family smooth chat IM is related to the service package and the rights and interests, the service package of the main user is effective, the user automatically creates a session for the user after signing a doctor, and the patient or other session members can manage the session members, session contents, message contents and the like in the scene of departing from the questionnaire.

The message aggregation process of the embodiment of the present application is shown in fig. 5:

1) in a family doctor (health management) scene, all IM messages need to have a uniform output channel, so that the reminding of a patient end and the use of other processes are facilitated, and the messages of the inquiry IM and the family smooth chat IM need to be aggregated and output.

2) Since the mutual medical IM message is also generated from the family doctor service package, the mutual medical IM session itself also carries a family doctor scene value (the scene value businessScene of the inquiry list/mutual medical session is family register), the mutual medical IM message may be filtered by using the scene value, and the filtered message is the inquiry message generated in the family doctor scene.

3) And designing an adapter for aggregating the filtered mutual medical IM messages and family smooth chat IM messages. All messages carry the user service pack ID generated in the home doctor scenario.

4) In the PRE _ PROCESS stage, enhancing the basic information of the user service package through the ID of the user service package carried in the session information, wherein the enhanced content comprises: service package information: such as service package ID, service package type; sender information: such as From factor; the session type is as follows: e.g., chatting/inter-medical; the type of change: e.g., new message/clear unread; the reason for the change is as follows: for example: doctor/patient new message, patient enter session; original session information: title, content, time, etc. The solution for enhancing information is a comprehensive communication and information sharing platform across communication networks and the Internet. The user uses a real mobile phone number as a login account number, can communicate through a mobile phone client of the RCS, and can share contents such as pictures, music, videos, texts and the like. The RCS not only expands the social network of people, but also provides diversified life forms for people. The use of the enhanced information function requires that the mobile VoLTE service is started first, and the mobile operator is consulted for details.

After the message aggregation processing, the message data is asynchronously sent to the message distribution service, the distribution service sends message events through an eventbus (eventbus event communication framework (sending event | obtaining subscriber | according to event type to call subscription method)), and each sending end which is responsible for sending messages to specific clients receives the message events and then sends the message events to different clients, so that the purpose of one message and multi-terminal touch is achieved.

In the embodiment of the application, the message queues are used for summarizing and uniformly processing the messages of all the service systems. And analyzing and processing the user login information by using the buried point uploading statistical capability, and judging the latest login equipment of the user. And the EventBus technology is utilized to distribute and process the user message pushing so as to achieve the aim of respectively triggering.

Fig. 6 is a schematic diagram of target device determination logic of a message processing method according to a sixth embodiment of the present application. As shown in fig. 6, the user logs in, and the device and time of user login are recorded. When the user logs in online, the online/offline state of the user is recorded through long TCP connection. The user can complete the management of the nearby login and the requirement of sending some messages to the latest login device of the user through the login state of the user and the latest login device, such as 15:01App1 login, 14:01App2 login, … and 10:01IOT3 login.

In some embodiments, the apparatus further comprises a message filtering unit, not shown in fig. 7, configured to: acquiring a scene identifier carried in a message processing request; filtering the message according to the scene identification to obtain a message corresponding to the scene identification; and the message aggregation unit is further configured to: and aggregating the messages corresponding to the scene identifications to generate an aggregated message.

In some embodiments, the message processing apparatus further comprises a session creation unit, not shown in fig. 7, configured to: in response to detecting that a user signing event is triggered, acquiring a corresponding user identifier and a signing object identifier, and further establishing a session based on the user identifier and the signing object identifier; and acquiring the session content corresponding to the created session, and further generating and outputting a session document based on the session content.

In some embodiments, the message processing apparatus further comprises a listening unit, not shown in fig. 7, configured to: and calling a session change message monitoring program, acquiring the unread message in the session content, generating an unread identifier based on the unread message, and displaying the unread identifier at a display position corresponding to the unread message.

In some embodiments, the listening unit is further configured to: and acquiring the existence time of the unread message, and clearing the unread message and the unread mark in response to the existence time exceeding a preset time threshold.

It should be noted that, in the present application, the message processing method and the message processing apparatus have corresponding relation in the specific implementation content, so the repeated content is not described again.

It should be understood that the number of terminal devices, networks, and servers in fig. 8 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

It should be noted that the computer readable medium shown in the present application may be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may include, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In this application, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units described in the embodiments of the present application may be implemented by software or hardware. The described units may also be provided in a processor, which may be described as: a processor includes a receiving unit, a message aggregating unit, a login time acquiring unit, and a message pushing unit. Wherein the names of the elements do not in some way constitute a limitation on the elements themselves.

As another aspect, the present application also provides a computer-readable medium, which may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs, which when executed by a device, cause the device to receive a message processing request and obtain a corresponding message source identifier and a corresponding user identifier; calling message middleware to acquire corresponding messages based on the message source identifiers, and further aggregating the messages to generate aggregated messages; determining a corresponding device identifier according to the user identifier, acquiring login log data of the device corresponding to the device identifier, and acquiring login time corresponding to the user identifier from the login log data; and determining target equipment in each equipment corresponding to the equipment identifier according to the login time, and further pushing the aggregation message to the target equipment.

According to the technical scheme of the embodiment of the application, the messages from multiple sources are aggregated to generate the aggregated message, the target device is determined according to the login time corresponding to the login log information of the multi-terminal device, and the aggregated message is sent to the target device, so that repeated indiscriminate multi-terminal sending is avoided, and the user is prevented from being disturbed.

The above-described embodiments are not intended to limit the scope of the present disclosure. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application.