CN113824625B - Information interaction method and device - Google Patents

Information interaction method and device Download PDF

Info

Publication number
CN113824625B
CN113824625B CN202110129558.XA CN202110129558A CN113824625B CN 113824625 B CN113824625 B CN 113824625B CN 202110129558 A CN202110129558 A CN 202110129558A CN 113824625 B CN113824625 B CN 113824625B
Authority
CN
China
Prior art keywords
application
information
user
identifier
user identifier
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.)
Active
Application number
CN202110129558.XA
Other languages
Chinese (zh)
Other versions
CN113824625A (en
Inventor
王守艺
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Jingdong Tuoxian Technology Co Ltd
Original Assignee
Beijing Jingdong Tuoxian Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Jingdong Tuoxian Technology Co Ltd filed Critical Beijing Jingdong Tuoxian Technology Co Ltd
Priority to CN202110129558.XA priority Critical patent/CN113824625B/en
Publication of CN113824625A publication Critical patent/CN113824625A/en
Application granted granted Critical
Publication of CN113824625B publication Critical patent/CN113824625B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04Real-time or near real-time messaging, e.g. instant messaging [IM]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/55Push-based network services

Abstract

The embodiment of the disclosure discloses a method and a device for information interaction. One embodiment of the method comprises the following steps: in response to receiving the first interaction instruction, extracting first information and a first user identifier from the first interaction instruction; determining a second user identifier corresponding to the first user identifier based on a predetermined corresponding relation between the first user identifier and the second user identifier; generating a second interaction instruction based on the first information and the second user identifier; sending a second interaction instruction to a client of a second application; responding to a third interaction instruction sent by a client of the second application, and extracting second information from the third interaction instruction; generating a fourth interaction instruction based on the second information, the first user identification and the application identification of the second application in the first application; and sending the fourth interaction instruction to the server side of the first application to instruct the server side of the first application to send the second information to the client side of the first application. The flexibility of information interaction can be improved.

Description

Information interaction method and device
Technical Field
The embodiment of the disclosure relates to the technical field of computers, in particular to the technical field of networks, and particularly relates to a method and a device for information interaction.
Background
With popularization of smart phones, functions of APP (Application) applicable to smart phones are becoming more and more abundant. For example, a user may communicate online with a healthcare worker through a health advisory-like APP; the user can also interact with other users in real time through the instant messaging APP.
In the related art, when a user obtains services through an APP of some function class, the APP needs to be downloaded, and a message pushed by the APP needs to be checked at any time.
Disclosure of Invention
The embodiment of the disclosure provides a method and a device for information interaction.
In a first aspect, embodiments of the present disclosure provide a method of information interaction, the method comprising: responding to a first interaction instruction received from a server of a first application, extracting first information and a first user identification of a first user in the first application from the first interaction instruction, wherein the first information is information generated by the first user at a client of the first application, and the first application is an instant messaging application; determining a second user identifier corresponding to the first user identifier based on a predetermined corresponding relation between the first user identifier and the second user identifier, wherein the second user identifier is the user identifier of the first user in the second application; generating a second interaction instruction based on the first information and the second user identifier; sending a second interaction instruction to a client of a second application to present second information to a second user; and responding to a third interaction instruction sent by the client of the second application, and extracting second information from the third interaction instruction, wherein the second information is generated by a second user on the client of the second application aiming at the second information; generating a fourth interaction instruction based on the second information, the first user identification and the application identification of the second application in the first application; and sending the fourth interaction instruction to the server side of the first application to instruct the server side of the first application to send the second information to the client side of the first application pointed by the first user identifier.
In some embodiments, the correspondence of the first user identification and the second user identification is determined via the steps of: responding to the binding request, extracting a current second user identifier of the current user from the binding request, and generating a first scene value corresponding to the current second user identifier; generating an image identifier based on an application identifier of the second application in the first application, a first scene value and an information sending instruction, wherein the information sending instruction is used for indicating a client of the first application for identifying the image identifier to send the first scene value and the application identifier of the second application in the first application to a server of the first application; presenting an image identifier; in response to receiving scene information sent by a server of a first application, extracting a second scene value and a current first user identifier corresponding to the second scene value from the scene information, wherein the scene information is generated by the server of the first application based on the scene value sent by a client of the first application and the first user identifier corresponding to the client of the first application; determining a corresponding relation between the current first user identifier and the current second user identifier in response to the first scene value being the same as the second scene value; and pushing prompt information of successful binding.
In some embodiments, the method further comprises: and sending the pre-generated communication address to the server side of the first application so as to instruct the server side of the first application to send the first interaction instruction and/or scene information to the communication address.
In some embodiments, sending the second interaction instruction to the client of the second application to present the second information to the second user includes: acquiring historical data corresponding to the second user identifier; determining, based on the historical data, a third user identification associated with the second user identification, the third user identification characterizing an identification of the second user in the second application; and sending the second interaction instruction to the client of the second application pointed by the third user identification.
In some embodiments, the method further comprises: responding to an information pushing request, and extracting information to be pushed and a second user identification of an object to be pushed from the information pushing request; determining a first user identifier of an object to be pushed based on a corresponding relation between the first user identifier and a second user identifier; generating an information pushing instruction based on the information to be pushed, the first user identification of the object to be pushed and the application identification of the second application in the first application; and sending the pushing information instruction to the server side of the first application to instruct the server side of the first application to send the information to be pushed to the client side of the first application pointed by the first user identification of the object to be pushed.
In a second aspect, embodiments of the present disclosure provide an apparatus for information interaction, the apparatus including: a first receiving unit configured to: responding to a first interaction instruction received from a server of a first application, extracting first information and a first user identification of a first user in the first application from the first interaction instruction, wherein the first information is information generated by the first user at a client of the first application, and the first application is an instant messaging application; the identification determining unit is configured to determine a second user identification corresponding to the first user identification based on a predetermined corresponding relation between the first user identification and the second user identification, wherein the second user identification is the user identification of the first user in the second application; the first generation unit is configured to generate a second interaction instruction based on the first information and the second user identifier; a first sending unit configured to send a second interaction instruction to a client of a second application to present second information to a second user; the second receiving unit is configured to respond to a third interaction instruction sent by the client of the second application, and extract second information from the third interaction instruction, wherein the second information is generated by a second user on the client of the second application aiming at the second information; a second generating unit configured to generate a fourth interaction instruction based on the second information, the first user identification, and an application identification of the second application in the first application; the second sending unit is configured to send a fourth interaction instruction to the server side of the first application so as to instruct the server side of the first application to send second information to the client side of the first application pointed by the first user identifier.
In some embodiments, the apparatus further comprises a binding unit configured to: responding to the binding request, extracting a current second user identifier of the current user from the binding request, and generating a first scene value corresponding to the current second user identifier; generating an image identifier based on an application identifier of the second application in the first application, a first scene value and an information sending instruction, wherein the information sending instruction is used for indicating a client of the first application for identifying the image identifier to send the first scene value and the application identifier of the second application in the first application to a server of the first application; presenting an image identifier; in response to receiving scene information sent by a server of a first application, extracting a second scene value and a current first user identifier corresponding to the second scene value from the scene information, wherein the scene information is generated by the server of the first application based on the scene value sent by a client of the first application and the first user identifier corresponding to the client of the first application; determining a corresponding relation between the current first user identifier and the current second user identifier in response to the first scene value being the same as the second scene value; and pushing prompt information of successful binding.
In some embodiments, the apparatus further comprises a communication unit configured to: and sending the pre-generated communication address to the server side of the first application so as to instruct the server side of the first application to send the first interaction instruction and/or scene information to the communication address.
In some embodiments, the first transmitting unit further comprises: the historical data acquisition module is configured to acquire historical data corresponding to the second user identifier; an associated user determination module configured to determine, based on the historical data, a third user identification associated with the second user identification, the third user identification characterizing an identification of the second user in the second application; and the instruction sending module is configured to send a second interaction instruction to the client of the second application pointed by the third user identifier.
In some embodiments, the apparatus further comprises an information push unit configured to: responding to an information pushing request, and extracting information to be pushed and a second user identification of an object to be pushed from the information pushing request; determining a first user identifier of an object to be pushed based on a corresponding relation between the first user identifier and a second user identifier; generating an information pushing instruction based on the information to be pushed, the first user identification of the object to be pushed and the application identification of the second application in the first application; and sending the pushing information instruction to the server side of the first application to instruct the server side of the first application to send the information to be pushed to the client side of the first application pointed by the first user identification of the object to be pushed.
According to the information interaction method and device, the first user can send information to the client of the second application through the first application of the instant messaging type, and receive the information sent by the second user through the client of the second application, so that the first application and the second application are communicated, information interaction among different applications is achieved, flexibility of information interaction is improved, and the user can check information sent by other applications in time through the instant messaging type application.
Drawings
Other features, objects and advantages of the present disclosure will become more apparent upon reading of the detailed description of non-limiting embodiments, made with reference to the following drawings:
FIG. 1 is an exemplary system architecture diagram in which some embodiments of the present disclosure may be applied;
FIG. 2 is a flow chart of one embodiment of a method of information interaction according to the present disclosure;
FIG. 3 is an application scenario diagram of one embodiment of the method of information interaction shown in FIG. 2;
FIG. 4 is a flow chart of yet another embodiment of a method of information interaction according to the present disclosure;
FIG. 5 is a schematic structural view of one embodiment of an apparatus for information interaction according to the present disclosure;
Fig. 6 is a schematic structural diagram of an electronic device suitable for use in implementing embodiments of the present disclosure.
Detailed Description
The present disclosure is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be noted that, for convenience of description, only the portions related to the present invention are shown in the drawings.
It should be noted that, without conflict, the embodiments of the present disclosure and features of the embodiments may be combined with each other. The present disclosure will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
Fig. 1 illustrates an exemplary system architecture 100 of a method of information interaction or an apparatus of information interaction to which embodiments of the present disclosure may be applied.
As shown in fig. 1, the system architecture 100 may include terminal devices 101, 102, 103, 104, a network 105, a server 106, and a server 107. The network 105 serves as a medium providing communication links between the terminal devices 101, 102 and the server 106, between the terminal devices 103, 104 and the server 107, and between the server 106 and the server 107. The network 105 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
The user may interact with the server 106 via the network 105 using the terminal devices 101, 102 to receive or send information or the like, for example, information generated by a first user via a client of a first application loaded on the terminal devices 101, 102 may be sent to the server 106, such that the server 106 generates an interaction instruction based on the information and sends to the server 107, and information generated by a second user via a client of a second application loaded on the terminal devices 103, 104 may also be received from the server 106.
The user may interact with the server 107 via the network 105, for example, by using the terminal devices 103, 104 to receive or send information, for example, information generated by the first user via the client of the first application may be received from the server 107, information generated by the second user via the client of the second application loaded on the terminal devices 103, 104 may be sent to the server 107, an interaction instruction may be generated by the server 107 based on the information and sent to the server 106, and finally the information may be presented to the client of the first application loaded on the terminal devices 101, 102.
The terminal devices 101, 102, 103, 104 may be hardware or software. When the terminal devices 101, 102, 103, 104 are hardware, they may be electronic devices with communication functions, including but not limited to smartphones, tablets, electronic book readers, laptop portable computers, desktop computers, and the like. The clients on which various applications are loaded, such as the clients of the first application of the instant messaging class, for example, may include WeChat, QQ, gtalk, etc., and the clients of the second application with other functionalities may be loaded, for example, may include applications of the health consultation class APP, the shopping class APP, etc. When the terminal devices 101, 102, 103, 104 are software, they can be installed in the above-listed electronic devices. It may be implemented as a plurality of software or software modules, for example, for providing distributed services, or as a single software or software module. The present invention is not particularly limited herein.
The server 106 may be a server providing various services, such as a background information server processing user information uploaded by the terminal devices 101, 102 (e.g. generating and forwarding interaction instructions based on user information and user identification). The server 107 may be a server providing various services, such as a background information server processing user information uploaded by the terminal devices 103, 104 (e.g. generating and forwarding interaction instructions based on user information and user identification). The background information server can analyze the interaction instruction analysis to send the information in the interaction instruction to the client pointed by the user identification.
It should be noted that the method of information interaction provided by the embodiment of the present disclosure may be performed by the server 107. Accordingly, the means for information interaction may be provided in the server 107.
The server may be hardware or software. When the server is hardware, the server may be implemented as a distributed server cluster formed by a plurality of servers, or may be implemented as a single server. When the server is software, it may be implemented as a plurality of software or software modules, for example, for providing distributed services, or as a single software or software module. The present invention is not particularly limited herein.
With continued reference to fig. 2, a flow 200 of one embodiment of a method of information interaction according to the present disclosure is shown. The information interaction method comprises the following steps:
in step 201, in response to receiving a first interaction instruction from a server of a first application, first information and a first user identification of a first user in the first application are extracted from the first interaction instruction.
In this embodiment, the first information is information generated by the first user at a client of the first application, and the first application is an instant messaging application.
In general, when a user sends information through a client of an application, the terminal device of the client loading the application needs to send the information to a server of the application, and then the server of the application forwards the information to other clients of the application.
As an example, the first application is a WeChat, and the second application may be another application different from the WeChat, for example, may be an APP of a health consultation class, where the APP of the health consultation class may have an enterprise public number previously set in the WeChat, and the enterprise public number is an application identifier of the health consultation class APP in the WeChat. For example, when the user needs to consult the self health problem like the APP of the health consultation class, the user can open a WeChat on the smart phone, then input information which the user wants to send in a dialogue window of the public number of the enterprise of the APP of the health consultation class, and send the information to the WeChat server (i.e. the server side of the first application) by the smart phone. After the micro-letter server receives the information, a first interaction instruction can be generated by the micro-letter ID (Identity document, identity code) of the user and the content of the information, and the first interaction instruction is sent to the server side of the health consultation APP. The WeChat ID of the user is a first user identification, and the server side of the health consultation APP is an execution subject in the example. After the execution body receives the first interaction instruction, the WeChat ID of the user and the content of the information can be extracted from the first interaction instruction.
Step 202, determining a second user identifier corresponding to the first user identifier based on a predetermined correspondence between the first user identifier and the second user identifier.
In this embodiment, the second user identifier is a user identifier of the first user in the second application, for example, may be a user ID that the first user registers in the second application in advance.
As an example, when the user registers information in the second application, the contact manner of the user may be provided in advance, where the contact manner may include the first user identifier of the user in the first application, so the execution body may establish a correspondence between the first user identifier and the second user identifier of the user.
In some optional implementations of this embodiment, the correspondence between the first user identifier and the second user identifier is determined via the following steps: responding to the binding request, extracting a current second user identifier of the current user from the binding request, and generating a first scene value corresponding to the current second user identifier; generating an image identifier based on an application identifier of the second application in the first application, a first scene value and an information sending instruction, wherein the information sending instruction is used for indicating a client of the first application for identifying the image identifier to send the first scene value and the application identifier of the second application in the first application to a server of the first application; presenting an image identifier; in response to receiving scene information sent by a server of a first application, extracting a second scene value and a current first user identifier corresponding to the second scene value from the scene information, wherein the scene information is generated by the server of the first application based on the scene value sent by a client of the first application and the first user identifier corresponding to the client of the first application; determining a corresponding relation between the current first user identifier and the current second user identifier in response to the first scene value being the same as the second scene value; and pushing prompt information of successful binding.
In this implementation manner, the image identifier may be permanently valid, or may be preset with a validity period, and since the permanent image identifier occupies more storage space, the execution subject may provide a small amount of permanent image identifiers, and the temporary image identifier with the preset validity period may be used as cache data, which may not be limited in number.
As an example, when a first user wants to associate a first application with a second application, a binding request may be entered in a web page provided by the second application, and a second user identification of the user in the second application may be entered in the binding request. After receiving the binding request, the executing body (e.g., the server 107 shown in fig. 1) may extract the current second user identifier of the current user from the binding request, generate a first scene value a, and generate a corresponding relationship between the first scene value a and the second user identifier in the background of the executing body. Then, the execution body generates an image identifier, which may be, for example, a temporary two-dimensional code image, based on the application identifier of the second application in the first application (for example, an ID registered in the first application by the name of the second application), the first scene value a, and the information transmission instruction, and presents the image identifier on the web page. The user uses the client side of the first application loaded on the terminal equipment to identify the image identifier, can acquire the application identifiers of the first scene A and the second application in the first application, and executes an information sending instruction to send the application identifiers of the first scene A and the second application in the first application to the server side of the first application. After the server of the first application receives the information sent by the client, scene value information (for example, a data packet in XML format) may be generated based on the current first application identifier corresponding to the client that sends the information and the first scene value a. Then, the server side of the first application may send the scene information to the location pointed by the application identifier of the second application in the first application. In this way, after the execution body (i.e. the location pointed to by the application identification of the second application in the first application) receives the context information, the second context value B and the current first user identification can be extracted therefrom. If the second scene value B is the same as the first scene value A, the binding operation of the current user is verified, and the corresponding relation between the first user identifier and the second user identifier can be determined. Finally, a prompt message of "successful binding" can be presented on the web page.
The method for establishing the corresponding relation between the first user identifier and the second user identifier simplifies the association operation of the same user between two applications.
The implementation method can further comprise the following steps: the pre-generated communication address is sent to the server side of the first application, so that the server side of the first application is instructed to send the first interaction instruction and/or scene information to the communication address.
The communication address characterizes the communication address of the executing body, so that after the server side of the first application receives the information (for example, the first interaction instruction or the scene information) containing the application identifier of the second application in the first application, the information can be sent to the executing body. The communication address may be, for example, a URL (uniform resource locator ) of the server side of the second application.
Step 203, generating a second interaction instruction based on the first information and the second user identification.
In this embodiment, the second interaction instruction characterizes an interaction instruction of the first user with other users through the second application, and the second user identifier characterizes an identifier of the user sending the first information. As an example, the execution body may combine the second user identification with the first information to obtain the second interaction instruction.
And step 204, sending the second interaction instruction to the client of the second application.
In this embodiment, the execution body may send the second interaction instruction to the client that determines the second application according to the preset policy, so as to present the second information to the second user, so that the execution body realizes that the information generated by the first application is transferred to the user of the second application.
The second user may characterize a general user as well as a user providing business services.
By way of example, the preset policy may be, for example, a randomly determined user providing a business service. For another example, the executing body may identify a keyword in the first information, determine a plurality of second users matching the keyword, and then send a second interaction instruction to clients corresponding to the plurality of second users, so that the second information is presented to the second users, where the second information includes information content and a second user identifier for sending the information.
In step 205, in response to receiving the third interaction instruction sent by the client of the second application, second information is extracted from the third interaction instruction.
In this embodiment, the second information is information generated by the second user at the client of the second application for the second information, and represents a reply made by the second user to the first user through the client of the second application.
It should be noted that, the second application in this embodiment may support two types of uplink messages and offline messages of a session at the same time, so that a user of the second application may perform real-time interaction or send an offline message.
In one specific example, the second user is a user providing business services. In step 204, after the execution body presents the second information to the second user, the second user learns the service requirement of the first user through the second information, and may make a targeted reply through the client of the second application, and the terminal device of the second user may combine the reply information and the reply object (the first user represented by the second user identifier) into a third interaction instruction, and send the third interaction instruction to the execution body. Thus, the execution body can extract the second information from the third interaction instruction, namely the reply information provided for the second user.
Step 206, generating a fourth interaction instruction based on the second information, the first user identification and the application identification of the second application in the first application.
In this embodiment, the execution body may use the first user represented by the first user identifier as the receiving party of the second information, and use the user represented by the application identifier of the second application in the first application as the sending party of the second information, so as to obtain the fourth interaction instruction.
Step 207, sending the fourth interaction instruction to the server of the first application, so as to instruct the server of the first application to send the second information to the client of the first application pointed by the first user identifier.
As an example, after the execution body sends the fourth interaction instruction to the server side of the first application, the service short of the first application may extract the second information, the first user identifier and the application identifier of the second application in the first application from the fourth interaction instruction, then use the client side of the first application pointed by the first user identifier as a receiver of the second information, and then use the user pointed by the second application identifier in the first application as a sender of the second information, and present the second information on the terminal device of the first user.
In the flow 200 shown in fig. 2, steps 201 to 204 implement that the first user sends information to the second application through the first application, and steps 205 to 207 implement that the second user sends information to the first application through the second application, so that information interaction between different applications by different users is implemented.
With continued reference to fig. 3, fig. 3 is a schematic illustration of an application scenario of the flow of the method shown in fig. 2. In the scenario 300 shown in fig. 3, the first application may be a WeChat and the second application may be a health advisory type application, and then the application identification of the second application in the first application is the public number of the enterprise of the health advisory type application in the WeChat. The first user may send information to the public number of the enterprise in the WeChat by using the WeChat client loaded on the smartphone 301, and the smartphone 301 sends the information to the WeChat server 302 through the network. After receiving the information, the server 302 may generate a first interaction instruction according to the first user ID and the information content, and send the first interaction instruction to the server 303 of the health consultation application (that is, the execution subject of the present example). The server 303 may extract the first information 305 and the WeChat ID (i.e. the first user identifier) of the first user from the first interaction instruction, and determine the ID (i.e. the second user identifier) of the first user in the health consultation type application based on the corresponding relationship between the predetermined WeChat ID and the ID in the health consultation type application. The server 303 may then generate a second interaction instruction based on the first information 305 and the ID of the first user in the health advisory class application and send the second interaction instruction to the smartphone 304 used by the second user, such that the second user (which may be, for example, a healthcare worker providing advisory services) may receive the information sent by the first user through the health advisory class application loaded on the smartphone 304.
After that, the second user may reply to the received information, and the smartphone 304 generates a third interaction instruction according to the information content (i.e. the second information 306) replied by the second user and the ID of the second user in the health consultation application, and sends the third interaction instruction to the server 303. The server 303 may extract the second information 306 from the third interaction instruction and generate a fourth interaction instruction based on the second information 306, the WeChat ID of the first user, and the public number of the enterprise in the WeChat for which the health advisory class is applied. The server 303 then sends the fourth interaction instruction to the WeChat server 302, and the WeChat server 302 sends the second information to the smartphone 301, so that the WeChat client loaded on the smartphone 301 can receive the second information, which is sent on behalf of the public number of the enterprise in the WeChat, where the health consultation type is applied. The method and the system realize that the first user sends the information to the health consultation type application through the WeChat, the health consultation type application sends the information to the second user, and the second user sends the information replied by the client of the health consultation type application to the WeChat client of the first user, so that the information interaction between the first user and the second user is realized.
According to the information interaction method and device, the first user can send information to the client of the second application through the first application of the instant messaging type, and receive the information sent by the second user through the client of the second application, so that the first application and the second application are communicated, information interaction among different applications is achieved, flexibility of information interaction is improved, and the user can check information sent by other applications in time through the instant messaging type application.
With further reference to fig. 4, a flow 400 of yet another embodiment of a method of information interaction is shown. The flow 400 of the method of information interaction comprises the steps of:
in step 401, in response to receiving the first interaction instruction from the server of the first application, first information and a first user identification of the first user in the first application are extracted from the first interaction instruction.
Step 402, determining a second user identifier corresponding to the first user identifier based on a predetermined correspondence between the first user identifier and the second user identifier, where the second user identifier is a user identifier of the first user in the second application.
Step 403, generating a second interaction instruction based on the first information and the second user identification.
Steps 401 to 403 correspond to steps 201 to 203, respectively, and are not described here again.
Step 404, obtaining historical data corresponding to the second user identifier.
The history data may include session records or registration information, etc. of the user in the second application, as characterized by the second user identification.
Step 405, determining a third user identification associated with the second user identification based on the history data.
In this embodiment, the third user identification characterizes the identification of the second user in the second application.
In a specific example, the execution body may retrieve whether a session of the second user identification exists in the database, and if so, determine the user identification of the session object in the session as the third user identification.
Taking the health consultation application as an example, the historical data may include physical condition information (for example, may be a physiological index, inquiry information or pathology information) provided by the first user, the execution subject may input the historical data corresponding to the second user identifier into a pre-trained machine learning model, for example, a time semantic analysis model or a classification model, etc., estimate an information category (for example, may be information including symptoms or pathology) that the first user desires to consult, and then combine the service areas that the service personnel is good at, and determine the user identifier of the service personnel corresponding to the service area with the highest matching degree of the information category as the third user identifier.
And step 406, sending the second interaction instruction to the client of the second application pointed by the third user identifier.
Step 407, in response to receiving the third interaction instruction sent by the client of the second application, extracting second information from the third interaction instruction, where the second information is information generated by the second user at the client of the second application for the second information.
In step 408, a fourth interaction instruction is generated based on the second information, the first user identification, and an application identification of the second application in the first application.
Step 409, sending a fourth interaction instruction to the server of the first application, so as to instruct the server of the first application to send the second information to the client of the first application pointed by the first user identifier. Steps 407 to 409 correspond to steps 205 to 207, and are not described here again.
As can be seen from fig. 4, the flow 400 of the method for information interaction in this embodiment highlights the step of determining the second user that matches the first user based on the history data of the first user in the second application, so that the pertinence of information interaction can be improved.
In some optional implementations of the foregoing embodiments, the method for information interaction of the present disclosure may further include the steps of: responding to an information pushing request, and extracting information to be pushed and a second user identification of an object to be pushed from the information pushing request; determining a first user identifier of an object to be pushed based on a corresponding relation between the first user identifier and a second user identifier; generating an information pushing instruction based on the information to be pushed, the first user identification of the object to be pushed and the application identification of the second application in the first application; and sending the pushing information instruction to the server side of the first application to instruct the server side of the first application to send the information to be pushed to the client side of the first application pointed by the first user identification of the object to be pushed.
In a specific example, an operator of the application may generate information to be pushed according to service requirements, generate an information push request based on the information to be pushed and the object to be pushed, and send the information push request to a server of the application (i.e., an execution subject of the present example). And then the execution body extracts the information to be pushed and the second user identification of the object to be pushed from the information push request, and determines the first user identification of the user represented by the second user identification in the first application. And then, the execution main body generates an information pushing instruction based on the information to be pushed, the first user identification of the object to be pushed and the application identification of the second application in the first application, and sends the information pushing instruction to a server of the first application. And the server of the first application determines the user represented by the application identifier of the second application in the first application as a sender of the information to be pushed, and sends the information to be pushed to the client of the first application corresponding to each first user identifier in the information pushing instruction. Therefore, the information is pushed to the user of the first application by the user through the second application.
In the implementation manner, the user can push information to the user of the first application through the second application, so that the flexibility of information interaction can be improved.
With further reference to fig. 5, as an implementation of the method shown in the foregoing figures, the present disclosure provides an embodiment of an apparatus for information interaction, where the embodiment of the apparatus corresponds to the embodiment of the method shown in fig. 2, and the apparatus may be specifically applied to various electronic devices.
As shown in fig. 5, the information interaction device 500 of the present embodiment includes: the first receiving unit 501 is configured to: responding to a first interaction instruction received from a server of a first application, extracting first information and a first user identification of a first user in the first application from the first interaction instruction, wherein the first information is information generated by the first user at a client of the first application, and the first application is an instant messaging application; an identification determining unit 502 configured to determine a second user identification corresponding to the first user identification based on a predetermined correspondence between the first user identification and the second user identification, the second user identification being a user identification of the first user in the second application; a first generating unit 503 configured to generate a second interaction instruction based on the first information and the second user identification; a first sending unit 504 configured to send a second interaction instruction to the client of the second application to present the second information to the second user; and a second receiving unit 505, configured to respond to receiving a third interaction instruction sent by the client of the second application, and extract second information from the third interaction instruction, where the second information is information generated by the second user at the client of the second application for the second information; a second generating unit 506 configured to generate a fourth interaction instruction based on the second information, the first user identification, and an application identification of the second application in the first application; the second sending unit 507 is configured to send a fourth interaction instruction to the server side of the first application, so as to instruct the server side of the first application to send the second information to the client side of the first application pointed by the first user identifier.
In this embodiment, the apparatus 500 further includes a binding unit configured to: responding to the binding request, extracting a current second user identifier of the current user from the binding request, and generating a first scene value corresponding to the current second user identifier; generating an image identifier based on an application identifier of the second application in the first application, a first scene value and an information sending instruction, wherein the information sending instruction is used for indicating a client of the first application for identifying the image identifier to send the first scene value and the application identifier of the second application in the first application to a server of the first application; presenting an image identifier; in response to receiving scene information sent by a server of a first application, extracting a second scene value and a current first user identifier corresponding to the second scene value from the scene information, wherein the scene information is generated by the server of the first application based on the scene value sent by a client of the first application and the first user identifier corresponding to the client of the first application; determining a corresponding relation between the current first user identifier and the current second user identifier in response to the first scene value being the same as the second scene value; and pushing prompt information of successful binding.
In this embodiment, the apparatus 500 further comprises a communication unit configured to: and sending the pre-generated communication address to the server side of the first application so as to instruct the server side of the first application to send the first interaction instruction and/or scene information to the communication address.
In this embodiment, the first transmitting unit 504 further includes: the historical data acquisition module is configured to acquire historical data corresponding to the second user identifier; an associated user determination module configured to determine, based on the historical data, a third user identification associated with the second user identification, the third user identification characterizing an identification of the second user in the second application; and the instruction sending module is configured to send a second interaction instruction to the client of the second application pointed by the third user identifier.
In this embodiment, the apparatus 500 further includes an information pushing unit configured to: responding to an information pushing request, and extracting information to be pushed and a second user identification of an object to be pushed from the information pushing request; determining a first user identifier of an object to be pushed based on a corresponding relation between the first user identifier and a second user identifier; generating an information pushing instruction based on the information to be pushed, the first user identification of the object to be pushed and the application identification of the second application in the first application; and sending the pushing information instruction to the server side of the first application to instruct the server side of the first application to send the information to be pushed to the client side of the first application pointed by the first user identification of the object to be pushed.
Referring now to fig. 6, a schematic diagram of an electronic device (e.g., server or terminal device of fig. 1) 600 suitable for use in implementing embodiments of the present disclosure is shown. The terminal device in the embodiments of the present disclosure may include, but is not limited to, a mobile terminal such as a mobile phone, a notebook computer, a digital broadcast receiver, a PDA (personal digital assistant), a PAD (tablet computer), etc., and a fixed terminal such as a digital TV, a desktop computer, etc. The terminal device shown in fig. 6 is only one example, and should not impose any limitation on the functions and scope of use of the embodiments of the present disclosure.
As shown in fig. 6, the electronic device 600 may include a processing means (e.g., a central processing unit, a graphics processor, etc.) 601, which may perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 602 or a program loaded from a storage means 608 into a Random Access Memory (RAM) 603. In the RAM603, various programs and data required for the operation of the electronic apparatus 600 are also stored. The processing device 601, the ROM 602, and the RAM603 are connected to each other through a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
In general, the following devices may be connected to the I/O interface 605: input devices 606 including, for example, a touch screen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, and the like; an output device 607 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 608 including, for example, magnetic tape, hard disk, etc.; and a communication device 609. The communication means 609 may allow the electronic device 600 to communicate with other devices wirelessly or by wire to exchange data. While fig. 6 shows an electronic device 600 having various means, it is to be understood that not all of the illustrated means are required to be implemented or provided. More or fewer devices may be implemented or provided instead. Each block shown in fig. 6 may represent one device or a plurality of devices as needed.
In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network via communication means 609, or from storage means 608, or from ROM 602. The above-described functions defined in the methods of the embodiments of the present disclosure are performed when the computer program is executed by the processing means 601. It should be noted that, the computer readable medium according to the embodiments of the present disclosure may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any 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 an embodiment of the present disclosure, 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. Whereas in embodiments of the present disclosure, the computer-readable signal medium may comprise a data signal propagated in baseband or as part of a carrier wave, with computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. 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: electrical wires, fiber optic cables, RF (radio frequency), and the like, or any suitable combination of the foregoing.
The computer readable medium may be contained in the electronic device; or may exist alone without being incorporated into the electronic device. The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: responding to a first interaction instruction received from a server of a first application, extracting first information and a first user identification of a first user in the first application from the first interaction instruction, wherein the first information is information generated by the first user at a client of the first application, and the first application is an instant messaging application; determining a second user identifier corresponding to the first user identifier based on a predetermined corresponding relation between the first user identifier and the second user identifier, wherein the second user identifier is the user identifier of the first user in the second application; generating a second interaction instruction based on the first information and the second user identifier; sending a second interaction instruction to a client of a second application to present second information to a second user; and responding to a third interaction instruction sent by the client of the second application, and extracting second information from the third interaction instruction, wherein the second information is generated by a second user on the client of the second application aiming at the second information; generating a fourth interaction instruction based on the second information, the first user identification and the application identification of the second application in the first application; and sending the fourth interaction instruction to the server side of the first application to instruct the server side of the first application to send the second information to the client side of the first application pointed by the first user identifier.
Computer program code for carrying out operations of embodiments of the present disclosure may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).
The flowcharts 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 disclosure. 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 and/or flowchart illustration, and combinations of blocks in the block diagrams and/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 involved in the embodiments described in the present disclosure may be implemented by means of software, or may be implemented by means of hardware. The described units may also be provided in a processor, for example, described as: a processor includes a first receiving unit, an identification determining unit, a first generating unit, a first transmitting unit, a second receiving unit, a second generating unit, and a second transmitting unit. The names of these units do not in some cases limit the unit itself, for example, the first receiving unit may also be described as "a unit that, in response to receiving the first interaction instruction from the service end of the first application, extracts the first information from the first interaction instruction and the first user identification of the first user in the first application".
The foregoing description is only of the preferred embodiments of the present disclosure and description of the principles of the technology being employed. It will be appreciated by those skilled in the art that the scope of the invention in the embodiments of the present disclosure is not limited to the specific combination of the above technical features, but encompasses other technical features formed by any combination of the above technical features or their equivalents without departing from the spirit of the invention. Such as the above-described features, are mutually substituted with (but not limited to) the features having similar functions disclosed in the embodiments of the present disclosure.

Claims (10)

1. A method of information interaction, comprising:
responding to a first interaction instruction received from a server of a first application, extracting first information and a first user identification of a first user in the first application from the first interaction instruction, wherein the first information is generated by the first user at a client of the first application, and the first application is an instant messaging application; determining a second user identifier corresponding to the first user identifier based on a predetermined corresponding relation between the first user identifier and the second user identifier, wherein the second user identifier is the user identifier of the first user in a second application; generating a second interaction instruction based on the first information and the second user identifier; acquiring historical data corresponding to the second user identifier; determining a third user identification associated with the second user identification based on the historical data, comprising: inputting the historical data into a pre-trained machine learning model, generating an information category corresponding to the historical data, and determining a user identifier of a business person with the highest matching degree with the information category as a third user identifier associated with the second user identifier, wherein the third user identifier characterizes the identifier of the second user in the second application; sending the second interaction instruction to a client of the second application pointed by the third user identifier; the method comprises the steps of,
Responding to a third interaction instruction sent by a client of the second application, and extracting second information from the third interaction instruction, wherein the second information is generated by the second user on the client of the second application aiming at the first information; generating a fourth interaction instruction based on the second information, the first user identification and an application identification of the second application in the first application; and sending the fourth interaction instruction to the server side of the first application to instruct the server side of the first application to send the second information to the client side of the first application pointed by the first user identifier.
2. The method of claim 1, wherein the correspondence of the first user identification to the second user identification is determined via:
responding to a binding request, extracting a current second user identifier of a current user from the binding request, and generating a first scene value corresponding to the current second user identifier;
generating an image identifier based on an application identifier of the second application in the first application, the first scene value and an information sending instruction, wherein the information sending instruction is used for indicating a client of the first application identifying the image identifier to send the first scene value and the application identifier of the second application in the first application to a server of the first application;
Presenting the image identifier;
responding to receiving scene information sent by a server side of the first application, extracting a second scene value and a current first user identifier corresponding to the second scene value from the scene information, wherein the scene information is generated by the server side of the first application based on the scene value sent by a client side of the first application and the first user identifier corresponding to the client side of the first application;
determining a corresponding relation between the current first user identification and the current second user identification in response to the first scene value being the same as the second scene value;
and pushing prompt information of successful binding.
3. The method of claim 2, the method further comprising:
and sending a pre-generated communication address to the server side of the first application so as to instruct the server side of the first application to send the first interaction instruction and/or the scene information to the communication address.
4. A method according to one of claims 1 to 3, the method further comprising:
responding to an information pushing request, and extracting information to be pushed and a second user identification of an object to be pushed from the information pushing request;
Determining the first user identification of the object to be pushed based on the corresponding relation between the first user identification and the second user identification;
generating an information pushing instruction based on the information to be pushed, the first user identification of the object to be pushed and the application identification of the second application in the first application;
and sending the information pushing instruction to the server side of the first application to instruct the server side of the first application to send the information to be pushed to the client side of the first application pointed by the first user identifier of the object to be pushed.
5. An apparatus for information interaction, comprising:
a first receiving unit configured to: responding to a first interaction instruction received from a server of a first application, extracting first information and a first user identification of a first user in the first application from the first interaction instruction, wherein the first information is generated by the first user at a client of the first application, and the first application is an instant messaging application;
an identification determining unit configured to determine a second user identification corresponding to a first user identification based on a predetermined correspondence between the first user identification and the second user identification, the second user identification being a user identification of the first user in a second application;
The first generation unit is configured to generate a second interaction instruction based on the first information and the second user identifier;
a first transmitting unit comprising: the historical data acquisition module is configured to acquire historical data corresponding to the second user identifier; an associated user determination module configured to determine a third user identification associated with the second user identification based on the historical data, comprising: inputting the historical data into a pre-trained machine learning model, generating an information category corresponding to the historical data, and determining a user identifier of a business person with the highest matching degree with the information category as a third user identifier associated with the second user identifier, wherein the third user identifier characterizes the identifier of the second user in the second application; the instruction sending module is configured to send the second interaction instruction to a client of the second application pointed by the third user identifier; the method comprises the steps of,
the second receiving unit is configured to respond to receiving a third interaction instruction sent by the client of the second application, and extract second information from the third interaction instruction, wherein the second information is generated by the second user on the client of the second application aiming at the second information;
A second generating unit configured to generate a fourth interaction instruction based on the second information, the first user identification, and an application identification of the second application in the first application;
and the second sending unit is configured to send the fourth interaction instruction to the server side of the first application so as to instruct the server side of the first application to send the second information to the client side of the first application pointed by the first user identifier.
6. The apparatus of claim 5, further comprising a binding unit configured to:
responding to a binding request, extracting a current second user identifier of a current user from the binding request, and generating a first scene value corresponding to the current second user identifier;
generating an image identifier based on an application identifier of the second application in the first application, the first scene value and an information sending instruction, wherein the information sending instruction is used for indicating a client of the first application identifying the image identifier to send the first scene value and the application identifier of the second application in the first application to a server of the first application;
presenting the image identifier;
Responding to receiving scene information sent by a server side of the first application, extracting a second scene value and a current first user identifier corresponding to the second scene value from the scene information, wherein the scene information is generated by the server side of the first application based on the scene value sent by a client side of the first application and the first user identifier corresponding to the client side of the first application;
determining a corresponding relation between the current first user identification and the current second user identification in response to the first scene value being the same as the second scene value;
and pushing prompt information of successful binding.
7. The apparatus of claim 6, further comprising a communication unit configured to:
and sending a pre-generated communication address to the server side of the first application so as to instruct the server side of the first application to send the first interaction instruction and/or the scene information to the communication address.
8. The apparatus according to one of claims 5 to 7, further comprising an information push unit configured to:
responding to an information pushing request, and extracting information to be pushed and a second user identification of an object to be pushed from the information pushing request;
Determining the first user identification of the object to be pushed based on the corresponding relation between the first user identification and the second user identification;
generating an information pushing instruction based on the information to be pushed, the first user identification of the object to be pushed and the application identification of the second application in the first application;
and sending the information pushing instruction to the server side of the first application to instruct the server side of the first application to send the information to be pushed to the client side of the first application pointed by the first user identifier of the object to be pushed.
9. An electronic device, comprising:
one or more processors;
a storage device having one or more programs stored thereon,
when executed by the one or more processors, causes the one or more processors to implement the method of any of claims 1-4.
10. A computer readable medium having stored thereon a computer program, wherein the program when executed by a processor implements the method of any of claims 1-4.
CN202110129558.XA 2021-01-29 2021-01-29 Information interaction method and device Active CN113824625B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110129558.XA CN113824625B (en) 2021-01-29 2021-01-29 Information interaction method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110129558.XA CN113824625B (en) 2021-01-29 2021-01-29 Information interaction method and device

Publications (2)

Publication Number Publication Date
CN113824625A CN113824625A (en) 2021-12-21
CN113824625B true CN113824625B (en) 2023-05-12

Family

ID=78912372

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110129558.XA Active CN113824625B (en) 2021-01-29 2021-01-29 Information interaction method and device

Country Status (1)

Country Link
CN (1) CN113824625B (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111125512A (en) * 2019-11-18 2020-05-08 口碑(上海)信息技术有限公司 Service recommendation processing method, device and system
CN111612512A (en) * 2020-04-11 2020-09-01 上海淇玥信息技术有限公司 Resource allocation method and device and electronic equipment
CN111861228A (en) * 2020-07-23 2020-10-30 深圳前海微众银行股份有限公司 Customer service information processing method, device, equipment and medium based on user behaviors

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104639424B (en) * 2015-01-07 2020-09-25 腾讯科技(深圳)有限公司 Data transmission method and related equipment and system
CN104717131B (en) * 2015-02-13 2017-09-15 腾讯科技(深圳)有限公司 Information interacting method and server
US10204098B2 (en) * 2017-02-13 2019-02-12 Antonio GONZALO VACA Method and system to communicate between devices through natural language using instant messaging applications and interoperable public identifiers
CN108809805B (en) * 2018-05-25 2020-04-28 腾讯科技(深圳)有限公司 Information interaction method and system and public account client
CN110708346B (en) * 2018-07-09 2023-03-21 北京高绎信息技术有限公司 Information processing system and method
CN109672749B (en) * 2019-01-07 2021-08-10 腾讯科技(深圳)有限公司 Method and device for intercommunicating applications of heterogeneous systems
CN111612135B (en) * 2020-05-22 2024-04-16 京东科技控股股份有限公司 Method and device for information interaction

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111125512A (en) * 2019-11-18 2020-05-08 口碑(上海)信息技术有限公司 Service recommendation processing method, device and system
CN111612512A (en) * 2020-04-11 2020-09-01 上海淇玥信息技术有限公司 Resource allocation method and device and electronic equipment
CN111861228A (en) * 2020-07-23 2020-10-30 深圳前海微众银行股份有限公司 Customer service information processing method, device, equipment and medium based on user behaviors

Also Published As

Publication number Publication date
CN113824625A (en) 2021-12-21

Similar Documents

Publication Publication Date Title
CN107622135B (en) Method and apparatus for displaying information
CN105721462B (en) Information pushing method and device
CN112311841B (en) Information pushing method and device, electronic equipment and computer readable medium
CN111160845A (en) Service processing method and device
CN110430292B (en) Method and device for inviting login of network platform, electronic equipment and readable medium
CN112395509A (en) Information display method, information providing method, apparatus, and computer-readable medium
CN108549586B (en) Information processing method and device
CN111460049A (en) Content sharing method and device, electronic equipment and computer readable storage medium
CN110618768B (en) Information presentation method and device
CN109241409B (en) Method and device for sending and receiving information
CN111447191A (en) Information interaction method and device and electronic equipment
CN108667915B (en) Information pushing system, method and device
CN110855655B (en) Information verification method, device, equipment and storage medium
CN110708238B (en) Method and apparatus for processing information
CN110519373B (en) Method and device for pushing information
CN109995543B (en) Method and apparatus for adding group members
CN113824625B (en) Information interaction method and device
CN111787041A (en) Method and apparatus for processing data
CN113079085B (en) Business service interaction method, business service interaction device, business service interaction equipment and storage medium
CN113722589B (en) Information generation method, device, server and storage medium
CN111460020B (en) Method, device, electronic equipment and medium for resolving message
CN114417318A (en) Third-party page jumping method and device and electronic equipment
KR20150072680A (en) Apparatus and Method for managing Safety Number
CN109768921B (en) Data transparent transmission method and corresponding instant communication terminal
CN111597485B (en) Information presentation 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
GR01 Patent grant
GR01 Patent grant