CN110417915B - Push message transmission method and device, storage medium and electronic equipment - Google Patents
Push message transmission method and device, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN110417915B CN110417915B CN201910778386.1A CN201910778386A CN110417915B CN 110417915 B CN110417915 B CN 110417915B CN 201910778386 A CN201910778386 A CN 201910778386A CN 110417915 B CN110417915 B CN 110417915B
- Authority
- CN
- China
- Prior art keywords
- user terminal
- long connection
- server
- service
- push message
- 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
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
Abstract
The embodiment of the application discloses a push message transmission method, a push message transmission device, a storage medium and a server, wherein the method comprises the following steps: receiving a push message sent by a service server through a domain name server, wherein the push message is a fault notification message generated when the service server detects that a network fault occurs in a first user terminal, and establishing a long connection service between a long connection server and a second user terminal by adopting a preset communication architecture, and the second user terminal is a terminal device which is in network communication with the first user terminal and transmits the push message to the second user terminal by adopting the long connection service. By adopting the embodiment of the application, the time delay of the server for sending the push message to the user terminal can be reduced.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a push message transmission method and apparatus, a storage medium, and an electronic device.
Background
With the development of internet technology, a new education mode, remote teaching, is more and more popular.
In remote lessons, students and teachers generally acquire lesson data of the other party through an online education system, thereby realizing the lesson function. When a student or a teacher has a party who has a class break due to a network failure, the online education system pushes a notification message of the network failure of the other party to a party who is in a normal state of the network through the server.
Before the server pushes the message to the user terminal, a communication connection between the server and the user terminal needs to be established. Currently, a user terminal establishes a communication connection with a server in a polling manner, that is, the user terminal periodically sends a connection request to the server based on a polling period to establish a connection service between the user terminal and the server, and releases the connection service after completing message push through the connection service, and reestablishes the connection service between the user terminal and the server when the user terminal needs to push a message next time. In the process, the user terminal can only send the connection request to the server at regular time, but when the time that the students and teachers interrupt the class due to network failure does not reach the regular time, the students and teachers need to wait for the arrival of the regular time, so that the time delay of sending the push message to the user terminal by the server is increased.
Disclosure of Invention
The embodiment of the application provides a push message transmission method, a push message transmission device, a storage medium and electronic equipment, which can reduce the time delay of a server for sending a push message to a user terminal. The technical scheme is as follows:
in a first aspect, an embodiment of the present application provides a push message transmission method, where the method includes:
receiving a push message sent by a service server through a domain name server, wherein the push message is a fault notification message generated when the service server detects that a first user terminal has a network fault;
establishing a long connection service between a long connection server and a second user terminal by adopting a preset communication architecture, wherein the second user terminal is a terminal device which is in network communication with the first user terminal;
and transmitting the push message to the second user terminal by adopting a long connection service.
In a second aspect, an embodiment of the present application provides a push message transmission apparatus, where the apparatus includes:
the message receiving module is used for receiving a push message sent by a service server through a domain name server, wherein the push message is a fault notification message generated when the service server detects that a first user terminal has a network fault;
the system comprises a connection establishing module, a first user terminal and a second user terminal, wherein the connection establishing module is used for establishing a long connection service between a long connection server and the second user terminal by adopting a preset communication architecture, and the second user terminal is terminal equipment which is in network communication with the first user terminal;
and the message transmission module is used for transmitting the push message to the second user terminal by adopting a long connection service.
In a third aspect, embodiments of the present application provide a computer storage medium storing a plurality of instructions adapted to be loaded by a processor and to perform the above-mentioned method steps.
In a fourth aspect, an embodiment of the present application provides an electronic device, which may include: a processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and to perform the above-mentioned method steps.
The beneficial effects brought by the technical scheme provided by some embodiments of the application at least comprise:
in one or more embodiments of the present application, a long connection server receives a push message sent by a service server through a domain name server, where the push message is a failure notification message generated when the service server detects a network failure of a first user terminal, and a preset communication architecture is used to establish a long connection service between the long connection server and a second user terminal, where the second user terminal is a terminal device that performs network communication with the first user terminal, and transmits the push message to the second user terminal by using the long connection service. By establishing the long connection service between the second user terminal and the long connection server, the fault notification message can be directly sent to the second user terminal through the long connection service, and the time delay of sending the push message to the user terminal by the server is reduced.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic view of a scenario architecture of push message transmission according to an embodiment of the present application;
fig. 2 is a schematic flowchart of a push message transmission method according to an embodiment of the present application;
fig. 3 is a schematic flowchart of another push message transmission method provided in an embodiment of the present application;
fig. 4a is a scene diagram related to a push message transmission according to an embodiment of the present application;
fig. 4b is a diagram of a scenario involved in another push message transmission provided in an embodiment of the present application;
fig. 5 is a schematic structural diagram of a push message transmission apparatus according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of another push message transmission apparatus provided in an embodiment of the present application;
fig. 7 is a schematic structural diagram of a connection establishing module according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of a server according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In the description of the present application, it is to be understood that the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. In the description of the present application, it is noted that, unless explicitly stated or limited otherwise, "including" and "having" and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus. The specific meaning of the above terms in the present application can be understood in a specific case by those of ordinary skill in the art. Further, in the description of the present application, "a plurality" means two or more unless otherwise specified. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.
The present application will be described in detail with reference to specific examples.
Please refer to fig. 1, which is a schematic structural diagram of a push message transmission system according to an embodiment of the present application. As shown in fig. 1, the push message transmission system may include a service server 100, a domain name server 110, a long connection server 120, and a user terminal 130.
The service server 100, the domain name server 110, and the long connection server 120 may be separate server devices, such as: rack, blade, tower or cabinet type server equipment, or hardware equipment with stronger computing power such as a workstation and a large computer; the server cluster can also be a server cluster formed by a plurality of servers, each server in the service cluster can be formed in a symmetrical mode, wherein each server has equivalent functions and equivalent positions in a service link, each server can provide services for the outside independently, and the independent service can be understood as the assistance without other servers.
The user terminal 130 may be a terminal device with a network access function, which includes but is not limited to: personal computers, tablet computers, handheld devices, in-vehicle devices, wearable devices, computing devices or other processing devices connected to a wireless modem, and the like. The user terminals 130 may be called different names in different networks, for example: user equipment, access terminal, subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent or user equipment, cellular telephone, cordless telephone, Personal Digital Assistant (PDA), terminal equipment in a 5G network or future evolution network, and the like.
In the embodiment of the present application, the push message transmission device is the long connection server 120.
When the service server 100 detects a network failure of the first user terminal, a failure notification message is sent to the second user terminal 130 via the messaging link.
The message transmission link refers to a data link or a physical link for transmitting message data, and generally, the message transmission link includes a service server, a switch, a gateway device, and the like. In this embodiment, the message transmission link may be understood as a path where the failure notification message is transmitted at each node, that is, a link composed of the service server 100, the domain name server 110, the long connection server 120, and the user terminal 130.
Specifically, when the first user terminal has a network failure, the network failure may be a network device failure, or a network failure caused by human misoperation. When the service server 100 detects the network failure, the service server 100 reads and executes a machine executable instruction corresponding to the control logic of the "network failure", and the service server 100 identifies and detects that the first user terminal has the network failure by executing the instruction, so as to generate the failure notification message, transmit the failure notification message through each node (domain name server, long connection server, etc.) of the message transmission link, and finally send the failure notification message to the second user terminal 130.
The second user terminal 130 sends a long connection request to the domain name server 110 based on a preset communication architecture, so that the domain name server 110 determines a long connection server 120 in a long connection server cluster and establishes a long connection service between the long connection server 120 and the second user terminal 130.
The communication architecture is a communication structure for performing data communication, and defines various aspects of a data network communication system, including interface types of communication, network protocols used, implemented data frameworks, types of communication wiring, and the like. Common communication architectures may be TCP/IP architectures, Netty architectures, C/S architectures, SOA architectures, and the like. In this embodiment, the communication architecture may be understood as a Netty framework based on java open source, and a WebSocket technology is used in cooperation, so as to implement a communication structure for establishing a long connection service between the second user terminal 130 and the long connection server 120 in the communication network, and implement pushing of a message to the second user terminal 130.
The long connection service refers to a connection service that can continuously send a plurality of data packets on a long connection and can maintain a connection state for a long time to perform data transmission, and in this embodiment, the long connection service may be understood as a process in which the second user terminal 130 and the long connection server 120 continue to maintain connection without immediately releasing connection after completing a data transmission operation.
Specifically, the second user terminal 130 sends a long connection request to the domain name server 110 based on a preset communication architecture, where the long connection request carries first address information, user authentication information, and the like of the second user terminal 130, the user authentication information may be understood as authentication information (user name, password, and the like) of the second user terminal 130, the first address information may be understood as address information (IP address, MAC address, port number, and the like) of the second user terminal 130, after receiving the long connection request, the domain name server 110 may perform identity authentication on the user authentication information carried by the long connection request, after the identity authentication is passed, allocate a long connection server 120 for establishing connection with the second client terminal from a long connection server cluster, and based on the first address information of the second user terminal carried by the long connection request and second address information of the long connection server 120(s) IP address, MAC address, port number, etc.), establishing a long connection service between the first address information and the second address information.
After receiving the failure notification message on the message link, the long connection server 120 sends a heartbeat packet to the second user terminal 130 by using the long connection server.
When the long connection server 120 receives the response information fed back by the second user terminal 130 for the heartbeat packet, the long connection service between the long connection server 120 and the second user terminal 130 is determined to be in a normal connection state, and the push message is transmitted to the second user terminal 130 by using the long connection service.
When the long connection server 120 receives the response information fed back by the second user terminal 130 for the heartbeat packet, the long connection server 120 determines that the long connection service between the long connection server 120 and the second user terminal 130 is in an abnormal connection state, and the long connection server 120 stores the push message in a message database. When detecting that the long connection service between the long connection server and the second user terminal 130 recovers the normal connection state, obtaining the push message from the message database, and transmitting the push message to the second user terminal 130 by using the long connection service.
The long connection server 120 receives a push message sent by the first user terminal through the domain name server 110, where the push message is a fault notification message generated when the first user terminal has a network fault, a long connection service between the long connection server 120 and the second user terminal 130 is established by using a preset communication architecture, and the fault notification message is transmitted to the second user terminal 130 through the long connection service, where the second user terminal 130 is a terminal device in network communication with the first user terminal.
In one or more embodiments of the present application, a long connection server receives a push message sent by a service server through a domain name server, where the push message is a failure notification message generated when the service server detects a network failure of a first user terminal, and a preset communication architecture is used to establish a long connection service between the long connection server and a second user terminal, where the second user terminal is a terminal device that performs network communication with the first user terminal, and transmits the push message to the second user terminal by using the long connection service. By establishing the long connection service between the second user terminal and the long connection server, the fault notification message can be directly sent to the second user terminal through the long connection service, and the time delay of sending the push message to the user terminal by the server is reduced.
In one embodiment, as shown in fig. 2, a push message transmission method is proposed, which may be implemented in dependence on a computer program, operable on a push message transmission device based on the von neumann architecture. The computer program may be integrated into the application or may run as a separate tool-like application. The push message transfer device may be a long connection server as shown in fig. 1.
Specifically, the push message transmission method includes:
step 101: and receiving a push message sent by a service server through a domain name server, wherein the push message is a fault notification message generated when the service server detects that a network fault occurs in a first user terminal.
The service server may be considered as a server for detecting a network condition between a first user terminal or a second user terminal and an online education platform, where the first user terminal may be an intelligent terminal device connected to the online education platform, the online education platform includes a plurality of devices (a gateway, a routing device, a load balancing device, a server device, etc.) for online education, and after the first user terminal establishes a network connection with the second user terminal through the online education platform, the first user terminal and the second user terminal may implement real-time transmission of online education data, the online education data may be online real-time video data or online real-time audio data, and the network connection established between the first user terminal or the second user terminal and the online education platform may be through wireless communication, the communication may be through wired communication, and is not limited specifically.
In this embodiment, the network fault may be a network connection fault between the first user terminal and the online education platform, where the type of the network fault may be that part or all of functions of the online education platform are unavailable, that data of real-time online education of the online education platform is abnormal, that a network of the online education platform is unavailable, or that a user using the online platform performs a misoperation, and the like, and is not specifically limited herein.
Optionally, the service server for detecting the network failure may be based on an independent deployment manner, where the independent deployment may be understood as setting detection points respectively at a communication channel of a network connection or a plurality of devices (a gateway, a routing device, a load balancing device, a server device, and the like) of an online education platform, for detecting the network failure.
Specifically, when the network connection between the first user terminal and the online education platform is forced to be interrupted due to a network fault, the independently deployed service server detects that the communication connection channel of the first user terminal has a network fault, generates the fault notification message by reading and executing a machine executable instruction corresponding to the control logic of "sending fault notification information", analyzes the fault notification message by the domain name server of the message transmission link, obtains the address of the analyzed long connection server, and transmits the fault notification message to the long connection server corresponding to the address through the service link.
Step 102: and establishing a long connection service between a long connection server and a second user terminal by adopting a preset communication architecture, wherein the second user terminal is a terminal device which is in network communication with the first user terminal.
The communication architecture is a communication structure for performing data communication, and defines various aspects of a data network communication system, including interface types of communication, network protocols used, implemented data frameworks, types of communication wiring, and the like. Common communication architectures may be TCP/IP architectures, Netty architectures, C/S architectures, SOA architectures, and the like. In this embodiment, the communication architecture may be understood as a communication structure in which a long connection is established between a second user terminal and a server in a communication network by using a Netty framework based on a java open source and cooperating with a WebSocket technology, and a message is pushed to the second user terminal.
Specifically, the long connection server receives a long connection request sent by a second user terminal through a domain name server, the second user terminal is a terminal device in network communication with the first user terminal, the long connection request carries device information (a device name, an address, a device identifier, and the like) of the second user terminal, the long connection server initializes a long connection service based on the long connection request, then sends an instruction for establishing the long connection service to the second user terminal according to the device information of the second user terminal, and the second user terminal verifies the instruction after receiving the instruction for establishing the long connection service.
Specifically, the second client determines whether the return value of the long connection service establishing instruction is matched with a preset return value according to the return value by reading and analyzing the return value, where the return value may be understood as a string of codes, a character string, an array, and the like in this embodiment, and when the return value is matched with the preset return value, the long connection service is established successfully. When the return value is not matched with the preset return value, the second user terminal may send a long connection request to the long connection server again, and establish a long connection service between the long connection server and the second user terminal by using a preset communication architecture.
Step 103: and transmitting the push message to the second user terminal by adopting a long connection service.
The long connection server receives the fault notification message on the message transmission link, acquires message data of the fault notification message, analyzes the message, acquires device information (device name, address, device identification and the like) of a second user terminal carried by the fault notification message, finds a message distribution interface between the long connection server and the second user terminal based on a mapping relation between the device information of the second user terminal and the message distribution interface of the long connection server, and the long connection server transmits the fault notification message to the second user terminal by calling the message distribution interface at the bottom layer.
Optionally, when the message distribution interface of the long connection needs to push a plurality of notification messages, the push priority of the fault notification message is set to be the highest, and the long connection server preferentially calls the message distribution interface to transmit the fault notification message to the second user terminal.
In one or more embodiments of the present application, a long connection server receives a push message sent by a service server through a domain name server, where the push message is a failure notification message generated when the service server detects a network failure of a first user terminal, and a preset communication architecture is used to establish a long connection service between the long connection server and a second user terminal, where the second user terminal is a terminal device that performs network communication with the first user terminal, and transmits the push message to the second user terminal by using the long connection service. By establishing the long connection service between the second user terminal and the long connection server, the fault notification message can be directly sent to the second user terminal through the long connection service, and the time delay of sending the push message to the user terminal by the server is reduced.
Referring to fig. 3, fig. 3 is a flowchart illustrating another embodiment of a push message transmission method according to the present application. Specifically, the method comprises the following steps:
step 201: and receiving a push message sent by a service server through a domain name server, wherein the push message is a fault notification message generated when the service server detects that a network fault occurs in a first user terminal.
Specifically, refer to step 101, which is not described herein again.
Step 202: receiving a long connection request sent by a second user terminal through a preset communication architecture, and acquiring first address information of the second user terminal carried by the long connection request. Determining a long connection server in a long connection server cluster, acquiring second address information of the long connection server, and establishing a long connection service between the first address information and the second address information.
The first and second address information are information for defining the location of a network device (communication device) and a user terminal, and may be Mac addresses, IP addresses, physical addresses, hardware addresses, and the like.
The communication architecture can be understood as adopting a Netty framework based on a java open source and matching with a WebSocket technology to realize that a second user terminal in a communication network establishes a communication structure of a long connection service with a server and pushes a message to the second user terminal.
Specifically, the long connection request is used to establish a long connection service between the second client and the long connection server based on a preset communication architecture, where the long connection request carries first address information of the second user terminal and information of a type of establishing a long connection, and the type of establishing a long connection in this embodiment may be understood as establishing a Websocket long connection type long connection service.
Optionally, the domain name server receives the long connection request, acquires information of a long connection type carried by the long connection request, where the domain name server may establish a mapping relationship with a server cluster of multiple connection types, where the connection types include a long connection type, a short connection type, and the like, a connection of the same connection type includes connections of multiple connection protocols, such as a long connection based on an http1.0/1.1 protocol, a long connection based on a Jetty continuity, a long connection based on a Servlet3, a long connection based on a Websocket protocol, and the like, and the domain name server determines to establish a long connection server cluster of the long connection type from each server cluster based on the information of the long connection type carried by the long connection request, which may be understood as a long connection server cluster supporting the Websocket protocol in this embodiment.
Specifically, after determining that the long connection server cluster of the long connection type is established, the domain name server allocates a long connection server to the second client according to a preset connection allocation rule, acquires second address information of the connection server, and sends the long connection request to the long connection server.
Optionally, the connection allocation rule may be a dynamic bandwidth allocation algorithm based on a connection type, a queuing network connection allocation algorithm based on a game theory, a timeslot allocation algorithm based on connection duration prediction, a cross-layer resource allocation algorithm based on connection establishment priority, or the like.
It should be noted that there are many connection allocation rules, which may be one or more of the above, and the connection allocation rules are not specifically limited herein.
Specifically, the long connection server receives a long connection request sent by a second user terminal through a domain name server, initializes a long connection service based on the long connection request, acquires first address information (Mac address, IP address, physical address, hardware address, and the like) of second user equipment carried by the long connection request, and sends an instruction for establishing the long connection service to the second user terminal indicated by the first address information according to the first address information, thereby establishing the long connection service between the first address information and the second address information.
Step 203: and sending a heartbeat packet to the second user terminal, determining that the long connection service between the long connection server and the second user terminal is in a normal connection state in response to that response information fed back by the second user terminal aiming at the heartbeat packet is not overtime, and transmitting the push message to the second user terminal by adopting the long connection service.
The heartbeat packet is detection data for notifying the state of equipment of the other side between the user terminal and the server, the detection data can be a self-defined structural body (codes, character strings, command words and the like), the heartbeat packet can be sent to determine whether the current long connection service is normal, the server generally needs to send the heartbeat packet according to a certain time interval, and the side receiving the heartbeat packet detects whether the heartbeat packet is received on time, so as to judge whether the connection is normal. The heartbeat packet is usually a small probe packet, and is usually implemented by sending a null packet containing only a header at the logic layer.
In this embodiment, it may be understood that a heartbeat packet is sent to the second user terminal at regular time, and the second user terminal returns a response message after receiving the heartbeat packet.
In an alternative embodiment, the second user terminal has a sleep function, where the sleep function is understood to be that when it is detected that the long connection service of the second user terminal and the long connection server has no data to send within a preset time, the long connection service is automatically disconnected.
Optionally, after the second user terminal establishes the long connection service with the long connection server, the long connection server may send a heartbeat packet to the second user terminal to keep sending the long connection data within a preset time, so as to maintain the long connection service between the second user terminal and the long connection server.
Specifically, the long connection server sends a heartbeat packet to the second user terminal to detect the state of the long connection service, and when the second user terminal receives the heartbeat packet, a response message is fed back to the long connection server.
And after receiving the response information fed back by the second user terminal, the long connection server acquires response time and judges whether the response time is overtime, when the response information fed back by the second user terminal aiming at the heartbeat packet is not overtime, the long connection server determines that the long connection service between the long connection server and the second user terminal is in a normal state, and then the long connection server transmits the fault notification message to the second user terminal by adopting the long connection service.
Step 204: and responding to overtime response information fed back by the second user terminal aiming at the heartbeat packet, determining that the long connection service between the long connection server and the second user terminal is in an abnormal connection state, and storing the push message into a message database.
The response information fed back by the heartbeat packet is overtime, which means that the second user terminal has abnormal state and does not feed back response information within a preset response time, and the abnormal state may be that the second user terminal has an excessively large load, a message transmission channel is blocked, and the like.
Specifically, when the long connection server does not receive a response message fed back by the second user terminal within a preset response time, it is determined that the long connection service between the long connection server and the second user terminal is in an abnormal connection state, a push message backup mechanism of the long connection server is triggered, and the fault notification information is backed up in a database by reading and executing a machine executable instruction corresponding to a control logic of "push message backup".
Step 205: and when detecting that the long connection service between the long connection server and the second user terminal is recovered to a normal connection state, acquiring the push message from the message database, and transmitting the push message to the second user terminal by adopting the long connection service.
Specifically, the connection recovery may be understood as that the working state of the second user terminal is recovered to be normal, at this time, the second user terminal may send a long link recovery request to the long connection server, and after receiving the recovery request, the long connection server obtains configuration information of the long connection service before connection interruption, where the configuration information includes information such as a message distribution interface, a port number, a message processing thread, and a message processing rule, and establishes the long connection service between the long connection server and the second user terminal based on the configuration information.
Optionally, the long connection server may send a heartbeat packet to the second user terminal, where the heartbeat packet is used to detect whether the long connection service recovers to a normal connection state, the second user terminal receives the heartbeat packet and then sends response information fed back by the heartbeat packet to the long connection server, and when the long connection server receives the response information within a preset time, it is determined that the long connection service between the long connection server and the second user terminal recovers to the normal connection state.
Specifically, when it is detected that the long connection service between the long connection server and the second user terminal is restored to the normal connection state, the failure push message is acquired from the message database, and is transmitted to the second user terminal by using the long connection service.
Step 206: and receiving a push message sent by the first user terminal through the domain name server, wherein the push message is a fault notification message generated when the first user terminal has a network fault, and establishing a long connection service between a long connection server and a second user terminal by adopting a preset communication architecture, and the second user terminal is a terminal device which is in network communication with the first user terminal and transmits the push message to the second user terminal through the long connection service.
Specifically, refer to step 101-step 103, which are not described herein.
In a possible implementation manner, when a network failure occurs in the first user terminal, the network connection between the first user terminal and the online education platform is disconnected, the first user terminal sends a failure notification message, and the failure notification message is sent to the second user terminal through the message push link.
Optionally, the first user terminal may establish peer-to-peer real-time communication with the second user terminal through the long connection server based on a preset communication architecture. In this embodiment, the method can be understood as a Netty framework based on java open source, and the WebSocket technology is matched to implement the establishment of the point-to-point real-time communication between the first user terminal and the second user terminal through the long connection server.
Optionally, the first user terminal sends a peer-to-peer connection request to the domain name server, where the peer-to-peer connection request may be understood as being used to establish peer-to-peer real-time communication between the first user terminal and the second user terminal through the long connection server in this embodiment. The domain name server receives the point-to-point connection request, and determines a long connection server in a long connection server cluster, wherein the long connection server is used for establishing point-to-point communication service with a first user terminal and a second user terminal.
In a possible embodiment, the peer-to-peer real-time communication between the first user terminal and the second user terminal may be implemented based on different long connection servers. Referring to fig. 4a, in fig. 4a, the second user terminal establishes a long connection service with the long connection server 1, the first user terminal establishes a long connection service with the long connection server 2, and the long connection server 1 establishes a communication transmission channel with the long connection server 2, so as to establish point-to-point real-time communication among the first user terminal, the long connection server 1, the long connection server 2, and the second user terminal. The first user terminal may invoke the long connection service of the long connection server 2 to send a push message to the second user terminal, where the push message may be a failure notification message, the notification message is sent to the second user terminal through the long connection server 1 and the long connection server 2, and the second user terminal may send a response message to the first user terminal after receiving the push message.
In a possible embodiment, the peer-to-peer real-time communication between the first user terminal and the second user terminal may be implemented based on the same long connection server. Referring to fig. 4b, in fig. 4a, a second user terminal establishes a long connection service with the long connection server 1, and a first user terminal establishes a long connection service with the long connection server 1, so as to establish point-to-point real-time communication among the first user terminal, the long connection server 1, and the second user terminal, where the first user terminal sends a push message to the second user terminal through the long connection server 1, and the second user terminal may send a response message to the first user terminal after receiving the push message.
In one or more embodiments of the present application, a long connection server receives a push message sent by a service server through a domain name server, where the push message is a failure notification message generated when the service server detects a network failure of a first user terminal, and a preset communication architecture is used to establish a long connection service between the long connection server and a second user terminal, where the second user terminal is a terminal device that performs network communication with the first user terminal, and transmits the push message to the second user terminal by using the long connection service. By establishing the long connection service between the second user terminal and the long connection server, the fault notification message can be directly sent to the second user terminal through the long connection service, and the time delay of sending the push message to the user terminal by the server is reduced. Meanwhile, the long connection service between the second user terminal and the long connection server is in a continuous connection state, and when the push message needs to be sent next time, the push message can be directly sent without requesting connection from the long connection server, so that the load of the long connection server can be reduced.
The following are embodiments of the apparatus of the present application that may be used to perform embodiments of the method of the present application. For details which are not disclosed in the embodiments of the apparatus of the present application, reference is made to the embodiments of the method of the present application.
Please refer to fig. 5, which shows a schematic structural diagram of a push message transmission apparatus according to an exemplary embodiment of the present application. The push messaging device may be implemented as all or part of a device in software, hardware, or a combination of both. The device 1 comprises a message receiving module 11, a connection establishing module 12 and a message transmitting module 13.
A message receiving module 11, configured to receive a push message sent by a service server through a domain name server, where the push message is a fault notification message generated by the service server when detecting that a network fault occurs in a first user terminal;
a connection establishing module 12, configured to establish a long connection service between a long connection server and a second user terminal by using a preset communication architecture, where the second user terminal is a terminal device that performs network communication with the first user terminal;
a message transmission module 13, configured to transmit the push message to the second user terminal by using a long connection service.
Optionally, as shown in fig. 6, the connection establishing module 12 may specifically include:
an address obtaining unit 121, configured to receive a long connection request sent by a second user terminal through a preset communication architecture, and obtain first address information of the second user terminal carried in the long connection request;
a long connection establishing unit 122, configured to determine a long connection server in a long connection server cluster, acquire second address information of the long connection server, and establish a long connection service between the first address information and the second address information.
Optionally, as shown in fig. 7, the apparatus 1 further includes:
the state determining module 14 is configured to send a heartbeat packet to the second user terminal, and determine that the long connection service between the long connection server and the second user terminal is in a normal connection state in response to that the feedback information of the second user terminal for the heartbeat packet is not overtime.
Optionally, as shown in fig. 7, the apparatus 1 further includes:
and the message storage module 15 is configured to determine that the long connection service between the long connection server and the second user terminal is in an abnormal connection state in response to that the feedback information of the second user terminal for the heartbeat packet is overtime, and store the push message in a message database.
Optionally, as shown in fig. 7, the apparatus 1 further includes:
and a message retransmission module 16, configured to, when it is detected that the long connection service between the long connection server and the second user terminal recovers the normal connection state, obtain the push message from the message database, and transmit the push message to the second user terminal by using the long connection service.
Optionally, the message receiving module 11 is configured to receive a push message sent by the first user terminal through the domain name server, where the push message is a fault notification message generated when a network fault occurs in the first user terminal;
the connection establishing module 12 is configured to establish a long connection service between a long connection server and a second user terminal by using a preset communication architecture, where the second user terminal is a terminal device that performs network communication with the first user terminal;
the message transmission module 13 is configured to transmit the push message to the second user terminal through a long connection service.
It should be noted that, when the push message transmission apparatus provided in the foregoing embodiment executes the push message transmission method, only the division of the functional modules is taken as an example, and in practical applications, the functions may be distributed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules, so as to complete all or part of the functions described above. In addition, the push message transmission device and the push message transmission method provided by the above embodiments belong to the same concept, and details of implementation processes thereof are referred to in the method embodiments and are not described herein again.
The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.
In one or more embodiments of the present application, a long connection server receives a push message sent by a service server through a domain name server, where the push message is a failure notification message generated when the service server detects a network failure of a first user terminal, and a preset communication architecture is used to establish a long connection service between the long connection server and a second user terminal, where the second user terminal is a terminal device that performs network communication with the first user terminal, and transmits the push message to the second user terminal by using the long connection service. By establishing the long connection service between the second user terminal and the long connection server, the fault notification message can be directly sent to the second user terminal through the long connection service, and the time delay of sending the push message to the user terminal by the server is reduced. Meanwhile, the long connection service between the second user terminal and the long connection server is in a continuous connection state, and when the push message needs to be sent next time, the push message can be directly sent without requesting connection from the long connection server, so that the load of the long connection server can be reduced.
An embodiment of the present application further provides a computer storage medium, where the computer storage medium may store a plurality of instructions, where the instructions are suitable for being loaded by a processor and executing the method steps in the embodiments shown in fig. 1 to 4b, and a specific execution process may refer to specific descriptions of the embodiments shown in fig. 1 to 4b, which is not described herein again.
The present application further provides a computer program product storing at least one instruction, which is loaded and executed by the processor to implement the score generation method according to the above embodiments.
Please refer to fig. 8, which provides a schematic structural diagram of a server according to an embodiment of the present application. As shown in fig. 8, the server 1000 may include: at least one processor 1001, at least one network interface 1004, a user interface 1003, memory 1005, at least one communication bus 1002.
Wherein a communication bus 1002 is used to enable connective communication between these components.
The user interface 1003 may include a Display screen (Display) and a Camera (Camera), and the optional user interface 1003 may also include a standard wired interface and a wireless interface.
The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface), among others.
The Memory 1005 may include a Random Access Memory (RAM) or a Read-Only Memory (Read-Only Memory). Optionally, the memory 1005 includes a non-transitory computer-readable medium. The memory 1005 may be used to store an instruction, a program, code, a set of codes, or a set of instructions. The memory 1005 may include a stored program area and a stored data area, wherein the stored program area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playing function, an image playing function, etc.), instructions for implementing the various method embodiments described above, and the like; the storage data area may store data and the like referred to in the above respective method embodiments. The memory 1005 may optionally be at least one memory device located remotely from the processor 1001. As shown in fig. 8, a memory 1005, which is one type of computer storage medium, may include an operating system, a network communication module, a user interface module, and a push messaging application.
In the server 1000 shown in fig. 8, the user interface 1003 is mainly used as an interface for providing input for a user, and acquiring data input by the user; and the processor 1001 may be configured to invoke the push messaging application stored in the memory 1005 and specifically perform the following operations:
receiving a push message sent by a service server through a domain name server, wherein the push message is a fault notification message generated when the service server detects that a first user terminal has a network fault;
establishing a long connection service between a long connection server and a second user terminal by adopting a preset communication architecture, wherein the second user terminal is a terminal device which is in network communication with the first user terminal;
and transmitting the push message to the second user terminal by adopting a long connection service.
In an embodiment, when the processor 1001 executes the long connection service established between the long connection server and the second user terminal by using the preset communication architecture, the following operations are specifically executed:
receiving a long connection request sent by a second user terminal through a preset communication architecture, and acquiring first address information of the second user terminal carried by the long connection request;
determining a long connection server in a long connection server cluster, acquiring second address information of the long connection server, and establishing a long connection service between the first address information and the second address information.
In one embodiment, after the processor 1001 performs the long connection service between the long connection server and the second user terminal using the preset communication architecture, the following operations are further performed:
and sending a heartbeat packet to the second user terminal, and determining that the long connection service between the long connection server and the second user terminal is in a normal connection state in response to that the feedback information of the second user terminal for the heartbeat packet is not overtime.
In one embodiment, the processor 1001 further performs the following operations:
responding to the overtime feedback information of the second user terminal aiming at the heartbeat packet, and determining that the long connection service between the long connection server and the second user terminal is in an abnormal connection state;
and storing the push message into a message database.
In one embodiment, after the saving the push message to the message database, the processor 1001 further performs the following operations:
and when detecting that the long connection service between the long connection server and the second user terminal is recovered to a normal connection state, acquiring the push message from the message database, and transmitting the push message to the second user terminal by adopting the long connection service.
In one embodiment, the processor 1001 further performs the following operations:
and receiving a push message sent by the first user terminal through the domain name server, wherein the push message is a fault notification message generated when the first user terminal has a network fault, and establishing a long connection service between a long connection server and a second user terminal by adopting a preset communication architecture, and the second user terminal is a terminal device which is in network communication with the first user terminal and transmits the push message to the second user terminal through the long connection service.
In one or more embodiments of the present application, a long connection server receives a push message sent by a service server through a domain name server, where the push message is a failure notification message generated when the service server detects a network failure of a first user terminal, and a preset communication architecture is used to establish a long connection service between the long connection server and a second user terminal, where the second user terminal is a terminal device that performs network communication with the first user terminal, and transmits the push message to the second user terminal by using the long connection service. By establishing the long connection service between the second user terminal and the long connection server, the fault notification message can be directly sent to the second user terminal through the long connection service, and the time delay of sending the push message to the user terminal by the server is reduced. Meanwhile, the long connection service between the second user terminal and the long connection server is in a continuous connection state, and when the push message needs to be sent next time, the push message can be directly sent without requesting connection from the long connection server, so that the load of the long connection server can be reduced.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a read-only memory or a random access memory.
The above disclosure is only for the purpose of illustrating the preferred embodiments of the present application and is not to be construed as limiting the scope of the present application, so that the present application is not limited thereto, and all equivalent variations and modifications can be made to the present application.
Claims (10)
1. A method of push message transmission, the method comprising:
receiving a push message sent by a service server through a domain name server, wherein the push message is a fault notification message generated when the service server detects that a first user terminal has a network fault, and a network connection is established between the first user terminal and a second user terminal so as to realize real-time data transmission between the first user terminal and the second user terminal;
establishing a long connection service between a long connection server and a second user terminal by adopting a preset communication architecture, wherein the second user terminal is a terminal device which is in network communication with the first user terminal;
and transmitting the push message to the second user terminal by adopting a long connection service.
2. The method according to claim 1, wherein the establishing of the long connection service between the long connection server and the second user terminal using the preset communication architecture comprises:
receiving a long connection request sent by a second user terminal through a preset communication architecture, and acquiring first address information of the second user terminal carried by the long connection request;
determining a long connection server in a long connection server cluster, acquiring second address information of the long connection server, and establishing a long connection service between the first address information and the second address information.
3. The method according to claim 1, wherein after the establishing the long connection service between the long connection server and the second user terminal by using the preset communication architecture, the method further comprises:
and sending a heartbeat packet to the second user terminal, and determining that the long connection service between the long connection server and the second user terminal is in a normal connection state in response to that the feedback information of the second user terminal for the heartbeat packet is not overtime.
4. The method of claim 3, further comprising:
responding to the overtime feedback information of the second user terminal aiming at the heartbeat packet, and determining that the long connection service between the long connection server and the second user terminal is in an abnormal connection state;
and storing the push message into a message database.
5. The method of claim 4, further comprising, after saving the push message to a message database:
and when detecting that the long connection service between the long connection server and the second user terminal is recovered to a normal connection state, acquiring the push message from the message database, and transmitting the push message to the second user terminal by adopting the long connection service.
6. The method of claim 1, further comprising:
receiving a push message sent by the first user terminal through the domain name server, wherein the push message is a fault notification message generated when the first user terminal has a network fault;
establishing a long connection service between a long connection server and a second user terminal by adopting a preset communication architecture, wherein the second user terminal is a terminal device which is in network communication with the first user terminal;
and transmitting the push message to the second user terminal through a long-connection service.
7. A push message transmission apparatus, the apparatus comprising:
the message receiving module is used for receiving a push message sent by a service server through a domain name server, wherein the push message is a fault notification message generated by the service server when a network fault occurs in a first user terminal, and a network connection is established between the first user terminal and a second user terminal so as to realize real-time data transmission between the first user terminal and the second user terminal;
the system comprises a connection establishing module, a first user terminal and a second user terminal, wherein the connection establishing module is used for establishing a long connection service between a long connection server and the second user terminal by adopting a preset communication architecture, and the second user terminal is terminal equipment which is in network communication with the first user terminal;
and the message transmission module is used for transmitting the push message to the second user terminal by adopting a long connection service.
8. The apparatus of claim 7, wherein the connection establishing module comprises:
the address acquisition unit is used for receiving a long connection request sent by a second user terminal through a preset communication architecture and acquiring first address information of the second user terminal carried by the long connection request;
and the long connection establishing unit is used for determining a long connection server in the long connection server cluster, acquiring second address information of the long connection server and establishing a long connection service between the first address information and the second address information.
9. A computer storage medium, characterized in that it stores a plurality of instructions adapted to be loaded by a processor and to perform the method steps according to any of claims 1 to 6.
10. An electronic device, comprising: a processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and to perform the method steps of any of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910778386.1A CN110417915B (en) | 2019-08-22 | 2019-08-22 | Push message transmission method and device, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910778386.1A CN110417915B (en) | 2019-08-22 | 2019-08-22 | Push message transmission method and device, storage medium and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110417915A CN110417915A (en) | 2019-11-05 |
| CN110417915B true CN110417915B (en) | 2021-12-31 |
Family
ID=68368170
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910778386.1A Active CN110417915B (en) | 2019-08-22 | 2019-08-22 | Push message transmission method and device, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110417915B (en) |
Families Citing this family (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111028578A (en) * | 2019-11-21 | 2020-04-17 | 湖北时代万新国际教育发展有限公司 | Professional qualification education-oriented remote sharing system |
| CN111131392A (en) * | 2019-11-27 | 2020-05-08 | 北京文渊佳科技有限公司 | Method, device, electronic equipment and medium for processing message |
| CN111078342A (en) * | 2019-12-06 | 2020-04-28 | 拉扎斯网络科技（上海）有限公司 | Information display method and device, electronic equipment and computer readable storage medium |
| CN111614752B (en) * | 2020-05-19 | 2022-08-30 | 北京百度网讯科技有限公司 | Method and device for data transmission |
| CN113727406B (en) * | 2020-05-21 | 2022-11-29 | 北京三快在线科技有限公司 | Communication control method, device, equipment and computer readable storage medium |
| CN111754671B (en) * | 2020-06-28 | 2022-11-18 | 北京百度网讯科技有限公司 | Verification method, device, equipment and computer storage medium |
| CN112492020B (en) * | 2020-11-24 | 2023-04-25 | 杭州萤石软件有限公司 | Message pushing method, system, equipment and storage medium |
| CN112769675B (en) * | 2020-12-31 | 2021-09-07 | 北京金色大数据有限公司 | Method and system for improving communication speed of real-time message |
| CN113079504A (en) * | 2021-03-23 | 2021-07-06 | 广州讯鸿网络技术有限公司 | Method, device and system for realizing access of 5G message DM multi-load balancer |
| CN114374705A (en) * | 2022-01-06 | 2022-04-19 | 青岛海信智慧生活科技股份有限公司 | Service cluster and message pushing method |
| CN114760297A (en) * | 2022-03-16 | 2022-07-15 | 广联达科技股份有限公司 | Message pushing method, system, equipment and readable storage medium |
| CN115174135A (en) * | 2022-05-17 | 2022-10-11 | 贝壳找房(北京)科技有限公司 | Method, device, equipment, medium and program product for prompting real-time risk in session |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104239310A (en) * | 2013-06-08 | 2014-12-24 | 中国移动通信集团公司 | Distributed database data synchronizing method and device |
| CN104852991A (en) * | 2015-06-01 | 2015-08-19 | 上海雷腾软件股份有限公司 | Distributed push server system and data push method using the system |
| CN107193674A (en) * | 2017-06-29 | 2017-09-22 | 武汉斗鱼网络科技有限公司 | The processing method and processing device of online PUSH message |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060072707A1 (en) * | 2004-09-30 | 2006-04-06 | International Business Machines Corporation | Method and apparatus for determining impact of faults on network service |
| CN105338563B (en) * | 2011-12-02 | 2018-10-09 | 华为技术有限公司 | A kind of fault detection method, gateway, user equipment and communication system |
| CN103874035B (en) * | 2012-12-13 | 2018-10-02 | 中国移动通信集团公司 | A kind of Mobile terminal message push method and equipment |
| CN107104838A (en) * | 2017-05-15 | 2017-08-29 | 北京奇艺世纪科技有限公司 | A kind of information processing method, server and terminal |
| CN107483260B (en) * | 2017-08-28 | 2021-03-02 | 北京三快在线科技有限公司 | Fault processing method and device and electronic equipment |
| CN108600085A (en) * | 2018-04-04 | 2018-09-28 | 腾讯科技（深圳）有限公司 | Message is sent and output method, device, server, terminal and storage medium |
-
2019
- 2019-08-22 CN CN201910778386.1A patent/CN110417915B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104239310A (en) * | 2013-06-08 | 2014-12-24 | 中国移动通信集团公司 | Distributed database data synchronizing method and device |
| CN104852991A (en) * | 2015-06-01 | 2015-08-19 | 上海雷腾软件股份有限公司 | Distributed push server system and data push method using the system |
| CN107193674A (en) * | 2017-06-29 | 2017-09-22 | 武汉斗鱼网络科技有限公司 | The processing method and processing device of online PUSH message |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110417915A (en) | 2019-11-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110417915B (en) | Push message transmission method and device, storage medium and electronic equipment | |
| CN107645529B (en) | Heartbeat packet sending method and device | |
| CN110300404B (en) | Network control method and mobile terminal | |
| CN111224999A (en) | Transmission protocol switching method, device, equipment and storage medium | |
| CN111629452A (en) | Data transmission control method and device, storage medium and electronic equipment | |
| US20170279748A1 (en) | Information processing method and terminal, and computer storage medium | |
| CN105959827A (en) | Data interaction method, set top box, and front-end server | |
| CN111629024A (en) | Data transmission control method and device, storage medium and electronic equipment | |
| CN112398689A (en) | Network recovery method and device, storage medium and electronic equipment | |
| CN101702712B (en) | Detection technology and voice call backup linkage method and device thereof | |
| CN109729582B (en) | Information interaction method and device and computer readable storage medium | |
| JP2006166244A (en) | Network telephone system, and main device of the network telephone system | |
| CN111741175B (en) | Call center system, signal transmission method, device, server and medium | |
| EP2949083A1 (en) | Receiving a communication event | |
| CN115665713A (en) | Multi-device communication method, device, equipment and storage medium | |
| US9866644B2 (en) | Terminal, message distribution system, message distribution method, and computer-readable medium | |
| CN114172815B (en) | Behavior traffic transmission method, device, computer equipment and computer readable storage medium | |
| CN113053374B (en) | Large screen control system | |
| CN112333690B (en) | Data transmission method, device, storage medium, terminal and network access point equipment | |
| CN114884805A (en) | Data transmission method, device, terminal and storage medium | |
| CN111615219B (en) | PC5 link establishing method, equipment and system | |
| US9485458B2 (en) | Data processing method and device | |
| CN104935571A (en) | Interaction method of TV game server and client | |
| JP2007066117A (en) | Information notification method and server | |
| US10159027B2 (en) | Media degradation recovery during a communication session |
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 |