CN111131483A

CN111131483A - Vehicle-mounted intelligent computing device, cloud server and method for reporting and acquiring IP address

Info

Publication number: CN111131483A
Application number: CN201911394985.XA
Authority: CN
Inventors: 覃树才; 唐焱
Original assignee: Shanghai Pateo Network Technology Service Co Ltd
Current assignee: Shanghai Pateo Network Technology Service Co Ltd
Priority date: 2019-12-30
Filing date: 2019-12-30
Publication date: 2020-05-08

Abstract

The invention provides a vehicle-mounted intelligent computing device and a cloud server. The in-vehicle intelligent computing device includes: the network communication module comprises a TCP protocol stack to realize communication with a cloud server, acquires a current IP address of the vehicle-mounted intelligent computing device, judges whether the current IP address is the same as a previous IP address or not, and reports the current IP address to the cloud server through the TCP protocol stack in response to the fact that the current IP address is different from the previous IP address. The cloud server comprises: and the IP reporting interface is coupled with the vehicle-mounted intelligent computing device of each vehicle to receive the encrypted IP address reported by each vehicle-mounted intelligent computing device, and decrypts the encrypted IP address of each vehicle-mounted intelligent computing device by utilizing the token information of each vehicle-mounted intelligent computing device to obtain and update the current IP address of each vehicle-mounted intelligent computing device.

Description

Vehicle-mounted intelligent computing device, cloud server and method for reporting and acquiring IP address

Technical Field

The invention relates to the field of background management of vehicles, in particular to a vehicle-mounted intelligent computing device, a cloud server, an IP address reporting method suitable for the vehicle-mounted intelligent computing device and an IP address obtaining method suitable for the cloud server.

Background

In 2017, the automobile sales volume in China reaches 2888 thousands of automobiles, and the increase is 3 percent on the same scale. The sales volume of the passenger cars is 2472 thousands of cars, and the increase of the cars is 1.4 percent on the same scale. The automobile keeping amount in China is also gradually increased, and by the end of 2016, the automobile keeping amount in China is 1.94 hundred million, which is increased by 13% on a par, wherein the automobile keeping amount of a private family reaches 1.46 hundred million, which is increased by 18% on a par, and accounts for 75% of the total automobile keeping amount.

As automobiles gradually become the most convenient travel tool in the market, users have higher and higher requirements on convenience of automobile use. Vehicle keys have also evolved from mechanical keys to electronic keys, and are currently moving from electronic keys to virtual keys.

In the virtual key system, a user can remotely control a vehicle through a user terminal, and wake up the vehicle in a dormant state, so as to perform adaptive setting in advance, such as opening a vehicle window, adjusting a seat, opening an air conditioner and the like.

In the awakening mechanism of the vehicle, a user can request the cloud server to awaken the vehicle through the user terminal application, the cloud server generates an awakening instruction and sends the awakening instruction to the IP address of the vehicle TBox so as to awaken the TBox module of the vehicle, and therefore communication and control with the vehicle are achieved.

In the scheme of waking up the vehicle by using the IP address of the vehicle TBox, the IP address of the vehicle TBox changes after the TBox dials each time, so that if the vehicle TBox needs to be woken up by initiating the IP address at the cloud server, the IP address of the vehicle TBox needs to be acquired in advance. In order to acquire the IP address of the vehicle TBox, the vehicle TBox can be set to periodically report the IP address of the TBox to a cloud server.

However, vehicle tboxes typically have stringent requirements on power consumption, do not allow the entire vehicle TBox to wake up frequently, and only allow the network communication module in the TBox to wake up itself periodically. However, the network communication module in the prior art has limited capability, generally only supports a basic IP protocol, and cannot directly establish application layer communication with the cloud server.

In addition, the IP awakening mechanism of the vehicle also relates to an encryption mechanism in the IP address reporting process and the safety verification problem of the awakening instruction.

In order to solve the problems of reporting and acquiring the IP address in the IP wakeup mechanism, the present invention aims to provide a special Tbox, i.e., a vehicle-mounted intelligent computing device, a cloud server, an IP address reporting method suitable for the vehicle-mounted intelligent computing device, and an IP address acquiring method suitable for the cloud server.

Disclosure of Invention

The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

According to an aspect of the present invention, there is provided an in-vehicle intelligent computing device, including: the network communication module comprises a TCP protocol stack to realize communication with a cloud server, acquires a current IP address of the vehicle-mounted intelligent computing device, judges whether the current IP address is the same as a previous IP address or not, and reports the current IP address to the cloud server through the TCP protocol stack in response to the fact that the current IP address is different from the previous IP address.

Furthermore, the network communication module receives an IP report response sent by the cloud server through the TCP protocol stack, and reports the current IP address to the cloud server again in response to not receiving the IP report response within a preset time.

Furthermore, the network communication module gives up reporting the current IP address to the cloud server in response to the reporting times of the same current IP address exceeding a preset number.

Further, the network communication module periodically wakes up to acquire the current IP address of the vehicle-mounted intelligent computing device in response to the vehicle-mounted intelligent computing device being in the dormant state.

Further, the network communication module continues to enter a dormant state in response to receiving the IP report response.

Further, the network communication module encrypts the current IP address by using token information of the vehicle-mounted intelligent computing device to obtain an encrypted IP address, and reports the encrypted IP address and the device ID of the vehicle-mounted intelligent computing device to the cloud server through the TCP protocol stack.

Further, the network communication module acquires the latest token information of the vehicle-mounted intelligent computing device as the token information of the vehicle-mounted intelligent computing device.

Still further, the in-vehicle intelligent computing device further comprises: and the application module is coupled with the network communication module and the cloud server, requests the cloud server for obtaining token information and sends the token information obtained from the cloud server to the network communication module to serve as the latest token information.

Furthermore, the application module responds to the first connection of the cloud server or receives a token information updating instruction sent by the cloud server, and requests the cloud server to acquire token information; or requesting to acquire token information from the cloud server at regular time.

According to another aspect of the invention, an IP address reporting method for an in-vehicle intelligent computing device is provided, which includes: acquiring a current IP address of the vehicle-mounted intelligent computing device; judging whether the current IP address is the same as the previous IP address; and reporting the current IP address to a cloud server through a TCP protocol stack in response to the current IP address being different from the previous IP address.

Further, the IP address reporting method further includes: receiving an IP report response sent by a cloud server through the TCP protocol stack; and in response to the fact that the IP report response is not received within the preset time, reporting the current IP address to a cloud server through the TCP protocol stack again.

Further, the IP address reporting method further includes: and in response to the fact that the sending times of the same current IP address exceed the preset number, giving up reporting of the current IP address to a cloud server.

Further, the obtaining the current IP address of the in-vehicle intelligent computing device includes: and responding to the fact that the vehicle-mounted intelligent computing device is in a dormant state, and periodically acquiring the current IP address of the vehicle-mounted intelligent computing device.

Further, the IP address reporting method further includes: and continuing to enter a dormant state in response to receiving the IP report response.

Further, the reporting the current IP address to the cloud server includes: encrypting the current IP address by adopting token information of the vehicle-mounted intelligent computing device to obtain an encrypted IP address; and reporting the encrypted IP address and the equipment ID of the vehicle-mounted intelligent computing device to a cloud server through the TCP protocol stack.

Further, the encrypting the current IP address using the token information of the in-vehicle smart computing device to obtain an encrypted IP address includes: obtaining the latest token information of the vehicle-mounted intelligent computing device as the token information of the vehicle-mounted intelligent computing device.

Further, the obtaining of the latest token information of the vehicle-mounted intelligent computing device comprises: requesting to acquire token information from the cloud server; and updating the token information acquired from the cloud server into the latest token information.

Further, the requesting token information from the cloud server includes: responding to a first connection of the cloud server or receiving a token information updating instruction sent by the cloud server, and requesting the cloud server to acquire token information; or requesting to acquire token information from the cloud server at regular time.

According to a further aspect of the present invention, there is provided a computer storage medium having stored thereon a computer program which, when executed, carries out the steps of the IP address reporting method as claimed in any one of the preceding claims.

According to still another aspect of the present invention, there is provided a cloud server for a vehicle, including: and the IP reporting interface is coupled with the vehicle-mounted intelligent computing device of each vehicle to receive the encrypted IP address reported by each vehicle-mounted intelligent computing device, and decrypts the encrypted IP address of each vehicle-mounted intelligent computing device by utilizing the token information of each vehicle-mounted intelligent computing device to obtain and update the current IP address of each vehicle-mounted intelligent computing device.

Furthermore, the cloud server stores the device ID and the associated token information of each vehicle-mounted intelligent computing device, the IP reporting interface receives the encrypted IP address and the device ID of each vehicle-mounted intelligent computing device, and the cloud server decrypts the encrypted IP address corresponding to the device ID by using the token information associated with each received device ID to obtain the current IP address of the vehicle-mounted intelligent computing device corresponding to the device ID and stores the current IP address and the received device ID in an associated manner.

Still further, the cloud server further comprises: and the cloud server generates token information by adopting a random algorithm, stores the token information and the equipment ID of the vehicle-mounted intelligent computing device in a correlation manner, and feeds the generated token information back to the vehicle-mounted intelligent computing device corresponding to the associated equipment ID.

Further, the cloud server sends a token information updating instruction to the vehicle-mounted intelligent computing device in response to the fact that the token information of the vehicle-mounted intelligent computing device is leaked, so that the vehicle-mounted intelligent computing device requests the token service interface to obtain the token information.

Further, the cloud server feeds back an IP report response to the vehicle-mounted intelligent computing device in response to receiving the encrypted IP address reported by the vehicle-mounted intelligent computing device.

According to another aspect of the present invention, there is provided a vehicle IP address acquisition method including: receiving an encrypted IP address reported by each vehicle-mounted intelligent computing device; and decrypting the encrypted IP address of each vehicle-mounted intelligent computing device by utilizing the token information of the vehicle-mounted intelligent computing device to obtain and update the current IP address of the vehicle-mounted intelligent computing device.

Still further, the receiving the encrypted IP address of each in-vehicle intelligent computing device comprises: receiving the encrypted IP address and the equipment ID of each vehicle-mounted intelligent computing device; and the decrypting the encrypted IP address of each vehicle-mounted intelligent computing device by using the token information of the vehicle-mounted intelligent computing device to obtain and store the current IP address of the vehicle-mounted intelligent computing device comprises the following steps: decrypting the encrypted IP address corresponding to the equipment ID by utilizing the token information associated with each received equipment ID to obtain the current IP address of the vehicle-mounted intelligent computing device corresponding to the equipment ID; and storing the current IP address in association with the received device ID.

Further, the IP address obtaining method further includes: responding to a request for acquiring token information of a vehicle-mounted intelligent computing device, and generating token information by adopting a random algorithm; storing the token information in association with a device ID of the in-vehicle smart computing device; and feeding back the generated token information to the vehicle-mounted intelligent computing device corresponding to the associated equipment ID.

Further, the IP address obtaining method further includes: and in response to the judgment that the token information of the vehicle-mounted intelligent computing device leaks, sending a token information updating instruction to the vehicle-mounted intelligent computing device to enable the vehicle-mounted intelligent computing device to request to acquire the token information.

Further, the IP address obtaining method further includes: and feeding back an IP report response to the vehicle-mounted intelligent computing device in response to receiving the encrypted IP address reported by the vehicle-mounted intelligent computing device.

According to yet another aspect of the present invention, there is provided a computer storage medium having stored thereon a computer program that, when executed, performs the steps of the IP address acquisition method as set forth in any one of the above.

Drawings

The above features and advantages of the present disclosure will be better understood upon reading the detailed description of embodiments of the disclosure in conjunction with the following drawings.

FIG. 1 is a schematic diagram of a virtual key architecture according to one aspect of the present invention;

FIG. 2 is a system diagram of a cloud server and an in-vehicle smart computing device according to an aspect of the present invention;

fig. 3 is a flow chart illustrating an on-board IP address reporting method according to an aspect of the present invention;

FIG. 4 is a partial flow diagram of an on-board IP address reporting method according to an aspect of the present invention;

fig. 5 is a flowchart illustrating an IP address obtaining method of a cloud server according to an aspect of the present invention;

FIG. 6 is a partial flow diagram of an on-board IP address reporting method according to an aspect of the present invention;

fig. 7 is a flowchart illustrating an IP address obtaining method of a cloud server according to an aspect of the present invention;

fig. 8 is a partial flow chart of an on-board IP address reporting method according to an aspect of the invention.

Detailed Description

The following description is presented to enable any person skilled in the art to make and use the invention and is incorporated in the context of a particular application. Various modifications, as well as various uses in different applications will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to a wide range of embodiments. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

In the following detailed description, numerous specific details are set forth in order to provide a more thorough understanding of the invention. It will be apparent, however, to one skilled in the art that the practice of the invention may not necessarily be limited to these specific details. In other instances, well-known structures and devices are shown in block diagram form, rather than in detail, in order to avoid obscuring the present invention.

The reader's attention is directed to all papers and documents which are filed concurrently with this specification and which are open to public inspection with this specification, and the contents of all such papers and documents are incorporated herein by reference. All the features disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise. Thus, unless expressly stated otherwise, each feature disclosed is one example only of a generic series of equivalent or similar features.

Note that where used, the designations left, right, front, back, top, bottom, positive, negative, clockwise, and counterclockwise are used for convenience only and do not imply any particular fixed orientation. In fact, they are used to reflect the relative position and/or orientation between the various parts of the object. Furthermore, the terms "first" and "second" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance.

In the description of the present invention, it should be noted that, unless otherwise explicitly specified or limited, the terms "mounted," "connected," and "connected" are to be construed broadly, e.g., as meaning either a fixed connection, a removable connection, or an integral connection; can be mechanically or electrically connected; they may be connected directly or indirectly through intervening media, or they may be interconnected between two elements. The specific meanings of the above terms in the present invention can be understood in specific cases to those skilled in the art.

It is noted that, where used, further, preferably, still further and more preferably is a brief introduction to the exposition of the alternative embodiment on the basis of the preceding embodiment, the contents of the further, preferably, still further or more preferably back band being combined with the preceding embodiment as a complete constituent of the alternative embodiment. Several further, preferred, still further or more preferred arrangements of the belt after the same embodiment may be combined in any combination to form a further embodiment.

The invention is described in detail below with reference to the figures and specific embodiments. It is noted that the aspects described below in connection with the figures and the specific embodiments are only exemplary and should not be construed as imposing any limitation on the scope of the present invention.

First, a brief introduction is made to the technical architecture of the virtual key that may be involved in the present disclosure, so that those skilled in the art can comprehensively understand the technical content and technical concept of the present invention as a water container for high buildings.

As shown in fig. 1, the virtual key architecture may include an in-vehicle smart computing device 110, a cloud server 120, and a user terminal 130.

The vehicle-mounted smart computing device 110 can be understood by those skilled in the art based on the conventional vehicle-mounted Tbox module, and the vehicle-mounted smart computing device 110 is further configured to implement a special function in the technical architecture of the virtual key, such as issuing, logging out, or replacing the virtual key, on the basis of implementing the function of the conventional vehicle-mounted Tbox.

Those skilled in the art will appreciate that the cloud server 120 may be based on a conventional content service provider (TSP) server, and the cloud server 120 may include, but is not limited to, the functions of a conventional TSP cloud platform, and may communicate with the in-vehicle smart computing device 110 and the user terminal 130 remotely via the internet. The cloud server 120 may perform management service of the virtual key of the vehicle by sending a control command to each in-vehicle smart computing device 110, and provide a vehicle borrowing authorization service to non-owner users. Specifically, the cloud server 120 may be responsible for providing services such as application of a virtual key, binding of the virtual key to a vehicle, logout and postponement of the virtual key to the owner's user terminal 130. The cloud server 120 does not directly manage the virtual key, but merely forwards the request related to the virtual key to the corresponding in-vehicle smart computing device 110, so as to perform corresponding management through the in-vehicle smart computing device 10. In an embodiment, the cloud server 120 may further provide services related to account registration, certificate application and issuance, and the like to the user, and provide an authorization service of the non-owner virtual key to the non-owner user.

The user terminal 130 includes, but is not limited to, a user's mobile phone, a tablet computer, and other handheld smart devices and wearable smart devices. The users may include owner users and non-owner users. When the user terminal 130 is located within a certain range of the vicinity of the in-vehicle smart computing device 110, near field communication with the in-vehicle smart computing device 110 may be achieved through bluetooth communication technology. When the user terminal 130 is far away from the in-vehicle smart computing device 110 and cannot communicate with the near field communication means, the user terminal can communicate with the cloud server 120 through the TCP/IP protocol, and then the cloud server 120 forwards the in-vehicle smart computing device 110.

When the vehicle is in the parking state, the in-vehicle smart computing device 110 may enter a deep sleep state, at which time communication with the user terminal 130 or the cloud server 120 cannot be achieved. However, in some cases, such as: the user may need to remotely perform the start and setting of the vehicle in advance, or the cloud server may need to perform background data update, and the like, and the user or the cloud server needs to control the vehicle or communicate with the in-vehicle smart computing device 110 when the vehicle is in a dormant state. Then, at this time, the cloud server 120 is first required to wake up the in-vehicle smart computing device 110. However, the communication module in the conventional vehicle Tbox only supports the IP protocol, and cannot directly establish application layer communication with the cloud server.

In order to realize the communication between the vehicle-mounted intelligent computing device 110 and the application layer of the cloud server in the dormant state, the invention provides the vehicle-mounted intelligent computing device and the corresponding cloud server.

Taking the in-vehicle intelligent computing device 200 and the cloud server 300 shown in fig. 2 as an example, in this embodiment, the in-vehicle intelligent computing device 200 includes a network communication module 210, and an open-source TCP protocol stack 211 is embedded in the network communication module 210 to achieve a simple TCP communication capability, so as to meet the communication requirement between the in-vehicle intelligent computing device 110 and the cloud server 120.

Since the vehicle-mounted intelligent device 200 is in a dormant state and cannot be awakened integrally, the network communication module 210 therein may periodically awaken itself, obtain the current IP address of the vehicle-mounted intelligent computing device 200 after awakening, determine whether the current IP address is the same as the previous IP address, and report the current IP address to the cloud server 300 through the TCP protocol stack 211 in response to that the current IP address is different from the previous IP address.

Preferably, before reporting the current IP address to the cloud server 300, the network communication module 210 may encrypt the current IP address by using the token information of the vehicle-mounted intelligent computing device to obtain an encrypted IP address, and then report the encrypted IP address to the cloud server 300 through the TCP protocol stack 211.

Correspondingly, the cloud server 300 includes an IP reporting interface 310 for providing IP reporting services. The IP reporting interface 310 is coupled to the on-board intelligent computing devices of each vehicle to receive the encrypted IP addresses reported by each on-board intelligent computing device, and decrypts the encrypted IP addresses of the on-board intelligent computing devices by using the token information of each on-board intelligent computing device to obtain and update the current IP addresses of the on-board intelligent computing devices.

The Token information (Token) is an irregular character string corresponding to the in-vehicle intelligent computing device 200, and on one hand, the Token information can be used for indicating the identity information of the in-vehicle intelligent computing device 200, and on the other hand, the Token information can be used for encrypting and decrypting communication data between the in-vehicle intelligent computing device 200 and the cloud server 300.

In-vehicle smart computing device 200 may include application module 220, and cloud server 300 includes a corresponding token service interface 320.

The application module 220 is coupled to the cloud server 300, and specifically, may implement application layer communication with the cloud server 300 through the token server interface 320 of the cloud server 300. Specifically, the application module 220 may request the cloud server 300 to obtain the token information of the in-vehicle smart computing device 200 through the token server interface 320 of the cloud server 300.

The token information request sent to the cloud server 300 may include identity information of the requesting end, i.e., the vehicle-mounted smart computing device 200, so that the cloud server 300 can verify the validity of the vehicle-mounted smart computing device 200 and identify the identity of the vehicle-mounted smart computing device 200.

The cloud server 300 receives the token information request sent by the vehicle-mounted intelligent computing device 200, and can identify the identity of the vehicle-mounted intelligent computing device 200 through the identity information included in the token information request. It can be understood that the cloud server 300 may also perform identity verification on the sending end after receiving the token information request, and continue the subsequent steps after the verification passes, and if the verification fails, the illegal token information request may be discarded.

Further, in response to receiving a token information request from the on-vehicle smart computing device 200, the cloud server 300 generates a token information by using a random algorithm, stores the token information in association with the device ID of the on-vehicle smart computing device 200, and feeds back the generated token information to the on-vehicle smart computing device 200 that sent the token information request.

The token information request of the in-vehicle intelligent apparatus 200 may be appended with the device ID of the in-vehicle intelligent computing apparatus 200, and the cloud server 300 stores the token information generated based on the token information request of the in-vehicle intelligent apparatus 200 in association with the device ID of the in-vehicle intelligent computing apparatus, so as to facilitate subsequent identification of the associated in-vehicle intelligent computing apparatus based on the token information or calling of the token information associated with the device ID based on the device ID of the in-vehicle intelligent computing apparatus.

It can be understood that the generated token information can implement symmetric encrypted communication between the cloud server 300 and the in-vehicle smart computing device 200, and therefore, after the token information is generated, the token information needs to be returned to the application module 220 of the requesting end based on the identity information (device ID) of the requesting end, and stored on the cloud server 300.

After receiving the token information returned by the cloud server, the application module 220 updates the latest token information to the network communication module 210, so that the network communication module encrypts the IP address by using the latest token information to obtain an encrypted IP address.

More specifically, when the in-vehicle smart computing device 200 first attempts to connect to the cloud server 300 after leaving the factory, the application module 220 may request the cloud server 300 to acquire the token information in response to the first connection to the cloud server 300.

Further, after the in-vehicle smart computing device 200 enters the operation phase after leaving the factory, when the user terminal determines that the token information may have a leak and requires to be replaced, or when the cloud server determines that the token information may have a leak and requires to be replaced, the cloud server 300 may generate a token information updating command and send the token information updating command to the corresponding in-vehicle smart computing device 200 to command the in-vehicle smart computing device to update the token information, so that the in-vehicle smart computing device 200 sends the token information request.

In response to the cloud server 300 sending the update token information instruction, the in-vehicle smart computing device 200 may request the cloud server 300 to obtain new token information in response to receiving the update token information instruction sent by the cloud server.

Further, to prevent data leakage caused by leakage of token information, the token information of the in-vehicle smart computing device 200 may be updated periodically, and the application module 220 may request the cloud server for obtaining the token information periodically.

It will be appreciated that in some other application scenarios, the application module 220 may also request token information from the cloud server for other scenarios.

Further, the cloud server 300 may feed back an IP report response to the in-vehicle intelligent computing device 200 through the IP report interface 310 in response to receiving the encrypted IP address reported by the in-vehicle intelligent computing device 200.

Preferably, the cloud server may verify the validity of the vehicle-mounted intelligent computing device 200 reporting the IP address, and when it is determined that the vehicle-mounted intelligent computing device 200 is a valid user, an ACK response is returned through the IP reporting interface.

Even more, the cloud server 300 returns an IP report success response after verifying the user validity and decrypting and storing the encrypted IP address.

Correspondingly, the in-vehicle intelligent computing device 200 receives an IP report response returned by the cloud server through the TCP protocol stack 211. It can be understood that a reasonable reporting time can be set for one IP address reporting, and when an IP reporting response returned by the cloud server 300 is not received within a preset time, the internet communication module 210 can report the current IP address of the vehicle-mounted intelligent computing device to the IP reporting interface 310 again through the TCP protocol stack 211. When receiving the IP report response returned by the cloud server 300 within the preset time, the network communication module 210 continues to enter the sleep state to wait for the next self-wakeup.

Preferably, when the IP reporting interface 310 of the cloud server 300 fails, it may affect the cloud server 300 to receive the IP address report data or generate the IP report response data, so that the IP address report response data cannot be obtained even if the network communication module 210 reports an IP address for an infinite number of times, and therefore, the reporting times may be set, and in response to the reporting times of the same current IP address exceeding a preset number, for example, three times, the network communication module 210 abandons reporting the current IP address to the cloud server 300, continues to enter the dormant state, and waits for the next self-wakeup.

According to another aspect of the invention, an IP address reporting method suitable for an on-vehicle intelligent computing device and an IP address obtaining method suitable for a cloud server are provided. The steps of the two corresponding methods are specifically set forth in an interactive fashion.

In one embodiment, as shown in fig. 3, the IP address reporting method for the vehicle-mounted intelligent computing device includes steps S310 to S330.

Wherein, step S310 is: and acquiring the current IP address of the vehicle-mounted intelligent computing device.

Step S320 is: and judging whether the current IP address is the same as the previous IP address.

Step S330 is: and in response to the current IP address being different from the previous IP address, reporting the current IP address to a cloud server through a TCP protocol stack.

The vehicle-mounted intelligent device is in a dormant state and cannot be integrally awakened, so that the network communication module can be periodically awakened, the current IP address of the vehicle-mounted intelligent computing device is obtained after the vehicle-mounted intelligent computing device is awakened, whether the current IP address is the same as the previous IP address or not is judged, and the current IP address is reported to a cloud server through the TCP protocol stack in response to the fact that the current IP address is different from the previous IP address.

Preferably, before reporting the current IP address to the cloud server, the current IP address may be encrypted by using token information of the vehicle-mounted intelligent computing device to obtain an encrypted IP address, and then the encrypted IP address may be reported to the cloud server through the TCP protocol stack.

The step S330 in the IP address reporting method can be subdivided into steps S331 to S332 as shown in fig. 4.

Step S331 is: and encrypting the current IP address of the vehicle-mounted intelligent computing device by using the token information of the vehicle-mounted intelligent computing device to obtain an encrypted IP address.

Step S332 is: and reporting the encrypted IP address and the equipment ID of the vehicle-mounted intelligent computing device to a cloud server through a TCP protocol stack.

Correspondingly, as shown in fig. 5, the method for acquiring an IP address of a cloud server includes steps S510 to S520.

Step S510 is: and receiving the encrypted IP address reported by each vehicle-mounted intelligent computing device.

Step S520 is: decrypting the encrypted IP address of each vehicle-mounted intelligent computing device by using the token information of the vehicle-mounted intelligent computing device to obtain and update the current IP address of the vehicle-mounted intelligent computing device.

The Token information (Token) is irregular character strings corresponding to the vehicle-mounted intelligent computing devices one to one, and on one hand, the Token information can be used for indicating identity information of the vehicle-mounted intelligent computing devices, and on the other hand, encryption and decryption of communication data between the vehicle-mounted intelligent computing devices and the cloud server can be achieved.

When the data reported by the vehicle-mounted intelligent computing device includes the encrypted IP address and the device ID, step S510 may correspond to: and receiving the encrypted IP address and the equipment ID of each vehicle-mounted intelligent computing device. Step S520 may correspond to: and decrypting the encrypted IP address corresponding to the equipment ID by utilizing the token information associated with each received equipment ID to obtain the current IP address of the vehicle-mounted intelligent computing device corresponding to the equipment ID, and storing the current IP address and the received equipment ID in an associated manner.

The token information can be requested by the vehicle-mounted intelligent computing device to the cloud server, and is generated by the cloud server and returned to the vehicle-mounted intelligent computing device.

Then, step S331 in the IP address reporting method may further include: obtaining the latest token information of the vehicle-mounted intelligent computing device as the token information of the vehicle-mounted intelligent computing device.

To obtain the latest token information of the in-vehicle smart computing device, as shown in fig. 6, the in-vehicle smart computing device may include steps S610 to S620.

Wherein, step S610 is: and requesting to acquire token information from the cloud server.

Step S620 is: and updating the token information acquired from the cloud server into the latest token information.

The token information request sent to the cloud server may include device information (such as a device ID) of the requesting end, i.e., the vehicle-mounted intelligent computing device, so that the cloud server can verify the validity of the vehicle-mounted intelligent computing device and identify the identity of the vehicle-mounted intelligent computing device.

More specifically, when the in-vehicle smart computing device first attempts to connect to the cloud server after leaving the factory, step S610 may be implemented as: in response to the first connection to the cloud server, the token information may be requested from the cloud server.

Furthermore, after the vehicle-mounted intelligent computing device enters an operation stage after leaving the factory, when the user terminal judges that the token information may have leakage and requires to be replaced, or when the cloud server judges that the token information may have leakage and requires to be replaced, the cloud server may generate a token information updating instruction and send the token information updating instruction to the corresponding vehicle-mounted intelligent computing device to instruct the vehicle-mounted intelligent computing device to update the token information, so that the vehicle-mounted intelligent computing device sends the token information request.

Corresponding to the cloud server sending the token information updating command, step S610 may be implemented as: and responding to a received token information updating instruction sent by the cloud server, and requesting the cloud server to acquire new token information.

Further, to prevent data leakage caused by leakage of token information, the token information of the in-vehicle smart computing device may be updated periodically, and step S610 may be implemented as: and requesting the cloud server to acquire the token information at regular time.

It is to be understood that in some other application scenarios, step S610 may also be implemented because other scenarios request the cloud server for obtaining token information.

Correspondingly, the cloud server receives a token information request sent by the vehicle-mounted intelligent computing device, and the identity of the vehicle-mounted intelligent computing device can be identified through equipment information included in the token information request. It can be understood that the cloud server can also perform identity authentication on the sending end after receiving the token information request, and the subsequent steps are continued after the authentication is passed, and if the authentication is not passed, the illegal token information request can be discarded.

Further, as shown in fig. 7, the IP address obtaining method may further include steps S530 to S550.

Step S530 is: and generating token information by adopting a random algorithm in response to receiving a request for obtaining the token information of the vehicle-mounted intelligent computing device.

Step S540 is: storing the token information in association with a device ID of the in-vehicle smart computing device.

Step S550 is: and feeding back the generated token information to the vehicle-mounted intelligent computing device corresponding to the associated equipment ID.

The cloud server stores the token information generated based on the token information request of the vehicle-mounted intelligent device and the device ID of the vehicle-mounted intelligent computing device in an associated manner, so that the associated vehicle-mounted intelligent computing device can be identified based on the token information or the device ID associated token information can be called based on the vehicle-mounted intelligent computing device.

Further, the cloud server may feed back an IP report response to the on-vehicle intelligent computing device in response to receiving the encrypted IP address reported by the on-vehicle intelligent computing device. The IP address obtaining method further includes: and feeding back an IP report response to the vehicle-mounted intelligent computing device in response to receiving the encrypted IP address reported by the vehicle-mounted intelligent computing device.

Preferably, the cloud server can verify the validity of the vehicle-mounted intelligent computing device reporting the IP address, and when the vehicle-mounted intelligent computing device is judged to be a legal user, an ACK response is returned through the IP reporting interface.

Even, the cloud server returns an IP report success response after verifying the user validity, decrypting the encrypted IP address and storing the encrypted IP address.

Correspondingly, the vehicle-mounted intelligent computing device receives an IP report response returned by the cloud server through a TCP protocol stack. It can be understood that a reasonable reporting time can be set for one-time IP address reporting, and when an IP reporting response returned by the cloud server is not received within a preset time, the internet communication module can report the current IP address of the vehicle-mounted intelligent computing device to the IP reporting interface again through the TCP protocol stack. When receiving the IP report response returned by the cloud server within the preset time, the network communication module 210 continues to enter the sleep state to wait for the next self-wakeup.

Preferably, when the cloud server fails, the cloud server may be affected to receive the IP address report data or generate the IP report response data, so that the IP address report response data cannot be obtained even if the vehicle-mounted intelligent computing device reports an IP address for numerous times.

Then, as shown in fig. 8, the IP address reporting method further includes steps S340 to S370.

Step S340 is: and receiving an IP report response sent by the cloud server through the TCP protocol stack.

Step S350 is: and in response to the fact that the IP report response is not received within the preset time, reporting the current IP address to a cloud server through the TCP protocol stack again.

Step S360 is: and in response to the fact that the sending times of the same current IP address exceed the preset number, giving up reporting of the current IP address to a cloud server.

Step S370 is: and continuing to enter a dormant state in response to receiving the IP report response.

While, for purposes of simplicity of explanation, the methodologies are shown and described as a series of acts, it is to be understood and appreciated that the methodologies are not limited by the order of acts, as some acts may, in accordance with one or more embodiments, occur in different orders and/or concurrently with other acts from that shown and described herein or not shown and described herein, as would be understood by one skilled in the art.

According to another aspect of the present invention, there is provided a computer storage medium, wherein the computer program is executed to implement the steps of the IP address reporting method for a vehicle side according to any one of the above.

According to a further aspect of the present invention, there is provided a computer storage medium, wherein when executed, the computer program implements the steps of the IP address obtaining method suitable for the cloud server according to any one of the above.

Those of skill in the art would understand that information, signals, and data may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits (bits), symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. 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 invention.

The various illustrative logical modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

In one or more exemplary embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software as a computer program product, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a web site, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk (disk) and disc (disc), as used herein, includes Compact Disc (CD), laser disc, optical disc, Digital Versatile Disc (DVD), floppy disk and blu-ray disc where disks (disks) usually reproduce data magnetically, while discs (discs) reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. It is to be understood that the scope of the invention is to be defined by the appended claims and not by the specific constructions and components of the embodiments illustrated above. Those skilled in the art can make various changes and modifications to the embodiments within the spirit and scope of the present invention, and these changes and modifications also fall within the scope of the present invention.

Claims

1. An in-vehicle smart computing device, comprising:

the network communication module comprises a TCP protocol stack to realize communication with a cloud server, acquires a current IP address of the vehicle-mounted intelligent computing device, judges whether the current IP address is the same as a previous IP address or not, and reports the current IP address to the cloud server through the TCP protocol stack in response to the fact that the current IP address is different from the previous IP address.

2. The vehicle-mounted intelligent computing device according to claim 1, wherein the network communication module receives an IP report response sent by the cloud server through the TCP protocol stack, and reports the current IP address to the cloud server again in response to not receiving the IP report response within a preset time.

3. The in-vehicle intelligent computing device of claim 2, wherein the network communication module abandons reporting the current IP address to a cloud server in response to the number of reporting times for the same current IP address exceeding a preset number.

4. The in-vehicle smart computing device of claim 2, wherein the network communication module periodically wakes itself up to obtain the current IP address of the in-vehicle smart computing device in response to the in-vehicle smart computing device being in a sleep state.

5. The in-vehicle intelligent computing device of claim 4, wherein the network communication module continues to enter a dormant state in response to receiving the IP report response.

6. The vehicle-mounted intelligent computing device according to claims 1-5, wherein the network communication module encrypts the current IP address with token information of the vehicle-mounted intelligent computing device to obtain an encrypted IP address and reports the encrypted IP address and the device ID of the vehicle-mounted intelligent computing device to the cloud server through the TCP protocol stack.

7. The in-vehicle smart computing device of claim 6, wherein the network communication module obtains up-to-date token information of the in-vehicle smart computing device as the token information of the in-vehicle smart computing device.

8. The in-vehicle smart computing device of claim 7, further comprising:

and the application module is coupled with the network communication module and the cloud server, requests the cloud server for obtaining token information and sends the token information obtained from the cloud server to the network communication module to serve as the latest token information.

9. The vehicle-mounted intelligent computing device according to claim 8, wherein the application module requests the cloud server for token information in response to first connecting to the cloud server or receiving an update token information instruction sent by the cloud server; or requesting to acquire token information from the cloud server at regular time.

10. An IP address reporting method of a vehicle-mounted intelligent computing device comprises the following steps:

acquiring a current IP address of the vehicle-mounted intelligent computing device;

judging whether the current IP address is the same as the previous IP address; and

and in response to the current IP address being different from the previous IP address, reporting the current IP address to a cloud server through a TCP protocol stack.

11. The IP address reporting method of claim 10, further comprising:

receiving an IP report response sent by a cloud server through the TCP protocol stack; and

and in response to the fact that the IP report response is not received within the preset time, reporting the current IP address to a cloud server through the TCP protocol stack again.

12. The IP address reporting method of claim 11, further comprising:

and in response to the fact that the sending times of the same current IP address exceed the preset number, giving up reporting of the current IP address to a cloud server.

13. The IP address reporting method of claim 11, wherein the obtaining the current IP address of the in-vehicle intelligent computing device comprises:

and responding to the fact that the vehicle-mounted intelligent computing device is in a dormant state, and periodically acquiring the current IP address of the vehicle-mounted intelligent computing device.

14. The IP address reporting method of claim 13, further comprising:

and continuing to enter a dormant state in response to receiving the IP report response.

15. The IP address reporting method according to any one of claims 10 to 14, wherein the reporting of the current IP address to the cloud server comprises:

encrypting the current IP address by adopting token information of the vehicle-mounted intelligent computing device to obtain an encrypted IP address; and

and reporting the encrypted IP address and the equipment ID of the vehicle-mounted intelligent computing device to a cloud server through the TCP protocol stack.

16. The IP address reporting method of claim 15, wherein the encrypting the current IP address using the token information of the in-vehicle intelligent computing device to obtain an encrypted IP address comprises:

obtaining the latest token information of the vehicle-mounted intelligent computing device as the token information of the vehicle-mounted intelligent computing device.

17. The IP address reporting method of claim 16, wherein the obtaining the latest token information of the in-vehicle intelligent computing device comprises:

requesting to acquire token information from the cloud server; and

and updating the token information acquired from the cloud server into the latest token information.

18. The IP address reporting method of claim 17, wherein the requesting token information from a cloud server comprises:

responding to a first connection of the cloud server or receiving a token information updating instruction sent by the cloud server, and requesting the cloud server to acquire token information; or

And requesting to acquire token information from the cloud server at regular time.

19. A computer storage medium having a computer program stored thereon, wherein the computer program when executed implements the steps of the IP address reporting method of any of claims 10-18.

20. A cloud server of a vehicle, comprising:

and the IP reporting interface is coupled with the vehicle-mounted intelligent computing device of each vehicle to receive the encrypted IP address reported by each vehicle-mounted intelligent computing device, and decrypts the encrypted IP address of each vehicle-mounted intelligent computing device by utilizing the token information of each vehicle-mounted intelligent computing device to obtain and update the current IP address of each vehicle-mounted intelligent computing device.

21. The cloud server of claim 20, wherein the cloud server stores a device ID of each in-vehicle smart computing device and its associated token information, the IP reporting interface receives an encrypted IP address of each in-vehicle smart computing device and its device ID, and the cloud server decrypts the encrypted IP address corresponding to the device ID by using the token information associated with each received device ID to obtain a current IP address of the in-vehicle smart computing device corresponding to the device ID and stores the current IP address in association with the received device ID.

22. The cloud server of claim 21, further comprising:

and the cloud server generates token information by adopting a random algorithm, stores the token information and the equipment ID of the vehicle-mounted intelligent computing device in a correlation manner, and feeds the generated token information back to the vehicle-mounted intelligent computing device corresponding to the associated equipment ID.

23. The cloud server of claim 20, wherein said cloud server is configured to send an update token information instruction to an in-vehicle smart computing device to cause said in-vehicle smart computing device to request token information from said token service interface in response to determining that token information of said in-vehicle smart computing device is leaked.

24. The cloud server of claim 20, wherein said cloud server feeds back an IP report response to an onboard smart computing device in response to receiving an encrypted IP address reported by said onboard smart computing device.

25. A vehicle IP address acquisition method includes:

receiving an encrypted IP address reported by each vehicle-mounted intelligent computing device; and

decrypting the encrypted IP address of each vehicle-mounted intelligent computing device by using the token information of the vehicle-mounted intelligent computing device to obtain and update the current IP address of the vehicle-mounted intelligent computing device.

26. The IP address acquisition method of claim 25,

the receiving an encrypted IP address of each in-vehicle intelligent computing device comprises:

receiving the encrypted IP address and the equipment ID of each vehicle-mounted intelligent computing device; and

the decrypting the encrypted IP address of each in-vehicle intelligent computing device with the token information of the in-vehicle intelligent computing device to obtain and store the current IP address of the in-vehicle intelligent computing device comprises:

decrypting the encrypted IP address corresponding to the equipment ID by utilizing the token information associated with each received equipment ID to obtain the current IP address of the vehicle-mounted intelligent computing device corresponding to the equipment ID; and

storing the current IP address in association with the received device ID.

27. The IP address acquisition method according to claim 25, further comprising:

responding to a request for acquiring token information of a vehicle-mounted intelligent computing device, and generating token information by adopting a random algorithm;

storing the token information in association with a device ID of the in-vehicle smart computing device; and

and feeding back the generated token information to the vehicle-mounted intelligent computing device corresponding to the associated equipment ID.

28. The IP address acquisition method according to claim 27, further comprising:

and in response to the judgment that the token information of the vehicle-mounted intelligent computing device leaks, sending a token information updating instruction to the vehicle-mounted intelligent computing device to enable the vehicle-mounted intelligent computing device to request to acquire the token information.

29. The IP address acquisition method according to claim 25, further comprising:

and feeding back an IP report response to the vehicle-mounted intelligent computing device in response to receiving the encrypted IP address reported by the vehicle-mounted intelligent computing device.

30. A computer storage medium having a computer program stored thereon, wherein the computer program when executed implements the steps of the IP address acquisition method of any of claims 25-29.