CN114327956A - Request processing method and device for vehicle-mounted application, electronic equipment and storage medium - Google Patents

Request processing method and device for vehicle-mounted application, electronic equipment and storage medium Download PDF

Info

Publication number
CN114327956A
CN114327956A CN202111681328.0A CN202111681328A CN114327956A CN 114327956 A CN114327956 A CN 114327956A CN 202111681328 A CN202111681328 A CN 202111681328A CN 114327956 A CN114327956 A CN 114327956A
Authority
CN
China
Prior art keywords
application
vehicle
party application
party
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.)
Withdrawn
Application number
CN202111681328.0A
Other languages
Chinese (zh)
Inventor
陆明亮
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Apollo Zhilian Beijing Technology Co Ltd
Original Assignee
Apollo Zhilian Beijing Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Apollo Zhilian Beijing Technology Co Ltd filed Critical Apollo Zhilian Beijing Technology Co Ltd
Priority to CN202111681328.0A priority Critical patent/CN114327956A/en
Publication of CN114327956A publication Critical patent/CN114327956A/en
Withdrawn legal-status Critical Current

Links

Images

Landscapes

  • Information Transfer Between Computers (AREA)

Abstract

The disclosure provides a request processing method, a request processing device, equipment and a storage medium for vehicle-mounted application, and relates to the technical field of computers, in particular to the technical field of car networking and intelligent cabins. The specific implementation scheme is as follows: sending a resource acquisition request to a third-party application by adopting a preset login token of the third-party application in the vehicle-mounted application; under the condition that the resource acquisition request fails, analyzing the error code of which the request fails to obtain an analysis result; and under the condition that the analysis result is that the login token is invalid, determining a target third-party application with the invalid token, and generating login authorization reminding information of the target third-party application to the vehicle-mounted application. The embodiment of the disclosure can improve the calling efficiency of the vehicle-mounted application to the third-party application.

Description

Request processing method and device for vehicle-mounted application, electronic equipment and storage medium
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method and an apparatus for processing a request of a vehicle-mounted application, an electronic device, and a computer-readable storage medium.
Background
With the development of vehicle-mounted scenes becoming faster and faster, the use requirements of vehicle-mounted applications become more and more abundant. The vehicle-mounted application can call the resource data of the third-party application, so that the third-party application is required to log in and authorize the vehicle-mounted application.
How the vehicle-mounted application obtains the login authorization of the third-party application belongs to an important problem in the industry.
Disclosure of Invention
The disclosure provides a request processing method and device for vehicle-mounted application, electronic equipment and a storage medium.
According to an aspect of the present disclosure, a method for processing a request of a vehicle-mounted application is provided, including:
sending a resource acquisition request to a third-party application by adopting a preset login token of the third-party application in the vehicle-mounted application;
under the condition that the resource acquisition request fails, analyzing the error code of which the request fails to obtain an analysis result;
and under the condition that the analysis result is that the login token is invalid, determining a target third-party application with the invalid token, and generating login authorization reminding information of the target third-party application to the vehicle-mounted application.
According to still another aspect of the present disclosure, there is provided a request processing apparatus of an in-vehicle application, including:
a request sending module for adopting a login token of a preset third-party application in the vehicle-mounted application,
sending a resource acquisition request to a third-party application;
the error analysis module is used for analyzing the error code with the failed request to obtain an analysis result under the condition that the resource acquisition request fails;
and the authorization reminding module is used for determining the target third-party application with the failed token and generating login authorization reminding information of the target third-party application to the vehicle-mounted application under the condition that the analysis result is that the login token is failed.
According to still another aspect of the present disclosure, there is provided an electronic device including:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the request processing method of the vehicle-mounted application provided by any embodiment of the disclosure.
According to yet another aspect of the present disclosure, there is provided a non-transitory computer-readable storage medium storing computer instructions for causing a computer to perform a request processing method for an in-vehicle application provided by any of the embodiments of the present disclosure.
According to yet another aspect of the present disclosure, there is provided a computer program product comprising a computer program which, when executed by a processor, implements a request processing method of an in-vehicle application provided by any of the embodiments of the present disclosure.
It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.
Drawings
The drawings are included to provide a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:
FIG. 1a is a schematic diagram of a request processing method for an in-vehicle application according to an embodiment of the present disclosure;
FIG. 1b is a schematic diagram of a call relationship of an in-vehicle application provided according to an embodiment of the present disclosure;
FIG. 2 is a schematic diagram of another request processing method for an in-vehicle application provided according to an embodiment of the disclosure;
FIG. 3 is a schematic diagram of a request processing method for another in-vehicle application provided according to an embodiment of the present disclosure;
FIG. 4 is a schematic diagram of a request processing device for an in-vehicle application provided in accordance with an embodiment of the present disclosure;
fig. 5 is a block diagram of an electronic device for implementing a request processing method of an in-vehicle application according to an embodiment of the present disclosure.
Detailed Description
Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which various details of the embodiments of the disclosure are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
The scheme provided by the embodiment of the disclosure is described in detail below with reference to the accompanying drawings.
Fig. 1a is a schematic diagram of a request processing method of an in-vehicle application according to an embodiment of the present disclosure, which is applicable to a case where the in-vehicle application calls resource data of a third-party application. The method can be executed by a request processing device of the vehicle-mounted application, the device can be realized in a hardware and/or software mode, and the device can be configured in the electronic equipment. Referring to fig. 1a, the method specifically includes the following:
s110, sending a resource acquisition request to a third-party application by adopting a preset login token of the third-party application in the vehicle-mounted application;
s120, under the condition that the resource acquisition request fails, analyzing the error code with the failed request to obtain an analysis result;
s130, under the condition that the analysis result is that the login token is invalid, determining the target third-party application with the invalid token, and generating login authorization reminding information of the target third-party application to the vehicle-mounted application.
In the embodiment of the disclosure, the in-vehicle application may be an application program adapted to an in-vehicle operating system, and is used for providing the in-vehicle service to the user in a specific scene. The vehicle-mounted application can call the resource data of the third-party application through the rear-end interface of the third-party application. Taking the vehicle-mounted application as the vehicle-mounted resource recommendation application as an example, the third-party application may be a third-party music application, a third-party movie application, or the like. The number of third-party applications is not specifically limited in the embodiment of the present disclosure, and fig. 1b is a schematic diagram of a call relationship of a vehicle-mounted application provided in the embodiment of the present disclosure, and referring to fig. 1b, the vehicle-mounted application may call at least two third-party applications.
The login token of the third-party application can be generated according to the historical login authorization operation of the third-party application on the vehicle-mounted application. The local database of the in-vehicle application client can store the login token of the third-party application. For example, when a user logs in a vehicle-mounted application client for the first time, whether a login token of a third-party application exists in the vehicle-mounted application can be detected, if not, the user can be reminded to log in the third-party application, the third-party application is applied for authorization of the vehicle-mounted application to obtain the login token of the third-party application, and the login token of the third-party application is stored in a local database of the vehicle-mounted application.
In the process of providing the vehicle-mounted service by the vehicle-mounted application, a preset login token of the third-party application in the vehicle-mounted application can be used for generating a resource acquisition request comprising the login token, and the resource acquisition request is sent to a rear-end interface of the third-party application. And if the resource acquisition request cannot acquire the third-party resource data, the resource acquisition request fails, and the vehicle-mounted application acquires the error code from the rear-end interface of the third-party application which fails to request. The vehicle-mounted application can analyze the error code of the request failure to obtain a request failure type as an analysis result.
And under the condition that the analysis result is that the login token is invalid, the vehicle-mounted application can also take the third-party application to which the login token with the invalid token belongs as the target third-party application with the invalid token, generate login authorization reminding information of the target third-party application to the vehicle-mounted application, remind a user of login authorization of the vehicle-mounted application by adopting the target third-party application, and enable the vehicle-mounted application to obtain the login token of the target third-party application again. The error code of the request failure is automatically utilized through the vehicle-mounted application, the failure of the login token of the third-party application is detected, the login authorization reminding information of the target third-party application to the vehicle-mounted application is automatically generated and used for reminding a user of performing login authorization on the vehicle-mounted application again through the target third-party application, and compared with the method that the error log is manually checked under the condition that the resource acquisition request fails, the calling efficiency of the vehicle-mounted application to the third-party application can be improved, and the use experience of the vehicle-mounted application is improved.
According to the technical scheme, whether the login token of the third-party application fails or not is automatically detected by the vehicle-mounted application, and under the condition that the login token fails, the target third-party application with the failed token is automatically reminded to log in and authorize the vehicle-mounted application again, manual error log troubleshooting is not needed, the calling efficiency of the vehicle-mounted application to the third-party application can be improved, and the use experience of the vehicle-mounted application is improved.
In an optional implementation manner, the generating the login authorization reminding information of the target third-party application to the in-vehicle application includes: generating login reminding information of the target third-party application in the vehicle-mounted application; and generating authorization application reminding information of the target third-party application to the vehicle-mounted application in the vehicle-mounted application.
And under the condition that the login token of the target third-party application is determined to be invalid, the vehicle-mounted application can remind the user to log in the target third-party application again, and the authorization of the target third-party application to the vehicle-mounted application is applied in the vehicle-mounted application again. Specifically, the vehicle-mounted application can display login reminding information of the target third-party application for reminding the user to log in again; the vehicle-mounted application can also display an authorization interface of the target third-party application, and the authorization interface is used for applying the authorization of the target third-party application to the vehicle-mounted application for the user, acquiring a new login token of the target third-party application under the condition that the user agrees to the authorization, and storing the new login token into a local database of the vehicle-mounted application. And by acquiring the new login token of the target third-party application, the vehicle-mounted application can conveniently continue to call the target third-party application.
Fig. 2 is a schematic diagram of another request processing method for an in-vehicle application provided according to an embodiment of the present disclosure. The present embodiment is an alternative proposed on the basis of the above-described embodiments. Referring to fig. 2, the method for processing a request of a vehicle-mounted application provided in this embodiment includes:
s210, sending a resource acquisition request to a third-party application by adopting a preset login token of the third-party application in the vehicle-mounted application;
s220, under the condition that the resource acquisition request fails, adopting an error code analysis rule preset in the vehicle-mounted application to analyze the error code which fails to request to obtain an analysis result;
and S230, under the condition that the analysis result is that the login token is invalid, determining the target third-party application with the invalid token, and generating login authorization reminding information of the target third-party application to the vehicle-mounted application.
The error code analysis rule may be predetermined, and the error code rule includes a preset association relationship between an error code and a request failure type, for example, the request failure type associated with the first error code is a login token failure, and the request failure type associated with the second error code is a signature failure. Specifically, the vehicle-mounted application may match the error code with which the request fails with an association relationship between a preset error code and the request failure type in the error code analysis rule, so as to obtain an associated request failure type. The error code failed in the request is automatically analyzed through the vehicle-mounted application based on the error code analysis rule, manual error log checking is not needed, the calling efficiency of the vehicle-mounted application to the third-party application is improved, and the labor cost is saved.
In an alternative embodiment, the determining the target third party application for which the token fails comprises: and determining a target third-party application with a failed token from the at least two candidate third-party applications according to the incidence relation between the at least two candidate third-party applications and the at least two candidate login tokens and the login token with the failed token carried in the resource acquisition request with the failed request.
And under the condition that the vehicle-mounted application can call at least two candidate third-party applications, the association relationship between the at least two candidate third-party applications and the at least two candidate login tokens is preset in the vehicle-mounted application. For example, the login token candidates 1, 2 and 3 of the third-party music application 1, 2 and 3 are preset in the vehicle-mounted application.
Specifically, the login token with the failed token may be matched with the at least two candidate third-party applications and the association relationship between the at least two candidate login tokens, the candidate login token successfully matched may be used as the target login token, and the candidate third-party application associated with the target login token may be used as the target third-party application. The vehicle-mounted application automatically positions the target third-party application with the failed login token, so that the calling efficiency of the vehicle-mounted application to the third-party application is improved and the labor cost is saved compared with the manual positioning of the target third-party application.
It should be noted that, after analyzing the error code that fails to request to obtain an analysis result, the method further includes: and under the condition that the signature is invalid according to the analysis result, determining a third-party application with the invalid signature, and updating the signature key of the third-party application in the vehicle-mounted application.
Specifically, under the condition that the signature is invalid, the vehicle-mounted application may obtain a signature key of the third-party application from the third-party application server side with the invalid signature, and use the signature key to perform the signature again. The signature key of the third-party application may be a public signature key of an asymmetric signature key pair of the third-party application. And the signature private key in the asymmetric signature key pair is only stored in the third-party application server and is used for verifying the signature of the vehicle-mounted application. Under the condition that the signature is invalid, the vehicle-mounted application automatically updates the signature key of the third-party application, and the call success rate of the third-party application can be improved.
In an optional implementation manner, after sending the resource obtaining request to the third-party application, the method further includes: under the condition that the resource acquisition request is successful, acquiring resource data returned by the third-party application; and displaying the resource data in the vehicle-mounted application.
And under the condition that the resource acquisition request is successful, the vehicle-mounted application acquires and displays the resource data from the third-party application, so that the third-party resource use requirement of the vehicle-mounted user can be met. Still taking the vehicle-mounted application as the vehicle-mounted resource recommendation application as an example, the third-party application includes a third-party music application and a third-party movie application as an example, the vehicle-mounted application may actively recommend music resource data acquired from the third-party music application and power resource data acquired from the third-party power application to the user. The vehicle-mounted application can also perform processing such as sorting and screening on the resource data of the third-party application, and display the third-party resource according to the processing result, so that the matching degree between the resource recommendation result and the vehicle-mounted user is improved, and the user experience is further improved.
According to the technical scheme of the embodiment, the manual log checking and the process of reminding the client of logging in again and authorization are changed into automatic reminding through the error code fed back by the third-party application, the calling efficiency of the vehicle-mounted application to the third-party application is improved, and the labor cost is saved. In addition, the vehicle-mounted application also supports automatic updating of the signature key of the third-party application, and the calling success rate of the third-party application is improved.
In an alternative embodiment, the method further comprises: detecting whether the signature of a third-party application in the vehicle-mounted application is invalid; and in the case of signature failure, determining a third-party application with the failed signature, and updating the signature key of the third-party application in the vehicle-mounted application.
In the embodiment of the disclosure, the vehicle-mounted application may update the signing key of the third-party application not only in the calling process of the third-party application, but also actively update the signing key of the third-party application independent of the calling process of the third-party application, for example, the signing key of the third-party application may also be updated regularly from the third-party application server. By updating the signature key, the calling failure of the third-party application caused by the failure of the signature key is avoided, and the calling success of the third-party application is further improved. The updating of the signature key can carry out silent processing on the vehicle-mounted user, and the use experience of the user is prevented from being influenced.
Fig. 3 is a schematic diagram of another request processing method for an in-vehicle application provided according to an embodiment of the present disclosure. The present embodiment is an alternative proposed on the basis of the above-described embodiments. Referring to fig. 3, the method for processing a request of an in-vehicle application provided in this embodiment includes:
s310, adopting login tokens of at least two candidate third-party applications preset in the vehicle-mounted application, and respectively sending resource acquisition requests to the at least two candidate third-party applications;
if any resource acquisition request fails, continuing to execute S320; skipping execution S350 under the condition that at least one resource acquisition request is successful;
s320, analyzing the error code failing to request by adopting the error code analysis rule preset in the vehicle-mounted application to obtain an analysis result;
if the analysis result is that the login token is invalid, continuing to execute S330; if the analysis result is that the signature is invalid, skipping execution S340;
s330, determining a target third-party application with a failed token, and generating login authorization reminding information of the target third-party application to the vehicle-mounted application;
s340, determining a third party application with a signature failure, and updating a signature key of the third party application in the vehicle-mounted application;
s350, resource data returned by the candidate third-party applications are obtained;
and S360, displaying the resource data in the vehicle-mounted application.
Under the condition that the vehicle-mounted application has at least two candidate third-party applications, aiming at each candidate third-party application, the vehicle-mounted application can adopt a preset login token of the candidate third-party application to send a resource acquisition request to the candidate third-party application; in the case of a failure of the resource acquisition request, the candidate third-party application may return an error code for the failure of the request; in the event that the resource acquisition request is successful, the candidate third party application may return resource data.
For a failed request, the vehicle-mounted application can automatically analyze an error code of the request failure and determine a request failure type. And under the condition that the request failure type is the failure of the login token, automatically generating login authorization reminding information for the vehicle-mounted application for the third-party application with the failed login token, and reminding the user to adopt the third-party application again to perform login authorization on the vehicle-mounted application. In the event that the request failure type is signature failure, the signature key of the third party application may be automatically updated.
Under the condition that at least one resource acquisition request is successful, the vehicle-mounted application can acquire third-party resource data from the third-party application which successfully requests, and display the third-party resource data, so that the third-party resource use requirement of a vehicle-mounted user is met.
According to the technical scheme of the embodiment, under the condition that the vehicle-mounted application fails to call any candidate third-party application, the error code returned by the candidate third-party application can be automatically analyzed, the user can be actively reminded to log in the third-party application again under the condition that the login token is detected to be invalid, and the login token authorized by the third-party application is obtained again in the vehicle-mounted application. User experience of the vehicle-mounted application can be improved, labor cost for error log troubleshooting is reduced, and calling efficiency of the vehicle-mounted application to the third-party application is improved.
Fig. 4 is a schematic diagram of a request processing apparatus for an in-vehicle application according to an embodiment of the present disclosure, where the embodiment is applicable to a case where the in-vehicle application calls resource data of a third-party application, and the apparatus is configured in an electronic device, and can implement a request processing method for the in-vehicle application according to any embodiment of the present disclosure. Referring to fig. 4, the request processing device 400 of the in-vehicle application specifically includes the following:
a request sending module 410, configured to send a resource obtaining request to a third-party application by using a login token of the third-party application preset in the vehicle-mounted application;
an error analysis module 420, configured to, in a case that the resource acquisition request fails, analyze an error code that fails to request to obtain an analysis result;
and the authorization reminding module 430 is configured to determine a target third-party application with a failed token and generate login authorization reminding information of the target third-party application to the vehicle-mounted application, when the analysis result is that the login token is failed.
In an optional implementation manner, the error resolution module 420 is specifically configured to:
and analyzing the error code failing to request by adopting the error code analysis rule preset in the vehicle-mounted application to obtain an analysis result.
In an optional implementation manner, the authorization reminding module 430 is specifically configured to:
and determining a target third-party application with a failed token from the at least two candidate third-party applications according to the incidence relation between the at least two candidate third-party applications and the at least two candidate login tokens and the login token with the failed token carried in the resource acquisition request with the failed request.
In an alternative embodiment, the authorization reminding module 430 includes:
the login reminding unit is used for generating login reminding information of the target third-party application in the vehicle-mounted application;
and the authorization application unit is used for generating authorization application reminding information of the target third-party application to the vehicle-mounted application in the vehicle-mounted application.
In an optional implementation manner, the request processing device 400 of the in-vehicle application further includes a resource presentation module, where the resource presentation module includes:
the resource acquisition unit is used for acquiring resource data returned by the third-party application under the condition that the resource acquisition request is successful;
and the resource display unit is used for displaying the resource data in the vehicle-mounted application.
In an optional implementation manner, the request processing device 400 of the in-vehicle application further includes a signing key updating module, which includes:
the signature detection unit is used for detecting whether the signature of the third-party application in the vehicle-mounted application is invalid or not;
and the signature key updating unit is used for determining the third-party application with the signature failure under the condition that the signature fails, and updating the signature key of the third-party application in the vehicle-mounted application.
According to the technical scheme, the error code returned by the third-party application with the failed request is utilized, the process of manually checking the error log and reminding re-login and authorization is changed into automatic reminding, the calling efficiency of the vehicle-mounted application to the third-party application is improved, the user embodiment is improved, and the labor cost is saved.
In the technical scheme of the disclosure, the acquisition, storage, application and the like of the personal information of the related user all accord with the regulations of related laws and regulations, and do not violate the good customs of the public order.
The present disclosure also provides an electronic device, a readable storage medium, and a computer program product according to embodiments of the present disclosure.
FIG. 5 illustrates a schematic block diagram of an example electronic device 500 that can be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the disclosure described and/or claimed herein.
As shown in fig. 5, the apparatus 500 comprises a computing unit 501 which may perform various appropriate actions and processes in accordance with a computer program stored in a Read Only Memory (ROM)502 or a computer program loaded from a storage unit 508 into a Random Access Memory (RAM) 503. In the RAM 503, various programs and data required for the operation of the device 500 can also be stored. The calculation unit 501, the ROM 502, and the RAM 503 are connected to each other by a bus 504. An input/output (I/O) interface 505 is also connected to bus 504.
A number of components in the device 500 are connected to the I/O interface 505, including: an input unit 506 such as a keyboard, a mouse, or the like; an output unit 507 such as various types of displays, speakers, and the like; a storage unit 508, such as a magnetic disk, optical disk, or the like; and a communication unit 509 such as a network card, modem, wireless communication transceiver, etc. The communication unit 509 allows the device 500 to exchange information/data with other devices through a computer network such as the internet and/or various telecommunication networks.
The computing unit 501 may be a variety of general-purpose and/or special-purpose processing components having processing and computing capabilities. Some examples of the computing unit 501 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various computing units that perform machine learning model algorithms, a digital information processor (DSP), and any suitable processor, controller, microcontroller, and so forth. The calculation unit 501 executes the respective methods and processes described above, such as the request processing method of the in-vehicle application. For example, in some embodiments, the request processing method of the in-vehicle application may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as storage unit 508. In some embodiments, part or all of the computer program may be loaded and/or installed onto the device 500 via the ROM 502 and/or the communication unit 509. When the computer program is loaded into the RAM 503 and executed by the computing unit 501, one or more steps of the request processing method of the in-vehicle application described above may be performed. Alternatively, in other embodiments, the computing unit 501 may be configured in any other suitable way (e.g., by means of firmware) to execute the request processing method of the in-vehicle application.
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), system on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), blockchain networks, and the internet.
The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs executing on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical host and VPS service are overcome.
It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present disclosure may be executed in parallel, sequentially, or in different orders, as long as the desired results of the technical solutions disclosed in the present disclosure can be achieved, and the present disclosure is not limited herein.
The above detailed description should not be construed as limiting the scope of the disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present disclosure should be included in the scope of protection of the present disclosure.

Claims (15)

1. A request processing method of an in-vehicle application comprises the following steps:
sending a resource acquisition request to a third-party application by adopting a preset login token of the third-party application in the vehicle-mounted application;
under the condition that the resource acquisition request fails, analyzing the error code of which the request fails to obtain an analysis result;
and under the condition that the analysis result is that the login token is invalid, determining a target third-party application with the invalid token, and generating login authorization reminding information of the target third-party application to the vehicle-mounted application.
2. The method of claim 1, wherein the parsing the error code that fails to request to obtain a parsing result comprises:
and analyzing the error code failing to request by adopting the error code analysis rule preset in the vehicle-mounted application to obtain an analysis result.
3. The method of claim 1, wherein the determining the target third party application for which the token failed comprises:
and determining a target third-party application with a failed token from the at least two candidate third-party applications according to the incidence relation between the at least two candidate third-party applications and the at least two candidate login tokens and the login token with the failed token carried in the resource acquisition request with the failed request.
4. The method of claim 1, wherein the generating of the login authorization reminding information of the target third-party application to the in-vehicle application comprises:
generating login reminding information of the target third-party application in the vehicle-mounted application;
and generating authorization application reminding information of the target third-party application to the vehicle-mounted application in the vehicle-mounted application.
5. The method of claim 1, after sending the resource acquisition request to the third-party application, further comprising:
under the condition that the resource acquisition request is successful, acquiring resource data returned by the third-party application;
and displaying the resource data in the vehicle-mounted application.
6. The method of claim 1, further comprising:
detecting whether the signature of a third-party application in the vehicle-mounted application is invalid;
and in the case of signature failure, determining a third-party application with the failed signature, and updating the signature key of the third-party application in the vehicle-mounted application.
7. A request processing apparatus of an in-vehicle application, comprising:
the request sending module is used for sending a resource obtaining request to a third-party application by adopting a preset login token of the third-party application in the vehicle-mounted application;
the error analysis module is used for analyzing the error code with the failed request to obtain an analysis result under the condition that the resource acquisition request fails;
and the authorization reminding module is used for determining the target third-party application with the failed token and generating login authorization reminding information of the target third-party application to the vehicle-mounted application under the condition that the analysis result is that the login token is failed.
8. The apparatus of claim 7, wherein the error resolution module is specifically configured to:
and analyzing the error code failing to request by adopting the error code analysis rule preset in the vehicle-mounted application to obtain an analysis result.
9. The device of claim 7, wherein the authorization reminding module is specifically configured to:
and determining a target third-party application with a failed token from the at least two candidate third-party applications according to the incidence relation between the at least two candidate third-party applications and the at least two candidate login tokens and the login token with the failed token carried in the resource acquisition request with the failed request.
10. The apparatus of claim 7, wherein the authorization alert module comprises:
the login reminding unit is used for generating login reminding information of the target third-party application in the vehicle-mounted application;
and the authorization application unit is used for generating authorization application reminding information of the target third-party application to the vehicle-mounted application in the vehicle-mounted application.
11. The apparatus of claim 7, the apparatus further comprising a resource presentation module, the resource presentation module comprising:
the resource acquisition unit is used for acquiring resource data returned by the third-party application under the condition that the resource acquisition request is successful;
and the resource display unit is used for displaying the resource data in the vehicle-mounted application.
12. The apparatus of claim 7, the apparatus further comprising a signing rekeying module, the signing rekeying module comprising:
the signature detection unit is used for detecting whether the signature of the third-party application in the vehicle-mounted application is invalid or not;
and the signature key updating unit is used for determining the third-party application with the signature failure under the condition that the signature fails, and updating the signature key of the third-party application in the vehicle-mounted application.
13. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-6.
14. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 1-6.
15. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of claims 1-6.
CN202111681328.0A 2021-12-28 2021-12-28 Request processing method and device for vehicle-mounted application, electronic equipment and storage medium Withdrawn CN114327956A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111681328.0A CN114327956A (en) 2021-12-28 2021-12-28 Request processing method and device for vehicle-mounted application, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111681328.0A CN114327956A (en) 2021-12-28 2021-12-28 Request processing method and device for vehicle-mounted application, electronic equipment and storage medium

Publications (1)

Publication Number Publication Date
CN114327956A true CN114327956A (en) 2022-04-12

Family

ID=81022203

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111681328.0A Withdrawn CN114327956A (en) 2021-12-28 2021-12-28 Request processing method and device for vehicle-mounted application, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN114327956A (en)

Citations (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106209749A (en) * 2015-05-08 2016-12-07 阿里巴巴集团控股有限公司 Single-point logging method and the processing method and processing device of device, relevant device and application
CN106230838A (en) * 2016-08-04 2016-12-14 ***股份有限公司 A kind of third-party application accesses the method and apparatus of resource
CN106603528A (en) * 2016-12-13 2017-04-26 北京小米移动软件有限公司 Method and apparatus for webpage invoking terminal local functions
CN107358089A (en) * 2017-06-30 2017-11-17 北京小米移动软件有限公司 Call the method and device of termination function
US20170366547A1 (en) * 2015-06-02 2017-12-21 ALTR Solutions, Inc. Remotely deauthenticating a user from a web-based application using a centralized login server
CN108810006A (en) * 2018-06-25 2018-11-13 百度在线网络技术(北京)有限公司 resource access method, device, equipment and storage medium
CN109309683A (en) * 2018-10-30 2019-02-05 泰华智慧产业集团股份有限公司 The method and system of client identity verifying based on token
CN110730171A (en) * 2019-10-10 2020-01-24 北京东软望海科技有限公司 Service request processing method, device and system, electronic equipment and storage medium
CN111600899A (en) * 2020-05-25 2020-08-28 华人运通(上海)云计算科技有限公司 Micro-service access control method and device, electronic equipment and storage medium
CN112733107A (en) * 2021-04-02 2021-04-30 腾讯科技(深圳)有限公司 Information verification method, related device, equipment and storage medium
CN113553572A (en) * 2021-07-02 2021-10-26 深圳追一科技有限公司 Resource information acquisition method and device, computer equipment and storage medium
CN113572718A (en) * 2020-04-29 2021-10-29 华为技术有限公司 Login method, login device, electronic equipment and storage medium

Patent Citations (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106209749A (en) * 2015-05-08 2016-12-07 阿里巴巴集团控股有限公司 Single-point logging method and the processing method and processing device of device, relevant device and application
US20170366547A1 (en) * 2015-06-02 2017-12-21 ALTR Solutions, Inc. Remotely deauthenticating a user from a web-based application using a centralized login server
CN106230838A (en) * 2016-08-04 2016-12-14 ***股份有限公司 A kind of third-party application accesses the method and apparatus of resource
CN106603528A (en) * 2016-12-13 2017-04-26 北京小米移动软件有限公司 Method and apparatus for webpage invoking terminal local functions
CN107358089A (en) * 2017-06-30 2017-11-17 北京小米移动软件有限公司 Call the method and device of termination function
CN108810006A (en) * 2018-06-25 2018-11-13 百度在线网络技术(北京)有限公司 resource access method, device, equipment and storage medium
CN109309683A (en) * 2018-10-30 2019-02-05 泰华智慧产业集团股份有限公司 The method and system of client identity verifying based on token
CN110730171A (en) * 2019-10-10 2020-01-24 北京东软望海科技有限公司 Service request processing method, device and system, electronic equipment and storage medium
CN113572718A (en) * 2020-04-29 2021-10-29 华为技术有限公司 Login method, login device, electronic equipment and storage medium
CN111600899A (en) * 2020-05-25 2020-08-28 华人运通(上海)云计算科技有限公司 Micro-service access control method and device, electronic equipment and storage medium
CN112733107A (en) * 2021-04-02 2021-04-30 腾讯科技(深圳)有限公司 Information verification method, related device, equipment and storage medium
CN113553572A (en) * 2021-07-02 2021-10-26 深圳追一科技有限公司 Resource information acquisition method and device, computer equipment and storage medium

Similar Documents

Publication Publication Date Title
CN114328132A (en) Method, device, equipment and medium for monitoring state of external data source
CN114389969A (en) Client test method and device, electronic equipment and storage medium
CN114036248A (en) High-precision map data processing method and device and electronic equipment
CN111367934B (en) Data consistency checking method, device, server and medium
CN114138397B (en) Page display method and device, electronic equipment and storage medium
CN114327956A (en) Request processing method and device for vehicle-mounted application, electronic equipment and storage medium
CN114091909A (en) Collaborative development method, system, device and electronic equipment
CN114218313A (en) Data management method, device, electronic equipment, storage medium and product
CN114371863A (en) Data processing method and device, electronic equipment and computer readable storage medium
CN114218166A (en) Data processing method and device, electronic equipment and readable storage medium
CN114003497A (en) Method, device and equipment for testing service system and storage medium
CN114116688A (en) Data processing and data quality inspection method, device and readable storage medium
CN113836291B (en) Data processing method, device, equipment and storage medium
CN114996119B (en) Fault diagnosis method, fault diagnosis device, electronic device and storage medium
CN115190008B (en) Fault processing method, fault processing device, electronic equipment and storage medium
CN114610511A (en) Input verification method and device, electronic equipment and storage medium
CN115309717A (en) Database loading method, device, equipment, medium and computer program product
CN116226867A (en) Script processing method, device, equipment and medium
CN117453747A (en) Data quality detection method and device, electronic equipment and storage medium
CN113327133A (en) Data recommendation method, data recommendation device, electronic equipment and readable storage medium
CN115080205A (en) Task execution method and device, electronic equipment and readable storage medium
CN114238149A (en) Batch testing method of accounting system, electronic device and storage medium
CN118171676A (en) Graphic code generation and storage method, device, equipment, medium and product
CN114328224A (en) Method and device for reproducing exception request, electronic equipment and storage medium
CN117670236A (en) Mobile-terminal-based to-be-handled flow approval method, device, equipment and 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
WW01 Invention patent application withdrawn after publication

Application publication date: 20220412

WW01 Invention patent application withdrawn after publication