WO2021120678A1

WO2021120678A1 - Software management method, apparatus and system

Info

Publication number: WO2021120678A1
Application number: PCT/CN2020/111485
Authority: WO
Inventors: 朱锦涛
Original assignee: 华为技术有限公司
Priority date: 2019-12-19
Filing date: 2020-08-26
Publication date: 2021-06-24
Also published as: CN113010893A

Abstract

Provided are a software management method, apparatus and system, wherein same can be applied to fields such as the Internet of Vehicles, intelligent driving and intelligent connected vehicles. The method comprises: after a first terminal receives a management notification message, the first terminal being able to determine an authentication terminal according to a management policy corresponding to first software, and authenticating, by means of the authentication terminal, a user who confirms the management of the first software; and when it is determined that the user is a user authorized to manage the first software, and a first confirmation instruction input by the user is acquired and a second conformation instruction from a second terminal is received, executing a management operation, which is indicated by the management notification message, on the first software. According to the method, a first terminal and a second terminal simultaneously authenticate a user, such that an illegitimate user can be prevented from unauthorized management of first software in the first terminal, thereby realizing management and control over the authorization of the updating of the first software and improving the security of the first terminal.

Description

Software management method, device and system

Cross-references to related applications

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office, the application number is 201911318704.2, and the application name is "a software management method, device and system" on December 19, 2019. The entire content is incorporated herein by reference. Applying.

Technical field

This application relates to the technical field of Internet of Vehicles, and in particular to a software management method, device and system.

Background technique

With the continuous development of the automobile industry and the deepening of the electrification, intelligence, networking and sharing of automobiles, the software functions of automobiles themselves are becoming more and more complex. Compared with the car's hardware, the car's software is updated faster. Therefore, the errors caused by the software update will increase day by day, which brings great risks to the safe driving of the car.

At present, over-the-air programming (OTA) technology is generally used to perform management operations such as installing, updating, and uninstalling software in a car through a remote wireless manner. Take updating software as an example. Due to the very high requirements of automobile safety, updating the software in the automobile is quite different from ordinary software updating. Specifically, according to current industry standards and relevant legal frameworks, before the software in the car is updated, the user needs to be notified of the relevant update operation, and the relevant update execution operation should also be authorized by the user. Therefore, using OTA technology to update the software in the car is a process that requires user participation. In this process, it is necessary to ensure that the entire software update process has been reasonably authorized by legitimate users.

However, in the current management operation process of installing, updating and uninstalling the software in the vehicle, it is easy for unauthorized users to perform management operations on the software, which leads to problems such as unauthorized installation, update and uninstallation of the software in the vehicle. As a result, the car cannot run normally. These problems are extremely dangerous to the car in motion.

To sum up, in the prior art, due to the lack of authorization control of software management in the process of using OTA technology to manage the software in the car, it leads to improper upgrade or upgrade accidents, which will seriously affect the safe driving or normal driving of the car. .

Summary of the invention

The embodiments of the present application provide a software management method, device, and system to solve how to perform authorization management and control in the process of software management, so as to avoid security problems due to software management.

In a first aspect, an embodiment of the present application provides a software management method. The method includes: a first terminal receives a management notification message; the management notification message is used to notify a management operation of the first software; and the management operation includes updating the software. Any one of the first software, installing the first software, and uninstalling the first software; the first terminal determines according to the management policy corresponding to the first software that the authentication terminal includes the first terminal and the first software In the case of the second terminal, the user who confirms the management of the first software is authenticated through the authentication terminal; when it is determined that the user is an authorized user who manages the first software, and the first confirmation instruction input by the user is obtained , And when receiving a second confirmation instruction from the second terminal, the first terminal executes the management notification message instruction on the first software according to the first confirmation instruction and the second confirmation instruction The management operation; wherein the first confirmation instruction is used to instruct the user to confirm the execution of the management operation on the first software through the first terminal.

Through the above method, before performing the management operation on the first software in the first terminal, the first terminal and the second terminal simultaneously determine whether the user is an authorized user. When both the first terminal and the second terminal determine that the user is When the user is authorized, the first terminal can manage the first software. In this way, it is possible to prevent unauthorized users from unauthorized management of the first software in the first terminal, realize management authorization management and control of the first software, and avoid security problems of the first terminal due to software management.

In a possible implementation manner, the management policy includes first information, and the first information is used to indicate the authentication terminal; the first terminal determines that the authentication terminal includes all the authentication terminals according to the management policy corresponding to the first software. The first terminal and the second terminal include: the first terminal determines that the authentication terminal includes the first terminal and the first terminal according to the first information in the management policy corresponding to the first software Two terminal.

In a possible implementation manner, the management policy includes second information, and the second information is used to indicate the authorization mode of the first software; Before certification, it also includes:

The first terminal determines the authorization mode of the first software according to the second information in the management policy; the first terminal determines according to the authorization mode that the user needs to be authenticated by the authentication terminal .

In a possible implementation manner, the authorization mode includes a first mode and a second mode, and the first mode is that each management operation of the first software requires the authentication terminal to perform the authentication on the user. Authentication; the second mode is that the first management operation of the first software needs to authenticate the user through the authentication terminal, and the management operation after the first management operation of the first software does not need to pass The authentication terminal authenticates the user; before the first terminal authenticates the user confirming the management of the first software through the authentication terminal, the method further includes: when it is determined that the authorization mode of the first software is all In the first mode, or when it is determined that the authorization mode of the first software is the second mode, and the first software is the first management operation, it is determined that the user needs to be authenticated through the authentication terminal.

In a possible implementation manner, the method further includes: the first terminal obtains the first authorization information input by the user in the first terminal, and obtains the second authorization information from the second terminal The first authorization information includes the authentication information entered by the user to the first terminal, and the second authorization information includes the authentication information entered by the user to the second terminal; when the first authorization information When it matches the authorization information pre-configured in the first terminal, and the first authorization information or the pre-configured authorization information matches the second authorization information, the first terminal determines that the user Is the authorized user.

In a possible implementation manner, the management policy includes third information, and the third information is used to indicate the authorized user; the first terminal confirms the user who manages the first software through the authentication terminal Before performing the authentication, the method further includes: the first terminal determines the authorized user according to the third information in the management policy.

In a possible implementation manner, before the first terminal receives the management notification message, the method further includes: the first terminal obtains the management policy set by the authorized user, and sends the management policy to the network device Or the first terminal receives the management policy from the network device.

In a possible implementation manner, the first terminal is a vehicle-mounted terminal, and the second terminal is a mobile terminal.

In the second aspect, the present application also provides a communication device that has any method provided in the first aspect. The communication device can be implemented by hardware, or can be implemented by hardware executing corresponding software. The hardware or software includes one or more units or units corresponding to the above-mentioned functions. The communication device may be a vehicle.

In a possible implementation manner, the communication device includes a processor configured to support the communication device to perform the corresponding function of the first terminal in the above-mentioned method. The communication device may further include a memory, and the storage may be coupled with the processor, which stores program instructions and data necessary for the communication device. Optionally, the communication device further includes a communication interface, and the communication interface is used to support communication between the communication device and the second terminal, network equipment and other devices.

In a possible implementation manner, the communication device includes corresponding functional units, which are respectively used to implement the steps in the above method. The function can be realized by hardware, or the corresponding software can be executed by hardware. The hardware or software includes one or more units corresponding to the above-mentioned functions.

In a possible implementation manner, the structure of the communication device includes a processing unit and a communication unit, and these units can perform corresponding functions in the foregoing method examples. For details, refer to the description of the method provided in the third aspect, which is not repeated here.

In a third aspect, a software management method is provided, including: a second terminal receives the management notification message; the management notification message is used to notify a management operation of the first software; the management operation includes updating the first software , Install the first software, uninstall any one of the first software; when the second terminal determines that the authentication terminal includes the second terminal according to the management policy corresponding to the first software, confirm the management office The user of the first software is authenticated;

When it is determined that the user is an authorized user who manages the first software, the second terminal sends a second confirmation instruction input by the user to the first terminal, and the second confirmation instruction is used to instruct the user to pass The second terminal confirms that the management operation indicated by the management notification message is performed on the first software.

In a possible implementation manner, the determining, by the second terminal, that the user is an authorized user who manages the first software includes: the second terminal acquiring the second input by the user in the second terminal Authorization information; the second authorization information includes the authentication information input by the user to the second terminal; when the first authorization information matches the authorization information pre-configured in the second terminal, the first authorization information The second terminal determines that the user is the authorized user who manages the first software.

In a possible implementation manner, the method further includes: the second terminal obtains the management policy set by the authorized user, and sends the management policy to the network device; or the second terminal receives The management policy from the network device.

In a possible implementation manner, the second terminal determining that the user is an authorized user to update the first software includes: the second terminal obtains second authorization information; the second authorization information includes the The authentication information entered by the user into the second terminal; when it is determined that the second authorization information matches the authorization information pre-configured in the second terminal, the second terminal determines that the user is the authorized user .

In a possible implementation manner, the management policy includes first information, and the first information is used to indicate the authentication terminal; and the second terminal determines the The authentication terminal is the second terminal.

In a possible implementation manner, the management policy includes third information, and the third information is used to indicate the authorized user; the method further includes: the second terminal according to the management policy The third information determines the authorized user.

In a fourth aspect, the present application also provides a communication device having any method provided in the third aspect. The communication device can be implemented by hardware, or can be implemented by hardware executing corresponding software. The hardware or software includes one or more units or units corresponding to the above-mentioned functions.

In a possible implementation manner, the communication device includes a processor configured to support the communication device to perform the corresponding function of the second terminal in the method shown above. The communication device may further include a memory, and the storage may be coupled with the processor, which stores program instructions and data necessary for the communication device. Optionally, the communication device further includes a communication interface, and the communication interface is used to support communication between the communication device and the first terminal, network equipment and other devices.

In a fifth aspect, a software management method is provided, which includes: when it is determined to perform a management operation on the first software, the network device determines an authentication terminal according to a management policy corresponding to the first software, and the authentication terminal is used to confirm the management office. The user of the first software is authenticated; the authentication terminal includes a first terminal and a second terminal; the management operation includes updating the first software, installing the first software, and uninstalling any of the first software. One item

The network device sends a management notification message to the authentication terminal, where the management notification message is used to notify the first software to perform the management operation.

In a possible implementation manner, before the determining to perform a management operation on the first software, the method further includes:

The network device sends the management policy to the first terminal and the second terminal; or the network device receives the management policy from the first terminal or the second terminal.

In a possible implementation manner, the management policy includes first information, and the first information is used to indicate the authentication terminal; the network device determines the authentication terminal according to the management policy corresponding to the first software, including: The network device determines the authentication terminal according to the first information in the management policy.

In a possible implementation manner, the management policy includes first information, and the first information is used to indicate the authentication terminal; the network device determines the authentication according to the first information in the management policy terminal.

In a sixth aspect, the present application also provides a communication device that has any method provided in the fifth aspect. The communication device can be implemented by hardware, or can be implemented by hardware executing corresponding software. The hardware or software includes one or more units or units corresponding to the above-mentioned functions.

In a possible implementation manner, the communication device includes a processor configured to support the communication device to perform the corresponding function of the network device in the method shown above. The communication device may further include a memory, and the storage may be coupled with the processor, which stores program instructions and data necessary for the communication device. Optionally, the communication device further includes a communication interface, and the communication interface is used to support communication between the communication device and the first terminal, the second terminal, and other devices.

In a seventh aspect, the present application provides a system that includes: a network device, configured to determine an authentication terminal according to a management policy corresponding to the first software when determining to perform management operations on the first software, and the authentication terminal is used to confirm The user who manages the first software is authenticated; the authentication terminal includes a first terminal and a second terminal; and a management notification message is sent to the authentication terminal, and the management notification message is used to notify the first software to perform the authentication. The management operation; the management operation includes any one of updating the first software, installing the first software, and uninstalling the first software;

The second terminal is configured to receive the management notification message; when it is determined that the authentication terminal includes the second terminal according to the management policy corresponding to the first software, authenticate the user who confirms the management of the first software; when When it is determined that the user is an authorized user who manages the first software, a second confirmation instruction input by the user is sent to the first terminal, where the second confirmation instruction is used to instruct the user to pass the second The terminal confirms that the management operation indicated by the management notification message is performed on the first software;

The first terminal is configured to receive the management notification message; when it is determined that the authentication terminal includes the first terminal and the second terminal according to the management policy corresponding to the first software, the authentication terminal is used to confirm management The user of the first software is authenticated; when it is determined that the user is an authorized user who manages the first software, and the first confirmation instruction input by the user is obtained, and the first confirmation instruction from the second terminal is received 2. When confirming the instruction, perform the management operation indicated by the management notification message on the first software according to the first confirmation instruction and the second confirmation instruction; wherein, the first confirmation instruction is used to instruct all The user confirms the execution of the management operation on the first software through the first terminal.

Through the above system, before the first software in the first terminal is updated, the first terminal and the second terminal simultaneously determine whether the user is an authorized user. When both the first terminal and the second terminal determine that the user is an authorized user , The first terminal can manage the first software. In this way, it is possible to prevent unauthorized users from unauthorized management of the first software in the first terminal, realize management authorization management and control of the first software, and avoid security problems of the first terminal due to software management.

In a possible implementation manner, the management policy includes first information, and the first information is used to indicate the authentication terminal; the determining the authentication terminal according to the management policy corresponding to the first software includes: The first information in the management policy determines the authentication terminal.

In a possible implementation manner, the management policy includes second information, and the second information is used to indicate the authorization mode of the first software; the first terminal confirms the user who manages the first software Before performing authentication, the method further includes: determining an authorization mode of the first software according to the second information in the management policy; and determining, according to the authorization mode, that the user needs to be authenticated by the authentication terminal.

In a possible implementation manner, the authorization mode includes a first mode and a second mode, and the first mode is that each management operation of the first software requires the authentication terminal to authenticate the user. To be certified;

The second mode is that the first management operation of the first software needs to authenticate the user through the authentication terminal, and the management operations after the first management operation of the first software do not need to pass the The authentication terminal authenticates the user; the first terminal is specifically configured to: when determining that the authorization mode of the first software is the first mode, or determining that the authorization mode of the first software is the second mode, And when the first software is the first management operation, it is determined that the user needs to be authenticated through the authentication terminal.

In a possible implementation manner, the first terminal is specifically configured to:

Obtain the first authorization information entered by the user in the first terminal, and obtain the second authorization information from the second terminal; the first authorization information includes the information entered by the user in the first terminal Authentication information, the second authorization information includes the authentication information input by the user to the second terminal; when the first authorization information matches the authorization information pre-configured in the first terminal, and the first authorization information When a piece of authorization information or the pre-configured authorization information matches the second authorization information, it is determined that the user is the authorized user.

In a possible implementation manner, the management policy includes third information, and the third information is used to indicate the authorized user; before the first terminal authenticates the user confirming to manage the first software, It is also used to determine the authorized user according to the third information in the management policy.

In a possible implementation, before the first terminal receives the management notification message, it is further used to: obtain the management policy set by the authorized user, and send the management policy to the network device; or receive The management policy from the network device.

In a possible implementation manner, the second terminal is specifically configured to: obtain the second authorization information input by the user in the second terminal; the second authorization information includes the user input to the Authentication information of the second terminal;

When the first authorization information matches the authorization information pre-configured in the second terminal, it is determined that the user is the authorized user.

In a possible implementation manner, the second terminal is further configured to: obtain the management policy set by the authorized user, and send the management policy to the network device; or receive information from the network device The management strategy.

In an eighth aspect, the present application provides a communication device. The communication device includes a processor and a memory. The memory is used to store computer programs or instructions; the processor is used to execute the computer programs or instructions stored in the memory. So that the communication device executes the corresponding method as described in the first aspect or the third aspect or the fifth aspect.

In a ninth aspect, the present application provides a communication device that includes a processor, a memory, and a transceiver. The transceiver is used to receive signals or send signals; and the memory is used to store computer programs or instructions; The processor is configured to call the computer program or instruction from the memory to execute the method according to the first aspect or the third aspect or the fifth aspect.

In a tenth aspect, the present application provides a communication device, the communication device includes a processor and an interface circuit, the interface circuit is configured to receive code instructions and transmit them to the processor; the processor runs the code instructions In order to perform the corresponding method as described in the first aspect or the third aspect or the fifth aspect.

In an eleventh aspect, the present application provides a computer-readable storage medium for storing a computer program or instruction. When the computer reads and executes the computer program or instruction, the first aspect or The method described in the third or fifth aspect is implemented.

In a twelfth aspect, the present application provides a computer program product including instructions. When the computer reads and executes the computer program product, the method described in the first aspect or the third aspect or the fifth aspect is realized.

In a thirteenth aspect, the present application provides a chip including a processor, the processor is coupled with a memory, and is configured to execute a computer program or instruction stored in the memory. When the processor executes the computer program or instruction At this time, the method described in the first aspect or the third aspect or the fifth aspect is realized.

In a fourteenth aspect, the present application provides a communication device that includes a processor, and when the processor executes a computer program or instruction in a memory, as described in the first or third or fifth aspects The method is executed.

Description of the drawings

FIG. 1 is a schematic diagram of an architecture applicable to an embodiment of the present application;

2 is a schematic flowchart of a software management method provided by an embodiment of the application;

Fig. 3 is a management policy configuration intention provided by an embodiment of the application;

FIG. 4 is a schematic flowchart of a software management method provided by an embodiment of the application;

FIG. 5 is a schematic diagram of an interface provided by an embodiment of the application;

FIG. 6 is a schematic diagram of an interface provided by an embodiment of this application;

FIG. 7A is a schematic diagram of a software management interface provided by an embodiment of this application;

FIG. 7B is a schematic diagram of another software management interface provided by an embodiment of the application;

FIG. 8 is a schematic flowchart of a software management method provided by an embodiment of the application;

FIG. 9 is a schematic flowchart of a software management method provided by an embodiment of this application;

FIG. 10 is a schematic structural diagram of a communication device provided by an embodiment of this application;

FIG. 11 is a schematic structural diagram of a communication device provided by an embodiment of this application;

FIG. 12 is a schematic diagram of a system structure provided by an embodiment of this application.

Detailed ways

In order to make the objectives, technical solutions, and advantages of the embodiments of the present application clearer, the embodiments of the present application will be further described below with reference to the accompanying drawings.

The ordinal numbers such as “first” and “second” mentioned in the embodiments of the present application are used to distinguish multiple objects, and are not used to limit the order, timing, priority, or importance of multiple objects. For example, the first terminal and the second terminal are only used to distinguish different terminals, but do not indicate the difference in priority or importance of the two terminals.

At present, more and more software are installed in vehicles. Therefore, a method is needed to manage the software in vehicles to ensure that software installation, update, and uninstallation processes are reasonably authorized by legitimate users. As shown in Figure 1, the embodiments of the present application relate to network equipment, vehicle-mounted terminals, and mobile terminals. Wherein, the location of the mobile terminal may not be limited. FIG. 1 takes the mobile terminal located outside the vehicle-mounted terminal as an example for illustration, and the mobile terminal may also be located in the vehicle-mounted terminal.

When it is necessary to perform management operations on the software in the vehicle-mounted terminal, such as installing software, updating software, or uninstalling software, in order to ensure that legitimate users authorize software management operations, in the embodiments of the present application, the execution may be performed at the user's instruction according to different situations. Before the management operation, the vehicle-mounted terminal and the mobile terminal jointly authenticate the user's identity, thereby ensuring that the management operation of the software is managed and controlled, and improving the safety of the vehicle-mounted terminal.

It should be noted that, in the embodiments of the present application, the vehicle-mounted terminal is installed in the vehicle and may be a component of the vehicle, for example, it may be a smart device equipped in the vehicle, which is structurally integrated in the vehicle and belongs to a part of the vehicle.

The mobile terminal may be a smart device independent of the vehicle, such as a (mobile phone), a tablet computer (Pad), and so on.

In the embodiments of this application, a vehicle-mounted terminal is taken as an example for description, but the method applicable to a vehicle-mounted terminal in this application can also be applied to other types of terminals, such as airplanes, drones, ships, trains, and so on.

In addition, the network architecture and business scenarios described in the embodiments of this application are intended to illustrate the technical solutions of the embodiments of this application more clearly, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. Those of ordinary skill in the art will know that With the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are equally applicable to similar technical problems.

For ease of introduction, in the following, the method is described by the interaction between the first terminal, the second terminal, and the network device as an example. Because this embodiment is applied to the system architecture shown in FIG. 1 as an example, the network device described below may be a network device in the network architecture shown in FIG. 1, and the network device may be an OTA server or a vehicle. Networking (vehicle-to-everything, V2X) server, or other servers. The first terminal described below may refer to the vehicle-mounted terminal in the network architecture shown in FIG. 1. The second terminal described below may refer to the mobile terminal in the network architecture shown in FIG. 1. In practical applications, the second terminal in the embodiment of the present application may be a mobile phone or a tablet computer ( Pad) and other equipment.

In the embodiment of the present application, the communication data between the first terminal and the second terminal may be transmitted through a secure transmission channel. At present, any two terminals cannot establish a secure transmission channel, and only two terminals with an association relationship can establish a secure transmission channel. Therefore, before establishing a secure transmission channel, an association relationship needs to be established between the first terminal and the second terminal. The so-called association relationship specifically refers to the establishment of a secure communication channel between the first terminal and the second terminal. There can be multiple implementation methods for how to establish an association relationship, which will be described separately below.

Association method 1:

The second terminal sends an association request message to the network device, and the association request message includes information such as the identity of the user to which the first terminal belongs (for example, the certificate number of the user, etc.), and the identity of the first terminal.

After receiving the association request message from the second terminal, the network device determines that the user identification and the identification of the first terminal carried in it are both legal and valid, and can send a verification code to the second terminal.

After the second terminal receives the verification code sent by the network device, the user using the second terminal enters the verification code in the first terminal.

When the first terminal sends the verification code entered by the user to the network device, the network device determines that the verification code sent by the first terminal is the same as the verification code sent by the network device to the second terminal, and then instructs the first terminal to establish an association relationship with the second terminal , Or instruct the second terminal to establish an association relationship with the first terminal.

Association method two:

The second terminal sends an association request message to the network device, where the association request message includes information such as the identity of the user to which the first terminal belongs, and the identity of the first terminal.

After receiving the association request message from the second terminal, the network device determines that the user identification and the identification of the first terminal carried in it are legal and valid, and can send a verification code to the first terminal and the second terminal.

When the first terminal determines that the verification code input by the user is the same as the verification code sent by the network device to the first terminal, the first terminal may establish an association relationship with the second terminal.

Association three:

After receiving the association request message from the second terminal, the network device determines that the user identity and the identity of the first terminal carried in it are both legal and valid, and can send a verification code to the first terminal.

After receiving the verification code sent by the network device, the first terminal may display the verification code on the display screen and prompt the user to input the verification code into the second terminal.

The user using the second terminal inputs the verification code displayed in the first terminal into the second terminal, and sends the verification code to the network device through the second terminal.

When the network device determines that the verification code sent by the second terminal is the same as the verification code sent by the network device to the first terminal, it instructs the first terminal to establish an association relationship with the second terminal, or instructs the second terminal to establish an association relationship with the first terminal.

The above is just an example, the first terminal and the second terminal may also establish an association relationship in other ways, which will not be illustrated one by one here.

After the first terminal and the second terminal establish an association relationship, a secure transmission channel can be established through wireless or wired communication, and data can be transmitted through the established secure transmission channel. It should be noted that how to specifically establish a secure transmission channel between the first terminal and the second terminal is not limited in the embodiment of the present application, and will not be repeated here.

In combination with the foregoing description, as shown in FIG. 2, it is a schematic flowchart of a software management method provided by an embodiment of this application. The method includes:

Step 201: When it is determined to perform a management operation on the first software, an authentication terminal is determined according to the management policy corresponding to the first software.

In the embodiment of the present application, the management operation includes but is not limited to any one of updating the first software, installing the first software, and uninstalling the first software. The above are just examples, and there may be other management operations, so I won't repeat them here.

For example, when the management operation is to update the first software, when the network device obtains the update package of the first software in the first terminal, it can determine that the first software needs to be updated. Of course, the network device can also determine that the first software needs to be updated in other ways, which will not be repeated here.

The first software may be any software installed in the first terminal. For example, the first software may be map navigation software, in-vehicle central control entertainment software, or in-vehicle communication module system software. The specific type of software is not limited.

In order to prevent unauthorized users from unauthorized management operations on the software in the first terminal, the security of the first terminal is improved. For this reason, in the embodiment of the present application, the user who confirms the management operation of the first software may be authenticated through the authentication terminal to ensure that the user who performs the management operation of the first software is an authorized user, which will be described in detail below.

Exemplarily, the authentication terminal may include at least one of a first terminal and a second terminal, and the second terminal has an association relationship with the first terminal. For details on how to establish an association relationship between the second terminal and the first terminal, reference may be made to the foregoing description.

Exemplarily, the management strategy corresponding to the first software may include a variety of information, for example, may include one or more of the following: first information, the first information is used to indicate the authentication terminal; second information, the second information The information is used to indicate the authorization mode of the first software; the third information is used to indicate the authorized user.

Among them, the authorization mode may include a first mode and a second mode. The first mode is that each management operation of the first software needs to authenticate the user through the authentication terminal; the second mode is that the first management operation of the first software needs to pass all the operations. The authentication terminal authenticates the user, and the management operation after the first management operation of the first software does not need to authenticate the user through the authentication terminal.

For example, the first mode may be applicable to software that has a greater impact on the security of the first terminal, such as operating system software in the first terminal. The second mode may be suitable for software that frequently manages operations but has a small impact on the security of the first terminal, such as map navigation software in the first terminal.

The authorized user may be the owner of the first terminal, or may be a user designated by the owner of the first terminal. The owner of the first terminal may also have other names, such as the user of the first terminal, the owner of the first terminal, the owner of the first terminal, and so on.

Through the first information to the third information in the management policy, the first terminal and the second terminal can determine information such as the authentication terminal, the authorization mode, and the authorized user.

It should be noted that the management policies corresponding to different software in the first terminal may be different. For example, the management policies of different software in the first terminal may be as shown in Table 1.

Table 1

Of course, Table 1 is only an example, and the software in the first terminal may also correspond to other management strategies, which will not be illustrated one by one here.

It should be noted that the authentication terminal in the management policy may also include other terminals, such as a third terminal, a fourth terminal, etc., and authorized users can configure according to actual conditions. When the authentication terminal includes other terminals, the specific execution content can be referred to The description of the second terminal will not be repeated here in this embodiment of the application.

It should be noted that, in the embodiment of the present application, there may be multiple implementation manners for the specific configuration of the management strategy corresponding to the first software. In the first possible implementation manner, the management policy corresponding to the first software may be configured by the network device, and the network device may send the management policy corresponding to the first software to the first terminal and the second terminal.

In the second possible implementation manner, the management policy corresponding to the first software may also be set by the authorized user in the first terminal, and the first terminal may send the management policy set by the authorized user to the network device and the second terminal.

For example, in this implementation manner, the configuration options of the management policy may be displayed on the display screen of the first terminal, and the first terminal may save the management policy input by the user and send it to the network device and the second terminal.

For example, as shown in FIG. 3, a schematic diagram of an interface provided by an embodiment of this application. In Figure 3, the first software is the map navigation software as an example. In Fig. 3, the authentication terminal that can be selected in the management strategy, the authorization mode that can be selected, and the authorized user that can be set are displayed. The user can set the management strategy in the first terminal through the interface shown in Fig. 3.

In a third possible implementation manner, the management policy corresponding to the first software may also be set by the authorized user in the second terminal, and the second terminal may send the management policy set by the authorized user to the network device and the first terminal.

For example, in this implementation manner, the configuration options of the management policy may be displayed on the display screen of the second terminal, and the second terminal may save the management policy input by the user and send it to the network device and the first terminal. For the configuration options of the management policy displayed by the second terminal, reference may be made to the example in FIG. 3, and details are not described here.

Step 202: The network device sends a management notification message to the authentication terminal.

Wherein, the management notification message is used to notify the management operation of the first software.

It should be noted that the management notification message may also include other information, such as the identification of the first software, and the identification of the authentication terminal, which is not limited in the embodiment of the present application.

Step 203: The first terminal receives the management notification message.

Step 204: The second terminal receives the management notification message.

It should be noted that the order of step 203 and step 204 is not limited, and the above description is only performed by taking step 203 first as an example. In practical applications, step 204 can also be performed first, or step 203 and step 204 can be performed at the same time, which will not be repeated here.

Step 205: When the second terminal determines that the authentication terminal includes the second terminal according to the management policy corresponding to the first software, authenticate the user who is confirmed to manage the first software.

For example, the second terminal may obtain second authorization information input by the user in the second terminal; the second authorization information includes authentication information input by the user to the second terminal. When the first authorization information matches the authorization information pre-configured in the second terminal, the second terminal can determine that the user is the authorized user; when the first authorization information matches the second terminal When the pre-configured authorization information in the data does not match, the second terminal may determine that the user is the authorized user. Wherein, the authentication information input by the user in the second terminal may be a verification password or a fingerprint or a face image, etc., which is specifically determined according to actual conditions, which is not limited in the embodiment of the present application.

Of course, the above is only an example, and the second terminal may also authenticate the user in other ways, which will not be repeated here.

Step 206: When it is determined that the user is an authorized user who manages the first software, the second terminal sends a second confirmation instruction input by the user to the first terminal.

The second confirmation instruction is used to instruct the user to confirm, through the second terminal, to perform the management operation indicated by the management notification message on the first software.

Step 207: When the first terminal determines that the authentication terminal includes the first terminal and the second terminal according to the management policy corresponding to the first software, authenticate the user who confirms the management of the first software through the authentication terminal .

In the embodiment of the present application, the authentication terminal may be used to authenticate the user who confirms the management operation of the first software. The authentication terminal is at least one of the first terminal and the second terminal. There is an association relationship between the second terminal and the first terminal. For how to establish an association relationship between the first terminal and the second terminal, reference may be made to the foregoing description, and details are not repeated here.

It should be noted that the order of step 205 and step 207 is not limited, and the above description is only performed by taking step 205 first as an example. In practical applications, step 207 can also be performed first, or step 205 and step 207 can be performed at the same time, which will not be repeated here.

Step 208: When the first terminal determines that the user is an authorized user who manages the first software, and obtains the first confirmation instruction input by the user, and receives the second confirmation instruction from the second terminal , The first terminal performs the management operation on the first software according to the first confirmation instruction and the second confirmation instruction.

The first confirmation instruction is used to instruct the user to confirm the execution of the management operation on the first software through the first terminal.

From the above process, it can be seen that before the management operation of the first software in the first terminal, the first terminal and the second terminal determine whether the user is an authorized user at the same time. When the first terminal and the second terminal both determine the user When it is an authorized user, the first terminal can manage the first software. In this way, unauthorized users can be prevented from unauthorized management of the first software in the first terminal, the authorization management and control of the first software can be realized, and the security of the first terminal can be improved.

In the process shown in FIG. 2, the authentication terminal may include at least one of the first terminal and the second terminal. When the authentication terminal is different, the management operation process of the first software may be different, which will be described separately below.

Embodiment 1: The authentication terminal includes a first terminal and a second terminal.

When the authentication terminals are the first terminal and the second terminal, both the first terminal and the second terminal are required to determine that the user currently managing and operating the first software is an authorized user, and then the first software is managed. For details, refer to Figure 4 The process shown.

Step 401: The network device determines that the authentication terminal is the first terminal and the second terminal according to the management policy corresponding to the first software, and sends a management notification message to the first terminal and the second terminal respectively.

As mentioned above, the network device can determine the authentication terminal according to the first information in the management policy.

The network device sends a management notification message to indicate to the first terminal and the second terminal that the first software in the first terminal needs to be managed and operated, and the management operation needs to be performed. After the first terminal and the second terminal obtain the management notification message, they can execute the management operation process of the first software according to the management policy corresponding to the first software. For details, refer to the following process.

It should be noted that the first terminal and the second terminal determine that the first software needs to be managed and operated when receiving the management notification message of the network device, and the management notification message is equivalent to a trigger message for the first software to perform the management operation.

The following describes the management operation as an example of updating the first software or installing the first software. When the management operation is to update the first software or install the first software, step 402 and step 403 may be included.

Step 402: The first terminal sends a first request message to the network device.

The first request message may be used to request an installation package or an update package of the first software.

The first request message may include the identification of the first terminal, the identification of the first software, and other information.

Step 403: The network device sends a first response message to the first terminal.

In a possible implementation manner, the first response message includes an installation package or an update package of the first software. In this manner, the first terminal can directly obtain the installation update package or the update package through the first response message.

In another possible implementation manner, the first response message includes the installation update package or the download address of the update package of the first software, and the first terminal may obtain the installation update package or the update package through the download address.

The specific implementation manner of the download address is not limited. For example, the download address may be implemented using a uniform resource locator (URL). For example, the first response message may include a uniform resource locator (uniform resource locator, URL), and the URL indicates an installation update package or a download address of the update package. The first terminal can download the installation update package or update package of the first software through the URL.

Step 404: The first terminal receives the first response message, and obtains the installation package or the update package of the first software.

Step 405: The first terminal determines the authorization mode of the first software according to the second information in the management policy corresponding to the first software.

The first terminal may determine whether the user needs to be authenticated by the authentication terminal according to the authorization mode. Specifically, in a possible implementation manner, when it is determined that the authorization mode of the first software is the first mode, the first terminal determines that the user needs to be authenticated through the authentication terminal, and then the first The terminal can perform step 406 to step 411.

In a possible implementation, when it is determined that the authorization mode of the first software is the second mode, and the first software is the first management operation, the first terminal determines that it needs to pass the authentication terminal pair The user is authenticated, and the first terminal can execute step 406 to step 411 at this time.

In a possible implementation, when it is determined that the authorization mode of the first software is the second mode and the first software is the Nth management operation, N is an integer greater than 1, and the first terminal It is determined that the user does not need to be authenticated by the authentication terminal. In this case, the first terminal may not perform step 406 and directly perform step 411.

Optionally, after the first terminal obtains the installation update package or update package of the first software, if it has not received the second authorization information of the second terminal for a long time, a message may be sent to remind the second terminal. For details, please refer to the steps 406. Of course, the first terminal may also execute step 406 in other situations, which is not limited in the embodiment of the present application. It should be noted that step 406 may not be executed. When step 406 is not performed, the second terminal may perform step 408 after receiving the management notification message in step 403.

Step 406: When the first terminal determines that the authentication terminal includes the first terminal and the second terminal according to the management policy corresponding to the first software, the first terminal sends an authentication request message to the second terminal for requesting the second terminal to authenticate the user.

It should be noted that a secure transmission channel can be established between the first terminal and the second terminal through Near Field Communication (NFC), Bluetooth, Wireless Fidelity (WiFi), or wired mode, and the first terminal The information with the second terminal is transmitted through the secure transmission channel.

Step 407: The first terminal obtains the first authorization information from the user.

The first authorization information includes the authentication information input by the user to the first terminal. For example, the authentication information input by the user in the first terminal may be a verification password or a fingerprint or a face image, etc., which is specifically determined according to actual conditions.

For example, the first terminal may display the interface shown in FIG. 5 to prompt the user to input authentication information. In Figure 5, the user is prompted to enter the verification password as an example. In practical applications, multiple options can also be displayed for the user to choose. For example, in Figure 5, under the input verification password, the user can also switch to input fingerprints or face images.

Step 408: The second terminal obtains the second authorization information from the user, and obtains the second confirmation instruction input by the user in the second terminal.

Wherein, the second authorization information includes authentication information input by the user to the second terminal. The second confirmation instruction is used to instruct the user to confirm the management operation of the first software.

The authentication information input by the user in the second terminal may be a verification password or a fingerprint or a face image, etc., which is specifically determined according to actual conditions. Similar to step 407, an interface as shown in FIG. 6 can be displayed in the second terminal, and the user can input authentication information according to the prompt information in the interface.

For example, assuming that the management operation is to update the first software, the second terminal can display the interface shown in Figure 7A on the display screen. Figure 7A shows the precautions for the software update, the estimated update time and other information for information The user decides whether to update the first software immediately. When the user clicks "Confirm" in FIG. 7A, the second confirmation instruction is triggered, and the second terminal obtains the user's second confirmation instruction. When the user clicks "Cancel" in FIG. 7A, an update cancel instruction is triggered, indicating that the first software is not updated.

Of course, the above is only an example, and the second terminal may also obtain the second confirmation instruction in other ways, which will not be repeated here.

It should be noted that when the user clicks "Cancel" in FIG. 7A, the second terminal obtains the update cancellation instruction, and at this time, the second terminal sends the update cancellation instruction to the first terminal. When the first terminal determines that the update cancellation instruction is received, the update operation of the first software may no longer be performed.

It should be noted that the order of step 407 and step 408 is not limited, and the above description is only performed by taking step 407 first as an example. In practical applications, step 408 can also be performed first, or step 407 and step 408 can be performed at the same time, which will not be repeated here.

Step 409: The second terminal sends a second confirmation instruction and second authorization information to the first terminal.

When the second terminal sends the second authorization information to the first terminal, the first terminal may verify the second authorization information, thereby determining whether the user is an authorized user according to the second authorization information.

Of course, in step 409, the second terminal may also only send a second confirmation instruction to the first terminal. In this case, the second terminal may verify the second authorization information to determine whether the user is Is an authorized user. In the process of FIG. 4, the second terminal sends the second authorization information as an example for description.

After the first terminal obtains the second authorization information from the second terminal, it can determine whether the user currently performing the software management operation is an authorized user according to the first authorization information and the second authorization information. For details, refer to step 410.

Step 410: When the first authorization information matches the authorization information pre-configured in the first terminal, and the first authorization information or the pre-configured authorization information matches the second authorization information, the first authorization information A terminal determines that the user is the authorized user.

In the embodiment of the present application, when the first authorization information does not match the authorization information pre-configured in the first terminal, or the first authorization information does not match the second authorization information, or the pre-configured When the authorization information of does not match the second authorization information, the first terminal determines that the user is not the authorized user. When the first terminal determines that the user is not the authorized user, the software management operation may not be performed.

Alternatively, when the first terminal determines that the second authorization information includes an instruction to cancel the management operation, the management operation of the first software may no longer be performed.

For example, the pre-configured authorization information includes a pre-configured verification password, the first authorization information includes a verification password entered by the user, and the second authorization information includes a verification password entered by the user. When the first terminal determines that the verification password entered by the user in the first terminal is the same as the pre-configured verification password, and the verification password entered in the second terminal is the same as the pre-configured verification password, the first terminal can determine the user Is an authorized user, otherwise it can be determined that the user is not an authorized user.

For example, the pre-configured authorization information includes a pre-configured authentication password and pre-configured fingerprint information, the first authorization information includes the authentication password entered by the user, and the second authorization information includes the fingerprint information entered by the user. When the first terminal determines that the verification password entered by the user is the same as the pre-configured verification password, and the fingerprint information entered by the user is the same as the pre-configured fingerprint information, the first terminal may determine that the user is an authorized user, otherwise it may determine that the user is an authorized user. The user is not an authorized user.

It should be noted that the first terminal may determine the authorized user according to the third information in the management policy, and the specific process will not be repeated.

Before the first terminal performs the management operation on the first software, the first confirmation instruction input by the user in the first terminal may also be obtained. For details, refer to the following step 411.

Step 411: The first terminal obtains the user's first confirmation instruction.

The first confirmation instruction is used to instruct the user to confirm the management operation of the first software.

For example, assuming that the management operation is to update the first software, the first terminal may display an interface as shown in FIG. 7B on the display screen. The user decides whether to update the first software immediately. When the user clicks "Confirm" in FIG. 7B, the first confirmation instruction is triggered, and the first terminal obtains the user's first confirmation instruction. When the user clicks "Cancel" in FIG. 7B, an update cancel instruction is triggered, which means that the first software is not updated and the first terminal will not install the update package of the first software.

Of course, the above is only an example, and the first terminal may also obtain the first confirmation instruction in other ways, which will not be repeated here.

It should be noted that in the above process, step 411 can also be executed between steps 403 and 410, for example, between step 403 and step 404, and step 411 can also be executed simultaneously with step 403. The application embodiment does not limit the specific execution order of step 411.

Step 412: The first terminal performs the management operation on the first software according to the first confirmation instruction and the second confirmation instruction of the user.

When the authentication terminals are the first terminal and the second terminal, and the first terminal obtains the first confirmation instruction input by the user in the first terminal and the second confirmation instruction input by the user in the second terminal, it can be determined to execute The management operation of the first software. For example, the first terminal may install the installation package or update package of the first software obtained in step 404, and the specific installation process will not be repeated.

From the above process, it can be known that before the first software in the first terminal is managed and operated, the first terminal and the second terminal are required to determine whether the user who operates the first software is an authorized user. When both the first terminal and the second terminal determine that the user is an authorized user, the first terminal can manage and operate the first software. In this way, double authentication of the user is realized, it can be ensured that the management operation of the first software is authorized by the authorized user, the authorization control of the management operation of the first software is realized, and the security of the first terminal is improved.

In the process shown in FIG. 4, steps 409 to 410 can also be replaced by the following steps. In the following steps, the second terminal does not forward the second authorization information, but determines whether the user is an authorized user based on the second authorization information.

Step 409a: The second terminal sends a second confirmation instruction to the first terminal.

In step 409a, the second terminal sends a second confirmation instruction to the first terminal when it is determined that it matches the authorization information pre-configured in the second terminal according to the second authorization information.

Correspondingly, when it is determined that the second authorization information does not match the authorization information pre-configured in the second terminal, the second terminal determines that the user is not an authorized user, and may send a suspension management operation message to the first terminal; the suspension The management operation message is used to indicate that the user is not the authorized user.

Alternatively, when the second terminal obtains the management cancellation instruction input by the user, it may determine not to perform management operations on the first software, so that a management cancellation message can be sent to the first terminal, where the management cancellation message is used to instruct the The user cancels the execution of the management operation.

Correspondingly, step 410 can be replaced by the following steps:

Step 410a: When the first authorization information matches the authorization information pre-configured in the first terminal, and a second confirmation instruction from the second terminal is received, the first terminal determines that the user is the authorized user.

Correspondingly, when the first terminal determines that the first authorization information does not match the authorization information pre-configured in the first terminal, or the first terminal receives a suspension management operation message from the first terminal, the first terminal determines that the user is not The authorized user can no longer perform the management operation.

In the process shown in FIG. 4, the authentication terminal includes a first terminal and a second terminal. In an actual application process, the authentication terminal may also be the first terminal or the second terminal. The following will describe the authentication terminal as the first terminal.

Embodiment 2: The authentication terminal is the first terminal.

When the authentication terminal is the first terminal, the first terminal is required to determine whether the user currently operating, managing, and operating the first software is an authorized user. For details, refer to the flow shown in FIG. 8.

Step 801: The network device determines that the authentication terminal is the first terminal according to the management policy corresponding to the first software, and sends a management notification message to the first terminal.

Step 802: The first terminal sends a first request message to the network device for requesting an installation package or an update package of the first software.

The following describes the management operation as an example of updating the first software or installing the first software. When the management operation is to update the first software or install the first software, step 802 and step 803 may be included.

Step 803: The network device sends a first response message to the first terminal.

Step 804: The first terminal receives the first response message, and obtains the installation package or the update package of the first software.

For step 801 to step 804, reference may be made to the description in step 401 to step 404, which will not be repeated here.

Step 805: The first terminal determines the authorization mode of the first software according to the second information in the management policy corresponding to the first software.

The first terminal may determine whether the user needs to be authenticated by the authentication terminal according to the authorization mode. Specifically, in a possible implementation manner, when it is determined that the authorization mode of the first software is the first mode, the first terminal determines that the user needs to be authenticated through the authentication terminal, and then the first The terminal may perform step 806.

In a possible implementation, when it is determined that the authorization mode of the first software is the second mode, and the first software is the first management operation, the first terminal determines that it needs to pass the authentication terminal pair The user is authenticated, and the first terminal may execute step 806 at this time.

In a possible implementation manner, when it is determined that the authorization mode of the first software is the second mode and the first software is the Nth management operation, N is an integer greater than 1, and the first terminal It is determined that the user does not need to be authenticated by the authentication terminal. In this case, the first terminal may not perform step 806 and directly perform step 809.

Step 806: When the first terminal determines that the authentication terminal is the first terminal according to the management policy corresponding to the first software, the first terminal obtains the first authorization information from the user.

Step 807: When the first authorization information matches the authorization information pre-configured in the first terminal, the first terminal determines that the user is the authorized user.

For example, the pre-configured authorization information includes a pre-configured verification password, and the first authorization information includes a verification password entered by the user. When the first terminal determines that the authentication password entered by the user in the first terminal is the same as the pre-configured authentication password, the first terminal may determine that the user is an authorized user.

In the embodiment of the present application, when the first authorization information does not match the authorization information pre-configured in the first terminal, the first terminal determines that the user is not the authorized user. When the first terminal determines that the user is not the authorized user, the management operation may not be performed.

Before the first terminal performs the management operation on the first software, it may also obtain the user's first confirmation instruction. For details, refer to the following step 808.

Step 808: The first terminal obtains the user's first confirmation instruction.

For specifically how the first terminal obtains the first confirmation instruction, reference may be made to the description in step 411, which will not be repeated here.

Step 809: The first terminal performs the management operation on the first software according to the first confirmation instruction of the user.

For example, the first software may be installed according to the installation package obtained in step 804, or the first software may be updated according to the update package obtained in step 804.

For steps 808 to 809, reference may be made to the descriptions of the corresponding steps in the flow shown in FIG. 4, which will not be repeated here.

It should be noted that, in the above process, step 808 can also be executed between step 803 and step 807, for example, between step 803 and step 804. The specific execution order of step 808 in the embodiment of this application is Not limited.

From the above process, it can be known that before the management operation of the first software in the first terminal, the first terminal is required to determine whether the user performing the management operation of the first software is an authorized user. In this way, the authorization control of the management operation of the first software is realized, and the security of the first terminal is improved.

The following will describe the authentication terminal as the second terminal.

Embodiment 3: The authentication terminal is the second terminal.

When the authentication terminal is the second terminal, the second terminal is required to determine whether the user currently executing the management operation of the first software is an authorized user. For details, refer to the flow shown in FIG. 9.

Step 901: The network device determines that the authentication terminal is the second terminal according to the management policy corresponding to the first software, and sends a management notification message to the first terminal and the second terminal respectively.

The following describes the management operation as an example of updating the first software or installing the first software. When the management operation is to update the first software or install the first software, step 902 and step 903 may be included.

Step 902: The first terminal sends a first request message to the network device for requesting an installation package or an update package of the first software.

Step 903: The network device sends a first response message to the first terminal.

Step 904: The first terminal receives the first response message, and obtains the installation package or the update package of the first software.

For steps 901 to 904, reference may be made to the descriptions in the corresponding steps in the flow shown in FIG. 4, which will not be repeated here.

Step 905: The first terminal determines the authorization mode of the first software according to the second information in the management policy corresponding to the first software.

The first terminal may determine whether the user needs to be authenticated by the authentication terminal according to the authorization mode. Specifically, in a possible implementation manner, when it is determined that the authorization mode of the first software is the first mode, the first terminal determines that the user needs to be authenticated by the authentication terminal, and then the first The terminal may perform step 906.

In a possible implementation, when it is determined that the authorization mode of the first software is the second mode, and the first software is the first management operation, the first terminal determines that it needs to pass the authentication terminal pair The user is authenticated, and the first terminal can execute step 906 at this time.

In a possible implementation manner, when it is determined that the authorization mode of the first software is the second mode and the first software is the Nth management operation, N is an integer greater than 1, and the first terminal It is determined that the user does not need to be authenticated by the authentication terminal. In this case, the first terminal may not perform step 906 and directly perform step 910.

Optionally, after the first terminal obtains the installation package or update package of the first software, if it has not received the second authorization information of the second terminal for a long time, a message may be sent to remind the second terminal. For details, refer to step 906 . Of course, the first terminal may also perform step 906 in other situations, which is not limited in the embodiment of the present application. It should be noted that when step 906 is not performed, the second terminal may perform step 907 after receiving the management notification message in step 903.

Optionally, step 906: when the first terminal determines that the authentication terminal is the second terminal according to the management policy corresponding to the first software, the first terminal sends an authentication request message to the second terminal for requesting the second terminal to authenticate the user.

Step 907: The second terminal obtains the second authorization information from the user.

Wherein, the second authorization information may include a verification password or fingerprint or face image input by the user.

Wherein, when the second terminal determines that the second authorization information matches the authorization information pre-configured in the second terminal, the second terminal determines that the user is an authorized user; correspondingly, when the second authorization information is determined When it does not match the authorization information pre-configured in the second terminal, the second terminal determines that the user is not an authorized user.

For example, the pre-configured authorization information includes a pre-configured authentication password, and the second authorization information includes the authentication password input by the user to the second terminal. When the first terminal determines that the authentication password entered by the user in the first terminal is the same as the pre-configured authentication password, the first terminal may determine that the user is an authorized user, otherwise, it may determine that the user is not an authorized user.

Step 908: The second terminal obtains the user's second confirmation instruction.

For specifically how the second terminal obtains the second confirmation instruction of the user, reference may be made to the description in step 408, which will not be repeated here.

It should be noted that step 908 may also be executed before step 907, and the specific execution order of step 907 and step 908 is not limited in the embodiment of the present application.

When the second terminal determines that the user is an authorized user according to the second authorization information, step 909 is executed.

Step 909: The second terminal sends a second confirmation instruction to the first terminal.

Step 910: The first terminal receives a second confirmation instruction, and executes the management operation on the first software according to the second confirmation instruction.

It should be noted that when the second terminal determines that the second authorization information does not match the authorization information pre-configured in the second terminal, the second terminal may send a suspension management operation message to the first terminal; the suspension management The operation message is used to indicate that the user is not the authorized user. Or when the second terminal obtains the management cancellation instruction input by the user, the second terminal may send a management cancellation message to the first terminal; the management cancellation message is used to instruct to cancel the management operation of the first software.

Correspondingly, when the first terminal receives the message of suspending the management operation or the message of canceling the management operation, the first terminal may not perform the software management operation on the first software.

In the above process, before the first terminal performs the management operation, the second terminal is required to determine whether the user of the first software performing the management operation is an authorized user. In this way, it is possible to remotely authorize the management operation of the first software through the first terminal, and improve the flexibility of the management operation of the first software.

It should be noted that in the process shown in FIG. 9, step 909 can also be replaced by the following step 909a. In step 909a, the second terminal does not determine whether the user is an authorized user according to the second authorization information, but forwards the first 2. Authorization information.

Step 909a: The second terminal sends the second confirmation instruction and second authorization information to the first terminal.

After the first terminal obtains the second authorization information from the second terminal, it can determine whether the user currently performing the software management operation is an authorized user according to the second authorization information. In this case, step 910 is replaced with step 910a.

Step 910a: When the second authorization information matches the authorization information pre-configured in the first terminal, the first terminal determines that the user is the authorized user, and executes the first software according to the second confirmation instruction Management operations.

In the embodiment of the present application, when the second authorization information does not match the authorization information pre-configured in the first terminal, the first terminal determines that the user is not the authorized user. When the first terminal determines that the user is not the authorized user, the management operation may not be performed.

For example, the pre-configured authorization information includes a pre-configured verification password, and the second authorization information includes a verification password entered by the user. When the first terminal determines that the authentication password entered by the user in the second terminal is the same as the pre-configured authentication password, the first terminal may determine that the user is an authorized user, otherwise, it may determine that the user is not an authorized user.

For example, the pre-configured authorization information includes pre-configured fingerprint information, and the second authorization information includes fingerprint information input by the user. When the first terminal determines that the fingerprint information input by the user is the same as the pre-configured fingerprint information, the first terminal may determine that the user is an authorized user, otherwise, it may determine that the user is not an authorized user.

The processes shown in Figs. 4 to 9 describe the process of how to perform software management operations in the case of different authentication terminals. In the specific application process, the required process can be selected according to the actual situation.

The various embodiments described in this document may be independent solutions, or may be combined according to internal logic, and these solutions fall within the protection scope of the present application.

It is understandable that, in the foregoing method embodiments, the methods and operations implemented by the first terminal can also be implemented by components (such as chips or circuits) that can be used in the first terminal, and the methods and operations implemented by the second terminal can also be implemented by the second terminal. It can also be implemented by a component (such as a chip or circuit) that can be used in the second terminal, and the method and operation implemented by a network device can also be implemented by a component (such as a chip or circuit) that can be used in the network device.

In the foregoing embodiments provided in the present application, the methods provided in the embodiments of the present application are respectively introduced from the perspective of interaction between various devices. In order to implement the functions in the methods provided in the above embodiments of the present application, the first terminal, the second terminal, and the network device may include a hardware structure and/or a software module, in the form of a hardware structure, a software module, or a hardware structure plus a software module To achieve the above functions. Whether a certain function among the above-mentioned functions is executed by a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraint conditions of the technical solution.

The division of modules in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation. In addition, the functional modules in the various embodiments of the present application may be integrated in one processor, or may exist alone physically, or two or more modules may be integrated in one module. The above-mentioned integrated modules can be implemented in the form of hardware or software functional modules.

Similar to the foregoing concept, as shown in FIG. 10, an embodiment of the present application further provides an apparatus 1000 for implementing the functions of the first terminal or the second terminal or the network device in the foregoing method. For example, the device may be a software module or a chip system. In the embodiments of the present application, the chip system may be composed of chips, or may include chips and other discrete devices. The apparatus 1000 may include: a processing unit 1001 and a communication unit 1002.

In the embodiments of the present application, the communication unit may also be referred to as a transceiver unit, and may include a sending unit and/or a receiving unit, which are respectively used to perform the sending and receiving steps of the first terminal or the second terminal or the network device in the above method embodiment. .

Hereinafter, the communication device provided by the embodiment of the present application will be described in detail with reference to FIGS. It should be understood that the description of the device embodiment and the description of the method embodiment correspond to each other. Therefore, for the content that is not described in detail, please refer to the above method embodiment. For brevity, details are not repeated here.

In a possible design, the apparatus 1000 can implement the steps or processes corresponding to the terminal device or the network device in the above method embodiment, which will be described separately below.

Exemplarily, when the device 1000 implements the function of the first terminal in the previous process:

The communication unit 1002 is configured to receive management notification messages; the management notification messages are used to notify management operations of the first software; the management operations include updating the first software, installing the first software, and uninstalling the first software. Any item in a piece of software;

The processing unit 1001 is configured to, when it is determined that the authentication terminal includes the first terminal and the second terminal according to the management policy corresponding to the first software, authenticate the user who confirms the management of the first software through the authentication terminal; When it is determined that the user is an authorized user who manages the first software, and the first confirmation instruction input by the user is obtained, and the second confirmation instruction from the second terminal is received, according to the first confirmation An instruction and the second confirmation instruction to perform the management operation indicated by the management notification message on the first software;

The first confirmation instruction is used to instruct the user to confirm the execution of the management operation on the first software.

In a possible implementation manner, the management policy includes first information, and the first information is used to indicate the authentication terminal;

The processing unit 1001 is specifically configured to:

The first terminal determines, according to the first information in the management policy corresponding to the first software, that the authentication terminal includes the first terminal and the second terminal.

In a possible implementation manner, the management policy includes second information, and the second information is used to indicate an authorization mode of the first software;

Before the authentication of the user confirming the management of the first software, the processing unit 1001 is further configured to:

Determining the authorization mode of the first software according to the second information in the management policy;

It is determined according to the authorization mode that the user needs to be authenticated by the authentication terminal.

In a possible implementation manner, the authorization mode includes a first mode and a second mode, and the first mode is that each management operation of the first software requires the authentication terminal to authenticate the user To be certified;

The second mode is that the first management operation of the first software needs to authenticate the user through the authentication terminal, and the management operations after the first management operation of the first software do not need to pass the The authentication terminal authenticates the user;

Before the authentication of the user confirming the management of the first software through the authentication terminal, the processing unit 1001 is further configured to:

When it is determined that the authorization mode of the first software is the first mode, or the authorization mode of the first software is determined to be the second mode, and the first software is the first management operation, it is determined that the authorization mode needs to be passed The authentication terminal authenticates the user.

In a possible implementation manner, the processing unit 1001 is specifically configured to:

Obtain the first authorization information entered by the user in the first terminal, and obtain the second authorization information from the second terminal; the first authorization information includes the information entered by the user in the first terminal Authentication information, where the second authorization information includes authentication information input by the user to the second terminal;

When the first authorization information matches the authorization information pre-configured in the first terminal, and the first authorization information or the pre-configured authorization information matches the second authorization information, it is determined The user is the authorized user.

In a possible implementation manner, the management policy includes third information, and the third information is used to indicate the authorized user;

The processing unit 1001 is further configured to:

The authorized user is determined according to the third information in the management policy.

In a possible implementation manner, before the receiving the management notification message, the communication unit 1002 is further configured to:

Acquiring the management policy set by the authorized user, and sending the management policy to the network device;

Or receive the management policy from the network device.

In a possible implementation manner, the communication device is a vehicle-mounted terminal, and the second terminal is a mobile terminal.

Exemplarily, when the device 1000 implements the function of the second terminal in the previous process:

The communication unit 1002 is configured to receive the management notification message; the management notification message is used to notify the management operation of the first software; the management operation includes updating the first software, installing the first software, and uninstalling the first software. Any item of the first software;

The processing unit 1001 is configured to authenticate the user confirming to manage the first software when it is determined that the authentication terminal includes the second terminal according to the management policy corresponding to the first software;

When it is determined that the user is an authorized user who manages the first software, the second terminal sends a second confirmation instruction input by the user to the first terminal, and the second confirmation instruction is used to instruct the user to confirm Performing the management operation indicated by the management notification message on the first software.

Acquiring second authorization information entered by the user in the second terminal; the second authorization information includes authentication information entered by the user in the second terminal;

When the first authorization information matches the authorization information pre-configured in the second terminal, it is determined that the user is the authorized user who manages the first software.

In a possible implementation manner, the communication unit 1002 is further configured to:

Or receive the management policy from the network device.

In a possible implementation manner, the management policy includes first information, and the first information is used to indicate the authentication terminal; the processing unit 1001 determines the The authentication terminal is the second terminal.

In a possible implementation manner, the management policy includes third information, and the third information is used to indicate the authorized user; the processing unit 1001 is further used to:

Exemplarily, when the apparatus 1000 implements the function of the network device in the previous process:

The processing unit 1001 is configured to determine an authentication terminal according to a management policy corresponding to the first software when it is determined to perform a management operation on the first software, and the authentication terminal is used to authenticate a user who confirms the management of the first software; The authentication terminal includes a first terminal and a second terminal; the management operation includes any one of updating the first software, installing the first software, and uninstalling the first software;

The communication unit 1002 is configured to send a management notification message to the authentication terminal, where the management notification message is used to notify the first software to perform the management operation.

In a possible implementation manner, before the determining to perform a management operation on the first software, the communication unit 1002 is further configured to:

Sending the management policy to the first terminal and the second terminal;

Or receive the management policy from the first terminal or the second terminal.

The processing unit 1001 is specifically configured to:

The authentication terminal is determined according to the first information in the management policy.

In a possible implementation manner, the management policy includes first information, and the first information is used to indicate the authentication terminal; the processing unit 1001 determines the Authentication terminal.

FIG. 11 shows an apparatus 1100 provided by an embodiment of the application, and the apparatus shown in FIG. 11 may be a hardware circuit implementation of the apparatus shown in FIG. 10. The communication device can be applied to the flowchart shown in FIG. 2 to perform the functions of the terminal device or the network device in the foregoing method embodiment. For ease of description, FIG. 11 only shows the main components of the communication device.

The apparatus 1100 shown in FIG. 11 includes at least one processor 1120, configured to implement any method in FIG. 2 provided in an embodiment of the present application.

The device 1100 may further include at least one memory 1130 for storing program instructions and/or data. The memory 1130 and the processor 1120 are coupled. The coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, and may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules. The processor 1120 may operate in cooperation with the memory 1130. The processor 1120 may execute program instructions stored in the memory 1130. At least one of the at least one memory may be included in the processor.

In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in the processor or instructions in the form of software. The steps of the method disclosed in combination with the embodiments of the present application may be embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor. The software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware. To avoid repetition, it will not be described in detail here.

It should be noted that the processor in the embodiment of the present application may be an integrated circuit chip with signal processing capability. In the implementation process, the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software. The above-mentioned processor may be a general-purpose processor, a digital signal processing circuit (digital signal processor, DSP), a dedicated integrated circuit (application specific integrated circuit, ASIC), a field programmable gate array (field programmable gate array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

It can be understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electrically available Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory. The volatile memory may be random access memory (RAM), which is used as an external cache. By way of exemplary but not restrictive description, many forms of RAM are available, such as static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), and synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (synchlink DRAM, SLDRAM) ) And direct memory bus random access memory (direct rambus RAM, DR RAM). It should be noted that the memories of the systems and methods described herein are intended to include, but are not limited to, these and any other suitable types of memories.

The apparatus 1100 may further include a communication interface 1110 for communicating with other devices through a transmission medium, so that the apparatus used in the apparatus 1100 can communicate with other devices. In the embodiment of the present application, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface. In the embodiment of the present application, when the communication interface is a transceiver, the transceiver may include an independent receiver and an independent transmitter; it may also be a transceiver with integrated transceiver functions, or an interface circuit.

The device 1100 may also include a communication line 1140. Among them, the communication interface 1110, the processor 1120, and the memory 1130 may be connected to each other through a communication line 1140; the communication line 1140 may be a peripheral component interconnection standard (peripheral component interconnect, PCI for short) bus or an extended industry standard architecture (extended industry standard architecture) , Referred to as EISA) bus and so on. The communication line 1140 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is used to represent in FIG. 11, but it does not mean that there is only one bus or one type of bus.

Exemplarily, when the device 1100 implements the function of the first terminal in the previous process:

The communication interface 1110 is used to receive management notification messages; the management notification messages are used to notify management operations of the first software; the management operations include updating the first software, installing the first software, and uninstalling the first software. Any item in a piece of software;

The processor 1120 is configured to, according to the management policy corresponding to the first software, determine that the authentication terminal includes the first terminal and the second terminal, authenticate the user who confirms the management of the first software through the authentication terminal; When it is determined that the user is an authorized user who manages the first software, and the first confirmation instruction input by the user is obtained, and the second confirmation instruction from the second terminal is received, according to the first confirmation An instruction and the second confirmation instruction to perform the management operation indicated by the management notification message on the first software;

The processor 1120 is specifically configured to:

Before the authentication of the user confirming the management of the first software, the processor 1120 is further configured to:

Before the authentication of the user confirming to manage the first software through the authentication terminal, the processor 1120 is further configured to:

When it is determined that the authorization mode of the first software is the first mode, or the authorization mode of the first software is determined to be the second mode, and the first software is the first management operation, it is determined that it needs to pass The authentication terminal authenticates the user.

In a possible implementation manner, the processor 1120 is specifically configured to:

The processor 1120 is further configured to:

In a possible implementation manner, before the receiving the management notification message, the communication interface 1110 is further configured to:

Or receive the management policy from the network device.

Exemplarily, when the device 1100 implements the function of the second terminal in the previous process:

The communication interface 1110 is used to receive the management notification message; the management notification message is used to notify the management operation of the first software; the management operation includes updating the first software, installing the first software, and uninstalling the first software. Any item of the first software;

The processor 1120 is configured to, when it is determined that the authentication terminal includes the second terminal according to the management policy corresponding to the first software, authenticate the user who is confirmed to manage the first software;

In a possible implementation manner, the communication interface 1110 is further used for:

Or receive the management policy from the network device.

In a possible implementation manner, the management policy includes first information, and the first information is used to indicate the authentication terminal; the processor 1120 determines the The authentication terminal is the second terminal.

In a possible implementation manner, the management policy includes third information, and the third information is used to indicate the authorized user; the processor 1120 is further configured to:

Exemplarily, when the apparatus 1100 implements the function of the network device in the previous process:

The processor 1120 is configured to determine an authentication terminal according to a management policy corresponding to the first software when it is determined to perform a management operation on the first software, where the authentication terminal is used to authenticate a user who has confirmed the management of the first software; The authentication terminal includes a first terminal and a second terminal; the management operation includes any one of updating the first software, installing the first software, and uninstalling the first software;

The communication interface 1110 is configured to send a management notification message to the authentication terminal, where the management notification message is used to notify the first software to perform the management operation.

In a possible implementation manner, before the determining to perform a management operation on the first software, the communication interface 1110 is further used for:

Sending the management policy to the first terminal and the second terminal;

The processor 1120 is specifically configured to:

In a possible implementation manner, the management policy includes first information, and the first information is used to indicate the authentication terminal; the processor 1120 determines the Authentication terminal.

The embodiment of the present application also provides a system. For details, refer to FIG. 12. The system 1200 includes a network device 1201, a first terminal 1202, and a second terminal 1203.

The network device 1201 is configured to determine an authentication terminal according to a management policy corresponding to the first software when determining to perform a management operation on the first software, and the authentication terminal is used to authenticate a user who has confirmed the management of the first software; The authentication terminal includes a first terminal and a second terminal; a management notification message is sent to the authentication terminal, and the management notification message is used to notify the management operation of the first software; the management operation includes updating the Any one of the first software, installing the first software, and uninstalling the first software;

The second terminal 1203 is configured to receive the management notification message; when it is determined that the authentication terminal includes the second terminal according to the management policy corresponding to the first software, authenticate the user who confirms the management of the first software; when it is determined When the user is an authorized user who manages the first software, a second confirmation instruction input by the user is sent to the first terminal, where the second confirmation instruction is used to instruct the user to use the second terminal Confirming that the management operation indicated by the management notification message is performed on the first software;

The first terminal 1202 is configured to receive the management notification message; when it is determined that the authentication terminal includes the first terminal and the second terminal according to the management policy corresponding to the first software, the authentication terminal is used to confirm the management office The user of the first software is authenticated; when it is determined that the user is an authorized user who manages the first software, and the first confirmation instruction input by the user is obtained, and the second terminal is received from the second terminal. When confirming the instruction, perform the management operation indicated by the management notification message on the first software according to the first confirmation instruction and the second confirmation instruction; wherein, the first confirmation instruction is used to instruct the The user confirms to perform the management operation on the first software through the first terminal.

The network device 1201, the first terminal 1202, and the second terminal 1203 may also execute other content. For details, reference may be made to the foregoing description, which will not be repeated here.

Those skilled in the art should understand that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, this application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, optical storage, etc.) containing computer-usable program codes.

This application is described with reference to flowcharts and/or block diagrams of methods, equipment (systems), and computer program products according to this application. It should be understood that each process and/or block in the flowchart and/or block diagram, and the combination of processes and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing equipment to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing equipment are used to generate It is a device that realizes the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device. The device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

Obviously, those skilled in the art can make various changes and modifications to the application without departing from the scope of the application. In this way, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalent technologies, then this application is also intended to include these modifications and variations.

Claims

A software management system, characterized in that it includes:

The network device is configured to determine an authentication terminal according to a management policy corresponding to the first software when determining to perform a management operation on the first software, and the authentication terminal is used to authenticate a user who has confirmed the management of the first software; The authentication terminal includes a first terminal and a second terminal; a management notification message is sent to the authentication terminal, the management notification message is used to notify the management operation of the first software; the management operation includes updating the first software 1. Software, any one of installing the first software and uninstalling the first software;

The second terminal is configured to receive the management notification message; when it is determined that the authentication terminal includes the second terminal according to the management policy corresponding to the first software, authenticate the user who confirms the management of the first software; when When it is determined that the user is an authorized user who manages the first software, a second confirmation instruction input by the user is sent to the first terminal, and the second confirmation instruction is used to instruct the user to pass the second The terminal confirms that the management operation indicated by the management notification message is performed on the first software;

The first terminal is configured to receive the management notification message; when it is determined that the authentication terminal includes the first terminal and the second terminal according to the management policy corresponding to the first software, the authentication terminal is used to confirm management The user of the first software is authenticated; when it is determined that the user is an authorized user who manages the first software, and the first confirmation instruction input by the user is obtained, and the first confirmation instruction from the second terminal is received 2. When confirming the instruction, perform the management operation indicated by the management notification message on the first software according to the first confirmation instruction and the second confirmation instruction; wherein, the first confirmation instruction is used to instruct all The user confirms the execution of the management operation on the first software through the first terminal.
The system according to claim 1, wherein the management policy includes first information, and the first information is used to indicate the authentication terminal;

The determining the authentication terminal according to the management policy corresponding to the first software includes:

The authentication terminal is determined according to the first information in the management policy.
The system according to any one of claims 1 to 2, wherein the management policy includes second information, and the second information is used to indicate the authorization mode of the first software;

Before the first terminal authenticates the user confirming to manage the first software, the method further includes:

Determining the authorization mode of the first software according to the second information in the management policy;

It is determined according to the authorization mode that the user needs to be authenticated by the authentication terminal.
The system according to claim 3, wherein the authorization mode includes a first mode and a second mode, and the first mode is that each management operation of the first software requires passing the authentication terminal Authenticate the user;

The second mode is that the first management operation of the first software needs to authenticate the user through the authentication terminal, and the management operations after the first management operation of the first software do not need to pass the The authentication terminal authenticates the user;

The first terminal is specifically configured to:

When it is determined that the authorization mode of the first software is the first mode, or the authorization mode of the first software is determined to be the second mode, and the first software is the first management operation, it is determined that it needs to pass The authentication terminal authenticates the user.
The system according to any one of claims 1 to 4, wherein the first terminal is specifically configured to:

Obtain the first authorization information entered by the user in the first terminal, and obtain the second authorization information from the second terminal; the first authorization information includes the information entered by the user in the first terminal Authentication information, where the second authorization information includes authentication information input by the user to the second terminal;

When the first authorization information matches the authorization information pre-configured in the first terminal, and the first authorization information or the pre-configured authorization information matches the second authorization information, it is determined The user is the authorized user.
The system according to any one of claims 1 to 5, wherein the management policy includes third information, and the third information is used to indicate the authorized user;

Before the first terminal authenticates the user confirming to manage the first software, it is also used to:

The authorized user is determined according to the third information in the management policy.
The system according to any one of claims 1 to 6, wherein before the first terminal receives the management notification message, it is further used for:

Acquiring the management policy set by the authorized user, and sending the management policy to the network device;

Or receive the management policy from the network device.
The system according to any one of claims 1 to 7, wherein the second terminal is specifically configured to:

Acquiring second authorization information entered by the user in the second terminal; the second authorization information includes authentication information entered by the user in the second terminal;

When the first authorization information matches the authorization information pre-configured in the second terminal, it is determined that the user is the authorized user.
The system according to any one of claims 1 to 8, wherein the second terminal is further configured to:

Acquiring the management policy set by the authorized user, and sending the management policy to the network device;

Or receive the management policy from the network device.
The system according to any one of claims 1 to 9, wherein the first terminal is a vehicle-mounted terminal, and the second terminal is a mobile terminal.
A software management method, characterized in that it comprises:

The first terminal receives a management notification message; the management notification message is used to notify the management operation of the first software; the management operation includes updating the first software, installing the first software, and uninstalling the first software. Any of

When the first terminal determines that the authentication terminal includes the first terminal and the second terminal according to the management policy corresponding to the first software, the user who confirms the management of the first software is authenticated through the authentication terminal;

When it is determined that the user is an authorized user who manages the first software, and the first confirmation instruction input by the user is obtained, and the second confirmation instruction from the second terminal is received, the first terminal Performing the management operation indicated by the management notification message on the first software according to the first confirmation instruction and the second confirmation instruction;

The first confirmation instruction is used to instruct the user to confirm the execution of the management operation on the first software through the first terminal.
The method according to claim 11, wherein the management policy includes first information, and the first information is used to indicate the authentication terminal;

The first terminal determines that the authentication terminal includes the first terminal and the second terminal according to the management policy corresponding to the first software, including:

The first terminal determines, according to the first information in the management policy corresponding to the first software, that the authentication terminal includes the first terminal and the second terminal.
The method according to any one of claims 11 to 12, wherein the management policy includes second information, and the second information is used to indicate the authorization mode of the first software;

Before the first terminal authenticates the user confirming to manage the first software, the method further includes:

Determining, by the first terminal, the authorization mode of the first software according to the second information in the management policy;

The first terminal determines according to the authorization mode that the user needs to be authenticated by the authentication terminal.
The method according to claim 13, wherein the authorization mode includes a first mode and a second mode, and the first mode is that each management operation of the first software needs to pass the authentication terminal Authenticate the user;

The second mode is that the first management operation of the first software needs to authenticate the user through the authentication terminal, and the management operations after the first management operation of the first software do not need to pass the The authentication terminal authenticates the user;

Before the first terminal authenticates the user confirming to manage the first software through the authentication terminal, the method further includes:

When it is determined that the authorization mode of the first software is the first mode, or the authorization mode of the first software is determined to be the second mode, and the first software is the first management operation, it is determined that it needs to pass The authentication terminal authenticates the user.
The method according to any one of claims 11 to 14, wherein the determining that the user is an authorized user who manages the first software comprises:

The first terminal obtains the first authorization information input by the user in the first terminal, and obtains the second authorization information from the second terminal; the first authorization information includes the user input to the The authentication information of the first terminal, where the second authorization information includes the authentication information input by the user to the second terminal;

When the first authorization information matches the authorization information pre-configured in the first terminal, and the first authorization information or the pre-configured authorization information matches the second authorization information, the The first terminal determines that the user is the authorized user.
The method according to any one of claims 11 to 15, wherein the management policy includes third information, and the third information is used to indicate the authorized user;

Before the first terminal authenticates the user confirming to manage the first software through the authentication terminal, the method further includes:

The first terminal determines the authorized user according to the third information in the management policy.
The method according to any one of claims 11 to 16, wherein before the first terminal receives the management notification message, the method further comprises:

Acquiring, by the first terminal, the management policy set by the authorized user, and sending the management policy to the network device;

Or the first terminal receives the management policy from the network device.
The method according to any one of claims 11 to 17, wherein the first terminal is a vehicle-mounted terminal, and the second terminal is a mobile terminal.
A software management method, characterized in that it comprises:

The second terminal receives the management notification message; the management notification message is used to notify the management operation of the first software; the management operation includes updating the first software, installing the first software, and uninstalling the first software. Any item in the software;

When the second terminal determines that the authentication terminal includes the second terminal according to the management policy corresponding to the first software, authenticate the user who is confirmed to manage the first software;

When it is determined that the user is an authorized user who manages the first software, the second terminal sends a second confirmation instruction input by the user to the first terminal, and the second confirmation instruction is used to instruct the user to pass The second terminal confirms that the management operation indicated by the management notification message is performed on the first software.
The method according to claim 19, wherein the determining by the second terminal that the user is an authorized user who manages the first software comprises:

Acquiring, by the second terminal, second authorization information input by the user in the second terminal; the second authorization information includes authentication information input by the user to the second terminal;

When the first authorization information matches the authorization information pre-configured in the second terminal, the second terminal determines that the user is the authorized user who manages the first software.
The method according to claim 19 or 20, wherein the method further comprises:

Acquiring, by the second terminal, the management policy set by the authorized user, and sending the management policy to the network device;

Or the second terminal receives the management policy from the network device.
A communication device, characterized in that it comprises:

The communication unit is configured to receive management notification messages; the management notification messages are used to notify management operations of the first software; the management operations include updating the first software, installing the first software, and uninstalling the first software. Any item in the software;

The processing unit is configured to: when it is determined that the authentication terminal includes the first terminal and the second terminal according to the management policy corresponding to the first software, authenticate the user who confirms the management of the first software through the authentication terminal; When the user is an authorized user who manages the first software and obtains the first confirmation instruction input by the user and receives the second confirmation instruction from the second terminal, according to the first confirmation instruction And the second confirmation instruction to perform the management operation indicated by the management notification message on the first software;

The first confirmation instruction is used to instruct the user to confirm the execution of the management operation on the first software.
The apparatus according to claim 22, wherein the management policy comprises first information, and the first information is used to indicate the authentication terminal;

The processing unit is specifically used for:

The first terminal determines, according to the first information in the management policy corresponding to the first software, that the authentication terminal includes the first terminal and the second terminal.
The device according to any one of claims 22 to 23, wherein the management policy comprises second information, and the second information is used to indicate the authorization mode of the first software;

Before the authentication of the user confirming the management of the first software, the processing unit is further configured to:

Determining the authorization mode of the first software according to the second information in the management policy;

It is determined according to the authorization mode that the user needs to be authenticated by the authentication terminal.
The device according to claim 24, wherein the authorization mode includes a first mode and a second mode, the first mode is that each management operation of the first software requires the authentication terminal Authenticate the user;

The second mode is that the first management operation of the first software needs to authenticate the user through the authentication terminal, and the management operations after the first management operation of the first software do not need to pass the The authentication terminal authenticates the user;

Before the authentication of the user confirming the management of the first software through the authentication terminal, the processing unit is further configured to:

When it is determined that the authorization mode of the first software is the first mode, or the authorization mode of the first software is determined to be the second mode, and the first software is the first management operation, it is determined that it needs to pass The authentication terminal authenticates the user.
The device according to any one of claims 22 to 25, wherein the processing unit is specifically configured to:

Obtain the first authorization information entered by the user in the first terminal, and obtain the second authorization information from the second terminal; the first authorization information includes the information entered by the user in the first terminal Authentication information, where the second authorization information includes authentication information input by the user to the second terminal;

When the first authorization information matches the authorization information pre-configured in the first terminal, and the first authorization information or the pre-configured authorization information matches the second authorization information, it is determined The user is the authorized user.
The device according to any one of claims 22 to 26, wherein the management policy includes third information, and the third information is used to indicate the authorized user;

The processing unit is also used for:

The authorized user is determined according to the third information in the management policy.
The apparatus according to any one of claims 22 to 27, wherein before the receiving the management notification message, the communication unit is further configured to:

Acquiring the management policy set by the authorized user, and sending the management policy to the network device;

Or receive the management policy from the network device.
The device according to any one of claims 22 to 28, wherein the communication device is a vehicle-mounted terminal, and the second terminal is a mobile terminal.
A communication device, characterized in that it comprises:

The communication unit is configured to receive the management notification message; the management notification message is used to notify the management operation of the first software; the management operation includes updating the first software, installing the first software, and uninstalling the first software. Any item in the first software;

A processing unit, configured to authenticate the user confirming to manage the first software when it is determined that the authentication terminal includes the second terminal according to the management policy corresponding to the first software;

When it is determined that the user is an authorized user who manages the first software, the second terminal sends a second confirmation instruction input by the user to the first terminal, and the second confirmation instruction is used to instruct the user to confirm Performing the management operation indicated by the management notification message on the first software.
The device according to claim 30, wherein the processing unit is specifically configured to:

Acquiring second authorization information entered by the user in the second terminal; the second authorization information includes authentication information entered by the user in the second terminal;

When the first authorization information matches the authorization information pre-configured in the second terminal, it is determined that the user is the authorized user who manages the first software.
The device according to claim 30 or 31, wherein the communication unit is further configured to:

Acquiring the management policy set by the authorized user, and sending the management policy to the network device;

Or receive the management policy from the network device.
A computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program runs on a computer, the computer executes any one of claims 11-18 The method, or the computer is caused to execute the method according to any one of claims 19-21.
A communication device, characterized in that, the communication device includes:

Communication interface, used to communicate with other devices;

A processor, coupled with the communication interface, to enable the communication device to execute the method according to any one of claims 11 to 18, or to enable the communication device to execute the method according to any one of claims 19 to 21 Methods.
A computer program product, characterized in that the computer program product comprises a computer program, when the computer program runs on a computer, the computer is caused to execute the method according to any one of claims 11 to 18, or The computer executes the method according to any one of claims 19-21.