CN111741075A - Communication connection method, vehicle remote connection system and connection equipment - Google Patents
Communication connection method, vehicle remote connection system and connection equipment Download PDFInfo
- Publication number
- CN111741075A CN111741075A CN202010466228.5A CN202010466228A CN111741075A CN 111741075 A CN111741075 A CN 111741075A CN 202010466228 A CN202010466228 A CN 202010466228A CN 111741075 A CN111741075 A CN 111741075A
- Authority
- CN
- China
- Prior art keywords
- vehicle
- connection
- vehicle remote
- equipment
- request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000004891 communication Methods 0.000 title claims abstract description 74
- 238000000034 method Methods 0.000 title claims abstract description 69
- 238000004080 punching Methods 0.000 claims description 101
- 238000012790 confirmation Methods 0.000 claims description 94
- 238000004590 computer program Methods 0.000 claims description 29
- 238000012546 transfer Methods 0.000 claims description 24
- 238000004171 remote diagnosis Methods 0.000 abstract description 13
- 230000005540 biological transmission Effects 0.000 abstract description 9
- 230000000694 effects Effects 0.000 abstract description 7
- 238000010586 diagram Methods 0.000 description 10
- 230000008569 process Effects 0.000 description 8
- 230000003993 interaction Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000004044 response Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000003745 diagnosis Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 238000013519 translation Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- 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
- H04L67/104—Peer-to-peer [P2P] networks
-
- 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/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Computer And Data Communications (AREA)
Abstract
The application discloses a communication connection method, a vehicle remote connection system and a connection device, a P2P communication mode is used as a communication mode between a vehicle near-end connection device and a vehicle far-end connection device, so that the real-time performance of vehicle remote diagnosis and the efficiency of data transmission are improved, when P2P communication is limited, the communication between the vehicle near-end connection device and the vehicle far-end connection device is realized in a mode of forwarding data through a server, and the experience effect of a user is further improved.
Description
Technical Field
The application belongs to the technical field of automobile communication, and particularly relates to a communication connection method, a vehicle remote connection system, vehicle near-end connection equipment and vehicle far-end connection equipment.
Background
Currently, in vehicle remote diagnosis, remote data interaction between a vehicle and a remote diagnosis device is realized by providing a relay device between the vehicle and the remote diagnosis device, for example, it is common to provide a vehicle connector (also referred to as a vehicle near-end connection device) at a vehicle end, provide a device connector (also referred to as a vehicle far-end connection device) at the remote diagnosis device end, and perform diagnosis data relay with the device connector through the vehicle connector, thereby realizing data interaction between the vehicle and the remote diagnosis device. The existing vehicle connector and the equipment connector mainly realize remote data transmission in a server forwarding mode, and the problems of low data transmission efficiency and high time delay exist.
Disclosure of Invention
The application provides a communication connection method, a vehicle remote connection system and a connection device, a P2P communication mode is used as a communication mode between a vehicle near-end connection device and a vehicle far-end connection device, so that the real-time performance of vehicle remote diagnosis and the efficiency of data transmission are improved, when P2P communication is limited, the communication between the vehicle near-end connection device and the vehicle far-end connection device is realized in a mode of forwarding data through a server, and the experience effect of a user is further improved.
In a first aspect, the present application provides a communication connection method applied to a vehicle near-end connection device, the method including:
sending a P2P punching request to a vehicle remote connection device;
if confirmation information returned by the vehicle remote connection equipment based on the P2P punching request is received, connecting with the vehicle remote connection equipment P2P;
and if the confirmation information returned by the vehicle remote-end connecting equipment is not received, establishing connection with the vehicle remote-end connecting equipment through a specified data transfer server.
In an optional implementation manner, the P2P hole punching request includes a first P2P hole punching request sent by a TCP-based NAT hole punching protocol and a second P2P hole punching request sent by a UDP-based NAT hole punching protocol;
correspondingly, sending a P2P hole-making request to the vehicle remote connection device includes:
sending the first P2P hole-making request to the vehicle remote connection device;
if the confirmation information returned by the vehicle remote connection equipment based on the first P2P punching request is not received, sending the second P2P punching request to the vehicle remote connection equipment;
if the confirmation information returned by the vehicle remote connection device based on the P2P hole punching request is received, the establishing P2P connection with the vehicle remote connection device includes:
and if the confirmation information returned by the vehicle remote connection equipment based on the first P2P punching request is received, or if the confirmation information returned by the vehicle remote connection equipment based on the second P2P punching request is received, establishing P2P connection with the vehicle remote connection equipment.
In an optional implementation manner, the P2P hole request includes a first P2P hole request sent by a TCP-based NAT hole protocol;
correspondingly, sending a P2P hole-making request to the vehicle remote connection device includes:
sending the first P2P hole-making request to the vehicle remote connection device;
if the confirmation information returned by the vehicle remote connection device based on the P2P hole punching request is received, the establishing P2P connection with the vehicle remote connection device includes:
and if the confirmation information returned by the vehicle remote connection equipment based on the first P2P punching request is received, establishing P2P connection with the vehicle remote connection equipment.
In an optional implementation manner, the P2P hole punching request includes a second P2P hole punching request sent by a UDP-based NAT hole punching protocol;
correspondingly, sending a P2P hole-making request to the vehicle remote connection device includes:
sending the second P2P hole-making request to the vehicle remote connection device;
if the confirmation information returned by the vehicle remote connection device based on the P2P hole punching request is received, the establishing P2P connection with the vehicle remote connection device includes:
and if the confirmation information returned by the vehicle remote connection equipment based on the second P2P punching request is received, establishing P2P connection with the vehicle remote connection equipment.
In an optional implementation manner, before sending the P2P punching request to the vehicle remote connection device, the method further includes:
acquiring the IP address and the port number of the vehicle remote connection equipment through the data transfer server;
correspondingly, sending a P2P hole-making request to the vehicle remote connection device includes:
and sending the P2P punching request to the vehicle far-end connection equipment according to the IP address and the port number of the vehicle far-end connection equipment.
In a second aspect, the present application provides a communication connection method applied to a vehicle remote connection device, the method including:
if a P2P punching request sent by a vehicle near-end connecting device is received, generating confirmation information based on the P2P punching request;
sending the confirmation information to the vehicle near-end connection equipment;
if the vehicle near-end connecting equipment receives the confirmation information, establishing P2P connection with the vehicle near-end connecting equipment;
and if the vehicle near-end connecting equipment cannot receive the confirmation information, establishing connection with the vehicle near-end connecting equipment through a specified data transfer server.
In a third aspect, the present application provides a communication connection method applied to a vehicle remote connection system, where the vehicle remote connection system includes a vehicle near-end connection device, a vehicle far-end connection device, and a specified data relay server, and the method includes:
the vehicle near-end connecting device sends a P2P punching request to the vehicle far-end connecting device;
after receiving the P2P punching request, the vehicle remote-end connecting equipment generates confirmation information based on the P2P punching request;
the vehicle far-end connecting device sends the confirmation information to the vehicle near-end connecting device;
if the vehicle near-end connecting device receives the confirmation information returned by the vehicle far-end connecting device, the vehicle near-end connecting device establishes P2P connection with the vehicle far-end connecting device;
and if the vehicle near-end connecting equipment cannot receive the confirmation information returned by the vehicle far-end connecting equipment, the vehicle near-end connecting equipment establishes connection with the vehicle far-end connecting equipment through the data transfer server.
In a fourth aspect, the present application provides a vehicle remote connection system, including a vehicle near-end connection device, a vehicle far-end connection device, and a designated data transfer server;
the vehicle near-end connecting device is used for sending a P2P punching request to the vehicle far-end connecting device; if confirmation information returned by the vehicle remote connection equipment based on the P2P punching request is received, establishing P2P connection with the vehicle remote connection equipment; if the confirmation information returned by the vehicle remote-end connection equipment is not received, connection is established with the vehicle remote-end connection equipment through the data transfer server;
the vehicle far-end connecting device is used for generating confirmation information based on the P2P punching request if the P2P punching request sent by the vehicle near-end connecting device is received; sending the confirmation information to the vehicle near-end connection equipment; if the vehicle near-end connecting device is determined to receive the confirmation information, establishing P2P connection with the vehicle near-end connecting device; and if the vehicle near-end connecting equipment is determined not to receive the confirmation information, establishing connection with the vehicle near-end connecting equipment through the data transfer server.
In a fifth aspect, the present application provides a vehicle proximal end connection apparatus comprising:
a memory for storing an executable computer program;
a processor for invoking the executable computer program to perform the self-identified communication connection method as described in any one of the optional implementations of the first aspect.
In a sixth aspect, the present application provides a vehicle remote connection apparatus comprising:
a memory for storing an executable computer program;
a processor for invoking the executable computer program to perform the self-identified communication connection method as described in the second aspect above.
In a seventh aspect, the present application provides a vehicle proximity connection apparatus, the apparatus comprising:
the device comprises a sending module, a receiving module and a processing module, wherein the sending module is used for sending a P2P punching request to the vehicle remote end connecting equipment;
the first connection module is used for establishing P2P connection with the vehicle remote connection equipment if confirmation information returned by the vehicle remote connection equipment based on the P2P punching request is received;
and the second connection module is used for establishing connection with the vehicle far-end connection equipment through a specified data transfer server if the confirmation information returned by the vehicle far-end connection equipment is not received.
In an eighth aspect, the present application provides a vehicle remote connection apparatus, the apparatus comprising:
the generating module is used for generating confirmation information based on the P2P punching request if the P2P punching request sent by the vehicle near-end connecting equipment is received;
the sending module is used for sending the confirmation information to the vehicle near-end connecting equipment;
the third connection module is used for establishing P2P connection with the vehicle near-end connection equipment if the vehicle near-end connection equipment is determined to receive the confirmation information;
and the fourth connection module is used for establishing connection with the vehicle near-end connection equipment through the specified data transfer server if the vehicle near-end connection equipment is determined not to receive the confirmation information.
In a ninth aspect, the present application provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the method according to the first aspect described above, or which, when executed by a processor, performs the steps of the method according to the second aspect described above.
In a tenth aspect, the present application provides a computer program product comprising a computer program that when executed by one or more processors performs the steps of the method as in the first aspect described above, or a computer program that when executed by one or more processors performs the steps of the method as in the second aspect described above.
According to the communication connection method provided by the first aspect of the application, the P2P communication mode is used as a communication mode between the vehicle near-end connecting device and the vehicle far-end connecting device, so that the real-time performance of vehicle remote diagnosis and the data transmission efficiency are improved, when the P2P communication is limited, the communication between the vehicle near-end connecting device and the vehicle far-end connecting device is realized in a mode that a server forwards data, and the experience effect of a user is further improved.
Compared with the prior art, the second to tenth aspects of the present application have the same advantageous effects as the communication connection method provided by the first aspect of the present application has.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and those skilled in the art can also obtain other drawings according to the drawings without creative efforts.
FIG. 1 is a schematic system architecture diagram of a vehicle remote connection system provided in a first embodiment of the present application;
fig. 2 is a flowchart of an implementation of a communication connection method according to a second embodiment of the present application;
fig. 3 is a flowchart of an implementation of a communication connection method according to a third embodiment of the present application;
fig. 4 is a flowchart of an implementation of a communication connection method according to a fourth embodiment of the present application;
fig. 5 is an interaction flow chart of a communication connection method provided in a fifth embodiment of the present application;
FIG. 6 is a schematic structural diagram of a vehicle proximal end connection apparatus provided in a sixth embodiment of the present application;
fig. 7 is a schematic structural diagram of a vehicle remote connection device according to a seventh embodiment of the present application;
FIG. 8 is a schematic structural diagram of a vehicle near-end connection device provided by an embodiment of the present application;
fig. 9 is a schematic structural diagram of a vehicle remote connection device provided in an embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It should also be understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to" determining "or" in response to detecting ". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".
Furthermore, in the description of the present application and the appended claims, the terms "first," "second," "third," and the like are used for distinguishing between descriptions and not necessarily for describing or implying relative importance.
Reference throughout this specification to "one embodiment" or "some embodiments," or the like, means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," or the like, in various places throughout this specification are not necessarily all referring to the same embodiment, but rather "one or more but not all embodiments" unless specifically stated otherwise. The terms "comprising," "including," "having," and variations thereof mean "including, but not limited to," unless expressly specified otherwise.
When vehicle remote diagnosis is performed, a vehicle near-end connection device and a vehicle far-end connection device are often used for transferring diagnostic information, which requires that the vehicle near-end connection device and the vehicle far-end connection device are connected through the Internet, common Internet connection includes a Peer-to-Peer (P2P) communication connection mode and a connection mode transferred through a designated server, because the P2P communication connection mode is limited by Network Address Translation (NAT) devices of both communication parties and Network support conditions of an operator, at present, the vehicle near-end device and the vehicle far-end device are mainly connected in a data forwarding mode through the designated server, because data needs to be forwarded through the server, communication delay is high, the number of accessed communication is related to the performance of the server, and the number of accessed users is limited.
The embodiments of the present application can solve the above technical problems, and in order to explain the technical solutions proposed by the embodiments of the present application, the following description is given by using specific embodiments.
First, as shown in fig. 1, a schematic system structure diagram of a vehicle remote connection system according to a first embodiment of the present application is provided. As can be seen from fig. 1, the vehicle remote connection system 100 provided by this embodiment includes a vehicle near-end connection device 101, a vehicle far-end connection device 102, and a designated data relay server 103; the vehicle near-end connection device 101 establishes a P2P connection with the vehicle far-end connection device 102, or establishes a connection with the vehicle far-end connection device 102 through a specified data relay server 103.
In the embodiment of the application, the vehicle near-end connecting device 101 is used for sending a P2P punching request to the vehicle far-end connecting device; if confirmation information returned by the vehicle remote-end connecting equipment based on the P2P punching request is received, establishing P2P connection with the vehicle remote-end connecting equipment; and if the confirmation information returned by the vehicle remote-end connection equipment is not received, establishing connection with the vehicle remote-end connection equipment through the data transfer server 103.
The vehicle far-end connecting device 102 is used for generating confirmation information based on a P2P punching request if the P2P punching request sent by the vehicle near-end connecting device 102 is received; sending the confirmation information to the vehicle near-end connection device 101; if the vehicle near-end connecting device 101 is determined to receive the confirmation information, establishing a P2P connection with the vehicle near-end connecting device 101; and if the vehicle near-end connecting equipment is determined not to receive the confirmation information, establishing connection with the vehicle near-end connecting equipment 101 through the data transfer server 103.
It should be noted that, in the embodiment of the present application, the vehicle near-end connection device 102 is a device that is connected to the vehicle to be diagnosed through short-range communication via a preset communication protocol, for example, a device that is connected to the vehicle to be diagnosed through short-range communication via an OBD protocol.
The vehicle remote connection device 102 is a device that is connected to the vehicle diagnosis device by short-range communication via a preset communication protocol, for example, a device that is connected to the vehicle diagnosis device by OBD communication.
In the embodiment of the application, the P2P communication mode is used as a communication mode between the vehicle near-end connection device 102 and the vehicle far-end connection device 103, so that the real-time performance of vehicle remote diagnosis and the efficiency of data transmission are improved, and when the P2P communication is limited, the communication between the vehicle near-end connection device and the vehicle far-end connection device is realized in a mode that a server forwards data, so that the experience effect of a user is further improved.
The communication connection method provided by the embodiment of the present application will be described below with reference to fig. 2 and fig. 3, where the vehicle near-end connection device and the vehicle far-end connection device are respectively used as execution subjects.
Fig. 2 is a flowchart illustrating an implementation of a communication connection method according to a second embodiment of the present application. It should be noted that the communication connection method provided in this embodiment is applied to the vehicle near-end connection device 101 shown in fig. 1, and may be specifically implemented by hardware or software of the vehicle near-end connection device 101. The details are as follows:
s201 sends a P2P hole-making request to the vehicular remote-end connection device.
It should be noted that, when a P2P communication connection needs to be established between devices, a party initiating a P2P connection request needs to acquire an IP address and a port number of a device to be connected to the P2P data relay server, and send a P2P request to a device to be connected to the P2P communication connection according to the acquired IP address and port number of the device to be connected to the P2 3526 data relay server. In this embodiment, a P2P hole punching request including the IP address and the port number of the vehicle remote connection device is sent to the vehicle remote connection device according to the IP address and the port number of the vehicle remote connection device.
It should be noted that, in this embodiment of the present application, the P2P hole punching request includes a first P2P hole punching request sent by a network address translation NAT hole punching protocol based on the transmission control protocol TCP and a second P2P hole punching request sent by a NAT hole punching protocol based on the user datagram protocol UDP. Wherein, the first P2P hole request of the TCP-based NAT hole protocol is used for sending a TCP-based P2P connection to the vehicle remote connection device; the second P2P hole request sent by the UDP based NAT hole protocol is used to send a UDP based P2P connection to the vehicular remote connection device.
Since the TCP-based P2P connection has reliability of TCP itself and high efficiency of P2P connection, a TCP-based P2P connection is generally a preferable connection method. However, because the TCP-based P2P connection is limited by NAT devices and network support conditions of both connecting parties, so that the TCP-based P2P connection success rate is not very high, and is usually lower than 50%, in an optional implementation manner of the present application, in order to improve the connection power of P2P and improve the experience effect of a user, the first P2P hole punching request is first sent to the vehicle remote connection device; if the confirmation information returned by the vehicle remote connection device based on the first P2P hole punching request is not received, it indicates that the NAT device corresponding to the vehicle remote connection device or the network condition does not support TCP-based P2P connection, and at this time, further sends the second P2P hole punching request to the vehicle remote connection device; it should be noted that, because the UDP-based P2P connection has the advantage of high UDP communication efficiency, and compared to the TCP communication, there are many networks supporting UDP communication, so in this embodiment, when the NAT device or the network corresponding to the vehicle remote device does not support the TCP-based P2P connection, the second P2P hole request is further sent to the vehicle connection device to attempt to establish the P2P communication connection.
Although the UDP-based P2P connection has the advantage of UDP communication, it is similar to the TCP-based P2P connection, and the connection process is limited by the NAT devices of both sides, so if the NAT devices of both sides do not support P2P connection, it is necessary to establish a connection with the vehicle remote connection device through a specified data relay server.
For example, in other optional implementations of the present application, before the sending of the P2P hole request to the vehicle remote connection device, it may be determined whether the NAT device corresponding to the vehicle remote connection device supports a TCP-based P2P connection or supports a UDP-based P2P connection, and if the NAT device of the vehicle connection device supports a TCP-based P2P connection and does not support a UDP-based P2P connection, the first P2P hole request is correspondingly sent to the vehicle remote connection device, and at this time, it is determined whether it is possible to receive confirmation information that the vehicle remote connection device returns based on the first P2P hole request only according to whether a current network supports a TCP-based P2P connection. Correspondingly, if the NAT device of the vehicle connection device supports UDP-based P2P connection and does not support TCP-based P2P connection, the second P2P hole request is correspondingly sent to the vehicle remote connection device, and at this time, it is determined whether the confirmation information returned by the vehicle remote connection device based on the second P2P hole request can be received only according to whether the current network supports UDP-based P2P connection.
S202, if confirmation information returned by the vehicle far-end connecting equipment based on the P2P punching request is received, establishing P2P connection with the vehicle far-end connecting equipment.
It can be understood that, in the embodiment of the present application, since the P2P hole request includes a first P2P hole request sent by a TCP-based NAT hole protocol and a second P2P hole request sent by a UDP-based NAT hole protocol, the type of the acknowledgement information returned by the vehicle far-end connection device received by the vehicle near-end connection device is related to the type of the P2P hole request sent by the vehicle near-end connection device. For example, if the first P2P hole request is sent to the vehicle remote connection device, the vehicle near-end connection device may receive the confirmation information returned by the vehicle remote connection device based on the first P2P hole request; if the second P2P hole request is sent to the vehicle remote connection device, the vehicle near-end connection device may receive confirmation information returned by the vehicle remote connection device based on the second P2P hole request.
For example, in this embodiment, if receiving the confirmation information returned by the vehicle remote connection device based on the first P2P punching request, or receiving the confirmation information returned by the vehicle remote connection device based on the second P2P punching request, the P2P connection is established with the vehicle remote connection device.
It can be understood that, if the P2P hole request includes a first P2P hole request sent by a TCP-based NAT hole protocol; correspondingly, sending a P2P hole-making request to the vehicle remote connection device, including:
sending the first P2P hole-making request to the vehicle remote connection device;
it should be understood that, in this alternative implementation, if the confirmation information returned by the vehicle remote connection device based on the P2P punching request is received, the establishing the P2P connection with the vehicle remote connection device includes:
and if the confirmation information returned by the vehicle remote connection equipment based on the first P2P punching request is received, establishing P2P connection with the vehicle remote connection equipment.
Exemplarily, if the P2P hole request includes a second P2P hole request sent by UDP-based NAT hole protocol; correspondingly, sending a P2P hole request to the vehicular remote connection device, including sending the second P2P hole request to the vehicular remote connection device;
it should be understood that, in this alternative implementation, if the confirmation information returned by the vehicle remote connection device based on the P2P punching request is received, the establishing the P2P connection with the vehicle remote connection device includes:
and if the confirmation information returned by the vehicle remote connection equipment based on the second P2P punching request is received, establishing P2P connection with the vehicle remote connection equipment.
And S203, if the confirmation information returned by the vehicle far-end connecting equipment is not received, establishing connection with the vehicle far-end connecting equipment through a specified data transfer server.
It can be understood that, if the confirmation information returned by the vehicle remote connection device is not received, the NAT device of the vehicle remote connection device may not support the corresponding P2P connection, and at this time, in order to ensure smooth data transmission, a connection is established with the vehicle remote connection device through a specified data relay server, it should be noted that the specified data relay server may be a P2P relay server between the vehicle near-end connection device and the vehicle remote connection device, or may not be the P2P relay server.
As can be seen from the above analysis, in this embodiment, the P2P communication mode is used as a communication mode between the vehicle near-end connection device and the vehicle far-end connection device, so as to improve the real-time performance of the vehicle remote diagnosis and the efficiency of data transmission, and when the P2P communication is limited, the communication between the vehicle near-end connection device and the vehicle far-end connection device is realized in a mode of forwarding data by the server, so as to further improve the experience effect of the user.
Fig. 3 is a flowchart illustrating an implementation of a communication connection method according to a third embodiment of the present application. It should be noted that, compared with the communication connection method shown in fig. 2, the communication connection method provided in this embodiment has the same implementation processes as those of S302 to S304 and S201 to S203, which are not described herein again, and the difference is that S301 is further included before S302. The details are as follows:
s301, obtaining the IP address and the port number of the vehicle remote connection device through the data relay server.
And S302, sending a P2P punching request to the vehicle remote connection device.
And S303, if confirmation information returned by the vehicle remote connection equipment based on the P2P punching request is received, establishing P2P connection with the vehicle remote connection equipment.
And S304, if the confirmation information returned by the vehicle remote end connection equipment is not received, establishing connection with the vehicle remote end connection equipment through a specified data transfer server.
Fig. 4 is a flowchart of an implementation of a communication connection method according to a fourth embodiment of the present application. It should be noted that, in this embodiment, hardware or software of the vehicle remote connection device 102 shown in fig. 1 is used for implementation, and specific implementation processes of each step may refer to descriptions of each step in fig. 2, which are not described herein again. Specifically, the communication connection method provided in this embodiment includes:
s401, if a P2P punching request sent by a vehicle near-end connecting device is received, generating confirmation information based on the P2P punching request.
S402, sending the confirmation information to the vehicle near-end connecting equipment.
And S403, if the vehicle near-end connecting device is determined to receive the confirmation information, establishing P2P connection with the vehicle near-end connecting device.
And S404, if the vehicle near-end connecting equipment is determined not to receive the confirmation information, establishing connection with the vehicle near-end connecting equipment through a specified data transfer server.
Fig. 5 is an interaction flowchart of a communication connection method according to a fifth embodiment of the present application. Specifically, the communication connection method provided in this embodiment includes:
s501, the vehicle near-end connecting device sends a P2P hole punching request to the vehicle far-end connecting device;
s502, after the vehicle remote end connecting device receives the P2P punching request, generating confirmation information based on the P2P punching request;
s503, the vehicle far-end connecting device sends the confirmation information to the vehicle near-end connecting device;
s504, if the vehicle near-end connecting device receives the confirmation information returned by the vehicle far-end connecting device, the vehicle near-end connecting device establishes P2P connection with the vehicle far-end connecting device;
and S505, if the vehicle near-end connecting device does not receive the confirmation information returned by the vehicle far-end connecting device, the vehicle near-end connecting device establishes connection with the vehicle far-end connecting device through the data transfer server.
Based on the communication connection method provided by the above embodiment, the embodiment of the invention further provides an embodiment of the vehicle connection device implementing the above communication connection method embodiment.
Fig. 6 is a schematic structural diagram of a vehicle near-end connection device according to a sixth embodiment of the present application. It should be noted that, the vehicle near-end connection device 600 provided in this embodiment includes modules for executing steps in the embodiment corresponding to fig. 2 or fig. 3, and refer to the related description in the embodiment corresponding to fig. 2 or fig. 3 specifically. For convenience of explanation, only the portions related to the present embodiment are shown. As shown in fig. 6, the vehicle proximal end connection apparatus 600 includes:
a sending module 601, configured to send a P2P hole punching request to a vehicle remote connection device.
A first connection module 602, configured to establish a P2P connection with the vehicle remote connection device if receiving a confirmation message returned by the vehicle remote connection device based on the P2P hole request.
A second connection module 603, configured to establish a connection with the vehicle remote connection device through a specified data relay server if the confirmation information returned by the vehicle remote connection device is not received.
In an optional implementation manner, the P2P hole punching request includes a first P2P hole punching request sent by a TCP-based NAT hole punching protocol and a second P2P hole punching request sent by a UDP-based NAT hole punching protocol;
correspondingly, the sending module 601 includes:
a first sending unit, configured to send the first P2P hole punching request to the vehicle remote connection device;
a second sending unit, configured to send the second P2P hole punching request to the vehicle remote connection device if no confirmation information returned by the vehicle remote connection device based on the first P2P hole punching request is received;
correspondingly, the first connection module 602 is specifically configured to:
and if the confirmation information returned by the vehicle remote connection equipment based on the first P2P punching request is received or the confirmation information returned by the vehicle remote connection equipment based on the second P2P punching request is received, establishing P2P connection with the vehicle remote connection equipment.
In an optional implementation manner, the P2P hole request includes a first P2P hole request sent by a TCP-based NAT hole protocol;
correspondingly, the sending module 601 is specifically configured to:
sending the first P2P hole-making request to the vehicle remote connection device;
correspondingly, the first connection module 602 is specifically configured to:
and if the confirmation information returned by the vehicle remote connection equipment based on the first P2P punching request is received, establishing P2P connection with the vehicle remote connection equipment.
In an optional implementation manner, the P2P hole punching request includes a second P2P hole punching request sent by a UDP-based NAT hole punching protocol;
correspondingly, the sending module 601 is specifically configured to:
sending the second P2P hole-making request to the vehicle remote connection device;
correspondingly, the first connection module 602 is specifically configured to:
and if the confirmation information returned by the vehicle remote connection equipment based on the second P2P punching request is received, establishing P2P connection with the vehicle remote connection equipment.
In an optional implementation manner, the method further includes:
the acquisition module is used for acquiring the IP address and the port number of the vehicle remote connection equipment through the data transfer server;
correspondingly, the sending module 601 is specifically configured to:
and sending the P2P punching request to the vehicle far-end connection equipment according to the IP address and the port number of the vehicle far-end connection equipment.
Fig. 7 is a schematic structural diagram of a vehicle remote connection device according to a seventh embodiment of the present application. It should be noted that, the vehicle far-end connection device 700 provided in this embodiment includes modules for executing steps in the embodiment corresponding to fig. 4, and refer to the related description in the embodiment corresponding to fig. 4 specifically. For convenience of explanation, only the portions related to the present embodiment are shown. As shown in fig. 7, the vehicle remote connection apparatus 700 includes:
a generating module 701, configured to generate acknowledgement information based on a P2P punching request if the punching request of P2P sent by a vehicle near-end connection device is received;
a sending module 702, configured to send the confirmation information to the vehicle near-end connection device;
a third connection module 703, configured to establish a P2P connection with the vehicle near-end connection device if it is determined that the vehicle near-end connection device receives the confirmation information;
a fourth connection module 704, configured to establish a connection with the vehicle near-end connection device through a specified data relay server if it is determined that the vehicle near-end connection device does not receive the confirmation information.
Fig. 8 is a schematic structural diagram of a vehicle near-end connection device provided in an embodiment of the present application. As shown in fig. 8, the vehicle proximal end connecting device 8 of this embodiment includes: a processor 80, a memory 81 and a computer program 82 stored in said memory 81 and being executable on said processor 80, said processor 80 implementing the steps in the method embodiments described above with reference to fig. 2 or fig. 3 when executing said computer program 82.
The Processor 80 may be a Central Processing Unit (CPU), and the Processor 80 may be other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 81 may in some embodiments be an internal storage unit of the vehicle proximity connection device 8, such as a hard disk or a memory of the vehicle proximity connection device 8. The memory 81 may also be an external storage device of the vehicle near-end connection device 8 in other embodiments, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a flash memory Card (FlashCard), and the like, which are provided on the vehicle near-end connection device 8. Further, the memory 81 may also include both an internal storage unit and an external storage device of the vehicle near-end connection device 8. The memory 81 is used for storing an operating system, an application program, a BootLoader (BootLoader), data, and other programs, such as program codes of the computer program. The memory 81 may also be used to temporarily store data that has been output or is to be output.
Fig. 9 is a schematic structural diagram of a vehicle remote connection device provided in an embodiment of the present application. As shown in fig. 9, the vehicle distal end connecting apparatus 9 of this embodiment includes: a processor 90, a memory 91 and a computer program 92 stored in said memory 91 and executable on said processor 90, said processor 90 implementing the steps in the method embodiment described above with reference to fig. 4 when executing said computer program 92.
The Processor 90 may be a Central Processing Unit (CPU), and the Processor 90 may be other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 91 may in some embodiments be an internal storage unit of the vehicle remote connection device 9, such as a hard disk or a memory of the vehicle remote connection device 9. The memory 91 may also be an external storage device of the vehicle remote connection device 9 in other embodiments, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a flash Card (FlashCard), and the like, which are provided on the vehicle remote connection device 9. Further, the memory 91 may also include both an internal storage unit and an external storage device of the vehicle remote connection device 9. The memory 91 is used for storing an operating system, an application program, a BootLoader (BootLoader), data, and other programs, such as program codes of the computer program. The memory 91 may also be used to temporarily store data that has been output or is to be output.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
An embodiment of the present application further provides a network device, where the network device includes: at least one processor, a memory, and a computer program stored in the memory and executable on the at least one processor, the processor implementing the steps of any of the various method embodiments described above when executing the computer program.
An embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored, and the computer program, when executed by a processor, implements the steps in the method embodiment described in fig. 2 above, or the computer program, when executed by the processor, implements the steps in the method embodiment described in fig. 3 above.
The present application further provides a computer program product, which when running on a vehicle near-end connection device for vehicle remote diagnosis, causes the vehicle near-end connection device to execute the steps in the method embodiment described in fig. 2 or fig. 3 above, or when running on a vehicle far-end connection device for vehicle remote diagnosis, causes the vehicle far-end connection device to execute the steps in the method embodiment described in fig. 4 above.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, all or part of the processes in 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 can implement the steps of the embodiments of the methods described above when the computer program is executed by a processor. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer readable medium may include at least: any entity or device capable of carrying computer program code to a photographing apparatus/electronic device, a recording medium, computer Memory, Read-Only Memory (ROM), random-access Memory (RAM), an electrical carrier signal, a telecommunications signal, and a software distribution medium. Such as a usb-disk, a removable hard disk, a magnetic or optical disk, etc. In certain jurisdictions, computer-readable media may not be an electrical carrier signal or a telecommunications signal in accordance with legislative and patent practice.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus/network device and method may be implemented in other ways. For example, the above-described apparatus/network device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implementing, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.
Claims (10)
1. A communication connection method is applied to vehicle near-end connection equipment and is characterized by comprising the following steps:
sending a P2P punching request to a vehicle remote connection device;
if confirmation information returned by the vehicle remote connection equipment based on the P2P punching request is received, establishing P2P connection with the vehicle remote connection equipment;
and if the confirmation information returned by the vehicle remote-end connecting equipment is not received, establishing connection with the vehicle remote-end connecting equipment through a specified data transfer server.
2. The method of claim 1, wherein the P2P hole requests include a first P2P hole request sent by a TCP-based NAT hole protocol and a second P2P hole request sent by a UDP-based NAT hole protocol;
correspondingly, sending a P2P hole-making request to the vehicle remote connection device includes:
sending the first P2P hole-making request to the vehicle remote connection device;
if the confirmation information returned by the vehicle remote connection equipment based on the first P2P punching request is not received, sending the second P2P punching request to the vehicle remote connection equipment;
if the confirmation information returned by the vehicle remote connection device based on the P2P hole punching request is received, the establishing P2P connection with the vehicle remote connection device includes:
and if the confirmation information returned by the vehicle remote connection equipment based on the first P2P punching request is received, or if the confirmation information returned by the vehicle remote connection equipment based on the second P2P punching request is received, establishing P2P connection with the vehicle remote connection equipment.
3. The method of claim 1, wherein the P2P punch request comprises a first P2P punch request sent by a TCP-based NAT punch protocol;
correspondingly, sending a P2P hole-making request to the vehicle remote connection device includes:
sending the first P2P hole-making request to the vehicle remote connection device;
if the confirmation information returned by the vehicle remote connection device based on the P2P hole punching request is received, the establishing P2P connection with the vehicle remote connection device includes:
and if the confirmation information returned by the vehicle remote connection equipment based on the first P2P punching request is received, establishing P2P connection with the vehicle remote connection equipment.
4. The method of claim 1, wherein the P2P hole request comprises a second P2P hole request sent by UDP-based NAT hole protocol;
correspondingly, sending a P2P hole-making request to the vehicle remote connection device includes:
sending the second P2P hole-making request to the vehicle remote connection device;
if the confirmation information returned by the vehicle remote connection device based on the P2P hole punching request is received, the establishing P2P connection with the vehicle remote connection device includes:
and if the confirmation information returned by the vehicle remote connection equipment based on the second P2P punching request is received, establishing P2P connection with the vehicle remote connection equipment.
5. The method of any of claims 1 to 4, further comprising, prior to sending a P2P hole request to the vehicular remote connection device:
acquiring the IP address and the port number of the vehicle remote connection equipment through the data transfer server;
correspondingly, sending a P2P hole-making request to the vehicle remote connection device includes:
and sending the P2P punching request to the vehicle far-end connection equipment according to the IP address and the port number of the vehicle far-end connection equipment.
6. A communication connection method is applied to a vehicle far-end connection device and is characterized by comprising the following steps:
if a P2P punching request sent by a vehicle near-end connecting device is received, generating confirmation information based on the P2P punching request;
sending the confirmation information to the vehicle near-end connection equipment;
if the vehicle near-end connecting device is determined to receive the confirmation information, establishing P2P connection with the vehicle near-end connecting device;
and if the vehicle near-end connecting equipment is determined not to receive the confirmation information, establishing connection with the vehicle near-end connecting equipment through a specified data transfer server.
7. A communication connection method is applied to a vehicle remote connection system, wherein the vehicle remote connection system comprises a vehicle near-end connection device, a vehicle far-end connection device and a specified data transfer server, and the method comprises the following steps:
the vehicle near-end connecting device sends a P2P punching request to the vehicle far-end connecting device;
after receiving the P2P punching request, the vehicle remote-end connecting equipment generates confirmation information based on the P2P punching request;
the vehicle far-end connecting device sends the confirmation information to the vehicle near-end connecting device;
if the vehicle near-end connecting device receives the confirmation information returned by the vehicle far-end connecting device, the vehicle near-end connecting device establishes P2P connection with the vehicle far-end connecting device;
and if the vehicle near-end connecting equipment cannot receive the confirmation information returned by the vehicle far-end connecting equipment, the vehicle near-end connecting equipment establishes connection with the vehicle far-end connecting equipment through the data transfer server.
8. A vehicle remote connection system is characterized by comprising a vehicle near-end connection device, a vehicle far-end connection device and a specified data transfer server;
the vehicle near-end connecting device is used for sending a P2P punching request to the vehicle far-end connecting device; if confirmation information returned by the vehicle remote connection equipment based on the P2P punching request is received, establishing P2P connection with the vehicle remote connection equipment; if the confirmation information returned by the vehicle remote-end connection equipment is not received, connection is established with the vehicle remote-end connection equipment through the data transfer server;
the vehicle far-end connecting device is used for generating confirmation information based on the P2P punching request if the P2P punching request sent by the vehicle near-end connecting device is received; sending the confirmation information to the vehicle near-end connection equipment; if the vehicle near-end connecting device is determined to receive the confirmation information, establishing P2P connection with the vehicle near-end connecting device; and if the vehicle near-end connecting equipment is determined not to receive the confirmation information, establishing connection with the vehicle near-end connecting equipment through the data transfer server.
9. A vehicle proximity connection apparatus, comprising:
a memory for storing an executable computer program;
a processor for invoking the executable computer program to perform the communication connection method of any one of claims 1-5.
10. A vehicle remote connection apparatus, comprising:
a memory for storing an executable computer program;
a processor for invoking the executable computer program to perform the communication connection method of claim 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010466228.5A CN111741075A (en) | 2020-05-28 | 2020-05-28 | Communication connection method, vehicle remote connection system and connection equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010466228.5A CN111741075A (en) | 2020-05-28 | 2020-05-28 | Communication connection method, vehicle remote connection system and connection equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111741075A true CN111741075A (en) | 2020-10-02 |
Family
ID=72646480
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010466228.5A Pending CN111741075A (en) | 2020-05-28 | 2020-05-28 | Communication connection method, vehicle remote connection system and connection equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111741075A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114143907A (en) * | 2021-11-26 | 2022-03-04 | 阿波罗智联(北京)科技有限公司 | Wireless connection establishing method and device, electronic equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080109130A1 (en) * | 2006-11-08 | 2008-05-08 | Huang Chung-Yi | Remote Vehicle Diagnosis System |
| US20180286146A1 (en) * | 2017-03-29 | 2018-10-04 | Launch Tech Co., Ltd. | Communication method, device, and system for vehicle remote diagnosis |
| CN109660637A (en) * | 2018-11-16 | 2019-04-19 | 深圳市网心科技有限公司 | P2P burrows transmission method and system, electronic device and computer readable storage medium |
| CN110888418A (en) * | 2019-12-23 | 2020-03-17 | 深圳市元征科技股份有限公司 | Vehicle diagnosis method, device, equipment and readable storage medium |
-
2020
- 2020-05-28 CN CN202010466228.5A patent/CN111741075A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080109130A1 (en) * | 2006-11-08 | 2008-05-08 | Huang Chung-Yi | Remote Vehicle Diagnosis System |
| US20180286146A1 (en) * | 2017-03-29 | 2018-10-04 | Launch Tech Co., Ltd. | Communication method, device, and system for vehicle remote diagnosis |
| CN109660637A (en) * | 2018-11-16 | 2019-04-19 | 深圳市网心科技有限公司 | P2P burrows transmission method and system, electronic device and computer readable storage medium |
| CN110888418A (en) * | 2019-12-23 | 2020-03-17 | 深圳市元征科技股份有限公司 | Vehicle diagnosis method, device, equipment and readable storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 齐虹: "《网络通信系统设计与应用研究》", 31 December 2015 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114143907A (en) * | 2021-11-26 | 2022-03-04 | 阿波罗智联(北京)科技有限公司 | Wireless connection establishing method and device, electronic equipment and storage medium |
| CN114143907B (en) * | 2021-11-26 | 2023-05-12 | 阿波罗智联(北京)科技有限公司 | Wireless connection establishment method, device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101207604B (en) | Virtual machine system and communication processing method thereof | |
| CN110677432A (en) | Network protocol internal proxy forwarding method, device, medium and terminal equipment | |
| US6442612B1 (en) | Device and method for communication over a network | |
| CN111427335A (en) | Vehicle remote diagnosis method, equipment connector and vehicle connector | |
| CN109857572B (en) | Method, device and equipment for realizing remote calling and computer readable storage medium | |
| CN113391979A (en) | Processing method, equipment and system for monitoring data display and storage medium | |
| CN106357654B (en) | Remote procedure calling method, device and communication system | |
| CN102594886A (en) | Method and device for direct communication between browsers, and communication system | |
| CN111741075A (en) | Communication connection method, vehicle remote connection system and connection equipment | |
| CN114697388B (en) | Data transmission method and device | |
| CN110430478B (en) | Networking communication method, device, terminal equipment and storage medium | |
| CN111416851A (en) | Method for session synchronization among multiple load balancers and load balancer | |
| CN114697888B (en) | 5G message processing method, device and storage medium | |
| CN110661850A (en) | Edge calculation method, system, computer equipment and storage medium | |
| CN110661895A (en) | Network address mapping method and network address mapping equipment of server | |
| CN114326673A (en) | Vehicle remote diagnosis method and device, connector and storage medium | |
| CN110896414B (en) | Method for realizing message notification between services by using IOT (Internet of things) | |
| CN111624983B (en) | Synchronous connection method and vehicle remote diagnosis system | |
| CN114363204A (en) | Request monitoring method, network device and storage medium | |
| CN106060155A (en) | P2P (Peer to Peer) resource sharing method and device | |
| CN111464654A (en) | Data transmission method and device | |
| CN111580987A (en) | Remote procedure calling method and device, storage medium and terminal equipment | |
| CN113419907B (en) | Operating system detection method and device, electronic device and computer equipment | |
| CN114125017B (en) | Media information display method and device, storage medium and electronic equipment | |
| CN115225706B (en) | Data transmission method, device, vehicle and storage medium |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20201002 |
|
| RJ01 | Rejection of invention patent application after publication |